Revert to 3.4.7...for now?

git-svn-id: svn://svn.debian.org/svn/pkg-samba/trunk/samba@3416 fc4039ab-9d04-0410-8cac-899223bdd6b0
author: bubulle <bubulle@alioth.debian.org> 2010-04-06 18:12:47 +0000
committer: bubulle <bubulle@alioth.debian.org> 2010-04-06 18:12:47 +0000
commit: c038a4e9c09ba4ac77d885ac0afee418f41b8891 (patch)
tree: f5b2444727ff995f46dabbbf94863e9926501444 /docs/htmldocs
parent: 9e2f5a6ab663f7a111832217c527508c75ddae8a (diff)
download: samba-c038a4e9c09ba4ac77d885ac0afee418f41b8891.tar.gz
452 files changed, 52115 insertions, 10596 deletions
diff --git a/docs/htmldocs/Samba3-ByExample/net2000users.html b/docs/htmldocs/Samba3-ByExample/2000users.html
index c12e5abb70..5ba3718066 100644
--- a/docs/htmldocs/Samba3-ByExample/net2000users.html
+++ b/docs/htmldocs/Samba3-ByExample/2000users.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�6.�A Distributed 2000-User Network</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="happy.html" title="Chapter�5.�Making Happy Users"><link rel="next" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�6.�A Distributed 2000-User Network</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="happy.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="DMSMig.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="net2000users"></a>Chapter�6.�A Distributed 2000-User Network</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="net2000users.html#id2583726">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2583756">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2583824">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2584098">Technical Issues</a></span></dt><dt><span class="sect2"><a href="net2000users.html#id2585046">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2585064">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2588223">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2588370">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�6.�A Distributed 2000-User Network</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="happy.html" title="Chapter�5.�Making Happy Users"><link rel="next" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�6.�A Distributed 2000-User Network</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="happy.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="DMSMig.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="2000users"></a>Chapter�6.�A Distributed 2000-User Network</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="2000users.html#id2583740">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2583770">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2583839">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2584112">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2585057">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2585074">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2588234">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2588381">Questions and Answers</a></span></dt></dl></div><p>
 There is something indeed mystical about things that are
 big. Large networks exhibit a certain magnetism and exude a sense of
 importance that obscures reality. You and I know that it is no more
@@ -30,7 +30,7 @@ implementing a DNS or a DHCP server are under control. Even the basics of
 Samba are largely under control. So in this section you focus on the
 specifics of implementing LDAP changes, Samba changes, and approach and
 design of the solution and its deployment.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583726"></a>Introduction</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583740"></a>Introduction</h2></div></div></div><p>
 Abmas is a miracle company. Most businesses would have collapsed under
 the weight of rapid expansion that this company has experienced. Samba 
 is flexible, so there is no need to reinstall the whole operating 
@@ -39,19 +39,19 @@ you can keep an old server running right up to the moment of cutover
 and then do a near-live conversion. There is no need to reinstall a 
 Samba server just to change the way your network should function.
 </p><p>
-<a class="indexterm" name="id2583745"></a>
+<a class="indexterm" name="id2583759"></a>
 Network growth is common to all organizations. In this exercise,
 your preoccupation is with the mechanics of implementing Samba and
 LDAP so that network users on each network segment can work
 without impediment.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583756"></a>Assignment Tasks</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583770"></a>Assignment Tasks</h3></div></div></div><p>
 	Starting with the configuration files for the server called
 	<code class="constant">MASSIVE</code> in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, you now deal with the
 	issues that are particular to large distributed networks. Your task
 	is simple  identify the challenges, consider the 
 	alternatives, and then design and implement a solution.
 	</p><p>
-	<a class="indexterm" name="id2583784"></a>
+	<a class="indexterm" name="id2583798"></a>
 	Remember, you have users based in London (UK), Los Angeles,
 	Washington. DC, and, three buildings in New York. A significant portion
 	of your workforce have notebook computers and roam all over the
@@ -72,18 +72,18 @@ without impediment.
 	You have outsourced all desktop deployment and management to
 	DirectPointe. Your concern is server maintenance and third-level
 	support. Build a plan and show what must be done.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583824"></a>Dissection and Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2583832"></a>
-<a class="indexterm" name="id2583839"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583839"></a>Dissection and Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2583847"></a>
+<a class="indexterm" name="id2583854"></a>
 In <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, you implemented an LDAP server that provided the
 <em class="parameter"><code>passdb backend</code></em> for the Samba servers. You
 explored ways to accelerate Windows desktop profile handling and you
 took control of network performance.
 </p><p>
-<a class="indexterm" name="id2583864"></a>
-<a class="indexterm" name="id2583871"></a>
 <a class="indexterm" name="id2583878"></a>
-<a class="indexterm" name="id2583884"></a>
+<a class="indexterm" name="id2583885"></a>
+<a class="indexterm" name="id2583892"></a>
+<a class="indexterm" name="id2583899"></a>
 The implementation of an LDAP-based passdb backend (known as
 <span class="emphasis"><em>ldapsam</em></span> in Samba parlance), or some form of database
 that can be distributed, is essential to permit the deployment of Samba
@@ -96,8 +96,8 @@ using a tool such as <code class="literal">rsync</code>, but
 support the range of account facilities demanded by modern network
 managers.
 </p><p>
-<a class="indexterm" name="id2583924"></a>
-<a class="indexterm" name="id2583931"></a>
+<a class="indexterm" name="id2583938"></a>
+<a class="indexterm" name="id2583945"></a>
 The new <span class="emphasis"><em>tdbsam</em></span> facility supports functionality
 that is similar to an <span class="emphasis"><em>ldapsam</em></span>, but the lack of
 distributed infrastructure sorely limits the scope for its
@@ -105,10 +105,10 @@ deployment. This raises the following questions: Why can't I just use
 an XML-based backend, or for that matter, why not use an SQL-based
 backend? Is support for these tools broken? Answers to these
 questions require a bit of background.</p><p>
-<a class="indexterm" name="id2583954"></a>
-<a class="indexterm" name="id2583961"></a>
-<a class="indexterm" name="id2583968"></a>
-<a class="indexterm" name="id2583975"></a>
+<a class="indexterm" name="id2583969"></a>
+<a class="indexterm" name="id2583976"></a>
+<a class="indexterm" name="id2583982"></a>
+<a class="indexterm" name="id2583990"></a>
 <span class="emphasis"><em>What is a directory?</em></span> A directory is a
 collection of information regarding objects that can be accessed to
 rapidly find information that is relevant in a particular and
@@ -116,19 +116,19 @@ consistent manner. A directory differs from a database in that it is
 generally more often searched (read) than updated. As a consequence, the
 information is organized to facilitate read access rather than to
 support transaction processing.</p><p>
-<a class="indexterm" name="id2583995"></a>
-<a class="indexterm" name="id2584005"></a>
-<a class="indexterm" name="id2584012"></a>
-<a class="indexterm" name="id2584019"></a>
+<a class="indexterm" name="id2584010"></a>
+<a class="indexterm" name="id2584020"></a>
+<a class="indexterm" name="id2584026"></a>
+<a class="indexterm" name="id2584033"></a>
 The Lightweight Directory Access Protocol (LDAP) differs
 considerably from a traditional database. It has a simple search
 facility that uniquely makes a highly preferred mechanism for managing
 user identities. LDAP provides a scalable mechanism for distributing
 the data repository and for keeping all copies (slaves) in sync with
 the master repository.</p><p>
-<a class="indexterm" name="id2584035"></a>
-<a class="indexterm" name="id2584042"></a>
 <a class="indexterm" name="id2584049"></a>
+<a class="indexterm" name="id2584056"></a>
+<a class="indexterm" name="id2584063"></a>
 Samba is a flexible and powerful file and print sharing
 technology. It can use many external authentication sources and can be
 part of a total authentication and identity management
@@ -136,7 +136,7 @@ infrastructure. The two most important external sources for large sites
 are Microsoft Active Directory and LDAP. Sites that specifically wish to
 avoid the proprietary implications of Microsoft Active Directory
 naturally gravitate toward OpenLDAP.</p><p>
-<a class="indexterm" name="id2584066"></a>
+<a class="indexterm" name="id2584080"></a>
 In <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, you had to deal with a locally routed
 network. All deployment concerns focused around making users happy,
 and that simply means taking control over all network practices and
@@ -147,12 +147,12 @@ function. In particular, you must be concerned with users who move
 between offices. You must take into account the way users need to
 access information globally. And you must make the network robust
 enough so that it can sustain partial breakdown without causing loss of
-productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584098"></a>Technical Issues</h3></div></div></div><p>
+productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584112"></a>Technical Issues</h3></div></div></div><p>
 	There are at least three areas that need to be addressed as you
 	approach the challenge of designing a network solution for the newly
 	expanded business:
-	</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2584114"></a>
-		User needs such as mobility and data access</p></li><li><p>The nature of Windows networking protocols</p></li><li><p>Identity management infrastructure needs</p></li></ul></div><p>Let's look at each in turn.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584137"></a>User Needs</h4></div></div></div><p>
+	</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2584128"></a>
+		User needs such as mobility and data access</p></li><li><p>The nature of Windows networking protocols</p></li><li><p>Identity management infrastructure needs</p></li></ul></div><p>Let's look at each in turn.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584151"></a>User Needs</h4></div></div></div><p>
 	The new company has three divisions. Staff for each division are spread across
 	the company. Some staff are office-bound and some are mobile users. Mobile
 	users travel globally. Some spend considerable periods working in other offices.
@@ -163,7 +163,7 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	curtail user needs. Parts of the global Internet infrastructure remain shielded
 	off for reasons outside the scope of this discussion.
 	</p><p>
-	<a class="indexterm" name="id2584162"></a>
+	<a class="indexterm" name="id2584176"></a>
 	Decisions must be made regarding where data is to be stored, how it will be
 	replicated (if at all), and what the network bandwidth implications are. For
 	example, one decision that can be made is to give each office its own master
@@ -174,8 +174,8 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	This way, they can synchronize all files that have changed since each logon
 	to the network.
 	</p><p>
-	<a class="indexterm" name="id2584188"></a>
-	<a class="indexterm" name="id2584198"></a>
+	<a class="indexterm" name="id2584203"></a>
+	<a class="indexterm" name="id2584212"></a>
 	No matter which way you look at this, the bandwidth requirements
 	for acceptable performance are substantial even if only 10 percent of
 	staff are global data users. A company with 3,500 employees,
@@ -188,11 +188,11 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	profile involves a transfer of over 750 KB from the profile
 	server to and from the client.
 	</p><p>
-	<a class="indexterm" name="id2584219"></a>
+	<a class="indexterm" name="id2584233"></a>
 	Obviously then, user needs and wide-area practicalities dictate the economic and
 	technical aspects of your network design as well as for standard operating procedures.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584231"></a>The Nature of Windows Networking Protocols</h4></div></div></div><p>
-	<a class="indexterm" name="id2584239"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584245"></a>The Nature of Windows Networking Protocols</h4></div></div></div><p>
+	<a class="indexterm" name="id2584254"></a>
 	Network logons that include roaming profile handling requires from 140 KB to 2 MB.
 	The inclusion of support for a minimal set of common desktop applications can push
 	the size of a complete profile to over 15 MB. This has substantial implications
@@ -200,8 +200,8 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	determining the nature and style of mandatory profiles that may be enforced as
 	part of a total service-level assurance program that might be implemented.
 	</p><p>
-	<a class="indexterm" name="id2584260"></a>
-	<a class="indexterm" name="id2584267"></a>
+	<a class="indexterm" name="id2584274"></a>
+	<a class="indexterm" name="id2584281"></a>
 	One way to reduce the network bandwidth impact of user logon
 	traffic is through folder redirection. In <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, you
 	implemented this in the new Windows XP Professional standard
@@ -210,14 +210,14 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	also be excluded from synchronization to and from the server on
 	logon or logout. Redirected folders are analogous to network drive
 	connections.
-	</p><p><a class="indexterm" name="id2584294"></a>
+	</p><p><a class="indexterm" name="id2584309"></a>
 	Of course, network applications should only be run off
 	local application servers. As a general rule, even with 2 Mb/sec
 	network bandwidth, it would not make sense at all for someone who
 	is working out of the London office to run applications off a
 	server that is located in New York.
 	</p><p>
-	<a class="indexterm" name="id2584310"></a>
+	<a class="indexterm" name="id2584324"></a>
 	When network bandwidth becomes a precious commodity (that is most
 	of the time), there is a significant demand to understand network
 	processes and to mold the limits of acceptability around the
@@ -226,15 +226,15 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	When a Windows NT4/200x/XP Professional client user logs onto
 	the network, several important things must happen.
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2584332"></a>
+		<a class="indexterm" name="id2584347"></a>
 		The client obtains an IP address via DHCP. (DHCP is
 		necessary so that users can roam between offices.)
 		</p></li><li><p>
-		<a class="indexterm" name="id2584345"></a>
-		<a class="indexterm" name="id2584352"></a>
+		<a class="indexterm" name="id2584360"></a>
+		<a class="indexterm" name="id2584366"></a>
 		The client must register itself with the WINS and/or DNS server.
 		</p></li><li><p>
-		<a class="indexterm" name="id2584364"></a>
+		<a class="indexterm" name="id2584379"></a>
 		The client must locate the closest domain controller.
 		</p></li><li><p>
 		The client must log onto a domain controller and obtain as part of
@@ -256,15 +256,15 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	name both by broadcast and Unicast registration that is directed
 	at the WINS server.
 	</p><p>
-	<a class="indexterm" name="id2584411"></a>
-	<a class="indexterm" name="id2584418"></a><a class="indexterm" name="id2584427"></a>
+	<a class="indexterm" name="id2584426"></a>
+	<a class="indexterm" name="id2584432"></a><a class="indexterm" name="id2584442"></a>
 	Given that the client is already a domain member, it then sends
 	a directed (Unicast) request to the WINS server seeking the list of
 	IP addresses for domain controllers (NetBIOS name type 0x1C). The
 	WINS server replies with the information requested.</p><p>
-	<a class="indexterm" name="id2584442"></a>
-	<a class="indexterm" name="id2584451"></a>
-	<a class="indexterm" name="id2584458"></a>
+	<a class="indexterm" name="id2584456"></a>
+	<a class="indexterm" name="id2584465"></a>
+	<a class="indexterm" name="id2584472"></a>
 	The client sends two netlogon mailslot broadcast requests
 	to the local network and to each of the IP addresses returned by
 	the WINS server. Whichever answers this request first appears to
@@ -274,9 +274,9 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	was listed in the WINS server response to a request for the list of
 	domain controllers.
 	</p><p>
-	<a class="indexterm" name="id2584476"></a>
-	<a class="indexterm" name="id2584485"></a>
-	<a class="indexterm" name="id2584492"></a>
+	<a class="indexterm" name="id2584498"></a>
+	<a class="indexterm" name="id2584507"></a>
+	<a class="indexterm" name="id2584514"></a>
 	The logon process begins with negotiation of the SMB/CIFS
 	protocols that are to be used; this is followed by an exchange of
 	information that ultimately includes the client sending the
@@ -287,10 +287,10 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	needs. A secondary fact we need to know is, what happens when
 	local domain controllers fail or break?
 	</p><p>
-	<a class="indexterm" name="id2584511"></a>
-	<a class="indexterm" name="id2584518"></a>
-	<a class="indexterm" name="id2584525"></a>
-	<a class="indexterm" name="id2584531"></a>
+	<a class="indexterm" name="id2584534"></a>
+	<a class="indexterm" name="id2584541"></a>
+	<a class="indexterm" name="id2584547"></a>
+	<a class="indexterm" name="id2584554"></a>
 	Under most circumstances, the nearest domain controller
 	responds to the netlogon mailslot broadcast. The exception to this
 	norm occurs when the nearest domain controller is too busy or is out
@@ -299,18 +299,18 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	domain controllers. Since there can be only one PDC, all additional
 	domain controllers are by definition BDCs.
 	</p><p>
-	<a class="indexterm" name="id2584549"></a>
-	<a class="indexterm" name="id2584556"></a>
+	<a class="indexterm" name="id2584571"></a>
+	<a class="indexterm" name="id2584578"></a>
 	The provision of sufficient servers that are BDCs is an
 	important design factor. The second important design factor
 	involves how each of the BDCs obtains user authentication
 	data. That is the subject of the next section, which involves key
 	decisions regarding Identity Management facilities.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584570"></a>Identity Management Needs</h4></div></div></div><p>
-	<a class="indexterm" name="id2584578"></a>
-	<a class="indexterm" name="id2584584"></a>
-	<a class="indexterm" name="id2584591"></a>
-	<a class="indexterm" name="id2584598"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2584592"></a>Identity Management Needs</h4></div></div></div><p>
+	<a class="indexterm" name="id2584600"></a>
+	<a class="indexterm" name="id2584607"></a>
+	<a class="indexterm" name="id2584614"></a>
+	<a class="indexterm" name="id2584621"></a>
 	Network managers recognize that in large organizations users
 	generally need to be given resource access based on needs, while
 	being excluded from other resources for reasons of privacy. It is
@@ -319,9 +319,9 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	by which user credentials are validated and filtered and appropriate
 	rights and privileges are allocated.
 	</p><p>
-	<a class="indexterm" name="id2584616"></a>
-	<a class="indexterm" name="id2584622"></a>
-	<a class="indexterm" name="id2584629"></a>
+	<a class="indexterm" name="id2584638"></a>
+	<a class="indexterm" name="id2584645"></a>
+	<a class="indexterm" name="id2584652"></a>
 	Unfortunately, network resources tend to have their own Identity 
 	Management facilities, the quality and manageability of which varies 
 	from quite poor to exceptionally good. Corporations that use a mixture 
@@ -333,7 +333,7 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	What was once called <code class="constant">Yellow Pages</code> is today known 
 	as <code class="constant">Network Information System</code> (NIS).
 	</p><p>
-	<a class="indexterm" name="id2584660"></a>
+	<a class="indexterm" name="id2584683"></a>
 	NIS gained a strong following throughout the UNIX/VMS space in a short
 	period of time and retained that appeal and use for over a decade.
 	Security concerns and inherent limitations have caused it to enter its
@@ -343,9 +343,9 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	demands as the demand for directory services that can be coupled with
 	other information systems is catching on.
 	</p><p>
-	<a class="indexterm" name="id2584679"></a>
-	<a class="indexterm" name="id2584686"></a>
-	<a class="indexterm" name="id2584693"></a>
+	<a class="indexterm" name="id2584702"></a>
+	<a class="indexterm" name="id2584708"></a>
+	<a class="indexterm" name="id2584715"></a>
 	Nevertheless, both NIS and NIS+ continue to hold ground in
 	business areas where UNIX still has major sway. Examples of
 	organizations that remain firmly attached to the use of NIS and
@@ -353,14 +353,14 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	and large corporations that have a scientific or engineering
 	focus.
 	</p><p>
-	<a class="indexterm" name="id2584708"></a>
-	<a class="indexterm" name="id2584715"></a>
+	<a class="indexterm" name="id2584731"></a>
+	<a class="indexterm" name="id2584737"></a>
 	Today's networking world needs a scalable, distributed Identity 
 	Management infrastructure, commonly called a directory. The most 
 	popular technologies today are Microsoft Active Directory service 
 	and a number of LDAP implementations.
 	</p><p>
-	<a class="indexterm" name="id2584729"></a>
+	<a class="indexterm" name="id2584752"></a>
 	The problem of managing multiple directories has become a focal
 	point over the past decade, creating a large market for
 	metadirectory products and services that allow organizations that
@@ -369,15 +369,15 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	another. The attendant benefit to end users is the promise of
 	having to remember and deal with fewer login identities and
 	passwords.</p><p>
-	<a class="indexterm" name="id2584747"></a>
+	<a class="indexterm" name="id2584769"></a>
 	The challenge of every large network is to find the optimum
 	balance of internal systems and facilities for Identity
 	Management resources. How well the solution is chosen and
 	implemented has potentially significant impact on network bandwidth
 	and systems response needs.</p><p>
-	<a class="indexterm" name="id2584764"></a>
-	<a class="indexterm" name="id2584771"></a>
-	<a class="indexterm" name="id2584780"></a>
+	<a class="indexterm" name="id2584786"></a>
+	<a class="indexterm" name="id2584793"></a>
+	<a class="indexterm" name="id2584802"></a>
 	In <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, you implemented a single LDAP server for the
 	entire network. This may work for smaller networks, but almost
 	certainly fails to meet the needs of large and complex networks. The
@@ -386,11 +386,11 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	What is the best method for implementing master/slave LDAP
 	servers within the context of a distributed 2,000-user network is a
 	question that remains to be answered.</p><p>
-	<a class="indexterm" name="id2584809"></a>
-	<a class="indexterm" name="id2584816"></a>
+	<a class="indexterm" name="id2584832"></a>
+	<a class="indexterm" name="id2584838"></a>
 	One possibility that has great appeal is to create a single,
 	large distributed domain. The practical implications of this
-	design (see <a class="link" href="net2000users.html#chap7net" title="Figure�6.6.�Network Topology 2000 User Complex Design A">&#8220;Network Topology  2000 User Complex Design A&#8221;</a>) demands the placement of
+	design (see <a class="link" href="2000users.html#chap7net" title="Figure�6.6.�Network Topology 2000 User Complex Design A">&#8220;Network Topology  2000 User Complex Design A&#8221;</a>) demands the placement of
 	sufficient BDCs in each location. Additionally, network
 	administrators must make sure that profiles are not transferred
 	over the wide-area links, except as a totally unavoidable
@@ -398,8 +398,8 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	productivity against the cost of network management and
 	maintenance.
 	</p><p>
-	<a class="indexterm" name="id2584847"></a>
-	The network design in <a class="link" href="net2000users.html#chap7net2" title="Figure�6.7.�Network Topology 2000 User Complex Design B">&#8220;Network Topology  2000 User Complex Design B&#8221;</a> takes the approach
+	<a class="indexterm" name="id2584863"></a>
+	The network design in <a class="link" href="2000users.html#chap7net2" title="Figure�6.7.�Network Topology 2000 User Complex Design B">&#8220;Network Topology  2000 User Complex Design B&#8221;</a> takes the approach
 	that management of networks that are too remote to be managed
 	effectively from New York ought to be given a certain degree of
 	autonomy. With this rationale, the Los Angeles and London networks,
@@ -409,22 +409,22 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	the ability for network users to roam globally without some compromise
 	in how they may access global resources.
 	</p><p>
-	<a class="indexterm" name="id2584873"></a>
+	<a class="indexterm" name="id2584890"></a>
 	Desk-bound users need not be negatively affected by this design, since
 	the use of interdomain trusts can be used to satisfy the need for global
 	data sharing.
 	</p><p>
-	<a class="indexterm" name="id2584886"></a>
-	<a class="indexterm" name="id2584892"></a>
 	<a class="indexterm" name="id2584902"></a>
+	<a class="indexterm" name="id2584909"></a>
+	<a class="indexterm" name="id2584918"></a>
 	When Samba-3 is configured to use an LDAP backend, it stores the domain
 	account information in a directory entry. This account entry contains the
 	domain SID. An unintended but exploitable side effect is that this makes it
 	possible to operate with more than one PDC on a distributed network.
 	</p><p>
-	<a class="indexterm" name="id2584916"></a>
-	<a class="indexterm" name="id2584923"></a>
-	<a class="indexterm" name="id2584930"></a>
+	<a class="indexterm" name="id2584933"></a>
+	<a class="indexterm" name="id2584940"></a>
+	<a class="indexterm" name="id2584947"></a>
 	How might this peculiar feature be exploited? The answer is simple. It is
 	imperative that each network segment have its own WINS server. Major
 	servers on remote network segments can be given a static WINS entry in
@@ -434,8 +434,8 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	same domain SID. Since all domain account information can be stored in a
 	single LDAP backend, users have unfettered ability to roam.
 	</p><p>
-	<a class="indexterm" name="id2584955"></a>
-	<a class="indexterm" name="id2584964"></a>
+	<a class="indexterm" name="id2584972"></a>
+	<a class="indexterm" name="id2584981"></a>
 	This concept has not been exhaustively validated, though we can see no reason
 	why this should not work. The important facets are the following: The name of
 	the domain must be identical in all locations. Each network segment must have
@@ -446,10 +446,10 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	on every network segment. Finally, the BDCs should each use failover LDAP servers
 	that are in fact slave LDAP servers on the local segments.
 	</p><p>
-	<a class="indexterm" name="id2584986"></a>
-	<a class="indexterm" name="id2584995"></a>
-	<a class="indexterm" name="id2585002"></a>
-	<a class="indexterm" name="id2585011"></a>
+	<a class="indexterm" name="id2585003"></a>
+	<a class="indexterm" name="id2585012"></a>
+	<a class="indexterm" name="id2585019"></a>
+	<a class="indexterm" name="id2585028"></a>
 	With a single master LDAP server, all network updates are effected on a single
 	server. In the event that this should become excessively fragile or network
 	bandwidth limiting, one could implement a delegated LDAP domain. This is also
@@ -463,7 +463,7 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	administrators must of necessity follow the same standard
 	procedures for managing the directory, because retroactive correction of
 	inconsistent directory information can be exceedingly difficult.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585046"></a>Political Issues</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585057"></a>Political Issues</h3></div></div></div><p>
 	As organizations grow, the number of points of control increases
 	also. In a large distributed organization, it is important that the
 	Identity Management system be capable of being updated from
@@ -471,25 +471,25 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	become usable in a reasonable period, typically
 	minutes rather than days (the old limitation of highly manual
 	systems).
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2585064"></a>Implementation</h2></div></div></div><p>
-	<a class="indexterm" name="id2585071"></a>
-	<a class="indexterm" name="id2585078"></a>
-	<a class="indexterm" name="id2585085"></a>
-	<a class="indexterm" name="id2585092"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2585074"></a>Implementation</h2></div></div></div><p>
+	<a class="indexterm" name="id2585082"></a>
+	<a class="indexterm" name="id2585089"></a>
+	<a class="indexterm" name="id2585096"></a>
+	<a class="indexterm" name="id2585102"></a>
 	Samba-3 has the ability to use multiple password (authentication and
-	identity resolution) backends. The diagram in <a class="link" href="net2000users.html#chap7idres" title="Figure�6.1.�Samba and Authentication Backend Search Pathways">&#8220;Samba and Authentication Backend Search Pathways&#8221;</a>
+	identity resolution) backends. The diagram in <a class="link" href="2000users.html#chap7idres" title="Figure�6.1.�Samba and Authentication Backend Search Pathways">&#8220;Samba and Authentication Backend Search Pathways&#8221;</a>
 	demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system
 	password database. The diagram only documents the mechanisms for
 	authentication and identity resolution (obtaining a UNIX UID/GID)
 	using the specific systems shown.
 	</p><div class="figure"><a name="chap7idres"></a><p class="title"><b>Figure�6.1.�Samba and Authentication Backend Search Pathways</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap7-idresol.png" width="297" alt="Samba and Authentication Backend Search Pathways"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2585156"></a>
-	<a class="indexterm" name="id2585163"></a>
-	<a class="indexterm" name="id2585170"></a>
-	<a class="indexterm" name="id2585177"></a>
-	<a class="indexterm" name="id2585183"></a>
-	<a class="indexterm" name="id2585190"></a>
-	<a class="indexterm" name="id2585197"></a>
+	<a class="indexterm" name="id2585167"></a>
+	<a class="indexterm" name="id2585174"></a>
+	<a class="indexterm" name="id2585181"></a>
+	<a class="indexterm" name="id2585188"></a>
+	<a class="indexterm" name="id2585194"></a>
+	<a class="indexterm" name="id2585201"></a>
+	<a class="indexterm" name="id2585208"></a>
 	Samba is capable of using the <code class="constant">smbpasswd</code>,
 	<code class="constant">tdbsam</code>, <code class="constant">xmlsam</code>,
 	and <code class="constant">mysqlsam</code> authentication databases. The SMB
@@ -497,7 +497,7 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 	backend. LDAP is the preferred passdb backend for distributed network
 	operations.
 	</p><p>
-	<a class="indexterm" name="id2585225"></a>
+	<a class="indexterm" name="id2585236"></a>
 	Additionally, it is possible to use multiple passdb backends
 	concurrently as well as have multiple LDAP backends. As a result, you
 	can specify a failover LDAP backend. The syntax for specifying a
@@ -507,10 +507,10 @@ productivity.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><
 passdb backend = ldapsam:ldap://master.abmas.biz
 ...
 </pre><p>
-	This configuration tells Samba to use a single LDAP server, as shown in <a class="link" href="net2000users.html#ch7singleLDAP" title="Figure�6.2.�Samba Configuration to Use a Single LDAP Server">&#8220;Samba Configuration to Use a Single LDAP Server&#8221;</a>.
+	This configuration tells Samba to use a single LDAP server, as shown in <a class="link" href="2000users.html#ch7singleLDAP" title="Figure�6.2.�Samba Configuration to Use a Single LDAP Server">&#8220;Samba Configuration to Use a Single LDAP Server&#8221;</a>.
 	</p><div class="figure"><a name="ch7singleLDAP"></a><p class="title"><b>Figure�6.2.�Samba Configuration to Use a Single LDAP Server</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ch7-singleLDAP.png" width="351" alt="Samba Configuration to Use a Single LDAP Server"></div></div></div><p><br class="figure-break">
-	<a class="indexterm" name="id2585298"></a>
-	<a class="indexterm" name="id2585308"></a>
+	<a class="indexterm" name="id2585309"></a>
+	<a class="indexterm" name="id2585318"></a>
 	The addition of a failover LDAP server can simply be done by adding a
 	second entry for the failover server to the single <em class="parameter"><code>ldapsam</code></em>
 	entry, as shown here (note the particular use of the double quotes):
@@ -521,7 +521,7 @@ passdb backend = ldapsam:"ldap://master.abmas.biz \
 ...
 </pre><p>
 	This configuration tells Samba to use a master LDAP server, with failover to a slave server if necessary,
-	as shown in <a class="link" href="net2000users.html#ch7dualLDAP" title="Figure�6.3.�Samba Configuration to Use a Dual (Fail-over) LDAP Server">&#8220;Samba Configuration to Use a Dual (Fail-over) LDAP Server&#8221;</a>.
+	as shown in <a class="link" href="2000users.html#ch7dualLDAP" title="Figure�6.3.�Samba Configuration to Use a Dual (Fail-over) LDAP Server">&#8220;Samba Configuration to Use a Dual (Fail-over) LDAP Server&#8221;</a>.
 	</p><div class="figure"><a name="ch7dualLDAP"></a><p class="title"><b>Figure�6.3.�Samba Configuration to Use a Dual (Fail-over) LDAP Server</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ch7-fail-overLDAP.png" width="351" alt="Samba Configuration to Use a Dual (Fail-over) LDAP Server"></div></div></div><p><br class="figure-break">
 	</p><p>
 	Some folks have tried to implement this without the use of double quotes. This is the type of entry they
@@ -532,17 +532,17 @@ passdb backend = ldapsam:ldap://master.abmas.biz \
                  ldapsam:ldap://slave.abmas.biz
 ...
 </pre><p>
-	<a class="indexterm" name="id2585394"></a>
+	<a class="indexterm" name="id2585405"></a>
 	The effect of this style of entry is that Samba lists the users
 	that are in both LDAP databases. If both contain the same information,
 	it results in each record being shown twice. This is, of course, not the
 	solution desired for a failover implementation. The net effect of this
-	configuration is shown in <a class="link" href="net2000users.html#ch7dualadd" title="Figure�6.4.�Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!">&#8220;Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!&#8221;</a>
+	configuration is shown in <a class="link" href="2000users.html#ch7dualadd" title="Figure�6.4.�Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!">&#8220;Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!&#8221;</a>
 	</p><div class="figure"><a name="ch7dualadd"></a><p class="title"><b>Figure�6.4.�Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ch7-dual-additive-LDAP.png" width="297" alt="Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!"></div></div></div><br class="figure-break"><p>
 	If, however, each LDAP database contains unique information, this may 
 	well be an advantageous way to effectively integrate multiple LDAP databases 
 	into one seemingly contiguous directory. Only the first database will be updated.
-	An example of this configuration is shown in <a class="link" href="net2000users.html#ch7dualok" title="Figure�6.5.�Samba Configuration to Use Two LDAP Databases - The result is additive.">&#8220;Samba Configuration to Use Two LDAP Databases - The result is additive.&#8221;</a>.
+	An example of this configuration is shown in <a class="link" href="2000users.html#ch7dualok" title="Figure�6.5.�Samba Configuration to Use Two LDAP Databases - The result is additive.">&#8220;Samba Configuration to Use Two LDAP Databases - The result is additive.&#8221;</a>.
 	</p><div class="figure"><a name="ch7dualok"></a><p class="title"><b>Figure�6.5.�Samba Configuration to Use Two LDAP Databases - The result is additive.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ch7-dual-additive-LDAP-Ok.png" width="297" alt="Samba Configuration to Use Two LDAP Databases - The result is additive."></div></div></div><br class="figure-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 	When the use of ldapsam is specified twice, as shown here, it is imperative
 	that the two LDAP directories must be disjoint. If the entries are for a
@@ -553,9 +553,9 @@ passdb backend = ldapsam:ldap://master.abmas.biz \
 	It is assumed that the network you are working with follows in a
 	pattern similar to what was covered in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>. The following steps
     permit the operation of a master/slave OpenLDAP arrangement.
-	</p><div class="procedure"><a name="id2585536"></a><p class="title"><b>Procedure�6.1.�Implementation Steps for an LDAP Slave Server</b></p><ol type="1"><li><p>
-	    <a class="indexterm" name="id2585548"></a>
-		<a class="indexterm" name="id2585555"></a>
+	</p><div class="procedure"><a name="id2585547"></a><p class="title"><b>Procedure�6.1.�Implementation Steps for an LDAP Slave Server</b></p><ol type="1"><li><p>
+	    <a class="indexterm" name="id2585559"></a>
+		<a class="indexterm" name="id2585566"></a>
 		Log onto the master LDAP server as <code class="constant">root</code>.
 		You are about to change the configuration of the LDAP server, so it
 		makes sense to temporarily halt it. Stop OpenLDAP from running on 
@@ -568,9 +568,9 @@ passdb backend = ldapsam:ldap://master.abmas.biz \
 <code class="prompt">root# </code> service ldap stop
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2585600"></a>
+		<a class="indexterm" name="id2585611"></a>
 		Edit the <code class="filename">/etc/openldap/slapd.conf</code> file so it
-		matches the content of <a class="link" href="net2000users.html#ch7-LDAP-master" title="Example�6.1.�LDAP Master Server Configuration File /etc/openldap/slapd.conf">&#8220;LDAP Master Server Configuration File  /etc/openldap/slapd.conf&#8221;</a>.
+		matches the content of <a class="link" href="2000users.html#ch7-LDAP-master" title="Example�6.1.�LDAP Master Server Configuration File /etc/openldap/slapd.conf">&#8220;LDAP Master Server Configuration File  /etc/openldap/slapd.conf&#8221;</a>.
 		</p></li><li><p>
 		Create a file called <code class="filename">admin-accts.ldif</code> with the following contents:
 </p><pre class="screen">
@@ -592,8 +592,8 @@ userPassword: buttercup
 <code class="prompt">root# </code> slapadd -v -l admin-accts.ldif
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2585673"></a>
-		<a class="indexterm" name="id2585680"></a>
+		<a class="indexterm" name="id2585684"></a>
+		<a class="indexterm" name="id2585691"></a>
 		Change directory to a suitable place to dump the contents of the
 		LDAP server. The dump file (and LDIF file) is used to preload
 		the slave LDAP server database. You can dump the database by executing:
@@ -602,14 +602,14 @@ userPassword: buttercup
 </pre><p>
 		Each record is written to the file.	
 		</p></li><li><p>
-		<a class="indexterm" name="id2585712"></a>
+		<a class="indexterm" name="id2585723"></a>
 		Copy the file <code class="filename">LDAP-transfer-LDIF.txt</code> to the intended
 		slave LDAP server. A good location could be in the directory 
 		<code class="filename">/etc/openldap/preload</code>.
 		</p></li><li><p>
 		Log onto the slave LDAP server as <code class="constant">root</code>. You can
 		now configure this server so the <code class="filename">/etc/openldap/slapd.conf</code>
-		file matches the content of <a class="link" href="net2000users.html#ch7-LDAP-slave" title="Example�6.2.�LDAP Slave Configuration File /etc/openldap/slapd.conf">&#8220;LDAP Slave Configuration File  /etc/openldap/slapd.conf&#8221;</a>.
+		file matches the content of <a class="link" href="2000users.html#ch7-LDAP-slave" title="Example�6.2.�LDAP Slave Configuration File /etc/openldap/slapd.conf">&#8220;LDAP Slave Configuration File  /etc/openldap/slapd.conf&#8221;</a>.
 		</p></li><li><p>
 		Change directory to the location in which you stored the 
 		<code class="filename">LDAP-transfer-LDIF.txt</code> file (<code class="filename">/etc/openldap/preload</code>).
@@ -652,9 +652,9 @@ added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013)
 <code class="prompt">root# </code> chkconfig ldap on
 </pre><p>
 		</p></li><li><p>
-	    <a class="indexterm" name="id2585885"></a>
-		<a class="indexterm" name="id2585892"></a>
-		<a class="indexterm" name="id2585899"></a>
+	    <a class="indexterm" name="id2585896"></a>
+		<a class="indexterm" name="id2585903"></a>
+		<a class="indexterm" name="id2585910"></a>
 		Go back to the master LDAP server. Execute the following to start LDAP as well
 		as <code class="literal">slurpd</code>, the synchronization daemon, as shown here:
 </p><pre class="screen">
@@ -663,10 +663,10 @@ added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013)
 <code class="prompt">root# </code> rcslurpd start
 <code class="prompt">root# </code> chkconfig slurpd on
 </pre><p>
-	    <a class="indexterm" name="id2585944"></a>
+	    <a class="indexterm" name="id2585955"></a>
 		On Red Hat Linux, check the equivalent command to start <code class="literal">slurpd</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2585965"></a>
+		<a class="indexterm" name="id2585976"></a>
 		On the master LDAP server you may now add an account to validate that replication
 		is working. Assuming the configuration shown in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, execute:
 </p><pre class="screen">
@@ -701,8 +701,8 @@ modifyTimestamp: 20031227004338Z
 		implement additional slave LDAP servers as required.
 		</p></li><li><p>
 		On each machine (PDC and BDCs) after the respective <code class="filename">smb.conf</code> files have been created as shown in
-		<a class="link" href="net2000users.html#ch7-massmbconfA" title="Example�6.3.�Primary Domain Controller smb.conf File Part A">Primary Domain Controller <code class="filename">smb.conf</code> File  Part A + B + C</a> and
-		on BDCs the <a class="link" href="net2000users.html#ch7-slvsmbocnfA" title="Example�6.6.�Backup Domain Controller smb.conf File Part A">Backup Domain Controller <code class="filename">smb.conf</code> File  Part A
+		<a class="link" href="2000users.html#ch7-massmbconfA" title="Example�6.3.�Primary Domain Controller smb.conf File Part A">Primary Domain Controller <code class="filename">smb.conf</code> File  Part A + B + C</a> and
+		on BDCs the <a class="link" href="2000users.html#ch7-slvsmbocnfA" title="Example�6.6.�Backup Domain Controller smb.conf File Part A">Backup Domain Controller <code class="filename">smb.conf</code> File  Part A
 		+ B + C</a> execute the following:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbpasswd -w buttercup
@@ -791,12 +791,12 @@ index sambaSID              eq
 index sambaPrimaryGroupSID  eq
 index sambaDomainName       eq
 index default               sub
-</pre></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfA"></a><p class="title"><b>Example�6.3.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2586228"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2586240"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2586252"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586264"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2586276"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2586288"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2586299"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2586311"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2586323"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2586335"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2586347"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586358"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2586370"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586383"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586395"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2586408"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2586420"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586433"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586446"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586459"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586471"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2586484"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2586496"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2586508"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2586520"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2586531"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586543"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586555"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586567"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586578"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586590"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586602"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2586614"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2586626"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586639"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586651"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586663"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586674"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2586686"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfB"></a><p class="title"><b>Example�6.4.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[IPC$]</code></em></td></tr><tr><td><a class="indexterm" name="id2586732"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2586752"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586764"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2586776"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2586796"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586808"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2586820"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2586840"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586852"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2586864"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2586884"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2586896"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2586908"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586919"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2586940"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2586951"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2586963"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586975"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586986"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfC"></a><p class="title"><b>Example�6.5.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part C</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2587032"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587044"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2587055"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2587067"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2587087"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2587099"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2587111"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2587123"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587135"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2587155"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2587167"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2587179"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587190"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2587211"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2587223"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2587235"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587246"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2587267"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2587279"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2587291"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2587302"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-slvsmbocnfA"></a><p class="title"><b>Example�6.6.�Backup Domain Controller <code class="filename">smb.conf</code> File  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># # Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2587352"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2587363"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2587375"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2587387"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587399"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2587411"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2587423"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2587434"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2587446"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2587458"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2587469"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2587481"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2587493"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587505"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2587517"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2587529"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2587541"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587553"></a><em class="parameter"><code>os level = 63</code></em></td></tr><tr><td><a class="indexterm" name="id2587564"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587576"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2587588"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587600"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2587612"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2587624"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2587636"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2587648"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587660"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587671"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587683"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2587695"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2587707"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2587727"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587739"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2587751"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2587771"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587783"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2587795"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-slvsmbocnfB"></a><p class="title"><b>Example�6.7.�Backup Domain Controller <code class="filename">smb.conf</code> File  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2587841"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587853"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2587864"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2587884"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2587896"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2587908"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587919"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2587940"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2587952"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2587963"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587975"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587987"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2588007"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2588019"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2588030"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2588042"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2588063"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2588075"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2588086"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2588098"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2588119"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2588130"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2588142"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2588154"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2588174"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2588186"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2588198"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2588210"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588223"></a>Key Points Learned</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2588234"></a><a class="indexterm" name="id2588239"></a>
+</pre></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfA"></a><p class="title"><b>Example�6.3.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2586239"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2586251"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2586263"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586275"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2586287"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2586299"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2586310"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2586322"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2586334"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2586346"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2586358"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586369"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2586381"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586394"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586406"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2586418"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2586431"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586444"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586457"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586470"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2586482"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2586495"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2586507"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2586519"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2586531"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2586542"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586554"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586566"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586578"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586589"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586601"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2586613"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2586625"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2586637"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586650"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2586662"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586674"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2586685"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2586697"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfB"></a><p class="title"><b>Example�6.4.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[IPC$]</code></em></td></tr><tr><td><a class="indexterm" name="id2586743"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2586763"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586775"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2586787"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2586807"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586819"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2586831"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2586851"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2586863"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2586875"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2586895"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2586907"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2586918"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2586930"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2586951"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2586962"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2586974"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586986"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2586997"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-massmbconfC"></a><p class="title"><b>Example�6.5.�Primary Domain Controller <code class="filename">smb.conf</code> File  Part C</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2587043"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587055"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2587066"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2587078"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2587098"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2587110"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2587122"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2587134"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587146"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2587166"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2587178"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2587190"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587201"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2587222"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2587234"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2587246"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587257"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2587278"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2587290"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2587302"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2587313"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-slvsmbocnfA"></a><p class="title"><b>Example�6.6.�Backup Domain Controller <code class="filename">smb.conf</code> File  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># # Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2587363"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2587374"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2587386"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2587398"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587410"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2587422"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2587434"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2587445"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2587457"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2587469"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2587480"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2587492"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2587504"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587516"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2587528"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2587540"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2587552"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587564"></a><em class="parameter"><code>os level = 63</code></em></td></tr><tr><td><a class="indexterm" name="id2587575"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587587"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2587599"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587610"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2587622"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2587634"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2587646"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2587658"></a><em class="parameter"><code>ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587671"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587682"></a><em class="parameter"><code>idmap backend = ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2587694"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2587706"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2587718"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2587738"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587750"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2587762"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2587782"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587794"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2587806"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch7-slvsmbocnfB"></a><p class="title"><b>Example�6.7.�Backup Domain Controller <code class="filename">smb.conf</code> File  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2587852"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2587864"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2587875"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2587895"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2587907"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2587919"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2587930"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2587951"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2587963"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2587974"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587986"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2587998"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2588018"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2588030"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2588041"></a><em class="parameter"><code>admin users = bjones</code></em></td></tr><tr><td><a class="indexterm" name="id2588053"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2588074"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2588086"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2588097"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2588109"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2588130"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2588141"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2588153"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2588165"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2588185"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2588197"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2588209"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2588221"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588234"></a>Key Points Learned</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+			<a class="indexterm" name="id2588245"></a><a class="indexterm" name="id2588250"></a>
 			Where Samba-3 is used as a domain controller, the use of LDAP is an 
 			essential component to permit the use of BDCs.
 			</p></li><li><p>
-			<a class="indexterm" name="id2588252"></a>
+			<a class="indexterm" name="id2588263"></a>
 			Replication of the LDAP master server to create a network of BDCs
 			is an important mechanism for limiting WAN traffic.
 			</p></li><li><p>
@@ -808,55 +808,55 @@ index default               sub
 			Roaming profiles must be contained to the local network segment. Any
 			departure from this may clog wide-area arteries and slow legitimate network
 			traffic to a crawl.
-			</p></li></ul></div></div><div class="figure"><a name="chap7net"></a><p class="title"><b>Figure�6.6.�Network Topology  2000 User Complex Design A</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap7-net-Ar.png" width="432" alt="Network Topology 2000 User Complex Design A"></div></div></div><br class="figure-break"><div class="figure"><a name="chap7net2"></a><p class="title"><b>Figure�6.7.�Network Topology  2000 User Complex Design B</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap7-net2-Br.png" width="432" alt="Network Topology 2000 User Complex Design B"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2588370"></a>Questions and Answers</h2></div></div></div><p>
+			</p></li></ul></div></div><div class="figure"><a name="chap7net"></a><p class="title"><b>Figure�6.6.�Network Topology  2000 User Complex Design A</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap7-net-Ar.png" width="432" alt="Network Topology 2000 User Complex Design A"></div></div></div><br class="figure-break"><div class="figure"><a name="chap7net2"></a><p class="title"><b>Figure�6.7.�Network Topology  2000 User Complex Design B</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap7-net2-Br.png" width="432" alt="Network Topology 2000 User Complex Design B"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2588381"></a>Questions and Answers</h2></div></div></div><p>
 	There is much rumor and misinformation regarding the use of MS Windows networking protocols.
 	These questions are just a few of those frequently asked.
-	</p><div class="qandaset"><dl><dt> <a href="net2000users.html#id2588388">
+	</p><div class="qandaset"><dl><dt> <a href="2000users.html#id2588399">
 		
 		
 		Is it true that DHCP uses lots of WAN bandwidth?
-		</a></dt><dt> <a href="net2000users.html#id2588523">
+		</a></dt><dt> <a href="2000users.html#id2588534">
 		
 		
 		How much background communication takes place between a master LDAP server and its slave LDAP servers?
-		</a></dt><dt> <a href="net2000users.html#id2588584">
+		</a></dt><dt> <a href="2000users.html#id2588595">
 		LDAP has a database. Is LDAP not just a fancy database front end?
-		</a></dt><dt> <a href="net2000users.html#id2588648">
+		</a></dt><dt> <a href="2000users.html#id2588659">
 		
 		Can Active Directory obtain account information from an OpenLDAP server?
-		</a></dt><dt> <a href="net2000users.html#id2588683">
+		</a></dt><dt> <a href="2000users.html#id2588694">
 		What are the parts of a roaming profile? How large is each part?
-		</a></dt><dt> <a href="net2000users.html#id2588832">
+		</a></dt><dt> <a href="2000users.html#id2588842">
 		Can the My Documents folder be stored on a network drive?
-		</a></dt><dt> <a href="net2000users.html#id2588880">
+		</a></dt><dt> <a href="2000users.html#id2588890">
 		
 		
 		
 		How much WAN bandwidth does WINS consume?
-		</a></dt><dt> <a href="net2000users.html#id2588964">
+		</a></dt><dt> <a href="2000users.html#id2588975">
 		How many BDCs should I have? What is the right number of Windows clients per server?
-		</a></dt><dt> <a href="net2000users.html#id2589000">
+		</a></dt><dt> <a href="2000users.html#id2589011">
 		
 		I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to
 		run an NIS server?
-		</a></dt><dt> <a href="net2000users.html#id2589034">
+		</a></dt><dt> <a href="2000users.html#id2589044">
 		Can I use NIS in place of LDAP?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2588388"></a><a name="id2588390"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588395"></a>
-		<a class="indexterm" name="id2588401"></a>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2588399"></a><a name="id2588401"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2588406"></a>
+		<a class="indexterm" name="id2588412"></a>
 		Is it true that DHCP uses lots of WAN bandwidth?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588418"></a>
-		<a class="indexterm" name="id2588427"></a>
-		<a class="indexterm" name="id2588434"></a>
+		<a class="indexterm" name="id2588429"></a>
+		<a class="indexterm" name="id2588438"></a>
+		<a class="indexterm" name="id2588445"></a>
 		It is a smart practice to localize DHCP servers on each network segment. As a 
 		rule, there should be two DHCP servers per network segment. This means that if
 		one server fails, there is always another to service user needs. DHCP requests use
 		only UDP broadcast protocols. It is possible to run a DHCP Relay Agent on network
 		routers. This makes it possible to run fewer DHCP servers.
 		</p><p>
-		<a class="indexterm" name="id2588453"></a>
-		<a class="indexterm" name="id2588462"></a>
+		<a class="indexterm" name="id2588464"></a>
+		<a class="indexterm" name="id2588473"></a>
 		A DHCP network address request and confirmation usually results in about six UDP packets.
 		The packets are from 60 to 568 bytes in length. Let us consider a site that has 300 DHCP
 		clients and that uses a 24-hour IP address lease. This means that all clients renew
@@ -874,28 +874,28 @@ DHCP traffic:          300 (clients) x 6 (packets)
 </pre><p>
 		From this can be seen that the traffic impact would be minimal.
 		</p><p>
-		<a class="indexterm" name="id2588500"></a>
-		<a class="indexterm" name="id2588509"></a>
+		<a class="indexterm" name="id2588511"></a>
+		<a class="indexterm" name="id2588520"></a>
 		Even when DHCP is configured to do DNS update (dynamic DNS) over a wide-area link,
 		the impact of the update is no more than the DHCP IP address renewal traffic and thus
 		still insignificant for most practical purposes.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588523"></a><a name="id2588525"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588529"></a>
-		<a class="indexterm" name="id2588536"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588534"></a><a name="id2588536"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2588540"></a>
+		<a class="indexterm" name="id2588547"></a>
 		How much background communication takes place between a master LDAP server and its slave LDAP servers?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588557"></a>
+		<a class="indexterm" name="id2588568"></a>
 		The process that controls the replication of data from the master LDAP server to the slave LDAP
 		servers is called <code class="literal">slurpd</code>. The <code class="literal">slurpd</code> remains nascent (quiet)
 		until an update must be propagated. The propagation traffic per LDAP slave to update (add/modify/delete)
 		two user accounts requires less than 10KB traffic.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588584"></a><a name="id2588586"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588595"></a><a name="id2588597"></a></td><td align="left" valign="top"><p>
 		LDAP has a database. Is LDAP not just a fancy database front end?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588598"></a>
-		<a class="indexterm" name="id2588605"></a>
-		<a class="indexterm" name="id2588614"></a>
-		<a class="indexterm" name="id2588620"></a>
+		<a class="indexterm" name="id2588609"></a>
+		<a class="indexterm" name="id2588616"></a>
+		<a class="indexterm" name="id2588625"></a>
+		<a class="indexterm" name="id2588631"></a>
 		LDAP does store its data in a database of sorts. In fact, the LDAP backend is an application-specific
 		data storage system. This type of database is indexed so that records can be rapidly located, but the
 		database is not generic and can be used only in particular pre-programmed ways. General external
@@ -904,17 +904,17 @@ DHCP traffic:          300 (clients) x 6 (packets)
 		orientation and typically allows external programs to perform ad hoc queries, even across data tables.
 		An LDAP front end is a purpose-built tool that has a search orientation that is designed around specific
 		simple queries. The term <code class="constant">database</code> is heavily overloaded and thus much misunderstood.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588648"></a><a name="id2588650"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588654"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588659"></a><a name="id2588661"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2588665"></a>
 		Can Active Directory obtain account information from an OpenLDAP server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588669"></a>
+		<a class="indexterm" name="id2588680"></a>
 		No, at least not directly. It is possible to provision Active Directory from and/or to an OpenLDAP
 		database through use of a metadirectory server. Microsoft MMS (now called MIIS) can interface
 		to OpenLDAP using standard LDAP queries and updates. 
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588683"></a><a name="id2588685"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588694"></a><a name="id2588696"></a></td><td align="left" valign="top"><p>
 		What are the parts of a roaming profile? How large is each part?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2588696"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2588707"></a>
 		A roaming profile consists of
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
 			Desktop folders such as <code class="constant">Desktop</code>, <code class="constant">My Documents</code>,
@@ -922,39 +922,39 @@ DHCP traffic:          300 (clients) x 6 (packets)
 			<code class="constant">Cookies</code>, <code class="constant">Application Data</code>,
 			<code class="constant">Local Settings,</code> and more. See <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>, <a class="link" href="happy.html#XP-screen001" title="Figure�5.3.�Windows XP Professional User Shared Folders">&#8220;Windows XP Professional  User Shared Folders&#8221;</a>.
 			</p><p>
-			<a class="indexterm" name="id2588757"></a>
+			<a class="indexterm" name="id2588768"></a>
 			Each of these can be anywhere from a few bytes to gigabytes in capacity. Fortunately, all
 			such folders can be redirected to network drive resources. See <a class="link" href="happy.html#redirfold" title="Configuration of Default Profile with Folder Redirection">&#8220;Configuration of Default Profile with Folder Redirection&#8221;</a>
 			for more information regarding folder redirection.
 			</p></li><li><p>
 			A static or rewritable portion that is typically only a few files (2-5 KB of information).
 			</p></li><li><p>
-			<a class="indexterm" name="id2588784"></a>
-			<a class="indexterm" name="id2588790"></a>
+			<a class="indexterm" name="id2588795"></a>
+			<a class="indexterm" name="id2588801"></a>
 			The registry load file that modifies the <code class="constant">HKEY_LOCAL_USER</code> hive. This is
 			the <code class="filename">NTUSER.DAT</code> file. It can be from 0.4 to 1.5 MB.
 			</p></li></ul></div><p>
-		<a class="indexterm" name="id2588813"></a>
+		<a class="indexterm" name="id2588824"></a>
 		Microsoft Outlook PST files may be stored in the <code class="constant">Local Settings\Application Data</code>
 		folder. It can be up to 2 GB in size per PST file.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588832"></a><a name="id2588834"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588842"></a><a name="id2588845"></a></td><td align="left" valign="top"><p>
 		Can the <code class="constant">My Documents</code> folder be stored on a network drive?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588849"></a>
-		<a class="indexterm" name="id2588856"></a>
+		<a class="indexterm" name="id2588860"></a>
+		<a class="indexterm" name="id2588867"></a>
 		Yes. More correctly, such folders can be redirected to network shares. No specific network drive
 		connection is required. Registry settings permit this to be redirected directly to a UNC (Universal
 		Naming Convention) resource, though it is possible to specify a network drive letter instead of a
 		UNC name. See <a class="link" href="happy.html#redirfold" title="Configuration of Default Profile with Folder Redirection">&#8220;Configuration of Default Profile with Folder Redirection&#8221;</a>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588880"></a><a name="id2588882"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588886"></a>
-		<a class="indexterm" name="id2588893"></a>
-		<a class="indexterm" name="id2588902"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588890"></a><a name="id2588893"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2588897"></a>
+		<a class="indexterm" name="id2588904"></a>
+		<a class="indexterm" name="id2588913"></a>
 		How much WAN bandwidth does WINS consume?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2588916"></a>
-		<a class="indexterm" name="id2588925"></a>
-		<a class="indexterm" name="id2588932"></a>
+		<a class="indexterm" name="id2588927"></a>
+		<a class="indexterm" name="id2588936"></a>
+		<a class="indexterm" name="id2588943"></a>
 		MS Windows clients cache information obtained from WINS lookups in a local NetBIOS name cache.
 		This keeps WINS lookups to a minimum. On a network with 3500 MS Windows clients and a central WINS
 		server, the total bandwidth demand measured at the WINS server, averaged over an 8-hour working day,
@@ -966,7 +966,7 @@ DHCP traffic:          300 (clients) x 6 (packets)
 		</p><p>
 		In conclusion, the total load afforded through WINS traffic is again marginal to total operational
 		usage  as it should be.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588964"></a><a name="id2588966"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2588975"></a><a name="id2588977"></a></td><td align="left" valign="top"><p>
 		How many BDCs should I have? What is the right number of Windows clients per server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		It is recommended to have at least one BDC per network segment, including the segment served
@@ -980,19 +980,19 @@ DHCP traffic:          300 (clients) x 6 (packets)
 		</p><p>
 		As unsatisfactory as the answer might sound, it all depends on network and server load
 		characteristics.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2589000"></a><a name="id2589002"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2589006"></a><a class="indexterm" name="id2589012"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2589011"></a><a name="id2589013"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2589017"></a><a class="indexterm" name="id2589023"></a>
 		I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to
 		run an NIS server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The correct answer to both questions is yes. But do understand that an LDAP server has
 		a configurable schema that can store far more information for many more purposes than
 		just NIS.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2589034"></a><a name="id2589036"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2589044"></a><a name="id2589047"></a></td><td align="left" valign="top"><p>
 		Can I use NIS in place of LDAP?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2589047"></a>
-		<a class="indexterm" name="id2589054"></a>
+		<a class="indexterm" name="id2589058"></a>
+		<a class="indexterm" name="id2589065"></a>
 		No. The NIS database does not have provision to store Microsoft encrypted passwords and does not deal
 		with the types of data necessary for interoperability with Microsoft Windows networking. The use
 		of LDAP with Samba requires the use of a number of schemas, one of which is the NIS schema, but also
diff --git a/docs/htmldocs/Samba3-ByExample/Big500users.html b/docs/htmldocs/Samba3-ByExample/Big500users.html
index ad248b0bf5..b14b7eb5fc 100644
--- a/docs/htmldocs/Samba3-ByExample/Big500users.html
+++ b/docs/htmldocs/Samba3-ByExample/Big500users.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�The 500-User Office</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="secure.html" title="Chapter�3.�Secure Office Networking"><link rel="next" href="happy.html" title="Chapter�5.�Making Happy Users"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�The 500-User Office</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="secure.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="happy.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Big500users"></a>Chapter�4.�The 500-User Office</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Big500users.html#id2565229">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565274">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565373">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565409">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565612">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565635">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566362">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566927">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570125">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570184">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�The 500-User Office</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="secure.html" title="Chapter�3.�Secure Office Networking"><link rel="next" href="happy.html" title="Chapter�5.�Making Happy Users"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�The 500-User Office</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="secure.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="happy.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Big500users"></a>Chapter�4.�The 500-User Office</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Big500users.html#id2565220">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565265">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565371">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565407">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565610">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565632">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566360">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566924">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570124">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570183">Questions and Answers</a></span></dt></dl></div><p>
 	The Samba-3 networking you explored in <a class="link" href="secure.html" title="Chapter�3.�Secure Office Networking">&#8220;Secure Office Networking&#8221;</a> covers the finer points of 
 	configuration of peripheral services such as DHCP and DNS, and WINS. You experienced
 	implementation of a simple configuration of the services that are important adjuncts 
@@ -17,9 +17,9 @@
 	that same approach to printing, but <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a> presents an opportunity 
 	to make printing more complex for the administrator while making it easier for the user.
 	</p><p>
-	<a class="indexterm" name="id2565165"></a>
-	<a class="indexterm" name="id2565172"></a>
-	<a class="indexterm" name="id2565178"></a>
+	<a class="indexterm" name="id2565156"></a>
+	<a class="indexterm" name="id2565163"></a>
+	<a class="indexterm" name="id2565169"></a>
 	<a class="link" href="secure.html" title="Chapter�3.�Secure Office Networking">&#8220;Secure Office Networking&#8221;</a> demonstrates operation of a DHCP server and a DNS server 
 	as well as a central WINS server. You validated the operation of these services and
 	saw an effective implementation of a Samba domain controller using the 
@@ -41,7 +41,7 @@
 	improve network management and control while reducing human resource overheads.
 	You should take the opportunity to innovate and expand on the methods presented 
 	here and explore them to the fullest.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565229"></a>Introduction</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565220"></a>Introduction</h2></div></div></div><p>
 	Business continues to go well for Abmas. Mr. Meany is driving your success and the
 	network continues to grow thanks to the hard work Christine has done. You recently
 	hired Stanley Soroka as manager of information systems. Christine recommended Stan
@@ -66,7 +66,7 @@
 	and to allow Stan and Christine to fully stage the new network and test it before
 	it is rolled out. Your strategy is to complete the new network so that it
 	is ready for operation when the old office moves into the new premises.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565274"></a>Assignment Tasks</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565265"></a>Assignment Tasks</h3></div></div></div><p>
 		The acquired business had 280 network users. The old Abmas building housed
 		220 network users in unbelievably cramped conditions. The network that
 		initially served 130 users now handles 220 users quite well.
@@ -107,7 +107,7 @@
 		DirectPointe Inc. receives from you a new standard desktop configuration
 		every four months. They automatically roll that out to each desktop system.
 		You must keep DirectPointe informed of all changes.
-		</p><p><a class="indexterm" name="id2565345"></a>
+		</p><p><a class="indexterm" name="id2565342"></a>
 		The new network has a single Samba Primary Domain Controller (PDC) located in the
 		Network Operation Center (NOC). Buildings 1 and 2 each have a local server
 		for local application servicing. It is a domain member. The new system
@@ -115,8 +115,8 @@
 		</p><p>
 		Printing is based on raw pass-through facilities just as it has been used so far.
 		All printer drivers are installed on the desktop and notebook computers.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565373"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2565381"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565371"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2565379"></a>
 	The example you are building in this chapter is of a network design that works, but this
 	does not make it a design that is recommended. As a general rule, there should be at least
 	one Backup Domain Controller (BDC) per 150 Windows network clients. The principle behind
@@ -127,22 +127,22 @@
 	responsiveness. This network will have 500 clients serviced by one central domain
 	controller. This is not a good omen for user satisfaction. You, of course, address this
 	very soon (see <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>).
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565409"></a>Technical Issues</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565407"></a>Technical Issues</h3></div></div></div><p>
 		Stan has talked you into a horrible compromise, but it is addressed. Just make
 		certain that the performance of this network is well validated before going live.
 		</p><p>
 		Design decisions made in this design include the following:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2565430"></a>
-			<a class="indexterm" name="id2565437"></a>
-			<a class="indexterm" name="id2565444"></a>
+			<a class="indexterm" name="id2565428"></a>
+			<a class="indexterm" name="id2565435"></a>
+			<a class="indexterm" name="id2565442"></a>
 			A single PDC is being implemented. This limitation is based on the choice not to
 			use LDAP. Many network administrators fear using LDAP because of the perceived
 			complexity of implementation and management of an LDAP-based backend for all user
 			identity management as well as to store network access credentials.
 			</p></li><li><p>
-			<a class="indexterm" name="id2565461"></a>
-			<a class="indexterm" name="id2565468"></a>
+			<a class="indexterm" name="id2565458"></a>
+			<a class="indexterm" name="id2565465"></a>
 			Because of the refusal to use an LDAP (ldapsam) passdb backend at this time, the
 			only choice that makes sense with 500 users is to use the tdbsam passwd backend. 
 			This type of backend is not receptive to replication to BDCs.  If the tdbsam
@@ -156,7 +156,7 @@
 			for a simple mode of operation but has to be balanced with network performance and
 			integrity of operations considerations.
 			</p></li><li><p>
-			<a class="indexterm" name="id2565508"></a>
+			<a class="indexterm" name="id2565506"></a>
 			A single central WINS server is being used. The PDC is also the WINS server.
 			Any attempt to operate a routed network without a WINS server while using NetBIOS
 			over TCP/IP protocols does not work unless on each client the name resolution
@@ -167,12 +167,12 @@
 			At this time the Samba WINS database cannot be replicated. That is
 			why a single WINS server is being implemented. This should work without a problem.
 			</p></li><li><p>
-			<a class="indexterm" name="id2565545"></a>
+			<a class="indexterm" name="id2565543"></a>
 			BDCs make use of <code class="literal">winbindd</code> to provide
 			access to domain security credentials for file system access and object storage.
 			</p></li><li><p>
-			<a class="indexterm" name="id2565564"></a>
-			<a class="indexterm" name="id2565574"></a>
+			<a class="indexterm" name="id2565562"></a>
+			<a class="indexterm" name="id2565571"></a>
 			Configuration of Windows XP Professional clients is achieved using DHCP. Each
 			subnet has its own DHCP server. Backup DHCP serving is provided by one
 			alternate DHCP server. This necessitates enabling of the DHCP Relay agent on
@@ -188,13 +188,13 @@
 			The network address and subnetmask chosen provide 1022 usable IP addresses in
 			each subnet. If in the future more addresses are required, it would make sense
 			to add further subnets rather than change addressing.
-			</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565612"></a>Political Issues</h3></div></div></div><p>
+			</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565610"></a>Political Issues</h3></div></div></div><p>
 		This case gets close to the real world. You and I know the right way to implement
 		domain control. Politically, we have to navigate a minefield. In this case, the need is to
 		get the PDC rolled out in compliance with expectations and also to be ready to save the day
 		by having the real solution ready before it is needed. That real solution is presented in
 		<a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565635"></a>Implementation</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565632"></a>Implementation</h2></div></div></div><p>
 	The following configuration process begins following installation of Red Hat Fedora Core2 on the
 	three servers shown in the network topology diagram in <a class="link" href="Big500users.html#chap05net" title="Figure�4.1.�Network Topology 500 User Network Using tdbsam passdb backend.">&#8220;Network Topology  500 User Network Using tdbsam passdb backend.&#8221;</a>. You have
 	selected hardware that is appropriate to the task.
@@ -205,9 +205,9 @@
 	</p><p>
 	The abbreviation shown in this table as <code class="constant">{VLN}</code> refers to
 	the directory location beginning with <code class="filename">/var/lib/named</code>.
-	</p><div class="table"><a name="ch5-filelocations"></a><p class="title"><b>Table�4.1.�Domain: <code class="constant">MEGANET</code>, File Locations for Servers</b></p><div class="table-contents"><table summary="Domain: MEGANET, File Locations for Servers" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th colspan="2" align="center">File Information</th><th colspan="3" align="center">Server Name</th></tr><tr><th align="center">Source</th><th align="center">Target Location</th><th align="center">MASSIVE</th><th align="center">BLDG1</th><th align="center">BLDG2</th></tr></thead><tbody><tr><td align="left"><a class="link" href="Big500users.html#ch5-massivesmb" title="Example�4.1.�Server: MASSIVE (PDC), File: /etc/samba/smb.conf">&#8220;Server: MASSIVE (PDC), File: /etc/samba/smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-dc-common" title="Example�4.2.�Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf">&#8220;Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/dc-common.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-commonsmb" title="Example�4.3.�Common Samba Configuration File: /etc/samba/common.conf">&#8220;Common Samba Configuration File: /etc/samba/common.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/common.conf</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-bldg1-smb" title="Example�4.4.�Server: BLDG1 (Member), File: smb.conf">&#8220;Server: BLDG1 (Member), File: smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-bldg2-smb" title="Example�4.5.�Server: BLDG2 (Member), File: smb.conf">&#8220;Server: BLDG2 (Member), File: smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">No</td><td align="center">No</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-dommem-smb" title="Example�4.6.�Common Domain Member Include File: dom-mem.conf">&#8220;Common Domain Member Include File: dom-mem.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/dommem.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-dhcp" title="Example�4.7.�Server: MASSIVE, File: dhcpd.conf">&#8220;Server: MASSIVE, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg1dhcp" title="Example�4.8.�Server: BLDG1, File: dhcpd.conf">&#8220;Server: BLDG1, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg2dhcp" title="Example�4.9.�Server: BLDG2, File: dhcpd.conf">&#8220;Server: BLDG2, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">No</td><td align="center">No</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-nameda" title="Example�4.10.�Server: MASSIVE, File: named.conf, Part: A">&#8220;Server: MASSIVE, File: named.conf, Part: A&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part A)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-namedb" title="Example�4.11.�Server: MASSIVE, File: named.conf, Part: B">&#8220;Server: MASSIVE, File: named.conf, Part: B&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part B)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-namedc" title="Example�4.12.�Server: MASSIVE, File: named.conf, Part: C">&#8220;Server: MASSIVE, File: named.conf, Part: C&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part C)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#abmasbizdns" title="Example�4.13.�Forward Zone File: abmas.biz.hosts">&#8220;Forward Zone File: abmas.biz.hosts&#8221;</a></td><td align="left"><code class="filename">{VLN}/master/abmas.biz.hosts</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#abmasusdns" title="Example�4.14.�Forward Zone File: abmas.biz.hosts">&#8220;Forward Zone File: abmas.biz.hosts&#8221;</a></td><td align="left"><code class="filename">{VLN}/master/abmas.us.hosts</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg12nameda" title="Example�4.15.�Servers: BLDG1/BLDG2, File: named.conf, Part: A">&#8220;Servers: BLDG1/BLDG2, File: named.conf, Part: A&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part A)</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg12namedb" title="Example�4.16.�Servers: BLDG1/BLDG2, File: named.conf, Part: B">&#8220;Servers: BLDG1/BLDG2, File: named.conf, Part: B&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part B)</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#loopback" title="Example�15.3.�DNS Localhost Forward Zone File: /var/lib/named/localhost.zone">&#8220;DNS Localhost Forward Zone File: /var/lib/named/localhost.zone&#8221;</a></td><td align="left"><code class="filename">{VLN}/localhost.zone</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#dnsloopy" title="Example�15.4.�DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone">&#8220;DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone&#8221;</a></td><td align="left"><code class="filename">{VLN}/127.0.0.zone</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#roothint" title="Example�15.5.�DNS Root Name Server Hint File: /var/lib/named/root.hint">&#8220;DNS Root Name Server Hint File: /var/lib/named/root.hint&#8221;</a></td><td align="left"><code class="filename">{VLN}/root.hint</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566362"></a>Server Preparation: All Servers</h3></div></div></div><p>
+	</p><div class="table"><a name="ch5-filelocations"></a><p class="title"><b>Table�4.1.�Domain: <code class="constant">MEGANET</code>, File Locations for Servers</b></p><div class="table-contents"><table summary="Domain: MEGANET, File Locations for Servers" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th colspan="2" align="center">File Information</th><th colspan="3" align="center">Server Name</th></tr><tr><th align="center">Source</th><th align="center">Target Location</th><th align="center">MASSIVE</th><th align="center">BLDG1</th><th align="center">BLDG2</th></tr></thead><tbody><tr><td align="left"><a class="link" href="Big500users.html#ch5-massivesmb" title="Example�4.1.�Server: MASSIVE (PDC), File: /etc/samba/smb.conf">&#8220;Server: MASSIVE (PDC), File: /etc/samba/smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-dc-common" title="Example�4.2.�Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf">&#8220;Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/dc-common.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-commonsmb" title="Example�4.3.�Common Samba Configuration File: /etc/samba/common.conf">&#8220;Common Samba Configuration File: /etc/samba/common.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/common.conf</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-bldg1-smb" title="Example�4.4.�Server: BLDG1 (Member), File: smb.conf">&#8220;Server: BLDG1 (Member), File: smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-bldg2-smb" title="Example�4.5.�Server: BLDG2 (Member), File: smb.conf">&#8220;Server: BLDG2 (Member), File: smb.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/smb.conf</code></td><td align="center">No</td><td align="center">No</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#ch5-dommem-smb" title="Example�4.6.�Common Domain Member Include File: dom-mem.conf">&#8220;Common Domain Member Include File: dom-mem.conf&#8221;</a></td><td align="left"><code class="filename">/etc/samba/dommem.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-dhcp" title="Example�4.7.�Server: MASSIVE, File: dhcpd.conf">&#8220;Server: MASSIVE, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg1dhcp" title="Example�4.8.�Server: BLDG1, File: dhcpd.conf">&#8220;Server: BLDG1, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg2dhcp" title="Example�4.9.�Server: BLDG2, File: dhcpd.conf">&#8220;Server: BLDG2, File: dhcpd.conf&#8221;</a></td><td align="left"><code class="filename">/etc/dhcpd.conf</code></td><td align="center">No</td><td align="center">No</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-nameda" title="Example�4.10.�Server: MASSIVE, File: named.conf, Part: A">&#8220;Server: MASSIVE, File: named.conf, Part: A&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part A)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-namedb" title="Example�4.11.�Server: MASSIVE, File: named.conf, Part: B">&#8220;Server: MASSIVE, File: named.conf, Part: B&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part B)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#massive-namedc" title="Example�4.12.�Server: MASSIVE, File: named.conf, Part: C">&#8220;Server: MASSIVE, File: named.conf, Part: C&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part C)</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#abmasbizdns" title="Example�4.13.�Forward Zone File: abmas.biz.hosts">&#8220;Forward Zone File: abmas.biz.hosts&#8221;</a></td><td align="left"><code class="filename">{VLN}/master/abmas.biz.hosts</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#abmasusdns" title="Example�4.14.�Forward Zone File: abmas.biz.hosts">&#8220;Forward Zone File: abmas.biz.hosts&#8221;</a></td><td align="left"><code class="filename">{VLN}/master/abmas.us.hosts</code></td><td align="center">Yes</td><td align="center">No</td><td align="center">No</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg12nameda" title="Example�4.15.�Servers: BLDG1/BLDG2, File: named.conf, Part: A">&#8220;Servers: BLDG1/BLDG2, File: named.conf, Part: A&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part A)</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="Big500users.html#bldg12namedb" title="Example�4.16.�Servers: BLDG1/BLDG2, File: named.conf, Part: B">&#8220;Servers: BLDG1/BLDG2, File: named.conf, Part: B&#8221;</a></td><td align="left"><code class="filename">/etc/named.conf (part B)</code></td><td align="center">No</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#loopback" title="Example�15.3.�DNS Localhost Forward Zone File: /var/lib/named/localhost.zone">&#8220;DNS Localhost Forward Zone File: /var/lib/named/localhost.zone&#8221;</a></td><td align="left"><code class="filename">{VLN}/localhost.zone</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#dnsloopy" title="Example�15.4.�DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone">&#8220;DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone&#8221;</a></td><td align="left"><code class="filename">{VLN}/127.0.0.zone</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr><tr><td align="left"><a class="link" href="appendix.html#roothint" title="Example�15.5.�DNS Root Name Server Hint File: /var/lib/named/root.hint">&#8220;DNS Root Name Server Hint File: /var/lib/named/root.hint&#8221;</a></td><td align="left"><code class="filename">{VLN}/root.hint</code></td><td align="center">Yes</td><td align="center">Yes</td><td align="center">Yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566360"></a>Server Preparation: All Servers</h3></div></div></div><p>
 	The following steps apply to all servers. Follow each step carefully.
-	</p><div class="procedure"><a name="id2566373"></a><p class="title"><b>Procedure�4.1.�Server Preparation Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2566371"></a><p class="title"><b>Procedure�4.1.�Server Preparation Steps</b></p><ol type="1"><li><p>
 			Using the UNIX/Linux system tools, set the name of the server as shown in the network
 			topology diagram in <a class="link" href="Big500users.html#chap05net" title="Figure�4.1.�Network Topology 500 User Network Using tdbsam passdb backend.">&#8220;Network Topology  500 User Network Using tdbsam passdb backend.&#8221;</a>. For SUSE Linux products, the tool
 			that permits this is called <code class="literal">yast2</code>; for Red Hat Linux products,
@@ -221,8 +221,8 @@
 <code class="prompt">root# </code> hostname -f
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2566437"></a>
-			<a class="indexterm" name="id2566444"></a>
+			<a class="indexterm" name="id2566435"></a>
+			<a class="indexterm" name="id2566442"></a>
 			Edit your <code class="filename">/etc/hosts</code> file to include the primary names and addresses
 			of all network interfaces that are on the host server. This is necessary so that during
 			startup the system is able to resolve all its own names to the IP address prior to
@@ -230,7 +230,7 @@
 			CUPS print server is started before the DNS server (<code class="literal">named</code>), you 
 			should also include an entry for the printers in the <code class="filename">/etc/hosts</code> file.
 			</p></li><li><p>
-			<a class="indexterm" name="id2566483"></a>
+			<a class="indexterm" name="id2566480"></a>
 			All DNS name resolution should be handled locally. To ensure that the server is configured
 			correctly to handle this, edit <code class="filename">/etc/resolv.conf</code> so it has the following
 			content:
@@ -241,8 +241,8 @@ nameserver 127.0.0.1
 			This instructs the name resolver function (when configured correctly) to ask the DNS server
 			that is running locally to resolve names to addresses.
 			</p></li><li><p>
-			<a class="indexterm" name="id2566514"></a>
-			<a class="indexterm" name="id2566521"></a>
+			<a class="indexterm" name="id2566512"></a>
+			<a class="indexterm" name="id2566519"></a>
 			Add the <code class="constant">root</code> user to the password backend:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbpasswd -a root
@@ -255,8 +255,8 @@ Retype new SMB password: XXXXXXXX
 			deleted. If for any reason the account is deleted, you may not be able to recreate this account
 			without considerable trouble.
 			</p></li><li><p>
-			<a class="indexterm" name="id2566567"></a>
-			<a class="indexterm" name="id2566574"></a>
+			<a class="indexterm" name="id2566564"></a>
+			<a class="indexterm" name="id2566571"></a>
 			Create the username map file to permit the <code class="constant">root</code> account to be called
 			<code class="constant">Administrator</code> from the Windows network environment. To do this, create
 			the file <code class="filename">/etc/samba/smbusers</code> with the following contents:
@@ -294,16 +294,16 @@ root = Administrator
 			Follow the instructions in the printer manufacturer's manuals to permit printing 
 			to port 9100.  Use any other port the manufacturer specifies for direct mode, 
 			raw printing.  This allows the CUPS spooler to print using raw mode protocols.
-			<a class="indexterm" name="id2566665"></a>
-			<a class="indexterm" name="id2566672"></a>
+			<a class="indexterm" name="id2566663"></a>
+			<a class="indexterm" name="id2566669"></a>
 			</p></li><li><p>
-			<a class="indexterm" name="id2566685"></a>
+			<a class="indexterm" name="id2566683"></a>
 			Only on the server to which the printer is attached configure the CUPS Print 
 			Queues as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p <em class="parameter"><code>printque</code></em> -v socket://<em class="parameter"><code>printer-name</code></em>.abmas.biz:9100 -E
 </pre><p>
-			<a class="indexterm" name="id2566720"></a>
+			<a class="indexterm" name="id2566718"></a>
 			This step creates the necessary print queue to use no assigned print filter. This
 			is ideal for raw printing, that is, printing without use of filters.
 			The name <em class="parameter"><code>printque</code></em> is the name you have assigned for
@@ -323,9 +323,9 @@ root = Administrator
 <code class="prompt">root# </code> /usr/bin/accept <em class="parameter"><code>printque</code></em>
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2566799"></a>
-			<a class="indexterm" name="id2566806"></a>
-			<a class="indexterm" name="id2566813"></a>
+			<a class="indexterm" name="id2566797"></a>
+			<a class="indexterm" name="id2566804"></a>
+			<a class="indexterm" name="id2566811"></a>
 			This step, as well as the next one, may be omitted where CUPS version 1.1.18
 			or later is in use.  Although it does no harm to follow it anyway, and may
 			help to avoid time spent later trying to figure out why print jobs may be
@@ -336,7 +336,7 @@ root = Administrator
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2566849"></a>
+			<a class="indexterm" name="id2566847"></a>
 			Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
@@ -359,17 +359,17 @@ application/octet-stream
 	processes to automap Windows client drives to an application server that is nearest to the client. This
 	is considerably more difficult when a single PDC is used on a routed network. It can be done, but not
 	as elegantly as you see in the next chapter.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566927"></a>Server-Specific Preparation</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566924"></a>Server-Specific Preparation</h3></div></div></div><p>
 	There are some steps that apply to particular server functionality only. Each step is critical
 	to correct server operation. The following step-by-step installation guidance will assist you 
 	in working through the process of configuring the PDC and then both BDC's.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2566940"></a>Configuration for Server: <code class="constant">MASSIVE</code></h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2566938"></a>Configuration for Server: <code class="constant">MASSIVE</code></h4></div></div></div><p>
 		The steps presented here attempt to implement Samba installation in a generic manner. While
 		some steps are clearly specific to Linux, it should not be too difficult to apply them to
 		your platform of choice.
-		</p><div class="procedure"><a name="id2566955"></a><p class="title"><b>Procedure�4.2.�Primary Domain Controller Preparation</b></p><ol type="1"><li><p>
-			<a class="indexterm" name="id2566967"></a>
-			<a class="indexterm" name="id2566974"></a>
+		</p><div class="procedure"><a name="id2566953"></a><p class="title"><b>Procedure�4.2.�Primary Domain Controller Preparation</b></p><ol type="1"><li><p>
+			<a class="indexterm" name="id2566965"></a>
+			<a class="indexterm" name="id2566972"></a>
 			The host server acts as a router between the two internal network segments as well
 			as for all Internet access. This necessitates that IP forwarding be enabled. This can be
 			achieved by adding to the <code class="filename">/etc/rc.d/boot.local</code> an entry as follows:
@@ -397,7 +397,7 @@ echo 1 &gt; /proc/sys/net/ipv4/ip_forward
 			startup files as follows: (SUSE) <code class="filename">/etc/rc.d/boot.local</code>, (Red Hat)
 			<code class="filename">/etc/rc.d/init.d/rc.local</code>.
 			</p></li><li><p>
-			<a class="indexterm" name="id2567068"></a>
+			<a class="indexterm" name="id2567065"></a>
 			The final step that must be completed is to edit the <code class="filename">/etc/nsswitch.conf</code> file.
 			This file controls the operation of the various resolver libraries that are part of the Linux
 			Glibc libraries. Edit this file so that it contains the following entries:
@@ -405,24 +405,24 @@ echo 1 &gt; /proc/sys/net/ipv4/ip_forward
 hosts:      files dns wins
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2567098"></a>
+			<a class="indexterm" name="id2567095"></a>
 			Create and map Windows domain groups to UNIX groups. A sample script is provided in
 			<a class="link" href="Big500users.html#ch5-initgrps" title="Example�4.17.�Initialize Groups Script, File: /etc/samba/initGrps.sh">&#8220;Initialize Groups Script, File: /etc/samba/initGrps.sh&#8221;</a>. Create a file containing this script. You called yours
 			<code class="filename">/etc/samba/initGrps.sh</code>. Set this file so it can be executed
 			and then execute the script. An example of the execution of this script as well as its
 			validation are shown in Section 4.3.2, Step 5.
 			</p></li><li><p>
-			<a class="indexterm" name="id2567129"></a>
-			<a class="indexterm" name="id2567136"></a>
-			<a class="indexterm" name="id2567145"></a>
+			<a class="indexterm" name="id2567127"></a>
+			<a class="indexterm" name="id2567134"></a>
+			<a class="indexterm" name="id2567143"></a>
 			For each user who needs to be given a Windows domain account, make an entry in the
 			<code class="filename">/etc/passwd</code> file as well as in the Samba password backend.
 			Use the system tool of your choice to create the UNIX system account, and use the Samba
 			<code class="literal">smbpasswd</code> to create a domain user account.
 			</p><p>
-			<a class="indexterm" name="id2567172"></a>
-			<a class="indexterm" name="id2567179"></a>
-			<a class="indexterm" name="id2567185"></a>
+			<a class="indexterm" name="id2567170"></a>
+			<a class="indexterm" name="id2567176"></a>
+			<a class="indexterm" name="id2567183"></a>
 			There are a number of tools for user management under UNIX, such as
 			<code class="literal">useradd</code>, <code class="literal">adduser</code>, as well as a plethora of custom
 			tools. With the tool of your choice, create a home directory for each user.
@@ -435,7 +435,7 @@ hosts:      files dns wins
 			file is <code class="filename">/data</code>. Format the file system as required and mount the formatted
 			file system partition using appropriate system tools.
 			</p></li><li><p>
-		<a class="indexterm" name="id2567249"></a>
+		<a class="indexterm" name="id2567247"></a>
 			Create the top-level file storage directories for data and applications as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> mkdir -p /data/{accounts,finsvcs,pidata}
@@ -475,8 +475,8 @@ hosts:      files dns wins
 <code class="prompt">root# </code> chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2567455"></a>
-			<a class="indexterm" name="id2567462"></a>
+			<a class="indexterm" name="id2567453"></a>
+			<a class="indexterm" name="id2567459"></a>
 			Create a logon script. It is important that each line is correctly terminated with
 			a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
 			works if the right tools (<code class="constant">unxi2dos</code> and <code class="constant">dos2unix</code>) are installed.
@@ -518,8 +518,8 @@ Added user <em class="parameter"><code>username</code></em>.
 		The following steps will guide you through the nuances of implementing BDCs for the broadcast
 		isolated network segments. Remember that if the target installation platform is not Linux, it may
 		be necessary to adapt some commands to the equivalent on the target platform.
-		</p><div class="procedure"><a name="id2567648"></a><p class="title"><b>Procedure�4.3.�Backup Domain Controller Configuration Steps</b></p><ol type="1"><li><p>
-			<a class="indexterm" name="id2567660"></a>
+		</p><div class="procedure"><a name="id2567646"></a><p class="title"><b>Procedure�4.3.�Backup Domain Controller Configuration Steps</b></p><ol type="1"><li><p>
+			<a class="indexterm" name="id2567658"></a>
 			The final step that must be completed is to edit the <code class="filename">/etc/nsswitch.conf</code> file.
 			This file controls the operation of the various resolver libraries that are part of the Linux
 			Glibc libraries. Edit this file so that it contains the following entries:
@@ -532,14 +532,14 @@ hosts:      files dns wins
 			Follow the steps outlined in <a class="link" href="Big500users.html#ch5-procstart" title="Process Startup Configuration">&#8220;Process Startup Configuration&#8221;</a> to start all services. Do not
 			start Samba at this time. Samba is controlled by the process called <code class="literal">smb</code>.
 			</p></li><li><p>
-			<a class="indexterm" name="id2567712"></a>
+			<a class="indexterm" name="id2567710"></a>
 			You must now attempt to join the domain member servers to the domain. The following
 			instructions should be executed to effect this:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join 
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2567744"></a>
+			<a class="indexterm" name="id2567742"></a>
 			You now start the Samba services by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code> service smb start
@@ -548,7 +548,7 @@ hosts:      files dns wins
                         Your server is ready for validation testing. Do not proceed with the steps in
                         <a class="link" href="Big500users.html#ch5-domsvrspec" title="Configuration Specific to Domain Member Servers: BLDG1, BLDG2">&#8220;Configuration Specific to Domain Member Servers: BLDG1, BLDG2&#8221;</a> until after the operation of the server has been
                         validated following the same methods as outlined in <a class="link" href="secure.html#ch4valid" title="Validation">&#8220;Validation&#8221;</a>.
-                        </p></li></ol></div></div></div><div class="example"><a name="ch5-massivesmb"></a><p class="title"><b>Example�4.1.�Server: MASSIVE (PDC), File: <code class="filename">/etc/samba/smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2567829"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2567841"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2567853"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2567865"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567877"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2567888"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2567900"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567912"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567924"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2567937"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2567949"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567961"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567974"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567986"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567998"></a><em class="parameter"><code>include = /etc/samba/dc-common.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2568019"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568030"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2568042"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2568063"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568074"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2568086"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2568107"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568119"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2568130"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-dc-common"></a><p class="title"><b>Example�4.2.�Server: MASSIVE (PDC), File: <code class="filename">/etc/samba/dc-common.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568178"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2568190"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2568202"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2568214"></a><em class="parameter"><code>logon path = \%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2568226"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2568238"></a><em class="parameter"><code>logon home = \%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2568250"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568261"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568273"></a><em class="parameter"><code>include = /etc/samba/common.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2568294"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2568306"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2568317"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568329"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2568349"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2568361"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2568373"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568385"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2568405"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2568417"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2568429"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568440"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-commonsmb"></a><p class="title"><b>Example�4.3.�Common Samba Configuration File: <code class="filename">/etc/samba/common.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568485"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2568497"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2568508"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2568520"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2568532"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2568543"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2568555"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2568567"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568579"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2568590"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568603"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2568615"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2568627"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568639"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568651"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2568662"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2568674"></a><em class="parameter"><code>veto oplock files = /*.doc/*.xls/*.mdb/</code></em></td></tr><tr><td><a class="indexterm" name="id2568686"></a><em class="parameter"><code>include =  </code></em></td></tr><tr><td># Share and Service Definitions are common to all servers</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2568711"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2568723"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2568734"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568746"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568758"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568769"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568781"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2568802"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568814"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2568825"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2568837"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-bldg1-smb"></a><p class="title"><b>Example�4.4.�Server: BLDG1 (Member), File: smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568880"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2568891"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2568903"></a><em class="parameter"><code>include = /etc/samba/dom-mem.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-bldg2-smb"></a><p class="title"><b>Example�4.5.�Server: BLDG2 (Member), File: smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568946"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2568958"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2568970"></a><em class="parameter"><code>include = /etc/samba/dom-mem.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-dommem-smb"></a><p class="title"><b>Example�4.6.�Common Domain Member Include File: dom-mem.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2569013"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2569025"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2569038"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2569049"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2569061"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2569073"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2569085"></a><em class="parameter"><code>include = /etc/samba/common.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="massive-dhcp"></a><p class="title"><b>Example�4.7.�Server: MASSIVE, File: dhcpd.conf</b></p><div class="example-contents"><pre class="screen">
+                        </p></li></ol></div></div></div><div class="example"><a name="ch5-massivesmb"></a><p class="title"><b>Example�4.1.�Server: MASSIVE (PDC), File: <code class="filename">/etc/samba/smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2567827"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2567839"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2567851"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2567862"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567874"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2567886"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2567898"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567910"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567922"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2567934"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2567947"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567959"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2567972"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567984"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2567996"></a><em class="parameter"><code>include = /etc/samba/dc-common.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2568016"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568028"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2568040"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2568060"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568072"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2568084"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2568104"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568116"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2568128"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-dc-common"></a><p class="title"><b>Example�4.2.�Server: MASSIVE (PDC), File: <code class="filename">/etc/samba/dc-common.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568176"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2568188"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2568200"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2568212"></a><em class="parameter"><code>logon path = \%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2568224"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2568236"></a><em class="parameter"><code>logon home = \%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2568247"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568259"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568271"></a><em class="parameter"><code>include = /etc/samba/common.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2568292"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2568303"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2568315"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568327"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2568347"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2568359"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2568371"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568382"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2568403"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2568415"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2568427"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568438"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-commonsmb"></a><p class="title"><b>Example�4.3.�Common Samba Configuration File: <code class="filename">/etc/samba/common.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568483"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2568494"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2568506"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2568517"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2568529"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2568541"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2568553"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2568565"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568576"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2568588"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2568600"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2568613"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2568625"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568636"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568648"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2568660"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2568672"></a><em class="parameter"><code>veto oplock files = /*.doc/*.xls/*.mdb/</code></em></td></tr><tr><td><a class="indexterm" name="id2568684"></a><em class="parameter"><code>include =  </code></em></td></tr><tr><td># Share and Service Definitions are common to all servers</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2568709"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2568720"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2568732"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568744"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568755"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568767"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568779"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2568800"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2568811"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2568823"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2568835"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-bldg1-smb"></a><p class="title"><b>Example�4.4.�Server: BLDG1 (Member), File: smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568877"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2568889"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2568901"></a><em class="parameter"><code>include = /etc/samba/dom-mem.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-bldg2-smb"></a><p class="title"><b>Example�4.5.�Server: BLDG2 (Member), File: smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2568944"></a><em class="parameter"><code>workgroup = MEGANET</code></em></td></tr><tr><td><a class="indexterm" name="id2568956"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2568967"></a><em class="parameter"><code>include = /etc/samba/dom-mem.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch5-dommem-smb"></a><p class="title"><b>Example�4.6.�Common Domain Member Include File: dom-mem.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2569011"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2569023"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2569035"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2569047"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2569059"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2569071"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2569082"></a><em class="parameter"><code>include = /etc/samba/common.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="massive-dhcp"></a><p class="title"><b>Example�4.7.�Server: MASSIVE, File: dhcpd.conf</b></p><div class="example-contents"><pre class="screen">
 # Abmas Accounting Inc.
 
 default-lease-time 86400;
@@ -898,8 +898,8 @@ net groupmap add ntgroup="Accounts Dept"       unixgroup=acctsdep type=d
 net groupmap add ntgroup="Financial Services"  unixgroup=finsrvcs type=d
 net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 </pre></div></div><br class="example-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch5-procstart"></a>Process Startup Configuration</h3></div></div></div><p>
-		<a class="indexterm" name="id2569434"></a>
-		<a class="indexterm" name="id2569441"></a>
+		<a class="indexterm" name="id2569438"></a>
+		<a class="indexterm" name="id2569445"></a>
         There are two essential steps to process startup configuration. A process
         must be configured so that it is automatically restarted each time the server
         is rebooted. This step involves use of the <code class="literal">chkconfig</code> tool that
@@ -908,7 +908,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
         directories. Links are created so that when the system run-level is changed, the
         necessary start or kill script is run.
         </p><p>
-        <a class="indexterm" name="id2569477"></a>
+        <a class="indexterm" name="id2569481"></a>
         In the event that a service is provided not as a daemon but via the internetworking
         super daemon (<code class="literal">inetd</code> or <code class="literal">xinetd</code>), then the <code class="literal">chkconfig</code>
         tool makes the necessary entries in the <code class="filename">/etc/xinetd.d</code> directory
@@ -918,10 +918,10 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
         Last, each service must be started to permit system validation to proceed. The following steps
 		are for a Red Hat Linux system, please adapt them to suit the target OS platform on which you 
 		are installing Samba.
-        </p><div class="procedure"><a name="id2569521"></a><p class="title"><b>Procedure�4.4.�Process Startup Configuration Steps</b></p><ol type="1"><li><p>
+        </p><div class="procedure"><a name="id2569525"></a><p class="title"><b>Procedure�4.4.�Process Startup Configuration Steps</b></p><ol type="1"><li><p>
                 Use the standard system tool to configure each service to restart
                 automatically at every system reboot. For example,
-                <a class="indexterm" name="id2569535"></a>
+                <a class="indexterm" name="id2569540"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig dhpc on
 <code class="prompt">root# </code> chkconfig named on
@@ -930,9 +930,9 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 <code class="prompt">root# </code> chkconfig swat on
 </pre><p>
                 </p></li><li><p>
-                <a class="indexterm" name="id2569585"></a>
-                <a class="indexterm" name="id2569592"></a>
-                <a class="indexterm" name="id2569599"></a>
+                <a class="indexterm" name="id2569589"></a>
+                <a class="indexterm" name="id2569596"></a>
+                <a class="indexterm" name="id2569603"></a>
                 Now start each service to permit the system to be validated.
                 Execute each of the following in the sequence shown:
 
@@ -946,11 +946,11 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
                 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch5wincfg"></a>Windows Client Configuration</h3></div></div></div><p>
 	The procedure for desktop client configuration for the network in this chapter is similar to
 	that used for the previous one. There are a few subtle changes that should be noted.
-	</p><div class="procedure"><a name="id2569665"></a><p class="title"><b>Procedure�4.5.�Windows Client Configuration Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2569669"></a><p class="title"><b>Procedure�4.5.�Windows Client Configuration Steps</b></p><ol type="1"><li><p>
 		Install MS Windows XP Professional. During installation, configure the client to use DHCP for 
 		TCP/IP protocol configuration.
-		<a class="indexterm" name="id2569678"></a>
-		<a class="indexterm" name="id2569685"></a>
+		<a class="indexterm" name="id2569683"></a>
+		<a class="indexterm" name="id2569689"></a>
 		DHCP configures all Windows clients to use the WINS Server address that has been defined
 		for the local subnet.
 		</p></li><li><p>
@@ -984,7 +984,8 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers, and you
 		also configure use of the identical printers that are located in the financial services department.
 		Install printers on each machine using the following steps:
-	</p><div class="procedure"><a name="id2569817"></a><p class="title"><b>Procedure�4.6.�Steps to Install Printer Drivers on Windows Clients</b></p><ol type="1"><li><p>
+
+			</p><div class="procedure"><a name="id2569820"></a><p class="title"><b>Procedure�4.6.�Steps to Install Printer Drivers on Windows Clients</b></p><ol type="1"><li><p>
 				Click <span class="guimenu">Start</span> &#8594; <span class="guimenuitem">Settings</span> &#8594; <span class="guimenuitem">Printers</span>+<span class="guiicon">Add Printer</span>+<span class="guibutton">Next</span>. Do not click <span class="guimenuitem">Network printer</span>.
 					Ensure that <span class="guimenuitem">Local printer</span> is selected.
 				</p></li><li><p>
@@ -1000,7 +1001,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 				<span class="guibutton">Finish</span>.
 				</p></li><li><p>
 				You may be prompted for the name of a file to print to. If so, close the
-				dialog panel. Right-click <span class="guiicon">HP LaserJet 6</span> &#8594; <span class="guimenuitem">Properties</span> &#8594; <span class="guisubmenu">Details (Tab)</span>+<span class="guibutton">Add Port</span>.
+				dialog panel. Right-click <span class="guiicon">HP LaserJet 6</span> &#8594; <span class="guimenuitem">Properties</span>.
 				</p></li><li><p>
 				In the <span class="guimenuitem">Network</span> panel, enter the name of
 				the print queue on the Samba server as follows: <code class="constant">\\BLDG1\hplj6a</code>.
@@ -1016,7 +1017,8 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 				procedures, it would be wise to document the need to redirect the printer
 				configuration (as well as the applications server drive mapping) to the
 				server on the network segment on which the workstation is to be located.
-				</p></li></ol></div></li><li><p>
+				</p></li></ol></div><p>
+		</p></li><li><p>
 		When you are satisfied that the staging systems are complete, use the appropriate procedure to
 		remove the client from the domain. Reboot the system, and then log on as the local administrator
 		and clean out all temporary files stored on the system. Before shutting down, use the disk
@@ -1036,7 +1038,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		user, of course.
 		</p></li><li><p>
 		Instruct all users to log onto the workstation using their assigned username and password.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570125"></a>Key Points Learned</h3></div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570124"></a>Key Points Learned</h3></div></div></div><p>
 		The network you have just deployed has been a valuable exercise in forced constraint.
 		You have deployed a network that works well, although you may soon start to see
 		performance problems, at which time the modifications demonstrated in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a>
@@ -1052,33 +1054,33 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 			to resources on the domain member servers
 			</p></li><li><p>
 			The introduction of roaming profiles
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2570184"></a>Questions and Answers</h2></div></div></div><p>
-	</p><div class="qandaset"><dl><dt> <a href="Big500users.html#id2570200">
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2570183"></a>Questions and Answers</h2></div></div></div><p>
+	</p><div class="qandaset"><dl><dt> <a href="Big500users.html#id2570199">
 		The example smb.conf files in this chapter make use of the include facility.
 		How may I get to see what the actual working smb.conf settings are?
-		</a></dt><dt> <a href="Big500users.html#id2570249">
+		</a></dt><dt> <a href="Big500users.html#id2570248">
 		Why does the include file common.conf have an empty include statement?
-		</a></dt><dt> <a href="Big500users.html#id2570311">
+		</a></dt><dt> <a href="Big500users.html#id2570310">
 		I accept that the simplest configuration necessary to do the job is the best. The use of tdbsam
 		passdb backend is much simpler than having to manage an LDAP-based ldapsam passdb backend.
 		I tried using rsync to replicate the passdb.tdb, and it seems to work fine!
 		So what is the problem?
-		</a></dt><dt> <a href="Big500users.html#id2570366">
+		</a></dt><dt> <a href="Big500users.html#id2570365">
 		You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash?
 		</a></dt><dt> <a href="Big500users.html#id2570396">
 		How does the Windows client find the PDC?
-		</a></dt><dt> <a href="Big500users.html#id2570419">
+		</a></dt><dt> <a href="Big500users.html#id2570418">
 		Why did you enable IP forwarding (routing) only on the server called MASSIVE?
-		</a></dt><dt> <a href="Big500users.html#id2570450">
+		</a></dt><dt> <a href="Big500users.html#id2570449">
 		You did nothing special to implement roaming profiles. Why?
 		</a></dt><dt> <a href="Big500users.html#id2570469">
 		On the domain member computers, you configured winbind in the /etc/nsswitch.conf file.
 		You did not configure any PAM settings. Is this an omission?
-		</a></dt><dt> <a href="Big500users.html#id2570501">
+		</a></dt><dt> <a href="Big500users.html#id2570500">
 		You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this?
-		</a></dt><dt> <a href="Big500users.html#id2570543">
+		</a></dt><dt> <a href="Big500users.html#id2570542">
 		The domain controller has an auto-shutdown script. Isn't that dangerous?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2570200"></a><a name="id2570202"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2570199"></a><a name="id2570201"></a></td><td align="left" valign="top"><p>
 		The example <code class="filename">smb.conf</code> files in this chapter make use of the <em class="parameter"><code>include</code></em> facility.
 		How may I get to see what the actual working <code class="filename">smb.conf</code> settings are?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -1086,7 +1088,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 </p><pre class="screen">
 <code class="prompt">root# </code> testparm -s | less
 </pre><p>
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570249"></a><a name="id2570251"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570248"></a><a name="id2570250"></a></td><td align="left" valign="top"><p>
 		Why does the include file <code class="filename">common.conf</code> have an empty include statement?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The use of the empty include statement nullifies further includes. For example, let's say you 
@@ -1099,7 +1101,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		If the include parameter was not in the common.conf file, the final <code class="filename">smb.conf</code> file leaves
 		the include in place, even though the file it points to has already been included. This is a bug
 		that will be fixed at a future date.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570311"></a><a name="id2570313"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570310"></a><a name="id2570312"></a></td><td align="left" valign="top"><p>
 		I accept that the simplest configuration necessary to do the job is the best. The use of <em class="parameter"><code>tdbsam</code></em>
 		passdb backend is much simpler than having to manage an LDAP-based <em class="parameter"><code>ldapsam</code></em> passdb backend.
 		I tried using <code class="literal">rsync</code> to replicate the <code class="filename">passdb.tdb</code>, and it seems to work fine!
@@ -1109,7 +1111,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		contents between the PDC and BDCs. The most notable symptom is that workstations may not be able
 		to log onto the network following a reboot and may have to rejoin the domain to recover network
 		access capability.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570366"></a><a name="id2570368"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570365"></a><a name="id2570368"></a></td><td align="left" valign="top"><p>
 		You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		No. It is possible to have as many DHCP servers on a network segment as makes sense. A DHCP server
@@ -1125,14 +1127,14 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		obtains from the DHCP lease information the parameter that causes it to use directed UDP (UDP Unicast)
 		to register itself with the WINS server and to obtain enumeration of vital network information to 
 		enable it to operate successfully.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570419"></a><a name="id2570421"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570418"></a><a name="id2570420"></a></td><td align="left" valign="top"><p>
 		Why did you enable IP forwarding (routing) only on the server called <code class="constant">MASSIVE</code>?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The server called <code class="constant">MASSIVE</code> is acting as a router to the Internet. No other server
 		(BLDG1 or BLDG2) has any need for IP forwarding because they are attached only to their own network.
 		Route table entries are needed to direct MASSIVE to send all traffic intended for the remote network
 		segments to the router that is its gateway to them.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570450"></a><a name="id2570452"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570449"></a><a name="id2570451"></a></td><td align="left" valign="top"><p>
 		You did nothing special to implement roaming profiles. Why?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Unless configured to do otherwise, the default behavior with Samba-3 and Windows XP Professional
@@ -1146,7 +1148,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		member servers using Windows networking usernames and passwords, it is necessary to configure PAM
 		to enable the use of winbind. Samba makes use only of the identity resolution facilities of the name
 		service switch (NSS).
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570501"></a><a name="id2570503"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570500"></a><a name="id2570503"></a></td><td align="left" valign="top"><p>
 		You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Oh, I did not think you would notice that. It is there so that it can be used. This is more fully discussed
@@ -1155,7 +1157,7 @@ net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
 		of <code class="filename">smb.conf</code> <em class="parameter"><code>include</code></em> files because SWAT optimizes them out into an aggregated 
 		file but leaves in place a broken reference to the top-layer include file. SWAT was not designed to 
 		handle this functionality gracefully.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570543"></a><a name="id2570545"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2570542"></a><a name="id2570544"></a></td><td align="left" valign="top"><p>
 		The domain controller has an auto-shutdown script. Isn't that dangerous?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Well done, you spotted that! I guess it is dangerous. It is good to know that you can do this, though.
diff --git a/docs/htmldocs/Samba3-ByExample/DMSMig.html b/docs/htmldocs/Samba3-ByExample/DMSMig.html
index b4f22d7cd2..ef1db16894 100644
--- a/docs/htmldocs/Samba3-ByExample/DMSMig.html
+++ b/docs/htmldocs/Samba3-ByExample/DMSMig.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Domain Members, Updating Samba and Migration</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="net2000users.html" title="Chapter�6.�A Distributed 2000-User Network"><link rel="next" href="unixclients.html" title="Chapter�7.�Adding Domain Member Servers and Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Domain Members, Updating Samba and Migration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="net2000users.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="unixclients.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="DMSMig"></a>Part�II.�Domain Members, Updating Samba and Migration</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2589087"></a>Domain Members, Updating Samba and Migration</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Domain Members, Updating Samba and Migration</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="2000users.html" title="Chapter�6.�A Distributed 2000-User Network"><link rel="next" href="unixclients.html" title="Chapter�7.�Adding Domain Member Servers and Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Domain Members, Updating Samba and Migration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="2000users.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="unixclients.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="DMSMig"></a>Part�II.�Domain Members, Updating Samba and Migration</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2589098"></a>Domain Members, Updating Samba and Migration</h1></div></div></div><p>
 This section <span class="emphasis"><em>Samba-3 by Example</em></span> covers two main topics: How to add
 Samba Domain Member Servers and Samba Domain Member Clients to a Samba domain, the other
 subject is that of how to migrate from and NT4 Domain, a NetWare server, or from an earlier
@@ -7,4 +7,4 @@ Samba version to environments that use the most recent Samba-3 release.
 Those who are making use of the chapter on Adding UNIX clients and servers running Samba
 to a Samba or a Windows networking domain may also benefit by referring to the book
 <span class="emphasis"><em>The Official Samba-3 HOWTO and Reference Guide.</em></span>
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="unixclients.html">7. Adding Domain Member Servers and Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="unixclients.html#id2589228">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589282">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589317">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589345">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2589994">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590094">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596918">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596972">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrades.html">8. Updating Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrades.html#id2598125">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598221">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599550">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600245">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600542">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600746">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601160">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ntmigration.html">9. Migrating NT4 Domain to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntmigration.html#id2601332">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601417">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601472">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601658">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601981">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2602007">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2605013">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605051">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="nw4migration.html">10. Migrating NetWare Server to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="nw4migration.html#id2606026">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606137">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606228">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606305">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606495">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606504">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="net2000users.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="unixclients.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�6.�A Distributed 2000-User Network�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�7.�Adding Domain Member Servers and Clients</td></tr></table></div></body></html>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="unixclients.html">7. Adding Domain Member Servers and Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="unixclients.html#id2589239">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589292">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589328">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589356">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2590005">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590105">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596886">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596940">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrades.html">8. Updating Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrades.html#id2598100">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598196">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599525">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600227">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600519">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600723">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601137">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ntmigration.html">9. Migrating NT4 Domain to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntmigration.html#id2601309">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601394">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601449">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601635">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601958">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601984">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604990">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605028">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="nw4migration.html">10. Migrating NetWare Server to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="nw4migration.html#id2606004">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606120">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606233">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606310">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606500">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606509">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="2000users.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="unixclients.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�6.�A Distributed 2000-User Network�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�7.�Adding Domain Member Servers and Clients</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/DomApps.html b/docs/htmldocs/Samba3-ByExample/DomApps.html
index a35f836cb2..6f5c1fefbd 100644
--- a/docs/htmldocs/Samba3-ByExample/DomApps.html
+++ b/docs/htmldocs/Samba3-ByExample/DomApps.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Integrating Additional Services</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="kerberos.html" title="Chapter�11.�Active Directory, Kerberos, and Security"><link rel="next" href="HA.html" title="Chapter�13.�Performance, Reliability, and Availability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Integrating Additional Services</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="kerberos.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="HA.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DomApps"></a>Chapter�12.�Integrating Additional Services</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="DomApps.html#id2616020">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616051">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616160">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616193">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616349">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616373">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618225">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618286">Questions and Answers</a></span></dt></dl></div><p>
-	<a class="indexterm" name="id2615971"></a>
-	<a class="indexterm" name="id2615977"></a>
-	<a class="indexterm" name="id2615984"></a>
-	<a class="indexterm" name="id2615991"></a>
-	<a class="indexterm" name="id2615998"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Integrating Additional Services</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="kerberos.html" title="Chapter�11.�Active Directory, Kerberos, and Security"><link rel="next" href="HA.html" title="Chapter�13.�Performance, Reliability, and Availability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Integrating Additional Services</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="kerberos.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="HA.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DomApps"></a>Chapter�12.�Integrating Additional Services</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="DomApps.html#id2616145">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616176">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616287">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616320">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616476">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616493">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618345">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618406">Questions and Answers</a></span></dt></dl></div><p>
+	<a class="indexterm" name="id2616096"></a>
+	<a class="indexterm" name="id2616102"></a>
+	<a class="indexterm" name="id2616109"></a>
+	<a class="indexterm" name="id2616116"></a>
+	<a class="indexterm" name="id2616123"></a>
 	You've come a long way now. You have pretty much mastered Samba-3 for 
 	most uses it can be put to. Up until now, you have cast Samba-3 in the leading 
 	role, and where authentication was required, you have used one or another of 
@@ -14,7 +14,7 @@
 	implementing Samba and Samba-supported services in a domain controlled by 
 	the latest Windows authentication technologies. Let's get started  this is 
 	leading edge.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616020"></a>Introduction</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616145"></a>Introduction</h2></div></div></div><p>
 	Abmas has continued its miraculous growth; indeed, nothing seems to be able 
 	to stop its diversification into multiple (and seemingly unrelated) fields. 
 	Its latest acquisition is Abmas Snack Foods, a big player in the snack-food 
@@ -30,17 +30,17 @@
 	You have decided to set the ball rolling by introducing Samba-3 into the network 
 	gradually, taking over key services and easing the way to a full migration and, 
 	therefore, integration into Abmas's existing business later.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616051"></a>Assignment Tasks</h3></div></div></div><p>
-		<a class="indexterm" name="id2616059"></a>
-		<a class="indexterm" name="id2616068"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616176"></a>Assignment Tasks</h3></div></div></div><p>
+		<a class="indexterm" name="id2616184"></a>
+		<a class="indexterm" name="id2616193"></a>
 	        You've promised the skeptical Abmas Snack Foods management team 
 		that you can show them how Samba can ease itself and other Open Source 
 		technologies into their existing infrastructure and deliver sound business 
 		advantages. Cost cutting is high on their agenda (a major promise of the 
 		acquisition). You have chosen Web proxying and caching as your proving ground.
 		</p><p>
-		<a class="indexterm" name="id2616086"></a>
-		<a class="indexterm" name="id2616093"></a>
+		<a class="indexterm" name="id2616211"></a>
+		<a class="indexterm" name="id2616218"></a>
 		Abmas Snack Foods has several thousand users housed at its head office 
 		and multiple regional offices, plants, and warehouses. A high proportion of 
 		the business's work is done online, so Internet access for most of these 
@@ -50,9 +50,9 @@
 		the team soon discovered proxying and caching. In fact, they became one of 
 		the earliest commercial users of Microsoft ISA.
 		</p><p>
-		<a class="indexterm" name="id2616114"></a>
-		<a class="indexterm" name="id2616121"></a>
-		<a class="indexterm" name="id2616128"></a>
+		<a class="indexterm" name="id2616249"></a>
+		<a class="indexterm" name="id2616256"></a>
+		<a class="indexterm" name="id2616262"></a>
 		The team is not happy with ISA. Because it never lived up to its marketing promises, 
 		it underperformed and had reliability problems. You have pounced on the opportunity 
 		to show what Open Source can do. The one thing they do like, however, is ISA's 
@@ -63,7 +63,7 @@
 		</p><p>
 		This is a hands-on exercise. You build software applications so
 		that you obtain the functionality Abmas needs.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616160"></a>Dissection and Discussion</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616287"></a>Dissection and Discussion</h2></div></div></div><p>
 	The key requirements in this business example are straightforward. You are not required 
 	to do anything new, just to replicate an existing system, not lose any existing features, 
 	and improve performance. The key points are:
@@ -73,20 +73,20 @@
 		Distributed system to accommodate load and geographical distribution of users
 		</p></li><li><p>
 		Seamless and transparent interoperability with the existing Active Directory domain
-		</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616193"></a>Technical Issues</h3></div></div></div><p>
-		<a class="indexterm" name="id2616201"></a>
-		<a class="indexterm" name="id2616208"></a>
-		<a class="indexterm" name="id2616215"></a>
-		<a class="indexterm" name="id2616221"></a>
-		<a class="indexterm" name="id2616228"></a>
-		<a class="indexterm" name="id2616235"></a>
-		<a class="indexterm" name="id2616242"></a>
-		<a class="indexterm" name="id2616249"></a>
-		<a class="indexterm" name="id2616256"></a>
-		<a class="indexterm" name="id2616263"></a>
-		<a class="indexterm" name="id2616270"></a>
-		<a class="indexterm" name="id2616277"></a>
-		<a class="indexterm" name="id2616286"></a><a class="indexterm" name="id2616292"></a>
+		</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616320"></a>Technical Issues</h3></div></div></div><p>
+		<a class="indexterm" name="id2616327"></a>
+		<a class="indexterm" name="id2616334"></a>
+		<a class="indexterm" name="id2616341"></a>
+		<a class="indexterm" name="id2616348"></a>
+		<a class="indexterm" name="id2616355"></a>
+		<a class="indexterm" name="id2616362"></a>
+		<a class="indexterm" name="id2616368"></a>
+		<a class="indexterm" name="id2616375"></a>
+		<a class="indexterm" name="id2616382"></a>
+		<a class="indexterm" name="id2616389"></a>
+		<a class="indexterm" name="id2616396"></a>
+		<a class="indexterm" name="id2616403"></a>
+		<a class="indexterm" name="id2616412"></a><a class="indexterm" name="id2616418"></a>
 		Functionally, the user's Internet Explorer requests a browsing session with the 
 		Squid proxy, for which it offers its AD authentication token. Squid hands off 
 		the authentication request to the Samba-3 authentication helper application
@@ -107,25 +107,25 @@
 			Configuring, compiling, and then installing the supporting Samba-3 components
 			</p></li><li><p>
 			Tying it all together
-			</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616349"></a>Political Issues</h3></div></div></div><p>
+			</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616476"></a>Political Issues</h3></div></div></div><p>
 		You are a stranger in a strange land, and all eyes are upon you. Some would even like to see 
 		you fail. For you to gain the trust of your newly acquired IT people, it is essential that your 
 		solution does everything the old one did, but does it better in every way. Only then 
 		will the entrenched positions consider taking up your new way of doing things on a 
 		wider scale.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616373"></a>Implementation</h2></div></div></div><p>
-	<a class="indexterm" name="id2616381"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616493"></a>Implementation</h2></div></div></div><p>
+	<a class="indexterm" name="id2616501"></a>
 	First, your system needs to be prepared and in a known good state to proceed. This consists 
 	of making sure that everything the system depends on is present and that everything that could 
 	interfere or conflict with the system is removed. You will be configuring the Squid and Samba-3 
 	packages and updating them if necessary. If conflicting packages of these programs are installed, 
 	they must be removed.
 	</p><p>
-	<a class="indexterm" name="id2616398"></a>
+	<a class="indexterm" name="id2616518"></a>
 	The following packages should be available on your Red Hat Linux system:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2616413"></a>
-		<a class="indexterm" name="id2616420"></a>
+		<a class="indexterm" name="id2616533"></a>
+		<a class="indexterm" name="id2616540"></a>
 		krb5-libs
 		</p></li><li><p>
 		krb5-devel
@@ -136,14 +136,14 @@
 		</p></li><li><p>
 		pam_krb5
 		</p></li></ul></div><p>
-	<a class="indexterm" name="id2616450"></a>
+	<a class="indexterm" name="id2616570"></a>
 	In the case of SUSE Linux, these packages are called:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
                 heimdal-lib
                 </p></li><li><p>
                 heimdal-devel
                 </p></li><li><p>
-		<a class="indexterm" name="id2616475"></a>
+		<a class="indexterm" name="id2616595"></a>
                 heimdal
                 </p></li><li><p>
                 pam_krb5
@@ -152,26 +152,26 @@
 	them from the vendor's installation media. Follow the administrative guide
 	for your Linux system to ensure that the packages are correctly updated.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2616500"></a>
-	<a class="indexterm" name="id2616507"></a>
-	<a class="indexterm" name="id2616514"></a>
+	<a class="indexterm" name="id2616620"></a>
+	<a class="indexterm" name="id2616627"></a>
+	<a class="indexterm" name="id2616634"></a>
 	If the requirement is for interoperation with MS Windows Server 2003, it
 	will be necessary to ensure that you are using MIT Kerberos version 1.3.1
 	or later. Red Hat Linux 9 ships with MIT Kerberos 1.2.7 and thus requires
 	updating.
 	</p><p>
-	<a class="indexterm" name="id2616528"></a>
-	<a class="indexterm" name="id2616534"></a>
+	<a class="indexterm" name="id2616647"></a>
+	<a class="indexterm" name="id2616654"></a>
 	Heimdal 0.6 or later is required in the case of SUSE Linux. SUSE Enterprise
 	Linux Server 8 ships with Heimdal 0.4. SUSE 9 ships with the necessary version.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch10-one"></a>Removal of Pre-Existing Conflicting RPMs</h3></div></div></div><p>
-	<a class="indexterm" name="id2616557"></a>
+	<a class="indexterm" name="id2616677"></a>
 	If Samba and/or Squid RPMs are installed, they should be updated. You can 
 	build both from source.
 	</p><p>
-	<a class="indexterm" name="id2616569"></a>
-	<a class="indexterm" name="id2616576"></a>
-	<a class="indexterm" name="id2616582"></a>
+	<a class="indexterm" name="id2616689"></a>
+	<a class="indexterm" name="id2616695"></a>
+	<a class="indexterm" name="id2616702"></a>
 	Locating the packages to be un-installed can be achieved by running:
 </p><pre class="screen">
 <code class="prompt">root# </code> rpm -qa | grep -i samba
@@ -181,11 +181,11 @@
 </p><pre class="screen">
 <code class="prompt">root# </code> rpm -e samba-common
 </pre><p>
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616622"></a>Kerberos Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2616630"></a>
-	<a class="indexterm" name="id2616637"></a>
-	<a class="indexterm" name="id2616647"></a>
-	<a class="indexterm" name="id2616653"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616742"></a>Kerberos Configuration</h3></div></div></div><p>
+	<a class="indexterm" name="id2616750"></a>
+	<a class="indexterm" name="id2616757"></a>
+	<a class="indexterm" name="id2616766"></a>
+	<a class="indexterm" name="id2616773"></a>
 	The systems Kerberos installation must be configured to communicate with 
 	your primary Active Directory server (ADS KDC).
 	</p><p>
@@ -193,13 +193,13 @@
 	although the current default Red Hat MIT version 1.2.7 gives acceptable results 
 	unless you are using Windows 2003 servers.
 	</p><p>
-	<a class="indexterm" name="id2616672"></a>
-	<a class="indexterm" name="id2616679"></a>
-	<a class="indexterm" name="id2616686"></a>
-	<a class="indexterm" name="id2616692"></a>
-	<a class="indexterm" name="id2616699"></a>
-	<a class="indexterm" name="id2616708"></a>
-	<a class="indexterm" name="id2616715"></a>
+	<a class="indexterm" name="id2616792"></a>
+	<a class="indexterm" name="id2616799"></a>
+	<a class="indexterm" name="id2616806"></a>
+	<a class="indexterm" name="id2616812"></a>
+	<a class="indexterm" name="id2616819"></a>
+	<a class="indexterm" name="id2616828"></a>
+	<a class="indexterm" name="id2616835"></a>
 	Officially, neither MIT (1.3.4) nor Heimdal (0.63) Kerberos needs an <code class="filename">/etc/krb5.conf</code> 
 	file in order to work correctly. All ADS domains automatically create SRV records in the 
 	DNS zone <code class="constant">Kerberos.REALM.NAME</code> for each KDC in the realm. Since both 
@@ -207,25 +207,25 @@
 	automatically find the KDCs. In addition, <code class="filename">krb5.conf</code> allows 
 	specifying only a single KDC, even if there is more than one. Using the DNS lookup 
 	allows the KRB5 libraries to use whichever KDCs are available.
-	</p><div class="procedure"><a name="id2616749"></a><p class="title"><b>Procedure�12.1.�Kerberos Configuration Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2616760"></a>
+	</p><div class="procedure"><a name="id2616869"></a><p class="title"><b>Procedure�12.1.�Kerberos Configuration Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2616880"></a>
 		If you find the need to manually configure the <code class="filename">krb5.conf</code>, you should edit it
 		to have the contents shown in <a class="link" href="DomApps.html#ch10-krb5conf" title="Example�12.1.�Kerberos Configuration File: /etc/krb5.conf">&#8220;Kerberos Configuration  File: /etc/krb5.conf&#8221;</a>. The final fully qualified path for this file 
 		should be <code class="filename">/etc/krb5.conf</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2616795"></a>
-		<a class="indexterm" name="id2616802"></a>
-		<a class="indexterm" name="id2616809"></a>
-		<a class="indexterm" name="id2616816"></a>
-		<a class="indexterm" name="id2616822"></a>
-		<a class="indexterm" name="id2616829"></a>
-		<a class="indexterm" name="id2616836"></a>
-		<a class="indexterm" name="id2616843"></a>
-		<a class="indexterm" name="id2616850"></a>
-		<a class="indexterm" name="id2616859"></a>
-		<a class="indexterm" name="id2616866"></a>
-		<a class="indexterm" name="id2616873"></a>
-		<a class="indexterm" name="id2616880"></a>
+		<a class="indexterm" name="id2616915"></a>
+		<a class="indexterm" name="id2616922"></a>
+		<a class="indexterm" name="id2616929"></a>
+		<a class="indexterm" name="id2616936"></a>
+		<a class="indexterm" name="id2616942"></a>
+		<a class="indexterm" name="id2616949"></a>
+		<a class="indexterm" name="id2616956"></a>
+		<a class="indexterm" name="id2616963"></a>
+		<a class="indexterm" name="id2616970"></a>
+		<a class="indexterm" name="id2616979"></a>
+		<a class="indexterm" name="id2616986"></a>
+		<a class="indexterm" name="id2616993"></a>
+		<a class="indexterm" name="id2616999"></a>
 		The following gotchas often catch people out. Kerberos is case sensitive. Your realm must
 		be in UPPERCASE, or you will get an error: &#8220;<span class="quote">Cannot find KDC for requested realm while getting
 		initial credentials</span>&#8221;.  Kerberos is picky about time synchronization. The time
@@ -241,7 +241,7 @@
 		NetBIOS name. If Kerberos cannot do this reverse lookup, you will get a local error
 		when you try to join the realm.
 		</p></li><li><p>
-		<a class="indexterm" name="id2616924"></a>
+		<a class="indexterm" name="id2617044"></a>
 		You are now ready to test your installation by issuing the command:
 </p><pre class="screen">
 <code class="prompt">root# </code> kinit [USERNAME@REALM]
@@ -261,29 +261,29 @@ Password for ADMINISTRATOR@LONDON.ABMAS.BIZ:
 	LONDON.ABMAS.BIZ = {
 	kdc = w2k3s.london.abmas.biz
 	}
-</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2616989"></a>
+</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2617108"></a>
 	The command
 </p><pre class="screen">
 <code class="prompt">root# </code> klist -e 
 </pre><p>
 	shows the Kerberos tickets cached by the system.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617012"></a>Samba Configuration</h4></div></div></div><p>
-	<a class="indexterm" name="id2617020"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617132"></a>Samba Configuration</h4></div></div></div><p>
+	<a class="indexterm" name="id2617139"></a>
 	Samba must be configured to correctly use Active Directory. Samba-3 must be used, since it 
 	has the necessary components to interface with Active Directory.
-	</p><div class="procedure"><a name="id2617030"></a><p class="title"><b>Procedure�12.2.�Securing Samba-3 With ADS Support Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2617042"></a>
-		<a class="indexterm" name="id2617049"></a>
-		<a class="indexterm" name="id2617056"></a>
-		<a class="indexterm" name="id2617063"></a>
-		<a class="indexterm" name="id2617070"></a>
+	</p><div class="procedure"><a name="id2617150"></a><p class="title"><b>Procedure�12.2.�Securing Samba-3 With ADS Support Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2617162"></a>
+		<a class="indexterm" name="id2617169"></a>
+		<a class="indexterm" name="id2617176"></a>
+		<a class="indexterm" name="id2617183"></a>
+		<a class="indexterm" name="id2617189"></a>
 		Download the latest stable Samba-3 for Red Hat Linux from the official Samba Team
 		<a class="ulink" href="http://ftp.samba.org" target="_top">FTP site.</a> The official Samba Team
 		RPMs for Red Hat Fedora Linux contain the <code class="literal">ntlm_auth</code> tool
 		needed, and are linked against MIT KRB5 version 1.3.1 and therefore are ready for use.
 		</p><p>
-		<a class="indexterm" name="id2617096"></a>
-		<a class="indexterm" name="id2617103"></a>
+		<a class="indexterm" name="id2617216"></a>
+		<a class="indexterm" name="id2617223"></a>
 		The necessary, validated RPM packages for SUSE Linux may be obtained from
 		the <a class="ulink" href="ftp://ftp.sernet.de/pub/samba" target="_top">SerNet</a> FTP site that
 		is located in Germany. All SerNet RPMs are validated, have the necessary
@@ -293,11 +293,11 @@ Password for ADMINISTRATOR@LONDON.ABMAS.BIZ:
 		Using your favorite editor, change the <code class="filename">/etc/samba/smb.conf</code>
 		file so it has contents similar to the example shown in <a class="link" href="DomApps.html#ch10-smbconf" title="Example�12.2.�Samba Configuration File: /etc/samba/smb.conf">&#8220;Samba Configuration  File: /etc/samba/smb.conf&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2617154"></a>
-		<a class="indexterm" name="id2617161"></a>
-		<a class="indexterm" name="id2617168"></a>i
-		<a class="indexterm" name="id2617179"></a>
-		<a class="indexterm" name="id2617186"></a>
+		<a class="indexterm" name="id2617274"></a>
+		<a class="indexterm" name="id2617281"></a>
+		<a class="indexterm" name="id2617288"></a>i
+		<a class="indexterm" name="id2617299"></a>
+		<a class="indexterm" name="id2617306"></a>
 		Next you need to create a computer account in the Active Directory. 
 		This sets up the trust relationship needed for other clients to 
 		authenticate to the Samba server with an Active Directory Kerberos ticket. 
@@ -307,11 +307,11 @@ Password for ADMINISTRATOR@LONDON.ABMAS.BIZ:
 <code class="prompt">root# </code> net ads join -U administrator%vulcon
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2617220"></a>
-		<a class="indexterm" name="id2617227"></a>
-		<a class="indexterm" name="id2617234"></a>
-		<a class="indexterm" name="id2617240"></a>
-		<a class="indexterm" name="id2617247"></a>
+		<a class="indexterm" name="id2617340"></a>
+		<a class="indexterm" name="id2617347"></a>
+		<a class="indexterm" name="id2617354"></a>
+		<a class="indexterm" name="id2617360"></a>
+		<a class="indexterm" name="id2617367"></a>
 		Your new Samba binaries must be started in the standard manner as is applicable
 		to the platform you are running on. Alternatively, start your Active Directory-enabled Samba with the following commands:
 </p><pre class="screen">
@@ -320,11 +320,11 @@ Password for ADMINISTRATOR@LONDON.ABMAS.BIZ:
 <code class="prompt">root# </code> winbindd -D
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2617288"></a>
-		<a class="indexterm" name="id2617295"></a>
-		<a class="indexterm" name="id2617304"></a>
-		<a class="indexterm" name="id2617311"></a>
-		<a class="indexterm" name="id2617318"></a>
+		<a class="indexterm" name="id2617408"></a>
+		<a class="indexterm" name="id2617415"></a>
+		<a class="indexterm" name="id2617424"></a>
+		<a class="indexterm" name="id2617431"></a>
+		<a class="indexterm" name="id2617438"></a>
 		We now need to test that Samba is communicating with the Active 
 		Directory domain; most specifically, we want to see whether winbind 
 		is enumerating users and groups. Issue the following commands:
@@ -357,8 +357,8 @@ LONDON+DnsUpdateProxy
 </pre><p>
 		This enumerates all the groups in your Active Directory tree.
 		</p></li><li><p>
-		<a class="indexterm" name="id2617382"></a>
-		<a class="indexterm" name="id2617389"></a>
+		<a class="indexterm" name="id2617502"></a>
+		<a class="indexterm" name="id2617509"></a>
 		Squid uses the <code class="literal">ntlm_auth</code> helper build with Samba-3.
 		You may test <code class="literal">ntlm_auth</code> with the command:
 </p><pre class="screen">
@@ -370,14 +370,14 @@ password: XXXXXXXX
 <code class="prompt">root# </code> NT_STATUS_OK: Success (0x0)
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2617441"></a>
-		<a class="indexterm" name="id2617448"></a>
-		<a class="indexterm" name="id2617455"></a>
-		<a class="indexterm" name="id2617462"></a>
-		<a class="indexterm" name="id2617468"></a>
-		<a class="indexterm" name="id2617475"></a>
-		<a class="indexterm" name="id2617482"></a>
-		<a class="indexterm" name="id2617489"></a>
+		<a class="indexterm" name="id2617561"></a>
+		<a class="indexterm" name="id2617568"></a>
+		<a class="indexterm" name="id2617575"></a>
+		<a class="indexterm" name="id2617581"></a>
+		<a class="indexterm" name="id2617588"></a>
+		<a class="indexterm" name="id2617595"></a>
+		<a class="indexterm" name="id2617602"></a>
+		<a class="indexterm" name="id2617609"></a>
 		The <code class="literal">ntlm_auth</code> helper, when run from a command line as the user 
 		&#8220;<span class="quote">root</span>&#8221;, authenticates against your Active Directory domain (with 
 		the aid of winbind). It manages this by reading from the winbind privileged pipe. 
@@ -395,37 +395,37 @@ password: XXXXXXXX
 <code class="prompt">root# </code> chgrp squid /var/lib/samba/winbindd_privileged
 <code class="prompt">root# </code> chmod 750 /var/lib/samba/winbindd_privileged
 </pre><p>
-		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617564"></a>NSS Configuration</h4></div></div></div><p>
-	<a class="indexterm" name="id2617572"></a>
-	<a class="indexterm" name="id2617578"></a>
-	<a class="indexterm" name="id2617585"></a>
+		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617684"></a>NSS Configuration</h4></div></div></div><p>
+	<a class="indexterm" name="id2617692"></a>
+	<a class="indexterm" name="id2617698"></a>
+	<a class="indexterm" name="id2617705"></a>
 	For Squid to benefit from Samba-3, NSS must be updated to allow winbind as a valid route to user authentication.
 	</p><p>
 	Edit your <code class="filename">/etc/nsswitch.conf</code> file so it has the parameters shown
 	in <a class="link" href="DomApps.html#ch10-etcnsscfg" title="Example�12.3.�NSS Configuration File Extract File: /etc/nsswitch.conf">&#8220;NSS Configuration File Extract  File: /etc/nsswitch.conf&#8221;</a>.
-	</p><div class="example"><a name="ch10-smbconf"></a><p class="title"><b>Example�12.2.�Samba Configuration  File: <code class="filename">/etc/samba/smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617643"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2617655"></a><em class="parameter"><code>netbios name = W2K3S</code></em></td></tr><tr><td><a class="indexterm" name="id2617667"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2617679"></a><em class="parameter"><code>security = ads</code></em></td></tr><tr><td><a class="indexterm" name="id2617690"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617702"></a><em class="parameter"><code>password server = w2k3s.london.abmas.biz</code></em></td></tr><tr><td># separate domain and username with '/', like DOMAIN/username</td></tr><tr><td><a class="indexterm" name="id2617719"></a><em class="parameter"><code>winbind separator = /</code></em></td></tr><tr><td># use UIDs from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2617735"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td># use GIDs from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2617750"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td># allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2617766"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617778"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617790"></a><em class="parameter"><code>winbind user default domain = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch10-etcnsscfg"></a><p class="title"><b>Example�12.3.�NSS Configuration File Extract  File: <code class="filename">/etc/nsswitch.conf</code></b></p><div class="example-contents"><pre class="screen">
+	</p><div class="example"><a name="ch10-smbconf"></a><p class="title"><b>Example�12.2.�Samba Configuration  File: <code class="filename">/etc/samba/smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617763"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2617775"></a><em class="parameter"><code>netbios name = W2K3S</code></em></td></tr><tr><td><a class="indexterm" name="id2617787"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2617798"></a><em class="parameter"><code>security = ads</code></em></td></tr><tr><td><a class="indexterm" name="id2617810"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617822"></a><em class="parameter"><code>password server = w2k3s.london.abmas.biz</code></em></td></tr><tr><td># separate domain and username with '/', like DOMAIN/username</td></tr><tr><td><a class="indexterm" name="id2617838"></a><em class="parameter"><code>winbind separator = /</code></em></td></tr><tr><td># use UIDs from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2617854"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td># use GIDs from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2617870"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td># allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2617886"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617898"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2617910"></a><em class="parameter"><code>winbind user default domain = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch10-etcnsscfg"></a><p class="title"><b>Example�12.3.�NSS Configuration File Extract  File: <code class="filename">/etc/nsswitch.conf</code></b></p><div class="example-contents"><pre class="screen">
 passwd: files winbind
 shadow: files
 group: files winbind
-</pre></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617829"></a>Squid Configuration</h4></div></div></div><p>
-	<a class="indexterm" name="id2617837"></a>
-	<a class="indexterm" name="id2617844"></a>
+</pre></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617949"></a>Squid Configuration</h4></div></div></div><p>
+	<a class="indexterm" name="id2617957"></a>
+	<a class="indexterm" name="id2617964"></a>
 	Squid must be configured correctly to interact with the Samba-3 
 	components that handle Active Directory authentication.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617859"></a>Configuration</h3></div></div></div></div><div class="procedure"><a name="id2617864"></a><p class="title"><b>Procedure�12.3.�Squid Configuration Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2617876"></a>
-		<a class="indexterm" name="id2617882"></a>
-		<a class="indexterm" name="id2617890"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617978"></a>Configuration</h3></div></div></div></div><div class="procedure"><a name="id2617984"></a><p class="title"><b>Procedure�12.3.�Squid Configuration Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2617996"></a>
+		<a class="indexterm" name="id2618002"></a>
+		<a class="indexterm" name="id2618010"></a>
 		If your Linux distribution is SUSE Linux 9, the version of Squid 
 		supplied is already enabled to use the winbind helper agent. You
 		can therefore omit the steps that would build the Squid binary
 		programs.
 		</p></li><li><p>
-		<a class="indexterm" name="id2617908"></a>
-		<a class="indexterm" name="id2617914"></a>
-		<a class="indexterm" name="id2617921"></a>
-		<a class="indexterm" name="id2617928"></a>
-		<a class="indexterm" name="id2617935"></a>
+		<a class="indexterm" name="id2618027"></a>
+		<a class="indexterm" name="id2618034"></a>
+		<a class="indexterm" name="id2618041"></a>
+		<a class="indexterm" name="id2618048"></a>
+		<a class="indexterm" name="id2618055"></a>
 		Squid, by default, runs as the user <code class="constant">nobody</code>. You need to 
 		add a system user <code class="constant">squid</code> and a system group 
 		<code class="constant">squid</code> if they are not set up already (if the default 
@@ -433,16 +433,16 @@ group: files winbind
 		<code class="constant">squid</code> user in <code class="filename">/etc/passwd</code> 
 		and a <code class="constant">squid</code> group in <code class="filename">/etc/group</code> if these aren't there already.
 		</p></li><li><p>
-		<a class="indexterm" name="id2617982"></a>
-		<a class="indexterm" name="id2617989"></a>
+		<a class="indexterm" name="id2618102"></a>
+		<a class="indexterm" name="id2618109"></a>
 		You now need to change the permissions on Squid's <code class="constant">var</code>
 		directory.  Enter the following command:
 </p><pre class="screen">
 <code class="prompt">root# </code> chown -R squid /var/cache/squid
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2618020"></a>
-		<a class="indexterm" name="id2618027"></a>
+		<a class="indexterm" name="id2618140"></a>
+		<a class="indexterm" name="id2618147"></a>
 		Squid must also have control over its logging. Enter the following commands:
 </p><pre class="screen">
 <code class="prompt">root# </code> chown -R chown squid:squid /var/log/squid
@@ -456,11 +456,11 @@ group: files winbind
 <code class="prompt">root# </code> chmod 770 /var/cache/squid
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2618087"></a>
+		<a class="indexterm" name="id2618207"></a>
 		The <code class="filename">/etc/squid/squid.conf</code> file must be edited to include the lines from 
 		<a class="link" href="DomApps.html#etcsquidcfg" title="Example�12.4.�Squid Configuration File Extract /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]">&#8220;Squid Configuration File Extract  /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]&#8221;</a> and <a class="link" href="DomApps.html#etcsquid2" title="Example�12.5.�Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]">&#8220;Squid Configuration File extract  File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2618121"></a>
+		<a class="indexterm" name="id2618241"></a>
 		You must create Squid's cache directories before it may be run.  Enter the following command: 
 </p><pre class="screen">
 <code class="prompt">root# </code> squid -z
@@ -487,23 +487,23 @@ group: files winbind
 	auth_param basic credentialsttl 2 hours
 	acl AuthorizedUsers proxy_auth REQUIRED
 	http_access allow all AuthorizedUsers
-</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618225"></a>Key Points Learned</h3></div></div></div><p>
-		<a class="indexterm" name="id2618233"></a>
-		<a class="indexterm" name="id2618240"></a>
-		<a class="indexterm" name="id2618247"></a>
-		<a class="indexterm" name="id2618254"></a>
-		<a class="indexterm" name="id2618266"></a>
+</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618345"></a>Key Points Learned</h3></div></div></div><p>
+		<a class="indexterm" name="id2618353"></a>
+		<a class="indexterm" name="id2618360"></a>
+		<a class="indexterm" name="id2618367"></a>
+		<a class="indexterm" name="id2618374"></a>
+		<a class="indexterm" name="id2618386"></a>
 		Microsoft Windows networking protocols permeate the spectrum of technologies that Microsoft
 		Windows clients use, even when accessing traditional services such as Web browsers. Depending 
 		on whom you discuss this with, this is either good or bad. No matter how you might evaluate this,
 		the use of NTLMSSP as the authentication protocol for Web proxy access has some advantages over
 		the cookie-based authentication regime used by all competing browsers. It is Samba's implementation
 		of NTLMSSP that makes it attractive to implement the solution that has been demonstrated in this chapter.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618286"></a>Questions and Answers</h2></div></div></div><p>
-	<a class="indexterm" name="id2618294"></a>
-	<a class="indexterm" name="id2618301"></a>
-	<a class="indexterm" name="id2618308"></a>
-	<a class="indexterm" name="id2618314"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618406"></a>Questions and Answers</h2></div></div></div><p>
+	<a class="indexterm" name="id2618414"></a>
+	<a class="indexterm" name="id2618421"></a>
+	<a class="indexterm" name="id2618428"></a>
+	<a class="indexterm" name="id2618434"></a>
 	The development of the <code class="literal">ntlm_auth</code> module was first discussed in many Open Source circles
 	in 2002. At the SambaXP conference in Goettingen, Germany, Mr. Francesco Chemolli demonstrated the use of 
 	<code class="literal">ntlm_auth</code> during one of the late developer meetings that took place. Since that time, the 
@@ -522,34 +522,34 @@ group: files winbind
 	You would be well-advised to recognize that all cache-intensive proxying solutions demand a lot of memory.
 	Make certain that your Squid proxy server is equipped with sufficient memory to permit all proxy operations to run 
 	out of memory without invoking the overheads involved in the use of memory that has to be swapped to disk.
-	</p><div class="qandaset"><dl><dt> <a href="DomApps.html#id2618392">
+	</p><div class="qandaset"><dl><dt> <a href="DomApps.html#id2618520">
 		What does Samba have to do with Web proxy serving?
-		</a></dt><dt> <a href="DomApps.html#id2618558">
+		</a></dt><dt> <a href="DomApps.html#id2618686">
 		What other services does Samba provide?
-		</a></dt><dt> <a href="DomApps.html#id2618701">
+		</a></dt><dt> <a href="DomApps.html#id2618829">
 		Does use of Samba (ntlm_auth) improve the performance of Squid?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2618392"></a><a name="id2618394"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2618520"></a><a name="id2618522"></a></td><td align="left" valign="top"><p>
 		What does Samba have to do with Web proxy serving?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2618406"></a>
-		<a class="indexterm" name="id2618413"></a>
-		<a class="indexterm" name="id2618420"></a>
-		<a class="indexterm" name="id2618429"></a>
-		<a class="indexterm" name="id2618436"></a>
+		<a class="indexterm" name="id2618533"></a>
+		<a class="indexterm" name="id2618541"></a>
+		<a class="indexterm" name="id2618548"></a>
+		<a class="indexterm" name="id2618557"></a>
+		<a class="indexterm" name="id2618564"></a>
 		To provide transparent interoperability between Windows clients and the network services
 		that are used from them, Samba had to develop tools and facilities that deliver that feature. The benefit
 		of Open Source software is that it can readily be reused. The current <code class="literal">ntlm_auth</code>
 		module is basically a wrapper around authentication code from the core of the Samba project.
 		</p><p>
-		<a class="indexterm" name="id2618458"></a>
-		<a class="indexterm" name="id2618465"></a>
-		<a class="indexterm" name="id2618474"></a>
-		<a class="indexterm" name="id2618483"></a>
-		<a class="indexterm" name="id2618492"></a>
-		<a class="indexterm" name="id2618499"></a>
-		<a class="indexterm" name="id2618506"></a>
-		<a class="indexterm" name="id2618513"></a>
-		<a class="indexterm" name="id2618520"></a>
+		<a class="indexterm" name="id2618586"></a>
+		<a class="indexterm" name="id2618593"></a>
+		<a class="indexterm" name="id2618602"></a>
+		<a class="indexterm" name="id2618611"></a>
+		<a class="indexterm" name="id2618620"></a>
+		<a class="indexterm" name="id2618627"></a>
+		<a class="indexterm" name="id2618634"></a>
+		<a class="indexterm" name="id2618640"></a>
+		<a class="indexterm" name="id2618648"></a>
 		The <code class="literal">ntlm_auth</code> module supports basic plain-text authentication and NTLMSSP 
 		protocols. This module makes it possible for Web and FTP proxy requests to be authenticated without
 		the user being interrupted via his or her Windows logon credentials. This facility is available with
@@ -557,36 +557,36 @@ group: files winbind
 		There are a few open source initiatives to provide support for these protocols in the Apache Web server
 		also.
 		</p><p>
-		<a class="indexterm" name="id2618544"></a>
+		<a class="indexterm" name="id2618672"></a>
 		The short answer is that by adding a wrapper around key authentication components of Samba, other
 		projects (like Squid) can benefit from the labors expended in meeting user interoperability needs.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2618558"></a><a name="id2618560"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2618686"></a><a name="id2618688"></a></td><td align="left" valign="top"><p>
 		What other services does Samba provide?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2618572"></a>
-		<a class="indexterm" name="id2618579"></a>
-		<a class="indexterm" name="id2618586"></a>
-		<a class="indexterm" name="id2618592"></a>
-		<a class="indexterm" name="id2618599"></a>
+		<a class="indexterm" name="id2618699"></a>
+		<a class="indexterm" name="id2618706"></a>
+		<a class="indexterm" name="id2618713"></a>
+		<a class="indexterm" name="id2618720"></a>
+		<a class="indexterm" name="id2618727"></a>
 		Samba-3 is a file and print server. The core components that provide this functionality are <code class="literal">smbd</code>,
 		<code class="literal">nmbd</code>, and the identity resolver daemon, <code class="literal">winbindd</code>.
 		</p><p>
-		<a class="indexterm" name="id2618630"></a>
-		<a class="indexterm" name="id2618636"></a>
+		<a class="indexterm" name="id2618757"></a>
+		<a class="indexterm" name="id2618764"></a>
 		Samba-3 is an SMB/CIFS client. The core component that provides this is called <code class="literal">smbclient</code>.
 		</p><p>
-		<a class="indexterm" name="id2618654"></a>
-		<a class="indexterm" name="id2618661"></a>
-		<a class="indexterm" name="id2618668"></a>
-		<a class="indexterm" name="id2618674"></a>
-		<a class="indexterm" name="id2618681"></a>
+		<a class="indexterm" name="id2618781"></a>
+		<a class="indexterm" name="id2618788"></a>
+		<a class="indexterm" name="id2618795"></a>
+		<a class="indexterm" name="id2618802"></a>
+		<a class="indexterm" name="id2618809"></a>
 		Samba-3 includes a number of helper tools, plug-in modules, utilities, and test and validation facilities.
 		Samba-3 includes glue modules that help provide interoperability between MS Windows clients and UNIX/Linux
 		servers and clients. It includes Winbind agents that make it possible to authenticate UNIX/Linux access attempts
 		as well as logins to an SMB/CIFS authentication server backend. Samba-3 includes name service switch (NSS) modules
 		to permit identity resolution via SMB/CIFS servers (Windows NT4/200x, Samba, and a host of other commercial
 		server products).
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2618701"></a><a name="id2618703"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2618829"></a><a name="id2618831"></a></td><td align="left" valign="top"><p>
 		Does use of Samba (<code class="literal">ntlm_auth</code>) improve the performance of Squid?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Not really. Samba's <code class="literal">ntlm_auth</code> module handles only authentication. It requires that
diff --git a/docs/htmldocs/Samba3-ByExample/ExNetworks.html b/docs/htmldocs/Samba3-ByExample/ExNetworks.html
index c46ccae905..12c7deaf95 100644
--- a/docs/htmldocs/Samba3-ByExample/ExNetworks.html
+++ b/docs/htmldocs/Samba3-ByExample/ExNetworks.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�Example Network Configurations</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="preface.html" title="Preface"><link rel="next" href="simple.html" title="Chapter�1.�No-Frills Samba Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�Example Network Configurations</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="preface.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="simple.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="ExNetworks"></a>Part�I.�Example Network Configurations</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2550769"></a>Example Network Configurations</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�Example Network Configurations</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="preface.html" title="Preface"><link rel="next" href="simple.html" title="Chapter�1.�No-Frills Samba Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�Example Network Configurations</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="preface.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="simple.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="ExNetworks"></a>Part�I.�Example Network Configurations</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2550763"></a>Example Network Configurations</h1></div></div></div><p>
 This section of <span class="emphasis"><em>Samba-3 by Example</em></span> provides example network
 configurations that can be copied, or modified as needed, and deployed as-is.
 The contents have been marginally updated to reflect changes made in Samba=3.0.23.
@@ -20,4 +20,4 @@ option to purchase commercial, professional, Samba support. Information regardin
 commercial support options may be obtained from the commercial
 <a class="ulink" href="http://www.samba.org/samba/support/" target="_top">support</a> pages from 
 the Samba web site.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="simple.html">1. No-Frills Samba Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="simple.html#id2550843">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550883">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550925">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551634">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554969">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="small.html">2. Small Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="small.html#id2555439">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555462">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555522">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555570">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555768">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555790">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557337">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557985">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558010">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558084">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="secure.html">3. Secure Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="secure.html#id2558563">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558614">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558848">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558863">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559289">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559329">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560183">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564645">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564707">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="Big500users.html">4. The 500-User Office</a></span></dt><dd><dl><dt><span class="sect1"><a href="Big500users.html#id2565229">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565274">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565373">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565409">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565612">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565635">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566362">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566927">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570125">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570184">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="happy.html">5. Making Happy Users</a></span></dt><dd><dl><dt><span class="sect1"><a href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571164">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571262">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571399">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573730">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573745">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573925">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580771">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580791">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580886">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581130">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581241">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581375">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582445">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583127">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583163">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583197">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583303">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="net2000users.html">6. A Distributed 2000-User Network</a></span></dt><dd><dl><dt><span class="sect1"><a href="net2000users.html#id2583726">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2583756">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2583824">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2584098">Technical Issues</a></span></dt><dt><span class="sect2"><a href="net2000users.html#id2585046">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2585064">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2588223">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2588370">Questions and Answers</a></span></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="preface.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="simple.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Preface�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�No-Frills Samba Servers</td></tr></table></div></body></html>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="simple.html">1. No-Frills Samba Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="simple.html#id2550837">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550877">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550918">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551628">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554965">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="small.html">2. Small Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="small.html#id2555435">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555458">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555518">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555566">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555765">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555786">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557330">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557978">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558003">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558077">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="secure.html">3. Secure Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="secure.html#id2558556">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558607">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558840">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559282">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559322">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560176">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564636">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564698">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="Big500users.html">4. The 500-User Office</a></span></dt><dd><dl><dt><span class="sect1"><a href="Big500users.html#id2565220">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565265">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565371">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565407">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565610">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565632">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566360">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566924">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570124">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570183">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="happy.html">5. Making Happy Users</a></span></dt><dd><dl><dt><span class="sect1"><a href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571163">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571398">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573734">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573749">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573929">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580776">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580797">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580892">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581136">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581247">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581381">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582451">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583133">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583169">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583203">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583318">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="2000users.html">6. A Distributed 2000-User Network</a></span></dt><dd><dl><dt><span class="sect1"><a href="2000users.html#id2583740">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2583770">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2583839">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2584112">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2585057">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2585074">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2588234">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2588381">Questions and Answers</a></span></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="preface.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="simple.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Preface�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�No-Frills Samba Servers</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/HA.html b/docs/htmldocs/Samba3-ByExample/HA.html
index 33a2338c40..f839c120e9 100644
--- a/docs/htmldocs/Samba3-ByExample/HA.html
+++ b/docs/htmldocs/Samba3-ByExample/HA.html
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�13.�Performance, Reliability, and Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="DomApps.html" title="Chapter�12.�Integrating Additional Services"><link rel="next" href="ch14.html" title="Chapter�14.�Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�13.�Performance, Reliability, and Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DomApps.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="HA"></a>Chapter�13.�Performance, Reliability, and Availability</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="HA.html#id2618805">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2618892">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619366">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619393">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2619868">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620205">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620281">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620352">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620452">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620600">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620704">Key Points Learned</a></span></dt></dl></div><p>
-	<a class="indexterm" name="id2618767"></a>
-	<a class="indexterm" name="id2618774"></a>
-	<a class="indexterm" name="id2618780"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�13.�Performance, Reliability, and Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="DomApps.html" title="Chapter�12.�Integrating Additional Services"><link rel="next" href="ch14.html" title="Chapter�14.�Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�13.�Performance, Reliability, and Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DomApps.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="HA"></a>Chapter�13.�Performance, Reliability, and Availability</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="HA.html#id2618932">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619030">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619530">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620006">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620334">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620409">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620480">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620581">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620728">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620832">Key Points Learned</a></span></dt></dl></div><p>
+	<a class="indexterm" name="id2618895"></a>
+	<a class="indexterm" name="id2618901"></a>
+	<a class="indexterm" name="id2618908"></a>
 	Well, you have reached one of the last chapters of this book. It is customary to attempt
 	to wrap up the theme and contents of a book in what is generally regarded as the
 	chapter that should draw conclusions. This book is a suspense thriller, and since
@@ -10,8 +10,8 @@
 	regarding some of the things everyone can do to deliver a reliable Samba-3 network.
 	</p><div class="blockquote"><table border="0" width="100%" cellspacing="0" cellpadding="0" class="blockquote" summary="Block quote"><tr><td width="10%" valign="top">�</td><td width="80%" valign="top"><p>
 	In a world so full of noise, how can the sparrow be heard?
-	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Anonymous</span></td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618805"></a>Introduction</h2></div></div></div><p>
-	<a class="indexterm" name="id2618813"></a>
+	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Anonymous</span></td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618932"></a>Introduction</h2></div></div></div><p>
+	<a class="indexterm" name="id2618940"></a>
 	The sparrow is a small bird whose sounds are drowned out by the noise of the busy
 	world it lives in. Likewise, the simple steps that can be taken to improve the
 	reliability and availability of a Samba network are often drowned out by the volume
@@ -20,22 +20,22 @@
 	itself to discussion of clustering because each clustering methodology uses its own
 	custom tools and methods. Only passing comments are offered concerning these methods.
 	</p><p>
-	<a class="indexterm" name="id2618833"></a>
-	<a class="indexterm" name="id2618840"></a>
-	<a class="indexterm" name="id2618847"></a>
+	<a class="indexterm" name="id2618970"></a>
+	<a class="indexterm" name="id2618977"></a>
+	<a class="indexterm" name="id2618984"></a>
 <a class="ulink" href="http://www.google.com/search?hl=en&amp;lr=&amp;ie=ISO-8859-1&amp;q=samba+cluster&amp;btnG=Google+Search" target="_top">A search</a> 
 	for &#8220;<span class="quote">samba cluster</span>&#8221; produced 71,600 hits. And a search for &#8220;<span class="quote">highly available samba</span>&#8221;
 	and &#8220;<span class="quote">highly available windows</span>&#8221; produced an amazing number of references.
 	It is clear from the resources on the Internet that Windows file and print services 
 	availability, reliability, and scalability are of vital interest to corporate network users.
 	</p><p>
-	<a class="indexterm" name="id2618880"></a>
+	<a class="indexterm" name="id2619018"></a>
 	So without further background, you can review a checklist of simple steps that
 	can be taken to ensure acceptable network performance while keeping costs of ownership
 	well under control.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618892"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2618900"></a>
-	<a class="indexterm" name="id2618907"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619030"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2619038"></a>
+	<a class="indexterm" name="id2619045"></a>
 	If it is your purpose to get the best mileage out of your Samba servers, there is one rule that
 	must be obeyed. If you want the best, keep your implementation as simple as possible. You may
 	well be forced to introduce some complexities, but you should do so only as a last resort.
@@ -44,8 +44,8 @@
 	make life easier for your successor. Simple implementations can be more readily audited than can
 	complex ones. 
 	</p><p>
-	<a class="indexterm" name="id2618929"></a>
-	<a class="indexterm" name="id2618936"></a>
+	<a class="indexterm" name="id2619067"></a>
+	<a class="indexterm" name="id2619074"></a>
 	Problems reported by users fall into three categories: configurations that do not work, those 
 	that have broken behavior, and poor performance. The term <span class="emphasis"><em>broken behavior</em></span>
 	means that the function of a particular Samba component appears to work sometimes, but not at
@@ -54,12 +54,12 @@
 	list of Windows machines in MS Explorer changes, sometimes listing machines that are running
 	and at other times not listing them even though the machines are in use on the network.
 	</p><p>
-	<a class="indexterm" name="id2618964"></a>
-	<a class="indexterm" name="id2618970"></a>
-	<a class="indexterm" name="id2618977"></a>
-	<a class="indexterm" name="id2618984"></a>
-	<a class="indexterm" name="id2618991"></a>
-	<a class="indexterm" name="id2618998"></a>
+	<a class="indexterm" name="id2619101"></a>
+	<a class="indexterm" name="id2619108"></a>
+	<a class="indexterm" name="id2619115"></a>
+	<a class="indexterm" name="id2619121"></a>
+	<a class="indexterm" name="id2619128"></a>
+	<a class="indexterm" name="id2619135"></a>
 	A significant number of reports concern problems with the <code class="literal">smbfs</code> file system
 	driver that is part of the Linux kernel, not part of Samba. Users continue to interpret that
 	<code class="literal">smbfs</code> is part of Samba, simply because Samba includes the front-end tools
@@ -70,32 +70,32 @@
 	common infrastructure with some Samba components, but they are not maintained as part of
 	Samba and are really foreign to it.
 	</p><p>
-	<a class="indexterm" name="id2619058"></a>
+	<a class="indexterm" name="id2619196"></a>
 	The new project, <code class="literal">cifsfs</code>, is destined to replace <code class="literal">smbfs</code>.
 	It, too, is not part of Samba, even though one of the Samba Team members is a prime mover in
 	this project.
 	</p><p>
 	Table 13.1 lists typical causes of:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Not Working (NW)</p></li><li><p>Broken Behavior (BB)</p></li><li><p>Poor Performance (PP)</p></li></ul></div><div class="table"><a name="ProbList"></a><p class="title"><b>Table�13.1.�Effect of Common Problems</b></p><div class="table-contents"><table summary="Effect of Common Problems" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>Problem</p></th><th align="center"><p>NW</p></th><th align="center"><p>BB</p></th><th align="center"><p>PP</p></th></tr></thead><tbody><tr><td align="left"><p>File locking</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Hardware problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Incorrect authentication</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Incorrect configuration</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>LDAP problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Name resolution</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Printing problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Slow file transfer</p></td><td align="center"><p>-</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Winbind problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr></tbody></table></div></div><br class="table-break"><p>
-	<a class="indexterm" name="id2619352"></a>
+	<a class="indexterm" name="id2619490"></a>
 	It is obvious to all that the first requirement (as a matter of network hygiene) is to eliminate
 	problems that affect basic network operation. This book has provided sufficient working examples
 	to help you to avoid all these problems.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619366"></a>Guidelines for Reliable Samba Operation</h2></div></div></div><p>
-	<a class="indexterm" name="id2619374"></a>
-	<a class="indexterm" name="id2619381"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619503"></a>Guidelines for Reliable Samba Operation</h2></div></div></div><p>
+	<a class="indexterm" name="id2619511"></a>
+	<a class="indexterm" name="id2619518"></a>
 	Your objective is to provide a network that works correctly, can grow at all times, is resilient
 	at times of extreme demand, and can scale to meet future needs. The following subject areas provide
 	pointers that can help you today.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619393"></a>Name Resolution</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619530"></a>Name Resolution</h3></div></div></div><p>
 	There are three basic current problem areas: bad hostnames, routed networks, and network collisions.
 	These are covered in the following discussion.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619404"></a>Bad Hostnames</h4></div></div></div><p>
-		<a class="indexterm" name="id2619412"></a>
-		<a class="indexterm" name="id2619421"></a>
-		<a class="indexterm" name="id2619428"></a>
-		<a class="indexterm" name="id2619435"></a>
-		<a class="indexterm" name="id2619442"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619542"></a>Bad Hostnames</h4></div></div></div><p>
+		<a class="indexterm" name="id2619550"></a>
+		<a class="indexterm" name="id2619559"></a>
+		<a class="indexterm" name="id2619566"></a>
+		<a class="indexterm" name="id2619573"></a>
+		<a class="indexterm" name="id2619579"></a>
 		When configured as a DHCP client, a number of Linux distributions set the system hostname
 		to <code class="constant">localhost</code>. If the parameter <em class="parameter"><code>netbios name</code></em> is not
 		specified to something other than <code class="constant">localhost</code>, the Samba server appears
@@ -107,13 +107,13 @@
 		the local Windows machine itself. Hostnames must be valid for Windows networking to function
 		correctly.
 		</p><p>
-		<a class="indexterm" name="id2619497"></a>
+		<a class="indexterm" name="id2619634"></a>
 		A few sites have tried to name Windows clients and Samba servers with a name that begins
 		with the digits 1-9. This does not work either because it may result in the client or
 		server attempting to use that name as an IP address.
 		</p><p>
-		<a class="indexterm" name="id2619511"></a>
-		<a class="indexterm" name="id2619520"></a>
+		<a class="indexterm" name="id2619648"></a>
+		<a class="indexterm" name="id2619657"></a>
 		A Samba server called <code class="constant">FRED</code> in a NetBIOS domain called <code class="constant">COLLISION</code>
 		in a network environment that is part of the fully-qualified Internet domain namespace known
 		as <code class="constant">parrots.com</code>, results in DNS name lookups for <code class="constant">fred.parrots.com</code>
@@ -122,49 +122,49 @@
 		attempts to resolve <code class="constant">fred.parrots.com.parrots.com</code>, which most likely
 		fails given that you probably do not have this in your DNS namespace.
 		</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-		<a class="indexterm" name="id2619564"></a>
-		<a class="indexterm" name="id2619573"></a>
-		<a class="indexterm" name="id2619580"></a>
+		<a class="indexterm" name="id2619702"></a>
+		<a class="indexterm" name="id2619711"></a>
+		<a class="indexterm" name="id2619717"></a>
 		An Active Directory realm called <code class="constant">collision.parrots.com</code> is perfectly okay,
 		although it too must be capable of being resolved via DNS, something that functions correctly
 		if Windows 200x ADS has been properly installed and configured.
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619596"></a>Routed Networks</h4></div></div></div><p>
-		<a class="indexterm" name="id2619604"></a>
-		<a class="indexterm" name="id2619611"></a>
-		<a class="indexterm" name="id2619620"></a>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619734"></a>Routed Networks</h4></div></div></div><p>
+		<a class="indexterm" name="id2619742"></a>
+		<a class="indexterm" name="id2619748"></a>
+		<a class="indexterm" name="id2619758"></a>
 		NetBIOS networks (Windows networking with NetBIOS over TCP/IP enabled) makes extensive use
 		of UDP-based broadcast traffic, as you saw during the exercises in <a class="link" href="primer.html" title="Chapter�16.�Networking Primer">&#8220;Networking Primer&#8221;</a>.
 		</p><p>
-		<a class="indexterm" name="id2619640"></a>
-		<a class="indexterm" name="id2619647"></a>
-		<a class="indexterm" name="id2619653"></a>
+		<a class="indexterm" name="id2619777"></a>
+		<a class="indexterm" name="id2619784"></a>
+		<a class="indexterm" name="id2619791"></a>
 		UDP broadcast traffic is not forwarded by routers. This means that NetBIOS broadcast-based
 		networking cannot function across routed networks (i.e., multi-subnet networks) unless
 		special provisions are made:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2619670"></a>
-			<a class="indexterm" name="id2619677"></a>
-			<a class="indexterm" name="id2619684"></a>
+			<a class="indexterm" name="id2619808"></a>
+			<a class="indexterm" name="id2619815"></a>
+			<a class="indexterm" name="id2619822"></a>
 			Either install on every Windows client an LMHOSTS file (located in the directory
 			<code class="filename">C:\windows\system32\drivers\etc</code>). It is also necessary to
 			add to the Samba server <code class="filename">smb.conf</code> file the parameters <em class="parameter"><code>remote announce</code></em>
 			and <em class="parameter"><code>remote browse sync</code></em>. For more information, refer to the online
 			manual page for the <code class="filename">smb.conf</code> file.
 			</p></li><li><p>
-			<a class="indexterm" name="id2619730"></a>
+			<a class="indexterm" name="id2619867"></a>
 			Or configure Samba as a WINS server, and configure all network clients to use that
 			WINS server in their TCP/IP configuration.
 			</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-		<a class="indexterm" name="id2619747"></a>
-		<a class="indexterm" name="id2619756"></a>
+		<a class="indexterm" name="id2619884"></a>
+		<a class="indexterm" name="id2619893"></a>
 		The use of DNS is not an acceptable substitute for WINS. DNS does not store specific
 		information regarding NetBIOS networking particulars that get stored in the WINS
 		name resolution database and that Windows clients require and depend on.
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619769"></a>Network Collisions</h4></div></div></div><p>
-		<a class="indexterm" name="id2619777"></a>
-		<a class="indexterm" name="id2619786"></a>
-		<a class="indexterm" name="id2619795"></a>
-		<a class="indexterm" name="id2619802"></a>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619906"></a>Network Collisions</h4></div></div></div><p>
+		<a class="indexterm" name="id2619914"></a>
+		<a class="indexterm" name="id2619923"></a>
+		<a class="indexterm" name="id2619933"></a>
+		<a class="indexterm" name="id2619940"></a>
 		Excessive network activity causes NetBIOS network timeouts. Timeouts may result in
 		blue screen of death (BSOD) experiences. High collision rates may be caused by excessive
 		UDP broadcast activity, by defective networking hardware, or through excessive network
@@ -173,9 +173,9 @@
 		The use of WINS is highly recommended to reduce network broadcast traffic, as outlined
 		in <a class="link" href="primer.html" title="Chapter�16.�Networking Primer">&#8220;Networking Primer&#8221;</a>.
 		</p><p>
-		<a class="indexterm" name="id2619831"></a>
-		<a class="indexterm" name="id2619838"></a>
-		<a class="indexterm" name="id2619845"></a>
+		<a class="indexterm" name="id2619968"></a>
+		<a class="indexterm" name="id2619975"></a>
+		<a class="indexterm" name="id2619982"></a>
 		Under no circumstances should the facility be supported by many routers, known as <code class="constant">NetBIOS
 		forwarding</code>, unless you know exactly what you are doing. Inappropriate use of this
 		facility can result in UDP broadcast storms. In one case in 1999, a university network became
@@ -183,13 +183,13 @@
 		testing of a Samba server. The maximum throughput on a 100-Base-T (100 MB/sec) network was
 		less than 15 KB/sec. After the NetBIOS forwarding was turned off, file transfer performance
 		immediately returned to 11 MB/sec.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619868"></a>Samba Configuration</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620006"></a>Samba Configuration</h3></div></div></div><p>
 	As a general rule, the contents of the <code class="filename">smb.conf</code> file should be kept as simple as possible.
 	No parameter should be specified unless you know it is essential to operation.
 	</p><p>
-	<a class="indexterm" name="id2619888"></a>
-	<a class="indexterm" name="id2619895"></a>
-	<a class="indexterm" name="id2619902"></a>
+	<a class="indexterm" name="id2620026"></a>
+	<a class="indexterm" name="id2620033"></a>
+	<a class="indexterm" name="id2620040"></a>
 	Many UNIX administrators like to fully document the settings in the <code class="filename">smb.conf</code> file. This is a
 	bad idea because it adds content to the file. The <code class="filename">smb.conf</code> file is re-read by every <code class="literal">smbd</code>
 	process every time the file timestamp changes (or, on systems where this does not work, every 20 seconds or so).
@@ -197,7 +197,7 @@
 	As the size of the <code class="filename">smb.conf</code> file grows, the risk of introducing parsing errors also increases.
 	It is recommended to keep a fully documented <code class="filename">smb.conf</code> file on hand, and then to operate Samba only
 	with an optimized file.
-	</p><p><a class="indexterm" name="id2619952"></a>
+	</p><p><a class="indexterm" name="id2620090"></a>
 	The preferred way to maintain a documented file is to call it something like <code class="filename">smb.conf.master</code>.
 	You can generate the optimized file by executing:
 </p><pre class="screen">
@@ -223,7 +223,7 @@ Loaded services file OK.
 Server role: ROLE_DOMAIN_PDC
 Press enter to see a dump of your service definitions
 </pre><p>
-	<a class="indexterm" name="id2620011"></a>
+	<a class="indexterm" name="id2620149"></a>
 	You now, of course, press the enter key to complete the command, or else abort it by pressing Ctrl-C.
 	The important thing to note is the noted Server role, as well as warning messages. Noted configuration
 	conflicts must be remedied before proceeding. For example, the following error message represents a
@@ -233,28 +233,28 @@ ERROR: both 'wins support = true' and 'wins server = &lt;server list&gt;'
 cannot be set in the smb.conf file. nmbd will abort with this setting.
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2620039"></a>
-	<a class="indexterm" name="id2620046"></a>
-	<a class="indexterm" name="id2620053"></a>
+	<a class="indexterm" name="id2620177"></a>
+	<a class="indexterm" name="id2620184"></a>
+	<a class="indexterm" name="id2620191"></a>
 	There are two parameters that can cause severe network performance degradation: <em class="parameter"><code>socket options</code></em>
 	and <em class="parameter"><code>socket address</code></em>. The <em class="parameter"><code>socket options</code></em> parameter was often necessary
 	when Samba was used with the Linux 2.2.x kernels. Later kernels are largely self-tuning and seldom benefit from
 	this parameter being set. Do not use either parameter unless it has been proven necessary to use them.
 	</p><p>
-	<a class="indexterm" name="id2620087"></a>
-	<a class="indexterm" name="id2620094"></a>
-	<a class="indexterm" name="id2620101"></a>
-	<a class="indexterm" name="id2620108"></a>
+	<a class="indexterm" name="id2620225"></a>
+	<a class="indexterm" name="id2620231"></a>
+	<a class="indexterm" name="id2620238"></a>
+	<a class="indexterm" name="id2620245"></a>
 	Another <code class="filename">smb.conf</code> parameter that may cause severe network performance degradation is the 
 	<em class="parameter"><code>strict sync</code></em> parameter. Do not use this at all. There is no good reason
 	to use this with any modern Windows client. The <em class="parameter"><code>strict sync</code></em> is often
 	used with the <em class="parameter"><code>sync always</code></em> parameter. This, too, can severely	
 	degrade network performance, so do not set it; if you must, do so with caution.
 	</p><p>
-	<a class="indexterm" name="id2620149"></a>
-	<a class="indexterm" name="id2620156"></a>
-	<a class="indexterm" name="id2620163"></a>
-	<a class="indexterm" name="id2620170"></a>
+	<a class="indexterm" name="id2620287"></a>
+	<a class="indexterm" name="id2620294"></a>
+	<a class="indexterm" name="id2620301"></a>
+	<a class="indexterm" name="id2620308"></a>
 	Finally, many network administrators deliberately disable opportunistic locking support. While this
 	does not degrade Samba performance, it significantly degrades Windows client performance because
 	this disables local file caching on Windows clients and forces every file read and written to
@@ -262,12 +262,12 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	support, do so only on the share on which it is required. That way, all other shares can provide
 	oplock support for operations that are tolerant of it. See <a class="link" href="appendix.html#ch12dblck" title="Shared Data Integrity">&#8220;Shared Data Integrity&#8221;</a> for more
 	information.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620205"></a>Use and Location of BDCs</h3></div></div></div><p>
-	<a class="indexterm" name="id2620213"></a>
-	<a class="indexterm" name="id2620220"></a>
-	<a class="indexterm" name="id2620226"></a>
-	<a class="indexterm" name="id2620233"></a>
-	<a class="indexterm" name="id2620240"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620334"></a>Use and Location of BDCs</h3></div></div></div><p>
+	<a class="indexterm" name="id2620342"></a>
+	<a class="indexterm" name="id2620348"></a>
+	<a class="indexterm" name="id2620354"></a>
+	<a class="indexterm" name="id2620361"></a>
+	<a class="indexterm" name="id2620368"></a>
 	On a network segment where there is a PDC and a BDC, the BDC carries the bulk of the network logon
 	processing. If the BDC is a heavily loaded server, the PDC carries a greater proportion of
 	authentication and logon processing. When a sole BDC on a routed network segment gets heavily
@@ -275,13 +275,13 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	to a BDC on a distant network segment. This significantly hinders WAN operations
 	and is undesirable.
 	</p><p>
-	<a class="indexterm" name="id2620258"></a>
-	<a class="indexterm" name="id2620265"></a>
+	<a class="indexterm" name="id2620387"></a>
+	<a class="indexterm" name="id2620394"></a>
 	As a general guide, instead of adding domain member servers to a network, you would be better advised
 	to add BDCs until there are fewer than 30 Windows clients per BDC. Beyond that ratio, you should add
 	domain member servers. This practice ensures that there are always sufficient domain controllers
 	to handle logon requests and authentication traffic.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620281"></a>Use One Consistent Version of MS Windows Client</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620409"></a>Use One Consistent Version of MS Windows Client</h3></div></div></div><p>
 	Every network client has its own peculiarities. From a management perspective, it is easier to deal
 	with one version of MS Windows that is maintained to a consistent update level than it is to deal
 	with a mixture of clients.
@@ -289,61 +289,61 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	On a number of occasions, particular Microsoft service pack updates of a Windows server or client
 	have necessitated special handling from the Samba server end. If you want to remain sane, keep you
 	client workstation configurations consistent.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620303"></a>For Scalability, Use SAN-Based Storage on Samba Servers</h3></div></div></div><p>
-	<a class="indexterm" name="id2620311"></a>
-	<a class="indexterm" name="id2620318"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620431"></a>For Scalability, Use SAN-Based Storage on Samba Servers</h3></div></div></div><p>
+	<a class="indexterm" name="id2620439"></a>
+	<a class="indexterm" name="id2620446"></a>
 	Many SAN-based storage systems permit more than one server to share a common data store.
 	Use of a shared SAN data store means that you do not need to use time- and resource-hungry data 
 	synchronization techniques.
 	</p><p>
-	<a class="indexterm" name="id2620332"></a>
-	<a class="indexterm" name="id2620339"></a>
+	<a class="indexterm" name="id2620460"></a>
+	<a class="indexterm" name="id2620467"></a>
 	The use of a collection of relatively low-cost front-end Samba servers that are coupled to
 	a shared backend SAN data store permits load distribution while containing costs below that
 	of installing and managing a complex clustering facility.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620352"></a>Distribute Network Load with MSDFS</h3></div></div></div><p>
-	<a class="indexterm" name="id2620360"></a>
-	<a class="indexterm" name="id2620367"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620480"></a>Distribute Network Load with MSDFS</h3></div></div></div><p>
+	<a class="indexterm" name="id2620488"></a>
+	<a class="indexterm" name="id2620495"></a>
 	Microsoft DFS (distributed file system) technology has been implemented in Samba. MSDFS permits
 	data to be accessed from a single share and yet to actually be distributed across multiple actual
 	servers. Refer to <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 19, for information regarding
 	implementation of an MSDFS installation.
 	</p><p>
-	<a class="indexterm" name="id2620386"></a>
-	<a class="indexterm" name="id2620395"></a>
+	<a class="indexterm" name="id2620514"></a>
+	<a class="indexterm" name="id2620523"></a>
 	The combination of multiple backend servers together with a front-end server and use of MSDFS
 	can achieve almost the same as you would obtain with a clustered Samba server.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620407"></a>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</h3></div></div></div><p>
-	<a class="indexterm" name="id2620415"></a>
-	<a class="indexterm" name="id2620422"></a>
-	<a class="indexterm" name="id2620429"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620535"></a>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</h3></div></div></div><p>
+	<a class="indexterm" name="id2620544"></a>
+	<a class="indexterm" name="id2620550"></a>
+	<a class="indexterm" name="id2620557"></a>
 	Consider using <code class="literal">rsync</code> to replicate data across the WAN during times
 	of low utilization. Users can then access the replicated data store rather than needing to do so
 	across the WAN. This works best for read-only data, but with careful planning can be
 	implemented so that modified files get replicated back to the point of origin. Be careful with your
 	implementation if you choose to permit modification and return replication of the modified file;
 	otherwise, you may inadvertently overwrite important data.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620452"></a>Hardware Problems</h3></div></div></div><p>
-	<a class="indexterm" name="id2620460"></a>
-	<a class="indexterm" name="id2620467"></a>
-	<a class="indexterm" name="id2620474"></a>
-	<a class="indexterm" name="id2620481"></a>
-	<a class="indexterm" name="id2620490"></a>
-	<a class="indexterm" name="id2620499"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620581"></a>Hardware Problems</h3></div></div></div><p>
+	<a class="indexterm" name="id2620588"></a>
+	<a class="indexterm" name="id2620595"></a>
+	<a class="indexterm" name="id2620602"></a>
+	<a class="indexterm" name="id2620609"></a>
+	<a class="indexterm" name="id2620618"></a>
+	<a class="indexterm" name="id2620628"></a>
 	Networking hardware prices have fallen sharply over the past 5 years. A surprising number
 	of Samba networking problems over this time have been traced to defective network interface
 	cards (NICs) or defective HUBs, switches, and cables.
 	</p><p>
-	<a class="indexterm" name="id2620516"></a>
+	<a class="indexterm" name="id2620644"></a>
 	Not surprising is the fact that network administrators do not like to be shown to have made
 	a bad decision. Money saved in buying low-cost hardware may result in high costs incurred
 	in corrective action.
 	</p><p>
-	<a class="indexterm" name="id2620530"></a>
-	<a class="indexterm" name="id2620537"></a>
-	<a class="indexterm" name="id2620544"></a>
-	<a class="indexterm" name="id2620550"></a>
-	<a class="indexterm" name="id2620557"></a>
+	<a class="indexterm" name="id2620658"></a>
+	<a class="indexterm" name="id2620665"></a>
+	<a class="indexterm" name="id2620672"></a>
+	<a class="indexterm" name="id2620679"></a>
+	<a class="indexterm" name="id2620686"></a>
 	Defective NICs, HUBs, and switches may appear as intermittent network access problems, intermittent
 	or persistent data corruption, slow network throughput, low performance, or even as BSOD
 	problems with MS Windows clients. In one case, a company updated several workstations with newer, faster
@@ -352,14 +352,14 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	</p><p>
 	Defective hardware problems may take patience and persistence before the real cause can be discovered.
 	</p><p>
-	<a class="indexterm" name="id2620581"></a>
+	<a class="indexterm" name="id2620709"></a>
 	Networking hardware defects can significantly impact perceived Samba performance, but defective
 	RAID controllers as well as SCSI and IDE hard disk controllers have also been known to impair Samba server
 	operations. One business came to this realization only after replacing a Samba installation with MS 
 	Windows Server 2000 running on the same hardware. The root of the problem completely eluded the network
 	administrator until the entire server was replaced. While you may well think that this would never
 	happen to you, experience shows that given the right (unfortunate) circumstances, this can happen to anyone.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620600"></a>Large Directories</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620728"></a>Large Directories</h3></div></div></div><p>
 	There exist applications that create or manage directories containing many thousands of files. Such
 	applications typically generate many small files (less than 100 KB). At the best of times, under UNIX,
 	listing of the files in a directory that contains many files is slow. By default, Windows NT, 200x, 
@@ -399,7 +399,7 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	All files and directories under the <em class="parameter"><code>path</code></em> directory must be in the same case
 	as specified in the <code class="filename">smb.conf</code> stanza. This means that smbd will not be able to find lower case 
 	filenames with these settings.  Note, this is done on a per-share basis.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620704"></a>Key Points Learned</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620832"></a>Key Points Learned</h2></div></div></div><p>
 	This chapter has touched in broad sweeps on a number of simple steps that can be taken
 	to ensure that your Samba network is resilient, scalable, and reliable, and that it
 	performs well.
@@ -408,7 +408,7 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.
 	In the long term, that may not be you. Spare a thought for your successor and give him or
 	her an even break.
 	</p><p>
-	<a class="indexterm" name="id2620725"></a>
+	<a class="indexterm" name="id2620853"></a>
 	Last, but not least, you should not only keep the network design simple, but also be sure it is
 	well documented. This book may serve as your pattern for documenting every
 	aspect of your design, its implementation, and particularly the objects and assumptions
diff --git a/docs/htmldocs/Samba3-ByExample/RefSection.html b/docs/htmldocs/Samba3-ByExample/RefSection.html
index e4fc2136dc..2c5b9ece45 100644
--- a/docs/htmldocs/Samba3-ByExample/RefSection.html
+++ b/docs/htmldocs/Samba3-ByExample/RefSection.html
@@ -1,52 +1,52 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Reference Section</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="nw4migration.html" title="Chapter�10.�Migrating NetWare Server to Samba-3"><link rel="next" href="kerberos.html" title="Chapter�11.�Active Directory, Kerberos, and Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Reference Section</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="nw4migration.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="kerberos.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="RefSection"></a>Part�III.�Reference Section</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2610399"></a>Reference Section</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Reference Section</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="nw4migration.html" title="Chapter�10.�Migrating NetWare Server to Samba-3"><link rel="next" href="kerberos.html" title="Chapter�11.�Active Directory, Kerberos, and Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Reference Section</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="nw4migration.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="kerberos.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="RefSection"></a>Part�III.�Reference Section</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2610490"></a>Reference Section</h1></div></div></div><p>
 This section <span class="emphasis"><em>Samba-3 by Example</em></span> provides important reference material
 that may help you to solve network performance issues, to answer some of the critiques
 published regarding Samba, or just to gain a more broad understanding of how Samba can
 play in a Windows networking world.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="kerberos.html">11. Active Directory, Kerberos, and Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="kerberos.html#id2610496">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611138">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611154">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611545">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613169">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613518">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615257">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615391">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="DomApps.html">12. Integrating Additional Services</a></span></dt><dd><dl><dt><span class="sect1"><a href="DomApps.html#id2616020">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616051">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616160">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616193">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616349">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616373">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618225">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618286">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="HA.html">13. Performance, Reliability, and Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="HA.html#id2618805">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2618892">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619366">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619393">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2619868">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620205">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620281">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620352">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620452">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620600">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620704">Key Points Learned</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch14.html">14. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch14.html#id2620874">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621092">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="appendix.html">15. A Collection of Useful Tidbits</a></span></dt><dd><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621811">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622232">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622592">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622604">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622652">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622792">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622851">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623411">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624406">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2624881">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625028">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625113">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="primer.html">16. Networking Primer</a></span></dt><dd><dl><dt><span class="sect1"><a href="primer.html#id2625280">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625441">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625502">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625618">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625744">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627962">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628077">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="kerberos.html">11. Active Directory, Kerberos, and Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="kerberos.html#id2610586">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611237">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611253">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611650">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613280">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613629">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615382">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615516">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="DomApps.html">12. Integrating Additional Services</a></span></dt><dd><dl><dt><span class="sect1"><a href="DomApps.html#id2616145">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616176">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616287">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616320">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616476">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616493">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618345">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618406">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="HA.html">13. Performance, Reliability, and Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="HA.html#id2618932">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619030">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619530">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620006">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620334">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620409">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620480">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620581">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620728">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620832">Key Points Learned</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch14.html">14. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch14.html#id2621002">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621220">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="appendix.html">15. A Collection of Useful Tidbits</a></span></dt><dd><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621928">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622349">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622689">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622700">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622749">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622889">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622948">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623534">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624531">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2625006">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625153">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625237">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="primer.html">16. Networking Primer</a></span></dt><dd><dl><dt><span class="sect1"><a href="primer.html#id2625404">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625565">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625625">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625742">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625868">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2628086">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628200">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
     GNU General Public License version 3
-  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2628743">A. 
+  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2628866">A. 
     Preamble
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628888">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629012">A. 
     TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628892">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629015">A. 
     0. Definitions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628984">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629108">A. 
     1. Source Code.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629082">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629206">A. 
     2. Basic Permissions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629122">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629154">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629281">A. 
     4. Conveying Verbatim Copies.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629181">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629308">A. 
     5. Conveying Modified Source Versions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629277">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629404">A. 
     6. Conveying Non-Source Forms.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629466">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629594">A. 
      7. Additional Terms.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629602">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629729">A. 
      8. Termination.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629646">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629773">A. 
      9. Acceptance Not Required for Having Copies.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629675">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629792">A. 
      10. Automatic Licensing of Downstream Recipients.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629727">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629844">A. 
     11. Patents.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629872">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 
     12. No Surrender of Others&#8217; Freedom.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629894">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
     13. Use with the ???TITLE??? Affero General Public License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629923">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630041">A. 
     14. Revised Versions of this License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629986">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630103">A. 
     15. Disclaimer of Warranty.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630129">A. 
     16. Limitation of Liability.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630032">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630150">A. 
     17. Interpretation of Sections 15 and 16.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630049">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630166">A. 
     END OF TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630052">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630170">A. 
     How to Apply These Terms to Your New Programs
   </a></span></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="nw4migration.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="kerberos.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�10.�Migrating NetWare Server to Samba-3�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�11.�Active Directory, Kerberos, and Security</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/apa.html b/docs/htmldocs/Samba3-ByExample/apa.html
index 6ef840cf3c..caf1a1cc22 100644
--- a/docs/htmldocs/Samba3-ByExample/apa.html
+++ b/docs/htmldocs/Samba3-ByExample/apa.html
@@ -1,50 +1,50 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix�A.� GNU General Public License version 3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="primer.html" title="Chapter�16.�Networking Primer"><link rel="next" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix�A.�
     GNU General Public License version 3
-  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="primer.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2628713"></a>Appendix�A.�
+  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="primer.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2628837"></a>Appendix�A.�
     <acronym class="acronym">GNU</acronym> General Public License version 3
-  </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="bridgehead"><a href="apa.html#id2628743">A. 
+  </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="bridgehead"><a href="apa.html#id2628866">A. 
     Preamble
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628888">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629012">A. 
     TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628892">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629015">A. 
     0. Definitions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628984">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629108">A. 
     1. Source Code.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629082">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629206">A. 
     2. Basic Permissions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629122">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629154">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629281">A. 
     4. Conveying Verbatim Copies.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629181">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629308">A. 
     5. Conveying Modified Source Versions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629277">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629404">A. 
     6. Conveying Non-Source Forms.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629466">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629594">A. 
      7. Additional Terms.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629602">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629729">A. 
      8. Termination.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629646">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629773">A. 
      9. Acceptance Not Required for Having Copies.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629675">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629792">A. 
      10. Automatic Licensing of Downstream Recipients.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629727">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629844">A. 
     11. Patents.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629872">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 
     12. No Surrender of Others&#8217; Freedom.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629894">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
     13. Use with the ???TITLE??? Affero General Public License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629923">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630041">A. 
     14. Revised Versions of this License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629986">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630103">A. 
     15. Disclaimer of Warranty.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630129">A. 
     16. Limitation of Liability.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630032">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630150">A. 
     17. Interpretation of Sections 15 and 16.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630049">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630166">A. 
     END OF TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630052">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630170">A. 
     How to Apply These Terms to Your New Programs
   </a></span></dt></dl></div><p>
     Version 3, 29 June 2007
@@ -54,7 +54,7 @@
   </p><p>
     Everyone is permitted to copy and distribute verbatim copies of this license
     document, but changing it is not allowed.
-  </p><h2><a name="id2628743"></a>
+  </p><h2><a name="id2628866"></a>
     Preamble
   </h2><p>
     The <acronym class="acronym">GNU</acronym> General Public License is a free, copyleft
@@ -118,9 +118,9 @@
   </p><p>
     The precise terms and conditions for copying, distribution and modification
     follow.
-  </p><h2><a name="id2628888"></a>
+  </p><h2><a name="id2629012"></a>
     TERMS AND CONDITIONS
-  </h2><h2><a name="id2628892"></a>
+  </h2><h2><a name="id2629015"></a>
     0. Definitions.
   </h2><p>
     &#8220;This License&#8221; refers to version 3 of the <acronym class="acronym">GNU</acronym>
@@ -162,7 +162,7 @@
     License, and how to view a copy of this License.  If the interface presents
     a list of user commands or options, such as a menu, a prominent item in the
     list meets this criterion.
-  </p><h2><a name="id2628984"></a>
+  </p><h2><a name="id2629108"></a>
     1. Source Code.
   </h2><p>
     The &#8220;source code&#8221; for a work means the preferred form of the
@@ -202,7 +202,7 @@
     automatically from other parts of the Corresponding Source.
   </p><p>
     The Corresponding Source for a work in source code form is that same work.
-  </p><h2><a name="id2629082"></a>
+  </p><h2><a name="id2629206"></a>
     2. Basic Permissions.
   </h2><p>
     All rights granted under this License are granted for the term of copyright
@@ -227,7 +227,7 @@
     Conveying under any other circumstances is permitted solely under the
     conditions stated below.  Sublicensing is not allowed; section 10 makes it
     unnecessary.
-  </p><h2><a name="id2629122"></a>
+  </p><h2><a name="id2629246"></a>
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
   </h2><p>
     No covered work shall be deemed part of an effective technological measure
@@ -242,7 +242,7 @@
     the work as a means of enforcing, against the work&#8217;s users, your or
     third parties&#8217; legal rights to forbid circumvention of technological
     measures.
-  </p><h2><a name="id2629154"></a>
+  </p><h2><a name="id2629281"></a>
     4. Conveying Verbatim Copies.
   </h2><p>
     You may convey verbatim copies of the Program&#8217;s source code as you
@@ -255,7 +255,7 @@
   </p><p>
     You may charge any price or no price for each copy that you convey, and you
     may offer support or warranty protection for a fee.
-  </p><h2><a name="id2629181"></a>
+  </p><h2><a name="id2629308"></a>
     5. Conveying Modified Source Versions.
   </h2><p>
     You may convey a work based on the Program, or the modifications to produce
@@ -291,7 +291,7 @@
     or legal rights of the compilation&#8217;s users beyond what the individual works
     permit.  Inclusion of a covered work in an aggregate does not cause
     this License to apply to the other parts of the aggregate.
-  </p><h2><a name="id2629277"></a>
+  </p><h2><a name="id2629404"></a>
     6. Conveying Non-Source Forms.
   </h2><p>
     You may convey a covered work in object code form under the terms of
@@ -386,7 +386,7 @@
     (and with an implementation available to the public in source code form),
     and must require no special password or key for unpacking, reading or
     copying.
-  </p><h2><a name="id2629466"></a>
+  </p><h2><a name="id2629594"></a>
      7. Additional Terms.
    </h2><p>
      &#8220;Additional permissions&#8221; are terms that supplement the terms of
@@ -450,7 +450,7 @@
      Additional terms, permissive or non-permissive, may be stated in the form
      of a separately written license, or stated as exceptions; the above
      requirements apply either way.
-   </p><h2><a name="id2629602"></a>
+   </p><h2><a name="id2629729"></a>
      8. Termination.
    </h2><p>
      You may not propagate or modify a covered work except as expressly provided
@@ -476,7 +476,7 @@
      License.  If your rights have been terminated and not permanently
      reinstated, you do not qualify to receive new licenses for the same
      material under section 10.
-   </p><h2><a name="id2629646"></a>
+   </p><h2><a name="id2629773"></a>
      9. Acceptance Not Required for Having Copies.
    </h2><p>
      You are not required to accept this License in order to receive or run a
@@ -487,7 +487,7 @@
      These actions infringe copyright if you do not accept this License.
      Therefore, by modifying or propagating a covered work, you indicate your
      acceptance of this License to do so.
-   </p><h2><a name="id2629675"></a>
+   </p><h2><a name="id2629792"></a>
      10. Automatic Licensing of Downstream Recipients.
    </h2><p>
      Each time you convey a covered work, the recipient automatically receives a
@@ -512,7 +512,7 @@
      or counterclaim in a lawsuit) alleging that any patent claim is infringed
      by making, using, selling, offering for sale, or importing the Program or
      any portion of it.
-   </p><h2><a name="id2629727"></a>
+   </p><h2><a name="id2629844"></a>
     11. Patents.
   </h2><p>
     A &#8220;contributor&#8221; is a copyright holder who authorizes use under
@@ -579,7 +579,7 @@
     Nothing in this License shall be construed as excluding or limiting any
     implied license or other defenses to infringement that may otherwise be
     available to you under applicable patent law.
-  </p><h2><a name="id2629872"></a>
+  </p><h2><a name="id2629990"></a>
     12. No Surrender of Others&#8217; Freedom.
   </h2><p>
     If conditions are imposed on you (whether by court order, agreement or
@@ -591,7 +591,7 @@
     to collect a royalty for further conveying from those to whom you convey the
     Program, the only way you could satisfy both those terms and this License
     would be to refrain entirely from conveying the Program.
-  </p><h2><a name="id2629894"></a>
+  </p><h2><a name="id2630012"></a>
     13. Use with the <acronym class="acronym">GNU</acronym> Affero General Public License.
   </h2><p>
     Notwithstanding any other provision of this License, you have permission to
@@ -602,7 +602,7 @@
     requirements of the <acronym class="acronym">GNU</acronym> Affero General Public License,
     section 13, concerning interaction through a network will apply to the
     combination as such.
-  </p><h2><a name="id2629923"></a>
+  </p><h2><a name="id2630041"></a>
     14. Revised Versions of this License.
   </h2><p>
     The Free Software Foundation may publish revised and/or new versions of the
@@ -627,7 +627,7 @@
     Later license versions may give you additional or different permissions.
     However, no additional obligations are imposed on any author or copyright
     holder as a result of your choosing to follow a later version.
-  </p><h2><a name="id2629986"></a>
+  </p><h2><a name="id2630103"></a>
     15. Disclaimer of Warranty.
   </h2><p>
     THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
@@ -638,7 +638,7 @@
     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
     YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
     NECESSARY SERVICING, REPAIR OR CORRECTION.
-  </p><h2><a name="id2630012"></a>
+  </p><h2><a name="id2630129"></a>
     16. Limitation of Liability.
   </h2><p>
     IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
@@ -650,7 +650,7 @@
     PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
     EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
     SUCH DAMAGES.
-  </p><h2><a name="id2630032"></a>
+  </p><h2><a name="id2630150"></a>
     17. Interpretation of Sections 15 and 16.
   </h2><p>
     If the disclaimer of warranty and limitation of liability provided above
@@ -659,9 +659,9 @@
     waiver of all civil liability in connection with the Program, unless a
     warranty or assumption of liability accompanies a copy of the Program in
     return for a fee.
-  </p><h2><a name="id2630049"></a>
+  </p><h2><a name="id2630166"></a>
     END OF TERMS AND CONDITIONS
-  </h2><h2><a name="id2630052"></a>
+  </h2><h2><a name="id2630170"></a>
     How to Apply These Terms to Your New Programs
   </h2><p>
     If you develop a new program, and you want it to be of the greatest possible
diff --git a/docs/htmldocs/Samba3-ByExample/appendix.html b/docs/htmldocs/Samba3-ByExample/appendix.html
index e276164a9f..e944d450ba 100644
--- a/docs/htmldocs/Samba3-ByExample/appendix.html
+++ b/docs/htmldocs/Samba3-ByExample/appendix.html
@@ -1,18 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�A Collection of Useful Tidbits</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="ch14.html" title="Chapter�14.�Samba Support"><link rel="next" href="primer.html" title="Chapter�16.�Networking Primer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�A Collection of Useful Tidbits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch14.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="primer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="appendix"></a>Chapter�15.�A Collection of Useful Tidbits</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621811">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622232">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622592">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622604">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622652">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622792">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622851">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623411">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624406">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2624881">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625028">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625113">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p>
-	<a class="indexterm" name="id2621228"></a>
-	<a class="indexterm" name="id2621234"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�A Collection of Useful Tidbits</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="ch14.html" title="Chapter�14.�Samba Support"><link rel="next" href="primer.html" title="Chapter�16.�Networking Primer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�A Collection of Useful Tidbits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch14.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="primer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="appendix"></a>Chapter�15.�A Collection of Useful Tidbits</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621928">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622349">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622689">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622700">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622749">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622889">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622948">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623534">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624531">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2625006">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625153">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625237">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p>
+	<a class="indexterm" name="id2621349"></a>
+	<a class="indexterm" name="id2621356"></a>
 	Information presented here is considered to be either basic or well-known material that is informative
 	yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that
 	the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps
 	different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical,
 	as shown in the example given below.
 	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domjoin"></a>Joining a Domain: Windows 200x/XP Professional</h2></div></div></div><p>
-	<a class="indexterm" name="id2621264"></a>
+	<a class="indexterm" name="id2621386"></a>
 	Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security.
 	This section steps through the process for making a Windows 200x/XP Professional machine a
 	member of a Domain Security environment. It should be noted that this process is identical
 	when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
-	</p><div class="procedure"><a name="id2621278"></a><p class="title"><b>Procedure�15.1.�Steps to Join a Domain</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2621400"></a><p class="title"><b>Procedure�15.1.�Steps to Join a Domain</b></p><ol type="1"><li><p>
 		Click <span class="guimenu">Start</span>.
 		</p></li><li><p>
 		Right-click <span class="guimenu">My Computer</span>, and then select <span class="guimenuitem">Properties</span>.
@@ -50,19 +50,19 @@
 		The &#8220;<span class="quote">Welcome to the MIDEARTH domain</span>&#8221; dialog box should appear. At this point, the machine must be rebooted.
 		Joining the domain is now complete.
 		</p></li></ol></div><p>
-	<a class="indexterm" name="id2621696"></a>
-	<a class="indexterm" name="id2621703"></a>
+	<a class="indexterm" name="id2621818"></a>
+	<a class="indexterm" name="id2621825"></a>
 	The screen capture shown in <a class="link" href="appendix.html#swxpp007" title="Figure�15.4.�The Computer Name Changes Panel Domain MIDEARTH">&#8220;The Computer Name Changes Panel  Domain MIDEARTH&#8221;</a> has a button labeled <span class="guimenu">More...</span>. This button opens a
 	panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members
 	of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace.
 	</p><p>
-	<a class="indexterm" name="id2621730"></a>
-	<a class="indexterm" name="id2621736"></a>
+	<a class="indexterm" name="id2621851"></a>
+	<a class="indexterm" name="id2621858"></a>
 	Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers
 	register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server
 	to find the services (like which machines are domain controllers or which machines have the Netlogon service running).
 	</p><p>
-	<a class="indexterm" name="id2621755"></a>
+	<a class="indexterm" name="id2621876"></a>
 	The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix,
 	this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to
 	a valid IP address.
@@ -70,12 +70,12 @@
 	The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain.
 	Where the client is a member of a Samba domain, it is preferable to leave this field blank.
 	</p><p>
-	<a class="indexterm" name="id2621783"></a>
+	<a class="indexterm" name="id2621900"></a>
 	According to Microsoft documentation, &#8220;<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code>
 	enabled on <code class="literal">Primary DNS suffice of this computer</code>, the string specified in the Group Policy is used
 	as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is
 	used only if Group Policy is disabled or unspecified.</span>&#8221;
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621811"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2621818"></a><a class="indexterm" name="id2621826"></a><a class="indexterm" name="id2621834"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621928"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2621935"></a><a class="indexterm" name="id2621943"></a><a class="indexterm" name="id2621951"></a>
 	One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team
 	build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is
 	in the <code class="filename">/usr/local/samba</code> directory. This is a perfectly reasonable location, particularly given all the other
@@ -83,7 +83,7 @@
 	</p><p>
 	Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team
 	default. 
-	</p><p><a class="indexterm" name="id2621870"></a><a class="indexterm" name="id2621882"></a><a class="indexterm" name="id2621889"></a><a class="indexterm" name="id2621901"></a><a class="indexterm" name="id2621909"></a><a class="indexterm" name="id2621920"></a><a class="indexterm" name="id2621928"></a><a class="indexterm" name="id2621936"></a><a class="indexterm" name="id2621944"></a><a class="indexterm" name="id2621952"></a><a class="indexterm" name="id2621960"></a><a class="indexterm" name="id2621968"></a><a class="indexterm" name="id2621976"></a><a class="indexterm" name="id2621984"></a><a class="indexterm" name="id2621992"></a><a class="indexterm" name="id2622000"></a>
+	</p><p><a class="indexterm" name="id2621987"></a><a class="indexterm" name="id2621999"></a><a class="indexterm" name="id2622006"></a><a class="indexterm" name="id2622018"></a><a class="indexterm" name="id2622026"></a><a class="indexterm" name="id2622037"></a><a class="indexterm" name="id2622045"></a><a class="indexterm" name="id2622053"></a><a class="indexterm" name="id2622061"></a><a class="indexterm" name="id2622069"></a><a class="indexterm" name="id2622077"></a><a class="indexterm" name="id2622084"></a><a class="indexterm" name="id2622092"></a><a class="indexterm" name="id2622100"></a><a class="indexterm" name="id2622109"></a><a class="indexterm" name="id2622116"></a>
 	Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy	
 	System (FHS), have elected to locate the configuration files under the <code class="filename">/etc/samba</code> directory, common binary
 	files (those used by users) in the <code class="filename">/usr/bin</code> directory, and the administrative files (daemons) in the
@@ -92,13 +92,13 @@
 	<code class="filename">/usr/share/swat</code>. There are additional support files for <code class="literal">smbd</code> in the
 	<code class="filename">/usr/lib/samba</code> directory tree. The files located there include the dynamically loadable modules for the
 	passdb backend as well as for the VFS modules.
-	</p><p><a class="indexterm" name="id2622069"></a><a class="indexterm" name="id2622077"></a><a class="indexterm" name="id2622085"></a>
+	</p><p><a class="indexterm" name="id2622186"></a><a class="indexterm" name="id2622194"></a><a class="indexterm" name="id2622202"></a>
 	Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in
 	the <code class="filename">/var/lib/samba</code> directory. Log files are created in <code class="filename">/var/log/samba.</code>
 	</p><p>
 	When Samba is built and installed using the default Samba Team process, all files are located under the 
 	<code class="filename">/usr/local/samba</code> directory tree. This makes it simple to find the files that Samba owns.
-	</p><p><a class="indexterm" name="id2622123"></a>
+	</p><p><a class="indexterm" name="id2622240"></a>
 	One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location
 	of all files called <code class="literal">smbd</code>. Here is an example:
 </p><pre class="screen">
@@ -131,7 +131,7 @@ Version 3.0.20-SUSE
 	</p><p>
 	Many people have been caught by installation of Samba using the default Samba Team process when it was already installed
 	by the platform vendor's method. If your platform uses RPM format packages, you can check to see if Samba is installed by
-	executing:<a class="indexterm" name="id2622196"></a>
+	executing:<a class="indexterm" name="id2622313"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> rpm -qa | grep samba
 samba3-pdb-3.0.20-1
@@ -143,9 +143,9 @@ samba3-utils-3.0.20-1
 samba3-doc-3.0.20-1
 samba3-client-3.0.20-1
 samba3-cifsmount-3.0.20-1
-	</pre><p><a class="indexterm" name="id2622219"></a>
+	</pre><p><a class="indexterm" name="id2622336"></a>
 	The package names, of course, vary according to how the vendor, or the binary package builder, prepared them.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622232"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2622239"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622349"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2622356"></a>
 	Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
 	An example of a service is the Apache Web server for which the daemon is called <code class="literal">httpd</code>. In the case of Samba, there
 	are three daemons, two of which are needed as a minimum.
@@ -186,19 +186,19 @@ if [ $1 == 'restart' ]; then
 fi
 exit 0
 </pre></div></div><br class="example-break"><div class="variablelist"><dl><dt><span class="term">nmbd</span></dt><dd><p>
-			<a class="indexterm" name="id2622312"></a>
-			<a class="indexterm" name="id2622319"></a>
+			<a class="indexterm" name="id2622419"></a>
+			<a class="indexterm" name="id2622425"></a>
 			This daemon handles all name registration and resolution requests. It is the primary vehicle involved
 			in network browsing. It handles all UDP-based protocols. The <code class="literal">nmbd</code> daemon should
 			be the first command started as part of the Samba startup process.
 			</p></dd><dt><span class="term">smbd</span></dt><dd><p>
-			<a class="indexterm" name="id2622349"></a>
-			<a class="indexterm" name="id2622355"></a>
+			<a class="indexterm" name="id2622455"></a>
+			<a class="indexterm" name="id2622462"></a>
 			This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
 			manages local authentication. It should be started immediately following the startup of <code class="literal">nmbd</code>.
 			</p></dd><dt><span class="term">winbindd</span></dt><dd><p>
-			<a class="indexterm" name="id2622384"></a>
-			<a class="indexterm" name="id2622391"></a>
+			<a class="indexterm" name="id2622490"></a>
+			<a class="indexterm" name="id2622497"></a>
 			This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
 			Samba has trust relationships with another domain. The <code class="literal">winbindd</code> daemon will check the
 			<code class="filename">smb.conf</code> file for the presence of the <em class="parameter"><code>idmap uid</code></em> and <em class="parameter"><code>idmap gid</code></em>
@@ -252,22 +252,22 @@ case "$1" in
         echo "Usage: smb {start|stop|restart|status}"
         exit 1
 esac
-</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2622513"></a>
+</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2622610"></a>
 	SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently
 	executed from the command line is shown in <a class="link" href="appendix.html#ch12SL" title="Example�15.1.�A Useful Samba Control Script for SUSE Linux">&#8220;A Useful Samba Control Script for SUSE Linux&#8221;</a>. This can be located in the directory
 	<code class="filename">/sbin</code> in a file called <code class="filename">samba</code>. This type of control script should be
 	owned by user root and group root, and set so that only root can execute it.
-	</p><p><a class="indexterm" name="id2622549"></a>
+	</p><p><a class="indexterm" name="id2622646"></a>
 	A sample startup script for a Red Hat Linux system is shown in <a class="link" href="appendix.html#ch12RHscript" title="Example�15.2.�A Sample Samba Control Script for Red Hat Linux">&#8220;A Sample Samba Control Script for Red Hat Linux&#8221;</a>.
 	This file could be located in the directory <code class="filename">/etc/rc.d</code> and can be called
 	<code class="filename">samba</code>. A similar startup script is required to control <code class="literal">winbind</code>.
 	If you want to find more information regarding startup scripts please refer to the packaging section of
 	the Samba source code distribution tarball. The packaging files for each platform include a
 	startup control file.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622592"></a>DNS Configuration Files</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622689"></a>DNS Configuration Files</h2></div></div></div><p>
 	The following files are common to all DNS server configurations. Rather than repeat them multiple times, they
 	are presented here for general reference.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622604"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622700"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p>
 	The forward zone file for the loopback address never changes. An example file is shown
 	in <a class="link" href="appendix.html#loopback" title="Example�15.3.�DNS Localhost Forward Zone File: /var/lib/named/localhost.zone">&#8220;DNS Localhost Forward Zone File: /var/lib/named/localhost.zone&#8221;</a>. All traffic destined for an IP address that is hosted on a
 	physical interface on the machine itself is routed to the loopback adaptor. This is
@@ -284,7 +284,7 @@ $TTL 1W
 
 		IN NS		@
 		IN A		127.0.0.1
-</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622652"></a>The Reverse Zone File for the Loopback Adaptor</h3></div></div></div><p>
+</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622749"></a>The Reverse Zone File for the Loopback Adaptor</h3></div></div></div><p>
 	The reverse zone file for the loopback address as shown in <a class="link" href="appendix.html#dnsloopy" title="Example�15.4.�DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone">&#8220;DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone&#8221;</a>
 	is necessary so that references to the address <code class="constant">127.0.0.1</code> can be
 	resolved to the correct name of the interface. 
@@ -344,15 +344,15 @@ L.ROOT-SERVERS.NET.      3600000      A     198.32.64.12
 .                        3600000      NS    M.ROOT-SERVERS.NET.
 M.ROOT-SERVERS.NET.      3600000      A     202.12.27.33
 ; End of File
-</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622792"></a>DNS Root Server Hint File</h3></div></div></div><p>
+</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622889"></a>DNS Root Server Hint File</h3></div></div></div><p>
 	The content of the root hints file as shown in <a class="link" href="appendix.html#roothint" title="Example�15.5.�DNS Root Name Server Hint File: /var/lib/named/root.hint">&#8220;DNS Root Name Server Hint File: /var/lib/named/root.hint&#8221;</a>  changes slowly over time. 
 	Periodically this file should be updated from the source shown. Because
 	  of its size, this file is located at the end of this chapter.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altldapcfg"></a>Alternative LDAP Database Initialization</h2></div></div></div><p><a class="indexterm" name="id2622823"></a><a class="indexterm" name="id2622834"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altldapcfg"></a>Alternative LDAP Database Initialization</h2></div></div></div><p><a class="indexterm" name="id2622920"></a><a class="indexterm" name="id2622931"></a>
 	The following procedure may be used as an alternative means of configuring
 	the initial LDAP database. Many administrators prefer to have greater control
 	over how system files get configured.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622851"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2622858"></a><a class="indexterm" name="id2622866"></a><a class="indexterm" name="id2622878"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622948"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2622955"></a><a class="indexterm" name="id2622963"></a><a class="indexterm" name="id2622975"></a>
 	The first step to get the LDAP server ready for action is to create the LDIF file from
 	which the LDAP database will be preloaded. This is necessary to create the containers
 	into which the user, group, and other accounts are written. It is also necessary to
@@ -705,14 +705,14 @@ sambaSID: DOMSID-513
 sambaGroupType: 2
 displayName: Domain Users
 description: Domain Users
-</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2623411"></a>The LDAP Account Manager</h2></div></div></div><p>
-<a class="indexterm" name="id2623419"></a>
-<a class="indexterm" name="id2623426"></a>
-<a class="indexterm" name="id2623435"></a>
-<a class="indexterm" name="id2623442"></a>
-<a class="indexterm" name="id2623448"></a>
-<a class="indexterm" name="id2623455"></a>
-<a class="indexterm" name="id2623462"></a>
+</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2623534"></a>The LDAP Account Manager</h2></div></div></div><p>
+<a class="indexterm" name="id2623542"></a>
+<a class="indexterm" name="id2623549"></a>
+<a class="indexterm" name="id2623558"></a>
+<a class="indexterm" name="id2623564"></a>
+<a class="indexterm" name="id2623571"></a>
+<a class="indexterm" name="id2623578"></a>
+<a class="indexterm" name="id2623585"></a>
 The LDAP Account Manager (LAM) is an application suite that has been written in PHP.
 LAM can be used with any Web server that has PHP4 support. It connects to the LDAP
 server either using unencrypted connections or via SSL/TLS. LAM can be used to manage
@@ -724,24 +724,24 @@ home page and from its mirror sites. LAM has been released under the GNU GPL ver
 The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter
 of 2005.
 </p><p>
-<a class="indexterm" name="id2623493"></a>
-<a class="indexterm" name="id2623500"></a>
-<a class="indexterm" name="id2623507"></a>
+<a class="indexterm" name="id2623616"></a>
+<a class="indexterm" name="id2623623"></a>
+<a class="indexterm" name="id2623630"></a>
 Requirements:
 </p><div class="itemizedlist"><ul type="disc"><li><p>A web server that will work with PHP4.</p></li><li><p>PHP4 (available from the <a class="ulink" href="http://www.php.net/" target="_top">PHP</a> home page.)</p></li><li><p>OpenLDAP 2.0 or later.</p></li><li><p>A Web browser that supports CSS.</p></li><li><p>Perl.</p></li><li><p>The gettext package.</p></li><li><p>mcrypt + mhash (optional).</p></li><li><p>It is also a good idea to install SSL support.</p></li></ul></div><p>
 LAM is a useful tool that provides a simple Web-based device that can be used to
 manage the contents of the LDAP directory to:
-<a class="indexterm" name="id2623568"></a>
-<a class="indexterm" name="id2623575"></a>
-<a class="indexterm" name="id2623582"></a>
+<a class="indexterm" name="id2623691"></a>
+<a class="indexterm" name="id2623698"></a>
+<a class="indexterm" name="id2623705"></a>
 </p><div class="itemizedlist"><ul type="disc"><li><p>Display user/group/host and Domain entries.</p></li><li><p>Manage entries (Add/Delete/Edit).</p></li><li><p>Filter and sort entries.</p></li><li><p>Store and use multiple operating profiles.</p></li><li><p>Edit organizational units (OUs).</p></li><li><p>Upload accounts from a file.</p></li><li><p>Is compatible with Samba-2.2.x and Samba-3.</p></li></ul></div><p>
 When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba
 user, group, and windows domain member machine accounts.
 </p><p>
-<a class="indexterm" name="id2623636"></a>
-<a class="indexterm" name="id2623643"></a>
-<a class="indexterm" name="id2623650"></a>
-<a class="indexterm" name="id2623656"></a>
+<a class="indexterm" name="id2623759"></a>
+<a class="indexterm" name="id2623766"></a>
+<a class="indexterm" name="id2623772"></a>
+<a class="indexterm" name="id2623779"></a>
 The default password is &#8220;<span class="quote">lam.</span>&#8221; It is highly recommended that you use only 
 an SSL connection to your Web server for all remote operations involving LAM. If you 
 want secure connections, you must configure your Apache Web server to permit connections 
@@ -760,7 +760,7 @@ to LAM using only SSL.
 	For example, on SUSE Linux Enterprise Server 9, copy to the 
 	<code class="filename">/srv/www/htdocs</code> directory.
 	</p></li><li><p>
-	<a class="indexterm" name="id2623736"></a>
+	<a class="indexterm" name="id2623859"></a>
 	Set file permissions using the following commands:
 </p><pre class="screen">
 <code class="prompt">root# </code> chown -R wwwrun:www /srv/www/htdocs/lam
@@ -770,7 +770,7 @@ to LAM using only SSL.
 <code class="prompt">root# </code> chmod 755 /srv/www/htdocs/lam/lib/*pl
 </pre><p>
 	</p></li><li><p>
-	<a class="indexterm" name="id2623789"></a>
+	<a class="indexterm" name="id2623912"></a>
        Using your favorite editor create the following <code class="filename">config.cfg</code>
        LAM configuration file:
 </p><pre class="screen">
@@ -778,8 +778,8 @@ to LAM using only SSL.
 <code class="prompt">root# </code> cp config.cfg_sample config.cfg
 <code class="prompt">root# </code> vi config.cfg
 </pre><p>
-	<a class="indexterm" name="id2623830"></a>
-	<a class="indexterm" name="id2623839"></a>
+	<a class="indexterm" name="id2623953"></a>
+	<a class="indexterm" name="id2623962"></a>
 	An example file is shown in <a class="link" href="appendix.html#lamcfg" title="Example�15.11.�Example LAM Configuration File config.cfg">&#8220;Example LAM Configuration File  config.cfg&#8221;</a>.
 	This is the minimum configuration that must be completed. The LAM profile
 	file can be created using a convenient wizard that is part of the LAM
@@ -794,7 +794,7 @@ to LAM using only SSL.
 	<code class="filename">lam.conf</code> then, using your favorite editor, 
 	change the settings to match local site needs.
 	</p></li></ol></div><p>
-	<a class="indexterm" name="id2623898"></a>
+	<a class="indexterm" name="id2624021"></a>
 	An example of a working file is shown here in <a class="link" href="appendix.html#lamconf" title="Example�15.12.�LAM Profile Control File lam.conf">&#8220;LAM Profile Control File  lam.conf&#8221;</a>.
 	This file has been stripped of comments to keep the size small. The comments
 	and help information provided in the profile file that the wizard creates
@@ -802,12 +802,12 @@ to LAM using only SSL.
 	Your configuration file obviously reflects the configuration options that
 	are preferred at your site.
 	</p><p>
-	<a class="indexterm" name="id2623921"></a>
+	<a class="indexterm" name="id2624044"></a>
 	It is important that your LDAP server is running at the time that LAM is 
 	being configured. This permits you to validate correct operation.
 	An example of the LAM login screen is provided in <a class="link" href="appendix.html#lam-login" title="Figure�15.6.�The LDAP Account Manager Login Screen">&#8220;The LDAP Account Manager Login Screen&#8221;</a>.
 	</p><div class="figure"><a name="lam-login"></a><p class="title"><b>Figure�15.6.�The LDAP Account Manager Login Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-login.png" width="270" alt="The LDAP Account Manager Login Screen"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2623984"></a>
+	<a class="indexterm" name="id2624107"></a>
 	The LAM configuration editor has a number of options that must be managed correctly.
 	An example of use of the LAM configuration editor is shown in <a class="link" href="appendix.html#lam-config" title="Figure�15.7.�The LDAP Account Manager Configuration Screen">&#8220;The LDAP Account Manager Configuration Screen&#8221;</a>.
 	It is important that you correctly set the minimum and maximum UID/GID values that are
@@ -817,13 +817,13 @@ to LAM using only SSL.
 	the initial settings to be made. Do not forget to reset these to sensible values before
 	using LAM to add additional users and groups.
 	</p><div class="figure"><a name="lam-config"></a><p class="title"><b>Figure�15.7.�The LDAP Account Manager Configuration Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-config.png" width="270" alt="The LDAP Account Manager Configuration Screen"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2624056"></a>
+	<a class="indexterm" name="id2624178"></a>
 	LAM has some nice, but unusual features. For example, one unexpected feature in most application
 	screens permits the generation of a PDF file that lists configuration information. This is a well
 	thought out facility. This option has been edited out of the following screen shots to conserve
 	space.
 	</p><p>
-	<a class="indexterm" name="id2624071"></a>
+	<a class="indexterm" name="id2624194"></a>
 	When you log onto LAM the opening screen drops you right into the user manager as shown in
 	<a class="link" href="appendix.html#lam-user" title="Figure�15.8.�The LDAP Account Manager User Edit Screen">&#8220;The LDAP Account Manager User Edit Screen&#8221;</a>. This is a logical action as it permits the most-needed facility
 	to be used immediately. The editing of an existing user, as with the addition of a new user,
@@ -837,7 +837,7 @@ to LAM using only SSL.
 	shows a sub-screen from the group editor that permits users to be assigned secondary group
 	memberships. 
 	</p><div class="figure"><a name="lam-group"></a><p class="title"><b>Figure�15.9.�The LDAP Account Manager Group Edit Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-groups.png" width="270" alt="The LDAP Account Manager Group Edit Screen"></div></div></div><br class="figure-break"><div class="figure"><a name="lam-group-mem"></a><p class="title"><b>Figure�15.10.�The LDAP Account Manager Group Membership Edit Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-group-members.png" width="270" alt="The LDAP Account Manager Group Membership Edit Screen"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2624251"></a><a class="indexterm" name="id2624256"></a>
+	<a class="indexterm" name="id2624374"></a><a class="indexterm" name="id2624379"></a>
 	The final screen presented here is one that you should not normally need to use. Host accounts will
 	be automatically managed using the smbldap-tools scripts. This means that the screen <a class="link" href="appendix.html#lam-host" title="Figure�15.11.�The LDAP Account Manager Host Edit Screen">&#8220;The LDAP Account Manager Host Edit Screen&#8221;</a>
 	will, in most cases, not be used.
@@ -883,7 +883,7 @@ scriptServer:
 samba3: yes
 cachetimeout: 5
 pwdhash: SSHA
-</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2624406"></a>IDEALX Management Console</h2></div></div></div><p>
+</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2624531"></a>IDEALX Management Console</h2></div></div></div><p>
 	IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive
 	web-based management interface for UNIX and Linux systems.
 	</p><p>
@@ -897,7 +897,7 @@ pwdhash: SSHA
 	</p><p>
 	For further information regarding IMC refer to the web <a class="ulink" href="http://imc.sourceforge.net/" target="_top">site.</a>
 	Prebuilt RPM packages are also <a class="ulink" href="http://imc.sourceforge.net/download.html" target="_top">available.</a>
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12-SUIDSGID"></a>Effect of Setting File and Directory SUID/SGID Permissions Explained</h2></div></div></div><a class="indexterm" name="id2624512"></a><a class="indexterm" name="id2624519"></a><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12-SUIDSGID"></a>Effect of Setting File and Directory SUID/SGID Permissions Explained</h2></div></div></div><a class="indexterm" name="id2624636"></a><a class="indexterm" name="id2624643"></a><p>
 	The setting of the SUID/SGID bits on the file or directory permissions flag has particular
 	consequences. If the file is executable and the SUID bit is set, it executes with the privilege
 	of (with the UID of) the owner of the file. For example, if you are logged onto a system as
@@ -967,34 +967,34 @@ drwx------    2 root     root           48 Jan 26  2002 lost+found
 total 1
 drw-rw-r--    2 bobj     Domain Users  12346 Dec 18 18:11 maryvfile.txt
 </pre><p>
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12dblck"></a>Shared Data Integrity</h2></div></div></div><p><a class="indexterm" name="id2624750"></a><a class="indexterm" name="id2624757"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12dblck"></a>Shared Data Integrity</h2></div></div></div><p><a class="indexterm" name="id2624874"></a><a class="indexterm" name="id2624882"></a>
 	The integrity of shared data is often viewed as a particularly emotional issue, especially where
 	there are concurrent problems with multiuser data access. Contrary to the assertions of some who have
 	experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter.
 	</p><p>
 	The solution to concurrent multiuser data access problems must consider three separate areas
-	from which the problem may stem:<a class="indexterm" name="id2624781"></a><a class="indexterm" name="id2624792"></a><a class="indexterm" name="id2624803"></a>
-	</p><div class="itemizedlist"><ul type="disc"><li><p>application-level locking controls</p></li><li><p>client-side locking controls</p></li><li><p>server-side locking controls</p></li></ul></div><p><a class="indexterm" name="id2624836"></a><a class="indexterm" name="id2624844"></a>
+	from which the problem may stem:<a class="indexterm" name="id2624905"></a><a class="indexterm" name="id2624917"></a><a class="indexterm" name="id2624928"></a>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>application-level locking controls</p></li><li><p>client-side locking controls</p></li><li><p>server-side locking controls</p></li></ul></div><p><a class="indexterm" name="id2624961"></a><a class="indexterm" name="id2624969"></a>
 	Many database applications use some form of application-level access control. An example of one
 	well-known application that uses application-level locking is Microsoft Access. Detailed guidance
 	is provided here because this is the most common application for which problems have been reported.
-	</p><p><a class="indexterm" name="id2624860"></a><a class="indexterm" name="id2624868"></a>
+	</p><p><a class="indexterm" name="id2624985"></a><a class="indexterm" name="id2624993"></a>
 	Common applications that are affected by client- and server-side locking controls include MS
 	Excel and Act!. Important locking guidance is provided here.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2624881"></a>Microsoft Access</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625006"></a>Microsoft Access</h3></div></div></div><p>
 	The best advice that can be given is to carefully read the Microsoft knowledgebase articles that
 	cover this area. Examples of relevant documents include:
-	</p><div class="itemizedlist"><ul type="disc"><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</p></li><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</p></li></ul></div><p><a class="indexterm" name="id2624908"></a><a class="indexterm" name="id2624919"></a>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</p></li><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</p></li></ul></div><p><a class="indexterm" name="id2625033"></a><a class="indexterm" name="id2625044"></a>
 	Make sure that your MS Access database file is configured for multiuser access (not set for 
 	exclusive open). Open MS Access on each client workstation, then set the following: <span class="guimenu">(Menu bar) Tools</span>+<span class="guimenu">Options</span>+<span class="guimenu">[tab] General</span>.  Set network path to Default database folder: <code class="filename">\\server\share\folder</code>.
 	</p><p>
         You can configure MS Access file sharing behavior as follows: click <span class="guimenu">[tab] Advanced</span>.
-	  Set:<a class="indexterm" name="id2624970"></a>
-	</p><div class="itemizedlist"><ul type="disc"><li><p>Default open mode: Shared</p></li><li><p>Default Record Locking: Edited Record</p></li><li><p>Open databases using record_level locking</p></li></ul></div><p><a class="indexterm" name="id2625000"></a>
+	  Set:<a class="indexterm" name="id2625095"></a>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>Default open mode: Shared</p></li><li><p>Default Record Locking: Edited Record</p></li><li><p>Open databases using record_level locking</p></li></ul></div><p><a class="indexterm" name="id2625124"></a>
         You must now commit the changes so that they will take effect. To do so, click 
 	<span class="guimenu">Apply</span><span class="guimenu">Ok</span>. At this point, you should exit MS Access, restart 
 	it, and then validate that these settings have not changed.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625028"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2625035"></a><a class="indexterm" name="id2625043"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625153"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2625160"></a><a class="indexterm" name="id2625168"></a>
 	Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you 
 	must disable opportunistic locking on the server and all workstations. Failure to do so
 	results in data corruption. This information is available from the Act! Web site
@@ -1002,7 +1002,7 @@ drw-rw-r--    2 bobj     Domain Users  12346 Dec 18 18:11 maryvfile.txt
 	<a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/1998223162925" target="_top">1998223162925</a>
 	as well as from article
 	<a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/200110485036" target="_top">200110485036</a>.
-	</p><p><a class="indexterm" name="id2625073"></a><a class="indexterm" name="id2625081"></a>
+	</p><p><a class="indexterm" name="id2625198"></a><a class="indexterm" name="id2625206"></a>
 	These documents clearly state that opportunistic locking must be disabled on both
 	the server (Samba in the case we are interested in here), as well as on every workstation
 	from which the centrally shared Act! database will be accessed. Act! provides
@@ -1010,18 +1010,18 @@ drw-rw-r--    2 bobj     Domain Users  12346 Dec 18 18:11 maryvfile.txt
 	registry settings that may otherwise interfere with the operation of Act! 
 	Registered Act! users may download this utility from the Act! Web 
 	<a class="ulink" href="http://www.act.com/support/updates/index.cfm" target="_top">site.</a>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625113"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2625120"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625237"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2625244"></a>
 	Third-party Windows applications may not be compatible with the use of opportunistic file
-	and record locking. For applications that are known not to be compatible,<sup>[<a name="id2625132" href="#ftn.id2625132" class="footnote">14</a>]</sup> oplock
+	and record locking. For applications that are known not to be compatible,<sup>[<a name="id2625256" href="#ftn.id2625256" class="footnote">14</a>]</sup> oplock
 	support may need to be disabled both on the Samba server and on the Windows workstations.
-	</p><p><a class="indexterm" name="id2625147"></a><a class="indexterm" name="id2625155"></a><a class="indexterm" name="id2625163"></a>
+	</p><p><a class="indexterm" name="id2625271"></a><a class="indexterm" name="id2625278"></a><a class="indexterm" name="id2625286"></a>
 	Oplocks enable a Windows client to cache parts of a file that are being
 	edited. Another windows client may then request to open the file with the
 	ability to write to it. The server will then ask the original workstation
 	that had the file open with a write lock to release its lock. Before
 	doing so, that workstation must flush the file from cache memory to the
 	disk or network drive.
-	</p><p><a class="indexterm" name="id2625184"></a>
+	</p><p><a class="indexterm" name="id2625308"></a>
 	Disabling of Oplocks usage may require server and client changes.
 	Oplocks may be disabled by file, by file pattern, on the share, or on the
 	Samba server.
@@ -1057,9 +1057,4 @@ REGEDIT4
 	</p><p>
 	Comprehensive coverage of file and record-locking controls is provided in TOSHARG2, Chapter 13.
 	The information in that chapter was obtained from a wide variety of sources.
-	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2625132" href="#id2625132" class="para">14</a>] </sup>Refer to
-	the application manufacturer's installation guidelines and knowledge base for specific
-	information regarding compatibility. It is often safe to assume that if the software
-	manufacturer does not specifically mention incompatibilities with opportunistic file
-	and record locking, or with Windows client file caching, the application is probably
-	compatible with Windows (as well as Samba) default settings.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch14.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="primer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�14.�Samba Support�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�16.�Networking Primer</td></tr></table></div></body></html>
+	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch14.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="primer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�14.�Samba Support�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�16.�Networking Primer</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/ch14.html b/docs/htmldocs/Samba3-ByExample/ch14.html
index e3239a06a6..57d4492cee 100644
--- a/docs/htmldocs/Samba3-ByExample/ch14.html
+++ b/docs/htmldocs/Samba3-ByExample/ch14.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�14.�Samba Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="HA.html" title="Chapter�13.�Performance, Reliability, and Availability"><link rel="next" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�14.�Samba Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="HA.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="appendix.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2620743"></a>Chapter�14.�Samba Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch14.html#id2620874">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621092">Commercial Support</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2620752"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�14.�Samba Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="HA.html" title="Chapter�13.�Performance, Reliability, and Availability"><link rel="next" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�14.�Samba Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="HA.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="appendix.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2620871"></a>Chapter�14.�Samba Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch14.html#id2621002">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621220">Commercial Support</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2620880"></a>
 One of the most difficult to answer questions in the information technology industry is, &#8220;<span class="quote">What is
 support?</span>&#8221;. That question irritates some folks, as much as common answers may annoy others.
 </p><p>
-<a class="indexterm" name="id2620769"></a>
+<a class="indexterm" name="id2620897"></a>
 The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
 an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
 &#8220;<span class="quote">Oh, Linux? We do not support Linux!</span>&#8221;. It has happened to me, and similar situations happen
@@ -15,50 +15,50 @@ One way to consider support is to view it as consisting of the right answer, in
 at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
 inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
 </p><p>
-<a class="indexterm" name="id2620800"></a>
-<a class="indexterm" name="id2620807"></a>
-<a class="indexterm" name="id2620814"></a>
+<a class="indexterm" name="id2620928"></a>
+<a class="indexterm" name="id2620935"></a>
+<a class="indexterm" name="id2620942"></a>
 One of the forces that has become a driving force for the adoption of open source software is the fact that
 many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
 that have been found wanting for other reasons.
 </p><p>
-<a class="indexterm" name="id2620828"></a>
-<a class="indexterm" name="id2620835"></a>
+<a class="indexterm" name="id2620956"></a>
+<a class="indexterm" name="id2620963"></a>
 In recognition of the need for needs satisfaction as the primary experience an information technology user or
 consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
 in respect of problem resolution.
 </p><p>
-<a class="indexterm" name="id2620850"></a>
-<a class="indexterm" name="id2620857"></a>
-<a class="indexterm" name="id2620864"></a>
+<a class="indexterm" name="id2620978"></a>
+<a class="indexterm" name="id2620985"></a>
+<a class="indexterm" name="id2620992"></a>
 In the open source software arena there are two support options: free support and paid-for (commercial)
 support.
-</p><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620874"></a>Free Support</h2></div></div></div><p>
-<a class="indexterm" name="id2620881"></a>
-<a class="indexterm" name="id2620888"></a>
-<a class="indexterm" name="id2620895"></a>
-<a class="indexterm" name="id2620902"></a>
-<a class="indexterm" name="id2620909"></a>
-<a class="indexterm" name="id2620916"></a>
+</p><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621002"></a>Free Support</h2></div></div></div><p>
+<a class="indexterm" name="id2621010"></a>
+<a class="indexterm" name="id2621016"></a>
+<a class="indexterm" name="id2621023"></a>
+<a class="indexterm" name="id2621030"></a>
+<a class="indexterm" name="id2621037"></a>
+<a class="indexterm" name="id2621044"></a>
 	Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
 	facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
 	supported mutual assistance.
 	</p><p>
-<a class="indexterm" name="id2620930"></a>
-<a class="indexterm" name="id2620937"></a>
-<a class="indexterm" name="id2620944"></a>
-<a class="indexterm" name="id2620951"></a>
-<a class="indexterm" name="id2620958"></a>
+<a class="indexterm" name="id2621058"></a>
+<a class="indexterm" name="id2621065"></a>
+<a class="indexterm" name="id2621072"></a>
+<a class="indexterm" name="id2621079"></a>
+<a class="indexterm" name="id2621086"></a>
 	The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
 	Information regarding subscription to the Samba mailing list can be found on the Samba <a class="ulink" href="https://lists.samba.org/mailman/" target="_top">web</a> site. The public mailing list that can be used to obtain
 	free, user contributed, support is called the <code class="literal">samba</code> list. The email address for this list
 	is at <code class="literal">mail:samba@samba.org</code>.  Information regarding the Samba IRC channels may be found on
 	the Samba <a class="ulink" href="http://www.samba.org/samba.irc.html" target="_top">IRC</a> web page.
 	</p><p>
-<a class="indexterm" name="id2620999"></a>
-<a class="indexterm" name="id2621006"></a>
-<a class="indexterm" name="id2621013"></a>
-<a class="indexterm" name="id2621020"></a>
+<a class="indexterm" name="id2621127"></a>
+<a class="indexterm" name="id2621134"></a>
+<a class="indexterm" name="id2621141"></a>
+<a class="indexterm" name="id2621148"></a>
 	As a general rule, it is considered poor net behavior to contact a Samba Team member directly
 	for free support. Most active members of the Samba Team work exceptionally long hours to assist
 	users who have demonstrated a qualified problem. Some team members may respond to direct email
@@ -66,9 +66,9 @@ support.
 	Team members actually provide professional paid-for Samba support and it is therefore wise
 	to show appropriate discretion and reservation in all direct contact.
 	</p><p>
-<a class="indexterm" name="id2621040"></a>
-<a class="indexterm" name="id2621046"></a>
-<a class="indexterm" name="id2621053"></a>
+<a class="indexterm" name="id2621168"></a>
+<a class="indexterm" name="id2621174"></a>
+<a class="indexterm" name="id2621181"></a>
 	When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
 	a bug <a class="ulink" href="https://bugzilla.samba.org/" target="_top">report</a>. All such reports are mailed to
 	the responsible code maintainer for action. The better the report, and the more serious it is,
@@ -76,16 +76,16 @@ support.
 	the reported bug it is likely to be rejected. It is up to you to provide sufficient information
 	that will permit the problem to be reproduced.
 	</p><p>
-<a class="indexterm" name="id2621078"></a>
+<a class="indexterm" name="id2621206"></a>
 	We all recognize that sometimes free support does not provide the answer that is sought within
 	the time-frame required. At other times the problem is elusive and you may lack the experience
 	necessary to isolate the problem and thus to resolve it. This is a situation where is may be
 	prudent to purchase paid-for support.
-	</p></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621092"></a>Commercial Support</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621220"></a>Commercial Support</h2></div></div></div><p>
 	There are six basic support oriented services that are most commonly sought by Samba sites:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Assistance with network design</p></li><li><p>Staff Training</p></li><li><p>Assistance with Samba network deployment and installation</p></li><li><p>Priority telephone or email Samba configuration assistance</p></li><li><p>Trouble-shooting and diagnostic assistance</p></li><li><p>Provision of quality assured ready-to-install Samba binary packages</p></li></ul></div><p>
-<a class="indexterm" name="id2621139"></a>
-<a class="indexterm" name="id2621146"></a>
+<a class="indexterm" name="id2621267"></a>
+<a class="indexterm" name="id2621274"></a>
 	Information regarding companies that provide professional Samba support can be obtained by performing a Google
 	search, as well as by reference to the Samba <a class="ulink" href="http://www.samba.org/samba/support.html" target="_top">Support</a> web page. Companies who notify the Samba Team
 	that they provide commercial support are given a free listing that is sorted by the country of origin.
@@ -93,13 +93,13 @@ support.
 	provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
 	them.
 	</p><p>
-<a class="indexterm" name="id2621172"></a>
+<a class="indexterm" name="id2621300"></a>
 	The policy within the Samba Team is to treat all commercial support providers equally and to show no
 	preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
 	You are encouraged to obtain the services needed from a company in your local area. The open source movement
 	is pro-community; so do what you can to help a local business to prosper.
 	</p><p>
-<a class="indexterm" name="id2621195"></a>
+<a class="indexterm" name="id2621317"></a>
 	Open source software support can be found in any quality, at any price and in any place you can
 	to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
 	suffering in the mistaken belief that Samba is unsupported software  it is supported.
diff --git a/docs/htmldocs/Samba3-ByExample/go01.html b/docs/htmldocs/Samba3-ByExample/go01.html
index 3eb565bccf..250b594de9 100644
--- a/docs/htmldocs/Samba3-ByExample/go01.html
+++ b/docs/htmldocs/Samba3-ByExample/go01.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="apa.html" title="Appendix�A.� GNU General Public License version 3"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id2630241"></a>Glossary</h2></div></div></div><dl><dt>Access Control List</dt><dd><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="apa.html" title="Appendix�A.� GNU General Public License version 3"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id2630359"></a>Glossary</h2></div></div></div><dl><dt>Access Control List</dt><dd><p>
 		A detailed list of permissions granted to users or groups with respect to file and network
 		resource access.
 		</p></dd><dt>Active Directory Service</dt><dd><p>
diff --git a/docs/htmldocs/Samba3-ByExample/happy.html b/docs/htmldocs/Samba3-ByExample/happy.html
index eee7cb97f1..41cd3b5a67 100644
--- a/docs/htmldocs/Samba3-ByExample/happy.html
+++ b/docs/htmldocs/Samba3-ByExample/happy.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Making Happy Users</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="Big500users.html" title="Chapter�4.�The 500-User Office"><link rel="next" href="net2000users.html" title="Chapter�6.�A Distributed 2000-User Network"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Making Happy Users</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Big500users.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="net2000users.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="happy"></a>Chapter�5.�Making Happy Users</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571164">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571262">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571399">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573730">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573745">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573925">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580771">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580791">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580886">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581130">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581241">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581375">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582445">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583127">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583163">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583197">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583303">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Making Happy Users</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="Big500users.html" title="Chapter�4.�The 500-User Office"><link rel="next" href="2000users.html" title="Chapter�6.�A Distributed 2000-User Network"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Making Happy Users</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Big500users.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="2000users.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="happy"></a>Chapter�5.�Making Happy Users</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571163">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571398">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573734">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573749">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573929">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580776">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580797">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580892">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581136">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581247">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581381">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582451">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583133">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583169">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583203">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583318">Questions and Answers</a></span></dt></dl></div><p>
 	It is said that &#8220;<span class="quote">a day that is without troubles is not fulfilling.  Rather, give 
 	me a day of troubles well handled so that I can be content with my achievements.</span>&#8221;
 	</p><p>
@@ -6,7 +6,7 @@
 	or experience them. The design of the network implemented in <a class="link" href="Big500users.html" title="Chapter�4.�The 500-User Office">&#8220;The 500-User Office&#8221;</a>
 	may create problems for some network users. The following lists some of the problems that
 	may occur:
-	</p><a class="indexterm" name="id2570600"></a><a class="indexterm" name="id2570606"></a><a class="indexterm" name="id2570616"></a><a class="indexterm" name="id2570622"></a><a class="indexterm" name="id2570629"></a><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>
+	</p><a class="indexterm" name="id2570599"></a><a class="indexterm" name="id2570606"></a><a class="indexterm" name="id2570615"></a><a class="indexterm" name="id2570621"></a><a class="indexterm" name="id2570628"></a><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>
 A significant number of network administrators have responded to the guidance given
 here. It should be noted that there are sites that have a single PDC for many hundreds of
 concurrent network clients. Network bandwidth, network bandwidth utilization, and server load
@@ -20,7 +20,7 @@ overloaded or network bandwidth is overloaded. The guidance given for PDC/BDC ra
 clients is conservative and if followed will minimize problems  but it is not absolute.
 </p></div><div class="variablelist"><dl><dt><span class="term">Users experiencing difficulty logging onto the network</span></dt><dd><p>
 		<a class="indexterm" name="id2570674"></a>
-		<a class="indexterm" name="id2570684"></a>
+		<a class="indexterm" name="id2570683"></a>
 		When a Windows client logs onto the network, many data packets are exchanged
 		between the client and the server that is providing the network logon services.
 		Each request between the client and the server must complete within a specific
@@ -30,9 +30,9 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		30 to 150 clients. The actual limits are determined by network operational
 		characteristics. 
 		</p><p>
-		<a class="indexterm" name="id2570704"></a>
-		<a class="indexterm" name="id2570710"></a>
-		<a class="indexterm" name="id2570717"></a>
+		<a class="indexterm" name="id2570703"></a>
+		<a class="indexterm" name="id2570709"></a>
+		<a class="indexterm" name="id2570716"></a>
 		If the domain controller provides only network logon services
 		and all file and print activity is handled by domain member servers, one domain	
 		controller per 150 clients on a single network segment may suffice. In any
@@ -50,16 +50,16 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		Slow logons and log-offs may be caused by many factors that include:
 
 			</p><div class="itemizedlist"><ul type="disc"><li><p>
-				<a class="indexterm" name="id2570764"></a>
-				<a class="indexterm" name="id2570776"></a>
+				<a class="indexterm" name="id2570763"></a>
+				<a class="indexterm" name="id2570775"></a>
 				Excessive delays in the resolution of a NetBIOS name to its IP
 				address. This may be observed when an overloaded domain controller 
 				is also the WINS server. Another cause may be the failure to use
 				a WINS server (this assumes that there is a single network segment).
 				</p></li><li><p>
-				<a class="indexterm" name="id2570794"></a>
-				<a class="indexterm" name="id2570801"></a>
-				<a class="indexterm" name="id2570808"></a>
+				<a class="indexterm" name="id2570793"></a>
+				<a class="indexterm" name="id2570800"></a>
+				<a class="indexterm" name="id2570807"></a>
 				Network traffic collisions due to overloading of the network
 				segment. One short-term workaround to this may be to replace
 				network HUBs with Ethernet switches.
@@ -72,8 +72,8 @@ clients is conservative and if followed will minimize problems  but it is not ab
 				it was the erratic nature of the problem that ultimately pointed to
 				the cause of the problem.
 				</p></li><li><p>
-				<a class="indexterm" name="id2570843"></a>
-				<a class="indexterm" name="id2570852"></a>
+				<a class="indexterm" name="id2570842"></a>
+				<a class="indexterm" name="id2570851"></a>
 				Excessively large roaming profiles. This type of problem is typically
 				the result of poor user education as well as poor network management.
 				It can be avoided by users not storing huge quantities of email in
@@ -90,7 +90,7 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		Loss of access to network resources during client operation may be caused by a number
 		of factors, including:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-				<a class="indexterm" name="id2570905"></a>
+				<a class="indexterm" name="id2570904"></a>
 				Network overload (typically indicated by a high network collision rate)
 				</p></li><li><p>
 				Server overload
@@ -102,7 +102,7 @@ clients is conservative and if followed will minimize problems  but it is not ab
 				<a class="indexterm" name="id2570940"></a>
 				Defective networking hardware
 				</p></li></ul></div><p>
-		<a class="indexterm" name="id2570955"></a>
+		<a class="indexterm" name="id2570954"></a>
 		No matter what the cause, a sudden loss of access to network resources can
 		result in BSOD (blue screen of death) situations that necessitate rebooting of the client
 		workstation. In the case of a mild problem, retrying to access the network drive of the printer
@@ -123,28 +123,28 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	anticipate and combat network performance issues. You can work through complex and thorny
 	methods to improve the reliability of your network environment, but be warned that all such steps
 	demand the price of complexity.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571022"></a>Regarding LDAP Directories and Windows Computer Accounts</h2></div></div></div><p>
-	<a class="indexterm" name="id2571030"></a>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571021"></a>Regarding LDAP Directories and Windows Computer Accounts</h2></div></div></div><p>
+	<a class="indexterm" name="id2571029"></a>
 	Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some 
 	constraints that are described in this section.
 	</p><p>
-	<a class="indexterm" name="id2571045"></a>
-	<a class="indexterm" name="id2571052"></a>
-	<a class="indexterm" name="id2571059"></a>
-	<a class="indexterm" name="id2571066"></a>
+	<a class="indexterm" name="id2571044"></a>
+	<a class="indexterm" name="id2571051"></a>
+	<a class="indexterm" name="id2571058"></a>
+	<a class="indexterm" name="id2571065"></a>
 	The POSIX and SambaSAMAccount components of computer (machine) accounts are both used by Samba. 
 	That is, machine  accounts are treated inside Samba in the same way that Windows NT4/200X treats 
 	them. A user account and a machine account are indistinguishable from each other, except that
 	the machine account ends in a $ character, as do trust accounts.
 	</p><p>
-	<a class="indexterm" name="id2571082"></a>
-	<a class="indexterm" name="id2571089"></a>
+	<a class="indexterm" name="id2571081"></a>
+	<a class="indexterm" name="id2571088"></a>
 	The need for Windows user, group, machine, trust, and other such accounts to be tied to a valid UNIX UID
 	is a design decision that was made a long way back in the history of Samba development. It is 
 	unlikely that this decision will be reversed or changed during the remaining life of the 
 	Samba-3.x series. 
 	</p><p>
-	<a class="indexterm" name="id2571104"></a>
+	<a class="indexterm" name="id2571103"></a>
 	<a class="indexterm" name="id2571110"></a>
 	The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
 	must refer back to the host operating system on which Samba is running. The name service
@@ -158,13 +158,13 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
 	all account entities can be located in an LDAP directory.
 	</p><p>
-	<a class="indexterm" name="id2571148"></a>
+	<a class="indexterm" name="id2571147"></a>
 	For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
 	be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
 	is fundamentally an LDAP design question.  The information provided on the Samba list and
 	in the documentation is directed at providing working examples only. The design
 	of an LDAP directory is a complex subject that is beyond the scope of this documentation.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571164"></a>Introduction</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571163"></a>Introduction</h2></div></div></div><p>
 	You just opened an email from Christine that reads:
 	</p><p>
 	Good morning,
@@ -193,8 +193,8 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	regain control of our vital IT operations.
 	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Christine</span></td></tr></table></div><p>
 	</p><p>
-	<a class="indexterm" name="id2571226"></a>	
-	<a class="indexterm" name="id2571233"></a>
+	<a class="indexterm" name="id2571225"></a>	
+	<a class="indexterm" name="id2571232"></a>
 	Every compromise has consequences. Having a large routed (i.e., multisegment) network with only a
 	single domain controller is a poor design that has obvious operational effects that may
 	frustrate users. Here is your reply:
@@ -204,13 +204,13 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	boost staff morale. Please go ahead with your plans. If you have any problems, please let me know.
 	Please let Stan know what the estimated cost will be so I can approve the expense. Do not wait
 	for approval; I appreciate the urgency.
-	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Bob</span></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571262"></a>Assignment Tasks</h3></div></div></div><p>
+	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Bob</span></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571261"></a>Assignment Tasks</h3></div></div></div><p>
 		The priority of assigned tasks in this chapter is:
 		</p><div class="orderedlist"><ol type="1"><li><p>
-			<a class="indexterm" name="id2571282"></a>
-			<a class="indexterm" name="id2571291"></a>
+			<a class="indexterm" name="id2571281"></a>
+			<a class="indexterm" name="id2571290"></a>
 			<a class="indexterm" name="id2571297"></a>
-			<a class="indexterm" name="id2571304"></a><a class="indexterm" name="id2571310"></a>
+			<a class="indexterm" name="id2571304"></a><a class="indexterm" name="id2571309"></a>
 			Implement Backup Domain Controllers (BDCs) in each building. This involves
 			a change from a <span class="emphasis"><em>tdbsam</em></span> backend that was used in the previous
 			chapter to an LDAP-based backend.
@@ -218,15 +218,15 @@ clients is conservative and if followed will minimize problems  but it is not ab
 			You can implement a single central LDAP server for this purpose.
 			</p></li><li><p>
 			<a class="indexterm" name="id2571332"></a>
-			<a class="indexterm" name="id2571339"></a>
-			<a class="indexterm" name="id2571346"></a>
-			<a class="indexterm" name="id2571353"></a>
+			<a class="indexterm" name="id2571338"></a>
+			<a class="indexterm" name="id2571345"></a>
+			<a class="indexterm" name="id2571352"></a>
 			Rectify the problem of excessive logon times. This involves redirection of
 			folders to network shares as well as modification of all user desktops to
 			exclude the redirected folders from being loaded at login time. You can also
 			create a new default profile that can be used for all new users.
 			</p></li></ol></div><p>
-		<a class="indexterm" name="id2571372"></a>
+		<a class="indexterm" name="id2571371"></a>
 		You configure a new MS Windows XP Professional workstation disk image that you roll out
 		to all desktop users. The instructions you have created are followed on a staging machine
 		from which all changes can be carefully tested before inflicting them on your network users.
@@ -234,26 +234,26 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		<a class="indexterm" name="id2571386"></a>
 		This is the last network example in which specific mention of printing is made. The example
 		again makes use of the CUPS printing system.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571399"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2571407"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2571398"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2571406"></a>
 	<a class="indexterm" name="id2571413"></a>
 	<a class="indexterm" name="id2571420"></a>
 	The implementation of Samba BDCs necessitates the installation and configuration of LDAP.
 	For this site, you use OpenLDAP, the open source software LDAP server platform. Commercial
 	LDAP servers in current use with Samba-3 include:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2571438"></a>
+		<a class="indexterm" name="id2571437"></a>
 		Novell <a class="ulink" href="http://www.novell.com/products/edirectory/" target="_top">eDirectory</a>
 		is being successfully used by some sites. Information on how to use eDirectory can be
 		obtained from the Samba mailing lists or from Novell.
 		</p></li><li><p>
-		<a class="indexterm" name="id2571458"></a>
+		<a class="indexterm" name="id2571457"></a>
 		IBM <a class="ulink" href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">Tivoli 
 		Directory Server</a> can be used to provide the Samba LDAP backend. Example schema 
 		files are provided in the Samba source code tarball under the directory 
 		<code class="filename">~samba/example/LDAP.</code>
 		</p></li><li><p>
-		<a class="indexterm" name="id2571485"></a>
+		<a class="indexterm" name="id2571484"></a>
 		Sun <a class="ulink" href="http://www.sun.com/software/software/products/identity_srvr/home_identity.xml" target="_top">ONE Identity 
 		Server product suite</a> provides an LDAP server that can be used for Samba.
 		Example schema files are provided in the Samba source code tarball under the directory
@@ -270,13 +270,13 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	GUI-based directory management tools. Even a simple task such as adding users to the OpenLDAP database 
 	requires an understanding of what you are doing, why you are doing it, and the tools that you must use.
 	</p><p>
-	<a class="indexterm" name="id2571540"></a>
-	<a class="indexterm" name="id2571547"></a>
-	<a class="indexterm" name="id2571554"></a>
-	<a class="indexterm" name="id2571563"></a>
-	<a class="indexterm" name="id2571572"></a>
-	<a class="indexterm" name="id2571579"></a>
-	<a class="indexterm" name="id2571588"></a>
+	<a class="indexterm" name="id2571539"></a>
+	<a class="indexterm" name="id2571546"></a>
+	<a class="indexterm" name="id2571553"></a>
+	<a class="indexterm" name="id2571562"></a>
+	<a class="indexterm" name="id2571571"></a>
+	<a class="indexterm" name="id2571578"></a>
+	<a class="indexterm" name="id2571587"></a>
 	When installed and configured, an OpenLDAP Identity Management backend for Samba functions well. 
 	High availability operation may be obtained through directory replication/synchronization and 
 	master/slave server configurations. OpenLDAP is a mature platform to host the organizational 
@@ -286,10 +286,10 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	contents with greater ability to back up, restore, and modify the directory than is generally possible
 	with Microsoft Active Directory.
 	</p><p>
-	<a class="indexterm" name="id2571613"></a>
-	<a class="indexterm" name="id2571623"></a>
-	<a class="indexterm" name="id2571630"></a>
-	<a class="indexterm" name="id2571637"></a>
+	<a class="indexterm" name="id2571612"></a>
+	<a class="indexterm" name="id2571622"></a>
+	<a class="indexterm" name="id2571629"></a>
+	<a class="indexterm" name="id2571636"></a>
 	A comparison of OpenLDAP with Microsoft Active Directory does not do justice to either. OpenLDAP is an LDAP directory
 	tool-set. Microsoft Active Directory Server is an implementation of an LDAP server that is largely preconfigured
 	for a specific task orientation. It comes with a set of administrative tools that is entirely customized
@@ -335,9 +335,9 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	by Jerry Carter quite useful.
 	</p><p>
 	<a class="indexterm" name="id2571791"></a>
-	<a class="indexterm" name="id2571798"></a>
-	<a class="indexterm" name="id2571807"></a>
-	<a class="indexterm" name="id2571814"></a>
+	<a class="indexterm" name="id2571797"></a>
+	<a class="indexterm" name="id2571806"></a>
+	<a class="indexterm" name="id2571813"></a>
 	Mary's problems are due to two factors. First, the absence of a domain controller on the local network is the
 	main cause of the errors that result in blue screen crashes. Second, Mary has a large profile that must
 	be loaded over the WAN connection. The addition of BDCs on each network segment significantly
@@ -353,7 +353,7 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	in the default desktop profile. Only one example of printing configuration is given. It is assumed that
 	you can extrapolate the principles and use them to install all printers that may be needed.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571856"></a>Technical Issues</h3></div></div></div><p>
-	<a class="indexterm" name="id2571864"></a>
+	<a class="indexterm" name="id2571863"></a>
 	<a class="indexterm" name="id2571873"></a>
 	<a class="indexterm" name="id2571882"></a>
 	The solution provided is a minimal approach to getting OpenLDAP running as an identity management directory
@@ -361,15 +361,15 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	accounts are stored POSIX schema extensions. Samba provides its own schema to permit storage of account 
 	attributes Samba needs. Samba-3 can use the LDAP backend to store:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Windows Networking User Accounts</p></li><li><p>Windows NT Group Accounts</p></li><li><p>Mapping Information between UNIX Groups and Windows NT Groups</p></li><li><p>ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)</p></li></ul></div><p>
-	<a class="indexterm" name="id2571923"></a>
-	<a class="indexterm" name="id2571930"></a>
-	<a class="indexterm" name="id2571937"></a>
-	<a class="indexterm" name="id2571944"></a>
-	<a class="indexterm" name="id2571951"></a>
-	<a class="indexterm" name="id2571958"></a>
-	<a class="indexterm" name="id2571967"></a>
-	<a class="indexterm" name="id2571973"></a>
-	<a class="indexterm" name="id2571980"></a>
+	<a class="indexterm" name="id2571922"></a>
+	<a class="indexterm" name="id2571929"></a>
+	<a class="indexterm" name="id2571936"></a>
+	<a class="indexterm" name="id2571943"></a>
+	<a class="indexterm" name="id2571950"></a>
+	<a class="indexterm" name="id2571957"></a>
+	<a class="indexterm" name="id2571966"></a>
+	<a class="indexterm" name="id2571972"></a>
+	<a class="indexterm" name="id2571979"></a>
 	The use of LDAP with Samba-3 makes it necessary to store UNIX accounts as well as Windows Networking
 	accounts in the LDAP backend. This implies the need to use the 
 	<a class="ulink" href="http://www.padl.com/Contents/OpenSourceSoftware.html" target="_top">PADL LDAP tools</a>. The resolution 
@@ -384,10 +384,10 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	ought to learn how to configure secure communications over LDAP so that site security is not
 	at risk. This is not covered in the following guidance.
 	</p><p>
-	<a class="indexterm" name="id2572089"></a>
+	<a class="indexterm" name="id2572088"></a>
 	<a class="indexterm" name="id2572095"></a>
-	<a class="indexterm" name="id2572105"></a>
-	<a class="indexterm" name="id2572112"></a>
+	<a class="indexterm" name="id2572104"></a>
+	<a class="indexterm" name="id2572111"></a>
 	When OpenLDAP has been made operative, you configure the PDC called <code class="constant">MASSIVE</code>.
 	You initialize the Samba <code class="filename">secrets.tdb<sub></sub></code> file. Then you
 	create the LDAP Interchange Format (LDIF) file from which the LDAP database can be initialized.
@@ -395,27 +395,27 @@ clients is conservative and if followed will minimize problems  but it is not ab
 	You can also find on the enclosed CD-ROM, in the <code class="filename">Chap06</code> directory, a few tools
 	that help to manage user and group configuration.
 	</p><p>
-	<a class="indexterm" name="id2572146"></a>
+	<a class="indexterm" name="id2572145"></a>
 	<a class="indexterm" name="id2572152"></a>
-	<a class="indexterm" name="id2572159"></a>
+	<a class="indexterm" name="id2572158"></a>
 	In order to effect folder redirection and to add robustness to the implementation,
 	create a network default profile. All network users workstations are configured to use
 	the new profile. Roaming profiles will automatically be deleted from the workstation
 	when the user logs off.
 	</p><p>
-	<a class="indexterm" name="id2572174"></a>
+	<a class="indexterm" name="id2572178"></a>
 	The profile is configured so that users cannot change the appearance
 	of their desktop. This is known as a mandatory profile. You make certain that users
 	are able to use their computers efficiently.
 	</p><p>
-	<a class="indexterm" name="id2572188"></a>
+	<a class="indexterm" name="id2572192"></a>
 	A network logon script is used to deliver flexible but consistent network drive
 	connections.
 	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sbehap-ppc"></a>Addition of Machines to the Domain</h4></div></div></div><p>
-		<a class="indexterm" name="id2572209"></a>
-		<a class="indexterm" name="id2572215"></a>
-		<a class="indexterm" name="id2572220"></a>
-		<a class="indexterm" name="id2572226"></a>
+		<a class="indexterm" name="id2572213"></a>
+		<a class="indexterm" name="id2572219"></a>
+		<a class="indexterm" name="id2572224"></a>
+		<a class="indexterm" name="id2572230"></a>
 		Samba versions prior to 3.0.11 necessitated the use of a domain administrator account
 		that maps to the UNIX UID=0. The UNIX operating system permits only the <code class="constant">root</code>
 		user to add user and group accounts. Samba 3.0.11 introduced a new facility known as
@@ -425,13 +425,13 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		In this network example use is made of one of the supported privileges purely to demonstrate
 		how any user can now be given the ability to add machines to the domain using a normal user account
 		that has been given the appropriate privileges.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572363"></a>Roaming Profile Background</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572367"></a>Roaming Profile Background</h4></div></div></div><p>
 		As XP roaming profiles grow, so does the amount of time it takes to log in and out.
 		</p><p>
-		<a class="indexterm" name="id2572376"></a>
-		<a class="indexterm" name="id2572383"></a>
-		<a class="indexterm" name="id2572390"></a>
-		<a class="indexterm" name="id2572397"></a>
+		<a class="indexterm" name="id2572380"></a>
+		<a class="indexterm" name="id2572387"></a>
+		<a class="indexterm" name="id2572394"></a>
+		<a class="indexterm" name="id2572401"></a>
 		An XP roaming profile consists of the <code class="constant">HKEY_CURRENT_USER</code> hive file
 		<code class="filename">NTUSER.DAT</code> and a number of folders (My Documents, Application Data,
 		Desktop, Start Menu, Templates, NetHood, Favorites, and so on).  When a user logs onto the 
@@ -453,20 +453,20 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		user to not place large files on the desktop and to use his or her mapped home directory
 		instead of the <code class="filename">My Documents</code> folder for saving documents.
 		</p><p>
-		<a class="indexterm" name="id2572476"></a>
+		<a class="indexterm" name="id2572480"></a>
 		Using a folder other than <code class="filename">My Documents</code> is a nuisance for 
 		some users, since many applications use it by default.
 		</p><p>
-		<a class="indexterm" name="id2572494"></a>
-		<a class="indexterm" name="id2572501"></a>
-		<a class="indexterm" name="id2572508"></a>
+		<a class="indexterm" name="id2572498"></a>
+		<a class="indexterm" name="id2572505"></a>
+		<a class="indexterm" name="id2572512"></a>
 		The secret to rapid loading of roaming profiles is to prevent unnecessary data from 
 		being copied back and forth, without losing any functionality. This is not difficult; 
 		it can be done by making changes to the Local Group Policy on each client as well 
 		as changing some paths in each user's <code class="filename">NTUSER.DAT</code> hive.
 		</p><p>
-		<a class="indexterm" name="id2572529"></a>
-		<a class="indexterm" name="id2572536"></a>
+		<a class="indexterm" name="id2572533"></a>
+		<a class="indexterm" name="id2572540"></a>
 		Every user profile has its own <code class="filename">NTUSER.DAT</code> file. This means
 		you need to edit every user's profile, unless a better method can be
 		followed. Fortunately, with the right preparations, this is not difficult.
@@ -475,10 +475,10 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		necessary to copy all files from redirected folders to the network share to which
 		they are redirected.
 		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sbehap-locgrppol"></a>The Local Group Policy</h4></div></div></div><p>
-		<a class="indexterm" name="id2572576"></a>
-		<a class="indexterm" name="id2572583"></a>
-		<a class="indexterm" name="id2572590"></a>
-		<a class="indexterm" name="id2572596"></a>
+		<a class="indexterm" name="id2572580"></a>
+		<a class="indexterm" name="id2572587"></a>
+		<a class="indexterm" name="id2572594"></a>
+		<a class="indexterm" name="id2572600"></a>
 		Without an Active Directory PDC, you cannot take full advantage of Group Policy 
 		Objects. However, you can still make changes to the Local Group Policy by using 
 		the Group Policy editor (<code class="literal">gpedit.msc</code>).
@@ -492,26 +492,26 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		Simply add the folders you do not wish to be copied back and forth to this 
 		semicolon-separated list. Note that this change must be made on all clients 
 		that are using roaming profiles.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572664"></a>Profile Changes</h4></div></div></div><p>
-		<a class="indexterm" name="id2572672"></a>
-		<a class="indexterm" name="id2572678"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572668"></a>Profile Changes</h4></div></div></div><p>
+		<a class="indexterm" name="id2572676"></a>
+		<a class="indexterm" name="id2572682"></a>
 		There are two changes that should be done to each user's profile. Move each of 
 		the directories that you have excluded from being copied back and forth out of 
 		the usual profile path. Modify each user's <code class="filename">NTUSER.DAT</code> file 
 		to point to the new paths that are shared over the network instead of to the default
 		path (<code class="filename">C:\Documents and Settings\%USERNAME%</code>).
 		</p><p>
-		<a class="indexterm" name="id2572706"></a>
-		<a class="indexterm" name="id2572713"></a>
+		<a class="indexterm" name="id2572710"></a>
+		<a class="indexterm" name="id2572717"></a>
 		The above modifies existing user profiles. So that newly created profiles have 
 		these settings, you need to modify the <code class="filename">NTUSER.DAT</code> in 
 		the <code class="filename">C:\Documents and Settings\Default User</code> folder on each 
 		client machine, changing the same registry keys.  You could do this by copying 
 		<code class="filename">NTUSER.DAT</code> to a Linux box and using <code class="literal">regedt32</code>.
 		The basic method is described under <a class="link" href="happy.html#redirfold" title="Configuration of Default Profile with Folder Redirection">&#8220;Configuration of Default Profile with Folder Redirection&#8221;</a>.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572758"></a>Using a Network Default User Profile</h4></div></div></div><p>
-		<a class="indexterm" name="id2572766"></a>
-		<a class="indexterm" name="id2572773"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572762"></a>Using a Network Default User Profile</h4></div></div></div><p>
+		<a class="indexterm" name="id2572770"></a>
+		<a class="indexterm" name="id2572777"></a>
 		If you are using Samba as your PDC, you should create a file share called 
 		<code class="constant">NETLOGON</code> and within that create a directory called 
 		<code class="filename">Default User</code>, which is a copy of the desired default user 
@@ -520,10 +520,10 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		the first login from a new account pulls its configuration from it.
 		See also <a class="ulink" href="http://isg.ee.ethz.ch/tools/realmen/det/skel.en.html" target="_top">
 		the Real Men Don't Click</a> Web site.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572816"></a>Installation of Printer Driver Auto-Download</h4></div></div></div><p>
-		<a class="indexterm" name="id2572825"></a>
-		<a class="indexterm" name="id2572834"></a>
-		<a class="indexterm" name="id2572841"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2572820"></a>Installation of Printer Driver Auto-Download</h4></div></div></div><p>
+		<a class="indexterm" name="id2572829"></a>
+		<a class="indexterm" name="id2572838"></a>
+		<a class="indexterm" name="id2572845"></a>
 		The subject of printing is quite topical. Printing problems run second place to name
 		resolution issues today. So far in this book, you have experienced only what is generally
 		known as &#8220;<span class="quote">dumb</span>&#8221; printing. Dumb printing is the arrangement by which all drivers
@@ -532,8 +532,8 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		many problems, but it has its limitations also. Dumb printing is better known as
 		<code class="literal">Raw-Print-Through</code> printing.
 		</p><p>
-		<a class="indexterm" name="id2572870"></a>
-		<a class="indexterm" name="id2572879"></a>
+		<a class="indexterm" name="id2572874"></a>
+		<a class="indexterm" name="id2572883"></a>
 		Samba permits the configuration of <code class="literal">smart</code> printing using the Microsoft
 		Windows point-and-click (also called drag-and-drop) printing. What this provides is
 		essentially the ability to print to any printer. If the local client does not yet have a
@@ -547,9 +547,9 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		then invokes a suitable print filter to convert the incoming data stream into a format
 		suited to the printer to which the job is dispatched.
 		</p><p>
-		<a class="indexterm" name="id2572926"></a>
-		<a class="indexterm" name="id2572933"></a>
-		<a class="indexterm" name="id2572940"></a>
+		<a class="indexterm" name="id2572930"></a>
+		<a class="indexterm" name="id2572937"></a>
+		<a class="indexterm" name="id2572944"></a>
 		The CUPS printing subsystem is capable of intelligent printing. It has the capacity to
 		detect the data format and apply a print filter. This means that it is feasible to install
 		on all Windows clients a single printer driver for use with all printers that are routed
@@ -574,10 +574,10 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		simple problems efficiently and effectively.
 		</p><p>
 		Here are some diagnostic guidelines that can be referred to when things go wrong:
-		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573007"></a>Preliminary Advice: Dangers Can Be Avoided</h5></div></div></div><p>
+		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573011"></a>Preliminary Advice: Dangers Can Be Avoided</h5></div></div></div><p>
 		The best advice regarding how to mend a broken leg is &#8220;<span class="quote">Never break a leg!</span>&#8221;
 		</p><p>
-		<a class="indexterm" name="id2573023"></a>
+		<a class="indexterm" name="id2573027"></a>
 		Newcomers to Samba and LDAP seem to struggle a great deal at first.  If you want advice
 		regarding the best way to remedy LDAP and Samba problems: &#8220;<span class="quote">Avoid them like the plague!</span>&#8221;
 		</p><p>
@@ -593,7 +593,7 @@ clients is conservative and if followed will minimize problems  but it is not ab
 		Do not be lulled into thinking that you can easily adopt the examples in this
 		book and adapt them without first working through the examples provided. A little
 		thing overlooked can cause untold pain and may permanently tarnish your experience.
-		</p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573067"></a>The Name Service Caching Daemon</h5></div></div></div><p>
+		</p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573071"></a>The Name Service Caching Daemon</h5></div></div></div><p>
 		The name service caching daemon (nscd) is a primary cause of difficulties with name
 		resolution, particularly where <code class="literal">winbind</code> is used. Winbind does its
 		own caching, thus nscd causes double caching which can lead to peculiar problems during
@@ -660,17 +660,17 @@ clients is conservative and if followed will minimize problems  but it is not ab
 <code class="prompt">root# </code> chkconfig nscd off
 <code class="prompt">root# </code> rcnscd off
 </pre><p>
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573240"></a>Debugging LDAP</h5></div></div></div><p>
-		<a class="indexterm" name="id2573248"></a>
-		<a class="indexterm" name="id2573255"></a>
-		<a class="indexterm" name="id2573262"></a>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573244"></a>Debugging LDAP</h5></div></div></div><p>
+		<a class="indexterm" name="id2573252"></a>
+		<a class="indexterm" name="id2573259"></a>
+		<a class="indexterm" name="id2573266"></a>
 		In the example <code class="filename">/etc/openldap/slapd.conf</code> control file
 		(see <a class="link" href="happy.html#sbehap-dbconf" title="Example�5.1.�LDAP DB_CONFIG File">&#8220;LDAP DB_CONFIG File&#8221;</a>) there is an entry for <code class="constant">loglevel	256</code>.
 		To enable logging via the syslog infrastructure, it is necessary to uncomment this parameter
 		and restart <code class="literal">slapd</code>.
 		</p><p>
-		<a class="indexterm" name="id2573298"></a>
-		<a class="indexterm" name="id2573305"></a>
+		<a class="indexterm" name="id2573302"></a>
+		<a class="indexterm" name="id2573309"></a>
 		LDAP log information can be directed into a file that is separate from the normal system
 		log files by changing the <code class="filename">/etc/syslog.conf</code> file so it has the following
 		contents:
@@ -689,7 +689,7 @@ local4.*                        -/var/log/ldaplogs
 		local site needs. The configuration used later in this chapter reflects such
 		customization with the intent that LDAP log files will be stored at a location
 		that meets local site needs and wishes more fully.
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573347"></a>Debugging NSS_LDAP</h5></div></div></div><p>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573351"></a>Debugging NSS_LDAP</h5></div></div></div><p>
 		The basic mechanism for diagnosing problems with the nss_ldap utility involves adding to the
 		<code class="filename">/etc/ldap.conf</code> file the following parameters:
 </p><pre class="screen">
@@ -702,7 +702,7 @@ logdir /data/logs
 </pre><p>
 		</p><p>
 		The diagnostic process should follow these steps:
-		</p><div class="procedure"><a name="id2573390"></a><p class="title"><b>Procedure�5.1.�NSS_LDAP Diagnostic Steps</b></p><ol type="1"><li><p>
+		</p><div class="procedure"><a name="id2573394"></a><p class="title"><b>Procedure�5.1.�NSS_LDAP Diagnostic Steps</b></p><ol type="1"><li><p>
 			Verify the <code class="constant">nss_base_passwd, nss_base_shadow, nss_base_group</code> entries
 			in the <code class="filename">/etc/ldap.conf</code> file and compare them closely with the directory
 			tree location that was chosen when the directory was first created.
@@ -792,7 +792,7 @@ slapd[12164]: conn=1 fd=10 closed
 			Check that the bindpw entry in the <code class="filename">/etc/ldap.conf</code> or in the
 			<code class="filename">/etc/ldap.secrets</code> file is correct, as specified in the
 			<code class="filename">/etc/openldap/slapd.conf</code> file.
-			</p></li></ol></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573641"></a>Debugging Samba</h5></div></div></div><p>
+			</p></li></ol></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573645"></a>Debugging Samba</h5></div></div></div><p>
 		The following parameters in the <code class="filename">smb.conf</code> file can be useful in tracking down Samba-related problems:
 </p><pre class="screen">
 [global]
@@ -822,17 +822,17 @@ slapd[12164]: conn=1 fd=10 closed
 		</p><p>
 		Search for hints of what may have failed by looking for the words <span class="emphasis"><em>fail</em></span>
 		and <span class="emphasis"><em>error</em></span>.
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573712"></a>Debugging on the Windows Client</h5></div></div></div><p>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2573716"></a>Debugging on the Windows Client</h5></div></div></div><p>
 		MS Windows 2000 Professional and Windows  XP Professional clients can be configured
 		to create a netlogon.log file that can be very helpful in diagnosing network logon problems. Search
 		the Microsoft knowledge base for detailed instructions. The techniques vary a little with each
 		version of MS Windows.
-		</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573730"></a>Political Issues</h3></div></div></div><p>
+		</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573734"></a>Political Issues</h3></div></div></div><p>
 		MS Windows network users are generally very sensitive to limits that may be imposed when 
 		confronted with locked-down workstation configurations. The challenge you face must 
 		be promoted as a choice between reliable, fast network operation and a constant flux 	
 		of problems that result in user irritation.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573745"></a>Installation Checklist</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573749"></a>Installation Checklist</h3></div></div></div><p>
 	You are starting a complex project. Even though you went through the installation of a complex
 	network in <a class="link" href="Big500users.html" title="Chapter�4.�The 500-User Office">&#8220;The 500-User Office&#8221;</a>, this network is a bigger challenge because of the
 	large number of complex applications that must be configured before the first few steps
@@ -840,14 +840,14 @@ slapd[12164]: conn=1 fd=10 closed
 	frequently review the steps ahead while making at least a mental note of what has already
 	been completed. The following task list may help you to keep track of the task items
 	that are covered:
-	</p><div class="itemizedlist"><ul type="disc"><li><p>Samba-3 PDC Server Configuration</p><div class="orderedlist"><ol type="1"><li><p>DHCP and DNS servers</p></li><li><p>OpenLDAP server</p></li><li><p>PAM and NSS client tools</p></li><li><p>Samba-3 PDC</p></li><li><p>Idealx smbldap scripts</p></li><li><p>LDAP initialization</p></li><li><p>Create user and group accounts</p></li><li><p>Printers</p></li><li><p>Share point directory roots</p></li><li><p>Profile directories</p></li><li><p>Logon scripts</p></li><li><p>Configuration of user rights and privileges</p></li></ol></div></li><li><p>Samba-3 BDC Server Configuration</p><div class="orderedlist"><ol type="1"><li><p>DHCP and DNS servers</p></li><li><p>PAM and NSS client tools</p></li><li><p>Printers</p></li><li><p>Share point directory roots</p></li><li><p>Profiles directories</p></li></ol></div></li><li><p>Windows XP Client Configuration</p><div class="orderedlist"><ol type="1"><li><p>Default profile folder redirection</p></li><li><p>MS Outlook PST file relocation</p></li><li><p>Delete roaming profile on logout</p></li><li><p>Upload printer drivers to Samba servers</p></li><li><p>Install software</p></li><li><p>Creation of roll-out images</p></li></ol></div></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573925"></a>Samba Server Implementation</h2></div></div></div><p>
-	<a class="indexterm" name="id2573933"></a>
-	<a class="indexterm" name="id2573940"></a>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>Samba-3 PDC Server Configuration</p><div class="orderedlist"><ol type="1"><li><p>DHCP and DNS servers</p></li><li><p>OpenLDAP server</p></li><li><p>PAM and NSS client tools</p></li><li><p>Samba-3 PDC</p></li><li><p>Idealx smbldap scripts</p></li><li><p>LDAP initialization</p></li><li><p>Create user and group accounts</p></li><li><p>Printers</p></li><li><p>Share point directory roots</p></li><li><p>Profile directories</p></li><li><p>Logon scripts</p></li><li><p>Configuration of user rights and privileges</p></li></ol></div></li><li><p>Samba-3 BDC Server Configuration</p><div class="orderedlist"><ol type="1"><li><p>DHCP and DNS servers</p></li><li><p>PAM and NSS client tools</p></li><li><p>Printers</p></li><li><p>Share point directory roots</p></li><li><p>Profiles directories</p></li></ol></div></li><li><p>Windows XP Client Configuration</p><div class="orderedlist"><ol type="1"><li><p>Default profile folder redirection</p></li><li><p>MS Outlook PST file relocation</p></li><li><p>Delete roaming profile on logout</p></li><li><p>Upload printer drivers to Samba servers</p></li><li><p>Install software</p></li><li><p>Creation of roll-out images</p></li></ol></div></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573929"></a>Samba Server Implementation</h2></div></div></div><p>
+	<a class="indexterm" name="id2573937"></a>
+	<a class="indexterm" name="id2573944"></a>
 	The network design shown in <a class="link" href="happy.html#chap6net" title="Figure�5.2.�Network Topology 500 User Network Using ldapsam passdb backend">&#8220;Network Topology  500 User Network Using ldapsam passdb backend&#8221;</a> is not comprehensive. It is assumed
 	that you will install additional file servers and possibly additional BDCs.
 	</p><div class="figure"><a name="chap6net"></a><p class="title"><b>Figure�5.2.�Network Topology  500 User Network Using ldapsam passdb backend</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap6-net.png" width="270" alt="Network Topology 500 User Network Using ldapsam passdb backend"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2574003"></a>
-	<a class="indexterm" name="id2574010"></a>
+	<a class="indexterm" name="id2574007"></a>
+	<a class="indexterm" name="id2574014"></a>
 	All configuration files and locations are shown for SUSE Linux 9.2 and are equally valid for SUSE
 	Linux Enterprise Server 9. The file locations for Red Hat Linux are similar. You may need to
 	adjust the locations for your particular Linux system distribution/implementation.
@@ -868,22 +868,22 @@ They could just as well be located under the rdn <code class="constant">cn=NextF
 	with newly installed Linux servers, you must complete the steps shown in
 	<a class="link" href="Big500users.html#ch5-dnshcp-setup" title="Installation of DHCP, DNS, and Samba Control Files">&#8220;Installation of DHCP, DNS, and Samba Control Files&#8221;</a> before commencing at <a class="link" href="happy.html#ldapsetup" title="OpenLDAP Server Configuration">&#8220;OpenLDAP Server Configuration&#8221;</a>.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ldapsetup"></a>OpenLDAP Server Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2574092"></a>
-	<a class="indexterm" name="id2574098"></a>
-	<a class="indexterm" name="id2574105"></a>
+	<a class="indexterm" name="id2574096"></a>
+	<a class="indexterm" name="id2574102"></a>
+	<a class="indexterm" name="id2574109"></a>
 	Confirm that the packages shown in <a class="link" href="happy.html#oldapreq" title="Table�5.2.�Required OpenLDAP Linux Packages">&#8220;Required OpenLDAP Linux Packages&#8221;</a> are installed on your system.
 	</p><div class="table"><a name="oldapreq"></a><p class="title"><b>Table�5.2.�Required OpenLDAP Linux Packages</b></p><div class="table-contents"><table summary="Required OpenLDAP Linux Packages" border="1"><colgroup><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="center">SUSE Linux 8.x</th><th align="center">SUSE Linux 9.x</th><th align="center">Red Hat Linux</th></tr></thead><tbody><tr><td align="left">nss_ldap</td><td align="left">nss_ldap</td><td align="left">nss_ldap</td></tr><tr><td align="left">pam_ldap</td><td align="left">pam_ldap</td><td align="left">pam_ldap</td></tr><tr><td align="left">openldap2</td><td align="left">openldap2</td><td align="left">openldap</td></tr><tr><td align="left">openldap2-client</td><td align="left">openldap2-client</td><td align="left">�</td></tr></tbody></table></div></div><br class="table-break"><p>
 	Samba-3 and OpenLDAP will have a degree of interdependence that is unavoidable. The method
 	for bootstrapping the LDAP and Samba-3 configuration is relatively straightforward. If you
 	follow these guidelines, the resulting system should work fine.
-	</p><div class="procedure"><a name="id2574237"></a><p class="title"><b>Procedure�5.2.�OpenLDAP Server Configuration Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2574249"></a>
+	</p><div class="procedure"><a name="id2574241"></a><p class="title"><b>Procedure�5.2.�OpenLDAP Server Configuration Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2574253"></a>
 		Install the file shown in <a class="link" href="happy.html#sbehap-slapdconf" title="Example�5.2.�LDAP Master Configuration File /etc/openldap/slapd.conf Part A">&#8220;LDAP Master Configuration File  /etc/openldap/slapd.conf Part A&#8221;</a> in the directory
 		<code class="filename">/etc/openldap</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2574277"></a>
-		<a class="indexterm" name="id2574283"></a>
-		<a class="indexterm" name="id2574290"></a>
+		<a class="indexterm" name="id2574281"></a>
+		<a class="indexterm" name="id2574287"></a>
+		<a class="indexterm" name="id2574294"></a>
 		Remove all files from the directory <code class="filename">/data/ldap</code>, making certain that
 		the directory exists with permissions:
 </p><pre class="screen">
@@ -892,14 +892,14 @@ drwx------   2 ldap    ldap       48 Dec 15 22:11 ldap
 </pre><p>
 		This may require you to add a user and a group account for LDAP if they do not exist.
 		</p></li><li><p>
-		<a class="indexterm" name="id2574326"></a>
+		<a class="indexterm" name="id2574330"></a>
 		Install the file shown in <a class="link" href="happy.html#sbehap-dbconf" title="Example�5.1.�LDAP DB_CONFIG File">&#8220;LDAP DB_CONFIG File&#8221;</a> in the directory
 		<code class="filename">/data/ldap</code>. In the event that this file is added after <code class="constant">ldap</code>
 		has been started, it is possible to cause the new settings to take effect by shutting down
 		the <code class="constant">LDAP</code> server, executing the <code class="literal">db_recover</code> command inside the
 		<code class="filename">/data/ldap</code> directory, and then restarting the <code class="constant">LDAP</code> server.
 		</p></li><li><p>
-		<a class="indexterm" name="id2574379"></a>
+		<a class="indexterm" name="id2574383"></a>
 		Performance logging can be enabled and should preferably be sent to a file on
 		a file system that is large enough to handle significantly sized logs. To enable
 		the logging at a verbose level to permit detailed analysis, uncomment the entry in
@@ -975,31 +975,31 @@ index sambaPrimaryGroupSID  eq
 index sambaDomainName       eq
 index default               sub
 </pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbehap-PAM-NSS"></a>PAM and NSS Client Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2574531"></a>
-	<a class="indexterm" name="id2574537"></a>
-	<a class="indexterm" name="id2574544"></a>
+	<a class="indexterm" name="id2574542"></a>
+	<a class="indexterm" name="id2574549"></a>
+	<a class="indexterm" name="id2574555"></a>
 	The steps that follow involve configuration of LDAP, NSS LDAP-based resolution of users and
 	groups. Also, so that LDAP-based accounts can log onto the system, the steps ahead configure
 	the Pluggable Authentication Modules (PAM) to permit LDAP-based authentication.
 	</p><p>
-	<a class="indexterm" name="id2574558"></a>
-	<a class="indexterm" name="id2574568"></a>
+	<a class="indexterm" name="id2574570"></a>
+	<a class="indexterm" name="id2574579"></a>
 	Since you have chosen to put UNIX user and group accounts into the LDAP database, it is likely
 	that you may want to use them for UNIX system (Linux) local machine logons. This necessitates
 	correct configuration of PAM. The <code class="literal">pam_ldap</code> open source package provides the
 	PAM modules that most people would use. On SUSE Linux systems, the <code class="literal">pam_unix2.so</code>
 	module also has the ability to redirect authentication requests through LDAP.
 	</p><p>
-	<a class="indexterm" name="id2574596"></a>
-	<a class="indexterm" name="id2574603"></a>
-	<a class="indexterm" name="id2574610"></a>
-	<a class="indexterm" name="id2574617"></a>
+	<a class="indexterm" name="id2574607"></a>
+	<a class="indexterm" name="id2574614"></a>
+	<a class="indexterm" name="id2574621"></a>
+	<a class="indexterm" name="id2574628"></a>
 	You have chosen to configure these services by directly editing the system files, but of course, you
 	know that this configuration can be done using system tools provided by the Linux system vendor.
 	SUSE Linux has a facility in YaST (the system admin tool) through <span class="guimenu">yast</span> &#8594; <span class="guimenuitem">system</span> &#8594; <span class="guimenuitem">ldap-client</span> that permits
 	configuration of SUSE Linux as an LDAP client. Red Hat Linux provides the <code class="literal">authconfig</code>
 	tool for this.
-	</p><div class="procedure"><a name="id2574656"></a><p class="title"><b>Procedure�5.3.�PAM and NSS Client Configuration Steps</b></p><div class="example"><a name="sbehap-nss01"></a><p class="title"><b>Example�5.4.�Configuration File for NSS LDAP Support  <code class="filename">/etc/ldap.conf</code></b></p><div class="example-contents"><pre class="screen">
+	</p><div class="procedure"><a name="id2574668"></a><p class="title"><b>Procedure�5.3.�PAM and NSS Client Configuration Steps</b></p><div class="example"><a name="sbehap-nss01"></a><p class="title"><b>Example�5.4.�Configuration File for NSS LDAP Support  <code class="filename">/etc/ldap.conf</code></b></p><div class="example-contents"><pre class="screen">
 host 127.0.0.1
 
 base dc=abmas,dc=biz
@@ -1042,9 +1042,9 @@ nss_base_group  ou=Groups,dc=abmas,dc=biz?one
 
 ssl off
 </pre></div></div><br class="example-break"><ol type="1"><li><p>
-		<a class="indexterm" name="id2574668"></a>
-		<a class="indexterm" name="id2574675"></a>
-		<a class="indexterm" name="id2574682"></a>
+		<a class="indexterm" name="id2574679"></a>
+		<a class="indexterm" name="id2574686"></a>
+		<a class="indexterm" name="id2574693"></a>
 		Execute the following command to find where the <code class="filename">nss_ldap</code> module
 		expects to find its control file:
 </p><pre class="screen">
@@ -1057,7 +1057,7 @@ ssl off
 		On the servers called <code class="constant">BLDG1</code> and <code class="constant">BLDG2</code>, install the file shown in
 		<a class="link" href="happy.html#sbehap-nss02" title="Example�5.5.�Configuration File for NSS LDAP Clients Support /etc/ldap.conf">&#8220;Configuration File for NSS LDAP Clients Support  /etc/ldap.conf&#8221;</a> into the path that was obtained from the step above.
 		</p></li><li><p>
-		<a class="indexterm" name="id2574821"></a>
+		<a class="indexterm" name="id2574827"></a>
 		Edit the NSS control file (<code class="filename">/etc/nsswitch.conf</code>) so that the lines that
 		control user and group resolution will obtain information from the normal system files as
 		well as from <code class="literal">ldap</code>:
@@ -1080,7 +1080,7 @@ hosts:  files dns wins
 		Even at the risk of overstating the issue, incorrect and inappropriate configuration of the
 		<code class="filename">nsswitch.conf</code> file is a significant cause of operational problems with LDAP.
 		</p></li><li><p>
-		<a class="indexterm" name="id2574897"></a>
+		<a class="indexterm" name="id2574902"></a>
 		For PAM LDAP configuration on this SUSE Linux 9.0 system, the simplest solution is to edit the following
 		files in the <code class="filename">/etc/pam.d</code> directory: <code class="literal">login</code>, <code class="literal">password</code>,
 		<code class="literal">samba</code>, <code class="literal">sshd</code>.  In each file, locate every entry that has the
@@ -1102,7 +1102,7 @@ session   required   pam_unix2.so   none use_ldap # debug or trace
 session   required   pam_limits.so
 </pre><p>
 		</p><p>
-		<a class="indexterm" name="id2574976"></a>
+		<a class="indexterm" name="id2574982"></a>
 		On other Linux systems that do not have an LDAP-enabled <code class="literal">pam_unix2.so</code> module,
 		you must edit these files by adding the <code class="literal">pam_ldap.so</code> modules as shown here:
 </p><pre class="screen">
@@ -1126,14 +1126,14 @@ session  optional    pam_mail.so
 		implementation, but if the <code class="literal">pam_unix2.so</code> on your system supports
 		LDAP, you probably want to use it rather than add an additional module.
 		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbehap-massive"></a>Samba-3 PDC Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2575059"></a>
+	<a class="indexterm" name="id2575065"></a>
 	Verify that the Samba-3.0.20 (or later) packages are installed on each SUSE Linux server 
 	before following the steps below. If Samba-3.0.20 (or later) is not installed, you have the
 	choice to either build your own or obtain the packages from a dependable source.
 	Packages for SUSE Linux 8.x, 9.x, and SUSE Linux Enterprise Server 9, as well as for 
 	Red Hat Fedora Core and Red Hat Enterprise Linux Server 3 and 4, are included on the CD-ROM that
 	is included with this book.
-	</p><div class="procedure"><a name="id2575075"></a><p class="title"><b>Procedure�5.4.�Configuration of PDC Called <code class="constant">MASSIVE</code></b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2575080"></a><p class="title"><b>Procedure�5.4.�Configuration of PDC Called <code class="constant">MASSIVE</code></b></p><ol type="1"><li><p>
 		Install the files in <a class="link" href="happy.html#sbehap-massive-smbconfa" title="Example�5.6.�LDAP Based smb.conf File, Server: MASSIVE global Section: Part A">&#8220;LDAP Based smb.conf File, Server: MASSIVE  global Section: Part A&#8221;</a>, 
 		<a class="link" href="happy.html#sbehap-massive-smbconfb" title="Example�5.7.�LDAP Based smb.conf File, Server: MASSIVE global Section: Part B">&#8220;LDAP Based smb.conf File, Server: MASSIVE  global Section: Part B&#8221;</a>, <a class="link" href="happy.html#sbehap-shareconfa" title="Example�5.10.�LDAP Based smb.conf File, Shares Section Part A">&#8220;LDAP Based smb.conf File, Shares Section  Part A&#8221;</a>, 
 		and <a class="link" href="happy.html#sbehap-shareconfb" title="Example�5.11.�LDAP Based smb.conf File, Shares Section Part B">&#8220;LDAP Based smb.conf File, Shares Section  Part B&#8221;</a> into the <code class="filename">/etc/samba/</code> 
@@ -1143,7 +1143,7 @@ session  optional    pam_mail.so
 		on the master file. The operational <code class="filename">smb.conf</code> is then generated as shown in
 		the next step.
 		</p></li><li><p>
-		<a class="indexterm" name="id2575151"></a>
+		<a class="indexterm" name="id2575157"></a>
 		Create and verify the contents of the <code class="filename">smb.conf</code> file that is generated by:
 </p><pre class="screen">
 <code class="prompt">root# </code> testparm -s smb.conf.master &gt; smb.conf
@@ -1180,8 +1180,8 @@ Press enter to see a dump of your service definitions
 <code class="prompt">root# </code> rm /var/log/samba/*
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2575251"></a>
-		<a class="indexterm" name="id2575257"></a>
+		<a class="indexterm" name="id2575256"></a>
+		<a class="indexterm" name="id2575263"></a>
 		Samba-3 communicates with the LDAP server. The password that it uses to
 		authenticate to the LDAP server must be stored in the <code class="filename">secrets.tdb</code>
 		file. Execute the following to create the new <code class="filename">secrets.tdb</code> files
@@ -1194,8 +1194,8 @@ Press enter to see a dump of your service definitions
 Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2575306"></a>
-		<a class="indexterm" name="id2575313"></a>
+		<a class="indexterm" name="id2575312"></a>
+		<a class="indexterm" name="id2575319"></a>
 		Samba-3 generates a Windows Security Identifier (SID) only when <code class="literal">smbd</code>
 		has been started. For this reason, you start Samba. After a few seconds delay,
 		execute:
@@ -1229,10 +1229,10 @@ SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765
 		</p></li><li><p>
 		When a positive domain SID has been reported, stop Samba.
 		</p></li><li><p>
-		<a class="indexterm" name="id2575425"></a>
-		<a class="indexterm" name="id2575432"></a>
-		<a class="indexterm" name="id2575439"></a>
-		<a class="indexterm" name="id2575445"></a>
+		<a class="indexterm" name="id2575431"></a>
+		<a class="indexterm" name="id2575438"></a>
+		<a class="indexterm" name="id2575444"></a>
+		<a class="indexterm" name="id2575451"></a>
 		Configure the NFS server for your Linux system. So you can complete the steps that
 		follow, enter into the <code class="filename">/etc/exports</code> the following entry:
 </p><pre class="screen">
@@ -1250,8 +1250,8 @@ SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765
 		</p></li></ol></div><p>
 	Your Samba-3 PDC is now ready to communicate with the LDAP password backend. Let's get on with
 	configuration of the LDAP server.
-	</p><div class="example"><a name="sbehap-massive-smbconfa"></a><p class="title"><b>Example�5.6.�LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE  global Section: Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2575532"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2575544"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2575555"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2575567"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2575579"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575591"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2575603"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575615"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2575627"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2575639"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2575650"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2575662"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2575674"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2575685"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2575698"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575709"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2575721"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2575733"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575746"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575758"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575770"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575783"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575796"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575809"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575822"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u"</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-massive-smbconfb"></a><p class="title"><b>Example�5.7.�LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE  global Section: Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2575859"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2575871"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2575883"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2575895"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575906"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575918"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575930"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2575942"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2575954"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2575966"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2575978"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2575990"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2576002"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2576014"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2576026"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2576038"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2576050"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2576061"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbeidealx"></a>Install and Configure Idealx smbldap-tools Scripts</h3></div></div></div><p>
-	<a class="indexterm" name="id2576087"></a>
+	</p><div class="example"><a name="sbehap-massive-smbconfa"></a><p class="title"><b>Example�5.6.�LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE  global Section: Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2575538"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2575549"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2575561"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2575573"></a><em class="parameter"><code>interfaces = eth1, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2575585"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575597"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2575609"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575621"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2575633"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2575644"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2575656"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2575668"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2575680"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2575691"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2575703"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575715"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2575727"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2575739"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575751"></a><em class="parameter"><code>delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575764"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575776"></a><em class="parameter"><code>delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575789"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575802"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2575815"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2575827"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u"</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-massive-smbconfb"></a><p class="title"><b>Example�5.7.�LDAP Based <code class="filename">smb.conf</code> File, Server: MASSIVE  global Section: Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2575865"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2575877"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2575889"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2575900"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575912"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575924"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575936"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2575948"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2575960"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2575972"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2575984"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2575996"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2576008"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2576020"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2576032"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2576044"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2576055"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2576067"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbeidealx"></a>Install and Configure Idealx smbldap-tools Scripts</h3></div></div></div><p>
+	<a class="indexterm" name="id2576093"></a>
 	The Idealx scripts, or equivalent, are necessary to permit Samba-3 to manage accounts
 	on the LDAP server. You have chosen the Idealx scripts because they are the best-known
 	LDAP configuration scripts. The use of these scripts will help avoid the necessity
@@ -1268,7 +1268,7 @@ change the path to them in your <code class="filename">smb.conf</code> file on t
 	The smbldap-tools are located in <code class="filename">/opt/IDEALX/sbin</code>.
 	The scripts are not needed on BDC machines because all LDAP updates are handled by
 	the PDC alone.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576154"></a>Installation of smbldap-tools from the Tarball</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576160"></a>Installation of smbldap-tools from the Tarball</h4></div></div></div><p>
 	To perform a manual installation of the smbldap-tools scripts, the following procedure may be used:
 	</p><div class="procedure"><a name="idealxscript"></a><p class="title"><b>Procedure�5.5.�Unpacking and Installation Steps for the <code class="constant">smbldap-tools</code> Tarball</b></p><ol type="1"><li><p>
 		Create the <code class="filename">/opt/IDEALX/sbin</code> directory, and set its permissions
@@ -1320,10 +1320,10 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf";
 </pre><p>
 		The smbldap-tools scripts are now ready for the configuration step outlined in
 		<a class="link" href="happy.html#smbldap-init" title="Configuration of smbldap-tools">&#8220;Configuration of smbldap-tools&#8221;</a>.
-		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576407"></a>Installing smbldap-tools from the RPM Package</h4></div></div></div><p>
+		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576412"></a>Installing smbldap-tools from the RPM Package</h4></div></div></div><p>
 	In the event that you have elected to use the RPM package provided by Idealx, download the
 	source RPM <code class="filename">smbldap-tools-0.9.1-1.src.rpm</code>, then follow this procedure:
-	</p><div class="procedure"><a name="id2576425"></a><p class="title"><b>Procedure�5.6.�Installation Steps for <code class="constant">smbldap-tools</code> RPM's</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2576431"></a><p class="title"><b>Procedure�5.6.�Installation Steps for <code class="constant">smbldap-tools</code> RPM's</b></p><ol type="1"><li><p>
 		Install the source RPM that has been downloaded as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> rpm -i smbldap-tools-0.9.1-1.src.rpm
@@ -1368,7 +1368,7 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf";
 	</p><p>
 	The smbldap-tools require that the NetBIOS name (machine name) of the Samba server be included
 	in the <code class="filename">smb.conf</code> file.
-	</p><div class="procedure"><a name="id2576620"></a><p class="title"><b>Procedure�5.7.�Configuration Steps for <code class="constant">smbldap-tools</code> to Enable Use</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2576625"></a><p class="title"><b>Procedure�5.7.�Configuration Steps for <code class="constant">smbldap-tools</code> to Enable Use</b></p><ol type="1"><li><p>
 		Change into the directory that contains the <code class="filename">configure.pl</code> script.
 </p><pre class="screen">
 <code class="prompt">root# </code> cd /opt/IDEALX/sbin
@@ -1474,7 +1474,7 @@ writing new configuration file:
 		then verify its contents.
 		</p></li></ol></div><p>
 	The smbldap-tools are now ready for use.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2576821"></a>LDAP Initialization and Creation of User and Group Accounts</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2576827"></a>LDAP Initialization and Creation of User and Group Accounts</h3></div></div></div><p>
 	The LDAP database must be populated with well-known Windows domain user accounts and domain group 
 	accounts before Samba can be used. The following procedures step you through the process.
 	</p><p>
@@ -1487,12 +1487,12 @@ writing new configuration file:
 	</p><p>
 	Addition of an account to the LDAP backend can be done in two ways:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2576855"></a>
-		<a class="indexterm" name="id2576862"></a>
-		<a class="indexterm" name="id2576869"></a>
-		<a class="indexterm" name="id2576876"></a>
-		<a class="indexterm" name="id2576882"></a>
-		<a class="indexterm" name="id2576889"></a>
+		<a class="indexterm" name="id2576861"></a>
+		<a class="indexterm" name="id2576868"></a>
+		<a class="indexterm" name="id2576874"></a>
+		<a class="indexterm" name="id2576881"></a>
+		<a class="indexterm" name="id2576888"></a>
+		<a class="indexterm" name="id2576895"></a>
 		If you always have a user account in the <code class="filename">/etc/passwd</code> on every 
 		server or in a NIS(+) backend, it is not necessary to add POSIX accounts for them in 
 		LDAP. In this case, you can add Windows domain user accounts using the 
@@ -1510,20 +1510,20 @@ writing new configuration file:
 		Idealx smbldap-tools scripts. A copy of these tools, preconfigured for this system,
 		is included on the enclosed CD-ROM under <code class="filename">Chap06/Tools.</code>
 		</p></li></ul></div><p>
-	<a class="indexterm" name="id2576949"></a>
+	<a class="indexterm" name="id2576955"></a>
 	If you wish to have more control over how the LDAP database is initialized or 
 	if you don't want to use the Idealx smbldap-tools, you should refer to 
 	<a class="link" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits">&#8220;A Collection of Useful Tidbits&#8221;</a>, <a class="link" href="appendix.html#altldapcfg" title="Alternative LDAP Database Initialization">&#8220;Alternative LDAP Database Initialization&#8221;</a>.
 	</p><p>
-	<a class="indexterm" name="id2576976"></a>
+	<a class="indexterm" name="id2576982"></a>
 	The following steps initialize the LDAP database, and then you can add user and group
 	accounts that Samba can use. You use the <code class="literal">smbldap-populate</code> to
 	seed the LDAP database. You then manually add the accounts shown in <a class="link" href="happy.html#sbehap-bigacct" title="Table�5.3.�Abmas Network Users and Groups">&#8220;Abmas Network Users and Groups&#8221;</a>. 
 	The list of users does not cover all 500 network users; it provides examples only.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2577006"></a>
-	<a class="indexterm" name="id2577015"></a>
-	<a class="indexterm" name="id2577024"></a>
+	<a class="indexterm" name="id2577012"></a>
+	<a class="indexterm" name="id2577021"></a>
+	<a class="indexterm" name="id2577030"></a>
 	In the following examples, as the LDAP database is initialized, we do create a container
 	for Computer (machine) accounts. In the Samba-3 <code class="filename">smb.conf</code> files, specific use is made
 	of the People container, not the Computers container, for domain member accounts. This is not a
@@ -1600,7 +1600,7 @@ Shutting down ldap-server                            done
 Starting ldap-server                                 done
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2577444"></a>
+		<a class="indexterm" name="id2577450"></a>
 		So that we can use a global IDMAP repository, the LDAP directory must have a container object for IDMAP data. 
 		There are several ways you can check that your LDAP database is able to receive IDMAP information. One of 
 		the simplest is to execute:
@@ -1609,7 +1609,7 @@ Starting ldap-server                                 done
 dn: ou=Idmap,dc=abmas,dc=biz
 ou: idmap
 </pre><p>
-		<a class="indexterm" name="id2577468"></a>
+		<a class="indexterm" name="id2577473"></a>
 	        If the execution of this command does not return IDMAP entries, you need to create an LDIF
 		template file (see <a class="link" href="happy.html#sbehap-ldifadd" title="Example�5.12.�LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF">&#8220;LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF&#8221;</a>). You can add the required entries using 
 		the following command:
@@ -1619,7 +1619,7 @@ ou: idmap
 </pre><p>
 		Samba automatically populates this LDAP directory container when it needs to.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577507"></a>
+		<a class="indexterm" name="id2577513"></a>
 		It looks like all has gone well, as expected. Let's confirm that this is the case
 		by running a few tests. First we check the contents of the database directly
 		by running <code class="literal">slapcat</code> as follows (the output has been cut down):
@@ -1657,7 +1657,7 @@ modifyTimestamp: 20031217234206Z
 </pre><p>
 		This looks good so far.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577558"></a>
+		<a class="indexterm" name="id2577564"></a>
 		The next step is to prove that the LDAP server is running and responds to a
 		search request. Execute the following as shown (output has been cut to save space):
 </p><pre class="screen">
@@ -1702,7 +1702,7 @@ result: 0 Success
 </pre><p>
 		Good. It is all working just fine.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577615"></a>
+		<a class="indexterm" name="id2577621"></a>
 		You must now make certain that the NSS resolver can interrogate LDAP also.
 		Execute the following commands:
 </p><pre class="screen">
@@ -1715,16 +1715,16 @@ Domain Users:x:513:
 Domain Guests:x:514:
 Domain Computers:x:553:
 </pre><p>
-		<a class="indexterm" name="id2577645"></a>
+		<a class="indexterm" name="id2577651"></a>
 		This demonstrates that the <code class="literal">nss_ldap</code> library is functioning
 		as it should. If these two steps fail to produce this information, refer to
 		<a class="link" href="happy.html#sbeavoid" title="Avoiding Failures: Solving Problems Before They Happen">&#8220;Avoiding Failures: Solving Problems Before They Happen&#8221;</a> for diagnostic procedures that can be followed to
 		isolate the cause of the problem. Proceed to the next step only when the previous steps
 		have been successfully completed.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577675"></a>
-		<a class="indexterm" name="id2577682"></a>
-		<a class="indexterm" name="id2577689"></a>
+		<a class="indexterm" name="id2577681"></a>
+		<a class="indexterm" name="id2577688"></a>
+		<a class="indexterm" name="id2577695"></a>
 		Our database is now ready for the addition of network users. For each user for
 		whom an account must be created, execute the following:
 </p><pre class="screen">
@@ -1740,7 +1740,7 @@ Retype new SMB password: XXXXXXXX
 </pre><p>
 		where <code class="constant">username</code> is the login ID for each user.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577750"></a>
+		<a class="indexterm" name="id2577756"></a>
 		Now verify that the UNIX (POSIX) accounts can be resolved via NSS by executing the
 		following:
 </p><pre class="screen">
@@ -1768,7 +1768,7 @@ uid=1002(chrisr) gid=513(Domain Users) groups=513(Domain Users)
 		This confirms that the UNIX (POSIX) user account information can be resolved from LDAP
 		by system tools that make a getentpw() system call.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577816"></a>
+		<a class="indexterm" name="id2577822"></a>
 		The root account must have UID=0; if not, this means that operations conducted from
 		a Windows client using tools such as the Domain User Manager fails under UNIX because
 		the management of user and group accounts requires that the UID=0. Additionally, it is
@@ -1802,8 +1802,8 @@ drwx------   7 stans  Domain Users     568 Dec 17 01:43 stans/
 </pre><p>
 		This is precisely what we want to see.
 		</p></li><li><p>
-		<a class="indexterm" name="id2577915"></a>
-		<a class="indexterm" name="id2577922"></a>
+		<a class="indexterm" name="id2577921"></a>
+		<a class="indexterm" name="id2577928"></a>
 		The final validation step involves making certain that Samba-3 can obtain the user
 		accounts from the LDAP ldapsam passwd backend. Execute the following command as shown:
 </p><pre class="screen">
@@ -1834,7 +1834,7 @@ Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 </pre><p>
 		This looks good. Of course, you fully expected that it would all work, didn't you?
 		</p></li><li><p>
-		<a class="indexterm" name="id2577967"></a>
+		<a class="indexterm" name="id2577973"></a>
 		Now you add the group accounts that are used on the Abmas network. Execute
 		the following exactly as shown:
 </p><pre class="screen">
@@ -1845,7 +1845,7 @@ Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 		The addition of groups does not involve keyboard interaction, so the lack of console
 		output is of no concern.
 		</p></li><li><p>
-		<a class="indexterm" name="id2578010"></a>
+		<a class="indexterm" name="id2578015"></a>
 		You really do want to confirm that UNIX group resolution from LDAP is functioning 
 		as it should. Let's do this as shown here:
 </p><pre class="screen">
@@ -1862,7 +1862,7 @@ PIOps:x:1002:
 		The well-known special accounts (Domain Admins, Domain Users, Domain Guests), as well
 		as our own site-specific group accounts, are correctly listed. This is looking good.
 		</p></li><li><p>
-		<a class="indexterm" name="id2578042"></a>
+		<a class="indexterm" name="id2578048"></a>
 		The final step we need to validate is that Samba can see all the Windows domain groups
 		and that they are correctly mapped to the respective UNIX group account. To do this,
 		just execute the following command:
@@ -1917,7 +1917,7 @@ Joined domain MEGANET2.
 <code class="prompt">root# </code> rcwinbind restart
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2578257"></a>
+		<a class="indexterm" name="id2578263"></a>
 		You may now check Samba-3 operation as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbclient -L massive -U%
@@ -1963,12 +1963,12 @@ smb: \&gt; q
 		</p></li></ol></div><p>
 	The server <code class="constant">MASSIVE</code> is now configured, and it is time to move onto the next task.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbehap-ptrcfg"></a>Printer Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2578368"></a>
+	<a class="indexterm" name="id2578374"></a>
 	The configuration for Samba-3 to enable CUPS raw-print-through printing has already been
 	taken care of in the <code class="filename">smb.conf</code> file. The only preparation needed for <code class="constant">smart</code>
 	printing to be possible involves creation of the directories in which Samba-3 stores
 	Windows printing driver files.
-	</p><div class="procedure"><a name="id2578390"></a><p class="title"><b>Procedure�5.9.�Printer Configuration Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2578396"></a><p class="title"><b>Procedure�5.9.�Printer Configuration Steps</b></p><ol type="1"><li><p>
                 Configure all network-attached printers to have a fixed IP address.
                 </p></li><li><p>
                 Create an entry in the DNS database on the server <code class="constant">MASSIVE</code>
@@ -1980,18 +1980,18 @@ smb: \&gt; q
                 Follow the instructions in the printer manufacturers' manuals to permit printing
                 to port 9100.  Use any other port the manufacturer specifies for direct mode,
                 raw printing.  This allows the CUPS spooler to print using raw mode protocols.
-                <a class="indexterm" name="id2578451"></a>
-                <a class="indexterm" name="id2578458"></a>
+                <a class="indexterm" name="id2578457"></a>
+                <a class="indexterm" name="id2578464"></a>
                 </p></li><li><p>
-		<a class="indexterm" name="id2578472"></a>
-                <a class="indexterm" name="id2578478"></a>
+		<a class="indexterm" name="id2578477"></a>
+                <a class="indexterm" name="id2578484"></a>
                 Only on the server to which the printer is attached, configure the CUPS Print
                 Queues as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p <em class="parameter"><code>printque</code></em>
 	 -v socket://<em class="parameter"><code>printer-name</code></em>.abmas.biz:9100 -E
 </pre><p>
-                <a class="indexterm" name="id2578514"></a>
+                <a class="indexterm" name="id2578520"></a>
                 This step creates the necessary print queue to use no assigned print filter. This
                 is ideal for raw printing, that is, printing without use of filters.
                 The name <em class="parameter"><code>printque</code></em> is the name you have assigned for
@@ -2011,15 +2011,15 @@ smb: \&gt; q
 <code class="prompt">root# </code> /usr/bin/accept <em class="parameter"><code>printque</code></em>
 </pre><p>
                 </p></li><li><p>
-                <a class="indexterm" name="id2578595"></a>
-                <a class="indexterm" name="id2578602"></a>
-                <a class="indexterm" name="id2578609"></a>
+                <a class="indexterm" name="id2578601"></a>
+                <a class="indexterm" name="id2578608"></a>
+                <a class="indexterm" name="id2578615"></a>
                 Edit the file <code class="filename">/etc/cups/mime.convs</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
 		</p></li><li><p>
-		 <a class="indexterm" name="id2578638"></a>
+		 <a class="indexterm" name="id2578643"></a>
 		 Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
@@ -2038,7 +2038,7 @@ application/octet-stream
 <code class="prompt">root# </code> chown -R root:root /var/lib/samba/drivers
 <code class="prompt">root# </code> chmod -R ug=rwx,o=rx /var/lib/samba/drivers
 </pre><p>
-		</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sbehap-bldg1"></a>Samba-3 BDC Configuration</h2></div></div></div><div class="procedure"><a name="id2578721"></a><p class="title"><b>Procedure�5.10.�Configuration of BDC Called: <code class="constant">BLDG1</code></b></p><ol type="1"><li><p>
+		</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sbehap-bldg1"></a>Samba-3 BDC Configuration</h2></div></div></div><div class="procedure"><a name="id2578727"></a><p class="title"><b>Procedure�5.10.�Configuration of BDC Called: <code class="constant">BLDG1</code></b></p><ol type="1"><li><p>
 		Install the files in <a class="link" href="happy.html#sbehap-bldg1-smbconf" title="Example�5.8.�LDAP Based smb.conf File, Server: BLDG1">&#8220;LDAP Based smb.conf File, Server: BLDG1&#8221;</a>,
 		<a class="link" href="happy.html#sbehap-shareconfa" title="Example�5.10.�LDAP Based smb.conf File, Shares Section Part A">&#8220;LDAP Based smb.conf File, Shares Section  Part A&#8221;</a>, and <a class="link" href="happy.html#sbehap-shareconfb" title="Example�5.11.�LDAP Based smb.conf File, Shares Section Part B">&#8220;LDAP Based smb.conf File, Shares Section  Part B&#8221;</a>
 		into the <code class="filename">/etc/samba/</code> directory. The three files
@@ -2081,7 +2081,7 @@ bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false
 </pre><p>
 		This is the correct output. If the accounts that have UIDs above 512 are not shown, there is a problem.
 		</p></li><li><p>
-		<a class="indexterm" name="id2578881"></a>
+		<a class="indexterm" name="id2578887"></a>
 		The next step in the verification process involves testing the operation of UNIX group
 		resolution via the NSS LDAP resolver. Execute these commands:
 </p><pre class="screen">
@@ -2111,7 +2111,7 @@ PIOps:x:1002:
 		This is also the correct and desired output, because it demonstrates that the LDAP client
 		is able to communicate correctly with the LDAP server (<code class="constant">MASSIVE</code>).
 		</p></li><li><p>
-		<a class="indexterm" name="id2578922"></a>
+		<a class="indexterm" name="id2578928"></a>
 		You must now set the LDAP administrative password into the Samba-3 <code class="filename">secrets.tdb</code>
 		file by executing this command:
 </p><pre class="screen">
@@ -2143,7 +2143,7 @@ Joined domain MEGANET2.
 </pre><p>
 		This indicates that the domain security account for the BDC has been correctly created.
 		</p></li><li><p>
-		<a class="indexterm" name="id2579023"></a>
+		<a class="indexterm" name="id2579029"></a>
 		Verify that user and group account resolution works via Samba-3 tools as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> pdbedit -L
@@ -2231,19 +2231,19 @@ smb: \&gt; q
 		should be added together to form the <code class="filename">smb.conf</code> file.
 		</p></li><li><p>
 		Follow carefully the steps shown in <a class="link" href="happy.html#sbehap-bldg1" title="Samba-3 BDC Configuration">&#8220;Samba-3 BDC Configuration&#8221;</a>, starting at step 2.
-		</p></li></ol></div><div class="example"><a name="sbehap-bldg1-smbconf"></a><p class="title"><b>Example�5.8.�LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG1</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2579369"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2579381"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2579393"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2579405"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579417"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579429"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2579441"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2579452"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2579464"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2579476"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2579487"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2579499"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2579511"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2579523"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579535"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2579547"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2579559"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2579571"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579582"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579594"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2579606"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579618"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2579630"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2579642"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2579654"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2579666"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579678"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579690"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2579702"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2579714"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2579725"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-bldg2-smbconf"></a><p class="title"><b>Example�5.9.�LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG2</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2579772"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2579784"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2579795"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2579807"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579819"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579831"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2579843"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2579855"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2579866"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2579878"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2579890"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2579902"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2579914"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2579926"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579938"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2579950"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2579962"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2579973"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579985"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579997"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2580008"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580020"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2580032"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2580044"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2580056"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2580068"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580080"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580093"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2580104"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2580116"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2580128"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-shareconfa"></a><p class="title"><b>Example�5.10.�LDAP Based <code class="filename">smb.conf</code> File, Shares Section  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2580174"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580186"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2580198"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2580218"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580230"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2580241"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2580262"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580274"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2580285"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2580306"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2580318"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2580329"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580341"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2580361"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2580373"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2580385"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580396"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580408"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-shareconfb"></a><p class="title"><b>Example�5.11.�LDAP Based <code class="filename">smb.conf</code> File, Shares Section  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2580454"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580466"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2580477"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2580489"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2580509"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2580521"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2580533"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580544"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2580565"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2580577"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2580589"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580600"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2580621"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2580633"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2580645"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580656"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2580677"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2580689"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2580700"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580712"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2580724"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580735"></a><em class="parameter"><code>write list = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-ldifadd"></a><p class="title"><b>Example�5.12.�LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</b></p><div class="example-contents"><pre class="screen">
+		</p></li></ol></div><div class="example"><a name="sbehap-bldg1-smbconf"></a><p class="title"><b>Example�5.8.�LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG1</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2579375"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2579387"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2579398"></a><em class="parameter"><code>netbios name = BLDG1</code></em></td></tr><tr><td><a class="indexterm" name="id2579410"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579423"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579434"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2579446"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2579458"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2579470"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2579481"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2579493"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2579505"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2579517"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2579529"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579541"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2579553"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2579565"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2579576"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579588"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579600"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2579612"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579623"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2579635"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2579647"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2579659"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2579671"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579684"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579696"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2579708"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2579719"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2579731"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-bldg2-smbconf"></a><p class="title"><b>Example�5.9.�LDAP Based <code class="filename">smb.conf</code> File, Server: BLDG2</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2579777"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2579789"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2579801"></a><em class="parameter"><code>netbios name = BLDG2</code></em></td></tr><tr><td><a class="indexterm" name="id2579813"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2579825"></a><em class="parameter"><code>enable privileges = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579837"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2579849"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2579861"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2579872"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2579884"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2579896"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2579907"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2579919"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2579931"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2579943"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2579955"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2579967"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2579979"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2579991"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580002"></a><em class="parameter"><code>wins server = 172.16.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2580014"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580026"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2580038"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2580050"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2580062"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2580074"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580086"></a><em class="parameter"><code>idmap backend = ldap:ldap://massive.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2580098"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2580110"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2580122"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2580133"></a><em class="parameter"><code>printer admin = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-shareconfa"></a><p class="title"><b>Example�5.10.�LDAP Based <code class="filename">smb.conf</code> File, Shares Section  Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2580180"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580192"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2580203"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2580223"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580235"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2580247"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2580268"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580279"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2580291"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2580312"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2580323"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2580335"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580346"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2580367"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2580379"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2580390"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580402"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580414"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-shareconfb"></a><p class="title"><b>Example�5.11.�LDAP Based <code class="filename">smb.conf</code> File, Shares Section  Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2580460"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2580471"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2580483"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr><tr><td><a class="indexterm" name="id2580494"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2580515"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2580527"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2580539"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580550"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2580571"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2580582"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2580594"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580606"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2580627"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2580638"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2580650"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2580662"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2580683"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2580694"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2580706"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580718"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2580729"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2580741"></a><em class="parameter"><code>write list = root, chrisr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbehap-ldifadd"></a><p class="title"><b>Example�5.12.�LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</b></p><div class="example-contents"><pre class="screen">
 dn: ou=Idmap,dc=abmas,dc=biz
 objectClass: organizationalUnit
 ou: idmap
 structuralObjectClass: organizationalUnit
-</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2580771"></a>Miscellaneous Server Preparation Tasks</h2></div></div></div><p>
+</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2580776"></a>Miscellaneous Server Preparation Tasks</h2></div></div></div><p>
 	My father would say, &#8220;<span class="quote">Dinner is not over until the dishes have been done.</span>&#8221;
 	The makings of a great network environment take a lot of effort and attention to detail.
 	So far, you have completed most of the complex (and to many administrators, the interesting
 	part of server configuration) steps, but remember to tie it all together. Here are
 	a few more steps that must be completed so that your network runs like a well-rehearsed
 	orchestra.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580791"></a>Configuring Directory Share Point Roots</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580797"></a>Configuring Directory Share Point Roots</h3></div></div></div><p>
 	In your <code class="filename">smb.conf</code> file, you have specified Windows shares. Each has a <em class="parameter"><code>path</code></em>
 	parameter. Even though it is obvious to all, one of the common Samba networking problems is
 	caused by forgetting to verify that every such share root directory actually exists and that it
@@ -2261,7 +2261,7 @@ structuralObjectClass: organizationalUnit
 <code class="prompt">root# </code> chmod -R ug+rwxs,o-rwx /data
 <code class="prompt">root# </code> chmod -R ug+rwx,o+rx-w /apps
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580886"></a>Configuring Profile Directories</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580892"></a>Configuring Profile Directories</h3></div></div></div><p>
 	You made a conscious decision to do everything it would take to improve network client
 	performance. One of your decisions was to implement folder redirection. This means that Windows
 	user desktop profiles are now made up of two components: a dynamically loaded part and a set of file
@@ -2286,8 +2286,8 @@ structuralObjectClass: organizationalUnit
 <code class="prompt">root# </code> chmod -R 750 <span class="emphasis"><em>username</em></span>
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2581002"></a>
-	<a class="indexterm" name="id2581009"></a>
+	<a class="indexterm" name="id2581008"></a>
+	<a class="indexterm" name="id2581015"></a>
 	You have three options insofar as the dynamically loaded portion of the roaming profile
 	is concerned: 
 	</p><div class="itemizedlist"><ul type="disc"><li><p>You may permit the user to obtain a default profile.</p></li><li><p>You can create a mandatory profile.</p></li><li><p>You can create a group profile (which is almost always a mandatory profile).</p></li></ul></div><p>
@@ -2295,8 +2295,8 @@ structuralObjectClass: organizationalUnit
 	profile is effected by renaming the <code class="filename">NTUSER.DAT</code> to <code class="filename">NTUSER.MAN</code>,
 	that is, just by changing the filename extension.
 	</p><p>
-	<a class="indexterm" name="id2581059"></a>
-	<a class="indexterm" name="id2581066"></a>
+	<a class="indexterm" name="id2581064"></a>
+	<a class="indexterm" name="id2581071"></a>
 	The location of the profile that a user can obtain is set in the user's account in the LDAP passdb backend.
 	You can manage this using the Idealx smbldap-tools or using the 
 	<a class="ulink" href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">Windows NT4 Domain User Manager</a>.
@@ -2309,8 +2309,8 @@ structuralObjectClass: organizationalUnit
 	    /var/lib/samba/profiles/<span class="emphasis"><em>username</em></span>
 <code class="prompt">root# </code> chmod 700  /var/lib/samba/profiles/<span class="emphasis"><em>username</em></span>
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2581130"></a>Preparation of Logon Scripts</h3></div></div></div><p>
-	<a class="indexterm" name="id2581138"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2581136"></a>Preparation of Logon Scripts</h3></div></div></div><p>
+	<a class="indexterm" name="id2581144"></a>
 	The use of a logon script with Windows XP Professional is an option that every site should consider.
 	Unless you have locked down the desktop so the user cannot change anything, there is risk that
 	a vital network drive setting may be broken or that printer connections may be lost. Logon scripts
@@ -2335,7 +2335,7 @@ structuralObjectClass: organizationalUnit
 	You should research the options for logon script implementation by referring to <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 24,
 	Section 24.4. A quick Web search will bring up a host of options. One of the most popular logon
 	facilities in use today is called <a class="ulink" href="http://www.kixtart.org" target="_top">KiXtart</a>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2581241"></a>Assigning User Rights and Privileges</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2581247"></a>Assigning User Rights and Privileges</h3></div></div></div><p>
 	The ability to perform tasks such as joining Windows clients to the domain can be assigned to
 	normal user accounts. By default, only the domain administrator account (<code class="constant">root</code> on UNIX
 	systems because it has UID=0) can add accounts. New to Samba 3.0.11 is the ability to grant
@@ -2347,7 +2347,7 @@ structuralObjectClass: organizationalUnit
 	Samba limits privileges on a per-server basis. This is a deliberate limitation so that users who
 	are granted rights can be restricted to particular machines. It is left to the network administrator
 	to determine which rights should be provided and to whom.
-	</p><div class="procedure"><a name="id2581277"></a><p class="title"><b>Procedure�5.12.�Steps for Assignment of User Rights and Privileges</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2581283"></a><p class="title"><b>Procedure�5.12.�Steps for Assignment of User Rights and Privileges</b></p><ol type="1"><li><p>
 		Log onto the PDC as the <code class="constant">root</code> account.
 		</p></li><li><p>
 		Execute the following command to grant the <code class="constant">Domain Admins</code> group all
@@ -2405,8 +2405,8 @@ SeAddUsersPrivilege
 SeRemoteShutdownPrivilege
 SeDiskOperatorPrivilege
 </pre><p>
-		</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2581375"></a>Windows Client Configuration</h2></div></div></div><p>
-	<a class="indexterm" name="id2581383"></a>
+		</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2581381"></a>Windows Client Configuration</h2></div></div></div><p>
+	<a class="indexterm" name="id2581389"></a>
 	In the next few sections, you can configure a new Windows XP Professional disk image on a staging
 	machine. You will configure all software, printer settings, profile and policy handling, and desktop
 	default profile settings on this system. When it is complete, you copy the contents of the
@@ -2419,24 +2419,24 @@ SeDiskOperatorPrivilege
 	Base Profile for All Users."</a>
 
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="redirfold"></a>Configuration of Default Profile with Folder Redirection</h3></div></div></div><p>
-	<a class="indexterm" name="id2581433"></a>
+	<a class="indexterm" name="id2581439"></a>
 	Log onto the Windows XP Professional workstation as the local <code class="constant">Administrator</code>.
 	It is necessary to expose folders that are generally hidden to provide access to the
 	<code class="constant">Default User</code> folder.
-	</p><div class="procedure"><a name="id2581451"></a><p class="title"><b>Procedure�5.13.�Expose Hidden Folders</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2581457"></a><p class="title"><b>Procedure�5.13.�Expose Hidden Folders</b></p><ol type="1"><li><p>
 		Launch the Windows Explorer by clicking
 			<span class="guimenu">Start</span> &#8594; <span class="guimenuitem">My Computer</span> &#8594; <span class="guimenuitem">Tools</span> &#8594; <span class="guimenuitem">Folder Options</span> &#8594; <span class="guimenuitem">View Tab</span>.
 		Select <span class="guilabel">Show hidden files and folders</span>,
 		and click <span class="guibutton">OK</span>.  Exit Windows Explorer.
 		</p></li><li><p>
-		<a class="indexterm" name="id2581518"></a>
+		<a class="indexterm" name="id2581523"></a>
 		Launch the Registry Editor. Click 
 		<span class="guimenu">Start</span> &#8594; <span class="guimenuitem">Run</span>. Key in <code class="literal">regedt32</code>, and click
 		<span class="guibutton">OK</span>.
 		</p></li></ol></div><p>
 	</p><div class="procedure"><a name="sbehap-rdrfldr"></a><p class="title"><b>Procedure�5.14.�Redirect Folders in Default System User Profile</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2581576"></a>
-		<a class="indexterm" name="id2581582"></a>
+		<a class="indexterm" name="id2581581"></a>
+		<a class="indexterm" name="id2581588"></a>
 		Give focus to <code class="constant">HKEY_LOCAL_MACHINE</code> hive entry in the left panel.
 		Click <span class="guimenu">File</span> &#8594; <span class="guimenuitem">Load Hive...</span> &#8594; <span class="guimenuitem">Documents and Settings</span> &#8594; <span class="guimenuitem">Default User</span> &#8594; <span class="guimenuitem">NTUSER</span> &#8594; <span class="guimenuitem">Open</span>. In the dialog box that opens, enter the key name
 		<code class="constant">Default</code> and click <span class="guibutton">OK</span>.
@@ -2448,15 +2448,15 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 </pre><p>
 		The right panel reveals the contents as shown in <a class="link" href="happy.html#XP-screen001" title="Figure�5.3.�Windows XP Professional User Shared Folders">&#8220;Windows XP Professional  User Shared Folders&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2581675"></a>
-		<a class="indexterm" name="id2581682"></a>
+		<a class="indexterm" name="id2581681"></a>
+		<a class="indexterm" name="id2581688"></a>
 		You edit hive keys. Acceptable values to replace the 
 		<code class="constant">%USERPROFILE%</code> variable includes:
 
 		</p><div class="itemizedlist"><ul type="disc"><li><p>A drive letter such as <code class="constant">U:</code></p></li><li><p>A direct network path such as
 				<code class="constant">\\MASSIVE\profdata</code></p></li><li><p>A network redirection (UNC name) that contains a macro such as </p><p><code class="constant">%LOGONSERVER%\profdata\</code></p></li></ul></div><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2581729"></a>
+		<a class="indexterm" name="id2581735"></a>
 		Set the registry keys as shown in <a class="link" href="happy.html#proffold" title="Table�5.4.�Default Profile Redirections">&#8220;Default Profile Redirections&#8221;</a>. Your implementation makes the assumption
 		that users have statically located machines. Notebook computers (mobile users) need to be
 		accommodated using local profiles. This is not an uncommon assumption.
@@ -2464,14 +2464,14 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 		Click back to the root of the loaded hive <code class="constant">Default</code>.
 		Click <span class="guimenu">File</span> &#8594; <span class="guimenuitem">Unload Hive...</span> &#8594; <span class="guimenuitem">Yes</span>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2581784"></a>
+		<a class="indexterm" name="id2581790"></a>
 		Click <span class="guimenu">File</span> &#8594; <span class="guimenuitem">Exit</span>. This exits the
 		Registry Editor.
 		</p></li><li><p>
 		Now follow the procedure given in <a class="link" href="happy.html#sbehap-locgrppol" title="The Local Group Policy">&#8220;The Local Group Policy&#8221;</a>. Make sure that each folder you
 		have redirected is in the exclusion list.
 		</p></li><li><p>
-		You are now ready to copy<sup>[<a name="id2581828" href="#ftn.id2581828" class="footnote">11</a>]</sup> 
+		You are now ready to copy<sup>[<a name="id2581834" href="#ftn.id2581834" class="footnote">11</a>]</sup> 
 		the Default User profile to the Samba domain controllers. Launch Microsoft Windows Explorer,
 		and use it to copy the full contents of the directory <code class="filename">Default User</code> that
 		is in the <code class="filename">C:\Documents and Settings</code> to the root directory of the
@@ -2482,14 +2482,14 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 	Before punching out new desktop images for the client workstations, it is perhaps a good idea that
 	desktop behavior should be returned to the original Microsoft settings. The following steps achieve
 	that ojective:
-	</p><div class="procedure"><a name="id2581895"></a><p class="title"><b>Procedure�5.15.�Reset Folder Display to Original Behavior</b></p><ul><li><p>
+	</p><div class="procedure"><a name="id2581901"></a><p class="title"><b>Procedure�5.15.�Reset Folder Display to Original Behavior</b></p><ul><li><p>
 		To launch the Windows Explorer, click
 			<span class="guimenu">Start</span> &#8594; <span class="guimenuitem">My Computer</span> &#8594; <span class="guimenuitem">Tools</span> &#8594; <span class="guimenuitem">Folder Options</span> &#8594; <span class="guimenuitem">View Tab</span>.
 		Deselect <span class="guilabel">Show hidden files and folders</span>, and click <span class="guibutton">OK</span>.
 		Exit Windows Explorer.
-		</p></li></ul></div><div class="figure"><a name="XP-screen001"></a><p class="title"><b>Figure�5.3.�Windows XP Professional  User Shared Folders</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/XP-screen001.png" width="351" alt="Windows XP Professional User Shared Folders"></div></div></div><br class="figure-break"><div class="table"><a name="proffold"></a><p class="title"><b>Table�5.4.�Default Profile Redirections</b></p><div class="table-contents"><table summary="Default Profile Redirections" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Registry Key</th><th align="left">Redirected Value</th></tr></thead><tbody><tr><td align="left">Cache</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\InternetFiles</td></tr><tr><td align="left">Cookies</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\Cookies</td></tr><tr><td align="left">History</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\History</td></tr><tr><td align="left">Local AppData</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\AppData</td></tr><tr><td align="left">Local Settings</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\LocalSettings</td></tr><tr><td align="left">My Pictures</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\MyPictures</td></tr><tr><td align="left">Personal</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\MyDocuments</td></tr><tr><td align="left">Recent</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\Recent</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582129"></a>Configuration of MS Outlook to Relocate PST File</h3></div></div></div><p>
-	<a class="indexterm" name="id2582138"></a>
-	<a class="indexterm" name="id2582147"></a>
+		</p></li></ul></div><div class="figure"><a name="XP-screen001"></a><p class="title"><b>Figure�5.3.�Windows XP Professional  User Shared Folders</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/XP-screen001.png" width="351" alt="Windows XP Professional User Shared Folders"></div></div></div><br class="figure-break"><div class="table"><a name="proffold"></a><p class="title"><b>Table�5.4.�Default Profile Redirections</b></p><div class="table-contents"><table summary="Default Profile Redirections" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Registry Key</th><th align="left">Redirected Value</th></tr></thead><tbody><tr><td align="left">Cache</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\InternetFiles</td></tr><tr><td align="left">Cookies</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\Cookies</td></tr><tr><td align="left">History</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\History</td></tr><tr><td align="left">Local AppData</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\AppData</td></tr><tr><td align="left">Local Settings</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\LocalSettings</td></tr><tr><td align="left">My Pictures</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\MyPictures</td></tr><tr><td align="left">Personal</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\MyDocuments</td></tr><tr><td align="left">Recent</td><td align="left">%LOGONSERVER%\profdata\%USERNAME%\Recent</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582135"></a>Configuration of MS Outlook to Relocate PST File</h3></div></div></div><p>
+	<a class="indexterm" name="id2582144"></a>
+	<a class="indexterm" name="id2582153"></a>
 	Microsoft Outlook can store a Personal Storage file, generally known as a PST file.
 	It is the nature of email storage that this file grows, at times quite rapidly.
 	So that users' email is available to them at every workstation they may log onto,
@@ -2498,7 +2498,7 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 	</p><p>
 	To redirect the Outlook PST file in Outlook 2003 (older versions of Outlook behave
 	slightly differently), follow these steps:
-	</p><div class="procedure"><a name="id2582170"></a><p class="title"><b>Procedure�5.16.�Outlook PST File Relocation</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2582175"></a><p class="title"><b>Procedure�5.16.�Outlook PST File Relocation</b></p><ol type="1"><li><p>
 		Close Outlook if it is open.
 		</p></li><li><p>
 		From the <span class="guimenu">Control Panel</span>, launch the Mail icon.
@@ -2528,11 +2528,11 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 		</p></li><li><p>
 		Go back to the <span class="guimenu">Data Files</span> window, then delete the old data file entry.
 		</p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2582319"></a>
+	<a class="indexterm" name="id2582325"></a>
 	You may have to remove and reinstall the Outlook Address Book (Contacts) entries, otherwise 
 	the user may be not be able to retrieve contacts when addressing a new email message.
 	</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2582334"></a>
+	<a class="indexterm" name="id2582340"></a>
 	Outlook Express is not at all like MS OutLook. It stores file very differently also. Outlook
 	Express storage files can not be redirected to network shares. The options panel will not permit
 	this, but they can be moved to folders outside of the user's profile. They can also be excluded
@@ -2541,34 +2541,34 @@ HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
 	While it is possible to redirect the data stores for Outlook Express data stores by editing the 
 	registry, experience has shown that data corruption and loss of email messages will result.
 	</p><p>
-	<a class="indexterm" name="id2582357"></a>
-	<a class="indexterm" name="id2582364"></a>
+	<a class="indexterm" name="id2582362"></a>
+	<a class="indexterm" name="id2582369"></a>
 	In the same vane as MS Outlook, Outlook Express data stores can become very large. When used with
 	roaming profiles this can result in excruciatingly long login and logout behavior will files are
 	synchronized. For this reason, it is highly recommended not to use Outlook Express where roaming
 	profiles are used.
 	</p></div><p>
-	<a class="indexterm" name="id2582379"></a>
+	<a class="indexterm" name="id2582385"></a>
 	Microsoft does not support storing PST files on network shares, although the practice does appear
 	to be rather popular. Anyone who does relocation the PST file to a network resource should refer
 	the Microsoft <a class="ulink" href="http://support.microsoft.com/kb/297019/" target="_top">reference</a> to better
 	understand the issues.
 	</p><p>
-	<a class="indexterm" name="id2582400"></a>
+	<a class="indexterm" name="id2582406"></a>
 	Apart from manually moving PST files to a network share, it is possible to set the default PST
 	location for new accounts by following the instructions at the WindowsITPro <a class="ulink" href="http://www.windowsitpro.com/Windows/Article/ArticleID/48228/48228.html" target="_top">web</a> site.
 	</p><p>
-	<a class="indexterm" name="id2582420"></a>
+	<a class="indexterm" name="id2582426"></a>
 	User feedback suggests that disabling of oplocks on PST files will significantly improve
 	network performance by reducing locking overheads. One way this can be done is to add to the
 	<code class="filename">smb.conf</code> file stanza for the share the PST file the following:
 </p><pre class="screen">
 veto oplock files = /*.pdf/*.PST/
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582445"></a>Configure Delete Cached Profiles on Logout</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582451"></a>Configure Delete Cached Profiles on Logout</h3></div></div></div><p>
 	Configure the Windows XP Professional client to auto-delete roaming profiles on logout:
 	</p><p>
-	<a class="indexterm" name="id2582458"></a>
+	<a class="indexterm" name="id2582464"></a>
 	Click 
 	<span class="guimenu">Start</span> &#8594; <span class="guimenuitem">Run</span>. In the dialog box, enter <code class="literal">MMC</code> and click <span class="guibutton">OK</span>.
 	</p><p>
@@ -2576,7 +2576,7 @@ veto oplock files = /*.pdf/*.PST/
 	profiles are deleted as network users log out of the system. Click
 	<span class="guimenu">File</span> &#8594; <span class="guimenuitem">Add/Remove Snap-in</span> &#8594; <span class="guimenuitem">Add</span> &#8594; <span class="guimenuitem">Group Policy</span> &#8594; <span class="guimenuitem">Add</span> &#8594; <span class="guimenuitem">Finish</span> &#8594; <span class="guimenuitem">Close</span> &#8594; <span class="guimenuitem">OK</span>. 
 	</p><p>
-	<a class="indexterm" name="id2582554"></a>
+	<a class="indexterm" name="id2582560"></a>
 	The Microsoft Management Console now shows the <span class="guimenu">Group Policy</span>
 	utility that enables you to set the policies needed. In the left panel, click
 	<span class="guimenuitem">Local Computer Policy</span> &#8594; <span class="guimenuitem">Administrative Templates</span> &#8594; <span class="guimenuitem">System</span> &#8594; <span class="guimenuitem">User Profiles</span>. In the right panel, set the properties shown here by double-clicking on each
@@ -2584,15 +2584,15 @@ veto oplock files = /*.pdf/*.PST/
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Do not check for user ownership of Roaming Profile Folders = Enabled</p></li><li><p>Delete cached copies of roaming profiles = Enabled</p></li></ul></div><p>
 	Close the Microsoft Management Console. The settings take immediate effect and persist onto all image copies
 	made of this system to deploy the new standard desktop system.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582625"></a>Uploading Printer Drivers to Samba Servers</h3></div></div></div><p>
-	<a class="indexterm" name="id2582633"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582630"></a>Uploading Printer Drivers to Samba Servers</h3></div></div></div><p>
+	<a class="indexterm" name="id2582639"></a>
 	Users want to be able to use network printers. You have a vested interest in making
 	it easy for them to print. You have chosen to install the printer drivers onto the Samba
 	servers and to enable point-and-click (drag-and-drop) printing. This process results in
 	Samba being able to automatically provide the Windows client with the driver necessary to
 	print to the printer chosen. The following procedure must be followed for every network
 	printer:
-	</p><div class="procedure"><a name="id2582651"></a><p class="title"><b>Procedure�5.17.�Steps to Install Printer Drivers on the Samba Servers</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2582657"></a><p class="title"><b>Procedure�5.17.�Steps to Install Printer Drivers on the Samba Servers</b></p><ol type="1"><li><p>
 		Join your Windows XP Professional workstation (the staging machine) to the 
 		<code class="constant">MEGANET2</code> domain. If you are not sure of the procedure, 
 		follow the guidance given in <a class="link" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits">&#8220;A Collection of Useful Tidbits&#8221;</a>, <a class="link" href="appendix.html#domjoin" title="Joining a Domain: Windows 200x/XP Professional">&#8220;Joining a Domain: Windows 200x/XP Professional&#8221;</a>.
@@ -2617,8 +2617,8 @@ veto oplock files = /*.pdf/*.PST/
 		Note that the box labeled <span class="guimenu">Driver</span> is empty. Click the <span class="guimenu">New Driver</span>
 		button that is next to the <span class="guimenu">Driver</span> box. This launches the &#8220;<span class="quote">Add Printer Wizard</span>&#8221;.
 		</p></li><li><p>
-		<a class="indexterm" name="id2582840"></a>
-		<a class="indexterm" name="id2582849"></a>
+		<a class="indexterm" name="id2582846"></a>
+		<a class="indexterm" name="id2582855"></a>
 		The &#8220;<span class="quote">Add Printer Driver Wizard on <code class="constant">MASSIVE</code></span>&#8221; panel 
 		is now presented. Click <span class="guimenu">Next</span> to continue. From the left panel, select the 
 		printer manufacturer. In your case, you are adding a driver for a printer manufactured by 
@@ -2627,12 +2627,12 @@ veto oplock files = /*.pdf/*.PST/
 		progress bar appears and instructs you as each file is being uploaded and that it is being 
 		directed at the network server <code class="constant">\\massive\ps01-color</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2582898"></a>
-		<a class="indexterm" name="id2582907"></a>
-		<a class="indexterm" name="id2582916"></a>
-		<a class="indexterm" name="id2582925"></a>
-		<a class="indexterm" name="id2582934"></a>
-		<a class="indexterm" name="id2582944"></a>
+		<a class="indexterm" name="id2582904"></a>
+		<a class="indexterm" name="id2582913"></a>
+		<a class="indexterm" name="id2582922"></a>
+		<a class="indexterm" name="id2582931"></a>
+		<a class="indexterm" name="id2582940"></a>
+		<a class="indexterm" name="id2582950"></a>
 		The driver upload completes in anywhere from a few seconds to a few minutes. When it completes,
 		you are returned to the <span class="guimenu">Advanced</span> tab in the <span class="guimenu">Properties</span> panel. 
 		You can set the Location (under the <span class="guimenu">General</span> tab) and Security settings (under 
@@ -2641,7 +2641,7 @@ veto oplock files = /*.pdf/*.PST/
 		directory</span>&#8221;. When this box is checked, the printer will be published in Active Directory
 		(Applicable to Active Directory use only.)
 		</p></li><li><p>
-		<a class="indexterm" name="id2582999"></a>
+		<a class="indexterm" name="id2583004"></a>
 		Click <span class="guimenu">OK</span>. It will take a minute or so to upload the settings to the server. 
 		You are now returned to the <span class="guimenu">Printers and Faxes on Massive</span> monitor.
 		Right-click on the printer, click <span class="guimenu">Properties</span> &#8594; <span class="guimenuitem">Device Settings</span>.  Now change the settings to suit 
@@ -2653,7 +2653,7 @@ veto oplock files = /*.pdf/*.PST/
 		just to initialize the Samba printers database entry for this printer. If you need to revert a setting,
 		click <span class="guimenu">Apply</span> again.
 		</p></li><li><p>
-		<a class="indexterm" name="id2583072"></a>
+		<a class="indexterm" name="id2583078"></a>
 		Verify that all printer settings are at the desired configuration. When you are satisfied that they are,
 		click the <span class="guimenu">General</span> tab. Now click the <span class="guimenu">Print Test Page</span> button.
 		A test page should print. Verify that it has printed correctly. Then click <span class="guimenu">OK</span>
@@ -2663,7 +2663,7 @@ veto oplock files = /*.pdf/*.PST/
 		You must repeat this process for all network printers (i.e., for every printer on each server).
 		When you have finished uploading drivers to all printers, close all applications. The next task
 		is to install software your users require to do their work.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583127"></a>Software Installation</h3></div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583133"></a>Software Installation</h3></div></div></div><p>
 	Your network has both fixed desktop workstations as well as notebook computers. As a general rule, it is
 	a good idea to not tamper with the operating system that is provided by the notebook computer manufacturer.
 	Notebooks require special handling that is beyond the scope of this chapter.
@@ -2678,7 +2678,7 @@ veto oplock files = /*.pdf/*.PST/
 	When you believe that the overall configuration is complete, be sure to create a shared group profile
 	and migrate that to the Samba server for later reuse when creating custom mandatory profiles, just in
 	case a user may have specific needs you had not anticipated.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583163"></a>Roll-out Image Creation</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583169"></a>Roll-out Image Creation</h3></div></div></div><p>
 	The final steps before preparing the distribution Norton Ghost image file you might follow are:
 	</p><div class="blockquote"><blockquote class="blockquote"><p>
 	Unjoin the domain  Each workstation requires a unique name and must be independently
@@ -2687,7 +2687,7 @@ veto oplock files = /*.pdf/*.PST/
 	Defragment the hard disk  While not obvious to the uninitiated, defragmentation results
 	in better performance and often significantly reduces the size of the compressed disk image. That
 	also means it will take less time to deploy the image onto 500 workstations.
-	</p></blockquote></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583197"></a>Key Points Learned</h2></div></div></div><p>
+	</p></blockquote></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583203"></a>Key Points Learned</h2></div></div></div><p>
 	This chapter introduced many new concepts. Is it a sad fact that the example presented deliberately
 	avoided any consideration of security. Security does not just happen; you must design it into your total
 	network. Security begins with a systems design and implementation that anticipates hostile behavior from
@@ -2696,8 +2696,8 @@ veto oplock files = /*.pdf/*.PST/
 	practices, you must not deploy the design presented in this book in an environment where there is risk
 	of compromise.
 	</p><p>
-	<a class="indexterm" name="id2583218"></a>
-	<a class="indexterm" name="id2583228"></a>
+	<a class="indexterm" name="id2583224"></a>
+	<a class="indexterm" name="id2583234"></a>
 	As a minimum, the LDAP server must be protected by way of Access Control Lists (ACLs), and it must be
 	configured to use secure protocols for all communications over the network. Of course, secure networking
 	does not result just from systems design and implementation but involves constant user education
@@ -2724,37 +2724,37 @@ veto oplock files = /*.pdf/*.PST/
 		Control over roaming profiles, with particular focus on folder redirection to network drives.
 		</p></li><li><p>
 		Use of the CUPS printing system together with Samba-based printer driver auto-download.
-		</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583303"></a>Questions and Answers</h2></div></div></div><p>
+		</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583318"></a>Questions and Answers</h2></div></div></div><p>
 	Well, here we are at the end of this chapter and we have only ten questions to help you to
 	remember so much. There are bound to be some sticky issues here.
-	</p><div class="qandaset"><dl><dt> <a href="happy.html#id2583322">
+	</p><div class="qandaset"><dl><dt> <a href="happy.html#id2583337">
 		Why did you not cover secure practices? Isn't it rather irresponsible to instruct
 		network administrators to implement insecure solutions?
-		</a></dt><dt> <a href="happy.html#id2583366">
+		</a></dt><dt> <a href="happy.html#id2583381">
 		You have focused much on SUSE Linux and little on the market leader, Red Hat. Do
 		you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant
 		to the Linux I might be using?
-		</a></dt><dt> <a href="happy.html#id2583427">
+		</a></dt><dt> <a href="happy.html#id2583442">
 		You did not use SWAT to configure Samba. Is there something wrong with it?
-		</a></dt><dt> <a href="happy.html#id2583466">
+		</a></dt><dt> <a href="happy.html#id2583481">
 		You have exposed a well-used password not24get. Is that
 		not irresponsible? 
-		</a></dt><dt> <a href="happy.html#id2583491">
+		</a></dt><dt> <a href="happy.html#id2583506">
 		The Idealx smbldap-tools create many domain group accounts that are not used. Is that
 		a good thing?
-		</a></dt><dt> <a href="happy.html#id2583518">
+		</a></dt><dt> <a href="happy.html#id2583532">
 		Can I use LDAP just for Samba accounts and not for UNIX system accounts?
-		</a></dt><dt> <a href="happy.html#id2583543">
+		</a></dt><dt> <a href="happy.html#id2583558">
 		Why are the Windows domain RID portions not the same as the UNIX UID?
-		</a></dt><dt> <a href="happy.html#id2583579">
+		</a></dt><dt> <a href="happy.html#id2583593">
 		Printer configuration examples all show printing to the HP port 9100. Does this
 		mean that I must have HP printers for these solutions to work?
-		</a></dt><dt> <a href="happy.html#id2583608">
+		</a></dt><dt> <a href="happy.html#id2583622">
 		Is folder redirection dangerous? I've heard that you can lose your data that way.
-		</a></dt><dt> <a href="happy.html#id2583635">
+		</a></dt><dt> <a href="happy.html#id2583650">
 		Is it really necessary to set a local Group Policy to exclude the redirected
 		folders from the roaming profile?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2583322"></a><a name="id2583324"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2583337"></a><a name="id2583339"></a></td><td align="left" valign="top"><p>
 		Why did you not cover secure practices? Isn't it rather irresponsible to instruct
 		network administrators to implement insecure solutions?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -2773,7 +2773,7 @@ veto oplock files = /*.pdf/*.PST/
 		This book makes little mention of backup techniques. Does that mean that I am recommending
 		that you should implement a network without provision for data recovery and for disaster
 		management? Back to our focus: The deployment of Samba has been clearly demonstrated.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583366"></a><a name="id2583368"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583381"></a><a name="id2583383"></a></td><td align="left" valign="top"><p>
 		You have focused much on SUSE Linux and little on the market leader, Red Hat. Do
 		you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant
 		to the Linux I might be using?
@@ -2800,7 +2800,7 @@ veto oplock files = /*.pdf/*.PST/
 		of open source software. I favor neither and respect both. I like particular
 		features of both products (companies also). No bias in presentation is intended.
 		Oh, before I forget, I particularly like Debian Linux; that is my favorite playground.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583427"></a><a name="id2583429"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583442"></a><a name="id2583444"></a></td><td align="left" valign="top"><p>
 		You did not use SWAT to configure Samba. Is there something wrong with it?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		That is a good question. As it is, the <code class="filename">smb.conf</code> file configurations are presented
@@ -2811,14 +2811,14 @@ veto oplock files = /*.pdf/*.PST/
 		There are people in the Linux and open source community who feel that SWAT is dangerous
 		and insecure. Many will not touch it with a barge-pole. By not introducing SWAT, I
 		hope to have brought their interests on board. SWAT is well covered is <span class="emphasis"><em>TOSHARG2</em></span>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583466"></a><a name="id2583468"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583481"></a><a name="id2583483"></a></td><td align="left" valign="top"><p>
 		You have exposed a well-used password <span class="emphasis"><em>not24get</em></span>. Is that
 		not irresponsible? 
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Well, I had to use a password of some sort. At least this one has been consistently
 		used throughout. I guess you can figure out that in a real deployment it would make 
 		sense to use a more secure and original password.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583491"></a><a name="id2583493"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583506"></a><a name="id2583508"></a></td><td align="left" valign="top"><p>
 		The Idealx smbldap-tools create many domain group accounts that are not used. Is that
 		a good thing?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -2826,7 +2826,7 @@ veto oplock files = /*.pdf/*.PST/
 		Let's give Idealx some credit for the contribution they have made. I appreciate their work
 		and, besides, it does no harm to create accounts that are not now used  at some time 
 		Samba may well use them.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583518"></a><a name="id2583520"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583532"></a><a name="id2583535"></a></td><td align="left" valign="top"><p>
 		Can I use LDAP just for Samba accounts and not for UNIX system accounts?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Yes, you can do that for user accounts only. Samba requires there to be a POSIX (UNIX)
@@ -2834,7 +2834,7 @@ veto oplock files = /*.pdf/*.PST/
 		the system password account, how do you plan to keep all domain controller system
 		password files in sync? I think that having everything in LDAP makes a lot of sense
 		for the UNIX administrator who is still learning the craft and is migrating from MS Windows.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583543"></a><a name="id2583545"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583558"></a><a name="id2583560"></a></td><td align="left" valign="top"><p>
 		Why are the Windows domain RID portions not the same as the UNIX UID?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Samba uses a well-known public algorithm for assigning RIDs from UIDs and GIDs.
@@ -2843,7 +2843,7 @@ veto oplock files = /*.pdf/*.PST/
 		assignment used the calculation: RID = UID x 2 + 1000. Of course, Samba does
 		permit you to override that to some extent. See the <code class="filename">smb.conf</code> man page entry
 		for <em class="parameter"><code>algorithmic rid base</code></em>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583579"></a><a name="id2583581"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583593"></a><a name="id2583596"></a></td><td align="left" valign="top"><p>
 		Printer configuration examples all show printing to the HP port 9100. Does this
 		mean that I must have HP printers for these solutions to work?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -2853,7 +2853,7 @@ veto oplock files = /*.pdf/*.PST/
 		inkjet printer. Use the appropriate device URI (Universal Resource Interface)
 		argument to the <code class="constant">lpadmin -v</code> option that is right for your
 		printer.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583608"></a><a name="id2583610"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583622"></a><a name="id2583625"></a></td><td align="left" valign="top"><p>
 		Is folder redirection dangerous? I've heard that you can lose your data that way.
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The only loss of data I know of that involved folder redirection was caused by
@@ -2863,16 +2863,16 @@ veto oplock files = /*.pdf/*.PST/
 		he declined to move the data because he thought it was still in the local profile
 		folder. That was not the case, so by declining to move the data back, he wiped out
 		the data. You cannot hold the tool responsible for that. Caveat emptor still applies.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583635"></a><a name="id2583637"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2583650"></a><a name="id2583652"></a></td><td align="left" valign="top"><p>
 		Is it really necessary to set a local Group Policy to exclude the redirected
 		folders from the roaming profile?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Yes. If you do not do this, the data will still be copied from the network folder
 		(share) to the local cached copy of the profile.
-		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2581828" href="#id2581828" class="para">11</a>] </sup>
+		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2581834" href="#id2581834" class="para">11</a>] </sup>
 			There is an alternate method by which a default user profile can be added to the
 			<code class="constant">NETLOGON</code> share. This facility in the Windows System tool 
 			permits profiles to be exported. The export target may be a particular user or 
 			group profile share point or else the <code class="constant">NETLOGON</code> share. 
 			In this case, the profile directory must be named <code class="constant">Default User</code>.
-			</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Big500users.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="ExNetworks.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="net2000users.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�4.�The 500-User Office�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�6.�A Distributed 2000-User Network</td></tr></table></div></body></html>
+			</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Big500users.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="ExNetworks.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="2000users.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�4.�The 500-User Office�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�6.�A Distributed 2000-User Network</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png b/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png
new file mode 100644
index 0000000000..cf6bf8ba12
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/Charity-Network.png b/docs/htmldocs/Samba3-ByExample/images/Charity-Network.png
new file mode 100644
index 0000000000..eaabea6169
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/Charity-Network.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/HostAnnouncment.png b/docs/htmldocs/Samba3-ByExample/images/HostAnnouncment.png
new file mode 100644
index 0000000000..56f9fb8576
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/HostAnnouncment.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/NullConnect.png b/docs/htmldocs/Samba3-ByExample/images/NullConnect.png
new file mode 100644
index 0000000000..5320fc6db1
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/NullConnect.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png b/docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png
new file mode 100644
index 0000000000..8b6e86dde1
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/UserConnect.png b/docs/htmldocs/Samba3-ByExample/images/UserConnect.png
new file mode 100644
index 0000000000..0b9acce15e
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/UserConnect.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/UserMgrNT4.png b/docs/htmldocs/Samba3-ByExample/images/UserMgrNT4.png
new file mode 100644
index 0000000000..516c75b4b1
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/UserMgrNT4.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture.png b/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture.png
new file mode 100644
index 0000000000..3b6dc3ae56
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture2.png b/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture2.png
new file mode 100644
index 0000000000..b9b82c2287
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/WINREPRESSME-Capture2.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/WindowsXP-NullConnection.png b/docs/htmldocs/Samba3-ByExample/images/WindowsXP-NullConnection.png
new file mode 100644
index 0000000000..76d1ac2c9a
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/WindowsXP-NullConnection.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/WindowsXP-UserConnection.png b/docs/htmldocs/Samba3-ByExample/images/WindowsXP-UserConnection.png
new file mode 100644
index 0000000000..d60fefc659
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/WindowsXP-UserConnection.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/XP-screen001.png b/docs/htmldocs/Samba3-ByExample/images/XP-screen001.png
new file mode 100644
index 0000000000..6f0fe58e78
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/XP-screen001.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/acct2net.png b/docs/htmldocs/Samba3-ByExample/images/acct2net.png
new file mode 100644
index 0000000000..2c1cd6c558
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/acct2net.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png b/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png
new file mode 100644
index 0000000000..b10f33ff24
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png b/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png
new file mode 100644
index 0000000000..9b5b15beae
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png b/docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png
new file mode 100644
index 0000000000..7c407e13b7
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png b/docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png
new file mode 100644
index 0000000000..ccbf65095a
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/ch8-migration.png b/docs/htmldocs/Samba3-ByExample/images/ch8-migration.png
new file mode 100644
index 0000000000..b0e449cac4
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/ch8-migration.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap4-net.png b/docs/htmldocs/Samba3-ByExample/images/chap4-net.png
new file mode 100644
index 0000000000..e6c5a77fc0
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap4-net.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap5-net.png b/docs/htmldocs/Samba3-ByExample/images/chap5-net.png
new file mode 100644
index 0000000000..163f9fafb4
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap5-net.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap6-net.png b/docs/htmldocs/Samba3-ByExample/images/chap6-net.png
new file mode 100644
index 0000000000..cd7fcc9fbf
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap6-net.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png b/docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png
new file mode 100644
index 0000000000..43a317db2b
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap7-net-Ar.png b/docs/htmldocs/Samba3-ByExample/images/chap7-net-Ar.png
new file mode 100644
index 0000000000..2f4d80f47b
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap7-net-Ar.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap7-net2-Br.png b/docs/htmldocs/Samba3-ByExample/images/chap7-net2-Br.png
new file mode 100644
index 0000000000..a75a47dc5d
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap7-net2-Br.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png b/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png
new file mode 100644
index 0000000000..a82ac485a7
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png b/docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png
new file mode 100644
index 0000000000..d487d17ec0
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/imc-usermanager2.png b/docs/htmldocs/Samba3-ByExample/images/imc-usermanager2.png
new file mode 100644
index 0000000000..3cfcc6a6ec
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/imc-usermanager2.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-config.png b/docs/htmldocs/Samba3-ByExample/images/lam-config.png
new file mode 100644
index 0000000000..15f989bf37
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-config.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-group-members.png b/docs/htmldocs/Samba3-ByExample/images/lam-group-members.png
new file mode 100644
index 0000000000..cab8e42fc7
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-group-members.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-groups.png b/docs/htmldocs/Samba3-ByExample/images/lam-groups.png
new file mode 100644
index 0000000000..da17b19a77
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-groups.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-hosts.png b/docs/htmldocs/Samba3-ByExample/images/lam-hosts.png
new file mode 100644
index 0000000000..27806eb9ab
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-hosts.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-login.png b/docs/htmldocs/Samba3-ByExample/images/lam-login.png
new file mode 100644
index 0000000000..cce500fc43
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-login.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/lam-users.png b/docs/htmldocs/Samba3-ByExample/images/lam-users.png
new file mode 100644
index 0000000000..0ca4b437ec
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/lam-users.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/openmag.png b/docs/htmldocs/Samba3-ByExample/images/openmag.png
new file mode 100644
index 0000000000..52eca30c35
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/openmag.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/wxpp001.png b/docs/htmldocs/Samba3-ByExample/images/wxpp001.png
new file mode 100644
index 0000000000..2e689a17e2
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/wxpp001.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/wxpp004.png b/docs/htmldocs/Samba3-ByExample/images/wxpp004.png
new file mode 100644
index 0000000000..656f67942e
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/wxpp004.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/wxpp006.png b/docs/htmldocs/Samba3-ByExample/images/wxpp006.png
new file mode 100644
index 0000000000..a20b3ed583
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/wxpp006.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/wxpp007.png b/docs/htmldocs/Samba3-ByExample/images/wxpp007.png
new file mode 100644
index 0000000000..cf41352220
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/wxpp007.png
diff --git a/docs/htmldocs/Samba3-ByExample/images/wxpp008.png b/docs/htmldocs/Samba3-ByExample/images/wxpp008.png
new file mode 100644
index 0000000000..9958c7c873
--- /dev/null
+++ b/docs/htmldocs/Samba3-ByExample/images/wxpp008.png
diff --git a/docs/htmldocs/Samba3-ByExample/index.html b/docs/htmldocs/Samba3-ByExample/index.html
index 48198c11d1..2195ac2c35 100644
--- a/docs/htmldocs/Samba3-ByExample/index.html
+++ b/docs/htmldocs/Samba3-ByExample/index.html
@@ -1,47 +1,47 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba-3 by Example</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="next" href="pr01.html" title="About the Cover Artwork"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba-3 by Example</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="S3bE"></a>Samba-3 by Example</h1></div><div><h2 class="subtitle">Practical Exercises in Successful Samba Deployment</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div><div><p class="pubdate">July, 2006</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">About the Cover Artwork</a></span></dt><dt><span class="preface"><a href="pr02.html">Acknowledgments</a></span></dt><dt><span class="preface"><a href="pr03.html">Foreword</a></span></dt><dd><dl><dt><span class="sect1"><a href="pr03.html#id2501062">By John M. Weathersby, Executive Director, OSSI</a></span></dt></dl></dd><dt><span class="preface"><a href="preface.html">Preface</a></span></dt><dd><dl><dt><span class="sect1"><a href="preface.html#id2501251">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2498970">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2498857">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498889">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498954">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2550647">Conventions Used</a></span></dt></dl></dd><dt><span class="part"><a href="ExNetworks.html">I. Example Network Configurations</a></span></dt><dd><dl><dt><span class="chapter"><a href="simple.html">1. No-Frills Samba Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="simple.html#id2550843">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550883">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550925">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551634">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554969">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="small.html">2. Small Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="small.html#id2555439">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555462">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555522">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555570">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555768">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555790">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557337">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557985">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558010">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558084">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="secure.html">3. Secure Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="secure.html#id2558563">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558614">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558848">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558863">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559289">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559329">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560183">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564645">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564707">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="Big500users.html">4. The 500-User Office</a></span></dt><dd><dl><dt><span class="sect1"><a href="Big500users.html#id2565229">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565274">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565373">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565409">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565612">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565635">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566362">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566927">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570125">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570184">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="happy.html">5. Making Happy Users</a></span></dt><dd><dl><dt><span class="sect1"><a href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571164">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571262">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571399">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573730">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573745">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573925">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580771">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580791">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580886">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581130">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581241">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581375">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582445">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583127">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583163">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583197">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583303">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="net2000users.html">6. A Distributed 2000-User Network</a></span></dt><dd><dl><dt><span class="sect1"><a href="net2000users.html#id2583726">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2583756">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2583824">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2584098">Technical Issues</a></span></dt><dt><span class="sect2"><a href="net2000users.html#id2585046">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2585064">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="net2000users.html#id2588223">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="net2000users.html#id2588370">Questions and Answers</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="DMSMig.html">II. Domain Members, Updating Samba and Migration</a></span></dt><dd><dl><dt><span class="chapter"><a href="unixclients.html">7. Adding Domain Member Servers and Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="unixclients.html#id2589228">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589282">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589317">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589345">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2589994">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590094">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596918">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596972">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrades.html">8. Updating Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrades.html#id2598125">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598221">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599550">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600245">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600542">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600746">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601160">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ntmigration.html">9. Migrating NT4 Domain to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntmigration.html#id2601332">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601417">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601472">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601658">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601981">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2602007">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2605013">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605051">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="nw4migration.html">10. Migrating NetWare Server to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="nw4migration.html#id2606026">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606137">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606228">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606305">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606495">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606504">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="RefSection.html">III. Reference Section</a></span></dt><dd><dl><dt><span class="chapter"><a href="kerberos.html">11. Active Directory, Kerberos, and Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="kerberos.html#id2610496">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611138">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611154">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611545">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613169">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613518">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615257">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615391">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="DomApps.html">12. Integrating Additional Services</a></span></dt><dd><dl><dt><span class="sect1"><a href="DomApps.html#id2616020">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616051">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616160">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616193">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616349">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616373">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618225">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618286">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="HA.html">13. Performance, Reliability, and Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="HA.html#id2618805">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2618892">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619366">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619393">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2619868">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620205">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620281">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620352">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620452">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620600">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620704">Key Points Learned</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch14.html">14. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch14.html#id2620874">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621092">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="appendix.html">15. A Collection of Useful Tidbits</a></span></dt><dd><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621811">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622232">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622592">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622604">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622652">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622792">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622851">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623411">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624406">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2624881">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625028">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625113">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="primer.html">16. Networking Primer</a></span></dt><dd><dl><dt><span class="sect1"><a href="primer.html#id2625280">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625441">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625502">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625618">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625744">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627962">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628077">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba-3 by Example</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="next" href="pr01.html" title="About the Cover Artwork"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba-3 by Example</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="S3bE"></a>Samba-3 by Example</h1></div><div><h2 class="subtitle">Practical Exercises in Successful Samba Deployment</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div><div><p class="pubdate">July, 2006</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">About the Cover Artwork</a></span></dt><dt><span class="preface"><a href="pr02.html">Acknowledgments</a></span></dt><dt><span class="preface"><a href="pr03.html">Foreword</a></span></dt><dd><dl><dt><span class="sect1"><a href="pr03.html#id2501052">By John M. Weathersby, Executive Director, OSSI</a></span></dt></dl></dd><dt><span class="preface"><a href="preface.html">Preface</a></span></dt><dd><dl><dt><span class="sect1"><a href="preface.html#id2501240">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2498964">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2498848">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498880">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498945">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2550640">Conventions Used</a></span></dt></dl></dd><dt><span class="part"><a href="ExNetworks.html">I. Example Network Configurations</a></span></dt><dd><dl><dt><span class="chapter"><a href="simple.html">1. No-Frills Samba Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="simple.html#id2550837">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550877">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550918">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551628">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554965">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="small.html">2. Small Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="small.html#id2555435">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555458">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555518">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555566">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555765">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555786">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557330">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557978">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558003">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558077">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="secure.html">3. Secure Office Networking</a></span></dt><dd><dl><dt><span class="sect1"><a href="secure.html#id2558556">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558607">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558840">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559282">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559322">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560176">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564636">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564698">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="Big500users.html">4. The 500-User Office</a></span></dt><dd><dl><dt><span class="sect1"><a href="Big500users.html#id2565220">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565265">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565371">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#id2565407">Technical Issues</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2565610">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2565632">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="Big500users.html#ch5-dnshcp-setup">Installation of DHCP, DNS, and Samba Control Files</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566360">Server Preparation: All Servers</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2566924">Server-Specific Preparation</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5-procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#ch5wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="Big500users.html#id2570124">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="Big500users.html#id2570183">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="happy.html">5. Making Happy Users</a></span></dt><dd><dl><dt><span class="sect1"><a href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></span></dt><dt><span class="sect1"><a href="happy.html#id2571163">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571261">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2571398">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2571856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573734">Political Issues</a></span></dt><dt><span class="sect2"><a href="happy.html#id2573749">Installation Checklist</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2573929">Samba Server Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></span></dt><dt><span class="sect2"><a href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></span></dt><dt><span class="sect2"><a href="happy.html#sbehap-ptrcfg">Printer Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a></span></dt><dt><span class="sect1"><a href="happy.html#id2580776">Miscellaneous Server Preparation Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#id2580797">Configuring Directory Share Point Roots</a></span></dt><dt><span class="sect2"><a href="happy.html#id2580892">Configuring Profile Directories</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581136">Preparation of Logon Scripts</a></span></dt><dt><span class="sect2"><a href="happy.html#id2581247">Assigning User Rights and Privileges</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2581381">Windows Client Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582451">Configure Delete Cached Profiles on Logout</a></span></dt><dt><span class="sect2"><a href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583133">Software Installation</a></span></dt><dt><span class="sect2"><a href="happy.html#id2583169">Roll-out Image Creation</a></span></dt></dl></dd><dt><span class="sect1"><a href="happy.html#id2583203">Key Points Learned</a></span></dt><dt><span class="sect1"><a href="happy.html#id2583318">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="2000users.html">6. A Distributed 2000-User Network</a></span></dt><dd><dl><dt><span class="sect1"><a href="2000users.html#id2583740">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2583770">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2583839">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2584112">Technical Issues</a></span></dt><dt><span class="sect2"><a href="2000users.html#id2585057">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2585074">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="2000users.html#id2588234">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="2000users.html#id2588381">Questions and Answers</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="DMSMig.html">II. Domain Members, Updating Samba and Migration</a></span></dt><dd><dl><dt><span class="chapter"><a href="unixclients.html">7. Adding Domain Member Servers and Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="unixclients.html#id2589239">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589292">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589328">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589356">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2590005">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590105">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596886">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596940">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrades.html">8. Updating Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrades.html#id2598100">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598196">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599525">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600227">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600519">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600723">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601137">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ntmigration.html">9. Migrating NT4 Domain to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntmigration.html#id2601309">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601394">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601449">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601635">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601958">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601984">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604990">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605028">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="nw4migration.html">10. Migrating NetWare Server to Samba-3</a></span></dt><dd><dl><dt><span class="sect1"><a href="nw4migration.html#id2606004">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606120">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606233">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606310">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606500">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606509">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="RefSection.html">III. Reference Section</a></span></dt><dd><dl><dt><span class="chapter"><a href="kerberos.html">11. Active Directory, Kerberos, and Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="kerberos.html#id2610586">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611237">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611253">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611650">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613280">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613629">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615382">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615516">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="DomApps.html">12. Integrating Additional Services</a></span></dt><dd><dl><dt><span class="sect1"><a href="DomApps.html#id2616145">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616176">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616287">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#id2616320">Technical Issues</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2616476">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2616493">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></span></dt><dt><span class="sect2"><a href="DomApps.html#id2618345">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="DomApps.html#id2618406">Questions and Answers</a></span></dt></dl></dd><dt><span class="chapter"><a href="HA.html">13. Performance, Reliability, and Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="HA.html#id2618932">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619030">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619530">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620006">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620334">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620409">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620480">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620581">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620728">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620832">Key Points Learned</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch14.html">14. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch14.html#id2621002">Free Support</a></span></dt><dt><span class="sect1"><a href="ch14.html#id2621220">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="appendix.html">15. A Collection of Useful Tidbits</a></span></dt><dd><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621928">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622349">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622689">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622700">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622749">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622889">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622948">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623534">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624531">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2625006">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625153">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625237">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="primer.html">16. Networking Primer</a></span></dt><dd><dl><dt><span class="sect1"><a href="primer.html#id2625404">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625565">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625625">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625742">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625868">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2628086">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628200">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
     GNU General Public License version 3
-  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2628743">A. 
+  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2628866">A. 
     Preamble
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628888">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629012">A. 
     TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628892">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629015">A. 
     0. Definitions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2628984">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629108">A. 
     1. Source Code.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629082">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629206">A. 
     2. Basic Permissions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629122">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629246">A. 
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629154">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629281">A. 
     4. Conveying Verbatim Copies.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629181">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629308">A. 
     5. Conveying Modified Source Versions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629277">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629404">A. 
     6. Conveying Non-Source Forms.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629466">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629594">A. 
      7. Additional Terms.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629602">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629729">A. 
      8. Termination.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629646">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629773">A. 
      9. Acceptance Not Required for Having Copies.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629675">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629792">A. 
      10. Automatic Licensing of Downstream Recipients.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629727">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629844">A. 
     11. Patents.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629872">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629990">A. 
     12. No Surrender of Others&#8217; Freedom.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629894">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
     13. Use with the ???TITLE??? Affero General Public License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629923">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630041">A. 
     14. Revised Versions of this License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2629986">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630103">A. 
     15. Disclaimer of Warranty.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630012">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630129">A. 
     16. Limitation of Liability.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630032">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630150">A. 
     17. Interpretation of Sections 15 and 16.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630049">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630166">A. 
     END OF TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630052">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2630170">A. 
     How to Apply These Terms to Your New Programs
-  </a></span></dt></dl></dd></dl></dd><dt><span class="glossary"><a href="go01.html">Glossary</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="simple.html#charitynet">Charity Administration Office Network</a></dt><dt>1.2. <a href="simple.html#acctingnet2">Accounting Office Network Topology</a></dt><dt>2.1. <a href="small.html#acct2net">Abmas Accounting  52-User Network Topology</a></dt><dt>3.1. <a href="secure.html#ch04net">Abmas Network Topology  130 Users</a></dt><dt>4.1. <a href="Big500users.html#chap05net">Network Topology  500 User Network Using tdbsam passdb backend.</a></dt><dt>5.1. <a href="happy.html#sbehap-LDAPdiag">The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts</a></dt><dt>5.2. <a href="happy.html#chap6net">Network Topology  500 User Network Using ldapsam passdb backend</a></dt><dt>5.3. <a href="happy.html#XP-screen001">Windows XP Professional  User Shared Folders</a></dt><dt>6.1. <a href="net2000users.html#chap7idres">Samba and Authentication Backend Search Pathways</a></dt><dt>6.2. <a href="net2000users.html#ch7singleLDAP">Samba Configuration to Use a Single LDAP Server</a></dt><dt>6.3. <a href="net2000users.html#ch7dualLDAP">Samba Configuration to Use a Dual (Fail-over) LDAP Server</a></dt><dt>6.4. <a href="net2000users.html#ch7dualadd">Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!</a></dt><dt>6.5. <a href="net2000users.html#ch7dualok">Samba Configuration to Use Two LDAP Databases - The result is additive.</a></dt><dt>6.6. <a href="net2000users.html#chap7net">Network Topology  2000 User Complex Design A</a></dt><dt>6.7. <a href="net2000users.html#chap7net2">Network Topology  2000 User Complex Design B</a></dt><dt>7.1. <a href="unixclients.html#ch09openmag">Open Magazine Samba Survey</a></dt><dt>7.2. <a href="unixclients.html#ch9-sambadc">Samba Domain: Samba Member Server</a></dt><dt>7.3. <a href="unixclients.html#ch9-adsdc">Active Directory Domain: Samba Member Server</a></dt><dt>9.1. <a href="ntmigration.html#ch8-migration">Schematic Explaining the net rpc vampire Process</a></dt><dt>9.2. <a href="ntmigration.html#NT4DUM">View of Accounts in NT4 Domain User Manager</a></dt><dt>15.1. <a href="appendix.html#swxpp001">The General Panel.</a></dt><dt>15.2. <a href="appendix.html#swxpp004">The Computer Name Panel.</a></dt><dt>15.3. <a href="appendix.html#swxpp006">The Computer Name Changes Panel</a></dt><dt>15.4. <a href="appendix.html#swxpp007">The Computer Name Changes Panel  Domain MIDEARTH</a></dt><dt>15.5. <a href="appendix.html#swxpp008">Computer Name Changes  User name and Password Panel</a></dt><dt>15.6. <a href="appendix.html#lam-login">The LDAP Account Manager Login Screen</a></dt><dt>15.7. <a href="appendix.html#lam-config">The LDAP Account Manager Configuration Screen</a></dt><dt>15.8. <a href="appendix.html#lam-user">The LDAP Account Manager User Edit Screen</a></dt><dt>15.9. <a href="appendix.html#lam-group">The LDAP Account Manager Group Edit Screen</a></dt><dt>15.10. <a href="appendix.html#lam-group-mem">The LDAP Account Manager Group Membership Edit Screen</a></dt><dt>15.11. <a href="appendix.html#lam-host">The LDAP Account Manager Host Edit Screen</a></dt><dt>15.12. <a href="appendix.html#imcidealx">The IMC Samba User Account Screen</a></dt><dt>16.1. <a href="primer.html#pktcap01">Windows Me  Broadcasts  The First 10 Minutes</a></dt><dt>16.2. <a href="primer.html#pktcap02">Windows Me  Later Broadcast Sample</a></dt><dt>16.3. <a href="primer.html#hostannounce">Typical Windows 9x/Me Host Announcement</a></dt><dt>16.4. <a href="primer.html#nullconnect">Typical Windows 9x/Me NULL SessionSetUp AndX Request</a></dt><dt>16.5. <a href="primer.html#userconnect">Typical Windows 9x/Me User SessionSetUp AndX Request</a></dt><dt>16.6. <a href="primer.html#XPCap01">Typical Windows XP NULL Session Setup AndX Request</a></dt><dt>16.7. <a href="primer.html#XPCap02">Typical Windows XP User Session Setup AndX Request</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1. <a href="preface.html#pref-new">Samba Changes  3.0.2 to 3.0.20</a></dt><dt>1.1. <a href="simple.html#acctingnet">Accounting Office Network Information</a></dt><dt>3.1. <a href="secure.html#chap4netid">Abmas.US ISP Information</a></dt><dt>3.2. <a href="secure.html#namedrscfiles">DNS (named) Resource Files</a></dt><dt>4.1. <a href="Big500users.html#ch5-filelocations">Domain: MEGANET, File Locations for Servers</a></dt><dt>5.1. <a href="happy.html#sbehap-privs">Current Privilege Capabilities</a></dt><dt>5.2. <a href="happy.html#oldapreq">Required OpenLDAP Linux Packages</a></dt><dt>5.3. <a href="happy.html#sbehap-bigacct">Abmas Network Users and Groups</a></dt><dt>5.4. <a href="happy.html#proffold">Default Profile Redirections</a></dt><dt>9.1. <a href="ntmigration.html#ch8-vampire">Samba smb.conf Scripts Essential to Samba Operation</a></dt><dt>13.1. <a href="HA.html#ProbList">Effect of Common Problems</a></dt><dt>16.1. <a href="primer.html#capsstats01">Windows Me  Startup Broadcast Capture Statistics</a></dt><dt>16.2. <a href="primer.html#capsstats02">Second Machine (Windows 98)  Capture Statistics</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>1.1. <a href="simple.html#draft-smbconf">Drafting Office smb.conf File</a></dt><dt>1.2. <a href="simple.html#charity-smbconfnew">Charity Administration Office smb.conf New-style File</a></dt><dt>1.3. <a href="simple.html#charity-smbconf">Charity Administration Office smb.conf Old-style File</a></dt><dt>1.4. <a href="simple.html#MEreg">Windows Me  Registry Edit File: Disable Password Caching</a></dt><dt>1.5. <a href="simple.html#acctconf">Accounting Office Network smb.conf Old Style Configuration File</a></dt><dt>2.1. <a href="small.html#initGrps">Script to Map Windows NT Groups to UNIX Groups</a></dt><dt>2.2. <a href="small.html#dhcp01">Abmas Accounting DHCP Server Configuration File  /etc/dhcpd.conf</a></dt><dt>2.3. <a href="small.html#acct2conf">Accounting Office Network smb.conf File  [globals] Section</a></dt><dt>2.4. <a href="small.html#acct3conf">Accounting Office Network smb.conf File  Services and Shares Section</a></dt><dt>3.1. <a href="secure.html#ch4memoryest">Estimation of Memory Requirements</a></dt><dt>3.2. <a href="secure.html#ch4diskest">Estimation of Disk Storage Requirements</a></dt><dt>3.3. <a href="secure.html#ch4natfw">NAT Firewall Configuration Script</a></dt><dt>3.4. <a href="secure.html#promisnet">130 User Network with tdbsam  [globals] Section</a></dt><dt>3.5. <a href="secure.html#promisnetsvca">130 User Network with tdbsam  Services Section Part A</a></dt><dt>3.6. <a href="secure.html#promisnetsvcb">130 User Network with tdbsam  Services Section Part B</a></dt><dt>3.7. <a href="secure.html#ch4initGrps">Script to Map Windows NT Groups to UNIX Groups</a></dt><dt>3.8. <a href="secure.html#prom-dhcp">DHCP Server Configuration File  /etc/dhcpd.conf</a></dt><dt>3.9. <a href="secure.html#ch4namedcfg">DNS Master Configuration File  /etc/named.conf Master Section</a></dt><dt>3.10. <a href="secure.html#ch4namedvarfwd">DNS Master Configuration File  /etc/named.conf Forward Lookup Definition Section</a></dt><dt>3.11. <a href="secure.html#ch4namedvarrev">DNS Master Configuration File  /etc/named.conf Reverse Lookup Definition Section</a></dt><dt>3.12. <a href="secure.html#eth1zone">DNS 192.168.1 Reverse Zone File</a></dt><dt>3.13. <a href="secure.html#eth2zone">DNS 192.168.2 Reverse Zone File</a></dt><dt>3.14. <a href="secure.html#abmasbiz">DNS Abmas.biz Forward Zone File</a></dt><dt>3.15. <a href="secure.html#abmasus">DNS Abmas.us Forward Zone File</a></dt><dt>4.1. <a href="Big500users.html#ch5-massivesmb">Server: MASSIVE (PDC), File: /etc/samba/smb.conf</a></dt><dt>4.2. <a href="Big500users.html#ch5-dc-common">Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf</a></dt><dt>4.3. <a href="Big500users.html#ch5-commonsmb">Common Samba Configuration File: /etc/samba/common.conf</a></dt><dt>4.4. <a href="Big500users.html#ch5-bldg1-smb">Server: BLDG1 (Member), File: smb.conf</a></dt><dt>4.5. <a href="Big500users.html#ch5-bldg2-smb">Server: BLDG2 (Member), File: smb.conf</a></dt><dt>4.6. <a href="Big500users.html#ch5-dommem-smb">Common Domain Member Include File: dom-mem.conf</a></dt><dt>4.7. <a href="Big500users.html#massive-dhcp">Server: MASSIVE, File: dhcpd.conf</a></dt><dt>4.8. <a href="Big500users.html#bldg1dhcp">Server: BLDG1, File: dhcpd.conf</a></dt><dt>4.9. <a href="Big500users.html#bldg2dhcp">Server: BLDG2, File: dhcpd.conf</a></dt><dt>4.10. <a href="Big500users.html#massive-nameda">Server: MASSIVE, File: named.conf, Part: A</a></dt><dt>4.11. <a href="Big500users.html#massive-namedb">Server: MASSIVE, File: named.conf, Part: B</a></dt><dt>4.12. <a href="Big500users.html#massive-namedc">Server: MASSIVE, File: named.conf, Part: C</a></dt><dt>4.13. <a href="Big500users.html#abmasbizdns">Forward Zone File: abmas.biz.hosts</a></dt><dt>4.14. <a href="Big500users.html#abmasusdns">Forward Zone File: abmas.biz.hosts</a></dt><dt>4.15. <a href="Big500users.html#bldg12nameda">Servers: BLDG1/BLDG2, File: named.conf, Part: A</a></dt><dt>4.16. <a href="Big500users.html#bldg12namedb">Servers: BLDG1/BLDG2, File: named.conf, Part: B</a></dt><dt>4.17. <a href="Big500users.html#ch5-initgrps">Initialize Groups Script, File: /etc/samba/initGrps.sh</a></dt><dt>5.1. <a href="happy.html#sbehap-dbconf">LDAP DB_CONFIG File</a></dt><dt>5.2. <a href="happy.html#sbehap-slapdconf">LDAP Master Configuration File  /etc/openldap/slapd.conf Part A</a></dt><dt>5.3. <a href="happy.html#sbehap-slapdconf2">LDAP Master Configuration File  /etc/openldap/slapd.conf Part B</a></dt><dt>5.4. <a href="happy.html#sbehap-nss01">Configuration File for NSS LDAP Support  /etc/ldap.conf</a></dt><dt>5.5. <a href="happy.html#sbehap-nss02">Configuration File for NSS LDAP Clients Support  /etc/ldap.conf</a></dt><dt>5.6. <a href="happy.html#sbehap-massive-smbconfa">LDAP Based smb.conf File, Server: MASSIVE  global Section: Part A</a></dt><dt>5.7. <a href="happy.html#sbehap-massive-smbconfb">LDAP Based smb.conf File, Server: MASSIVE  global Section: Part B</a></dt><dt>5.8. <a href="happy.html#sbehap-bldg1-smbconf">LDAP Based smb.conf File, Server: BLDG1</a></dt><dt>5.9. <a href="happy.html#sbehap-bldg2-smbconf">LDAP Based smb.conf File, Server: BLDG2</a></dt><dt>5.10. <a href="happy.html#sbehap-shareconfa">LDAP Based smb.conf File, Shares Section  Part A</a></dt><dt>5.11. <a href="happy.html#sbehap-shareconfb">LDAP Based smb.conf File, Shares Section  Part B</a></dt><dt>5.12. <a href="happy.html#sbehap-ldifadd">LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</a></dt><dt>6.1. <a href="net2000users.html#ch7-LDAP-master">LDAP Master Server Configuration File  /etc/openldap/slapd.conf</a></dt><dt>6.2. <a href="net2000users.html#ch7-LDAP-slave">LDAP Slave Configuration File  /etc/openldap/slapd.conf</a></dt><dt>6.3. <a href="net2000users.html#ch7-massmbconfA">Primary Domain Controller smb.conf File  Part A</a></dt><dt>6.4. <a href="net2000users.html#ch7-massmbconfB">Primary Domain Controller smb.conf File  Part B</a></dt><dt>6.5. <a href="net2000users.html#ch7-massmbconfC">Primary Domain Controller smb.conf File  Part C</a></dt><dt>6.6. <a href="net2000users.html#ch7-slvsmbocnfA">Backup Domain Controller smb.conf File  Part A</a></dt><dt>6.7. <a href="net2000users.html#ch7-slvsmbocnfB">Backup Domain Controller smb.conf File  Part B</a></dt><dt>7.1. <a href="unixclients.html#ch9-sdmsdc">Samba Domain Member in Samba Domain Using LDAP  smb.conf File</a></dt><dt>7.2. <a href="unixclients.html#ch9-ldifadd">LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</a></dt><dt>7.3. <a href="unixclients.html#ch9-sdmlcnf">Configuration File for NSS LDAP Support  /etc/ldap.conf</a></dt><dt>7.4. <a href="unixclients.html#ch9-sdmnss">NSS using LDAP for Identity Resolution  File: /etc/nsswitch.conf</a></dt><dt>7.5. <a href="unixclients.html#ch0-NT4DSDM">Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain</a></dt><dt>7.6. <a href="unixclients.html#ch0-NT4DSCM">Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain</a></dt><dt>7.7. <a href="unixclients.html#ch9-adssdm">Samba Domain Member smb.conf File for Active Directory Membership</a></dt><dt>7.8. <a href="unixclients.html#sbe-idmapridex">Example smb.conf File Using idmap_rid</a></dt><dt>7.9. <a href="unixclients.html#sbeunxa">Typical ADS Style Domain smb.conf File</a></dt><dt>7.10. <a href="unixclients.html#sbewinbindex">ADS Membership Using RFC2307bis Identity Resolution smb.conf File</a></dt><dt>7.11. <a href="unixclients.html#ch9-pamwnbdlogin">SUSE: PAM login Module Using Winbind</a></dt><dt>7.12. <a href="unixclients.html#ch9-pamwbndxdm">SUSE: PAM xdm Module Using Winbind</a></dt><dt>7.13. <a href="unixclients.html#ch9-rhsysauth">Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind</a></dt><dt>9.1. <a href="ntmigration.html#sbent4smb">NT4 Migration Samba-3 Server smb.conf  Part: A</a></dt><dt>9.2. <a href="ntmigration.html#sbent4smb2">NT4 Migration Samba-3 Server smb.conf  Part: B</a></dt><dt>9.3. <a href="ntmigration.html#sbentslapd">NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf  Part A</a></dt><dt>9.4. <a href="ntmigration.html#sbentslapd2">NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf  Part B</a></dt><dt>9.5. <a href="ntmigration.html#sbrntldapconf">NT4 Migration NSS LDAP File: /etc/ldap.conf</a></dt><dt>9.6. <a href="ntmigration.html#sbentnss">NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)</a></dt><dt>9.7. <a href="ntmigration.html#sbentnss2">NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)</a></dt><dt>10.1. <a href="nw4migration.html#sbeamg">A Rough Tool to Create an LDIF File from the System Account Files</a></dt><dt>10.2. <a href="nw4migration.html#ch8ldap">NSS LDAP Control File  /etc/ldap.conf</a></dt><dt>10.3. <a href="nw4migration.html#sbepu2">The PAM Control File /etc/security/pam_unix2.conf</a></dt><dt>10.4. <a href="nw4migration.html#ch8smbconf">Samba Configuration File  smb.conf Part A</a></dt><dt>10.5. <a href="nw4migration.html#ch8smbconf2">Samba Configuration File  smb.conf Part B</a></dt><dt>10.6. <a href="nw4migration.html#ch8smbconf3">Samba Configuration File  smb.conf Part C</a></dt><dt>10.7. <a href="nw4migration.html#ch8smbconf4">Samba Configuration File  smb.conf Part D</a></dt><dt>10.8. <a href="nw4migration.html#ch8smbconf5">Samba Configuration File  smb.conf Part E</a></dt><dt>10.9. <a href="nw4migration.html#sbersync">Rsync Script</a></dt><dt>10.10. <a href="nw4migration.html#sbexcld">Rsync Files Exclusion List  /root/excludes.txt</a></dt><dt>10.11. <a href="nw4migration.html#ch8ideal">Idealx smbldap-tools Control File  Part A</a></dt><dt>10.12. <a href="nw4migration.html#ch8ideal2">Idealx smbldap-tools Control File  Part B</a></dt><dt>10.13. <a href="nw4migration.html#ch8ideal3">Idealx smbldap-tools Control File  Part C</a></dt><dt>10.14. <a href="nw4migration.html#ch8ideal4">Idealx smbldap-tools Control File  Part D</a></dt><dt>10.15. <a href="nw4migration.html#ch8kix">Kixtart Control File  File: logon.kix</a></dt><dt>10.16. <a href="nw4migration.html#ch8kix2">Kixtart Control File  File: main.kix</a></dt><dt>10.17. <a href="nw4migration.html#ch8kix3">Kixtart Control File  File: setup.kix, Part A</a></dt><dt>10.18. <a href="nw4migration.html#ch8kix3b">Kixtart Control File  File: setup.kix, Part B</a></dt><dt>10.19. <a href="nw4migration.html#ch8kix4">Kixtart Control File  File: acct.kix</a></dt><dt>12.1. <a href="DomApps.html#ch10-krb5conf">Kerberos Configuration  File: /etc/krb5.conf</a></dt><dt>12.2. <a href="DomApps.html#ch10-smbconf">Samba Configuration  File: /etc/samba/smb.conf</a></dt><dt>12.3. <a href="DomApps.html#ch10-etcnsscfg">NSS Configuration File Extract  File: /etc/nsswitch.conf</a></dt><dt>12.4. <a href="DomApps.html#etcsquidcfg">Squid Configuration File Extract  /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]</a></dt><dt>12.5. <a href="DomApps.html#etcsquid2">Squid Configuration File extract  File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]</a></dt><dt>15.1. <a href="appendix.html#ch12SL">A Useful Samba Control Script for SUSE Linux</a></dt><dt>15.2. <a href="appendix.html#ch12RHscript">A Sample Samba Control Script for Red Hat Linux</a></dt><dt>15.3. <a href="appendix.html#loopback">DNS Localhost Forward Zone File: /var/lib/named/localhost.zone</a></dt><dt>15.4. <a href="appendix.html#dnsloopy">DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone</a></dt><dt>15.5. <a href="appendix.html#roothint">DNS Root Name Server Hint File: /var/lib/named/root.hint</a></dt><dt>15.6. <a href="appendix.html#sbehap-ldapreconfa">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part A</a></dt><dt>15.7. <a href="appendix.html#sbehap-ldapreconfb">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part B</a></dt><dt>15.8. <a href="appendix.html#sbehap-ldapreconfc">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part C</a></dt><dt>15.9. <a href="appendix.html#sbehap-ldifpata">LDIF Pattern File Used to Pre-configure LDAP  Part A</a></dt><dt>15.10. <a href="appendix.html#sbehap-ldifpatb">LDIF Pattern File Used to Pre-configure LDAP  Part B</a></dt><dt>15.11. <a href="appendix.html#lamcfg">Example LAM Configuration File  config.cfg</a></dt><dt>15.12. <a href="appendix.html#lamconf">LAM Profile Control File  lam.conf</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�About the Cover Artwork</td></tr></table></div></body></html>
+  </a></span></dt></dl></dd></dl></dd><dt><span class="glossary"><a href="go01.html">Glossary</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="simple.html#charitynet">Charity Administration Office Network</a></dt><dt>1.2. <a href="simple.html#acctingnet2">Accounting Office Network Topology</a></dt><dt>2.1. <a href="small.html#acct2net">Abmas Accounting  52-User Network Topology</a></dt><dt>3.1. <a href="secure.html#ch04net">Abmas Network Topology  130 Users</a></dt><dt>4.1. <a href="Big500users.html#chap05net">Network Topology  500 User Network Using tdbsam passdb backend.</a></dt><dt>5.1. <a href="happy.html#sbehap-LDAPdiag">The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts</a></dt><dt>5.2. <a href="happy.html#chap6net">Network Topology  500 User Network Using ldapsam passdb backend</a></dt><dt>5.3. <a href="happy.html#XP-screen001">Windows XP Professional  User Shared Folders</a></dt><dt>6.1. <a href="2000users.html#chap7idres">Samba and Authentication Backend Search Pathways</a></dt><dt>6.2. <a href="2000users.html#ch7singleLDAP">Samba Configuration to Use a Single LDAP Server</a></dt><dt>6.3. <a href="2000users.html#ch7dualLDAP">Samba Configuration to Use a Dual (Fail-over) LDAP Server</a></dt><dt>6.4. <a href="2000users.html#ch7dualadd">Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!</a></dt><dt>6.5. <a href="2000users.html#ch7dualok">Samba Configuration to Use Two LDAP Databases - The result is additive.</a></dt><dt>6.6. <a href="2000users.html#chap7net">Network Topology  2000 User Complex Design A</a></dt><dt>6.7. <a href="2000users.html#chap7net2">Network Topology  2000 User Complex Design B</a></dt><dt>7.1. <a href="unixclients.html#ch09openmag">Open Magazine Samba Survey</a></dt><dt>7.2. <a href="unixclients.html#ch9-sambadc">Samba Domain: Samba Member Server</a></dt><dt>7.3. <a href="unixclients.html#ch9-adsdc">Active Directory Domain: Samba Member Server</a></dt><dt>9.1. <a href="ntmigration.html#ch8-migration">Schematic Explaining the net rpc vampire Process</a></dt><dt>9.2. <a href="ntmigration.html#NT4DUM">View of Accounts in NT4 Domain User Manager</a></dt><dt>15.1. <a href="appendix.html#swxpp001">The General Panel.</a></dt><dt>15.2. <a href="appendix.html#swxpp004">The Computer Name Panel.</a></dt><dt>15.3. <a href="appendix.html#swxpp006">The Computer Name Changes Panel</a></dt><dt>15.4. <a href="appendix.html#swxpp007">The Computer Name Changes Panel  Domain MIDEARTH</a></dt><dt>15.5. <a href="appendix.html#swxpp008">Computer Name Changes  User name and Password Panel</a></dt><dt>15.6. <a href="appendix.html#lam-login">The LDAP Account Manager Login Screen</a></dt><dt>15.7. <a href="appendix.html#lam-config">The LDAP Account Manager Configuration Screen</a></dt><dt>15.8. <a href="appendix.html#lam-user">The LDAP Account Manager User Edit Screen</a></dt><dt>15.9. <a href="appendix.html#lam-group">The LDAP Account Manager Group Edit Screen</a></dt><dt>15.10. <a href="appendix.html#lam-group-mem">The LDAP Account Manager Group Membership Edit Screen</a></dt><dt>15.11. <a href="appendix.html#lam-host">The LDAP Account Manager Host Edit Screen</a></dt><dt>15.12. <a href="appendix.html#imcidealx">The IMC Samba User Account Screen</a></dt><dt>16.1. <a href="primer.html#pktcap01">Windows Me  Broadcasts  The First 10 Minutes</a></dt><dt>16.2. <a href="primer.html#pktcap02">Windows Me  Later Broadcast Sample</a></dt><dt>16.3. <a href="primer.html#hostannounce">Typical Windows 9x/Me Host Announcement</a></dt><dt>16.4. <a href="primer.html#nullconnect">Typical Windows 9x/Me NULL SessionSetUp AndX Request</a></dt><dt>16.5. <a href="primer.html#userconnect">Typical Windows 9x/Me User SessionSetUp AndX Request</a></dt><dt>16.6. <a href="primer.html#XPCap01">Typical Windows XP NULL Session Setup AndX Request</a></dt><dt>16.7. <a href="primer.html#XPCap02">Typical Windows XP User Session Setup AndX Request</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1. <a href="preface.html#pref-new">Samba Changes  3.0.2 to 3.0.20</a></dt><dt>1.1. <a href="simple.html#acctingnet">Accounting Office Network Information</a></dt><dt>3.1. <a href="secure.html#chap4netid">Abmas.US ISP Information</a></dt><dt>3.2. <a href="secure.html#namedrscfiles">DNS (named) Resource Files</a></dt><dt>4.1. <a href="Big500users.html#ch5-filelocations">Domain: MEGANET, File Locations for Servers</a></dt><dt>5.1. <a href="happy.html#sbehap-privs">Current Privilege Capabilities</a></dt><dt>5.2. <a href="happy.html#oldapreq">Required OpenLDAP Linux Packages</a></dt><dt>5.3. <a href="happy.html#sbehap-bigacct">Abmas Network Users and Groups</a></dt><dt>5.4. <a href="happy.html#proffold">Default Profile Redirections</a></dt><dt>9.1. <a href="ntmigration.html#ch8-vampire">Samba smb.conf Scripts Essential to Samba Operation</a></dt><dt>13.1. <a href="HA.html#ProbList">Effect of Common Problems</a></dt><dt>16.1. <a href="primer.html#capsstats01">Windows Me  Startup Broadcast Capture Statistics</a></dt><dt>16.2. <a href="primer.html#capsstats02">Second Machine (Windows 98)  Capture Statistics</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>1.1. <a href="simple.html#draft-smbconf">Drafting Office smb.conf File</a></dt><dt>1.2. <a href="simple.html#charity-smbconfnew">Charity Administration Office smb.conf New-style File</a></dt><dt>1.3. <a href="simple.html#charity-smbconf">Charity Administration Office smb.conf Old-style File</a></dt><dt>1.4. <a href="simple.html#MEreg">Windows Me  Registry Edit File: Disable Password Caching</a></dt><dt>1.5. <a href="simple.html#acctconf">Accounting Office Network smb.conf Old Style Configuration File</a></dt><dt>2.1. <a href="small.html#initGrps">Script to Map Windows NT Groups to UNIX Groups</a></dt><dt>2.2. <a href="small.html#dhcp01">Abmas Accounting DHCP Server Configuration File  /etc/dhcpd.conf</a></dt><dt>2.3. <a href="small.html#acct2conf">Accounting Office Network smb.conf File  [globals] Section</a></dt><dt>2.4. <a href="small.html#acct3conf">Accounting Office Network smb.conf File  Services and Shares Section</a></dt><dt>3.1. <a href="secure.html#ch4memoryest">Estimation of Memory Requirements</a></dt><dt>3.2. <a href="secure.html#ch4diskest">Estimation of Disk Storage Requirements</a></dt><dt>3.3. <a href="secure.html#ch4natfw">NAT Firewall Configuration Script</a></dt><dt>3.4. <a href="secure.html#promisnet">130 User Network with tdbsam  [globals] Section</a></dt><dt>3.5. <a href="secure.html#promisnetsvca">130 User Network with tdbsam  Services Section Part A</a></dt><dt>3.6. <a href="secure.html#promisnetsvcb">130 User Network with tdbsam  Services Section Part B</a></dt><dt>3.7. <a href="secure.html#ch4initGrps">Script to Map Windows NT Groups to UNIX Groups</a></dt><dt>3.8. <a href="secure.html#prom-dhcp">DHCP Server Configuration File  /etc/dhcpd.conf</a></dt><dt>3.9. <a href="secure.html#ch4namedcfg">DNS Master Configuration File  /etc/named.conf Master Section</a></dt><dt>3.10. <a href="secure.html#ch4namedvarfwd">DNS Master Configuration File  /etc/named.conf Forward Lookup Definition Section</a></dt><dt>3.11. <a href="secure.html#ch4namedvarrev">DNS Master Configuration File  /etc/named.conf Reverse Lookup Definition Section</a></dt><dt>3.12. <a href="secure.html#eth1zone">DNS 192.168.1 Reverse Zone File</a></dt><dt>3.13. <a href="secure.html#eth2zone">DNS 192.168.2 Reverse Zone File</a></dt><dt>3.14. <a href="secure.html#abmasbiz">DNS Abmas.biz Forward Zone File</a></dt><dt>3.15. <a href="secure.html#abmasus">DNS Abmas.us Forward Zone File</a></dt><dt>4.1. <a href="Big500users.html#ch5-massivesmb">Server: MASSIVE (PDC), File: /etc/samba/smb.conf</a></dt><dt>4.2. <a href="Big500users.html#ch5-dc-common">Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf</a></dt><dt>4.3. <a href="Big500users.html#ch5-commonsmb">Common Samba Configuration File: /etc/samba/common.conf</a></dt><dt>4.4. <a href="Big500users.html#ch5-bldg1-smb">Server: BLDG1 (Member), File: smb.conf</a></dt><dt>4.5. <a href="Big500users.html#ch5-bldg2-smb">Server: BLDG2 (Member), File: smb.conf</a></dt><dt>4.6. <a href="Big500users.html#ch5-dommem-smb">Common Domain Member Include File: dom-mem.conf</a></dt><dt>4.7. <a href="Big500users.html#massive-dhcp">Server: MASSIVE, File: dhcpd.conf</a></dt><dt>4.8. <a href="Big500users.html#bldg1dhcp">Server: BLDG1, File: dhcpd.conf</a></dt><dt>4.9. <a href="Big500users.html#bldg2dhcp">Server: BLDG2, File: dhcpd.conf</a></dt><dt>4.10. <a href="Big500users.html#massive-nameda">Server: MASSIVE, File: named.conf, Part: A</a></dt><dt>4.11. <a href="Big500users.html#massive-namedb">Server: MASSIVE, File: named.conf, Part: B</a></dt><dt>4.12. <a href="Big500users.html#massive-namedc">Server: MASSIVE, File: named.conf, Part: C</a></dt><dt>4.13. <a href="Big500users.html#abmasbizdns">Forward Zone File: abmas.biz.hosts</a></dt><dt>4.14. <a href="Big500users.html#abmasusdns">Forward Zone File: abmas.biz.hosts</a></dt><dt>4.15. <a href="Big500users.html#bldg12nameda">Servers: BLDG1/BLDG2, File: named.conf, Part: A</a></dt><dt>4.16. <a href="Big500users.html#bldg12namedb">Servers: BLDG1/BLDG2, File: named.conf, Part: B</a></dt><dt>4.17. <a href="Big500users.html#ch5-initgrps">Initialize Groups Script, File: /etc/samba/initGrps.sh</a></dt><dt>5.1. <a href="happy.html#sbehap-dbconf">LDAP DB_CONFIG File</a></dt><dt>5.2. <a href="happy.html#sbehap-slapdconf">LDAP Master Configuration File  /etc/openldap/slapd.conf Part A</a></dt><dt>5.3. <a href="happy.html#sbehap-slapdconf2">LDAP Master Configuration File  /etc/openldap/slapd.conf Part B</a></dt><dt>5.4. <a href="happy.html#sbehap-nss01">Configuration File for NSS LDAP Support  /etc/ldap.conf</a></dt><dt>5.5. <a href="happy.html#sbehap-nss02">Configuration File for NSS LDAP Clients Support  /etc/ldap.conf</a></dt><dt>5.6. <a href="happy.html#sbehap-massive-smbconfa">LDAP Based smb.conf File, Server: MASSIVE  global Section: Part A</a></dt><dt>5.7. <a href="happy.html#sbehap-massive-smbconfb">LDAP Based smb.conf File, Server: MASSIVE  global Section: Part B</a></dt><dt>5.8. <a href="happy.html#sbehap-bldg1-smbconf">LDAP Based smb.conf File, Server: BLDG1</a></dt><dt>5.9. <a href="happy.html#sbehap-bldg2-smbconf">LDAP Based smb.conf File, Server: BLDG2</a></dt><dt>5.10. <a href="happy.html#sbehap-shareconfa">LDAP Based smb.conf File, Shares Section  Part A</a></dt><dt>5.11. <a href="happy.html#sbehap-shareconfb">LDAP Based smb.conf File, Shares Section  Part B</a></dt><dt>5.12. <a href="happy.html#sbehap-ldifadd">LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</a></dt><dt>6.1. <a href="2000users.html#ch7-LDAP-master">LDAP Master Server Configuration File  /etc/openldap/slapd.conf</a></dt><dt>6.2. <a href="2000users.html#ch7-LDAP-slave">LDAP Slave Configuration File  /etc/openldap/slapd.conf</a></dt><dt>6.3. <a href="2000users.html#ch7-massmbconfA">Primary Domain Controller smb.conf File  Part A</a></dt><dt>6.4. <a href="2000users.html#ch7-massmbconfB">Primary Domain Controller smb.conf File  Part B</a></dt><dt>6.5. <a href="2000users.html#ch7-massmbconfC">Primary Domain Controller smb.conf File  Part C</a></dt><dt>6.6. <a href="2000users.html#ch7-slvsmbocnfA">Backup Domain Controller smb.conf File  Part A</a></dt><dt>6.7. <a href="2000users.html#ch7-slvsmbocnfB">Backup Domain Controller smb.conf File  Part B</a></dt><dt>7.1. <a href="unixclients.html#ch9-sdmsdc">Samba Domain Member in Samba Domain Using LDAP  smb.conf File</a></dt><dt>7.2. <a href="unixclients.html#ch9-ldifadd">LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</a></dt><dt>7.3. <a href="unixclients.html#ch9-sdmlcnf">Configuration File for NSS LDAP Support  /etc/ldap.conf</a></dt><dt>7.4. <a href="unixclients.html#ch9-sdmnss">NSS using LDAP for Identity Resolution  File: /etc/nsswitch.conf</a></dt><dt>7.5. <a href="unixclients.html#ch0-NT4DSDM">Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain</a></dt><dt>7.6. <a href="unixclients.html#ch0-NT4DSCM">Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain</a></dt><dt>7.7. <a href="unixclients.html#ch9-adssdm">Samba Domain Member smb.conf File for Active Directory Membership</a></dt><dt>7.8. <a href="unixclients.html#sbe-idmapridex">Example smb.conf File Using idmap_rid</a></dt><dt>7.9. <a href="unixclients.html#sbeunxa">Typical ADS Style Domain smb.conf File</a></dt><dt>7.10. <a href="unixclients.html#sbewinbindex">ADS Membership Using RFC2307bis Identity Resolution smb.conf File</a></dt><dt>7.11. <a href="unixclients.html#ch9-pamwnbdlogin">SUSE: PAM login Module Using Winbind</a></dt><dt>7.12. <a href="unixclients.html#ch9-pamwbndxdm">SUSE: PAM xdm Module Using Winbind</a></dt><dt>7.13. <a href="unixclients.html#ch9-rhsysauth">Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind</a></dt><dt>9.1. <a href="ntmigration.html#sbent4smb">NT4 Migration Samba-3 Server smb.conf  Part: A</a></dt><dt>9.2. <a href="ntmigration.html#sbent4smb2">NT4 Migration Samba-3 Server smb.conf  Part: B</a></dt><dt>9.3. <a href="ntmigration.html#sbentslapd">NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf  Part A</a></dt><dt>9.4. <a href="ntmigration.html#sbentslapd2">NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf  Part B</a></dt><dt>9.5. <a href="ntmigration.html#sbrntldapconf">NT4 Migration NSS LDAP File: /etc/ldap.conf</a></dt><dt>9.6. <a href="ntmigration.html#sbentnss">NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)</a></dt><dt>9.7. <a href="ntmigration.html#sbentnss2">NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)</a></dt><dt>10.1. <a href="nw4migration.html#sbeamg">A Rough Tool to Create an LDIF File from the System Account Files</a></dt><dt>10.2. <a href="nw4migration.html#ch8ldap">NSS LDAP Control File  /etc/ldap.conf</a></dt><dt>10.3. <a href="nw4migration.html#sbepu2">The PAM Control File /etc/security/pam_unix2.conf</a></dt><dt>10.4. <a href="nw4migration.html#ch8smbconf">Samba Configuration File  smb.conf Part A</a></dt><dt>10.5. <a href="nw4migration.html#ch8smbconf2">Samba Configuration File  smb.conf Part B</a></dt><dt>10.6. <a href="nw4migration.html#ch8smbconf3">Samba Configuration File  smb.conf Part C</a></dt><dt>10.7. <a href="nw4migration.html#ch8smbconf4">Samba Configuration File  smb.conf Part D</a></dt><dt>10.8. <a href="nw4migration.html#ch8smbconf5">Samba Configuration File  smb.conf Part E</a></dt><dt>10.9. <a href="nw4migration.html#sbersync">Rsync Script</a></dt><dt>10.10. <a href="nw4migration.html#sbexcld">Rsync Files Exclusion List  /root/excludes.txt</a></dt><dt>10.11. <a href="nw4migration.html#ch8ideal">Idealx smbldap-tools Control File  Part A</a></dt><dt>10.12. <a href="nw4migration.html#ch8ideal2">Idealx smbldap-tools Control File  Part B</a></dt><dt>10.13. <a href="nw4migration.html#ch8ideal3">Idealx smbldap-tools Control File  Part C</a></dt><dt>10.14. <a href="nw4migration.html#ch8ideal4">Idealx smbldap-tools Control File  Part D</a></dt><dt>10.15. <a href="nw4migration.html#ch8kix">Kixtart Control File  File: logon.kix</a></dt><dt>10.16. <a href="nw4migration.html#ch8kix2">Kixtart Control File  File: main.kix</a></dt><dt>10.17. <a href="nw4migration.html#ch8kix3">Kixtart Control File  File: setup.kix, Part A</a></dt><dt>10.18. <a href="nw4migration.html#ch8kix3b">Kixtart Control File  File: setup.kix, Part B</a></dt><dt>10.19. <a href="nw4migration.html#ch8kix4">Kixtart Control File  File: acct.kix</a></dt><dt>12.1. <a href="DomApps.html#ch10-krb5conf">Kerberos Configuration  File: /etc/krb5.conf</a></dt><dt>12.2. <a href="DomApps.html#ch10-smbconf">Samba Configuration  File: /etc/samba/smb.conf</a></dt><dt>12.3. <a href="DomApps.html#ch10-etcnsscfg">NSS Configuration File Extract  File: /etc/nsswitch.conf</a></dt><dt>12.4. <a href="DomApps.html#etcsquidcfg">Squid Configuration File Extract  /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]</a></dt><dt>12.5. <a href="DomApps.html#etcsquid2">Squid Configuration File extract  File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]</a></dt><dt>15.1. <a href="appendix.html#ch12SL">A Useful Samba Control Script for SUSE Linux</a></dt><dt>15.2. <a href="appendix.html#ch12RHscript">A Sample Samba Control Script for Red Hat Linux</a></dt><dt>15.3. <a href="appendix.html#loopback">DNS Localhost Forward Zone File: /var/lib/named/localhost.zone</a></dt><dt>15.4. <a href="appendix.html#dnsloopy">DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone</a></dt><dt>15.5. <a href="appendix.html#roothint">DNS Root Name Server Hint File: /var/lib/named/root.hint</a></dt><dt>15.6. <a href="appendix.html#sbehap-ldapreconfa">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part A</a></dt><dt>15.7. <a href="appendix.html#sbehap-ldapreconfb">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part B</a></dt><dt>15.8. <a href="appendix.html#sbehap-ldapreconfc">LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh  Part C</a></dt><dt>15.9. <a href="appendix.html#sbehap-ldifpata">LDIF Pattern File Used to Pre-configure LDAP  Part A</a></dt><dt>15.10. <a href="appendix.html#sbehap-ldifpatb">LDIF Pattern File Used to Pre-configure LDAP  Part B</a></dt><dt>15.11. <a href="appendix.html#lamcfg">Example LAM Configuration File  config.cfg</a></dt><dt>15.12. <a href="appendix.html#lamconf">LAM Profile Control File  lam.conf</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�About the Cover Artwork</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/ix01.html b/docs/htmldocs/Samba3-ByExample/ix01.html
index 28a0d1b141..26daf725c4 100644
--- a/docs/htmldocs/Samba3-ByExample/ix01.html
+++ b/docs/htmldocs/Samba3-ByExample/ix01.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2630726"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>%LOGONSERVER%, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>%USERNAME%, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2572664">Profile Changes</a></dt><dt>%USERPROFILE%, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>/data/ldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>/etc/cups/mime.convs, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/cups/mime.types, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/dhcpd.conf, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>/etc/exports, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>/etc/group, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>/etc/hosts, <a class="indexterm" href="simple.html#id2551061">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>/etc/krb5.conf, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>/etc/ldap.conf, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>/etc/mime.convs, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>/etc/mime.types, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>/etc/named.conf, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></dt><dt>/etc/nsswitch.conf, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>/etc/openldap/slapd.conf, <a class="indexterm" href="happy.html#id2573240">Debugging LDAP</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>/etc/passwd, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>/etc/rc.d/boot.local, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>/etc/rc.d/rc.local, <a class="indexterm" href="small.html#id2555790">Implementation</a></dt><dt>/etc/resolv.conf, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a></dt><dt>/etc/samba, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/etc/samba/secrets.tdb, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>/etc/samba/smbusers, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a></dt><dt>/etc/shadow, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a></dt><dt>/etc/squid/squid.conf, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>/etc/syslog.conf, <a class="indexterm" href="happy.html#id2573240">Debugging LDAP</a></dt><dt>/etc/xinetd.d, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>/lib/libnss_ldap.so.2, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>/opt/IDEALX/sbin, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>/proc/sys/net/ipv4/ip_forward, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>/usr/bin, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/lib/samba, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/local, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/local/samba, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/local/samba/var/locks, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>/usr/sbin, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/share, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/share/samba/swat, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/usr/share/swat, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/var/cache/samba, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>/var/lib/samba, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>/var/log/ldaplogs, <a class="indexterm" href="happy.html#id2573240">Debugging LDAP</a></dt><dt>/var/log/samba, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>8-bit, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt>, <a class="indexterm" href="simple.html#id2551061">Implementation</a>, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a>, <a class="indexterm" href="Big500users.html#id2565635">Implementation</a>, <a class="indexterm" href="happy.html#sbehap-ppc">Addition of Machines to the Domain</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617564">NSS Configuration</a></dt><dd><dl><dt>Domain account, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>liability, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>logon, <a class="indexterm" href="simple.html#id2551953">Implementation</a></dt><dt>problem, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>transparent inter-operability, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>abmas-netfw.sh, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>accept, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a></dt><dt>accepts liability, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>access, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>access control, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a>, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>Access Control Lists (see ACLs)</dt><dt>access control settings, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>access controls, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>accessible, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>account, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dd><dl><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></dd><dt>account credentials, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>account information, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>account names, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>account policies, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>accountable, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>accounts</dt><dd><dl><dt>authoritative, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Domain, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>machine, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>manage, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>user, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt></dl></dd><dt>ACL, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>ACLs, <a class="indexterm" href="happy.html#id2583197">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>acquisitions, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Act!, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>ACT! database, <a class="indexterm" href="appendix.html#id2625028">Act! Database Sharing</a></dt><dt>Act!Diag, <a class="indexterm" href="appendix.html#id2625028">Act! Database Sharing</a></dt><dt>Active Directory, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2589282">Assignment Tasks</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dd><dl><dt>authentication, <a class="indexterm" href="DomApps.html#id2617829">Squid Configuration</a></dt><dt>domain, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>join, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>management tools, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>realm, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>Replacement, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>server, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>Server, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>tree, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt></dl></dd><dt>active directory, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>AD printer publishing, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>ADAM, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a></dt><dt>add group script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add machine script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>Add Printer Wizard</dt><dd><dl><dt>APW, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>add user script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add user to group script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>adduser, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>adequate precautions, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a></dt><dt>administrative installation, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>administrative rights, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>administrator, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a></dt><dt>ADMT, <a class="indexterm" href="upgrades.html#id2601160">Migration of Samba Accounts to Active Directory</a></dt><dt>ADS, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></dd><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>affordability, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>alarm, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>algorithm, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>allow trusted domains, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>alternative, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>analysis, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>anonymous connection, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>Apache Web server, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>appliance mode, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>application server, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>application servers, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>application/octet-stream, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>APW, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>arp, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>assessment, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>assistance, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>assumptions, <a class="indexterm" href="HA.html#id2620704">Key Points Learned</a></dt><dt>authconfig, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>authenticate, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>authenticated, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a></dt><dt>authenticated connection, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>authentication, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617564">NSS Configuration</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dd><dl><dt>plain-text, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt></dl></dd><dt>authentication process, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt><dt>authentication protocols, <a class="indexterm" href="DomApps.html#id2618225">Key Points Learned</a></dt><dt>authoritative, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>authorized location, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>auto-generated SID, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>automatically allocate, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>availability, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>backends, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>background communication, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>Backup, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Backup Domain Controller (see BDC)</dt><dt>bandwidth, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a></dt><dd><dl><dt>requirements, <a class="indexterm" href="net2000users.html#id2584137">User Needs</a></dt></dl></dd><dt>bandwidth calculations, <a class="indexterm" href="secure.html#id2559135">Hardware Requirements</a></dt><dt>BDC, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2573925">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="net2000users.html#id2588223">Key Points Learned</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dt>benefit, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>best practices, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>bias, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>binary database, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>binary files, <a class="indexterm" href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></dt><dt>binary package, <a class="indexterm" href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></dt><dt>bind interfaces only, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>broadcast, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>directed, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>mailslot, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>broadcast messages, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>broadcast storms, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>broken, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>broken behavior, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>browse, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>browse master, <a class="indexterm" href="primer.html#id2625878">Findings</a></dt><dt>Browse Master, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>browse.dat, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a></dt><dt>Browser Election Service, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>browsing, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="primer.html#id2625502">Assignment Tasks</a></dt><dt>budgetted, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>bug fixes, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>bug report, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>cache, <a class="indexterm" href="appendix.html#id2625113">Opportunistic Locking Controls</a></dt><dt>cache directories, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>caching, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>case-sensitive, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>centralized storage, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>character set, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>check samba daemons, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>check-point, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>check-point controls, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>Checkpoint Controls, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>chgrp, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>chkconfig, <a class="indexterm" href="simple.html#id2551061">Implementation</a>, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>chmod, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>choice, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>chown, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>CIFS, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="primer.html#id2625878">Findings</a></dt><dt>cifsfs, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>clean database, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>clients per DC, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>Clock skew, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>cluster, <a class="indexterm" href="HA.html#id2618805">Introduction</a></dt><dt>clustering, <a class="indexterm" href="HA.html#id2618805">Introduction</a>, <a class="indexterm" href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>code maintainer, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>codepage, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>collision rates, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>commercial, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>commercial software, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>commercial support, <a class="indexterm" href="ch14.html">Samba Support</a>, <a class="indexterm" href="ch14.html#id2621092">Commercial Support</a></dt><dt>Common Internet File System (see CIFS)</dt><dt>comparison</dt><dd><dl><dt>Active Directory &amp; OpenLDAP, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt></dl></dd><dt>compat, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>compatible, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>compile-time, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dt>complexities, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>compromise, <a class="indexterm" href="happy.html#id2571164">Introduction</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>computer account, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>Computer Management, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>computer name, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>condemns, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>conferences, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>configuration files, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a></dt><dt>configure.pl, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>connection, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>connectivity, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>consequential risk, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>consultant, <a class="indexterm" href="simple.html#id2550925">Drafting Office</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>consumer, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>consumer expects, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>contiguous directory, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>contributions, <a class="indexterm" href="upgrades.html">Updating Samba-3</a></dt><dt>control files, <a class="indexterm" href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></dt><dt>convmv, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>copy, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>corrective action, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>cost, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>cost-benefit, <a class="indexterm" href="nw4migration.html#id2606137">Assignment Tasks</a></dt><dt>country of origin, <a class="indexterm" href="ch14.html#id2621092">Commercial Support</a></dt><dt>Courier-IMAP, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>credential, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>credentials, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>crippled, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>criticism, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Critics, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Cryptographic, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>CUPS, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="small.html#id2558010">Key Points Learned</a>, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dd><dl><dt>queue, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt></dl></dd><dt>cupsd, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>customer expected, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>customers, <a class="indexterm" href="ch14.html">Samba Support</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>daemon control, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>data</dt><dd><dl><dt>corruption, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>integrity, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt></dl></dd><dt>data corruption, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a>, <a class="indexterm" href="appendix.html#id2625028">Act! Database Sharing</a></dt><dt>data integrity, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a>, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>data storage, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>database, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a></dt><dt>database applications, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>DB_CONFIG, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>DCE, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>DDNS (see dynamic DNS)</dt><dt>Debian, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>default installation, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>default password, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>default profile, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>Default User, <a class="indexterm" href="happy.html#id2572664">Profile Changes</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>defective</dt><dd><dl><dt>cables, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>HUBs, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>switches, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt></dl></dd><dt>defects, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>defensible standards, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>defragmentation, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a></dt><dt>delete group script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delete user from group script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delimiter, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>dependability, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>deployment, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>desired security setting, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>development, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>DHCP, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="small.html#id2558010">Key Points Learned</a>, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="Big500users.html#ch5wincfg">Windows Client Configuration</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dd><dl><dt>client, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>relay, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a></dt><dt>Relay Agent, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>request, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>requests, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a></dt><dt>servers, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>traffic, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt></dl></dd><dt>dhcp client validation, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>DHCP Server, <a class="indexterm" href="small.html#id2555790">Implementation</a></dt><dt>DHCP server, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a></dt><dt>diagnostic, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a></dt><dt>diffusion, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>digital rights, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>digital sign'n'seal, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>digits, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>diligence, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>directory, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2589994">Political Issues</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dd><dl><dt>Computers container, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>management, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>People container, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>replication, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>schema, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>server, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>synchronization, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt></dl></dd><dt>directory tree, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>disable, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>disaster recovery, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>disk image, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a></dt><dt>disruptive, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>distributed, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2620352">Distribute Network Load with MSDFS</a></dt><dt>distributed domain, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>DMB, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>DMS, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a></dt><dt>DNS, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a>, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dd><dl><dt>configuration, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>Dynamic, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>dynamic, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>lookup, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>name lookup, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>SRV records, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>suffix, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt></dl></dd><dt>DNS server, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></dt><dt>document the settings, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>documentation, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>documented, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>Domain, <a class="indexterm" href="small.html#id2555570">Technical Issues</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2555570">Technical Issues</a></dt></dl></dd><dt>domain</dt><dd><dl><dt>Active Directory, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>controller, <a class="indexterm" href="upgrades.html#id2600960">Replacing a Domain Controller</a></dt><dt>joining, <a class="indexterm" href="appendix.html">A Collection of Useful Tidbits</a></dt><dt>trusted, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt></dl></dd><dt>Domain accounts, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Domain Administrator, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>Domain Controller, <a class="indexterm" href="small.html#id2558010">Key Points Learned</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a>, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dd><dl><dt>closest, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>domain controller, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>domain controllers, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Domain Controllers, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>Domain Groups</dt><dd><dl><dt>well-known, <a class="indexterm" href="appendix.html#id2622851">Initialization of the LDAP Database</a></dt></dl></dd><dt>Domain join, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>domain master, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></dt><dt>Domain Master Browser (see DMB)</dt><dt>Domain Member, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dd><dl><dt>authoritative</dt><dd><dl><dt>local accounts, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt></dl></dd><dt>client, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt><dt>desktop, <a class="indexterm" href="unixclients.html#id2589228">Introduction</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2589228">Introduction</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>servers, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>workstations, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt></dl></dd><dt>domain member</dt><dd><dl><dt>servers, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt></dl></dd><dt>Domain Member server, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>Domain Member servers, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>domain members, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>domain name space, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>domain replication, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>domain SID, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>Domain SID, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>domain tree, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>Domain User Manager, <a class="indexterm" href="happy.html#id2580886">Configuring Profile Directories</a></dt><dt>Domain users, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>DOS, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>dos2unix, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>down-grade, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a></dt><dt>drive letters, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>drive mapping, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>dumb printing, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>dump, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>duplicate accounts, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>dynamic DNS, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>e-Directory, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a></dt><dt>Easy Software Products, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>economically sustainable, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>eDirectory, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>education, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>election, <a class="indexterm" href="primer.html#id2625878">Findings</a></dt><dt>employment, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>enable, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a></dt><dt>encrypted, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>encrypted password, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>encrypted passwords, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>End User License Agreement (see EULA)</dt><dt>enumerating, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>essential, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>ethereal, <a class="indexterm" href="primer.html#id2625618">Exercises</a></dt><dt>Ethernet switch, <a class="indexterm" href="small.html#id2555570">Technical Issues</a></dt><dt>ethernet switch, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>EULA, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>Everyone, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>Excel, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>exclusive open, <a class="indexterm" href="appendix.html#id2624881">Microsoft Access</a></dt><dt>experiment, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a></dt><dt>export, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>extent, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>External Domains, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>extreme demand, <a class="indexterm" href="HA.html#id2619366">Guidelines for Reliable Samba Operation</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fail, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>fail-over, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>failed, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>failed join, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>failure, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>familiar, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>fatal problem, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>fear, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>fears, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Fedora, <a class="indexterm" href="simple.html#id2550925">Drafting Office</a></dt><dt>FHS, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>file and print server, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>file and print service, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>file caching, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2625113">Opportunistic Locking Controls</a></dt><dt>File Hierarchy System (see FHS)</dt><dt>file locations, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>file permissions, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>file server</dt><dd><dl><dt>read-only, <a class="indexterm" href="simple.html#id2551005">Dissection and Discussion</a></dt></dl></dd><dt>file servers, <a class="indexterm" href="happy.html#id2573925">Samba Server Implementation</a></dt><dt>file system, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dd><dl><dt>access control, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a></dt><dt>Ext3, <a class="indexterm" href="simple.html#id2551061">Implementation</a></dt><dt>permissions, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>file system security, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>filter, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>financial responsibility, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>firewall, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>fix, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>flaws, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>flexibility, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>flush</dt><dd><dl><dt>cache memory, <a class="indexterm" href="appendix.html#id2625113">Opportunistic Locking Controls</a></dt></dl></dd><dt>folder redirection, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>force group, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>force user, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>forced settings, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a></dt><dt>foreign, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>foreign SID, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>forwarded, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>foundation members, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Free Standards Group (see FSG)</dt><dt>free support, <a class="indexterm" href="ch14.html">Samba Support</a>, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>front-end, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dd><dl><dt>server, <a class="indexterm" href="HA.html#id2620352">Distribute Network Load with MSDFS</a></dt></dl></dd><dt>frustration, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a></dt><dt>FSG, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>FTP</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt></dl></dd><dt>full control, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2614876">Using MS Windows Explorer (File Manager)</a></dt><dt>fully qualified, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>functional differences, <a class="indexterm" href="upgrades.html#id2598221">Cautions and Notes</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>generation, <a class="indexterm" href="upgrades.html#id2598221">Cautions and Notes</a></dt><dt>Gentoo, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>getent, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>getfacl, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>getgrnam, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>getpwnam, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>getpwnam(), <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>GID, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>Goettingen, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>government, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>GPL, <a class="indexterm" href="secure.html#id2564093">Comments Regarding Software Terms of Use</a></dt><dt>group account, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>group management, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>group mapping, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>group membership, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>group names, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>group policies, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a></dt><dt>Group Policy, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>Group Policy editor, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a></dt><dt>Group Policy Objects, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a></dt><dt>groupadd, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>groupdel, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>groupmem, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>groupmod, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>GSS-API, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>guest account, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a>, <a class="indexterm" href="primer.html#chap01conc">Dissection and Discussion</a>, <a class="indexterm" href="primer.html#id2628077">Technical Issues</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hackers, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>hardware prices, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>hardware problems, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>Heimdal, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>Heimdal Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>Heimdal kerberos, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a></dt><dt>help, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>helper agent, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>hesiod, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>hierarchy of control, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>high availability, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>hire, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>HKEY_CURRENT_USER, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a></dt><dt>HKEY_LOCAL_MACHINE, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>HKEY_LOCAL_USER, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>host announcement, <a class="indexterm" href="primer.html#id2625502">Assignment Tasks</a>, <a class="indexterm" href="primer.html#id2626531">Findings</a></dt><dt>hostname, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>hosts, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>HUB, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>Hybrid, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>hypothetical, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>Idealx, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dd><dl><dt>smbldap-tools, <a class="indexterm" href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt></dl></dd><dt>identifiers, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>identity, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dd><dl><dt>management, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt></dl></dd><dt>identity management, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2589994">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a></dt><dt>Identity Management, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>Identity management, <a class="indexterm" href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a></dt><dt>Identity resolution, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>Identity resolver, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>IDMAP, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>idmap backend, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>IDMAP backend, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>idmap gid, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>idmap uid, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>idmap_rid, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>IMAP, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a></dt><dt>import, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>income, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>independent expert, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>inetd, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>inetOrgPerson, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a></dt><dt>inheritance, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>initGrps.sh, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>initial credentials, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>inoperative, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>install, <a class="indexterm" href="upgrades.html">Updating Samba-3</a></dt><dt>installation, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>integrate, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>integrity, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>inter-domain, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>inter-operability, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>interactive help, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>interdomain trusts, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>interfaces, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>intermittent, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>internationalization, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>Internet Explorer, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>Internet Information Server, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>interoperability, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>IP forwarding, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>IPC$, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>iptables, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a></dt><dt>IRC, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>isolated, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Italian, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>J</h3><dl><dt>jobs, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>joining a domain, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KDC, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dd><dl><dt>Heimdal, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>interoperability, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>libraries, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>MIT, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>unspecified fields, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt></dl></dd><dt>kerberos, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt></dl></dd><dt>Kerberos ticket, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>kinit, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>Kixtart, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>klist, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>krb5, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a></dt><dt>krb5.conf, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LAM, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dd><dl><dt>configuration editor, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>configuration file, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>login screen, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>opening screen, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>profile, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>wizard, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt></dl></dd><dt>large domain, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>LDAP, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2573007">Preliminary Advice: Dangers Can Be Avoided</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="net2000users.html#id2583726">Introduction</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="net2000users.html#id2588223">Key Points Learned</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2601417">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dd><dl><dt>backend, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>database, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></dt><dt>directory, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>fail-over, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>initial configuration, <a class="indexterm" href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></dt><dt>master, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>master/slave</dt><dd><dl><dt>background communication, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt></dl></dd><dt>preload, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>schema, <a class="indexterm" href="upgrades.html#id2600576">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>secure, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>slave, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>updates, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt></dl></dd><dt>ldap, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>LDAP Account Manager (see LAM)</dt><dt>LDAP backend, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>LDAP database, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>LDAP Interchange Format (see LDIF)</dt><dt>LDAP server, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>LDAP-transfer-LDIF.txt, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>ldap.conf, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapadd, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapsam, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="upgrades.html#id2600576">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601417">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>ldapsam backend, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapsearch, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>LDIF, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2622851">Initialization of the LDAP Database</a></dt><dt>leadership, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Lightweight Directory Access Protocol (see LDAP)</dt><dt>limit, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>Linux desktop, <a class="indexterm" href="unixclients.html#id2589228">Introduction</a></dt><dt>Linux Standards Base (see LSB)</dt><dt>LMB, <a class="indexterm" href="primer.html#id2625878">Findings</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>LMHOSTS, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>load distribution, <a class="indexterm" href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>local accounts, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Local Group Policy, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a></dt><dt>Local Master Announcement, <a class="indexterm" href="primer.html#id2626531">Findings</a></dt><dt>Local Master Browser (see LMB)</dt><dt>localhost, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>lock directory, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>locking</dt><dd><dl><dt>Application level, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Client side, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Server side, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt></dl></dd><dt>logging, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>login, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a></dt><dt>loglevel, <a class="indexterm" href="happy.html#id2573240">Debugging LDAP</a></dt><dt>logon credentials, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>logon hours, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a></dt><dt>logon machines, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>logon path, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>logon process, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt><dt>logon scrip, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a></dt><dt>logon script, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2581130">Preparation of Logon Scripts</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>logon server, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>logon services, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>logon time, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a></dt><dt>logon traffic, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>logon.kix, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>loopback, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>low performance, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>lower-case, <a class="indexterm" href="ntmigration.html#id2602007">Implementation</a></dt><dt>lpadmin, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>LSB, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>machine, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>machine account, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>machine accounts, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>machine secret password, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a></dt><dt>MACHINE.SID, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>mailing list, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>mailing lists, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>managed, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>management, <a class="indexterm" href="unixclients.html#id2589994">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dd><dl><dt>group, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>User, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></dd><dt>mandatory profile, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2580886">Configuring Profile Directories</a></dt><dt>Mandrake, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>mapped drives, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>mapping, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dd><dl><dt>consistent, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt></dl></dd><dt>Mars_NWE, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>master, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>material, <a class="indexterm" href="appendix.html">A Collection of Useful Tidbits</a></dt><dt>memberUID, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>memory requirements, <a class="indexterm" href="secure.html#id2559135">Hardware Requirements</a></dt><dt>merge, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>merged, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>meta-directory, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>meta-service, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>Microsoft Access, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Microsoft Excel, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Microsoft ISA, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a></dt><dt>Microsoft Management Console (see MMC)</dt><dt>Microsoft Office, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>Microsoft Outlook</dt><dd><dl><dt>PST files, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt></dl></dd><dt>migrate, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>migration, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2601332">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dd><dl><dt>objectives, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt></dl></dd><dt>Migration speed, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>mime type, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>mime types, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>missing RPC's, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>MIT, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>MIT Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>MIT kerberos, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a></dt><dt>MIT KRB5, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>mixed mode, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>mixed-mode, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>MMC, <a class="indexterm" href="happy.html#id2582445">Configure Delete Cached Profiles on Logout</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>mobile computing, <a class="indexterm" href="small.html#id2555522">Dissection and Discussion</a></dt><dt>mobility, <a class="indexterm" href="net2000users.html#id2584098">Technical Issues</a></dt><dt>modularization, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>modules, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>MS Access</dt><dd><dl><dt>validate, <a class="indexterm" href="appendix.html#id2624881">Microsoft Access</a></dt></dl></dd><dt>MS Outlook, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt><dt>PST file, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>MS Windows Server 2003, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a></dt><dt>MS Word, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>MSDFS, <a class="indexterm" href="HA.html#id2620352">Distribute Network Load with MSDFS</a></dt><dt>multi-subnet, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>multi-user</dt><dd><dl><dt>access, <a class="indexterm" href="appendix.html#id2624881">Microsoft Access</a></dt><dt>data access, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt></dl></dd><dt>multiple directories, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>multiple domain controllers, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>multiple group mappings, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>mutual assistance, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>My Documents, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a></dt><dt>My Network Places, <a class="indexterm" href="simple.html#id2551953">Implementation</a></dt><dt>mysqlsam, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>name resolution, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2625502">Assignment Tasks</a></dt><dd><dl><dt>Defective, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt></dl></dd><dt>name resolve order, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>name service switch, <a class="indexterm" href="small.html#id2555790">Implementation</a> (see NSS)</dt><dt>named, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a></dt><dt>NAT, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a></dt><dt>native, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>net</dt><dd><dl><dt>ads</dt><dd><dl><dt>info, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>join, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>status, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt></dl></dd><dt>getlocalsid, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></dt><dt>groupmap</dt><dd><dl><dt>add, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a></dt><dt>list, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>modify, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a></dt></dl></dd><dt>rpc</dt><dd><dl><dt>info, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>join, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></dt><dt>vampire, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></dt></dl></dd><dt>setlocalsid, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt></dl></dd><dt>NetBIOS, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>name cache, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>name resolution</dt><dd><dl><dt>delays, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>Node Type, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt></dl></dd><dt>netbios</dt><dd><dl><dt>machine  name, <a class="indexterm" href="upgrades.html#id2599053">Change of hostname</a></dt></dl></dd><dt>netbios forwarding, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>NetBIOS name, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dd><dl><dt>aliases, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt></dl></dd><dt>netbios name, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599053">Change of hostname</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>NETLOGON, <a class="indexterm" href="happy.html#id2572758">Using a Network Default User Profile</a>, <a class="indexterm" href="happy.html#id2581375">Windows Client Configuration</a></dt><dt>netlogon, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>Netlogon, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>netmask, <a class="indexterm" href="simple.html#id2551061">Implementation</a></dt><dt>Netware, <a class="indexterm" href="small.html">Small Office Networking</a></dt><dt>NetWare, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>network</dt><dd><dl><dt>administrators, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>analyzer, <a class="indexterm" href="primer.html#id2625502">Assignment Tasks</a></dt><dt>bandwidth, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>broadcast, <a class="indexterm" href="primer.html#id2625441">Introduction</a></dt><dt>captures, <a class="indexterm" href="primer.html#id2625280">Requirements and Notes</a></dt><dt>collisions, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>load, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>logon, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>logon scripts, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>management, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>multi-segment, <a class="indexterm" href="happy.html#id2571164">Introduction</a></dt><dt>overload, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>performance, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>routed, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>secure, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>segment, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>services, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>sniffer, <a class="indexterm" href="primer.html#id2625280">Requirements and Notes</a></dt><dt>timeout, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>timeouts, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>trace, <a class="indexterm" href="primer.html#id2625502">Assignment Tasks</a></dt><dt>traffic</dt><dd><dl><dt>observation, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></dd><dt>wide-area, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt></dl></dd><dt>Network Address Translation (see NAT)</dt><dt>network administrators, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>network attached storage (see NAS)</dt><dt>network bandwidth</dt><dd><dl><dt>utilization, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>Network Default Profile, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a></dt><dt>network hardware</dt><dd><dl><dt>defective, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>network hygiene, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>network Identities, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>network load factors, <a class="indexterm" href="Big500users.html#id2565373">Dissection and Discussion</a></dt><dt>Network Neighborhood, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>network segment, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dt>network segments, <a class="indexterm" href="secure.html#id2559135">Hardware Requirements</a></dt><dt>network share, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a></dt><dt>networking</dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt></dl></dd><dt>networking hardware</dt><dd><dl><dt>defective, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>networking protocols, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>next generation, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>NextFreeUnixId, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>NFS server, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>NICs, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>NIS, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2589994">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>nis, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>NIS schema, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>NIS server, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>NIS+, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>nisplus, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>NLM, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>nmap, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>nmbd, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>nobody, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>Novell, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a>, <a class="indexterm" href="nw4migration.html#id2606026">Introduction</a></dt><dt>Novell SUSE SLES 9, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>NSS, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617564">NSS Configuration</a> (see same service switch)</dt><dt>nss_ldap, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>nt acl support, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a></dt><dt>NT4 registry, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>NTLM, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>NTLM authentication daemon, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>NTLMSSP, <a class="indexterm" href="DomApps.html#id2618225">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>NTLMSSP_AUTH, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>ntlm_auth, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>NTP, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>NTUSER.DAT, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2572664">Profile Changes</a>, <a class="indexterm" href="happy.html#id2572758">Using a Network Default User Profile</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>NULL connection, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>NULL session, <a class="indexterm" href="primer.html#id2627129">Findings and Comments</a></dt><dt>NULL-Session, <a class="indexterm" href="primer.html#id2627931">Discussion</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>objectClass, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>off-site storage, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Open Magazine, <a class="indexterm" href="unixclients.html">Adding Domain Member Servers and Clients</a></dt><dt>Open Source, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>OpenLDAP, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2589994">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>openldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>OpenOffice, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>operating profiles, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>oplock break, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a></dt><dt>oplocks, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>Oplocks</dt><dd><dl><dt>disabled, <a class="indexterm" href="appendix.html#id2625113">Opportunistic Locking Controls</a></dt></dl></dd><dt>opportunistic</dt><dd><dl><dt>locking, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a></dt></dl></dd><dt>opportunistic locking, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2625028">Act! Database Sharing</a></dt><dt>optimized, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>organizational units, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>OS/2, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>Outlook</dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt></dl></dd><dt>Outlook Address Book, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt><dt>Outlook Express, <a class="indexterm" href="secure.html#id2559289">Political Issues</a>, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt><dt>over-ride, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>over-ride controls, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a></dt><dt>over-rule, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2614876">Using MS Windows Explorer (File Manager)</a></dt><dt>overheads, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a></dt><dt>ownership, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package, <a class="indexterm" href="simple.html#id2551061">Implementation</a></dt><dt>package names, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>packages, <a class="indexterm" href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></dt><dt>PADL, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a></dt><dt>PADL LDAP tools, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>PADL Software, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>paid-for support, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>PAM, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>pam_ldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>pam_ldap.so, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>pam_unix2.so, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dd><dl><dt>use_ldap, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt></dl></dd><dt>parameters, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>passdb backend, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2600576">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601417">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>passdb.tdb, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>passwd, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a></dt><dt>password</dt><dd><dl><dt>backend, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>password caching, <a class="indexterm" href="simple.html#id2551953">Implementation</a></dt><dt>password change, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a></dt><dt>password length, <a class="indexterm" href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>payroll, <a class="indexterm" href="nw4migration.html#id2606026">Introduction</a></dt><dt>pdbedit, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>PDC, <a class="indexterm" href="Big500users.html#id2565274">Assignment Tasks</a>, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2602007">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dt>PDC/BDC ratio, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>PDF, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>performance, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a>, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a>, <a class="indexterm" href="HA.html#id2618805">Introduction</a>, <a class="indexterm" href="HA.html#id2619769">Network Collisions</a></dt><dt>performance degradation, <a class="indexterm" href="kerberos.html#id2613970">Override Controls</a>, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>Perl, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>permission, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>permissions, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dd><dl><dt>excessive, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>group, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>user, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt></dl></dd><dt>Permissions, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>permits, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>permitted group, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>PHP, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>PHP4, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>pile-driver, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>ping, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>pitfalls, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>plain-text, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>Pluggable Authentication Modules (see PAM)</dt><dt>policy, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>poor performance, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>POP3, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a></dt><dt>Posix, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2602007">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>POSIX, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>Posix accounts, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Posix ACLs, <a class="indexterm" href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></dt><dt>PosixAccount, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>posixAccount, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>Postfix, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>Postscript, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>powers, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>practices, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>precaution, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a></dt><dt>presence and leadership, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>price paid, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>primary group, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>principals, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>print filter, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>print queue, <a class="indexterm" href="simple.html#id2551634">Charity Administration Office</a>, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a></dt><dt>print spooler, <a class="indexterm" href="simple.html#id2551634">Charity Administration Office</a></dt><dt>Print Test Page, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>printcap name, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>printer validation, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>printers</dt><dd><dl><dt>Advanced, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>Default Settings, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>General, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>Properties, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>Security, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>Sharing, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>printing, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dd><dl><dt>drag-and-drop, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a>, <a class="indexterm" href="happy.html#id2582625">Uploading Printer Drivers to Samba Servers</a></dt><dt>dumb, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>point-n-click, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>raw, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a></dt></dl></dd><dt>privacy, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>Privilege Attribute Certificates (see PAC)</dt><dt>privilege controls, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>privileged pipe, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>privileges, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2600654">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt><dt>problem report, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>problem resolution, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>product defects, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>professional support, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>profile</dt><dd><dl><dt>default, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a></dt><dt>mandatory, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>roaming, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>profile path, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>profile share, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>profiles, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>profiles share, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>programmer, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>project, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>project maintainers, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Properties, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>proprietary, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>protected, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>protection, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>protocol</dt><dd><dl><dt>negotiation, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>protocol analysis, <a class="indexterm" href="primer.html#id2625280">Requirements and Notes</a></dt><dt>protocols, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>provided services, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>proxy, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>PST file, <a class="indexterm" href="happy.html#id2582129">Configuration of MS Outlook to Relocate PST File</a></dt><dt>public specifications, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>purchase support, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>Qbasic, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>qualified problem, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID, <a class="indexterm" href="secure.html#id2559135">Hardware Requirements</a></dt><dt>RAID controllers, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>Raw Print Through, <a class="indexterm" href="happy.html#id2572816">Installation of Printer Driver Auto-Download</a></dt><dt>raw printing, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>Rbase, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>rcldap, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>realm, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2595411">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>recognize, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>record locking, <a class="indexterm" href="appendix.html#id2624881">Microsoft Access</a></dt><dt>recursively, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Red Hat, <a class="indexterm" href="simple.html#id2550925">Drafting Office</a>, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>Red Hat Fedora Linux, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>Red Hat Linux, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="simple.html#AccountingOffice">Accounting Office</a>, <a class="indexterm" href="happy.html#id2573925">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>redirected folders, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>refereed standards, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>regedit, <a class="indexterm" href="simple.html#id2551953">Implementation</a></dt><dt>regedt32, <a class="indexterm" href="happy.html#id2572664">Profile Changes</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>registry, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dd><dl><dt>keys</dt><dd><dl><dt>SAM, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>SECURITY, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt></dl></dd></dl></dd><dt>registry change, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>Registry Editor, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>registry hacks, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>registry keys, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>reimburse, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>rejected, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>rejoin, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>reliability, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a></dt><dt>remote announce, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>remote browse sync, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>remote procedure call (see RPC)</dt><dt>replicate, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>replicated, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>requesting payment, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>resilient, <a class="indexterm" href="HA.html#id2619366">Guidelines for Reliable Samba Operation</a></dt><dt>resolution, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a></dt><dt>resolve, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="HA.html#id2619404">Bad Hostnames</a></dt><dt>response, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a></dt><dt>responsibility, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>responsible, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>restrict anonymous, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>restricted export, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>Restrictive security, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>reverse DNS, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a></dt><dt>rfc2307bis, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>RID, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>risk, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>road-map, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dd><dl><dt>published, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></dd><dt>roaming profile, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2580886">Configuring Profile Directories</a>, <a class="indexterm" href="net2000users.html#id2584137">User Needs</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>roaming profiles, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="happy.html#id2572363">Roaming Profile Background</a></dt><dt>routed network, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a></dt><dt>router, <a class="indexterm" href="small.html#id2555790">Implementation</a></dt><dt>routers, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>RPC, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>rpc, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>rpcclient, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>RPM, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a></dt><dd><dl><dt>install, <a class="indexterm" href="simple.html#id2551061">Implementation</a></dt></dl></dd><dt>rpm, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>RPMs, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>rpms, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>rsync, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>rsyncd.conf, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>run-time control files, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>safe-guards, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>SAM, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>samba, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dd><dl><dt>starting samba, <a class="indexterm" href="simple.html#id2551061">Implementation</a></dt></dl></dd><dt>Samba, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>Samba accounts, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>samba cluster, <a class="indexterm" href="HA.html#id2618805">Introduction</a></dt><dt>samba control script, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>Samba Domain, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>Samba Domain server, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>Samba RPM Packages, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>Samba Tea, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>sambaDomainName, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>sambaGroupMapping, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>SambaSAMAccount, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>SambaSamAccount, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>sambaSamAccount, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>SambaXP conference, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>SAN, <a class="indexterm" href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>SAS, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>scalability, <a class="indexterm" href="HA.html#id2618805">Introduction</a></dt><dt>scalable, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>schannel, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>schema, <a class="indexterm" href="unixclients.html#id2596006">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2600245">Samba-2.x with LDAP Support</a>, <a class="indexterm" href="upgrades.html#id2600576">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>scripts, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>secondary group, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>secret, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>secrets.tdb, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dt>secure, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>secure account password, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>secure connections, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>secure networking, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>secure networking protocols, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>security, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dd><dl><dt>identifier, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>share mode, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a></dt><dt>user mode, <a class="indexterm" href="simple.html#id2553799">Dissection and Discussion</a></dt></dl></dd><dt>Security, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614585">Using the MMC Computer Management Interface</a></dt><dt>Security Account Manager (see SAM)</dt><dt>security controls, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>security descriptors, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>security fixes, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>security updates, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>SerNet, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>server</dt><dd><dl><dt>domain member, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>stand-alone, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt></dl></dd><dt>service, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dd><dl><dt>smb</dt><dd><dl><dt>start, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a></dt></dl></dd></dl></dd><dt>Service Packs, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>services, <a class="indexterm" href="DomApps.html#id2618225">Key Points Learned</a></dt><dt>services provided, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>session setup, <a class="indexterm" href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>Session Setup, <a class="indexterm" href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a></dt><dt>SessionSetUpAndX, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>set primary group script, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>setfacl, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>severely degrade, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>SFU, <a class="indexterm" href="unixclients.html#id2596292">IDMAP, Active Directory, and MS Services for UNIX 3.5</a></dt><dt>SGID, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a>, <a class="indexterm" href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></dt><dt>shadow-utils, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>Share Access Controls, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>share ACLs, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>share definition, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>Share Definition</dt><dd><dl><dt>Controls, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a></dt></dl></dd><dt>share definition controls, <a class="indexterm" href="kerberos.html#id2613518">Share Definition Controls</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>share level access controls, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>share level ACL, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>Share Permissions, <a class="indexterm" href="kerberos.html#id2613169">Share Access Controls</a></dt><dt>shared resource, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>shares, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>SID, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2594807">IDMAP_RID with Winbind</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599119">Change of Workgroup (Domain) Name</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622851">Initialization of the LDAP Database</a></dt><dt>side effects, <a class="indexterm" href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></dt><dt>Sign'n'seal, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>silent return, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>simple, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>Single Sign-On (see SSO)</dt><dt>slapcat, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>slapd, <a class="indexterm" href="happy.html#id2573240">Debugging LDAP</a></dt><dt>slapd.conf, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>slave, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>slow logon, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>slow network, <a class="indexterm" href="HA.html#id2620452">Hardware Problems</a></dt><dt>slurpd, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>smart printing, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>SMB, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>SMB passwords, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>SMB/CIFS, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>smbclient, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>smbd, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dd><dl><dt>location of files, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt></dl></dd><dt>smbfs, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>smbldap-groupadd, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>smbldap-groupmod, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>smbldap-passwd, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-populate, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-tools, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>smbldap-tools updating, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>smbldap-useradd, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt><dt>smbldap-usermod, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>smbmnt, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>smbmount, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>smbpasswd, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="happy.html#id2576821">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>smbumnt, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>smbumount, <a class="indexterm" href="HA.html#id2618892">Dissection and Discussion</a></dt><dt>SMTP, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a></dt><dt>snap-shot, <a class="indexterm" href="ntmigration.html#id2601472">Dissection and Discussion</a></dt><dt>socket address, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>socket options, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>software, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>solve, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>source code, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>SPNEGO, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>SQL, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>Squid, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2617829">Squid Configuration</a></dt><dt>squid, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>Squid proxy, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>SRVTOOLS.EXE, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="happy.html#id2580886">Configuring Profile Directories</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>SSL, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>stand-alone server, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>starting CUPS, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>starting dhcpd, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>starting samba, <a class="indexterm" href="simple.html#id2551061">Implementation</a>, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dd><dl><dt>nmbd, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>smbd, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>winbindd, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt></dl></dd><dt>startingCUPS, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>startup script, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>sticky bit, <a class="indexterm" href="small.html#id2555790">Implementation</a></dt><dt>storage capacity, <a class="indexterm" href="secure.html#id2559135">Hardware Requirements</a></dt><dt>strategic, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a></dt><dt>strategy, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>straw-man, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a></dt><dt>strict sync, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>stripped, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>strong cryptography, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>subscription, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>SUID, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a>, <a class="indexterm" href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></dt><dt>Sun ONE Identity Server, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>super daemon, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>support, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a>, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>survey, <a class="indexterm" href="unixclients.html">Adding Domain Member Servers and Clients</a></dt><dt>SUSE, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>SUSE Enterprise Linux Server, <a class="indexterm" href="simple.html#id2551634">Charity Administration Office</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a></dt><dt>SUSE Linux, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2573925">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616373">Implementation</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>SWAT, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>sync always, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>synchronization, <a class="indexterm" href="DomApps.html#id2616622">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2620303">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>synchronize, <a class="indexterm" href="net2000users.html#id2584137">User Needs</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>synchronized, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>syslog, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>system level logins, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>system security, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>tattooing, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>TCP/IP, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>tdbdump, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>tdbsam, <a class="indexterm" href="secure.html#id2558863">Technical Issues</a>, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2571262">Assignment Tasks</a>, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2600576">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601658">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>testparm, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="HA.html#id2619868">Samba Configuration</a></dt><dt>ticket, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>time server, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>Tivoli Directory Server, <a class="indexterm" href="happy.html#id2571399">Dissection and Discussion</a></dt><dt>TLS, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>token, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a></dt><dt>tool, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>TOSHARG2, <a class="indexterm" href="simple.html#id2551953">Implementation</a></dt><dt>track record, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>traffic collisions, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>transaction processing, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>transactional, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>transfer, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>translate, <a class="indexterm" href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></dt><dt>traverse, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>tree, <a class="indexterm" href="nw4migration.html#id2606228">Dissection and Discussion</a></dt><dt>Tree Connect, <a class="indexterm" href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a></dt><dt>trust account, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>trusted computing, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Trusted Domains, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>trusted domains, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>trusted third-party, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>trusting, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>turn-around time, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UDP</dt><dd><dl><dt>broadcast, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt></dl></dd><dt>UID, <a class="indexterm" href="simple.html#id2551758">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571022">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>un-join, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>unauthorized activities, <a class="indexterm" href="kerberos.html#id2612822">Kerberos Exposed</a></dt><dt>UNC name, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>unencrypted, <a class="indexterm" href="appendix.html#id2623411">The LDAP Account Manager</a></dt><dt>Unicast, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a></dt><dt>unicode, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>Universal Naming Convention (see UNC name)</dt><dt>UNIX, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a></dt></dl></dd><dt>UNIX accounts, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>UNIX/Linux server, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>unix2dos, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt><dt>unknown, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>unsupported software, <a class="indexterm" href="ch14.html#id2621092">Commercial Support</a></dt><dt>update, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a>, <a class="indexterm" href="upgrades.html#id2598221">Cautions and Notes</a></dt><dt>updates, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>updating smbldap-tools, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>upgrade, <a class="indexterm" href="upgrades.html#id2598125">Introduction</a>, <a class="indexterm" href="upgrades.html#id2598221">Cautions and Notes</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>uppercase, <a class="indexterm" href="ntmigration.html#id2602007">Implementation</a></dt><dt>user</dt><dd><dl><dt>management, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>user account, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>User and Group Controls, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>user credentials, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a></dt><dt>user errors, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>user groups, <a class="indexterm" href="ch14.html#id2620874">Free Support</a></dt><dt>user identities, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt><dt>user logins, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>user management, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>User Manager, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>User Mode, <a class="indexterm" href="secure.html#id2559329">Implementation</a>, <a class="indexterm" href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>useradd, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566940">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>userdel, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>usermod, <a class="indexterm" href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></dt><dt>username, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>username map, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#id2560183">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566362">Server Preparation: All Servers</a></dt><dt>UTF-8, <a class="indexterm" href="upgrades.html#id2599385">International Language Support</a></dt><dt>utilities, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>validate, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>validated, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>validation, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>vampire, <a class="indexterm" href="ntmigration.html#id2605051">Questions and Answers</a></dt><dt>vendor, <a class="indexterm" href="kerberos.html#id2611154">Dissection and Discussion</a></dt><dt>vendors, <a class="indexterm" href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></dt><dt>VFS modules, <a class="indexterm" href="appendix.html#id2621811">Samba System File Location</a></dt><dt>virus, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>VPN, <a class="indexterm" href="net2000users.html#id2583756">Assignment Tasks</a></dt><dt>vulnerabilities, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>wbinfo, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a></dt><dt>weakness, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a></dt><dt>web</dt><dd><dl><dt>caching, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a></dt><dt>proxying, <a class="indexterm" href="DomApps.html#id2616051">Assignment Tasks</a></dt></dl></dd><dt>Web</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dd><dl><dt>access, <a class="indexterm" href="DomApps.html#id2618225">Key Points Learned</a></dt></dl></dd></dl></dd><dt>Web browsers, <a class="indexterm" href="DomApps.html#id2618225">Key Points Learned</a></dt><dt>WebClient, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>WHATSNEW.txt, <a class="indexterm" href="upgrades.html#id2600245">Samba-2.x with LDAP Support</a></dt><dt>white-pages, <a class="indexterm" href="nw4migration.html#id2606305">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>wide-area, <a class="indexterm" href="net2000users.html#id2584137">User Needs</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2588223">Key Points Learned</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>wide-area network, <a class="indexterm" href="HA.html#id2620205">Use and Location of BDCs</a>, <a class="indexterm" href="HA.html#id2620407">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>winbind, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a>, <a class="indexterm" href="unixclients.html#id2589317">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616193">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2617564">NSS Configuration</a></dt><dt>Winbind, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611545">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615257">Key Points Learned</a></dt><dt>winbind trusted domains only, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>winbind use default domain, <a class="indexterm" href="kerberos.html#id2613658">Checkpoint Controls</a></dt><dt>winbindd, <a class="indexterm" href="small.html#id2557337">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600654">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617012">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622232">Starting Samba</a></dt><dt>winbindd_cache.tdb, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>winbindd_idmap.tdb, <a class="indexterm" href="unixclients.html#id2589345">Technical Issues</a></dt><dt>Windows, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt><dt>NT, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a></dt></dl></dd><dt>Windows 2000 ACLs, <a class="indexterm" href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></dt><dt>Windows 2003 Serve, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Windows 200x ACLs, <a class="indexterm" href="kerberos.html#id2615391">Questions and Answers</a></dt><dt>Windows accounts, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>Windows ACLs, <a class="indexterm" href="kerberos.html#id2615047">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Windows Address Book, <a class="indexterm" href="nw4migration.html#id2606568">LDAP Server Configuration</a></dt><dt>Windows ADS Domain, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>Windows clients, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>Windows Explorer, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>Windows explorer, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>Windows security identifier (see SID)</dt><dt>Windows Servers, <a class="indexterm" href="kerberos.html#id2610496">Introduction</a></dt><dt>Windows Services for UNIX (see SUS)</dt><dt>Windows XP, <a class="indexterm" href="small.html#id2555462">Assignment Tasks</a></dt><dt>WINS, <a class="indexterm" href="simple.html#id2551953">Implementation</a>, <a class="indexterm" href="small.html#id2555570">Technical Issues</a>, <a class="indexterm" href="small.html#id2555790">Implementation</a>, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="Big500users.html#id2565409">Technical Issues</a>, <a class="indexterm" href="Big500users.html#ch5wincfg">Windows Client Configuration</a>, <a class="indexterm" href="net2000users.html#id2584231">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>lookup, <a class="indexterm" href="unixclients.html#id2596972">Questions and Answers</a></dt><dt>name resolution, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt><dt>server, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="HA.html#id2619596">Routed Networks</a></dt></dl></dd><dt>WINS server, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="net2000users.html#id2588370">Questions and Answers</a></dt><dt>WINS serving, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>wins support, <a class="indexterm" href="secure.html#id2559329">Implementation</a></dt><dt>wins.dat, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2600758">Replacing a Domain Member Server</a></dt><dt>Wireshark, <a class="indexterm" href="primer.html#id2625280">Requirements and Notes</a></dt><dt>wireshark, <a class="indexterm" href="primer.html#id2625618">Exercises</a></dt><dt>Word, <a class="indexterm" href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></dt><dt>workgroup, <a class="indexterm" href="simple.html#id2551061">Implementation</a>, <a class="indexterm" href="upgrades.html#id2598325">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599119">Change of Workgroup (Domain) Name</a></dt><dt>Workgroup Announcement, <a class="indexterm" href="primer.html#id2626531">Findings</a></dt><dt>workstation, <a class="indexterm" href="unixclients.html#id2590094">Implementation</a></dt><dt>wrapper, <a class="indexterm" href="DomApps.html#id2618286">Questions and Answers</a></dt><dt>write lock, <a class="indexterm" href="appendix.html#id2625113">Opportunistic Locking Controls</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>xinetd, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>XML, <a class="indexterm" href="net2000users.html#id2583824">Dissection and Discussion</a></dt><dt>xmlsam, <a class="indexterm" href="net2000users.html#id2585064">Implementation</a></dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>YaST, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>Yellow Pages, <a class="indexterm" href="net2000users.html#id2584570">Identity Management Needs</a></dt><dt>yellow pages (see NIS)</dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�</td></tr><tr><td width="40%" align="left" valign="top">Glossary�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2630868"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>%LOGONSERVER%, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>%USERNAME%, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2572668">Profile Changes</a></dt><dt>%USERPROFILE%, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>/data/ldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>/etc/cups/mime.convs, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/cups/mime.types, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>/etc/dhcpd.conf, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>/etc/exports, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>/etc/group, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>/etc/hosts, <a class="indexterm" href="simple.html#id2551055">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>/etc/krb5.conf, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>/etc/ldap.conf, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>/etc/mime.convs, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>/etc/mime.types, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>/etc/named.conf, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></dt><dt>/etc/nsswitch.conf, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>/etc/openldap/slapd.conf, <a class="indexterm" href="happy.html#id2573244">Debugging LDAP</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>/etc/passwd, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>/etc/rc.d/boot.local, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>/etc/rc.d/rc.local, <a class="indexterm" href="small.html#id2555786">Implementation</a></dt><dt>/etc/resolv.conf, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a></dt><dt>/etc/samba, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/etc/samba/secrets.tdb, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>/etc/samba/smbusers, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a></dt><dt>/etc/shadow, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a></dt><dt>/etc/squid/squid.conf, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>/etc/syslog.conf, <a class="indexterm" href="happy.html#id2573244">Debugging LDAP</a></dt><dt>/etc/xinetd.d, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>/lib/libnss_ldap.so.2, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>/opt/IDEALX/sbin, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>/proc/sys/net/ipv4/ip_forward, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>/usr/bin, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/lib/samba, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/local, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/local/samba, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/local/samba/var/locks, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>/usr/sbin, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/share, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/share/samba/swat, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/usr/share/swat, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/var/cache/samba, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>/var/lib/samba, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>/var/log/ldaplogs, <a class="indexterm" href="happy.html#id2573244">Debugging LDAP</a></dt><dt>/var/log/samba, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>8-bit, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt>, <a class="indexterm" href="simple.html#id2551055">Implementation</a>, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a>, <a class="indexterm" href="Big500users.html#id2565632">Implementation</a>, <a class="indexterm" href="happy.html#sbehap-ppc">Addition of Machines to the Domain</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617684">NSS Configuration</a></dt><dd><dl><dt>Domain account, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>liability, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>logon, <a class="indexterm" href="simple.html#id2551947">Implementation</a></dt><dt>problem, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>transparent inter-operability, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>abmas-netfw.sh, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>accept, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a></dt><dt>accepts liability, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>access, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>access control, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a>, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>Access Control Lists (see ACLs)</dt><dt>access control settings, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>access controls, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>accessible, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>account, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dd><dl><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></dd><dt>account credentials, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>account information, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>account names, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>account policies, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>accountable, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>accounts</dt><dd><dl><dt>authoritative, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Domain, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>machine, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>manage, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>user, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt></dl></dd><dt>ACL, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>ACLs, <a class="indexterm" href="happy.html#id2583203">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>acquisitions, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Act!, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>ACT! database, <a class="indexterm" href="appendix.html#id2625153">Act! Database Sharing</a></dt><dt>Act!Diag, <a class="indexterm" href="appendix.html#id2625153">Act! Database Sharing</a></dt><dt>Active Directory, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2589292">Assignment Tasks</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dd><dl><dt>authentication, <a class="indexterm" href="DomApps.html#id2617949">Squid Configuration</a></dt><dt>domain, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>join, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>management tools, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>realm, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>Replacement, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>server, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>Server, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>tree, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt></dl></dd><dt>active directory, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>AD printer publishing, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>ADAM, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a></dt><dt>add group script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add machine script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>Add Printer Wizard</dt><dd><dl><dt>APW, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>add user script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>add user to group script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>adduser, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>adequate precautions, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a></dt><dt>administrative installation, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>administrative rights, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>administrator, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a></dt><dt>ADMT, <a class="indexterm" href="upgrades.html#id2601137">Migration of Samba Accounts to Active Directory</a></dt><dt>ADS, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></dd><dt>ADS Domain, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>affordability, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>alarm, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>algorithm, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>allow trusted domains, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>alternative, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>analysis, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>anonymous connection, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>Apache Web server, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>appliance mode, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>application server, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>application servers, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>application/octet-stream, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>APW, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>arp, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>assessment, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>assistance, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>assumptions, <a class="indexterm" href="HA.html#id2620832">Key Points Learned</a></dt><dt>authconfig, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>authenticate, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>authenticated, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a></dt><dt>authenticated connection, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>authentication, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617684">NSS Configuration</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dd><dl><dt>plain-text, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt></dl></dd><dt>authentication process, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt><dt>authentication protocols, <a class="indexterm" href="DomApps.html#id2618345">Key Points Learned</a></dt><dt>authoritative, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>authorized location, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>auto-generated SID, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>automatically allocate, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>availability, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>backends, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>background communication, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>Backup, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Backup Domain Controller (see BDC)</dt><dt>bandwidth, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a></dt><dd><dl><dt>requirements, <a class="indexterm" href="2000users.html#id2584151">User Needs</a></dt></dl></dd><dt>bandwidth calculations, <a class="indexterm" href="secure.html#id2559128">Hardware Requirements</a></dt><dt>BDC, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2573929">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2588234">Key Points Learned</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dt>benefit, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>best practices, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>bias, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>binary database, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>binary files, <a class="indexterm" href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></dt><dt>binary package, <a class="indexterm" href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></dt><dt>bind interfaces only, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>broadcast, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>directed, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>mailslot, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>broadcast messages, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>broadcast storms, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>broken, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>broken behavior, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>browse, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>browse master, <a class="indexterm" href="primer.html#id2626002">Findings</a></dt><dt>Browse Master, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>browse.dat, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a></dt><dt>Browser Election Service, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>browsing, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="primer.html#id2625625">Assignment Tasks</a></dt><dt>budgetted, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>bug fixes, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>bug report, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>cache, <a class="indexterm" href="appendix.html#id2625237">Opportunistic Locking Controls</a></dt><dt>cache directories, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>caching, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>case-sensitive, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>centralized storage, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>character set, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>check samba daemons, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>check-point, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>check-point controls, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>Checkpoint Controls, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>chgrp, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>chkconfig, <a class="indexterm" href="simple.html#id2551055">Implementation</a>, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>chmod, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>choice, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>chown, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>CIFS, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="primer.html#id2626002">Findings</a></dt><dt>cifsfs, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>clean database, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>clients per DC, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>Clock skew, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>cluster, <a class="indexterm" href="HA.html#id2618932">Introduction</a></dt><dt>clustering, <a class="indexterm" href="HA.html#id2618932">Introduction</a>, <a class="indexterm" href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>code maintainer, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>codepage, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>collision rates, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>commercial, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>commercial software, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>commercial support, <a class="indexterm" href="ch14.html">Samba Support</a>, <a class="indexterm" href="ch14.html#id2621220">Commercial Support</a></dt><dt>Common Internet File System (see CIFS)</dt><dt>comparison</dt><dd><dl><dt>Active Directory &amp; OpenLDAP, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt></dl></dd><dt>compat, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>compatible, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>compile-time, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dt>complexities, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>compromise, <a class="indexterm" href="happy.html#id2571163">Introduction</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>computer account, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>Computer Management, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>computer name, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>condemns, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>conferences, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>configuration files, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a></dt><dt>configure.pl, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>connection, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>connectivity, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>consequential risk, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>consultant, <a class="indexterm" href="simple.html#id2550918">Drafting Office</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>consumer, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>consumer expects, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>contiguous directory, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>contributions, <a class="indexterm" href="upgrades.html">Updating Samba-3</a></dt><dt>control files, <a class="indexterm" href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></dt><dt>convmv, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>copy, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>corrective action, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>cost, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>cost-benefit, <a class="indexterm" href="nw4migration.html#id2606120">Assignment Tasks</a></dt><dt>country of origin, <a class="indexterm" href="ch14.html#id2621220">Commercial Support</a></dt><dt>Courier-IMAP, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>credential, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>credentials, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>crippled, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>criticism, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Critics, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Cryptographic, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>CUPS, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="small.html#id2558003">Key Points Learned</a>, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dd><dl><dt>queue, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt></dl></dd><dt>cupsd, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a></dt><dt>customer expected, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>customers, <a class="indexterm" href="ch14.html">Samba Support</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>daemon control, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>data</dt><dd><dl><dt>corruption, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>integrity, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt></dl></dd><dt>data corruption, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a>, <a class="indexterm" href="appendix.html#id2625153">Act! Database Sharing</a></dt><dt>data integrity, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a>, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>data storage, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>database, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a></dt><dt>database applications, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>DB_CONFIG, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>DCE, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>DDNS (see dynamic DNS)</dt><dt>Debian, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>default installation, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>default password, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>default profile, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>Default User, <a class="indexterm" href="happy.html#id2572668">Profile Changes</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>defective</dt><dd><dl><dt>cables, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>HUBs, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>switches, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt></dl></dd><dt>defects, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>defensible standards, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>defragmentation, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a></dt><dt>delete group script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delete user from group script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>delimiter, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>dependability, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>deployment, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>desired security setting, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>development, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>DHCP, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="small.html#id2558003">Key Points Learned</a>, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="Big500users.html#ch5wincfg">Windows Client Configuration</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dd><dl><dt>client, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>relay, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a></dt><dt>Relay Agent, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>request, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>requests, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a></dt><dt>servers, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>traffic, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt></dl></dd><dt>dhcp client validation, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>DHCP Server, <a class="indexterm" href="small.html#id2555786">Implementation</a></dt><dt>DHCP server, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a></dt><dt>diagnostic, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a></dt><dt>diffusion, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>digital rights, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>digital sign'n'seal, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>digits, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>diligence, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>directory, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2590005">Political Issues</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dd><dl><dt>Computers container, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>management, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>People container, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>replication, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>schema, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>server, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>synchronization, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt></dl></dd><dt>directory tree, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>disable, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>disaster recovery, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>disk image, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a></dt><dt>disruptive, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>distributed, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2620480">Distribute Network Load with MSDFS</a></dt><dt>distributed domain, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>DMB, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>DMS, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a></dt><dt>DNS, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a>, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dd><dl><dt>configuration, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>Dynamic, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>dynamic, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>lookup, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>name lookup, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>SRV records, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>suffix, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt></dl></dd><dt>DNS server, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></dt><dt>document the settings, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>documentation, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>documented, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>Domain, <a class="indexterm" href="small.html#id2555566">Technical Issues</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2555566">Technical Issues</a></dt></dl></dd><dt>domain</dt><dd><dl><dt>Active Directory, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>controller, <a class="indexterm" href="upgrades.html#id2600937">Replacing a Domain Controller</a></dt><dt>joining, <a class="indexterm" href="appendix.html">A Collection of Useful Tidbits</a></dt><dt>trusted, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt></dl></dd><dt>Domain accounts, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Domain Administrator, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>Domain Controller, <a class="indexterm" href="small.html#id2558003">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a>, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dd><dl><dt>closest, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>domain controller, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>domain controllers, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Domain Controllers, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>Domain Groups</dt><dd><dl><dt>well-known, <a class="indexterm" href="appendix.html#id2622948">Initialization of the LDAP Database</a></dt></dl></dd><dt>Domain join, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>domain master, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></dt><dt>Domain Master Browser (see DMB)</dt><dt>Domain Member, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dd><dl><dt>authoritative</dt><dd><dl><dt>local accounts, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt></dl></dd><dt>client, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt><dt>desktop, <a class="indexterm" href="unixclients.html#id2589239">Introduction</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2589239">Introduction</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>servers, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>workstations, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt></dl></dd><dt>domain member</dt><dd><dl><dt>servers, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt></dl></dd><dt>Domain Member server, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>Domain Member servers, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>domain members, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>domain name space, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>domain replication, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>domain SID, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>Domain SID, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>domain tree, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>Domain User Manager, <a class="indexterm" href="happy.html#id2580892">Configuring Profile Directories</a></dt><dt>Domain users, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>DOS, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>dos2unix, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>down-grade, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a></dt><dt>drive letters, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>drive mapping, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>dumb printing, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>dump, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>duplicate accounts, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>dynamic DNS, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>e-Directory, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a></dt><dt>Easy Software Products, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>economically sustainable, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>eDirectory, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>education, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>election, <a class="indexterm" href="primer.html#id2626002">Findings</a></dt><dt>employment, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>enable, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a></dt><dt>encrypted, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>encrypted password, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>encrypted passwords, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>End User License Agreement (see EULA)</dt><dt>enumerating, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>essential, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>ethereal, <a class="indexterm" href="primer.html#id2625742">Exercises</a></dt><dt>Ethernet switch, <a class="indexterm" href="small.html#id2555566">Technical Issues</a></dt><dt>ethernet switch, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>EULA, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>Everyone, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>Excel, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>exclusive open, <a class="indexterm" href="appendix.html#id2625006">Microsoft Access</a></dt><dt>experiment, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a></dt><dt>export, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>extent, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>External Domains, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>extreme demand, <a class="indexterm" href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fail, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>fail-over, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>failed, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>failed join, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>failure, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>familiar, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>fatal problem, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>fear, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>fears, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Fedora, <a class="indexterm" href="simple.html#id2550918">Drafting Office</a></dt><dt>FHS, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>file and print server, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>file and print service, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>file caching, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2625237">Opportunistic Locking Controls</a></dt><dt>File Hierarchy System (see FHS)</dt><dt>file locations, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>file permissions, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>file server</dt><dd><dl><dt>read-only, <a class="indexterm" href="simple.html#id2550999">Dissection and Discussion</a></dt></dl></dd><dt>file servers, <a class="indexterm" href="happy.html#id2573929">Samba Server Implementation</a></dt><dt>file system, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dd><dl><dt>access control, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a></dt><dt>Ext3, <a class="indexterm" href="simple.html#id2551055">Implementation</a></dt><dt>permissions, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>file system security, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>filter, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>financial responsibility, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>firewall, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>fix, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>flaws, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>flexibility, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>flush</dt><dd><dl><dt>cache memory, <a class="indexterm" href="appendix.html#id2625237">Opportunistic Locking Controls</a></dt></dl></dd><dt>folder redirection, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>force group, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>force user, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>forced settings, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a></dt><dt>foreign, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>foreign SID, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>forwarded, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>foundation members, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Free Standards Group (see FSG)</dt><dt>free support, <a class="indexterm" href="ch14.html">Samba Support</a>, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>front-end, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dd><dl><dt>server, <a class="indexterm" href="HA.html#id2620480">Distribute Network Load with MSDFS</a></dt></dl></dd><dt>frustration, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a></dt><dt>FSG, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>FTP</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt></dl></dd><dt>full control, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2615000">Using MS Windows Explorer (File Manager)</a></dt><dt>fully qualified, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>functional differences, <a class="indexterm" href="upgrades.html#id2598196">Cautions and Notes</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>generation, <a class="indexterm" href="upgrades.html#id2598196">Cautions and Notes</a></dt><dt>Gentoo, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>getent, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>getfacl, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>getgrnam, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>getpwnam, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>getpwnam(), <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>GID, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>Goettingen, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>government, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>GPL, <a class="indexterm" href="secure.html#id2564084">Comments Regarding Software Terms of Use</a></dt><dt>group account, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>group management, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>group mapping, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>group membership, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>group names, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>group policies, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a></dt><dt>Group Policy, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>Group Policy editor, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a></dt><dt>Group Policy Objects, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a></dt><dt>groupadd, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>groupdel, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>groupmem, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>groupmod, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>GSS-API, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>guest account, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a>, <a class="indexterm" href="primer.html#chap01conc">Dissection and Discussion</a>, <a class="indexterm" href="primer.html#id2628200">Technical Issues</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hackers, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>hardware prices, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>hardware problems, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>Heimdal, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>Heimdal Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>Heimdal kerberos, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a></dt><dt>help, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>helper agent, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>hesiod, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>hierarchy of control, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>high availability, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>hire, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>HKEY_CURRENT_USER, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a></dt><dt>HKEY_LOCAL_MACHINE, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>HKEY_LOCAL_USER, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>host announcement, <a class="indexterm" href="primer.html#id2625625">Assignment Tasks</a>, <a class="indexterm" href="primer.html#id2626655">Findings</a></dt><dt>hostname, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>hosts, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>HUB, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>Hybrid, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>hypothetical, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>Idealx, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dd><dl><dt>smbldap-tools, <a class="indexterm" href="happy.html#sbeidealx">Install and Configure Idealx smbldap-tools Scripts</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt></dl></dd><dt>identifiers, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>identity, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dd><dl><dt>management, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt></dl></dd><dt>identity management, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#id2590005">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a></dt><dt>Identity Management, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>Identity management, <a class="indexterm" href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a></dt><dt>Identity resolution, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>Identity resolver, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>IDMAP, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>idmap backend, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>IDMAP backend, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>idmap gid, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>idmap uid, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>idmap_rid, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>IMAP, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a></dt><dt>import, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>income, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>independent expert, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>inetd, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>inetOrgPerson, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a></dt><dt>inheritance, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>initGrps.sh, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>initial credentials, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>inoperative, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>install, <a class="indexterm" href="upgrades.html">Updating Samba-3</a></dt><dt>installation, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>integrate, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>integrity, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>inter-domain, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>inter-operability, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>interactive help, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>interdomain trusts, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>interfaces, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>intermittent, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>internationalization, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>Internet Explorer, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>Internet Information Server, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>interoperability, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>IP forwarding, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>IPC$, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>iptables, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a></dt><dt>IRC, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>isolated, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Italian, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>J</h3><dl><dt>jobs, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>joining a domain, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KDC, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dd><dl><dt>Heimdal, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>interoperability, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>libraries, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>MIT, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>unspecified fields, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt></dl></dd><dt>kerberos, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dd><dl><dt>server, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt></dl></dd><dt>Kerberos ticket, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>kinit, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>Kixtart, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>klist, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>krb5, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a></dt><dt>krb5.conf, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LAM, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dd><dl><dt>configuration editor, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>configuration file, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>login screen, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>opening screen, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>profile, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>wizard, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt></dl></dd><dt>large domain, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>LDAP, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2573011">Preliminary Advice: Dangers Can Be Avoided</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="2000users.html#id2583740">Introduction</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="2000users.html#id2588234">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2601394">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dd><dl><dt>backend, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>database, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></dt><dt>directory, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>fail-over, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>initial configuration, <a class="indexterm" href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></dt><dt>master, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>master/slave</dt><dd><dl><dt>background communication, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt></dl></dd><dt>preload, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>schema, <a class="indexterm" href="upgrades.html#id2600553">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>secure, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>server, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>slave, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>updates, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt></dl></dd><dt>ldap, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>LDAP Account Manager (see LAM)</dt><dt>LDAP backend, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>LDAP database, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>LDAP Interchange Format (see LDIF)</dt><dt>LDAP server, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>LDAP-transfer-LDIF.txt, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>ldap.conf, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapadd, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapsam, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="upgrades.html#id2600553">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601394">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>ldapsam backend, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>ldapsearch, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>LDIF, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2622948">Initialization of the LDAP Database</a></dt><dt>leadership, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Lightweight Directory Access Protocol (see LDAP)</dt><dt>limit, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>Linux desktop, <a class="indexterm" href="unixclients.html#id2589239">Introduction</a></dt><dt>Linux Standards Base (see LSB)</dt><dt>LMB, <a class="indexterm" href="primer.html#id2626002">Findings</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dt>LMHOSTS, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>load distribution, <a class="indexterm" href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>local accounts, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Local Group Policy, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a></dt><dt>Local Master Announcement, <a class="indexterm" href="primer.html#id2626655">Findings</a></dt><dt>Local Master Browser (see LMB)</dt><dt>localhost, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>lock directory, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>locking</dt><dd><dl><dt>Application level, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Client side, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Server side, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt></dl></dd><dt>logging, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>login, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a></dt><dt>loglevel, <a class="indexterm" href="happy.html#id2573244">Debugging LDAP</a></dt><dt>logon credentials, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>logon hours, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a></dt><dt>logon machines, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>logon path, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>logon process, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt><dt>logon scrip, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a></dt><dt>logon script, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2581136">Preparation of Logon Scripts</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>logon server, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>logon services, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>logon time, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a></dt><dt>logon traffic, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>logon.kix, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>loopback, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>low performance, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>lower-case, <a class="indexterm" href="ntmigration.html#id2601984">Implementation</a></dt><dt>lpadmin, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>LSB, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>machine, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>machine account, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>machine accounts, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>machine secret password, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a></dt><dt>MACHINE.SID, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>mailing list, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>mailing lists, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>managed, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>management, <a class="indexterm" href="unixclients.html#id2590005">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dd><dl><dt>group, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>User, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></dd><dt>mandatory profile, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2580892">Configuring Profile Directories</a></dt><dt>Mandrake, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>mapped drives, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>mapping, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dd><dl><dt>consistent, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt></dl></dd><dt>Mars_NWE, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>master, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>material, <a class="indexterm" href="appendix.html">A Collection of Useful Tidbits</a></dt><dt>memberUID, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>memory requirements, <a class="indexterm" href="secure.html#id2559128">Hardware Requirements</a></dt><dt>merge, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>merged, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>meta-directory, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>meta-service, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>Microsoft Access, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Microsoft Excel, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt><dt>Microsoft ISA, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a></dt><dt>Microsoft Management Console (see MMC)</dt><dt>Microsoft Office, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>Microsoft Outlook</dt><dd><dl><dt>PST files, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt></dl></dd><dt>migrate, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>migration, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2601309">Introduction</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dd><dl><dt>objectives, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt></dl></dd><dt>Migration speed, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>mime type, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>mime types, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>missing RPC's, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>MIT, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>MIT Kerberos, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>MIT kerberos, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a></dt><dt>MIT KRB5, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>mixed mode, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>mixed-mode, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>MMC, <a class="indexterm" href="happy.html#id2582451">Configure Delete Cached Profiles on Logout</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>mobile computing, <a class="indexterm" href="small.html#id2555518">Dissection and Discussion</a></dt><dt>mobility, <a class="indexterm" href="2000users.html#id2584112">Technical Issues</a></dt><dt>modularization, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>modules, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>MS Access</dt><dd><dl><dt>validate, <a class="indexterm" href="appendix.html#id2625006">Microsoft Access</a></dt></dl></dd><dt>MS Outlook, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt><dt>PST file, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>MS Windows Server 2003, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a></dt><dt>MS Word, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>MSDFS, <a class="indexterm" href="HA.html#id2620480">Distribute Network Load with MSDFS</a></dt><dt>multi-subnet, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>multi-user</dt><dd><dl><dt>access, <a class="indexterm" href="appendix.html#id2625006">Microsoft Access</a></dt><dt>data access, <a class="indexterm" href="appendix.html#ch12dblck">Shared Data Integrity</a></dt></dl></dd><dt>multiple directories, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>multiple domain controllers, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>multiple group mappings, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>mutual assistance, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>My Documents, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a></dt><dt>My Network Places, <a class="indexterm" href="simple.html#id2551947">Implementation</a></dt><dt>mysqlsam, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>name resolution, <a class="indexterm" href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2625625">Assignment Tasks</a></dt><dd><dl><dt>Defective, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt></dl></dd><dt>name resolve order, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>name service switch, <a class="indexterm" href="small.html#id2555786">Implementation</a> (see NSS)</dt><dt>named, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a></dt><dt>NAT, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a></dt><dt>native, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>net</dt><dd><dl><dt>ads</dt><dd><dl><dt>info, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>join, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>status, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt></dl></dd><dt>getlocalsid, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>group, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></dt><dt>groupmap</dt><dd><dl><dt>add, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a></dt><dt>list, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>modify, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a></dt></dl></dd><dt>rpc</dt><dd><dl><dt>info, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>join, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></dt><dt>vampire, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></dt></dl></dd><dt>setlocalsid, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt></dl></dd><dt>NetBIOS, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a>, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>name cache, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>name resolution</dt><dd><dl><dt>delays, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>Node Type, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt></dl></dd><dt>netbios</dt><dd><dl><dt>machine  name, <a class="indexterm" href="upgrades.html#id2599028">Change of hostname</a></dt></dl></dd><dt>netbios forwarding, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>NetBIOS name, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dd><dl><dt>aliases, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt></dl></dd><dt>netbios name, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599028">Change of hostname</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>NETLOGON, <a class="indexterm" href="happy.html#id2572762">Using a Network Default User Profile</a>, <a class="indexterm" href="happy.html#id2581381">Windows Client Configuration</a></dt><dt>netlogon, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>Netlogon, <a class="indexterm" href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></dt><dt>netmask, <a class="indexterm" href="simple.html#id2551055">Implementation</a></dt><dt>Netware, <a class="indexterm" href="small.html">Small Office Networking</a></dt><dt>NetWare, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>network</dt><dd><dl><dt>administrators, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>analyzer, <a class="indexterm" href="primer.html#id2625625">Assignment Tasks</a></dt><dt>bandwidth, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>broadcast, <a class="indexterm" href="primer.html#id2625565">Introduction</a></dt><dt>captures, <a class="indexterm" href="primer.html#id2625404">Requirements and Notes</a></dt><dt>collisions, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>load, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>logon, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>logon scripts, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>management, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>multi-segment, <a class="indexterm" href="happy.html#id2571163">Introduction</a></dt><dt>overload, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>performance, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>routed, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>secure, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>segment, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>services, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>sniffer, <a class="indexterm" href="primer.html#id2625404">Requirements and Notes</a></dt><dt>timeout, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>timeouts, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>trace, <a class="indexterm" href="primer.html#id2625625">Assignment Tasks</a></dt><dt>traffic</dt><dd><dl><dt>observation, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></dd><dt>wide-area, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt></dl></dd><dt>Network Address Translation (see NAT)</dt><dt>network administrators, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>network attached storage (see NAS)</dt><dt>network bandwidth</dt><dd><dl><dt>utilization, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>Network Default Profile, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a></dt><dt>network hardware</dt><dd><dl><dt>defective, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>network hygiene, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>network Identities, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>network load factors, <a class="indexterm" href="Big500users.html#id2565371">Dissection and Discussion</a></dt><dt>Network Neighborhood, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>network segment, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dt>network segments, <a class="indexterm" href="secure.html#id2559128">Hardware Requirements</a></dt><dt>network share, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a></dt><dt>networking</dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt></dl></dd><dt>networking hardware</dt><dd><dl><dt>defective, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>networking protocols, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>next generation, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>NextFreeUnixId, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>NFS server, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>NICs, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>NIS, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2590005">Political Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>nis, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>NIS schema, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>NIS server, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>NIS+, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>nisplus, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>NLM, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>nmap, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>nmbd, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>nobody, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>Novell, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a>, <a class="indexterm" href="nw4migration.html#id2606004">Introduction</a></dt><dt>Novell SUSE SLES 9, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>NSS, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="DomApps.html#id2617684">NSS Configuration</a> (see same service switch)</dt><dt>nss_ldap, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>nt acl support, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a></dt><dt>NT4 registry, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>NTLM, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>NTLM authentication daemon, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>NTLMSSP, <a class="indexterm" href="DomApps.html#id2618345">Key Points Learned</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a>, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>NTLMSSP_AUTH, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>ntlm_auth, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>NTP, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>NTUSER.DAT, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2572668">Profile Changes</a>, <a class="indexterm" href="happy.html#id2572762">Using a Network Default User Profile</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>NULL connection, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>NULL session, <a class="indexterm" href="primer.html#id2627253">Findings and Comments</a></dt><dt>NULL-Session, <a class="indexterm" href="primer.html#id2628054">Discussion</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>objectClass, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>off-site storage, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Open Magazine, <a class="indexterm" href="unixclients.html">Adding Domain Member Servers and Clients</a></dt><dt>Open Source, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>OpenLDAP, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#id2590005">Political Issues</a>, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>openldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>OpenOffice, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>operating profiles, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>oplock break, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a></dt><dt>oplocks, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>Oplocks</dt><dd><dl><dt>disabled, <a class="indexterm" href="appendix.html#id2625237">Opportunistic Locking Controls</a></dt></dl></dd><dt>opportunistic</dt><dd><dl><dt>locking, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a></dt></dl></dd><dt>opportunistic locking, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a>, <a class="indexterm" href="appendix.html#id2625153">Act! Database Sharing</a></dt><dt>optimized, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>organizational units, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>OS/2, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>Outlook</dt><dd><dl><dt>PST, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt></dl></dd><dt>Outlook Address Book, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt><dt>Outlook Express, <a class="indexterm" href="secure.html#id2559282">Political Issues</a>, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt><dt>over-ride, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>over-ride controls, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a></dt><dt>over-rule, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2615000">Using MS Windows Explorer (File Manager)</a></dt><dt>overheads, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a></dt><dt>ownership, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package, <a class="indexterm" href="simple.html#id2551055">Implementation</a></dt><dt>package names, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>packages, <a class="indexterm" href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></dt><dt>PADL, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a></dt><dt>PADL LDAP tools, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>PADL Software, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>paid-for support, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>PAM, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>pam_ldap, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>pam_ldap.so, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>pam_unix2.so, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dd><dl><dt>use_ldap, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt></dl></dd><dt>parameters, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>passdb backend, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2600553">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601394">Assignment Tasks</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>passdb.tdb, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>passwd, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a></dt><dt>password</dt><dd><dl><dt>backend, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>password caching, <a class="indexterm" href="simple.html#id2551947">Implementation</a></dt><dt>password change, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a></dt><dt>password length, <a class="indexterm" href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>payroll, <a class="indexterm" href="nw4migration.html#id2606004">Introduction</a></dt><dt>pdbedit, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>PDC, <a class="indexterm" href="Big500users.html#id2565265">Assignment Tasks</a>, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-locgrppol">The Local Group Policy</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2601984">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a>, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dt>PDC/BDC ratio, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>PDF, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>performance, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a>, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a>, <a class="indexterm" href="HA.html#id2618932">Introduction</a>, <a class="indexterm" href="HA.html#id2619906">Network Collisions</a></dt><dt>performance degradation, <a class="indexterm" href="kerberos.html#id2614081">Override Controls</a>, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>Perl, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>permission, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>permissions, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dd><dl><dt>excessive, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>group, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>user, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt></dl></dd><dt>Permissions, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>permits, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>permitted group, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>PHP, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>PHP4, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>pile-driver, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>ping, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>pitfalls, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>plain-text, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>Pluggable Authentication Modules (see PAM)</dt><dt>policy, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>poor performance, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>POP3, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a></dt><dt>Posix, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2601984">Implementation</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>POSIX, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>Posix accounts, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Posix ACLs, <a class="indexterm" href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></dt><dt>PosixAccount, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>posixAccount, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>Postfix, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>Postscript, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>powers, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>practices, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>precaution, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a></dt><dt>presence and leadership, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>price paid, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>primary group, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>principals, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>print filter, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>print queue, <a class="indexterm" href="simple.html#id2551628">Charity Administration Office</a>, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a></dt><dt>print spooler, <a class="indexterm" href="simple.html#id2551628">Charity Administration Office</a></dt><dt>Print Test Page, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>printcap name, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>printer validation, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a></dt><dt>printers</dt><dd><dl><dt>Advanced, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>Default Settings, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>General, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>Properties, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>Security, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>Sharing, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt></dl></dd><dt>printing, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dd><dl><dt>drag-and-drop, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a>, <a class="indexterm" href="happy.html#id2582630">Uploading Printer Drivers to Samba Servers</a></dt><dt>dumb, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>point-n-click, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>raw, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a></dt></dl></dd><dt>privacy, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>Privilege Attribute Certificates (see PAC)</dt><dt>privilege controls, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>privileged pipe, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>privileges, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2600632">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt><dt>problem report, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>problem resolution, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>product defects, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>professional support, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>profile</dt><dd><dl><dt>default, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a></dt><dt>mandatory, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>roaming, <a class="indexterm" href="happy.html">Making Happy Users</a></dt></dl></dd><dt>profile path, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>profile share, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>profiles, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>profiles share, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>programmer, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>project, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>project maintainers, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Properties, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>proprietary, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>protected, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>protection, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>protocol</dt><dd><dl><dt>negotiation, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt></dl></dd><dt>protocol analysis, <a class="indexterm" href="primer.html#id2625404">Requirements and Notes</a></dt><dt>protocols, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>provided services, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>proxy, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>PST file, <a class="indexterm" href="happy.html#id2582135">Configuration of MS Outlook to Relocate PST File</a></dt><dt>public specifications, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>purchase support, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>Qbasic, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>qualified problem, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID, <a class="indexterm" href="secure.html#id2559128">Hardware Requirements</a></dt><dt>RAID controllers, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>Raw Print Through, <a class="indexterm" href="happy.html#id2572820">Installation of Printer Driver Auto-Download</a></dt><dt>raw printing, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4ptrcfg">Printer Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="happy.html#sbehap-ptrcfg">Printer Configuration</a></dt><dt>Rbase, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>rcldap, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>realm, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="unixclients.html#id2595379">IDMAP Storage in LDAP using Winbind</a>, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>recognize, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>record locking, <a class="indexterm" href="appendix.html#id2625006">Microsoft Access</a></dt><dt>recursively, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Red Hat, <a class="indexterm" href="simple.html#id2550918">Drafting Office</a>, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>Red Hat Fedora Linux, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>Red Hat Linux, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="simple.html#AccountingOffice">Accounting Office</a>, <a class="indexterm" href="happy.html#id2573929">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>redirected folders, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>refereed standards, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>regedit, <a class="indexterm" href="simple.html#id2551947">Implementation</a></dt><dt>regedt32, <a class="indexterm" href="happy.html#id2572668">Profile Changes</a>, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>registry, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dd><dl><dt>keys</dt><dd><dl><dt>SAM, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>SECURITY, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt></dl></dd></dl></dd><dt>registry change, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>Registry Editor, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>registry hacks, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>registry keys, <a class="indexterm" href="happy.html#redirfold">Configuration of Default Profile with Folder Redirection</a></dt><dt>reimburse, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>rejected, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>rejoin, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>reliability, <a class="indexterm" href="HA.html">Performance, Reliability, and Availability</a></dt><dt>remote announce, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>remote browse sync, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>remote procedure call (see RPC)</dt><dt>replicate, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>replicated, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>requesting payment, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>resilient, <a class="indexterm" href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></dt><dt>resolution, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a></dt><dt>resolve, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="HA.html#id2619542">Bad Hostnames</a></dt><dt>response, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a></dt><dt>responsibility, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>responsible, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>restrict anonymous, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>restricted export, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>Restrictive security, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>reverse DNS, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a></dt><dt>rfc2307bis, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>RID, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>risk, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>road-map, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dd><dl><dt>published, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></dd><dt>roaming profile, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a>, <a class="indexterm" href="happy.html#id2580892">Configuring Profile Directories</a>, <a class="indexterm" href="2000users.html#id2584151">User Needs</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>roaming profiles, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="happy.html#id2572367">Roaming Profile Background</a></dt><dt>routed network, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a></dt><dt>router, <a class="indexterm" href="small.html#id2555786">Implementation</a></dt><dt>routers, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>RPC, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>rpc, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>rpcclient, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>RPM, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a></dt><dd><dl><dt>install, <a class="indexterm" href="simple.html#id2551055">Implementation</a></dt></dl></dd><dt>rpm, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>RPMs, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>rpms, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>rsync, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>rsyncd.conf, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>run-time control files, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>safe-guards, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>SAM, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>samba, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dd><dl><dt>starting samba, <a class="indexterm" href="simple.html#id2551055">Implementation</a></dt></dl></dd><dt>Samba, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>Samba accounts, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>samba cluster, <a class="indexterm" href="HA.html#id2618932">Introduction</a></dt><dt>samba control script, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>Samba Domain, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>Samba Domain server, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>Samba RPM Packages, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a></dt><dt>Samba Tea, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>sambaDomainName, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>sambaGroupMapping, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>SambaSAMAccount, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>SambaSamAccount, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>sambaSamAccount, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>SambaXP conference, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>SAN, <a class="indexterm" href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>SAS, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>scalability, <a class="indexterm" href="HA.html#id2618932">Introduction</a></dt><dt>scalable, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>schannel, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>schema, <a class="indexterm" href="unixclients.html#id2595974">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2600227">Samba-2.x with LDAP Support</a>, <a class="indexterm" href="upgrades.html#id2600553">Updating from Samba Versions between 3.0.6 and 3.0.10</a></dt><dt>scripts, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>secondary group, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></dt><dt>secret, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>secrets.tdb, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a></dt><dt>secure, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>secure account password, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>secure connections, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>secure networking, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>secure networking protocols, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>security, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dd><dl><dt>identifier, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>share mode, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a></dt><dt>user mode, <a class="indexterm" href="simple.html#id2553794">Dissection and Discussion</a></dt></dl></dd><dt>Security, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2614709">Using the MMC Computer Management Interface</a></dt><dt>Security Account Manager (see SAM)</dt><dt>security controls, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>security descriptors, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>security fixes, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>security updates, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>SerNet, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>server</dt><dd><dl><dt>domain member, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>stand-alone, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt></dl></dd><dt>service, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dd><dl><dt>smb</dt><dd><dl><dt>start, <a class="indexterm" href="Big500users.html#ch5-domsvrspec">Configuration Specific to Domain Member Servers: BLDG1, BLDG2</a></dt></dl></dd></dl></dd><dt>Service Packs, <a class="indexterm" href="secure.html#ch4appscfg">Application Share Configuration</a></dt><dt>services, <a class="indexterm" href="DomApps.html#id2618345">Key Points Learned</a></dt><dt>services provided, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>session setup, <a class="indexterm" href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>Session Setup, <a class="indexterm" href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a></dt><dt>SessionSetUpAndX, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>set primary group script, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>setfacl, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>severely degrade, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>SFU, <a class="indexterm" href="unixclients.html#id2596260">IDMAP, Active Directory, and MS Services for UNIX 3.5</a></dt><dt>SGID, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a>, <a class="indexterm" href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></dt><dt>shadow-utils, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>Share Access Controls, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>share ACLs, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>share definition, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>Share Definition</dt><dd><dl><dt>Controls, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a></dt></dl></dd><dt>share definition controls, <a class="indexterm" href="kerberos.html#id2613629">Share Definition Controls</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>share level access controls, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>share level ACL, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>Share Permissions, <a class="indexterm" href="kerberos.html#id2613280">Share Access Controls</a></dt><dt>shared resource, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>shares, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>SID, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2594775">IDMAP_RID with Winbind</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599094">Change of Workgroup (Domain) Name</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622948">Initialization of the LDAP Database</a></dt><dt>side effects, <a class="indexterm" href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></dt><dt>Sign'n'seal, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>silent return, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></dt><dt>simple, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>Single Sign-On (see SSO)</dt><dt>slapcat, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>slapd, <a class="indexterm" href="happy.html#id2573244">Debugging LDAP</a></dt><dt>slapd.conf, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>slave, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>slow logon, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>slow network, <a class="indexterm" href="HA.html#id2620581">Hardware Problems</a></dt><dt>slurpd, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>smart printing, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>SMB, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>SMB passwords, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>SMB/CIFS, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>smbclient, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>smbd, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#sbeug1">Location of config files</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dd><dl><dt>location of files, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt></dl></dd><dt>smbfs, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>smbldap-groupadd, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>smbldap-groupmod, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>smbldap-passwd, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-populate, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a></dt><dt>smbldap-tools, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a>, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>smbldap-tools updating, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>smbldap-useradd, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt><dt>smbldap-usermod, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>smbmnt, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>smbmount, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>smbpasswd, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="happy.html#id2576827">LDAP Initialization and Creation of User and Group Accounts</a>, <a class="indexterm" href="happy.html#sbehap-bldg1">Samba-3 BDC Configuration</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html">Updating Samba-3</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="DomApps.html">Integrating Additional Services</a></dt><dt>smbumnt, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>smbumount, <a class="indexterm" href="HA.html#id2619030">Dissection and Discussion</a></dt><dt>SMTP, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a></dt><dt>snap-shot, <a class="indexterm" href="ntmigration.html#id2601449">Dissection and Discussion</a></dt><dt>socket address, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>socket options, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>software, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>solve, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>source code, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>SPNEGO, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>SQL, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>Squid, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2617949">Squid Configuration</a></dt><dt>squid, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>Squid proxy, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>SRVTOOLS.EXE, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="happy.html#id2580892">Configuring Profile Directories</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>SSL, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>stand-alone server, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>starting CUPS, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>starting dhcpd, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dt>starting samba, <a class="indexterm" href="simple.html#id2551055">Implementation</a>, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a>, <a class="indexterm" href="Big500users.html#ch5-procstart">Process Startup Configuration</a></dt><dd><dl><dt>nmbd, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>smbd, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>winbindd, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt></dl></dd><dt>startingCUPS, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a></dt><dt>startup script, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>sticky bit, <a class="indexterm" href="small.html#id2555786">Implementation</a></dt><dt>storage capacity, <a class="indexterm" href="secure.html#id2559128">Hardware Requirements</a></dt><dt>strategic, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a></dt><dt>strategy, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>straw-man, <a class="indexterm" href="kerberos.html">Active Directory, Kerberos, and Security</a></dt><dt>strict sync, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>stripped, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></dt><dt>strong cryptography, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>subscription, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>SUID, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a>, <a class="indexterm" href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></dt><dt>Sun ONE Identity Server, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>super daemon, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>support, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a>, <a class="indexterm" href="ch14.html">Samba Support</a></dt><dt>survey, <a class="indexterm" href="unixclients.html">Adding Domain Member Servers and Clients</a></dt><dt>SUSE, <a class="indexterm" href="nw4migration.html">Migrating NetWare Server to Samba-3</a></dt><dt>SUSE Enterprise Linux Server, <a class="indexterm" href="simple.html#id2551628">Charity Administration Office</a>, <a class="indexterm" href="secure.html#ch4bsc">Basic System Configuration</a>, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a></dt><dt>SUSE Linux, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2573929">Samba Server Implementation</a>, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2616493">Implementation</a>, <a class="indexterm" href="DomApps.html#ch10-one">Removal of Pre-Existing Conflicting RPMs</a></dt><dt>SWAT, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>sync always, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>synchronization, <a class="indexterm" href="DomApps.html#id2616742">Kerberos Configuration</a>, <a class="indexterm" href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></dt><dt>synchronize, <a class="indexterm" href="2000users.html#id2584151">User Needs</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>synchronized, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>syslog, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>system level logins, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>system security, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>tattooing, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>TCP/IP, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>tdbdump, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>tdbsam, <a class="indexterm" href="secure.html#id2558856">Technical Issues</a>, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="happy.html#id2571261">Assignment Tasks</a>, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="upgrades.html#id2600553">Updating from Samba Versions between 3.0.6 and 3.0.10</a>, <a class="indexterm" href="ntmigration.html#id2601635">Technical Issues</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>testparm, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="happy.html#sbehap-massive">Samba-3 PDC Configuration</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="HA.html#id2620006">Samba Configuration</a></dt><dt>ticket, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>time server, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>Tivoli Directory Server, <a class="indexterm" href="happy.html#id2571398">Dissection and Discussion</a></dt><dt>TLS, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>token, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a></dt><dt>tool, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>TOSHARG2, <a class="indexterm" href="simple.html#id2551947">Implementation</a></dt><dt>track record, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>traffic collisions, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>transaction processing, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>transactional, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>transfer, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>translate, <a class="indexterm" href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></dt><dt>traverse, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>tree, <a class="indexterm" href="nw4migration.html#id2606233">Dissection and Discussion</a></dt><dt>Tree Connect, <a class="indexterm" href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a></dt><dt>trust account, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a></dt><dt>trusted computing, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Trusted Domains, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>trusted domains, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>trusted third-party, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>trusting, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>turn-around time, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UDP</dt><dd><dl><dt>broadcast, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt></dl></dd><dt>UID, <a class="indexterm" href="simple.html#id2551752">Dissection and Discussion</a>, <a class="indexterm" href="happy.html#id2571021">Regarding LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a>, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>un-join, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>unauthorized activities, <a class="indexterm" href="kerberos.html#id2612934">Kerberos Exposed</a></dt><dt>UNC name, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>unencrypted, <a class="indexterm" href="appendix.html#id2623534">The LDAP Account Manager</a></dt><dt>Unicast, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a></dt><dt>unicode, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>Universal Naming Convention (see UNC name)</dt><dt>UNIX, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dd><dl><dt>groups, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a></dt></dl></dd><dt>UNIX accounts, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>UNIX/Linux server, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>unix2dos, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt><dt>unknown, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>unsupported software, <a class="indexterm" href="ch14.html#id2621220">Commercial Support</a></dt><dt>update, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a>, <a class="indexterm" href="upgrades.html#id2598196">Cautions and Notes</a></dt><dt>updates, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>updating smbldap-tools, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>upgrade, <a class="indexterm" href="upgrades.html#id2598100">Introduction</a>, <a class="indexterm" href="upgrades.html#id2598196">Cautions and Notes</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>uppercase, <a class="indexterm" href="ntmigration.html#id2601984">Implementation</a></dt><dt>user</dt><dd><dl><dt>management, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a></dt></dl></dd><dt>user account, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="happy.html#ldapsetup">OpenLDAP Server Configuration</a></dt><dt>User and Group Controls, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>user credentials, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a></dt><dt>user errors, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>user groups, <a class="indexterm" href="ch14.html#id2621002">Free Support</a></dt><dt>user identities, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt><dt>user logins, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>user management, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>User Manager, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>User Mode, <a class="indexterm" href="secure.html#id2559322">Implementation</a>, <a class="indexterm" href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a>, <a class="indexterm" href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></dt><dt>useradd, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="simple.html#AcctgNet">Implementation</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566938">Configuration for Server: MASSIVE</a>, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>userdel, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></dt><dt>usermod, <a class="indexterm" href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a>, <a class="indexterm" href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></dt><dt>username, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>username map, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#id2560176">Samba Configuration</a>, <a class="indexterm" href="Big500users.html#id2566360">Server Preparation: All Servers</a></dt><dt>UTF-8, <a class="indexterm" href="upgrades.html#id2599360">International Language Support</a></dt><dt>utilities, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a>, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>validate, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>validated, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>validation, <a class="indexterm" href="simple.html#validate1">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>vampire, <a class="indexterm" href="ntmigration.html#id2605028">Questions and Answers</a></dt><dt>vendor, <a class="indexterm" href="kerberos.html#id2611253">Dissection and Discussion</a></dt><dt>vendors, <a class="indexterm" href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></dt><dt>VFS modules, <a class="indexterm" href="appendix.html#id2621928">Samba System File Location</a></dt><dt>virus, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>VPN, <a class="indexterm" href="2000users.html#id2583770">Assignment Tasks</a></dt><dt>vulnerabilities, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>wbinfo, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a></dt><dt>weakness, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a></dt><dt>web</dt><dd><dl><dt>caching, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a></dt><dt>proxying, <a class="indexterm" href="DomApps.html#id2616176">Assignment Tasks</a></dt></dl></dd><dt>Web</dt><dd><dl><dt>proxy, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dd><dl><dt>access, <a class="indexterm" href="DomApps.html#id2618345">Key Points Learned</a></dt></dl></dd></dl></dd><dt>Web browsers, <a class="indexterm" href="DomApps.html#id2618345">Key Points Learned</a></dt><dt>WebClient, <a class="indexterm" href="happy.html">Making Happy Users</a></dt><dt>WHATSNEW.txt, <a class="indexterm" href="upgrades.html#id2600227">Samba-2.x with LDAP Support</a></dt><dt>white-pages, <a class="indexterm" href="nw4migration.html#id2606310">Technical Issues</a>, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>wide-area, <a class="indexterm" href="2000users.html#id2584151">User Needs</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2588234">Key Points Learned</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>wide-area network, <a class="indexterm" href="HA.html#id2620334">Use and Location of BDCs</a>, <a class="indexterm" href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></dt><dt>winbind, <a class="indexterm" href="2000users.html#id2585074">Implementation</a>, <a class="indexterm" href="unixclients.html#id2589328">Dissection and Discussion</a>, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2616320">Technical Issues</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2617684">NSS Configuration</a></dt><dt>Winbind, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="kerberos.html#id2611650">Technical Issues</a>, <a class="indexterm" href="kerberos.html#id2615382">Key Points Learned</a></dt><dt>winbind trusted domains only, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>winbind use default domain, <a class="indexterm" href="kerberos.html#id2613769">Checkpoint Controls</a></dt><dt>winbindd, <a class="indexterm" href="small.html#id2557330">Validation</a>, <a class="indexterm" href="secure.html#ch4valid">Validation</a>, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a>, <a class="indexterm" href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a>, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a>, <a class="indexterm" href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a>, <a class="indexterm" href="upgrades.html#id2600632">Updating from Samba Versions after 3.0.6 to a Current Release</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a>, <a class="indexterm" href="DomApps.html#id2617132">Samba Configuration</a>, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a>, <a class="indexterm" href="appendix.html#id2622349">Starting Samba</a></dt><dt>winbindd_cache.tdb, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>winbindd_idmap.tdb, <a class="indexterm" href="unixclients.html#id2589356">Technical Issues</a></dt><dt>Windows, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dd><dl><dt>client, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt><dt>NT, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a></dt></dl></dd><dt>Windows 2000 ACLs, <a class="indexterm" href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></dt><dt>Windows 2003 Serve, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Windows 200x ACLs, <a class="indexterm" href="kerberos.html#id2615516">Questions and Answers</a></dt><dt>Windows accounts, <a class="indexterm" href="happy.html#id2571856">Technical Issues</a></dt><dt>Windows ACLs, <a class="indexterm" href="kerberos.html#id2615172">Setting Posix ACLs in UNIX/Linux</a></dt><dt>Windows Address Book, <a class="indexterm" href="nw4migration.html#id2606584">LDAP Server Configuration</a></dt><dt>Windows ADS Domain, <a class="indexterm" href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></dt><dt>Windows clients, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>Windows Explorer, <a class="indexterm" href="simple.html#validate1">Validation</a></dt><dt>Windows explorer, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>Windows security identifier (see SID)</dt><dt>Windows Servers, <a class="indexterm" href="kerberos.html#id2610586">Introduction</a></dt><dt>Windows Services for UNIX (see SUS)</dt><dt>Windows XP, <a class="indexterm" href="small.html#id2555458">Assignment Tasks</a></dt><dt>WINS, <a class="indexterm" href="simple.html#id2551947">Implementation</a>, <a class="indexterm" href="small.html#id2555566">Technical Issues</a>, <a class="indexterm" href="small.html#id2555786">Implementation</a>, <a class="indexterm" href="secure.html#ch4wincfg">Windows Client Configuration</a>, <a class="indexterm" href="Big500users.html#id2565407">Technical Issues</a>, <a class="indexterm" href="Big500users.html#ch5wincfg">Windows Client Configuration</a>, <a class="indexterm" href="2000users.html#id2584245">The Nature of Windows Networking Protocols</a>, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a>, <a class="indexterm" href="primer.html#chap01qa">Questions and Answers</a></dt><dd><dl><dt>lookup, <a class="indexterm" href="unixclients.html#id2596940">Questions and Answers</a></dt><dt>name resolution, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt><dt>server, <a class="indexterm" href="happy.html">Making Happy Users</a>, <a class="indexterm" href="HA.html#id2619734">Routed Networks</a></dt></dl></dd><dt>WINS server, <a class="indexterm" href="Big500users.html">The 500-User Office</a>, <a class="indexterm" href="2000users.html#id2588381">Questions and Answers</a></dt><dt>WINS serving, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>wins support, <a class="indexterm" href="secure.html#id2559322">Implementation</a></dt><dt>wins.dat, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a>, <a class="indexterm" href="upgrades.html#id2600735">Replacing a Domain Member Server</a></dt><dt>Wireshark, <a class="indexterm" href="primer.html#id2625404">Requirements and Notes</a></dt><dt>wireshark, <a class="indexterm" href="primer.html#id2625742">Exercises</a></dt><dt>Word, <a class="indexterm" href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></dt><dt>workgroup, <a class="indexterm" href="simple.html#id2551055">Implementation</a>, <a class="indexterm" href="upgrades.html#id2598300">Security Identifiers (SIDs)</a>, <a class="indexterm" href="upgrades.html#id2599094">Change of Workgroup (Domain) Name</a></dt><dt>Workgroup Announcement, <a class="indexterm" href="primer.html#id2626655">Findings</a></dt><dt>workstation, <a class="indexterm" href="unixclients.html#id2590105">Implementation</a></dt><dt>wrapper, <a class="indexterm" href="DomApps.html#id2618406">Questions and Answers</a></dt><dt>write lock, <a class="indexterm" href="appendix.html#id2625237">Opportunistic Locking Controls</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>xinetd, <a class="indexterm" href="secure.html#procstart">Process Startup Configuration</a></dt><dt>XML, <a class="indexterm" href="2000users.html#id2583839">Dissection and Discussion</a></dt><dt>xmlsam, <a class="indexterm" href="2000users.html#id2585074">Implementation</a></dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>YaST, <a class="indexterm" href="happy.html#sbehap-PAM-NSS">PAM and NSS Client Configuration</a></dt><dt>Yellow Pages, <a class="indexterm" href="2000users.html#id2584592">Identity Management Needs</a></dt><dt>yellow pages (see NIS)</dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�</td></tr><tr><td width="40%" align="left" valign="top">Glossary�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/kerberos.html b/docs/htmldocs/Samba3-ByExample/kerberos.html
index e1c3ea2ca9..1cee1b6fdf 100644
--- a/docs/htmldocs/Samba3-ByExample/kerberos.html
+++ b/docs/htmldocs/Samba3-ByExample/kerberos.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�Active Directory, Kerberos, and Security</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="RefSection.html" title="Part�III.�Reference Section"><link rel="next" href="DomApps.html" title="Chapter�12.�Integrating Additional Services"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�Active Directory, Kerberos, and Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="RefSection.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="DomApps.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="kerberos"></a>Chapter�11.�Active Directory, Kerberos, and Security</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="kerberos.html#id2610496">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611138">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611154">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611545">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613169">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613518">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614131">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614530">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615257">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615391">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2610431"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�Active Directory, Kerberos, and Security</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="RefSection.html" title="Part�III.�Reference Section"><link rel="next" href="DomApps.html" title="Chapter�12.�Integrating Additional Services"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�Active Directory, Kerberos, and Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="RefSection.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="DomApps.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="kerberos"></a>Chapter�11.�Active Directory, Kerberos, and Security</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="kerberos.html#id2610586">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611237">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2611253">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2611650">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#ch10expl">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="kerberos.html#id2613280">Share Access Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2613629">Share Definition Controls</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614242">Share Point Directory and File Permissions</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2614655">Managing Windows 200x ACLs</a></span></dt><dt><span class="sect2"><a href="kerberos.html#id2615382">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="kerberos.html#id2615516">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2610522"></a>
 	By this point in the book, you have been exposed to many Samba-3 features and capabilities.
 	More importantly, if you have implemented the examples given, you are well on your way to becoming 
 	a Samba-3 networking guru who knows a lot about Microsoft Windows. If you have taken the time to 
 	practice, you likely have thought of improvements and scenarios with which you can experiment. You 
 	are rather well plugged in to the many flexible ways Samba can be used.
-	</p><p><a class="indexterm" name="id2610450"></a>
+	</p><p><a class="indexterm" name="id2610541"></a>
 	This is a book about Samba-3. Understandably, its intent is to present it in a positive light. 
 	The casual observer might conclude that this book is one-eyed about Samba. It is  what 
 	would you expect? This chapter exposes some criticisms that have been raised concerning 
@@ -13,13 +13,13 @@
 	Some criticism always comes from deep inside ranks that one would expect to be supportive of a particular 
 	decision. Criticism can be expected from the outside. Let's see how the interesting dynamic of 
 	criticism develops with respect to Abmas.
-	</p><p><a class="indexterm" name="id2610478"></a>
+	</p><p><a class="indexterm" name="id2610569"></a>
 	This chapter provides a shameless self-promotion of Samba-3. The objections raised were not pulled
 	out of thin air. They were drawn from comments made by Samba users and from criticism during 
 	discussions with Windows network administrators. The tone of the objections reflects as closely 
 	as possible that of the original. The case presented is a straw-man example that is designed to 
 	permit each objection to be answered as it might occur in real life.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610496"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2610502"></a><a class="indexterm" name="id2610510"></a><a class="indexterm" name="id2610518"></a><a class="indexterm" name="id2610526"></a><a class="indexterm" name="id2610534"></a>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610586"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2610593"></a><a class="indexterm" name="id2610601"></a><a class="indexterm" name="id2610609"></a><a class="indexterm" name="id2610616"></a><a class="indexterm" name="id2610624"></a>
 	Abmas is continuing its meteoric growth with yet further acquisitions. The investment community took
 	note of the spectacular projection of Abmas onto the global business stage. Abmas is building an
 	interesting portfolio of companies that includes accounting services, financial advice, investment
@@ -28,42 +28,42 @@
 	interesting business growth and development plan. Abmas Video Rentals was recently acquired. 
 	During the time that the acquisition was closing, the Video Rentals business upgraded its Windows 
 	NT4-based network to Windows 2003 Server and Active Directory.
-	</p><p><a class="indexterm" name="id2610558"></a>
+	</p><p><a class="indexterm" name="id2610649"></a>
 	You have accepted the fact that Abmas Video Rentals will use Microsoft Active Directory.
 	The IT team, led by Stan Soroka, is committed to Samba-3 and to maintaining a uniform technology platform. 
 	Stan Soroka's team voiced its disapproval over the decision to permit this business to continue to 
 	operate with a solution that is viewed by Christine and her group as &#8220;<span class="quote">an island of broken 
 	technologies.</span>&#8221; This comment was made by one of Christine's staff as they were installing a new 
 	Samba-3 server at the new business.
-	</p><p><a class="indexterm" name="id2610581"></a><a class="indexterm" name="id2610589"></a>
+	</p><p><a class="indexterm" name="id2610672"></a><a class="indexterm" name="id2610680"></a>
 	Abmas Video Rentals' head of IT heard of this criticism. He was offended that a junior engineer
 	should make such a comment. He felt that he had to prepare in case he might be criticized for his 
 	decision to use Active Directory. He decided he would defend his decision by hiring the services 
-	of an outside security systems consultant to report<sup>[<a name="id2610604" href="#ftn.id2610604" class="footnote">12</a>]</sup> on his unit's operations 
+	of an outside security systems consultant to report<sup>[<a name="id2610695" href="#ftn.id2610695" class="footnote">12</a>]</sup> on his unit's operations 
 	and to investigate the role of Samba at his site. Here are key extracts from this hypothetical 
 	report:
-	</p><div class="blockquote"><blockquote class="blockquote"><p><a class="indexterm" name="id2610616"></a><a class="indexterm" name="id2610624"></a><a class="indexterm" name="id2610632"></a><a class="indexterm" name="id2610640"></a>
+	</p><div class="blockquote"><blockquote class="blockquote"><p><a class="indexterm" name="id2610706"></a><a class="indexterm" name="id2610714"></a><a class="indexterm" name="id2610721"></a><a class="indexterm" name="id2610729"></a>
 	... the implementation of Microsoft Active Directory at the Abmas Video Rentals, Bamingsham site,
 	 has been examined. We find no evidence to support a notion that vulnerabilities exist at your site.  
 	... we took additional steps to validate the integrity of the installation and operation of Active 
 	Directory and are pleased that your staff are following sound practices.
 	</p><p>
 	...
-	</p><p><a class="indexterm" name="id2610661"></a><a class="indexterm" name="id2610672"></a><a class="indexterm" name="id2610683"></a><a class="indexterm" name="id2610691"></a><a class="indexterm" name="id2610699"></a><a class="indexterm" name="id2610707"></a>
+	</p><p><a class="indexterm" name="id2610750"></a><a class="indexterm" name="id2610762"></a><a class="indexterm" name="id2610773"></a><a class="indexterm" name="id2610781"></a><a class="indexterm" name="id2610789"></a><a class="indexterm" name="id2610797"></a>
 	User and group accounts, and respective privileges, have been well thought out. File system shares are
 	appropriately secured. Backup and disaster recovery plans are well managed and validated regularly, and
 	effective off-site storage practices are considered to exceed industry norms.
-	</p><p><a class="indexterm" name="id2610723"></a><a class="indexterm" name="id2610731"></a><a class="indexterm" name="id2610739"></a>
+	</p><p><a class="indexterm" name="id2610813"></a><a class="indexterm" name="id2610821"></a><a class="indexterm" name="id2610829"></a>
 	Your staff are justifiably concerned that the use of Samba may compromise their good efforts to maintain
 	a secure network. 
-	</p><p><a class="indexterm" name="id2610756"></a><a class="indexterm" name="id2610764"></a><a class="indexterm" name="id2610772"></a><a class="indexterm" name="id2610779"></a>
+	</p><p><a class="indexterm" name="id2610846"></a><a class="indexterm" name="id2610853"></a><a class="indexterm" name="id2610861"></a><a class="indexterm" name="id2610869"></a>
 	The recently installed Linux file and application server uses a tool called <code class="literal">winbind</code> 
 	that is indiscriminate about security. All user accounts in Active Directory can be used to access data 
 	stored on the Linux system. We are alarmed that secure information is accessible to staff who should 
 	not even be aware that it exists. We share the concerns of your network management staff who have gone 
 	to great lengths to set fine-grained controls that limit information access to those who need access. 
 	It seems incongruous to us that Samba winbind should be permitted to be used considering that it voids this fine work.
-	</p><p><a class="indexterm" name="id2610810"></a><a class="indexterm" name="id2610818"></a><a class="indexterm" name="id2610826"></a>
+	</p><p><a class="indexterm" name="id2610909"></a><a class="indexterm" name="id2610917"></a><a class="indexterm" name="id2610925"></a>
 	Graham Judd [head of network administration] has locked down the security of all systems and is following 
 	the latest Microsoft guidelines. ... null session connections have been disabled ... the internal network 
 	is isolated from the outside world, the [product name removed] firewall is under current contract 
@@ -72,7 +72,7 @@
 	detail and for following Microsoft recommended best practices.
 	</p><p>
 	...
-	</p><p><a class="indexterm" name="id2610851"></a><a class="indexterm" name="id2610859"></a><a class="indexterm" name="id2610866"></a><a class="indexterm" name="id2610874"></a>
+	</p><p><a class="indexterm" name="id2610949"></a><a class="indexterm" name="id2610957"></a><a class="indexterm" name="id2610965"></a><a class="indexterm" name="id2610973"></a>
 	Regarding the use of Samba, we offer the following comments: Samba is in use in nearly half of
 	all sites we have surveyed. ... It is our opinion that Samba offers no better security than Microsoft
 	... what worries us regarding Samba is the need to disable essential Windows security features such as
@@ -80,14 +80,14 @@
 	mixed mode so that Samba clients and servers can authenticate all of it. Additionally, we are concerned that
 	Samba is not at the full capabilities of Microsoft Windows NT4 server. Microsoft has moved well beyond that
 	with trusted computing initiatives that the Samba developers do not participate in.
-	</p><p><a class="indexterm" name="id2610898"></a><a class="indexterm" name="id2610906"></a><a class="indexterm" name="id2610913"></a><a class="indexterm" name="id2610921"></a><a class="indexterm" name="id2610929"></a><a class="indexterm" name="id2610937"></a><a class="indexterm" name="id2610945"></a>
+	</p><p><a class="indexterm" name="id2610996"></a><a class="indexterm" name="id2611004"></a><a class="indexterm" name="id2611012"></a><a class="indexterm" name="id2611020"></a><a class="indexterm" name="id2611028"></a><a class="indexterm" name="id2611036"></a><a class="indexterm" name="id2611044"></a>
 	One wonders about the integrity of an open source program that is developed by a team of hackers 
 	who cannot be held accountable for the flaws in their code. The sheer number of updates and bug
 	fixes they have released should ring alarm bells in any business.
-	</p><p><a class="indexterm" name="id2610960"></a><a class="indexterm" name="id2610968"></a><a class="indexterm" name="id2610976"></a>
+	</p><p><a class="indexterm" name="id2611059"></a><a class="indexterm" name="id2611067"></a><a class="indexterm" name="id2611075"></a>
 	Another factor that should be considered is that buying Microsoft products and services helps to 
 	provide employment in the IT industry. Samba and Open Source software place those jobs at risk.
-	</p></blockquote></div><p><a class="indexterm" name="id2610991"></a><a class="indexterm" name="id2610999"></a>
+	</p></blockquote></div><p><a class="indexterm" name="id2611089"></a><a class="indexterm" name="id2611097"></a>
 	This is also a challenge to rise above the trouble spot. You call Stan's team together for a simple 
 	discussion, but it gets further out of hand.  When you return to your office, you find the following 
 	email in your in-box:
@@ -100,23 +100,23 @@
 	I also wish to advise that two of the recent recruits want to implement Kerberos authentication 
 	across all systems. I concur with the desire to improve security. One of the new guys who is championing
 	the move to Kerberos was responsible for the comment that caused the embarrassment.
-	</p><p><a class="indexterm" name="id2611036"></a><a class="indexterm" name="id2611043"></a><a class="indexterm" name="id2611051"></a><a class="indexterm" name="id2611059"></a>
+	</p><p><a class="indexterm" name="id2611134"></a><a class="indexterm" name="id2611142"></a><a class="indexterm" name="id2611150"></a><a class="indexterm" name="id2611158"></a>
 	I am experiencing difficulty in handling the sharp push for Kerberos. He claims that Kerberos, OpenLDAP, 
 	plus Samba-3 will seamlessly replace Microsoft Active Directory. I am a little out of my depth with respect 
 	to the feasibility of such a move, but have taken steps to pull both of them into line. With your consent, 
 	I would like to hire the services of a well-known Samba consultant to set the record straight.
-	</p><p><a class="indexterm" name="id2611078"></a><a class="indexterm" name="id2611085"></a><a class="indexterm" name="id2611093"></a><a class="indexterm" name="id2611101"></a><a class="indexterm" name="id2611109"></a><a class="indexterm" name="id2611117"></a>
+	</p><p><a class="indexterm" name="id2611176"></a><a class="indexterm" name="id2611184"></a><a class="indexterm" name="id2611192"></a><a class="indexterm" name="id2611200"></a><a class="indexterm" name="id2611208"></a><a class="indexterm" name="id2611216"></a>
 	I intend to use this report to answer the criticism raised and would like to establish a policy that we
 	will approve the use of Microsoft Windows Servers (and Active Directory) subject to all costs being covered 
 	out of the budget of the division that wishes to go its own way. I propose that dissenters will still remain
 	responsible to meet the budgeted contribution to IT operations as a whole. I believe we should not coerce 
 	use of any centrally proposed standards, but make all noncompliance the financial responsibility of the 
 	out-of-step division. Hopefully, this will encourage all divisions to walk with us and not alone.
-	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Stan</span></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611138"></a>Assignment Tasks</h3></div></div></div><p>
+	</p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Stan</span></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611237"></a>Assignment Tasks</h3></div></div></div><p>
 		You agreed with Stan's recommendations and hired a consultant to help defuse the powder
 		keg. The consultant's task is to provide a tractable answer to each of the issues raised. The consultant must be able
 		to support his or her claims, keep emotions to the side, and answer technically.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611154"></a>Dissection and Discussion</h2></div></div></div><p><a class="indexterm" name="id2611161"></a><a class="indexterm" name="id2611169"></a><a class="indexterm" name="id2611177"></a><a class="indexterm" name="id2611185"></a><a class="indexterm" name="id2611193"></a><a class="indexterm" name="id2611201"></a><a class="indexterm" name="id2611209"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611253"></a>Dissection and Discussion</h2></div></div></div><p><a class="indexterm" name="id2611260"></a><a class="indexterm" name="id2611268"></a><a class="indexterm" name="id2611276"></a><a class="indexterm" name="id2611284"></a><a class="indexterm" name="id2611291"></a><a class="indexterm" name="id2611299"></a><a class="indexterm" name="id2611307"></a>
 	Samba-3 is a tool. No one is pounding your door to make you use Samba. That is a choice that you are free to 
 	make or reject. It is likely that your decision to use Samba can greatly benefit your company. 
 	The Samba Team obviously believes that the Samba software is a worthy choice. 
@@ -124,18 +124,18 @@
 	someone to help manage your Samba installation, you can create income and employment. Alternately, 
 	money saved by not spending in the IT area can be spent elsewhere in the business. All money saved 
 	or spent creates employment.
-	</p><p><a class="indexterm" name="id2611230"></a><a class="indexterm" name="id2611238"></a><a class="indexterm" name="id2611246"></a><a class="indexterm" name="id2611254"></a><a class="indexterm" name="id2611262"></a>
+	</p><p><a class="indexterm" name="id2611329"></a><a class="indexterm" name="id2611337"></a><a class="indexterm" name="id2611345"></a><a class="indexterm" name="id2611353"></a><a class="indexterm" name="id2611361"></a>
 	In the long term, the use of Samba must be economically sustainable. In some situations, Samba is adopted
 	purely to provide file and print service interoperability on platforms that otherwise cannot provide 
 	access to data and to printers for Microsoft Windows clients. Samba is used by some businesses to
 	effect a reduction in the cost of providing IT services. Obviously, it is also used by some as an 
 	alternative to the use of a Microsoft file and print serving platforms with no consideration of costs.
-	</p><p><a class="indexterm" name="id2611282"></a><a class="indexterm" name="id2611290"></a><a class="indexterm" name="id2611298"></a><a class="indexterm" name="id2611306"></a>
+	</p><p><a class="indexterm" name="id2611381"></a><a class="indexterm" name="id2611389"></a><a class="indexterm" name="id2611397"></a><a class="indexterm" name="id2611405"></a>
 	It would be foolish to adopt a technology that might put any data or users at risk. Security affects 
 	everyone. The Samba-Team is fully cognizant of the responsibility they have to their users. 
 	The Samba documentation clearly reveals that full responsibility is accepted to fix anything 
 	that is broken.
-	</p><p><a class="indexterm" name="id2611322"></a><a class="indexterm" name="id2611330"></a><a class="indexterm" name="id2611338"></a><a class="indexterm" name="id2611346"></a><a class="indexterm" name="id2611358"></a><a class="indexterm" name="id2611366"></a><a class="indexterm" name="id2611374"></a><a class="indexterm" name="id2611382"></a><a class="indexterm" name="id2611389"></a><a class="indexterm" name="id2611397"></a><a class="indexterm" name="id2611405"></a>
+	</p><p><a class="indexterm" name="id2611421"></a><a class="indexterm" name="id2611429"></a><a class="indexterm" name="id2611437"></a><a class="indexterm" name="id2611445"></a><a class="indexterm" name="id2611456"></a><a class="indexterm" name="id2611464"></a><a class="indexterm" name="id2611472"></a><a class="indexterm" name="id2611480"></a><a class="indexterm" name="id2611488"></a><a class="indexterm" name="id2611496"></a><a class="indexterm" name="id2611504"></a>
 	There is a mistaken perception in the IT industry that commercial software providers are fully 
 	accountable for the defects in products. Open Source software comes with no warranty, so it is 
 	often assumed that its use confers a higher degree of risk. Everyone should read commercial software 
@@ -143,34 +143,34 @@
 	extent of liability that is accepted. Doing so soon dispels the popular notion that
 	commercial software vendors are willingly accountable for product defects. In many cases, the
 	commercial vendor accepts liability only to reimburse the price paid for the software. 
-	</p><p><a class="indexterm" name="id2611428"></a><a class="indexterm" name="id2611435"></a><a class="indexterm" name="id2611443"></a><a class="indexterm" name="id2611451"></a><a class="indexterm" name="id2611459"></a><a class="indexterm" name="id2611467"></a>
+	</p><p><a class="indexterm" name="id2611526"></a><a class="indexterm" name="id2611534"></a><a class="indexterm" name="id2611542"></a><a class="indexterm" name="id2611550"></a><a class="indexterm" name="id2611558"></a><a class="indexterm" name="id2611566"></a>
 	The real issues that a consumer (like you) needs answered are What is the way of escape from technical 
 	problems, and how long will it take? The average problem turnaround time in the Open Source community is 
 	approximately 48 hours. What does the EULA offer? What is the track record in the commercial software 
 	industry? What happens when your commercial vendor decides to cease providing support?
-	</p><p><a class="indexterm" name="id2611485"></a><a class="indexterm" name="id2611493"></a><a class="indexterm" name="id2611501"></a><a class="indexterm" name="id2611509"></a><a class="indexterm" name="id2611517"></a><a class="indexterm" name="id2611524"></a><a class="indexterm" name="id2611532"></a>
+	</p><p><a class="indexterm" name="id2611591"></a><a class="indexterm" name="id2611598"></a><a class="indexterm" name="id2611606"></a><a class="indexterm" name="id2611614"></a><a class="indexterm" name="id2611622"></a><a class="indexterm" name="id2611630"></a><a class="indexterm" name="id2611638"></a>
 	Open Source software at least puts you in possession of the source code. This means that when
 	all else fails, you can hire a programmer to solve the problem.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611545"></a>Technical Issues</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611650"></a>Technical Issues</h3></div></div></div><p>
 		Each issue is now discussed and, where appropriate, example implementation steps are
 		provided.
-		</p><div class="variablelist"><dl><dt><span class="term">Winbind and Security</span></dt><dd><p><a class="indexterm" name="id2611566"></a><a class="indexterm" name="id2611574"></a><a class="indexterm" name="id2611582"></a><a class="indexterm" name="id2611593"></a><a class="indexterm" name="id2611601"></a><a class="indexterm" name="id2611609"></a><a class="indexterm" name="id2611617"></a><a class="indexterm" name="id2611625"></a><a class="indexterm" name="id2611633"></a><a class="indexterm" name="id2611641"></a>
+		</p><div class="variablelist"><dl><dt><span class="term">Winbind and Security</span></dt><dd><p><a class="indexterm" name="id2611671"></a><a class="indexterm" name="id2611679"></a><a class="indexterm" name="id2611687"></a><a class="indexterm" name="id2611698"></a><a class="indexterm" name="id2611706"></a><a class="indexterm" name="id2611714"></a><a class="indexterm" name="id2611722"></a><a class="indexterm" name="id2611730"></a><a class="indexterm" name="id2611738"></a><a class="indexterm" name="id2611746"></a>
 				Windows network administrators may be dismayed to find that <code class="literal">winbind</code> 
 				exposes all domain users so that they may use their domain account credentials to 
 				log on to a UNIX/Linux system. The fact that all users in the domain can see the 
 				UNIX/Linux server in their Network Neighborhood and can browse the shares on the 
 				server seems to excite them further.
-				</p><p><a class="indexterm" name="id2611664"></a><a class="indexterm" name="id2611673"></a><a class="indexterm" name="id2611680"></a><a class="indexterm" name="id2611688"></a>
+				</p><p><a class="indexterm" name="id2611770"></a><a class="indexterm" name="id2611778"></a><a class="indexterm" name="id2611786"></a><a class="indexterm" name="id2611794"></a>
 				<code class="literal">winbind</code> provides for the UNIX/Linux domain member server or 
 				client, the same as one would obtain by adding a Microsoft Windows server or 
 				client to the domain. The real objection is the fact that Samba is not MS Windows 
 				and therefore requires handling a little differently from the familiar Windows systems.
 				One must recognize fear of the unknown.
-				</p><p><a class="indexterm" name="id2611711"></a><a class="indexterm" name="id2611719"></a><a class="indexterm" name="id2611727"></a><a class="indexterm" name="id2611735"></a><a class="indexterm" name="id2611743"></a><a class="indexterm" name="id2611755"></a>
+				</p><p><a class="indexterm" name="id2611817"></a><a class="indexterm" name="id2611825"></a><a class="indexterm" name="id2611833"></a><a class="indexterm" name="id2611841"></a><a class="indexterm" name="id2611848"></a><a class="indexterm" name="id2611860"></a>
 				Windows network administrators need to recognize that <code class="literal">winbind</code> does
 				not, and cannot, override account controls set using the Active Directory management
 				tools. The control is the same. Have no fear.
-				</p><p><a class="indexterm" name="id2611775"></a><a class="indexterm" name="id2611783"></a><a class="indexterm" name="id2611794"></a><a class="indexterm" name="id2611802"></a><a class="indexterm" name="id2611810"></a><a class="indexterm" name="id2611818"></a><a class="indexterm" name="id2611826"></a><a class="indexterm" name="id2611834"></a><a class="indexterm" name="id2611842"></a><a class="indexterm" name="id2611850"></a>
+				</p><p><a class="indexterm" name="id2611881"></a><a class="indexterm" name="id2611888"></a><a class="indexterm" name="id2611900"></a><a class="indexterm" name="id2611908"></a><a class="indexterm" name="id2611916"></a><a class="indexterm" name="id2611923"></a><a class="indexterm" name="id2611931"></a><a class="indexterm" name="id2611939"></a><a class="indexterm" name="id2611947"></a><a class="indexterm" name="id2611955"></a>
 				Where Samba and the ADS domain account information obtained through the use of
 				<code class="literal">winbind</code> permits access, by browsing or by the drive mapping to
 				a share, to data that should be better protected. This can only happen when security
@@ -178,14 +178,14 @@
 				on:
 				</p><div class="itemizedlist"><ul type="disc"><li><p>Shares themselves (i.e., the logical share itself)</p></li><li><p>The share definition in <code class="filename">smb.conf</code></p></li><li><p>The shared directories and files using UNIX permissions</p></li><li><p>Using Windows 2000 ACLs  if the file system is POSIX enabled</p></li></ul></div><p>
 				Examples of each are given in <a class="link" href="kerberos.html#ch10expl" title="Implementation">&#8220;Implementation&#8221;</a>.
-				</p></dd><dt><span class="term">User and Group Controls</span></dt><dd><p><a class="indexterm" name="id2611924"></a><a class="indexterm" name="id2611932"></a><a class="indexterm" name="id2611943"></a><a class="indexterm" name="id2611954"></a><a class="indexterm" name="id2611962"></a><a class="indexterm" name="id2611970"></a><a class="indexterm" name="id2611978"></a><a class="indexterm" name="id2611986"></a><a class="indexterm" name="id2611994"></a>
+				</p></dd><dt><span class="term">User and Group Controls</span></dt><dd><p><a class="indexterm" name="id2612029"></a><a class="indexterm" name="id2612037"></a><a class="indexterm" name="id2612049"></a><a class="indexterm" name="id2612060"></a><a class="indexterm" name="id2612068"></a><a class="indexterm" name="id2612075"></a><a class="indexterm" name="id2612083"></a><a class="indexterm" name="id2612091"></a><a class="indexterm" name="id2612099"></a>
 				User and group management facilities as known in the Windows ADS environment may be
 				used to provide equivalent access control constraints or to provide equivalent
 				permissions and privileges on Samba servers. Samba offers greater flexibility in the
 				use of user and group controls because it has additional layers of control compared to
 				Windows 200x/XP. For example, access controls on a Samba server may be set within
 				the share definition in a manner for which Windows has no equivalent.
-				</p><p><a class="indexterm" name="id2612014"></a><a class="indexterm" name="id2612022"></a><a class="indexterm" name="id2612030"></a><a class="indexterm" name="id2612037"></a><a class="indexterm" name="id2612049"></a><a class="indexterm" name="id2612057"></a><a class="indexterm" name="id2612065"></a>
+				</p><p><a class="indexterm" name="id2612119"></a><a class="indexterm" name="id2612127"></a><a class="indexterm" name="id2612135"></a><a class="indexterm" name="id2612143"></a><a class="indexterm" name="id2612154"></a><a class="indexterm" name="id2612162"></a><a class="indexterm" name="id2612170"></a>
 				In any serious analysis of system security, it is important to examine the safeguards
 				that remain when all other protective measures fail. An administrator may inadvertently
 				set excessive permissions on the file system of a shared resource, or he may set excessive
@@ -193,35 +193,35 @@
 				the data would indeed be laid bare to abuse. Yet, within a Samba share definition, it is
 				possible to guard against that by enforcing controls on the share definition itself. You
 				see a practical example of this a little later in this chapter.
-				</p><p><a class="indexterm" name="id2612097"></a><a class="indexterm" name="id2612105"></a>
+				</p><p><a class="indexterm" name="id2612192"></a><a class="indexterm" name="id2612200"></a>
 				The report that is critical of Samba really ought to have exercised greater due
 				diligence: the real weakness is on the side of a Microsoft Windows environment.
-				</p></dd><dt><span class="term">Security Overall</span></dt><dd><p><a class="indexterm" name="id2612127"></a>
+				</p></dd><dt><span class="term">Security Overall</span></dt><dd><p><a class="indexterm" name="id2612222"></a>
 				Samba is designed in such a manner that weaknesses inherent in the design of
 				Microsoft Windows networking ought not to expose the underlying UNIX/Linux file
 				system in any way. All software has potential defects, and Samba is no exception.
 				What matters more is how defects that are discovered get dealt with.
-				</p><p><a class="indexterm" name="id2612144"></a><a class="indexterm" name="id2612151"></a><a class="indexterm" name="id2612159"></a><a class="indexterm" name="id2612167"></a>
+				</p><p><a class="indexterm" name="id2612238"></a><a class="indexterm" name="id2612246"></a><a class="indexterm" name="id2612254"></a><a class="indexterm" name="id2612262"></a>
 				The Samba Team totally agrees with the necessity to observe and fully implement
 				every security facility to provide a level of protection and security that is necessary
 				and that the end user (or network administrator) needs. Never would the Samba Team
 				recommend a compromise to system security, nor would deliberate defoliation of
 				security be publicly condoned; yet this is the practice by many Windows network
 				administrators just to make happy users who have no notion of consequential risk.
-				</p><p><a class="indexterm" name="id2612187"></a><a class="indexterm" name="id2612195"></a><a class="indexterm" name="id2612203"></a><a class="indexterm" name="id2612211"></a><a class="indexterm" name="id2612219"></a><a class="indexterm" name="id2612227"></a><a class="indexterm" name="id2612235"></a>
+				</p><p><a class="indexterm" name="id2612282"></a><a class="indexterm" name="id2612290"></a><a class="indexterm" name="id2612298"></a><a class="indexterm" name="id2612306"></a><a class="indexterm" name="id2612314"></a><a class="indexterm" name="id2612322"></a><a class="indexterm" name="id2612330"></a>
 				The report condemns Samba for releasing updates and security fixes, yet Microsoft
 				online updates need to be applied almost weekly. The answer to the criticism 
 				lies in the fact that Samba development is continuing, documentation is improving, 
 				user needs are being increasingly met or exceeded, and security updates are issued 
 				with a short turnaround time.
-				</p><p><a class="indexterm" name="id2612252"></a><a class="indexterm" name="id2612260"></a><a class="indexterm" name="id2612268"></a><a class="indexterm" name="id2612276"></a><a class="indexterm" name="id2612284"></a>
+				</p><p><a class="indexterm" name="id2612347"></a><a class="indexterm" name="id2612355"></a><a class="indexterm" name="id2612363"></a><a class="indexterm" name="id2612371"></a><a class="indexterm" name="id2612379"></a>
 				The release of Samba-4 is expected around late 2004 to early 2005 and involves a near 
 				complete rewrite to permit extensive modularization and to prepare Samba for new 
 				functionality planned for addition during the next-generation series. The Samba Team 
 				is responsible and can be depended upon; the history to date suggests a high 
 				degree of dependability and on charter development consistent with published 
 				roadmap projections.
-				</p><p><a class="indexterm" name="id2612307"></a><a class="indexterm" name="id2612315"></a><a class="indexterm" name="id2612326"></a><a class="indexterm" name="id2612338"></a><a class="indexterm" name="id2612346"></a><a class="indexterm" name="id2612354"></a><a class="indexterm" name="id2612362"></a>
+				</p><p><a class="indexterm" name="id2612409"></a><a class="indexterm" name="id2612417"></a><a class="indexterm" name="id2612429"></a><a class="indexterm" name="id2612440"></a><a class="indexterm" name="id2612448"></a><a class="indexterm" name="id2612456"></a><a class="indexterm" name="id2612464"></a>
 				Not well published is the fact that Microsoft was a foundation member of
 				the Common Internet File System (CIFS) initiative, together with the participation 
 				of the network attached storage (NAS) industry. Unfortunately, for the past few years,
@@ -230,7 +230,7 @@
 				space. The Samba Team has maintained consistent presence and leadership at all
 				CIFS conferences and at the interoperability laboratories run concurrently with
 				them.
-				</p></dd><dt><span class="term">Cryptographic Controls (schannel, sign'n'seal)</span></dt><dd><p><a class="indexterm" name="id2612391"></a><a class="indexterm" name="id2612399"></a><a class="indexterm" name="id2612407"></a>
+				</p></dd><dt><span class="term">Cryptographic Controls (schannel, sign'n'seal)</span></dt><dd><p><a class="indexterm" name="id2612494"></a><a class="indexterm" name="id2612502"></a><a class="indexterm" name="id2612510"></a>
 				The report correctly mentions that Samba did not support the most recent
 				<code class="constant">schannel</code> and <code class="constant">digital sign'n'seal</code> features
 				of Microsoft Windows NT/200x/XPPro products. This is one of the key features 
@@ -238,7 +238,7 @@
 				seldom a reflection of current practice, and in many respects reports are like a
 				pathology report  they reflect accurately (at best) status at a snapshot in time.
 				Meanwhile, the world moves on.
-				</p><p><a class="indexterm" name="id2612437"></a><a class="indexterm" name="id2612445"></a><a class="indexterm" name="id2612453"></a><a class="indexterm" name="id2612460"></a><a class="indexterm" name="id2612468"></a><a class="indexterm" name="id2612483"></a><a class="indexterm" name="id2612491"></a>
+				</p><p><a class="indexterm" name="id2612540"></a><a class="indexterm" name="id2612548"></a><a class="indexterm" name="id2612555"></a><a class="indexterm" name="id2612563"></a><a class="indexterm" name="id2612571"></a><a class="indexterm" name="id2612586"></a><a class="indexterm" name="id2612594"></a>
 				It should be pointed out that had clear public specifications for the protocols
 				been published, it would have been much easier to implement these features and would have
 				taken less time to do. The sole mechanism used to find an algorithm that is compatible
@@ -246,7 +246,7 @@
 				and trial-and-error implementation of potential techniques. The real value of public
 				and defensible standards is obvious to all and would have enabled more secure networking
 				for everyone.
-				</p><p><a class="indexterm" name="id2612512"></a><a class="indexterm" name="id2612520"></a>
+				</p><p><a class="indexterm" name="id2612614"></a><a class="indexterm" name="id2612622"></a>
 				Critics of Samba often ignore fundamental problems that may plague (or may have plagued)
 				the users of Microsoft's products also. Those who are first to criticize Samba
 				for not rushing into release of <code class="constant">digital sign'n'seal</code> support
@@ -258,7 +258,7 @@
 				implementation of sign'n'seal. They provide a work-around that is not trivial for many
 				Windows networking sites. From notes such as this it is clear that there are benefits
 				from not rushing new technology out of the door too soon.
-				</p><p><a class="indexterm" name="id2612560"></a><a class="indexterm" name="id2612568"></a><a class="indexterm" name="id2612576"></a><a class="indexterm" name="id2612584"></a><a class="indexterm" name="id2612592"></a><a class="indexterm" name="id2612600"></a><a class="indexterm" name="id2612608"></a><a class="indexterm" name="id2612616"></a><a class="indexterm" name="id2612624"></a>
+				</p><p><a class="indexterm" name="id2612662"></a><a class="indexterm" name="id2612670"></a><a class="indexterm" name="id2612678"></a><a class="indexterm" name="id2612686"></a><a class="indexterm" name="id2612694"></a><a class="indexterm" name="id2612702"></a><a class="indexterm" name="id2612710"></a><a class="indexterm" name="id2612718"></a><a class="indexterm" name="id2612726"></a>
 				One final comment is warranted. If companies want more secure networking protocols,
 				the most effective method by which this can be achieved is by users seeking
 				and working together to help define open and publicly refereed standards. The
@@ -266,10 +266,7 @@
 				clandestine framework of secrecy, under claims of digital rights protection, does
 				not favor the diffusion of safe networking protocols and certainly does not
 				help the consumer to make a better choice.
-				</p></dd><dt><span class="term">Active Directory Replacement with Kerberos, LDAP, and Samba
-				        <a class="indexterm" name="id2612649"></a><a class="indexterm" name="id2612661"></a><a class="indexterm" name="id2612669"></a><a class="indexterm" name="id2612677"></a>
-
-			</span></dt><dd><p>
+				</p></dd><dt><span class="term">Active Directory Replacement with Kerberos, LDAP, and Samba</span></dt><dd><p>
 				</p><div class="literallayout"><p>����</p></div><p>
 				The Microsoft networking protocols extensively make use of remote procedure call (RPC)
 				technology. Active Directory is not a simple mixture of LDAP and Kerberos together
@@ -277,7 +274,7 @@
 				of them that uses RPCs that are not supported by any of these component technologies
 				and yet by which they are made to interoperate in ways that the components do not
 				support.
-				</p><p><a class="indexterm" name="id2612711"></a><a class="indexterm" name="id2612723"></a><a class="indexterm" name="id2612731"></a><a class="indexterm" name="id2612739"></a><a class="indexterm" name="id2612747"></a>
+				</p><p><a class="indexterm" name="id2612814"></a><a class="indexterm" name="id2612825"></a><a class="indexterm" name="id2612833"></a><a class="indexterm" name="id2612841"></a><a class="indexterm" name="id2612849"></a>
 				In order to make the popular request for Samba to be an Active Directory Server a
 				reality, it is necessary to add to OpenLDAP, Kerberos, as well as Samba, RPC calls
 				that are not presently supported. The Samba Team has not been able to gain critical
@@ -285,34 +282,34 @@
 				challenge of developing and integrating the necessary technologies. Therefore, if
 				the Samba Team does not make it a priority to absorb Kerberos and LDAP functionality
 				into the Samba project, this dream request cannot become a reality.
-				</p><p><a class="indexterm" name="id2612768"></a><a class="indexterm" name="id2612776"></a><a class="indexterm" name="id2612784"></a><a class="indexterm" name="id2612795"></a><a class="indexterm" name="id2612802"></a>
+				</p><p><a class="indexterm" name="id2612880"></a><a class="indexterm" name="id2612888"></a><a class="indexterm" name="id2612896"></a><a class="indexterm" name="id2612907"></a><a class="indexterm" name="id2612914"></a>
 				At this time, the integration of LDAP, Kerberos, and the missing RPCs is not on the
 				Samba development roadmap. If it is not on the published roadmap, it cannot be delivered
 				anytime soon. Ergo, ADS server support is not a current goal for Samba development.
 				The Samba Team is most committed to permitting Samba to be a full ADS domain member
 				that is increasingly capable of being managed using Microsoft Windows MMC tools.
-				</p></dd></dl></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2612822"></a>Kerberos Exposed</h4></div></div></div><p><a class="indexterm" name="id2612829"></a><a class="indexterm" name="id2612837"></a><a class="indexterm" name="id2612845"></a>
+				</p></dd></dl></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2612934"></a>Kerberos Exposed</h4></div></div></div><p><a class="indexterm" name="id2612941"></a><a class="indexterm" name="id2612949"></a><a class="indexterm" name="id2612957"></a>
 	Kerberos is a network authentication protocol that provides secure authentication for 
 	client-server applications by using secret-key cryptography. Firewalls are an insufficient 
 	barrier mechanism in today's networking world; at best they only restrict incoming network 
 	traffic but cannot prevent network traffic that comes from authorized locations from 
 	performing unauthorized activities.
-	</p><p><a class="indexterm" name="id2612863"></a><a class="indexterm" name="id2612871"></a><a class="indexterm" name="id2612879"></a>
+	</p><p><a class="indexterm" name="id2612975"></a><a class="indexterm" name="id2612983"></a><a class="indexterm" name="id2612991"></a>
 	Kerberos was created by MIT as a solution to network security problems. The Kerberos protocol uses 
 	strong cryptography so that a client can prove its identity to a server (and vice versa) across an 
 	insecure network connection. After a client and server has used Kerberos to prove their identity, 
 	they can also encrypt all of their communications to assure privacy and data integrity as they go 
 	about their business.
-	</p><p><a class="indexterm" name="id2612897"></a><a class="indexterm" name="id2612905"></a><a class="indexterm" name="id2612913"></a><a class="indexterm" name="id2612921"></a><a class="indexterm" name="id2612932"></a>
+	</p><p><a class="indexterm" name="id2613009"></a><a class="indexterm" name="id2613017"></a><a class="indexterm" name="id2613025"></a><a class="indexterm" name="id2613033"></a><a class="indexterm" name="id2613044"></a>
 	Kerberos is a trusted third-party service. That means that there is a third party (the kerberos 
 	server) that is trusted by all the entities on the network (users and services, usually called 
 	principals). All principals share a secret password (or key) with the kerberos server and this 
 	enables principals to verify that the messages from the kerberos server are authentic. Therefore, 
 	trusting the kerberos server, users and services can authenticate each other.
 	</p><p>
-	<a class="indexterm" name="id2612952"></a>
-	<a class="indexterm" name="id2612959"></a>
-	<a class="indexterm" name="id2612966"></a>
+	<a class="indexterm" name="id2613064"></a>
+	<a class="indexterm" name="id2613071"></a>
+	<a class="indexterm" name="id2613078"></a>
 	Kerberos was, until recently, a technology that was restricted from being exported from the United States.
 	For many years that hindered global adoption of more secure networking technologies both within the United States
 	and abroad. A free and unencumbered implementation of MIT Kerberos has been produced in Europe
@@ -322,11 +319,11 @@
 	significant surge forward in the development of Kerberos-enabled applications and in the general deployment
 	and use of Kerberos across the spectrum of the information technology industry.
 	</p><p>
-	<a class="indexterm" name="id2612995"></a>
+	<a class="indexterm" name="id2613107"></a>
 	A storm has broken out concerning interoperability between MIT Kerberos and Microsofts' implementation
 	of it. For example, a 2002
 	<a class="ulink" href="http://www.idg.com.sg/idgwww.nsf/0/5DDA8D153A7505A748256BAB000D992A?OpenDocument" target="_top">IDG</a>
-	report<sup>[<a name="id2613014" href="#ftn.id2613014" class="footnote">13</a>]</sup> by
+	report<sup>[<a name="id2613126" href="#ftn.id2613126" class="footnote">13</a>]</sup> by
 	states:
 	</p><div class="blockquote"><blockquote class="blockquote"><p>
 	A Microsoft Corp. executive testified at the software giant's remedy hearing that the company goes to 
@@ -334,7 +331,7 @@
 	with Windows. But a lawyer with the states suing Microsoft pointed out that when it comes to the company's 
 	use of the Kerberos authentication specification, not everyone agrees.
 	</p><p>
-	<a class="indexterm" name="id2613041"></a>
+	<a class="indexterm" name="id2613152"></a>
 	Robert Short, vice president of Windows core technology at Microsoft, wrote in his direct testimony prepared 
 	before his appearance that non-Microsoft operating systems can disregard the portion of the Kerberos version 
 	5 specification that Windows clients use for proprietary purposes and still achieve interoperability with 
@@ -342,8 +339,8 @@
 	Windows-specific authorization data, Short wrote. The designers of Kerberos left these fields undefined so 
 	that software developers could add their own authorization information, he said.
 	</p></blockquote></div><p>
-	<a class="indexterm" name="id2613065"></a>
-	<a class="indexterm" name="id2613071"></a>
+	<a class="indexterm" name="id2613176"></a>
+	<a class="indexterm" name="id2613182"></a>
 	It so happens that Microsoft Windows clients depend on and expect the contents of the <span class="emphasis"><em>unspecified
 	fields</em></span> in the Kerberos 5 communications data stream for their Windows interoperability,
 	particularly when Samba is expected to emulate a Windows Server 200x domain controller. But the interoperability
@@ -355,7 +352,7 @@
 	Microsoft makes the following comment in a reference in a
 	<a class="ulink" href="http://www.microsoft.com/technet/itsolutions/interop/mgmt/kerberos.asp" target="_top">
 	technet</a> article:
-	</p><div class="blockquote"><blockquote class="blockquote"><p><a class="indexterm" name="id2613106"></a><a class="indexterm" name="id2613118"></a>
+	</p><div class="blockquote"><blockquote class="blockquote"><p><a class="indexterm" name="id2613217"></a><a class="indexterm" name="id2613229"></a>
 	The DCE Security Services are also layered on the Kerberos protocol. DCE authentication services use RPC 
 	representation of Kerberos protocol messages. In addition, DCE uses the authorization data field in Kerberos 
 	tickets to convey Privilege Attribute Certificates (PACs) that define user identity and group membership. 
@@ -365,10 +362,10 @@
 	Windows NT access control information.
 	</p></blockquote></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch10expl"></a>Implementation</h2></div></div></div><p>
 	The following procedures outline the implementation of the security measures discussed so far.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613169"></a>Share Access Controls</h3></div></div></div><p><a class="indexterm" name="id2613176"></a><a class="indexterm" name="id2613184"></a><a class="indexterm" name="id2613192"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613280"></a>Share Access Controls</h3></div></div></div><p><a class="indexterm" name="id2613287"></a><a class="indexterm" name="id2613295"></a><a class="indexterm" name="id2613303"></a>
 	Access control entries placed on the share itself act as a filter at the time a when CIFS/SMB client (such as
 	Windows XP Pro) attempts to make a connection to the Samba server.
-	</p><div class="procedure"><a name="id2613205"></a><p class="title"><b>Procedure�11.1.�Create/Edit/Delete Share ACLs</b></p><ol type="1"><li><p><a class="indexterm" name="id2613216"></a><a class="indexterm" name="id2613224"></a>
+	</p><div class="procedure"><a name="id2613316"></a><p class="title"><b>Procedure�11.1.�Create/Edit/Delete Share ACLs</b></p><ol type="1"><li><p><a class="indexterm" name="id2613327"></a><a class="indexterm" name="id2613335"></a>
 		From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator 
 		account (on Samba domains, this is usually the account called <code class="constant">root</code>).
 		</p></li><li><p>
@@ -377,16 +374,16 @@
 		</p></li><li><p>
 		In the left panel,
 		<span class="guimenu">[Right mouse menu item] Computer Management (Local)</span> &#8594; <span class="guimenuitem">Connect to another computer ...</span> &#8594; <span class="guimenuitem">Browse...</span> &#8594; <span class="guimenuitem">Advanced</span> &#8594; <span class="guimenuitem">Find Now</span>. In the lower panel, click on the name of the server you wish to
-		administer. Click <span class="guimenu">OK</span> &#8594; <span class="guimenuitem">OK</span> &#8594; <span class="guimenuitem">OK</span>.<a class="indexterm" name="id2613347"></a>
+		administer. Click <span class="guimenu">OK</span> &#8594; <span class="guimenuitem">OK</span> &#8594; <span class="guimenuitem">OK</span>.<a class="indexterm" name="id2613458"></a>
 		In the left panel, the entry <span class="guimenu">Computer Management (Local)</span> should now reflect
 		the change made. For example, if the server you are administering is called <code class="constant">FRODO</code>,
 		the Computer Management entry should now say <span class="guimenu">Computer Management (FRODO)</span>.
 		</p></li><li><p>
 		In the left panel, click <span class="guimenu">Computer Management (FRODO)</span> &#8594; <span class="guimenuitem">[+] Shared Folders</span> &#8594; <span class="guimenuitem">Shares</span>.
-		</p></li><li><p><a class="indexterm" name="id2613411"></a><a class="indexterm" name="id2613419"></a>
+		</p></li><li><p><a class="indexterm" name="id2613522"></a><a class="indexterm" name="id2613530"></a>
 		In the right panel, double-click on the share on which you wish to set/edit ACLs. This
 		will bring up the Properties panel. Click the <span class="guimenu">Share Permissions</span> tab.
-		</p></li><li><p><a class="indexterm" name="id2613442"></a><a class="indexterm" name="id2613450"></a><a class="indexterm" name="id2613458"></a><a class="indexterm" name="id2613466"></a><a class="indexterm" name="id2613474"></a><a class="indexterm" name="id2613482"></a>
+		</p></li><li><p><a class="indexterm" name="id2613553"></a><a class="indexterm" name="id2613561"></a><a class="indexterm" name="id2613569"></a><a class="indexterm" name="id2613577"></a><a class="indexterm" name="id2613585"></a><a class="indexterm" name="id2613593"></a>
 		You may now edit/add/remove access control settings. Be very careful. Many problems have been
 		created by people who decided that everyone should be rejected but one particular group should
 		have full control. This is a catch-22 situation because members of that particular group also
@@ -395,20 +392,20 @@
 		</p></li><li><p>
 		When you are done with editing, close all panels by clicking through the <span class="guimenu">OK</span>
 		buttons.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613518"></a>Share Definition Controls</h3></div></div></div><p><a class="indexterm" name="id2613525"></a><a class="indexterm" name="id2613536"></a><a class="indexterm" name="id2613544"></a><a class="indexterm" name="id2613552"></a><a class="indexterm" name="id2613560"></a><a class="indexterm" name="id2613568"></a>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613629"></a>Share Definition Controls</h3></div></div></div><p><a class="indexterm" name="id2613636"></a><a class="indexterm" name="id2613648"></a><a class="indexterm" name="id2613655"></a><a class="indexterm" name="id2613663"></a><a class="indexterm" name="id2613671"></a><a class="indexterm" name="id2613679"></a>
 	Share-definition-based access controls can be used like a checkpoint or like a pile-driver. Just as a
 	checkpoint can be used to require someone who wants to get through to meet certain requirements, so
 	it is possible to require the user (or group the user belongs to) to meet specified credential-related 
 	objectives. It can be likened to a pile-driver by overriding default controls in that having met the 
 	credential-related objectives, the user can be granted powers and privileges that would not normally be 
 	available under default settings.
-	</p><p><a class="indexterm" name="id2613588"></a><a class="indexterm" name="id2613596"></a><a class="indexterm" name="id2613604"></a><a class="indexterm" name="id2613612"></a>
+	</p><p><a class="indexterm" name="id2613699"></a><a class="indexterm" name="id2613707"></a><a class="indexterm" name="id2613715"></a><a class="indexterm" name="id2613723"></a>
 	It must be emphasized that the controls discussed here can act as a filter or give rights of passage
 	that act as a superstructure over normal directory and file access controls. However, share-level
 	ACLs act at a higher level than do share definition controls because the user must filter through the
 	share-level controls to get to the share-definition controls. The proper hierarchy of controls implemented
 	by Samba and Windows networking consists of:
-	</p><div class="orderedlist"><ol type="1"><li><p>Share-level ACLs</p></li><li><p>Share-definition controls</p></li><li><p>Directory and file permissions</p></li><li><p>Directory and file POSIX ACLs</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613658"></a>Checkpoint Controls</h4></div></div></div><p><a class="indexterm" name="id2613664"></a>
+	</p><div class="orderedlist"><ol type="1"><li><p>Share-level ACLs</p></li><li><p>Share-definition controls</p></li><li><p>Directory and file permissions</p></li><li><p>Directory and file POSIX ACLs</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613769"></a>Checkpoint Controls</h4></div></div></div><p><a class="indexterm" name="id2613775"></a>
 	Consider the following extract from a <code class="filename">smb.conf</code> file defining the share called <code class="constant">Apps</code>:
 </p><pre class="screen">
 [Apps]
@@ -419,19 +416,19 @@
 </pre><p>
 	This definition permits only those who are members of the group called <code class="constant">Employees</code> to 
 	access the share.
-	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p><a class="indexterm" name="id2613700"></a><a class="indexterm" name="id2613711"></a><a class="indexterm" name="id2613720"></a><a class="indexterm" name="id2613728"></a><a class="indexterm" name="id2613735"></a>
+	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p><a class="indexterm" name="id2613811"></a><a class="indexterm" name="id2613822"></a><a class="indexterm" name="id2613831"></a><a class="indexterm" name="id2613839"></a><a class="indexterm" name="id2613846"></a>
 	On domain member servers and clients, even when the <em class="parameter"><code>winbind use default domain</code></em> has
 	been specified, the use of domain accounts in security controls requires fully qualified domain specification,
 	for example, <a class="link" href="smb.conf.5.html#VALIDUSERS" target="_top">valid users = @"MEGANET\Northern Engineers"</a>. 
 	Note the necessity to use the double quotes to avoid having the space in the Windows group name interpreted as a
 	delimiter. 
-	</p></div><p><a class="indexterm" name="id2613771"></a><a class="indexterm" name="id2613778"></a><a class="indexterm" name="id2613786"></a>
+	</p></div><p><a class="indexterm" name="id2613882"></a><a class="indexterm" name="id2613889"></a><a class="indexterm" name="id2613897"></a>
 	If there is an ACL on the share itself to permit read/write access for all <code class="constant">Employees</code>
 	as well as read/write for the group <code class="constant">Doctors</code>, both groups are permitted through
 	to the share. However, at the moment an attempt is made to set up a connection to the share, a member of
 	the group <code class="constant">Doctors</code>, who is not also a member of the group <code class="constant">Employees</code>,
 	would immediately fail to validate.
-	</p><p><a class="indexterm" name="id2613817"></a>
+	</p><p><a class="indexterm" name="id2613928"></a>
 	Consider another example. In this case, you want to permit all members of the group <code class="constant">Employees</code>
 	except the user <code class="constant">patrickj</code> to access the <code class="constant">Apps</code> share. This can be
 	easily achieved by setting a share-level ACL permitting only <code class="constant">Employees</code> to access the share,
@@ -444,7 +441,7 @@
         read only = Yes
         invalid users = patrickj
 </pre><p>
-	    <a class="indexterm" name="id2613858"></a>
+	    <a class="indexterm" name="id2613969"></a>
 	Let us assume that you want to permit the user <code class="constant">gbshaw</code> to manage any file in the
 	UNIX/Linux file system directory <code class="filename">/data/apps</code>, but you do not want to grant any write
 	permissions beyond that directory tree. Here is one way this can be done:
@@ -456,7 +453,7 @@
         invalid users = patrickj
         admin users = gbshaw
 </pre><p>
-	    <a class="indexterm" name="id2613888"></a>
+	    <a class="indexterm" name="id2613999"></a>
 	Now we have a set of controls that permits only <code class="constant">Employees</code> who are also members of
 	the group <code class="constant">Doctors</code>, excluding the user <code class="constant">patrickj</code>, to have 
 	read-only privilege, but the user <code class="constant">gbshaw</code> is granted administrative rights.
@@ -478,11 +475,11 @@
         admin users = gbshaw
         write list = peters
 </pre><p>
-	    <a class="indexterm" name="id2613948"></a>
+	    <a class="indexterm" name="id2614059"></a>
 	This is a particularly complex example at this point, but it begins to demonstrate the possibilities.
 	You should refer to the online manual page for the <code class="filename">smb.conf</code> file for more information regarding
 	the checkpoint controls that Samba implements.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613970"></a>Override Controls</h4></div></div></div><p><a class="indexterm" name="id2613977"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614081"></a>Override Controls</h4></div></div></div><p><a class="indexterm" name="id2614088"></a>
 	Override controls implemented by Samba permit actions like the adoption of a different identity 
 	during file system operations, the forced overwriting of normal file and directory permissions,
 	and so on. You should refer to the online manual page for the <code class="filename">smb.conf</code> file for more information regarding
@@ -500,14 +497,14 @@
 	force user = billc
 	force group = Mentors
 </pre><p>
-	    <a class="indexterm" name="id2614020"></a><a class="indexterm" name="id2614028"></a>
+	    <a class="indexterm" name="id2614132"></a><a class="indexterm" name="id2614140"></a>
 	That is all there is to it. Well, it is almost that simple. The downside of this method is that
 	users are logged onto the Windows client as themselves, and then immediately before accessing the
 	file, Samba makes system calls to change the effective user and group to the forced settings
 	specified, completes the file transaction, and then reverts to the actually logged-on identity.
 	This imposes significant overhead on Samba. The alternative way to effectively achieve the same result
 	(but with lower system CPU overheads) is described next.
-	</p><p><a class="indexterm" name="id2614049"></a><a class="indexterm" name="id2614057"></a><a class="indexterm" name="id2614065"></a><a class="indexterm" name="id2614076"></a><a class="indexterm" name="id2614084"></a>
+	</p><p><a class="indexterm" name="id2614160"></a><a class="indexterm" name="id2614168"></a><a class="indexterm" name="id2614176"></a><a class="indexterm" name="id2614187"></a><a class="indexterm" name="id2614195"></a>
 	The use of the <em class="parameter"><code>force user</code></em> or the <em class="parameter"><code>force group</code></em> may
 	also have a severe impact on system (particularly on Windows client) performance. If opportunistic
 	locking is enabled on the share (the default), it causes an <code class="constant">oplock break</code> to be
@@ -517,7 +514,7 @@
 	waiting for the file system transaction (read or write) to complete. The result can be a profound
 	apparent performance degradation as the client continually attempts to reconnect to overcome the
 	effect of the lost <code class="constant">oplock break</code>, or time-out.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614131"></a>Share Point Directory and File Permissions</h3></div></div></div><p><a class="indexterm" name="id2614138"></a><a class="indexterm" name="id2614146"></a><a class="indexterm" name="id2614154"></a><a class="indexterm" name="id2614162"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614242"></a>Share Point Directory and File Permissions</h3></div></div></div><p><a class="indexterm" name="id2614250"></a><a class="indexterm" name="id2614257"></a><a class="indexterm" name="id2614265"></a><a class="indexterm" name="id2614273"></a>
 	Samba has been designed and implemented so that it respects as far as is feasible the security and
 	user privilege controls that are built into the UNIX/Linux operating system. Samba does nothing
 	with respect to file system access that violates file system permission settings, unless it is
@@ -525,11 +522,13 @@
 	UNIX file system controls, this chapter does not document simple information that can be obtained
 	from a basic UNIX training guide. Instead, one common example of a typical problem is used
 	to demonstrate the most effective solution referred to in the immediately preceding paragraph.
-	</p><p><a class="indexterm" name="id2614185"></a><a class="indexterm" name="id2614193"></a><a class="indexterm" name="id2614201"></a>
+	</p><p><a class="indexterm" name="id2614296"></a><a class="indexterm" name="id2614304"></a><a class="indexterm" name="id2614312"></a>
 	One of the common issues that repeatedly pops up on the Samba mailing lists involves the saving of
 	Microsoft Office files (Word and Excel) to a network drive. Here is the typical sequence:
 	</p><div class="orderedlist"><ol type="1"><li><p>
 		A user opens a Word document from a network drive. The file was owned by user <code class="constant">janetp</code>
+		and  [users], and was set read/write-enabled for everyone.
+		A user opens a Word document from a network drive. The file was owned by user <code class="constant">janetp</code>
 		and <code class="constant">users</code>, and was set read/write-enabled for everyone.
 		</p></li><li><p>
 		File changes and edits are made.
@@ -545,7 +544,7 @@
 	There have been many postings over the years that report the same basic problem. Frequently Samba users
 	want to know when this &#8220;<span class="quote">bug</span>&#8221; will be fixed. The fact is, this is not a bug in Samba at all.
 	Here is the real sequence of what happens in this case.
-	</p><p><a class="indexterm" name="id2614288"></a><a class="indexterm" name="id2614296"></a><a class="indexterm" name="id2614304"></a>
+	</p><p><a class="indexterm" name="id2614413"></a><a class="indexterm" name="id2614421"></a><a class="indexterm" name="id2614429"></a>
 	When the user saves a file, MS Word creates a new (temporary) file. This file is naturally owned
 	by the user who creates the file (<code class="constant">billc</code>) and has the permissions that follow
 	that user's default settings within the operating system (UNIX/Linux). When MS Word has finished writing
@@ -563,7 +562,7 @@
 	The solution is simple. Use UNIX file system permissions and controls to your advantage. Follow these
 	simple steps to create a share in which all files will consistently be owned by the same user and the
 	same group:
-	</p><div class="procedure"><a name="id2614351"></a><p class="title"><b>Procedure�11.2.�Using Directory Permissions to Force File User and Group Ownership</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2614475"></a><p class="title"><b>Procedure�11.2.�Using Directory Permissions to Force File User and Group Ownership</b></p><ol type="1"><li><p>
 		Change your share definition so that it matches this pattern:
 </p><pre class="screen">
 [finance]
@@ -571,18 +570,18 @@
         browseable = Yes
         read only = No
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2614377"></a><a class="indexterm" name="id2614388"></a>
+		</p></li><li><p><a class="indexterm" name="id2614501"></a><a class="indexterm" name="id2614513"></a>
 		Set consistent user and group permissions recursively down the directory tree as shown here:
 </p><pre class="screen">
 <code class="prompt">root# </code> chown -R janetp.users /usr/data/finance
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2614420"></a>
+		</p></li><li><p><a class="indexterm" name="id2614544"></a>
 		Set the files and directory permissions to be read/write for owner and group, and not accessible
 		to others (everyone), using the following command:
 </p><pre class="screen">
 <code class="prompt">root# </code> chmod ug+rwx,o-rwx /usr/data/finance
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2614449"></a>
+		</p></li><li><p><a class="indexterm" name="id2614574"></a>
 		Set the SGID (supergroup) bit on all directories from the top down. This means all files 
 		can be created with the permissions of the group set on the directory. It means all users 
 		who are members of the group <code class="constant">finance</code> can read and write all files in 
@@ -592,11 +591,11 @@
 <code class="prompt">root# </code> find /usr/data/finance -type d -exec chmod ug+s {}\;
 </pre><p>
 
-		</p></li><li><p><a class="indexterm" name="id2614489"></a><a class="indexterm" name="id2614497"></a><a class="indexterm" name="id2614505"></a>
+		</p></li><li><p><a class="indexterm" name="id2614614"></a><a class="indexterm" name="id2614622"></a><a class="indexterm" name="id2614630"></a>
 		Make sure all users that must have read/write access to the directory have 
 		<code class="constant">finance</code> group membership as their primary group, 
 		for example, the group they belong to in <code class="filename">/etc/passwd</code>.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614530"></a>Managing Windows 200x ACLs</h3></div></div></div><p><a class="indexterm" name="id2614537"></a><a class="indexterm" name="id2614545"></a><a class="indexterm" name="id2614553"></a><a class="indexterm" name="id2614561"></a>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614655"></a>Managing Windows 200x ACLs</h3></div></div></div><p><a class="indexterm" name="id2614662"></a><a class="indexterm" name="id2614670"></a><a class="indexterm" name="id2614678"></a><a class="indexterm" name="id2614686"></a>
 	Samba must translate Windows 2000 ACLs to UNIX POSIX ACLs. This has some interesting side effects because
 	there is not a one-to-one equivalence between them. The as-close-as-possible ACLs match means
 	that some transactions are not possible from MS Windows clients. One of these is to reset the ownership
@@ -604,7 +603,7 @@
 	</p><p>
 	There are two possible ways to set ACLs on UNIX/Linux file systems from a Windows network workstation,
 	either via File Manager or via the Microsoft Management Console (MMC) Computer Management interface.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614585"></a>Using the MMC Computer Management Interface</h4></div></div></div><div class="procedure"><ol type="1"><li><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614709"></a>Using the MMC Computer Management Interface</h4></div></div></div><div class="procedure"><ol type="1"><li><p>
 		From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator 
 		account (on Samba domains, this is usually the account called <code class="constant">root</code>).
 		</p></li><li><p>
@@ -619,14 +618,14 @@
 		the Computer Management entry should now say: <span class="guimenu">Computer Management (FRODO)</span>.
 		</p></li><li><p>
 		In the left panel, click <span class="guimenu">Computer Management (FRODO)</span> &#8594; <span class="guimenuitem">[+] Shared Folders</span> &#8594; <span class="guimenuitem">Shares</span>.
-		</p></li><li><p><a class="indexterm" name="id2614768"></a><a class="indexterm" name="id2614776"></a><a class="indexterm" name="id2614783"></a><a class="indexterm" name="id2614791"></a>
+		</p></li><li><p><a class="indexterm" name="id2614892"></a><a class="indexterm" name="id2614900"></a><a class="indexterm" name="id2614908"></a><a class="indexterm" name="id2614916"></a>
 		In the right panel, double-click on the share on which you wish to set/edit ACLs. This
 		brings up the Properties panel. Click the <span class="guimenu">Security</span> tab. It is best
 		to edit ACLs using the <code class="constant">Advanced</code> editing features. Click the 
 		<span class="guimenu">Advanced</span> button. This opens a panel that has four tabs. Only the 
 		functionality under the <code class="constant">Permissions</code> tab can be utilized with respect 
 		to a Samba domain server.
-		</p></li><li><p><a class="indexterm" name="id2614831"></a><a class="indexterm" name="id2614839"></a>
+		</p></li><li><p><a class="indexterm" name="id2614956"></a><a class="indexterm" name="id2614964"></a>
 		You may now edit/add/remove access control settings. Be very careful. Many problems have been
 		created by people who decided that everyone should be rejected but one particular group should
 		have full control. This is a catch-22 situation because members of that particular group also
@@ -635,7 +634,7 @@
 		</p></li><li><p>
 		When you are done with editing, close all panels by clicking through the <span class="guimenu">OK</span>
 		buttons until the last panel closes.
-		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614876"></a>Using MS Windows Explorer (File Manager)</h4></div></div></div><p>
+		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2615000"></a>Using MS Windows Explorer (File Manager)</h4></div></div></div><p>
 	The following alternative method may be used from a Windows workstation. In this example we work
 	with a domain called <code class="constant">MEGANET</code>, a server called <code class="constant">MASSIVE</code>, and a
 	share called <code class="constant">Apps</code>. The underlying UNIX/Linux share point for this share is
@@ -643,7 +642,7 @@
 	</p><div class="procedure"><ol type="1"><li><p>
 		Click <span class="guimenu">Start</span> &#8594; <span class="guimenuitem">[right-click] My Computer</span> &#8594; <span class="guimenuitem">Explore</span> &#8594; <span class="guimenuitem">[left panel] [+] My Network Places</span> &#8594; <span class="guimenuitem">[+] Entire Network</span> &#8594; <span class="guimenuitem">[+] Microsoft Windows Network</span> &#8594; <span class="guimenuitem">[+] Meganet</span> &#8594; <span class="guimenuitem">[+] Massive</span> &#8594; <span class="guimenuitem">[right-click] Apps</span> &#8594; <span class="guimenuitem">Properties</span> &#8594; <span class="guimenuitem">Security</span> &#8594; <span class="guimenuitem">Advanced</span>. This opens a panel that has four tabs. Only the functionality under the 
 		<code class="constant">Permissions</code> tab can be utilized for a Samba domain server.
-		</p></li><li><p><a class="indexterm" name="id2615000"></a><a class="indexterm" name="id2615008"></a>
+		</p></li><li><p><a class="indexterm" name="id2615125"></a><a class="indexterm" name="id2615133"></a>
                 You may now edit/add/remove access control settings. Be very careful. Many problems have been
                 created by people who decided that everyone should be rejected but one particular group should
                 have full control. This is a catch-22 situation because members of that particular group also
@@ -652,7 +651,7 @@
                 </p></li><li><p>
                 When you are done with editing, close all panels by clicking through the <span class="guimenu">OK</span>
                 buttons until the last panel closes.
-                </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2615047"></a>Setting Posix ACLs in UNIX/Linux</h4></div></div></div><p><a class="indexterm" name="id2615054"></a><a class="indexterm" name="id2615062"></a>
+                </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2615172"></a>Setting Posix ACLs in UNIX/Linux</h4></div></div></div><p><a class="indexterm" name="id2615179"></a><a class="indexterm" name="id2615187"></a>
 	Yet another alternative method for setting desired security settings on the shared resource files and
 	directories can be achieved by logging into UNIX/Linux and setting POSIX ACLs directly using command-line
 	tools. Here is an example session on the same resource as in the immediately preceding example on a SUSE 9
@@ -675,7 +674,7 @@ user::rwx
 group::rwx
 other::r-x
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2615136"></a>
+		</p></li><li><p><a class="indexterm" name="id2615261"></a>
 		You want to add permission for <code class="constant">AppsMgrs</code> to enable them to
 		manage the applications (apps) share. It is important to set the ACL recursively
 		so that the AppsMgrs have this capability throughout the directory tree that is 
@@ -698,26 +697,26 @@ mask::rwx
 other::r-x
 </pre><p>
 		This confirms that the change of POSIX ACL permissions has been effective.
-		</p></li><li><p><a class="indexterm" name="id2615192"></a><a class="indexterm" name="id2615199"></a><a class="indexterm" name="id2615207"></a><a class="indexterm" name="id2615215"></a><a class="indexterm" name="id2615223"></a>
+		</p></li><li><p><a class="indexterm" name="id2615316"></a><a class="indexterm" name="id2615324"></a><a class="indexterm" name="id2615332"></a><a class="indexterm" name="id2615340"></a><a class="indexterm" name="id2615348"></a>
 		It is highly recommended that you read the online manual page for the <code class="literal">setfacl</code>
 		and <code class="literal">getfacl</code> commands. This provides information regarding how to set/read the default
 		ACLs and how that may be propagated through the directory tree. In Windows ACLs terms, this is the equivalent
 		of setting <code class="constant">inheritance</code> properties.
-		</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615257"></a>Key Points Learned</h3></div></div></div><p>
+		</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615382"></a>Key Points Learned</h3></div></div></div><p>
 		The mish-mash of issues were thrown together into one chapter because it seemed like a good idea.
 		Looking back, this chapter could be broken into two, but it's too late now. It has been done.
 		The highlights covered are as follows:
-		</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2615274"></a><a class="indexterm" name="id2615282"></a><a class="indexterm" name="id2615290"></a><a class="indexterm" name="id2615298"></a>
+		</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2615399"></a><a class="indexterm" name="id2615407"></a><a class="indexterm" name="id2615415"></a><a class="indexterm" name="id2615423"></a>
 			Winbind honors and does not override account controls set in Active Directory.
 			This means that password change, logon hours, and so on, are (or soon will be) enforced
 			by Samba winbind. At this time, an out-of-hours login is denied and password
 			change is enforced. At this time, if logon hours expire, the user is not forcibly
 			logged off. That may be implemented at some later date.
-			</p></li><li><p><a class="indexterm" name="id2615317"></a><a class="indexterm" name="id2615325"></a>
+			</p></li><li><p><a class="indexterm" name="id2615442"></a><a class="indexterm" name="id2615450"></a>
 			Sign'n'seal (plus schannel support) has been implemented in Samba-3. Beware of potential
 			problems acknowledged by Microsoft as having been fixed but reported by some as still
 			possibly an open issue.
-			</p></li><li><p><a class="indexterm" name="id2615341"></a><a class="indexterm" name="id2615349"></a><a class="indexterm" name="id2615356"></a><a class="indexterm" name="id2615364"></a>
+			</p></li><li><p><a class="indexterm" name="id2615466"></a><a class="indexterm" name="id2615473"></a><a class="indexterm" name="id2615481"></a><a class="indexterm" name="id2615489"></a>
 			The combination of Kerberos 5, plus OpenLDAP, plus Samba, cannot replace Microsoft
 			Active Directory. The possibility to do this is not planned in the current Samba-3
 			roadmap. Samba-3 does aim to provide further improvements in interoperability so that
@@ -726,83 +725,83 @@ other::r-x
 			This chapter reviewed mechanisms by which Samba servers may be kept secure. Each of
 			the four key methodologies was reviewed with specific reference to example deployment
 			techniques.
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2615391"></a>Questions and Answers</h2></div></div></div><p>
-	</p><div class="qandaset"><dl><dt> <a href="kerberos.html#id2615407">
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2615516"></a>Questions and Answers</h2></div></div></div><p>
+	</p><div class="qandaset"><dl><dt> <a href="kerberos.html#id2615532">
 		Does Samba-3 require the Sign'n'seal registry hacks needed by Samba-2?
-		</a></dt><dt> <a href="kerberos.html#id2615477">
+		</a></dt><dt> <a href="kerberos.html#id2615602">
 		Does Samba-3 support Active Directory?
-		</a></dt><dt> <a href="kerberos.html#id2615508">
+		</a></dt><dt> <a href="kerberos.html#id2615633">
 		When Samba-3 is used with Active Directory, is it necessary to run mixed-mode operation, as was
 		necessary with Samba-2?
-		</a></dt><dt> <a href="kerberos.html#id2615547">
+		</a></dt><dt> <a href="kerberos.html#id2615672">
 		Is it safe to set share-level access controls in Samba?
-		</a></dt><dt> <a href="kerberos.html#id2615576">
+		</a></dt><dt> <a href="kerberos.html#id2615701">
 		Is it mandatory to set share ACLs to get a secure Samba-3 server?
-		</a></dt><dt> <a href="kerberos.html#id2615653">
+		</a></dt><dt> <a href="kerberos.html#id2615778">
 		The valid users did not work on the [homes].
 		Has this functionality been restored yet?
-		</a></dt><dt> <a href="kerberos.html#id2615719">
+		</a></dt><dt> <a href="kerberos.html#id2615844">
 		Is the bias against use of the force user and force group
 		really warranted?
-		</a></dt><dt> <a href="kerberos.html#id2615782">
+		</a></dt><dt> <a href="kerberos.html#id2615907">
 		The example given for file and directory access control forces all files to be owned by one
 		particular user. I do not like that. Is there any way I can see who created the file?
-		</a></dt><dt> <a href="kerberos.html#id2615830">
+		</a></dt><dt> <a href="kerberos.html#id2615955">
 		In the book, &#8220;The Official Samba-3 HOWTO and Reference Guide&#8221;, you recommended use
 		of the Windows NT4 Server Manager (part of the SRVTOOLS.EXE) utility. Why
 		have you mentioned only the use of the Windows 200x/XP MMC Computer Management utility?
-		</a></dt><dt> <a href="kerberos.html#id2615896">
+		</a></dt><dt> <a href="kerberos.html#id2616022">
 		I tried to set valid users = @Engineers, but it does not work. My Samba
 		server is an Active Directory domain member server. Has this been fixed now?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2615407"></a><a name="id2615409"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615412"></a><a class="indexterm" name="id2615420"></a>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2615532"></a><a name="id2615534"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615537"></a><a class="indexterm" name="id2615545"></a>
 		Does Samba-3 require the <code class="constant">Sign'n'seal</code> registry hacks needed by Samba-2?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615440"></a><a class="indexterm" name="id2615447"></a><a class="indexterm" name="id2615455"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615564"></a><a class="indexterm" name="id2615572"></a><a class="indexterm" name="id2615580"></a>
 		No. Samba-3 fully supports <code class="constant">Sign'n'seal</code> as well as <code class="constant">schannel</code>
 		operation. The registry change should not be applied when Samba-3 is used as a domain controller.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615477"></a><a name="id2615480"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615602"></a><a name="id2615604"></a></td><td align="left" valign="top"><p>
 		Does Samba-3 support Active Directory?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615490"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615615"></a>
 		Yes. Samba-3 can be a fully participating native mode Active Directory client. Samba-3 does not
 		provide Active Directory services. It cannot be used to replace a Microsoft Active Directory
 		server implementation. Samba-3 can function as an Active Directory client (workstation) toolkit,
 		and it can function as an Active Directory domain member server.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615508"></a><a name="id2615511"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615514"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615633"></a><a name="id2615635"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615639"></a>
 		When Samba-3 is used with Active Directory, is it necessary to run mixed-mode operation, as was
 		necessary with Samba-2?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615530"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615655"></a>
 		No. Samba-3 can be used with NetBIOS over TCP/IP disabled, just as can be done with Windows 200x
 		Server and 200x/XPPro client products. It is no longer necessary to run mixed-mode operation,
 		because Samba-3 can join a native Windows 2003 Server ADS domain.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615547"></a><a name="id2615549"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615552"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615672"></a><a name="id2615674"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615677"></a>
 		Is it safe to set share-level access controls in Samba?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Yes. Share-level access controls have been supported since early versions of Samba-2. This is
 		very mature technology. Not enough sites make use of this powerful capability, neither on
 		Windows server or with Samba servers.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615576"></a><a name="id2615578"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615582"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615701"></a><a name="id2615703"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615706"></a>
 		Is it mandatory to set share ACLs to get a secure Samba-3 server?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615597"></a><a class="indexterm" name="id2615605"></a><a class="indexterm" name="id2615613"></a><a class="indexterm" name="id2615622"></a><a class="indexterm" name="id2615630"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615722"></a><a class="indexterm" name="id2615730"></a><a class="indexterm" name="id2615738"></a><a class="indexterm" name="id2615746"></a><a class="indexterm" name="id2615754"></a>
 		No. Samba-3 honors UNIX/Linux file system security, supports Windows 200x ACLs, and provides 
 		means of securing shares through share definition controls in the <code class="filename">smb.conf</code> file. The additional
 		support for share-level ACLs is like frosting on the cake. It adds to security but is not essential
 		to it.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615653"></a><a name="id2615655"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615658"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615778"></a><a name="id2615780"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615783"></a>
 		The <em class="parameter"><code>valid users</code></em> did not work on the <em class="parameter"><code>[homes]</code></em>.
 		Has this functionality been restored yet?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615686"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615810"></a>
 		Yes. This was fixed in Samba-3.0.2. The use of this parameter is strongly recommended as a safeguard
 		on the <em class="parameter"><code>[homes]</code></em> meta-service. The correct way to specify this is:
 		<a class="link" href="smb.conf.5.html#VALIDUSERS" target="_top">valid users = %S</a>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615719"></a><a name="id2615721"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615724"></a><a class="indexterm" name="id2615732"></a><a class="indexterm" name="id2615740"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615844"></a><a name="id2615846"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615849"></a><a class="indexterm" name="id2615856"></a><a class="indexterm" name="id2615864"></a>
 		Is the bias against use of the <em class="parameter"><code>force user</code></em> and <em class="parameter"><code>force group</code></em>
 		really warranted?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615767"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615892"></a>
 		There is no bias. There is a determination to recommend the right tool for the task at hand.
 		After all, it is better than putting users through performance problems, isn't it?
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615782"></a><a name="id2615784"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615907"></a><a name="id2615909"></a></td><td align="left" valign="top"><p>
 		The example given for file and directory access control forces all files to be owned by one
 		particular user. I do not like that. Is there any way I can see who created the file?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615797"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615922"></a>
 		Sure. You do not have to set the SUID bit on the directory. Simply execute the following command
 		to permit file ownership to be retained by the user who created it:
 </p><pre class="screen">
@@ -810,22 +809,20 @@ other::r-x
 </pre><p>
 		Note that this required no more than removing the <code class="constant">u</code> argument so that the
 		SUID bit is not set for the owner.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615830"></a><a name="id2615832"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615835"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615955"></a><a name="id2615957"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615960"></a>
 		In the book, &#8220;<span class="quote">The Official Samba-3 HOWTO and Reference Guide</span>&#8221;, you recommended use
 		of the Windows NT4 Server Manager (part of the <code class="filename">SRVTOOLS.EXE</code>) utility. Why
 		have you mentioned only the use of the Windows 200x/XP MMC Computer Management utility?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615863"></a><a class="indexterm" name="id2615870"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2615988"></a><a class="indexterm" name="id2615996"></a>
 		Either tool can be used with equal effect. There is no benefit of one over the other, except that
 		the MMC utility is present on all Windows 200x/XP systems and does not require additional software
 		to be downloaded and installed. Note that if you want to manage user and group accounts in your
 		Samba-controlled domain, the only tool that permits that is the NT4 Domain User Manager, which
 		is provided as part of the <code class="filename">SRVTOOLS.EXE</code> utility.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2615896"></a><a name="id2615898"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2615902"></a><a class="indexterm" name="id2615909"></a><a class="indexterm" name="id2615917"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2616022"></a><a name="id2616024"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2616027"></a><a class="indexterm" name="id2616035"></a><a class="indexterm" name="id2616043"></a>
 		I tried to set <em class="parameter"><code>valid users = @Engineers</code></em>, but it does not work. My Samba
 		server is an Active Directory domain member server. Has this been fixed now?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The use of this parameter has always required the full specification of the domain account, for
 		example, <em class="parameter"><code>valid users = @"MEGANET2\Domain Admins"</code></em>.
-		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2610604" href="#id2610604" class="para">12</a>] </sup>This report is entirely fictitious. 
-			Any resemblance to a factual report is purely coincidental.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2613014" href="#id2613014" class="para">13</a>] </sup>Note: This link is no longer active. The same article is still
-			available from <a class="ulink" href="http://199.105.191.226/Man/2699/020430msdoj/" target="_top">ITWorld.com</a> (July 5, 2005)</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="RefSection.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="DomApps.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�III.�Reference Section�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�12.�Integrating Additional Services</td></tr></table></div></body></html>
+		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"></div><div class="footnote"><a class="ulink" href="http://199.105.191.226/Man/2699/020430msdoj/" target="_top"><sup>[<a name="ftn.id2613126" href="#id2613126" class="ulink">13</a>] </sup>ITWorld.com</a></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="RefSection.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="DomApps.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�III.�Reference Section�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�12.�Integrating Additional Services</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/ntmigration.html b/docs/htmldocs/Samba3-ByExample/ntmigration.html
index dbb565b5ff..8afb95420f 100644
--- a/docs/htmldocs/Samba3-ByExample/ntmigration.html
+++ b/docs/htmldocs/Samba3-ByExample/ntmigration.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�Migrating NT4 Domain to Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="upgrades.html" title="Chapter�8.�Updating Samba-3"><link rel="next" href="nw4migration.html" title="Chapter�10.�Migrating NetWare Server to Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�Migrating NT4 Domain to Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrades.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="nw4migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntmigration"></a>Chapter�9.�Migrating NT4 Domain to Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ntmigration.html#id2601332">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601417">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601472">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601658">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601981">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2602007">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602148">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604606">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2605013">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605051">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�Migrating NT4 Domain to Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="upgrades.html" title="Chapter�8.�Updating Samba-3"><link rel="next" href="nw4migration.html" title="Chapter�10.�Migrating NetWare Server to Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�Migrating NT4 Domain to Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrades.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="nw4migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntmigration"></a>Chapter�9.�Migrating NT4 Domain to Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ntmigration.html#id2601309">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601394">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601449">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2601635">Technical Issues</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2601958">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2601984">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntmigration.html#id2602125">NT4 Migration Using LDAP Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604584">NT4 Migration Using tdbsam Backend</a></span></dt><dt><span class="sect2"><a href="ntmigration.html#id2604990">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntmigration.html#id2605028">Questions and Answers</a></span></dt></dl></div><p>
 	Ever since Microsoft announced that it was discontinuing support for Windows
 	NT4, Samba users started to ask for detailed instructions on how to migrate
 	from NT4 to Samba-3. This chapter provides background information that should
@@ -6,23 +6,23 @@
 	</p><p>
 	One wonders how many NT4 systems will be left in service by the time you read this
 	book though.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601332"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2601338"></a>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601309"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2601316"></a>
 	Network administrators who want to migrate off a Windows NT4 environment know
 	one thing with certainty. They feel that NT4 has been abandoned, and they want
 	to update. The desire to get off NT4 and to not adopt Windows 200x and Active
 	Directory is driven by a mixture of concerns over complexity, cost, fear of
 	failure, and much more.
 	</p><p>
-	<a class="indexterm" name="id2601356"></a>
-	<a class="indexterm" name="id2601363"></a>
-	<a class="indexterm" name="id2601373"></a>
-	<a class="indexterm" name="id2601382"></a>
+	<a class="indexterm" name="id2601334"></a>
+	<a class="indexterm" name="id2601341"></a>
+	<a class="indexterm" name="id2601350"></a>
+	<a class="indexterm" name="id2601359"></a>
 	The migration from NT4 to Samba-3 can involve a number of factors, including
 	migration of data to another server, migration of network environment controls
 	such as group policies, and migration of the users, groups, and machine
 	accounts.
 	</p><p>
-	<a class="indexterm" name="id2601398"></a>
+	<a class="indexterm" name="id2601376"></a>
 	It should be pointed out now that it is possible to migrate some systems from
 	a Windows NT4 domain environment to a Samba-3 domain environment. This is certainly
 	not possible in every case. It is possible to just migrate the domain accounts
@@ -30,10 +30,10 @@
 	the exception than the rule. Most systems require some tweaking after
 	migration before an environment that is acceptable for immediate use
 	is obtained.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601417"></a>Assignment Tasks</h3></div></div></div><p>
-	<a class="indexterm" name="id2601425"></a>
-	<a class="indexterm" name="id2601432"></a>
-	<a class="indexterm" name="id2601438"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601394"></a>Assignment Tasks</h3></div></div></div><p>
+	<a class="indexterm" name="id2601402"></a>
+	<a class="indexterm" name="id2601409"></a>
+	<a class="indexterm" name="id2601416"></a>
 	You are about to migrate an MS Windows NT4 domain accounts database to
 	a Samba-3 server. The Samba-3 server is using a 
 	<em class="parameter"><code>passdb backend</code></em> based on LDAP. The 
@@ -42,27 +42,27 @@
 	</p><p>
 	Your objective is to document the process of migrating user and group accounts
 	from several NT4 domains into a single Samba-3 LDAP backend database.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601472"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2601479"></a>
-	<a class="indexterm" name="id2601486"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601449"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2601456"></a>
+	<a class="indexterm" name="id2601463"></a>
+	<a class="indexterm" name="id2601470"></a>
+	<a class="indexterm" name="id2601482"></a>
 	<a class="indexterm" name="id2601493"></a>
-	<a class="indexterm" name="id2601504"></a>
-	<a class="indexterm" name="id2601516"></a>
-	<a class="indexterm" name="id2601522"></a>
+	<a class="indexterm" name="id2601500"></a>
 	The migration process takes a snapshot of information that is stored in the
 	Windows NT4 registry-based accounts database. That information resides in
 	the Security Account Manager (SAM) portion of the NT4 registry under keys called
 	<code class="constant">SAM</code> and <code class="constant">SECURITY</code>.
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-	<a class="indexterm" name="id2601547"></a>
-	<a class="indexterm" name="id2601554"></a>
+	<a class="indexterm" name="id2601524"></a>
+	<a class="indexterm" name="id2601531"></a>
 	The Windows NT4 registry keys called <code class="constant">SAM</code> and <code class="constant">SECURITY</code>
 	are protected so that you cannot view the contents. If you change the security setting
 	to reveal the contents under these hive keys, your Windows NT4 domain is crippled. Do not
 	do this unless you are willing to render your domain controller inoperative.
 	</p></div><p>
-	<a class="indexterm" name="id2601576"></a>
-	<a class="indexterm" name="id2601585"></a>
+	<a class="indexterm" name="id2601553"></a>
+	<a class="indexterm" name="id2601562"></a>
 	Before commencing an NT4 to Samba-3 migration, you should consider what your objectives are.
 	While in some cases it is possible simply to migrate an NT4 domain to a single Samba-3 server,
 	that may not be a good idea from an administration perspective. Since the process involves going
@@ -70,9 +70,9 @@
 	review the structure of the network, how Windows clients are controlled and how they
 	interact with the network environment.
 	</p><p>
-	<a class="indexterm" name="id2601604"></a>
-	<a class="indexterm" name="id2601613"></a>
-	<a class="indexterm" name="id2601620"></a>
+	<a class="indexterm" name="id2601581"></a>
+	<a class="indexterm" name="id2601590"></a>
+	<a class="indexterm" name="id2601597"></a>
 	MS Windows NT4 was introduced some time around 1996. Many environments in which NT4 was deployed
 	have done little to keep the NT4 server environment up to date with more recent Windows releases, 
 	particularly Windows XP Professional. The migration provides opportunity to revise and update 
@@ -83,9 +83,9 @@
 	as a good time to update desktop systems also. In all, the extra effort should constitute no
 	real disruption to users, but rather, with due diligence and care, should make their network experience
 	a much happier one.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601658"></a>Technical Issues</h3></div></div></div><p>
-	<a class="indexterm" name="id2601666"></a>
-	<a class="indexterm" name="id2601672"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601635"></a>Technical Issues</h3></div></div></div><p>
+	<a class="indexterm" name="id2601643"></a>
+	<a class="indexterm" name="id2601650"></a>
 	Migration of an NT4 domain user and group database to Samba-3 involves a certain strategic
 	element. Many sites have asked for instructions regarding merging of multiple NT4
 	domains into one Samba-3 LDAP database. It seems that this is viewed as a significant
@@ -93,35 +93,35 @@
 	Directory. The diagram in <a class="link" href="ntmigration.html#ch8-migration" title="Figure�9.1.�Schematic Explaining the net rpc vampire Process">&#8220;Schematic Explaining the net rpc vampire Process&#8221;</a> illustrates the effect of migration
 	from a Windows NT4 domain to a Samba domain.
 	</p><div class="figure"><a name="ch8-migration"></a><p class="title"><b>Figure�9.1.�Schematic Explaining the <code class="literal">net rpc vampire</code> Process</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ch8-migration.png" width="297" alt="Schematic Explaining the net rpc vampire Process"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2601746"></a>
-	<a class="indexterm" name="id2601752"></a>
+	<a class="indexterm" name="id2601723"></a>
+	<a class="indexterm" name="id2601730"></a>
 	If you want to merge multiple NT4 domain account databases into one Samba domain,
 	you must now dump the contents of the first migration and edit it as appropriate. Now clean
 	out (remove) the tdbsam backend file (<code class="filename">passdb.tdb</code>) or the LDAP database
 	files. You must start each migration with a new database into which you merge your NT4 
 	domains.
-	</p><p><a class="indexterm" name="id2601773"></a>
+	</p><p><a class="indexterm" name="id2601750"></a>
 	At this point, you are ready to perform the second migration, following the same steps as
 	for the first. In other words, dump the database, edit it, and then you may merge the
 	dump for the first and second migrations.
-	</p><p><a class="indexterm" name="id2601788"></a><a class="indexterm" name="id2601796"></a><a class="indexterm" name="id2601804"></a>
+	</p><p><a class="indexterm" name="id2601765"></a><a class="indexterm" name="id2601773"></a><a class="indexterm" name="id2601781"></a>
 	You must be careful. If you choose to migrate to an LDAP backend, your dump file
 	now contains the full account information, including the domain SID. The domain SID for each 
 	of the two NT4 domains will be different. You must choose one and change the domain 
 	portion of the account SIDs so that all are the same.
 	</p><p>
-	<a class="indexterm" name="id2601821"></a>
-	<a class="indexterm" name="id2601828"></a>
-	<a class="indexterm" name="id2601835"></a>
-	<a class="indexterm" name="id2601842"></a>
-	<a class="indexterm" name="id2601849"></a>
-	<a class="indexterm" name="id2601855"></a>
-	<a class="indexterm" name="id2601862"></a>
-	<a class="indexterm" name="id2601869"></a>
-	<a class="indexterm" name="id2601876"></a>
-	<a class="indexterm" name="id2601883"></a>
-	<a class="indexterm" name="id2601890"></a>
-	<a class="indexterm" name="id2601897"></a>
+	<a class="indexterm" name="id2601798"></a>
+	<a class="indexterm" name="id2601805"></a>
+	<a class="indexterm" name="id2601812"></a>
+	<a class="indexterm" name="id2601819"></a>
+	<a class="indexterm" name="id2601826"></a>
+	<a class="indexterm" name="id2601833"></a>
+	<a class="indexterm" name="id2601840"></a>
+	<a class="indexterm" name="id2601846"></a>
+	<a class="indexterm" name="id2601853"></a>
+	<a class="indexterm" name="id2601860"></a>
+	<a class="indexterm" name="id2601867"></a>
+	<a class="indexterm" name="id2601874"></a>
 	If you choose to use a tdbsam (<code class="filename">passdb.tdb</code>) backend file, your best choice
 	is to use <code class="literal">pdbedit</code> to export the contents of the tdbsam file into an
 	smbpasswd data file. This automatically strips out all domain-specific information,
@@ -131,7 +131,7 @@
 	file must have an account in <code class="filename">/etc/passwd</code>. The resulting smbpasswd file
 	may be exported or imported into either a tdbsam (<code class="filename">passdb.tdb</code>) or
 	an LDAP backend.
-	</p><div class="figure"><a name="NT4DUM"></a><p class="title"><b>Figure�9.2.�View of Accounts in NT4 Domain User Manager</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/UserMgrNT4.png" width="270" alt="View of Accounts in NT4 Domain User Manager"></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601981"></a>Political Issues</h3></div></div></div><p>
+	</p><div class="figure"><a name="NT4DUM"></a><p class="title"><b>Figure�9.2.�View of Accounts in NT4 Domain User Manager</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/UserMgrNT4.png" width="270" alt="View of Accounts in NT4 Domain User Manager"></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601958"></a>Political Issues</h3></div></div></div><p>
 	The merging of multiple Windows NT4-style domains into a single LDAP-backend-based Samba-3
 	domain may be seen by those who had power over them as a loss of prestige or a loss of
 	power. The imposition of a single domain may even be seen as a threat. So in migrating and
@@ -141,7 +141,7 @@
 	The best advice that can be given to those who set out to merge NT4 domains into a single
 	Samba-3 domain is to promote (sell) the action as one that reduces costs and delivers
 	greater network interoperability and manageability.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2602007"></a>Implementation</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601984"></a>Implementation</h2></div></div></div><p>
 	From feedback on the Samba mailing lists, it seems that most Windows NT4 migrations
 	to Samba-3 are being performed using a new server or a new installation of a Linux or UNIX
 	server. If you contemplate doing this, please note that the steps that follow in this
@@ -164,9 +164,9 @@
 		Prepare the target Samba-3 server. This involves configuring Samba-3 for
 		migration to either a tdbsam or an ldapsam backend.
 		</p></li><li><p>
-		<a class="indexterm" name="id2602094"></a>
-		<a class="indexterm" name="id2602100"></a>
-		<a class="indexterm" name="id2602107"></a>
+		<a class="indexterm" name="id2602071"></a>
+		<a class="indexterm" name="id2602078"></a>
+		<a class="indexterm" name="id2602084"></a>
 		Clean up the source NT4 PDC. Delete all accounts that need not be migrated.
 		Delete all files that should not be migrated. Where possible, change NT group
 		names so there are no spaces or uppercase characters. This is important if
@@ -174,14 +174,14 @@
 		names.
 		</p></li><li><p>
 		Step through the migration process.
-		</p></li><li><p><a class="indexterm" name="id2602128"></a>
+		</p></li><li><p><a class="indexterm" name="id2602105"></a>
 		Remove the NT4 PDC from the network.
 		</p></li><li><p>
 		Upgrade the Samba-3 server from a BDC to a PDC, and validate all account
 		information.
 		</p></li></ul></div><p>
 	It may help to use the above outline as a pre-migration checklist.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602148"></a>NT4 Migration Using LDAP Backend</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602125"></a>NT4 Migration Using LDAP Backend</h3></div></div></div><p>
 	In this example, the migration is of an NT4 PDC to a Samba-3 PDC with an LDAP backend. The accounts about
 	to be migrated are shown in <a class="link" href="ntmigration.html#NT4DUM" title="Figure�9.2.�View of Accounts in NT4 Domain User Manager">&#8220;View of Accounts in NT4 Domain User Manager&#8221;</a>. In this example use is made of the
 	smbldap-tools scripts to add the accounts that are migrated into the ldapsam passdb backend.
@@ -199,9 +199,9 @@
 	Delete the <code class="filename">/etc/samba/secrets.tdb</code> file and all Samba control tdb files
 	before commencing the following configuration steps.
 	</p></div><div class="table"><a name="ch8-vampire"></a><p class="title"><b>Table�9.1.�Samba <code class="filename">smb.conf</code> Scripts Essential to Samba Operation</b></p><div class="table-contents"><table summary="Samba smb.conf Scripts Essential to Samba Operation" border="1"><colgroup><col align="left"><col align="center"><col align="center"></colgroup><thead><tr><th align="left">Entity</th><th align="center">ldapsam Script</th><th align="center">tdbsam Script</th></tr></thead><tbody><tr><td align="left">Add User Accounts</td><td align="center">smbldap-useradd</td><td align="center">useradd</td></tr><tr><td align="left">Delete User Accounts</td><td align="center">smbldap-userdel</td><td align="center">userdel</td></tr><tr><td align="left">Add Group Accounts</td><td align="center">smbldap-groupadd</td><td align="center">groupadd</td></tr><tr><td align="left">Delete Group Accounts</td><td align="center">smbldap-groupdel</td><td align="center">groupdel</td></tr><tr><td align="left">Add User to Group</td><td align="center">smbldap-groupmod</td><td align="center">usermod (See Note)</td></tr><tr><td align="left">Add Machine Accounts</td><td align="center">smbldap-useradd</td><td align="center">useradd</td></tr></tbody></table></div></div><br class="table-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2602350"></a>
-	<a class="indexterm" name="id2602357"></a>
-	<a class="indexterm" name="id2602364"></a>
+	<a class="indexterm" name="id2602328"></a>
+	<a class="indexterm" name="id2602334"></a>
+	<a class="indexterm" name="id2602341"></a>
 	The UNIX/Linux <code class="literal">usermod</code> utility does not permit simple user addition to (or deletion
 	of users from) groups. This is a feature provided by the smbldap-tools scripts. If you want this
 	capability, you must create your own tool to do this. Alternately, you can search the Web
@@ -209,13 +209,13 @@
 	The <code class="literal">groupmem</code> utility was contributed to the shadow package but has not surfaced
 	in the formal commands provided by Linux distributions (March 2004).
 	</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2602401"></a>
+	<a class="indexterm" name="id2602378"></a>
 	The <code class="literal">tdbdump</code> utility is a utility that you can build from the Samba source-code tree. Not all Linux binary distributions include this tool. If it is missing from your
 	Linux distribution, you will need to build this yourself or else forgo its use.
 	</p></div><p>
-	<a class="indexterm" name="id2602421"></a>
+	<a class="indexterm" name="id2602398"></a>
 	Before starting the migration, all dead accounts were removed from the NT4 domain using the User Manager for Domains.
-	</p><div class="procedure"><a name="id2602431"></a><p class="title"><b>Procedure�9.1.�User Migration Steps</b></p><div class="example"><a name="sbent4smb"></a><p class="title"><b>Example�9.1.�NT4 Migration Samba-3 Server <code class="filename">smb.conf</code>  Part: A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2602491"></a><em class="parameter"><code>workgroup = DAMNATION</code></em></td></tr><tr><td><a class="indexterm" name="id2602503"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2602515"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2602527"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2602539"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2602550"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2602562"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2602574"></a><em class="parameter"><code>smb ports = 139 445</code></em></td></tr><tr><td><a class="indexterm" name="id2602585"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2602598"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602610"></a><em class="parameter"><code>#delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602622"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602635"></a><em class="parameter"><code>#delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602647"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602660"></a><em class="parameter"><code>#delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602673"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602686"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602699"></a><em class="parameter"><code>logon script = scripts\logon.cmd</code></em></td></tr><tr><td><a class="indexterm" name="id2602711"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2602722"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2602734"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2602746"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602758"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2602769"></a><em class="parameter"><code>#wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602781"></a><em class="parameter"><code>wins server = 192.168.123.124</code></em></td></tr><tr><td><a class="indexterm" name="id2602793"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=terpstra-world,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2602805"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2602817"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2602829"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2602841"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602853"></a><em class="parameter"><code>ldap suffix = dc=terpstra-world,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2602865"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2602877"></a><em class="parameter"><code>ldap timeout = 20</code></em></td></tr><tr><td><a class="indexterm" name="id2602888"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2602900"></a><em class="parameter"><code>idmap backend = ldap:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2602912"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2602924"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2602936"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602948"></a><em class="parameter"><code>ea support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602960"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbent4smb2"></a><p class="title"><b>Example�9.2.�NT4 Migration Samba-3 Server <code class="filename">smb.conf</code>  Part: B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2603005"></a><em class="parameter"><code>comment = Application Data</code></em></td></tr><tr><td><a class="indexterm" name="id2603017"></a><em class="parameter"><code>path = /data/home/apps</code></em></td></tr><tr><td><a class="indexterm" name="id2603028"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2603049"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2603061"></a><em class="parameter"><code>path = /home/users/%U/Documents</code></em></td></tr><tr><td><a class="indexterm" name="id2603072"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2603084"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603096"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2603116"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2603128"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2603140"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603151"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603163"></a><em class="parameter"><code>use client driver = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603175"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2603195"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2603207"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2603219"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603231"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2603251"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2603263"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2603275"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603286"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2603307"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2603319"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2603331"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603342"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2603363"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2603375"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbentslapd"></a><p class="title"><b>Example�9.3.�NT4 Migration LDAP Server Configuration File: <code class="filename">/etc/openldap/slapd.conf</code>  Part A</b></p><div class="example-contents"><pre class="screen">
+	</p><div class="procedure"><a name="id2602409"></a><p class="title"><b>Procedure�9.1.�User Migration Steps</b></p><div class="example"><a name="sbent4smb"></a><p class="title"><b>Example�9.1.�NT4 Migration Samba-3 Server <code class="filename">smb.conf</code>  Part: A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2602469"></a><em class="parameter"><code>workgroup = DAMNATION</code></em></td></tr><tr><td><a class="indexterm" name="id2602480"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2602492"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2602504"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2602516"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2602527"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2602539"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2602551"></a><em class="parameter"><code>smb ports = 139 445</code></em></td></tr><tr><td><a class="indexterm" name="id2602563"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2602575"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602587"></a><em class="parameter"><code>#delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602600"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602612"></a><em class="parameter"><code>#delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602625"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602637"></a><em class="parameter"><code>#delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2602650"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602663"></a><em class="parameter"><code>add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2602676"></a><em class="parameter"><code>logon script = scripts\logon.cmd</code></em></td></tr><tr><td><a class="indexterm" name="id2602688"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2602700"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2602711"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2602723"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602735"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2602746"></a><em class="parameter"><code>#wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602758"></a><em class="parameter"><code>wins server = 192.168.123.124</code></em></td></tr><tr><td><a class="indexterm" name="id2602770"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=terpstra-world,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2602782"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2602794"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2602806"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2602818"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602830"></a><em class="parameter"><code>ldap suffix = dc=terpstra-world,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2602842"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2602854"></a><em class="parameter"><code>ldap timeout = 20</code></em></td></tr><tr><td><a class="indexterm" name="id2602866"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2602878"></a><em class="parameter"><code>idmap backend = ldap:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2602890"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2602901"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2602913"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602925"></a><em class="parameter"><code>ea support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2602937"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbent4smb2"></a><p class="title"><b>Example�9.2.�NT4 Migration Samba-3 Server <code class="filename">smb.conf</code>  Part: B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2602982"></a><em class="parameter"><code>comment = Application Data</code></em></td></tr><tr><td><a class="indexterm" name="id2602994"></a><em class="parameter"><code>path = /data/home/apps</code></em></td></tr><tr><td><a class="indexterm" name="id2603006"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2603026"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2603038"></a><em class="parameter"><code>path = /home/users/%U/Documents</code></em></td></tr><tr><td><a class="indexterm" name="id2603050"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2603061"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603073"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2603093"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2603105"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2603117"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603128"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603140"></a><em class="parameter"><code>use client driver = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603152"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2603172"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2603184"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2603196"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2603208"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2603228"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2603240"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2603252"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603264"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2603284"></a><em class="parameter"><code>comment = Profile Data Share</code></em></td></tr><tr><td><a class="indexterm" name="id2603296"></a><em class="parameter"><code>path = /var/lib/samba/profdata</code></em></td></tr><tr><td><a class="indexterm" name="id2603308"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2603320"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2603340"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2603352"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sbentslapd"></a><p class="title"><b>Example�9.3.�NT4 Migration LDAP Server Configuration File: <code class="filename">/etc/openldap/slapd.conf</code>  Part A</b></p><div class="example-contents"><pre class="screen">
 include         /etc/openldap/schema/core.schema
 include         /etc/openldap/schema/cosine.schema
 include         /etc/openldap/schema/inetorgperson.schema
@@ -336,18 +336,18 @@ aliases:        files
 		The delete scripts are commented out so that during the process of migration
 		no account information can be deleted.
 		</p></li><li><p>
-		<a class="indexterm" name="id2603393"></a>
+		<a class="indexterm" name="id2603370"></a>
 		Configure OpenLDAP in preparation for the migration. An example
 		<code class="filename">sladp.conf</code> file is shown in <a class="link" href="ntmigration.html#sbentslapd" title="Example�9.3.�NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A">&#8220;NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf  Part A&#8221;</a>.
 		The <code class="constant">rootpw</code> value is an encrypted password string that can
 		be obtained by executing the <code class="literal">slappasswd</code> command.
 		</p></li><li><p>
-		<a class="indexterm" name="id2603507"></a>
-		<a class="indexterm" name="id2603514"></a>
+		<a class="indexterm" name="id2603484"></a>
+		<a class="indexterm" name="id2603491"></a>
 		Install the PADL <code class="literal">nss_ldap</code> tool set, then configure the <code class="filename">/etc/ldap.conf</code>
 		as shown in <a class="link" href="ntmigration.html#sbrntldapconf" title="Example�9.5.�NT4 Migration NSS LDAP File: /etc/ldap.conf">&#8220;NT4 Migration NSS LDAP File: /etc/ldap.conf&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2603574"></a>
+		<a class="indexterm" name="id2603552"></a>
 		Edit the <code class="filename">/etc/nsswitch.conf</code> file so it has the entries shown
 		in <a class="link" href="ntmigration.html#sbentnss" title="Example�9.6.�NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)">&#8220;NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)&#8221;</a>. Note that the LDAP entries have been commented out.
 		This is deliberate. If these entries are active (not commented out), and the
@@ -392,10 +392,10 @@ Storing SID S-1-5-21-1385457007-882775198-1210191635 \
 <code class="prompt">root# </code> net setlocalsid S-1-5-21-1385457007-882775198-1210191635
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2603744"></a>
-		<a class="indexterm" name="id2603750"></a>
-		<a class="indexterm" name="id2603757"></a>
-		<a class="indexterm" name="id2603764"></a>
+		<a class="indexterm" name="id2603721"></a>
+		<a class="indexterm" name="id2603728"></a>
+		<a class="indexterm" name="id2603735"></a>
+		<a class="indexterm" name="id2603742"></a>
 		Install the Idealx <code class="literal">smbldap-tools</code> software package, following
 		the instructions given in <a class="link" href="happy.html#sbeidealx" title="Install and Configure Idealx smbldap-tools Scripts">&#8220;Install and Configure Idealx smbldap-tools Scripts&#8221;</a>. The resulting perl scripts
 		should be located in the <code class="filename">/opt/IDEALX/sbin</code> directory.
@@ -489,10 +489,10 @@ writing new configuration file:
   /etc/smbldap-tools/smbldap.conf done.
   /etc/smbldap-tools/smbldap_bind.conf done.
 </pre><p>
-		<a class="indexterm" name="id2603914"></a>
-		<a class="indexterm" name="id2603921"></a>
-		<a class="indexterm" name="id2603928"></a>
-		<a class="indexterm" name="id2603935"></a>
+		<a class="indexterm" name="id2603891"></a>
+		<a class="indexterm" name="id2603898"></a>
+		<a class="indexterm" name="id2603905"></a>
+		<a class="indexterm" name="id2603912"></a>
 		Note that the NT4 domain SID that was previously obtained was entered above. Also,
 		the sambaUnixIdPooldn object was specified as sambaDomainName=DAMNATION. This is
 		the location into which the Idealx smbldap-tools store the next available UID/GID
@@ -545,7 +545,7 @@ adding new entry: cn=Replicators,ou=Groups,dc=terpstra-world,dc=org
 		The script tries to add the ou=People container twice, hence the error message.
 		This is expected behavior.
 		</p></li><li><p>
-		<a class="indexterm" name="id2604099"></a>
+		<a class="indexterm" name="id2604077"></a>
 		Restart the LDAP server following initialization of the LDAP directory. Execute the
 		system control script provided on your system. The following steps can be used on
 		Novell SUSE SLES 9:
@@ -712,8 +712,8 @@ Users (S-1-5-32-545) -&gt; Users
 		shares and printing resources on the new Samba-3 server, copy all data
 		across, set up privileges, and set share and file/directory access controls.
 		</p></li><li><p>
-		<a class="indexterm" name="id2604414"></a>
-		<a class="indexterm" name="id2604420"></a>
+		<a class="indexterm" name="id2604391"></a>
+		<a class="indexterm" name="id2604398"></a>
 		Edit the <code class="filename">smb.conf</code> file to  reset the parameter 
 		<a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = Yes</a> so that
 		the Samba server functions as a PDC for the purpose of migration.
@@ -841,7 +841,7 @@ Creating unix group: 'Guests'
 Creating unix group: 'Server Operators'
 Creating unix group: 'Users'
 </pre><p>
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604606"></a>NT4 Migration Using tdbsam Backend</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604584"></a>NT4 Migration Using tdbsam Backend</h3></div></div></div><p>
 	In this example, we change the domain name of the NT4 server from
 	<code class="constant">DRUGPREP</code> to <code class="constant">MEGANET</code> prior to the use
 	of the vampire (migration) tool. This migration process makes use of Linux system tools
@@ -849,22 +849,22 @@ Creating unix group: 'Users'
 	UNIX/Linux <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code>
 	databases. These entries must therefore be present, and correct options specified,
 	in your <code class="filename">smb.conf</code> file, or else the migration does not work as it should.
-	</p><div class="procedure"><a name="id2604653"></a><p class="title"><b>Procedure�9.2.�Migration Steps Using tdbsam</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2604630"></a><p class="title"><b>Procedure�9.2.�Migration Steps Using tdbsam</b></p><ol type="1"><li><p>
 		Prepare a Samba-3 server precisely per the instructions shown in <a class="link" href="Big500users.html" title="Chapter�4.�The 500-User Office">&#8220;The 500-User Office&#8221;</a>.
 		Set the workgroup name to <code class="constant">MEGANET</code>.
-		</p></li><li><p><a class="indexterm" name="id2604681"></a><a class="indexterm" name="id2604689"></a>
+		</p></li><li><p><a class="indexterm" name="id2604658"></a><a class="indexterm" name="id2604666"></a>
 		Edit the <code class="filename">smb.conf</code> file to temporarily change the parameter 
 		<a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = No</a> so
 		the Samba server functions as a BDC for the purpose of migration.
                 </p></li><li><p>
 		Start Samba as you have done previously.
-		</p></li><li><p><a class="indexterm" name="id2604732"></a>
+		</p></li><li><p><a class="indexterm" name="id2604709"></a>
 		Join the NT4 Domain as a BDC, as shown here:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join -S oldnt4pdc -W MEGANET -UAdministrator%not24get
 Joined domain MEGANET.
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2604766"></a>
+		</p></li><li><p><a class="indexterm" name="id2604743"></a>
 		You may vampire the accounts from the NT4 PDC by executing the command, as shown here:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc vampire -S oldnt4pdc -U Administrator%not24get
@@ -904,7 +904,7 @@ Creating unix group: 'Gnomes'
 Fetching BUILTIN database
 SAM_DELTA_DOMAIN_INFO not handled
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2604820"></a>
+		</p></li><li><p><a class="indexterm" name="id2604798"></a>
 		At this point, we can validate our migration. Let's look at the accounts
 		in the form in which they are seen in a smbpasswd file. This achieves that:
 </p><pre class="screen">
@@ -936,7 +936,7 @@ jacko:508:BC472F3BF9A0A5F63832C92FC614B7D1:
 maryk:509:3636AB7E12EBE79AB79AE2610DD89D4C:
      CF271B744F7A55AFDA277FF88D80C527:[UX         ]:LCT-3E8B4270:
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2604897"></a>
+		</p></li><li><p><a class="indexterm" name="id2604874"></a>
 		An expanded view of a user account entry shows more of what was
 		obtained from the NT4 PDC:
 </p><pre class="screen">
@@ -962,7 +962,7 @@ Password last set:    Wed, 02 Apr 2003 13:05:04 GMT
 Password can change:  0
 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2604932"></a>
+		</p></li><li><p><a class="indexterm" name="id2604910"></a>
 		The following command lists the long names of the groups that have been
 		imported (vampired) from the NT4 PDC:
 </p><pre class="screen">
@@ -979,11 +979,11 @@ Administrators        Members can fully administer the computer/domain
 Users                 Ordinary users
 </pre><p>
 		Everything looks well and in order.
-		</p></li><li><p><a class="indexterm" name="id2604972"></a><a class="indexterm" name="id2604980"></a>
+		</p></li><li><p><a class="indexterm" name="id2604949"></a><a class="indexterm" name="id2604957"></a>
 		Edit the <code class="filename">smb.conf</code> file to  reset the parameter 
 		<a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = Yes</a> so
 		the Samba server functions as a PDC for the purpose of migration.
-                </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605013"></a>Key Points Learned</h3></div></div></div><p>
+                </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604990"></a>Key Points Learned</h3></div></div></div><p>
 		Migration of an NT4 PDC database to a Samba-3 PDC is possible.
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
 			An LDAP backend is a suitable vehicle for NT4 migrations.
@@ -995,52 +995,52 @@ Users                 Ordinary users
 			</p></li><li><p>
 			The net Samba-3 domain most likely requires some
 			administration and updating before going live.
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605051"></a>Questions and Answers</h2></div></div></div><p>
-	</p><div class="qandaset"><dl><dt> <a href="ntmigration.html#id2605066">
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605028"></a>Questions and Answers</h2></div></div></div><p>
+	</p><div class="qandaset"><dl><dt> <a href="ntmigration.html#id2605044">
 		Why must I start each migration with a clean database?
-		</a></dt><dt> <a href="ntmigration.html#id2605107">
+		</a></dt><dt> <a href="ntmigration.html#id2605084">
 		Is it possible to set my domain SID to anything I like?
-		</a></dt><dt> <a href="ntmigration.html#id2605164">
+		</a></dt><dt> <a href="ntmigration.html#id2605141">
 		When using a tdbsam passdb backend, why must I have all domain user and group accounts
 		in /etc/passwd and /etc/group?
-		</a></dt><dt> <a href="ntmigration.html#id2605344">
+		</a></dt><dt> <a href="ntmigration.html#id2605321">
 		Why did you validate connectivity before attempting migration?
-		</a></dt><dt> <a href="ntmigration.html#id2605389">
+		</a></dt><dt> <a href="ntmigration.html#id2605367">
 		How would you merge 10 tdbsam-based domains into an LDAP database?
-		</a></dt><dt> <a href="ntmigration.html#id2605512">
+		</a></dt><dt> <a href="ntmigration.html#id2605489">
 		I want to change my domain name after I migrate all accounts from an NT4 domain to a 
 		Samba-3 domain. Does it make any sense to migrate the machine accounts in that case?
-		</a></dt><dt> <a href="ntmigration.html#id2605588">
+		</a></dt><dt> <a href="ntmigration.html#id2605565">
 		After merging multiple NT4 domains into a Samba-3 domain, I lost all multiple group mappings. Why?
-		</a></dt><dt> <a href="ntmigration.html#id2605652">
+		</a></dt><dt> <a href="ntmigration.html#id2605630">
 		How can I reset group membership after loading the account information into the LDAP database?
-		</a></dt><dt> <a href="ntmigration.html#id2605687">
+		</a></dt><dt> <a href="ntmigration.html#id2605664">
 		What are the limits or constraints that apply to group names?
-		</a></dt><dt> <a href="ntmigration.html#id2605791">
+		</a></dt><dt> <a href="ntmigration.html#id2605769">
 		My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba-3
 		LDAP backend system using the vampire process?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2605066"></a><a name="id2605069"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605072"></a>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2605044"></a><a name="id2605046"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605049"></a>
 		Why must I start each migration with a clean database?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605087"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605065"></a>
 		This is a recommendation that permits the data from each NT4 domain to
 		be kept separate until you are ready to merge them. Also, if you do not start with a clean database,
 		you may find errors due to users or groups from multiple domains having the
 		same name but different SIDs. It is better to permit each migration to complete
 		without undue errors and then to handle the merging of vampired data under
 		proper supervision.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605107"></a><a name="id2605109"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605112"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605084"></a><a name="id2605086"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605090"></a>
 		Is it possible to set my domain SID to anything I like?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605128"></a><a class="indexterm" name="id2605136"></a><a class="indexterm" name="id2605143"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605105"></a><a class="indexterm" name="id2605113"></a><a class="indexterm" name="id2605121"></a>
 		Yes, so long as the SID you create has the same structure as an autogenerated SID.
 		The typical SID looks like this: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX, where
 		the XXXXXXXXXX can be any number with from 6 to 10 digits. On the other hand, why
 		would you really want to create your own SID? I cannot think of a good reason.
 		You may want to set the SID to one that is already in use somewhere on your network,
 		but that is a little different from straight out creating your own domain SID.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605164"></a><a name="id2605166"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605169"></a><a class="indexterm" name="id2605177"></a><a class="indexterm" name="id2605184"></a><a class="indexterm" name="id2605192"></a><a class="indexterm" name="id2605200"></a><a class="indexterm" name="id2605212"></a><a class="indexterm" name="id2605223"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605141"></a><a name="id2605143"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605147"></a><a class="indexterm" name="id2605154"></a><a class="indexterm" name="id2605162"></a><a class="indexterm" name="id2605169"></a><a class="indexterm" name="id2605177"></a><a class="indexterm" name="id2605189"></a><a class="indexterm" name="id2605200"></a>
 		When using a tdbsam passdb backend, why must I have all domain user and group accounts
 		in <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code>?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605254"></a><a class="indexterm" name="id2605262"></a><a class="indexterm" name="id2605270"></a><a class="indexterm" name="id2605277"></a><a class="indexterm" name="id2605285"></a><a class="indexterm" name="id2605293"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605232"></a><a class="indexterm" name="id2605239"></a><a class="indexterm" name="id2605247"></a><a class="indexterm" name="id2605255"></a><a class="indexterm" name="id2605262"></a><a class="indexterm" name="id2605270"></a>
 		Samba-3 must be able to tie all user and group account SIDs to a UNIX UID or GID. Samba
 		does not fabricate the UNIX IDs from thin air, but rather requires them to be located
 		in a suitable place. 
@@ -1055,15 +1055,15 @@ Users                 Ordinary users
 		migration to the LDAP database, the accounts may be removed from the UNIX database files. 
 		In short then, all UNIX and Windows networking accounts, both in tdbsam as well as in 
 		LDAP, require UIDs/GIDs.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605344"></a><a name="id2605346"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605349"></a><a class="indexterm" name="id2605357"></a><a class="indexterm" name="id2605365"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605321"></a><a name="id2605323"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605327"></a><a class="indexterm" name="id2605334"></a><a class="indexterm" name="id2605342"></a>
 		Why did you validate connectivity before attempting migration?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Access validation before attempting to migrate NT4 domain accounts helps to pinpoint
 		potential problems that may otherwise affect or impede account migration. I am always
 		mindful of the 4 P's of migration: Planning Prevents Poor Performance.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605389"></a><a name="id2605392"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605367"></a><a name="id2605369"></a></td><td align="left" valign="top"><p>
 		How would you merge 10 tdbsam-based domains into an LDAP database?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605402"></a><a class="indexterm" name="id2605410"></a><a class="indexterm" name="id2605418"></a><a class="indexterm" name="id2605426"></a><a class="indexterm" name="id2605434"></a><a class="indexterm" name="id2605442"></a><a class="indexterm" name="id2605449"></a><a class="indexterm" name="id2605457"></a><a class="indexterm" name="id2605465"></a><a class="indexterm" name="id2605473"></a><a class="indexterm" name="id2605481"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605380"></a><a class="indexterm" name="id2605388"></a><a class="indexterm" name="id2605395"></a><a class="indexterm" name="id2605403"></a><a class="indexterm" name="id2605411"></a><a class="indexterm" name="id2605419"></a><a class="indexterm" name="id2605426"></a><a class="indexterm" name="id2605434"></a><a class="indexterm" name="id2605442"></a><a class="indexterm" name="id2605450"></a><a class="indexterm" name="id2605458"></a>
 		If you have 10 tdbsam Samba domains, there is considerable risk that there are a number of
 		accounts that have the same UNIX identifier (UID/GID). This means that you almost 
 		certainly have to edit a lot of data. It would be easiest to dump each database in smbpasswd
@@ -1073,17 +1073,17 @@ Users                 Ordinary users
 		tdbsam and then to LDAP. The final choice is yours. Just remember to verify all accounts that
 		you have migrated before handing over access to a user. After all, too many users with a bad
 		migration experience may threaten your career.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605512"></a><a name="id2605514"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605517"></a><a class="indexterm" name="id2605525"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605489"></a><a name="id2605491"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605494"></a><a class="indexterm" name="id2605502"></a>
 		I want to change my domain name after I migrate all accounts from an NT4 domain to a 
 		Samba-3 domain. Does it make any sense to migrate the machine accounts in that case?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605546"></a><a class="indexterm" name="id2605554"></a><a class="indexterm" name="id2605562"></a><a class="indexterm" name="id2605570"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605523"></a><a class="indexterm" name="id2605531"></a><a class="indexterm" name="id2605539"></a><a class="indexterm" name="id2605547"></a>
 		I would recommend not to migrate the machine account. The machine accounts should still work, but there are registry entries
 		on each Windows NT4 and upward client that have a tattoo of the old domain name. If you
 		unjoin the domain and then rejoin the newly renamed Samba-3 domain, you can be certain to avoid
 		this tattooing effect.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605588"></a><a name="id2605590"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605593"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605565"></a><a name="id2605567"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605570"></a>
 		After merging multiple NT4 domains into a Samba-3 domain, I lost all multiple group mappings. Why?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605609"></a><a class="indexterm" name="id2605617"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605586"></a><a class="indexterm" name="id2605594"></a>
 		Samba-3 currently does not implement multiple group membership internally. If you use the Windows 
 		NT4 Domain User Manager to manage accounts and you have an LDAP backend, the multiple group
 		membership is stored in the POSIX groups area. If you use either tdbsam or smbpasswd backend,
@@ -1092,14 +1092,14 @@ Users                 Ordinary users
 		file to which you migrated the NT4 Domain data, do not forget to edit the UNIX <code class="filename">/etc/passwd</code>
 		and <code class="filename">/etc/group</code> information also. That is where the multiple group information
 		is most closely at your fingertips.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605652"></a><a name="id2605655"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605630"></a><a name="id2605632"></a></td><td align="left" valign="top"><p>
 		How can I reset group membership after loading the account information into the LDAP database?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605666"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605643"></a>
 		You can use the NT4 Domain User Manager that can be downloaded from the Microsoft Web site. The
 		installation file is called <code class="filename">SRVTOOLS.EXE</code>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605687"></a><a name="id2605689"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605692"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605664"></a><a name="id2605666"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605669"></a>
 		What are the limits or constraints that apply to group names?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605708"></a><a class="indexterm" name="id2605715"></a><a class="indexterm" name="id2605723"></a><a class="indexterm" name="id2605731"></a><a class="indexterm" name="id2605739"></a><a class="indexterm" name="id2605747"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2605685"></a><a class="indexterm" name="id2605693"></a><a class="indexterm" name="id2605701"></a><a class="indexterm" name="id2605708"></a><a class="indexterm" name="id2605716"></a><a class="indexterm" name="id2605724"></a>
 		A Windows 200x group name can be up to 254 characters long, while in Windows NT4 the group
 		name is limited to 20 characters. Most UNIX systems limit this to 32 characters. Windows 
 		groups can contain upper- and lowercase characters, as well as spaces.
@@ -1111,7 +1111,7 @@ Users                 Ordinary users
 		of the POSIX standards and likewise do not permit uppercase or space characters in group
 		or user account names. You have to experiment with your system to find what its 
 		peculiarities are.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605791"></a><a name="id2605794"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605797"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2605769"></a><a name="id2605771"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2605774"></a>
 		My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba-3
 		LDAP backend system using the vampire process?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -1120,7 +1120,7 @@ Users                 Ordinary users
 		you would not be able to migrate 323,000 accounts because this number cannot fit into a 16-bit unsigned
 		integer. UNIX/Linux systems that have a 32-bit UID/GID can easily handle this number of accounts. 
 		Please check this carefully before you attempt to effect a migration using the vampire process.
-		</p><p><a class="indexterm" name="id2605834"></a>
+		</p><p><a class="indexterm" name="id2605811"></a>
 		Migration speed depends much on the processor speed, the network speed, disk I/O capability, and
 		LDAP update overheads. On a dual processor AMD MP1600+ with 1 GB memory that was mirroring LDAP
 		to a second identical system over 1 Gb Ethernet, I was able to migrate around 180 user accounts
diff --git a/docs/htmldocs/Samba3-ByExample/nw4migration.html b/docs/htmldocs/Samba3-ByExample/nw4migration.html
index d07af7ba00..18f7b8d6f2 100644
--- a/docs/htmldocs/Samba3-ByExample/nw4migration.html
+++ b/docs/htmldocs/Samba3-ByExample/nw4migration.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�Migrating NetWare Server to Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="ntmigration.html" title="Chapter�9.�Migrating NT4 Domain to Samba-3"><link rel="next" href="RefSection.html" title="Part�III.�Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�Migrating NetWare Server to Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ntmigration.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="RefSection.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="nw4migration"></a>Chapter�10.�Migrating NetWare Server to Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="nw4migration.html#id2606026">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606137">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606228">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606305">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606495">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606504">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></div><p>
-	<a class="indexterm" name="id2605872"></a>
-	<a class="indexterm" name="id2605878"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�Migrating NetWare Server to Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="ntmigration.html" title="Chapter�9.�Migrating NT4 Domain to Samba-3"><link rel="next" href="RefSection.html" title="Part�III.�Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�Migrating NetWare Server to Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ntmigration.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="RefSection.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="nw4migration"></a>Chapter�10.�Migrating NetWare Server to Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="nw4migration.html#id2606004">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606120">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606233">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606310">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id2606500">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id2606509">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></div><p>
+	<a class="indexterm" name="id2605849"></a>
+	<a class="indexterm" name="id2605855"></a>
 	Novell is a company any seasoned IT manager has to admire. It has become increasingly
 	Linux-friendly and is emerging out of a deep regression that almost saw the company
 	disappear into obscurity. Novell's SUSE Linux hosts the NetWare server and it is the
@@ -8,24 +8,24 @@
 	It will be interesting to see what becomes of NetWare over time.
 	Meanwhile, there can be no denying that Novell is a Linux company.
 	</p><p>
-	<a class="indexterm" name="id2605896"></a>
-	<a class="indexterm" name="id2605903"></a>
-	<a class="indexterm" name="id2605910"></a>
-	<a class="indexterm" name="id2605917"></a>
+	<a class="indexterm" name="id2605873"></a>
+	<a class="indexterm" name="id2605880"></a>
+	<a class="indexterm" name="id2605887"></a>
+	<a class="indexterm" name="id2605894"></a>
 	Whatever flavor of Linux is preferred in your environment, whether Red Hat, Debian,
 	Gentoo, Mandrake, or SUSE (Novell), the information in this chapter should be read with
 	the knowledge that file locations may vary a little; even so, the information
 	in this chapter should provide something of value.
 	</p><p>
-	<a class="indexterm" name="id2605932"></a>
+	<a class="indexterm" name="id2605909"></a>
 	Contributions to this chapter were made by Misty Stanley-Jones, a UNIX administrator of many
 	years who surfaced on the Samba mailing list with a barrage of questions and who
 	regularly helps other administrators to solve thorny Samba migration questions.
 	</p><p>
-	<a class="indexterm" name="id2605946"></a>
-	<a class="indexterm" name="id2605953"></a>
-	<a class="indexterm" name="id2605960"></a>
-	<a class="indexterm" name="id2605966"></a>
+	<a class="indexterm" name="id2605923"></a>
+	<a class="indexterm" name="id2605930"></a>
+	<a class="indexterm" name="id2605937"></a>
+	<a class="indexterm" name="id2605944"></a>
 	One wonders how many NetWare servers remain in active service. Many are being migrated
 	to Samba on Linux. Red Hat Linux, SUSE Linux 9.x, and SUSE Linux Enterprise Server 9 are
 	ideal target platforms to which a NetWare server may be migrated. The migration method
@@ -49,28 +49,28 @@
 	File paths have been modified to permit use of RPM packages provided by Novell. In the
 	original documentation contributed by Misty, the Courier-IMAP package had been built
 	directly from the original source tarball.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606026"></a>Introduction</h2></div></div></div><p>
-	<a class="indexterm" name="id2606034"></a>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606004"></a>Introduction</h2></div></div></div><p>
+	<a class="indexterm" name="id2606011"></a>
 	Misty Stanley-Jones was recruited by Abmas to administer a network that had
 	not received much attention for some years and was much in need of a makeover.
 	As a brand-new sysadmin to this company, she inherited a very old Novell file server
 	and came with a determination to change things for the better.
 	</p><p>
 	A site survey turned up the following details for the old NetWare server:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td>200 MHz MMX processor</td></tr><tr><td>512K RAM</td></tr><tr><td>24 GB disk space in RAID1</td></tr><tr><td>Novell 4.11 patched to service pack 7</td></tr><tr><td>60+ users</td></tr><tr><td>7 network-attached printers</td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>200 MHz MMX processor</p></td></tr><tr><td><p>512K RAM</p></td></tr><tr><td><p>24 GB disk space in RAID1</p></td></tr><tr><td><p>Novell 4.11 patched to service pack 7</p></td></tr><tr><td><p>60+ users</p></td></tr><tr><td><p>7 network-attached printers</p></td></tr></table><p>
 	The company had outgrown this server several years before and was dealing with
 	severe growing pains. Some of the problems experienced were:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Very slow performance</p></li><li><p>Available storage hovering around the 5% range</p><div class="itemizedlist"><ul type="circle"><li><p>Extremely slow print spooling.</p></li><li><p>
 					Users storing information on their local hard
 					drives, causing backup integrity problems
 					</p></li></ul></div></li></ul></div><p>
-	<a class="indexterm" name="id2606123"></a>
+	<a class="indexterm" name="id2606107"></a>
 	At one point disk space had filled up to 100 percent, causing the payroll database
 	to become corrupt. This caused the accounting department to be down for over
 	a week and necessitated deployment of another file server. The replacement
 	server was created with very poor security and design considerations from
 	a discarded desktop PC.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606137"></a>Assignment Tasks</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606120"></a>Assignment Tasks</h3></div></div></div><p>
 	Misty has provided this summary of her migration experience in the hope
 	that it will help someone to avoid the challenges she faced. Perhaps her
 	configuration files and background will accelerate your learning as you
@@ -89,55 +89,55 @@
 	is the result of treatment given to her files in an attempt to make
 	the overall information more useful to you.
 	</p><p>
-	<a class="indexterm" name="id2606174"></a>
+	<a class="indexterm" name="id2606158"></a>
 	After management reviewed a cost-benefit report as well as an estimated
 	time-to-completion, approval was given proceed with the solution proposed.
 	The server was built from purchased components. The total project cost
 	was $3,000. A brief description of the configuration follows:
 	</p><table class="simplelist" border="0" summary="Simple list"><tr><td>
-			3.0 GHz P4 Processor
+			<p>3.0 GHz P4 Processor</p>
 		</td></tr><tr><td>
-			1 GB RAM
+			<p>1 GB RAM</p>
 		</td></tr><tr><td>
-			120 GB SATA operating system drive
+			<p>120 GB SATA operating system drive</p>
 		</td></tr><tr><td>
-			4 x 80 GB SATA data drives (RAID5 240 GB capacity)
+			<p>4 x 80 GB SATA data drives (RAID5 240 GB capacity)</p>
 		</td></tr><tr><td>
-			2 x 80 GB SATA removable drives for online backup
+			<p>2 x 80 GB SATA removable drives for online backup</p>
 		</td></tr><tr><td>
-			A DLT drive for asynchronous offline backup
+			<p>A DLT drive for asynchronous offline backup</p>
 		</td></tr><tr><td>
-			SUSE Linux Professional 9.1
+			<p>SUSE Linux Professional 9.1</p>
 		</td></tr></table><p>
 	The new system has operated for 6 months without problems. Over the past months
 	much attention has been focused on cleaning up desktops and user profiles.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606228"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2606236"></a>
-	<a class="indexterm" name="id2606243"></a>
-	<a class="indexterm" name="id2606250"></a>
-	<a class="indexterm" name="id2606257"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606233"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2606241"></a>
+	<a class="indexterm" name="id2606248"></a>
+	<a class="indexterm" name="id2606255"></a>
+	<a class="indexterm" name="id2606262"></a>
 	A decision to use LDAP was made even though I knew nothing about LDAP except that
 	I had been reading the book &#8220;<span class="quote">LDAP System Administration,</span>&#8221; by Gerald Carter.
 	LDAP seemed to provide some of the functionality of Novell's e-Directory Services
 	and would provide centralized authentication and identity management.
 	</p><p>
-	<a class="indexterm" name="id2606276"></a>
-	<a class="indexterm" name="id2606282"></a>
-	<a class="indexterm" name="id2606289"></a>
+	<a class="indexterm" name="id2606281"></a>
+	<a class="indexterm" name="id2606288"></a>
+	<a class="indexterm" name="id2606294"></a>
 	Building the LDAP database took a while and a lot of trial and error. Following
 	the guidance I obtained from &#8220;<span class="quote">LDAP System 
 	Administration,</span>&#8221; I installed OpenLDAP (from RPM; later I compiled
 	a more current version from source) and built my initial LDAP tree.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606305"></a>Technical Issues</h3></div></div></div><p>
-	<a class="indexterm" name="id2606313"></a>
-	<a class="indexterm" name="id2606319"></a>
-	<a class="indexterm" name="id2606326"></a>
-	<a class="indexterm" name="id2606333"></a>
-	<a class="indexterm" name="id2606340"></a>
-	<a class="indexterm" name="id2606347"></a>
-	<a class="indexterm" name="id2606354"></a>
-	<a class="indexterm" name="id2606360"></a>
-	<a class="indexterm" name="id2606367"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606310"></a>Technical Issues</h3></div></div></div><p>
+	<a class="indexterm" name="id2606318"></a>
+	<a class="indexterm" name="id2606325"></a>
+	<a class="indexterm" name="id2606332"></a>
+	<a class="indexterm" name="id2606338"></a>
+	<a class="indexterm" name="id2606345"></a>
+	<a class="indexterm" name="id2606352"></a>
+	<a class="indexterm" name="id2606359"></a>
+	<a class="indexterm" name="id2606366"></a>
+	<a class="indexterm" name="id2606372"></a>
 	The first challenge was to create a company white pages, followed by manually
 	entering everything from the printed company directory. This used only the inetOrgPerson
 	object class from the OpenLDAP schemas. The next step was to write a shell script that
@@ -189,15 +189,15 @@ done
 	the LDAP directory. The tools consist of a set of Perl scripts for migration of users, groups,
 	aliases, hosts, netgroups, networks, protocols, PRCs, and services from the existing ASCII text
 	files (or from a name service such as NIS). This too set can be obtained from the <a class="ulink" href="http://www.padl.com" target="_top">PADL Web site</a>.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606495"></a>Implementation</h2></div></div></div><p>
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606504"></a>NetWare Migration Using LDAP Backend</h3></div></div></div><p>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606500"></a>Implementation</h2></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606509"></a>NetWare Migration Using LDAP Backend</h3></div></div></div><p>
 	The following software must be installed on the SUSE Linux Enterprise Server to perform
 	this migration:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td>courier-imap</td></tr><tr><td>courier-imap-ldap</td></tr><tr><td>nss_ldap</td></tr><tr><td>openldap2-client</td></tr><tr><td>openldap2-devel (only for Samba compilation)</td></tr><tr><td>openldap2</td></tr><tr><td>pam_ldap</td></tr><tr><td>samba-3.0.20 or later</td></tr><tr><td>samba-client-3.0.20 or later</td></tr><tr><td>samba-winbind-3.0.20 or later</td></tr><tr><td>smbldap-tools Version 0.9.1</td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>courier-imap</p></td></tr><tr><td><p>courier-imap-ldap</p></td></tr><tr><td><p>nss_ldap</p></td></tr><tr><td><p>openldap2-client</p></td></tr><tr><td><p>openldap2-devel (only for Samba compilation)</p></td></tr><tr><td><p>openldap2</p></td></tr><tr><td><p>pam_ldap</p></td></tr><tr><td><p>samba-3.0.20 or later</p></td></tr><tr><td><p>samba-client-3.0.20 or later</p></td></tr><tr><td><p>samba-winbind-3.0.20 or later</p></td></tr><tr><td><p>smbldap-tools Version 0.9.1</p></td></tr></table><p>
 	Each software application must be carefully configured in preparation for migration.
 	The configuration files used at Abmas are provided as a guide and should be modified
 	to meet needs at your site.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606568"></a>LDAP Server Configuration</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606584"></a>LDAP Server Configuration</h4></div></div></div><p>
 	The <code class="filename">/etc/openldap/slapd.conf</code> file Misty used is shown here:
 </p><pre class="programlisting">
 #/etc/openldap/slapd.conf
@@ -362,7 +362,7 @@ access to *
   by * read
 </pre><p>
 </p><p>
-	<a class="indexterm" name="id2606766"></a>
+	<a class="indexterm" name="id2606776"></a>
 	The <code class="filename">/etc/ldap.conf</code> file used is listed in <a class="link" href="nw4migration.html#ch8ldap" title="Example�10.2.�NSS LDAP Control File /etc/ldap.conf">&#8220;NSS LDAP Control File  /etc/ldap.conf&#8221;</a>.
 	</p><div class="example"><a name="ch8ldap"></a><p class="title"><b>Example�10.2.�NSS LDAP Control File  /etc/ldap.conf</b></p><div class="example-contents"><pre class="screen">
 # /etc/ldap.conf
@@ -416,8 +416,8 @@ group:    compat ldap
 # possibilities to store hosts, services, ethers, and lots of other things.
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2606851"></a>
-	<a class="indexterm" name="id2606857"></a>
+	<a class="indexterm" name="id2606860"></a>
+	<a class="indexterm" name="id2606867"></a>
 	In my setup, users authenticate via PAM and NSS using LDAP-based accounts.
 	The configuration file that controls the behavior of the PAM <code class="literal">pam_unix2</code>
 	module is shown in <a class="link" href="nw4migration.html#sbepu2" title="Example�10.3.�The PAM Control File /etc/security/pam_unix2.conf">&#8220;The PAM Control File /etc/security/pam_unix2.conf&#8221;</a> file.
@@ -458,7 +458,7 @@ auth: use_ldap
 account: use_ldap
 password: use_ldap
 session: none
-</pre></div></div><br class="example-break"><a class="indexterm" name="id2606922"></a><a class="indexterm" name="id2606929"></a><a class="indexterm" name="id2606936"></a><div class="itemizedlist"><ul type="disc"><li><p>
+</pre></div></div><br class="example-break"><a class="indexterm" name="id2606949"></a><a class="indexterm" name="id2606956"></a><a class="indexterm" name="id2606963"></a><div class="itemizedlist"><ul type="disc"><li><p>
 			If your LDAP database goes down, nobody can authenticate except for root.
 			</p></li><li><p>
 			If failover is configured incorrectly, weird behavior can occur. For example, 
@@ -468,31 +468,31 @@ session: none
 	of this document, and steps for implementing it are well documented.
 	</p><p>
 	The following services authenticate using LDAP:
-	</p><a class="indexterm" name="id2606972"></a><a class="indexterm" name="id2606979"></a><a class="indexterm" name="id2606986"></a><table class="simplelist" border="0" summary="Simple list"><tr><td>UNIX login/ssh</td></tr><tr><td>Postfix (SMTP)</td></tr><tr><td>Courier-IMAP/IMAPS/POP3/POP3S</td></tr></table><p>
-	<a class="indexterm" name="id2607011"></a>
-	<a class="indexterm" name="id2607018"></a>
+	</p><a class="indexterm" name="id2606999"></a><a class="indexterm" name="id2607006"></a><a class="indexterm" name="id2607013"></a><table class="simplelist" border="0" summary="Simple list"><tr><td><p>UNIX login/ssh</p></td></tr><tr><td><p>Postfix (SMTP)</p></td></tr><tr><td><p>Courier-IMAP/IMAPS/POP3/POP3S</p></td></tr></table><p>
+	<a class="indexterm" name="id2607042"></a>
+	<a class="indexterm" name="id2607048"></a>
 	Companywide white pages can be searched using an LDAP client
 	such as the one in the Windows Address Book.
 	</p><p>
-	<a class="indexterm" name="id2607030"></a>
-	<a class="indexterm" name="id2607037"></a>
+	<a class="indexterm" name="id2607061"></a>
+	<a class="indexterm" name="id2607067"></a>
 	Having gained a solid understanding of LDAP and a relatively workable LDAP tree
 	thus far, it was time to configure Samba. I compiled the latest stable Samba and
 	also installed the latest <code class="literal">smbldap-tools</code> from 
 	<a class="ulink" href="http://idealx.com" target="_top">Idealx</a>.
 	</p><p>
 	The Samba <code class="filename">smb.conf</code> file was configured as shown in <a class="link" href="nw4migration.html#ch8smbconf" title="Example�10.4.�Samba Configuration File smb.conf Part A">&#8220;Samba Configuration File  smb.conf Part A&#8221;</a>.
-	</p><div class="example"><a name="ch8smbconf"></a><p class="title"><b>Example�10.4.�Samba Configuration File  smb.conf Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607107"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2607119"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2607130"></a><em class="parameter"><code>server string = Corp File Server</code></em></td></tr><tr><td><a class="indexterm" name="id2607142"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2607155"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607166"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2607178"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2607190"></a><em class="parameter"><code>log file = /data/samba/log/%m.log</code></em></td></tr><tr><td><a class="indexterm" name="id2607202"></a><em class="parameter"><code>name resolve order = wins host bcast</code></em></td></tr><tr><td><a class="indexterm" name="id2607214"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607226"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2607238"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607250"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2607261"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2607274"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607286"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607299"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607312"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2607325"></a><em class="parameter"><code>add machine script = /usr/local/sbin/smbldap-useradd -w "%m"</code></em></td></tr><tr><td><a class="indexterm" name="id2607338"></a><em class="parameter"><code>logon script = logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2607349"></a><em class="parameter"><code>logon path = \\%L\profiles\%U\%a</code></em></td></tr><tr><td><a class="indexterm" name="id2607361"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2607373"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2607385"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607396"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607408"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2607420"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2607432"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607444"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607456"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607468"></a><em class="parameter"><code>ldap suffix = ou=MEGANET2,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2607480"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2607492"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607504"></a><em class="parameter"><code>admin users = root, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607516"></a><em class="parameter"><code>printer admin = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607528"></a><em class="parameter"><code>force printername = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf2"></a><p class="title"><b>Example�10.5.�Samba Configuration File  smb.conf Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2607567"></a><em class="parameter"><code>comment = Network logon service</code></em></td></tr><tr><td><a class="indexterm" name="id2607579"></a><em class="parameter"><code>path = /data/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2607591"></a><em class="parameter"><code>write list = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607603"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2607623"></a><em class="parameter"><code>comment = Roaming Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2607635"></a><em class="parameter"><code>path = /data/samba/profiles/</code></em></td></tr><tr><td><a class="indexterm" name="id2607647"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607658"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607670"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607682"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2607702"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2607714"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2607726"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607737"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2607749"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607761"></a><em class="parameter"><code>hide files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607772"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[software]</code></em></td></tr><tr><td><a class="indexterm" name="id2607793"></a><em class="parameter"><code>comment = Software for %a computers</code></em></td></tr><tr><td><a class="indexterm" name="id2607805"></a><em class="parameter"><code>path = /data/samba/shares/software/%a</code></em></td></tr><tr><td><a class="indexterm" name="id2607817"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2607837"></a><em class="parameter"><code>comment = Public Files</code></em></td></tr><tr><td><a class="indexterm" name="id2607849"></a><em class="parameter"><code>path = /data/samba/shares/public</code></em></td></tr><tr><td><a class="indexterm" name="id2607861"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607873"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[PDF]</code></em></td></tr><tr><td><a class="indexterm" name="id2607893"></a><em class="parameter"><code>comment = Location of documents printed to PDFCreator printer</code></em></td></tr><tr><td><a class="indexterm" name="id2607906"></a><em class="parameter"><code>path = /data/samba/shares/pdf</code></em></td></tr><tr><td><a class="indexterm" name="id2607917"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf3"></a><p class="title"><b>Example�10.6.�Samba Configuration File  smb.conf Part C</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[EVERYTHING]</code></em></td></tr><tr><td><a class="indexterm" name="id2607956"></a><em class="parameter"><code>comment = All shares</code></em></td></tr><tr><td><a class="indexterm" name="id2607968"></a><em class="parameter"><code>path = /data/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2607980"></a><em class="parameter"><code>valid users = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607992"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[CDROM]</code></em></td></tr><tr><td><a class="indexterm" name="id2608012"></a><em class="parameter"><code>comment = CD-ROM on MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2608024"></a><em class="parameter"><code>path = /mnt</code></em></td></tr><tr><td><a class="indexterm" name="id2608035"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2608056"></a><em class="parameter"><code>comment = Printer Drivers Share</code></em></td></tr><tr><td><a class="indexterm" name="id2608068"></a><em class="parameter"><code>path = /data/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2608079"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2608091"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2608112"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2608123"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2608135"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608147"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608158"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[acct_hp8500]</code></em></td></tr><tr><td><a class="indexterm" name="id2608179"></a><em class="parameter"><code>comment = "Accounting Color Laser Printer"</code></em></td></tr><tr><td><a class="indexterm" name="id2608191"></a><em class="parameter"><code>path = /data/samba/spool/private</code></em></td></tr><tr><td><a class="indexterm" name="id2608203"></a><em class="parameter"><code>valid users = @acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry</code></em></td></tr><tr><td><a class="indexterm" name="id2608216"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608227"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608239"></a><em class="parameter"><code>copy = printers</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[plotter]</code></em></td></tr><tr><td><a class="indexterm" name="id2608259"></a><em class="parameter"><code>comment = Engineering Plotter</code></em></td></tr><tr><td><a class="indexterm" name="id2608271"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2608283"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608295"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608306"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608318"></a><em class="parameter"><code>copy = printers</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf4"></a><p class="title"><b>Example�10.7.�Samba Configuration File  smb.conf Part D</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[APPS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608357"></a><em class="parameter"><code>path = /data/samba/shares/Apps</code></em></td></tr><tr><td><a class="indexterm" name="id2608369"></a><em class="parameter"><code>force group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2608381"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ACCT]</code></em></td></tr><tr><td><a class="indexterm" name="id2608402"></a><em class="parameter"><code>path = /data/samba/shares/Accounting</code></em></td></tr><tr><td><a class="indexterm" name="id2608414"></a><em class="parameter"><code>valid users = @acct, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2608426"></a><em class="parameter"><code>force group = acct</code></em></td></tr><tr><td><a class="indexterm" name="id2608437"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608449"></a><em class="parameter"><code>create mask = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2608460"></a><em class="parameter"><code>directory mask = 0770</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ACCT_ADMIN]</code></em></td></tr><tr><td><a class="indexterm" name="id2608481"></a><em class="parameter"><code>path = /data/samba/shares/Acct_Admin</code></em></td></tr><tr><td><a class="indexterm" name="id2608493"></a><em class="parameter"><code>valid users = @"acct_admin"</code></em></td></tr><tr><td><a class="indexterm" name="id2608505"></a><em class="parameter"><code>force group = acct_admin</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[HR_PR]</code></em></td></tr><tr><td><a class="indexterm" name="id2608526"></a><em class="parameter"><code>path = /data/samba/shares/HR_PR</code></em></td></tr><tr><td><a class="indexterm" name="id2608538"></a><em class="parameter"><code>valid users = @hr, @acct_admin</code></em></td></tr><tr><td><a class="indexterm" name="id2608549"></a><em class="parameter"><code>force group = hr</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ENGR]</code></em></td></tr><tr><td><a class="indexterm" name="id2608570"></a><em class="parameter"><code>path = /data/samba/shares/Engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608582"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2608594"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608606"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608617"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[DATA]</code></em></td></tr><tr><td><a class="indexterm" name="id2608638"></a><em class="parameter"><code>path = /data/samba/shares/DATA</code></em></td></tr><tr><td><a class="indexterm" name="id2608650"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2608662"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608674"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608685"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608697"></a><em class="parameter"><code>copy = engr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf5"></a><p class="title"><b>Example�10.8.�Samba Configuration File  smb.conf Part E</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[X]</code></em></td></tr><tr><td><a class="indexterm" name="id2608736"></a><em class="parameter"><code>path = /data/samba/shares/X</code></em></td></tr><tr><td><a class="indexterm" name="id2608748"></a><em class="parameter"><code>valid users = @engr, @acct</code></em></td></tr><tr><td><a class="indexterm" name="id2608759"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608771"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608782"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608794"></a><em class="parameter"><code>copy = engr</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[NETWORK]</code></em></td></tr><tr><td><a class="indexterm" name="id2608814"></a><em class="parameter"><code>path = /data/samba/shares/network</code></em></td></tr><tr><td><a class="indexterm" name="id2608826"></a><em class="parameter"><code>valid users = "@Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2608838"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608850"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608861"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[UTILS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608882"></a><em class="parameter"><code>path = /data/samba/shares/Utils</code></em></td></tr><tr><td><a class="indexterm" name="id2608894"></a><em class="parameter"><code>write list = "@Domain Admins"</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[SYS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608915"></a><em class="parameter"><code>path = /data/samba/shares/SYS</code></em></td></tr><tr><td><a class="indexterm" name="id2608926"></a><em class="parameter"><code>valid users = chad</code></em></td></tr><tr><td><a class="indexterm" name="id2608938"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608950"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2608964"></a>
-	<a class="indexterm" name="id2608971"></a>
-	<a class="indexterm" name="id2608978"></a>
+	</p><div class="example"><a name="ch8smbconf"></a><p class="title"><b>Example�10.4.�Samba Configuration File  smb.conf Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607137"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2607149"></a><em class="parameter"><code>netbios name = MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2607161"></a><em class="parameter"><code>server string = Corp File Server</code></em></td></tr><tr><td><a class="indexterm" name="id2607173"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2607185"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607197"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2607209"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2607220"></a><em class="parameter"><code>log file = /data/samba/log/%m.log</code></em></td></tr><tr><td><a class="indexterm" name="id2607232"></a><em class="parameter"><code>name resolve order = wins host bcast</code></em></td></tr><tr><td><a class="indexterm" name="id2607244"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607256"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2607268"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607280"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2607292"></a><em class="parameter"><code>add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2607304"></a><em class="parameter"><code>add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607317"></a><em class="parameter"><code>add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607330"></a><em class="parameter"><code>delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</code></em></td></tr><tr><td><a class="indexterm" name="id2607343"></a><em class="parameter"><code>set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</code></em></td></tr><tr><td><a class="indexterm" name="id2607355"></a><em class="parameter"><code>add machine script = /usr/local/sbin/smbldap-useradd -w "%m"</code></em></td></tr><tr><td><a class="indexterm" name="id2607368"></a><em class="parameter"><code>logon script = logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2607380"></a><em class="parameter"><code>logon path = \\%L\profiles\%U\%a</code></em></td></tr><tr><td><a class="indexterm" name="id2607392"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2607403"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2607415"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607427"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607438"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2607451"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2607463"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607475"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607487"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607498"></a><em class="parameter"><code>ldap suffix = ou=MEGANET2,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2607510"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2607522"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2607534"></a><em class="parameter"><code>admin users = root, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607546"></a><em class="parameter"><code>printer admin = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607558"></a><em class="parameter"><code>force printername = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf2"></a><p class="title"><b>Example�10.5.�Samba Configuration File  smb.conf Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2607598"></a><em class="parameter"><code>comment = Network logon service</code></em></td></tr><tr><td><a class="indexterm" name="id2607609"></a><em class="parameter"><code>path = /data/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2607621"></a><em class="parameter"><code>write list = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2607633"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2607654"></a><em class="parameter"><code>comment = Roaming Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2607665"></a><em class="parameter"><code>path = /data/samba/profiles/</code></em></td></tr><tr><td><a class="indexterm" name="id2607677"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607689"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607701"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607712"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2607733"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2607745"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2607756"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607768"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2607779"></a><em class="parameter"><code>veto files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607791"></a><em class="parameter"><code>hide files = desktop.ini</code></em></td></tr><tr><td><a class="indexterm" name="id2607803"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[software]</code></em></td></tr><tr><td><a class="indexterm" name="id2607823"></a><em class="parameter"><code>comment = Software for %a computers</code></em></td></tr><tr><td><a class="indexterm" name="id2607835"></a><em class="parameter"><code>path = /data/samba/shares/software/%a</code></em></td></tr><tr><td><a class="indexterm" name="id2607847"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2607868"></a><em class="parameter"><code>comment = Public Files</code></em></td></tr><tr><td><a class="indexterm" name="id2607880"></a><em class="parameter"><code>path = /data/samba/shares/public</code></em></td></tr><tr><td><a class="indexterm" name="id2607891"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2607903"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[PDF]</code></em></td></tr><tr><td><a class="indexterm" name="id2607924"></a><em class="parameter"><code>comment = Location of documents printed to PDFCreator printer</code></em></td></tr><tr><td><a class="indexterm" name="id2607936"></a><em class="parameter"><code>path = /data/samba/shares/pdf</code></em></td></tr><tr><td><a class="indexterm" name="id2607948"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf3"></a><p class="title"><b>Example�10.6.�Samba Configuration File  smb.conf Part C</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[EVERYTHING]</code></em></td></tr><tr><td><a class="indexterm" name="id2607987"></a><em class="parameter"><code>comment = All shares</code></em></td></tr><tr><td><a class="indexterm" name="id2607998"></a><em class="parameter"><code>path = /data/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2608010"></a><em class="parameter"><code>valid users = "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2608022"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[CDROM]</code></em></td></tr><tr><td><a class="indexterm" name="id2608042"></a><em class="parameter"><code>comment = CD-ROM on MASSIVE</code></em></td></tr><tr><td><a class="indexterm" name="id2608054"></a><em class="parameter"><code>path = /mnt</code></em></td></tr><tr><td><a class="indexterm" name="id2608066"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2608086"></a><em class="parameter"><code>comment = Printer Drivers Share</code></em></td></tr><tr><td><a class="indexterm" name="id2608098"></a><em class="parameter"><code>path = /data/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2608110"></a><em class="parameter"><code>write list = root</code></em></td></tr><tr><td><a class="indexterm" name="id2608121"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2608142"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2608154"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2608165"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608177"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608189"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[acct_hp8500]</code></em></td></tr><tr><td><a class="indexterm" name="id2608209"></a><em class="parameter"><code>comment = "Accounting Color Laser Printer"</code></em></td></tr><tr><td><a class="indexterm" name="id2608221"></a><em class="parameter"><code>path = /data/samba/spool/private</code></em></td></tr><tr><td><a class="indexterm" name="id2608233"></a><em class="parameter"><code>valid users = @acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry</code></em></td></tr><tr><td><a class="indexterm" name="id2608246"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608258"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608269"></a><em class="parameter"><code>copy = printers</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[plotter]</code></em></td></tr><tr><td><a class="indexterm" name="id2608290"></a><em class="parameter"><code>comment = Engineering Plotter</code></em></td></tr><tr><td><a class="indexterm" name="id2608302"></a><em class="parameter"><code>path = /data/samba/spool</code></em></td></tr><tr><td><a class="indexterm" name="id2608313"></a><em class="parameter"><code>create mask = 0644</code></em></td></tr><tr><td><a class="indexterm" name="id2608325"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608337"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2608348"></a><em class="parameter"><code>copy = printers</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf4"></a><p class="title"><b>Example�10.7.�Samba Configuration File  smb.conf Part D</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[APPS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608388"></a><em class="parameter"><code>path = /data/samba/shares/Apps</code></em></td></tr><tr><td><a class="indexterm" name="id2608400"></a><em class="parameter"><code>force group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2608411"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ACCT]</code></em></td></tr><tr><td><a class="indexterm" name="id2608432"></a><em class="parameter"><code>path = /data/samba/shares/Accounting</code></em></td></tr><tr><td><a class="indexterm" name="id2608444"></a><em class="parameter"><code>valid users = @acct, "@Domain Admins"</code></em></td></tr><tr><td><a class="indexterm" name="id2608456"></a><em class="parameter"><code>force group = acct</code></em></td></tr><tr><td><a class="indexterm" name="id2608468"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608479"></a><em class="parameter"><code>create mask = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2608491"></a><em class="parameter"><code>directory mask = 0770</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ACCT_ADMIN]</code></em></td></tr><tr><td><a class="indexterm" name="id2608512"></a><em class="parameter"><code>path = /data/samba/shares/Acct_Admin</code></em></td></tr><tr><td><a class="indexterm" name="id2608524"></a><em class="parameter"><code>valid users = @”acct_admin”</code></em></td></tr><tr><td><a class="indexterm" name="id2608536"></a><em class="parameter"><code>force group = acct_admin</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[HR_PR]</code></em></td></tr><tr><td><a class="indexterm" name="id2608557"></a><em class="parameter"><code>path = /data/samba/shares/HR_PR</code></em></td></tr><tr><td><a class="indexterm" name="id2608569"></a><em class="parameter"><code>valid users = @hr, @acct_admin</code></em></td></tr><tr><td><a class="indexterm" name="id2608581"></a><em class="parameter"><code>force group = hr</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[ENGR]</code></em></td></tr><tr><td><a class="indexterm" name="id2608601"></a><em class="parameter"><code>path = /data/samba/shares/Engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608613"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2608625"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608637"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608649"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[DATA]</code></em></td></tr><tr><td><a class="indexterm" name="id2608669"></a><em class="parameter"><code>path = /data/samba/shares/DATA</code></em></td></tr><tr><td><a class="indexterm" name="id2608681"></a><em class="parameter"><code>valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri</code></em></td></tr><tr><td><a class="indexterm" name="id2608693"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608705"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608717"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608728"></a><em class="parameter"><code>copy = engr</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch8smbconf5"></a><p class="title"><b>Example�10.8.�Samba Configuration File  smb.conf Part E</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[X]</code></em></td></tr><tr><td><a class="indexterm" name="id2608767"></a><em class="parameter"><code>path = /data/samba/shares/X</code></em></td></tr><tr><td><a class="indexterm" name="id2608779"></a><em class="parameter"><code>valid users = @engr, @acct</code></em></td></tr><tr><td><a class="indexterm" name="id2608790"></a><em class="parameter"><code>force group = engr</code></em></td></tr><tr><td><a class="indexterm" name="id2608802"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608814"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608825"></a><em class="parameter"><code>copy = engr</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[NETWORK]</code></em></td></tr><tr><td><a class="indexterm" name="id2608846"></a><em class="parameter"><code>path = /data/samba/shares/network</code></em></td></tr><tr><td><a class="indexterm" name="id2608858"></a><em class="parameter"><code>valid users = "@Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2608869"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608881"></a><em class="parameter"><code>create mask = 0770</code></em></td></tr><tr><td><a class="indexterm" name="id2608893"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[UTILS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608913"></a><em class="parameter"><code>path = /data/samba/shares/Utils</code></em></td></tr><tr><td><a class="indexterm" name="id2608925"></a><em class="parameter"><code>write list = "@Domain Admins"</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[SYS]</code></em></td></tr><tr><td><a class="indexterm" name="id2608946"></a><em class="parameter"><code>path = /data/samba/shares/SYS</code></em></td></tr><tr><td><a class="indexterm" name="id2608958"></a><em class="parameter"><code>valid users = chad</code></em></td></tr><tr><td><a class="indexterm" name="id2608969"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2608981"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2608996"></a>
+	<a class="indexterm" name="id2609002"></a>
+	<a class="indexterm" name="id2609009"></a>
 	Most of these shares are only used by one company group, but they are required
 	because of some ancient Qbasic and Rbase applications were that written expecting
 	their own drive letters.
 	</p><p>
-	<a class="indexterm" name="id2608992"></a>
-	<a class="indexterm" name="id2608998"></a>
-	<a class="indexterm" name="id2609005"></a>
+	<a class="indexterm" name="id2609023"></a>
+	<a class="indexterm" name="id2609030"></a>
+	<a class="indexterm" name="id2609036"></a>
 	Note: During the process of building the new server, I kept data files
 	up to date with the Novell server via use of <code class="literal">rsync</code>. 
 	On a separate system (my workstation in fact), which could be rebooted
@@ -739,7 +739,7 @@ mailDomain="abmas.org"
 with_smbpasswd="0"
 smbpasswd="/usr/bin/smbpasswd"
 </pre></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2609419"></a>
+	<a class="indexterm" name="id2609499"></a>
 	Note: I chose not to take advantage of the TLS capability of this. 
 	Eventually I may go back and tweak it.  Also, I chose not to take advantage
 	of the master/slave configuration as I heard horror stories that it was
@@ -813,11 +813,11 @@ ou: Idmap
 ...
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2609520"></a>
-	<a class="indexterm" name="id2609527"></a>
-	<a class="indexterm" name="id2609534"></a>
-	<a class="indexterm" name="id2609540"></a>
-	<a class="indexterm" name="id2609547"></a>
+	<a class="indexterm" name="id2609600"></a>
+	<a class="indexterm" name="id2609607"></a>
+	<a class="indexterm" name="id2609613"></a>
+	<a class="indexterm" name="id2609620"></a>
+	<a class="indexterm" name="id2609627"></a>
 	With the LDAP directory now initialized, it was time to create the Windows and POSIX
 	(UNIX) group accounts as well as the mappings from Windows groups to UNIX groups.
 	The easiest way to do this was to use <code class="literal">smbldap-groupadd</code> command.
@@ -825,34 +825,34 @@ ou: Idmap
 	unique GID, and an automatically determined RID. I learned the hard way not to
 	try to do this by hand.
 	</p><p>
-	<a class="indexterm" name="id2609570"></a>
-	<a class="indexterm" name="id2609577"></a>
-	<a class="indexterm" name="id2609584"></a>
+	<a class="indexterm" name="id2609650"></a>
+	<a class="indexterm" name="id2609657"></a>
+	<a class="indexterm" name="id2609664"></a>
 	After I had my group mappings in place, I added users to the groups (the users
 	don't really have to exist yet). I used the <code class="literal">smbldap-groupmod</code>
 	command to accomplish this. It can also be done manually by adding memberUID
 	attributes to the group entries in LDAP.
 	</p><p>
-	<a class="indexterm" name="id2609604"></a>
-	<a class="indexterm" name="id2609611"></a>
-	<a class="indexterm" name="id2609618"></a>
+	<a class="indexterm" name="id2609684"></a>
+	<a class="indexterm" name="id2609691"></a>
+	<a class="indexterm" name="id2609698"></a>
 	The most monumental task of all was adding the sambaSamAccount information to each
 	already existent posixAccount entry.  I did it one at a time as I moved people onto
 	the new server, by issuing the command:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbldap-usermod -a -P username
 </pre><p>
-	<a class="indexterm" name="id2609640"></a>
-	<a class="indexterm" name="id2609647"></a>
-	<a class="indexterm" name="id2609654"></a>
+	<a class="indexterm" name="id2609720"></a>
+	<a class="indexterm" name="id2609727"></a>
+	<a class="indexterm" name="id2609734"></a>
 	I completed that step for every user after asking the person what his or her current
 	NetWare password was. The wiser way to have done it would probably have been to dump the
 	entire database to an LDIF file. This can be done by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code> slapcat &gt; somefile.ldif
 </pre><p>
-	<a class="indexterm" name="id2609678"></a>
-	<a class="indexterm" name="id2609684"></a>
+	<a class="indexterm" name="id2609758"></a>
+	<a class="indexterm" name="id2609764"></a>
 	Then update the LDIF file created by using a Perl script to parse and add the
 	appropriate attributes and objectClasses to each entry, followed by re-importing
 	the entire database into the LDAP directory. 
@@ -933,7 +933,7 @@ sambaPwdLastSet: 1103149236
 sambaAcctFlags: [W          ]
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2609789"></a>
+	<a class="indexterm" name="id2609879"></a>
 	So now I could log on with a test user from the machine w2kengrspare. It was all well and
 	good, but that user was in no groups yet and so had pretty boring access.  I fixed that
 	by writing the login script! To write the login script, I used
@@ -942,7 +942,7 @@ sambaAcctFlags: [W          ]
 	easier to learn and more powerful than the standard netlogon scripts I have seen.
 	I also did not have to do a logon script per user or per group.
 	</p><p>
-	<a class="indexterm" name="id2609813"></a>
+	<a class="indexterm" name="id2609904"></a>
 	I downloaded Kixtart and put the following files in my netlogon share:
 </p><pre class="screen">
 KIX32.EXE
@@ -954,7 +954,7 @@ kxrpc.exe &lt;-- Probably useless as it has to run on the server and can
           We can get around the need.
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2609844"></a>
+	<a class="indexterm" name="id2609935"></a>
 	I then wrote the <code class="filename">logon.kix</code> file that is shown in
 	<a class="link" href="nw4migration.html#ch8kix" title="Example�10.15.�Kixtart Control File File: logon.kix">&#8220;Kixtart Control File  File: logon.kix&#8221;</a>. I chose to keep it all in one file, but it
 	can be split up and linked via include directives.
@@ -1137,7 +1137,7 @@ ENDIF
 	have only three such machines, and one is going away in the very near future,
 	so it was easier to do it by hand.
 	</p><p>
-	<a class="indexterm" name="id2610141"></a>
+	<a class="indexterm" name="id2610232"></a>
 	At this point I was able to add the users. This is the part that really falls
 	into upgrade. I moved the users over one group at a time, starting with the
 	people who used the least amount of resources on the network. With each group
diff --git a/docs/htmldocs/Samba3-ByExample/pr01.html b/docs/htmldocs/Samba3-ByExample/pr01.html
index 5342814788..b2a3f97066 100644
--- a/docs/htmldocs/Samba3-ByExample/pr01.html
+++ b/docs/htmldocs/Samba3-ByExample/pr01.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>About the Cover Artwork</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="index.html" title="Samba-3 by Example"><link rel="next" href="pr02.html" title="Acknowledgments"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">About the Cover Artwork</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2540354"></a>About the Cover Artwork</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>About the Cover Artwork</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="index.html" title="Samba-3 by Example"><link rel="next" href="pr02.html" title="Acknowledgments"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">About the Cover Artwork</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2540348"></a>About the Cover Artwork</h2></div></div></div><p>
 	The cover artwork of this book continues the freedom theme of the first
 	edition of &#8220;<span class="quote">Samba-3 by Example</span>&#8221;. The history of civilization
 	demonstrates the fragile nature of freedom. It can be lost in a moment,
diff --git a/docs/htmldocs/Samba3-ByExample/pr02.html b/docs/htmldocs/Samba3-ByExample/pr02.html
index fdb0eb8b32..622272feca 100644
--- a/docs/htmldocs/Samba3-ByExample/pr02.html
+++ b/docs/htmldocs/Samba3-ByExample/pr02.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Acknowledgments</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr01.html" title="About the Cover Artwork"><link rel="next" href="pr03.html" title="Foreword"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Acknowledgments</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr03.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2500840"></a>Acknowledgments</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Acknowledgments</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr01.html" title="About the Cover Artwork"><link rel="next" href="pr03.html" title="Foreword"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Acknowledgments</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr03.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2500831"></a>Acknowledgments</h2></div></div></div><p>
 	<span class="emphasis"><em>Samba-3 by Example</em></span> would not have been written except
 	as a result of feedback provided by reviewers and readers of the book <span class="emphasis"><em>The
 	Official Samba-3 HOWTO and Reference Guide.</em></span> This second edition
diff --git a/docs/htmldocs/Samba3-ByExample/pr03.html b/docs/htmldocs/Samba3-ByExample/pr03.html
index d936c4f4e2..e1c97de2ee 100644
--- a/docs/htmldocs/Samba3-ByExample/pr03.html
+++ b/docs/htmldocs/Samba3-ByExample/pr03.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Foreword</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr02.html" title="Acknowledgments"><link rel="next" href="preface.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Foreword</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr02.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="preface.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2501056"></a>Foreword</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pr03.html#id2501062">By John M. Weathersby, Executive Director, OSSI</a></span></dt></dl></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2501062"></a>By John M. Weathersby, Executive Director, OSSI</h2></div></div></div><div class="blockquote"><blockquote class="blockquote"><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Foreword</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr02.html" title="Acknowledgments"><link rel="next" href="preface.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Foreword</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr02.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="preface.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2501044"></a>Foreword</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pr03.html#id2501052">By John M. Weathersby, Executive Director, OSSI</a></span></dt></dl></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2501052"></a>By John M. Weathersby, Executive Director, OSSI</h2></div></div></div><div class="blockquote"><blockquote class="blockquote"><p>
 The Open Source Software Institute (OSSI) is comprised of representatives from a broad spectrum of business and
 non-business organizations that share a common interest in the promotion of development and implementation
 of open source software solutions globally, and in particular within the United States of America.
diff --git a/docs/htmldocs/Samba3-ByExample/preface.html b/docs/htmldocs/Samba3-ByExample/preface.html
index 4471e155bf..0b44dd908e 100644
--- a/docs/htmldocs/Samba3-ByExample/preface.html
+++ b/docs/htmldocs/Samba3-ByExample/preface.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr03.html" title="Foreword"><link rel="next" href="ExNetworks.html" title="Part�I.�Example Network Configurations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr03.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ExNetworks.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="preface"></a>Preface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="preface.html#id2501251">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2498970">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2498857">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498889">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498954">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2550647">Conventions Used</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="index.html" title="Samba-3 by Example"><link rel="prev" href="pr03.html" title="Foreword"><link rel="next" href="ExNetworks.html" title="Part�I.�Example Network Configurations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr03.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ExNetworks.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="preface"></a>Preface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="preface.html#id2501240">Why Is This Book Necessary?</a></span></dt><dd><dl><dt><span class="sect2"><a href="preface.html#id2498964">Samba 3.0.20 Update Edition</a></span></dt></dl></dd><dt><span class="sect1"><a href="preface.html#id2498848">Prerequisites</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498880">Approach</a></span></dt><dt><span class="sect1"><a href="preface.html#id2498945">Summary of Topics</a></span></dt><dt><span class="sect1"><a href="preface.html#id2550640">Conventions Used</a></span></dt></dl></div><p>
 	Network administrators live busy lives. We face distractions and pressures
 	that drive us to seek proven, working case scenarios that can be easily
 	implemented. Often this approach lands us in trouble. There is a 
@@ -33,7 +33,7 @@
 	detailed information regarding secure operation and configuration of peripheral
 	services and applications such as OpenLDAP, DNS and DHCP, the need for which
 	can be met from other resources that are dedicated to the subject.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2501251"></a>Why Is This Book Necessary?</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2501240"></a>Why Is This Book Necessary?</h2></div></div></div><p>
 	This book is the result of observations and feedback. The feedback from
 	the Samba-HOWTO-Collection has been positive and complimentary. There
 	have been requests for far more worked examples, a
@@ -53,7 +53,7 @@
 	All example case configuration files, scripts, and other tools are provided
 	on the CD-ROM. This book is descriptive, provides detailed diagrams, and
 	makes deployment of Samba-3 a breeze.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2498970"></a>Samba 3.0.20 Update Edition</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2498964"></a>Samba 3.0.20 Update Edition</h3></div></div></div><p>
 	The Samba 3.0.x series has been remarkably popular. At the time this book first
 	went to print samba-3.0.2 was being released. There have been significant modifications
 	and enhancements between samba-3.0.2 and samba-3.0.14 (the current release) that
@@ -126,7 +126,7 @@
 						means that functions such as adding machines to the domain, managing printers, etc. can now
 						be delegated to normal user accounts or to groups of users.
 						</p>
-					</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498857"></a>Prerequisites</h2></div></div></div><p>
+					</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498848"></a>Prerequisites</h2></div></div></div><p>
 	This book is not a tutorial on UNIX or Linux administration. UNIX and Linux
 	training is best obtained from books dedicated to the subject. This book
 	assumes that you have at least the basic skill necessary to use these operating
@@ -139,7 +139,7 @@
 	find yourself at times intimidated by assumptions made. In this situation, you
 	may need to refer to administrative guides or manuals for your operating system
 	platform to find what is the best method to achieve what the text of this book describes.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498889"></a>Approach</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498880"></a>Approach</h2></div></div></div><p>
 	The first chapter deals with some rather thorny network analysis issues. Do not be
 	put off by this. The information you glean, even without a detailed understanding
 	of network protocol analysis, can help you understand how Windows networking functions.
@@ -167,7 +167,7 @@
 	</p><p>
 	Each chapter has a set of questions and answers to help you to
 	to understand and digest key attributes of the solutions presented.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498954"></a>Summary of Topics</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498945"></a>Summary of Topics</h2></div></div></div><p>
 	The contents of this second edition of <span class="emphasis"><em>Samba-3 by Example</em></span>
 	have been rearranged based on feedback from purchasers of the first edition.
 	</p><p>
@@ -364,7 +364,7 @@
 		have seen some of the information a Windows client sends to
 		a file and print server to create a connection over which file and print
 		operations may take place.
-		</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550647"></a>Conventions Used</h2></div></div></div><p>
+		</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550640"></a>Conventions Used</h2></div></div></div><p>
     The following notation conventions are used throughout this book:
     </p><div class="itemizedlist"><ul type="disc"><li><p>
 	TOSHARG2 is used as an abbreviation for the book, &#8220;<span class="quote">The Official Samba-3
diff --git a/docs/htmldocs/Samba3-ByExample/primer.html b/docs/htmldocs/Samba3-ByExample/primer.html
index 85bb76a6a2..e407e327b7 100644
--- a/docs/htmldocs/Samba3-ByExample/primer.html
+++ b/docs/htmldocs/Samba3-ByExample/primer.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�Networking Primer</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits"><link rel="next" href="apa.html" title="Appendix�A.� GNU General Public License version 3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�Networking Primer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="appendix.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="primer"></a>Chapter�16.�Networking Primer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="primer.html#id2625280">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625441">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625502">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625618">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625744">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2626892">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627394">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627962">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628077">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�Networking Primer</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part�III.�Reference Section"><link rel="prev" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits"><link rel="next" href="apa.html" title="Appendix�A.� GNU General Public License version 3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�Networking Primer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="appendix.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="primer"></a>Chapter�16.�Networking Primer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="primer.html#id2625404">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625565">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625625">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625742">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625868">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627015">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627518">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2628086">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628200">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></div><p>
 	You are about to use the equivalent of a microscope to look at the information
 	that runs through the veins of a Windows network. We do more to observe the information than
 	to interrogate it. When you are done with this primer, you should have a good understanding
@@ -8,7 +8,7 @@
 	</p><p>
 	Samba can be configured with a minimum of complexity. Simplicity should be mastered
 	before you get too deeply into complexities. Let's get moving: we have work to do.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625280"></a>Requirements and Notes</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625404"></a>Requirements and Notes</h2></div></div></div><p>
 	Successful completion of this primer requires two Microsoft Windows 9x/Me Workstations
 	as well as two Microsoft Windows XP Professional Workstations, each equipped with an Ethernet
 	card connected using a hub. Also required is one additional server (either Windows
@@ -16,7 +16,7 @@
 	sniffer and analysis application (Wireshark is a good choice). All work should be undertaken
 	on a quiet network where there is no other traffic. It is best to use a dedicated hub
 	with only the machines under test connected at the time of the exercises.
-	</p><p><a class="indexterm" name="id2625300"></a>
+	</p><p><a class="indexterm" name="id2625424"></a>
 	Wireshark (formerly Ethereal) has become the network protocol analyzer of choice for many network administrators.
 	You may find more information regarding this tool from the
 	<a class="ulink" href="http://www.wireshark.org" target="_top">Wireshark</a> Web site. Wireshark installation
@@ -36,11 +36,11 @@
 	filter. Ethernet switches may filter out traffic that is not directed at the machine
 	that is used to monitor traffic; this would not allow you to complete the projects.
 	</p></div><p>
-	<a class="indexterm" name="id2625370"></a>
+	<a class="indexterm" name="id2625494"></a>
 	Do not worry too much if you do not have access to all this equipment; network captures
 	from the exercises are provided on the enclosed CD-ROM. This makes it possible to dive directly
 	into the analytical part of the exercises if you so desire.
-	</p><p><a class="indexterm" name="id2625386"></a><a class="indexterm" name="id2625397"></a>
+	</p><p><a class="indexterm" name="id2625509"></a><a class="indexterm" name="id2625521"></a>
 	Please do not be alarmed at the use of a high-powered analysis tool (Wireshark) in this
 	primer.  We expose you only to a minimum of detail necessary to complete
 	the exercises. If you choose to use any other network sniffer and protocol
@@ -54,11 +54,11 @@
 	</p><p>
 	<a class="link" href="primer.html#chap01qa" title="Questions and Answers">&#8220;Questions and Answers&#8221;</a> also provides useful information
 	that may help you to avoid significantly time-consuming networking problems.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625441"></a>Introduction</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625565"></a>Introduction</h2></div></div></div><p>
 	The purpose of this chapter is to create familiarity with key aspects of Microsoft Windows
 	network computing. If you want a solid technical grounding, do not gloss over these exercises.
 	The points covered are recurrent issues on the Samba mailing lists.
-	</p><p><a class="indexterm" name="id2625456"></a>
+	</p><p><a class="indexterm" name="id2625579"></a>
 	You can see from these exercises that Windows networking involves quite a lot of network
 	broadcast traffic. You can look into the contents of some packets, but only to see
 	some particular information that the Windows client sends to a server in the course of
@@ -74,18 +74,18 @@
 	Recommended preparatory reading: <span class="emphasis"><em>The Official Samba-3 HOWTO and Reference Guide, Second
 	Edition</em></span> (TOSHARG2) Chapter 9, &#8220;<span class="quote">Network Browsing,</span>&#8221; and Chapter 3,
 	&#8220;<span class="quote">Server Types and Security Modes.</span>&#8221;
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625502"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2625508"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625625"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2625632"></a>
 		You are about to witness how Microsoft Windows computer networking functions. The
 		exercises step through identification of how a client machine establishes a
 		connection to a remote Windows server. You observe how Windows machines find
 		each other (i.e., how browsing works) and how the two key types of user identification
 		(share mode security and user mode security) are affected.
-		</p><p><a class="indexterm" name="id2625526"></a>
+		</p><p><a class="indexterm" name="id2625650"></a>
 		The networking protocols used by MS Windows networking when working with Samba
 		use TCP/IP as the transport protocol. The protocols that are specific to Windows
 		networking are encapsulated in TCP/IP. The network analyzer we use (Wireshark)
 		is able to show you the contents of the TCP/IP packets (or messages).
-		</p><div class="procedure"><a name="chap01tasks"></a><p class="title"><b>Procedure�16.1.�Diagnostic Tasks</b></p><ol type="1"><li><p><a class="indexterm" name="id2625559"></a><a class="indexterm" name="id2625570"></a><a class="indexterm" name="id2625578"></a>
+		</p><div class="procedure"><a name="chap01tasks"></a><p class="title"><b>Procedure�16.1.�Diagnostic Tasks</b></p><ol type="1"><li><p><a class="indexterm" name="id2625682"></a><a class="indexterm" name="id2625694"></a><a class="indexterm" name="id2625702"></a>
 			Examine network traces to witness SMB broadcasts, host announcements,
 			and name resolution processes.
 			</p></li><li><p>
@@ -95,8 +95,8 @@
 			</p></li><li><p>
 			Review traces of network logons for a Windows 9x/Me client as well as
 			a domain logon for a Windows XP Professional client.
-			</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625618"></a>Exercises</h2></div></div></div><p>
-	<a class="indexterm" name="id2625626"></a>
+			</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625742"></a>Exercises</h2></div></div></div><p>
+	<a class="indexterm" name="id2625750"></a>
 	You are embarking on a course of discovery. The first part of the exercise requires
 	two MS Windows 9x/Me systems. We called one machine <code class="constant">WINEPRESSME</code> and the
 	other <code class="constant">MILGATE98</code>. Each needs an IP address; we used <code class="literal">10.1.1.10</code>
@@ -111,7 +111,7 @@
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Windows 98  name: MILGATE98</p></li><li><p>Windows Me  name: WINEPRESSME</p></li><li><p>Windows XP Professional  name: LightrayXP</p></li><li><p>Samba-3.0.20 running on a SUSE Enterprise Linux 9</p></li></ul></div><p>
 	Choose a workgroup name (MIDEARTH) for each exercise.
 	</p><p>
-	<a class="indexterm" name="id2625715"></a>
+	<a class="indexterm" name="id2625839"></a>
 	The network captures provided on the CD-ROM included with this book were captured using <code class="constant">Ethereal</code>
 	version <code class="literal">0.10.6</code>. A later version suffices without problems (i.e. you should be using Wireshark), but an earlier version may not
 	expose all the information needed. Each capture file has been decoded and listed as a trace file. A summary of all
@@ -119,9 +119,9 @@
 	perform the time-consuming equipment configuration and test work. This is a good time to point out that the value
 	that can be derived from this book really does warrant your taking sufficient time to practice each exercise with
 	care and attention to detail.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625744"></a>Single-Machine Broadcast Activity</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625868"></a>Single-Machine Broadcast Activity</h3></div></div></div><p>
 	In this section, we start a single Windows 9x/Me machine, then monitor network activity for 30 minutes.
-	</p><div class="procedure"><a name="id2625755"></a><p class="title"><b>Procedure�16.2.�Monitoring Windows 9x Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2625879"></a><p class="title"><b>Procedure�16.2.�Monitoring Windows 9x Steps</b></p><ol type="1"><li><p>
 		Start the machine from which network activity will be monitored (using <code class="literal">Wireshark</code>).
 		Launch <code class="literal">Wireshark</code>, click
 			<span class="guimenu">Capture</span> &#8594; <span class="guimenuitem">Start</span>.
@@ -138,28 +138,28 @@
 		</p></li><li><p>
 		Analyze the capture. Identify each discrete message type that was captured. Note what transport protocol
 		was used. Identify the timing between messages of identical types.
-		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625878"></a>Findings</h4></div></div></div><p>
+		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2626002"></a>Findings</h4></div></div></div><p>
 		The summary of the first 10 minutes of the packet capture should look like <a class="link" href="primer.html#pktcap01" title="Figure�16.1.�Windows Me Broadcasts The First 10 Minutes">&#8220;Windows Me  Broadcasts  The First 10 Minutes&#8221;</a>.
 		A screenshot of a later stage of the same capture is shown in <a class="link" href="primer.html#pktcap02" title="Figure�16.2.�Windows Me Later Broadcast Sample">&#8220;Windows Me  Later Broadcast Sample&#8221;</a>.
-		</p><div class="figure"><a name="pktcap01"></a><p class="title"><b>Figure�16.1.�Windows Me  Broadcasts  The First 10 Minutes</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture.png" width="216" alt="Windows Me Broadcasts The First 10 Minutes"></div></div></div><br class="figure-break"><div class="figure"><a name="pktcap02"></a><p class="title"><b>Figure�16.2.�Windows Me  Later Broadcast Sample</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture2.png" width="226.8" alt="Windows Me Later Broadcast Sample"></div></div></div><br class="figure-break"><p><a class="indexterm" name="id2625995"></a><a class="indexterm" name="id2626006"></a>
+		</p><div class="figure"><a name="pktcap01"></a><p class="title"><b>Figure�16.1.�Windows Me  Broadcasts  The First 10 Minutes</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture.png" width="216" alt="Windows Me Broadcasts The First 10 Minutes"></div></div></div><br class="figure-break"><div class="figure"><a name="pktcap02"></a><p class="title"><b>Figure�16.2.�Windows Me  Later Broadcast Sample</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture2.png" width="226.8" alt="Windows Me Later Broadcast Sample"></div></div></div><br class="figure-break"><p><a class="indexterm" name="id2626119"></a><a class="indexterm" name="id2626130"></a>
 		Broadcast messages observed are shown in <a class="link" href="primer.html#capsstats01" title="Table�16.1.�Windows Me Startup Broadcast Capture Statistics">&#8220;Windows Me  Startup Broadcast Capture Statistics&#8221;</a>.
 		Actual observations vary a little, but not by much.
 		Early in the startup process, the Windows Me machine broadcasts its name for two reasons:
 		first to ensure that its name would not result in a name clash, and second to establish its
 		presence with the Local Master Browser (LMB).
-		</p><div class="table"><a name="capsstats01"></a><p class="title"><b>Table�16.1.�Windows Me  Startup Broadcast Capture Statistics</b></p><div class="table-contents"><table summary="Windows Me  Startup Broadcast Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">WINEPRESSME&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME&lt;03&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME&lt;20&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1d&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1e&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1b&gt;</td><td align="center">Qry</td><td align="center">84</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">__MSBROWSE__</td><td align="center">Reg</td><td align="center">8</td><td align="left">Registered after winning election to Browse Master</td></tr><tr><td align="left">JHT&lt;03&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 x 2. This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">2</td><td align="left">Observed at 10 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Get Backup List Request</td><td align="center">Qry</td><td align="center">12</td><td align="left">6 x 2 early in startup, 0.5 sec apart</td></tr><tr><td align="left">Browser Election Request</td><td align="center">Ann</td><td align="center">10</td><td align="left">5 x 2 early in startup</td></tr><tr><td align="left">Request Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">4</td><td align="left">Early in startup</td></tr></tbody></table></div></div><br class="table-break"><p><a class="indexterm" name="id2626353"></a><a class="indexterm" name="id2626361"></a>
+		</p><div class="table"><a name="capsstats01"></a><p class="title"><b>Table�16.1.�Windows Me  Startup Broadcast Capture Statistics</b></p><div class="table-contents"><table summary="Windows Me  Startup Broadcast Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">WINEPRESSME&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME&lt;03&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME&lt;20&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1d&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1e&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1b&gt;</td><td align="center">Qry</td><td align="center">84</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">__MSBROWSE__</td><td align="center">Reg</td><td align="center">8</td><td align="left">Registered after winning election to Browse Master</td></tr><tr><td align="left">JHT&lt;03&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 x 2. This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">2</td><td align="left">Observed at 10 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Get Backup List Request</td><td align="center">Qry</td><td align="center">12</td><td align="left">6 x 2 early in startup, 0.5 sec apart</td></tr><tr><td align="left">Browser Election Request</td><td align="center">Ann</td><td align="center">10</td><td align="left">5 x 2 early in startup</td></tr><tr><td align="left">Request Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">4</td><td align="left">Early in startup</td></tr></tbody></table></div></div><br class="table-break"><p><a class="indexterm" name="id2626477"></a><a class="indexterm" name="id2626485"></a>
 		From the packet trace, it should be noted that no messages were propagated over TCP/IP;
 		all messages employed UDP/IP.  When steady-state operation has been achieved, there is a cycle
 		of various announcements, re-election of a browse master, and name queries. These create
 		the symphony of announcements by which network browsing is made possible.
-		</p><p><a class="indexterm" name="id2626379"></a>
+		</p><p><a class="indexterm" name="id2626502"></a>
 		For detailed information regarding the precise behavior of the CIFS/SMB protocols,
 		refer to the book &#8220;<span class="quote">Implementing CIFS: The Common Internet File System,</span>&#8221;
 		by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X).
 		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="secondmachine"></a>Second Machine Startup Broadcast Interaction</h3></div></div></div><p>
 	At this time, the machine you used to capture the single-system startup trace should still be running.
 	The objective of this task is to identify the interaction of two machines in respect to broadcast activity.
-	</p><div class="procedure"><a name="id2626415"></a><p class="title"><b>Procedure�16.3.�Monitoring of Second Machine Activity</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2626538"></a><p class="title"><b>Procedure�16.3.�Monitoring of Second Machine Activity</b></p><ol type="1"><li><p>
 		On the machine from which network activity will be monitored (using <code class="literal">Wireshark</code>),
 		launch <code class="literal">Wireshark</code> and click
 			<span class="guimenu">Capture</span> &#8594; <span class="guimenuitem">Start</span>.
@@ -176,7 +176,7 @@
 		</p></li><li><p>
 		Analyze the capture trace, taking note of the transport protocols used, the types of messages observed,
 		and what interaction took place between the two machines. Leave both machines running for the next task.
-		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2626531"></a>Findings</h4></div></div></div><p>
+		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2626655"></a>Findings</h4></div></div></div><p>
 		<a class="link" href="primer.html#capsstats02" title="Table�16.2.�Second Machine (Windows 98) Capture Statistics">&#8220;Second Machine (Windows 98)  Capture Statistics&#8221;</a> summarizes capture statistics observed. As in the previous case,
 		all announcements used UDP/IP broadcasts. Also, as was observed with the last example, the second
 		Windows 9x/Me machine broadcasts its name on startup to ensure that there exists no name clash
@@ -184,18 +184,18 @@
 		to explore the inner details of the precise mechanism of how this functions should refer to
 		&#8220;<span class="quote">Implementing CIFS: The Common Internet File System.</span>&#8221;
 		</p><div class="table"><a name="capsstats02"></a><p class="title"><b>Table�16.2.�Second Machine (Windows 98)  Capture Statistics</b></p><div class="table-contents"><table summary="Second Machine (Windows 98)  Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">MILGATE98&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">MILGATE98&lt;03&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">MILGATE98&lt;20&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;00&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1d&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1e&gt;</td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH&lt;1b&gt;</td><td align="center">Qry</td><td align="center">18</td><td align="left">900 sec apart at stable operation</td></tr><tr><td align="left">JHT&lt;03&gt;</td><td align="center">Reg</td><td align="center">2</td><td align="left">This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement MILGATE98</td><td align="center">Ann</td><td align="center">14</td><td align="left">Every 120 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">6</td><td align="left">900 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">6</td><td align="left">Insufficient detail to determine frequency</td></tr></tbody></table></div></div><br class="table-break"><p>
-	    	<a class="indexterm" name="id2626813"></a>
-		<a class="indexterm" name="id2626820"></a>
-		<a class="indexterm" name="id2626827"></a>
+	    	<a class="indexterm" name="id2626937"></a>
+		<a class="indexterm" name="id2626944"></a>
+		<a class="indexterm" name="id2626951"></a>
 		Observation of the contents of Host Announcements, Domain/Workgroup Announcements,
 		and Local Master Announcements is instructive. These messages convey a significant
 		level of detail regarding the nature of each machine that is on the network. An example
 		dissection of a Host Announcement is given in <a class="link" href="primer.html#hostannounce" title="Figure�16.3.�Typical Windows 9x/Me Host Announcement">&#8220;Typical Windows 9x/Me Host Announcement&#8221;</a>.
-		</p><div class="figure"><a name="hostannounce"></a><p class="title"><b>Figure�16.3.�Typical Windows 9x/Me Host Announcement</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HostAnnouncment.png" width="221.4" alt="Typical Windows 9x/Me Host Announcement"></div></div></div><br class="figure-break"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626892"></a>Simple Windows Client Connection Characteristics</h3></div></div></div><p>
+		</p><div class="figure"><a name="hostannounce"></a><p class="title"><b>Figure�16.3.�Typical Windows 9x/Me Host Announcement</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HostAnnouncment.png" width="221.4" alt="Typical Windows 9x/Me Host Announcement"></div></div></div><br class="figure-break"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627015"></a>Simple Windows Client Connection Characteristics</h3></div></div></div><p>
 	The purpose of this exercise is to discover how Microsoft Windows clients create (establish)
 	connections with remote servers. The methodology involves analysis of a key aspect of how
 	Windows clients access remote servers: the session setup protocol.
-	</p><div class="procedure"><a name="id2626906"></a><p class="title"><b>Procedure�16.4.�Client Connection Exploration Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2627029"></a><p class="title"><b>Procedure�16.4.�Client Connection Exploration Steps</b></p><ol type="1"><li><p>
 		Configure a Windows 9x/Me machine (MILGATE98) with a share called <code class="constant">Stuff</code>.
 		Create a <em class="parameter"><code>Full Access</code></em> control password on this share.
 		</p></li><li><p>
@@ -216,11 +216,11 @@
 		When the share called <code class="constant">Stuff</code> is being displayed, stop the capture.
 		Save the captured data in case it is needed for later analysis.
 		</p></li><li><p>
-		<a class="indexterm" name="id2627037"></a>
+		<a class="indexterm" name="id2627160"></a>
 		From the top of the packets captured, scan down to locate the first packet that has
 		interpreted as <code class="constant">Session Setup AndX, User: anonymous; Tree Connect AndX,
 		Path: \\MILGATE98\IPC$</code>.
-		</p></li><li><p><a class="indexterm" name="id2627056"></a><a class="indexterm" name="id2627064"></a>
+		</p></li><li><p><a class="indexterm" name="id2627179"></a><a class="indexterm" name="id2627187"></a>
 		In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request,
 		and Tree Connect AndX Request</code>. Examine both operations. Identify the name of
 		the user Account and what password was used. The Account name should be empty.
@@ -230,29 +230,29 @@
 		decoded of the type <code class="constant">Session Setup AndX</code>. Locate the last such packet
 		that was targeted at the <code class="constant">\\MILGATE98\IPC$</code> service.
 		</p></li><li><p>
-		<a class="indexterm" name="id2627108"></a>
-		<a class="indexterm" name="id2627115"></a>
+		<a class="indexterm" name="id2627232"></a>
+		<a class="indexterm" name="id2627239"></a>
 		Dissect this packet as per the previous one. This packet should have a password length
 		of 24 (characters) and should have a password field, the contents of which is a
 		long hexadecimal number. Observe the name in the Account field. This is a User Mode
 		session setup packet.
-		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2627129"></a>Findings and Comments</h4></div></div></div><p>
-		<a class="indexterm" name="id2627138"></a>
-		The <code class="constant">IPC$</code> share serves a vital purpose<sup>[<a name="id2627149" href="#ftn.id2627149" class="footnote">15</a>]</sup>
+		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2627253"></a>Findings and Comments</h4></div></div></div><p>
+		<a class="indexterm" name="id2627261"></a>
+		The <code class="constant">IPC$</code> share serves a vital purpose<sup>[<a name="id2627272" href="#ftn.id2627272" class="footnote">15</a>]</sup>
 		in SMB/CIFS-based networking.  A Windows client connects to this resource to obtain the list of
 		resources that are available on the server. The server responds with the shares and print queues that
 		are available. In most but not all cases, the connection is made with a <code class="constant">NULL</code>
 		username and a <code class="constant">NULL</code> password.
 		</p><p>
-		<a class="indexterm" name="id2627169"></a>
+		<a class="indexterm" name="id2627293"></a>
 		The two packets examined are material evidence of how Windows clients may
 		interoperate with Samba. Samba requires every connection setup to be authenticated using
 		valid UNIX account credentials (UID/GID). This means that even a <code class="constant">NULL</code>
 		session setup can be established only by automatically mapping it to a valid UNIX
 		account.
 		</p><p>
-	    <a class="indexterm" name="id2627189"></a><a class="indexterm" name="id2627195"></a>
-	    <a class="indexterm" name="id2627204"></a>
+	    <a class="indexterm" name="id2627312"></a><a class="indexterm" name="id2627318"></a>
+	    <a class="indexterm" name="id2627327"></a>
 		Samba has a special name for the <code class="constant">NULL</code>, or empty, user account:
 		it calls it the <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a>. The
 		default value of this parameter is <code class="constant">nobody</code>; however, this can be
@@ -261,9 +261,9 @@
 		FTP account. A sample NULL Session Setup AndX packet dissection is shown in
 		<a class="link" href="primer.html#nullconnect" title="Figure�16.4.�Typical Windows 9x/Me NULL SessionSetUp AndX Request">&#8220;Typical Windows 9x/Me NULL SessionSetUp AndX Request&#8221;</a>.
 		</p><div class="figure"><a name="nullconnect"></a><p class="title"><b>Figure�16.4.�Typical Windows 9x/Me NULL SessionSetUp AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/NullConnect.png" width="221.4" alt="Typical Windows 9x/Me NULL SessionSetUp AndX Request"></div></div></div><br class="figure-break"><p>
-	    	<a class="indexterm" name="id2627289"></a>
-		<a class="indexterm" name="id2627296"></a>
-		<a class="indexterm" name="id2627303"></a>
+	    	<a class="indexterm" name="id2627413"></a>
+		<a class="indexterm" name="id2627419"></a>
+		<a class="indexterm" name="id2627426"></a>
 		When a UNIX/Linux system does not have a <code class="constant">nobody</code> user account
 		(<code class="filename">/etc/passwd</code>), the operation of the <code class="constant">NULL</code>
 		account cannot validate and thus connections that utilize the guest account
@@ -271,11 +271,11 @@
 		problem reported on the Samba mailing list. A sample User Mode session setup AndX
 		is shown in <a class="link" href="primer.html#userconnect" title="Figure�16.5.�Typical Windows 9x/Me User SessionSetUp AndX Request">&#8220;Typical Windows 9x/Me User SessionSetUp AndX Request&#8221;</a>.
 		</p><div class="figure"><a name="userconnect"></a><p class="title"><b>Figure�16.5.�Typical Windows 9x/Me User SessionSetUp AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/UserConnect.png" width="221.4" alt="Typical Windows 9x/Me User SessionSetUp AndX Request"></div></div></div><br class="figure-break"><p>
-		<a class="indexterm" name="id2627380"></a>
+		<a class="indexterm" name="id2627504"></a>
 		The User Mode connection packet contains the account name and the domain name.
 		The password is provided in Microsoft encrypted form, and its length is shown
 		as 24 characters. This is the length of Microsoft encrypted passwords.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627394"></a>Windows 200x/XP Client Interaction with Samba-3</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627518"></a>Windows 200x/XP Client Interaction with Samba-3</h3></div></div></div><p>
 	By now you may be asking, &#8220;<span class="quote">Why did you choose to work with Windows 9x/Me?</span>&#8221;
 	</p><p>
 	First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise
@@ -290,7 +290,7 @@
 	To complete this exercise, you need a Windows XP Professional client that has been configured as
 	a domain member of either a Samba-controlled domain or a Windows NT4 or 200x Active Directory domain.
 	Here we do not provide details for how to configure this, as full coverage is provided earlier in this book.
-	</p><div class="procedure"><a name="id2627437"></a><p class="title"><b>Procedure�16.5.�Steps to Explore Windows XP Pro Connection Set-up</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2627560"></a><p class="title"><b>Procedure�16.5.�Steps to Explore Windows XP Pro Connection Set-up</b></p><ol type="1"><li><p>
 		Start your domain controller. Also, start the Wireshark monitoring machine, launch Wireshark,
 		and then wait for the next step to complete.
 		</p></li><li><p>
@@ -319,14 +319,14 @@
 		If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises
 		in this chapter.
 		</p></li><li><p>
-		<a class="indexterm" name="id2627663"></a>
-                <a class="indexterm" name="id2627670"></a>
+		<a class="indexterm" name="id2627786"></a>
+                <a class="indexterm" name="id2627793"></a>
                 From the top of the packets captured, scan down to locate the first packet that has
                 interpreted as <code class="constant">Session Setup AndX Request, NTLMSSP_AUTH</code>.
                 </p></li><li><p>
-		<a class="indexterm" name="id2627690"></a>
-		<a class="indexterm" name="id2627697"></a>
-		<a class="indexterm" name="id2627704"></a>
+		<a class="indexterm" name="id2627814"></a>
+		<a class="indexterm" name="id2627820"></a>
+		<a class="indexterm" name="id2627827"></a>
                 In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request</code>.
 		Expand the packet decode information, beginning at the <code class="constant">Security Blob:</code>
 		entry. Expand the <code class="constant">GSS-API -&gt; SPNEGO -&gt; netTokenTarg -&gt; responseToken -&gt; NTLMSSP</code>
@@ -338,7 +338,7 @@
                 decoded of the type <code class="constant">Session Setup AndX Request</code>. Click the last such packet that
 		has been decoded as <code class="constant">Session Setup AndX Request, NTLMSSP_AUTH</code>.
                 </p></li><li><p>
-		<a class="indexterm" name="id2627766"></a>
+		<a class="indexterm" name="id2627890"></a>
                 In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request</code>.
                 Expand the packet decode information, beginning at the <code class="constant">Security Blob:</code>
                 entry. Expand the <code class="constant">GSS-API -&gt; SPNEGO -&gt; netTokenTarg -&gt; responseToken -&gt; NTLMSSP</code>
@@ -349,18 +349,18 @@
 		The values of these two parameters are the Microsoft encrypted password hashes: respectively, the LanMan
 		password and then the NT (case-preserving) password hash.
                 </p></li><li><p>
-                <a class="indexterm" name="id2627828"></a>
-                <a class="indexterm" name="id2627835"></a>
+                <a class="indexterm" name="id2627951"></a>
+                <a class="indexterm" name="id2627958"></a>
                 The passwords are 24-character hexadecimal numbers. This packet confirms that this is a User Mode
 		session setup packet.
-                </p></li></ol></div><div class="figure"><a name="XPCap01"></a><p class="title"><b>Figure�16.6.�Typical Windows XP NULL Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-NullConnection.png" width="270" alt="Typical Windows XP NULL Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="figure"><a name="XPCap02"></a><p class="title"><b>Figure�16.7.�Typical Windows XP User Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-UserConnection.png" width="270" alt="Typical Windows XP User Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2627931"></a>Discussion</h4></div></div></div><p><a class="indexterm" name="id2627938"></a>
+                </p></li></ol></div><div class="figure"><a name="XPCap01"></a><p class="title"><b>Figure�16.6.�Typical Windows XP NULL Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-NullConnection.png" width="270" alt="Typical Windows XP NULL Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="figure"><a name="XPCap02"></a><p class="title"><b>Figure�16.7.�Typical Windows XP User Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-UserConnection.png" width="270" alt="Typical Windows XP User Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628054"></a>Discussion</h4></div></div></div><p><a class="indexterm" name="id2628061"></a>
 		This exercise demonstrates that, while the specific protocol for the Session Setup AndX is handled
 		in a more sophisticated manner by recent MS Windows clients, the underlying rules or principles
 		remain the same. Thus it is demonstrated  that MS Windows XP Professional clients still use a
 		<code class="constant">NULL-Session</code> connection to query and locate resources on an advanced network
 		technology server (one using Windows NT4/200x or Samba). It also demonstrates that an authenticated
 		connection must be made before resources can be used.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627962"></a>Conclusions to Exercises</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2628086"></a>Conclusions to Exercises</h3></div></div></div><p>
 	In summary, the following points have been established in this chapter:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 		When NetBIOS over TCP/IP protocols are enabled, MS Windows networking employs broadcast-oriented messaging protocols to provide knowledge of network services.
@@ -379,7 +379,7 @@
 		file or in an LDAP database. Samba-3 permits use of multiple <em class="parameter"><code>passdb backend</code></em>
 		databases in concurrent deployment. Refer to <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 10, &#8220;<span class="quote">Account Information Databases.</span>&#8221;
 		</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap01conc"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2628050"></a>
+	<a class="indexterm" name="id2628173"></a>
 	The exercises demonstrate the use of the <code class="constant">guest</code> account, the way that
 	MS Windows clients and servers resolve computer names to a TCP/IP address, and how connections
 	between a client and a server are established.
@@ -387,8 +387,8 @@
 	Those wishing background information regarding NetBIOS name types should refer to
 	the Microsoft knowledgebase article
 	<a class="ulink" href="http://support.microsoft.com/support/kb/articles/Q102/78/8.asp" target="_top">Q102878.</a>
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2628077"></a>Technical Issues</h3></div></div></div><p>
-		<a class="indexterm" name="id2628085"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2628200"></a>Technical Issues</h3></div></div></div><p>
+		<a class="indexterm" name="id2628208"></a>
 		Network browsing involves SMB broadcast announcements, SMB enumeration requests,
 		connections to the <code class="constant">IPC$</code> share, share enumerations, and SMB connection
 		setup processes. The use of anonymous connections to a Samba server involve the use of
@@ -396,44 +396,44 @@
 		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap01qa"></a>Questions and Answers</h2></div></div></div><p>
 	The questions and answers given in this section are designed to highlight important aspects of Microsoft
 	Windows networking.
-	</p><div class="qandaset"><dl><dt> <a href="primer.html#id2628131">
+	</p><div class="qandaset"><dl><dt> <a href="primer.html#id2628254">
 		What is the significance of the MIDEARTH&lt;1b&gt; type query?
-		</a></dt><dt> <a href="primer.html#id2628177">
+		</a></dt><dt> <a href="primer.html#id2628301">
 		What is the significance of the MIDEARTH&lt;1d&gt; type name registration?
-		</a></dt><dt> <a href="primer.html#id2628251">
+		</a></dt><dt> <a href="primer.html#id2628375">
 		What is the role and significance of the &lt;01&gt;&lt;02&gt;__MSBROWSE__&lt;02&gt;&lt;01&gt;
 		name registration?
-                </a></dt><dt> <a href="primer.html#id2628284">
+                </a></dt><dt> <a href="primer.html#id2628408">
 		What is the significance of the MIDEARTH&lt;1e&gt; type name registration?
-		</a></dt><dt> <a href="primer.html#id2628315">
+		</a></dt><dt> <a href="primer.html#id2628438">
 		
 		What is the significance of the guest account in smb.conf?
-		</a></dt><dt> <a href="primer.html#id2628393">
+		</a></dt><dt> <a href="primer.html#id2628516">
 		Is it possible to reduce network broadcast activity with Samba-3?
-		</a></dt><dt> <a href="primer.html#id2628502">
+		</a></dt><dt> <a href="primer.html#id2628625">
 		Can I just use plain-text passwords with Samba?
-		</a></dt><dt> <a href="primer.html#id2628589">
+		</a></dt><dt> <a href="primer.html#id2628712">
 		What parameter in the smb.conf file is used to enable the use of encrypted passwords?
-		</a></dt><dt> <a href="primer.html#id2628630">
+		</a></dt><dt> <a href="primer.html#id2628754">
 		Is it necessary to specify encrypt passwords = Yes
 		when Samba-3 is configured as a domain member?
-		</a></dt><dt> <a href="primer.html#id2628662">
+		</a></dt><dt> <a href="primer.html#id2628785">
 		Is it necessary to specify a guest account when Samba-3 is configured
 		as a domain member server?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2628131"></a><a name="id2628133"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2628254"></a><a name="id2628257"></a></td><td align="left" valign="top"><p>
 		What is the significance of the MIDEARTH&lt;1b&gt; type query?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628145"></a>
-		<a class="indexterm" name="id2628155"></a>
+		<a class="indexterm" name="id2628269"></a>
+		<a class="indexterm" name="id2628278"></a>
 		This is a broadcast announcement by which the Windows machine is attempting to
 		locate a Domain Master Browser (DMB) in the event that it might exist on the network.
 		Refer to <span class="emphasis"><em>TOSHARG2,</em></span> Chapter 9, Section 9.7, &#8220;<span class="quote">Technical Overview of Browsing,</span>&#8221;
 		for details regarding the function of the DMB and its role in network browsing.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628177"></a><a name="id2628179"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628301"></a><a name="id2628303"></a></td><td align="left" valign="top"><p>
 		What is the significance of the MIDEARTH&lt;1d&gt; type name registration?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628192"></a>
-		<a class="indexterm" name="id2628201"></a>
+		<a class="indexterm" name="id2628315"></a>
+		<a class="indexterm" name="id2628324"></a>
 		This name registration records the machine IP addresses of the LMBs.
 		Network clients can query this name type to obtain a list of browser servers from the
 		master browser.
@@ -451,25 +451,25 @@
 			The IP address of the DMB (if one exists)
 			</p></li><li><p>
 			The IP address of the LMB on the local segment
-			</p></li></ul></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628251"></a><a name="id2628254"></a></td><td align="left" valign="top"><p>
+			</p></li></ul></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628375"></a><a name="id2628377"></a></td><td align="left" valign="top"><p>
 		What is the role and significance of the &lt;01&gt;&lt;02&gt;__MSBROWSE__&lt;02&gt;&lt;01&gt;
 		name registration?
                 </p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628269"></a>
+		<a class="indexterm" name="id2628392"></a>
 		This name is registered by the browse master to broadcast and receive domain announcements.
 		Its scope is limited to the local network segment, or subnet. By querying this name type,
 		master browsers on networks that have multiple domains can find the names of master browsers
 		for each domain.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628284"></a><a name="id2628286"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628408"></a><a name="id2628410"></a></td><td align="left" valign="top"><p>
 		What is the significance of the MIDEARTH&lt;1e&gt; type name registration?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628298"></a>
+		<a class="indexterm" name="id2628422"></a>
 		This name is registered by all browse masters in a domain or workgroup. The registration
 		name type is known as the Browser Election Service. Master browsers register themselves
 		with this name type so that DMBs can locate them to perform cross-subnet
 		browse list updates. This name type is also used to initiate elections for Master Browsers.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628315"></a><a name="id2628317"></a></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628321"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628438"></a><a name="id2628440"></a></td><td align="left" valign="top"><p>
+		<a class="indexterm" name="id2628445"></a>
 		What is the significance of the <em class="parameter"><code>guest account</code></em> in smb.conf?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		This parameter specifies the default UNIX account to which MS Windows networking
@@ -482,19 +482,19 @@
 		Samba operation. Either the operating system must have an account called <code class="constant">nobody</code>
 		or there must be an entry in the <code class="filename">smb.conf</code> file with a valid UNIX account, such as
 		<a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account = ftp</a>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628393"></a><a name="id2628395"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628516"></a><a name="id2628518"></a></td><td align="left" valign="top"><p>
 		Is it possible to reduce network broadcast activity with Samba-3?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2628407"></a>
-		<a class="indexterm" name="id2628413"></a>
+		<a class="indexterm" name="id2628530"></a>
+		<a class="indexterm" name="id2628537"></a>
 		Yes, there are two ways to do this. The first involves use of WINS (See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9,
 		Section 9.5, &#8220;<span class="quote">WINS  The Windows Inter-networking Name Server</span>&#8221;); the
 		alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires
 		a correctly configured DNS server (see <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9, Section 9.3, &#8220;<span class="quote">Discussion</span>&#8221;).
 		</p><p>
-		<a class="indexterm" name="id2628445"></a>
-		<a class="indexterm" name="id2628452"></a>
-		<a class="indexterm" name="id2628461"></a>
+		<a class="indexterm" name="id2628569"></a>
+		<a class="indexterm" name="id2628575"></a>
+		<a class="indexterm" name="id2628585"></a>
 		The use of WINS reduces network broadcast traffic. The reduction is greatest when all network
 		clients are configured to operate in <em class="parameter"><code>Hybrid Mode</code></em>. This can be effected through
 		use of DHCP to set the NetBIOS node type to type 8 for all network clients. Additionally, it is
@@ -502,7 +502,7 @@
 		</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 		Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as
 		well as with Samba-3.
-		</p></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628502"></a><a name="id2628504"></a></td><td align="left" valign="top"><p>
+		</p></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628625"></a><a name="id2628628"></a></td><td align="left" valign="top"><p>
 		Can I just use plain-text passwords with Samba?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Yes, you can configure Samba to use plain-text passwords, though this does create a few problems.
@@ -525,17 +525,17 @@
 		a UNIX system account for that user. On systems that run <code class="literal">winbindd</code> to access the Samba
 		PDC/BDC to provide Windows user and group accounts, the <em class="parameter"><code>idmap uid, idmap gid</code></em> ranges
 		set in the <code class="filename">smb.conf</code> file provide the local UID/GIDs needed for local identity management purposes.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628589"></a><a name="id2628591"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628712"></a><a name="id2628714"></a></td><td align="left" valign="top"><p>
 		What parameter in the <code class="filename">smb.conf</code> file is used to enable the use of encrypted passwords?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The parameter in the <code class="filename">smb.conf</code> file that controls this behavior is known as <em class="parameter"><code>encrypt
 		passwords</code></em>. The default setting for this in Samba-3 is <code class="constant">Yes (Enabled)</code>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628630"></a><a name="id2628632"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628754"></a><a name="id2628756"></a></td><td align="left" valign="top"><p>
 		Is it necessary to specify <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = Yes</a>
 		when Samba-3 is configured as a domain member?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		No. This is the default behavior.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628662"></a><a name="id2628664"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628785"></a><a name="id2628787"></a></td><td align="left" valign="top"><p>
 		Is it necessary to specify a <em class="parameter"><code>guest account</code></em> when Samba-3 is configured
 		as a domain member server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -543,6 +543,6 @@
 		<code class="constant">nobody</code>. If this account does not exist on the UNIX server, then it is
 		necessary to provide a <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account = an_account</a>,
 		where <code class="constant">an_account</code> is a valid local UNIX user account.
-		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2627149" href="#id2627149" class="para">15</a>] </sup>TOSHARG2, Sect 4.5.1</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="appendix.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�15.�A Collection of Useful Tidbits�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Appendix�A.�
+		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2627272" href="#id2627272" class="para">15</a>] </sup>TOSHARG2, Sect 4.5.1</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="appendix.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�15.�A Collection of Useful Tidbits�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Appendix�A.�
     GNU General Public License version 3
   </td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/secure.html b/docs/htmldocs/Samba3-ByExample/secure.html
index 33242abe91..2335411b7a 100644
--- a/docs/htmldocs/Samba3-ByExample/secure.html
+++ b/docs/htmldocs/Samba3-ByExample/secure.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Secure Office Networking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="small.html" title="Chapter�2.�Small Office Networking"><link rel="next" href="Big500users.html" title="Chapter�4.�The 500-User Office"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Secure Office Networking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="small.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="Big500users.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="secure"></a>Chapter�3.�Secure Office Networking</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="secure.html#id2558563">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558614">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558848">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558863">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559289">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559329">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560183">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564645">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564707">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Secure Office Networking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="small.html" title="Chapter�2.�Small Office Networking"><link rel="next" href="Big500users.html" title="Chapter�4.�The 500-User Office"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Secure Office Networking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="small.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="Big500users.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="secure"></a>Chapter�3.�Secure Office Networking</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="secure.html#id2558556">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558607">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2558840">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#id2558856">Technical Issues</a></span></dt><dt><span class="sect2"><a href="secure.html#id2559282">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2559322">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="secure.html#ch4bsc">Basic System Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2560176">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4dhcpdns">Configuration of DHCP and DNS Servers</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4ptrcfg">Printer Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#procstart">Process Startup Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4valid">Validation</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4appscfg">Application Share Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#ch4wincfg">Windows Client Configuration</a></span></dt><dt><span class="sect2"><a href="secure.html#id2564636">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="secure.html#id2564698">Questions and Answers</a></span></dt></dl></div><p>
 	Congratulations, your Samba networking skills are developing nicely. You started out
 	with three simple networks in <a class="link" href="simple.html" title="Chapter�1.�No-Frills Samba Servers">&#8220;No-Frills Samba Servers&#8221;</a>, and then in <a class="link" href="small.html" title="Chapter�2.�Small Office Networking">&#8220;Small Office Networking&#8221;</a>
 	you designed and built a network that provides a high degree of flexibility, integrity,
@@ -11,7 +11,7 @@
 	so caution is advised for anyone who tries to use Samba-2.2.x with the guidance here given. 
 	To avoid confusion, this book is all about Samba-3. Let's get the exercises in this 
 	chapter underway.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558563"></a>Introduction</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558556"></a>Introduction</h2></div></div></div><p>
 	You have made Mr. Meany a very happy man. Recently he paid you a fat bonus for work 
 	well done. It is one year since the last network upgrade. You have been quite busy. 
 	Two months ago Mr. Meany gave approval to hire Christine Roberson, who has taken over 
@@ -40,7 +40,7 @@
 	Occasionally she wants to work with you on a challenging problem. When you told her
 	about your move, she almost resigned, although she was reassured that a new manager would
 	be hired to run Information Technology, and she would be responsible only for operations.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558614"></a>Assignment Tasks</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558607"></a>Assignment Tasks</h3></div></div></div><p>
 		You promised the staff Internet services including Web browsing, electronic mail, virus
 		protection, and a company Web site.  Christine is eager to help turn the vision into 
 		reality. Let's see how close you can get to the promises made.
@@ -83,13 +83,13 @@
 		of users had to share a PC while waiting for new machines to arrive. This presented 
 		some problems with desktop computers and software installation into the new users' 
 		desktop profiles.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558848"></a>Dissection and Discussion</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558840"></a>Dissection and Discussion</h2></div></div></div><p>
 	Many of the conclusions you draw here are obvious. Some requirements are not very clear
 	or may simply be your means of drawing the most out of Samba-3. Much can be done more simply
 	than you will demonstrate here, but keep in mind that the network must scale to at least 500
 	users. This means that some functionality will be overdesigned for the current 130-user
 	environment.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558863"></a>Technical Issues</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558856"></a>Technical Issues</h3></div></div></div><p>
 		In this exercise we use a 24-bit subnet mask for the two local networks. This,
 		of course, limits our network to a maximum of 253 usable IP addresses. The network
 		address range chosen is one assigned by RFC1918 for private networks.
@@ -97,14 +97,14 @@
 		addresses, it is a good idea to switch to a network address specified in RFC1918
 		in the 172.16.0.0/16 range. This is done in subsequent chapters.
 		</p><p>
-		<a class="indexterm" name="id2558881"></a>
-		<a class="indexterm" name="id2558888"></a>
+		<a class="indexterm" name="id2558874"></a>
+		<a class="indexterm" name="id2558880"></a>
 		The high growth rates projected are a good reason to use the <code class="constant">tdbsam</code>
 		passdb backend. The use of <code class="constant">smbpasswd</code> for the backend may result in
 		performance problems. The <code class="constant">tdbsam</code> passdb backend offers features that
 		are not available with the older, flat ASCII-based <code class="constant">smbpasswd</code> database.
 		</p><p>
-		<a class="indexterm" name="id2558914"></a>
+		<a class="indexterm" name="id2558907"></a>
 		The proposed network design uses a single server to act as an Internet services host for
 		electronic mail, Web serving, remote administrative access via SSH, 
 		Samba-based file and print services. This design is often chosen by sites that feel 	
@@ -117,10 +117,10 @@
 		Samba will be configured to specifically not operate on the Ethernet interface that is
 		directly connected to the Internet.
 		</p><p>
-		<a class="indexterm" name="id2558939"></a>
+		<a class="indexterm" name="id2558932"></a>
+		<a class="indexterm" name="id2558938"></a>
 		<a class="indexterm" name="id2558945"></a>
-		<a class="indexterm" name="id2558952"></a>
-		<a class="indexterm" name="id2558960"></a>
+		<a class="indexterm" name="id2558953"></a>
 		You know that your ISP is providing full firewall services, but you cannot rely on that.
 		Always assume that human error will occur, so be prepared by using Linux firewall facilities
 		based on <code class="literal">iptables</code> to effect NAT. Block all
@@ -131,7 +131,7 @@
 		generic antivirus handling are beyond the scope of this book and therefore are not
 		covered except insofar as this affects Samba-3.
 		</p><p>
-		<a class="indexterm" name="id2558989"></a>
+		<a class="indexterm" name="id2558982"></a>
 		Notebook computers are configured to use a network login when in the office and a
 		local account to log in while away from the office. Users store all work done in
 		transit (away from the office) by using a local share for work files. Standard procedures
@@ -141,26 +141,26 @@
 		This is a preventative measure to protect client information as well as private business
 		records.
 		</p><p>
-		<a class="indexterm" name="id2559020"></a>
+		<a class="indexterm" name="id2559012"></a>
 		All applications are served from the central server from a share called <code class="constant">apps</code>.
 		Microsoft Office XP Professional and OpenOffice 1.1.0 will be installed using a network 
 		(or administrative) installation. Accounting and financial management software can also
 		be run only from the central application server. Notebook users are provided with
 		locally installed applications on a need-to-have basis only.
 		</p><p>
-		<a class="indexterm" name="id2559039"></a>
+		<a class="indexterm" name="id2559032"></a>
 		The introduction of roaming profiles support means that users can move between
 		desktop computer systems without constraint while retaining full access to their data.
 		The desktop travels with them as they move.
 		</p><p>
-		<a class="indexterm" name="id2559052"></a>
+		<a class="indexterm" name="id2559045"></a>
 		The DNS server implementation must now address both internal and external
 		needs. You forward DNS lookups to your ISP-provided server as well as the 
 		<code class="constant">abmas.us</code> external secondary DNS server.
 		</p><p>
-		<a class="indexterm" name="id2559069"></a>
-		<a class="indexterm" name="id2559075"></a>
-		<a class="indexterm" name="id2559083"></a>
+		<a class="indexterm" name="id2559062"></a>
+		<a class="indexterm" name="id2559068"></a>
+		<a class="indexterm" name="id2559076"></a>
 		Compared with the DHCP server configuration in <a class="link" href="small.html" title="Chapter�2.�Small Office Networking">&#8220;Small Office Networking&#8221;</a>, <a class="link" href="small.html#dhcp01" title="Example�2.2.�Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">&#8220;Abmas Accounting DHCP Server Configuration File  /etc/dhcpd.conf&#8221;</a>, the 
 		configuration used in this example has to deal with the presence of an Internet connection.
 		The scope set for it ensures that no DHCP services will be offered on the external
@@ -184,8 +184,8 @@
 		a problem because Christine is to install and configure one single workstation and
 		then clone that configuration, using Norton Ghost, to all workstations. Each machine is
 		identical, so this should pose no problem.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559135"></a>Hardware Requirements</h4></div></div></div><p>
-		<a class="indexterm" name="id2559143"></a>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559128"></a>Hardware Requirements</h4></div></div></div><p>
+		<a class="indexterm" name="id2559136"></a>
 		This server runs a considerable number of services. From similarly configured Linux
 		installations, the approximate calculated memory requirements are as shown in
 		<a class="link" href="secure.html#ch4memoryest" title="Example�3.1.�Estimation of Memory Requirements">&#8220;Estimation of Memory Requirements&#8221;</a>.
@@ -213,7 +213,7 @@ Basic OS        256.0             256            256
 		as the system load builds up. Given the low cost of memory, it does not make sense to
 		compromise in this area.
 		</p><p>
-		<a class="indexterm" name="id2559194"></a>
+		<a class="indexterm" name="id2559187"></a>
 		Aggregate input/output loads should be considered for sizing network configuration as 
 		well as disk subsystems. For network bandwidth calculations, one would typically use an
 		estimate of 0.1 MB/sec per user. This suggests that 100-Base-T (approx. 10 MB/sec)
@@ -222,8 +222,8 @@ Basic OS        256.0             256            256
 		to a 1 Gb Ethernet switch that provides connectivity to an expandable array of 100-Base-T
 		switched ports.
 		</p><p>
-		<a class="indexterm" name="id2559213"></a>
-		<a class="indexterm" name="id2559219"></a>
+		<a class="indexterm" name="id2559206"></a>
+		<a class="indexterm" name="id2559212"></a>
 		Considering the choice of 1 Gb Ethernet interfaces for the two local network segments,
 		the aggregate network I/O capacity will be 2100 Mb/sec (about 230 MB/sec), an I/O
 		demand that would require a fast disk storage I/O capability. Peak disk throughput is 
@@ -255,10 +255,10 @@ Given 500 Users and 2 years:
              Add 50% buffer                              303 GBytes
                        Recommended Storage:              908 GBytes
 </pre></div></div><p><br class="example-break">
-		<a class="indexterm" name="id2559277"></a>
+		<a class="indexterm" name="id2559270"></a>
 		The preferred storage capacity should be approximately 1 Terabyte. Use of RAID level 5
 		with two hot spare drives would require an 8-drive by 200 GB capacity per drive array.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559289"></a>Political Issues</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559282"></a>Political Issues</h3></div></div></div><p>
 		Your industry is coming under increasing accountability pressures. Increased paranoia
 		is necessary so you can demonstrate that you have acted with due diligence. You must
 		not trust your Internet connection.
@@ -267,12 +267,12 @@ Given 500 Users and 2 years:
 		an application server, your primary reason for the decision to implement this is that it
 		gives you greater control over software licensing.
 		</p><p>
-		<a class="indexterm" name="id2559311"></a>
+		<a class="indexterm" name="id2559304"></a>
 		You are well aware that the current configuration results in some performance issues
 		as the size of the desktop profile grows. Given that users use Microsoft Outlook
 		Express, you know that the storage implications of the <code class="constant">.PST</code> file
 		is something that needs to be addressed later.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559329"></a>Implementation</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559322"></a>Implementation</h2></div></div></div><p>
 	<a class="link" href="secure.html#ch04net" title="Figure�3.1.�Abmas Network Topology 130 Users">&#8220;Abmas Network Topology  130 Users&#8221;</a> demonstrates the overall design of the network that you will implement.
 	</p><p>
 	The information presented here assumes that you are already familiar with many basic steps.
@@ -288,9 +288,9 @@ Given 500 Users and 2 years:
 		</p></li><li><p>
 		The Domain name is set to <code class="constant">PROMISES</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559386"></a>
-		<a class="indexterm" name="id2559392"></a>
-		<a class="indexterm" name="id2559398"></a>
+		<a class="indexterm" name="id2559379"></a>
+		<a class="indexterm" name="id2559385"></a>
+		<a class="indexterm" name="id2559391"></a>
 		Ethernet interface <code class="constant">eth0</code> is attached to the Internet connection
 		and is externally exposed. This interface is explicitly not available for Samba to use.
 		Samba listens on this interface for broadcast messages but does not broadcast any
@@ -298,34 +298,34 @@ Given 500 Users and 2 years:
 		This is achieved by way of the <em class="parameter"><code>interfaces</code></em> parameter and the
 		<em class="parameter"><code>bind interfaces only</code></em> entry.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559431"></a>
-		<a class="indexterm" name="id2559438"></a>
-		<a class="indexterm" name="id2559444"></a>
+		<a class="indexterm" name="id2559424"></a>
+		<a class="indexterm" name="id2559430"></a>
+		<a class="indexterm" name="id2559437"></a>
 		The <em class="parameter"><code>passdb backend</code></em> parameter specifies the creation and use
 		of the <code class="constant">tdbsam</code> password backend. This is a binary database that
 		has excellent scalability for a large number of user account entries.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559466"></a>
-		<a class="indexterm" name="id2559472"></a>
-		<a class="indexterm" name="id2559478"></a>
+		<a class="indexterm" name="id2559459"></a>
+		<a class="indexterm" name="id2559465"></a>
+		<a class="indexterm" name="id2559471"></a>
 		WINS serving is enabled by the <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = Yes</a>,
 		and name resolution is set to use it by means of the
 		<a class="link" href="smb.conf.5.html#NAMERESOLVEORDER" target="_top">name resolve order = wins bcast hosts</a> entry.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559508"></a>
+		<a class="indexterm" name="id2559501"></a>
 		The Samba server is configured for use by Windows clients as a time server.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559520"></a>
-		<a class="indexterm" name="id2559526"></a>
-		<a class="indexterm" name="id2559532"></a>
+		<a class="indexterm" name="id2559513"></a>
+		<a class="indexterm" name="id2559519"></a>
+		<a class="indexterm" name="id2559525"></a>
 		Samba is configured to directly interface with CUPS via the direct internal interface
 		that is provided by CUPS libraries. This is achieved with the 
 		<a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = CUPS</a> as well as the
 		<a class="link" href="smb.conf.5.html#PRINTCAPNAME" target="_top">printcap name = CUPS</a> entries.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559563"></a>
-		<a class="indexterm" name="id2559569"></a>
-		<a class="indexterm" name="id2559576"></a>
+		<a class="indexterm" name="id2559556"></a>
+		<a class="indexterm" name="id2559562"></a>
+		<a class="indexterm" name="id2559568"></a>
 		External interface scripts are provided to enable Samba to interface smoothly to
 		essential operating system functions for user and group management. This is important
 		to enable workstations to join the Domain and is also important so that you can use
@@ -334,19 +334,19 @@ Given 500 Users and 2 years:
 		downloaded from the Microsoft FTP
 		<a class="ulink" href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">site</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559605"></a>
+		<a class="indexterm" name="id2559598"></a>
 		The <code class="filename">smb.conf</code> file specifies that the Samba server will operate in (default) <em class="parameter"><code>
-		security = user</code></em> mode<sup>[<a name="id2559623" href="#ftn.id2559623" class="footnote">5</a>]</sup>
+		security = user</code></em> mode<sup>[<a name="id2559616" href="#ftn.id2559616" class="footnote">5</a>]</sup>
 		(User Mode).
 		</p></li><li><p>
-		<a class="indexterm" name="id2559640"></a>
-		<a class="indexterm" name="id2559646"></a>
+		<a class="indexterm" name="id2559632"></a>
+		<a class="indexterm" name="id2559639"></a>
 		Domain logon services as well as a Domain logon script are specified. The logon script
 		will be used to add robustness to the overall network configuration.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559659"></a>
+		<a class="indexterm" name="id2559652"></a>
+		<a class="indexterm" name="id2559658"></a>
 		<a class="indexterm" name="id2559665"></a>
-		<a class="indexterm" name="id2559672"></a>
 		Roaming profiles are enabled through the specification of the parameter,
 		<a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path = \\%L\profiles\%U</a>. The value of this parameter translates the
 		<code class="constant">%L</code> to the name by which the Samba server is called by the client (for this
@@ -356,8 +356,8 @@ Given 500 Users and 2 years:
 		profile share for each user. This directory must be owned by the user also. An exception to this
 		requirement is when a profile is created for group use.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559712"></a>
-		<a class="indexterm" name="id2559718"></a>
+		<a class="indexterm" name="id2559705"></a>
+		<a class="indexterm" name="id2559711"></a>
 		Precautionary veto is effected for particular Windows file names that have been targeted by 
 		virus-related activity. Additionally, Microsoft Office files are vetoed from opportunistic locking
 		controls. This should help to prevent lock contention-related file access problems.
@@ -385,12 +385,12 @@ Given 500 Users and 2 years:
 		</p></li></ol></div><p>
 	The following sections cover each step in logical and defined detail.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch4bsc"></a>Basic System Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2559803"></a>
+	<a class="indexterm" name="id2559796"></a>
 	The preparation in this section assumes that your SUSE Enterprise Linux Server 8.0 system has been
 	freshly installed. It prepares basic files so that the system is ready for comprehensive
 	operation in line with the network diagram shown in <a class="link" href="secure.html#ch04net" title="Figure�3.1.�Abmas Network Topology 130 Users">&#8220;Abmas Network Topology  130 Users&#8221;</a>.
-	</p><div class="procedure"><a name="id2559820"></a><p class="title"><b>Procedure�3.1.�Server Configuration Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2559830"></a>
+	</p><div class="procedure"><a name="id2559813"></a><p class="title"><b>Procedure�3.1.�Server Configuration Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2559823"></a>
 		Using the UNIX/Linux system tools, name the server <code class="constant">server.abmas.us</code>.
 		Verify that your hostname is correctly set by running:
 </p><pre class="screen">
@@ -403,8 +403,8 @@ server
 server.abmas.us
 </pre><p>
 		</p></li><li><p>
+		<a class="indexterm" name="id2559863"></a>
 		<a class="indexterm" name="id2559870"></a>
-		<a class="indexterm" name="id2559877"></a>
 		Edit your <code class="filename">/etc/hosts</code> file to include the primary names and addresses
 		of all network interfaces that are on the host server. This is necessary so that during
 		startup the system can resolve all its own names to the IP address prior to
@@ -425,15 +425,15 @@ server.abmas.us
 192.168.2.20    qmsf.abmas.biz qmsf
 192.168.2.30    hplj6f.abmas.biz hplj6f
 </pre><p>
-		<a class="indexterm" name="id2559928"></a>
-		<a class="indexterm" name="id2559934"></a>
-		<a class="indexterm" name="id2559940"></a>
+		<a class="indexterm" name="id2559921"></a>
+		<a class="indexterm" name="id2559927"></a>
+		<a class="indexterm" name="id2559933"></a>
 		The printer entries are not necessary if <code class="literal">named</code> is started prior to
 		startup of <code class="literal">cupsd</code>, the CUPS daemon.
 		</p></li><li><p>
-		<a class="indexterm" name="id2559965"></a>
-		<a class="indexterm" name="id2559971"></a>
-		<a class="indexterm" name="id2559978"></a>
+		<a class="indexterm" name="id2559958"></a>
+		<a class="indexterm" name="id2559964"></a>
+		<a class="indexterm" name="id2559970"></a>
 		The host server is acting as a router between the two internal network segments as well
 		as for all Internet access. This necessitates that IP forwarding be enabled. This can be
 		achieved by adding to the <code class="filename">/etc/rc.d/boot.local</code> an entry as follows:
@@ -442,10 +442,10 @@ echo 1 &gt; /proc/sys/net/ipv4/ip_forward
 </pre><p>
 		To ensure that your kernel is capable of IP forwarding during configuration, you may 
 		wish to execute that command manually also. This setting permits the Linux system to 
-		act as a router.<sup>[<a name="id2560004" href="#ftn.id2560004" class="footnote">6</a>]</sup>
+		act as a router.<sup>[<a name="id2559997" href="#ftn.id2559997" class="footnote">6</a>]</sup>
 		</p></li><li><p>
+		<a class="indexterm" name="id2560009"></a>
 		<a class="indexterm" name="id2560016"></a>
-		<a class="indexterm" name="id2560023"></a>
 		Installation of a basic firewall and NAT facility is necessary.
 		The following script can be installed in the <code class="filename">/usr/local/sbin</code>
 		directory. It is executed from the <code class="filename">/etc/rc.d/boot.local</code> startup
@@ -524,15 +524,15 @@ echo -e "\nNAT firewall done.\n"
 /usr/local/sbin/abmas-natfw.sh
 </pre><p>
 		</p></li></ol></div><p>
-	<a class="indexterm" name="id2560162"></a>
+	<a class="indexterm" name="id2560155"></a>
 	The server is now ready for Samba configuration. During the validation step, you remove
 	the entry for the Samba server <code class="constant">diamond</code> from the <code class="filename">/etc/hosts</code>
 	file. This is done after you are satisfied that DNS-based name resolution is functioning correctly.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560183"></a>Samba Configuration</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560176"></a>Samba Configuration</h3></div></div></div><p>
 	When you have completed this section, the Samba server is ready for testing and validation;
 	however, testing and validation have to wait until DHCP, DNS, and printing (CUPS) services have 
 	been configured.
-	</p><div class="procedure"><a name="id2560195"></a><p class="title"><b>Procedure�3.2.�Samba Configuration Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2560188"></a><p class="title"><b>Procedure�3.2.�Samba Configuration Steps</b></p><ol type="1"><li><p>
 		Install the Samba-3 binary RPM from the Samba-Team FTP site. Assuming that the binary
 		RPM file is called <code class="filename">samba-3.0.20-1.i386.rpm</code>, one way to install this
 		file is as follows:
@@ -547,13 +547,13 @@ echo -e "\nNAT firewall done.\n"
 		and <a class="link" href="secure.html#promisnetsvcb" title="Example�3.6.�130 User Network with tdbsam Services Section Part B">&#8220;130 User Network with tdbsam  Services Section Part B&#8221;</a>. Concatenate (join) all three files to make a single <code class="filename">smb.conf</code>
 		file. The final, fully qualified path for this file should be <code class="filename">/etc/samba/smb.conf</code>.
 
-</p><div class="example"><a name="promisnet"></a><p class="title"><b>Example�3.4.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  [globals] Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2560301"></a><em class="parameter"><code>workgroup = PROMISES</code></em></td></tr><tr><td><a class="indexterm" name="id2560311"></a><em class="parameter"><code>netbios name = DIAMOND</code></em></td></tr><tr><td><a class="indexterm" name="id2560322"></a><em class="parameter"><code>interfaces = eth1, eth2, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2560332"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560342"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2560353"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560363"></a><em class="parameter"><code>passwd program = /usr/bin/passwd %u</code></em></td></tr><tr><td><a class="indexterm" name="id2560374"></a><em class="parameter"><code>passwd chat = *New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*</code></em></td></tr><tr><td><a class="indexterm" name="id2560385"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2560396"></a><em class="parameter"><code>unix password sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560407"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2560417"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2560428"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2560439"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2560449"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2560460"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2560471"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560481"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2560492"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560503"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560514"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560525"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560536"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560548"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560559"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560571"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2560582"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2560593"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2560604"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560616"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2560626"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560636"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560647"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560657"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560668"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560678"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560688"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2560699"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2560709"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2560720"></a><em class="parameter"><code>veto oplock files = /*.doc/*.xls/*.mdb/</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="promisnet"></a><p class="title"><b>Example�3.4.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  [globals] Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2560294"></a><em class="parameter"><code>workgroup = PROMISES</code></em></td></tr><tr><td><a class="indexterm" name="id2560304"></a><em class="parameter"><code>netbios name = DIAMOND</code></em></td></tr><tr><td><a class="indexterm" name="id2560314"></a><em class="parameter"><code>interfaces = eth1, eth2, lo</code></em></td></tr><tr><td><a class="indexterm" name="id2560325"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560335"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2560346"></a><em class="parameter"><code>pam password change = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560356"></a><em class="parameter"><code>passwd program = /usr/bin/passwd %u</code></em></td></tr><tr><td><a class="indexterm" name="id2560366"></a><em class="parameter"><code>passwd chat = *New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*</code></em></td></tr><tr><td><a class="indexterm" name="id2560378"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2560389"></a><em class="parameter"><code>unix password sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560400"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2560410"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2560421"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2560432"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2560442"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2560452"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2560464"></a><em class="parameter"><code>time server = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560474"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2560484"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560496"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560507"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560518"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560529"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2560541"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560552"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2560564"></a><em class="parameter"><code>shutdown script = /var/lib/samba/scripts/shutdown.sh</code></em></td></tr><tr><td><a class="indexterm" name="id2560575"></a><em class="parameter"><code>abort shutdown script = /sbin/shutdown -c</code></em></td></tr><tr><td><a class="indexterm" name="id2560586"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2560597"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560608"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2560619"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2560629"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560640"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560650"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560660"></a><em class="parameter"><code>utmp = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560671"></a><em class="parameter"><code>map acl inherit = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560681"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2560692"></a><em class="parameter"><code>cups options = Raw</code></em></td></tr><tr><td><a class="indexterm" name="id2560702"></a><em class="parameter"><code>veto files = /*.eml/*.nws/*.{*}/</code></em></td></tr><tr><td><a class="indexterm" name="id2560713"></a><em class="parameter"><code>veto oplock files = /*.doc/*.xls/*.mdb/</code></em></td></tr></table></div></div><p><br class="example-break">
 
-</p><div class="example"><a name="promisnetsvca"></a><p class="title"><b>Example�3.5.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  Services Section Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2560759"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2560770"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2560780"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560791"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2560809"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2560820"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2560830"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560841"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560851"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560861"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560872"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2560891"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2560901"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2560912"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560922"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2560941"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2560952"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2560963"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560973"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2560992"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561002"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2561013"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="promisnetsvca"></a><p class="title"><b>Example�3.5.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  Services Section Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2560752"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2560763"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2560773"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560784"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2560802"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2560813"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2560823"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560834"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560844"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560854"></a><em class="parameter"><code>default devmode = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560865"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2560884"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2560894"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2560905"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560915"></a><em class="parameter"><code>locking = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2560934"></a><em class="parameter"><code>comment = Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2560945"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2560956"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2560966"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2560985"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2560995"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2561006"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><p><br class="example-break">
 
-</p><div class="example"><a name="promisnetsvcb"></a><p class="title"><b>Example�3.6.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  Services Section Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2561051"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561062"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2561072"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2561091"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561102"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2561112"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2561131"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561141"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2561152"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2561162"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="promisnetsvcb"></a><p class="title"><b>Example�3.6.�130 User Network with <span class="emphasis"><em>tdbsam</em></span>  Services Section Part B</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[service]</code></em></td></tr><tr><td><a class="indexterm" name="id2561044"></a><em class="parameter"><code>comment = Financial Services Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561054"></a><em class="parameter"><code>path = /data/service</code></em></td></tr><tr><td><a class="indexterm" name="id2561065"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[pidata]</code></em></td></tr><tr><td><a class="indexterm" name="id2561084"></a><em class="parameter"><code>comment = Property Insurance Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561095"></a><em class="parameter"><code>path = /data/pidata</code></em></td></tr><tr><td><a class="indexterm" name="id2561105"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[apps]</code></em></td></tr><tr><td><a class="indexterm" name="id2561124"></a><em class="parameter"><code>comment = Application Files</code></em></td></tr><tr><td><a class="indexterm" name="id2561134"></a><em class="parameter"><code>path = /apps</code></em></td></tr><tr><td><a class="indexterm" name="id2561145"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2561155"></a><em class="parameter"><code>admin users = bjordan</code></em></td></tr></table></div></div><p><br class="example-break">
 		</p></li><li><p>
-	      <a class="indexterm" name="id2561180"></a><a class="indexterm" name="id2561185"></a>
+	      <a class="indexterm" name="id2561173"></a><a class="indexterm" name="id2561178"></a>
 		Add the <code class="constant">root</code> user to the password backend as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbpasswd -a root
@@ -566,7 +566,7 @@ Retype new SMB password: XXXXXXXX
 		deleted. If for any reason the account is deleted, you may not be able to recreate this account
 		without considerable trouble.
 		</p></li><li><p>
-		<a class="indexterm" name="id2561229"></a>
+		<a class="indexterm" name="id2561222"></a>
                 Create the username map file to permit the <code class="constant">root</code> account to be called
                 <code class="constant">Administrator</code> from the Windows network environment. To do this, create
                 the file <code class="filename">/etc/samba/smbusers</code> with the following contents:
@@ -593,16 +593,16 @@ root = Administrator
 ####
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2561271"></a>
-		<a class="indexterm" name="id2561277"></a>
-		<a class="indexterm" name="id2561288"></a>
-		<a class="indexterm" name="id2561298"></a>
+		<a class="indexterm" name="id2561264"></a>
+		<a class="indexterm" name="id2561270"></a>
+		<a class="indexterm" name="id2561281"></a>
+		<a class="indexterm" name="id2561291"></a>
                 Create and map Windows Domain Groups to UNIX groups. A sample script is provided in <a class="link" href="small.html" title="Chapter�2.�Small Office Networking">&#8220;Small Office Networking&#8221;</a>,
                 <a class="link" href="small.html#initGrps" title="Example�2.1.�Script to Map Windows NT Groups to UNIX Groups">&#8220;Script to Map Windows NT Groups to UNIX Groups&#8221;</a>. Create a file containing this script. We called ours
                 <code class="filename">/etc/samba/initGrps.sh</code>. Set this file so it can be executed,
                 and then execute the script. Sample output should be as follows:
 
-</p><div class="example"><a name="ch4initGrps"></a><p class="title"><b>Example�3.7.�Script to Map Windows NT Groups to UNIX Groups</b></p><div class="example-contents"><a class="indexterm" name="id2561336"></a><pre class="screen">
+</p><div class="example"><a name="ch4initGrps"></a><p class="title"><b>Example�3.7.�Script to Map Windows NT Groups to UNIX Groups</b></p><div class="example-contents"><a class="indexterm" name="id2561329"></a><pre class="screen">
 #!/bin/bash
 #
 # initGrps.sh
@@ -655,13 +655,13 @@ System Operators (S-1-5-32-549) -&gt; -1
 Users (S-1-5-32-545) -&gt; -1
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2561409"></a>
-		<a class="indexterm" name="id2561415"></a>
-		<a class="indexterm" name="id2561421"></a>
+		<a class="indexterm" name="id2561402"></a>
+		<a class="indexterm" name="id2561408"></a>
+		<a class="indexterm" name="id2561414"></a>
+		<a class="indexterm" name="id2561420"></a>
 		<a class="indexterm" name="id2561427"></a>
-		<a class="indexterm" name="id2561434"></a>
-		<a class="indexterm" name="id2561440"></a>
-		<a class="indexterm" name="id2561448"></a>
+		<a class="indexterm" name="id2561433"></a>
+		<a class="indexterm" name="id2561441"></a>
 		There is one preparatory step without which you will not have a working Samba 
 		network environment. You must add an account for each network user. 
                 For each user who needs to be given a Windows Domain account, make an entry in the
@@ -686,9 +686,9 @@ Added user <em class="parameter"><code>username</code></em>.
 </pre><p>
 		You do of course use a valid user login ID in place of <em class="parameter"><code>username</code></em>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2561553"></a>
-		<a class="indexterm" name="id2561561"></a>
-		<a class="indexterm" name="id2561569"></a>
+		<a class="indexterm" name="id2561546"></a>
+		<a class="indexterm" name="id2561554"></a>
+		<a class="indexterm" name="id2561562"></a>
                 Using the preferred tool for your UNIX system, add each user to the UNIX groups created
                 previously as necessary. File system access control will be based on UNIX group membership.
                 </p></li><li><p>
@@ -697,7 +697,7 @@ Added user <em class="parameter"><code>username</code></em>.
                 file is <code class="filename">/data</code>. Format the file system as required, and mount the formatted
                 file system partition using appropriate system tools.
                 </p></li><li><p>
-		<a class="indexterm" name="id2561609"></a>
+		<a class="indexterm" name="id2561602"></a>
                 Create the top-level file storage directories for data and applications as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> mkdir -p /data/{accounts,finsrvcs}
@@ -738,9 +738,9 @@ Added user <em class="parameter"><code>username</code></em>.
 <code class="prompt">root# </code> chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2561803"></a>
-		<a class="indexterm" name="id2561809"></a>
-		<a class="indexterm" name="id2561815"></a>
+		<a class="indexterm" name="id2561796"></a>
+		<a class="indexterm" name="id2561802"></a>
+		<a class="indexterm" name="id2561808"></a>
 		Create a logon script. It is important that each line is correctly terminated with
 		a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
 		works if the right tools (<code class="constant">unix2dos</code> and <code class="constant">dos2unix</code>) are installed.
@@ -760,8 +760,8 @@ net use p: \\diamond\apps
 	DHCP services are a basic component of the entire network client installation. DNS operation is
 	foundational to Internet access as well as to trouble-free operation of local networking. When
 	you have completed this section, the server should be ready for solid duty operation.
-	</p><div class="procedure"><a name="id2561886"></a><p class="title"><b>Procedure�3.3.�DHCP and DNS Server Configuration Steps</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2561897"></a>
+	</p><div class="procedure"><a name="id2561878"></a><p class="title"><b>Procedure�3.3.�DHCP and DNS Server Configuration Steps</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2561890"></a>
 		Create a file called <code class="filename">/etc/dhcpd.conf</code> with the contents as
 		shown in <a class="link" href="secure.html#prom-dhcp" title="Example�3.8.�DHCP Server Configuration File /etc/dhcpd.conf">&#8220;DHCP Server Configuration File  /etc/dhcpd.conf&#8221;</a>.
 
@@ -812,7 +812,7 @@ subnet 123.45.67.64 netmask 255.255.255.252 {
         }
 </pre></div></div><p><br class="example-break">
 		</p></li><li><p>
-		<a class="indexterm" name="id2561972"></a>
+		<a class="indexterm" name="id2561965"></a>
 		Create a file called <code class="filename">/etc/named.conf</code> that has the combined contents
 		of the <a class="link" href="secure.html#ch4namedcfg" title="Example�3.9.�DNS Master Configuration File /etc/named.conf Master Section">&#8220;DNS Master Configuration File  /etc/named.conf Master Section&#8221;</a>, <a class="link" href="secure.html#ch4namedvarfwd" title="Example�3.10.�DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section">&#8220;DNS Master Configuration File  /etc/named.conf Forward Lookup Definition Section&#8221;</a>, and
 		<a class="link" href="secure.html#ch4namedvarrev" title="Example�3.11.�DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section">&#8220;DNS Master Configuration File  /etc/named.conf Reverse Lookup Definition Section&#8221;</a> files that are concatenated (merged) in this
@@ -823,7 +823,7 @@ subnet 123.45.67.64 netmask 255.255.255.252 {
 
 			</p><div class="table"><a name="namedrscfiles"></a><p class="title"><b>Table�3.2.�DNS (named) Resource Files</b></p><div class="table-contents"><table summary="DNS (named) Resource Files" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Reference</th><th align="left">File Location</th></tr></thead><tbody><tr><td align="left"><a class="link" href="appendix.html#loopback" title="Example�15.3.�DNS Localhost Forward Zone File: /var/lib/named/localhost.zone">&#8220;DNS Localhost Forward Zone File: /var/lib/named/localhost.zone&#8221;</a></td><td align="left">/var/lib/named/localhost.zone</td></tr><tr><td align="left"><a class="link" href="appendix.html#dnsloopy" title="Example�15.4.�DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone">&#8220;DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone&#8221;</a></td><td align="left">/var/lib/named/127.0.0.zone</td></tr><tr><td align="left"><a class="link" href="appendix.html#roothint" title="Example�15.5.�DNS Root Name Server Hint File: /var/lib/named/root.hint">&#8220;DNS Root Name Server Hint File: /var/lib/named/root.hint&#8221;</a></td><td align="left">/var/lib/named/root.hint</td></tr><tr><td align="left"><a class="link" href="secure.html#abmasbiz" title="Example�3.14.�DNS Abmas.biz Forward Zone File">&#8220;DNS Abmas.biz Forward Zone File&#8221;</a></td><td align="left">/var/lib/named/master/abmas.biz.hosts</td></tr><tr><td align="left"><a class="link" href="secure.html#abmasus" title="Example�3.15.�DNS Abmas.us Forward Zone File">&#8220;DNS Abmas.us Forward Zone File&#8221;</a></td><td align="left">/var/lib/named/abmas.us.hosts</td></tr><tr><td align="left"><a class="link" href="secure.html#eth1zone" title="Example�3.12.�DNS 192.168.1 Reverse Zone File">&#8220;DNS 192.168.1 Reverse Zone File&#8221;</a></td><td align="left">/var/lib/named/192.168.1.0.rev</td></tr><tr><td align="left"><a class="link" href="secure.html#eth2zone" title="Example�3.13.�DNS 192.168.2 Reverse Zone File">&#8220;DNS 192.168.2 Reverse Zone File&#8221;</a></td><td align="left">/var/lib/named/192.168.2.0.rev</td></tr></tbody></table></div></div><p><br class="table-break">
 
-</p><div class="example"><a name="ch4namedcfg"></a><p class="title"><b>Example�3.9.�DNS Master Configuration File  <code class="filename">/etc/named.conf</code> Master Section</b></p><div class="example-contents"><a class="indexterm" name="id2562182"></a><pre class="screen">
+</p><div class="example"><a name="ch4namedcfg"></a><p class="title"><b>Example�3.9.�DNS Master Configuration File  <code class="filename">/etc/named.conf</code> Master Section</b></p><div class="example-contents"><a class="indexterm" name="id2562175"></a><pre class="screen">
 ###
 # Abmas Biz DNS Control File
 ###
@@ -1008,7 +1008,7 @@ dns                     CNAME   server
 </pre></div></div><p><br class="example-break">
 
 		</p></li><li><p>
-	      <a class="indexterm" name="id2562396"></a><a class="indexterm" name="id2562402"></a>
+	      <a class="indexterm" name="id2562388"></a><a class="indexterm" name="id2562394"></a>
 		All DNS name resolution should be handled locally. To ensure that the server is configured
 		correctly to handle this, edit <code class="filename">/etc/resolv.conf</code> to have the following
 		content:
@@ -1017,13 +1017,13 @@ search abmas.us abmas.biz
 nameserver 127.0.0.1
 nameserver 123.45.54.23
 </pre><p>
-	      <a class="indexterm" name="id2562427"></a>
+	      <a class="indexterm" name="id2562419"></a>
 		This instructs the name resolver function (when configured correctly) to ask the DNS server
 		that is running locally to resolve names to addresses. In the event that the local name server
 		is not available, ask the name server provided by the ISP. The latter, of course, does not resolve
 		purely local names to IP addresses.
 		</p></li><li><p>
-		<a class="indexterm" name="id2562448"></a>
+		<a class="indexterm" name="id2562440"></a>
 		The final step is to edit the <code class="filename">/etc/nsswitch.conf</code> file.
 		This file controls the operation of the various resolver libraries that are part of the Linux
 		Glibc libraries. Edit this file so that it contains the following entries:
@@ -1042,17 +1042,17 @@ hosts:      files dns wins
 	transparent print queue that performs no filtering, and only minimal handling of each print job that is
 	submitted to it. In other words, our configuration turns CUPS into a raw-mode print queue. This means that
 	the correct printer driver must be installed on all clients.
-	</p><div class="procedure"><a name="id2562506"></a><p class="title"><b>Procedure�3.4.�Printer Configuration Steps</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2562499"></a><p class="title"><b>Procedure�3.4.�Printer Configuration Steps</b></p><ol type="1"><li><p>
 		Configure each printer to be a DHCP client, carefully following the manufacturer's guidelines.
 		</p></li><li><p>
                 Follow the instructions in the printer manufacturer's manuals to permit printing to port 9100.
 		Use any other port the manufacturer specifies for direct-mode raw printing, and adjust the
 		port as necessary in the following example commands.
                 This allows the CUPS spooler to print using raw mode protocols.
-                <a class="indexterm" name="id2562532"></a>
-                <a class="indexterm" name="id2562539"></a>
+                <a class="indexterm" name="id2562524"></a>
+                <a class="indexterm" name="id2562531"></a>
                 </p></li><li><p>
-	      <a class="indexterm" name="id2562552"></a><a class="indexterm" name="id2562560"></a>
+	      <a class="indexterm" name="id2562545"></a><a class="indexterm" name="id2562553"></a>
                 Configure the CUPS Print Queues as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p qmsa -v socket://qmsa.abmas.biz:9100 -E
@@ -1060,9 +1060,9 @@ hosts:      files dns wins
 <code class="prompt">root# </code> lpadmin -p qmsf -v socket://qmsf.abmas.biz:9100 -E
 <code class="prompt">root# </code> lpadmin -p hplj6f -v socket://hplj6f.abmas.biz:9100 -E
 </pre><p>
-                <a class="indexterm" name="id2562603"></a>
+                <a class="indexterm" name="id2562596"></a>
                 This creates the necessary print queues with no assigned print filter.
-                </p></li><li><p><a class="indexterm" name="id2562618"></a>
+                </p></li><li><p><a class="indexterm" name="id2562610"></a>
 		Print queues may not be enabled at creation. Use <code class="literal">lpc stat</code> to check
 		the status of the print queues and, if necessary, make certain that the queues you have 
 		just created are enabled by executing the following:
@@ -1072,7 +1072,7 @@ hosts:      files dns wins
 <code class="prompt">root# </code> /usr/bin/enable qmsf
 <code class="prompt">root# </code> /usr/bin/enable hplj6f
 </pre><p>
-		</p></li><li><p><a class="indexterm" name="id2562673"></a>
+		</p></li><li><p><a class="indexterm" name="id2562665"></a>
 		Even though your print queues may be enabled, it is still possible that they
 		are not accepting print jobs. A print queue services incoming printing
 		requests only when configured to do so. Ensure that your print queues are
@@ -1084,15 +1084,15 @@ hosts:      files dns wins
 <code class="prompt">root# </code> /usr/sbin/accept hplj6f
 </pre><p>
 		</p></li><li><p>
-                <a class="indexterm" name="id2562724"></a>
-                <a class="indexterm" name="id2562731"></a>
-                <a class="indexterm" name="id2562738"></a>
+                <a class="indexterm" name="id2562716"></a>
+                <a class="indexterm" name="id2562723"></a>
+                <a class="indexterm" name="id2562730"></a>
                 Edit the file <code class="filename">/etc/cups/mime.convs</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
                 </p></li><li><p>
-                <a class="indexterm" name="id2562765"></a>
+                <a class="indexterm" name="id2562758"></a>
                 Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
@@ -1105,7 +1105,7 @@ application/octet-stream
 	</p><p>
 	The UNIX system print queues have been configured and are ready for validation testing.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="procstart"></a>Process Startup Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2562831"></a>
+	<a class="indexterm" name="id2562823"></a>
 	There are two essential steps to process startup configuration. First, the process
 	must be configured so that it automatically restarts each time the server
 	is rebooted. This step involves use of the <code class="literal">chkconfig</code> tool that
@@ -1114,11 +1114,11 @@ application/octet-stream
 	directories. Links are created so that when the system run level is changed, the
 	necessary start or kill script is run.
 	</p><p>
-	<a class="indexterm" name="id2562866"></a>
-	<a class="indexterm" name="id2562873"></a>
-	<a class="indexterm" name="id2562880"></a>
+	<a class="indexterm" name="id2562858"></a>
+	<a class="indexterm" name="id2562865"></a>
+	<a class="indexterm" name="id2562872"></a>
+	<a class="indexterm" name="id2562879"></a>
 	<a class="indexterm" name="id2562886"></a>
-	<a class="indexterm" name="id2562893"></a>
 	In the event that a service is not run as a daemon, but via the internetworking
 	super daemon (<code class="literal">inetd</code> or <code class="literal">xinetd</code>), then the <code class="literal">chkconfig</code>
 	tool makes the necessary entries in the <code class="filename">/etc/xinetd.d</code> directory
@@ -1129,7 +1129,7 @@ application/octet-stream
 	</p><div class="procedure"><ol type="1"><li><p>
                 Use the standard system tool to configure each service to restart
                 automatically at every system reboot. For example,
-                <a class="indexterm" name="id2562945"></a>
+                <a class="indexterm" name="id2562937"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig dhpcd on
 <code class="prompt">root# </code> chkconfig named on
@@ -1137,9 +1137,9 @@ application/octet-stream
 <code class="prompt">root# </code> chkconfig smb on
 </pre><p>
 		</p></li><li><p>
-                <a class="indexterm" name="id2562989"></a>
-                <a class="indexterm" name="id2562996"></a>
-                <a class="indexterm" name="id2563002"></a>
+                <a class="indexterm" name="id2562981"></a>
+                <a class="indexterm" name="id2562988"></a>
+                <a class="indexterm" name="id2562995"></a>
 		Now start each service to permit the system to be validated.
 		Execute each of the following in the sequence shown:
 
@@ -1150,7 +1150,7 @@ application/octet-stream
 <code class="prompt">root# </code> /etc/rc.d/init.d/smb restart
 </pre><p>
                 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch4valid"></a>Validation</h3></div></div></div><p>
-	<a class="indexterm" name="id2563057"></a>
+	<a class="indexterm" name="id2563049"></a>
 	Complex networking problems are most often caused by simple things that are poorly or incorrectly
 	configured. The validation process adopted here should be followed carefully; it is the result of the
 	experience gained from years of making and correcting the most common mistakes. Shortcuts often lead to basic errors. You should
@@ -1160,8 +1160,8 @@ application/octet-stream
 	days. A well debugged network is a foundation for happy network users and network administrators. 
 	Later in this book you learn how to make users happier. For now, it is enough to learn to 
 	validate. Let's get on with it.
-	</p><div class="procedure"><a name="id2563079"></a><p class="title"><b>Procedure�3.5.�Server Validation Steps</b></p><ol type="1"><li><p>
-			<a class="indexterm" name="id2563090"></a>
+	</p><div class="procedure"><a name="id2563072"></a><p class="title"><b>Procedure�3.5.�Server Validation Steps</b></p><ol type="1"><li><p>
+			<a class="indexterm" name="id2563083"></a>
 			One of the most important facets of Samba configuration is to ensure that
 			name resolution functions correctly. You can check name resolution
 			with a few simple tests. The most basic name resolution is provided from the
@@ -1187,7 +1187,7 @@ rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms
 			This proves that name resolution via the <code class="filename">/etc/hosts</code> file
 			is working.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563160"></a>
+			<a class="indexterm" name="id2563152"></a>
 			So far, your installation is going particularly well. In this step we validate
 			DNS server and name resolution operation. Using your favorite UNIX system editor,
 			change the <code class="filename">/etc/nsswitch.conf</code> file so that the
@@ -1196,7 +1196,7 @@ rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms
 hosts:        dns
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2563193"></a>
+			<a class="indexterm" name="id2563185"></a>
 			Before you test DNS operation, it is a good idea to verify that the DNS server
 			is running by executing the following:
 </p><pre class="screen">
@@ -1210,7 +1210,7 @@ hosts:        dns
  2552 pts/2    S      0:00 grep named
 </pre><p>
 			This means that we are ready to check DNS operation. Do so by executing:
-			<a class="indexterm" name="id2563223"></a>
+			<a class="indexterm" name="id2563215"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> ping diamond
 PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
@@ -1226,12 +1226,12 @@ rtt min/avg/max/mdev = 0.156/0.169/0.183/0.018 ms
 <code class="prompt">root# </code> host -f diamond.abmas.biz
 sleeth1.abmas.biz has address 192.168.1.1
 </pre><p>
-			<a class="indexterm" name="id2563261"></a>
+			<a class="indexterm" name="id2563254"></a>
 			You may now remove the entry called <code class="constant">diamond</code> from the
 			<code class="filename">/etc/hosts</code> file. It does not hurt to leave it there,
 			but its removal reduces the number of administrative steps for this name.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563287"></a>
+			<a class="indexterm" name="id2563279"></a>
 			WINS is a great way to resolve NetBIOS names to their IP address. You can test
 			the operation of WINS by starting <code class="literal">nmbd</code> (manually or by way
 			of the Samba startup method shown in <a class="link" href="secure.html#procstart" title="Process Startup Configuration">&#8220;Process Startup Configuration&#8221;</a>). You must edit
@@ -1242,7 +1242,7 @@ hosts:        wins
 </pre><p>
 			The next step is to make certain that Samba is running using <code class="literal">ps ax | grep mbd</code>.
 			The <code class="literal">nmbd</code> daemon will provide the WINS name resolution service when the
-			<code class="filename">smb.conf</code> file <em class="parameter"><code>global</code></em> parameter <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins    support = Yes</a> has been specified.  Having validated that Samba is operational,
+			<code class="filename">smb.conf</code> file <em class="parameter"><code></code></em> parameter <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins    support = Yes</a> has been specified.  Having validated that Samba is operational,
 			excute the following:
 </p><pre class="screen">
 <code class="prompt">root# </code> ping diamond
@@ -1250,7 +1250,7 @@ PING diamond (192.168.1.1) 56(84) bytes of data.
 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.094 ms
 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.479 ms
 </pre><p>
-			<a class="indexterm" name="id2563380"></a>
+			<a class="indexterm" name="id2563371"></a>
 			Now that you can relax with the knowledge that all three major forms of name
 			resolution to IP address resolution are working, edit the <code class="filename">/etc/nsswitch.conf</code>
 			again. This time you add all three forms of name resolution to this file.
@@ -1271,7 +1271,7 @@ hosts:       files dns wins
 			This shows that the server is running. The proof of whether or not it is working
 			comes when you try to add the first DHCP client to the network.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563440"></a>
+			<a class="indexterm" name="id2563431"></a>
 			This is a good point at which to start validating Samba operation. You are 
 			content that name resolution is working for basic TCP/IP needs. Let's move on.
 			If your <code class="filename">smb.conf</code> file has bogus options or parameters, this may cause Samba
@@ -1343,10 +1343,10 @@ Loaded services file OK.
 </pre><p>
 			Clear away all errors before proceeding.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563541"></a>
-			<a class="indexterm" name="id2563548"></a>
-			<a class="indexterm" name="id2563554"></a>
-			<a class="indexterm" name="id2563561"></a>
+			<a class="indexterm" name="id2563532"></a>
+			<a class="indexterm" name="id2563539"></a>
+			<a class="indexterm" name="id2563545"></a>
+			<a class="indexterm" name="id2563552"></a>
 			Check that the Samba server is running:
 </p><pre class="screen">
 <code class="prompt">root# </code> ps ax | grep mbd
@@ -1359,10 +1359,10 @@ $rootprompt; ps ax | grep winbind
 14295 ?        S     0:00 /usr/sbin/winbindd -D
 </pre><p>
 			The <code class="literal">winbindd</code> daemon is running in split mode (normal), so there are also
-			two instances<sup>[<a name="id2563592" href="#ftn.id2563592" class="footnote">7</a>]</sup> of it.
+			two instances<sup>[<a name="id2563584" href="#ftn.id2563584" class="footnote">7</a>]</sup> of it.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563623"></a>
-	      <a class="indexterm" name="id2563630"></a>
+			<a class="indexterm" name="id2563614"></a>
+	      <a class="indexterm" name="id2563621"></a>
 			Check that an anonymous connection can be made to the Samba server:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbclient -L localhost -U%
@@ -1394,9 +1394,9 @@ $rootprompt; ps ax | grep winbind
 			The <code class="constant">-U%</code> argument means to send a <code class="constant">NULL</code> username and
 			a <code class="constant">NULL</code> password.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563688"></a>
-			<a class="indexterm" name="id2563695"></a>
-			<a class="indexterm" name="id2563702"></a>
+			<a class="indexterm" name="id2563679"></a>
+			<a class="indexterm" name="id2563686"></a>
+			<a class="indexterm" name="id2563693"></a>
 			Verify that each printer has the IP address assigned in the DHCP server configuration file.
 			The easiest way to do this is to ping the printer name. Immediately after the ping response
 			has been received, execute <code class="literal">arp -a</code> to find the MAC address of the printer
@@ -1411,12 +1411,12 @@ PING hplj6a (192.168.1.30) 56(84) bytes of data.
 <code class="prompt">root# </code> arp -a
 hplj6a (192.168.1.30) at 00:03:47:CB:81:E0 [ether] on eth0
 </pre><p>
-	      <a class="indexterm" name="id2563748"></a>
+	      <a class="indexterm" name="id2563739"></a>
 			The MAC address <code class="constant">00:03:47:CB:81:E0</code> matches that specified for the
 			IP address from which the printer has responded and with the entry for it in the
 			<code class="filename">/etc/dhcpd.conf</code> file. Repeat this for each printer configured.
 			</p></li><li><p>
-			<a class="indexterm" name="id2563777"></a>
+			<a class="indexterm" name="id2563768"></a>
 			Make an authenticated connection to the server using the <code class="literal">smbclient</code> tool:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbclient //diamond/accounts -U gholmes
@@ -1435,7 +1435,7 @@ smb: \&gt; dir
 smb: \&gt; q
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2563834"></a>
+			<a class="indexterm" name="id2563825"></a>
 			Your new server is connected to an Internet-accessible connection. Before you start
 			your firewall, you should run a port scanner against your system. You should repeat that
 			after the firewall has been started. This helps you understand to what extent the
@@ -1510,8 +1510,8 @@ Port       State       Service
 Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 </pre><p>
 			</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch4appscfg"></a>Application Share Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2563937"></a>
-	<a class="indexterm" name="id2563944"></a>
+	<a class="indexterm" name="id2563928"></a>
+	<a class="indexterm" name="id2563935"></a>
 	The use of an application server is a key mechanism by which desktop administration overheads
 	can be reduced. Check the application manual for your software to identify how best to
 	create an administrative installation.
@@ -1532,7 +1532,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		on a central network share. This type of installation often prevents storage
 		of work files on the local workstation.
 		</p></li></ul></div><p>
-	<a class="indexterm" name="id2563996"></a>
+	<a class="indexterm" name="id2563987"></a>
 	A common application deployed in this environment is an office suite.
 	Enterprise editions of Microsoft Office XP Professional can be administratively installed
 	by launching the installation from a command shell. The command that achieves this is
@@ -1549,8 +1549,8 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 	A network workstation (minimum) installation requires typically 10 MB to 15 MB of
 	local disk space. In the latter case, when the applications are used, they load over the network.
 	</p><p>
-	<a class="indexterm" name="id2564033"></a>
-	<a class="indexterm" name="id2564040"></a>
+	<a class="indexterm" name="id2564024"></a>
+	<a class="indexterm" name="id2564031"></a>
 	Microsoft Office Service Packs can be unpacked to update an administrative share. This makes
 	it possible to update MS Office XP Professional for all users from a single installation
 	of the service pack and generally circumvents the need to run updates on each network
@@ -1559,7 +1559,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 	The default location for MS Office XP Professional data files can be set through registry
 	editing or by way of configuration options inside each Office XP Professional application.
 	</p><p>
-	<a class="indexterm" name="id2564062"></a>
+	<a class="indexterm" name="id2564053"></a>
 	OpenOffice.Org OpenOffice Version 1.1.0 can be installed locally. It can also
 	be installed to run off a network share. The latter is a most desirable solution for office-bound 
 	network users and for administrative staff alike. It permits quick and easy updates
@@ -1572,7 +1572,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 	prompted on screen for the target installation location. This is the administrative
 	share point. The full administrative OpenOffice share takes approximately 150 MB of disk
 	space.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564093"></a>Comments Regarding Software Terms of Use</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564084"></a>Comments Regarding Software Terms of Use</h4></div></div></div><p>
 			Many single-user products can be installed into an administrative share, but
 			personal versions of products such as Microsoft Office XP Professional do not permit this. 
 			Many people do not like terms of use typical with commercial products, so a few comments
@@ -1596,7 +1596,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 			also. Whatever the licensing terms may be, if you do not approve of the terms of use,
 			please do not use the software.
 			</p><p>
-			<a class="indexterm" name="id2564142"></a>
+			<a class="indexterm" name="id2564133"></a>
 			Samba is provided under the terms of the GNU GPL Version 2, a copy of which is provided
 			with the source code.
 			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ch4wincfg"></a>Windows Client Configuration</h3></div></div></div><p>
@@ -1607,8 +1607,8 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 	Ghost (enterprise edition) to replicate the staged machine to its target desktops. The same can
 	be done with notebook computers as long as they are identical or sufficiently similar.
 	</p><div class="procedure"><a name="sbewinclntprep"></a><p class="title"><b>Procedure�3.6.�Windows Client Configuration Procedure</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2564192"></a>
-		<a class="indexterm" name="id2564199"></a>
+		<a class="indexterm" name="id2564183"></a>
+		<a class="indexterm" name="id2564190"></a>
 		Install MS Windows XP Professional. During installation, configure the client to use DHCP for 
 		TCP/IP protocol configuration. DHCP configures all Windows clients to use the WINS Server
 		address that has been defined for the local subnet.
@@ -1641,7 +1641,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		Install printers on each machine following the steps shown in the Windows client printer
 		preparation procedure below.
 		</p></li><li><p>
-		<a class="indexterm" name="id2564337"></a>
+		<a class="indexterm" name="id2564328"></a>
 		When you are satisfied that the staging systems are complete, use the appropriate procedure to
 		remove the client from the domain. Reboot the system and then log on as the local administrator
 		and clean out all temporary files stored on the system. Before shutting down, use the disk
@@ -1650,8 +1650,8 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		Boot the workstation using the Norton (Symantec) Ghosting diskette (or CD-ROM) and image the
 		machine to a network share on the server.
 		</p></li><li><p>
+		<a class="indexterm" name="id2564357"></a>
 		<a class="indexterm" name="id2564366"></a>
-		<a class="indexterm" name="id2564375"></a>
 		You may now replicate the image to the target machines using the appropriate Norton Ghost 
 		procedure. Make sure to use the procedure that ensures each machine has a unique
 		Windows security identifier (SID). When the installation of the disk image has completed, boot the PC. 
@@ -1686,7 +1686,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		</p></li><li><p>
 		Repeat the printer installation steps above for both HP LaserJet 6 printers
 		as well as for both QMS Magicolor laser printers.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564645"></a>Key Points Learned</h3></div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564636"></a>Key Points Learned</h3></div></div></div><p>
 		How do you feel? You have built a capable network, a truly ambitious project.
 		Future network updates can be handled by
 		your staff. You must be a satisfied manager. Let's review the achievements.
@@ -1709,29 +1709,29 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 			You introduced an application server as well as the concept of cloning a Windows
 			client in order to effect improved standardization of desktops and to reduce
 			the costs of network management.
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564707"></a>Questions and Answers</h2></div></div></div><p>
-	</p><div class="qandaset"><dl><dt>1. <a href="secure.html#id2564723">
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564698"></a>Questions and Answers</h2></div></div></div><p>
+	</p><div class="qandaset"><dl><dt>1. <a href="secure.html#id2564714">
 		What is the maximum number of account entries that the tdbsam
 		passdb backend can handle?
-		</a></dt><dt>2. <a href="secure.html#id2564792">
+		</a></dt><dt>2. <a href="secure.html#id2564783">
 		Would Samba operate any better if the OS level is set to a value higher than 35?
-		</a></dt><dt>3. <a href="secure.html#id2564814">
+		</a></dt><dt>3. <a href="secure.html#id2564805">
 		Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups?
-		</a></dt><dt>4. <a href="secure.html#id2564836">
+		</a></dt><dt>4. <a href="secure.html#id2564827">
 		Why has a path been specified in the IPC$ share?
-		</a></dt><dt>5. <a href="secure.html#id2564865">
+		</a></dt><dt>5. <a href="secure.html#id2564856">
 		Why does the smb.conf file in this exercise include an entry for smb ports?
-		</a></dt><dt>6. <a href="secure.html#id2564911">
+		</a></dt><dt>6. <a href="secure.html#id2564902">
 		What is the difference between a print queue and a printer?
-		</a></dt><dt>7. <a href="secure.html#id2564947">
+		</a></dt><dt>7. <a href="secure.html#id2564938">
 		Can all MS Windows application software be installed onto an application server share?
-		</a></dt><dt>8. <a href="secure.html#id2564972">
+		</a></dt><dt>8. <a href="secure.html#id2564963">
 		Why use dynamic DNS (DDNS)?
-		</a></dt><dt>9. <a href="secure.html#id2564992">
+		</a></dt><dt>9. <a href="secure.html#id2564983">
 		Why would you use WINS as well as DNS-based name resolution?
-		</a></dt><dt>10. <a href="secure.html#id2565077">
+		</a></dt><dt>10. <a href="secure.html#id2565068">
 		What are the major benefits of using an application server?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2564723"></a><a name="id2564725"></a><p><b>1.</b></p></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2564714"></a><a name="id2564716"></a><p><b>1.</b></p></td><td align="left" valign="top"><p>
 		What is the maximum number of account entries that the <em class="parameter"><code>tdbsam</code></em>
 		passdb backend can handle?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -1757,26 +1757,26 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		at which most networks tend to want backup domain controllers (BDCs). Samba-3 does
 		not provide a mechanism for replicating tdbsam data so it can be used by a BDC. The
 		limitation of 250 users per tdbsam is predicated only on the need for replication,
-		not on the limits<sup>[<a name="id2564781" href="#ftn.id2564781" class="footnote">8</a>]</sup> of the tdbsam backend itself. 
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564792"></a><a name="id2564794"></a><p><b>2.</b></p></td><td align="left" valign="top"><p>
+		not on the limits<sup>[<a name="id2564772" href="#ftn.id2564772" class="footnote">8</a>]</sup> of the tdbsam backend itself. 
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564783"></a><a name="id2564785"></a><p><b>2.</b></p></td><td align="left" valign="top"><p>
 		Would Samba operate any better if the OS level is set to a value higher than 35?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		No. MS Windows workstations and servers do not use a value higher than 33. Setting this to a value
 		of 35 already assures Samba of precedence over MS Windows products in browser elections. There is
 		no gain to be had from setting this higher.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564814"></a><a name="id2564816"></a><p><b>3.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564805"></a><a name="id2564807"></a><p><b>3.</b></p></td><td align="left" valign="top"><p>
 		Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		At this time, Samba has the capacity to use only Domain Groups mappings. It is possible that at
 		a later date Samba may make use of Windows Local Groups, as well as of the Active Directory special
 		Groups. Proper operation requires Domain Groups to be mapped to valid UNIX groups.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564836"></a><a name="id2564838"></a><p><b>4.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564827"></a><a name="id2564830"></a><p><b>4.</b></p></td><td align="left" valign="top"><p>
 		Why has a path been specified in the <em class="parameter"><code>IPC$</code></em> share?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		This is done so that in the event that a software bug may permit a client connection to the IPC$ share to
 		obtain access to the file system, it does so at a location that presents least risk. Under normal operation
 		this type of paranoid step should not be necessary. The use of this parameter should not be necessary. 
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564865"></a><a name="id2564867"></a><p><b>5.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564856"></a><a name="id2564858"></a><p><b>5.</b></p></td><td align="left" valign="top"><p>
 		Why does the <code class="filename">smb.conf</code> file in this exercise include an entry for <a class="link" href="smb.conf.5.html#SMBPORTS" target="_top">smb ports</a>?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The default order by which Samba-3 attempts to communicate with MS Windows clients is via port 445 (the TCP port
@@ -1785,7 +1785,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		specifying the use of only port 139, the intent is to reduce unsuccessful service connection attempts.
 		The result of this is improved network performance. Where Samba-3 is installed as an Active Directory Domain
 		member, the default behavior is highly beneficial and should not be changed.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564911"></a><a name="id2564914"></a><p><b>6.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564902"></a><a name="id2564905"></a><p><b>6.</b></p></td><td align="left" valign="top"><p>
 		What is the difference between a print queue and a printer?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		A printer is a physical device that is connected either directly to the network or to a computer 
@@ -1799,7 +1799,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		print requests. When the data stream has been fully received, the input stream is closed,
 		and the job is then submitted to a sequential print queue where the job is stored until
 		the printer is ready to receive the job.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564947"></a><a name="id2564949"></a><p><b>7.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564938"></a><a name="id2564940"></a><p><b>7.</b></p></td><td align="left" valign="top"><p>
 		Can all MS Windows application software be installed onto an application server share?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Much older Windows software is not compatible with installation to and execution from
@@ -1807,13 +1807,13 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		be installed to an application server. Retail consumer versions of Microsoft Office XP
 		Professional do not permit installation to an application server share and can be installed
 		and used only to/from a local workstation hard disk.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564972"></a><a name="id2564974"></a><p><b>8.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564963"></a><a name="id2564965"></a><p><b>8.</b></p></td><td align="left" valign="top"><p>
 		Why use dynamic DNS (DDNS)?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		When DDNS records are updated directly from the DHCP server, it is possible for
 		network clients that are not NetBIOS-enabled, and thus cannot use WINS, to locate
 		Windows clients via DNS.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564992"></a><a name="id2564994"></a><p><b>9.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2564983"></a><a name="id2564985"></a><p><b>9.</b></p></td><td align="left" valign="top"><p>
 		Why would you use WINS as well as DNS-based name resolution?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		WINS is to NetBIOS names as DNS is to fully qualified domain names (FQDN). The FQDN is
@@ -1821,7 +1821,7 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		means <code class="constant">top-level domain</code>. A FQDN is a longhand but easy-to-remember
 		expression that may be up to 1024 characters in length and that represents an IP address. 
 		A NetBIOS name is always 16 characters long. The 16<sup>th</sup> character
-		is a name type indicator. A specific name type is registered<sup>[<a name="id2565029" href="#ftn.id2565029" class="footnote">9</a>]</sup> for each 
+		is a name type indicator. A specific name type is registered<sup>[<a name="id2565020" href="#ftn.id2565020" class="footnote">9</a>]</sup> for each 
 		type of service that is provided by the Windows server or client and that may be registered
 		where a WINS server is in use.
 		</p><p>
@@ -1836,24 +1836,24 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
 		which it has control.
 		</p><p>
 		Windows 200x Active Directory requires the registration in the DNS zone for the domain it 
-		controls of service locator<sup>[<a name="id2565063" href="#ftn.id2565063" class="footnote">10</a>]</sup> records 
+		controls of service locator<sup>[<a name="id2565054" href="#ftn.id2565054" class="footnote">10</a>]</sup> records 
 		that Windows clients and servers will use to locate Kerberos and LDAP services. ADS also 
 		requires the registration of special records that are called global catalog (GC) entries 
 		and site entries by which domain controllers and other essential ADS servers may be located. 
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2565077"></a><a name="id2565079"></a><p><b>10.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2565068"></a><a name="id2565070"></a><p><b>10.</b></p></td><td align="left" valign="top"><p>
 		What are the major benefits of using an application server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The use of an application server can significantly reduce application update maintenance.
 		By providing a centralized application share, software updates need be applied to only
 		one location for all major applications used. This results in faster update roll-outs and
 		significantly better application usage control.
-		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2559623" href="#id2559623" class="para">5</a>] </sup>See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 3.
+		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2559616" href="#id2559616" class="para">5</a>] </sup>See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 3.
 		This is necessary so that Samba can act as a Domain Controller (PDC); see
-		<span class="emphasis"><em>TOSHARG2</em></span>, Chapter 4, for additional information.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2560004" href="#id2560004" class="para">6</a>] </sup>You may want to do the echo command last and include 
-				"0" in the init scripts, since it opens up your network for a short time.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2563592" href="#id2563592" class="para">7</a>] </sup>For more information regarding winbindd, see <span class="emphasis"><em>TOSHARG2</em></span>, 
+		<span class="emphasis"><em>TOSHARG2</em></span>, Chapter 4, for additional information.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2559997" href="#id2559997" class="para">6</a>] </sup>You may want to do the echo command last and include 
+				"0" in the init scripts, since it opens up your network for a short time.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2563584" href="#id2563584" class="para">7</a>] </sup>For more information regarding winbindd, see <span class="emphasis"><em>TOSHARG2</em></span>, 
 			Chapter 23, Section 23.3. The single instance of <code class="literal">smbd</code> is normal. One additional
 			<code class="literal">smbd</code> slave process is spawned for each SMB/CIFS client 
-			connection.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2564781" href="#id2564781" class="para">8</a>] </sup>Bench tests have shown that tdbsam is a very
+			connection.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2564772" href="#id2564772" class="para">8</a>] </sup>Bench tests have shown that tdbsam is a very
 		effective database technology.  There is surprisingly little performance loss even
-		with over 4000 users.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2565029" href="#id2565029" class="para">9</a>] </sup>
-		See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9, for more information.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2565063" href="#id2565063" class="para">10</a>] </sup>See TOSHARG2, Chapter 9, Section 9.3.3.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="small.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="ExNetworks.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="Big500users.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Small Office Networking�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�4.�The 500-User Office</td></tr></table></div></body></html>
+		with over 4000 users.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2565020" href="#id2565020" class="para">9</a>] </sup>
+		See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9, for more information.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2565054" href="#id2565054" class="para">10</a>] </sup>See TOSHARG2, Chapter 9, Section 9.3.3.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="small.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="ExNetworks.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="Big500users.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Small Office Networking�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�4.�The 500-User Office</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/simple.html b/docs/htmldocs/Samba3-ByExample/simple.html
index 08a0b91f32..466f10e7d6 100644
--- a/docs/htmldocs/Samba3-ByExample/simple.html
+++ b/docs/htmldocs/Samba3-ByExample/simple.html
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�No-Frills Samba Servers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="next" href="small.html" title="Chapter�2.�Small Office Networking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�No-Frills Samba Servers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ExNetworks.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="small.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="simple"></a>Chapter�1.�No-Frills Samba Servers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="simple.html#id2550843">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550883">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550925">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551634">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554969">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�No-Frills Samba Servers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="next" href="small.html" title="Chapter�2.�Small Office Networking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�No-Frills Samba Servers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ExNetworks.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="small.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="simple"></a>Chapter�1.�No-Frills Samba Servers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="simple.html#id2550837">Introduction</a></span></dt><dt><span class="sect1"><a href="simple.html#id2550877">Assignment Tasks</a></span></dt><dd><dl><dt><span class="sect2"><a href="simple.html#id2550918">Drafting Office</a></span></dt><dt><span class="sect2"><a href="simple.html#id2551628">Charity Administration Office</a></span></dt><dt><span class="sect2"><a href="simple.html#AccountingOffice">Accounting Office</a></span></dt></dl></dd><dt><span class="sect1"><a href="simple.html#id2554965">Questions and Answers</a></span></dt></dl></div><p>
 	This is the start of the real journey toward the successful deployment of Samba. For some this chapter
 	is the end of the road because their needs will have been adequately met. For others, this chapter is
 	the beginning of a journey that will take them well past the contents of this book. This book provides
 	example configurations of, for the greater part, complete networking solutions. The intent of this book
 	is to help you to get your Samba installation working with the least amount of pain and aggravation.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550843"></a>Introduction</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550837"></a>Introduction</h2></div></div></div><p>
 	This chapter lays the groundwork for understanding the basics of Samba operation. 
 	Instead of a bland technical discussion, each principle is demonstrated by way of a 
-	real-world scenario for which a working solution<sup>[<a name="id2550854" href="#ftn.id2550854" class="footnote">1</a>]</sup> is fully described.
+	real-world scenario for which a working solution<sup>[<a name="id2550848" href="#ftn.id2550848" class="footnote">1</a>]</sup> is fully described.
 	</p><p>
 	The practical exercises take you on a journey through a drafting office, a charity administration
 	office, and an accounting office. You may choose to apply any or all of these exercises to your own environment.
@@ -17,7 +17,7 @@
 	find much improved solutions compared with those presented here. By the time you complete this book,
 	you should aim to be a Samba expert, so do attempt to find better solutions and try them as you work your
 	way through the examples.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550883"></a>Assignment Tasks</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550877"></a>Assignment Tasks</h2></div></div></div><p>
 	Each case presented highlights different aspects of Windows networking for which a simple 
 	Samba-based solution can be provided. Each has subtly different requirements taken from real-world cases.
 	The cases are briefly reviewed to cover important points. Instructions are based
@@ -28,7 +28,7 @@
 	</p><div class="itemizedlist"><ul type="disc"><li><p>A drafting office</p></li><li><p>A charity administration office</p></li><li><p>An accounting office</p></li></ul></div><p>
 	</p><p>
 	Let's get started.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550925"></a>Drafting Office</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550918"></a>Drafting Office</h3></div></div></div><p>
 	Our fictitious company is called <span class="emphasis"><em>Abmas Design, Inc.</em></span> This is a three-person
 	computer-aided design (CAD) business that often has more work than can be handled. The 
 	business owner hires contract draftspeople from wherever he can. They bring their own 
@@ -38,15 +38,15 @@
 	plans that are stored on a central server one day per month. She knows how to upload 
 	plans from each machine. The files available from the server must remain read-only. 
 	Anyone should be able to access the plans at any time and without barriers or difficulty.
-	</p><p><a class="indexterm" name="id2550950"></a>
-		<a class="indexterm" name="id2550956"></a>
+	</p><p><a class="indexterm" name="id2550944"></a>
+		<a class="indexterm" name="id2550950"></a>
 	Mr. Bob Jordan has asked you to install the new server as economically as possible. The central
 	server has a Pentium-IV 1.6GHz CPU, 768MB RAM, a 20GB IDE boot drive, a 160GB IDE second disk
 	to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Fedora CoreX and
 	have upgraded Samba to version 3.0.20 using the RPM package that is provided from the Samba
 	<a class="ulink" href="http://www.samba.org" target="_top">FTP</a> sites. (Note: Fedora CoreX indicates your favorite
 	version.)
-	</p><p><a class="indexterm" name="id2550984"></a>
+	</p><p><a class="indexterm" name="id2550978"></a>
 	The four permanent drafting machines (Microsoft Windows workstations) have attached printers 
 	and plotters that are shared on a peer-to-peer basis by any and all network users. The intent 
 	is to continue to share printers in this manner. The three permanent staff work together with 
@@ -55,15 +55,15 @@
 	area is copied to the central server and the files are removed from the main weekly storage 
 	machine. The office works best with this arrangement and does not want to change anything. 
 	Old habits are too ingrained.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551005"></a>Dissection and Discussion</h4></div></div></div><p>
-		<a class="indexterm" name="id2551012"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550999"></a>Dissection and Discussion</h4></div></div></div><p>
+		<a class="indexterm" name="id2551006"></a>
 		The requirements for this server installation demand simplicity. An anonymous read-only
 		file server adequately meets all needs. The network consultant determines how
 		to upload all files from the weekly storage area to the server. This installation should
 		focus only on critical aspects of the installation.
 		</p><p>
 		It is not necessary to have specific users on the server. The site has a method for storing
-		all design files (plans). Each plan is stored in a directory that is named YYYYWW,<sup>[<a name="id2551032" href="#ftn.id2551032" class="footnote">2</a>]</sup> where
+		all design files (plans). Each plan is stored in a directory that is named YYYYWW,<sup>[<a name="id2551026" href="#ftn.id2551026" class="footnote">2</a>]</sup> where
 		YYYY is the year, and WW is the week of the year. This arrangement allows work to be stored
 		by week of year to preserve the filing technique the site is familiar with.
 		There is also a customer directory that is alphabetically listed. At the top level are 26
@@ -73,18 +73,18 @@
 		plans to be located both by customer name and by the date the work was performed, without
 		demanding the disk space that would be needed if a duplicate file copy were to be stored. 
 		The share containing the plans is called <span class="emphasis"><em>Plans</em></span>.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551061"></a>Implementation</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551055"></a>Implementation</h4></div></div></div><p>
 		It is assumed that the server is fully installed and ready for installation and 
 		configuration of Samba 3.0.20 and any support files needed. All TCP/IP addresses 
 		have been hard-coded. In our case the IP address of the Samba server is 
 		<code class="constant">192.168.1.1</code> and the netmask is <code class="constant">255.255.255.0</code>. 
 		The hostname of the server used is <code class="constant">server</code>.
-		</p><div class="procedure"><a name="id2551084"></a><p class="title"><b>Procedure�1.1.�Samba Server Configuration</b></p><ol type="1"><li><p>
+		</p><div class="procedure"><a name="id2551078"></a><p class="title"><b>Procedure�1.1.�Samba Server Configuration</b></p><ol type="1"><li><p>
 			Download the Samba-3 RPM packages for Red Hat Fedora Core2 from the Samba
 			<a class="ulink" href="http://www.samba.org" target="_top">FTP servers.</a>
 			</p></li><li><p>
-			<a class="indexterm" name="id2551108"></a>
-			<a class="indexterm" name="id2551116"></a>
+			<a class="indexterm" name="id2551102"></a>
+			<a class="indexterm" name="id2551110"></a>
 			Install the RPM package using either the Red Hat Linux preferred GUI
 			tool or the <code class="literal">rpm</code>:
 </p><pre class="screen">
@@ -100,7 +100,7 @@
 			The 755 permissions on this directory (mount point) permit the owner to read, write,
 			and execute, and the group and everyone else to read and execute only.
 			</p><p>
-			<a class="indexterm" name="id2551175"></a>
+			<a class="indexterm" name="id2551169"></a>
 			Use Red Hat Linux system tools (refer to Red Hat instructions)
 			to format the 160GB hard drive with a suitable file system. An Ext3 file system
 			is suitable. Configure this drive to automatically mount using the <code class="filename">/plans</code>
@@ -109,35 +109,35 @@
 			Install the <code class="filename">smb.conf</code> file shown in <a class="link" href="simple.html#draft-smbconf" title="Example�1.1.�Drafting Office smb.conf File">&#8220;Drafting Office smb.conf File&#8221;</a> in the
 			<code class="filename">/etc/samba</code> directory.
 
-</p><div class="example"><a name="draft-smbconf"></a><p class="title"><b>Example�1.1.�Drafting Office <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2551244"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2551254"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[Plans]</code></em></td></tr><tr><td><a class="indexterm" name="id2551273"></a><em class="parameter"><code>path = /plans</code></em></td></tr><tr><td><a class="indexterm" name="id2551283"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2551294"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="draft-smbconf"></a><p class="title"><b>Example�1.1.�Drafting Office <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2551238"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2551248"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[Plans]</code></em></td></tr><tr><td><a class="indexterm" name="id2551267"></a><em class="parameter"><code>path = /plans</code></em></td></tr><tr><td><a class="indexterm" name="id2551277"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2551288"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><p><br class="example-break">
 			</p></li><li><p>
-			<a class="indexterm" name="id2551311"></a>
+			<a class="indexterm" name="id2551305"></a>
 			Verify that the <code class="filename">/etc/hosts</code> file contains the following entry:
 </p><pre class="screen">
 192.168.1.1	server
 </pre><p>
 
 			</p></li><li><p>
-			<a class="indexterm" name="id2551335"></a>
+			<a class="indexterm" name="id2551329"></a>
+			<a class="indexterm" name="id2551337"></a>
 			<a class="indexterm" name="id2551344"></a>
-			<a class="indexterm" name="id2551350"></a>
 			Use the standard system tool to start Samba and to configure it to restart
 			automatically at every system reboot. For example,
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig smb on
 <code class="prompt">root# </code> /etc/rc.d/init.d/smb restart
 </pre><p>
-			</p></li></ol></div><div class="procedure"><a name="id2551376"></a><p class="title"><b>Procedure�1.2.�Windows Client Configuration</b></p><ol type="1"><li><p>
+			</p></li></ol></div><div class="procedure"><a name="id2551370"></a><p class="title"><b>Procedure�1.2.�Windows Client Configuration</b></p><ol type="1"><li><p>
 			Make certain that all clients are set to the same network address range as
 			used for the Samba server. For example, one client might have an IP
 			address 192.168.1.10.
 			</p></li><li><p>
-			<a class="indexterm" name="id2551396"></a>
+			<a class="indexterm" name="id2551390"></a>
 			Ensure that the netmask used on the Windows clients matches that used
 			for the Samba server. All clients must have the same netmask, such as
 			255.255.255.0.
 			</p></li><li><p>
-			<a class="indexterm" name="id2551412"></a>
+			<a class="indexterm" name="id2551405"></a>
 			Set the workgroup name on all clients to <code class="constant">MIDEARTH</code>.
 			</p></li><li><p>
 			Verify on each client that the machine called <code class="constant">SERVER</code>
@@ -145,15 +145,15 @@
 			possible to connect to it and see the share <span class="guimenuitem">Plans</span>,
 			and that it is possible to open that share to reveal its contents.
 			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="validate1"></a>Validation</h4></div></div></div><p>
-		<a class="indexterm" name="id2551458"></a>
+		<a class="indexterm" name="id2551452"></a>
 		The first priority in validating the new Samba configuration should be to check
 		that Samba answers on the loop-back interface. Then it is time to check that Samba
 		answers its own name correctly. Last, check that a client can connect to the Samba
 		server.
 		</p><div class="procedure"><ol type="1"><li><p>
+			<a class="indexterm" name="id2551471"></a>
 			<a class="indexterm" name="id2551477"></a>
-			<a class="indexterm" name="id2551483"></a>
-			<a class="indexterm" name="id2551490"></a>
+			<a class="indexterm" name="id2551484"></a>
 			To check the ability to access the <code class="literal">smbd</code> daemon
 			services, execute the following:
 </p><pre class="screen">
@@ -172,8 +172,8 @@
         ---------          --------
         MIDEARTH           SERVER 
 </pre><p>
+			<a class="indexterm" name="id2551515"></a>
 			<a class="indexterm" name="id2551521"></a>
-			<a class="indexterm" name="id2551527"></a>
 			This indicates that Samba is able to respond on the loopback interface to
 			a NULL connection. The <em class="parameter"><code>-U%</code></em> means send an empty
 			username and an empty password. This command should be repeated after
@@ -188,12 +188,12 @@
 			configured to ignore all usernames given; instead it uses the
 			<em class="parameter"><code>guest account</code></em> for all connections.
 			</p></li><li><p>
+			<a class="indexterm" name="id2551571"></a>
 			<a class="indexterm" name="id2551577"></a>
-			<a class="indexterm" name="id2551583"></a>
 			From the Windows 9x/Me client, launch Windows Explorer: 
 			<span class="guiicon">[Desktop: right-click] Network Neighborhood</span>+<span class="guimenu">Explore</span> &#8594; <span class="guimenuitem">[Left Panel]  [+] Entire Network</span> &#8594; <span class="guimenuitem">[Left Panel] [+] Server</span> &#8594; <span class="guimenuitem">[Left Panel] [+] Plans</span>. In the right panel you should see the files and directories
 			(folders) that are in the <span class="guiicon">Plans</span> share.
-			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551634"></a>Charity Administration Office</h3></div></div></div><p>
+			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551628"></a>Charity Administration Office</h3></div></div></div><p>
 	The fictitious charity organization is called <span class="emphasis"><em>Abmas Vision NL</em></span>. This office
 	has five networked computers. Staff are all volunteers, staff changes are frequent.
 	Ms. Amy May, the director of operations, wants a no-hassle network. Anyone should be able to
@@ -216,8 +216,8 @@
 	that if the share name is not in lowercase, the application claims it cannot find the
 	file share.
 	</p><p>
+	<a class="indexterm" name="id2551691"></a>
 	<a class="indexterm" name="id2551697"></a>
-	<a class="indexterm" name="id2551703"></a>
 	Printer handling in Samba results in a significant level of confusion. Samba presents to the
 	MS Windows client only a print queue. The Samba <code class="literal">smbd</code> process passes a
 	print job sent to it from the Windows client to the native UNIX printing system. The native
@@ -231,7 +231,7 @@
 	to prevent leakage of confidential information. Only the five PCs owned by Abmas Vision NL are
 	used on this network.
 	</p><p>
-	<a class="indexterm" name="id2551736"></a>
+	<a class="indexterm" name="id2551730"></a>
 	The central server was donated by a local computer store. It is a dual processor Pentium-III
 	server, has 1GB RAM, a 3-Ware IDE RAID Controller that has four 200GB IDE hard drives, and a
 	100-base-T network card. The office has 100-base-T permanent network connections that go to
@@ -242,11 +242,11 @@
 	office and letter printing. Your recommendation to allow only the Linux server to print directly
 	to the printers was accepted. You have supplied SUSE Enterprise Linux Server 9 and
 	have upgraded Samba to version 3.0.20.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551758"></a>Dissection and Discussion</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551752"></a>Dissection and Discussion</h4></div></div></div><p>
+		<a class="indexterm" name="id2551759"></a>
 		<a class="indexterm" name="id2551766"></a>
 		<a class="indexterm" name="id2551772"></a>
 		<a class="indexterm" name="id2551778"></a>
-		<a class="indexterm" name="id2551784"></a>
 		This installation demands simplicity. Frequent turnover of volunteer staff indicates that
 		a network environment that requires users to logon might be problematic. It is suggested that the
 		best solution for this office would be one where the user can log onto any PC with any username
@@ -258,26 +258,26 @@
 		access control lists (Posix type) cannot be written to any file or directory. This prevents
 		an inadvertent ACL from overriding actual file permissions.
 		</p><p>
-		<a class="indexterm" name="id2551823"></a>
+		<a class="indexterm" name="id2551817"></a>
+		<a class="indexterm" name="id2551824"></a>
 		<a class="indexterm" name="id2551830"></a>
-		<a class="indexterm" name="id2551836"></a>
 		This organization is a prime candidate for Share Mode security. The <em class="parameter"><code>force user</code></em>
 		allows all files to be owned by the same user and group. In addition, it would not hurt to
 		set SUID and set SGID shared directories. This means that all new files that are created, no matter
 		who creates it, are owned by the owner or group of the directory in which they are created.
 		For further information regarding the significance of the SUID/SGID settings, see <a class="link" href="appendix.html" title="Chapter�15.�A Collection of Useful Tidbits">&#8220;A Collection of Useful Tidbits&#8221;</a>, <a class="link" href="appendix.html#ch12-SUIDSGID" title="Effect of Setting File and Directory SUID/SGID Permissions Explained">&#8220;Effect of Setting File and Directory SUID/SGID Permissions Explained&#8221;</a>.
 		</p><p>
+		<a class="indexterm" name="id2551863"></a>
 		<a class="indexterm" name="id2551869"></a>
-		<a class="indexterm" name="id2551875"></a>
-		<a class="indexterm" name="id2551883"></a>
-		<a class="indexterm" name="id2551890"></a>
+		<a class="indexterm" name="id2551877"></a>
+		<a class="indexterm" name="id2551884"></a>
 		All client workstations print to a print queue on the server. This ensures that print jobs
 		continue to print in the event that a user shuts down the workstation immediately after
 		sending a job to the printer. Today, both Red Hat Linux and SUSE Linux use CUPS-based printing. 
 		Older Linux systems offered a choice between the LPRng printing system or CUPS. It appears, however,
 		that CUPS has become the leading UNIX printing technology.
 		</p><p>
-		<a class="indexterm" name="id2551907"></a>
+		<a class="indexterm" name="id2551901"></a>
 		The print queues are set up as <code class="constant">Raw</code> devices, which means that CUPS will 
 		not do intelligent print processing, and vendor-supplied drivers must be installed locally on the 
 		Windows clients.
@@ -297,21 +297,21 @@
 		printer. In this example, therefore, the resource called <code class="constant">PRINTQ</code>
 		really is just a print queue. The name of the print queue is representative of
 		the device to which the print spooler delivers print jobs.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551953"></a>Implementation</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551947"></a>Implementation</h4></div></div></div><p>
 		It is assumed that the server is fully installed and ready for configuration of
 		Samba 3.0.20 and for necessary support files. All TCP/IP addresses should be hard-coded.
 		In our case, the IP address of the Samba server is 192.168.1.1 and the netmask is
 		255.255.255.0. The hostname of the server used is <code class="constant">server</code>.
 		The office network is built as shown in <a class="link" href="simple.html#charitynet" title="Figure�1.1.�Charity Administration Office Network">&#8220;Charity Administration Office Network&#8221;</a>.
-		</p><div class="figure"><a name="charitynet"></a><p class="title"><b>Figure�1.1.�Charity Administration Office Network</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Charity-Network.png" width="432" alt="Charity Administration Office Network"></div></div></div><br class="figure-break"><div class="procedure"><a name="id2552014"></a><p class="title"><b>Procedure�1.3.�Samba Server Configuration</b></p><ol type="1"><li><p>
-			<a class="indexterm" name="id2552024"></a>
+		</p><div class="figure"><a name="charitynet"></a><p class="title"><b>Figure�1.1.�Charity Administration Office Network</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Charity-Network.png" width="432" alt="Charity Administration Office Network"></div></div></div><br class="figure-break"><div class="procedure"><a name="id2552008"></a><p class="title"><b>Procedure�1.3.�Samba Server Configuration</b></p><ol type="1"><li><p>
+			<a class="indexterm" name="id2552018"></a>
 			Create a group account for office file storage:
 </p><pre class="screen">
 <code class="prompt">root# </code> groupadd office
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2552048"></a>
-			<a class="indexterm" name="id2552055"></a>
+			<a class="indexterm" name="id2552042"></a>
+			<a class="indexterm" name="id2552049"></a>
 			Create a user account for office file storage:
 </p><pre class="screen">
 <code class="prompt">root# </code> useradd -m abmas 
@@ -328,7 +328,7 @@ Password changed
 				(Refer to the 3-Ware RAID Controller Manual for the manufacturer's preferred procedure.)
 				The resulting drive has a capacity of approximately 500GB of usable space.
 				</p></li><li><p>
-				<a class="indexterm" name="id2552099"></a>
+				<a class="indexterm" name="id2552093"></a>
 				Create a mount point for the file system that can be used to store all data files.
 				Create a directory called <code class="filename">/data</code>:
 </p><pre class="screen">
@@ -360,7 +360,7 @@ Password changed
 /data/officefiles/invitations
 /data/officefiles/misc
 </pre><p>
-				<a class="indexterm" name="id2552207"></a>
+				<a class="indexterm" name="id2552201"></a>
 				The <code class="literal">chown</code> operation sets the owner to the user <code class="constant">abmas</code>
 				and the group to <code class="constant">office</code> on all directories just created.  It recursively
 				sets the permissions so that the owner and group have SUID/SGID with read, write, and execute
@@ -368,7 +368,7 @@ Password changed
 				directories are created with the same owner and group as the directory in which they are
 				created. Any new directories created still have the same owner, group, and permissions as the
 				directory they are in. This should eliminate all permissions-based file access problems.  For
-				more information on this subject, refer to TOSHARG2<sup>[<a name="id2552236" href="#ftn.id2552236" class="footnote">3</a>]</sup> or refer
+				more information on this subject, refer to TOSHARG2<sup>[<a name="id2552230" href="#ftn.id2552230" class="footnote">3</a>]</sup> or refer
 				to the UNIX man page for the <code class="literal">chmod</code> and the <code class="literal">chown</code> commands.
 				</p></li><li><p>
 				Install the <code class="filename">smb.conf</code> file shown in <a class="link" href="simple.html#charity-smbconfnew" title="Example�1.2.�Charity Administration Office smb.conf New-style File">&#8220;Charity Administration Office smb.conf New-style File&#8221;</a> in the
@@ -380,7 +380,7 @@ Password changed
 				can install the file shown in <a class="link" href="simple.html#charity-smbconf" title="Example�1.3.�Charity Administration Office smb.conf Old-style File">&#8220;Charity Administration Office smb.conf Old-style File&#8221;</a> in the
 				<code class="filename">/etc/samba</code> directory.
 				</p></li><li><p>
-				<a class="indexterm" name="id2552304"></a>
+				<a class="indexterm" name="id2552297"></a>
 				We must ensure that the <code class="literal">smbd</code> can resolve the name of the Samba
 				server to its IP address. Verify that the <code class="filename">/etc/hosts</code> file
 				contains the following entry:
@@ -392,7 +392,7 @@ Password changed
 				Follow the instructions in the manufacturer's manual to permit printing to port 9100
 				so that the CUPS spooler can print using raw mode protocols.
 				</p></li><li><p>
-				<a class="indexterm" name="id2552349"></a>
+				<a class="indexterm" name="id2552342"></a>
 				Configure the CUPS Print Queues:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p PRINTQ -v socket://192.168.1.20:9100 -E
@@ -400,61 +400,61 @@ Password changed
 </pre><p>
 				This creates the necessary print queues with no assigned print filter.
 				</p></li><li><p>
-				<a class="indexterm" name="id2552381"></a>
-				<a class="indexterm" name="id2552388"></a>
-				<a class="indexterm" name="id2552394"></a>
+				<a class="indexterm" name="id2552374"></a>
+				<a class="indexterm" name="id2552380"></a>
+				<a class="indexterm" name="id2552386"></a>
 				Edit the file <code class="filename">/etc/cups/mime.convs</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
 				</p></li><li><p>
-				<a class="indexterm" name="id2552418"></a>
+				<a class="indexterm" name="id2552411"></a>
 				Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
 </pre><p>
 				</p></li><li><p>
-				<a class="indexterm" name="id2552441"></a>
+				<a class="indexterm" name="id2552434"></a>
 				Use the standard system tool to start Samba and CUPS to configure them to restart
 				automatically at every system reboot. For example,
 				</p><p>
-				<a class="indexterm" name="id2552453"></a>
-				<a class="indexterm" name="id2552459"></a>
-				<a class="indexterm" name="id2552466"></a>
+				<a class="indexterm" name="id2552446"></a>
+				<a class="indexterm" name="id2552452"></a>
+				<a class="indexterm" name="id2552458"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig smb on
 <code class="prompt">root# </code> chkconfig cups on
 <code class="prompt">root# </code> /etc/rc.d/init.d/smb restart
 <code class="prompt">root# </code> /etc/rc.d/init.d/cups restart
 </pre><p>
-				</p></li></ol></div><div class="example"><a name="charity-smbconfnew"></a><p class="title"><b>Example�1.2.�Charity Administration Office <code class="filename">smb.conf</code> New-style File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters - Newer Configuration</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552530"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2552540"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552551"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552561"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2552572"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552582"></a><em class="parameter"><code>wins support = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[FTMFILES]</code></em></td></tr><tr><td><a class="indexterm" name="id2552601"></a><em class="parameter"><code>comment = Funds Tracking &amp; Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552612"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552623"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552633"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552644"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552654"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552664"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2552683"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552694"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552704"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552714"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552725"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552735"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552746"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2552764"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2552776"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2552786"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552796"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552807"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552817"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="charity-smbconf"></a><p class="title"><b>Example�1.3.�Charity Administration Office <code class="filename">smb.conf</code> Old-style File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters - Older Style Configuration</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552859"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2552869"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2552880"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552890"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552901"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552911"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552921"></a><em class="parameter"><code>wins support = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[FTMFILES]</code></em></td></tr><tr><td><a class="indexterm" name="id2552940"></a><em class="parameter"><code>comment = Funds Tracking &amp; Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552952"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552962"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552972"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552983"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552993"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553004"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2553022"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2553033"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2553043"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2553054"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2553064"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2553074"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553085"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2553104"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2553115"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2553125"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553136"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553146"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553157"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="procedure"><a name="id2553168"></a><p class="title"><b>Procedure�1.4.�Windows Client Configuration</b></p><ol type="1"><li><p>
+				</p></li></ol></div><div class="example"><a name="charity-smbconfnew"></a><p class="title"><b>Example�1.2.�Charity Administration Office <code class="filename">smb.conf</code> New-style File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters - Newer Configuration</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552523"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2552533"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552544"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552554"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2552564"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552575"></a><em class="parameter"><code>wins support = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[FTMFILES]</code></em></td></tr><tr><td><a class="indexterm" name="id2552594"></a><em class="parameter"><code>comment = Funds Tracking &amp; Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552605"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552615"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552626"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552636"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552647"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552657"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2552676"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552686"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552697"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552707"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552717"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552728"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552738"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2552757"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2552768"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2552779"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552789"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552800"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552810"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="charity-smbconf"></a><p class="title"><b>Example�1.3.�Charity Administration Office <code class="filename">smb.conf</code> Old-style File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global Parameters - Older Style Configuration</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552852"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2552862"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2552872"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552883"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2552893"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552904"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552914"></a><em class="parameter"><code>wins support = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[FTMFILES]</code></em></td></tr><tr><td><a class="indexterm" name="id2552933"></a><em class="parameter"><code>comment = Funds Tracking &amp; Management Files</code></em></td></tr><tr><td><a class="indexterm" name="id2552944"></a><em class="parameter"><code>path = /data/ftmfiles</code></em></td></tr><tr><td><a class="indexterm" name="id2552955"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2552965"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2552976"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2552986"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2552996"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2553015"></a><em class="parameter"><code>comment = General Office Files</code></em></td></tr><tr><td><a class="indexterm" name="id2553026"></a><em class="parameter"><code>path = /data/officefiles</code></em></td></tr><tr><td><a class="indexterm" name="id2553036"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2553046"></a><em class="parameter"><code>force user = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2553057"></a><em class="parameter"><code>force group = office</code></em></td></tr><tr><td><a class="indexterm" name="id2553067"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553078"></a><em class="parameter"><code>nt acl support = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2553096"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2553108"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2553118"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553128"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553139"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2553149"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="procedure"><a name="id2553161"></a><p class="title"><b>Procedure�1.4.�Windows Client Configuration</b></p><ol type="1"><li><p>
 				Configure clients to the network settings shown in <a class="link" href="simple.html#charitynet" title="Figure�1.1.�Charity Administration Office Network">&#8220;Charity Administration Office Network&#8221;</a>.
 				</p></li><li><p>
 				Ensure that the netmask used on the Windows clients matches that used
 				for the Samba server. All clients must have the same netmask, such as
 				<code class="constant">255.255.255.0</code>.
 				</p></li><li><p>
-				<a class="indexterm" name="id2553202"></a>
+				<a class="indexterm" name="id2553195"></a>
 				On all Windows clients, set the WINS Server address to <code class="constant">192.168.1.1</code>,
 				the IP address of the server.
 				</p></li><li><p>
 				Set the workgroup name on all clients to <code class="constant">MIDEARTH</code>.
 				</p></li><li><p>
-				<a class="indexterm" name="id2553230"></a>
+				<a class="indexterm" name="id2553223"></a>
 				Install the &#8220;<span class="quote">Client for Microsoft Networks.</span>&#8221; Ensure that the only option
 				enabled in its properties is the option &#8220;<span class="quote">Logon and restore network connections.</span>&#8221;
 				</p></li><li><p>
 				Click <span class="guibutton">OK</span> when you are prompted to reboot the system. Reboot the
 				system, then log on using any username and password you choose.
 				</p></li><li><p>
-				<a class="indexterm" name="id2553265"></a>
+				<a class="indexterm" name="id2553258"></a>
 				Verify on each client that the machine called <code class="constant">SERVER</code>
 				is visible in <span class="guimenu">My Network Places</span>, that it is
 				possible to connect to it and see the share <span class="guimenuitem">office</span>,
 				and that it is possible to open that share to reveal its contents.
 				</p></li><li><p>
-				<a class="indexterm" name="id2553295"></a>
-				<a class="indexterm" name="id2553301"></a>
+				<a class="indexterm" name="id2553288"></a>
+				<a class="indexterm" name="id2553294"></a>
 				Disable password caching on all Windows 9x/Me machines using the registry change file
 				shown in <a class="link" href="simple.html#MEreg" title="Example�1.4.�Windows Me Registry Edit File: Disable Password Caching">&#8220;Windows Me  Registry Edit File: Disable Password Caching&#8221;</a>. Be sure to remove all files that have the
 				<code class="filename">PWL</code> extension that are in the <code class="filename">C:\WINDOWS</code>
@@ -480,7 +480,7 @@ C:\WINDOWS: regedit ME-dpwc.reg
 				that redirects to the uniform naming convention (UNC) resource 
 				<code class="filename">\\server\office</code>. Make this a permanent drive connection:
 				</p><div class="procedure"><ol type="1"><li><p>
-								Right-click <span class="guimenu">My Network</span> &#8594; <span class="guimenuitem">Map Network Drive...</span>
+							<span class="guimenu">My Network</span> &#8594; <span class="guimenuitem">Map Network Drive...</span>
 						</p></li><li><p>
 						In the box labeled &#8220;<span class="quote">Drive:</span>&#8221;, type G.
 						</p></li><li><p>
@@ -532,7 +532,7 @@ C:\WINDOWS: regedit ME-dpwc.reg
 						It is a good idea to test the functionality of the complete installation before
 						handing the newly configured network over to the Charity Administration Office
 						for production use.
-						</p></li></ol></div></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553705"></a>Validation</h4></div></div></div><p>
+						</p></li></ol></div></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553699"></a>Validation</h4></div></div></div><p>
 		Use the same validation process as was followed in <a class="link" href="simple.html#validate1" title="Validation">&#8220;Validation&#8221;</a>.
 		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="AccountingOffice"></a>Accounting Office</h3></div></div></div><p>
 	Abmas Accounting is a 40-year-old family-run business. There are nine permanent
@@ -551,7 +551,7 @@ C:\WINDOWS: regedit ME-dpwc.reg
 	and enter an assigned password; they do not need to enter a password when accessing their files 
 	on the server.
 	</p><p>
-	<a class="indexterm" name="id2553768"></a>
+	<a class="indexterm" name="id2553763"></a>
 	The new server will run Red Hat Fedora Core2. You should install Samba-3.0.20 and 
 	copy all files from the old system to the new one. The existing Windows NT4 server has a parallel
 	port HP LaserJet 4 printer that is shared by all. The printer driver is installed on each
@@ -561,8 +561,8 @@ C:\WINDOWS: regedit ME-dpwc.reg
 	You have tried to educate Mr. Meany and found that he has no desire to understand networking.
 	He believes that Windows for Workgroups 3.11 was &#8220;<span class="quote">the best server Microsoft ever sold
 	</span>&#8221; and that Windows NT and 2000 are &#8220;<span class="quote">too fang-dangled complex!</span>&#8221;
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553799"></a>Dissection and Discussion</h4></div></div></div><p>
-			<a class="indexterm" name="id2553807"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553794"></a>Dissection and Discussion</h4></div></div></div><p>
+			<a class="indexterm" name="id2553802"></a>
 			The requirements of this network installation are not unusual. The staff are not interested in the
 			details of networking. Passwords are never changed. In this example solution, we demonstrate the use
 			of User Mode security in a simple context. Directories should be set SGID to ensure that members
@@ -582,7 +582,7 @@ C:\WINDOWS: regedit ME-dpwc.reg
 		share name is given in <a class="link" href="simple.html#acctingnet" title="Table�1.1.�Accounting Office Network Information">&#8220;Accounting Office Network Information&#8221;</a>. The overall network topology is shown in
 		<a class="link" href="simple.html#acctingnet2" title="Figure�1.2.�Accounting Office Network Topology">&#8220;Accounting Office Network Topology&#8221;</a>. All machines have been configured as indicated prior to the
 		start of Samba configuration. The following prescriptive steps may now commence.
-		</p><div class="figure"><a name="acctingnet2"></a><p class="title"><b>Figure�1.2.�Accounting Office Network Topology</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/AccountingNetwork.png" width="459" alt="Accounting Office Network Topology"></div></div></div><br class="figure-break"><div class="table"><a name="acctingnet"></a><p class="title"><b>Table�1.1.�Accounting Office Network Information</b></p><div class="table-contents"><table summary="Accounting Office Network Information" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">User</th><th align="left">Login-ID</th><th align="left">Password</th><th align="left">Share Name</th><th align="left">Directory</th><th align="left">Wkst</th></tr></thead><tbody><tr><td align="left">Alan Meany</td><td align="left">alan</td><td align="left">alm1961</td><td align="left">alan</td><td align="left">/data</td><td align="left">PC1</td></tr><tr><td align="left">James Meany</td><td align="left">james</td><td align="left">jimm1962</td><td align="left">james</td><td align="left">/data/james</td><td align="left">PC2</td></tr><tr><td align="left">Jeannie Meany</td><td align="left">jeannie</td><td align="left">jema1965</td><td align="left">jeannie</td><td align="left">/data/jeannie</td><td align="left">PC3</td></tr><tr><td align="left">Suzy Millicent</td><td align="left">suzy</td><td align="left">suzy1967</td><td align="left">suzy</td><td align="left">/data/suzy</td><td align="left">PC4</td></tr><tr><td align="left">Ursula Jenning</td><td align="left">ujen</td><td align="left">ujen1974</td><td align="left">ursula</td><td align="left">/data/ursula</td><td align="left">PC5</td></tr><tr><td align="left">Peter Pan</td><td align="left">peter</td><td align="left">pete1984</td><td align="left">peter</td><td align="left">/data/peter</td><td align="left">PC6</td></tr><tr><td align="left">Dale Roland</td><td align="left">dale</td><td align="left">dale1986</td><td align="left">dale</td><td align="left">/data/dale</td><td align="left">PC7</td></tr><tr><td align="left">Bertrand E Paoletti</td><td align="left">eric</td><td align="left">eric1993</td><td align="left">eric</td><td align="left">/data/eric</td><td align="left">PC8</td></tr><tr><td align="left">Russell Lewis</td><td align="left">russ</td><td align="left">russ2001</td><td align="left">russell</td><td align="left">/data/russell</td><td align="left">PC9</td></tr></tbody></table></div></div><br class="table-break"><div class="procedure"><a name="id2554178"></a><p class="title"><b>Procedure�1.5.�Migration from Windows NT4 Workstation System to Samba-3</b></p><ol type="1"><li><p><a class="indexterm" name="id2554188"></a>
+		</p><div class="figure"><a name="acctingnet2"></a><p class="title"><b>Figure�1.2.�Accounting Office Network Topology</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/AccountingNetwork.png" width="459" alt="Accounting Office Network Topology"></div></div></div><br class="figure-break"><div class="table"><a name="acctingnet"></a><p class="title"><b>Table�1.1.�Accounting Office Network Information</b></p><div class="table-contents"><table summary="Accounting Office Network Information" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">User</th><th align="left">Login-ID</th><th align="left">Password</th><th align="left">Share Name</th><th align="left">Directory</th><th align="left">Wkst</th></tr></thead><tbody><tr><td align="left">Alan Meany</td><td align="left">alan</td><td align="left">alm1961</td><td align="left">alan</td><td align="left">/data</td><td align="left">PC1</td></tr><tr><td align="left">James Meany</td><td align="left">james</td><td align="left">jimm1962</td><td align="left">james</td><td align="left">/data/james</td><td align="left">PC2</td></tr><tr><td align="left">Jeannie Meany</td><td align="left">jeannie</td><td align="left">jema1965</td><td align="left">jeannie</td><td align="left">/data/jeannie</td><td align="left">PC3</td></tr><tr><td align="left">Suzy Millicent</td><td align="left">suzy</td><td align="left">suzy1967</td><td align="left">suzy</td><td align="left">/data/suzy</td><td align="left">PC4</td></tr><tr><td align="left">Ursula Jenning</td><td align="left">ujen</td><td align="left">ujen1974</td><td align="left">ursula</td><td align="left">/data/ursula</td><td align="left">PC5</td></tr><tr><td align="left">Peter Pan</td><td align="left">peter</td><td align="left">pete1984</td><td align="left">peter</td><td align="left">/data/peter</td><td align="left">PC6</td></tr><tr><td align="left">Dale Roland</td><td align="left">dale</td><td align="left">dale1986</td><td align="left">dale</td><td align="left">/data/dale</td><td align="left">PC7</td></tr><tr><td align="left">Bertrand E Paoletti</td><td align="left">eric</td><td align="left">eric1993</td><td align="left">eric</td><td align="left">/data/eric</td><td align="left">PC8</td></tr><tr><td align="left">Russell Lewis</td><td align="left">russ</td><td align="left">russ2001</td><td align="left">russell</td><td align="left">/data/russell</td><td align="left">PC9</td></tr></tbody></table></div></div><br class="table-break"><div class="procedure"><a name="id2554172"></a><p class="title"><b>Procedure�1.5.�Migration from Windows NT4 Workstation System to Samba-3</b></p><ol type="1"><li><p><a class="indexterm" name="id2554183"></a>
 			Rename the old server from <code class="constant">CASHPOOL</code> to <code class="constant">STABLE</code>
 			by logging onto the console as the <code class="constant">Administrator</code>. Restart the machine
 			following system prompts.
@@ -593,19 +593,19 @@ C:\WINDOWS: regedit ME-dpwc.reg
 			Install the latest Samba-3 binary Red Hat Linux RPM that is available from the
 			Samba FTP site.
 			</p></li><li><p>
-			<a class="indexterm" name="id2554234"></a>
-			<a class="indexterm" name="id2554240"></a>
+			<a class="indexterm" name="id2554228"></a>
+			<a class="indexterm" name="id2554235"></a>
 			Add a group account for the office to use. Execute the following:
 </p><pre class="screen">
 <code class="prompt">root# </code> groupadd accts
 </pre><p>
 			</p></li><li><p>
-			Install the <code class="filename">smb.conf</code> file shown<sup>[<a name="id2554269" href="#ftn.id2554269" class="footnote">4</a>]</sup> 
+			Install the <code class="filename">smb.conf</code> file shown<sup>[<a name="id2554264" href="#ftn.id2554264" class="footnote">4</a>]</sup> 
 			in <a class="link" href="simple.html#acctconf" title="Example�1.5.�Accounting Office Network smb.conf Old Style Configuration File">&#8220;Accounting Office Network smb.conf Old Style Configuration File&#8221;</a>.
 			</p></li><li><p>
-			<a class="indexterm" name="id2554302"></a>
-			<a class="indexterm" name="id2554308"></a>
-			<a class="indexterm" name="id2554314"></a>
+			<a class="indexterm" name="id2554297"></a>
+			<a class="indexterm" name="id2554303"></a>
+			<a class="indexterm" name="id2554309"></a>
 			For each user who uses this system (see <a class="link" href="simple.html#acctingnet" title="Table�1.1.�Accounting Office Network Information">&#8220;Accounting Office Network Information&#8221;</a>),
 			execute the following:
 </p><pre class="screen">
@@ -620,7 +620,7 @@ Retype new SMB password: XXXXXXXXX
 Added user "LoginID"
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2554363"></a>
+			<a class="indexterm" name="id2554359"></a>
 			Create the directory structure for the file shares by executing the following:
 </p><pre class="screen">
 <code class="prompt">root# </code> mkdir -p /data
@@ -635,34 +635,34 @@ Added user "LoginID"
 </pre><p>
 			The data storage structure is now prepared for use.
 			</p></li><li><p>
-			<a class="indexterm" name="id2554412"></a>
+			<a class="indexterm" name="id2554408"></a>
 			Configure the CUPS Print Queues:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p hplj -v parallel:/dev/lp0 -E
 </pre><p>
 			This creates the necessary print queues with no assigned print filter.
 			</p></li><li><p>
-			<a class="indexterm" name="id2554438"></a>
-			<a class="indexterm" name="id2554444"></a>
+			<a class="indexterm" name="id2554434"></a>
+			<a class="indexterm" name="id2554440"></a>
 			Edit the file <code class="filename">/etc/cups/mime.convs</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2554468"></a>
-			<a class="indexterm" name="id2554474"></a>
+			<a class="indexterm" name="id2554464"></a>
+			<a class="indexterm" name="id2554470"></a>
 			Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
 </pre><p>
 			</p></li><li><p>
-			<a class="indexterm" name="id2554497"></a>
+			<a class="indexterm" name="id2554493"></a>
 			Use the standard system tool to start Samba and CUPS to configure them to restart
 			automatically at every system reboot. For example,
 			</p><p>
-			<a class="indexterm" name="id2554509"></a>
-			<a class="indexterm" name="id2554516"></a>
-			<a class="indexterm" name="id2554522"></a>
+			<a class="indexterm" name="id2554505"></a>
+			<a class="indexterm" name="id2554512"></a>
+			<a class="indexterm" name="id2554518"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig smb on
 <code class="prompt">root# </code> chkconfig cups on
@@ -707,40 +707,40 @@ application/octet-stream
 			The migration of all data should now be complete. It is time to validate the installation.
 			For this, you should make sure all applications, including printing, work before asking the
 			customer to test drive the new network.
-			</p></li></ol></div><div class="example"><a name="acctconf"></a><p class="title"><b>Example�1.5.�Accounting Office Network <code class="filename">smb.conf</code> Old Style Configuration File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554750"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2554761"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2554771"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554781"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554792"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[files]</code></em></td></tr><tr><td><a class="indexterm" name="id2554811"></a><em class="parameter"><code>comment = Work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2554822"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2554832"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[master]</code></em></td></tr><tr><td><a class="indexterm" name="id2554851"></a><em class="parameter"><code>comment = Master work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2554862"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2554872"></a><em class="parameter"><code>valid users = alan</code></em></td></tr><tr><td><a class="indexterm" name="id2554883"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2554902"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2554913"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2554923"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554934"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554944"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554954"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554969"></a>Questions and Answers</h2></div></div></div><p>
+			</p></li></ol></div><div class="example"><a name="acctconf"></a><p class="title"><b>Example�1.5.�Accounting Office Network <code class="filename">smb.conf</code> Old Style Configuration File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554746"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2554757"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2554767"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554778"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554789"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[files]</code></em></td></tr><tr><td><a class="indexterm" name="id2554807"></a><em class="parameter"><code>comment = Work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2554818"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2554828"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[master]</code></em></td></tr><tr><td><a class="indexterm" name="id2554847"></a><em class="parameter"><code>comment = Master work area files</code></em></td></tr><tr><td><a class="indexterm" name="id2554858"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2554868"></a><em class="parameter"><code>valid users = alan</code></em></td></tr><tr><td><a class="indexterm" name="id2554879"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2554898"></a><em class="parameter"><code>comment = Print Temporary Spool Configuration</code></em></td></tr><tr><td><a class="indexterm" name="id2554909"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2554919"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554930"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554940"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554951"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554965"></a>Questions and Answers</h2></div></div></div><p>
 	The following questions and answers draw from the examples in this chapter.
 	Many design decisions are impacted by the configurations chosen. The intent
 	is to expose some of the hidden implications.
-	</p><div class="qandaset"><dl><dt> <a href="simple.html#id2554987">
+	</p><div class="qandaset"><dl><dt> <a href="simple.html#id2554983">
 		What makes an anonymous Samba server more simple than a non-anonymous Samba server?
-		</a></dt><dt> <a href="simple.html#id2555013">
+		</a></dt><dt> <a href="simple.html#id2555009">
 		How is the operation of the parameter force user different from
 		setting the root directory of the share SUID?
-		</a></dt><dt> <a href="simple.html#id2555064">
+		</a></dt><dt> <a href="simple.html#id2555060">
 		When would you both use the per share parameter force user and set
 		the share root directory SUID?
-		</a></dt><dt> <a href="simple.html#id2555091">
+		</a></dt><dt> <a href="simple.html#id2555087">
 		What is better about CUPS printing than LPRng printing?
-		</a></dt><dt> <a href="simple.html#id2555135">
+		</a></dt><dt> <a href="simple.html#id2555131">
 		When should Windows client IP addresses be hard-coded?
-		</a></dt><dt> <a href="simple.html#id2555161">
+		</a></dt><dt> <a href="simple.html#id2555157">
 		Under what circumstances is it best to use a DHCP server?
-		</a></dt><dt> <a href="simple.html#id2555200">
+		</a></dt><dt> <a href="simple.html#id2555196">
 		What is the purpose of setting the parameter guest ok on a share?
-		</a></dt><dt> <a href="simple.html#id2555224">
+		</a></dt><dt> <a href="simple.html#id2555220">
 		When would you set the global parameter disable spoolss?
-		</a></dt><dt> <a href="simple.html#id2555310">
+		</a></dt><dt> <a href="simple.html#id2555306">
 		Why would you disable password caching on Windows 9x/Me clients?
-		</a></dt><dt> <a href="simple.html#id2555334">
+		</a></dt><dt> <a href="simple.html#id2555330">
 		The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2554987"></a><a name="id2554989"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2554983"></a><a name="id2554986"></a></td><td align="left" valign="top"><p>
 		What makes an anonymous Samba server more simple than a non-anonymous Samba server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		In the anonymous server, the only account used is the <code class="constant">guest</code> account.
 		In a non-anonymous configuration, it is necessary to add real user accounts to both the
 		UNIX system and to the Samba configuration. Non-anonymous servers require additional
 		administration.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555013"></a><a name="id2555015"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555009"></a><a name="id2555011"></a></td><td align="left" valign="top"><p>
 		How is the operation of the parameter <em class="parameter"><code>force user</code></em> different from
 		setting the root directory of the share SUID?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -754,14 +754,14 @@ application/octet-stream
 		</p><p>
 		The parameter <em class="parameter"><code>force user</code></em> has potential security implications that go
 		beyond the actual share root directory. Be careful and wary of using this parameter.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555064"></a><a name="id2555066"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555060"></a><a name="id2555062"></a></td><td align="left" valign="top"><p>
 		When would you both use the per share parameter <em class="parameter"><code>force user</code></em> and set
 		the share root directory SUID?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		You would use both parameters when it is necessary to guarantee that all share handling operations
 		are conducted as the forced user, while all file and directory creation are done as the SUID
 		directory owner.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555091"></a><a name="id2555093"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555087"></a><a name="id2555089"></a></td><td align="left" valign="top"><p>
 		What is better about CUPS printing than LPRng printing?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		CUPS is a print spooling system that has integrated remote management facilities, provides completely
@@ -779,7 +779,7 @@ application/octet-stream
 		</p><p>
 		Which spooling system is better is a matter of personal taste. It depends on what you want to do and how you want to
 		do it and manage it. Most modern Linux systems ship with CUPS as the default print management system.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555135"></a><a name="id2555137"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555131"></a><a name="id2555133"></a></td><td align="left" valign="top"><p>
 		When should Windows client IP addresses be hard-coded?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		When there are few MS Windows clients, little client change, no mobile users, and users are not
@@ -788,7 +788,7 @@ application/octet-stream
 		user ability to access network configuration controls, fixed configuration eliminates the need
 		for a DHCP server. This reduces maintenance overheads and eliminates a possible point of network
 		failure.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555161"></a><a name="id2555163"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555157"></a><a name="id2555159"></a></td><td align="left" valign="top"><p>
 		Under what circumstances is it best to use a DHCP server?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		In network configurations where there are mobile users, or where Windows client PCs move around
@@ -804,12 +804,12 @@ application/octet-stream
 		Another benefit of modern DHCP servers is their ability to register dynamically
 		assigned IP addresses with the DNS server. The benefits of Dynamic DNS (DDNS) are considerable in 
 		a large Windows network environment.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555200"></a><a name="id2555202"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555196"></a><a name="id2555198"></a></td><td align="left" valign="top"><p>
 		What is the purpose of setting the parameter <em class="parameter"><code>guest ok</code></em> on a share?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		If this parameter is set to yes for a service, then no password is required to connect to the service.
 		Privileges are those of the guest account.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555224"></a><a name="id2555226"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555220"></a><a name="id2555223"></a></td><td align="left" valign="top"><p>
 		When would you set the global parameter <em class="parameter"><code>disable spoolss</code></em>?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Setting this parameter to <code class="constant">Yes</code> disables Samba's support for the SPOOLSS set of 
@@ -833,14 +833,14 @@ application/octet-stream
 		that the client now displays an &#8220;<span class="quote">Access Denied; Unable to connect</span>&#8221; message in the printer queue window
 		(even though jobs may be printed successfully). This parameter MUST not be enabled on a print share that has a valid
 		print driver installed on the Samba server.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555310"></a><a name="id2555312"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555306"></a><a name="id2555308"></a></td><td align="left" valign="top"><p>
 		Why would you disable password caching on Windows 9x/Me clients?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Windows 9x/Me workstations that are set at default (password caching enabled) store the username and
 		password in files located in the Windows master directory. Such files can be scavenged (read off a client
 		machine) and decrypted, thus revealing the user's access credentials for all systems the user may have accessed.
 		It is most insecure to allow any Windows 9x/Me client to operate with password caching enabled.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555334"></a><a name="id2555336"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2555330"></a><a name="id2555333"></a></td><td align="left" valign="top"><p>
 		The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The example used does not provide anonymous access. Since the clients are all Windows 2000 Professional,
@@ -848,15 +848,14 @@ application/octet-stream
 		a remote server using currently logged in user credentials. By ensuring that the user's login ID and
 		password are the same as those set on the Samba server, access is transparent and does not require
 		separate user authentication.
-		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2550854" href="#id2550854" class="para">1</a>] </sup>The examples given mirror those documented
+		</p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2550848" href="#id2550848" class="para">1</a>] </sup>The examples given mirror those documented
 	in The Official Samba-3 HOWTO and Reference Guide, Second Edition (TOSHARG2) Chapter 2, Section 2.3.1. You may gain additional
 	insight from the standalone server configurations covered in TOSHARG2, sections 2.3.1.2 through 2.3.1.4.
-	</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551032" href="#id2551032" class="para">2</a>] </sup>
+	</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551026" href="#id2551026" class="para">2</a>] </sup>
 		This information is given purely as an example of how data may be stored in such a way that it
 		will be easy to locate records at a later date. The example is not meant to imply any instructions
 		that may be construed as essential to the design of the solution; this is something you will almost
-		certainly want to determine for yourself.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2552236" href="#id2552236" class="para">3</a>] </sup>The Official Samba-3 HOWTO and
-						Reference Guide, Chapter 15, File, Directory and Share Access Controls.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2554269" href="#id2554269" class="para">4</a>] </sup>This example uses the 
+		certainly want to determine for yourself.</p></div><div class="footnote"></div><div class="footnote"><p><sup>[<a name="ftn.id2554264" href="#id2554264" class="para">4</a>] </sup>This example uses the 
 			<em class="parameter"><code>smbpasswd</code></em> file in an obtuse way, since the use of 
 			the <em class="parameter"><code>passdb backend</code></em> has not been specified in the <code class="filename">smb.conf</code> 
 			file. This means that you are depending on correct default behavior.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ExNetworks.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="ExNetworks.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="small.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�I.�Example Network Configurations�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�2.�Small Office Networking</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/small.html b/docs/htmldocs/Samba3-ByExample/small.html
index 36a600861e..d9044134cf 100644
--- a/docs/htmldocs/Samba3-ByExample/small.html
+++ b/docs/htmldocs/Samba3-ByExample/small.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Small Office Networking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="simple.html" title="Chapter�1.�No-Frills Samba Servers"><link rel="next" href="secure.html" title="Chapter�3.�Secure Office Networking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Small Office Networking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="simple.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="secure.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="small"></a>Chapter�2.�Small Office Networking</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="small.html#id2555439">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555462">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555522">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555570">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555768">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555790">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557337">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557985">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558010">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558084">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Small Office Networking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="ExNetworks.html" title="Part�I.�Example Network Configurations"><link rel="prev" href="simple.html" title="Chapter�1.�No-Frills Samba Servers"><link rel="next" href="secure.html" title="Chapter�3.�Secure Office Networking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Small Office Networking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="simple.html">Prev</a>�</td><th width="60%" align="center">Part�I.�Example Network Configurations</th><td width="20%" align="right">�<a accesskey="n" href="secure.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="small"></a>Chapter�2.�Small Office Networking</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="small.html#id2555435">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555458">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555518">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2555566">Technical Issues</a></span></dt><dt><span class="sect2"><a href="small.html#id2555765">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2555786">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="small.html#id2557330">Validation</a></span></dt><dt><span class="sect2"><a href="small.html#id2557978">Notebook Computers: A Special Case</a></span></dt><dt><span class="sect2"><a href="small.html#id2558003">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="small.html#id2558077">Questions and Answers</a></span></dt></dl></div><p>
 	<a class="link" href="simple.html" title="Chapter�1.�No-Frills Samba Servers">&#8220;No-Frills Samba Servers&#8221;</a> focused on the basics of simple yet effective
 	network solutions. Network administrators who take pride in their work
 	(that's most of us, right?) take care to deliver what our users want,
@@ -8,7 +8,7 @@
 	operates. Some creativity is helpful, but keep it under control 
 	good advice that the following two scenarios illustrate.
 	</p><p>
-	<a class="indexterm" name="id2555395"></a>
+	<a class="indexterm" name="id2555391"></a>
 	In one case the network administrator of a mid-sized company spent three
 	months building a new network to replace an old Netware server. What he
 	delivered had all the bells and whistles he could muster. There were a
@@ -36,7 +36,7 @@
 	and got it. He often told me, &#8220;<span class="quote">Always keep a few new tricks up your
 	sleeves for when you need them.</span>&#8221; Was he smart? You decide. Let's
 	get on with our next exercise.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555439"></a>Introduction</h2></div></div></div><p>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555435"></a>Introduction</h2></div></div></div><p>
 	Abmas Accounting has grown. Mr. Meany likes you and says he knew you
 	were the right person for the job. That's why he asked you to install the
 	new server. The past few months have been hard work. You advised Mr. Meany
@@ -47,8 +47,8 @@
 	Some of the Windows clients are nearly past their use-by date.  You found damaged and unusable software on
 	some of the workstations that came with the acquired business and found some machines in need of both
 	hardware and software maintenance.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555462"></a>Assignment Tasks</h3></div></div></div><p>
-		<a class="indexterm" name="id2555469"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555458"></a>Assignment Tasks</h3></div></div></div><p>
+		<a class="indexterm" name="id2555465"></a>
 		Mr. Meany is retiring in 12 months. Before he goes, he wants you to help ensure
 		that the business is running efficiently. Many of the new staff want notebook
 		computers.  They visit customer business premises and need to use local network
@@ -80,14 +80,14 @@
 		Mr. Meany also asked if it would be possible for one of the staff to manage
 		user accounts from the Windows desktop. That person will be responsible for
 		basic operations.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555522"></a>Dissection and Discussion</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555518"></a>Dissection and Discussion</h2></div></div></div><p>
 	What are the key requirements in this business example? A quick review indicates
 	a need for
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 		Scalability, from 52 to over 100 users in 12 months
 		</p></li><li><p>
 		Mobile computing capability
-		<a class="indexterm" name="id2555543"></a>
+		<a class="indexterm" name="id2555539"></a>
 		</p></li><li><p>
 		Improved reliability and usability
 		</p></li><li><p>
@@ -96,12 +96,12 @@
 	In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server
 	(as in <a class="link" href="simple.html#AccountingOffice" title="Accounting Office">&#8220;Accounting Office&#8221;</a>).
 
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555570"></a>Technical Issues</h3></div></div></div><p>
-		<a class="indexterm" name="id2555577"></a>
-		<a class="indexterm" name="id2555584"></a>
-		<a class="indexterm" name="id2555590"></a>
-		<a class="indexterm" name="id2555596"></a>
-		<a class="indexterm" name="id2555602"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555566"></a>Technical Issues</h3></div></div></div><p>
+		<a class="indexterm" name="id2555574"></a>
+		<a class="indexterm" name="id2555580"></a>
+		<a class="indexterm" name="id2555586"></a>
+		<a class="indexterm" name="id2555592"></a>
+		<a class="indexterm" name="id2555599"></a>
 		It is time to implement a domain security environment. You will use the <code class="constant">
 		smbpasswd</code> (default) backend. You should implement a DHCP server. There is no need to
 		run DNS at this time, but the system will use WINS. The domain name will be <code class="constant">
@@ -122,7 +122,7 @@
 		Later on, when the Internet connection is implemented, you will add DNS as well as
 		other enhancements. It is important that you plan accordingly.
 		</p><p>
-		<a class="indexterm" name="id2555662"></a>
+		<a class="indexterm" name="id2555658"></a>
 		You have split the network into two separate areas. Each has its own Ethernet switch.
 		There are 20 users on the accounting network and 32 users on the financial services
 		network. The server has two network interfaces, one serving each network. The
@@ -137,8 +137,8 @@
 		Given that DNS will not be used, you will configure WINS name resolution for UNIX
 		hostname name resolution.
 		</p><p>
-		<a class="indexterm" name="id2555692"></a>
-		<a class="indexterm" name="id2555700"></a>
+		<a class="indexterm" name="id2555688"></a>
+		<a class="indexterm" name="id2555696"></a>
 		It is necessary to map Windows Domain Groups to UNIX groups. It is
 		advisable to also map Windows Local Groups to UNIX groups. Additionally, the two
 		key staff groups in the firm are accounting staff and financial services staff.
@@ -155,10 +155,10 @@
 		<span class="emphasis"><em>TOSHARG2</em></span>, Chapter 11, Section 11.3.1, Example 11.1, for
 		more information.
 		</p><p>
-		<a class="indexterm" name="id2555755"></a>
+		<a class="indexterm" name="id2555751"></a>
 		Vendor-supplied printer drivers will be installed on each client. The CUPS print
 		spooler on the UNIX host will be operated in <code class="constant">raw</code> mode.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555768"></a>Political Issues</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555765"></a>Political Issues</h3></div></div></div><p>
 		Mr. Meany is an old-school manager. He sets the rules and wants to see compliance.
 		He is willing to spend money on things he believes are of value. You need more
 		time to convince him of real priorities.
@@ -166,8 +166,8 @@
 		Go ahead, buy better notebooks. Wouldn't it be neat if they happened to be
 		supplied with antivirus software? Above all, demonstrate good purchase value and remember
 		to make your users happy.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555790"></a>Implementation</h2></div></div></div><p>
-	<a class="indexterm" name="id2555797"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555786"></a>Implementation</h2></div></div></div><p>
+	<a class="indexterm" name="id2555793"></a>
 	In this example, the assumption is made that this server is being configured from a clean start.
 	The alternate approach could be to demonstrate the migration of the system that is documented
 	in <a class="link" href="simple.html#AcctgNet" title="Implementation">&#8220;Implementation&#8221;</a> to meet the new requirements. The decision to treat this case, as with
@@ -175,25 +175,23 @@
 	the migration steps from the information provided in <a class="link" href="ntmigration.html" title="Chapter�9.�Migrating NT4 Domain to Samba-3">&#8220;Migrating NT4 Domain to Samba-3&#8221;</a>.
 	Additionally, a fresh installation makes the example easier to follow.
 	</p><p>
-	<a class="indexterm" name="id2555823"></a>
+	<a class="indexterm" name="id2555819"></a>
 	Each user will be given a home directory on the UNIX system, which will be available as a private
 	share. Two additional shares will be created, one for the accounting department and the other for
 	the financial services department. Network users will be given access to these shares by way
 	of group membership.
 	</p><p>
-	<a class="indexterm" name="id2555838"></a>
+	<a class="indexterm" name="id2555834"></a>
 	UNIX group membership is the primary mechanism by which Windows Domain users will be granted
 	rights and privileges within the Windows environment.
 	</p><p>
-	<a class="indexterm" name="id2555852"></a>
+	<a class="indexterm" name="id2555849"></a>
 	The user <code class="literal">alanm</code> will be made the owner of all files. This will be preserved
 	by setting the sticky bit (set UID/GID) on the top-level directories.
-	</p><p>
-	</p><div class="figure"><a name="acct2net"></a><p class="title"><b>Figure�2.1.�Abmas Accounting  52-User Network Topology</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/acct2net.png" alt="Abmas Accounting 52-User Network Topology"></div></div></div><p><br class="figure-break">
-</p><div class="procedure"><a name="id2555910"></a><p class="title"><b>Procedure�2.1.�Server Installation Steps</b></p><ol type="1"><li><p>
+	</p><div class="figure"><a name="acct2net"></a><p class="title"><b>Figure�2.1.�Abmas Accounting  52-User Network Topology</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/acct2net.png" alt="Abmas Accounting 52-User Network Topology"></div></div></div><br class="figure-break"><div class="procedure"><a name="id2555903"></a><p class="title"><b>Procedure�2.1.�Server Installation Steps</b></p><ol type="1"><li><p>
 		Using UNIX/Linux system tools, name the server <code class="constant">sleeth</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2555931"></a>
+		<a class="indexterm" name="id2555924"></a>
 		Place an entry for the machine <code class="constant">sleeth</code> in the <code class="filename">/etc/hosts</code>.
 		The printers are network attached, so there should be entries for the
 		network printers also. An example <code class="filename">/etc/hosts</code> file is shown here:
@@ -209,10 +207,10 @@
 		</p></li><li><p>
 		Install the ISC DHCP server using the UNIX/Linux system tools available to you.
 		</p></li><li><p>
-		<a class="indexterm" name="id2555982"></a>
+		<a class="indexterm" name="id2555975"></a>
+		<a class="indexterm" name="id2555981"></a>
 		<a class="indexterm" name="id2555988"></a>
-		<a class="indexterm" name="id2555995"></a>
-		<a class="indexterm" name="id2556001"></a>
+		<a class="indexterm" name="id2555994"></a>
 		Because Samba will be operating over two network interfaces and clients on each side
 		may want to be able to reach clients on the other side, it is imperative that IP forwarding
 		is enabled. Use the system tool of your choice to enable IP forwarding. In the
@@ -227,7 +225,7 @@ echo 1 &gt; /proc/sys/net/ipv4/ip_forward
 		<a class="link" href="small.html#acct3conf" title="Example�2.4.�Accounting Office Network smb.conf File Services and Shares Section">&#8220;Accounting Office Network smb.conf File  Services and Shares Section&#8221;</a>. Combine these two examples to form a single
 		<code class="filename">/etc/samba/smb.conf</code> file.
 		</p></li><li><p>
-		<a class="indexterm" name="id2556060"></a>
+		<a class="indexterm" name="id2556053"></a>
 		Add the user <code class="literal">root</code> to the Samba password backend:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbpasswd -a root
@@ -235,13 +233,13 @@ New SMB password: XXXXXXX
 Retype new SMB password: XXXXXXX
 <code class="prompt">root# </code>
 </pre><p>
-		<a class="indexterm" name="id2556089"></a>
+		<a class="indexterm" name="id2556082"></a>
 		This is the Windows Domain Administrator password. Never delete this account from
 		the password backend after Windows Domain Groups have been initialized. If you delete
 		this account, your system is crippled. You cannot restore this account,
 		and your Samba server can no longer be administered.
 		</p></li><li><p>
-		<a class="indexterm" name="id2556107"></a>
+		<a class="indexterm" name="id2556100"></a>
 		Create the username map file to permit the <code class="constant">root</code> account to be called
 		<code class="constant">Administrator</code> from the Windows network environment. To do this, create
 		the file <code class="filename">/etc/samba/smbusers</code> with the following contents:
@@ -268,13 +266,13 @@ root = Administrator
 ####
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556147"></a>
+		<a class="indexterm" name="id2556140"></a>
 		Create and map Windows Domain Groups to UNIX groups. A sample script is provided in
 		<a class="link" href="small.html#initGrps" title="Example�2.1.�Script to Map Windows NT Groups to UNIX Groups">&#8220;Script to Map Windows NT Groups to UNIX Groups&#8221;</a>. Create a file containing this script. We called ours
 		<code class="filename">/etc/samba/initGrps.sh</code>. Set this file so it can be executed,
 		and then execute the script. Sample output should be as follows:
 
-</p><div class="example"><a name="initGrps"></a><p class="title"><b>Example�2.1.�Script to Map Windows NT Groups to UNIX Groups</b></p><div class="example-contents"><a class="indexterm" name="id2556176"></a><pre class="screen">
+</p><div class="example"><a name="initGrps"></a><p class="title"><b>Example�2.1.�Script to Map Windows NT Groups to UNIX Groups</b></p><div class="example-contents"><a class="indexterm" name="id2556169"></a><pre class="screen">
 #!/bin/bash
 #
 # initGrps.sh
@@ -324,17 +322,17 @@ System Operators (S-1-5-32-549) -&gt; -1
 Users (S-1-5-32-545) -&gt; -1
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556254"></a>
-		<a class="indexterm" name="id2556260"></a>
-		<a class="indexterm" name="id2556268"></a>
+		<a class="indexterm" name="id2556247"></a>
+		<a class="indexterm" name="id2556253"></a>
+		<a class="indexterm" name="id2556261"></a>
 		For each user who needs to be given a Windows Domain account, make an entry in the
 		<code class="filename">/etc/passwd</code> file as well as in the Samba password backend.
 		Use the system tool of your choice to create the UNIX system accounts, and use the Samba
 		<code class="literal">smbpasswd</code> program to create the Domain user accounts.
 		</p><p>
-		<a class="indexterm" name="id2556293"></a>
-		<a class="indexterm" name="id2556300"></a>
-		<a class="indexterm" name="id2556306"></a>
+		<a class="indexterm" name="id2556286"></a>
+		<a class="indexterm" name="id2556292"></a>
+		<a class="indexterm" name="id2556299"></a>
 		There are a number of tools for user management under UNIX, such as
 		<code class="literal">useradd</code> and <code class="literal">adduser</code>, as well as a plethora of custom
 		tools. With the tool of your choice, create a home directory for each user.
@@ -352,8 +350,8 @@ Users (S-1-5-32-545) -&gt; -1
 </p><pre class="screen">
 <code class="prompt">root# </code> mkdir -p /data/{accounts,finsvcs}
 <code class="prompt">root# </code> chown -R root:root /data
-<code class="prompt">root# </code> chown -R alanm:acctsdep /data/accounts
-<code class="prompt">root# </code> chown -R alanm:finsrvcs /data/finsrvcs
+<code class="prompt">root# </code> chown -R alanm:accounts /data/accounts
+<code class="prompt">root# </code> chown -R alanm:finsvcs /data/finsvcs
 <code class="prompt">root# </code> chmod -R ug+rwx,o+rx-w /data
 </pre><p>
 		Each department is responsible for creating its own directory structure within its
@@ -363,38 +361,38 @@ Users (S-1-5-32-545) -&gt; -1
 		Configure the printers with the IP addresses as shown in <a class="link" href="small.html#acct2net" title="Figure�2.1.�Abmas Accounting 52-User Network Topology">&#8220;Abmas Accounting  52-User Network Topology&#8221;</a>.
 		Follow the instructions in the manufacturers' manuals to permit printing to port 9100.
 		This allows the CUPS spooler to print using raw mode protocols.
-		<a class="indexterm" name="id2556450"></a>
-		<a class="indexterm" name="id2556456"></a>
+		<a class="indexterm" name="id2556442"></a>
+		<a class="indexterm" name="id2556449"></a>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556468"></a>
-		<a class="indexterm" name="id2556477"></a>
+		<a class="indexterm" name="id2556461"></a>
+		<a class="indexterm" name="id2556470"></a>
 		Configure the CUPS Print Queues as follows:
 </p><pre class="screen">
 <code class="prompt">root# </code> lpadmin -p hplj4 -v socket://192.168.1.11:9100 -E
 <code class="prompt">root# </code> lpadmin -p hplj6 -v socket://192.168.1.10:9100 -E
 <code class="prompt">root# </code> lpadmin -p qms -v socket://192.168.2.10:9100 -E
 </pre><p>
-		<a class="indexterm" name="id2556508"></a>
+		<a class="indexterm" name="id2556500"></a>
 		This creates the necessary print queues with no assigned print filter.
 		</p></li><li><p>
-		<a class="indexterm" name="id2556522"></a>
-		<a class="indexterm" name="id2556528"></a>
-		<a class="indexterm" name="id2556534"></a>
+		<a class="indexterm" name="id2556514"></a>
+		<a class="indexterm" name="id2556521"></a>
+		<a class="indexterm" name="id2556527"></a>
 		Edit the file <code class="filename">/etc/cups/mime.convs</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream     application/vnd.cups-raw      0     -
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556558"></a>
+		<a class="indexterm" name="id2556551"></a>
 		Edit the file <code class="filename">/etc/cups/mime.types</code> to uncomment the line:
 </p><pre class="screen">
 application/octet-stream
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556581"></a>
+		<a class="indexterm" name="id2556574"></a>
 		Using your favorite system editor, create an <code class="filename">/etc/dhcpd.conf</code> with the
 		contents as shown in <a class="link" href="small.html#dhcp01" title="Example�2.2.�Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf">&#8220;Abmas Accounting DHCP Server Configuration File  /etc/dhcpd.conf&#8221;</a>.
-</p><div class="example"><a name="dhcp01"></a><p class="title"><b>Example�2.2.�Abmas Accounting DHCP Server Configuration File  <code class="filename">/etc/dhcpd.conf</code></b></p><div class="example-contents"><a class="indexterm" name="id2556614"></a><pre class="screen">
+</p><div class="example"><a name="dhcp01"></a><p class="title"><b>Example�2.2.�Abmas Accounting DHCP Server Configuration File  <code class="filename">/etc/dhcpd.conf</code></b></p><div class="example-contents"><a class="indexterm" name="id2556607"></a><pre class="screen">
 default-lease-time 86400;
 max-lease-time 172800;
 default-lease-time 86400;
@@ -442,11 +440,11 @@ subnet 127.0.0.0 netmask 255.0.0.0 {
 		Use the standard system tool to start Samba and CUPS and configure them to start
 		automatically at every system reboot. For example,
 		</p><p>
-		<a class="indexterm" name="id2556658"></a>
-		<a class="indexterm" name="id2556664"></a>
-		<a class="indexterm" name="id2556670"></a>
+		<a class="indexterm" name="id2556650"></a>
+		<a class="indexterm" name="id2556657"></a>
+		<a class="indexterm" name="id2556663"></a>
+		<a class="indexterm" name="id2556669"></a>
 		<a class="indexterm" name="id2556676"></a>
-		<a class="indexterm" name="id2556683"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> chkconfig dhcp on
 <code class="prompt">root# </code> chkconfig smb on
@@ -456,12 +454,12 @@ subnet 127.0.0.0 netmask 255.0.0.0 {
 <code class="prompt">root# </code> /etc/rc.d/init.d/cups restart
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2556733"></a>
-		<a class="indexterm" name="id2556739"></a>
-		<a class="indexterm" name="id2556748"></a>
-		<a class="indexterm" name="id2556754"></a>
-		<a class="indexterm" name="id2556760"></a>
-		<a class="indexterm" name="id2556766"></a>
+		<a class="indexterm" name="id2556726"></a>
+		<a class="indexterm" name="id2556732"></a>
+		<a class="indexterm" name="id2556740"></a>
+		<a class="indexterm" name="id2556747"></a>
+		<a class="indexterm" name="id2556753"></a>
+		<a class="indexterm" name="id2556759"></a>
 		Configure the name service switch (NSS) to handle WINS-based name resolution.
 		Since this system does not use a DNS server, it is safe to remove this option from
 		the NSS configuration. Edit the <code class="filename">/etc/nsswitch.conf</code> file so that
@@ -469,11 +467,11 @@ subnet 127.0.0.0 netmask 255.0.0.0 {
 </p><pre class="screen">
 hosts:	files wins
 </pre><p>
-		</p></li></ol></div><div class="example"><a name="acct2conf"></a><p class="title"><b>Example�2.3.�Accounting Office Network <code class="filename">smb.conf</code> File  [globals] Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556824"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2556834"></a><em class="parameter"><code>passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*</code></em></td></tr><tr><td><a class="indexterm" name="id2556846"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2556857"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2556867"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2556878"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2556889"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556900"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m -G users '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556911"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556922"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2556934"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2556945"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -A '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556956"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556968"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2556979"></a><em class="parameter"><code>logon path =  </code></em></td></tr><tr><td><a class="indexterm" name="id2556990"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2557000"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557011"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557021"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557031"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="acct3conf"></a><p class="title"><b>Example�2.4.�Accounting Office Network <code class="filename">smb.conf</code> File  Services and Shares Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2557072"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2557082"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557093"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557103"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2557122"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2557132"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2557143"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557153"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557163"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557174"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2557193"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2557204"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557214"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557224"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2557243"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2557254"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2557264"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2557274"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[finsrvcs]</code></em></td></tr><tr><td><a class="indexterm" name="id2557293"></a><em class="parameter"><code>comment = Financial Service Files</code></em></td></tr><tr><td><a class="indexterm" name="id2557304"></a><em class="parameter"><code>path = /data/finsrvcs</code></em></td></tr><tr><td><a class="indexterm" name="id2557315"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2557325"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557337"></a>Validation</h3></div></div></div><p>
+		</p></li></ol></div><div class="example"><a name="acct2conf"></a><p class="title"><b>Example�2.3.�Accounting Office Network <code class="filename">smb.conf</code> File  [globals] Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556817"></a><em class="parameter"><code>workgroup = BILLMORE</code></em></td></tr><tr><td><a class="indexterm" name="id2556827"></a><em class="parameter"><code>passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*</code></em></td></tr><tr><td><a class="indexterm" name="id2556839"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2556850"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2556860"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2556871"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2556882"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556893"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m -G users '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556904"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556915"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2556927"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2556938"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -A '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556949"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2556961"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2556972"></a><em class="parameter"><code>logon path =  </code></em></td></tr><tr><td><a class="indexterm" name="id2556983"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2556993"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557004"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557014"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557024"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="acct3conf"></a><p class="title"><b>Example�2.4.�Accounting Office Network <code class="filename">smb.conf</code> File  Services and Shares Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2557065"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2557075"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557086"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557096"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2557115"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2557125"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2557136"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557146"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557156"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557167"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2557186"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2557197"></a><em class="parameter"><code>path = /data/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557207"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557217"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[accounts]</code></em></td></tr><tr><td><a class="indexterm" name="id2557236"></a><em class="parameter"><code>comment = Accounting Files</code></em></td></tr><tr><td><a class="indexterm" name="id2557247"></a><em class="parameter"><code>path = /data/accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2557257"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2557267"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[finsvcs]</code></em></td></tr><tr><td><a class="indexterm" name="id2557286"></a><em class="parameter"><code>comment = Financial Service Files</code></em></td></tr><tr><td><a class="indexterm" name="id2557297"></a><em class="parameter"><code>path = /data/finsvcs</code></em></td></tr><tr><td><a class="indexterm" name="id2557308"></a><em class="parameter"><code>valid users = %G</code></em></td></tr><tr><td><a class="indexterm" name="id2557318"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557330"></a>Validation</h3></div></div></div><p>
 		Does everything function as it ought? That is the key question at this point.
 		Here are some simple steps to validate your Samba server configuration.
-		</p><div class="procedure"><a name="id2557348"></a><p class="title"><b>Procedure�2.2.�Validation Steps</b></p><ol type="1"><li><p>
-			<a class="indexterm" name="id2557358"></a>
+		</p><div class="procedure"><a name="id2557341"></a><p class="title"><b>Procedure�2.2.�Validation Steps</b></p><ol type="1"><li><p>
+			<a class="indexterm" name="id2557351"></a>
 			If your <code class="filename">smb.conf</code> file has bogus options or parameters, this may cause Samba
 			to refuse to start. The first step should always be to validate the contents
 			of this file by running:
@@ -520,10 +518,10 @@ Ignoring unknown parameter "dogbert"
 </pre><p>
 			Clear away all errors before proceeding, and start or restart samba as necessary.
 			</p></li><li><p>
-			<a class="indexterm" name="id2557438"></a>
-			<a class="indexterm" name="id2557444"></a>
+			<a class="indexterm" name="id2557431"></a>
+			<a class="indexterm" name="id2557437"></a>
+			<a class="indexterm" name="id2557443"></a>
 			<a class="indexterm" name="id2557450"></a>
-			<a class="indexterm" name="id2557457"></a>
 			Check that the Samba server is running:
 </p><pre class="screen">
 <code class="prompt">root# </code> ps ax | grep mbd
@@ -540,7 +538,7 @@ $rootprompt; ps ax | grep winbind
 			<span class="emphasis"><em>TOSHARG2</em></span>, Chapter 23, Section 23.3. The single instance of
 			<code class="literal">smbd</code> is normal.
 			</p></li><li><p>
-			<a class="indexterm" name="id2557508"></a>
+			<a class="indexterm" name="id2557500"></a>
 			Check that an anonymous connection can be made to the Samba server:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbclient -L localhost -U%
@@ -569,9 +567,9 @@ $rootprompt; ps ax | grep winbind
 			The <code class="constant">-U%</code> argument means to send a <code class="constant">NULL</code> username and
 			a <code class="constant">NULL</code> password.
 			</p></li><li><p>
-			<a class="indexterm" name="id2557558"></a>
+			<a class="indexterm" name="id2557551"></a>
+			<a class="indexterm" name="id2557557"></a>
 			<a class="indexterm" name="id2557564"></a>
-			<a class="indexterm" name="id2557571"></a>
 			Verify that the printers have the IP addresses assigned in the DHCP server configuration file.
 			The easiest way to do this is to ping the printer name. Immediately after the ping response
 			has been received, execute <code class="literal">arp -a</code> to find the MAC address of the printer
@@ -590,7 +588,7 @@ hplj4 (192.168.1.11) at 08:00:46:7A:35:E4 [ether] on eth0
 			IP address from which the printer has responded and the entry for it in the
 			<code class="filename">/etc/dhcpd.conf</code> file.
 			</p></li><li><p>
-			<a class="indexterm" name="id2557631"></a>
+			<a class="indexterm" name="id2557624"></a>
 			Make an authenticated connection to the server using the <code class="literal">smbclient</code> tool:
 </p><pre class="screen">
 <code class="prompt">root# </code> smbclient //sleeth/accounts -U alanm
@@ -607,11 +605,11 @@ smb: \&gt; dir
            65387 blocks of size 65536. 28590 blocks available
 smb: \&gt; q
 </pre><p>
-			</p></li></ol></div></div><div class="procedure"><a name="id2557680"></a><p class="title"><b>Procedure�2.3.�Windows XP Professional Client Configuration</b></p><ol type="1"><li><p>
+			</p></li></ol></div></div><div class="procedure"><a name="id2557672"></a><p class="title"><b>Procedure�2.3.�Windows XP Professional Client Configuration</b></p><ol type="1"><li><p>
 		Configure clients to the network settings shown in <a class="link" href="small.html#acct2net" title="Figure�2.1.�Abmas Accounting 52-User Network Topology">&#8220;Abmas Accounting  52-User Network Topology&#8221;</a>.
 		All clients use DHCP for TCP/IP protocol stack configuration.
-		<a class="indexterm" name="id2557698"></a>
-		<a class="indexterm" name="id2557704"></a>
+		<a class="indexterm" name="id2557690"></a>
+		<a class="indexterm" name="id2557697"></a>
 		DHCP configures all Windows clients to use the WINS Server address <code class="constant">192.168.1.1</code>.
 		</p></li><li><p>
 		Join the Windows Domain called <code class="constant">BILLMORE</code>. Use the Domain Administrator
@@ -653,7 +651,7 @@ smb: \&gt; q
 				</p></li><li><p>
 				Repeat the printer installation steps above for the HP LaserJet 6 printer
 				as well as for the QMS Magicolor XXXX laser printer.
-				</p></li></ol></div></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557985"></a>Notebook Computers: A Special Case</h3></div></div></div><p>
+				</p></li></ol></div></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557978"></a>Notebook Computers: A Special Case</h3></div></div></div><p>
 	As a network administrator, you already know how to create local machine accounts for Windows 200x/XP
 	Professional systems. This is the preferred solution to provide continuity of work for notebook users
 	so that absence from the office network environment does not become a barrier to productivity.
@@ -663,21 +661,21 @@ smb: \&gt; q
 	transparently access network resources as if logged onto the domain itself. There are some trade-offs
 	that mean that as the network is more tightly secured, it becomes necessary to modify Windows client
 	configuration somewhat.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558010"></a>Key Points Learned</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558003"></a>Key Points Learned</h3></div></div></div><p>
 		In this network design and implementation exercise, you created a Windows NT4-style Domain
 		Controller using Samba-3.0.20. Following these guidelines, you experienced
 		and implemented several important aspects of Windows networking. In the next chapter,
 		you build on the experience. These are the highlights from this chapter:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2558030"></a>
+			<a class="indexterm" name="id2558023"></a>
 			You implemented a DHCP server, and Microsoft Windows clients were able to obtain all necessary
 			network configuration settings from this server.
 			</p></li><li><p>
-			<a class="indexterm" name="id2558043"></a>
+			<a class="indexterm" name="id2558036"></a>
 			You created a Windows Domain Controller. You were able to use the network logon service
 			and successfully joined Windows 200x/XP Professional clients to the Domain.
 			</p></li><li><p>
-			<a class="indexterm" name="id2558057"></a>
+			<a class="indexterm" name="id2558050"></a>
 			You created raw print queues in the CUPS printing system. You maintained a simple
 			printing system so that all users can share centrally managed printers. You installed
 			native printer drivers on the Windows clients.
@@ -686,33 +684,33 @@ smb: \&gt; q
 			</p></li><li><p>
 			You offered Mobile notebook users a solution that allows them to continue to work
 			while away from the office and not connected to the corporate network.
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558084"></a>Questions and Answers</h2></div></div></div><p>
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558077"></a>Questions and Answers</h2></div></div></div><p>
 	Your new Domain Controller is ready to serve you. What does it mean? Here are some questions and answers that
 	may help.
-	</p><div class="qandaset"><dl><dt>1. <a href="small.html#id2558097">
+	</p><div class="qandaset"><dl><dt>1. <a href="small.html#id2558090">
 		What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
-		</a></dt><dt>2. <a href="small.html#id2558124">
+		</a></dt><dt>2. <a href="small.html#id2558117">
 		Are there any DHCP server configuration parameters in the /etc/dhcpd.conf
 		that should be noted in particular?
-		</a></dt><dt>3. <a href="small.html#id2558155">
+		</a></dt><dt>3. <a href="small.html#id2558148">
 		Is it possible to create a Windows Domain account that is specifically called Administrator?
-		</a></dt><dt>4. <a href="small.html#id2558192">
+		</a></dt><dt>4. <a href="small.html#id2558185">
 		Why is it necessary to give the Windows Domain Administrator a UNIX UID of 0?
-		</a></dt><dt>5. <a href="small.html#id2558230">
+		</a></dt><dt>5. <a href="small.html#id2558223">
 		One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
 		root access. How can we do this?
-		</a></dt><dt>6. <a href="small.html#id2558270">
+		</a></dt><dt>6. <a href="small.html#id2558262">
 		Why must I map Windows Domain Groups to UNIX groups?
-		</a></dt><dt>7. <a href="small.html#id2558306">
+		</a></dt><dt>7. <a href="small.html#id2558299">
 		I deleted my root account and now I cannot add it back! What can I do?
-		</a></dt><dt>8. <a href="small.html#id2558373">
+		</a></dt><dt>8. <a href="small.html#id2558366">
 		When I run net groupmap list, it reports a group called Administrators
 		as well as Domain Admins. What is the difference between them?
-		</a></dt><dt>9. <a href="small.html#id2558418">
+		</a></dt><dt>9. <a href="small.html#id2558411">
 		What is the effect of changing the name of a Samba server or of changing the Domain name?
-		</a></dt><dt>10. <a href="small.html#id2558467">
+		</a></dt><dt>10. <a href="small.html#id2558460">
 		How can I manage user accounts from my Windows XP Professional workstation?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2558097"></a><a name="id2558099"></a><p><b>1.</b></p></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2558090"></a><a name="id2558092"></a><p><b>1.</b></p></td><td align="left" valign="top"><p>
 		What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		First and foremost, portability. It means that notebook users can move between
@@ -721,7 +719,7 @@ smb: \&gt; q
 		either using DHCP assigned addressing or when using dial-up networking, settings such as
 		default routes and DNS server addresses that apply only to the Abmas office environment do
 		not interfere with remote operations. This is an extremely important feature of DHCP.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558124"></a><a name="id2558126"></a><p><b>2.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558117"></a><a name="id2558119"></a><p><b>2.</b></p></td><td align="left" valign="top"><p>
 		Are there any DHCP server configuration parameters in the <code class="filename">/etc/dhcpd.conf</code>
 		that should be noted in particular?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -730,14 +728,14 @@ smb: \&gt; q
 		with the WINS server, and then instructs the client to first query the WINS server when a
 		NetBIOS machine name needs to be resolved to an IP Address. This configuration
 		results in far lower UDP broadcast traffic than would be the case if WINS was not used.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558155"></a><a name="id2558157"></a><p><b>3.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558148"></a><a name="id2558150"></a><p><b>3.</b></p></td><td align="left" valign="top"><p>
 		Is it possible to create a Windows Domain account that is specifically called <code class="constant">Administrator</code>?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		You can surely create a Windows Domain account called <code class="constant">Administrator</code>. It is also
 		possible to map that account so that it has the effective UNIX UID of 0. This way it isn't
 		necessary to use the <em class="parameter"><code>username map</code></em> facility to map this account to the UNIX
 		account called <code class="constant">root</code>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558192"></a><a name="id2558194"></a><p><b>4.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558185"></a><a name="id2558187"></a><p><b>4.</b></p></td><td align="left" valign="top"><p>
 		Why is it necessary to give the Windows Domain <code class="constant">Administrator</code> a UNIX UID of 0?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		The Windows Domain <code class="constant">Administrator</code> account is the most privileged account that
@@ -747,7 +745,7 @@ smb: \&gt; q
 		Administrator to manage accounts as well as permissions, privileges, and security
 		settings within the Domain and on the Samba server, equivalent rights must be assigned. This is
 		achieved with the <code class="constant">root</code> UID equal to 0.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558230"></a><a name="id2558232"></a><p><b>5.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558223"></a><a name="id2558225"></a><p><b>5.</b></p></td><td align="left" valign="top"><p>
 		One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
 		<code class="constant">root</code> access. How can we do this?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -756,13 +754,13 @@ smb: \&gt; q
 		(or the equivalent <code class="constant">wheel</code> on some UNIX systems) that has a GID of 0.
 		This must be the primary GID of the account of the user who is a member of the Windows <code class="constant">
 		Domain Admins</code> account.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558270"></a><a name="id2558272"></a><p><b>6.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558262"></a><a name="id2558265"></a><p><b>6.</b></p></td><td align="left" valign="top"><p>
 		Why must I map Windows Domain Groups to UNIX groups?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Samba-3 does not permit a Domain Group to become visible to Domain network clients unless the account
 		has a UNIX group account equivalent. The Domain groups that should be given UNIX equivalents are
 		<span class="guimenu">Domain Guests</span>, <span class="guimenu">Domain Users</span>, and <span class="guimenu">Domain Admins</span>.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558306"></a><a name="id2558308"></a><p><b>7.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558299"></a><a name="id2558301"></a><p><b>7.</b></p></td><td align="left" valign="top"><p>
 		I deleted my <code class="constant">root</code> account and now I cannot add it back! What can I do?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		This is a nasty problem. Fortunately, there is a solution.
@@ -774,7 +772,7 @@ smb: \&gt; q
 			Use the <code class="literal">smbpasswd</code> to add the root account.
 			</p></li><li><p>
 			Restore the <code class="filename">group_mapping.tdb</code> file.
-			</p></li></ol></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558373"></a><a name="id2558375"></a><p><b>8.</b></p></td><td align="left" valign="top"><p>
+			</p></li></ol></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558366"></a><a name="id2558368"></a><p><b>8.</b></p></td><td align="left" valign="top"><p>
 		When I run <code class="literal">net groupmap list</code>, it reports a group called <span class="guimenu">Administrators</span>
 		as well as <span class="guimenu">Domain Admins</span>. What is the difference between them?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
@@ -782,7 +780,7 @@ smb: \&gt; q
 		present as the Local Group account on a Domain Member server or workstation. Samba uses only Domain
 		Groups at this time. A Workstation or Server Local Group has no meaning in a Samba context. This
 		may change at some later date. These accounts are provided only so that security objects are correctly shown.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558418"></a><a name="id2558420"></a><p><b>9.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558411"></a><a name="id2558413"></a><p><b>9.</b></p></td><td align="left" valign="top"><p>
 		What is the effect of changing the name of a Samba server or of changing the Domain name?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		If you elect to change the name of the Samba server, on restarting <code class="literal">smbd</code>,
@@ -794,7 +792,7 @@ smb: \&gt; q
 		SID before the change is made. You can back up the SID using the <code class="literal">net getlocalsid</code> (Samba-3)
 		or the <code class="literal">smbpasswd</code> (Samba-2.2.x). To change the SID, you use the same tool. Be sure
 		to check the man page for this command for detailed instructions regarding the steps involved.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558467"></a><a name="id2558469"></a><p><b>10.</b></p></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2558460"></a><a name="id2558462"></a><p><b>10.</b></p></td><td align="left" valign="top"><p>
 		How can I manage user accounts from my Windows XP Professional workstation?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Samba-3 implements a Windows NT4-style security domain architecture. This type of Domain cannot
diff --git a/docs/htmldocs/Samba3-ByExample/unixclients.html b/docs/htmldocs/Samba3-ByExample/unixclients.html
index 8305a9c6cc..b8bba0ad56 100644
--- a/docs/htmldocs/Samba3-ByExample/unixclients.html
+++ b/docs/htmldocs/Samba3-ByExample/unixclients.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�7.�Adding Domain Member Servers and Clients</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="next" href="upgrades.html" title="Chapter�8.�Updating Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�7.�Adding Domain Member Servers and Clients</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DMSMig.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="upgrades.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unixclients"></a>Chapter�7.�Adding Domain Member Servers and Clients</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unixclients.html#id2589228">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589282">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589317">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589345">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2589994">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590094">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596343">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596918">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596972">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2589130"></a><a class="indexterm" name="id2589137"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�7.�Adding Domain Member Servers and Clients</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="next" href="upgrades.html" title="Chapter�8.�Updating Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�7.�Adding Domain Member Servers and Clients</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DMSMig.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="upgrades.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unixclients"></a>Chapter�7.�Adding Domain Member Servers and Clients</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unixclients.html#id2589239">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589292">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2589328">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#id2589356">Technical Issues</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2590005">Political Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2590105">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="unixclients.html#sdcsdmldap">Samba Domain with Samba Domain Member Server  Using NSS LDAP</a></span></dt><dt><span class="sect2"><a href="unixclients.html#wdcsdm">NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</a></span></dt><dt><span class="sect2"><a href="unixclients.html#dcwonss">NT4/Samba Domain with Samba Domain Member Server without NSS Support</a></span></dt><dt><span class="sect2"><a href="unixclients.html#adssdm">Active Directory Domain with Samba Domain Member Server</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596311">UNIX/Linux Client Domain Member</a></span></dt><dt><span class="sect2"><a href="unixclients.html#id2596886">Key Points Learned</a></span></dt></dl></dd><dt><span class="sect1"><a href="unixclients.html#id2596940">Questions and Answers</a></span></dt></dl></div><p><a class="indexterm" name="id2589141"></a><a class="indexterm" name="id2589148"></a>
 	The most frequently discussed Samba subjects over the past 2 years have focused around domain control and printing. 
 	It is well known that Samba is a file and print server. A recent survey conducted by <span class="emphasis"><em>Open Magazine</em></span> found 
 	that of all respondents, 97 percent use Samba for file and print services, and 68 percent use Samba for Domain Control. See the 
@@ -11,16 +11,16 @@
 	exciting aspects of Samba deployment. This chapter directs your attention to provide important information on
 	the addition of Samba servers into your present Windows network  whatever the controlling technology
 	may be. So let's get back to our good friends at Abmas.
-	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589228"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2589234"></a><a class="indexterm" name="id2589242"></a>
+	</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589239"></a>Introduction</h2></div></div></div><p><a class="indexterm" name="id2589245"></a><a class="indexterm" name="id2589253"></a>
 	Looking back over the achievements of the past year or two, daily events at Abmas are rather straightforward
 	with not too many distractions or problems. Your team is doing well, but a number of employees
 	are asking for Linux desktop systems. Your network has grown and demands additional domain member servers. Let's
 	get on with this; Christine and Stan are ready to go.
-	</p><p><a class="indexterm" name="id2589263"></a>
+	</p><p><a class="indexterm" name="id2589274"></a>
 	Stan is firmly in control of the department of the future, while Christine is enjoying a stable and
 	predictable network environment. It is time to add more servers and to add Linux desktops. It is
 	time to meet the demands of future growth and endure trial by fire.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589282"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2589288"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589292"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2589299"></a>
 	You must now add UNIX/Linux domain member servers to your network. You have a friend who has a Windows 2003
 	Active Directory domain network who wants to add a Samba/Linux server and has asked Christine to help him
 	out. Your real objective is to help Christine to see more of the way the Microsoft world lives and use
@@ -30,8 +30,8 @@
 	these systems to make sure that Abmas is not building islands of technology. You ask Christine to
 	do likewise at Swodniw Biz NL (your friend's company) to help them to evaluate a Linux desktop. You want to make
 	the right decision, don't you?
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589317"></a>Dissection and Discussion</h2></div></div></div><p>
-	<a class="indexterm" name="id2589325"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589328"></a>Dissection and Discussion</h2></div></div></div><p>
+	<a class="indexterm" name="id2589336"></a>
 	Recent Samba mailing-list activity is witness to how many sites are using winbind. Some have no trouble
 	at all with it, yet to others the problems seem insurmountable. Periodically there are complaints concerning
 	an inability to achieve identical user and group IDs between Windows and UNIX environments.
@@ -39,28 +39,28 @@
 	You provide step-by-step implementations of the various tools that can be used for identity
 	resolution. You also provide working examples of solutions for integrated authentication for
 	both UNIX/Linux and Windows environments.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589345"></a>Technical Issues</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589356"></a>Technical Issues</h3></div></div></div><p>
 		One of the great challenges we face when people ask us, &#8220;<span class="quote">What is the best way to solve
 		this problem?</span>&#8221; is to get beyond the facts so we not only can clearly comprehend
 		the immediate technical problem, but also can understand how needs may change.
 		</p><p>
-		<a class="indexterm" name="id2589364"></a>
+		<a class="indexterm" name="id2589375"></a>
 		There are a few facts we should note when dealing with the question of how best to
 		integrate UNIX/Linux clients and servers into a Windows networking environment:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2589380"></a>
-			<a class="indexterm" name="id2589387"></a>
-			<a class="indexterm" name="id2589394"></a>
-			<a class="indexterm" name="id2589403"></a>
-			<a class="indexterm" name="id2589410"></a>
+			<a class="indexterm" name="id2589391"></a>
+			<a class="indexterm" name="id2589398"></a>
+			<a class="indexterm" name="id2589405"></a>
+			<a class="indexterm" name="id2589414"></a>
+			<a class="indexterm" name="id2589421"></a>
 			A domain controller (PDC or BDC) is always authoritative for all accounts in its domain.
 			This means that a BDC must (of necessity) be able to resolve all account UIDs and GIDs
 			to the same values that the PDC resolved them to.
 			</p></li><li><p>
-			<a class="indexterm" name="id2589425"></a>
-			<a class="indexterm" name="id2589432"></a>
-			<a class="indexterm" name="id2589444"></a>
-			<a class="indexterm" name="id2589451"></a>
+			<a class="indexterm" name="id2589436"></a>
+			<a class="indexterm" name="id2589443"></a>
+			<a class="indexterm" name="id2589455"></a>
+			<a class="indexterm" name="id2589462"></a>
 			A domain member can be authoritative for local accounts, but is never authoritative for
 			domain accounts. If a user is accessing a domain member server and that user's account
 			is not known locally, the domain member server must resolve the identity of that user
@@ -70,26 +70,26 @@
 			Samba, when running on a domain member server, can resolve user identities from a
 			number of sources:
 			</p><div class="itemizedlist"><ul type="circle"><li><p>
-				<a class="indexterm" name="id2589483"></a>
-				<a class="indexterm" name="id2589490"></a>
-				<a class="indexterm" name="id2589497"></a>
-				<a class="indexterm" name="id2589503"></a>
-				<a class="indexterm" name="id2589510"></a>
+				<a class="indexterm" name="id2589494"></a>
+				<a class="indexterm" name="id2589501"></a>
+				<a class="indexterm" name="id2589508"></a>
+				<a class="indexterm" name="id2589514"></a>
+				<a class="indexterm" name="id2589521"></a>
 				By executing a system <code class="literal">getpwnam()</code> or <code class="literal">getgrnam()</code> call. 
 				On systems that support it, this utilizes the name service switch (NSS) facility to 
 				resolve names according to the configuration of the <code class="filename">/etc/nsswitch.conf</code> 
 				file. NSS can be configured to use LDAP, winbind, NIS, or local files.
 				</p></li><li><p>
-				<a class="indexterm" name="id2589543"></a>
-				<a class="indexterm" name="id2589550"></a>
-				<a class="indexterm" name="id2589557"></a>
+				<a class="indexterm" name="id2589554"></a>
+				<a class="indexterm" name="id2589561"></a>
+				<a class="indexterm" name="id2589568"></a>
 				Performing, via NSS, a direct LDAP search (where an LDAP passdb backend has been configured).
 				This requires the use of the PADL nss_ldap tool (or equivalent).
 				</p></li><li><p>
-				<a class="indexterm" name="id2589571"></a>
-				<a class="indexterm" name="id2589578"></a>
-				<a class="indexterm" name="id2589584"></a>
-				<a class="indexterm" name="id2589591"></a>
+				<a class="indexterm" name="id2589582"></a>
+				<a class="indexterm" name="id2589589"></a>
+				<a class="indexterm" name="id2589595"></a>
+				<a class="indexterm" name="id2589602"></a>
 				Directly by querying <code class="literal">winbindd</code>. The <code class="literal">winbindd</code>
 				contacts a domain controller to attempt to resolve the identity of the user or group. It
 				receives the Windows networking security identifier (SID) for that appropriate
@@ -97,8 +97,8 @@
 				creates an entry in its <code class="filename">winbindd_idmap.tdb</code> and 
 				<code class="filename">winbindd_cache.tdb</code> files.
 				</p><p>
-				<a class="indexterm" name="id2589631"></a>
-				<a class="indexterm" name="id2589638"></a>
+				<a class="indexterm" name="id2589642"></a>
+				<a class="indexterm" name="id2589649"></a>
 				If the parameter <a class="link" href="smb.conf.5.html#IDMAPBACKEND" target="_top">idmap backend = ldap:ldap://myserver.domain</a>
 				was specified and the LDAP server has been configured with a container in which it may
 				store the IDMAP entries, all domain members may share a common mapping.
@@ -111,37 +111,37 @@
 			in the <code class="filename">smb.conf</code> file. Some of the configuration options are rather less than obvious to the 
 			casual user.
 			</p></li><li><p>
-			<a class="indexterm" name="id2589703"></a>
-			<a class="indexterm" name="id2589710"></a>
-			<a class="indexterm" name="id2589720"></a>
+			<a class="indexterm" name="id2589714"></a>
+			<a class="indexterm" name="id2589721"></a>
+			<a class="indexterm" name="id2589731"></a>
 			If you wish to make use of accounts (users and/or groups) that are local to (i.e., capable
 			of being resolved using) the NSS facility, it is possible to use the 
 			<a class="link" href="smb.conf.5.html#WINBINDTRUSTEDDOMAINSONLY" target="_top">winbind trusted domains only = Yes</a>
 			in the <code class="filename">smb.conf</code> file. This parameter specifically applies to domain controllers, 
 			and to domain member servers.
 			</p></li></ul></div><p>
-		<a class="indexterm" name="id2589755"></a>
-		<a class="indexterm" name="id2589762"></a>
-		<a class="indexterm" name="id2589769"></a>
+		<a class="indexterm" name="id2589766"></a>
+		<a class="indexterm" name="id2589773"></a>
+		<a class="indexterm" name="id2589780"></a>
 		For many administrators, it should be plain that the use of an LDAP-based repository for all network
 		accounts (both for POSIX accounts and for Samba accounts) provides the most elegant and
 		controllable facility. You eventually appreciate the decision to use LDAP.
 		</p><p>
-		<a class="indexterm" name="id2589784"></a>
-		<a class="indexterm" name="id2589790"></a>
-		<a class="indexterm" name="id2589797"></a>
+		<a class="indexterm" name="id2589795"></a>
+		<a class="indexterm" name="id2589801"></a>
+		<a class="indexterm" name="id2589808"></a>
 		If your network account information resides in an LDAP repository, you should use it ahead of any
 		alternative method. This means that if it is humanly possible to use the <code class="literal">nss_ldap</code>
 		tools to resolve UNIX account UIDs/GIDs via LDAP, this is the preferred solution, because it provides
 		a more readily controllable method for asserting the exact same user and group identifiers 
 		throughout the network.
 		</p><p>
-		<a class="indexterm" name="id2589820"></a>
-		<a class="indexterm" name="id2589829"></a>
-		<a class="indexterm" name="id2589836"></a>
-		<a class="indexterm" name="id2589843"></a>
-		<a class="indexterm" name="id2589850"></a>
-		<a class="indexterm" name="id2589857"></a>
+		<a class="indexterm" name="id2589831"></a>
+		<a class="indexterm" name="id2589840"></a>
+		<a class="indexterm" name="id2589847"></a>
+		<a class="indexterm" name="id2589854"></a>
+		<a class="indexterm" name="id2589861"></a>
+		<a class="indexterm" name="id2589868"></a>
 		In the situation where UNIX accounts are held on the domain member server itself, the only effective
 		way to use them involves the <code class="filename">smb.conf</code> entry 
 		<a class="link" href="smb.conf.5.html#WINBINDTRUSTEDDOMAINSONLY" target="_top">winbind trusted domains only = Yes</a>. This forces 
@@ -149,10 +149,10 @@
 		then be controlled via <code class="filename">/etc/nsswitch.conf</code> file settings. The use of this parameter
 		disables the use of Samba with trusted domains (i.e., external domains).
 		</p><p>
-		<a class="indexterm" name="id2589908"></a>
-		<a class="indexterm" name="id2589915"></a>
-		<a class="indexterm" name="id2589924"></a>
-		<a class="indexterm" name="id2589931"></a>
+		<a class="indexterm" name="id2589919"></a>
+		<a class="indexterm" name="id2589926"></a>
+		<a class="indexterm" name="id2589935"></a>
+		<a class="indexterm" name="id2589942"></a>
 		Winbind can be used to create an appliance mode domain member server. In this capacity, <code class="literal">winbindd</code>
 		is configured to automatically allocate UIDs/GIDs from numeric ranges set in the <code class="filename">smb.conf</code> file. The allocation
 		is made for all accounts that connect to that domain member server, whether within its own domain or from
@@ -161,16 +161,16 @@
 		same UID/GID on both servers  however, this is transparent to the Windows network user. This data
 		is stored in the <code class="filename">winbindd_idmap.tdb</code> and <code class="filename">winbindd_cache.tdb</code> files.
 		</p><p>
-		<a class="indexterm" name="id2589979"></a>
+		<a class="indexterm" name="id2589990"></a>
 		The use of an LDAP backend for the Winbind IDMAP facility permits Windows domain SIDs
 		mappings to UIDs/GIDs to be stored centrally. The result is a consistent mapping across all domain member
 		servers so configured. This solves one of the major headaches for network administrators who need to copy
 		files between or across network file servers.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589994"></a>Political Issues</h3></div></div></div><p>
-		<a class="indexterm" name="id2590002"></a>
-		<a class="indexterm" name="id2590009"></a>
-		<a class="indexterm" name="id2590015"></a>
-		<a class="indexterm" name="id2590024"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2590005"></a>Political Issues</h3></div></div></div><p>
+		<a class="indexterm" name="id2590013"></a>
+		<a class="indexterm" name="id2590020"></a>
+		<a class="indexterm" name="id2590026"></a>
+		<a class="indexterm" name="id2590035"></a>
 		One of the most fierce conflicts recently being waged is resistance to the adoption of LDAP, in
 		particular OpenLDAP, as a replacement for UNIX NIS (previously called Yellow Pages). Let's face it, LDAP
 		is different and requires a new approach to the need for a better identity management solution. The more
@@ -182,23 +182,23 @@
 		you can't use Windows Active Directory in a heterogenous environment  it can be done, it just requires 
 		commercial integration products. But it's not what Active Directory was designed for.
 		</p><p>
-		<a class="indexterm" name="id2590063"></a>
-		<a class="indexterm" name="id2590069"></a>
+		<a class="indexterm" name="id2590074"></a>
+		<a class="indexterm" name="id2590080"></a>
 		A number of long-term UNIX devotees have recently commented in various communications that the Samba Team
 		is the first application group to almost force network administrators to use LDAP. It should be pointed
 		out that we resisted this for as long as we could. It is not out of laziness or malice that LDAP has
 		finally emerged as the preferred identity management backend for Samba. We recommend LDAP for your total
 		organizational directory needs.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590094"></a>Implementation</h2></div></div></div><p>
-	<a class="indexterm" name="id2590102"></a>
-	<a class="indexterm" name="id2590112"></a>
-	<a class="indexterm" name="id2590121"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590105"></a>Implementation</h2></div></div></div><p>
+	<a class="indexterm" name="id2590113"></a>
+	<a class="indexterm" name="id2590123"></a>
+	<a class="indexterm" name="id2590132"></a>
 	The domain member server and the domain member client are at the center of focus in this chapter.
 	Configuration of Samba-3 domain controller is covered in earlier chapters, so if your 
 	interest is in domain controller configuration, you will not find that here. You will find good
 	oil that helps you to add domain member servers and clients.
 	</p><p>
-	<a class="indexterm" name="id2590137"></a>
+	<a class="indexterm" name="id2590148"></a>
 	In practice, domain member servers and domain member workstations are very different entities, but in
 	terms of technology they share similar core infrastructure. A technologist would argue that servers
 	and workstations are identical. Many users would argue otherwise, given that in a well-disciplined
@@ -206,15 +206,15 @@
 	are located on servers. A workstation is frequently viewed as a disposable (easy to replace) item,
 	but a server is viewed as a core component of the business.
 	</p><p>
-	<a class="indexterm" name="id2590159"></a>
+	<a class="indexterm" name="id2590170"></a>
 	We can look at this another way. If a workstation breaks down, one user is affected, but if a
 	server breaks down, hundreds of users may not be able to work. The services that a workstation
 	must provide are document- and file-production oriented; a server provides information storage
 	and is distribution oriented.
 	</p><p>
-	<a class="indexterm" name="id2590175"></a>
-	<a class="indexterm" name="id2590182"></a>
-	<a class="indexterm" name="id2590189"></a>
+	<a class="indexterm" name="id2590186"></a>
+	<a class="indexterm" name="id2590193"></a>
+	<a class="indexterm" name="id2590200"></a>
 	<span class="emphasis"><em>Why is this important?</em></span> For starters, we must identify what
 	components of the operating system and its environment must be configured. Also, it is necessary
 	to recognize where the interdependencies between the various services to be used are.
@@ -226,12 +226,12 @@
 	So, in this chapter we demonstrate how to implement the technology. It is done within a context of
 	what type of service need must be fulfilled.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sdcsdmldap"></a>Samba Domain with Samba Domain Member Server  Using NSS LDAP</h3></div></div></div><p>
-	<a class="indexterm" name="id2590230"></a>
-	<a class="indexterm" name="id2590236"></a>
-	<a class="indexterm" name="id2590243"></a>
-	<a class="indexterm" name="id2590250"></a>
-	<a class="indexterm" name="id2590259"></a>
-	<a class="indexterm" name="id2590266"></a>
+	<a class="indexterm" name="id2590241"></a>
+	<a class="indexterm" name="id2590247"></a>
+	<a class="indexterm" name="id2590254"></a>
+	<a class="indexterm" name="id2590261"></a>
+	<a class="indexterm" name="id2590270"></a>
+	<a class="indexterm" name="id2590277"></a>
 	In this example, it is assumed that you have Samba PDC/BDC servers. This means you are using
 	an LDAP ldapsam backend. We are adding to the LDAP backend database (directory)
 	containers for use by the IDMAP facility. This makes it possible to have globally consistent
@@ -247,9 +247,9 @@
 	<em class="parameter"><code>idmap gid</code></em> ranges. Where LDAP is used, the mappings can be stored in LDAP
 	so that all domain member servers can use a consistent mapping.
 	</p><p>
-	<a class="indexterm" name="id2590336"></a>
-	<a class="indexterm" name="id2590343"></a>
-	<a class="indexterm" name="id2590350"></a>
+	<a class="indexterm" name="id2590341"></a>
+	<a class="indexterm" name="id2590348"></a>
+	<a class="indexterm" name="id2590355"></a>
 	If your installation is accessed only from clients that are members of your own domain, and all 
 	user accounts are present in a local passdb backend then it is not necessary to run
 	<code class="literal">winbindd</code>. The local passdb backend can be in smbpasswd, tdbsam, or in ldapsam.
@@ -259,19 +259,19 @@
 	<code class="literal">getpwnam()</code> system call. On NSS-enabled systems, the actual POSIX account
 	source can be provided from
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2590387"></a>
-		<a class="indexterm" name="id2590394"></a>
+		<a class="indexterm" name="id2590392"></a>
+		<a class="indexterm" name="id2590398"></a>
 		Accounts in <code class="filename">/etc/passwd</code> or in <code class="filename">/etc/group</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2590417"></a>
-		<a class="indexterm" name="id2590424"></a>
-		<a class="indexterm" name="id2590430"></a>
-		<a class="indexterm" name="id2590437"></a>
-		<a class="indexterm" name="id2590444"></a>
-		<a class="indexterm" name="id2590450"></a>
-		<a class="indexterm" name="id2590457"></a>
-		<a class="indexterm" name="id2590464"></a>
-		<a class="indexterm" name="id2590471"></a>
+		<a class="indexterm" name="id2590422"></a>
+		<a class="indexterm" name="id2590428"></a>
+		<a class="indexterm" name="id2590435"></a>
+		<a class="indexterm" name="id2590442"></a>
+		<a class="indexterm" name="id2590449"></a>
+		<a class="indexterm" name="id2590455"></a>
+		<a class="indexterm" name="id2590462"></a>
+		<a class="indexterm" name="id2590469"></a>
+		<a class="indexterm" name="id2590476"></a>
 		Resolution via NSS. On NSS-enabled systems, there is usually a facility to resolve IDs
 		via multiple methods. The methods typically include <code class="literal">files</code>,
 		<code class="literal">compat</code>, <code class="literal">db</code>, <code class="literal">ldap</code>, 
@@ -283,13 +283,13 @@
 	the user account backend is not shared by any other Samba server  instead, it is
 	used only locally on the Samba domain member server under discussion.
 	</p></div><p>
-	<a class="indexterm" name="id2590550"></a>
+	<a class="indexterm" name="id2590555"></a>
 	The diagram in <a class="link" href="unixclients.html#ch9-sambadc" title="Figure�7.2.�Samba Domain: Samba Member Server">&#8220;Samba Domain: Samba Member Server&#8221;</a> demonstrates the relationship of Samba and system 
 	components that are involved in the identity resolution process where Samba is used as a domain
 	member server within a Samba domain control network.
 	</p><div class="figure"><a name="ch9-sambadc"></a><p class="title"><b>Figure�7.2.�Samba Domain: Samba Member Server</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap9-SambaDC.png" width="324" alt="Samba Domain: Samba Member Server"></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2590612"></a>
-	<a class="indexterm" name="id2590619"></a>
+	<a class="indexterm" name="id2590617"></a>
+	<a class="indexterm" name="id2590624"></a>
 	In this example configuration, Samba will directly search the LDAP-based passwd backend ldapsam
 	to obtain authentication and user identity information. The IDMAP information is stored in the LDAP
 	backend so that it can be shared by all domain member servers so that every user will have a
@@ -297,14 +297,14 @@
 	(i.e., not having the same SID as the domain it is a member of) domains. The configuration of 
 	NSS will ensure that all UNIX processes will obtain a consistent UID/GID.
 	</p><p>
-	The instructions given here apply to the Samba environment shown in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a> and <a class="link" href="net2000users.html" title="Chapter�6.�A Distributed 2000-User Network">&#8220;A Distributed 2000-User Network&#8221;</a>.
+	The instructions given here apply to the Samba environment shown in <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a> and <a class="link" href="2000users.html" title="Chapter�6.�A Distributed 2000-User Network">&#8220;A Distributed 2000-User Network&#8221;</a>.
 	If the network does not have an LDAP slave server (i.e., <a class="link" href="happy.html" title="Chapter�5.�Making Happy Users">&#8220;Making Happy Users&#8221;</a> configuration), 
 	change the target LDAP server from <code class="constant">lapdc</code> to <code class="constant">massive.</code>
-	</p><div class="procedure"><a name="id2590668"></a><p class="title"><b>Procedure�7.1.�Configuration of NSS_LDAP-Based Identity Resolution</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2590672"></a><p class="title"><b>Procedure�7.1.�Configuration of NSS_LDAP-Based Identity Resolution</b></p><ol type="1"><li><p>
 		Create the <code class="filename">smb.conf</code> file as shown in <a class="link" href="unixclients.html#ch9-sdmsdc" title="Example�7.1.�Samba Domain Member in Samba Domain Using LDAP smb.conf File">&#8220;Samba Domain Member in Samba Domain Using LDAP  smb.conf File&#8221;</a>. Locate
 		this file in the directory <code class="filename">/etc/samba</code>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2590706"></a>
+		<a class="indexterm" name="id2590710"></a>
 		Configure the file that will be used by <code class="constant">nss_ldap</code> to
 		locate and communicate with the LDAP server. This file is called <code class="filename">ldap.conf</code>.
 		If your implementation of <code class="constant">nss_ldap</code> is consistent with
@@ -326,8 +326,8 @@
 		Configure the NSS control file so it matches the one shown in
 		<a class="link" href="unixclients.html#ch9-sdmnss" title="Example�7.4.�NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf">&#8220;NSS using LDAP for Identity Resolution  File: /etc/nsswitch.conf&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2590794"></a>
-		<a class="indexterm" name="id2590800"></a>
+		<a class="indexterm" name="id2590798"></a>
+		<a class="indexterm" name="id2590805"></a>
 		Before proceeding to configure Samba, validate the operation of the NSS identity 
 		resolution via LDAP by executing:
 </p><pre class="screen">
@@ -362,9 +362,9 @@ Finances:x:1001:
 PIOps:x:1002:
 sammy:x:4321:
 </pre><p>
-		<a class="indexterm" name="id2590865"></a>
-		<a class="indexterm" name="id2590872"></a>
-		<a class="indexterm" name="id2590878"></a>
+		<a class="indexterm" name="id2590869"></a>
+		<a class="indexterm" name="id2590876"></a>
+		<a class="indexterm" name="id2590883"></a>
 		This shows that all is working as it should be. Notice that in the LDAP database
 		the users' primary and secondary group memberships are identical. It is not
 		necessary to add secondary group memberships (in the group database) if the
@@ -374,7 +374,7 @@ sammy:x:4321:
 		conditions. It is intended that these limitations with winbind will be resolved soon
 		after Samba-3.0.20 has been released.
 		</p></li><li><p>
-		<a class="indexterm" name="id2590902"></a>
+		<a class="indexterm" name="id2590906"></a>
 		The LDAP directory must have a container object for IDMAP data. There are several ways you can
 		check that your LDAP database is able to receive IDMAP information. One of the simplest is to
 		execute:
@@ -383,7 +383,7 @@ sammy:x:4321:
 dn: ou=Idmap,dc=abmas,dc=biz
 ou: idmap
 </pre><p>
-		<a class="indexterm" name="id2590925"></a>
+		<a class="indexterm" name="id2590929"></a>
 		If the execution of this command does not return IDMAP entries, you need to create an LDIF
 		template file (see <a class="link" href="unixclients.html#ch9-ldifadd" title="Example�7.2.�LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF">&#8220;LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF&#8221;</a>). You can add the required entries using
 		the following command:
@@ -399,8 +399,8 @@ ou: idmap
 <code class="prompt">root# </code> smbpasswd -w not24get
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2590989"></a>
-		<a class="indexterm" name="id2591000"></a>
+		<a class="indexterm" name="id2590993"></a>
+		<a class="indexterm" name="id2591004"></a>
 		The system is ready to join the domain. Execute the following:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join -U root%not24get
@@ -418,10 +418,10 @@ Joined domain MEGANET2.
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join -S 'pdc-name' -U administrator%password -d 5
 </pre><p>
-		<a class="indexterm" name="id2591072"></a>
-		<a class="indexterm" name="id2591079"></a>
-		<a class="indexterm" name="id2591086"></a>
-		<a class="indexterm" name="id2591093"></a>
+		<a class="indexterm" name="id2591076"></a>
+		<a class="indexterm" name="id2591083"></a>
+		<a class="indexterm" name="id2591090"></a>
+		<a class="indexterm" name="id2591097"></a>
 		Note: Use "root" for UNIX/Linux and Samba, use "Administrator" for Windows NT4/200X. If the cause of
 		the failure appears to be related to a rejected or failed NT_SESSION_SETUP*  or an error message that
 		says NT_STATUS_ACCESS_DENIED immediately check the Windows registry setting that controls the
@@ -449,7 +449,7 @@ NT_STATUS_ACCESS_DENIED
 Join to 'MEGANET2' failed.
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2591154"></a>
+		<a class="indexterm" name="id2591158"></a>
 		Just joining the domain is not quite enough; you must now provide a privileged set
 		of credentials through which <code class="literal">winbindd</code> can interact with the 
 		domain servers. Execute the following to implant the necessary credentials:
@@ -460,7 +460,7 @@ Join to 'MEGANET2' failed.
 		</p></li><li><p>
 		You may now start Samba in the usual manner, and your Samba domain member server
 		is ready for use. Just add shares as required.
-		</p></li></ol></div><div class="example"><a name="ch9-sdmsdc"></a><p class="title"><b>Example�7.1.�Samba Domain Member in Samba Domain Using LDAP  <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2591232"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2591244"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2591256"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2591267"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2591279"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id2591291"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2591302"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2591314"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2591326"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2591337"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2591350"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2591361"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2591373"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591385"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2591397"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2591409"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2591421"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2591433"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591445"></a><em class="parameter"><code>idmap backend = ldap:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591457"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2591469"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2591481"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591493"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2591505"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2591525"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2591537"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2591549"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2591560"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2591581"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2591593"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2591604"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591616"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591628"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2591648"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2591660"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2591672"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2591684"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch9-ldifadd"></a><p class="title"><b>Example�7.2.�LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</b></p><div class="example-contents"><pre class="screen">
+		</p></li></ol></div><div class="example"><a name="ch9-sdmsdc"></a><p class="title"><b>Example�7.1.�Samba Domain Member in Samba Domain Using LDAP  <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2591236"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2591248"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2591260"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2591271"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2591283"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id2591295"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2591306"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2591318"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2591330"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2591342"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2591354"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2591366"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2591377"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591389"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2591401"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2591413"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2591425"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2591437"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591449"></a><em class="parameter"><code>idmap backend = ldap:ldap://lapdc.abmas.biz</code></em></td></tr><tr><td><a class="indexterm" name="id2591461"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2591473"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2591485"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591497"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2591509"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2591530"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2591541"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2591553"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2591564"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2591585"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2591597"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2591608"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591620"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2591632"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2591652"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2591664"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2591676"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2591688"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="ch9-ldifadd"></a><p class="title"><b>Example�7.2.�LDIF IDMAP Add-On Load File  File: /etc/openldap/idmap.LDIF</b></p><div class="example-contents"><pre class="screen">
 dn: ou=Idmap,dc=abmas,dc=biz
 objectClass: organizationalUnit
 ou: idmap
@@ -507,18 +507,18 @@ aliases:        files
 		</p></li><li><p>
 		The Samba domain member server must be part of a Windows NT4 Domain, or a Samba Domain.
 		</p></li></ul></div><p>
-	<a class="indexterm" name="id2591815"></a>
-	<a class="indexterm" name="id2591821"></a>
-	<a class="indexterm" name="id2591828"></a>
+	<a class="indexterm" name="id2591819"></a>
+	<a class="indexterm" name="id2591825"></a>
+	<a class="indexterm" name="id2591832"></a>
 	Later in the chapter, you can see how to configure a Samba domain member server for a Windows ADS domain.
 	Right now your objective is to configure a Samba server that can be a member of a Windows NT4-style
 	domain and/or does not use LDAP.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2591844"></a>
+	<a class="indexterm" name="id2591848"></a>
 	If you use <code class="literal">winbind</code> for identity resolution, make sure that there are no
 	duplicate accounts.
 	</p><p>
-	<a class="indexterm" name="id2591861"></a>
+	<a class="indexterm" name="id2591865"></a>
 	For example, do not have more than one account that has UID=0 in the password database. If there 
 	is an account called <code class="constant">root</code> in the <code class="filename">/etc/passwd</code> database, 
 	it is okay to have an account called <code class="constant">root</code> in the LDAP ldapsam or in the 
@@ -526,32 +526,32 @@ aliases:        files
 	break. This means that the <code class="constant">Administrator</code> account must be called 
 	<code class="constant">root</code>.
 	</p><p>
-	<a class="indexterm" name="id2591898"></a>
-	<a class="indexterm" name="id2591904"></a>
-	<a class="indexterm" name="id2591911"></a>
+	<a class="indexterm" name="id2591902"></a>
+	<a class="indexterm" name="id2591909"></a>
+	<a class="indexterm" name="id2591915"></a>
 	Winbind will break if there is an account in <code class="filename">/etc/passwd</code> that has 
 	the same UID as an account that is in LDAP ldapsam (or in tdbsam) but that differs in name only.
 	</p></div><p>
-	<a class="indexterm" name="id2591930"></a>
-	<a class="indexterm" name="id2591937"></a>
-	<a class="indexterm" name="id2591944"></a>
-	<a class="indexterm" name="id2591950"></a>
-	<a class="indexterm" name="id2591960"></a>
+	<a class="indexterm" name="id2591934"></a>
+	<a class="indexterm" name="id2591941"></a>
+	<a class="indexterm" name="id2591948"></a>
+	<a class="indexterm" name="id2591954"></a>
+	<a class="indexterm" name="id2591964"></a>
 	The following configuration uses CIFS/SMB protocols alone to obtain user and group credentials.
 	The winbind information is locally cached in the <code class="filename">winbindd_cache.tdb winbindd_idmap.tdb</code>
 	files. This provides considerable performance benefits compared with the LDAP solution, particularly
 	where the LDAP lookups must traverse WAN links. You may examine the contents of these
 	files using the tool <code class="literal">tdbdump</code>, though you may have to build this from the Samba
 	source code if it has not been supplied as part of a binary package distribution that you may be using.
-	</p><div class="procedure"><a name="id2591989"></a><p class="title"><b>Procedure�7.2.�Configuration of Winbind-Based Identity Resolution</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2591993"></a><p class="title"><b>Procedure�7.2.�Configuration of Winbind-Based Identity Resolution</b></p><ol type="1"><li><p>
 		Using your favorite text editor, create the <code class="filename">smb.conf</code> file so it has the contents
 		shown in <a class="link" href="unixclients.html#ch0-NT4DSDM" title="Example�7.5.�Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain">&#8220;Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2592021"></a>
+		<a class="indexterm" name="id2592025"></a>
 		Edit the <code class="filename">/etc/nsswitch.conf</code> so it has the entries shown in
 		<a class="link" href="unixclients.html#ch9-sdmnss" title="Example�7.4.�NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf">&#8220;NSS using LDAP for Identity Resolution  File: /etc/nsswitch.conf&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2592047"></a>
+		<a class="indexterm" name="id2592051"></a>
 		The system is ready to join the domain. Execute the following:
 </p><pre class="screen">
 net rpc join -U root%not2g4et
@@ -560,8 +560,8 @@ Joined domain MEGANET2.
 		This indicates that the domain join succeed.
 
 		</p></li><li><p>
-		<a class="indexterm" name="id2592073"></a>
-		<a class="indexterm" name="id2592080"></a>
+		<a class="indexterm" name="id2592078"></a>
+		<a class="indexterm" name="id2592084"></a>
 		Validate operation of <code class="literal">winbind</code> using the <code class="literal">wbinfo</code>
 		tool as follows:
 </p><pre class="screen">
@@ -588,9 +588,9 @@ MEGANET2+PIOps
 </pre><p>
 		This shows that domain groups have been correctly obtained also.
 		</p></li><li><p>
-		<a class="indexterm" name="id2592136"></a>
-		<a class="indexterm" name="id2592143"></a>
-		<a class="indexterm" name="id2592150"></a>
+		<a class="indexterm" name="id2592140"></a>
+		<a class="indexterm" name="id2592147"></a>
+		<a class="indexterm" name="id2592154"></a>
 		The next step verifies that NSS is able to obtain this information
 		correctly from <code class="literal">winbind</code> also.
 </p><pre class="screen">
@@ -631,7 +631,7 @@ MEGANET2+PIOps:x:10005:
 </pre><p>
 		</p></li><li><p>
 		The Samba member server of a Windows NT4 domain is ready for use.
-		</p></li></ol></div><div class="example"><a name="ch0-NT4DSDM"></a><p class="title"><b>Example�7.5.�Samba Domain Member Server Using Winbind <code class="filename">smb.conf</code> File for NT4 Domain</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2592261"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2592272"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2592284"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2592296"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2592308"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2592319"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592331"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2592343"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592354"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2592366"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2592378"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2592390"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2592402"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592414"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592425"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2592438"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2592449"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2592461"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2592473"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2592485"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2592506"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2592517"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2592529"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2592541"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2592561"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2592573"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2592585"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592596"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592608"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2592628"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2592640"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2592652"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2592664"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="dcwonss"></a>NT4/Samba Domain with Samba Domain Member Server without NSS Support</h3></div></div></div><p>
+		</p></li></ol></div><div class="example"><a name="ch0-NT4DSDM"></a><p class="title"><b>Example�7.5.�Samba Domain Member Server Using Winbind <code class="filename">smb.conf</code> File for NT4 Domain</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2592265"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2592277"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2592288"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2592300"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2592312"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2592324"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592335"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2592347"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592359"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2592370"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2592382"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2592394"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2592406"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592418"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2592429"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2592442"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2592454"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2592465"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2592477"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2592489"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2592510"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2592522"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2592533"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2592545"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2592565"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2592577"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2592589"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592600"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2592612"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2592632"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2592644"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2592656"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2592668"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="dcwonss"></a>NT4/Samba Domain with Samba Domain Member Server without NSS Support</h3></div></div></div><p>
 	No matter how many UNIX/Linux administrators there may be who believe that a UNIX operating
 	system that does not have NSS and PAM support to be outdated, the fact is there
 	are still many such systems in use today. Samba can be used without NSS support, but this
@@ -642,10 +642,10 @@ MEGANET2+PIOps:x:10005:
 	to the Samba server will cause the look-up of the incoming username. If the account
 	is found, it is used. If the account is not found, one will be automatically created
 	on the local machine so that it can then be used for all access controls.
-	</p><div class="procedure"><a name="id2592707"></a><p class="title"><b>Procedure�7.3.�Configuration Using Local Accounts Only</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2592711"></a><p class="title"><b>Procedure�7.3.�Configuration Using Local Accounts Only</b></p><ol type="1"><li><p>
 		Using your favorite text editor, create the <code class="filename">smb.conf</code> file so it has the contents
 		shown in <a class="link" href="unixclients.html#ch0-NT4DSCM" title="Example�7.6.�Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain">&#8220;Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain&#8221;</a>.
-		</p></li><li><p><a class="indexterm" name="id2592740"></a>
+		</p></li><li><p><a class="indexterm" name="id2592744"></a>
 		The system is ready to join the domain. Execute the following:
 </p><pre class="screen">
 net rpc join -U root%not24get
@@ -656,10 +656,10 @@ Joined domain MEGANET2.
 		Be sure to run all three Samba daemons: <code class="literal">smbd</code>, <code class="literal">nmbd</code>, <code class="literal">winbindd</code>.
 		</p></li><li><p>
 		The Samba member server of a Windows NT4 domain is ready for use.
-		</p></li></ol></div><div class="example"><a name="ch0-NT4DSCM"></a><p class="title"><b>Example�7.6.�Samba Domain Member Server Using Local Accounts <code class="filename">smb.conf</code> File for NT4 Domain</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2592828"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2592840"></a><em class="parameter"><code>workgroup = MEGANET3</code></em></td></tr><tr><td><a class="indexterm" name="id2592852"></a><em class="parameter"><code>netbios name = BSDBOX</code></em></td></tr><tr><td><a class="indexterm" name="id2592864"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2592876"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2592888"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2592899"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592911"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2592923"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -M '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2592935"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2592947"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2592959"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592971"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2592982"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2592994"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2593006"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2593018"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2593030"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2593042"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2593062"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2593074"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2593086"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593097"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2593118"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2593130"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2593141"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593153"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593165"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2593185"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593197"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593209"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2593221"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="adssdm"></a>Active Directory Domain with Samba Domain Member Server</h3></div></div></div><p>
-	<a class="indexterm" name="id2593246"></a>
-	<a class="indexterm" name="id2593255"></a>
-	<a class="indexterm" name="id2593262"></a>
+		</p></li></ol></div><div class="example"><a name="ch0-NT4DSCM"></a><p class="title"><b>Example�7.6.�Samba Domain Member Server Using Local Accounts <code class="filename">smb.conf</code> File for NT4 Domain</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2592833"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2592844"></a><em class="parameter"><code>workgroup = MEGANET3</code></em></td></tr><tr><td><a class="indexterm" name="id2592856"></a><em class="parameter"><code>netbios name = BSDBOX</code></em></td></tr><tr><td><a class="indexterm" name="id2592868"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2592880"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2592892"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2592903"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592915"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2592927"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -M '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2592939"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2592951"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2592963"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2592975"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2592986"></a><em class="parameter"><code>name resolve order = wins bcast hosts</code></em></td></tr><tr><td><a class="indexterm" name="id2592999"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2593010"></a><em class="parameter"><code>wins server = 192.168.2.1</code></em></td></tr><tr><td><a class="indexterm" name="id2593022"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2593034"></a><em class="parameter"><code>hosts allow = 192.168.2., 192.168.3., 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2593046"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2593067"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2593078"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2593090"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2593102"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2593122"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2593134"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2593146"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593157"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2593169"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2593189"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593201"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2593213"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2593225"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="adssdm"></a>Active Directory Domain with Samba Domain Member Server</h3></div></div></div><p>
+	<a class="indexterm" name="id2593250"></a>
+	<a class="indexterm" name="id2593259"></a>
+	<a class="indexterm" name="id2593266"></a>
 	One of the much-sought-after features new to Samba-3 is the ability to join an Active Directory
 	domain using Kerberos protocols. This makes it possible to operate an entire Windows network
 	without the need to run NetBIOS over TCP/IP and permits more secure networking in general. An
@@ -667,10 +667,10 @@ Joined domain MEGANET2.
 	later book may explore the intricacies of the NetBIOS-less operation that Samba-3 can participate
 	in. For now, we simply focus on how a Samba-3 server can be made a domain member server.
 	</p><p>
-	<a class="indexterm" name="id2593284"></a>
-	<a class="indexterm" name="id2593291"></a>
-	<a class="indexterm" name="id2593298"></a>
-	<a class="indexterm" name="id2593305"></a>
+	<a class="indexterm" name="id2593288"></a>
+	<a class="indexterm" name="id2593295"></a>
+	<a class="indexterm" name="id2593302"></a>
+	<a class="indexterm" name="id2593309"></a>
 	The diagram in <a class="link" href="unixclients.html#ch9-adsdc" title="Figure�7.3.�Active Directory Domain: Samba Member Server">&#8220;Active Directory Domain: Samba Member Server&#8221;</a> demonstrates how Samba-3 interfaces with
 	Microsoft Active Directory components. It should be noted that if Microsoft Windows Services
 	for UNIX (SFU) has been installed and correctly configured, it is possible to use client LDAP
@@ -694,8 +694,8 @@ Joined domain MEGANET2.
 	name of the server is <code class="constant">W2K3S</code>. In ADS realm terms, the domain controller
 	is known as <code class="constant">w2k3s.london.abmas.biz</code>. In NetBIOS nomenclature, the
 	domain name is <code class="constant">LONDON</code> and the server name is <code class="constant">W2K3S</code>.
-	</p><div class="figure"><a name="ch9-adsdc"></a><p class="title"><b>Figure�7.3.�Active Directory Domain: Samba Member Server</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap9-ADSDC.png" width="324" alt="Active Directory Domain: Samba Member Server"></div></div></div><br class="figure-break"><div class="procedure"><a name="id2593418"></a><p class="title"><b>Procedure�7.4.�Joining a Samba Server as an ADS Domain Member</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2593430"></a>
+	</p><div class="figure"><a name="ch9-adsdc"></a><p class="title"><b>Figure�7.3.�Active Directory Domain: Samba Member Server</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/chap9-ADSDC.png" width="324" alt="Active Directory Domain: Samba Member Server"></div></div></div><br class="figure-break"><div class="procedure"><a name="id2593422"></a><p class="title"><b>Procedure�7.4.�Joining a Samba Server as an ADS Domain Member</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2593434"></a>
 		Before you try to use Samba-3, you want to know for certain that your executables have
 		support for Kerberos and for LDAP. Execute the following to identify whether or
 		not this build is perhaps suitable for use:
@@ -762,15 +762,15 @@ massive:/usr/sbin # smbd -b | grep LDAP
 		This does look promising; <code class="literal">smbd</code> has been built with Kerberos and LDAP
 		support. You are relieved to know that it is safe to progress.
 		</p></li><li><p>
-		<a class="indexterm" name="id2593529"></a>
-		<a class="indexterm" name="id2593538"></a>
-		<a class="indexterm" name="id2593545"></a>
-		<a class="indexterm" name="id2593552"></a>
-		<a class="indexterm" name="id2593561"></a>
-		<a class="indexterm" name="id2593570"></a>
-		<a class="indexterm" name="id2593577"></a>
-		<a class="indexterm" name="id2593584"></a>
-		<a class="indexterm" name="id2593591"></a>
+		<a class="indexterm" name="id2593533"></a>
+		<a class="indexterm" name="id2593542"></a>
+		<a class="indexterm" name="id2593549"></a>
+		<a class="indexterm" name="id2593556"></a>
+		<a class="indexterm" name="id2593565"></a>
+		<a class="indexterm" name="id2593574"></a>
+		<a class="indexterm" name="id2593581"></a>
+		<a class="indexterm" name="id2593588"></a>
+		<a class="indexterm" name="id2593595"></a>
 		The next step is to identify which version of the Kerberos libraries have been used.
 		In order to permit Samba-3 to interoperate with Windows 2003 Active Directory, it is
 		essential that it has been linked with either MIT Kerberos version 1.3.1 or later,
@@ -798,7 +798,7 @@ massive:/usr/sbin # smbd -b | grep LDAP
 		</p></li><li><p>
 		Edit or create the NSS control file so it has the contents shown in <a class="link" href="unixclients.html#ch9-sdmnss" title="Example�7.4.�NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf">&#8220;NSS using LDAP for Identity Resolution  File: /etc/nsswitch.conf&#8221;</a>.
 		</p></li><li><p>
-		<a class="indexterm" name="id2593692"></a>
+		<a class="indexterm" name="id2593697"></a>
 		Delete the file <code class="filename">/etc/samba/secrets.tdb</code> if it exists. Of course, you
 		do keep a backup, don't you?
 		</p></li><li><p>
@@ -809,7 +809,7 @@ massive:/usr/sbin # smbd -b | grep LDAP
 <code class="prompt">root# </code> rm /var/lib/samba/*tdb
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2593736"></a>
+		<a class="indexterm" name="id2593740"></a>
 		Validate your <code class="filename">smb.conf</code> file using <code class="literal">testparm</code> (as you have
 		done previously). Correct all errors reported before proceeding. The command you
 		execute is:
@@ -819,8 +819,8 @@ massive:/usr/sbin # smbd -b | grep LDAP
 		Now that you are satisfied that your Samba server is ready to join the Windows
 		ADS domain, let's move on.
 		</p></li><li><p>
-		<a class="indexterm" name="id2593778"></a>
-		<a class="indexterm" name="id2593789"></a>
+		<a class="indexterm" name="id2593782"></a>
+		<a class="indexterm" name="id2593793"></a>
 		This is a good time to double-check everything and then execute the following
 		command when everything you have done has checked out okay:
 </p><pre class="screen">
@@ -831,17 +831,17 @@ Joined 'FRAN' to realm 'LONDON.ABMAS.BIZ'
 		You have successfully made your Samba-3 server a member of the ADS domain
 		using Kerberos protocols.
 		</p><p>
-		<a class="indexterm" name="id2593817"></a>
-		<a class="indexterm" name="id2593824"></a>
+		<a class="indexterm" name="id2593821"></a>
+		<a class="indexterm" name="id2593828"></a>
 		In the event that you receive no output messages, a silent return means that the
 		domain join failed. You should use <code class="literal">ethereal</code> to identify what
 		may be failing. Common causes of a failed join include:
 
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-			<a class="indexterm" name="id2593845"></a>
+			<a class="indexterm" name="id2593850"></a>
 			Defective or misconfigured DNS name resolution.
 			</p></li><li><p>
-			<a class="indexterm" name="id2593860"></a>
+			<a class="indexterm" name="id2593864"></a>
 			Restrictive security settings on the Windows 200x ADS domain controller
 			preventing needed communications protocols. You can check this by searching
 			the Windows Server 200x Event Viewer.
@@ -853,16 +853,16 @@ Joined 'FRAN' to realm 'LONDON.ABMAS.BIZ'
 			functionality.
 			</p></li></ul></div><p>
 
-		<a class="indexterm" name="id2593891"></a>
-		<a class="indexterm" name="id2593902"></a>
-		<a class="indexterm" name="id2593909"></a>
+		<a class="indexterm" name="id2593895"></a>
+		<a class="indexterm" name="id2593906"></a>
+		<a class="indexterm" name="id2593913"></a>
 		In any case, never execute the <code class="literal">net rpc join</code> command in an attempt
 		to join the Samba server to the domain, unless you wish not to use the Kerberos
 		security protocols. Use of the older RPC-based domain join facility requires that
 		Windows Server 200x ADS has been configured appropriately for mixed mode operation.
 		</p></li><li><p>
-		<a class="indexterm" name="id2593934"></a>
-		<a class="indexterm" name="id2593941"></a>
+		<a class="indexterm" name="id2593938"></a>
+		<a class="indexterm" name="id2593945"></a>
 		If the <code class="literal">tdbdump</code> is installed on your system (not essential),
 		you can look inside the <code class="filename">/etc/samba/secrets.tdb</code> file. If
 		you wish to do this, execute:
@@ -893,7 +893,7 @@ data = "E\89\F6?"
 		It is now time to start Samba in the usual way (as has been done many time before
 		in this book).	
 		</p></li><li><p>
-		<a class="indexterm" name="id2593998"></a>
+		<a class="indexterm" name="id2594002"></a>
 		This is a good time to verify that everything is working. First, check that
 		winbind is able to obtain the list of users and groups from the ADS domain controller.
 		Execute the following:
@@ -919,7 +919,7 @@ LONDON+Group Policy Creator Owners
 LONDON+DnsUpdateProxy
 </pre><p>
 		Excellent. That worked also, as expected.
-		</p></li><li><p><a class="indexterm" name="id2594044"></a>
+		</p></li><li><p><a class="indexterm" name="id2594048"></a>
 		Now repeat this via NSS to validate that full identity resolution is
 		functional as required. Execute:
 </p><pre class="screen">
@@ -952,9 +952,9 @@ LONDON+DnsUpdateProxy:x:10008:
 </pre><p>
 		This is very pleasing. Everything works as expected.
 		</p></li><li><p>
-		<a class="indexterm" name="id2594102"></a>
-		<a class="indexterm" name="id2594113"></a>
-		<a class="indexterm" name="id2594122"></a>
+		<a class="indexterm" name="id2594106"></a>
+		<a class="indexterm" name="id2594117"></a>
+		<a class="indexterm" name="id2594126"></a>
 		You may now perform final verification that communications between Samba-3 winbind and
 		the Active Directory server is using Kerberos protocols. Execute the following:
 </p><pre class="screen">
@@ -972,7 +972,7 @@ Server time offset: 2
 		keep all server time clocks synchronized using the network time protocol (NTP).
 		In any case, the output we obtained confirms that all systems are operational.
 		</p></li><li><p>
-		<a class="indexterm" name="id2594158"></a>
+		<a class="indexterm" name="id2594162"></a>
 		There is one more action you elect to take, just because you are paranoid and disbelieving,
 		so you execute the following command:
 </p><pre class="programlisting">
@@ -1142,21 +1142,21 @@ data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
 </pre><p>
 	Now all is revealed. Your curiosity, as well as that of your team, has been put at ease.
 	May this server serve well all who happen upon it.
-	</p><div class="example"><a name="ch9-adssdm"></a><p class="title"><b>Example�7.7.�Samba Domain Member <code class="filename">smb.conf</code> File for Active Directory Membership</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594415"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2594427"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2594439"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2594450"></a><em class="parameter"><code>server string = Samba 3.0.20</code></em></td></tr><tr><td><a class="indexterm" name="id2594462"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2594474"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2594486"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2594498"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2594509"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2594521"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2594533"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2594544"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2594556"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2594568"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2594580"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2594592"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2594604"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2594616"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2594636"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2594648"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2594659"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2594671"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2594692"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2594703"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2594715"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594727"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594738"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2594759"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2594770"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2594782"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2594794"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594807"></a>IDMAP_RID with Winbind</h4></div></div></div><p>
-        <a class="indexterm" name="id2594815"></a>
-        <a class="indexterm" name="id2594822"></a>
-        <a class="indexterm" name="id2594828"></a>
-        <a class="indexterm" name="id2594835"></a>
+	</p><div class="example"><a name="ch9-adssdm"></a><p class="title"><b>Example�7.7.�Samba Domain Member <code class="filename">smb.conf</code> File for Active Directory Membership</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594383"></a><em class="parameter"><code>unix charset = LOCALE</code></em></td></tr><tr><td><a class="indexterm" name="id2594395"></a><em class="parameter"><code>workgroup = LONDON</code></em></td></tr><tr><td><a class="indexterm" name="id2594407"></a><em class="parameter"><code>realm = LONDON.ABMAS.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2594418"></a><em class="parameter"><code>server string = Samba 3.0.20</code></em></td></tr><tr><td><a class="indexterm" name="id2594430"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2594442"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2594454"></a><em class="parameter"><code>log level = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2594466"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2594477"></a><em class="parameter"><code>log file = /var/log/samba/%m</code></em></td></tr><tr><td><a class="indexterm" name="id2594489"></a><em class="parameter"><code>max log size = 50</code></em></td></tr><tr><td><a class="indexterm" name="id2594501"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2594512"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2594524"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2594536"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2594548"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2594560"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2594572"></a><em class="parameter"><code>winbind separator = +</code></em></td></tr><tr><td><a class="indexterm" name="id2594584"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2594604"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2594616"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2594627"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2594639"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2594660"></a><em class="parameter"><code>comment = SMB Print Spool</code></em></td></tr><tr><td><a class="indexterm" name="id2594671"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2594683"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594695"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594706"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2594727"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2594738"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2594750"></a><em class="parameter"><code>admin users = root, Administrator</code></em></td></tr><tr><td><a class="indexterm" name="id2594762"></a><em class="parameter"><code>write list = root</code></em></td></tr></table></div></div><br class="example-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594775"></a>IDMAP_RID with Winbind</h4></div></div></div><p>
+        <a class="indexterm" name="id2594783"></a>
+        <a class="indexterm" name="id2594790"></a>
+        <a class="indexterm" name="id2594796"></a>
+        <a class="indexterm" name="id2594803"></a>
         The <code class="literal">idmap_rid</code> facility is a new tool that, unlike native winbind, creates a
         predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
         of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
         in a central place. The downside is that it can be used only within a single ADS domain and
         is not compatible with trusted domain implementations.
         </p><p>
-        <a class="indexterm" name="id2594859"></a>
-        <a class="indexterm" name="id2594865"></a>
-        <a class="indexterm" name="id2594872"></a>
-        <a class="indexterm" name="id2594879"></a>
+        <a class="indexterm" name="id2594827"></a>
+        <a class="indexterm" name="id2594833"></a>
+        <a class="indexterm" name="id2594840"></a>
+        <a class="indexterm" name="id2594847"></a>
         This alternate method of SID to UID/GID  mapping can be achieved with the idmap_rid
         plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
         RID to a base value specified. This utility requires that the parameter
@@ -1164,18 +1164,18 @@ data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
         with multiple domain environments. The <em class="parameter"><code>idmap uid</code></em> and
         <em class="parameter"><code>idmap gid</code></em> ranges must be specified.
         </p><p>
-        <a class="indexterm" name="id2594912"></a>
-        <a class="indexterm" name="id2594919"></a>
+        <a class="indexterm" name="id2594880"></a>
+        <a class="indexterm" name="id2594887"></a>
         The idmap_rid facility can be used both for NT4/Samba-style domains as well as with Active Directory.
         To use this with an NT4 domain, the <em class="parameter"><code>realm</code></em> is not used. Additionally the
         method used to join the domain uses the <code class="constant">net rpc join</code> process.
         </p><p>
         An example <code class="filename">smb.conf</code> file for an ADS domain environment is shown in <a class="link" href="unixclients.html#sbe-idmapridex" title="Example�7.8.�Example smb.conf File Using idmap_rid">&#8220;Example smb.conf File Using idmap_rid&#8221;</a>.
-        </p><div class="example"><a name="sbe-idmapridex"></a><p class="title"><b>Example�7.8.�Example <code class="filename">smb.conf</code> File Using <code class="constant">idmap_rid</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594993"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id2595005"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id2595016"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595028"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id2595040"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2595052"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595064"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595076"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595088"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595100"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2595111"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2595124"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595135"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595147"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2595159"></a><em class="parameter"><code>printer admin = "KPAK\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
-        <a class="indexterm" name="id2595175"></a>
-        <a class="indexterm" name="id2595182"></a>
-        <a class="indexterm" name="id2595188"></a>
-        <a class="indexterm" name="id2595195"></a>
+        </p><div class="example"><a name="sbe-idmapridex"></a><p class="title"><b>Example�7.8.�Example <code class="filename">smb.conf</code> File Using <code class="constant">idmap_rid</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594961"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id2594973"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id2594984"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2594996"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id2595008"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2595020"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595032"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595044"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595056"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2595068"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2595079"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2595092"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595103"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id2595115"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2595127"></a><em class="parameter"><code>printer admin = "KPAK\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
+        <a class="indexterm" name="id2595143"></a>
+        <a class="indexterm" name="id2595150"></a>
+        <a class="indexterm" name="id2595156"></a>
+        <a class="indexterm" name="id2595163"></a>
         In a large domain with many users, it is imperative to disable enumeration of users and groups.
         For example, at a site that has 22,000 users in Active Directory the winbind-based user and
         group resolution is unavailable for nearly 12 minutes following first start-up of
@@ -1185,8 +1185,8 @@ data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
         commands. It will be possible to perform the lookup for individual users, as shown in the procedure
         below.
         </p><p>
-        <a class="indexterm" name="id2595234"></a>
-        <a class="indexterm" name="id2595241"></a>
+        <a class="indexterm" name="id2595202"></a>
+        <a class="indexterm" name="id2595209"></a>
         The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
         <code class="filename">/etc/nsswitch.conf</code> so it has the following parameters:
 </p><pre class="screen">
@@ -1212,7 +1212,7 @@ Using short domain name -- KPAK
 Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
 </pre><p>
                 </p><p>
-                <a class="indexterm" name="id2595322"></a>
+                <a class="indexterm" name="id2595290"></a>
                 An invalid or failed join can be detected by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads testjoin
@@ -1228,30 +1228,30 @@ Join to domain is not valid
                 Start the <code class="literal">nmbd</code>, <code class="literal">winbind,</code> and <code class="literal">smbd</code> daemons in the order shown.
                 </p></li><li><p>
                 Validate the operation of this configuration by executing:
-                <a class="indexterm" name="id2595389"></a>
+                <a class="indexterm" name="id2595357"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> getent passwd administrator
 administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
 </pre><p>
-                </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595411"></a>IDMAP Storage in LDAP using Winbind</h4></div></div></div><p>
-        <a class="indexterm" name="id2595419"></a>
-        <a class="indexterm" name="id2595426"></a>
+                </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595379"></a>IDMAP Storage in LDAP using Winbind</h4></div></div></div><p>
+        <a class="indexterm" name="id2595387"></a>
+        <a class="indexterm" name="id2595394"></a>
         The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains as well as
         with ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-compliant
         LDAP server can be used. It is therefore possible to deploy this IDMAP configuration using
         the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM, and so on.
         </p><p>
         The example in <a class="link" href="unixclients.html#sbeunxa" title="Example�7.9.�Typical ADS Style Domain smb.conf File">&#8220;Typical ADS Style Domain smb.conf File&#8221;</a> is for an ADS-style domain.
-        </p><div class="example"><a name="sbeunxa"></a><p class="title"><b>Example�7.9.�Typical ADS Style Domain <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2595486"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id2595498"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id2595510"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595521"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2595533"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2595545"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id2595557"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595569"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2595581"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595593"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id2595605"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2595617"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2595629"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2595641"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-        <a class="indexterm" name="id2595656"></a>
+        </p><div class="example"><a name="sbeunxa"></a><p class="title"><b>Example�7.9.�Typical ADS Style Domain <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2595454"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id2595466"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id2595478"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595489"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2595501"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2595513"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id2595525"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595537"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2595549"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2595561"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id2595573"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2595585"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2595597"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2595609"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+        <a class="indexterm" name="id2595624"></a>
         In the case of an NT4 or Samba-3-style domain the <em class="parameter"><code>realm</code></em> is not used, and the
         command used to join the domain is <code class="literal">net rpc join</code>. The above example also demonstrates
         advanced error reporting techniques that are documented in the chapter called "Reporting Bugs" in
 	&#8220;<span class="quote">The Official Samba-3 HOWTO and Reference Guide, Second Edition</span>&#8221; (TOSHARG2).
         </p><p>
-        <a class="indexterm" name="id2595687"></a>
-        <a class="indexterm" name="id2595694"></a>
-        <a class="indexterm" name="id2595701"></a>
+        <a class="indexterm" name="id2595655"></a>
+        <a class="indexterm" name="id2595662"></a>
+        <a class="indexterm" name="id2595669"></a>
         Where MIT kerberos is installed (version 1.3.4 or later), edit the <code class="filename">/etc/krb5.conf</code>
         file so it has the following contents:
 </p><pre class="screen">
@@ -1306,8 +1306,8 @@ hosts:  files wins
 ...
 </pre><p>
         </p><p>
-        <a class="indexterm" name="id2595785"></a>
-        <a class="indexterm" name="id2595792"></a>
+        <a class="indexterm" name="id2595753"></a>
+        <a class="indexterm" name="id2595760"></a>
         You will need the <a class="ulink" href="http://www.padl.com" target="_top">PADL</a> <code class="literal">nss_ldap</code>
         tool set for this solution. Configure the <code class="filename">/etc/ldap.conf</code> file so it has
         the information needed. The following is an example of a working file:
@@ -1370,20 +1370,20 @@ Joined 'GOODELF' to realm 'SNOWSHOW.COM'
                 </p></li><li><p>
                 Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown.
                 </p></li></ol></div><p>
-        <a class="indexterm" name="id2595993"></a>
+        <a class="indexterm" name="id2595961"></a>
         Follow the diagnostic procedures shown earlier in this chapter to identify success or failure of the join.
         In many cases a failure is indicated by a silent return to the command prompt with no indication of the
         reason for failure.
-        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2596006"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h4></div></div></div><p>
-        <a class="indexterm" name="id2596015"></a>
-        <a class="indexterm" name="id2596022"></a>
+        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595974"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h4></div></div></div><p>
+        <a class="indexterm" name="id2595983"></a>
+        <a class="indexterm" name="id2595990"></a>
         The use of this method is messy. The information provided in this section is for guidance only
         and is very definitely not complete. This method does work; it is used in a number of large sites
         and has an acceptable level of performance.
         </p><p>
         An example <code class="filename">smb.conf</code> file is shown in <a class="link" href="unixclients.html#sbewinbindex" title="Example�7.10.�ADS Membership Using RFC2307bis Identity Resolution smb.conf File">&#8220;ADS Membership Using RFC2307bis Identity Resolution smb.conf File&#8221;</a>.
-        </p><div class="example"><a name="sbewinbindex"></a><p class="title"><b>Example�7.10.�ADS Membership Using RFC2307bis Identity Resolution <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2596085"></a><em class="parameter"><code>workgroup = BUBBAH</code></em></td></tr><tr><td><a class="indexterm" name="id2596096"></a><em class="parameter"><code>netbios name = MADMAX</code></em></td></tr><tr><td><a class="indexterm" name="id2596108"></a><em class="parameter"><code>realm = BUBBAH.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2596120"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2596132"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2596143"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2596155"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2596167"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2596179"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2596191"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2596203"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-        <a class="indexterm" name="id2596218"></a>
+        </p><div class="example"><a name="sbewinbindex"></a><p class="title"><b>Example�7.10.�ADS Membership Using RFC2307bis Identity Resolution <code class="filename">smb.conf</code> File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2596053"></a><em class="parameter"><code>workgroup = BUBBAH</code></em></td></tr><tr><td><a class="indexterm" name="id2596064"></a><em class="parameter"><code>netbios name = MADMAX</code></em></td></tr><tr><td><a class="indexterm" name="id2596076"></a><em class="parameter"><code>realm = BUBBAH.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2596088"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2596100"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2596111"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2596123"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2596135"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2596147"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2596159"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2596171"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+        <a class="indexterm" name="id2596186"></a>
         The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
         to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
         following:
@@ -1392,7 +1392,7 @@ Joined 'GOODELF' to realm 'SNOWSHOW.COM'
 make install
 </pre><p>
         </p><p>
-        <a class="indexterm" name="id2596239"></a>
+        <a class="indexterm" name="id2596207"></a>
         The following <code class="filename">/etc/nsswitch.conf</code> file contents are required:
 </p><pre class="screen">
 ...
@@ -1404,30 +1404,30 @@ hosts:  files wins
 ...
 </pre><p>
         </p><p>
-        <a class="indexterm" name="id2596263"></a>
-        <a class="indexterm" name="id2596270"></a>
+        <a class="indexterm" name="id2596231"></a>
+        <a class="indexterm" name="id2596238"></a>
         The <code class="filename">/etc/ldap.conf</code> file must be configured also. Refer to the PADL documentation
         and source code for nss_ldap instructions.
         </p><p>
         The next step involves preparation on the ADS schema. This is briefly discussed in the remaining
         part of this chapter.
-        </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2596292"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h5></div></div></div><p>
-                <a class="indexterm" name="id2596301"></a>
+        </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2596260"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h5></div></div></div><p>
+                <a class="indexterm" name="id2596269"></a>
                 The Microsoft Windows Service for UNIX version 3.5 is available for free
                 <a class="ulink" href="http://www.microsoft.com/windows/sfu/" target="_top">download</a>
                 from the Microsoft Web site. You will need to download this tool and install it following
                 Microsoft instructions.
-                </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2596321"></a>IDMAP, Active Directory, and AD4UNIX</h5></div></div></div><p>
+                </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2596289"></a>IDMAP, Active Directory, and AD4UNIX</h5></div></div></div><p>
                 Instructions for obtaining and installing the AD4UNIX tool set can be found from the
                 <a class="ulink" href="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach" target="_top">
                 Geekcomix</a> Web site.
-                </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596343"></a>UNIX/Linux Client Domain Member</h3></div></div></div><p><a class="indexterm" name="id2596350"></a>
+                </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596311"></a>UNIX/Linux Client Domain Member</h3></div></div></div><p><a class="indexterm" name="id2596318"></a>
 	So far this chapter has been mainly concerned with the provision of file and print
 	services for domain member servers. However, an increasing number of UNIX/Linux
 	workstations are being installed that do not act as file or print servers to anyone
 	other than a single desktop user. The key demand for desktop systems is to be able
 	to log onto any UNIX/Linux or Windows desktop using the same network user credentials.
-	</p><p><a class="indexterm" name="id2596369"></a>
+	</p><p><a class="indexterm" name="id2596337"></a>
 	The ability to use a common set of user credential across a variety of network systems
 	is generally regarded as a single sign-on (SSO) solution. SSO systems are sold by a
 	large number of vendors and include a range of technologies such as:
@@ -1439,7 +1439,7 @@ hosts:  files wins
 		Metadirectory server solutions
 		</p></li><li><p>
 		Replacement authentication systems
-		</p></li></ul></div><p><a class="indexterm" name="id2596411"></a>
+		</p></li></ul></div><p><a class="indexterm" name="id2596379"></a>
 	There are really four solutions that provide integrated authentication and
 	user identity management facilities:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -1464,22 +1464,22 @@ hosts:  files wins
 	provides logon services for UNIX/Linux users, while Windows users obtain their sign-on
 	support via Samba-3.
 	</p><p>
-	<a class="indexterm" name="id2596490"></a>
+	<a class="indexterm" name="id2596458"></a>
 	On the other hand, if the authentication and identity resolution backend must be provided by
 	a Windows NT4-style domain or from an Active Directory Domain that does not have the Microsoft
 	Windows Services for UNIX installed, winbind is your best friend. Specific guidance for these
 	situations now follows.
 	</p><p>
-	<a class="indexterm" name="id2596508"></a>
-	<a class="indexterm" name="id2596514"></a>
-	<a class="indexterm" name="id2596521"></a>
+	<a class="indexterm" name="id2596476"></a>
+	<a class="indexterm" name="id2596482"></a>
+	<a class="indexterm" name="id2596489"></a>
 	To permit users to log on to a Linux system using Windows network credentials, you need to
 	configure identity resolution (NSS) and PAM. This means that the basic steps include those
 	outlined above with the addition of PAM configuration. Given that most workstations (desktop/client)
 	usually do not need to provide file and print services to a group of users, the configuration
 	of shares and printers is generally less important. Often this allows the share specifications
 	to be entirely removed from the <code class="filename">smb.conf</code> file. That is obviously an administrator decision.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2596544"></a>NT4 Domain Member</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2596512"></a>NT4 Domain Member</h4></div></div></div><p>
 		The following steps provide a Linux system that users can log onto using
 		Windows NT4 (or Samba-3) domain network credentials:
 		</p><div class="procedure"><ol type="1"><li><p>
@@ -1507,7 +1507,7 @@ hosts:  files wins
 			</p></li><li><p>
 			Edit only one file at a time. Carefully validate its operation before attempting
 			to reboot the machine.
-			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2596666"></a>ADS Domain Member</h4></div></div></div><p>
+			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2596634"></a>ADS Domain Member</h4></div></div></div><p>
 		This procedure should be followed to permit a Linux network client (workstation/desktop)
 		to permit users to log on using Microsoft Active Directory-based user credentials.
 		</p><div class="procedure"><ol type="1"><li><p>
@@ -1587,7 +1587,7 @@ password    required      /lib/security/$ISA/pam_deny.so
 session     required      /lib/security/$ISA/pam_limits.so
 session     sufficient    /lib/security/$ISA/pam_unix.so
 session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
-</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596918"></a>Key Points Learned</h3></div></div></div><p>
+</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596886"></a>Key Points Learned</h3></div></div></div><p>
 		The addition of UNIX/Linux Samba servers and clients is a common requirement. In this chapter, you
 		learned how to integrate such servers so that the UID/GID mappings they use can be consistent
 		across all domain member servers. You also discovered how to implement the ability to use Samba
@@ -1607,54 +1607,54 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 			</p></li><li><p>
 			On NSS/PAM enabled UNIX/Linux systems, NSS is responsible for identity management 
 			and PAM is responsible for authentication of logon credentials (username and password).
-			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596972"></a>Questions and Answers</h2></div></div></div><p>
+			</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596940"></a>Questions and Answers</h2></div></div></div><p>
 	The following questions were obtained from the mailing list and also from private discussions
 	with Windows network administrators.
-	</p><div class="qandaset"><dl><dt> <a href="unixclients.html#id2596990">
+	</p><div class="qandaset"><dl><dt> <a href="unixclients.html#id2596958">
 		We use NIS for all UNIX accounts. Why do we need winbind?
-		</a></dt><dt> <a href="unixclients.html#id2597105">
+		</a></dt><dt> <a href="unixclients.html#id2597073">
 		Our IT management people do not like LDAP but are looking at Microsoft Active Directory. 
 	      Which is better?
-		</a></dt><dt> <a href="unixclients.html#id2597189">
+		</a></dt><dt> <a href="unixclients.html#id2597157">
 		We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible 
 		to use NIS in place of LDAP?
-		</a></dt><dt> <a href="unixclients.html#id2597300">
+		</a></dt><dt> <a href="unixclients.html#id2597268">
 		Are you suggesting that users should not log on to a domain member server? If so, why?
-		</a></dt><dt> <a href="unixclients.html#id2597421">
+		</a></dt><dt> <a href="unixclients.html#id2597396">
 		We want to ensure that only users from our own domain plus from trusted domains can use our
 		Samba servers. In the smb.conf file on all servers, we have enabled the winbind
 		trusted domains only parameter. We now find that users from trusted domains 
 		cannot access our servers, and users from Windows clients that are not domain members
 		can also access our servers. Is this a Samba bug?
-		</a></dt><dt> <a href="unixclients.html#id2597596">
+		</a></dt><dt> <a href="unixclients.html#id2597571">
 		What are the benefits of using LDAP for my domain member servers?
-		</a></dt><dt> <a href="unixclients.html#id2597780">
+		</a></dt><dt> <a href="unixclients.html#id2597755">
 		Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into
 		my DNS configuration?
-		</a></dt><dt> <a href="unixclients.html#id2597938">
+		</a></dt><dt> <a href="unixclients.html#id2597913">
 		Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we
 		use Samba-3 with that configuration?
-		</a></dt><dt> <a href="unixclients.html#id2597956">
+		</a></dt><dt> <a href="unixclients.html#id2597931">
 		When I tried to execute net ads join, I got no output. It did not work, so
 		I think that it failed. I then executed net rpc join and that worked fine.
 		That is okay, isn't it?
-		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2596990"></a><a name="id2596992"></a></td><td align="left" valign="top"><p>
+		</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2596958"></a><a name="id2596960"></a></td><td align="left" valign="top"><p>
 		We use NIS for all UNIX accounts. Why do we need winbind?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
-		<a class="indexterm" name="id2597004"></a>
-		<a class="indexterm" name="id2597011"></a>
-		<a class="indexterm" name="id2597018"></a>
-		<a class="indexterm" name="id2597025"></a>
-		<a class="indexterm" name="id2597031"></a>
-		<a class="indexterm" name="id2597038"></a>
+		<a class="indexterm" name="id2596972"></a>
+		<a class="indexterm" name="id2596979"></a>
+		<a class="indexterm" name="id2596986"></a>
+		<a class="indexterm" name="id2596993"></a>
+		<a class="indexterm" name="id2596999"></a>
+		<a class="indexterm" name="id2597006"></a>
 		You can use NIS for your UNIX accounts. NIS does not store the Windows encrypted
 		passwords that need to be stored in one of the acceptable passdb backends.
 		Your choice of backend is limited to <em class="parameter"><code>smbpasswd</code></em> or
 		<em class="parameter"><code>tdbsam</code></em>. Winbind is needed to handle the resolution of
 		SIDs from trusted domains to local UID/GID values.
 		</p><p>
-		<a class="indexterm" name="id2597065"></a>
-		<a class="indexterm" name="id2597073"></a>
+		<a class="indexterm" name="id2597033"></a>
+		<a class="indexterm" name="id2597041"></a>
 		On a domain member server, you effectively map Windows domain users to local users
 		that are in your NIS database by specifying the <em class="parameter"><code>winbind trusted domains
 		only</code></em>. This causes user and group account lookups to be routed via
@@ -1662,17 +1662,17 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 		this pushes the resolution of users and groups out through NIS.
 		</p><p>
 		As a general rule, it is always a good idea to run winbind on all Samba servers.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597105"></a><a name="id2597107"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597073"></a><a name="id2597075"></a></td><td align="left" valign="top"><p>
 		Our IT management people do not like LDAP but are looking at Microsoft Active Directory. 
-	      Which is better?<a class="indexterm" name="id2597114"></a>
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597128"></a><a class="indexterm" name="id2597139"></a><a class="indexterm" name="id2597147"></a>
+	      Which is better?<a class="indexterm" name="id2597082"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597096"></a><a class="indexterm" name="id2597107"></a><a class="indexterm" name="id2597115"></a>
 		Microsoft Active Directory is an LDAP server that is intricately tied to a Kerberos
 		infrastructure. Most IT managers who object to LDAP do so because
 		an LDAP server is most often supplied as a raw tool that needs to be configured and
 		for which the administrator must create the schema, create the administration tools, and
 		devise the backup and recovery facilities in a site-dependent manner. LDAP servers
 		in general are seen as a high-energy, high-risk facility.
-		</p><p><a class="indexterm" name="id2597166"></a>
+		</p><p><a class="indexterm" name="id2597134"></a>
 		Microsoft Active Directory by comparison is easy to install and configure and
 		is supplied with all tools necessary to implement and manage the directory. For sites
 		that lack a lot of technical competence, Active Directory is a good choice. For sites
@@ -1681,28 +1681,28 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 		the site want? If management wants a choice to use an alternative, they may want to
 		consider the options. On the other hand, if management just wants a solution that works,
 		Microsoft Active Directory is a good solution.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597189"></a><a name="id2597191"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597157"></a><a name="id2597159"></a></td><td align="left" valign="top"><p>
 		We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible 
 		to use NIS in place of LDAP?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597203"></a><a class="indexterm" name="id2597211"></a><a class="indexterm" name="id2597219"></a><a class="indexterm" name="id2597227"></a><a class="indexterm" name="id2597235"></a><a class="indexterm" name="id2597243"></a><a class="indexterm" name="id2597250"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597171"></a><a class="indexterm" name="id2597179"></a><a class="indexterm" name="id2597187"></a><a class="indexterm" name="id2597195"></a><a class="indexterm" name="id2597203"></a><a class="indexterm" name="id2597211"></a><a class="indexterm" name="id2597218"></a>
 		Yes, it is possible to use NIS in place of LDAP, but there may be problems with keeping
 		the Windows (SMB) encrypted passwords database correctly synchronized across the entire
 		network. Workstations (Windows client machines) periodically change their domain
 		membership secure account password. How can you keep changes that are on remote BDCs
 		synchronized on the PDC?
-		</p><p><a class="indexterm" name="id2597268"></a><a class="indexterm" name="id2597276"></a><a class="indexterm" name="id2597284"></a>
+		</p><p><a class="indexterm" name="id2597236"></a><a class="indexterm" name="id2597244"></a><a class="indexterm" name="id2597252"></a>
 		LDAP is a more elegant solution because it permits centralized storage and management
 		of all network identities (user, group, and machine accounts) together with all information
 		Samba needs to provide to network clients and their users.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597300"></a><a name="id2597302"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597268"></a><a name="id2597270"></a></td><td align="left" valign="top"><p>
 		Are you suggesting that users should not log on to a domain member server? If so, why?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597314"></a><a class="indexterm" name="id2597322"></a><a class="indexterm" name="id2597333"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597282"></a><a class="indexterm" name="id2597290"></a><a class="indexterm" name="id2597301"></a>
 		Many UNIX administrators mock the model that the personal computer industry has adopted
 		as normative since the early days of Novell NetWare. The old
 		perception of the necessity to keep users off file and print servers was a result of
 		fears concerning the security and integrity of data. It was a simple and generally
 		effective measure to keep users away from servers, except through mapped drives.
-		</p><p><a class="indexterm" name="id2597351"></a><a class="indexterm" name="id2597359"></a><a class="indexterm" name="id2597367"></a><a class="indexterm" name="id2597375"></a><a class="indexterm" name="id2597382"></a>
+		</p><p><a class="indexterm" name="id2597326"></a><a class="indexterm" name="id2597334"></a><a class="indexterm" name="id2597342"></a><a class="indexterm" name="id2597350"></a><a class="indexterm" name="id2597357"></a>
 		UNIX administrators are fully correct in asserting that UNIX servers and workstations
 		are identical in terms of the software that is installed. They correctly assert that
 		in a well-secured environment it is safe to store files on a system that has hundreds
@@ -1711,17 +1711,17 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 		server the risk to operations through simple user errors.
 		Only then can one begin to appraise the best strategy and adopt a site-specific
 		policy that best protects the needs of users and of the organization alike.
-		</p><p><a class="indexterm" name="id2597405"></a>
+		</p><p><a class="indexterm" name="id2597380"></a>
 		From experience, it is my recommendation to keep general system-level logins to a
 		practical minimum and to eliminate them if possible. This should not be taken as a
 		hard rule, though. The better question is, what works best for the site?
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597421"></a><a name="id2597423"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2597426"></a><a class="indexterm" name="id2597434"></a><a class="indexterm" name="id2597446"></a><a class="indexterm" name="id2597454"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597396"></a><a name="id2597398"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2597401"></a><a class="indexterm" name="id2597409"></a><a class="indexterm" name="id2597421"></a><a class="indexterm" name="id2597429"></a>
 		We want to ensure that only users from our own domain plus from trusted domains can use our
 		Samba servers. In the <code class="filename">smb.conf</code> file on all servers, we have enabled the <em class="parameter"><code>winbind
 		trusted domains only</code></em> parameter. We now find that users from trusted domains 
 		cannot access our servers, and users from Windows clients that are not domain members
 		can also access our servers. Is this a Samba bug?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597487"></a><a class="indexterm" name="id2597495"></a><a class="indexterm" name="id2597502"></a><a class="indexterm" name="id2597510"></a><a class="indexterm" name="id2597518"></a><a class="indexterm" name="id2597526"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597462"></a><a class="indexterm" name="id2597470"></a><a class="indexterm" name="id2597477"></a><a class="indexterm" name="id2597485"></a><a class="indexterm" name="id2597493"></a><a class="indexterm" name="id2597501"></a>
 		The manual page for this <em class="parameter"><code>winbind trusted domains only</code></em> parameter says,
 		&#8220;<span class="quote">This parameter is designed to allow Samba servers that are members of a Samba-controlled 
 		domain to use UNIX accounts distributed vi NIS, rsync, or LDAP as the UIDs for winbindd users 
@@ -1729,7 +1729,7 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 		mapped to the account <code class="constant">user1</code> in <code class="filename">/etc/passwd</code> instead 
 		of allocating a new UID for him or her.</span>&#8221; This clearly suggests that you are trying
 		to use this parameter inappropriately.
-		</p><p><a class="indexterm" name="id2597568"></a>
+		</p><p><a class="indexterm" name="id2597542"></a>
 		A far better solution is to use the <em class="parameter"><code>valid users</code></em> by specifying
 		precisely the domain users and groups that should be permitted access to the shares. You could, 
 		for example, set the following parameters:
@@ -1738,24 +1738,24 @@ session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
 	path = /export/demodata
 	valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"
 </pre><p>
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597596"></a><a name="id2597598"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597571"></a><a name="id2597573"></a></td><td align="left" valign="top"><p>
 		What are the benefits of using LDAP for my domain member servers?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597609"></a><a class="indexterm" name="id2597617"></a><a class="indexterm" name="id2597625"></a><a class="indexterm" name="id2597633"></a><a class="indexterm" name="id2597640"></a><a class="indexterm" name="id2597648"></a><a class="indexterm" name="id2597656"></a><a class="indexterm" name="id2597664"></a><a class="indexterm" name="id2597672"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597584"></a><a class="indexterm" name="id2597592"></a><a class="indexterm" name="id2597600"></a><a class="indexterm" name="id2597608"></a><a class="indexterm" name="id2597615"></a><a class="indexterm" name="id2597623"></a><a class="indexterm" name="id2597631"></a><a class="indexterm" name="id2597639"></a><a class="indexterm" name="id2597647"></a>
 		The key benefit of using LDAP is that the UID of all users and the GID of all groups
 		are globally consistent on domain controllers as well as on domain member servers.
 		This means that it is possible to copy/replicate files across servers without
 		loss of identity.
-		</p><p><a class="indexterm" name="id2597688"></a><a class="indexterm" name="id2597696"></a><a class="indexterm" name="id2597704"></a><a class="indexterm" name="id2597712"></a><a class="indexterm" name="id2597720"></a><a class="indexterm" name="id2597728"></a><a class="indexterm" name="id2597739"></a><a class="indexterm" name="id2597747"></a>
+		</p><p><a class="indexterm" name="id2597663"></a><a class="indexterm" name="id2597671"></a><a class="indexterm" name="id2597679"></a><a class="indexterm" name="id2597687"></a><a class="indexterm" name="id2597695"></a><a class="indexterm" name="id2597703"></a><a class="indexterm" name="id2597714"></a><a class="indexterm" name="id2597722"></a>
 		When use is made of account identity resolution via winbind, even when an IDMAP backend
 		is stored in LDAP, the UID/GID on domain member servers is consistent, but differs
 		from the ID that the user/group has on domain controllers. The winbind allocated UID/GID
 		that is stored in LDAP (or locally) will be in the numeric range specified in the <em class="parameter"><code>
 		idmap uid/gid</code></em> in the <code class="filename">smb.conf</code> file. On domain controllers, the UID/GID is
 		that of the POSIX value assigned in the LDAP directory as part of the POSIX account information.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597780"></a><a name="id2597782"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597755"></a><a name="id2597757"></a></td><td align="left" valign="top"><p>
 		Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into
 		my DNS configuration?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597793"></a><a class="indexterm" name="id2597805"></a><a class="indexterm" name="id2597816"></a><a class="indexterm" name="id2597824"></a><a class="indexterm" name="id2597832"></a><a class="indexterm" name="id2597839"></a><a class="indexterm" name="id2597847"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597768"></a><a class="indexterm" name="id2597780"></a><a class="indexterm" name="id2597791"></a><a class="indexterm" name="id2597798"></a><a class="indexterm" name="id2597806"></a><a class="indexterm" name="id2597814"></a><a class="indexterm" name="id2597822"></a>
 		Samba depends on correctly functioning resolution of hostnames to their IP address. Samba
 		makes no direct DNS lookup calls, but rather redirects all name-to-address calls via the
 		<code class="literal">getXXXbyXXX()</code> function calls. The configuration of the <code class="constant">hosts</code>
@@ -1768,23 +1768,23 @@ hosts: files dns wins
 		this means that a hostname lookup first tries the <code class="filename">/etc/hosts</code>.
 		If this fails to resolve, it attempts a DNS lookup, and if that fails, it tries a
 		WINS lookup.
-		</p><p><a class="indexterm" name="id2597902"></a><a class="indexterm" name="id2597910"></a><a class="indexterm" name="id2597918"></a>
+		</p><p><a class="indexterm" name="id2597877"></a><a class="indexterm" name="id2597885"></a><a class="indexterm" name="id2597892"></a>
 		The addition of the WINS-based name lookup makes sense only if NetBIOS over TCP/IP has
 		been enabled on all Windows clients. Where NetBIOS over TCP/IP has been disabled, DNS
 		is the preferred name resolution technology. This usually makes most sense when Samba
 		is a client of an Active Directory domain, where NetBIOS use has been disabled. In this
 		case, the Windows 200x autoregisters all locator records it needs with its own DNS
 		server or servers.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597938"></a><a name="id2597940"></a></td><td align="left" valign="top"><p>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597913"></a><a name="id2597915"></a></td><td align="left" valign="top"><p>
 		Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we
 		use Samba-3 with that configuration?
 		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
 		Yes.
-		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597956"></a><a name="id2597958"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2597962"></a><a class="indexterm" name="id2597976"></a>
+		</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2597931"></a><a name="id2597933"></a></td><td align="left" valign="top"><p><a class="indexterm" name="id2597936"></a><a class="indexterm" name="id2597951"></a>
 		When I tried to execute net ads join, I got no output. It did not work, so
 		I think that it failed. I then executed net rpc join and that worked fine.
 		That is okay, isn't it?
-		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2598000"></a><a class="indexterm" name="id2598008"></a>
+		</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p><a class="indexterm" name="id2597975"></a><a class="indexterm" name="id2597982"></a>
 		No. This is not okay. It means that your Samba-3 client has joined the ADS domain as
 		a Windows NT4 client, and Samba-3 will not be using Kerberos-based authentication.
 		</p></td></tr></tbody></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="DMSMig.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="DMSMig.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="upgrades.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part�II.�Domain Members, Updating Samba and Migration�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�8.�Updating Samba-3</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-ByExample/upgrades.html b/docs/htmldocs/Samba3-ByExample/upgrades.html
index 7ae5245fbf..0d98656798 100644
--- a/docs/htmldocs/Samba3-ByExample/upgrades.html
+++ b/docs/htmldocs/Samba3-ByExample/upgrades.html
@@ -1,14 +1,14 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�Updating Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="unixclients.html" title="Chapter�7.�Adding Domain Member Servers and Clients"><link rel="next" href="ntmigration.html" title="Chapter�9.�Migrating NT4 Domain to Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�Updating Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unixclients.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="ntmigration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrades"></a>Chapter�8.�Updating Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="upgrades.html#id2598125">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598221">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599550">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599919">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600245">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600427">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600542">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600746">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601160">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2598040"></a>
-<a class="indexterm" name="id2598047"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�Updating Samba-3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part�II.�Domain Members, Updating Samba and Migration"><link rel="prev" href="unixclients.html" title="Chapter�7.�Adding Domain Member Servers and Clients"><link rel="next" href="ntmigration.html" title="Chapter�9.�Migrating NT4 Domain to Samba-3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�Updating Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unixclients.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Domain Members, Updating Samba and Migration</th><td width="20%" align="right">�<a accesskey="n" href="ntmigration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrades"></a>Chapter�8.�Updating Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="upgrades.html#id2598100">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2598196">Cautions and Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2599525">Upgrading from Samba 1.x and 2.x to Samba-3</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#sbeug2">Samba 1.9.x and 2.x Versions Without LDAP</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2599894">Applicable to All Samba 2.x to Samba-3 Upgrades</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600227">Samba-2.x with LDAP Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrades.html#id2600409">Updating a Samba-3 Installation</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrades.html#id2600519">Samba-3 to Samba-3 Updates on the Same Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2600723">Migrating Samba-3 to a New Server</a></span></dt><dt><span class="sect2"><a href="upgrades.html#id2601137">Migration of Samba Accounts to Active Directory</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2598015"></a>
+<a class="indexterm" name="id2598022"></a>
 It was a little difficult to select an appropriate title for this chapter.
 From email messages on the Samba mailing lists it is clear that many people
 consider the updating and upgrading of Samba to be a migration matter. Others
 talk about migrating Samba servers when in fact the issue at hand is one of
 installing a new Samba server to replace an older existing Samba server.
 </p><p>
-<a class="indexterm" name="id2598064"></a>
-<a class="indexterm" name="id2598070"></a>
+<a class="indexterm" name="id2598039"></a>
+<a class="indexterm" name="id2598045"></a>
 There has also been much talk about migration of Samba-3 from an smbpasswd
 passdb backend to the use of the tdbsam or ldapsam facilities that are new
 to Samba-3.
@@ -17,19 +17,19 @@ Clearly, there is not a great deal of clarity in the terminology that various
 people apply to these modes by which Samba servers are updated. This is further 
 highlighted by an email posting that included the following neat remark:
 </p><div class="blockquote"><blockquote class="blockquote"><p>
-<a class="indexterm" name="id2598092"></a>
+<a class="indexterm" name="id2598067"></a>
 I like the &#8220;<span class="quote">net rpc vampire</span>&#8221; on NT4, but that to my surprise does
 not seem to work against a Samba PDC and, if addressed in the Samba to Samba
 context in either book, I could not find it.
 </p></blockquote></div><p>
-<a class="indexterm" name="id2598113"></a>
+<a class="indexterm" name="id2598088"></a>
 So in response to the significant request for these situations to be better 
 documented, this chapter has now been added. User contributions and documentation
 of real-world experiences are a most welcome addition to this chapter.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598125"></a>Introduction</h2></div></div></div><p>
-<a class="indexterm" name="id2598133"></a>
-<a class="indexterm" name="id2598139"></a>
-<a class="indexterm" name="id2598146"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598100"></a>Introduction</h2></div></div></div><p>
+<a class="indexterm" name="id2598108"></a>
+<a class="indexterm" name="id2598114"></a>
+<a class="indexterm" name="id2598121"></a>
 A Windows network administrator explained in an email what changes he was
 planning to make and followed with the question: &#8220;<span class="quote">Anyone done this
 before?</span>&#8221; Many of us have upgraded and updated Samba without incident.
@@ -44,28 +44,28 @@ this precautionary step, users will punish an administrator who
 fails to take adequate steps to avoid situations that may inflict lost
 productivity on them.
 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2598177"></a>
-<a class="indexterm" name="id2598184"></a>
+<a class="indexterm" name="id2598152"></a>
+<a class="indexterm" name="id2598159"></a>
 Samba makes it possible to upgrade and update configuration files, but it
 is not possible to downgrade the configuration files. Please ensure that
 all configuration and control files are backed up to permit a down-grade
 in the rare event that this may be necessary.
 </p></div><p>
-<a class="indexterm" name="id2598199"></a>
-<a class="indexterm" name="id2598206"></a>
+<a class="indexterm" name="id2598174"></a>
+<a class="indexterm" name="id2598181"></a>
 It is prudent also to backup all data files on the server before attempting
 to perform a major upgrade. Many administrators have experienced the consequences
 of failure to take adequate precautions. So what is adequate? That is simple!
 If data is lost during an upgrade or update and it can not be restored,
 the precautions taken were inadequate. If a backup was not needed, but was available,
 caution was on the side of the victor.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598221"></a>Cautions and Notes</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598196"></a>Cautions and Notes</h3></div></div></div><p>
 	Someone once said, &#8220;<span class="quote">It is good to be sorry, but better never to need to be!</span>&#8221;
 	These are wise words of advice to those contemplating a Samba upgrade or update.
 	</p><p>
-	<a class="indexterm" name="id2598239"></a>
-	<a class="indexterm" name="id2598245"></a>
-	<a class="indexterm" name="id2598252"></a>
+	<a class="indexterm" name="id2598214"></a>
+	<a class="indexterm" name="id2598220"></a>
+	<a class="indexterm" name="id2598227"></a>
 	This is as good a time as any to define the terms <code class="constant">upgrade</code> and
 	<code class="constant">update</code>. The term <code class="constant">upgrade</code> refers to
 	the installation of a version of Samba that is a whole generation or more ahead of
@@ -73,12 +73,12 @@ caution was on the side of the victor.
 	number. So far Samba has been released in generations 1.x, 2.x, 3.x, and currently 4.0
 	is in development.
 	</p><p>
-	<a class="indexterm" name="id2598279"></a>
+	<a class="indexterm" name="id2598254"></a>
 	The term <code class="constant">update</code> refers to a minor version number installation
 	in place of one of the same generation. For example, updating from Samba 3.0.10 to 3.0.14
 	is an update. The move from Samba 2.0.7 to 3.0.14 is an upgrade.
 	</p><p>
-	<a class="indexterm" name="id2598296"></a>
+	<a class="indexterm" name="id2598271"></a>
 	While the use of these terms is an exercise in semantics, what needs to be realized
 	is that there are major functional differences between a Samba 2.x release and a Samba
 	3.0.x release. Such differences may require a significantly different approach to
@@ -90,13 +90,13 @@ caution was on the side of the victor.
 	the greater the risk that noone will read it, but where there is no documentation,
 	noone can read it!</span>&#8221; While true, some documentation is an evil necessity.
 	It is hoped that this update to the documentation will avoid both extremes.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2598325"></a>Security Identifiers (SIDs)</h4></div></div></div><p>
-	<a class="indexterm" name="id2598333"></a>
-	<a class="indexterm" name="id2598342"></a>
-	<a class="indexterm" name="id2598349"></a>
-	<a class="indexterm" name="id2598356"></a>
-	<a class="indexterm" name="id2598362"></a>
-	<a class="indexterm" name="id2598372"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2598300"></a>Security Identifiers (SIDs)</h4></div></div></div><p>
+	<a class="indexterm" name="id2598308"></a>
+	<a class="indexterm" name="id2598317"></a>
+	<a class="indexterm" name="id2598324"></a>
+	<a class="indexterm" name="id2598331"></a>
+	<a class="indexterm" name="id2598337"></a>
+	<a class="indexterm" name="id2598346"></a>
 	Before the days of Windows NT and OS/2, every Windows and DOS networking client
 	that used the SMB protocols was an entirely autonomous entity. There was no concept
 	of a security identifier for a machine or a user outside of the username, the
@@ -104,46 +104,46 @@ caution was on the side of the victor.
 	in the same context as the way that the SID is used since the development of
 	Windows NT 3.10.
 	</p><p>
-	<a class="indexterm" name="id2598391"></a>
-	<a class="indexterm" name="id2598398"></a>
-	<a class="indexterm" name="id2598405"></a>
-	<a class="indexterm" name="id2598412"></a>
-	<a class="indexterm" name="id2598418"></a>
-	<a class="indexterm" name="id2598425"></a>
+	<a class="indexterm" name="id2598366"></a>
+	<a class="indexterm" name="id2598373"></a>
+	<a class="indexterm" name="id2598380"></a>
+	<a class="indexterm" name="id2598387"></a>
+	<a class="indexterm" name="id2598393"></a>
+	<a class="indexterm" name="id2598400"></a>
 	Versions of Samba prior to 1.9 did not make use of a SID. Instead they make exclusive use
 	of the username that is embedded in the SessionSetUpAndX component of the connection
 	setup process between a Windows client and an SMB/CIFS server. 
 	</p><p>
-	<a class="indexterm" name="id2598442"></a>
-	<a class="indexterm" name="id2598449"></a>
-	<a class="indexterm" name="id2598455"></a>
+	<a class="indexterm" name="id2598417"></a>
+	<a class="indexterm" name="id2598424"></a>
+	<a class="indexterm" name="id2598430"></a>
 	Around November 1997 support was added to Samba-1.9 to handle the Windows security
 	RPC-based protocols that implemented support for Samba to store a machine SID. This
 	information was stored in a file called <code class="filename">MACHINE.SID.</code>
 	</p><p>
-	<a class="indexterm" name="id2598475"></a>
-	<a class="indexterm" name="id2598482"></a>
-	<a class="indexterm" name="id2598488"></a>
+	<a class="indexterm" name="id2598450"></a>
+	<a class="indexterm" name="id2598456"></a>
+	<a class="indexterm" name="id2598463"></a>
 	Within the lifetime of the early Samba 2.x series, the machine SID information was
 	relocated into a tdb file called <code class="filename">secrets.tdb</code>, which is where
 	it is still located in Samba 3.0.x along with other information that pertains to the
 	local machine and its role within a domain security context.
 	</p><p>
+	<a class="indexterm" name="id2598484"></a>
+	<a class="indexterm" name="id2598493"></a>
+	<a class="indexterm" name="id2598502"></a>
 	<a class="indexterm" name="id2598509"></a>
-	<a class="indexterm" name="id2598518"></a>
-	<a class="indexterm" name="id2598527"></a>
-	<a class="indexterm" name="id2598534"></a>
 	There are two types of SID, those pertaining to the machine itself and the domain to
 	which it may belong, and those pertaining to users and groups within the security
 	context of the local machine, in the case of standalone servers (SAS) and domain member
 	servers (DMS).
 	</p><p>
-	<a class="indexterm" name="id2598548"></a>
-	<a class="indexterm" name="id2598555"></a>
-	<a class="indexterm" name="id2598562"></a>
-	<a class="indexterm" name="id2598569"></a>
-	<a class="indexterm" name="id2598576"></a>
-	<a class="indexterm" name="id2598582"></a>
+	<a class="indexterm" name="id2598523"></a>
+	<a class="indexterm" name="id2598530"></a>
+	<a class="indexterm" name="id2598537"></a>
+	<a class="indexterm" name="id2598544"></a>
+	<a class="indexterm" name="id2598551"></a>
+	<a class="indexterm" name="id2598557"></a>
 	When the Samba <code class="literal">smbd</code> daemon is first started, if the <code class="filename">secrets.tdb</code>
 	file does not exist, it is created at the first client connection attempt. If this file does
 	exist, <code class="literal">smbd</code> checks that there is a machine SID (if it is a domain controller,
@@ -153,7 +153,7 @@ caution was on the side of the victor.
 	manner. This means that each time it is generated for a particular combination of machine name
 	(hostname) and domain name (workgroup), it will be different.
 	</p><p>
-	<a class="indexterm" name="id2598632"></a>
+	<a class="indexterm" name="id2598607"></a>
 	The SID is the key used by MS Windows networking for all networking operations. This means
 	that when the machine or domain SID changes, all security-encoded objects such as profiles
 	and ACLs may become unusable.
@@ -162,22 +162,22 @@ caution was on the side of the victor.
 	the event of a change of hostname (machine name) or domain name (workgroup) the SID can
 	be restored to its previous value.
 	</p></div><p>
-	<a class="indexterm" name="id2598653"></a>
-	<a class="indexterm" name="id2598660"></a>
-	<a class="indexterm" name="id2598667"></a>
-	<a class="indexterm" name="id2598673"></a>
-	<a class="indexterm" name="id2598680"></a>
-	<a class="indexterm" name="id2598687"></a>
-	<a class="indexterm" name="id2598694"></a>
-	<a class="indexterm" name="id2598701"></a>
-	<a class="indexterm" name="id2598708"></a>
-	<a class="indexterm" name="id2598714"></a>
+	<a class="indexterm" name="id2598628"></a>
+	<a class="indexterm" name="id2598635"></a>
+	<a class="indexterm" name="id2598642"></a>
+	<a class="indexterm" name="id2598648"></a>
+	<a class="indexterm" name="id2598655"></a>
+	<a class="indexterm" name="id2598662"></a>
+	<a class="indexterm" name="id2598669"></a>
+	<a class="indexterm" name="id2598676"></a>
+	<a class="indexterm" name="id2598683"></a>
+	<a class="indexterm" name="id2598689"></a>
 	In Samba-3 on a domain controller (PDC or BDC), the domain name controls the domain
 	SID. On all prior versions the hostname (computer name, or NetBIOS name) controlled
 	the SID. On a standalone server the hostname still controls the SID.
 	</p><p>
-	<a class="indexterm" name="id2598728"></a>
-	<a class="indexterm" name="id2598737"></a>
+	<a class="indexterm" name="id2598703"></a>
+	<a class="indexterm" name="id2598712"></a>
 	The local machine SID can be backed up using this procedure (Samba-3):
 </p><pre class="screen">
 <code class="prompt">root# </code> net getlocalsid &gt; /etc/samba/my-local-SID
@@ -200,7 +200,7 @@ SID for domain FRODO is: S-1-5-21-726309263-4128913605-1168186429
 	ability to read the older tdb file and to perform an in-situ update to the latest tdb format.
 	This is not a reversible process  it is a one-way upgrade.
 	</p><p>
-	<a class="indexterm" name="id2598826"></a>
+	<a class="indexterm" name="id2598801"></a>
 	In the course of the Samba 2.0.x series the <code class="literal">smbpasswd</code> was modified to
 	permit the domain SID to be captured to the <code class="filename">secrets.tdb</code> file by executing:
 </p><pre class="screen">
@@ -217,8 +217,8 @@ SID for domain FRODO is: S-1-5-21-726309263-4128913605-1168186429
 <code class="prompt">root# </code> smbpasswd -W S-1-5-21-726309263-4128913605-1168186429
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2598899"></a>
-	<a class="indexterm" name="id2598906"></a>
+	<a class="indexterm" name="id2598874"></a>
+	<a class="indexterm" name="id2598881"></a>
 	Domain security information, which includes the domain SID, can be obtained from Samba-2.2.x
 	systems by executing:
 </p><pre class="screen">
@@ -237,9 +237,9 @@ Num local groups: 0
 	It is a very good practice to store this SID information in a safely kept file, just in
 	case it is ever needed at a later date.
 	</p><p>
-	<a class="indexterm" name="id2598953"></a>
-	<a class="indexterm" name="id2598960"></a>
-	<a class="indexterm" name="id2598966"></a>
+	<a class="indexterm" name="id2598928"></a>
+	<a class="indexterm" name="id2598935"></a>
+	<a class="indexterm" name="id2598941"></a>
 	Take note that the domain SID is used extensively in Samba. Where LDAP is used for the
 	<em class="parameter"><code>passdb backend</code></em>, all user, group, and trust accounts are encoded
 	with the domain SID. This means that if the domain SID changes for any reason, the entire
@@ -250,9 +250,9 @@ Num local groups: 0
 <code class="prompt">root# </code> slapcat -v -l filename.ldif
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2599002"></a>
-	<a class="indexterm" name="id2599009"></a>
-	<a class="indexterm" name="id2599016"></a>
+	<a class="indexterm" name="id2598977"></a>
+	<a class="indexterm" name="id2598984"></a>
+	<a class="indexterm" name="id2598991"></a>
 	When the domain SID has changed, roaming profiles cease to be functional. The recovery
 	of roaming profiles necessitates resetting of the domain portion of the user SID
 	that owns the profile. This is encoded in the <code class="filename">NTUser.DAT</code> and can be
@@ -261,9 +261,9 @@ Num local groups: 0
 	complain to the Samba Team if this utility is missing; that issue that must be
 	addressed to the creator of the RPM package. The Samba Team do their best to make
 	available all the tools needed to manage a Samba-based Windows networking environment.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599053"></a>Change of hostname</h4></div></div></div><p>
-	<a class="indexterm" name="id2599061"></a>
-	<a class="indexterm" name="id2599070"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599028"></a>Change of hostname</h4></div></div></div><p>
+	<a class="indexterm" name="id2599036"></a>
+	<a class="indexterm" name="id2599045"></a>
 	Samba uses two methods by which the primary NetBIOS machine name (also known as a computer
 	name or the hostname) may be determined: If the <code class="filename">smb.conf</code> file contains a
 	<em class="parameter"><code>netbios name</code></em> entry, its value will be used directly. In the absence
@@ -277,13 +277,13 @@ Num local groups: 0
 	Do NOT change the hostname or the <em class="parameter"><code>netbios name</code></em>. If this
 	is changed, be sure to reset the machine SID to the original setting. Otherwise
 	there may be serious interoperability and/or operational problems.
-	</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599119"></a>Change of Workgroup (Domain) Name</h4></div></div></div><p>
-	<a class="indexterm" name="id2599127"></a>
+	</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599094"></a>Change of Workgroup (Domain) Name</h4></div></div></div><p>
+	<a class="indexterm" name="id2599102"></a>
 	The domain name of a Samba server is identical to the workgroup name and is
 	set in the <code class="filename">smb.conf</code> file using the <em class="parameter"><code>workgroup</code></em> parameter.
 	This has been consistent throughout the history of Samba and across all versions.
 	</p><p>
-	<a class="indexterm" name="id2599152"></a>
+	<a class="indexterm" name="id2599127"></a>
 	Be aware that when the workgroup name is changed, a new SID will be generated.
 	The old domain SID can be reset using the procedure outlined earlier in this chapter.
 	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sbeug1"></a>Location of config files</h4></div></div></div><p>
@@ -292,7 +292,7 @@ Num local groups: 0
 	have varied the location of the Samba control files. This has led to some confusion
 	for network administrators.
 	</p><p>
-	<a class="indexterm" name="id2599183"></a>
+	<a class="indexterm" name="id2599158"></a>
 	The Samba 1.9.x <code class="filename">smb.conf</code> file may be found either in the <code class="filename">/etc</code>
 	directory or in <code class="filename">/usr/local/samba/lib</code>.
 	</p><p>
@@ -300,12 +300,12 @@ Num local groups: 0
 	on Linux systems to the <code class="filename">/etc/samba</code> directory where it
 	remains located also for Samba 3.0.x installations.
 	</p><p>
-	<a class="indexterm" name="id2599230"></a>
+	<a class="indexterm" name="id2599205"></a>
 	Samba 2.x introduced the <code class="filename">secrets.tdb</code> file that is also stored in the
 	<code class="filename">/etc/samba</code> directory, or in the <code class="filename">/usr/local/samba/lib</code>
 	directory subsystem.
 	</p><p>
-	<a class="indexterm" name="id2599260"></a>
+	<a class="indexterm" name="id2599234"></a>
 	The location at which <code class="literal">smbd</code> expects to find all configuration and control
 	files is determined at the time of compilation of Samba. For versions of Samba prior to
 	3.0, one way to find the expected location of these files is to execute:
@@ -317,7 +317,7 @@ Num local groups: 0
 	Note: The <code class="literal">smbd</code> executable may be located in the path
 	<code class="filename">/usr/local/samba/sbin</code>.
 	</p><p>
-	<a class="indexterm" name="id2599318"></a>
+	<a class="indexterm" name="id2599292"></a>
 	Samba-3 provides a neat new way to track the location of all control files as well as to
 	find the compile-time options used as the Samba package was built. Here  is how the dark
 	secrets of the internals of the location of control files within Samba executables can
@@ -348,37 +348,37 @@ Paths:
  ... 
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2599355"></a>
+	<a class="indexterm" name="id2599330"></a>
 	It is important that both the <code class="filename">smb.conf</code> file and the <code class="filename">secrets.tdb</code>
 	be backed up before attempting any upgrade. The <code class="filename">secrets.tdb</code> file
 	is version-encoded, and therefore a newer version may not work with an older version
 	of Samba. A backup means that it is always possible to revert a failed or problematic
 	upgrade.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599385"></a>International Language Support</h4></div></div></div><p>
-	<a class="indexterm" name="id2599393"></a>
-	<a class="indexterm" name="id2599400"></a>
-	<a class="indexterm" name="id2599407"></a>
-	<a class="indexterm" name="id2599414"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599360"></a>International Language Support</h4></div></div></div><p>
+	<a class="indexterm" name="id2599368"></a>
+	<a class="indexterm" name="id2599375"></a>
+	<a class="indexterm" name="id2599382"></a>
+	<a class="indexterm" name="id2599388"></a>
 	Samba-2.x had no support for Unicode; instead, all national language character-set support in file names
 	was done using particular locale codepage mapping techniques. Samba-3 supports Unicode in file names, thus
 	providing true internationalization support.
 	</p><p>
-	<a class="indexterm" name="id2599428"></a>
+	<a class="indexterm" name="id2599403"></a>
 	Non-English users whose national language character set has special characters and who upgrade naively will 
 	find that many files that have the special characters in the file name will see them garbled and jumbled up.
 	This typically happens with umlauts and accents because these characters were particular to the codepage
 	that was in use with Samba-2.x using an 8-bit encoding scheme.
 	</p><p>
-	<a class="indexterm" name="id2599445"></a>
+	<a class="indexterm" name="id2599420"></a>
 	Files that are created with Samba-3 will use UTF-8 encoding. Should the file system ever end up with a
 	mix of codepage (unix charset)-encoded file names and UTF-8-encoded file names, the mess will take some
 	effort to set straight.
 	</p><p>
-	<a class="indexterm" name="id2599459"></a>
+	<a class="indexterm" name="id2599434"></a>
 	A very helpful tool is available from Bjorn Jacke's <a class="ulink" href="http://j3e.de/linux/convmv/" target="_top">convmv</a>
 	work. Convmv is a tool that can be used to convert file and directory names from one encoding method to
 	another. The most common use for this tool is to convert locale-encoded files to UTF-8 Unicode encoding.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599479"></a>Updates and Changes in Idealx smbldap-tools</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599454"></a>Updates and Changes in Idealx smbldap-tools</h4></div></div></div><p>
 	The smbldap-tools have been maturing rapidly over the past year. With maturation comes change.
 	The location of the <code class="filename">smbldap.conf</code> and the <code class="filename">smbldap_bind.conf</code>
 	configuration files have been moved from the directory <code class="filename">/etc/smbldap-tools</code> to
@@ -392,7 +392,7 @@ Paths:
 	<code class="constant">sambaDomainName</code>. Anyone who updates from an older version to the
 	current release should note that the information stored under <code class="constant">NextFreeUnixId</code>
 	must now be relocated to the DIT object <code class="constant">sambaDomainName</code>.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599550"></a>Upgrading from Samba 1.x and 2.x to Samba-3</h2></div></div></div><p>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599525"></a>Upgrading from Samba 1.x and 2.x to Samba-3</h2></div></div></div><p>
 Sites that are being upgraded from Samba-2 (or earlier versions) to Samba-3
 may experience little difficulty or may require a lot of effort, depending
 on the complexity of the configuration. Samba-1.9.x upgrades to Samba-3 will
@@ -405,10 +405,10 @@ Samba-2.x could be compiled with LDAP support.
 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sbeug2"></a>Samba 1.9.x and 2.x Versions Without LDAP</h3></div></div></div><p>
 	Where it is necessary to upgrade an old Samba installation to Samba-3,
 	the following procedure can be followed:
-	</p><div class="procedure"><a name="id2599588"></a><p class="title"><b>Procedure�8.1.�Upgrading from a Pre-Samba-3 Version</b></p><ol type="1"><li><p>
-		<a class="indexterm" name="id2599599"></a>
-		<a class="indexterm" name="id2599606"></a>
-		<a class="indexterm" name="id2599613"></a>
+	</p><div class="procedure"><a name="id2599563"></a><p class="title"><b>Procedure�8.1.�Upgrading from a Pre-Samba-3 Version</b></p><ol type="1"><li><p>
+		<a class="indexterm" name="id2599574"></a>
+		<a class="indexterm" name="id2599581"></a>
+		<a class="indexterm" name="id2599588"></a>
 		Stop Samba. This can be done using the appropriate system tool
 		that is particular for each operating system or by executing the
 		<code class="literal">kill</code> command on <code class="literal">smbd</code>,
@@ -423,10 +423,10 @@ Samba-2.x could be compiled with LDAP support.
 		Find the location of the <code class="filename">secrets.tdb</code> file and
 		back it up to a safe location.
 		</p></li><li><p>
-		<a class="indexterm" name="id2599694"></a>
-		<a class="indexterm" name="id2599701"></a>
-		<a class="indexterm" name="id2599708"></a>
-		<a class="indexterm" name="id2599715"></a>
+		<a class="indexterm" name="id2599669"></a>
+		<a class="indexterm" name="id2599676"></a>
+		<a class="indexterm" name="id2599683"></a>
+		<a class="indexterm" name="id2599690"></a>
 		Find the location of the lock directory. This is the directory
 		in which Samba stores all its tdb control files. The default
 		location used by the Samba Team is in
@@ -437,7 +437,7 @@ Samba-2.x could be compiled with LDAP support.
 		<code class="filename">/var/lib/samba</code> directory. Copy all the
 		tdb files to a safe location.
 		</p></li><li><p>
-		<a class="indexterm" name="id2599754"></a>
+		<a class="indexterm" name="id2599728"></a>
 		It is now safe to upgrade the Samba installation. On Linux systems
 		it is not necessary to remove the Samba RPMs because a simple
 		upgrade installation will automatically remove the old files.
@@ -456,7 +456,7 @@ Samba-2.x could be compiled with LDAP support.
 		</p></li><li><p>
 		Do not change the workgroup name.
 		</p></li><li><p>
-		<a class="indexterm" name="id2599809"></a>
+		<a class="indexterm" name="id2599784"></a>
 		Execute the <code class="literal">testparm</code> to validate the <code class="filename">smb.conf</code> file.
 		This process will flag any parameters that are no longer supported.
 		It will also flag configuration settings that may be in conflict.
@@ -468,67 +468,67 @@ Samba-2.x could be compiled with LDAP support.
 <code class="prompt">root# </code> cd /etc/samba
 <code class="prompt">root# </code> testparm -s smb.conf.master &gt; smb.conf
 </pre><p>
-	<a class="indexterm" name="id2599866"></a>
+	<a class="indexterm" name="id2599841"></a>
 		The resulting <code class="filename">smb.conf</code> file will be stripped of all comments
 		and of all nonconforming configuration settings.
 		</p></li><li><p>
-		<a class="indexterm" name="id2599888"></a>
+		<a class="indexterm" name="id2599863"></a>
 		It is now safe to start Samba using the appropriate system tool.
 		Alternately, it is possible to just execute <code class="literal">nmbd</code>,
 		<code class="literal">smbd</code>, and <code class="literal">winbindd</code> for the command
 		line while logged in as the root user.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2599919"></a>Applicable to All Samba 2.x to Samba-3 Upgrades</h3></div></div></div><p>
-	<a class="indexterm" name="id2599927"></a>
-	<a class="indexterm" name="id2599934"></a>
-	<a class="indexterm" name="id2599940"></a>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2599894"></a>Applicable to All Samba 2.x to Samba-3 Upgrades</h3></div></div></div><p>
+	<a class="indexterm" name="id2599902"></a>
+	<a class="indexterm" name="id2599908"></a>
+	<a class="indexterm" name="id2599915"></a>
 	Samba 2.x servers that were running as a domain controller (PDC)
 	require changes to the configuration of the scripting interface
 	tools that Samba uses to perform OS updates for
 	users, groups, and trust accounts (machines and interdomain).
 	</p><p>
-	<a class="indexterm" name="id2599955"></a>
+	<a class="indexterm" name="id2599930"></a>
 	The following parameters are new to Samba-3 and should be correctly configured.
-	Please refer to <a class="link" href="secure.html" title="Chapter�3.�Secure Office Networking">&#8220;Secure Office Networking&#8221;</a> through <a class="link" href="net2000users.html" title="Chapter�6.�A Distributed 2000-User Network">&#8220;A Distributed 2000-User Network&#8221;</a>
+	Please refer to <a class="link" href="secure.html" title="Chapter�3.�Secure Office Networking">&#8220;Secure Office Networking&#8221;</a> through <a class="link" href="2000users.html" title="Chapter�6.�A Distributed 2000-User Network">&#8220;A Distributed 2000-User Network&#8221;</a>
 	in this book for examples of use of the new parameters shown here:
-	<a class="indexterm" name="id2599976"></a>
-	<a class="indexterm" name="id2599983"></a>
-	<a class="indexterm" name="id2599990"></a>
-	<a class="indexterm" name="id2599997"></a>
-	<a class="indexterm" name="id2600004"></a>
-	<a class="indexterm" name="id2600011"></a>
-	<a class="indexterm" name="id2600018"></a>
-	</p><p>
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td>add group script</td></tr><tr><td>add machine script</td></tr><tr><td>add user to group script</td></tr><tr><td>delete group script</td></tr><tr><td>delete user from group script</td></tr><tr><td>passdb backend</td></tr><tr><td>set primary group script</td></tr></table><p>
-	</p><p>
-	<a class="indexterm" name="id2600063"></a>
-	<a class="indexterm" name="id2600070"></a>
+	<a class="indexterm" name="id2599951"></a>
+	<a class="indexterm" name="id2599958"></a>
+	<a class="indexterm" name="id2599964"></a>
+	<a class="indexterm" name="id2599972"></a>
+	<a class="indexterm" name="id2599978"></a>
+	<a class="indexterm" name="id2599986"></a>
+	<a class="indexterm" name="id2599993"></a>
+	</p><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>add group script</p></td></tr><tr><td><p>add machine script</p></td></tr><tr><td><p>add user to group script</p></td></tr><tr><td><p>delete group script</p></td></tr><tr><td><p>delete user from group script</p></td></tr><tr><td><p>passdb backend</p></td></tr><tr><td><p>set primary group script</p></td></tr></table><p>
+	</p><p>
+	<a class="indexterm" name="id2600045"></a>
+	<a class="indexterm" name="id2600052"></a>
 	The <em class="parameter"><code>add machine script</code></em> functionality was previously
 	handled by the <em class="parameter"><code>add user script</code></em>, which in Samba-3 is
 	used exclusively to add user accounts.
 	</p><p>
-	<a class="indexterm" name="id2600094"></a>
-	<a class="indexterm" name="id2600101"></a>
-	<a class="indexterm" name="id2600108"></a>
-	<a class="indexterm" name="id2600114"></a>
-	<a class="indexterm" name="id2600121"></a>
-	<a class="indexterm" name="id2600128"></a>
-	<a class="indexterm" name="id2600135"></a>
-	<a class="indexterm" name="id2600142"></a>
-	<a class="indexterm" name="id2600148"></a>
+	<a class="indexterm" name="id2600076"></a>
+	<a class="indexterm" name="id2600083"></a>
+	<a class="indexterm" name="id2600090"></a>
+	<a class="indexterm" name="id2600096"></a>
+	<a class="indexterm" name="id2600103"></a>
+	<a class="indexterm" name="id2600110"></a>
+	<a class="indexterm" name="id2600117"></a>
+	<a class="indexterm" name="id2600124"></a>
+	<a class="indexterm" name="id2600130"></a>
 	Where the <em class="parameter"><code>passdb backend</code></em> used is either <code class="constant">smbpasswd</code>
 	(the default) or the new <code class="constant">tdbsam</code>, the system interface scripts
 	are typically used. These involve use of OS tools such as <code class="literal">useradd</code>,
 	<code class="literal">usermod</code>, <code class="literal">userdel</code>, <code class="literal">groupadd</code>,
 	<code class="literal">groupmod</code>, <code class="literal">groupdel</code>, and so on.
 	</p><p>
-	<a class="indexterm" name="id2600209"></a>
-	<a class="indexterm" name="id2600216"></a>
-	<a class="indexterm" name="id2600223"></a>
+	<a class="indexterm" name="id2600191"></a>
+	<a class="indexterm" name="id2600198"></a>
+	<a class="indexterm" name="id2600205"></a>
 	Where the <em class="parameter"><code>passdb backend</code></em> makes use of an LDAP directory,
 	it is necessary either to use the <code class="constant">smbldap-tools</code> provided
 	by Idealx or to use an alternate toolset provided by a third
 	party or else home-crafted to manage the LDAP directory accounts.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600245"></a>Samba-2.x with LDAP Support</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600227"></a>Samba-2.x with LDAP Support</h3></div></div></div><p>
 	Samba version 2.x could be compiled for use either with or without LDAP.
 	The LDAP control settings in the <code class="filename">smb.conf</code> file in this old version are
 	completely different (and less complete) than they are with Samba-3. This
@@ -538,8 +538,8 @@ Samba-2.x could be compiled with LDAP support.
 	Follow the procedure outlined in <a class="link" href="upgrades.html#sbeug2" title="Samba 1.9.x and 2.x Versions Without LDAP">&#8220;Samba 1.9.x and 2.x Versions Without LDAP&#8221;</a> to affect a migration
 	of all files to the correct locations.
 	</p><p>
-	<a class="indexterm" name="id2600280"></a>
-	<a class="indexterm" name="id2600286"></a>
+	<a class="indexterm" name="id2600262"></a>
+	<a class="indexterm" name="id2600268"></a>
 	The Samba SAM schema required for Samba-3 is significantly different from that
 	used with Samba 2.x. This means that the LDAP directory must be updated
 	using the procedure outlined in the Samba WHATSNEW.txt file that accompanies
@@ -694,19 +694,19 @@ in the list.
 Due to a limitation in Samba's smb.conf parsing, you should not surround
 the DN's with quotation marks.
 </pre><p>
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2600427"></a>Updating a Samba-3 Installation</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2600409"></a>Updating a Samba-3 Installation</h2></div></div></div><p>
 The key concern in this section is to deal with the changes that have been
 affected in Samba-3 between the Samba-3.0.0 release and the current update.
 Network administrators have expressed concerns over the steps that should be
 taken to update Samba-3 versions.
 </p><p>
-<a class="indexterm" name="id2600443"></a>
+<a class="indexterm" name="id2600425"></a>
 The information in <a class="link" href="upgrades.html#sbeug1" title="Location of config files">&#8220;Location of config files&#8221;</a> would not be necessary if every
 person who has ever produced Samba executable (binary) files could agree on
 the preferred location of the <code class="filename">smb.conf</code> file and other Samba control files.
 Clearly, such agreement is further away than a pipedream.
 </p><p>
-<a class="indexterm" name="id2600468"></a>
+<a class="indexterm" name="id2600451"></a>
 Vendors and packagers who produce Samba binary installable packages do not,
 as a rule, use the default paths used by the Samba-Team for the location of
 the binary files, the <code class="filename">smb.conf</code> file, and the Samba control files (tdb's
@@ -719,54 +719,54 @@ by the Samba-Team. This can lead to confusion and to much lost time as the
 uninformed administrator deals with apparent failure of the update to take
 effect.
 </p><p>
-<a class="indexterm" name="id2600502"></a>
+<a class="indexterm" name="id2600484"></a>
 The best advice for those lacking in code compilation experience is to use
 only vendor (or Samba-Team) provided binary packages. The Samba packages
 that are provided by the Samba-Team are generally built to use file paths
 that are compatible with the original OS vendor's practices.
 </p><p>
-<a class="indexterm" name="id2600517"></a>
-<a class="indexterm" name="id2600524"></a>
+<a class="indexterm" name="id2600499"></a>
+<a class="indexterm" name="id2600506"></a>
 If you are not sure whether a binary package complies with the OS
 vendor's practices, it is better to ask the package maintainer via
 email than to waste much time dealing with the nuances.
 Alternately, just diagnose the paths specified by the binary files following
 the procedure outlined above.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600542"></a>Samba-3 to Samba-3 Updates on the Same Server</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600519"></a>Samba-3 to Samba-3 Updates on the Same Server</h3></div></div></div><p>
 	The guidance in this section deals with updates to an existing
 	Samba-3 server installation.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600553"></a>Updating from Samba Versions Earlier than 3.0.5</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600530"></a>Updating from Samba Versions Earlier than 3.0.5</h4></div></div></div><p>
 	With the provision that the binary Samba-3 package has been built
 	with the same path and feature settings as the existing Samba-3
 	package that is being updated, an update of Samba-3 versions 3.0.0
 	through 3.0.4 can be updated to 3.0.5 without loss of functionality
 	and without need to change either the <code class="filename">smb.conf</code> file or, where
 	used, the LDAP schema.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600576"></a>Updating from Samba Versions between 3.0.6 and 3.0.10</h4></div></div></div><p>
-	<a class="indexterm" name="id2600584"></a>
-	<a class="indexterm" name="id2600591"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600553"></a>Updating from Samba Versions between 3.0.6 and 3.0.10</h4></div></div></div><p>
+	<a class="indexterm" name="id2600561"></a>
+	<a class="indexterm" name="id2600568"></a>
 	When updating versions of Samba-3 prior to 3.0.6 to 3.0.6 through 3.0.10,
 	it is necessary only to update the LDAP schema (where LDAP is used).
 	Always use the LDAP schema file that is shipped with the latest Samba-3
 	update.
 	</p><p>
-	<a class="indexterm" name="id2600607"></a>
-	<a class="indexterm" name="id2600614"></a>
-	<a class="indexterm" name="id2600621"></a>
+	<a class="indexterm" name="id2600585"></a>
+	<a class="indexterm" name="id2600591"></a>
+	<a class="indexterm" name="id2600598"></a>
 	Samba-3.0.6 introduced the ability to remember the last <span class="emphasis"><em>n</em></span> number
 	of passwords a user has used. This information will work only with
 	the <code class="constant">tdbsam</code> and <code class="constant">ldapsam</code>
 	<em class="parameter"><code>passdb backend</code></em> facilities.
 	</p><p>
 	After updating the LDAP schema, do not forget to re-index the LDAP database.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600654"></a>Updating from Samba Versions after 3.0.6 to a Current Release</h4></div></div></div><p>
-	<a class="indexterm" name="id2600663"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600632"></a>Updating from Samba Versions after 3.0.6 to a Current Release</h4></div></div></div><p>
+	<a class="indexterm" name="id2600640"></a>
 	Samba-3.0.8 introduced changes in how the <em class="parameter"><code>username map</code></em>
 	behaves. It also included a change in behavior of <code class="literal">winbindd</code>.
 	Please refer to the man page for <code class="filename">smb.conf</code> before implementing any update
 	from versions prior to 3.0.8 to a current version.
 	</p><p>
-	<a class="indexterm" name="id2600695"></a>
+	<a class="indexterm" name="id2600672"></a>
 	In Samba-3.0.11 a new privileges interface was implemented. Please
 	refer to <a class="link" href="happy.html#sbehap-ppc" title="Addition of Machines to the Domain">&#8220;Addition of Machines to the Domain&#8221;</a> for information regarding this new
 	feature. It is not necessary to implement the privileges interface, but it
@@ -788,12 +788,12 @@ and all machine and inter-domain trust-accounts must be located
 below the machine suffix.  Previous Samba releases would fall
 back to searching the 'ldap suffix' in some cases.
 </pre><p>
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600746"></a>Migrating Samba-3 to a New Server</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2600723"></a>Migrating Samba-3 to a New Server</h3></div></div></div><p>
 	The two most likely candidates for replacement of a server are
 	domain member servers and domain controllers. Each needs to be
 	handled slightly differently.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600758"></a>Replacing a Domain Member Server</h4></div></div></div><p>
-	<a class="indexterm" name="id2600766"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600735"></a>Replacing a Domain Member Server</h4></div></div></div><p>
+	<a class="indexterm" name="id2600743"></a>
 	Replacement of a domain member server should be done
 	using the same procedure as outlined in <a class="link" href="unixclients.html" title="Chapter�7.�Adding Domain Member Servers and Clients">&#8220;Adding Domain Member Servers and Clients&#8221;</a>.
 	</p><p>
@@ -802,12 +802,12 @@ back to searching the 'ldap suffix' in some cases.
 	that the new server be renamed to that of the old server. This will
 	change its SID and will necessitate rejoining to the domain.
 	</p><p>
-	<a class="indexterm" name="id2600791"></a>
-	<a class="indexterm" name="id2600798"></a>
-	<a class="indexterm" name="id2600805"></a>
-	<a class="indexterm" name="id2600811"></a>
-	<a class="indexterm" name="id2600818"></a>
-	<a class="indexterm" name="id2600825"></a>
+	<a class="indexterm" name="id2600768"></a>
+	<a class="indexterm" name="id2600775"></a>
+	<a class="indexterm" name="id2600782"></a>
+	<a class="indexterm" name="id2600789"></a>
+	<a class="indexterm" name="id2600795"></a>
+	<a class="indexterm" name="id2600802"></a>
 	Following a change of hostname (NetBIOS name) it is a good idea on all servers
 	to shut down the Samba <code class="literal">smbd</code>, <code class="literal">nmbd</code>, and
 	<code class="literal">winbindd</code> services, delete the <code class="filename">wins.dat</code>
@@ -817,10 +817,10 @@ back to searching the 'ldap suffix' in some cases.
 	resolution problems. These problems usually clear within 45 minutes of a name
 	change, but can persist for a longer period of time.
 	</p><p>
-	<a class="indexterm" name="id2600872"></a>
-	<a class="indexterm" name="id2600879"></a>
-	<a class="indexterm" name="id2600886"></a>
-	<a class="indexterm" name="id2600893"></a>
+	<a class="indexterm" name="id2600850"></a>
+	<a class="indexterm" name="id2600856"></a>
+	<a class="indexterm" name="id2600863"></a>
+	<a class="indexterm" name="id2600870"></a>
 	If the old domain member server had local accounts, it is necessary to create
 	on the new domain member server the same accounts with the same UID and GID
 	for each account. Where the <em class="parameter"><code>passdb backend</code></em> database
@@ -831,13 +831,13 @@ back to searching the 'ldap suffix' in some cases.
 	<code class="filename">/etc/group</code> files. In this case, be sure to copy these
 	account entries to the new target server.
 	</p><p>
-	<a class="indexterm" name="id2600941"></a>
+	<a class="indexterm" name="id2600918"></a>
 	Where the user accounts for both UNIX and Samba are stored in LDAP, the new
 	target server must be configured to use the <code class="literal">nss_ldap</code> tool set.
 	This will automatically ensure that the appropriate user entities are
 	available on the new server.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600960"></a>Replacing a Domain Controller</h4></div></div></div><p>
-	<a class="indexterm" name="id2600968"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600937"></a>Replacing a Domain Controller</h4></div></div></div><p>
+	<a class="indexterm" name="id2600945"></a>
 	In the past, people who replaced a Windows NT4 domain controller typically
 	installed a new server, created printers and file shares on it, then migrate across
 	all data that was destined to reside on it. The same can of course be done with
@@ -890,10 +890,10 @@ back to searching the 'ldap suffix' in some cases.
 	or the <em class="parameter"><code>netbios name</code></em> is set to the original server name, Samba
 	should correctly pick up the original SID and preserve all other settings. It is
 	sound advice to validate this before turning the system over to users.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601160"></a>Migration of Samba Accounts to Active Directory</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601137"></a>Migration of Samba Accounts to Active Directory</h3></div></div></div><p>
 	Yes, it works. The Windows ADMT tool can be used to migrate Samba accounts
 	to MS Active Directory.  There are a few pitfalls to be aware of:
-	</p><div class="procedure"><a name="id2601172"></a><p class="title"><b>Procedure�8.2.�Migration to Active Directory</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2601149"></a><p class="title"><b>Procedure�8.2.�Migration to Active Directory</b></p><ol type="1"><li><p>
 		Administrator password must be THE SAME on the Samba server,
 		the 2003 ADS, and the local Administrator account on the workstations. 
 		Perhaps this goes without saying, but there needs to be an account
@@ -914,7 +914,7 @@ back to searching the 'ldap suffix' in some cases.
 		Disable the Windows Firewall on all workstations. Otherwise, 
 		workstations won't be migrated to the new domain.
 		</p></li><li><p>
-		<a class="indexterm" name="id2601238"></a>
+		<a class="indexterm" name="id2601216"></a>
 		When migrating machines, always test first (using ADMT's test mode) 
 		and satisfy all errors before committing the migration. Note that the 
 		test will always fail, because the machine will not have been actually 
@@ -922,7 +922,7 @@ back to searching the 'ldap suffix' in some cases.
 		failure was due to a problem or simply to the fact that it was just 
 		a test.
 		</p></li></ol></div><p>
-	<a class="indexterm" name="id2601256"></a>
+	<a class="indexterm" name="id2601233"></a>
 	There are some significant benefits of using the ADMT, besides just 
 	migrating user accounts. ADMT can be found on the Windows 2003 CD.
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/Packaging.html b/docs/htmldocs/Samba3-Developers-Guide/Packaging.html
index 70cb45f01f..15306be73a 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/Packaging.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/Packaging.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�Notes to packagers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt05.html" title="Part�V.�Appendices"><link rel="prev" href="pt05.html" title="Part�V.�Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�Notes to packagers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt05.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Appendices</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Packaging"></a>Chapter�16.�Notes to packagers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Packaging.html#id2562007">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562040">Modules</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562007"></a>Versioning</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�Notes to packagers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt05.html" title="Part�V.�Appendices"><link rel="prev" href="pt05.html" title="Part�V.�Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�Notes to packagers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt05.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Appendices</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Packaging"></a>Chapter�16.�Notes to packagers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Packaging.html#id2561975">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562008">Modules</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561975"></a>Versioning</h2></div></div></div><p>
 Please, please set the vendor version suffix and number in <code class="filename">source/VERSION</code> and call
 <code class="filename">source/script/mkvesion.sh</code> to include the versioning of your package. There is also
 the possibility to set a function to create the vendor version. This makes it easier to distinguish
@@ -6,7 +6,7 @@ standard samba builds from custom-build samba builds (distributions often patch
 a good version would be:
 </p><pre class="programlisting">
 Version 2.999+3.0.alpha21-5 for Debian
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562040"></a>Modules</h2></div></div></div><p>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562008"></a>Modules</h2></div></div></div><p>
 Samba3 has support for building parts of samba as plugins. This makes it possible to, for example,
 put ldap or mysql support in a separate package, thus making it possible to have a normal samba package not
 depending on ldap or mysql. To build as much parts of samba as a plugin, run:
diff --git a/docs/htmldocs/Samba3-Developers-Guide/architecture.html b/docs/htmldocs/Samba3-Developers-Guide/architecture.html
index 0b75b203d1..94ffad66ed 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/architecture.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/architecture.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Samba Architecture</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="pt02.html" title="Part�II.�Samba Basics"><link rel="next" href="debug.html" title="Chapter�4.�The samba DEBUG system"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Samba Architecture</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt02.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="debug.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="architecture"></a>Chapter�3.�Samba Architecture</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3></div></div><div><p class="pubdate"> November 1997</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="architecture.html#id2556684">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556727">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556759">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556820">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556865">nbmd Design</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556684"></a>Introduction</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Samba Architecture</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="pt02.html" title="Part�II.�Samba Basics"><link rel="next" href="debug.html" title="Chapter�4.�The samba DEBUG system"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Samba Architecture</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt02.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="debug.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="architecture"></a>Chapter�3.�Samba Architecture</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3></div></div><div><p class="pubdate"> November 1997</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="architecture.html#id2556692">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556735">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556767">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556828">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556873">nbmd Design</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556692"></a>Introduction</h2></div></div></div><p>
 This document gives a general overview of how Samba works
 internally. The Samba Team has tried to come up with a model which is
 the best possible compromise between elegance, portability, security
@@ -9,7 +9,7 @@ It also tries to answer some of the frequently asked questions such as:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	Is Samba secure when running on Unix? The xyz platform?
 	What about the root priveliges issue?
-</p></li><li><p>Pros and cons of multithreading in various parts of Samba</p></li><li><p>Why not have a separate process for name resolution, WINS, and browsing?</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556727"></a>Multithreading and Samba</h2></div></div></div><p>
+</p></li><li><p>Pros and cons of multithreading in various parts of Samba</p></li><li><p>Why not have a separate process for name resolution, WINS, and browsing?</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556735"></a>Multithreading and Samba</h2></div></div></div><p>
 People sometimes tout threads as a uniformly good thing. They are very
 nice in their place but are quite inappropriate for smbd. nmbd is
 another matter, and multi-threading it would be very nice. 
@@ -26,7 +26,7 @@ smbd multi-threaded.  Multi-threading would actually make Samba much
 slower, less scalable, less portable and much less robust. The fact
 that we use a separate process for each connection is one of Samba's
 biggest advantages.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556759"></a>Threading smbd</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556767"></a>Threading smbd</h2></div></div></div><p>
 A few problems that would arise from a threaded smbd are:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	It's not only to create threads instead of processes, but you
@@ -51,7 +51,7 @@ A few problems that would arise from a threaded smbd are:
 </p></li><li><p>
 	we couldn't use the system locking calls as the locking context of
 	fcntl() is a process, not a thread.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556820"></a>Threading nmbd</h2></div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556828"></a>Threading nmbd</h2></div></div></div><p>
 This would be ideal, but gets sunk by portability requirements.
 </p><p>
 Andrew tried to write a test threads library for nmbd that used only
@@ -78,7 +78,7 @@ packet that arrives. Having a pool of processes is possible but is
 nasty to program cleanly due to the enormous amount of shared data (in
 complex structures) between the processes. We can't rely on each
 platform having a shared memory system.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556865"></a>nbmd Design</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556873"></a>nbmd Design</h2></div></div></div><p>
 Originally Andrew used recursion to simulate a multi-threaded
 environment, which use the stack enormously and made for really
 confusing debugging sessions. Luke Leighton rewrote it to use a
diff --git a/docs/htmldocs/Samba3-Developers-Guide/debug.html b/docs/htmldocs/Samba3-Developers-Guide/debug.html
index a9c518e142..d00949d458 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/debug.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/debug.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�The samba DEBUG system</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="architecture.html" title="Chapter�3.�Samba Architecture"><link rel="next" href="internals.html" title="Chapter�5.�Samba Internals"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�The samba DEBUG system</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="architecture.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="internals.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="debug"></a>Chapter�4.�The samba DEBUG system</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">July 1998</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="debug.html#id2556921">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557030">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557136">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557172">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557262">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557268">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557284">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557303">format_debug_text()</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556921"></a>New Output Syntax</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�The samba DEBUG system</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="architecture.html" title="Chapter�3.�Samba Architecture"><link rel="next" href="internals.html" title="Chapter�5.�Samba Internals"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�The samba DEBUG system</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="architecture.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="internals.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="debug"></a>Chapter�4.�The samba DEBUG system</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">July 1998</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="debug.html#id2556929">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557038">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557144">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557180">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557271">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557276">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557292">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557311">format_debug_text()</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556929"></a>New Output Syntax</h2></div></div></div><p>
    The syntax of a debugging log file is represented as:
 </p><pre class="programlisting">
   &gt;debugfile&lt; :== { &gt;debugmsg&lt; }
@@ -51,7 +51,7 @@ by a newline.
 Note that in the above example the function names are not listed on
 the header line. That's because the example above was generated on an
 SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557030"></a>The DEBUG() Macro</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557038"></a>The DEBUG() Macro</h2></div></div></div><p>
 Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters.
 The first is the message level, the second is the body of a function
 call to the Debug1() function.
@@ -102,7 +102,7 @@ would look like this:
     [1998/07/30 16:00:51, 0] file.c:function(261)
       .
 </pre><p>Which isn't much use. The format buffer kludge fixes this problem.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557136"></a>The DEBUGADD() Macro</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557144"></a>The DEBUGADD() Macro</h2></div></div></div><p>
 In addition to the kludgey solution to the broken line problem
 described above, there is a clean solution. The DEBUGADD() macro never
 generates a header. It will append new text to the current debug
@@ -116,7 +116,7 @@ DEBUGADD() macro is the same as that of the DEBUG() macro.
       This is the first line.
       This is the second line.
       This is the third line.
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557172"></a>The DEBUGLVL() Macro</h2></div></div></div><p>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557180"></a>The DEBUGLVL() Macro</h2></div></div></div><p>
 One of the problems with the DEBUG() macro was that DEBUG() lines
 tended to get a bit long. Consider this example from
 nmbd_sendannounce.c:
@@ -151,7 +151,7 @@ within the DEBUGLVL() block.
 </p></li><li><p>
 Processing that is only relevant to debug output can be contained
 within the DEBUGLVL() block.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557262"></a>New Functions</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557268"></a>dbgtext()</h3></div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557271"></a>New Functions</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557276"></a>dbgtext()</h3></div></div></div><p>
 This function prints debug message text to the debug file (and
 possibly to syslog) via the format buffer. The function uses a
 variable argument list just like printf() or Debug1(). The
@@ -160,7 +160,7 @@ and then passed to format_debug_text().
 
 If you use DEBUGLVL() you will probably print the body of the
 message using dbgtext(). 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557284"></a>dbghdr()</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557292"></a>dbghdr()</h3></div></div></div><p>
 This is the function that writes a debug message header.
 Headers are not processed via the format buffer. Also note that
 if the format buffer is not empty, a call to dbghdr() will not
@@ -168,7 +168,7 @@ produce any output. See the comments in dbghdr() for more info.
 </p><p>
 It is not likely that this function will be called directly. It
 is used by DEBUG() and DEBUGADD().
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557303"></a>format_debug_text()</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557311"></a>format_debug_text()</h3></div></div></div><p>
 This is a static function in debug.c. It stores the output text
 for the body of the message in a buffer until it encounters a
 newline. When the newline character is found, the buffer is
diff --git a/docs/htmldocs/Samba3-Developers-Guide/devprinting.html b/docs/htmldocs/Samba3-Developers-Guide/devprinting.html
index 71771b7209..b19da0e6d7 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/devprinting.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/devprinting.html
@@ -1,16 +1,16 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�Samba Printing Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt04.html" title="Part�IV.�Debugging and tracing"><link rel="prev" href="tracing.html" title="Chapter�14.�Tracing samba system calls"><link rel="next" href="pt05.html" title="Part�V.�Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�Samba Printing Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tracing.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Debugging and tracing</th><td width="20%" align="right">�<a accesskey="n" href="pt05.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="devprinting"></a>Chapter�15.�Samba Printing Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="devprinting.html#id2561412">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561425">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�Samba Printing Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt04.html" title="Part�IV.�Debugging and tracing"><link rel="prev" href="tracing.html" title="Chapter�14.�Tracing samba system calls"><link rel="next" href="pt05.html" title="Part�V.�Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�Samba Printing Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tracing.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Debugging and tracing</th><td width="20%" align="right">�<a accesskey="n" href="pt05.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="devprinting"></a>Chapter�15.�Samba Printing Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="devprinting.html#id2561382">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561395">
 Printing Interface to Various Back ends
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561501">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561471">
 Print Queue TDB's
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561684">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561645">
 ChangeID and Client Caching of Printer Information
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561694">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561655">
 Windows NT/2K Printer Change Notify
-</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561412"></a>Abstract</h2></div></div></div><p>
+</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561382"></a>Abstract</h2></div></div></div><p>
 The purpose of this document is to provide some insight into
 Samba's printing functionality and also to describe the semantics
 of certain features of Windows client printing.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561425"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561395"></a>
 Printing Interface to Various Back ends
 </h2></div></div></div><p>
 Samba uses a table of function pointers to seven functions.  The
@@ -21,7 +21,7 @@ Currently there are only two printing back end implementations
 defined.
 </p><div class="itemizedlist"><ul type="disc"><li><p>a generic set of functions for working with standard UNIX
 	printing subsystems</p></li><li><p>a set of CUPS specific functions (this is only enabled if
-	the CUPS libraries were located at compile time).</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561501"></a>
+	the CUPS libraries were located at compile time).</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561471"></a>
 Print Queue TDB's
 </h2></div></div></div><p>
 Samba provides periodic caching of the output from the "lpq command"
@@ -110,11 +110,11 @@ and the job has the printer's device mode associated with it by default.
 Only non-default Device Mode are stored with print jobs in the print
 queue TDB.  Otherwise, the Device Mode is obtained from the printer
 object when the client issues a GetJob(level == 2) request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561684"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561645"></a>
 ChangeID and Client Caching of Printer Information
 </h2></div></div></div><p>
 [To be filled in later]
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561694"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561655"></a>
 Windows NT/2K Printer Change Notify
 </h2></div></div></div><p>
 When working with Windows NT+ clients, it is possible for a
diff --git a/docs/htmldocs/Samba3-Developers-Guide/index.html b/docs/htmldocs/Samba3-Developers-Guide/index.html
index 0fc97475bb..9f11b87081 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/index.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/index.html
@@ -11,15 +11,13 @@ can be found at <a class="ulink" href="http://devel.samba.org/" target="_top">ht
 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 class="ulink" href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a>
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3>
-	This document is incomplete and unmaintained. It is merely a 
-	collection of development-related notes.
-</div></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">Attribution</a></span></dt><dt><span class="part"><a href="pt01.html">I. The protocol</a></span></dt><dd><dl><dt><span class="chapter"><a href="unix-smb.html">1. NetBIOS in a Unix World</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-smb.html#id2499107">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499128">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499459">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499491">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498824">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498876">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498908">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498929">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2549963">Protocol Complexity</a></span></dt></dl></dd><dt><span class="chapter"><a href="ntdomain.html">2. NT Domain RPC's</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntdomain.html#id2550082">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550247">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550274">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550305">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550310">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550373">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550536">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552805">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552815">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552899">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553572">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553608">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553746">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553874">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553970">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554052">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554122">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554205">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554256">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554417">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554589">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554715">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554824">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554939">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555030">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555110">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555181">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555195">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555396">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555646">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555680">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555848">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555937">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555943">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556069">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556148">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556190">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556222">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556460">Well-known RIDS</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="pt02.html">II. Samba Basics</a></span></dt><dd><dl><dt><span class="chapter"><a href="architecture.html">3. Samba Architecture</a></span></dt><dd><dl><dt><span class="sect1"><a href="architecture.html#id2556684">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556727">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556759">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556820">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556865">nbmd Design</a></span></dt></dl></dd><dt><span class="chapter"><a href="debug.html">4. The samba DEBUG system</a></span></dt><dd><dl><dt><span class="sect1"><a href="debug.html#id2556921">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557030">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557136">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557172">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557262">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557268">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557284">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557303">format_debug_text()</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="internals.html">5. Samba Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="internals.html#id2557354">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557376">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557505">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557515">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557526">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557537">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557548">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557560">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557572">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557583">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557594">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557606">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557617">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557629">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557640">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557652">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557663">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557675">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557687">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557715">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557840">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557910">Code character table</a></span></dt></dl></dd><dt><span class="chapter"><a href="CodingSuggestions.html">6. Coding Suggestions</a></span></dt><dt><span class="chapter"><a href="contributing.html">7. Contributing code</a></span></dt><dt><span class="chapter"><a href="modules.html">8. Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="modules.html#id2558562">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558600">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558626">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558658">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558682">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558731">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="pt03.html">III. Samba Subsystems</a></span></dt><dd><dl><dt><span class="chapter"><a href="rpc-plugin.html">9. RPC Pluggable Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558890">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558905">General Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="vfs.html">10. VFS Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="vfs.html#id2559067">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559108">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559434">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559507">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559514">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559659">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559860">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559866">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560270">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560275">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560295">Implement OPAQUE functions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="parsing.html">11. The smb.conf file</a></span></dt><dd><dl><dt><span class="sect1"><a href="parsing.html#id2560352">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560424">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560469">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560520">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560597">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560655">About params.c</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wins.html">12. Samba WINS Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="wins.html#id2560693">WINS Failover</a></span></dt></dl></dd><dt><span class="chapter"><a href="pwencrypt.html">13. LanMan and NT Password Encryption</a></span></dt><dd><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560822">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560842">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560926">The smbpasswd file</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt04.html">IV. Debugging and tracing</a></span></dt><dd><dl><dt><span class="chapter"><a href="tracing.html">14. Tracing samba system calls</a></span></dt><dt><span class="chapter"><a href="devprinting.html">15. Samba Printing Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="devprinting.html#id2561412">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561425">
+</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>This document is incomplete and unmaintained. It is merely a 
+	collection of development-related notes.</p></div></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">Attribution</a></span></dt><dt><span class="part"><a href="pt01.html">I. The protocol</a></span></dt><dd><dl><dt><span class="chapter"><a href="unix-smb.html">1. NetBIOS in a Unix World</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-smb.html#id2499122">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499143">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499475">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499506">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498843">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498891">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498923">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498944">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498960">Protocol Complexity</a></span></dt></dl></dd><dt><span class="chapter"><a href="ntdomain.html">2. NT Domain RPC's</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntdomain.html#id2550090">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550255">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550282">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550313">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550318">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550381">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550543">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552813">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552823">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552907">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553580">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553616">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553755">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553883">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553978">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554060">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554130">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554213">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554264">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554425">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554597">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554723">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554832">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554947">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555038">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555118">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555189">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555203">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555404">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555654">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555688">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555856">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555945">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555952">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556077">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556156">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556198">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556230">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556468">Well-known RIDS</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="pt02.html">II. Samba Basics</a></span></dt><dd><dl><dt><span class="chapter"><a href="architecture.html">3. Samba Architecture</a></span></dt><dd><dl><dt><span class="sect1"><a href="architecture.html#id2556692">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556735">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556767">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556828">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556873">nbmd Design</a></span></dt></dl></dd><dt><span class="chapter"><a href="debug.html">4. The samba DEBUG system</a></span></dt><dd><dl><dt><span class="sect1"><a href="debug.html#id2556929">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557038">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557144">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557180">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557271">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557276">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557292">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557311">format_debug_text()</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="internals.html">5. Samba Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="internals.html#id2557363">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557384">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557513">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557523">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557534">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557545">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557556">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557568">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557580">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557591">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557603">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557614">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557625">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557637">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557648">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557660">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557671">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557683">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557696">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557723">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557848">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557918">Code character table</a></span></dt></dl></dd><dt><span class="chapter"><a href="CodingSuggestions.html">6. Coding Suggestions</a></span></dt><dt><span class="chapter"><a href="contributing.html">7. Contributing code</a></span></dt><dt><span class="chapter"><a href="modules.html">8. Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="modules.html#id2558570">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558608">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558634">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558666">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558690">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558739">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="pt03.html">III. Samba Subsystems</a></span></dt><dd><dl><dt><span class="chapter"><a href="rpc-plugin.html">9. RPC Pluggable Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558898">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558913">General Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="vfs.html">10. VFS Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="vfs.html#id2559076">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559117">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559428">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559489">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559495">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559640">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559841">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559847">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560251">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560257">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560276">Implement OPAQUE functions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="parsing.html">11. The smb.conf file</a></span></dt><dd><dl><dt><span class="sect1"><a href="parsing.html#id2560333">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560405">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560450">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560502">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560579">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560636">About params.c</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wins.html">12. Samba WINS Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="wins.html#id2560674">WINS Failover</a></span></dt></dl></dd><dt><span class="chapter"><a href="pwencrypt.html">13. LanMan and NT Password Encryption</a></span></dt><dd><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560792">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560813">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560896">The smbpasswd file</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt04.html">IV. Debugging and tracing</a></span></dt><dd><dl><dt><span class="chapter"><a href="tracing.html">14. Tracing samba system calls</a></span></dt><dt><span class="chapter"><a href="devprinting.html">15. Samba Printing Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="devprinting.html#id2561382">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561395">
 Printing Interface to Various Back ends
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561501">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561471">
 Print Queue TDB's
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561684">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561645">
 ChangeID and Client Caching of Printer Information
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561694">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561655">
 Windows NT/2K Printer Change Notify
-</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt05.html">V. Appendices</a></span></dt><dd><dl><dt><span class="chapter"><a href="Packaging.html">16. Notes to packagers</a></span></dt><dd><dl><dt><span class="sect1"><a href="Packaging.html#id2562007">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562040">Modules</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�Attribution</td></tr></table></div></body></html>
+</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt05.html">V. Appendices</a></span></dt><dd><dl><dt><span class="chapter"><a href="Packaging.html">16. Notes to packagers</a></span></dt><dd><dl><dt><span class="sect1"><a href="Packaging.html#id2561975">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562008">Modules</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�Attribution</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/internals.html b/docs/htmldocs/Samba3-Developers-Guide/internals.html
index 400a94cacc..357a932e70 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/internals.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/internals.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Samba Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="debug.html" title="Chapter�4.�The samba DEBUG system"><link rel="next" href="CodingSuggestions.html" title="Chapter�6.�Coding Suggestions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Samba Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="debug.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="CodingSuggestions.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter�5.�Samba Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Chappell</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:David.Chappell@mail.trincoll.edu">David.Chappell@mail.trincoll.edu</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">8 May 1996</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="internals.html#id2557354">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557376">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557505">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557515">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557526">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557537">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557548">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557560">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557572">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557583">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557594">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557606">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557617">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557629">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557640">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557652">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557663">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557675">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557687">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557715">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557840">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557910">Code character table</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557354"></a>Character Handling</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Samba Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="debug.html" title="Chapter�4.�The samba DEBUG system"><link rel="next" href="CodingSuggestions.html" title="Chapter�6.�Coding Suggestions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Samba Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="debug.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="CodingSuggestions.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter�5.�Samba Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Chappell</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:David.Chappell@mail.trincoll.edu">David.Chappell@mail.trincoll.edu</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">8 May 1996</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="internals.html#id2557363">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557384">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557513">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557523">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557534">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557545">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557556">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557568">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557580">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557591">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557603">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557614">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557625">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557637">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557648">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557660">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557671">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557683">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557696">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557723">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557848">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557918">Code character table</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557363"></a>Character Handling</h2></div></div></div><p>
 This section describes character set handling in Samba, as implemented in
 Samba 3.0 and above
 </p><p>
@@ -8,7 +8,7 @@ strings to/from DOS codepages. The problem is that there was no way of
 telling if a particular char* is in dos codepage or unix
 codepage. This led to a nightmare of code that tried to cope with
 particular cases without handlingt the general case.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557376"></a>The new functions</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557384"></a>The new functions</h2></div></div></div><p>
 The new system works like this:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	all char* strings inside Samba are "unix" strings. These are
@@ -70,28 +70,28 @@ The new system works like this:
 	parameters is gone.
 </p></li><li><p>
 	all vfs functions take unix strings. Don't convert when passing to them
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557505"></a>Macros in byteorder.h</h2></div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557513"></a>Macros in byteorder.h</h2></div></div></div><p>
 This section describes the macros defined in byteorder.h.  These macros 
 are used extensively in the Samba code.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557515"></a>CVAL(buf,pos)</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557523"></a>CVAL(buf,pos)</h3></div></div></div><p>
 returns the byte at offset pos within buffer buf as an unsigned character.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557526"></a>PVAL(buf,pos)</h3></div></div></div><p>returns the value of CVAL(buf,pos) cast to type unsigned integer.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557537"></a>SCVAL(buf,pos,val)</h3></div></div></div><p>sets the byte at offset pos within buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557548"></a>SVAL(buf,pos)</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557534"></a>PVAL(buf,pos)</h3></div></div></div><p>returns the value of CVAL(buf,pos) cast to type unsigned integer.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557545"></a>SCVAL(buf,pos,val)</h3></div></div></div><p>sets the byte at offset pos within buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557556"></a>SVAL(buf,pos)</h3></div></div></div><p>
 	returns the value of the unsigned short (16 bit) little-endian integer at 
 	offset pos within buffer buf.  An integer of this type is sometimes
 	refered to as "USHORT".
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557560"></a>IVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned 32 bit little-endian integer at offset 
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557572"></a>SVALS(buf,pos)</h3></div></div></div><p>returns the value of the signed short (16 bit) little-endian integer at 
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557583"></a>IVALS(buf,pos)</h3></div></div></div><p>returns the value of the signed 32 bit little-endian integer at offset pos
-within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557594"></a>SSVAL(buf,pos,val)</h3></div></div></div><p>sets the unsigned short (16 bit) little-endian integer at offset pos within 
-buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557606"></a>SIVAL(buf,pos,val)</h3></div></div></div><p>sets the unsigned 32 bit little-endian integer at offset pos within buffer 
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557617"></a>SSVALS(buf,pos,val)</h3></div></div></div><p>sets the short (16 bit) signed little-endian integer at offset pos within 
-buffer buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557629"></a>SIVALS(buf,pos,val)</h3></div></div></div><p>sets the signed 32 bit little-endian integer at offset pos withing buffer
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557640"></a>RSVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned short (16 bit) big-endian integer at 
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557652"></a>RIVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned 32 bit big-endian integer at offset 
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557663"></a>RSSVAL(buf,pos,val)</h3></div></div></div><p>sets the value of the unsigned short (16 bit) big-endian integer at 
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557568"></a>IVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned 32 bit little-endian integer at offset 
+pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557580"></a>SVALS(buf,pos)</h3></div></div></div><p>returns the value of the signed short (16 bit) little-endian integer at 
+offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557591"></a>IVALS(buf,pos)</h3></div></div></div><p>returns the value of the signed 32 bit little-endian integer at offset pos
+within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557603"></a>SSVAL(buf,pos,val)</h3></div></div></div><p>sets the unsigned short (16 bit) little-endian integer at offset pos within 
+buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557614"></a>SIVAL(buf,pos,val)</h3></div></div></div><p>sets the unsigned 32 bit little-endian integer at offset pos within buffer 
+buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557625"></a>SSVALS(buf,pos,val)</h3></div></div></div><p>sets the short (16 bit) signed little-endian integer at offset pos within 
+buffer buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557637"></a>SIVALS(buf,pos,val)</h3></div></div></div><p>sets the signed 32 bit little-endian integer at offset pos withing buffer
+buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557648"></a>RSVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned short (16 bit) big-endian integer at 
+offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557660"></a>RIVAL(buf,pos)</h3></div></div></div><p>returns the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557671"></a>RSSVAL(buf,pos,val)</h3></div></div></div><p>sets the value of the unsigned short (16 bit) big-endian integer at 
 offset pos within buffer buf to value val.
-refered to as "USHORT".</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557675"></a>RSIVAL(buf,pos,val)</h3></div></div></div><p>sets the value of the unsigned 32 bit big-endian integer at offset 
-pos within buffer buf to value val.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557687"></a>LAN Manager Samba API</h2></div></div></div><p>
+refered to as "USHORT".</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557683"></a>RSIVAL(buf,pos,val)</h3></div></div></div><p>sets the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf to value val.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557696"></a>LAN Manager Samba API</h2></div></div></div><p>
 This section describes the functions need to make a LAN Manager RPC call.
 This information had been obtained by examining the Samba code and the LAN
 Manager 2.0 API documentation.  It should not be considered entirely
@@ -104,7 +104,7 @@ call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,
 </p><p>
 This function is defined in client.c.  It uses an SMB transaction to call a
 remote api.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557715"></a>Parameters</h3></div></div></div><p>The parameters are as follows:</p><div class="orderedlist"><ol type="1"><li><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557723"></a>Parameters</h3></div></div></div><p>The parameters are as follows:</p><div class="orderedlist"><ol type="1"><li><p>
 	prcnt: the number of bytes of parameters begin sent.
 </p></li><li><p>
 	drcnt:   the number of bytes of data begin sent.
@@ -149,7 +149,7 @@ substructures apply, this string is of zero length.
 </p></li></ol></div><p>
 The code in client.c always calls call_api() with no data.  It is unclear
 when a non-zero length data buffer would be sent.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557840"></a>Return value</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557848"></a>Return value</h3></div></div></div><p>
 The returned parameters (pointed to by rparam), in their order of appearance
 are:</p><div class="orderedlist"><ol type="1"><li><p>
 An unsigned 16 bit integer which contains the API function's return code. 
@@ -180,7 +180,7 @@ fix_char_ptr() in client.c can be used for this purpose.
 The third parameter (which may be read as "SVAL(rparam,4)") has something to
 do with indicating the amount of data returned or possibly the amount of
 data which can be returned if enough buffer space is allowed.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557910"></a>Code character table</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2557918"></a>Code character table</h2></div></div></div><p>
 Certain data structures are described by means of ASCIIz strings containing
 code characters.  These are the code characters:
 </p><div class="orderedlist"><ol type="1"><li><p>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/modules.html b/docs/htmldocs/Samba3-Developers-Guide/modules.html
index 612d54cbbb..ab49c0d494 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/modules.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/modules.html
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="contributing.html" title="Chapter�7.�Contributing code"><link rel="next" href="pt03.html" title="Part�III.�Samba Subsystems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="contributing.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="pt03.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="modules"></a>Chapter�8.�Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="orgname">Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 19 March 2003 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="modules.html#id2558562">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558600">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558626">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558658">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558682">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558731">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558562"></a>Advantages</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt02.html" title="Part�II.�Samba Basics"><link rel="prev" href="contributing.html" title="Chapter�7.�Contributing code"><link rel="next" href="pt03.html" title="Part�III.�Samba Subsystems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="contributing.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Samba Basics</th><td width="20%" align="right">�<a accesskey="n" href="pt03.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="modules"></a>Chapter�8.�Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="orgname">Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 19 March 2003 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="modules.html#id2558570">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558608">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558634">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558666">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558690">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558739">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558570"></a>Advantages</h2></div></div></div><p>
 The new modules system has the following advantages:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>Transparent loading of static and shared modules (no need 
-for a subsystem to know about modules)</td></tr><tr><td>Simple selection between shared and static modules at configure time</td></tr><tr><td>"preload modules" option for increasing performance for stable modules</td></tr><tr><td>No nasty #define stuff anymore</td></tr><tr><td>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558600"></a>Loading modules</h2></div></div></div><p>
+for a subsystem to know about modules)</td></tr><tr><td>Simple selection between shared and static modules at configure time</td></tr><tr><td>"preload modules" option for increasing performance for stable modules</td></tr><tr><td>No nasty #define stuff anymore</td></tr><tr><td>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558608"></a>Loading modules</h2></div></div></div><p>
 Some subsystems in samba use different backends. These backends can be 
 either statically linked in to samba or available as a plugin. A subsystem 
 should have a function that allows a module to register itself. For example, 
@@ -11,7 +11,7 @@ NTSTATUS smb_register_passdb(int version, const char *name, pdb_init_function in
 </pre><p>
 This function will be called by the initialisation function of the module to 
 register itself. 
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558626"></a>Static modules</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558634"></a>Static modules</h3></div></div></div><p>
 The modules system compiles a list of initialisation functions for the 
 static modules of each subsystem. This is a define. For example, 
 it is here currently (from <code class="filename">include/config.h</code>): 
@@ -21,7 +21,7 @@ it is here currently (from <code class="filename">include/config.h</code>):
 </pre><p>
 These functions should be called before the subsystem is used. That 
 should be done when the subsystem is initialised or first used. 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558658"></a>Shared modules</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558666"></a>Shared modules</h3></div></div></div><p>
 If a subsystem needs a certain backend, it should check if it has 
 already been registered. If the backend hasn't been registered already, 
 the subsystem should call smb_probe_module(char *subsystem, char *backend).
@@ -31,7 +31,7 @@ is a slash, smb_probe_module() tries to load the module from the
 absolute path specified in 'backend'.
 </p><p>After smb_probe_module() has been executed, the subsystem 
 should check again if the module has been registered. 
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558682"></a>Writing modules</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558690"></a>Writing modules</h2></div></div></div><p>
 Each module has an initialisation function. For modules that are 
 included with samba this name is '<em class="replaceable"><code>subsystem</code></em>_<em class="replaceable"><code>backend</code></em>_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()).
 The prototype for these functions is:
@@ -46,7 +46,7 @@ smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam);
 smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua);
 	return NT_STATUS_OK;
 }
-</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558731"></a>Static/Shared selection in configure.in</h3></div></div></div><p>
+</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558739"></a>Static/Shared selection in configure.in</h3></div></div></div><p>
 Some macros in configure.in generate the various defines and substs that 
 are necessary for the system to work correct. All modules that should 
 be built by default have to be added to the variable 'default_modules'. 
diff --git a/docs/htmldocs/Samba3-Developers-Guide/ntdomain.html b/docs/htmldocs/Samba3-Developers-Guide/ntdomain.html
index f6222d9451..3a845792f3 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/ntdomain.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/ntdomain.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�NT Domain RPC's</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt01.html" title="Part�I.�The protocol"><link rel="prev" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World"><link rel="next" href="pt02.html" title="Part�II.�Samba Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�NT Domain RPC's</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unix-smb.html">Prev</a>�</td><th width="60%" align="center">Part�I.�The protocol</th><td width="20%" align="right">�<a accesskey="n" href="pt02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntdomain"></a>Chapter�2.�NT Domain RPC's</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:lkcl@switchboard.net">lkcl@switchboard.net</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Ashton</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:paul@argo.demon.co.uk">paul@argo.demon.co.uk</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Duncan</span> <span class="surname">Stansfield</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:duncans@sco.com">duncans@sco.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">01 November 97(version 0.0.24)</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ntdomain.html#id2550082">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550247">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550274">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550305">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550310">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550373">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550536">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552805">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552815">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552899">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553572">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553608">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553746">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553874">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553970">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554052">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554122">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554205">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554256">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554417">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554589">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554715">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554824">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554939">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555030">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555110">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555181">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555195">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555396">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555646">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555680">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555848">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555937">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555943">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556069">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556148">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556190">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556222">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556460">Well-known RIDS</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550082"></a>Introduction</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�NT Domain RPC's</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt01.html" title="Part�I.�The protocol"><link rel="prev" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World"><link rel="next" href="pt02.html" title="Part�II.�Samba Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�NT Domain RPC's</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unix-smb.html">Prev</a>�</td><th width="60%" align="center">Part�I.�The protocol</th><td width="20%" align="right">�<a accesskey="n" href="pt02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntdomain"></a>Chapter�2.�NT Domain RPC's</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:lkcl@switchboard.net">lkcl@switchboard.net</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Ashton</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:paul@argo.demon.co.uk">paul@argo.demon.co.uk</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Duncan</span> <span class="surname">Stansfield</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:duncans@sco.com">duncans@sco.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">01 November 97(version 0.0.24)</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ntdomain.html#id2550090">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550255">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550282">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550313">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550318">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550381">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550543">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552813">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552823">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552907">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553580">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553616">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553755">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553883">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553978">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554060">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554130">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554213">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554264">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554425">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554597">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554723">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554832">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554947">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555038">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555118">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555189">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555203">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555404">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555654">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555688">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555856">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555945">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555952">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556077">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556156">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556198">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556230">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556468">Well-known RIDS</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550090"></a>Introduction</h2></div></div></div><p>
 This document contains information to provide an NT workstation with login
 services, without the need for an NT server. It is the sgml version of <a class="ulink" href="http://mailhost.cb1.com/~lkcl/cifsntdomain.txt" target="_top">http://mailhost.cb1.com/~lkcl/cifsntdomain.txt</a>, controlled by Luke.
 </p><p>
@@ -44,7 +44,7 @@ Failure to return this error code will make the workstation report
 that it is already a member of the domain.</p></li><li><p>the cryptographic side of the NetrServerPasswordSet command, 
 which would allow the workstation to change its password.  This password is
 used to generate the long-term session key.  [It is possible to reject this
-command, and keep the default workstation password].</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550247"></a>Sources</h3></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>cket Traces from Netmonitor (Service Pack 1 and above)</td></tr><tr><td>ul Ashton and Luke Leighton's other "NT Domain" doc.</td></tr><tr><td>FS documentation - cifs6.txt</td></tr><tr><td>FS documentation - cifsrap2.txt</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550274"></a>Credits</h3></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</td></tr><tr><td>Duncan Stansfield: low-level analysis of MSRPC Pipes.</td></tr><tr><td>Linus Nordberg: producing c-code from Paul's crypto spec.</td></tr><tr><td>Windows Sourcer development team</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550305"></a>Notes and Structures</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550310"></a>Notes</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p>
+command, and keep the default workstation password].</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550255"></a>Sources</h3></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>cket Traces from Netmonitor (Service Pack 1 and above)</td></tr><tr><td>ul Ashton and Luke Leighton's other "NT Domain" doc.</td></tr><tr><td>FS documentation - cifs6.txt</td></tr><tr><td>FS documentation - cifsrap2.txt</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550282"></a>Credits</h3></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</td></tr><tr><td>Duncan Stansfield: low-level analysis of MSRPC Pipes.</td></tr><tr><td>Linus Nordberg: producing c-code from Paul's crypto spec.</td></tr><tr><td>Windows Sourcer development team</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2550313"></a>Notes and Structures</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550318"></a>Notes</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p>
 In the SMB Transact pipes, some "Structures", described here, appear to be
 4-byte aligned with the SMB header, at their start.  Exactly which
 "Structures" need aligning is not precisely known or documented.
@@ -72,15 +72,15 @@ into or taken out of the SMB data stream.  if the count is non-zero, then
 the pointer is also non-zero.  immediately following the pointer is the
 count again, followed by an array of container sub-structures.  the count
 appears a third time after the last sub-structure.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550373"></a>Enumerations</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550378"></a>MSRPC Header type</h4></div></div></div><p>command number in the msrpc packet header</p><div class="variablelist"><dl><dt><span class="term">MSRPC_Request:</span></dt><dd><p>0x00</p></dd><dt><span class="term">MSRPC_Response:</span></dt><dd><p>0x02</p></dd><dt><span class="term">MSRPC_Bind:</span></dt><dd><p>0x0B</p></dd><dt><span class="term">MSRPC_BindAck:</span></dt><dd><p>0x0C</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550436"></a>MSRPC Packet info</h4></div></div></div><p>The meaning of these flags is undocumented</p><div class="variablelist"><dl><dt><span class="term">FirstFrag:</span></dt><dd><p>0x01 </p></dd><dt><span class="term">LastFrag:</span></dt><dd><p>0x02 </p></dd><dt><span class="term">NotaFrag:</span></dt><dd><p>0x04  </p></dd><dt><span class="term">RecRespond:</span></dt><dd><p>0x08  </p></dd><dt><span class="term">NoMultiplex:</span></dt><dd><p>0x10  </p></dd><dt><span class="term">NotForIdemp:</span></dt><dd><p>0x20  </p></dd><dt><span class="term">NotforBcast:</span></dt><dd><p>0x40  </p></dd><dt><span class="term">NoUuid:</span></dt><dd><p>0x80 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550536"></a>Structures</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550541"></a>VOID *</h4></div></div></div><p>sizeof VOID* is 32 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550550"></a>char</h4></div></div></div><p>sizeof char is 8 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550558"></a>UTIME</h4></div></div></div><p>UTIME is 32 bits, indicating time in seconds since 01jan1970.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550569"></a>NTTIME</h4></div></div></div><p>NTTIME is 64 bits.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550579"></a>DOM_SID (domain SID structure)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8</span></dt><dd><p>SID revision number</p></dd><dt><span class="term">UINT8</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8[6]</span></dt><dd><p>6 bytes for domain SID - Identifier Authority.</p></dd><dt><span class="term">UINT16[n_subauths]</span></dt><dd><p>domain SID sub-authorities</p></dd></dl></div><p><span class="emphasis"><em>Note: the domain SID is documented elsewhere.</em></span>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550650"></a>STR (string)</h4></div></div></div><p>STR (string) is a char[] : a null-terminated string of ascii characters.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550660"></a>UNIHDR (unicode string header) </h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550702"></a>UNIHDR2 (unicode string header plus buffer pointer)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNIHDR</span></dt><dd><p>unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550734"></a>UNISTR (unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550755"></a>NAME (length-indicated unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550788"></a>UNISTR2 (aligned unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>string of uncode characters</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550853"></a>OBJ_ATTR (object attributes)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0x18 - length (in bytes) including the length field.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - root directory (pointer)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - object name (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - attributes (undocumented)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - security descriptior (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - security quality of service</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550926"></a>POL_HND (LSA policy handle)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[20]</span></dt><dd><p>policy handle</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550946"></a>DOM_SID2 (domain SID structure, SIDS stored in unicode)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - SID type</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain SID unicode string header</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain SID unicode string</p></dd></dl></div><p><span class="emphasis"><em>Note:	there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length.  this will need to be resolved.</em></span></p><p><span class="emphasis"><em>Note:	the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551013"></a>DOM_RID (domain RID structure)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - well-known SID.  1 - user SID (see ShowACLs)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain RID </p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - domain index out of above reference domains</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551067"></a>LOG_INFO (server, account, client structure)</h4></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>account name unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>sec_chan - security channel type</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551144"></a>CLNT_SRV (server, client names structure)</h4></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551203"></a>CREDS (credentials + time stamp)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>credentials</p></dd><dt><span class="term">UTIME</span></dt><dd><p>time stamp</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551235"></a>CLNT_INFO2 (server, client structure, client credentials)</h4></div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks.  the presumed intention is to
-	maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_SRV</span></dt><dd><p>client and server names</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding, for 4-byte alignment with SMB header.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to client credentials.</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551299"></a>CLNT_INFO (server, account, client structure, client credentials)</h4></div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks.  the presumed intention is to maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>logon account info</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551341"></a>ID_INFO_1 (id info structure, auth level 1)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>ptr_id_info_1</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>domain name unicode header</p></dd><dt><span class="term">UINT32</span></dt><dd><p>param control</p></dd><dt><span class="term">UINT64</span></dt><dd><p>logon ID</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user name unicode header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>workgroup name unicode header</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 LM OWF Password</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 NT OWF Password</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>workstation name unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551470"></a>SAM_INFO (sam logon/logoff id info structure)</h4></div></div></div><p><span class="emphasis"><em>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_INFO2</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to return credentials.</p></dd><dt><span class="term">CRED</span></dt><dd><p>return credentials - ignored.</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon level</p></dd><dt><span class="term">UINT16</span></dt><dd><p>switch value</p></dd></dl></div><pre class="programlisting">
+</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550381"></a>Enumerations</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550386"></a>MSRPC Header type</h4></div></div></div><p>command number in the msrpc packet header</p><div class="variablelist"><dl><dt><span class="term">MSRPC_Request:</span></dt><dd><p>0x00</p></dd><dt><span class="term">MSRPC_Response:</span></dt><dd><p>0x02</p></dd><dt><span class="term">MSRPC_Bind:</span></dt><dd><p>0x0B</p></dd><dt><span class="term">MSRPC_BindAck:</span></dt><dd><p>0x0C</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550444"></a>MSRPC Packet info</h4></div></div></div><p>The meaning of these flags is undocumented</p><div class="variablelist"><dl><dt><span class="term">FirstFrag:</span></dt><dd><p>0x01 </p></dd><dt><span class="term">LastFrag:</span></dt><dd><p>0x02 </p></dd><dt><span class="term">NotaFrag:</span></dt><dd><p>0x04  </p></dd><dt><span class="term">RecRespond:</span></dt><dd><p>0x08  </p></dd><dt><span class="term">NoMultiplex:</span></dt><dd><p>0x10  </p></dd><dt><span class="term">NotForIdemp:</span></dt><dd><p>0x20  </p></dd><dt><span class="term">NotforBcast:</span></dt><dd><p>0x40  </p></dd><dt><span class="term">NoUuid:</span></dt><dd><p>0x80 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550543"></a>Structures</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550548"></a>VOID *</h4></div></div></div><p>sizeof VOID* is 32 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550557"></a>char</h4></div></div></div><p>sizeof char is 8 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550566"></a>UTIME</h4></div></div></div><p>UTIME is 32 bits, indicating time in seconds since 01jan1970.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550576"></a>NTTIME</h4></div></div></div><p>NTTIME is 64 bits.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550586"></a>DOM_SID (domain SID structure)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8</span></dt><dd><p>SID revision number</p></dd><dt><span class="term">UINT8</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8[6]</span></dt><dd><p>6 bytes for domain SID - Identifier Authority.</p></dd><dt><span class="term">UINT16[n_subauths]</span></dt><dd><p>domain SID sub-authorities</p></dd></dl></div><p><span class="emphasis"><em>Note: the domain SID is documented elsewhere.</em></span>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550658"></a>STR (string)</h4></div></div></div><p>STR (string) is a char[] : a null-terminated string of ascii characters.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550669"></a>UNIHDR (unicode string header) </h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550710"></a>UNIHDR2 (unicode string header plus buffer pointer)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNIHDR</span></dt><dd><p>unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550742"></a>UNISTR (unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550763"></a>NAME (length-indicated unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550796"></a>UNISTR2 (aligned unicode string)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>string of uncode characters</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550861"></a>OBJ_ATTR (object attributes)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0x18 - length (in bytes) including the length field.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - root directory (pointer)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - object name (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - attributes (undocumented)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - security descriptior (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - security quality of service</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550934"></a>POL_HND (LSA policy handle)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[20]</span></dt><dd><p>policy handle</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2550954"></a>DOM_SID2 (domain SID structure, SIDS stored in unicode)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - SID type</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain SID unicode string header</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain SID unicode string</p></dd></dl></div><p><span class="emphasis"><em>Note:	there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length.  this will need to be resolved.</em></span></p><p><span class="emphasis"><em>Note:	the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551021"></a>DOM_RID (domain RID structure)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - well-known SID.  1 - user SID (see ShowACLs)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain RID </p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - domain index out of above reference domains</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551075"></a>LOG_INFO (server, account, client structure)</h4></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>account name unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>sec_chan - security channel type</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551152"></a>CLNT_SRV (server, client names structure)</h4></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551212"></a>CREDS (credentials + time stamp)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>credentials</p></dd><dt><span class="term">UTIME</span></dt><dd><p>time stamp</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551243"></a>CLNT_INFO2 (server, client structure, client credentials)</h4></div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks.  the presumed intention is to
+	maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_SRV</span></dt><dd><p>client and server names</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding, for 4-byte alignment with SMB header.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to client credentials.</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551308"></a>CLNT_INFO (server, account, client structure, client credentials)</h4></div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks.  the presumed intention is to maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>logon account info</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551349"></a>ID_INFO_1 (id info structure, auth level 1)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>ptr_id_info_1</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>domain name unicode header</p></dd><dt><span class="term">UINT32</span></dt><dd><p>param control</p></dd><dt><span class="term">UINT64</span></dt><dd><p>logon ID</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user name unicode header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>workgroup name unicode header</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 LM OWF Password</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 NT OWF Password</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>workstation name unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551478"></a>SAM_INFO (sam logon/logoff id info structure)</h4></div></div></div><p><span class="emphasis"><em>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_INFO2</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to return credentials.</p></dd><dt><span class="term">CRED</span></dt><dd><p>return credentials - ignored.</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon level</p></dd><dt><span class="term">UINT16</span></dt><dd><p>switch value</p></dd></dl></div><pre class="programlisting">
         switch (switch_value)
         case 1:
         {
             ID_INFO_1     id_info_1;
         }
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551551"></a>GID (group id info)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>group id</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user attributes (only used by NT 3.1 and 3.51)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551580"></a>DOM_REF (domain reference info)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num referenced domains?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>32 - max number of entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - num referenced domains?</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain name unicode string header</p></dd><dt><span class="term">UNIHDR2[num_ref_doms-1]</span></dt><dd><p>referenced domain unicode string headers</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">DOM_SID[num_ref_doms]</span></dt><dd><p>referenced domain SIDs</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551690"></a>DOM_INFO (domain info, levels 3 and 5 are the same))</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>??? padding to get 4-byte alignment with start of SMB header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name string buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID string buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name (unicode string)</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551778"></a>USER_INFO (user logon info)</h4></div></div></div><p><span class="emphasis"><em>Note: it would be nice to know what the 16 byte user session key is for.</em></span></p><div class="variablelist"><dl><dt><span class="term">NTTIME</span></dt><dd><p>logon time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>logoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>kickoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password last set time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password can change time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password must change time</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>username unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user's full name unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon script unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>profile path unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory drive unicode string header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon count</p></dd><dt><span class="term">UINT16</span></dt><dd><p>bad password count</p></dd><dt><span class="term">UINT32</span></dt><dd><p>User ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>Group ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer to groups.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user flags</p></dd><dt><span class="term">char[16]</span></dt><dd><p>user session key</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon server unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon domain unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented logon domain id pointer</p></dd><dt><span class="term">char[40]</span></dt><dd><p>40 undocumented padding bytes.  future expansion?</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - num_other_sids?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>NULL - undocumented pointer to other domain SIDs.</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>username unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user's full name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon script unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>profile path unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory drive unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">GID[num_groups]</span></dt><dd><p>group info</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon domain unicode string</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd><dt><span class="term">DOM_SID[num_sids]</span></dt><dd><p>other domain SIDs?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552210"></a>SH_INFO_1_PTR (pointers to level 1 share info strings)</h4></div></div></div><p><span class="emphasis"><em>Note:	see cifsrap2.txt section5, page 10.</em></span></p><table class="simplelist" border="0" summary="Simple list"><tr><td>0 for shi1_type indicates a  Disk.</td></tr><tr><td>1 for shi1_type indicates a  Print Queue.</td></tr><tr><td>2 for shi1_type indicates a  Device.</td></tr><tr><td>3 for shi1_type indicates an IPC pipe.</td></tr><tr><td>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</td></tr></table><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>shi1_netname - pointer to net name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>shi1_type    - type of share.  0 - undocumented.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>shi1_remark  - pointer to comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552285"></a>SH_INFO_1_STR (level 1 share info strings)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_netname - unicode string of net name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_remark  - unicode string of comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552318"></a>SHARE_INFO_1_CTR</h4></div></div></div><p>share container with 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - Buffer</p></dd></dl></div><p>share container with &gt; 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>non-zero - Buffer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">SH_INFO_1_PTR[EntriesRead]</span></dt><dd><p>share entry pointers</p></dd><dt><span class="term">SH_INFO_1_STR[EntriesRead]</span></dt><dd><p>share entry strings</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - padding</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552447"></a>SERVER_INFO_101</h4></div></div></div><p><span class="emphasis"><em>Note:	see cifs6.txt section 6.4 - the fields described therein will be of assistance here.  for example, the type listed below is the 	same as fServerType, which is described in 6.4.1. </em></span></p><div class="variablelist"><dl><dt><span class="term">SV_TYPE_WORKSTATION</span></dt><dd><p>0x00000001  All workstations</p></dd><dt><span class="term">SV_TYPE_SERVER</span></dt><dd><p>0x00000002  All servers</p></dd><dt><span class="term">SV_TYPE_SQLSERVER</span></dt><dd><p>0x00000004  Any server running with SQL server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_CTRL</span></dt><dd><p>0x00000008  Primary domain controller</p></dd><dt><span class="term">SV_TYPE_DOMAIN_BAKCTRL</span></dt><dd><p>0x00000010  Backup domain controller</p></dd><dt><span class="term">SV_TYPE_TIME_SOURCE</span></dt><dd><p>0x00000020  Server running the timesource service</p></dd><dt><span class="term">SV_TYPE_AFP</span></dt><dd><p>0x00000040  Apple File Protocol servers</p></dd><dt><span class="term">SV_TYPE_NOVELL</span></dt><dd><p>0x00000080  Novell servers</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MEMBER</span></dt><dd><p>0x00000100  Domain Member</p></dd><dt><span class="term">SV_TYPE_PRINTQ_SERVER</span></dt><dd><p>0x00000200  Server sharing print queue</p></dd><dt><span class="term">SV_TYPE_DIALIN_SERVER</span></dt><dd><p>0x00000400  Server running dialin service.</p></dd><dt><span class="term">SV_TYPE_XENIX_SERVER</span></dt><dd><p>0x00000800  Xenix server</p></dd><dt><span class="term">SV_TYPE_NT</span></dt><dd><p>0x00001000  NT server</p></dd><dt><span class="term">SV_TYPE_WFW</span></dt><dd><p>0x00002000  Server running Windows for </p></dd><dt><span class="term">SV_TYPE_SERVER_NT</span></dt><dd><p>0x00008000  Windows NT non DC server</p></dd><dt><span class="term">SV_TYPE_POTENTIAL_BROWSER</span></dt><dd><p>0x00010000  Server that can run the browser service</p></dd><dt><span class="term">SV_TYPE_BACKUP_BROWSER</span></dt><dd><p>0x00020000  Backup browser server</p></dd><dt><span class="term">SV_TYPE_MASTER_BROWSER</span></dt><dd><p>0x00040000  Master browser server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MASTER</span></dt><dd><p>0x00080000  Domain Master Browser server</p></dd><dt><span class="term">SV_TYPE_LOCAL_LIST_ONLY</span></dt><dd><p>0x40000000  Enumerate only entries marked "local"</p></dd><dt><span class="term">SV_TYPE_DOMAIN_ENUM</span></dt><dd><p>0x80000000  Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</p></dd></dl></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>500 - platform_id</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - major version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - minor version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>type (SV_TYPE_... bit field)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to comment</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv101_name - unicode string of server name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv_101_comment  - unicode string of server comment.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2552805"></a>MSRPC over Transact Named Pipe</h2></div></div></div><p>For details on the SMB Transact Named Pipe, see cifs6.txt</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552815"></a>MSRPC Pipes</h3></div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551559"></a>GID (group id info)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>group id</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user attributes (only used by NT 3.1 and 3.51)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551589"></a>DOM_REF (domain reference info)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num referenced domains?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>32 - max number of entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - num referenced domains?</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain name unicode string header</p></dd><dt><span class="term">UNIHDR2[num_ref_doms-1]</span></dt><dd><p>referenced domain unicode string headers</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">DOM_SID[num_ref_doms]</span></dt><dd><p>referenced domain SIDs</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551698"></a>DOM_INFO (domain info, levels 3 and 5 are the same))</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>??? padding to get 4-byte alignment with start of SMB header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name string buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID string buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name (unicode string)</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551786"></a>USER_INFO (user logon info)</h4></div></div></div><p><span class="emphasis"><em>Note: it would be nice to know what the 16 byte user session key is for.</em></span></p><div class="variablelist"><dl><dt><span class="term">NTTIME</span></dt><dd><p>logon time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>logoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>kickoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password last set time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password can change time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password must change time</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>username unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user's full name unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon script unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>profile path unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory drive unicode string header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon count</p></dd><dt><span class="term">UINT16</span></dt><dd><p>bad password count</p></dd><dt><span class="term">UINT32</span></dt><dd><p>User ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>Group ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer to groups.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user flags</p></dd><dt><span class="term">char[16]</span></dt><dd><p>user session key</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon server unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon domain unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented logon domain id pointer</p></dd><dt><span class="term">char[40]</span></dt><dd><p>40 undocumented padding bytes.  future expansion?</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - num_other_sids?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>NULL - undocumented pointer to other domain SIDs.</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>username unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user's full name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon script unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>profile path unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory drive unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">GID[num_groups]</span></dt><dd><p>group info</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon domain unicode string</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd><dt><span class="term">DOM_SID[num_sids]</span></dt><dd><p>other domain SIDs?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552218"></a>SH_INFO_1_PTR (pointers to level 1 share info strings)</h4></div></div></div><p><span class="emphasis"><em>Note:	see cifsrap2.txt section5, page 10.</em></span></p><table class="simplelist" border="0" summary="Simple list"><tr><td>0 for shi1_type indicates a  Disk.</td></tr><tr><td>1 for shi1_type indicates a  Print Queue.</td></tr><tr><td>2 for shi1_type indicates a  Device.</td></tr><tr><td>3 for shi1_type indicates an IPC pipe.</td></tr><tr><td>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</td></tr></table><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>shi1_netname - pointer to net name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>shi1_type    - type of share.  0 - undocumented.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>shi1_remark  - pointer to comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552293"></a>SH_INFO_1_STR (level 1 share info strings)</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_netname - unicode string of net name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_remark  - unicode string of comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552327"></a>SHARE_INFO_1_CTR</h4></div></div></div><p>share container with 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - Buffer</p></dd></dl></div><p>share container with &gt; 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>non-zero - Buffer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">SH_INFO_1_PTR[EntriesRead]</span></dt><dd><p>share entry pointers</p></dd><dt><span class="term">SH_INFO_1_STR[EntriesRead]</span></dt><dd><p>share entry strings</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - padding</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2552455"></a>SERVER_INFO_101</h4></div></div></div><p><span class="emphasis"><em>Note:	see cifs6.txt section 6.4 - the fields described therein will be of assistance here.  for example, the type listed below is the 	same as fServerType, which is described in 6.4.1. </em></span></p><div class="variablelist"><dl><dt><span class="term">SV_TYPE_WORKSTATION</span></dt><dd><p>0x00000001  All workstations</p></dd><dt><span class="term">SV_TYPE_SERVER</span></dt><dd><p>0x00000002  All servers</p></dd><dt><span class="term">SV_TYPE_SQLSERVER</span></dt><dd><p>0x00000004  Any server running with SQL server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_CTRL</span></dt><dd><p>0x00000008  Primary domain controller</p></dd><dt><span class="term">SV_TYPE_DOMAIN_BAKCTRL</span></dt><dd><p>0x00000010  Backup domain controller</p></dd><dt><span class="term">SV_TYPE_TIME_SOURCE</span></dt><dd><p>0x00000020  Server running the timesource service</p></dd><dt><span class="term">SV_TYPE_AFP</span></dt><dd><p>0x00000040  Apple File Protocol servers</p></dd><dt><span class="term">SV_TYPE_NOVELL</span></dt><dd><p>0x00000080  Novell servers</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MEMBER</span></dt><dd><p>0x00000100  Domain Member</p></dd><dt><span class="term">SV_TYPE_PRINTQ_SERVER</span></dt><dd><p>0x00000200  Server sharing print queue</p></dd><dt><span class="term">SV_TYPE_DIALIN_SERVER</span></dt><dd><p>0x00000400  Server running dialin service.</p></dd><dt><span class="term">SV_TYPE_XENIX_SERVER</span></dt><dd><p>0x00000800  Xenix server</p></dd><dt><span class="term">SV_TYPE_NT</span></dt><dd><p>0x00001000  NT server</p></dd><dt><span class="term">SV_TYPE_WFW</span></dt><dd><p>0x00002000  Server running Windows for </p></dd><dt><span class="term">SV_TYPE_SERVER_NT</span></dt><dd><p>0x00008000  Windows NT non DC server</p></dd><dt><span class="term">SV_TYPE_POTENTIAL_BROWSER</span></dt><dd><p>0x00010000  Server that can run the browser service</p></dd><dt><span class="term">SV_TYPE_BACKUP_BROWSER</span></dt><dd><p>0x00020000  Backup browser server</p></dd><dt><span class="term">SV_TYPE_MASTER_BROWSER</span></dt><dd><p>0x00040000  Master browser server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MASTER</span></dt><dd><p>0x00080000  Domain Master Browser server</p></dd><dt><span class="term">SV_TYPE_LOCAL_LIST_ONLY</span></dt><dd><p>0x40000000  Enumerate only entries marked "local"</p></dd><dt><span class="term">SV_TYPE_DOMAIN_ENUM</span></dt><dd><p>0x80000000  Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</p></dd></dl></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>500 - platform_id</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - major version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - minor version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>type (SV_TYPE_... bit field)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to comment</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv101_name - unicode string of server name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv_101_comment  - unicode string of server comment.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2552813"></a>MSRPC over Transact Named Pipe</h2></div></div></div><p>For details on the SMB Transact Named Pipe, see cifs6.txt</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552823"></a>MSRPC Pipes</h3></div></div></div><p>
 The MSRPC is conducted over an SMB Transact Pipe with a name of 
 <code class="filename">\PIPE\</code>.  You must first obtain a 16 bit file handle, by
 sending a SMBopenX with the pipe name <code class="filename">\PIPE\srvsvc</code> for
@@ -121,11 +121,11 @@ listed below:</p><pre class="programlisting">
         initial SMBopenX request:         RPC API command 0x26 params:
         "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
         "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552899"></a>Header</h3></div></div></div><p>[section to be rewritten, following receipt of work by Duncan Stansfield]</p><p>Interesting note: if you set packed data representation to 0x0100 0000
-then all 4-byte and 2-byte word ordering is turned around!</p><p>The start of each of the NTLSA and NETLOGON named pipes begins with:</p><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>00</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>5 - RPC major version</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>01</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - RPC minor version</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>02</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>2 - RPC response packet</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>03</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>3 - (FirstFrag bit-wise or with LastFrag)</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>04</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0x1000 0000 - packed data representation</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>08</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>fragment length - data size (bytes) inc header and tail.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>0A</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - authentication length </div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>0C</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>call identifier. matches 12th UINT32 of incoming RPC data.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>10</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>allocation hint - data size (bytes) minus header and tail.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>14</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - presentation context identifier</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>16</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - cancel count</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>17</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>in replies: 0 - reserved; in requests: opnum - see #defines.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>18</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>......</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>start of data (goes on for allocation_hint bytes)</div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553048"></a>RPC_Packet for request, response, bind and bind acknowledgement</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 versionmaj</span></dt><dd><p>reply same as request (0x05)</p></dd><dt><span class="term">UINT8 versionmin</span></dt><dd><p>reply same as request (0x00)</p></dd><dt><span class="term">UINT8 type</span></dt><dd><p>one of the MSRPC_Type enums</p></dd><dt><span class="term">UINT8 flags</span></dt><dd><p>reply same as request (0x00 for Bind, 0x03 for Request)</p></dd><dt><span class="term">UINT32 representation</span></dt><dd><p>reply same as request (0x00000010)</p></dd><dt><span class="term">UINT16 fraglength</span></dt><dd><p>the length of the data section of the SMB trans packet</p></dd><dt><span class="term">UINT16 authlength</span></dt><dd><p></p></dd><dt><span class="term">UINT32 callid</span></dt><dd><p>call identifier. (e.g. 0x00149594)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>the remainder of the packet depending on the "type"</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553151"></a>Interface identification</h4></div></div></div><p>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</p><pre class="programlisting">
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552907"></a>Header</h3></div></div></div><p>[section to be rewritten, following receipt of work by Duncan Stansfield]</p><p>Interesting note: if you set packed data representation to 0x0100 0000
+then all 4-byte and 2-byte word ordering is turned around!</p><p>The start of each of the NTLSA and NETLOGON named pipes begins with:</p><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>00</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>5 - RPC major version</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>01</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - RPC minor version</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>02</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>2 - RPC response packet</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>03</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>3 - (FirstFrag bit-wise or with LastFrag)</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>04</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0x1000 0000 - packed data representation</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>08</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>fragment length - data size (bytes) inc header and tail.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>0A</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - authentication length </div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>0C</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>call identifier. matches 12th UINT32 of incoming RPC data.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>10</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT32</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>allocation hint - data size (bytes) minus header and tail.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>14</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT16</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - presentation context identifier</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>16</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>0 - cancel count</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>17</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>UINT8</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>in replies: 0 - reserved; in requests: opnum - see #defines.</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">offset: </span></strong>18</div><div class="seg"><strong><span class="segtitle">Variable type: </span></strong>......</div><div class="seg"><strong><span class="segtitle">Variable data: </span></strong>start of data (goes on for allocation_hint bytes)</div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553056"></a>RPC_Packet for request, response, bind and bind acknowledgement</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 versionmaj</span></dt><dd><p>reply same as request (0x05)</p></dd><dt><span class="term">UINT8 versionmin</span></dt><dd><p>reply same as request (0x00)</p></dd><dt><span class="term">UINT8 type</span></dt><dd><p>one of the MSRPC_Type enums</p></dd><dt><span class="term">UINT8 flags</span></dt><dd><p>reply same as request (0x00 for Bind, 0x03 for Request)</p></dd><dt><span class="term">UINT32 representation</span></dt><dd><p>reply same as request (0x00000010)</p></dd><dt><span class="term">UINT16 fraglength</span></dt><dd><p>the length of the data section of the SMB trans packet</p></dd><dt><span class="term">UINT16 authlength</span></dt><dd><p></p></dd><dt><span class="term">UINT32 callid</span></dt><dd><p>call identifier. (e.g. 0x00149594)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>the remainder of the packet depending on the "type"</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553159"></a>Interface identification</h4></div></div></div><p>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</p><pre class="programlisting">
 abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
 transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553171"></a>RPC_Iface RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 byte[16]</span></dt><dd><p>16 bytes of number</p></dd><dt><span class="term">UINT32 version</span></dt><dd><p>the interface number</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553200"></a>RPC_ReqBind RW</h4></div></div></div><p>the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>maximum transmission fragment size (0x1630)</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>max receive fragment size (0x1630)</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>associated group id (0x0)</p></dd><dt><span class="term">UINT32 numelements</span></dt><dd><p>the number of elements (0x1)</p></dd><dt><span class="term">UINT16 contextid</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT8 numsyntaxes</span></dt><dd><p>the number of syntaxes (has always been 1?)(0x1)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">* abstractint USE RPC_Iface</span></dt><dd><p>num and vers. of interface client is using</p></dd><dt><span class="term">* transferint USE RPC_Iface</span></dt><dd><p>num and vers. of interface to use for replies</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553309"></a>RPC_Address RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16 length</span></dt><dd><p>length of the string including null terminator</p></dd><dt><span class="term">* port USE string</span></dt><dd><p>the string above in single byte, null terminated form</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553340"></a>RPC_ResBind RW</h4></div></div></div><p>the response to place after the header in the reply packet</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>zero</p></dd><dt><span class="term">* secondaddr USE RPC_Address</span></dt><dd><p>the address string, as described earlier</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT8 numresults</span></dt><dd><p>the number of results (0x01)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT16 result</span></dt><dd><p>result (0x00 = accept)</p></dd><dt><span class="term">UINT16 reason</span></dt><dd><p>reason (0x00 = no reason specified)</p></dd><dt><span class="term">* transfersyntax USE RPC_Iface</span></dt><dd><p>the transfer syntax from the request</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553456"></a>RPC_ReqNorm RW</h4></div></div></div><p>the remainder of the packet after the header for every other other request</p><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p>the size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT16 opnum</span></dt><dd><p>operation number (0x15)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>a packet dependent on the pipe name (probably the interface) and the op number)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553511"></a>RPC_ResNorm RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p># size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p># presentation context identifier (same as request)</p></dd><dt><span class="term">UINT8 cancelcount</span></dt><dd><p># cancel count? (0x0)</p></dd><dt><span class="term">UINT8 reserved</span></dt><dd><p># 0 - one byte padding</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p># the remainder of the reply</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553572"></a>Tail</h3></div></div></div><p>The end of each of the NTLSA and NETLOGON named pipes ends with:</p><div class="variablelist"><dl><dt><span class="term">......</span></dt><dd><p>end of data</p></dd><dt><span class="term">UINT32</span></dt><dd><p>return code</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553608"></a>RPC Bind / Bind Ack</h3></div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553180"></a>RPC_Iface RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 byte[16]</span></dt><dd><p>16 bytes of number</p></dd><dt><span class="term">UINT32 version</span></dt><dd><p>the interface number</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553208"></a>RPC_ReqBind RW</h4></div></div></div><p>the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>maximum transmission fragment size (0x1630)</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>max receive fragment size (0x1630)</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>associated group id (0x0)</p></dd><dt><span class="term">UINT32 numelements</span></dt><dd><p>the number of elements (0x1)</p></dd><dt><span class="term">UINT16 contextid</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT8 numsyntaxes</span></dt><dd><p>the number of syntaxes (has always been 1?)(0x1)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">* abstractint USE RPC_Iface</span></dt><dd><p>num and vers. of interface client is using</p></dd><dt><span class="term">* transferint USE RPC_Iface</span></dt><dd><p>num and vers. of interface to use for replies</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553317"></a>RPC_Address RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16 length</span></dt><dd><p>length of the string including null terminator</p></dd><dt><span class="term">* port USE string</span></dt><dd><p>the string above in single byte, null terminated form</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553348"></a>RPC_ResBind RW</h4></div></div></div><p>the response to place after the header in the reply packet</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>zero</p></dd><dt><span class="term">* secondaddr USE RPC_Address</span></dt><dd><p>the address string, as described earlier</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT8 numresults</span></dt><dd><p>the number of results (0x01)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT16 result</span></dt><dd><p>result (0x00 = accept)</p></dd><dt><span class="term">UINT16 reason</span></dt><dd><p>reason (0x00 = no reason specified)</p></dd><dt><span class="term">* transfersyntax USE RPC_Iface</span></dt><dd><p>the transfer syntax from the request</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553464"></a>RPC_ReqNorm RW</h4></div></div></div><p>the remainder of the packet after the header for every other other request</p><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p>the size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT16 opnum</span></dt><dd><p>operation number (0x15)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>a packet dependent on the pipe name (probably the interface) and the op number)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553519"></a>RPC_ResNorm RW</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p># size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p># presentation context identifier (same as request)</p></dd><dt><span class="term">UINT8 cancelcount</span></dt><dd><p># cancel count? (0x0)</p></dd><dt><span class="term">UINT8 reserved</span></dt><dd><p># 0 - one byte padding</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p># the remainder of the reply</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553580"></a>Tail</h3></div></div></div><p>The end of each of the NTLSA and NETLOGON named pipes ends with:</p><div class="variablelist"><dl><dt><span class="term">......</span></dt><dd><p>end of data</p></dd><dt><span class="term">UINT32</span></dt><dd><p>return code</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553616"></a>RPC Bind / Bind Ack</h3></div></div></div><p>
 RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc)
 with a "transfer syntax" (see RPC_Iface structure).  The purpose for doing
 this is unknown.
@@ -133,7 +133,7 @@ this is unknown.
 	returned by the SMBopenX Transact response.</em></span></p><p><span class="emphasis"><em>Note:	The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind.  The
 	RPC_ResBind member transfersyntax is the same in the response as
 	the</em></span></p><p><span class="emphasis"><em>Note:	The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe.  The
-	mapping identified so far is:</em></span></p><div class="variablelist"><dl><dt><span class="term">initial SMBopenX request:</span></dt><dd><p>RPC_ResBind response:</p></dd><dt><span class="term">"\\PIPE\\srvsvc"</span></dt><dd><p>"\\PIPE\\ntsvcs"</p></dd><dt><span class="term">"\\PIPE\\samr"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\lsarpc"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\wkssvc"</span></dt><dd><p>"\\PIPE\\wksvcs"</p></dd><dt><span class="term">"\\PIPE\\NETLOGON"</span></dt><dd><p>"\\PIPE\\NETLOGON"</p></dd></dl></div><p><span class="emphasis"><em>Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</em></span></p><p>Request:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ReqBind</td></tr></table><p>Response:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ResBind</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553746"></a>NTLSA Transact Named Pipe</h3></div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Establish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>Open an RPC Pipe with the name "\\PIPE\\lsarpc".  Store the file handle.</td></tr><tr><td>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>Send an LSA Open Policy request.  Store the Policy Handle.</td></tr><tr><td>Using the Policy Handle, send LSA Query Info Policy requests, etc.</td></tr><tr><td>Using the Policy Handle, send an LSA Close.</td></tr><tr><td>Close the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">LSA Open Policy:</span></dt><dd><p>0x2c</p></dd><dt><span class="term">LSA Query Info Policy:</span></dt><dd><p>0x07</p></dd><dt><span class="term">LSA Enumerate Trusted Domains:</span></dt><dd><p>0x0d</p></dd><dt><span class="term">LSA Open Secret:</span></dt><dd><p>0xff</p></dd><dt><span class="term">LSA Lookup SIDs:</span></dt><dd><p>0xfe</p></dd><dt><span class="term">LSA Lookup Names:</span></dt><dd><p>0xfd</p></dd><dt><span class="term">LSA Close:</span></dt><dd><p>0x00</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553874"></a>LSA Open Policy</h3></div></div></div><p><span class="emphasis"><em>Note:	The policy handle can be anything you like.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553885"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name - unicode string starting with two '\'s</p></dd><dt><span class="term">OBJ_ATTR</span></dt><dd><p>object attributes</p></dd><dt><span class="term">UINT32</span></dt><dd><p>1 - desired access</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553938"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">return</span></dt><dd><p>0 - indicates success</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553970"></a>LSA Query Info Policy</h3></div></div></div><p><span class="emphasis"><em>Note:	The info class in response must be the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553981"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (also a policy handle?)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554011"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (same as info class in request).</p></dd></dl></div><pre class="programlisting">
+	mapping identified so far is:</em></span></p><div class="variablelist"><dl><dt><span class="term">initial SMBopenX request:</span></dt><dd><p>RPC_ResBind response:</p></dd><dt><span class="term">"\\PIPE\\srvsvc"</span></dt><dd><p>"\\PIPE\\ntsvcs"</p></dd><dt><span class="term">"\\PIPE\\samr"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\lsarpc"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\wkssvc"</span></dt><dd><p>"\\PIPE\\wksvcs"</p></dd><dt><span class="term">"\\PIPE\\NETLOGON"</span></dt><dd><p>"\\PIPE\\NETLOGON"</p></dd></dl></div><p><span class="emphasis"><em>Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</em></span></p><p>Request:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ReqBind</td></tr></table><p>Response:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ResBind</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553755"></a>NTLSA Transact Named Pipe</h3></div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Establish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>Open an RPC Pipe with the name "\\PIPE\\lsarpc".  Store the file handle.</td></tr><tr><td>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>Send an LSA Open Policy request.  Store the Policy Handle.</td></tr><tr><td>Using the Policy Handle, send LSA Query Info Policy requests, etc.</td></tr><tr><td>Using the Policy Handle, send an LSA Close.</td></tr><tr><td>Close the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">LSA Open Policy:</span></dt><dd><p>0x2c</p></dd><dt><span class="term">LSA Query Info Policy:</span></dt><dd><p>0x07</p></dd><dt><span class="term">LSA Enumerate Trusted Domains:</span></dt><dd><p>0x0d</p></dd><dt><span class="term">LSA Open Secret:</span></dt><dd><p>0xff</p></dd><dt><span class="term">LSA Lookup SIDs:</span></dt><dd><p>0xfe</p></dd><dt><span class="term">LSA Lookup Names:</span></dt><dd><p>0xfd</p></dd><dt><span class="term">LSA Close:</span></dt><dd><p>0x00</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553883"></a>LSA Open Policy</h3></div></div></div><p><span class="emphasis"><em>Note:	The policy handle can be anything you like.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553893"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name - unicode string starting with two '\'s</p></dd><dt><span class="term">OBJ_ATTR</span></dt><dd><p>object attributes</p></dd><dt><span class="term">UINT32</span></dt><dd><p>1 - desired access</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553946"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">return</span></dt><dd><p>0 - indicates success</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553978"></a>LSA Query Info Policy</h3></div></div></div><p><span class="emphasis"><em>Note:	The info class in response must be the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553989"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (also a policy handle?)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554019"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (same as info class in request).</p></dd></dl></div><pre class="programlisting">
 switch (info class)
 case 3:
 case 5:
@@ -142,11 +142,11 @@ DOM_INFO domain info, levels 3 and 5 (are the same).
 }
 
 return    0 - indicates success
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554052"></a>LSA Enumerate Trusted Domains</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554058"></a>Request</h4></div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554068"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - enumeration context</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - entries read</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - trust information</p></dd><dt><span class="term">return</span></dt><dd><p>0x8000 001a - "no trusted domains" success code</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554122"></a>LSA Open Secret</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554127"></a>Request</h4></div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554137"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd></dl></div><p>return    0x0C00 0034 - "no such secret" success code</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554205"></a>LSA Close</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554210"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>policy handle to be closed</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554231"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>0s - closed policy handle (all zeros)</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554256"></a>LSA Lookup SIDS</h3></div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554266"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">VOID*[num_entries] undocumented domain SID pointers to be looked up.
-</span></dt><dd><p>DOM_SID[num_entries] domain SIDs to be looked up.</p></dd><dt><span class="term">char[16]</span></dt><dd><p>completely undocumented 16 bytes.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554344"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_SID2[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554417"></a>LSA Lookup Names</h3></div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554428"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">NAME[num_entries]</span></dt><dd><p>names to be looked up.</p></dd><dt><span class="term">char[]</span></dt><dd><p>undocumented bytes - falsely translated SID structure?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554514"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_RID[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554589"></a>NETLOGON rpc Transact Named Pipe</h2></div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>tablish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>en an RPC Pipe with the name "\\PIPE\\NETLOGON".  Store the file handle.</td></tr><tr><td>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>eate Client Challenge. Send LSA Request Challenge.  Store Server Challenge.</td></tr><tr><td>lculate Session Key.  Send an LSA Auth 2 Challenge.  Store Auth2 Challenge.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA Srv PW Set.  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logon .  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logoff.  Calc/Verify Server Creds.</td></tr><tr><td>ose the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are</p><div class="variablelist"><dl><dt><span class="term">LSA Request Challenge:</span></dt><dd><p>0x04</p></dd><dt><span class="term">LSA Server Password Set:</span></dt><dd><p>0x06</p></dd><dt><span class="term">LSA SAM Logon:</span></dt><dd><p>0x02</p></dd><dt><span class="term">LSA SAM Logoff:</span></dt><dd><p>0x03</p></dd><dt><span class="term">LSA Auth 2:</span></dt><dd><p>0x0f</p></dd><dt><span class="term">LSA Logon Control:</span></dt><dd><p>0x0e</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554715"></a>LSA Request Challenge</h3></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	logon client is the machine, not the user.</em></span></p><p><span class="emphasis"><em>Note:	the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case).  there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554746"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client unicode string</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client challenge</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554798"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server challenge</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554824"></a>LSA Authenticate 2</h3></div></div></div><p><span class="emphasis"><em>Note:	in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note:	neg_flags in the response is the same as that in the request.</em></span></p><p><span class="emphasis"><em>Note:	you must take a copy of the client-calculated credentials received 	here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554849"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>client identification info</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client-calculated credentials</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 4-byte align with start of SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - negotiated flags (usual value is 0x0000 01ff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554902"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server credentials.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - same as neg_flags in request.</p></dd></dl></div><p>return    0 - indicates success.  failure value unknown.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554939"></a>LSA Server Password Set</h3></div></div></div><p><span class="emphasis"><em>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</em></span></p><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554971"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">CLNT_INFO</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">char[]</span></dt><dd><p>new password - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555003"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return    0 - indicates success; 0xC000 006a indicates failure</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555030"></a>LSA SAM Logon</h3></div></div></div><p><span class="emphasis"><em>
+</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554060"></a>LSA Enumerate Trusted Domains</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554066"></a>Request</h4></div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554076"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - enumeration context</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - entries read</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - trust information</p></dd><dt><span class="term">return</span></dt><dd><p>0x8000 001a - "no trusted domains" success code</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554130"></a>LSA Open Secret</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554135"></a>Request</h4></div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554145"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd></dl></div><p>return    0x0C00 0034 - "no such secret" success code</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554213"></a>LSA Close</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554218"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>policy handle to be closed</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554239"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>0s - closed policy handle (all zeros)</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554264"></a>LSA Lookup SIDS</h3></div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554275"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">VOID*[num_entries] undocumented domain SID pointers to be looked up.
+</span></dt><dd><p>DOM_SID[num_entries] domain SIDs to be looked up.</p></dd><dt><span class="term">char[16]</span></dt><dd><p>completely undocumented 16 bytes.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554352"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_SID2[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554425"></a>LSA Lookup Names</h3></div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554436"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">NAME[num_entries]</span></dt><dd><p>names to be looked up.</p></dd><dt><span class="term">char[]</span></dt><dd><p>undocumented bytes - falsely translated SID structure?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554523"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_RID[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554597"></a>NETLOGON rpc Transact Named Pipe</h2></div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>tablish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>en an RPC Pipe with the name "\\PIPE\\NETLOGON".  Store the file handle.</td></tr><tr><td>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>eate Client Challenge. Send LSA Request Challenge.  Store Server Challenge.</td></tr><tr><td>lculate Session Key.  Send an LSA Auth 2 Challenge.  Store Auth2 Challenge.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA Srv PW Set.  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logon .  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logoff.  Calc/Verify Server Creds.</td></tr><tr><td>ose the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are</p><div class="variablelist"><dl><dt><span class="term">LSA Request Challenge:</span></dt><dd><p>0x04</p></dd><dt><span class="term">LSA Server Password Set:</span></dt><dd><p>0x06</p></dd><dt><span class="term">LSA SAM Logon:</span></dt><dd><p>0x02</p></dd><dt><span class="term">LSA SAM Logoff:</span></dt><dd><p>0x03</p></dd><dt><span class="term">LSA Auth 2:</span></dt><dd><p>0x0f</p></dd><dt><span class="term">LSA Logon Control:</span></dt><dd><p>0x0e</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554723"></a>LSA Request Challenge</h3></div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	logon client is the machine, not the user.</em></span></p><p><span class="emphasis"><em>Note:	the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case).  there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554754"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client unicode string</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client challenge</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554807"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server challenge</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554832"></a>LSA Authenticate 2</h3></div></div></div><p><span class="emphasis"><em>Note:	in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note:	neg_flags in the response is the same as that in the request.</em></span></p><p><span class="emphasis"><em>Note:	you must take a copy of the client-calculated credentials received 	here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554857"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>client identification info</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client-calculated credentials</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 4-byte align with start of SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - negotiated flags (usual value is 0x0000 01ff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554910"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server credentials.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - same as neg_flags in request.</p></dd></dl></div><p>return    0 - indicates success.  failure value unknown.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554947"></a>LSA Server Password Set</h3></div></div></div><p><span class="emphasis"><em>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</em></span></p><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554979"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">CLNT_INFO</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">char[]</span></dt><dd><p>new password - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555011"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return    0 - indicates success; 0xC000 006a indicates failure</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555038"></a>LSA SAM Logon</h3></div></div></div><p><span class="emphasis"><em>
 Note:	valid_user is True iff the username and password hash are valid for
 	the requested domain.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555042"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555062"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><pre class="programlisting">
+</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555050"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555070"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><pre class="programlisting">
 if (valid_user)
 {
 	UINT16      3 - switch value indicating USER_INFO structure.
@@ -166,16 +166,16 @@ else
 
     return    0xC000 0064 - NT_STATUS_NO_SUCH_USER.
 }
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555110"></a>LSA SAM Logoff</h3></div></div></div><p><span class="emphasis"><em>
+</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555118"></a>LSA SAM Logoff</h3></div></div></div><p><span class="emphasis"><em>
 Note:	presumably, the SAM_INFO structure is validated, and a (currently
 	undocumented) error code returned if the Logoff is invalid.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555122"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555142"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return      0 - indicates success.  undocumented failure indication.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555181"></a>\\MAILSLOT\NET\NTLOGON</h2></div></div></div><p><span class="emphasis"><em>
+</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555130"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555150"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return      0 - indicates success.  undocumented failure indication.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555189"></a>\\MAILSLOT\NET\NTLOGON</h2></div></div></div><p><span class="emphasis"><em>
 Note:	mailslots will contain a response mailslot, to which the response
 	should be sent.  the target NetBIOS name is REQUEST_NAME&lt;20&gt;, where
 	REQUEST_NAME is the name of the machine that sent the request.
-</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555195"></a>Query for PDC</h3></div></div></div><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those 	given in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555207"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0007 - Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555302"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x000A - Respose to Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name (in uppercase)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token (same as received in request)</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555396"></a>SAM Logon</h3></div></div></div><p><span class="emphasis"><em>Note: machine name in response is preceded by two '\' characters.</em></span></p><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><p><span class="emphasis"><em>Note:	user name in the response is presumably the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555419"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0012 - SAM Logon</p></dd><dt><span class="term">UINT16</span></dt><dd><p>request count</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT32</span></dt><dd><p>alloweable account</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain SID size</p></dd><dt><span class="term">char[sid_size]</span></dt><dd><p>domain SID, of sid_size bytes.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding to 4? 2? -byte align with start of mailslot.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555558"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0013 - Response to SAM Logon</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name - workstation trust account</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name </p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555646"></a>SRVSVC Transact Named Pipe</h2></div></div></div><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">Net Share Enum</span></dt><dd><p>0x0f</p></dd><dt><span class="term">Net Server Get Info</span></dt><dd><p>0x15</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555680"></a>Net Share Enum</h3></div></div></div><p><span class="emphasis"><em>Note:	share level and switch value in the response are presumably the same as those in the request.</em></span></p><p><span class="emphasis"><em>Note:	cifsrap2.txt (section 5) may be of limited assistance here.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555697"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>pointer (to server name?)</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info with 0 entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>preferred maximum length (0xffff ffff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555792"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info (only added if share info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555848"></a>Net Server Get Info</h3></div></div></div><p><span class="emphasis"><em>Note:	level is the same value as in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555858"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555889"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SERVER_INFO_101</p></dd><dt><span class="term">SERVER_INFO_101</span></dt><dd><p>server info (only added if server info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555937"></a>Cryptographic side of NT Domain Authentication</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555943"></a>Definitions</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Add(A1,A2)</span></dt><dd><p>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</p></dd><dt><span class="term">E(K,D)</span></dt><dd><p>DES ECB encryption of 8 byte data D using 7 byte key K</p></dd><dt><span class="term">lmowf()</span></dt><dd><p>Lan man hash</p></dd><dt><span class="term">ntowf()</span></dt><dd><p>NT hash</p></dd><dt><span class="term">PW</span></dt><dd><p>md4(machine_password) == md4(lsadump $machine.acc) ==
+</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555203"></a>Query for PDC</h3></div></div></div><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those 	given in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555215"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0007 - Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555311"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x000A - Respose to Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name (in uppercase)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token (same as received in request)</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555404"></a>SAM Logon</h3></div></div></div><p><span class="emphasis"><em>Note: machine name in response is preceded by two '\' characters.</em></span></p><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><p><span class="emphasis"><em>Note:	user name in the response is presumably the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555427"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0012 - SAM Logon</p></dd><dt><span class="term">UINT16</span></dt><dd><p>request count</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT32</span></dt><dd><p>alloweable account</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain SID size</p></dd><dt><span class="term">char[sid_size]</span></dt><dd><p>domain SID, of sid_size bytes.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding to 4? 2? -byte align with start of mailslot.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555566"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0013 - Response to SAM Logon</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name - workstation trust account</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name </p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555654"></a>SRVSVC Transact Named Pipe</h2></div></div></div><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">Net Share Enum</span></dt><dd><p>0x0f</p></dd><dt><span class="term">Net Server Get Info</span></dt><dd><p>0x15</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555688"></a>Net Share Enum</h3></div></div></div><p><span class="emphasis"><em>Note:	share level and switch value in the response are presumably the same as those in the request.</em></span></p><p><span class="emphasis"><em>Note:	cifsrap2.txt (section 5) may be of limited assistance here.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555705"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>pointer (to server name?)</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info with 0 entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>preferred maximum length (0xffff ffff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555800"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info (only added if share info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555856"></a>Net Server Get Info</h3></div></div></div><p><span class="emphasis"><em>Note:	level is the same value as in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555867"></a>Request</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555898"></a>Response</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SERVER_INFO_101</p></dd><dt><span class="term">SERVER_INFO_101</span></dt><dd><p>server info (only added if server info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2555945"></a>Cryptographic side of NT Domain Authentication</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555952"></a>Definitions</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Add(A1,A2)</span></dt><dd><p>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</p></dd><dt><span class="term">E(K,D)</span></dt><dd><p>DES ECB encryption of 8 byte data D using 7 byte key K</p></dd><dt><span class="term">lmowf()</span></dt><dd><p>Lan man hash</p></dd><dt><span class="term">ntowf()</span></dt><dd><p>NT hash</p></dd><dt><span class="term">PW</span></dt><dd><p>md4(machine_password) == md4(lsadump $machine.acc) ==
 pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))
-</p></dd><dt><span class="term">ARC4(K,Lk,D,Ld)</span></dt><dd><p>ARC4 encryption of data D of length Ld with key K of length Lk</p></dd><dt><span class="term">v[m..n(,l)]</span></dt><dd><p>subset of v from bytes m to n, optionally padded with zeroes to length l</p></dd><dt><span class="term">Cred(K,D)</span></dt><dd><p>E(K[7..7,7],E(K[0..6],D)) computes a credential</p></dd><dt><span class="term">Time()</span></dt><dd><p>4 byte current time</p></dd><dt><span class="term">Cc,Cs</span></dt><dd><p>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556069"></a>Protocol</h3></div></div></div><pre class="programlisting">
+</p></dd><dt><span class="term">ARC4(K,Lk,D,Ld)</span></dt><dd><p>ARC4 encryption of data D of length Ld with key K of length Lk</p></dd><dt><span class="term">v[m..n(,l)]</span></dt><dd><p>subset of v from bytes m to n, optionally padded with zeroes to length l</p></dd><dt><span class="term">Cred(K,D)</span></dt><dd><p>E(K[7..7,7],E(K[0..6],D)) computes a credential</p></dd><dt><span class="term">Time()</span></dt><dd><p>4 byte current time</p></dd><dt><span class="term">Cc,Cs</span></dt><dd><p>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556077"></a>Protocol</h3></div></div></div><pre class="programlisting">
 C-&gt;S ReqChal,Cc
 S-&gt;C Cs
 </pre><pre class="programlisting">
@@ -211,7 +211,7 @@ S: Ts = Time()
 S-&gt;C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
 C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
 C: Rc = Cred(Ks,Rc+Tc+1)
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556148"></a>Comments</h3></div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556156"></a>Comments</h3></div></div></div><p>
 On first joining the domain the session key could be computed by
 anyone listening in on the network as the machine password has a well
 known value. Until the machine is rebooted it will use this session
@@ -232,15 +232,15 @@ returned by the server.
 The password OWFs should NOT be sent over the network reversibly
 encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server
 computing the same function using the owf values in the SAM.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556190"></a>SIDs and RIDs</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2556198"></a>SIDs and RIDs</h2></div></div></div><p>
 SIDs and RIDs are well documented elsewhere.
 </p><p>
 A SID is an NT Security ID (see DOM_SID structure).  They are of the form:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>revision-NN-SubAuth1-SubAuth2-SubAuth3... </td></tr><tr><td>revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...</td></tr></table><p>
 currently, the SID revision is 1.
 The Sub-Authorities are known as Relative IDs (RIDs).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556222"></a>Well-known SIDs</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556227"></a>Universal well-known SIDs</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">Null SID</span></dt><dd><p>S-1-0-0</p></dd><dt><span class="term">World</span></dt><dd><p>S-1-1-0</p></dd><dt><span class="term">Local</span></dt><dd><p>S-1-2-0</p></dd><dt><span class="term">Creator Owner ID</span></dt><dd><p>S-1-3-0</p></dd><dt><span class="term">Creator Group ID</span></dt><dd><p>S-1-3-1</p></dd><dt><span class="term">Creator Owner Server ID</span></dt><dd><p>S-1-3-2</p></dd><dt><span class="term">Creator Group Server ID</span></dt><dd><p>S-1-3-3</p></dd><dt><span class="term">(Non-unique IDs)</span></dt><dd><p>S-1-4</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556322"></a>NT well-known SIDs</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">NT Authority</span></dt><dd><p>S-1-5</p></dd><dt><span class="term">Dialup</span></dt><dd><p>S-1-5-1</p></dd><dt><span class="term">Network</span></dt><dd><p>S-1-5-2</p></dd><dt><span class="term">Batch</span></dt><dd><p>S-1-5-3</p></dd><dt><span class="term">Interactive</span></dt><dd><p>S-1-5-4</p></dd><dt><span class="term">Service</span></dt><dd><p>S-1-5-6</p></dd><dt><span class="term">AnonymousLogon(aka null logon session)</span></dt><dd><p>S-1-5-7</p></dd><dt><span class="term">Proxy</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">ServerLogon(aka domain controller account)</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">(Logon IDs)</span></dt><dd><p>S-1-5-5-X-Y</p></dd><dt><span class="term">(NT non-unique IDs)</span></dt><dd><p>S-1-5-0x15-...</p></dd><dt><span class="term">(Built-in domain)</span></dt><dd><p>s-1-5-0x20</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556460"></a>Well-known RIDS</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556230"></a>Well-known SIDs</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556235"></a>Universal well-known SIDs</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">Null SID</span></dt><dd><p>S-1-0-0</p></dd><dt><span class="term">World</span></dt><dd><p>S-1-1-0</p></dd><dt><span class="term">Local</span></dt><dd><p>S-1-2-0</p></dd><dt><span class="term">Creator Owner ID</span></dt><dd><p>S-1-3-0</p></dd><dt><span class="term">Creator Group ID</span></dt><dd><p>S-1-3-1</p></dd><dt><span class="term">Creator Owner Server ID</span></dt><dd><p>S-1-3-2</p></dd><dt><span class="term">Creator Group Server ID</span></dt><dd><p>S-1-3-3</p></dd><dt><span class="term">(Non-unique IDs)</span></dt><dd><p>S-1-4</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556330"></a>NT well-known SIDs</h4></div></div></div><div class="variablelist"><dl><dt><span class="term">NT Authority</span></dt><dd><p>S-1-5</p></dd><dt><span class="term">Dialup</span></dt><dd><p>S-1-5-1</p></dd><dt><span class="term">Network</span></dt><dd><p>S-1-5-2</p></dd><dt><span class="term">Batch</span></dt><dd><p>S-1-5-3</p></dd><dt><span class="term">Interactive</span></dt><dd><p>S-1-5-4</p></dd><dt><span class="term">Service</span></dt><dd><p>S-1-5-6</p></dd><dt><span class="term">AnonymousLogon(aka null logon session)</span></dt><dd><p>S-1-5-7</p></dd><dt><span class="term">Proxy</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">ServerLogon(aka domain controller account)</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">(Logon IDs)</span></dt><dd><p>S-1-5-5-X-Y</p></dd><dt><span class="term">(NT non-unique IDs)</span></dt><dd><p>S-1-5-0x15-...</p></dd><dt><span class="term">(Built-in domain)</span></dt><dd><p>s-1-5-0x20</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556468"></a>Well-known RIDS</h3></div></div></div><p>
 A RID is a sub-authority value, as part of either a SID, or in the case
 of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1
 structure, in the LSA SAM Logon response.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556472"></a>Well-known RID users</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>DOMAIN_USER_RID_ADMIN</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>01F4</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>DOMAIN_USER_RID_GUEST</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>01F5</div></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556508"></a>Well-known RID groups</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_ADMINS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0200</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0201</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_GUESTS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0202</div></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556553"></a>Well-known RID aliases</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_ADMINS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0220</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0221</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_GUESTS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0222</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_POWER_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0223</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_ACCOUNT_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0224</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_SYSTEM_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0225</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_PRINT_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0226</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_BACKUP_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0227</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_REPLICATOR</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0228</div></div></div></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="unix-smb.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="pt01.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="pt02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�1.�NetBIOS in a Unix World�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�II.�Samba Basics</td></tr></table></div></body></html>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556480"></a>Well-known RID users</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>DOMAIN_USER_RID_ADMIN</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>01F4</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>DOMAIN_USER_RID_GUEST</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>01F5</div></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556516"></a>Well-known RID groups</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_ADMINS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0200</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0201</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_GROUP_RID_GUESTS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0202</div></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556561"></a>Well-known RID aliases</h4></div></div></div><div class="segmentedlist"><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_ADMINS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0220</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0221</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_GUESTS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0222</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_POWER_USERS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0223</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_ACCOUNT_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0224</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_SYSTEM_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0225</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_PRINT_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0226</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_BACKUP_OPS</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0227</div></div><div class="seglistitem"><div class="seg"><strong><span class="segtitle">Groupname: </span></strong>	DOMAIN_ALIAS_RID_REPLICATOR</div><div class="seg"><strong><span class="segtitle">????: </span></strong>0x0000</div><div class="seg"><strong><span class="segtitle">RID: </span></strong>0228</div></div></div></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="unix-smb.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="pt01.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="pt02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�1.�NetBIOS in a Unix World�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�II.�Samba Basics</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/parsing.html b/docs/htmldocs/Samba3-Developers-Guide/parsing.html
index a2e66b43d3..c776bbf48f 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/parsing.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/parsing.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�The smb.conf file</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="vfs.html" title="Chapter�10.�VFS Modules"><link rel="next" href="wins.html" title="Chapter�12.�Samba WINS Internals"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�The smb.conf file</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="vfs.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="wins.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="parsing"></a>Chapter�11.�The smb.conf file</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">November 1997</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="parsing.html#id2560352">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560424">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560469">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560520">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560597">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560655">About params.c</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560352"></a>Lexical Analysis</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�The smb.conf file</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="vfs.html" title="Chapter�10.�VFS Modules"><link rel="next" href="wins.html" title="Chapter�12.�Samba WINS Internals"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�The smb.conf file</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="vfs.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="wins.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="parsing"></a>Chapter�11.�The smb.conf file</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">November 1997</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="parsing.html#id2560333">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560405">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560450">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560502">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560579">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560636">About params.c</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560333"></a>Lexical Analysis</h2></div></div></div><p>
 Basically, the file is processed on a line by line basis.  There are
 four types of lines that are recognized by the lexical analyzer
 (params.c):
@@ -25,7 +25,7 @@ ignores them.  The latter two line types are scanned for
 These are the only tokens passed to the parameter loader
 (loadparm.c).  Parameter names and values are divided from one
 another by an equal sign: '='.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560424"></a>Handling of Whitespace</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560405"></a>Handling of Whitespace</h3></div></div></div><p>
 Whitespace is defined as all characters recognized by the isspace()
 function (see ctype(3C)) except for the newline character ('\n')
 The newline is excluded because it identifies the end of the line.
@@ -40,7 +40,7 @@ the exception of carriage return characters ('\r'), all of which
 are removed.
 </p></li><li><p>
 Leading and trailing whitespace is removed from names and values.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560469"></a>Handling of Line Continuation</h3></div></div></div><p>
+</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560450"></a>Handling of Line Continuation</h3></div></div></div><p>
 Long section header and parameter lines may be extended across
 multiple lines by use of the backslash character ('\\').  Line
 continuation is ignored for blank and comment lines.
@@ -63,7 +63,7 @@ line, plus the four preceeding the word 'with' in the second line.
 Line continuation characters are ignored on blank lines and at the end
 of comments.  They are *only* recognized within section and parameter
 lines.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560520"></a>Line Continuation Quirks</h3></div></div></div><p>Note the following example:</p><pre class="programlisting">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560502"></a>Line Continuation Quirks</h3></div></div></div><p>Note the following example:</p><pre class="programlisting">
 	param name = parameter value string \
     \
     with line continuation.
@@ -87,7 +87,7 @@ terminating character, and the rest of the line is ignored.  The lines
 </pre><p>are read as</p><pre class="programlisting">
 	[section name]
     param name = value
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560597"></a>Syntax</h2></div></div></div><p>The syntax of the smb.conf file is as follows:</p><pre class="programlisting">
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560579"></a>Syntax</h2></div></div></div><p>The syntax of the smb.conf file is as follows:</p><pre class="programlisting">
   &lt;file&gt;            :==  { &lt;section&gt; } EOF
   &lt;section&gt;         :==  &lt;section header&gt; { &lt;parameter line&gt; }
   &lt;section header&gt;  :==  '[' NAME ']'
@@ -106,7 +106,7 @@ terminating character, and the rest of the line is ignored.  The lines
 	A parameter line is divided into a NAME and a VALUE.  The *first*
 	equal sign on the line separates the NAME from the VALUE.  The
 	VALUE is terminated by a newline character (NL = '\n').
-</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560655"></a>About params.c</h3></div></div></div><p>
+</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560636"></a>About params.c</h3></div></div></div><p>
 The parsing of the config file is a bit unusual if you are used to
 lex, yacc, bison, etc.  Both lexical analysis (scanning) and parsing
 are performed by params.c.  Values are loaded via callbacks to
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pr01.html b/docs/htmldocs/Samba3-Developers-Guide/pr01.html
index 84ccc14fab..4a09fa06bd 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pr01.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pr01.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Attribution</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="index.html" title="SAMBA Developers Guide"><link rel="next" href="pt01.html" title="Part�I.�The protocol"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Attribution</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pt01.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2540380"></a>Attribution</h2></div></div></div><p><a class="link" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World">NetBIOS in a Unix World</a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Attribution</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="index.html" title="SAMBA Developers Guide"><link rel="next" href="pt01.html" title="Part�I.�The protocol"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Attribution</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pt01.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2540388"></a>Attribution</h2></div></div></div><p><a class="link" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World">NetBIOS in a Unix World</a>
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell</p></li></ul></div><p>
 </p><p><a class="link" href="ntdomain.html" title="Chapter�2.�NT Domain RPC's">NT Domain RPC's</a>
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Luke Leighton<a class="ulink" href="mailto:lkcl@switchboard.net" target="_top">mailto:lkcl@switchboard.net</a></p></li><li><p>Paul Ashton<a class="ulink" href="mailto:paul@argo.demon.co.uk" target="_top">mailto:paul@argo.demon.co.uk</a></p></li><li><p>Duncan Stansfield<a class="ulink" href="mailto:duncans@sco.com" target="_top">mailto:duncans@sco.com</a></p></li></ul></div><p>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pt01.html b/docs/htmldocs/Samba3-Developers-Guide/pt01.html
index 5f2e04e639..0e2eb68c79 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pt01.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pt01.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�The protocol</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="pr01.html" title="Attribution"><link rel="next" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�The protocol</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="unix-smb.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2499078"></a>Part�I.�The protocol</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="unix-smb.html">1. NetBIOS in a Unix World</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-smb.html#id2499107">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499128">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499459">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499491">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498824">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498876">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498908">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498929">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2549963">Protocol Complexity</a></span></dt></dl></dd><dt><span class="chapter"><a href="ntdomain.html">2. NT Domain RPC's</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntdomain.html#id2550082">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550247">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550274">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550305">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550310">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550373">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550536">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552805">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552815">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552899">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553572">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553608">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553746">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553874">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553970">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554052">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554122">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554205">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554256">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554417">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554589">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554715">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554824">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554939">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555030">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555110">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555181">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555195">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555396">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555646">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555680">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555848">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555937">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555943">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556069">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556148">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556190">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556222">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556460">Well-known RIDS</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="unix-smb.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Attribution�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�NetBIOS in a Unix World</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�The protocol</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="pr01.html" title="Attribution"><link rel="next" href="unix-smb.html" title="Chapter�1.�NetBIOS in a Unix World"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�The protocol</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="unix-smb.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2499093"></a>Part�I.�The protocol</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="unix-smb.html">1. NetBIOS in a Unix World</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-smb.html#id2499122">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499143">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499475">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499506">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498843">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498891">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498923">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498944">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498960">Protocol Complexity</a></span></dt></dl></dd><dt><span class="chapter"><a href="ntdomain.html">2. NT Domain RPC's</a></span></dt><dd><dl><dt><span class="sect1"><a href="ntdomain.html#id2550090">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550255">Sources</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550282">Credits</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2550313">Notes and Structures</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2550318">Notes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550381">Enumerations</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2550543">Structures</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2552813">MSRPC over Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2552823">MSRPC Pipes</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2552907">Header</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553580">Tail</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553616">RPC Bind / Bind Ack</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553755">NTLSA Transact Named Pipe</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553883">LSA Open Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2553978">LSA Query Info Policy</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554060">LSA Enumerate Trusted Domains</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554130">LSA Open Secret</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554213">LSA Close</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554264">LSA Lookup SIDS</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554425">LSA Lookup Names</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2554597">NETLOGON rpc Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2554723">LSA Request Challenge</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554832">LSA Authenticate 2</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2554947">LSA Server Password Set</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555038">LSA SAM Logon</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555118">LSA SAM Logoff</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555189">\\MAILSLOT\NET\NTLOGON</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555203">Query for PDC</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555404">SAM Logon</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555654">SRVSVC Transact Named Pipe</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555688">Net Share Enum</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2555856">Net Server Get Info</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2555945">Cryptographic side of NT Domain Authentication</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2555952">Definitions</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556077">Protocol</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556156">Comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="ntdomain.html#id2556198">SIDs and RIDs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ntdomain.html#id2556230">Well-known SIDs</a></span></dt><dt><span class="sect2"><a href="ntdomain.html#id2556468">Well-known RIDS</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="unix-smb.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Attribution�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�NetBIOS in a Unix World</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pt02.html b/docs/htmldocs/Samba3-Developers-Guide/pt02.html
index acafb8bcaf..c626d195bb 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pt02.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pt02.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Samba Basics</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="ntdomain.html" title="Chapter�2.�NT Domain RPC's"><link rel="next" href="architecture.html" title="Chapter�3.�Samba Architecture"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Samba Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ntdomain.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="architecture.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2556657"></a>Part�II.�Samba Basics</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="architecture.html">3. Samba Architecture</a></span></dt><dd><dl><dt><span class="sect1"><a href="architecture.html#id2556684">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556727">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556759">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556820">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556865">nbmd Design</a></span></dt></dl></dd><dt><span class="chapter"><a href="debug.html">4. The samba DEBUG system</a></span></dt><dd><dl><dt><span class="sect1"><a href="debug.html#id2556921">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557030">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557136">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557172">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557262">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557268">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557284">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557303">format_debug_text()</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="internals.html">5. Samba Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="internals.html#id2557354">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557376">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557505">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557515">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557526">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557537">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557548">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557560">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557572">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557583">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557594">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557606">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557617">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557629">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557640">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557652">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557663">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557675">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557687">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557715">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557840">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557910">Code character table</a></span></dt></dl></dd><dt><span class="chapter"><a href="CodingSuggestions.html">6. Coding Suggestions</a></span></dt><dt><span class="chapter"><a href="contributing.html">7. Contributing code</a></span></dt><dt><span class="chapter"><a href="modules.html">8. Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="modules.html#id2558562">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558600">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558626">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558658">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558682">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558731">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ntdomain.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="architecture.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�NT Domain RPC's�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�3.�Samba Architecture</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Samba Basics</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="ntdomain.html" title="Chapter�2.�NT Domain RPC's"><link rel="next" href="architecture.html" title="Chapter�3.�Samba Architecture"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Samba Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ntdomain.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="architecture.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2556665"></a>Part�II.�Samba Basics</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="architecture.html">3. Samba Architecture</a></span></dt><dd><dl><dt><span class="sect1"><a href="architecture.html#id2556692">Introduction</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556735">Multithreading and Samba</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556767">Threading smbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556828">Threading nmbd</a></span></dt><dt><span class="sect1"><a href="architecture.html#id2556873">nbmd Design</a></span></dt></dl></dd><dt><span class="chapter"><a href="debug.html">4. The samba DEBUG system</a></span></dt><dd><dl><dt><span class="sect1"><a href="debug.html#id2556929">New Output Syntax</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557038">The DEBUG() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557144">The DEBUGADD() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557180">The DEBUGLVL() Macro</a></span></dt><dt><span class="sect1"><a href="debug.html#id2557271">New Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="debug.html#id2557276">dbgtext()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557292">dbghdr()</a></span></dt><dt><span class="sect2"><a href="debug.html#id2557311">format_debug_text()</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="internals.html">5. Samba Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="internals.html#id2557363">Character Handling</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557384">The new functions</a></span></dt><dt><span class="sect1"><a href="internals.html#id2557513">Macros in byteorder.h</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557523">CVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557534">PVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557545">SCVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557556">SVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557568">IVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557580">SVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557591">IVALS(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557603">SSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557614">SIVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557625">SSVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557637">SIVALS(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557648">RSVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557660">RIVAL(buf,pos)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557671">RSSVAL(buf,pos,val)</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557683">RSIVAL(buf,pos,val)</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557696">LAN Manager Samba API</a></span></dt><dd><dl><dt><span class="sect2"><a href="internals.html#id2557723">Parameters</a></span></dt><dt><span class="sect2"><a href="internals.html#id2557848">Return value</a></span></dt></dl></dd><dt><span class="sect1"><a href="internals.html#id2557918">Code character table</a></span></dt></dl></dd><dt><span class="chapter"><a href="CodingSuggestions.html">6. Coding Suggestions</a></span></dt><dt><span class="chapter"><a href="contributing.html">7. Contributing code</a></span></dt><dt><span class="chapter"><a href="modules.html">8. Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="modules.html#id2558570">Advantages</a></span></dt><dt><span class="sect1"><a href="modules.html#id2558608">Loading modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558634">Static modules</a></span></dt><dt><span class="sect2"><a href="modules.html#id2558666">Shared modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="modules.html#id2558690">Writing modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="modules.html#id2558739">Static/Shared selection in configure.in</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ntdomain.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="architecture.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�NT Domain RPC's�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�3.�Samba Architecture</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pt03.html b/docs/htmldocs/Samba3-Developers-Guide/pt03.html
index d92a80d2ed..6811ff0ef1 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pt03.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pt03.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Samba Subsystems</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="modules.html" title="Chapter�8.�Modules"><link rel="next" href="rpc-plugin.html" title="Chapter�9.�RPC Pluggable Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Samba Subsystems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="rpc-plugin.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2558828"></a>Part�III.�Samba Subsystems</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="rpc-plugin.html">9. RPC Pluggable Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558890">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558905">General Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="vfs.html">10. VFS Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="vfs.html#id2559067">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559108">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559434">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559507">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559514">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559659">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559860">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559866">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560270">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560275">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560295">Implement OPAQUE functions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="parsing.html">11. The smb.conf file</a></span></dt><dd><dl><dt><span class="sect1"><a href="parsing.html#id2560352">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560424">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560469">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560520">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560597">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560655">About params.c</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wins.html">12. Samba WINS Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="wins.html#id2560693">WINS Failover</a></span></dt></dl></dd><dt><span class="chapter"><a href="pwencrypt.html">13. LanMan and NT Password Encryption</a></span></dt><dd><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560822">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560842">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560926">The smbpasswd file</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="rpc-plugin.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�8.�Modules�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�9.�RPC Pluggable Modules</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Samba Subsystems</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="modules.html" title="Chapter�8.�Modules"><link rel="next" href="rpc-plugin.html" title="Chapter�9.�RPC Pluggable Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Samba Subsystems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="rpc-plugin.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2558836"></a>Part�III.�Samba Subsystems</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="rpc-plugin.html">9. RPC Pluggable Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558898">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558913">General Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="vfs.html">10. VFS Modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="vfs.html#id2559076">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559117">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559428">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559489">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559495">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559640">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559841">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559847">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560251">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560257">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560276">Implement OPAQUE functions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="parsing.html">11. The smb.conf file</a></span></dt><dd><dl><dt><span class="sect1"><a href="parsing.html#id2560333">Lexical Analysis</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560405">Handling of Whitespace</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560450">Handling of Line Continuation</a></span></dt><dt><span class="sect2"><a href="parsing.html#id2560502">Line Continuation Quirks</a></span></dt></dl></dd><dt><span class="sect1"><a href="parsing.html#id2560579">Syntax</a></span></dt><dd><dl><dt><span class="sect2"><a href="parsing.html#id2560636">About params.c</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wins.html">12. Samba WINS Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="wins.html#id2560674">WINS Failover</a></span></dt></dl></dd><dt><span class="chapter"><a href="pwencrypt.html">13. LanMan and NT Password Encryption</a></span></dt><dd><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560792">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560813">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560896">The smbpasswd file</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="rpc-plugin.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�8.�Modules�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�9.�RPC Pluggable Modules</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pt04.html b/docs/htmldocs/Samba3-Developers-Guide/pt04.html
index 50e9b98295..6e112e9b8c 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pt04.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pt04.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�IV.�Debugging and tracing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="pwencrypt.html" title="Chapter�13.�LanMan and NT Password Encryption"><link rel="next" href="tracing.html" title="Chapter�14.�Tracing samba system calls"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�IV.�Debugging and tracing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pwencrypt.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="tracing.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2561182"></a>Part�IV.�Debugging and tracing</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="tracing.html">14. Tracing samba system calls</a></span></dt><dt><span class="chapter"><a href="devprinting.html">15. Samba Printing Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="devprinting.html#id2561412">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561425">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�IV.�Debugging and tracing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="pwencrypt.html" title="Chapter�13.�LanMan and NT Password Encryption"><link rel="next" href="tracing.html" title="Chapter�14.�Tracing samba system calls"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�IV.�Debugging and tracing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pwencrypt.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="tracing.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2561153"></a>Part�IV.�Debugging and tracing</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="tracing.html">14. Tracing samba system calls</a></span></dt><dt><span class="chapter"><a href="devprinting.html">15. Samba Printing Internals</a></span></dt><dd><dl><dt><span class="sect1"><a href="devprinting.html#id2561382">Abstract</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561395">
 Printing Interface to Various Back ends
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561501">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561471">
 Print Queue TDB's
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561684">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561645">
 ChangeID and Client Caching of Printer Information
-</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561694">
+</a></span></dt><dt><span class="sect1"><a href="devprinting.html#id2561655">
 Windows NT/2K Printer Change Notify
 </a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="pwencrypt.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="tracing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�13.�LanMan and NT Password Encryption�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�14.�Tracing samba system calls</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pt05.html b/docs/htmldocs/Samba3-Developers-Guide/pt05.html
index e158331748..818fc6e9a1 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pt05.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pt05.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�V.�Appendices</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="devprinting.html" title="Chapter�15.�Samba Printing Internals"><link rel="next" href="Packaging.html" title="Chapter�16.�Notes to packagers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�V.�Appendices</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="devprinting.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="Packaging.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2561984"></a>Part�V.�Appendices</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="Packaging.html">16. Notes to packagers</a></span></dt><dd><dl><dt><span class="sect1"><a href="Packaging.html#id2562007">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562040">Modules</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="devprinting.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="Packaging.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�15.�Samba Printing Internals�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�16.�Notes to packagers</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�V.�Appendices</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="index.html" title="SAMBA Developers Guide"><link rel="prev" href="devprinting.html" title="Chapter�15.�Samba Printing Internals"><link rel="next" href="Packaging.html" title="Chapter�16.�Notes to packagers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�V.�Appendices</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="devprinting.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="Packaging.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2561951"></a>Part�V.�Appendices</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="Packaging.html">16. Notes to packagers</a></span></dt><dd><dl><dt><span class="sect1"><a href="Packaging.html#id2561975">Versioning</a></span></dt><dt><span class="sect1"><a href="Packaging.html#id2562008">Modules</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="devprinting.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="Packaging.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�15.�Samba Printing Internals�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�16.�Notes to packagers</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html b/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html
index cc30ca2611..0be7dc0409 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html
@@ -1,12 +1,12 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�13.�LanMan and NT Password Encryption</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="wins.html" title="Chapter�12.�Samba WINS Internals"><link rel="next" href="pt04.html" title="Part�IV.�Debugging and tracing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�13.�LanMan and NT Password Encryption</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="wins.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="pt04.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pwencrypt"></a>Chapter�13.�LanMan and NT Password Encryption</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><br>
 				<code class="email">&lt;<a class="email" href="mailto:samba@samba.org">samba@samba.org</a>&gt;</code><br>
-			</p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560822">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560842">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560926">The smbpasswd file</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560822"></a>Introduction</h2></div></div></div><p>With the development of LanManager and Windows NT 
+			</p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pwencrypt.html#id2560792">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560813">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2560896">The smbpasswd file</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560792"></a>Introduction</h2></div></div></div><p>With the development of LanManager and Windows NT 
 	compatible password encryption for Samba, it is now able 
 	to validate user connections in exactly the same way as 
 	a LanManager or Windows NT server.</p><p>This document describes how the SMB password encryption 
 	algorithm works and what issues there are in choosing whether 
 	you want to use it. You should read it carefully, especially 
-	the part about security and the "PROS and CONS" section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560842"></a>How does it work?</h2></div></div></div><p>LanManager encryption is somewhat similar to UNIX 
+	the part about security and the "PROS and CONS" section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560813"></a>How does it work?</h2></div></div></div><p>LanManager encryption is somewhat similar to UNIX 
 	password encryption. The server uses a file containing a 
 	hashed value of a user's password.  This is created by taking 
 	the user's plaintext password, capitalising it, and either 
@@ -43,7 +43,7 @@
 	know the correct password and is denied access.</p><p>Note that the Samba server never knows or stores the cleartext 
 	of the user's password - just the 16 byte hashed values derived from 
 	it. Also note that the cleartext password or 16 byte hashed values 
-	are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560926"></a>The smbpasswd file</h2></div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol 
+	are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560896"></a>The smbpasswd file</h2></div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol 
 	it must be able to look up the 16 byte hashed values given a user name.
 	Unfortunately, as the UNIX password value is also a one way hash
 	function (ie. it is impossible to retrieve the cleartext of the user's
diff --git a/docs/htmldocs/Samba3-Developers-Guide/rpc-plugin.html b/docs/htmldocs/Samba3-Developers-Guide/rpc-plugin.html
index e129d44bc0..52ca69607c 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/rpc-plugin.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/rpc-plugin.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�RPC Pluggable Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="next" href="vfs.html" title="Chapter�10.�VFS Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�RPC Pluggable Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt03.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="vfs.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rpc-plugin"></a>Chapter�9.�RPC Pluggable Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="orgname">IBM</span> <span class="surname">Liguori</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="orgname">Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">January 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558890">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558905">General Overview</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558890"></a>About</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�RPC Pluggable Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="next" href="vfs.html" title="Chapter�10.�VFS Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�RPC Pluggable Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt03.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="vfs.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rpc-plugin"></a>Chapter�9.�RPC Pluggable Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="orgname">IBM</span> <span class="surname">Liguori</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="orgname">Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">January 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="rpc-plugin.html#id2558898">About</a></span></dt><dt><span class="sect1"><a href="rpc-plugin.html#id2558913">General Overview</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558898"></a>About</h2></div></div></div><p>
 This document describes how to make use the new RPC Pluggable Modules features
 of Samba 3.0.  This architecture was added to increase the maintainability of
 Samba allowing RPC Pipes to be worked on separately from the main CVS branch.
 The RPM architecture will also allow third-party vendors to add functionality
 to Samba through plug-ins.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558905"></a>General Overview</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558913"></a>General Overview</h2></div></div></div><p>
 When an RPC call is sent to smbd, smbd tries to load a shared library by the
 name <code class="filename">librpc_&lt;pipename&gt;.so</code> to handle the call if
 it doesn't know how to handle the call internally.  For instance, LSA calls
diff --git a/docs/htmldocs/Samba3-Developers-Guide/unix-smb.html b/docs/htmldocs/Samba3-Developers-Guide/unix-smb.html
index 0b25a15541..2c574c4d30 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/unix-smb.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/unix-smb.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�NetBIOS in a Unix World</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt01.html" title="Part�I.�The protocol"><link rel="prev" href="pt01.html" title="Part�I.�The protocol"><link rel="next" href="ntdomain.html" title="Chapter�2.�NT Domain RPC's"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�NetBIOS in a Unix World</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt01.html">Prev</a>�</td><th width="60%" align="center">Part�I.�The protocol</th><td width="20%" align="right">�<a accesskey="n" href="ntdomain.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unix-smb"></a>Chapter�1.�NetBIOS in a Unix World</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3></div></div><div><p class="pubdate">April 1995</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unix-smb.html#id2499107">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499128">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499459">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499491">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498824">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498876">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498908">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498929">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2549963">Protocol Complexity</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499107"></a>Introduction</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�NetBIOS in a Unix World</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt01.html" title="Part�I.�The protocol"><link rel="prev" href="pt01.html" title="Part�I.�The protocol"><link rel="next" href="ntdomain.html" title="Chapter�2.�NT Domain RPC's"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�NetBIOS in a Unix World</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pt01.html">Prev</a>�</td><th width="60%" align="center">Part�I.�The protocol</th><td width="20%" align="right">�<a accesskey="n" href="ntdomain.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unix-smb"></a>Chapter�1.�NetBIOS in a Unix World</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3></div></div><div><p class="pubdate">April 1995</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unix-smb.html#id2499122">Introduction</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499143">Usernames</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499475">File Ownership</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2499506">Passwords</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498843">Locking</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498891">Deny Modes</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498923">Trapdoor UIDs</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498944">Port numbers</a></span></dt><dt><span class="sect1"><a href="unix-smb.html#id2498960">Protocol Complexity</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499122"></a>Introduction</h2></div></div></div><p>
 This is a short document that describes some of the issues that
 confront a SMB implementation on unix, and how Samba copes with
 them. They may help people who are looking at unix&lt;-&gt;PC
@@ -6,7 +6,7 @@ interoperability.
 </p><p>
 It was written to help out a person who was writing a paper on unix to
 PC connectivity.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499128"></a>Usernames</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499143"></a>Usernames</h2></div></div></div><p>
 The SMB protocol has only a loose username concept. Early SMB
 protocols (such as CORE and COREPLUS) have no username concept at
 all. Even in later protocols clients often attempt operations
@@ -43,7 +43,7 @@ in the vast majority of cases. The methods include username maps, the
 service%user syntax, the saving of session setup usernames for later
 validation and the derivation of the username from the service name
 (either directly or via the user= option).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499459"></a>File Ownership</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499475"></a>File Ownership</h2></div></div></div><p>
 The commonly used SMB protocols have no way of saying "you can't do
 that because you don't own the file". They have, in fact, no concept
 of file ownership at all.
@@ -61,7 +61,7 @@ file time comparisons right.
 There are several possible solutions to this problem, including
 username mapping, and forcing a specific username for particular
 shares.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499491"></a>Passwords</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2499506"></a>Passwords</h2></div></div></div><p>
 Many SMB clients uppercase passwords before sending them. I have no
 idea why they do this. Interestingly WfWg uppercases the password only
 if the server is running a protocol greater than COREPLUS, so
@@ -83,7 +83,7 @@ This means that it is *VERY* important to ensure that the Samba
 smbpasswd file containing these password hashes is only readable
 by the root user. See the documentation ENCRYPTION.txt for more
 details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498824"></a>Locking</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498843"></a>Locking</h2></div></div></div><p>
 Since samba 2.2, samba supports other types of locking as well. This 
 section is outdated.
 </p><p>
@@ -114,7 +114,7 @@ asking the server to notify it if anyone else tries to do something on
 the same file, at which time the client will say if it is willing to
 give up its lock. Unix has no simple way of implementing
 opportunistic locking, and currently Samba has no support for it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498876"></a>Deny Modes</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498891"></a>Deny Modes</h2></div></div></div><p>
 When a SMB client opens a file it asks for a particular "deny mode" to
 be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE,
 DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be
@@ -128,7 +128,7 @@ directory or a shared memory implementation. The lock file method
 is clumsy and consumes processing and file resources,
 the shared memory implementation is vastly prefered and is turned on
 by default for those systems that support it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498908"></a>Trapdoor UIDs</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498923"></a>Trapdoor UIDs</h2></div></div></div><p>
 A SMB session can run with several uids on the one socket. This
 happens when a user connects to two shares with different
 usernames. To cope with this the unix server needs to switch uids
@@ -138,7 +138,7 @@ a single uid.
 </p><p>
 Note that you can also get the "trapdoor uid" message for other
 reasons. Please see the FAQ for details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498929"></a>Port numbers</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498944"></a>Port numbers</h2></div></div></div><p>
 There is a convention that clients on sockets use high "unprivileged"
 port numbers (&gt;1000) and connect to servers on low "privilegedg" port
 numbers. This is enforced in Unix as non-root users can't open a
@@ -161,7 +161,7 @@ to any of these OSes unless they are running as root. The answer comes
 back, but it goes to port 137 which the unix user can't listen
 on. Interestingly WinNT3.1 got this right - it sends node status
 responses back to the source port in the request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2549963"></a>Protocol Complexity</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498960"></a>Protocol Complexity</h2></div></div></div><p>
 There are many "protocol levels" in the SMB protocol. It seems that
 each time new functionality was added to a Microsoft operating system,
 they added the equivalent functions in a new protocol level of the SMB
diff --git a/docs/htmldocs/Samba3-Developers-Guide/vfs.html b/docs/htmldocs/Samba3-Developers-Guide/vfs.html
index f94bdb7c87..a0c8607dd4 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/vfs.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/vfs.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�VFS Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="rpc-plugin.html" title="Chapter�9.�RPC Pluggable Modules"><link rel="next" href="parsing.html" title="Chapter�11.�The smb.conf file"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�VFS Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rpc-plugin.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="parsing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="vfs"></a>Chapter�10.�VFS Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:ab@samba.org">ab@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:metze@samba.org">metze@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 27 May 2003 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="vfs.html#id2559067">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559108">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559434">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559507">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559514">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559659">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559860">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559866">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560270">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560275">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560295">Implement OPAQUE functions</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559067"></a>The Samba (Posix) VFS layer</h2></div></div></div><p>While most of Samba deployments are done using POSIX-compatible
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�VFS Modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="rpc-plugin.html" title="Chapter�9.�RPC Pluggable Modules"><link rel="next" href="parsing.html" title="Chapter�11.�The smb.conf file"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�VFS Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rpc-plugin.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="parsing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="vfs"></a>Chapter�10.�VFS Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:ab@samba.org">ab@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:metze@samba.org">metze@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 27 May 2003 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="vfs.html#id2559076">The Samba (Posix) VFS layer</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559117">The general interface</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559428">Possible VFS operation layers</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559489">The Interaction between the Samba VFS subsystem and the modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559495">Initialization and registration</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2559640">How the Modules handle per connection data</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2559841">Upgrading to the New VFS Interface</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2559847">Upgrading from 2.2.* and 3.0alpha modules</a></span></dt></dl></dd><dt><span class="sect1"><a href="vfs.html#id2560251">Some Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="vfs.html#id2560257">Implement TRANSPARENT functions</a></span></dt><dt><span class="sect2"><a href="vfs.html#id2560276">Implement OPAQUE functions</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559076"></a>The Samba (Posix) VFS layer</h2></div></div></div><p>While most of Samba deployments are done using POSIX-compatible
 operating systems, there is clearly more to a file system than what is
 required by POSIX when it comes to adopting semantics of NT file
 system. Since Samba 2.2 all file-system related operations go through
@@ -24,13 +24,13 @@ information that is specific to a context it is operating in. Multiple
 VFS modules could be loaded at the same time and it is even possible
 to load several instances of the same VFS module with different
 parameters.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559108"></a>The general interface</h3></div></div></div><p>A VFS module has three major components:
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>An initialization function</em></span> that is
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559117"></a>The general interface</h3></div></div></div><p>A VFS module has three major components:
+</p><div class="itemizedlist"><ul type="disc"><li><span class="emphasis"><em>An initialization function</em></span> that is
 called during the module load to register implemented
-operations.</p></li><li><p><span class="emphasis"><em>An operations table</em></span> representing a
+operations.</li><li><span class="emphasis"><em>An operations table</em></span> representing a
 mapping between statically defined module functions and VFS layer
-operations.</p></li><li><p><span class="emphasis"><em>Module functions</em></span> that do actual
-		work.</p></li></ul></div><p>
+operations.</li><li><span class="emphasis"><em>Module functions</em></span> that do actual
+work.</li></ul></div><p>
 </p><p>While this structure has been first applied to the VFS
 subsystem, it is now commonly used across all Samba 3 subsystems that
 support loadable modules. In fact, one module could provide a number
@@ -49,37 +49,38 @@ conflict is detected and module dropped to avoid any potential memory
 corruption when accessing (changed) Samba structures.
 </p><p>Therefore, initialization function passes three parameters to the
 VFS registration function, <code class="literal">smb_register_vfs()</code>
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>interface version number</em></span>, as constant
-			<code class="literal">SMB_VFS_INTERFACE_VERSION</code>, </p></li><li><p><span class="emphasis"><em>module name</em></span>, under which Samba core
-			will know it, and</p></li><li><p><span class="emphasis"><em>an operations' table</em></span>.</p></li></ul></div><p>
+</p><div class="itemizedlist"><ul type="disc"><li><span class="emphasis"><em>interface version number</em></span>, as constant
+  <code class="literal">SMB_VFS_INTERFACE_VERSION</code>, </li><li><span class="emphasis"><em>module name</em></span>, under which Samba core
+  will know it, and</li><li><span class="emphasis"><em>an operations' table</em></span>.</li></ul></div><p>
 </p><p>The <span class="emphasis"><em>operations' table</em></span> defines which
 functions in the module would correspond to specific VFS operations
 and how those functions would co-operate with the rest of VFS
 subsystem. Each operation could perform in a following ways:
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>transparent</em></span>, meaning that while
+</p><div class="itemizedlist"><ul type="disc"><li><span class="emphasis"><em>transparent</em></span>, meaning that while
   operation is overriden, the module will still call a previous
   implementation, before or after its own action. This mode is
   indicated by the constant
-  <code class="literal">SMB_VFS_LAYER_TRANSPARENT</code>;</p></li><li><p><span class="emphasis"><em>opaque</em></span>, for the implementations that
+  <code class="literal">SMB_VFS_LAYER_TRANSPARENT</code>;
+  </li><li><span class="emphasis"><em>opaque</em></span>, for the implementations that
   are terminating sequence of actions. For example, it is used to
   implement POSIX operation on top of non-POSIX file system or even
   not a file system at all, like a database for a personal audio
   collection. Use constant <code class="literal">SMB_VFS_LAYER_OPAQUE</code> for
-  this mode;</p></li><li><p><span class="emphasis"><em>splitter</em></span>, a way when some file system
+  this mode;</li><li><span class="emphasis"><em>splitter</em></span>, a way when some file system
   activity is done in addition to the transparently calling previous
   implentation. This usually involves mangling the result of that call
   before returning it back to the caller. This mode is selected by
-  <code class="literal">SMB_VFS_LAYER_SPLITTER</code> constant;</p></li><li><p><span class="emphasis"><em>logger</em></span> does not change anything or
+  <code class="literal">SMB_VFS_LAYER_SPLITTER</code> constant;</li><li><span class="emphasis"><em>logger</em></span> does not change anything or
   performs any additional VFS operations. When
   <span class="emphasis"><em>logger</em></span> module acts, information about
   operations is logged somewhere using an external facility (or
   Samba's own debugging tools) but not the VFS layer. In order to
   describe this type of activity use constant
   <code class="literal">SMB_VFS_LAYER_LOGGER</code>;
-  </p></li><li><p>On contrary, <span class="emphasis"><em>scanner</em></span> module does call
+  </li><li>On contrary, <span class="emphasis"><em>scanner</em></span> module does call
   other VFS operations while processing the data that goes through the
   system. This type of operation is indicated by the
-  <code class="literal">SMB_VFS_LAYER_SCANNER</code> constant.</p></li></ul></div><p>
+  <code class="literal">SMB_VFS_LAYER_SCANNER</code> constant.</li></ul></div><p>
 </p><p>Fundamentally, there are three types:
 <span class="emphasis"><em>transparent</em></span>, <span class="emphasis"><em>opaque</em></span>, and
 <span class="emphasis"><em>logger</em></span>. <span class="emphasis"><em>Splitter</em></span> and
@@ -186,7 +187,7 @@ DO NOT ACCESS conn-&gt;vfs.ops.* directly !!!
 	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
 
 ...
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559434"></a>Possible VFS operation layers</h3></div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559428"></a>Possible VFS operation layers</h3></div></div></div><p>
 These values are used by the VFS subsystem when building the conn-&gt;vfs 
 and conn-&gt;vfs_opaque structs for a connection with multiple VFS modules. 
 Internally, Samba differentiates only opaque and transparent layers at this process.
@@ -215,7 +216,7 @@ typedef enum _vfs_op_layer {
 	SMB_VFS_LAYER_SCANNER		/* - Checks data and possibly initiates additional */
 					/*   file activity like logging to files _inside_ samba VFS */
 } vfs_op_layer;
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559507"></a>The Interaction between the Samba VFS subsystem and the modules</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559514"></a>Initialization and registration</h3></div></div></div><p>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559489"></a>The Interaction between the Samba VFS subsystem and the modules</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559495"></a>Initialization and registration</h3></div></div></div><p>
 As each Samba module a VFS module should have a 
 </p><pre class="programlisting">NTSTATUS vfs_example_init(void);</pre><p> function if it's staticly linked to samba or
 </p><pre class="programlisting">NTSTATUS init_module(void);</pre><p> function if it's a shared module.
@@ -255,7 +256,7 @@ NTSTATUS init_module(void)
 {
 	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, "example", example_op_tuples);
 }
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559659"></a>How the Modules handle per connection data</h3></div></div></div><p>Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559640"></a>How the Modules handle per connection data</h3></div></div></div><p>Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
 </p><pre class="programlisting">
 typedef struct vfs_handle_struct {
 	struct vfs_handle_struct  *next, *prev;
@@ -356,7 +357,7 @@ you can set this function pointer to NULL.</p></dd></dl></div><p>Some useful MAC
 	(handle)-&gt;vfs_next.handles.sendfile,\
 	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
 ...
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559860"></a>Upgrading to the New VFS Interface</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559866"></a>Upgrading from 2.2.* and 3.0alpha modules</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559841"></a>Upgrading to the New VFS Interface</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559847"></a>Upgrading from 2.2.* and 3.0alpha modules</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p>
 Add "vfs_handle_struct *handle, " as first parameter to all vfs operation functions.
 e.g. example_connect(connection_struct *conn, const char *service, const char *user);
 -&gt;   example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user);
@@ -619,7 +620,7 @@ for your module.
 </p></li><li><p>
 Compiling &amp; Testing...
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><strong class="userinput"><code>./configure <code class="option">--enable-developer</code></code></strong> ...</td></tr><tr><td><strong class="userinput"><code>make</code></strong></td></tr><tr><td>Try to fix all compiler warnings</td></tr><tr><td><strong class="userinput"><code>make</code></strong></td></tr><tr><td>Testing, Testing, Testing ...</td></tr></table><p>
-</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560270"></a>Some Notes</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560275"></a>Implement TRANSPARENT functions</h3></div></div></div><p>
+</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560251"></a>Some Notes</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560257"></a>Implement TRANSPARENT functions</h3></div></div></div><p>
 Avoid writing functions like this:
 
 </p><pre class="programlisting">
@@ -630,7 +631,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
 </pre><p>
 
 Overload only the functions you really need to!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560295"></a>Implement OPAQUE functions</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560276"></a>Implement OPAQUE functions</h3></div></div></div><p>
 If you want to just implement a better version of a 
 default samba opaque function
 (e.g. like a disk_free() function for a special filesystem) 
diff --git a/docs/htmldocs/Samba3-Developers-Guide/wins.html b/docs/htmldocs/Samba3-Developers-Guide/wins.html
index 73a8ffa08b..ea61d8f634 100644
--- a/docs/htmldocs/Samba3-Developers-Guide/wins.html
+++ b/docs/htmldocs/Samba3-Developers-Guide/wins.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Samba WINS Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="parsing.html" title="Chapter�11.�The smb.conf file"><link rel="next" href="pwencrypt.html" title="Chapter�13.�LanMan and NT Password Encryption"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Samba WINS Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="parsing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="pwencrypt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wins"></a>Chapter�12.�Samba WINS Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="wins.html#id2560693">WINS Failover</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560693"></a>WINS Failover</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Samba WINS Internals</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part�III.�Samba Subsystems"><link rel="prev" href="parsing.html" title="Chapter�11.�The smb.conf file"><link rel="next" href="pwencrypt.html" title="Chapter�13.�LanMan and NT Password Encryption"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Samba WINS Internals</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="parsing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Samba Subsystems</th><td width="20%" align="right">�<a accesskey="n" href="pwencrypt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wins"></a>Chapter�12.�Samba WINS Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="wins.html#id2560674">WINS Failover</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560674"></a>WINS Failover</h2></div></div></div><p>
 The current Samba codebase possesses the capability to use groups of WINS
 servers that share a common namespace for NetBIOS name registration and 
 resolution.  The formal parameter syntax is
diff --git a/docs/htmldocs/Samba3-HOWTO/AccessControls.html b/docs/htmldocs/Samba3-HOWTO/AccessControls.html
index 92313a7623..68d034db92 100644
--- a/docs/htmldocs/Samba3-HOWTO/AccessControls.html
+++ b/docs/htmldocs/Samba3-HOWTO/AccessControls.html
@@ -1,59 +1,59 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�File, Directory, and Share Access Controls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="rights.html" title="Chapter�15.�User Rights and Privileges"><link rel="next" href="locking.html" title="Chapter�17.�File and Record Locking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�File, Directory, and Share Access Controls</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rights.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="locking.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter�16.�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="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</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><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AccessControls.html#id2610562">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610748">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611105">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611229">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611888">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611921">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612289">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612626">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612964">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613112">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613459">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613465">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613512">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613583">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613726">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613942">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614099">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614468">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614541">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614954">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614965">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615288">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615334">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2610392"></a>
-<a class="indexterm" name="id2610399"></a>
-<a class="indexterm" name="id2610406"></a>
-<a class="indexterm" name="id2610413"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�16.�File, Directory, and Share Access Controls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="rights.html" title="Chapter�15.�User Rights and Privileges"><link rel="next" href="locking.html" title="Chapter�17.�File and Record Locking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�16.�File, Directory, and Share Access Controls</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rights.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="locking.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter�16.�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="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</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><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AccessControls.html#id2610564">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610751">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611102">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611225">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611896">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611929">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612297">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612634">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612972">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613120">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613466">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613473">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613520">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613591">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613735">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613950">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614107">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614477">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614550">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614968">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614980">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615303">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615348">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2610395"></a>
+<a class="indexterm" name="id2610402"></a>
+<a class="indexterm" name="id2610408"></a>
+<a class="indexterm" name="id2610415"></a>
 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 unauthorized access.
 </p><p>
-<a class="indexterm" name="id2610429"></a>
-<a class="indexterm" name="id2610436"></a>
+<a class="indexterm" name="id2610432"></a>
+<a class="indexterm" name="id2610439"></a>
 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>
-<a class="indexterm" name="id2610451"></a>
-<a class="indexterm" name="id2610457"></a>
-<a class="indexterm" name="id2610464"></a>
-<a class="indexterm" name="id2610471"></a>
+<a class="indexterm" name="id2610453"></a>
+<a class="indexterm" name="id2610460"></a>
+<a class="indexterm" name="id2610467"></a>
+<a class="indexterm" name="id2610474"></a>
 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 cannot completely hide, even
 though it does try to bridge the chasm to a degree.
 </p><p>
-<a class="indexterm" name="id2610484"></a>
-<a class="indexterm" name="id2610491"></a>
-<a class="indexterm" name="id2610500"></a>
-<a class="indexterm" name="id2610507"></a>
+<a class="indexterm" name="id2610487"></a>
+<a class="indexterm" name="id2610494"></a>
+<a class="indexterm" name="id2610503"></a>
+<a class="indexterm" name="id2610510"></a>
 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>
-<a class="indexterm" name="id2610524"></a>
+<a class="indexterm" name="id2610527"></a>
 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>
-<a class="indexterm" name="id2610539"></a>
-<a class="indexterm" name="id2610546"></a>
+<a class="indexterm" name="id2610542"></a>
+<a class="indexterm" name="id2610549"></a>
 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 to 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="id2610562"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610564"></a>Features and Benefits</h2></div></div></div><p>
 	Samba offers much 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>
-		<a class="indexterm" name="id2610582"></a>
+		<a class="indexterm" name="id2610585"></a>
 		<span class="emphasis"><em>UNIX File and Directory Permissions</em></span>
 		</p><p>
-<a class="indexterm" name="id2610599"></a>
-<a class="indexterm" name="id2610606"></a>
-<a class="indexterm" name="id2610613"></a>
+<a class="indexterm" name="id2610602"></a>
+<a class="indexterm" name="id2610609"></a>
+<a class="indexterm" name="id2610616"></a>
 			Samba honors 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
@@ -64,7 +64,7 @@ beyond early plans and expectations, yet the gap continues to shrink.
 			</p></li><li><p>
 		<span class="emphasis"><em>Samba Share Definitions</em></span>
 		</p><p>
-<a class="indexterm" name="id2610641"></a>
+<a class="indexterm" name="id2610644"></a>
 			In configuring share settings and controls in the <code class="filename">smb.conf</code> file,
 			the network administrator can exercise overrides to native file
 			system permissions and behaviors. This can be handy and convenient
@@ -73,20 +73,20 @@ beyond early plans and expectations, yet the gap continues to shrink.
 			The basic options and techniques are described herein.
 			</p></li><li><p>
 		<span class="emphasis"><em>Samba Share ACLs</em></span>
-		<a class="indexterm" name="id2610673"></a>
+		<a class="indexterm" name="id2610676"></a>
 		</p><p>
-<a class="indexterm" name="id2610685"></a>
+<a class="indexterm" name="id2610688"></a>
 			Just as it is possible in MS Windows NT to set ACLs on shares
 			themselves, so it is possible to do in Samba.
 			Few people make use of this facility, yet it remains one 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>
-				<a class="indexterm" name="id2610703"></a>
-				<a class="indexterm" name="id2610712"></a>
+				<a class="indexterm" name="id2610706"></a>
+				<a class="indexterm" name="id2610715"></a>
 		<span class="emphasis"><em>MS Windows ACLs through UNIX POSIX ACLs</em></span>
 		</p><p>
-<a class="indexterm" name="id2610729"></a>
+<a class="indexterm" name="id2610731"></a>
 			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
@@ -94,16 +94,16 @@ beyond early plans and expectations, yet the gap continues to shrink.
 			this support. 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="id2610748"></a>File System Access Controls</h2></div></div></div><p>
+			</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610751"></a>File System Access Controls</h2></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. First we consider what the most significant differences are, then we look
 at how Samba helps to bridge the differences.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2610763"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div></div><p>
-	<a class="indexterm" name="id2610771"></a>
-	<a class="indexterm" name="id2610778"></a>
-	<a class="indexterm" name="id2610785"></a>
-	<a class="indexterm" name="id2610794"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2610766"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div></div><p>
+	<a class="indexterm" name="id2610774"></a>
+	<a class="indexterm" name="id2610781"></a>
+	<a class="indexterm" name="id2610788"></a>
+	<a class="indexterm" name="id2610797"></a>
 	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
 	behavior, that differs from UNIX file system behavior then somehow Samba is responsible for emulating
@@ -114,7 +114,7 @@ at how Samba helps to bridge the differences.
 	but for the greater part we stay within the bounds of default behavior. Those wishing to explore
 	the depths of control ability should review the <code class="filename">smb.conf</code> man page.
 	</p><p>The following compares file system features for UNIX with those of MS Windows NT/200x:
-	<a class="indexterm" name="id2610835"></a>
+	<a class="indexterm" name="id2610832"></a>
 	
 	</p><div class="variablelist"><dl><dt><span class="term">Name Space</span></dt><dd><p>
 		MS Windows NT4/200x/XP file names may be up to 254 characters long, and UNIX file names
@@ -123,8 +123,8 @@ at how Samba helps to bridge the differences.
 		</p><p>
 		What MS Windows calls a folder, UNIX calls a directory.
 		</p></dd><dt><span class="term">Case Sensitivity</span></dt><dd><p>
-		<a class="indexterm" name="id2610880"></a>
-		<a class="indexterm" name="id2610887"></a>
+		<a class="indexterm" name="id2610877"></a>
+		<a class="indexterm" name="id2610884"></a>
 		MS Windows file names are generally uppercase if made up of 8.3 (8-character file name
 		and 3 character extension. File names that are longer than 8.3 are case preserving and case
 		insensitive.
@@ -151,26 +151,26 @@ at how Samba helps to bridge the differences.
 		event that the UNIX directory contains multiple files that would match a case insensitive
 		file listing.
 		</p></dd><dt><span class="term">Directory Separators</span></dt><dd><p>
-		<a class="indexterm" name="id2610951"></a>
+		<a class="indexterm" name="id2610948"></a>
 		MS Windows and DOS use the backslash <code class="constant">\</code> as a directory delimiter, and UNIX uses
 		the forward-slash <code class="constant">/</code> as its directory delimiter. This is handled transparently by Samba.
 		</p></dd><dt><span class="term">Drive Identification</span></dt><dd><p>
-		<a class="indexterm" name="id2610979"></a>
+		<a class="indexterm" name="id2610976"></a>
 		MS Windows products support a notion of drive letters, like <code class="literal">C:</code>, to represent
 		disk partitions. UNIX has no concept of separate identifiers for file partitions; each
 		such file system is mounted to become part of the overall directory tree.
 		The UNIX directory tree begins at <code class="constant">/</code> just as the root of a DOS drive is specified as
 		<code class="constant">C:\</code>.
 		</p></dd><dt><span class="term">File Naming Conventions</span></dt><dd><p>
-		<a class="indexterm" name="id2611016"></a>
+		<a class="indexterm" name="id2611013"></a>
 		MS Windows generally never experiences file names that begin with a dot (<code class="constant">.</code>), while in UNIX these
 		are commonly found in a user's home directory. Files that begin with a dot (<code class="constant">.</code>) are typically
 		startup files for various UNIX applications, or they may be files that contain
 		startup configuration data.
 		</p></dd><dt><span class="term">Links and Short-Cuts</span></dt><dd><p>
-		<a class="indexterm" name="id2611046"></a>
-		<a class="indexterm" name="id2611056"></a>
-		<a class="indexterm" name="id2611065"></a>
+		<a class="indexterm" name="id2611043"></a>
+		<a class="indexterm" name="id2611052"></a>
+		<a class="indexterm" name="id2611061"></a>
 		MS Windows make use of <span class="emphasis"><em>links and shortcuts</em></span> 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.
@@ -183,17 +183,17 @@ at how Samba helps to bridge the differences.
 	There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort
 	in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the
 	purpose of UNIX/Linux training and education.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611105"></a>Managing Directories</h3></div></div></div><p>
-<a class="indexterm" name="id2611113"></a>
-<a class="indexterm" name="id2611120"></a>
-<a class="indexterm" name="id2611127"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611102"></a>Managing Directories</h3></div></div></div><p>
+<a class="indexterm" name="id2611110"></a>
+<a class="indexterm" name="id2611117"></a>
+<a class="indexterm" name="id2611124"></a>
 	There are three basic operations for managing directories: <code class="literal">create</code>, <code class="literal">delete</code>,
 	<code class="literal">rename</code>. <a class="link" href="AccessControls.html#TOSH-Accesstbl" title="Table�16.1.�Managing Directories with UNIX and Windows">Managing Directories with UNIX and
 	Windows</a> compares the commands in Windows and UNIX that implement these operations.
-	</p><div class="table"><a name="TOSH-Accesstbl"></a><p class="title"><b>Table�16.1.�Managing Directories with UNIX and Windows</b></p><div class="table-contents"><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></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611229"></a>File and Directory Access Control</h3></div></div></div><p>
-	<a class="indexterm" name="id2611237"></a>
-<a class="indexterm" name="id2611246"></a>
-<a class="indexterm" name="id2611253"></a>
+	</p><div class="table"><a name="TOSH-Accesstbl"></a><p class="title"><b>Table�16.1.�Managing Directories with UNIX and Windows</b></p><div class="table-contents"><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></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611225"></a>File and Directory Access Control</h3></div></div></div><p>
+	<a class="indexterm" name="id2611234"></a>
+<a class="indexterm" name="id2611243"></a>
+<a class="indexterm" name="id2611250"></a>
 	The network administrator is strongly advised to read basic UNIX 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 ACLs or extended attributes (EAs).
@@ -226,47 +226,47 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	</p><div class="figure"><a name="access1"></a><p class="title"><b>Figure�16.1.�Overview of UNIX permissions field.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/access1.png" width="216" alt="Overview of UNIX permissions field."></div></div></div><br class="figure-break"><p>
 		Any bit flag may be unset. An unset bit flag is the equivalent of "cannot" and is represented
 		as a &#8220;<span class="quote">-</span>&#8221; character (see <a class="link" href="AccessControls.html#access2" title="Example�16.1.�Example File">&#8220;Example File&#8221;</a>)
-<a class="indexterm" name="id2611381"></a>
-<a class="indexterm" name="id2611388"></a>
-<a class="indexterm" name="id2611395"></a>
-<a class="indexterm" name="id2611402"></a>
-<a class="indexterm" name="id2611408"></a>
-<a class="indexterm" name="id2611415"></a>
+<a class="indexterm" name="id2611391"></a>
+<a class="indexterm" name="id2611398"></a>
+<a class="indexterm" name="id2611405"></a>
+<a class="indexterm" name="id2611412"></a>
+<a class="indexterm" name="id2611418"></a>
+<a class="indexterm" name="id2611425"></a>
 	</p><div class="example"><a name="access2"></a><p class="title"><b>Example�16.1.�Example File</b></p><div class="example-contents"><pre class="programlisting">
 -rwxr-x---   Means: 
  ^^^                The owner (user) can read, write, execute
     ^^^             the group can read and execute
        ^^^          everyone else cannot do anything with it.
 </pre></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2611445"></a>
-<a class="indexterm" name="id2611452"></a>
-<a class="indexterm" name="id2611458"></a>
-<a class="indexterm" name="id2611465"></a>
+<a class="indexterm" name="id2611455"></a>
+<a class="indexterm" name="id2611462"></a>
+<a class="indexterm" name="id2611468"></a>
+<a class="indexterm" name="id2611475"></a>
 	Additional possibilities in the [type] field are c = character device, b = block device, p = pipe device,
 	s = UNIX Domain Socket.
 	</p><p>
-<a class="indexterm" name="id2611478"></a>
-<a class="indexterm" name="id2611485"></a>
-<a class="indexterm" name="id2611491"></a>
-<a class="indexterm" name="id2611498"></a>
-<a class="indexterm" name="id2611505"></a>
+<a class="indexterm" name="id2611488"></a>
+<a class="indexterm" name="id2611495"></a>
+<a class="indexterm" name="id2611501"></a>
+<a class="indexterm" name="id2611508"></a>
+<a class="indexterm" name="id2611515"></a>
 	The letters <code class="constant">rwxXst</code> 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 (SUID) or group ID (SGID) on execution (s), sticky (t).
 	</p><p>
-<a class="indexterm" name="id2611524"></a>
-<a class="indexterm" name="id2611530"></a>
-<a class="indexterm" name="id2611537"></a>
-<a class="indexterm" name="id2611544"></a>
+<a class="indexterm" name="id2611534"></a>
+<a class="indexterm" name="id2611540"></a>
+<a class="indexterm" name="id2611547"></a>
+<a class="indexterm" name="id2611554"></a>
 	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 <code class="filename">/tmp</code>, that are world-writable.
 	</p><p>
-<a class="indexterm" name="id2611566"></a>
-<a class="indexterm" name="id2611572"></a>
-<a class="indexterm" name="id2611579"></a>
-<a class="indexterm" name="id2611586"></a>
-<a class="indexterm" name="id2611595"></a>
+<a class="indexterm" name="id2611580"></a>
+<a class="indexterm" name="id2611587"></a>
+<a class="indexterm" name="id2611594"></a>
+<a class="indexterm" name="id2611601"></a>
+<a class="indexterm" name="id2611610"></a>
 	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 helpful in setting up directories 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
@@ -276,11 +276,11 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	the (r) read flags are not set, files cannot be listed (seen) in the directory by anyone. The group can read files in the
 	directory but cannot create new files. 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 class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2611627"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p>
-<a class="indexterm" name="id2611636"></a>
-<a class="indexterm" name="id2611643"></a>
-<a class="indexterm" name="id2611650"></a>
-<a class="indexterm" name="id2611657"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2611642"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p>
+<a class="indexterm" name="id2611651"></a>
+<a class="indexterm" name="id2611658"></a>
+<a class="indexterm" name="id2611664"></a>
+<a class="indexterm" name="id2611671"></a>
 	People have asked on the Samba mailing list how is it possible to protect files or directories from deletion by users.
 	For example, Windows NT/2K/XP provides the capacity to set access controls on a directory into which people can
 	write files but not delete them. It is possible to set an ACL on a Windows file that permits the file to be written to
@@ -288,27 +288,27 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	anyone who has the ability to create a file can write to it. Anyone who has write permission on the
 	directory that contains a file and has write permission for it has the capability to delete it.
 	</p><p>
-<a class="indexterm" name="id2611678"></a>
-<a class="indexterm" name="id2611685"></a>
-<a class="indexterm" name="id2611692"></a>
+<a class="indexterm" name="id2611693"></a>
+<a class="indexterm" name="id2611700"></a>
+<a class="indexterm" name="id2611707"></a>
 	For the record, in the UNIX environment the ability to delete a file is controlled by the permissions on
 	the directory that the file is in. In other words, a user can delete a file in a directory to which that
 	user has write access, even if that user does not own the file.
 	</p><p>
-<a class="indexterm" name="id2611707"></a>
-<a class="indexterm" name="id2611714"></a>
-<a class="indexterm" name="id2611721"></a>
-<a class="indexterm" name="id2611728"></a>
+<a class="indexterm" name="id2611722"></a>
+<a class="indexterm" name="id2611729"></a>
+<a class="indexterm" name="id2611736"></a>
+<a class="indexterm" name="id2611742"></a>
 	Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore
 	limited in the file system capabilities that can be made available through Windows ACLs, and therefore performs
 	a "best fit" translation to POSIX ACLs. Some UNIX file systems do, however support, a feature known
 	as extended attributes. Only the Windows concept of <span class="emphasis"><em>inheritance</em></span> is implemented by Samba through
 	the appropriate extended attribute.
 	</p><p>
-<a class="indexterm" name="id2611756"></a>
-<a class="indexterm" name="id2611763"></a>
-<a class="indexterm" name="id2611770"></a>
-<a class="indexterm" name="id2611776"></a>
+<a class="indexterm" name="id2611764"></a>
+<a class="indexterm" name="id2611771"></a>
+<a class="indexterm" name="id2611778"></a>
+<a class="indexterm" name="id2611785"></a>
 	The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux.
 	For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory
 	or file from being deleted. The extended attribute that may achieve this is called the <code class="constant">immutible</code> bit.
@@ -322,7 +322,7 @@ CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
 </pre><p>
 	A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host
 	server.
-	</p><div class="procedure"><a name="id2611815"></a><p class="title"><b>Procedure�16.1.�Test for File Immutibility Support</b></p><ol type="1"><li><p>
+	</p><div class="procedure"><a name="id2611823"></a><p class="title"><b>Procedure�16.1.�Test for File Immutibility Support</b></p><ol type="1"><li><p>
 	Create a file called <code class="filename">filename</code>.
 	</p></li><li><p>
 	Login as the <code class="constant">root</code> user, then set the immutibile flag on a test file as follows:
@@ -340,11 +340,11 @@ mystic:/home/hannibal &gt; rm filename
 	that cannot be deleted. Check the man page on your particular host system to determine whether or not
 	immutable directories are writable. If they are not, then the entire directory and its contents will effectively
 	be protected from writing (file creation also) and deletion.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611888"></a>Share Definition Access Controls</h2></div></div></div><p>
-	<a class="indexterm" name="id2611896"></a>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611896"></a>Share Definition Access Controls</h2></div></div></div><p>
+	<a class="indexterm" name="id2611904"></a>
 	The following parameters in the <code class="filename">smb.conf</code> file sections define a share control or affect access controls.
 	Before using any of the following options, please refer to the man page for <code class="filename">smb.conf</code>.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611921"></a>User- and Group-Based Controls</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611929"></a>User- and Group-Based Controls</h3></div></div></div><p>
 	User- and group-based controls can prove quite useful. In some situations it is distinctly desirable to
 	force all file system operations as if a single user were doing so. The use of the
 	<a class="link" href="smb.conf.5.html#FORCEUSER" target="_top">force user</a> and <a class="link" href="smb.conf.5.html#FORCEGROUP" target="_top">force group</a> behavior will achieve this.
@@ -385,7 +385,7 @@ mystic:/home/hannibal &gt; rm filename
 			List of users that should be allowed to login to this service.
 			</p></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#WRITELIST" target="_top">write list</a></td><td align="justify"><p>
 			List of users that are given read-write access to a service.
-			</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2612289"></a>File and Directory Permissions-Based Controls</h3></div></div></div><p>
+			</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2612297"></a>File and Directory Permissions-Based Controls</h3></div></div></div><p>
 	Directory permission-based controls, if misused, can result in considerable difficulty in diagnosing the causes of 
 	misconfiguration. Use them sparingly and carefully. By gradually introducing each, one at a time, undesirable side 
 	effects may be detected. In the event of a problem, always comment all of them out and then gradually reintroduce 
@@ -416,7 +416,7 @@ mystic:/home/hannibal &gt; rm filename
 			This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT ACLs.
 			</p></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#SECURITYMASK" target="_top">security mask</a></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><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2612626"></a>Miscellaneous Controls</h3></div></div></div><p>
+			</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2612634"></a>Miscellaneous Controls</h3></div></div></div><p>
 	The parameters documented in <a class="link" href="AccessControls.html#mcoc" title="Table�16.4.�Other Controls">Other Controls</a> are often used by administrators
 	in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the 
 	full implications of <code class="filename">smb.conf</code> file settings.
@@ -449,70 +449,70 @@ mystic:/home/hannibal &gt; rm filename
 			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="link" href="smb.conf.5.html#VETOFILES" target="_top">veto files</a></td><td align="justify"><p>
 			List of files and directories that are neither visible nor accessible.
-			</p></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2612964"></a>Access Controls on Shares</h2></div></div></div><p>
-<a class="indexterm" name="id2612972"></a>
-<a class="indexterm" name="id2612978"></a>
-<a class="indexterm" name="id2612986"></a>
-<a class="indexterm" name="id2612993"></a>
-	<a class="indexterm" name="id2613000"></a>
+			</p></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2612972"></a>Access Controls on Shares</h2></div></div></div><p>
+<a class="indexterm" name="id2612980"></a>
+<a class="indexterm" name="id2612987"></a>
+<a class="indexterm" name="id2612994"></a>
+<a class="indexterm" name="id2613001"></a>
+	<a class="indexterm" name="id2613008"></a>
 	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 an 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 <code class="constant">Everyone - Full Control</code> (full control, change and read).
 	</p><p>
-<a class="indexterm" name="id2613023"></a>
-<a class="indexterm" name="id2613030"></a>
-<a class="indexterm" name="id2613036"></a>
+<a class="indexterm" name="id2613031"></a>
+<a class="indexterm" name="id2613038"></a>
+<a class="indexterm" name="id2613045"></a>
 	At this time Samba does not provide a tool for configuring access control settings on the share
 	itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
 	Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide
 	this capability in the Samba command-line tool set.
 	</p><p>
-<a class="indexterm" name="id2613053"></a>
-<a class="indexterm" name="id2613060"></a>
-<a class="indexterm" name="id2613067"></a>
-<a class="indexterm" name="id2613073"></a>
+<a class="indexterm" name="id2613061"></a>
+<a class="indexterm" name="id2613068"></a>
+<a class="indexterm" name="id2613075"></a>
+<a class="indexterm" name="id2613082"></a>
 	Samba stores the per-share access control settings in a file called <code class="filename">share_info.tdb</code>.
 	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 <code class="filename">/usr/local/samba/var</code>. If the <code class="filename">tdbdump</code>
 	utility has been compiled and installed on your system, then you can examine the contents of this file
 	by executing <code class="literal">tdbdump share_info.tdb</code> in the directory containing the tdb files.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613112"></a>Share Permissions Management</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613120"></a>Share Permissions Management</h3></div></div></div><p>
 		The best tool for share permissions management is platform-dependent. Choose the best tool for your environment.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613123"></a>Windows NT4 Workstation/Server</h4></div></div></div><p>
-<a class="indexterm" name="id2613131"></a>
-<a class="indexterm" name="id2613138"></a>
-<a class="indexterm" name="id2613145"></a>
-<a class="indexterm" name="id2613152"></a>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613132"></a>Windows NT4 Workstation/Server</h4></div></div></div><p>
+<a class="indexterm" name="id2613140"></a>
+<a class="indexterm" name="id2613147"></a>
+<a class="indexterm" name="id2613154"></a>
+<a class="indexterm" name="id2613161"></a>
 			The tool you need to manage share permissions on a Samba server from a Windows NT4 Workstation or 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 the Microsoft
 			web site <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">support</a> section.
-			</p><div class="procedure"><a name="id2613173"></a><p class="title"><b>Procedure�16.2.�Instructions</b></p><ol type="1"><li><p>
+			</p><div class="procedure"><a name="id2613181"></a><p class="title"><b>Procedure�16.2.�Instructions</b></p><ol type="1"><li><p>
 			Launch the <span class="application">NT4 Server Manager</span> and click on the Samba server you want to
 			administer. From the menu select <span class="guimenu">Computer</span>, then click on
 			<span class="guimenuitem">Shared Directories</span>.
 			</p></li><li><p>
 			Click on the share that you wish to manage and click the <span class="guilabel">Properties</span> tab, then click
 			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="id2613228"></a>Windows 200x/XP</h4></div></div></div><p>
-<a class="indexterm" name="id2613236"></a>
-<a class="indexterm" name="id2613243"></a>
-<a class="indexterm" name="id2613250"></a>
-<a class="indexterm" name="id2613257"></a>
+			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613237"></a>Windows 200x/XP</h4></div></div></div><p>
+<a class="indexterm" name="id2613245"></a>
+<a class="indexterm" name="id2613252"></a>
+<a class="indexterm" name="id2613259"></a>
+<a class="indexterm" name="id2613265"></a>
 			On <span class="application">MS Windows NT4/200x/XP</span> systems, ACLs on the share itself are set using
 			tools like the MS Explorer. 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 permissions allow the group "Everyone" full control on the share.
 			</p><p>
-<a class="indexterm" name="id2613290"></a>
-<a class="indexterm" name="id2613297"></a>
-<a class="indexterm" name="id2613303"></a>
+<a class="indexterm" name="id2613298"></a>
+<a class="indexterm" name="id2613305"></a>
+<a class="indexterm" name="id2613312"></a>
 			MS Windows 200x and later versions come with a tool called the <span class="application">Computer Management</span>
 			snap-in for the MMC. This tool can be accessed via <span class="guimenu">Control Panel -&gt;
 			Administrative Tools -&gt; Computer Management</span>.
-			</p><div class="procedure"><a name="id2613327"></a><p class="title"><b>Procedure�16.3.�Instructions</b></p><ol type="1"><li><p>
+			</p><div class="procedure"><a name="id2613336"></a><p class="title"><b>Procedure�16.3.�Instructions</b></p><ol type="1"><li><p>
 			After launching the MMC with the Computer Management snap-in, click the menu item <span class="guimenuitem">Action</span>
 			and 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.
@@ -523,7 +523,7 @@ mystic:/home/hannibal &gt; rm filename
 			<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>
-<a class="indexterm" name="id2613408"></a>
+<a class="indexterm" name="id2613416"></a>
 			In the right panel, double-click on the share on which you wish to set access control permissions.
 			Then click the tab <span class="guilabel">Share Permissions</span>. It is now possible to add access control entities
 			to the shared folder. Remember to set what type of access (full control, change, read) you
@@ -534,8 +534,8 @@ mystic:/home/hannibal &gt; rm filename
 			ACL precedence. Everyone with <span class="emphasis"><em>no access</em></span> means that <code class="constant">MaryK</code> who is
 			part of the group <code class="constant">Everyone</code> will have no access even if she 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="id2613459"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613465"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p>
-		<a class="indexterm" name="id2613474"></a>
+			</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2613466"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613473"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p>
+		<a class="indexterm" name="id2613481"></a>
 		Windows NT clients can use their native security settings dialog box to view and modify the
 		underlying UNIX permissions.
 		</p><p>
@@ -549,7 +549,7 @@ mystic:/home/hannibal &gt; rm filename
 		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="id2613512"></a>Viewing File Security on a Samba Share</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613520"></a>Viewing File Security on a Samba Share</h3></div></div></div><p>
 		From an NT4/2000/XP client, right-click 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 <code class="constant">Properties</code> dialog box. Click on the 
@@ -560,7 +560,7 @@ mystic:/home/hannibal &gt; rm filename
 		to add auditing requirements to a file if the user is logged on as the NT administrator. This dialog is
 		nonfunctional with a Samba share at this time, because 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="id2613583"></a>Viewing File Ownership</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613591"></a>Viewing File Ownership</h3></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 displayed like this:
 		</p><pre class="screen">
@@ -574,7 +574,7 @@ mystic:/home/hannibal &gt; rm filename
 		If the parameter <a class="link" href="smb.conf.5.html#NTACLSUPPORT" target="_top">nt acl support</a> is set to <code class="constant">false</code>,
 		the file owner will be shown as the NT user <span class="emphasis"><em>Everyone</em></span>.
 		</p><p>
-<a class="indexterm" name="id2613657"></a>
+<a class="indexterm" name="id2613665"></a>
 		The <span class="guibutton">Take Ownership</span> button will not allow you to change the ownership of this file to
 		yourself (clicking it will display a dialog box complaining that the user as whom 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
@@ -582,14 +582,14 @@ mystic:/home/hannibal &gt; rm filename
 		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>
-<a class="indexterm" name="id2613686"></a>
-<a class="indexterm" name="id2613692"></a>
-<a class="indexterm" name="id2613699"></a>
+<a class="indexterm" name="id2613694"></a>
+<a class="indexterm" name="id2613701"></a>
+<a class="indexterm" name="id2613708"></a>
 		There is an NT <code class="literal">chown</code> 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 file system
 		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 and is downloadable from the main Samba FTP site.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613726"></a>Viewing File or Directory Permissions</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613735"></a>Viewing File or Directory Permissions</h3></div></div></div><p>
 		The third button is the <span class="guibutton">Permissions</span> button. Clicking on it brings up a dialog box
 		that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed like this:
 		</p><p><code class="literal"><em class="replaceable"><code>SERVER</code></em>\
@@ -603,7 +603,7 @@ mystic:/home/hannibal &gt; rm filename
 		shown as NT <span class="emphasis"><em>Full Control</em></span>.
 		</p><p>
 		The permissions field is displayed differently for files and directories. Both are discussed next.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613810"></a>File Permissions</h4></div></div></div><p>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613818"></a>File Permissions</h4></div></div></div><p>
 		The standard UNIX user/group/world triplet and the corresponding <code class="constant">read, write,
 		execute</code> permissions triplets are mapped by Samba into a three-element NT ACL with the
 		&#8220;<span class="quote">r</span>&#8221;, &#8220;<span class="quote">w</span>&#8221;, and &#8220;<span class="quote">x</span>&#8221; bits mapped into the corresponding NT
@@ -621,7 +621,7 @@ mystic:/home/hannibal &gt; rm filename
 		<code class="constant">Take Ownership</code> ACL attribute (which has no meaning in UNIX) and reports a component with
 		no permissions as having the NT <code class="literal">O</code> bit set.  This was chosen, of course, to make it look
 		like a zero, meaning zero permissions. More details on the decision behind this action are given below.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613904"></a>Directory Permissions</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613912"></a>Directory Permissions</h4></div></div></div><p>
 		Directories on an NT NTFS file system have two different sets of permissions. The first set is the ACL set on the
 		directory itself, which is usually displayed in the first set of parentheses in the normal <code class="constant">RW</code> 
 		NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described 
@@ -632,7 +632,7 @@ mystic:/home/hannibal &gt; rm filename
 		</p><p>
 		Samba synthesizes 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="id2613942"></a>Modifying File or Directory Permissions</h3></div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613950"></a>Modifying File or Directory Permissions</h3></div></div></div><p>
 	Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box
 	and clicking on <span class="guibutton">OK</span>. 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 also need to
@@ -665,7 +665,7 @@ mystic:/home/hannibal &gt; rm filename
 	If you wish to remove all permissions from a user/group/world  component, you may either highlight the
 	component and click on the <span class="guibutton">Remove</span> button or set the component to only have the special
 	<code class="constant">Take Ownership</code> permission (displayed as <code class="literal">O</code>) highlighted.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614099"></a>Interaction with the Standard Samba &#8220;<span class="quote">create mask</span>&#8221; Parameters</h3></div></div></div><p>There are four parameters that control interaction with the standard Samba <em class="parameter"><code>create mask</code></em> parameters:
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614107"></a>Interaction with the Standard Samba &#8220;<span class="quote">create mask</span>&#8221; Parameters</h3></div></div></div><p>There are four parameters that control interaction with the standard Samba <em class="parameter"><code>create mask</code></em> parameters:
 	
 
 	</p><div class="itemizedlist"><ul type="disc"><li><p><a class="link" href="smb.conf.5.html#SECURITYMASK" target="_top">security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCESECURITYMODE" target="_top">force security mode</a></p></li><li><p><a class="link" href="smb.conf.5.html#DIRECTORYSECURITYMASK" target="_top">directory security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCEDIRECTORYSECURITYMODE" target="_top">force directory security mode</a></p></li></ul></div><p>
@@ -719,7 +719,7 @@ mystic:/home/hannibal &gt; rm filename
 	does not force any particular bits to be set <span class="emphasis"><em>on</em></span>,
 	then set the following parameters in the <code class="filename">smb.conf</code> file in that
 	share-specific section:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2614420"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614431"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2614443"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614455"></a><em class="parameter"><code>force directory security mode = 0</code></em></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614468"></a>Interaction with the Standard Samba File Attribute Mapping</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2614428"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614439"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2614451"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614463"></a><em class="parameter"><code>force directory security mode = 0</code></em></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614477"></a>Interaction with the Standard Samba File Attribute Mapping</h3></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 &#8220;<span class="quote">read-only</span>&#8221;)
 	into the UNIX permissions of a file. This means there can 
 	be a conflict between the permission bits set via the security 
@@ -740,7 +740,7 @@ mystic:/home/hannibal &gt; rm filename
 	attributes dialog, you should always press <span class="guibutton">Cancel</span> 
 	rather than <span class="guibutton">OK</span> to ensure that your changes 
 	are not overridden.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614541"></a>Windows NT/200X ACLs and POSIX ACLs Limitations</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614550"></a>Windows NT/200X ACLs and POSIX ACLs Limitations</h3></div></div></div><p>
 	Windows administrators are familiar with simple ACL controls, and they typically
 	consider that UNIX user/group/other (ugo) permissions are inadequate and not
 	sufficiently fine-grained.
@@ -768,7 +768,7 @@ mystic:/home/hannibal &gt; rm filename
 	ACLs as implemented in UNIX file systems. Samba provides support for <span class="emphasis"><em>masks</em></span>
 	that permit normal ugo and ACLs functionality to be overrided. This further complicates
 	the way in which Windows ACLs must be implemented.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614599"></a>UNIX POSIX ACL Overview</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614613"></a>UNIX POSIX ACL Overview</h4></div></div></div><p>
 	In examining POSIX ACLs we must consider the manner in which they operate for 
 	both files and directories. File ACLs have the following significance:
 </p><pre class="screen">
@@ -797,7 +797,7 @@ default:group::r-x    &lt;-- inherited group perms
 default:mask:rwx      &lt;-- inherited default mask
 default:other:---     &lt;-- inherited permissions for everyone (other)
 </pre><p>
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614660"></a>Mapping of Windows File ACLs to UNIX POSIX ACLs</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614675"></a>Mapping of Windows File ACLs to UNIX POSIX ACLs</h4></div></div></div><p>
 	Microsoft Windows NT4/200X ACLs must of necessity be mapped to POSIX ACLs.
 	The mappings for file permissions are shown in <a class="link" href="AccessControls.html#fdsacls" title="Table�16.5.�How Windows File ACLs Map to UNIX POSIX File ACLs">How
 	Windows File ACLs Map to UNIX POSIX File ACLs</a>.
@@ -816,7 +816,7 @@ default:other:---     &lt;-- inherited permissions for everyone (other)
 	The UNIX administrator can set any directory permission from within the UNIX environment.
 	The Windows administrator is more restricted in that it is not possible from within 
 	Windows Explorer to remove read permission for the file owner.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614930"></a>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2614944"></a>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</h4></div></div></div><p>
 	Interesting things happen in the mapping of UNIX POSIX directory permissions and
 	UNIX POSIX ACLs to Windows ACEs (Access Control Entries, the discrete components of
 	an ACL) are mapped to Windows directory ACLs.
@@ -824,10 +824,10 @@ default:other:---     &lt;-- inherited permissions for everyone (other)
 	Directory permissions function in much the same way as shown for file permissions, but
 	there are some notable exceptions and a few peculiarities that the astute administrator
 	will want to take into account in the setting up of directory permissions.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2614954"></a>Common Errors</h2></div></div></div><p>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2614968"></a>Common Errors</h2></div></div></div><p>
 File, directory, and share access problems are common topics on the mailing list. The following
 are examples recently taken from the mailing list.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614965"></a>Users Cannot Write to a Public Share</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614980"></a>Users Cannot Write to a Public Share</h3></div></div></div><p>
 	The following complaint has frequently been voiced on the Samba mailing list: 
 	&#8220;<span class="quote">
 	We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root),
@@ -887,11 +887,11 @@ drwxrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
 		</p></li><li><p>
 		If the user that must have write permission in the directory is not a member of the group
 		<span class="emphasis"><em>engr</em></span> set in the <code class="filename">smb.conf</code> entry for the share:
-		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2615272"></a><em class="parameter"><code>force group = engr</code></em></td></tr></table><p>
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615288"></a>File Operations Done as <span class="emphasis"><em>root</em></span> with <span class="emphasis"><em>force user</em></span> Set</h3></div></div></div><p>
+		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2615287"></a><em class="parameter"><code>force group = engr</code></em></td></tr></table><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615303"></a>File Operations Done as <span class="emphasis"><em>root</em></span> with <span class="emphasis"><em>force user</em></span> Set</h3></div></div></div><p>
 		When you have a user in <a class="link" href="smb.conf.5.html#ADMINUSERS" target="_top">admin users</a>, Samba will always do file operations for
 		this user as <span class="emphasis"><em>root</em></span>, even if <a class="link" href="smb.conf.5.html#FORCEUSER" target="_top">force user</a> has been set.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615334"></a>MS Word with Samba Changes Owner of File</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615348"></a>MS Word with Samba Changes Owner of File</h3></div></div></div><p>
 		<span class="emphasis"><em>Question:</em></span> &#8220;<span class="quote">When user B saves a word document that is owned by user A,
 		the updated file is now owned by user B.  Why is Samba doing this? How do I fix this?</span>&#8221;
 		</p><p>
@@ -906,7 +906,7 @@ drwxrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
 		in which you are changing Word documents: <code class="literal">chmod g+s `directory_name'.</code> This ensures that all files will
 		be created with the group that owns the directory. In <code class="filename">smb.conf</code> share declaration section set:
 		</p><p>
-		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2615413"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2615424"></a><em class="parameter"><code>force directory mode = 0770</code></em></td></tr></table><p>
+		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2615427"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2615439"></a><em class="parameter"><code>force directory mode = 0770</code></em></td></tr></table><p>
 		</p><p>
 		These two settings will ensure that all directories and files that get created in the share will be readable/writable by the
 		owner and group set on the directory itself.
diff --git a/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html b/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html
index 9e79808019..f79fbedadc 100644
--- a/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html
+++ b/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�25.�Advanced Network Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts"><link rel="next" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�25.�Advanced Network Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="winbind.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="PolicyMgmt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter�25.�Advanced Network Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 15 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657466">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657636">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658226">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658451">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658494">Limiting Logon Connections</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2657454"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�25.�Advanced Network Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts"><link rel="next" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�25.�Advanced Network Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="winbind.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="PolicyMgmt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter�25.�Advanced Network Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 15 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657600">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657770">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658359">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658585">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658628">Limiting Logon Connections</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2657588"></a>
 This section documents peripheral issues that are of great importance to network
 administrators who want to improve network resource access control, to automate the user
 environment, and to make their lives a little easier.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657466"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657600"></a>Features and Benefits</h2></div></div></div><p>
 Often the difference between a working network environment and a well-appreciated one can
 best be measured by the <span class="emphasis"><em>little things</em></span> that make everything work more
 harmoniously. A key part of every network environment solution is the ability to remotely
@@ -13,48 +13,48 @@ network operations.
 </p><p>
 This chapter presents information on each of these areas. They are placed here, and not in
 other chapters, for ease of reference.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657493"></a>Remote Server Administration</h2></div></div></div><p>&#8220;<span class="quote">How do I get User Manager and Server Manager?</span>&#8221;</p><p>
-<a class="indexterm" name="id2657506"></a>
-<a class="indexterm" name="id2657513"></a>
-<a class="indexterm" name="id2657520"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657626"></a>Remote Server Administration</h2></div></div></div><p>&#8220;<span class="quote">How do I get User Manager and Server Manager?</span>&#8221;</p><p>
+<a class="indexterm" name="id2657640"></a>
+<a class="indexterm" name="id2657647"></a>
+<a class="indexterm" name="id2657654"></a>
 Since I do not need to buy an <span class="application">NT4 server</span>, how do I get the User Manager for Domains
 and the Server Manager?
 </p><p>
-<a class="indexterm" name="id2657538"></a>
-<a class="indexterm" name="id2657545"></a>
+<a class="indexterm" name="id2657672"></a>
+<a class="indexterm" name="id2657678"></a>
 Microsoft distributes a version of these tools called <code class="filename">Nexus.exe</code> for installation 
 on <span class="application">Windows 9x/Me</span> systems. The tools set includes:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Server Manager</p></li><li><p>User Manager for Domains</p></li><li><p>Event Viewer</p></li></ul></div><p>
 Download the archived file at the Microsoft <a class="ulink" href="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" target="_top">Nexus</a> link.
 </p><p>
-<a class="indexterm" name="id2657599"></a>
-<a class="indexterm" name="id2657606"></a>
-<a class="indexterm" name="id2657613"></a>
+<a class="indexterm" name="id2657732"></a>
+<a class="indexterm" name="id2657739"></a>
+<a class="indexterm" name="id2657746"></a>
 The <span class="application">Windows NT 4.0</span> version of the User Manager for 
 Domains and Server Manager are available from Microsoft
 <a class="ulink" href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">via ftp</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657636"></a>Remote Desktop Management</h2></div></div></div><p>
-<a class="indexterm" name="id2657644"></a>
-<a class="indexterm" name="id2657651"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657770"></a>Remote Desktop Management</h2></div></div></div><p>
+<a class="indexterm" name="id2657778"></a>
+<a class="indexterm" name="id2657785"></a>
 There are a number of possible remote desktop management solutions that range from free
 through costly. Do not let that put you off. Sometimes the most costly solution is the
 most cost effective. In any case, you will need to draw your own conclusions as to which
 is the best tool in your network environment.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657665"></a>Remote Management from NoMachine.Com</h3></div></div></div><p>
-	<a class="indexterm" name="id2657673"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657798"></a>Remote Management from NoMachine.Com</h3></div></div></div><p>
+	<a class="indexterm" name="id2657806"></a>
 	The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003.
 	It is presented in slightly edited form (with author details omitted for privacy reasons).
 	The entire answer is reproduced below with some comments removed.
 	</p><p>&#8220;<span class="quote">
-<a class="indexterm" name="id2657689"></a>
+<a class="indexterm" name="id2657822"></a>
 		I have a wonderful Linux/Samba server running as PDC for a network. Now I would like to add remote
 		desktop capabilities so users outside could login to the system and get their desktop up from home or
 		another country.
 		</span>&#8221;</p><p>&#8220;<span class="quote">
-<a class="indexterm" name="id2657704"></a>
-<a class="indexterm" name="id2657711"></a>
-<a class="indexterm" name="id2657717"></a>
-<a class="indexterm" name="id2657724"></a>
+<a class="indexterm" name="id2657837"></a>
+<a class="indexterm" name="id2657844"></a>
+<a class="indexterm" name="id2657851"></a>
+<a class="indexterm" name="id2657857"></a>
 		Is there a way to accomplish this? Do I need a Windows Terminal server?  Do I need to configure it so
 		it is a member of the domain or a BDC or PDC? Are there any hacks for MS Windows XP to enable remote login
 		even if the computer is in a domain?
@@ -62,22 +62,22 @@ is the best tool in your network environment.
 		Answer provided: Check out the new offer of &#8220;<span class="quote">NX</span>&#8221; software from
 		<a class="ulink" href="http://www.nomachine.com/" target="_top">NoMachine</a>.
 		</p><p>
-<a class="indexterm" name="id2657755"></a>
-<a class="indexterm" name="id2657762"></a>
-<a class="indexterm" name="id2657769"></a>
+<a class="indexterm" name="id2657888"></a>
+<a class="indexterm" name="id2657895"></a>
+<a class="indexterm" name="id2657902"></a>
 	It implements an easy-to-use interface to the Remote X protocol as
 	well as incorporating VNC/RFB and rdesktop/RDP into it, but at a speed
 	performance much better than anything you may have ever seen.
 	</p><p>
-<a class="indexterm" name="id2657782"></a>
+<a class="indexterm" name="id2657916"></a>
 	Remote X is not new at all, but what they did achieve successfully is
 	a new way of compression and caching technologies that makes the thing
 	fast enough to run even over slow modem/ISDN connections.
 	</p><p>
-<a class="indexterm" name="id2657796"></a>
-<a class="indexterm" name="id2657803"></a>
-<a class="indexterm" name="id2657810"></a>
-<a class="indexterm" name="id2657816"></a>
+<a class="indexterm" name="id2657929"></a>
+<a class="indexterm" name="id2657936"></a>
+<a class="indexterm" name="id2657943"></a>
+<a class="indexterm" name="id2657950"></a>
 	I test drove their (public) Red Hat machine in Italy, over a loaded
 	Internet connection, with enabled thumbnail previews in KDE konqueror,
 	which popped up immediately on &#8220;<span class="quote">mouse-over</span>&#8221;. From inside that (remote X)
@@ -85,18 +85,18 @@ is the best tool in your network environment.
 	To test the performance, I played Pinball. I am proud to announce
 	that my score was 631,750 points at first try.
 	</p><p>
-<a class="indexterm" name="id2657835"></a>
-<a class="indexterm" name="id2657842"></a>
-<a class="indexterm" name="id2657849"></a>
-<a class="indexterm" name="id2657856"></a>
+<a class="indexterm" name="id2657969"></a>
+<a class="indexterm" name="id2657975"></a>
+<a class="indexterm" name="id2657982"></a>
+<a class="indexterm" name="id2657989"></a>
 	NX performs better on my local LAN than any of the other &#8220;<span class="quote">pure</span>&#8221;
 	connection methods I use from time to time: TightVNC, rdesktop or
 	Remote X. It is even faster than a direct crosslink connection between
 	two nodes.
 	</p><p>
-<a class="indexterm" name="id2657873"></a>
-<a class="indexterm" name="id2657880"></a>
-<a class="indexterm" name="id2657886"></a>
+<a class="indexterm" name="id2658006"></a>
+<a class="indexterm" name="id2658013"></a>
+<a class="indexterm" name="id2658020"></a>
 	I even got sound playing from the Remote X app to my local boxes, and
 	had a working &#8220;<span class="quote">copy'n'paste</span>&#8221; from an NX  window (running a KDE session
 	in Italy) to my Mozilla mailing agent. These guys are certainly doing
@@ -118,7 +118,7 @@ is the best tool in your network environment.
 	full-screen, and after a short time you forget that it is a remote session
 	at all).
 	</p><p>
-<a class="indexterm" name="id2657936"></a>
+<a class="indexterm" name="id2658070"></a>
 	Now the best thing for last: All the core compression and caching
 	technologies are released under the GPL and available as source code
 	to anybody who wants to build on it! These technologies are working,
@@ -140,37 +140,37 @@ is the best tool in your network environment.
 		you can now use a (very inconvenient) command line at no cost,
 		but you can buy a comfortable (proprietary) NX GUI front end for money.
 		</p></li><li><p>
-<a class="indexterm" name="id2658000"></a>
-<a class="indexterm" name="id2658006"></a>
-<a class="indexterm" name="id2658013"></a>
-<a class="indexterm" name="id2658020"></a>
-<a class="indexterm" name="id2658026"></a>
+<a class="indexterm" name="id2658133"></a>
+<a class="indexterm" name="id2658139"></a>
+<a class="indexterm" name="id2658146"></a>
+<a class="indexterm" name="id2658153"></a>
+<a class="indexterm" name="id2658160"></a>
 		NoMachine is encouraging and offering help to OSS/Free Software implementations
 		for such a front-end too, even if it means competition to them (they have written
 		to this effect even to the LTSP, KDE, and GNOME developer mailing lists).
-		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658041"></a>Remote Management with ThinLinc</h3></div></div></div><p>
+		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658174"></a>Remote Management with ThinLinc</h3></div></div></div><p>
 	Another alternative for remote access is <span class="emphasis"><em>ThinLinc</em></span> from Cendio.
 	</p><p>
-<a class="indexterm" name="id2658057"></a>
-<a class="indexterm" name="id2658063"></a>
-<a class="indexterm" name="id2658070"></a>
-<a class="indexterm" name="id2658077"></a>
-<a class="indexterm" name="id2658084"></a>
-<a class="indexterm" name="id2658091"></a>
-<a class="indexterm" name="id2658097"></a>
-<a class="indexterm" name="id2658104"></a>
+<a class="indexterm" name="id2658190"></a>
+<a class="indexterm" name="id2658197"></a>
+<a class="indexterm" name="id2658204"></a>
+<a class="indexterm" name="id2658211"></a>
+<a class="indexterm" name="id2658217"></a>
+<a class="indexterm" name="id2658224"></a>
+<a class="indexterm" name="id2658231"></a>
+<a class="indexterm" name="id2658237"></a>
 	ThinLinc is a terminal server solution that is available for Linux and Solaris based on standard
 	protocols such as SSH, TightVNC, NFS and PulseAudio.
 	</p><p>
-<a class="indexterm" name="id2658116"></a>
-<a class="indexterm" name="id2658123"></a>
+<a class="indexterm" name="id2658250"></a>
+<a class="indexterm" name="id2658256"></a>
 	ThinLinc an be used both in the LAN environment to implement a Thin Client strategy for an organization, and as
 	secure remote access solution for people working from remote locations, even over smallband connections.
 	ThinLinc is free to use for a single concurrent user.
 	</p><p>
-<a class="indexterm" name="id2658138"></a>
-<a class="indexterm" name="id2658145"></a>
-<a class="indexterm" name="id2658152"></a>
+<a class="indexterm" name="id2658271"></a>
+<a class="indexterm" name="id2658278"></a>
+<a class="indexterm" name="id2658285"></a>
 	The product can also be used as a frontend to access Windows Terminal Server or Citrix farms, or even Windows
 	XP machines, securing the connection via the ssh protocol. The client is available both for Linux (supporting
 	all Linux distributions as well as numerous thin terminals) and for Windows. A Java-based Web client is also
@@ -185,7 +185,7 @@ is the best tool in your network environment.
 	<a class="ulink" href="http://pulseaudio.org" target="_top">PulseAudio</a> , unfsd,
 	<a class="ulink" href="http://www.python.org" target="_top">Python</a> and
 	<a class="ulink" href="http://www.rdesktop.org" target="_top">rdesktop</a>.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658226"></a>Network Logon Script Magic</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658359"></a>Network Logon Script Magic</h2></div></div></div><p>
 There are several opportunities for creating a custom network startup configuration environment.
 </p><div class="itemizedlist"><ul type="disc"><li><p>No Logon Script.</p></li><li><p>Simple universal Logon Script that applies to all users.</p></li><li><p>Use of a conditional Logon Script that applies per-user or per-group attributes.</p></li><li><p>Use of Samba's preexec and postexec functions on access to the NETLOGON share to create
 		a custom logon script and then execute it.</p></li><li><p>User of a tool such as KixStart.</p></li></ul></div><p>
@@ -195,7 +195,7 @@ See <code class="filename">examples</code> directory <code class="filename">genl
 </p><p>
 The following listings are from the genlogon directory.
 </p><p>
-<a class="indexterm" name="id2658296"></a>
+<a class="indexterm" name="id2658430"></a>
 This is the <code class="filename">genlogon.pl</code> file:
 
 </p><pre class="programlisting">
@@ -274,15 +274,15 @@ This is the <code class="filename">genlogon.pl</code> file:
 </pre><p>
 </p><p>
 Those wishing to use a more elaborate or capable logon processing system should check out these sites:
-</p><div class="itemizedlist"><ul type="disc"><li><p><a class="ulink" href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></p></li><li><p><a class="ulink" href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658451"></a>Adding Printers without User Intervention</h3></div></div></div><p>
-<a class="indexterm" name="id2658460"></a>
+</p><div class="itemizedlist"><ul type="disc"><li><p><a class="ulink" href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></p></li><li><p><a class="ulink" href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658585"></a>Adding Printers without User Intervention</h3></div></div></div><p>
+<a class="indexterm" name="id2658593"></a>
 Printers may be added automatically during logon script processing through the use of:
 </p><pre class="screen">
 <code class="prompt">C:\&gt; </code><strong class="userinput"><code>rundll32 printui.dll,PrintUIEntry /?</code></strong>
 </pre><p>
 
 See the documentation in the <a class="ulink" href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">Microsoft Knowledge Base article 189105</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658494"></a>Limiting Logon Connections</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658628"></a>Limiting Logon Connections</h3></div></div></div><p>
 		Sometimes it is necessary to limit the number of concurrent connections to a
 		Samba shared resource. For example, a site may wish to permit only one network
 		logon per user.
diff --git a/docs/htmldocs/Samba3-HOWTO/Appendix.html b/docs/htmldocs/Samba3-HOWTO/Appendix.html
index 3b76c60b09..cfa3e0d99a 100644
--- a/docs/htmldocs/Samba3-HOWTO/Appendix.html
+++ b/docs/htmldocs/Samba3-HOWTO/Appendix.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�VI.�Reference Section</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="tdb.html" title="Chapter�41.�Managing TDB Files"><link rel="next" href="compiling.html" title="Chapter�42.�How to Compile Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�VI.�Reference Section</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tdb.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="compiling.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendix"></a>Part�VI.�Reference Section</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="compiling.html">42. How to Compile Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="compiling.html#id2687392">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687398">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687440">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687637">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687711">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687849">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688088">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688359">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688579">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Portability.html">43. Portability</a></span></dt><dd><dl><dt><span class="sect1"><a href="Portability.html#id2688963">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689067">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689106">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689248">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689291">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689353">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689358">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Other-Clients.html">44. Samba and Other CIFS Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689543">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689627">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689633">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689752">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689809">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2689902">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689908">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689991">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690017">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690075">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690107">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690164">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690233">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690254">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690450">Windows NT 3.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="speed.html">45. Samba Performance Tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="speed.html#id2690558">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690596">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690693">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690737">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690785">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690809">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690876">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690928">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690952">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691160">Samba Performance is Very Slow</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-ldap-tls.html">46. LDAP and Transport Layer Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch47.html">47. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch47.html#id2692350">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692569">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="DNSDHCP.html">48. DNS and DHCP Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692722">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2692901">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2692992">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tdb.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="compiling.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�41.�Managing TDB Files�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�42.�How to Compile Samba</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�VI.�Reference Section</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="tdb.html" title="Chapter�41.�Managing TDB Files"><link rel="next" href="compiling.html" title="Chapter�42.�How to Compile Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�VI.�Reference Section</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tdb.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="compiling.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendix"></a>Part�VI.�Reference Section</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="compiling.html">42. How to Compile Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="compiling.html#id2687543">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687549">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687590">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687994">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688233">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688504">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688724">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Portability.html">43. Portability</a></span></dt><dd><dl><dt><span class="sect1"><a href="Portability.html#id2689108">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689212">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689251">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689392">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689436">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689498">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689503">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Other-Clients.html">44. Samba and Other CIFS Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689679">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689763">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689769">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689888">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689945">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690038">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690044">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690127">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690153">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690211">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690243">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690300">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690369">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690390">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690586">Windows NT 3.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="speed.html">45. Samba Performance Tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="speed.html#id2690694">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690732">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690829">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690873">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690921">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690945">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691012">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691088">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691200">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691296">Samba Performance is Very Slow</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-ldap-tls.html">46. LDAP and Transport Layer Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch47.html">47. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch47.html#id2692487">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692705">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="DNSDHCP.html">48. DNS and DHCP Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692858">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2693042">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2693133">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tdb.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="compiling.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�41.�Managing TDB Files�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�42.�How to Compile Samba</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/Backup.html b/docs/htmldocs/Samba3-HOWTO/Backup.html
index 65ae2120dc..f299a5aae8 100644
--- a/docs/htmldocs/Samba3-HOWTO/Backup.html
+++ b/docs/htmldocs/Samba3-HOWTO/Backup.html
@@ -1,33 +1,33 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�31.�Backup Techniques</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="unicode.html" title="Chapter�30.�Unicode/Charsets"><link rel="next" href="SambaHA.html" title="Chapter�32.�High Availability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�31.�Backup Techniques</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unicode.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="SambaHA.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter�31.�Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Backup.html#id2671241">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671286">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671383">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671554">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671724">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671772">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671241"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2671249"></a>
-<a class="indexterm" name="id2671256"></a>
-<a class="indexterm" name="id2671263"></a>
-<a class="indexterm" name="id2671270"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�31.�Backup Techniques</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="unicode.html" title="Chapter�30.�Unicode/Charsets"><link rel="next" href="SambaHA.html" title="Chapter�32.�High Availability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�31.�Backup Techniques</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unicode.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="SambaHA.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter�31.�Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Backup.html#id2671379">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671424">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671521">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671692">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671862">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671910">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671379"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2671387"></a>
+<a class="indexterm" name="id2671394"></a>
+<a class="indexterm" name="id2671401"></a>
+<a class="indexterm" name="id2671408"></a>
 The Samba project is over 10 years old. During the early history
 of Samba, UNIX administrators were its key implementors. UNIX administrators
 use UNIX system tools to backup UNIX system files. Over the past
 4 years, an increasing number of Microsoft network administrators have
 taken an interest in Samba. This is reflected in the questions about backup
 in general on the Samba mailing lists.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671286"></a>Discussion of Backup Solutions</h2></div></div></div><p>
-<a class="indexterm" name="id2671294"></a>
-<a class="indexterm" name="id2671301"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671424"></a>Discussion of Backup Solutions</h2></div></div></div><p>
+<a class="indexterm" name="id2671432"></a>
+<a class="indexterm" name="id2671438"></a>
 During discussions at a Microsoft Windows training course, one of
 the pro-UNIX delegates stunned the class when he pointed out that Windows
 NT4 is limiting compared with UNIX. He likened UNIX to a Meccano set
 that has an unlimited number of tools that are simple, efficient,
 and, in combination, capable of achieving any desired outcome.
 </p><p>
-<a class="indexterm" name="id2671316"></a>
-<a class="indexterm" name="id2671324"></a>
+<a class="indexterm" name="id2671454"></a>
+<a class="indexterm" name="id2671461"></a>
 One of the Windows networking advocates retorted that if she wanted a
 Meccano set, she would buy one. She made it clear that a complex single
 tool that does more than is needed but does it with a clear purpose and
 intent is preferred by some like her.
 </p><p>
-<a class="indexterm" name="id2671338"></a>
-<a class="indexterm" name="id2671345"></a>
-<a class="indexterm" name="id2671352"></a>
+<a class="indexterm" name="id2671476"></a>
+<a class="indexterm" name="id2671483"></a>
+<a class="indexterm" name="id2671490"></a>
 Please note that all information here is provided as is and without recommendation
 of fitness or suitability. The network administrator is strongly encouraged to
 perform due diligence research before implementing any backup solution, whether free
@@ -38,31 +38,31 @@ is located at <a class="ulink" href="http://www.allmerchants.com/Software/Backup
 www.allmerchants.com</a>.
 </p><p>
 The following three free software projects might also merit consideration.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671383"></a>BackupPC</h3></div></div></div><p>
-	<a class="indexterm" name="id2671391"></a>
-<a class="indexterm" name="id2671398"></a>
-<a class="indexterm" name="id2671404"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671521"></a>BackupPC</h3></div></div></div><p>
+	<a class="indexterm" name="id2671529"></a>
+<a class="indexterm" name="id2671535"></a>
+<a class="indexterm" name="id2671542"></a>
 	BackupPC version 2.0.0 has been released on <a class="ulink" href="http://backuppc.sourceforge.net" target="_top">SourceForge</a>.
 	 New features include support for <code class="literal">rsync/rsyncd</code> and internationalization of the CGI interface
 	(including English, French, Spanish, and German).
 	</p><p>
-<a class="indexterm" name="id2671429"></a>
-<a class="indexterm" name="id2671436"></a>
-<a class="indexterm" name="id2671443"></a>
-<a class="indexterm" name="id2671449"></a>
-<a class="indexterm" name="id2671456"></a>
-<a class="indexterm" name="id2671462"></a>
-<a class="indexterm" name="id2671469"></a>
-<a class="indexterm" name="id2671476"></a>
+<a class="indexterm" name="id2671567"></a>
+<a class="indexterm" name="id2671574"></a>
+<a class="indexterm" name="id2671580"></a>
+<a class="indexterm" name="id2671587"></a>
+<a class="indexterm" name="id2671594"></a>
+<a class="indexterm" name="id2671600"></a>
+<a class="indexterm" name="id2671607"></a>
+<a class="indexterm" name="id2671613"></a>
 	BackupPC is a high-performance Perl-based package for backing up Linux,
 	UNIX, and Windows PCs and laptops to a server's disk. BackupPC is highly
 	configurable and easy to install and maintain. SMB (via smbclient),
 	<code class="literal">tar</code> over <code class="literal">rsh/ssh</code>, or <code class="literal">rsync/rsyncd</code>
 	 are used to extract client data.
 	</p><p>
-<a class="indexterm" name="id2671508"></a>
-<a class="indexterm" name="id2671514"></a>
-<a class="indexterm" name="id2671521"></a>
+<a class="indexterm" name="id2671646"></a>
+<a class="indexterm" name="id2671652"></a>
+<a class="indexterm" name="id2671659"></a>
 	Given the ever-decreasing cost of disks and RAID systems, it is now
 	practical and cost effective to backup a large number of machines onto
 	a server's local disk or network storage. This is what BackupPC does.
@@ -71,24 +71,24 @@ The following three free software projects might also merit consideration.
 	space), compression, and a comprehensive CGI interface that allows users
 	to browse backups and restore files.
 	</p><p>
-<a class="indexterm" name="id2671542"></a>
+<a class="indexterm" name="id2671679"></a>
 	BackupPC is free software distributed under a GNU GPL license.
 	BackupPC runs on Linux/UNIX/freenix servers and has been tested
 	on Linux, UNIX, Windows 9x/Me, Windows 98, Windows 200x, Windows XP, and Mac OSX clients.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671554"></a>Rsync</h3></div></div></div><p>
-<a class="indexterm" name="id2671562"></a>
-<a class="indexterm" name="id2671569"></a>
-<a class="indexterm" name="id2671575"></a>
-<a class="indexterm" name="id2671582"></a>
-<a class="indexterm" name="id2671589"></a>
-<a class="indexterm" name="id2671596"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671692"></a>Rsync</h3></div></div></div><p>
+<a class="indexterm" name="id2671700"></a>
+<a class="indexterm" name="id2671707"></a>
+<a class="indexterm" name="id2671713"></a>
+<a class="indexterm" name="id2671720"></a>
+<a class="indexterm" name="id2671727"></a>
+<a class="indexterm" name="id2671734"></a>
 	<code class="literal">rsync</code> is a flexible program for efficiently copying files or
 		directory trees.</p><p><code class="literal">rsync</code> has many options to select which files will be copied
 	  and how they are to be transferred. It may be used as an
 	  alternative to <code class="literal">ftp, http, scp</code>, or <code class="literal">rcp</code>.</p><p>
-<a class="indexterm" name="id2671635"></a>
-<a class="indexterm" name="id2671642"></a>
-<a class="indexterm" name="id2671649"></a>
+<a class="indexterm" name="id2671773"></a>
+<a class="indexterm" name="id2671780"></a>
+<a class="indexterm" name="id2671787"></a>
 	The rsync remote-update protocol allows rsync to transfer just
 	  the differences between two sets of files across the network link,
 	  using an efficient checksum-search algorithm described in the
@@ -107,10 +107,10 @@ The following three free software projects might also merit consideration.
 		  </p></li><li><p>
 		    Support for anonymous or authenticated rsync servers (ideal for
 		    mirroring).
-		  </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671724"></a>Amanda</h3></div></div></div><p>
-	<a class="indexterm" name="id2671732"></a>
-<a class="indexterm" name="id2671738"></a>
-<a class="indexterm" name="id2671745"></a>
+		  </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671862"></a>Amanda</h3></div></div></div><p>
+	<a class="indexterm" name="id2671869"></a>
+<a class="indexterm" name="id2671876"></a>
+<a class="indexterm" name="id2671883"></a>
 	Amanda, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that
 	allows the administrator of a LAN to set up a single master backup server to back up
 	multiple hosts to a single large capacity tape drive. Amanda uses native dump and/or
@@ -119,8 +119,8 @@ The following three free software projects might also merit consideration.
 	</p><p>
 	For more information regarding Amanda, please check the <a class="ulink" href="http://www.amanda.org/" target="_top">
 	www.amanda.org/ site</a>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671772"></a>BOBS: Browseable Online Backup System</h3></div></div></div><p>
-	<a class="indexterm" name="id2671781"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671910"></a>BOBS: Browseable Online Backup System</h3></div></div></div><p>
+	<a class="indexterm" name="id2671919"></a>
 	Browseable Online Backup System (BOBS) is a complete online backup system. Uses large
 	disks for storing backups and lets users browse the files using a Web browser. Handles
 	some special files like AppleDouble and icon files.
diff --git a/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html b/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html
index 2b2c63ff7b..a04a911570 100644
--- a/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html
+++ b/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�22.�CUPS Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support"><link rel="next" href="VFS.html" title="Chapter�23.�Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�22.�CUPS Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter�22.�CUPS Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="orgname">Danka Deutschland GmbH </span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span>�<div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> (27 Jan 2004) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632896">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632902">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632962">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633679">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634056">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634359">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634646">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636764">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636922">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637109">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637277">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637547">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637850">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638424">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638437">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638506">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639941">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640064">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640159">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640176">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640238">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640414">Network Printing (Windows Clients and UNIX/Samba Print
-Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640432">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640622">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640702">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640792">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640836">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640904">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640919">Printer Drivers Running in Kernel Mode Cause Many
-Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640957">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640975">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641105">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641128">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641226">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641746">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641865">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641890">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642892">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643014">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643095">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643757">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643862">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645523">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645591">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645657">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645708">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646003">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646814">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647287">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647322">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647376">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647558">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647709">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647775">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647815">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647829">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648122">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648207">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648346">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648699">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648810">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648816">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648892">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648930">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649005">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649029">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649120">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649172">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649209">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649245">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649280">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649313">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649354">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649379">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649426">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649709">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649764">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649814">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649981">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650035">Overview of the CUPS Printing Processes</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632896"></a>Introduction</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632902"></a>Features and Benefits</h3></div></div></div><p>
-<a class="indexterm" name="id2632910"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�22.�CUPS Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support"><link rel="next" href="VFS.html" title="Chapter�23.�Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�22.�CUPS Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter�22.�CUPS Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="orgname">Danka Deutschland GmbH </span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span>�<div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> (27 Jan 2004) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632975">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632981">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633040">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633768">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634145">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634448">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634735">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636855">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637012">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637200">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637368">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637637">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637941">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638515">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638528">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638596">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640032">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640155">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640249">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640266">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640328">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640504">Network Printing (Windows Clients and UNIX/Samba Print
+Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640522">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640713">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640792">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640882">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640927">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640995">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641009">Printer Drivers Running in Kernel Mode Cause Many
+Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641048">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641066">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641196">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641218">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641316">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641837">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641956">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641981">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643037">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643159">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643240">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643902">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644007">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645668">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645735">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645802">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645852">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646148">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646969">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647442">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647478">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647532">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647713">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647858">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647924">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647964">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647978">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648271">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648356">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648495">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648838">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648950">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648956">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649032">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649070">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649144">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649169">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649260">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649311">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649349">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649384">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649419">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649452">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649493">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649519">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649565">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649848">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649904">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649954">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650121">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650175">Overview of the CUPS Printing Processes</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632975"></a>Introduction</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632981"></a>Features and Benefits</h3></div></div></div><p>
+<a class="indexterm" name="id2632989"></a>
 		The Common UNIX Print System (<a class="ulink" href="http://www.cups.org/" target="_top">CUPS</a>)
 		has become quite popular. All major Linux distributions now ship it as their default printing
 		system. To many, it is still a mystical tool. Mostly, it just works.  People tend to regard
@@ -11,21 +11,21 @@ Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.htm
 		<a class="link" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support">Classical Printing</a>, which contains much information
 		that is also relevant to CUPS.
 		</p><p>
-<a class="indexterm" name="id2632945"></a>
+<a class="indexterm" name="id2633024"></a>
 		CUPS sports quite a few unique and powerful features. While its basic functions may be grasped quite
 		easily, they are also new. Because it is different from other, more traditional printing systems, it is best
 		not to try to apply any prior knowledge about printing to this new system. Rather, try to understand CUPS from
 		the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most
 		basic things first.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632962"></a>Overview</h3></div></div></div><p>
-<a class="indexterm" name="id2632970"></a>
-<a class="indexterm" name="id2632977"></a>
-<a class="indexterm" name="id2632984"></a>
-<a class="indexterm" name="id2632991"></a>
-<a class="indexterm" name="id2632997"></a>
-<a class="indexterm" name="id2633007"></a>
-<a class="indexterm" name="id2633017"></a>
-<a class="indexterm" name="id2633024"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633040"></a>Overview</h3></div></div></div><p>
+<a class="indexterm" name="id2633048"></a>
+<a class="indexterm" name="id2633055"></a>
+<a class="indexterm" name="id2633062"></a>
+<a class="indexterm" name="id2633069"></a>
+<a class="indexterm" name="id2633076"></a>
+<a class="indexterm" name="id2633086"></a>
+<a class="indexterm" name="id2633095"></a>
+<a class="indexterm" name="id2633102"></a>
 	CUPS is more than just a print spooling system. It is a complete printer management system that
 	complies with the new Internet Printing Protocol (IPP). IPP is an industry and Internet Engineering Task Force
 	(IETF) standard for network printing. Many of its functions can be managed remotely (or locally) via a Web
@@ -33,19 +33,19 @@ Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.htm
 	traditional command line and several more modern GUI interfaces (GUI interfaces developed by third parties,
 	like KDE's overwhelming <a class="ulink" href="http://printing.kde.org/" target="_top">KDEPrint</a>).
 	</p><p>
-<a class="indexterm" name="id2633049"></a>
-<a class="indexterm" name="id2633056"></a>
+<a class="indexterm" name="id2633128"></a>
+<a class="indexterm" name="id2633135"></a>
 	CUPS allows creation of <span class="emphasis"><em>raw</em></span> printers (i.e., no print file format translation) as
 	well as <span class="emphasis"><em>smart</em></span> printers (i.e., CUPS does file format conversion as required for the
 	printer). In many ways, this gives CUPS capabilities similar to the MS Windows print monitoring system. Of
 	course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now explore how
 	to configure CUPS for interfacing with MS Windows print clients via Samba.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2633081"></a>Basic CUPS Support Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2633089"></a>
-<a class="indexterm" name="id2633096"></a>
-<a class="indexterm" name="id2633103"></a>
-<a class="indexterm" name="id2633110"></a>
-<a class="indexterm" name="id2633116"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2633159"></a>Basic CUPS Support Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2633168"></a>
+<a class="indexterm" name="id2633174"></a>
+<a class="indexterm" name="id2633181"></a>
+<a class="indexterm" name="id2633188"></a>
+<a class="indexterm" name="id2633195"></a>
 Printing with CUPS in the most basic <code class="filename">smb.conf</code> setup in Samba-3.0 (as was true for 2.2.x) requires just two
 parameters: <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = cups</a> and <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a>. CUPS does not need a printcap file.  However, the
 <code class="filename">cupsd.conf</code> configuration file knows of two related directives that control how such a
@@ -55,16 +55,16 @@ Legacy programs often require the existence of a printcap file containing printe
 print. Make sure CUPS is set to generate and maintain a printcap file. For details, see <code class="literal">man
 cupsd.conf</code> and other CUPS-related documentation, like the wealth of documents regarding the CUPS
 server itself available from the <a class="ulink" href="http://localhost:631/documentation.html" target="_top">CUPS</a> web site.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633196"></a>Linking smbd with libcups.so</h3></div></div></div><p>
-<a class="indexterm" name="id2633205"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633275"></a>Linking smbd with libcups.so</h3></div></div></div><p>
+<a class="indexterm" name="id2633283"></a>
 	Samba has a special relationship to CUPS. Samba can be compiled with CUPS library support.
 	Most recent installations have this support enabled. By default, CUPS linking is compiled
 	into smbd and other Samba binaries. Of course, you can use CUPS even
 	if Samba is not linked against <code class="filename">libcups.so</code>  but
 	there are some differences in required or supported configuration.
 	</p><p>
-<a class="indexterm" name="id2633230"></a>
-<a class="indexterm" name="id2633236"></a>
+<a class="indexterm" name="id2633308"></a>
+<a class="indexterm" name="id2633314"></a>
 	When Samba is compiled and linked with <code class="filename">libcups</code>, <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a>
 	uses the CUPS API to list printers, submit jobs, query queues, and so on. Otherwise it maps to the System V
 	commands with an additional <code class="literal">-oraw</code> option for printing. On a Linux
@@ -79,7 +79,7 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 [....]
 </pre><p>
 	</p><p>
-<a class="indexterm" name="id2633307"></a>
+<a class="indexterm" name="id2633386"></a>
 	The line <code class="computeroutput">libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)</code> shows
 	there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups
 	is set, then <span class="emphasis"><em>any otherwise manually set print command in <code class="filename">smb.conf</code> is ignored</em></span>.
@@ -95,14 +95,14 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	<a class="link" href="smb.conf.5.html#LPRMCOMMAND" target="_top">lprm command</a>,
 	<a class="link" href="smb.conf.5.html#QUEUEPAUSECOMMAND" target="_top">queuepause command</a> and
 	<a class="link" href="smb.conf.5.html#QUEUERESUMECOMMAND" target="_top">queue resume command</a>).
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633445"></a>Simple <code class="filename">smb.conf</code> Settings for CUPS</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633524"></a>Simple <code class="filename">smb.conf</code> Settings for CUPS</h3></div></div></div><p>
 	To summarize, <a class="link" href="CUPS-printing.html#cups-exam-simple" title="Example�22.1.�Simplest Printing-Related smb.conf">the Simplest Printing-Related 
 	<code class="filename">smb.conf</code> file</a> shows the simplest printing-related setup for <code class="filename">smb.conf</code> to 
 	enable basic CUPS support:
-	</p><div class="example"><a name="cups-exam-simple"></a><p class="title"><b>Example�22.1.�Simplest Printing-Related smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633505"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633517"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633528"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633549"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633561"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633573"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633584"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633596"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633607"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633619"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2633634"></a>
-<a class="indexterm" name="id2633641"></a>
-<a class="indexterm" name="id2633648"></a>
+	</p><div class="example"><a name="cups-exam-simple"></a><p class="title"><b>Example�22.1.�Simplest Printing-Related smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633584"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633595"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633607"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633628"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633639"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633651"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633662"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633674"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633685"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633697"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2633712"></a>
+<a class="indexterm" name="id2633719"></a>
+<a class="indexterm" name="id2633726"></a>
 	This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript
 	files submitted from Windows clients. However, most of your Windows users would not know how to send these
 	kinds of files to print without opening a GUI application. Windows clients tend to have local printer drivers
@@ -112,25 +112,25 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	hooked between the application's native format and the print data stream. If the backend printer is not a
 	PostScript device, the print data stream is &#8220;<span class="quote">binary,</span>&#8221; sensible only for the target printer. Read
 	on to learn what problem this may cause and how to avoid it.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633679"></a>More Complex CUPS <code class="filename">smb.conf</code> Settings</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633768"></a>More Complex CUPS <code class="filename">smb.conf</code> Settings</h3></div></div></div><p>
 	<a class="link" href="CUPS-printing.html#overridesettings" title="Example�22.2.�Overriding Global CUPS Settings for One Printer">The Overriding Global CUPS Settings for One Printer example</a> 
 	is a slightly more complex printing-related setup for <code class="filename">smb.conf</code>. It enables general CUPS printing
 	support for all printers, but defines one printer share, which is set up differently. 
-	</p><div class="example"><a name="overridesettings"></a><p class="title"><b>Example�22.2.�Overriding Global CUPS Settings for One Printer</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633736"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633747"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633759"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633780"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633791"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633803"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633815"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633826"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633838"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[special_printer]</code></em></td></tr><tr><td><a class="indexterm" name="id2633859"></a><em class="parameter"><code>comment = A special printer with his own settings</code></em></td></tr><tr><td><a class="indexterm" name="id2633871"></a><em class="parameter"><code>path = /var/spool/samba-special</code></em></td></tr><tr><td><a class="indexterm" name="id2633883"></a><em class="parameter"><code>printing = sysv</code></em></td></tr><tr><td><a class="indexterm" name="id2633895"></a><em class="parameter"><code>printcap = lpstat</code></em></td></tr><tr><td><a class="indexterm" name="id2633906"></a><em class="parameter"><code>print command = echo "NEW: `date`: printfile %f" &gt;&gt; /tmp/smbprn.log ; echo "     `date`: p-%p s-%s f-%f" &gt;&gt; /tmp/smbprn.log ; echo "     `date`: j-%j J-%J z-%z c-%c" &gt;&gt; /tmp/smbprn.log ; rm %f </code></em></td></tr><tr><td><a class="indexterm" name="id2633923"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633935"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633946"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633958"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2633970"></a><em class="parameter"><code>hosts deny = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2633982"></a><em class="parameter"><code>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr></table></div></div><br class="example-break"><p>
+	</p><div class="example"><a name="overridesettings"></a><p class="title"><b>Example�22.2.�Overriding Global CUPS Settings for One Printer</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633825"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633836"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633848"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633869"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633880"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633892"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633904"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633915"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633927"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[special_printer]</code></em></td></tr><tr><td><a class="indexterm" name="id2633948"></a><em class="parameter"><code>comment = A special printer with his own settings</code></em></td></tr><tr><td><a class="indexterm" name="id2633960"></a><em class="parameter"><code>path = /var/spool/samba-special</code></em></td></tr><tr><td><a class="indexterm" name="id2633972"></a><em class="parameter"><code>printing = sysv</code></em></td></tr><tr><td><a class="indexterm" name="id2633984"></a><em class="parameter"><code>printcap = lpstat</code></em></td></tr><tr><td><a class="indexterm" name="id2633995"></a><em class="parameter"><code>print command = echo "NEW: `date`: printfile %f" &gt;&gt; /tmp/smbprn.log ; echo "     `date`: p-%p s-%s f-%f" &gt;&gt; /tmp/smbprn.log ; echo "     `date`: j-%j J-%J z-%z c-%c" &gt;&gt; /tmp/smbprn.log ; rm %f </code></em></td></tr><tr><td><a class="indexterm" name="id2634012"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2634024"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2634035"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634047"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2634059"></a><em class="parameter"><code>hosts deny = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2634070"></a><em class="parameter"><code>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr></table></div></div><br class="example-break"><p>
 	This special share is only for testing purposes. It does not write the print job to a file. It just logs the job parameters
 	known to Samba into the <code class="filename">/tmp/smbprn.log</code> file and deletes the job-file. Moreover, the
 	<a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> of this share is &#8220;<span class="quote">kurt</span>&#8221; (not the &#8220;<span class="quote">@ntadmins</span>&#8221; group),
 	guest access is not allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it
 	allows access from only three hosts. To prevent CUPS from kicking in and taking over the print jobs for that share, we need to set
 	<a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv</a> and <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = lpstat</a>.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634056"></a>Advanced Configuration</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634145"></a>Advanced Configuration</h2></div></div></div><p>
 	Before we delve into all the configuration options, let us clarify a few points. <span class="emphasis"><em>Network printing
 	needs to be organized and set up correctly</em></span>. This frequently doesn't happen. Legacy systems or small
 	business LAN environments often lack design and good housekeeping.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634073"></a>Central Spooling vs. &#8220;<span class="quote">Peer-to-Peer</span>&#8221; Printing</h3></div></div></div><p>
-<a class="indexterm" name="id2634085"></a>
-	<a class="indexterm" name="id2634092"></a>
-	<a class="indexterm" name="id2634101"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634162"></a>Central Spooling vs. &#8220;<span class="quote">Peer-to-Peer</span>&#8221; Printing</h3></div></div></div><p>
+<a class="indexterm" name="id2634174"></a>
+	<a class="indexterm" name="id2634180"></a>
+	<a class="indexterm" name="id2634190"></a>
 	Many small office or home networks, as well as badly organized larger environments, allow each client a direct
 	access to available network printers. This is generally a bad idea. It often blocks one client's access to the
 	printer when another client's job is printing. It might freeze the first client's application while it is
@@ -138,9 +138,9 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	pages mixed with each other. A better concept is the use of a print server: it routes all jobs through one
 	central system, which responds immediately, takes jobs from multiple concurrent clients, and transfers them to
 	the printer(s) in the correct order.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634124"></a>Raw Print Serving: Vendor Drivers on Windows Clients</h3></div></div></div><p>
-	<a class="indexterm" name="id2634133"></a>
-	<a class="indexterm" name="id2634139"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634213"></a>Raw Print Serving: Vendor Drivers on Windows Clients</h3></div></div></div><p>
+	<a class="indexterm" name="id2634222"></a>
+	<a class="indexterm" name="id2634228"></a>
 	Most traditionally configured UNIX print servers acting on behalf of
 	Samba's Windows clients represented a really simple setup. Their only
 	task was to manage the &#8220;<span class="quote">raw</span>&#8221; spooling of all jobs handed to them by
@@ -149,8 +149,8 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	device. In this case, a native (vendor-supplied) Windows printer driver needs to
 	be installed on each and every client for the target device.
 	</p><p>
-<a class="indexterm" name="id2634161"></a>
-<a class="indexterm" name="id2634168"></a>
+<a class="indexterm" name="id2634250"></a>
+<a class="indexterm" name="id2634256"></a>
 	It is possible to configure CUPS, Samba, and your Windows clients in the
 	same traditional and simple way. When CUPS printers are configured
 	for raw print-through mode operation, it is the responsibility of the
@@ -164,15 +164,15 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	This is achieved by installation of the printer as if it were physically
 	attached to the Windows client. You then redirect output to a raw network
 	print queue. This procedure may be followed to achieve this:
-	</p><div class="procedure"><a name="id2634192"></a><p class="title"><b>Procedure�22.1.�Configuration Steps for Raw CUPS Printing Support</b></p><ol type="1"><li><p>
-<a class="indexterm" name="id2634204"></a>
+	</p><div class="procedure"><a name="id2634281"></a><p class="title"><b>Procedure�22.1.�Configuration Steps for Raw CUPS Printing Support</b></p><ol type="1"><li><p>
+<a class="indexterm" name="id2634293"></a>
 		Edit <code class="filename">/etc/cups/mime.types</code> to uncomment the line
 		near the end of the file that has:
 </p><pre class="screen">
 #application/octet-...
 </pre><p>
 		</p></li><li><p>
-<a class="indexterm" name="id2634231"></a>
+<a class="indexterm" name="id2634320"></a>
 		Do the same for the file <code class="filename">/etc/cups/mime.convs</code>.
 		</p></li><li><p>
 		Add a raw printer using the Web interface. Point your browser at
@@ -193,14 +193,14 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 		you have configured above. Example: <code class="constant">\\server\raw_q</code>.
 		Here, the name <code class="constant">raw_q</code> is the name you gave the print
 		queue in the CUPS environment.
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634359"></a>Installation of Windows Client Drivers</h3></div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634448"></a>Installation of Windows Client Drivers</h3></div></div></div><p>
 	The printer drivers on the Windows clients may be installed
 	in two functionally different ways:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Manually install the drivers locally on each client,
 	one by one; this yields the old LanMan style
 	printing and uses a <code class="filename">\\sambaserver\printershare</code>
 	type of connection.</p></li><li><p>
-	<a class="indexterm" name="id2634388"></a>
+	<a class="indexterm" name="id2634477"></a>
 			Deposit and prepare the drivers (for later download) on
 			the print server (Samba); this enables the clients to use
 	&#8220;<span class="quote">Point'n'Print</span>&#8221; to get drivers semi-automatically installed the
@@ -211,9 +211,9 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 	administrative efforts and prevents that different versions of the drivers
 	are used accidentally.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="cups-raw"></a>Explicitly Enable &#8220;<span class="quote">raw</span>&#8221; Printing for <span class="emphasis"><em>application/octet-stream</em></span></h3></div></div></div><p>
-	<a class="indexterm" name="id2634435"></a>
-	<a class="indexterm" name="id2634442"></a>
-	<a class="indexterm" name="id2634449"></a>
+	<a class="indexterm" name="id2634524"></a>
+	<a class="indexterm" name="id2634531"></a>
+	<a class="indexterm" name="id2634538"></a>
 	If you use the first option (drivers are installed on the client
 	side), there is one setting to take care of: CUPS needs to be told
 	that it should allow &#8220;<span class="quote">raw</span>&#8221; printing of deliberate (binary) file
@@ -225,10 +225,10 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 </p><pre class="programlisting">
 application/octet-stream
 </pre><p>
-	<a class="indexterm" name="id2634504"></a>
-	<a class="indexterm" name="id2634511"></a>
+	<a class="indexterm" name="id2634592"></a>
+	<a class="indexterm" name="id2634600"></a>
 	In <code class="filename">/etc/cups/mime.convs</code>, have this line:
-	<a class="indexterm" name="id2634524"></a>
+	<a class="indexterm" name="id2634613"></a>
 </p><pre class="programlisting">
 application/octet-stream   application/vnd.cups-raw   0   - 
 </pre><p>
@@ -239,8 +239,8 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	Editing the <code class="filename">mime.convs</code> and the <code class="filename">mime.types</code> file does
 	not <span class="emphasis"><em>enforce</em></span> &#8220;<span class="quote">raw</span>&#8221; printing, it only <span class="emphasis"><em>allows</em></span> it.
 	</p></div><p><b>Background.�</b>
-	<a class="indexterm" name="id2634588"></a>
-<a class="indexterm" name="id2634595"></a>
+	<a class="indexterm" name="id2634677"></a>
+<a class="indexterm" name="id2634684"></a>
 	That CUPS is a more security-aware printing system than traditional ones does not by default allow a user to
 	send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a
 	&#8220;<span class="quote">Denial of Service</span>&#8221; attack on your printer(s), causing at least the loss of a lot of paper and
@@ -254,11 +254,11 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	locally installed. If you are not interested in background information about
 	more advanced CUPS/Samba printing, simply skip the remaining sections
 	of this chapter.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634646"></a>Driver Upload Methods</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634735"></a>Driver Upload Methods</h3></div></div></div><p>
 	This section describes three familiar methods, plus one new one, by which
 	printer drivers may be uploaded.
 	</p><p>
-	<a class="indexterm" name="id2634659"></a>
+	<a class="indexterm" name="id2634748"></a>
 	If you want to use the MS-RPC-type printing, you must upload the
 	drivers onto the Samba server first (<em class="parameter"><code>[print$]</code></em>
 	share). For a discussion on how to deposit printer drivers on the
@@ -267,27 +267,27 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	chapter</a> of this book. There you will find a description or reference to
 	three methods of preparing the client drivers on the Samba server:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2634697"></a>
+		<a class="indexterm" name="id2634786"></a>
 		The GUI, &#8220;<span class="quote">Add Printer Wizard</span>&#8221; <span class="emphasis"><em>upload-from-a-Windows-client</em></span> method.
 		</p></li><li><p>
 		The command line, &#8220;<span class="quote">smbclient/rpcclient</span>&#8221; upload-from-a-UNIX-workstation method.
 		</p></li><li><p>
-		<a class="indexterm" name="id2634725"></a>
+		<a class="indexterm" name="id2634814"></a>
 		The Imprints tool set method.
 		</p></li></ul></div><p> 
-<a class="indexterm" name="id2634737"></a>
+<a class="indexterm" name="id2634826"></a>
 	These three methods apply to CUPS all the same. The <code class="literal">cupsaddsmb</code> utility is a new and more
 	convenient way to load the Windows drivers into Samba and is provided if you use CUPS.
 	</p><p>
 	<code class="literal">cupsaddsmb</code> is discussed in much detail later in this chapter. But we first
 	explore the CUPS filtering system and compare the Windows and UNIX printing architectures.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634767"></a>Advanced Intelligent Printing with PostScript Driver Download</h2></div></div></div><p>
-	<a class="indexterm" name="id2634776"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634856"></a>Advanced Intelligent Printing with PostScript Driver Download</h2></div></div></div><p>
+	<a class="indexterm" name="id2634865"></a>
 	We now know how to set up a &#8220;<span class="quote">dump</span>&#8221; print server, that is, a server that spools
 	print jobs &#8220;<span class="quote">raw</span>&#8221;, leaving the print data untouched.
 	</p><p>
 	You might need to set up CUPS in a smarter way. The reasons could be manifold:
-	</p><a class="indexterm" name="id2634800"></a><a class="indexterm" name="id2634807"></a><a class="indexterm" name="id2634814"></a><div class="itemizedlist"><ul type="disc"><li><p>Maybe your boss wants to get monthly statistics: Which
+	</p><a class="indexterm" name="id2634889"></a><a class="indexterm" name="id2634896"></a><a class="indexterm" name="id2634903"></a><div class="itemizedlist"><ul type="disc"><li><p>Maybe your boss wants to get monthly statistics: Which
 	printer did how many pages? What was the average data size of a job?
 	What was the average print run per day? What are the typical hourly
 	peaks in printing? Which department prints how much?</p></li><li><p>Maybe you are asked to set up a print quota system:
@@ -303,28 +303,28 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	Windows and UNIX printing, then a description of the
 	CUPS filtering system, how it works, and how you can tweak it.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gdipost"></a>GDI on Windows, PostScript on UNIX</h3></div></div></div><p>
-	<a class="indexterm" name="id2634883"></a>
-	<a class="indexterm" name="id2634890"></a>
+	<a class="indexterm" name="id2634972"></a>
+	<a class="indexterm" name="id2634979"></a>
 	Network printing is one of the most complicated and error-prone
 	day-to-day tasks any user or administrator may encounter. This is
 	true for all OS platforms, and there are reasons it is so.
 	</p><p>
-	<a class="indexterm" name="id2634903"></a>
-	<a class="indexterm" name="id2634910"></a>
-<a class="indexterm" name="id2634917"></a>
-<a class="indexterm" name="id2634924"></a>
-<a class="indexterm" name="id2634931"></a>
+	<a class="indexterm" name="id2634992"></a>
+	<a class="indexterm" name="id2634999"></a>
+<a class="indexterm" name="id2635006"></a>
+<a class="indexterm" name="id2635013"></a>
+<a class="indexterm" name="id2635020"></a>
 	You can't expect to throw just any file format at a printer and have it get printed. A file format conversion
 	must take place. The problem is that there is no common standard for print file formats across all
 	manufacturers and printer types. While PostScript (trademark held by Adobe) and, to an extent, PCL (trademark
 	held by Hewlett-Packard) have developed into semi-official &#8220;<span class="quote">standards</span>&#8221; by being the most widely
 	used page description languages (PDLs), there are still many manufacturers who &#8220;<span class="quote">roll their own</span>&#8221;
 	(their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, and so on).
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634960"></a>Windows Drivers, GDI, and EMF</h3></div></div></div><p>
-	<a class="indexterm" name="id2634968"></a>
-	<a class="indexterm" name="id2634974"></a>
-	<a class="indexterm" name="id2634981"></a>
-<a class="indexterm" name="id2634988"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635048"></a>Windows Drivers, GDI, and EMF</h3></div></div></div><p>
+	<a class="indexterm" name="id2635057"></a>
+	<a class="indexterm" name="id2635063"></a>
+	<a class="indexterm" name="id2635070"></a>
+<a class="indexterm" name="id2635077"></a>
 	In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all
 	application programmers have at their disposal a built-in API, the graphical device interface (GDI), as part
 	and parcel of the OS itself to base themselves on. This GDI core is used as one common unified ground for all
@@ -335,21 +335,21 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	the GDI, often produces a file format called Enhanced MetaFile (EMF). The EMF is processed by the printer
 	driver and converted to the printer-specific file format.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2635023"></a>
-<a class="indexterm" name="id2635030"></a>
-<a class="indexterm" name="id2635037"></a>
+	<a class="indexterm" name="id2635112"></a>
+<a class="indexterm" name="id2635119"></a>
+<a class="indexterm" name="id2635126"></a>
 	To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation
-	for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <a class="indexterm" name="id2635047"></a> <a class="indexterm" name="id2635054"></a>
-	<a class="indexterm" name="id2635060"></a> <a class="indexterm" name="id2635067"></a> systems.
+	for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <a class="indexterm" name="id2635136"></a> <a class="indexterm" name="id2635143"></a>
+	<a class="indexterm" name="id2635149"></a> <a class="indexterm" name="id2635156"></a> systems.
 	Apple's <span class="emphasis"><em>core graphic engine</em></span> uses a <span class="emphasis"><em>PDF</em></span> derivative for all display work.
 	</p></div><p>
-	The example in <a class="link" href="CUPS-printing.html#f1small" title="Figure�22.1.�Windows Printing to a Local Printer.">Windows Printing to a Local Printer</a> illustrates local Windows
+	The example in <a class="link" href="CUPS-printing.html#1small" title="Figure�22.1.�Windows Printing to a Local Printer.">Windows Printing to a Local Printer</a> illustrates local Windows
 	printing.
-	</p><div class="figure"><a name="f1small"></a><p class="title"><b>Figure�22.1.�Windows Printing to a Local Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/1small.png" alt="Windows Printing to a Local Printer."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635137"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div></div><p>
-	<a class="indexterm" name="id2635146"></a>
-	<a class="indexterm" name="id2635152"></a>
-	<a class="indexterm" name="id2635159"></a>
-	<a class="indexterm" name="id2635166"></a>
+	</p><div class="figure"><a name="1small"></a><p class="title"><b>Figure�22.1.�Windows Printing to a Local Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/1small.png" alt="Windows Printing to a Local Printer."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635227"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div></div><p>
+	<a class="indexterm" name="id2635235"></a>
+	<a class="indexterm" name="id2635242"></a>
+	<a class="indexterm" name="id2635249"></a>
+	<a class="indexterm" name="id2635256"></a>
 	In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server.
 	Every application is responsible for itself to create its print output. Fortunately, most use PostScript and
 	that at least gives some common ground. Unfortunately, there are many different levels of quality for this
@@ -363,16 +363,16 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	unfavorable inheritance up to the present day by looking into the various &#8220;<span class="quote">font</span>&#8221; directories on
 	your system; there are separate ones for fonts used for X display and fonts to be used on paper.
 	</p><p><b>Background.�</b>
-	<a class="indexterm" name="id2635216"></a>
-<a class="indexterm" name="id2635223"></a>
-<a class="indexterm" name="id2635230"></a>
-<a class="indexterm" name="id2635236"></a>
-<a class="indexterm" name="id2635243"></a>
-<a class="indexterm" name="id2635250"></a>
-<a class="indexterm" name="id2635257"></a>
-<a class="indexterm" name="id2635264"></a>
-<a class="indexterm" name="id2635270"></a>
-<a class="indexterm" name="id2635277"></a>
+	<a class="indexterm" name="id2635306"></a>
+<a class="indexterm" name="id2635313"></a>
+<a class="indexterm" name="id2635319"></a>
+<a class="indexterm" name="id2635326"></a>
+<a class="indexterm" name="id2635333"></a>
+<a class="indexterm" name="id2635340"></a>
+<a class="indexterm" name="id2635347"></a>
+<a class="indexterm" name="id2635353"></a>
+<a class="indexterm" name="id2635360"></a>
+<a class="indexterm" name="id2635367"></a>
 	The PostScript programming language is an &#8220;<span class="quote">invention</span>&#8221; by Adobe, but its specifications have been
 	published extensively. Its strength lies in its powerful abilities to describe graphical objects (fonts,
 	shapes, patterns, lines, curves, and dots), their attributes (color, linewidth), and the way to manipulate
@@ -384,11 +384,11 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer
 	program or on paper by a printer.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="post-and-ghost"></a>PostScript and Ghostscript</h3></div></div></div><p>
-	<a class="indexterm" name="id2635327"></a>
-	<a class="indexterm" name="id2635334"></a>
-	<a class="indexterm" name="id2635343"></a>
-<a class="indexterm" name="id2635352"></a>
-<a class="indexterm" name="id2635359"></a>
+	<a class="indexterm" name="id2635417"></a>
+	<a class="indexterm" name="id2635424"></a>
+	<a class="indexterm" name="id2635433"></a>
+<a class="indexterm" name="id2635442"></a>
+<a class="indexterm" name="id2635449"></a>
 	So UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable
 	legacy for UNIX, basic printing is fairly easy if you have PostScript printers at your disposal. The reason is
 	that these devices have a built-in PostScript language &#8220;<span class="quote">interpreter,</span>&#8221; also called a raster image
@@ -397,31 +397,31 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no
 	different than PostScript printing a file from a Windows origin.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2635388"></a>
-<a class="indexterm" name="id2635395"></a>
-<a class="indexterm" name="id2635402"></a>
+	<a class="indexterm" name="id2635478"></a>
+<a class="indexterm" name="id2635485"></a>
+<a class="indexterm" name="id2635491"></a>
 	Traditional UNIX programs and printing systems  while using PostScript  are largely not
 	PPD-aware. PPDs are &#8220;<span class="quote">PostScript Printer Description</span>&#8221; files. They enable you to specify and
 	control all options a printer supports: duplexing, stapling, and punching. Therefore, UNIX users for a long
 	time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now
-	there is CUPS. as illustrated in <a class="link" href="CUPS-printing.html#f2small" title="Figure�22.2.�Printing to a PostScript Printer.">Printing to a PostScript Printer</a>.
-	</p></div><div class="figure"><a name="f2small"></a><p class="title"><b>Figure�22.2.�Printing to a PostScript Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/2small.png" alt="Printing to a PostScript Printer."></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2635480"></a>
+	there is CUPS. as illustrated in <a class="link" href="CUPS-printing.html#2small" title="Figure�22.2.�Printing to a PostScript Printer.">Printing to a PostScript Printer</a>.
+	</p></div><div class="figure"><a name="2small"></a><p class="title"><b>Figure�22.2.�Printing to a PostScript Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/2small.png" alt="Printing to a PostScript Printer."></div></div></div><br class="figure-break"><p>
+	<a class="indexterm" name="id2635570"></a>
 	However, there are other types of printers out there. These do not know how to print PostScript. They use
 	their own PDL, often proprietary. To print to them is much more demanding. Since your UNIX applications mostly
 	produce PostScript, and since these devices do not understand PostScript, you need to convert the print files
 	to a format suitable for your printer on the host before you can send it away.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635495"></a>Ghostscript: The Software RIP for Non-PostScript Printers</h3></div></div></div><p>
-	<a class="indexterm" name="id2635504"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635586"></a>Ghostscript: The Software RIP for Non-PostScript Printers</h3></div></div></div><p>
+	<a class="indexterm" name="id2635594"></a>
 	Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter
 	used on UNIX platforms. It is a RIP in software, capable of doing a <span class="emphasis"><em>lot</em></span> of file format
 	conversions for a very broad spectrum of hardware devices as well as software file formats.  Ghostscript
 	technology and drivers are what enable PostScript printing to non-PostScript hardware. This is shown in
-	<a class="link" href="CUPS-printing.html#f3small" title="Figure�22.3.�Ghostscript as a RIP for Non-PostScript Printers.">Ghostscript as a RIP for Non-PostScript Printers</a>.
-	</p><div class="figure"><a name="f3small"></a><p class="title"><b>Figure�22.3.�Ghostscript as a RIP for Non-PostScript Printers.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/3small.png" alt="Ghostscript as a RIP for Non-PostScript Printers."></div></div></div><br class="figure-break"><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2635575"></a>
-<a class="indexterm" name="id2635582"></a>
-<a class="indexterm" name="id2635588"></a>
+	<a class="link" href="CUPS-printing.html#3small" title="Figure�22.3.�Ghostscript as a RIP for Non-PostScript Printers.">Ghostscript as a RIP for Non-PostScript Printers</a>.
+	</p><div class="figure"><a name="3small"></a><p class="title"><b>Figure�22.3.�Ghostscript as a RIP for Non-PostScript Printers.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/3small.png" alt="Ghostscript as a RIP for Non-PostScript Printers."></div></div></div><br class="figure-break"><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
+<a class="indexterm" name="id2635666"></a>
+<a class="indexterm" name="id2635672"></a>
+<a class="indexterm" name="id2635679"></a>
 	Use the &#8220;<span class="quote">gs -h</span>&#8221; command to check for all built-in &#8220;<span class="quote">devices</span>&#8221; on your Ghostscript
 	version. If you specify a parameter of <em class="parameter"><code>-sDEVICE=png256</code></em> on your Ghostscript command
 	line, you are asking Ghostscript to convert the input into a PNG file. Naming a &#8220;<span class="quote">device</span>&#8221; on the
@@ -429,14 +429,14 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	input. New Ghostscript versions are released at fairly regular intervals, now by artofcode LLC. They are
 	initially put under the &#8220;<span class="quote">AFPL</span>&#8221; license, but re-released under the GNU GPL as soon as the next
 	AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has some
-	deficiencies.  <a class="indexterm" name="id2635627"></a> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript,
+	deficiencies.  <a class="indexterm" name="id2635717"></a> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript,
 	with lots of bug-fixes, additional devices, and improvements. It is jointly maintained by developers from
 	CUPS, Gutenprint, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the &#8220;<span class="quote">cups</span>&#8221; device
 	(essential to print to non-PS printers from CUPS).
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635650"></a>PostScript Printer Description (PPD) Specification</h3></div></div></div><p>
-	<a class="indexterm" name="id2635658"></a>
-<a class="indexterm" name="id2635664"></a>
-<a class="indexterm" name="id2635671"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635740"></a>PostScript Printer Description (PPD) Specification</h3></div></div></div><p>
+	<a class="indexterm" name="id2635748"></a>
+<a class="indexterm" name="id2635755"></a>
+<a class="indexterm" name="id2635762"></a>
 	While PostScript in essence is a PDL to represent the page layout in a device-independent way, real-world
 	print jobs are always ending up being output on hardware with device-specific features. To take care of all
 	the differences in hardware and to allow for innovations, Adobe has specified a syntax and file format for
@@ -458,17 +458,17 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	PostScript, PJL, JCL, or vendor-dependent commands) into the PostScript
 	file created by the driver.
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-	<a class="indexterm" name="id2635711"></a>
-<a class="indexterm" name="id2635717"></a>
+	<a class="indexterm" name="id2635801"></a>
+<a class="indexterm" name="id2635808"></a>
 	A PostScript file that was created to contain device-specific commands
 	for achieving a certain print job output (e.g., duplexed, stapled, and
 	punched) on a specific target machine may not print as expected, or
 	may not be printable at all on other models; it also may not be fit
 	for further processing by software (e.g., by a PDF distilling program).
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635733"></a>Using Windows-Formatted Vendor PPDs</h3></div></div></div><p>
-<a class="indexterm" name="id2635741"></a>
-<a class="indexterm" name="id2635748"></a>
-<a class="indexterm" name="id2635754"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635823"></a>Using Windows-Formatted Vendor PPDs</h3></div></div></div><p>
+<a class="indexterm" name="id2635831"></a>
+<a class="indexterm" name="id2635838"></a>
+<a class="indexterm" name="id2635845"></a>
 	CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if
 	a vendor does not mention our favorite OS in his or her manuals and brochures, you can safely trust this:
 	<span class="emphasis"><em>If you get the Windows NT version of the PPD, you can use it unchanged in CUPS</em></span> and thus
@@ -479,31 +479,31 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	parsing and checking code enabled; in case of printing trouble, this online resource should be one of your
 	first pit stops.
 	</p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-	<a class="indexterm" name="id2635794"></a>
-	<a class="indexterm" name="id2635801"></a>
+	<a class="indexterm" name="id2635884"></a>
+	<a class="indexterm" name="id2635891"></a>
 	For real PostScript printers, <span class="emphasis"><em>do not</em></span> use the <span class="emphasis"><em>Foomatic</em></span> or
 	<span class="emphasis"><em>cupsomatic</em></span> PPDs from Linuxprinting.org. With these devices, the original vendor-provided
 	PPDs are always the first choice.
 	</p></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2635825"></a>
+<a class="indexterm" name="id2635916"></a>
 	If you are looking for an original vendor-provided PPD of a specific device, and you know that an NT4 box (or
 	any other Windows box) on your LAN has the PostScript driver installed, just use <code class="literal">smbclient
 	//NT4-box/print\$ -U username</code> to access the Windows directory where all printer driver files are
 	stored. First look in the <code class="filename">W32X86/2</code> subdirectory for the PPD you are seeking.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635852"></a>CUPS Also Uses PPDs for Non-PostScript Printers</h3></div></div></div><p>
-<a class="indexterm" name="id2635861"></a>
-<a class="indexterm" name="id2635868"></a>
-<a class="indexterm" name="id2635874"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635943"></a>CUPS Also Uses PPDs for Non-PostScript Printers</h3></div></div></div><p>
+<a class="indexterm" name="id2635951"></a>
+<a class="indexterm" name="id2635958"></a>
+<a class="indexterm" name="id2635965"></a>
 	CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available
 	from the vendors (and no, you can't just take the PPD of a PostScript printer with the same model name and
 	hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers, we
 	first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2635892"></a>The CUPS Filtering Architecture</h2></div></div></div><p>
-<a class="indexterm" name="id2635900"></a>
-<a class="indexterm" name="id2635907"></a>
-<a class="indexterm" name="id2635914"></a>
-<a class="indexterm" name="id2635920"></a>
-<a class="indexterm" name="id2635927"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2635982"></a>The CUPS Filtering Architecture</h2></div></div></div><p>
+<a class="indexterm" name="id2635990"></a>
+<a class="indexterm" name="id2635997"></a>
+<a class="indexterm" name="id2636004"></a>
+<a class="indexterm" name="id2636011"></a>
+<a class="indexterm" name="id2636018"></a>
 The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some
 other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data
 file formats under the label of various MIME types. Every incoming print file is subjected to an initial
@@ -514,82 +514,82 @@ given input data format.
 </p><p>
 If CUPS rasterizes a PostScript file natively to a bitmap, this is done in two stages:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2635957"></a>
-<a class="indexterm" name="id2635964"></a>
+<a class="indexterm" name="id2636047"></a>
+<a class="indexterm" name="id2636054"></a>
 	The first stage uses a Ghostscript device named &#8220;<span class="quote">cups</span>&#8221;
 	(this is since version 1.1.15) and produces a generic raster format
 	called &#8220;<span class="quote">CUPS raster</span>&#8221;.
 	</p></li><li><p>
-<a class="indexterm" name="id2635984"></a>
+<a class="indexterm" name="id2636075"></a>
 	The second stage uses a &#8220;<span class="quote">raster driver</span>&#8221; that converts
 	the generic CUPS raster to a device-specific raster.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2636001"></a>
-<a class="indexterm" name="id2636008"></a>
-<a class="indexterm" name="id2636015"></a>
+<a class="indexterm" name="id2636092"></a>
+<a class="indexterm" name="id2636098"></a>
+<a class="indexterm" name="id2636105"></a>
 Make sure your Ghostscript version has the &#8220;<span class="quote">cups</span>&#8221; device compiled in (check with <code class="literal">gs -h |
 grep cups</code>). Otherwise you may encounter the dreaded <code class="computeroutput">Unable to convert file
 0</code> in your CUPS error_log file. To have &#8220;<span class="quote">cups</span>&#8221; as a device in your Ghostscript,
 you either need to patch GNU Ghostscript and recompile or use
-<a class="indexterm" name="id2636045"></a><a class="ulink" href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The superior alternative is ESP
+<a class="indexterm" name="id2636136"></a><a class="ulink" href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The superior alternative is ESP
 Ghostscript. It supports not just CUPS, but 300 other devices (while GNU Ghostscript supports only about 180).
 Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers, too.
 It is now recommended by Linuxprinting.org for all spoolers.
 </p><p>
-<a class="indexterm" name="id2636068"></a>
-<a class="indexterm" name="id2636075"></a>
-<a class="indexterm" name="id2636082"></a>
-<a class="indexterm" name="id2636089"></a>
+<a class="indexterm" name="id2636159"></a>
+<a class="indexterm" name="id2636165"></a>
+<a class="indexterm" name="id2636172"></a>
+<a class="indexterm" name="id2636179"></a>
 CUPS printers may be set up to use external rendering paths. One of the most common is provided by the
 Foomatic/cupsomatic concept from <a class="ulink" href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a>. This
 uses the classical Ghostscript approach, doing everything in one step.  It does not use the
 &#8220;<span class="quote">cups</span>&#8221; device, but one of the many others. However, even for Foomatic/cupsomatic usage, best
-results and <a class="indexterm" name="id2636111"></a> broadest printer
+results and <a class="indexterm" name="id2636202"></a> broadest printer
 model support is provided by ESP Ghostscript (more about Foomatic/cupsomatic, particularly the new version
 called now <span class="emphasis"><em>foomatic-rip</em></span>, follows).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636128"></a>MIME Types and CUPS Filters</h3></div></div></div><p>
-	<a class="indexterm" name="id2636136"></a>
-	<a class="indexterm" name="id2636145"></a>
-<a class="indexterm" name="id2636152"></a>
-<a class="indexterm" name="id2636158"></a>
-<a class="indexterm" name="id2636165"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636218"></a>MIME Types and CUPS Filters</h3></div></div></div><p>
+	<a class="indexterm" name="id2636226"></a>
+	<a class="indexterm" name="id2636235"></a>
+<a class="indexterm" name="id2636242"></a>
+<a class="indexterm" name="id2636249"></a>
+<a class="indexterm" name="id2636256"></a>
 	CUPS reads the file <code class="filename">/etc/cups/mime.types</code> (and all other files carrying a
 	<code class="filename">*.types</code> suffix in the same directory) upon startup. These files contain the MIME type
 	recognition rules that are applied when CUPS runs its autotyping routines. The rule syntax is explained in the
 	man page for <code class="filename">mime.types</code> and in the comments section of the
 	<code class="filename">mime.types</code> file itself. A simple rule reads like this:
-	<a class="indexterm" name="id2636202"></a>
+	<a class="indexterm" name="id2636292"></a>
 </p><pre class="programlisting">
 application/pdf         pdf string(0,%PDF)
 </pre><p>
-<a class="indexterm" name="id2636215"></a>
-<a class="indexterm" name="id2636222"></a>
+<a class="indexterm" name="id2636306"></a>
+<a class="indexterm" name="id2636313"></a>
 	This means if a filename has a <code class="filename">.pdf</code> suffix or if the magic string
 	<span class="emphasis"><em>%PDF</em></span> is right at the beginning of the file itself (offset 0 from the start), then it is a
 	PDF file (<em class="parameter"><code>application/pdf</code></em>).  Another rule is this:
 </p><pre class="programlisting">
 application/postscript  ai eps ps string(0,%!) string(0,&lt;04&gt;%!)
 </pre><p>
-<a class="indexterm" name="id2636255"></a>
-<a class="indexterm" name="id2636262"></a>
-<a class="indexterm" name="id2636269"></a>
-<a class="indexterm" name="id2636276"></a>
-<a class="indexterm" name="id2636283"></a>
-<a class="indexterm" name="id2636290"></a>
+<a class="indexterm" name="id2636346"></a>
+<a class="indexterm" name="id2636353"></a>
+<a class="indexterm" name="id2636360"></a>
+<a class="indexterm" name="id2636366"></a>
+<a class="indexterm" name="id2636373"></a>
+<a class="indexterm" name="id2636380"></a>
 	If the filename has one of the suffixes <code class="filename">.ai</code>, <code class="filename">.eps</code>,
 	<code class="filename">.ps</code>, or if the file itself starts with one of the strings <span class="emphasis"><em>%!</em></span> or
 	<span class="emphasis"><em>&lt;04&gt;%!</em></span>, it is a generic PostScript file
 	(<em class="parameter"><code>application/postscript</code></em>).
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2636334"></a>
+<a class="indexterm" name="id2636424"></a>
 	Don't confuse the other mime.types files your system might be using
 	with the one in the <code class="filename">/etc/cups/</code> directory.
 	</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2636353"></a>
-<a class="indexterm" name="id2636360"></a>
-<a class="indexterm" name="id2636367"></a>
-<a class="indexterm" name="id2636373"></a>
-<a class="indexterm" name="id2636380"></a>
+<a class="indexterm" name="id2636443"></a>
+<a class="indexterm" name="id2636450"></a>
+<a class="indexterm" name="id2636457"></a>
+<a class="indexterm" name="id2636464"></a>
+<a class="indexterm" name="id2636470"></a>
 	There is an important difference between two similar MIME types in CUPS: one is
 	<em class="parameter"><code>application/postscript</code></em>, the other is
 	<em class="parameter"><code>application/vnd.cups-postscript</code></em>. While <em class="parameter"><code>application/postscript</code></em> is
@@ -600,32 +600,32 @@ application/postscript  ai eps ps string(0,%!) string(0,&lt;04&gt;%!)
 	(<em class="parameter"><code>application/vnd.cups-postscript</code></em>) is the responsibility of the CUPS
 	<em class="parameter"><code>pstops</code></em> filter. pstops uses information contained in the PPD to do the transformation.
 	</p></div><p>
-<a class="indexterm" name="id2636442"></a>
-<a class="indexterm" name="id2636449"></a>
-<a class="indexterm" name="id2636456"></a>
-<a class="indexterm" name="id2636463"></a>
-<a class="indexterm" name="id2636469"></a>
-<a class="indexterm" name="id2636476"></a>
-<a class="indexterm" name="id2636482"></a>
-<a class="indexterm" name="id2636489"></a>
-<a class="indexterm" name="id2636496"></a>
-<a class="indexterm" name="id2636503"></a>
-<a class="indexterm" name="id2636509"></a>
-<a class="indexterm" name="id2636516"></a>
-<a class="indexterm" name="id2636523"></a>
-<a class="indexterm" name="id2636530"></a>
-<a class="indexterm" name="id2636537"></a>
-<a class="indexterm" name="id2636544"></a>
+<a class="indexterm" name="id2636533"></a>
+<a class="indexterm" name="id2636540"></a>
+<a class="indexterm" name="id2636547"></a>
+<a class="indexterm" name="id2636553"></a>
+<a class="indexterm" name="id2636560"></a>
+<a class="indexterm" name="id2636566"></a>
+<a class="indexterm" name="id2636573"></a>
+<a class="indexterm" name="id2636580"></a>
+<a class="indexterm" name="id2636586"></a>
+<a class="indexterm" name="id2636593"></a>
+<a class="indexterm" name="id2636600"></a>
+<a class="indexterm" name="id2636607"></a>
+<a class="indexterm" name="id2636614"></a>
+<a class="indexterm" name="id2636621"></a>
+<a class="indexterm" name="id2636627"></a>
+<a class="indexterm" name="id2636634"></a>
 	CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and
 	many image formats (GIF, PNG, TIFF, JPEG, Photo-CD, SUN-Raster,
 	PNM, PBM, SGI-RGB, and more) and their associated MIME types
 	with its filters.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636556"></a>MIME Type Conversion Rules</h3></div></div></div><p>
-	<a class="indexterm" name="id2636564"></a>
-	<a class="indexterm" name="id2636571"></a>
-<a class="indexterm" name="id2636578"></a>
-<a class="indexterm" name="id2636585"></a>
-<a class="indexterm" name="id2636592"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636647"></a>MIME Type Conversion Rules</h3></div></div></div><p>
+	<a class="indexterm" name="id2636655"></a>
+	<a class="indexterm" name="id2636662"></a>
+<a class="indexterm" name="id2636668"></a>
+<a class="indexterm" name="id2636676"></a>
+<a class="indexterm" name="id2636682"></a>
 	CUPS reads the file <code class="filename">/etc/cups/mime.convs</code>
 	(and all other files named with a <code class="filename">*.convs</code>
 	suffix in the same directory) upon startup. These files contain
@@ -636,44 +636,44 @@ application/postscript  ai eps ps string(0,%!) string(0,&lt;04&gt;%!)
 </p><pre class="programlisting">
 application/pdf         application/postscript   33   pdftops
 </pre><p>
-<a class="indexterm" name="id2636624"></a>
+<a class="indexterm" name="id2636714"></a>
 	This means that the <em class="parameter"><code>pdftops</code></em> filter will take
 	<em class="parameter"><code>application/pdf</code></em> as input and produce
 	<em class="parameter"><code>application/postscript</code></em> as output; the virtual
 	cost of this operation is 33 CUPS-$. The next filter is more
 	expensive, costing 66 CUPS-$:
-	<a class="indexterm" name="id2636652"></a>
+	<a class="indexterm" name="id2636742"></a>
 </p><pre class="programlisting">
 application/vnd.hp-HPGL application/postscript   66   hpgltops
 </pre><p>
-<a class="indexterm" name="id2636666"></a>
+<a class="indexterm" name="id2636756"></a>
 	This is the <em class="parameter"><code>hpgltops</code></em>, which processes HP-GL
 	plotter files to PostScript.
-	<a class="indexterm" name="id2636680"></a>
+	<a class="indexterm" name="id2636770"></a>
 </p><pre class="programlisting">
 application/octet-stream
 </pre><p>
 	Here are two more examples: 
-	<a class="indexterm" name="id2636693"></a>
-<a class="indexterm" name="id2636700"></a>
-<a class="indexterm" name="id2636707"></a>
-<a class="indexterm" name="id2636714"></a>
+	<a class="indexterm" name="id2636784"></a>
+<a class="indexterm" name="id2636791"></a>
+<a class="indexterm" name="id2636798"></a>
+<a class="indexterm" name="id2636804"></a>
 </p><pre class="programlisting">
 application/x-shell     application/postscript   33    texttops
 text/plain              application/postscript   33    texttops
 </pre><p>
-<a class="indexterm" name="id2636729"></a>
+<a class="indexterm" name="id2636819"></a>
 	The last two examples name the <em class="parameter"><code>texttops</code></em> filter to work on
 	<em class="parameter"><code>text/plain</code></em> as well as on <em class="parameter"><code>application/x-shell</code></em>. (Hint: This
 	differentiation is needed for the syntax highlighting feature of <em class="parameter"><code>texttops</code></em>).
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636764"></a>Filtering  Overview</h3></div></div></div><p>
-	<a class="indexterm" name="id2636772"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636855"></a>Filtering  Overview</h3></div></div></div><p>
+	<a class="indexterm" name="id2636862"></a>
 	There are many more combinations named in <code class="filename">mime.convs</code>. However, you are not limited to use
 	the ones predefined there. You can plug in any filter you like to the CUPS framework. It must meet, or must be
 	made to meet, some minimal requirements. If you find (or write) a cool conversion filter of some kind, make
 	sure it complies with what CUPS needs and put in the right lines in <code class="filename">mime.types</code> and
 	<code class="filename">mime.convs</code>; then it will work seamlessly inside CUPS.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2636805"></a>Filter Requirements</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2636895"></a>Filter Requirements</h4></div></div></div><p>
 	The &#8220;<span class="quote">CUPS requirements</span>&#8221; for filters are simple. Take filenames or <code class="filename">stdin</code> as
 	input and write to <code class="filename">stdout</code>. They should take these arguments:
 	</p><div class="variablelist"><dl><dt><span class="term">printer</span></dt><dd><p>
@@ -692,24 +692,24 @@ text/plain              application/postscript   33    texttops
 			(optionally) The print request file (if missing, filters expect data
 			fed through <code class="filename">stdin</code>). In most cases, it is easy to
 			write a simple wrapper script around existing filters to make them work with CUPS.
-			</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636922"></a>Prefilters</h3></div></div></div><p>
-	<a class="indexterm" name="id2636929"></a>
-<a class="indexterm" name="id2636936"></a>
-<a class="indexterm" name="id2636943"></a>
+			</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637012"></a>Prefilters</h3></div></div></div><p>
+	<a class="indexterm" name="id2637020"></a>
+<a class="indexterm" name="id2637027"></a>
+<a class="indexterm" name="id2637034"></a>
 	As previously stated, PostScript is the central file format to any UNIX-based
 	printing system. From PostScript, CUPS generates raster data to feed
 	non-PostScript printers.
 	</p><p>
-<a class="indexterm" name="id2636956"></a>
-<a class="indexterm" name="id2636963"></a>
-<a class="indexterm" name="id2636970"></a>
-<a class="indexterm" name="id2636977"></a>
-<a class="indexterm" name="id2636983"></a>
-<a class="indexterm" name="id2636990"></a>
-<a class="indexterm" name="id2636996"></a>
-<a class="indexterm" name="id2637003"></a>
-<a class="indexterm" name="id2637010"></a>
-<a class="indexterm" name="id2637017"></a>
+<a class="indexterm" name="id2637047"></a>
+<a class="indexterm" name="id2637054"></a>
+<a class="indexterm" name="id2637060"></a>
+<a class="indexterm" name="id2637067"></a>
+<a class="indexterm" name="id2637074"></a>
+<a class="indexterm" name="id2637080"></a>
+<a class="indexterm" name="id2637087"></a>
+<a class="indexterm" name="id2637094"></a>
+<a class="indexterm" name="id2637101"></a>
+<a class="indexterm" name="id2637108"></a>
 	But what happens if you send one of the supported non-PS formats to print? Then CUPS runs
 	&#8220;<span class="quote">prefilters</span>&#8221; on these input formats to generate PostScript first. There are prefilters to create
 	PostScript from ASCII text, PDF, DVI, or HP-GL. The outcome of these filters is always of MIME type
@@ -717,21 +717,21 @@ text/plain              application/postscript   33    texttops
 	embedded into the PostScript by CUPS and that the next filter to be called is pstops). Another prefilter is
 	running on all supported image formats, the <em class="parameter"><code>imagetops</code></em> filter. Its outcome is always of
 	MIME type <em class="parameter"><code>application/vnd.cups-postscript</code></em> (not application/postscript), meaning it has
-	the print options already embedded into the file. This is shown in <a class="link" href="CUPS-printing.html#f4small" title="Figure�22.4.�Prefiltering in CUPS to Form PostScript.">Prefiltering in
+	the print options already embedded into the file. This is shown in <a class="link" href="CUPS-printing.html#4small" title="Figure�22.4.�Prefiltering in CUPS to Form PostScript.">Prefiltering in
 	CUPS to Form PostScript</a>.
-	</p><div class="figure"><a name="f4small"></a><p class="title"><b>Figure�22.4.�Prefiltering in CUPS to Form PostScript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/4small.png" width="135" alt="Prefiltering in CUPS to Form PostScript."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637109"></a>pstops</h3></div></div></div><p>
-<a class="indexterm" name="id2637117"></a>
-<a class="indexterm" name="id2637124"></a>
-<a class="indexterm" name="id2637131"></a>
-<a class="indexterm" name="id2637138"></a>
-<a class="indexterm" name="id2637145"></a>
-<a class="indexterm" name="id2637152"></a>
-<a class="indexterm" name="id2637158"></a>
+	</p><div class="figure"><a name="4small"></a><p class="title"><b>Figure�22.4.�Prefiltering in CUPS to Form PostScript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/4small.png" width="135" alt="Prefiltering in CUPS to Form PostScript."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637200"></a>pstops</h3></div></div></div><p>
+<a class="indexterm" name="id2637208"></a>
+<a class="indexterm" name="id2637215"></a>
+<a class="indexterm" name="id2637222"></a>
+<a class="indexterm" name="id2637229"></a>
+<a class="indexterm" name="id2637236"></a>
+<a class="indexterm" name="id2637243"></a>
+<a class="indexterm" name="id2637250"></a>
 	<span class="emphasis"><em>pstops</em></span> is a filter that is used to convert <em class="parameter"><code>application/postscript</code></em> to
 	<em class="parameter"><code>application/vnd.cups-postscript</code></em>. As stated earlier, this filter inserts all
 	device-specific print options (commands to the printer to ask for the duplexing of output, or stapling and
-	punching it, and so on) into the PostScript file. An example is illustrated in <a class="link" href="CUPS-printing.html#f5small" title="Figure�22.5.�Adding Device-Specific Print Options.">Adding Device-Specific Print Options</a>.
-	</p><div class="figure"><a name="f5small"></a><p class="title"><b>Figure�22.5.�Adding Device-Specific Print Options.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/5small.png" width="135" alt="Adding Device-Specific Print Options."></div></div></div><br class="figure-break"><p>
+	punching it, and so on) into the PostScript file. An example is illustrated in <a class="link" href="CUPS-printing.html#5small" title="Figure�22.5.�Adding Device-Specific Print Options.">Adding Device-Specific Print Options</a>.
+	</p><div class="figure"><a name="5small"></a><p class="title"><b>Figure�22.5.�Adding Device-Specific Print Options.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/5small.png" width="135" alt="Adding Device-Specific Print Options."></div></div></div><br class="figure-break"><p>
 	This is not all. Other tasks performed by it are:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 		Selecting the range of pages to be printed (e.g., you can choose to
@@ -742,10 +742,10 @@ text/plain              application/postscript   33    texttops
 		so-called &#8220;<span class="quote">number-up</span>&#8221; function).
 		</p></li><li><p>Counting the pages of the job to insert the accounting
 		information into the <code class="filename">/var/log/cups/page_log</code>.
-		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637277"></a>pstoraster</h3></div></div></div><p>
-<a class="indexterm" name="id2637285"></a>
-<a class="indexterm" name="id2637292"></a>
-<a class="indexterm" name="id2637299"></a>
+		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637368"></a>pstoraster</h3></div></div></div><p>
+<a class="indexterm" name="id2637376"></a>
+<a class="indexterm" name="id2637382"></a>
+<a class="indexterm" name="id2637389"></a>
 	<em class="parameter"><code>pstoraster</code></em> is at the core of the CUPS filtering system. It is responsible for the first
 	stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is
 	application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a
@@ -753,10 +753,10 @@ text/plain              application/postscript   33    texttops
 	generate device-specific printer data. This is shown in <a class="link" href="CUPS-printing.html#cups-raster" title="Figure�22.6.�PostScript to Intermediate Raster Format.">the PostScript to
 	Intermediate Raster Format diagram</a>.
 	</p><div class="figure"><a name="cups-raster"></a><p class="title"><b>Figure�22.6.�PostScript to Intermediate Raster Format.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/6small.png" width="135" alt="PostScript to Intermediate Raster Format."></div></div></div><br class="figure-break"><p>
-<a class="indexterm" name="id2637375"></a>
-<a class="indexterm" name="id2637381"></a>
-<a class="indexterm" name="id2637388"></a>
-<a class="indexterm" name="id2637395"></a>
+<a class="indexterm" name="id2637465"></a>
+<a class="indexterm" name="id2637472"></a>
+<a class="indexterm" name="id2637479"></a>
+<a class="indexterm" name="id2637486"></a>
 	CUPS raster is a generic raster format with powerful features. It is able to include per-page information,
 	color profiles, and more, to be used by the downstream raster drivers. Its MIME type is registered with IANA
 	and its specification is, of course, completely open. It is designed to make it quite easy and inexpensive for
@@ -766,10 +766,10 @@ text/plain              application/postscript   33    texttops
 	raster drivers). This is illustrated in <a class="link" href="CUPS-printing.html#cups-raster2" title="Figure�22.7.�CUPS-Raster Production Using Ghostscript.">the CUPS-Raster Production Using
 	Ghostscript illustration</a>.
 	</p><div class="figure"><a name="cups-raster2"></a><p class="title"><b>Figure�22.7.�CUPS-Raster Production Using Ghostscript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/7small.png" alt="CUPS-Raster Production Using Ghostscript."></div></div></div><br class="figure-break"><p>
-<a class="indexterm" name="id2637468"></a>
-<a class="indexterm" name="id2637474"></a>
-<a class="indexterm" name="id2637481"></a>
-<a class="indexterm" name="id2637488"></a>
+<a class="indexterm" name="id2637558"></a>
+<a class="indexterm" name="id2637565"></a>
+<a class="indexterm" name="id2637572"></a>
+<a class="indexterm" name="id2637579"></a>
 	CUPS versions before version 1.1.15 shipped a binary (or source code) standalone filter, named
 	<em class="parameter"><code>pstoraster</code></em>. <em class="parameter"><code>pstoraster</code></em>, which was derived from GNU Ghostscript
 	5.50 and could be installed instead of and in addition to any GNU or AFPL Ghostscript package without
@@ -780,27 +780,27 @@ text/plain              application/postscript   33    texttops
 	now a simple shell script calling <code class="literal">gs</code> with the <code class="literal">-sDEVICE=cups</code> parameter.
 	If your Ghostscript fails when this command is executed: <code class="literal">gs -h |grep cups</code>, you might not 
 	be able to print, update your Ghostscript.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637547"></a>imagetops and imagetoraster</h3></div></div></div><p>
-<a class="indexterm" name="id2637555"></a>
-<a class="indexterm" name="id2637562"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637637"></a>imagetops and imagetoraster</h3></div></div></div><p>
+<a class="indexterm" name="id2637645"></a>
+<a class="indexterm" name="id2637652"></a>
 	In the section about prefilters, we mentioned the prefilter
 	that generates PostScript from image formats. The <em class="parameter"><code>imagetoraster</code></em>
 	filter is used to convert directly from image to raster, without the
 	intermediate PostScript stage. It is used more often than the previously
 	mentioned prefilters. We summarize in a flowchart the image file
 	filtering in <a class="link" href="CUPS-printing.html#small8" title="Figure�22.8.�Image Format to CUPS-Raster Format Conversion.">the Image Format to CUPS-Raster Format Conversion illustration</a>.
-	</p><div class="figure"><a name="small8"></a><p class="title"><b>Figure�22.8.�Image Format to CUPS-Raster Format Conversion.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/8small.png" alt="Image Format to CUPS-Raster Format Conversion."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637631"></a>rasterto [printers specific]</h3></div></div></div><p>
-<a class="indexterm" name="id2637639"></a>
-<a class="indexterm" name="id2637646"></a>
-<a class="indexterm" name="id2637653"></a>
-<a class="indexterm" name="id2637660"></a>
-<a class="indexterm" name="id2637667"></a>
-<a class="indexterm" name="id2637674"></a>
-<a class="indexterm" name="id2637681"></a>
-<a class="indexterm" name="id2637688"></a>
-<a class="indexterm" name="id2637694"></a>
-<a class="indexterm" name="id2637701"></a>
-<a class="indexterm" name="id2637708"></a>
+	</p><div class="figure"><a name="small8"></a><p class="title"><b>Figure�22.8.�Image Format to CUPS-Raster Format Conversion.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/8small.png" alt="Image Format to CUPS-Raster Format Conversion."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637722"></a>rasterto [printers specific]</h3></div></div></div><p>
+<a class="indexterm" name="id2637730"></a>
+<a class="indexterm" name="id2637737"></a>
+<a class="indexterm" name="id2637744"></a>
+<a class="indexterm" name="id2637751"></a>
+<a class="indexterm" name="id2637758"></a>
+<a class="indexterm" name="id2637764"></a>
+<a class="indexterm" name="id2637771"></a>
+<a class="indexterm" name="id2637778"></a>
+<a class="indexterm" name="id2637785"></a>
+<a class="indexterm" name="id2637792"></a>
+<a class="indexterm" name="id2637799"></a>
 	CUPS ships with quite a variety of raster drivers for processing CUPS raster. On my system, I find in
 	/usr/lib/cups/filter/ the following: <em class="parameter"><code>rastertoalps</code></em>, <em class="parameter"><code>rastertobj</code></em>,
 	<em class="parameter"><code>rastertoepson</code></em>, <em class="parameter"><code>rastertoescp</code></em>, <em class="parameter"><code>rastertopcl</code></em>,
@@ -811,9 +811,9 @@ text/plain              application/postscript   33    texttops
 	<em class="parameter"><code>rastertoprinter</code></em>) by third-party driver development projects (such as Gutenprint)
 	wanting to cooperate as closely as possible with CUPS. See <a class="link" href="CUPS-printing.html#small9" title="Figure�22.9.�Raster to Printer-Specific Formats.">the Raster to
 	Printer-Specific Formats illustration</a>.
-	</p><div class="figure"><a name="small9"></a><p class="title"><b>Figure�22.9.�Raster to Printer-Specific Formats.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/9small.png" alt="Raster to Printer-Specific Formats."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637850"></a>CUPS Backends</h3></div></div></div><p>
-<a class="indexterm" name="id2637858"></a>
-<a class="indexterm" name="id2637865"></a>
+	</p><div class="figure"><a name="small9"></a><p class="title"><b>Figure�22.9.�Raster to Printer-Specific Formats.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/9small.png" alt="Raster to Printer-Specific Formats."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637941"></a>CUPS Backends</h3></div></div></div><p>
+<a class="indexterm" name="id2637949"></a>
+<a class="indexterm" name="id2637956"></a>
 	The last part of any CUPS filtering chain is a backend. Backends
 	are special programs that send the print-ready file to the final
 	device. There is a separate backend program for any transfer
@@ -887,8 +887,8 @@ text/plain              application/postscript   33    texttops
 	email back to the $USER asking him or her to always specify the correct
 	printer name.)
 	</p><p>
-<a class="indexterm" name="id2638145"></a>
-<a class="indexterm" name="id2638152"></a>
+<a class="indexterm" name="id2638235"></a>
+<a class="indexterm" name="id2638242"></a>
 	Not all of the mentioned backends may be present on your system or
 	usable (depending on your hardware configuration). One test for all
 	available CUPS backends is provided by the <span class="emphasis"><em>lpinfo</em></span>
@@ -896,12 +896,12 @@ text/plain              application/postscript   33    texttops
 	all available backends:
 	</p><pre class="screen">
 	<code class="prompt">$ </code><strong class="userinput"><code>lpinfo -v</code></strong>
-	</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638189"></a>The Role of <em class="parameter"><code>cupsomatic/foomatic</code></em></h3></div></div></div><p>
-	<a class="indexterm" name="id2638202"></a>
-	<a class="indexterm" name="id2638208"></a>
-<a class="indexterm" name="id2638215"></a>
-<a class="indexterm" name="id2638222"></a>
-<a class="indexterm" name="id2638229"></a>
+	</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638279"></a>The Role of <em class="parameter"><code>cupsomatic/foomatic</code></em></h3></div></div></div><p>
+	<a class="indexterm" name="id2638292"></a>
+	<a class="indexterm" name="id2638299"></a>
+<a class="indexterm" name="id2638306"></a>
+<a class="indexterm" name="id2638312"></a>
+<a class="indexterm" name="id2638319"></a>
 	<em class="parameter"><code>cupsomatic</code></em> filters may be the most widely used on CUPS
 	installations. You must be clear that these were not
 	developed by the CUPS people. They are a third-party add-on to
@@ -925,17 +925,17 @@ text/plain              application/postscript   33    texttops
 	autoconstructed from the selected PPD and command line options given to
 	the print job.
 	</p><p>
-	<a class="indexterm" name="id2638295"></a>
-<a class="indexterm" name="id2638302"></a>
-<a class="indexterm" name="id2638309"></a>
-<a class="indexterm" name="id2638316"></a>
-<a class="indexterm" name="id2638323"></a>
-<a class="indexterm" name="id2638330"></a>
-<a class="indexterm" name="id2638337"></a>
-<a class="indexterm" name="id2638344"></a>
-<a class="indexterm" name="id2638350"></a>
-<a class="indexterm" name="id2638357"></a>
-<a class="indexterm" name="id2638364"></a>
+	<a class="indexterm" name="id2638386"></a>
+<a class="indexterm" name="id2638393"></a>
+<a class="indexterm" name="id2638400"></a>
+<a class="indexterm" name="id2638407"></a>
+<a class="indexterm" name="id2638414"></a>
+<a class="indexterm" name="id2638420"></a>
+<a class="indexterm" name="id2638427"></a>
+<a class="indexterm" name="id2638434"></a>
+<a class="indexterm" name="id2638441"></a>
+<a class="indexterm" name="id2638448"></a>
+<a class="indexterm" name="id2638454"></a>
 	However, <em class="parameter"><code>cupsomatic</code></em> is now deprecated. Its PPDs (especially the first
 	generation of them, still in heavy use out there) are not meeting the
 	Adobe specifications. You might also suffer difficulties when you try
@@ -957,11 +957,11 @@ text/plain              application/postscript   33    texttops
 	best thing is that the new <code class="constant">foomatic-rip</code> works seamlessly with all
 	legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR, and so on), providing
 	for them access to use PPDs for their printing.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638424"></a>The Complete Picture</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638515"></a>The Complete Picture</h3></div></div></div><p>
 	If you want to see an overview of all the filters and how they
 	relate to each other, the complete picture of the puzzle is at the end
 	of this chapter.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638437"></a><code class="filename">mime.convs</code></h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638528"></a><code class="filename">mime.convs</code></h3></div></div></div><p>
 	CUPS autoconstructs all possible filtering chain paths for any given
 	MIME type and every printer installed. But how does it decide in
 	favor of or against a specific alternative?  (There may be cases
@@ -971,8 +971,8 @@ text/plain              application/postscript   33    texttops
 	assigned to this filter. Every possible filtering chain will sum up to
 	a total &#8220;<span class="quote">filter cost.</span>&#8221; CUPS decides for the most &#8220;<span class="quote">inexpensive</span>&#8221; route.
 	</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2638469"></a>
-<a class="indexterm" name="id2638475"></a>
+<a class="indexterm" name="id2638559"></a>
+<a class="indexterm" name="id2638566"></a>
 	Setting <em class="parameter"><code>FilterLimit 1000</code></em> in
 	<code class="filename">cupsd.conf</code> will not allow more filters to
 	run concurrently than will consume a total of 1000 virtual filter
@@ -980,10 +980,10 @@ text/plain              application/postscript   33    texttops
 	server by setting an appropriate &#8220;<span class="quote">FilterLimit</span>&#8221; value. A FilterLimit of
 	200 allows roughly one job at a time, while a FilterLimit of 1000 allows
 	approximately five jobs maximum at a time.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638506"></a>&#8220;<span class="quote">Raw</span>&#8221; Printing</h3></div></div></div><p>
-<a class="indexterm" name="id2638516"></a>
-<a class="indexterm" name="id2638522"></a>
-<a class="indexterm" name="id2638529"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638596"></a>&#8220;<span class="quote">Raw</span>&#8221; Printing</h3></div></div></div><p>
+<a class="indexterm" name="id2638606"></a>
+<a class="indexterm" name="id2638613"></a>
+<a class="indexterm" name="id2638620"></a>
 	You can tell CUPS to print (nearly) any file &#8220;<span class="quote">raw</span>&#8221;. &#8220;<span class="quote">Raw</span>&#8221; means it will not be
 	filtered. CUPS will send the file to the printer &#8220;<span class="quote">as is</span>&#8221; without bothering if the printer is able
 	to digest it. Users need to take care themselves that they send sensible data formats only. Raw printing can
@@ -1001,9 +1001,9 @@ text/plain              application/postscript   33    texttops
 	if it can't find a PPD associated with the queue. However, CUPS will
 	only send known MIME types (as defined in its own mime.types file) and
 	refuse others.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638614"></a>application/octet-stream Printing</h3></div></div></div><p>
-<a class="indexterm" name="id2638622"></a>
-<a class="indexterm" name="id2638629"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638704"></a>application/octet-stream Printing</h3></div></div></div><p>
+<a class="indexterm" name="id2638712"></a>
+<a class="indexterm" name="id2638720"></a>
 	Any MIME type with no rule in the <code class="filename">/etc/cups/mime.types</code> file is regarded as unknown
 	or <em class="parameter"><code>application/octet-stream</code></em> and will not be
 	sent. Because CUPS refuses to print unknown MIME types by default,
@@ -1016,11 +1016,11 @@ text/plain              application/postscript   33    texttops
 	To enable the printing of <em class="parameter"><code>application/octet-stream</code></em> files, edit
 	these two files:
 	</p><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">/etc/cups/mime.convs</code></p></li><li><p><code class="filename">/etc/cups/mime.types</code></p></li></ul></div><p>
-<a class="indexterm" name="id2638695"></a>
+<a class="indexterm" name="id2638785"></a>
 	Both contain entries (at the end of the respective files) that must be uncommented to allow raw mode
 	operation for <em class="parameter"><code>application/octet-stream</code></em>. In <code class="filename">/etc/cups/mime.types</code>
 	make sure this line is present:
-	<a class="indexterm" name="id2638716"></a>
+	<a class="indexterm" name="id2638807"></a>
 </p><pre class="programlisting">
 application/octet-stream
 </pre><p>
@@ -1031,7 +1031,7 @@ application/octet-stream
 </p><pre class="programlisting">
 application/octet-stream   application/vnd.cups-raw   0   -
 </pre><p>
-	<a class="indexterm" name="id2638751"></a>
+	<a class="indexterm" name="id2638842"></a>
 	This line tells CUPS to use the <span class="emphasis"><em>Null Filter</em></span>
 	(denoted as &#8220;<span class="quote">-</span>&#8221;, doing nothing at all) on
 	<em class="parameter"><code>application/octet-stream</code></em>, and tag the result as
@@ -1042,10 +1042,10 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	Editing the <code class="filename">mime.convs</code> and the <code class="filename">mime.types</code> file does not
 	<span class="emphasis"><em>enforce</em></span> &#8220;<span class="quote">raw</span>&#8221; printing, it only <span class="emphasis"><em>allows</em></span> it.
 	</p></div><p><b>Background.�</b>
-<a class="indexterm" name="id2638818"></a>
-<a class="indexterm" name="id2638825"></a>
-<a class="indexterm" name="id2638832"></a>
-<a class="indexterm" name="id2638839"></a>
+<a class="indexterm" name="id2638908"></a>
+<a class="indexterm" name="id2638915"></a>
+<a class="indexterm" name="id2638922"></a>
+<a class="indexterm" name="id2638929"></a>
 	That CUPS is a more security-aware printing system than traditional ones
 	does not by default allow one to send deliberate (possibly binary)
 	data to printing devices. (This could be easily abused to launch a
@@ -1057,13 +1057,13 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	<code class="filename">/etc/cups/mime.types</code> defines the &#8220;<span class="quote">rules</span>&#8221; of how CUPS
 	recognizes MIME types. The file <code class="filename">/etc/cups/mime.convs</code> decides which file
 	conversion filter(s) may be applied to which MIME types.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638893"></a>PostScript Printer Descriptions for Non-PostScript Printers</h3></div></div></div><p>
-	<a class="indexterm" name="id2638902"></a>
-<a class="indexterm" name="id2638908"></a>
-<a class="indexterm" name="id2638915"></a>
-<a class="indexterm" name="id2638922"></a>
-<a class="indexterm" name="id2638928"></a>
-<a class="indexterm" name="id2638935"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638984"></a>PostScript Printer Descriptions for Non-PostScript Printers</h3></div></div></div><p>
+	<a class="indexterm" name="id2638992"></a>
+<a class="indexterm" name="id2638999"></a>
+<a class="indexterm" name="id2639006"></a>
+<a class="indexterm" name="id2639012"></a>
+<a class="indexterm" name="id2639019"></a>
+<a class="indexterm" name="id2639026"></a>
 	Originally PPDs were meant to be used for PostScript printers
 	only. Here, they help to send device-specific commands and settings
 	to the RIP, which processes the job file. CUPS has extended this
@@ -1076,7 +1076,7 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	</p><p>
 	PPDs for a non-PostScript printer have a few lines that are unique to
 	CUPS. The most important one looks similar to this:
-	<a class="indexterm" name="id2638958"></a>
+	<a class="indexterm" name="id2639048"></a>
 </p><pre class="programlisting">
 *cupsFilter: application/vnd.cups-raster  66   rastertoprinter
 </pre><p>
@@ -1094,14 +1094,14 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	several hundred printer models. You may not be able to control
 	different paper trays, or you may get larger margins than your
 	specific model supports. See Table 21.1<a class="link" href="CUPS-printing.html#cups-ppds" title="Table�22.1.�PPDs Shipped with CUPS">&#8220;PPDs Shipped with CUPS&#8221;</a> for summary information.
-	</p><div class="table"><a name="cups-ppds"></a><p class="title"><b>Table�22.1.�PPDs Shipped with CUPS</b></p><div class="table-contents"><table summary="PPDs Shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9-pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24-pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers </td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639176"></a><span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> Versus <span class="emphasis"><em>Native CUPS</em></span> Printing</h3></div></div></div><p>
-	<a class="indexterm" name="id2639190"></a>
-	<a class="indexterm" name="id2639197"></a>
+	</p><div class="table"><a name="cups-ppds"></a><p class="title"><b>Table�22.1.�PPDs Shipped with CUPS</b></p><div class="table-contents"><table summary="PPDs Shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9-pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24-pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers </td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639267"></a><span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> Versus <span class="emphasis"><em>Native CUPS</em></span> Printing</h3></div></div></div><p>
+	<a class="indexterm" name="id2639281"></a>
+	<a class="indexterm" name="id2639288"></a>
 	Native CUPS rasterization works in two steps:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2639211"></a>
+<a class="indexterm" name="id2639302"></a>
 		First is the <em class="parameter"><code>pstoraster</code></em> step. It uses the special CUPS
-		<a class="indexterm" name="id2639225"></a>
+		<a class="indexterm" name="id2639315"></a>
 		device from ESP Ghostscript 7.05.x as its tool.
 		</p></li><li><p>
 		Second is the <em class="parameter"><code>rasterdriver</code></em> step. It uses various
@@ -1116,7 +1116,7 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	One other method is the <em class="parameter"><code>cupsomatic/foomatic-rip</code></em>
 	way. Note that <em class="parameter"><code>cupsomatic</code></em> is <span class="emphasis"><em>not</em></span> made by the CUPS
 	developers. It is an independent contribution to printing development,
-	made by people from Linuxprinting.org.<sup>[<a name="id2639328" href="#ftn.id2639328" class="footnote">6</a>]</sup>
+	made by people from Linuxprinting.org.<sup>[<a name="id2639418" href="#ftn.id2639418" class="footnote">6</a>]</sup>
 	<em class="parameter"><code>cupsomatic</code></em> is no longer developed, maintained, or supported. It now been
 	replaced by <em class="parameter"><code>foomatic-rip</code></em>. <em class="parameter"><code>foomatic-rip</code></em> is a complete rewrite
 	of the old <em class="parameter"><code>cupsomatic</code></em> idea, but very much improved and generalized to
@@ -1124,8 +1124,8 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	advised, especially if you are upgrading to a recent version of CUPS,
 	too.
 	</p><p>
-	<a class="indexterm" name="id2639377"></a>
-	<a class="indexterm" name="id2639384"></a>
+	<a class="indexterm" name="id2639468"></a>
+	<a class="indexterm" name="id2639475"></a>
 	Like the old <em class="parameter"><code>cupsomatic</code></em> method, the <em class="parameter"><code>foomatic-rip</code></em> (new) method
 	from Linuxprinting.org uses the traditional Ghostscript print file processing, doing everything in a single
 	step. It therefore relies on all the other devices built into Ghostscript. The quality is as good (or bad) as
@@ -1135,12 +1135,12 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	Of course, you can use both methods side by side on one system (and even for one printer, if you set up
 	different queues) and find out which works best for you.
 	</p><p>
-<a class="indexterm" name="id2639420"></a>
-<a class="indexterm" name="id2639426"></a>
-<a class="indexterm" name="id2639433"></a>
-<a class="indexterm" name="id2639440"></a>
-<a class="indexterm" name="id2639447"></a>
-<a class="indexterm" name="id2639454"></a>
+<a class="indexterm" name="id2639510"></a>
+<a class="indexterm" name="id2639517"></a>
+<a class="indexterm" name="id2639524"></a>
+<a class="indexterm" name="id2639531"></a>
+<a class="indexterm" name="id2639538"></a>
+<a class="indexterm" name="id2639544"></a>
 	<em class="parameter"><code>cupsomatic</code></em> kidnaps the print file after the
 	<em class="parameter"><code>application/vnd.cups-postscript</code></em> stage and deviates it through the CUPS-external,
 	systemwide Ghostscript installation. Therefore, the print file bypasses the <em class="parameter"><code>pstoraster</code></em>
@@ -1149,14 +1149,14 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	backend. <a class="link" href="CUPS-printing.html#cupsomatic-dia" title="Figure�22.10.�cupsomatic/foomatic Processing Versus Native CUPS.">cupsomatic/foomatic Processing Versus Native
 	CUPS</a>, illustrates the difference between native CUPS rendering and the
 	<em class="parameter"><code>Foomatic/cupsomatic</code></em> method.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639513"></a>Examples for Filtering Chains</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639604"></a>Examples for Filtering Chains</h3></div></div></div><p>
 	Here are a few examples of commonly occurring filtering chains to
 	illustrate the workings of CUPS.
 	</p><p>
-<a class="indexterm" name="id2639526"></a>
-<a class="indexterm" name="id2639533"></a>
-<a class="indexterm" name="id2639540"></a>
-<a class="indexterm" name="id2639547"></a>
+<a class="indexterm" name="id2639617"></a>
+<a class="indexterm" name="id2639624"></a>
+<a class="indexterm" name="id2639631"></a>
+<a class="indexterm" name="id2639637"></a>
 	Assume you want to print a PDF file to an HP JetDirect-connected
 	PostScript printer, but you want to print pages 3-5, 7, and 11-13
 	only, and you want to print them &#8220;<span class="quote">two-up</span>&#8221; and &#8220;<span class="quote">duplex</span>&#8221;:
@@ -1175,10 +1175,10 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	backend, which transfers the job to the printers.</p></li></ul></div><p>
 	The resulting filter chain, therefore, is as shown in <a class="link" href="CUPS-printing.html#pdftosocket" title="Figure�22.11.�PDF to Socket Chain.">the PDF to socket chain
 	illustration</a>.
-	</p><a class="indexterm" name="id2639658"></a><div class="figure"><a name="pdftosocket"></a><p class="title"><b>Figure�22.11.�PDF to Socket Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftosocket.png" alt="PDF to Socket Chain."></div></div></div><br class="figure-break"><p>
-<a class="indexterm" name="id2639708"></a>
-<a class="indexterm" name="id2639715"></a>
-<a class="indexterm" name="id2639722"></a>
+	</p><a class="indexterm" name="id2639748"></a><div class="figure"><a name="pdftosocket"></a><p class="title"><b>Figure�22.11.�PDF to Socket Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftosocket.png" alt="PDF to Socket Chain."></div></div></div><br class="figure-break"><p>
+<a class="indexterm" name="id2639798"></a>
+<a class="indexterm" name="id2639805"></a>
+<a class="indexterm" name="id2639812"></a>
 	Assume you want to print the same filter to an USB-connected Epson Stylus Photo Printer installed with the CUPS
 	<code class="filename">stphoto2.ppd</code>. The first few filtering stages are nearly the same:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -1188,14 +1188,14 @@ application/octet-stream   application/vnd.cups-raw   0   -
 		The (complete) PDF file is sent to CUPS and autotyped as
 		<em class="parameter"><code>application/pdf</code></em>.
 		</p></li><li><p>
-<a class="indexterm" name="id2639762"></a>
-<a class="indexterm" name="id2639769"></a>
+<a class="indexterm" name="id2639852"></a>
+<a class="indexterm" name="id2639859"></a>
 		The file must first pass the <em class="parameter"><code>pdftops</code></em> prefilter, which produces PostScript
 		MIME type <em class="parameter"><code>application/postscript</code></em> (a preview here would still show all
 		pages of the original PDF).
 		</p></li><li><p>
-<a class="indexterm" name="id2639794"></a>
-<a class="indexterm" name="id2639801"></a>
+<a class="indexterm" name="id2639885"></a>
+<a class="indexterm" name="id2639892"></a>
 		The file then passes the &#8220;<span class="quote">pstops</span>&#8221; filter that applies
 		the command line options: it selects the pages 2-5, 7, and 11-13,
 		creates the imposed layout &#8220;<span class="quote">two pages on one sheet,</span>&#8221; and inserts the
@@ -1207,7 +1207,7 @@ application/octet-stream   application/vnd.cups-raw   0   -
 		The file then passes the <em class="parameter"><code>pstoraster</code></em> stage and becomes MIME type
 		<em class="parameter"><code>application/cups-raster</code></em>.
 		</p></li><li><p>
-<a class="indexterm" name="id2639856"></a>
+<a class="indexterm" name="id2639947"></a>
 		Finally, the <em class="parameter"><code>rastertoepson</code></em> filter
 		does its work (as indicated in the printer's PPD), creating the
 		printer-specific raster data and embedding any user-selected
@@ -1217,11 +1217,11 @@ application/octet-stream   application/vnd.cups-raw   0   -
 		</p></li></ul></div><p>
 	The resulting filter chain therefore is as shown in <a class="link" href="CUPS-printing.html#pdftoepsonusb" title="Figure�22.12.�PDF to USB Chain.">the PDF to USB Chain
 	illustration</a>.
-	</p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure�22.12.�PDF to USB Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftoepsonusb.png" alt="PDF to USB Chain."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639941"></a>Sources of CUPS Drivers/PPDs</h3></div></div></div><p>
+	</p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure�22.12.�PDF to USB Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftoepsonusb.png" alt="PDF to USB Chain."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640032"></a>Sources of CUPS Drivers/PPDs</h3></div></div></div><p>
 	On the Internet you can now find many thousands of CUPS-PPD files
 	(with their companion filters), in many national languages
 	supporting more than 1,000 non-PostScript models.
-	</p><div class="itemizedlist"><a class="indexterm" name="id2639956"></a><a class="indexterm" name="id2639965"></a><ul type="disc"><li><p>
+	</p><div class="itemizedlist"><a class="indexterm" name="id2640046"></a><a class="indexterm" name="id2640055"></a><ul type="disc"><li><p>
 		<a class="ulink" href="http://www.easysw.com/printpro/" target="_top">ESP PrintPro</a>
 		(commercial, non-free) is packaged with more than 3,000 PPDs, ready for
 		successful use &#8220;<span class="quote">out of the box</span>&#8221; on Linux, Mac OS X, IBM-AIX,
@@ -1249,9 +1249,9 @@ application/octet-stream   application/vnd.cups-raw   0   -
 		<a class="ulink" href="http://www.linuxprinting.org/" target="_top">Foomatic/cupsomatic </a>
 		(LPGL, free) from Linuxprinting.org provide PPDs for practically every Ghostscript
 		filter known to the world (including Omni, Gutenprint, and HPIJS).
-		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640064"></a>Printing with Interface Scripts</h3></div></div></div><p>
-<a class="indexterm" name="id2640072"></a>
-<a class="indexterm" name="id2640079"></a>
+		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640155"></a>Printing with Interface Scripts</h3></div></div></div><p>
+<a class="indexterm" name="id2640163"></a>
+<a class="indexterm" name="id2640169"></a>
 	CUPS also supports the use of &#8220;<span class="quote">interface scripts</span>&#8221; as known from
 	System V AT&amp;T printing systems. These are often used for PCL
 	printers, from applications that generate PCL print jobs. Interface
@@ -1273,16 +1273,16 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	use of interface scripts is found at
 	<a class="ulink" href="http://playground.sun.com/printing/documentation/interface.html" target="_top">
 	http://playground.sun.com/printing/documentation/interface.html</a>).
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640159"></a>Network Printing (Purely Windows)</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640249"></a>Network Printing (Purely Windows)</h2></div></div></div><p>
 Network printing covers a lot of ground. To understand what exactly
 goes on with Samba when it is printing on behalf of its Windows
 clients, let's first look at a &#8220;<span class="quote">purely Windows</span>&#8221; setup: Windows clients
 with a Windows NT print server.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640176"></a>From Windows Clients to an NT Print Server</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640266"></a>From Windows Clients to an NT Print Server</h3></div></div></div><p>
 Windows clients printing to an NT-based print server have two
 options. They may:
-<a class="indexterm" name="id2640185"></a>
-<a class="indexterm" name="id2640192"></a>
+<a class="indexterm" name="id2640276"></a>
+<a class="indexterm" name="id2640282"></a>
 </p><div class="itemizedlist"><ul type="disc"><li><p>Execute the driver locally and render the GDI output
 			(EMF) into the printer-specific format on their own.
 	</p></li><li><p>Send the GDI output (EMF) to the server, where the
@@ -1291,7 +1291,7 @@ options. They may:
 Both print paths are shown in the flowcharts in <a class="link" href="CUPS-printing.html#small11" title="Figure�22.13.�Print Driver Execution on the Client.">
 Print Driver Execution on the Client</a>, and
 <a class="link" href="CUPS-printing.html#small12" title="Figure�22.14.�Print Driver Execution on the Server.">Print Driver Execution on the Server</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640238"></a>Driver Execution on the Client</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640328"></a>Driver Execution on the Client</h3></div></div></div><p>
 In the first case, the print server must spool the file as raw, meaning it shouldn't touch the job file and try
 to convert it in any way. This is what a traditional UNIX-based print server can do too, and at a better
 performance and more reliably than an NT print server. This is what most Samba administrators probably are
@@ -1299,12 +1299,12 @@ familiar with. One advantage of this setup is that this &#8220;<span class="quot
 even if no driver(s) for UNIX is available. It is sufficient to have the Windows client drivers available and
 installed on the clients. This is illustrated in <a class="link" href="CUPS-printing.html#small11" title="Figure�22.13.�Print Driver Execution on the Client.">the Print Driver Execution on the
 Client diagram</a>.
-</p><div class="figure"><a name="small11"></a><p class="title"><b>Figure�22.13.�Print Driver Execution on the Client.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/11small.png" alt="Print Driver Execution on the Client."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640309"></a>Driver Execution on the Server</h3></div></div></div><p>
-<a class="indexterm" name="id2640317"></a>
-<a class="indexterm" name="id2640324"></a>
-<a class="indexterm" name="id2640330"></a>
-<a class="indexterm" name="id2640337"></a>
-<a class="indexterm" name="id2640344"></a>
+</p><div class="figure"><a name="small11"></a><p class="title"><b>Figure�22.13.�Print Driver Execution on the Client.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/11small.png" alt="Print Driver Execution on the Client."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640399"></a>Driver Execution on the Server</h3></div></div></div><p>
+<a class="indexterm" name="id2640408"></a>
+<a class="indexterm" name="id2640414"></a>
+<a class="indexterm" name="id2640421"></a>
+<a class="indexterm" name="id2640428"></a>
+<a class="indexterm" name="id2640434"></a>
 The other path executes the printer driver on the server. The client transfers print files in EMF format to
 the server. The server uses the PostScript, PCL, ESC/P, or other driver to convert the EMF file into the
 printer-specific language. It is not possible for UNIX to do the same. Currently, there is no program or
@@ -1312,14 +1312,14 @@ method to convert a Windows client's GDI output on a UNIX server into something
 This is illustrated in <a class="link" href="CUPS-printing.html#small12" title="Figure�22.14.�Print Driver Execution on the Server.">the Print Driver Execution on the Server diagram</a>.
 </p><div class="figure"><a name="small12"></a><p class="title"><b>Figure�22.14.�Print Driver Execution on the Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/12small.png" alt="Print Driver Execution on the Server."></div></div></div><br class="figure-break"><p>
 However, something similar is possible with CUPS, so read on.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640414"></a>Network Printing (Windows Clients and UNIX/Samba Print
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640504"></a>Network Printing (Windows Clients and UNIX/Samba Print
 Servers)</h2></div></div></div><p>
 Since UNIX print servers <span class="emphasis"><em>cannot</em></span> execute the Win32
 program code on their platform, the picture is somewhat
 different. However, this does not limit your options all that
 much. On the contrary, you may have a way here to implement printing
 features that are not possible otherwise.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640432"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640522"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div></div><p>
 Here is a simple recipe showing how you can take advantage of CUPS's
 powerful features for the benefit of your Windows network printing
 clients:
@@ -1331,15 +1331,15 @@ driver on the CUPS server.
 </p><p>
 First, to enable CUPS-based printing through Samba, the following options should be set in your <code class="filename">smb.conf</code>
 file <em class="parameter"><code>[global]</code></em> section:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2640487"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2640498"></a><em class="parameter"><code>printcap = cups</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2640577"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2640589"></a><em class="parameter"><code>printcap = cups</code></em></td></tr></table><p>
 When these parameters are specified, all manually set print directives (like <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> or <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" target="_top">lppause command</a>) in <code class="filename">smb.conf</code> (as well as in Samba itself) will be
 ignored. Instead, Samba will directly interface with CUPS through its application program interface (API), as
 long as Samba has been compiled with CUPS library (libcups) support. If Samba has not been compiled with CUPS
 support, and if no other print commands are set up, then printing will use the <span class="emphasis"><em>System V</em></span>
 AT&amp;T command set, with the -oraw option automatically passing through (if you want your own defined print
-commands to work with a Samba server that has CUPS support compiled in, simply use <a class="link" href="smb.conf.5.html#CLASSICALPRINTING" target="_top">classicalprinting = sysv</a>). This is illustrated in <a class="link" href="CUPS-printing.html#f13small" title="Figure�22.15.�Printing via CUPS/Samba Server.">the Printing via
+commands to work with a Samba server that has CUPS support compiled in, simply use <a class="link" href="smb.conf.5.html#CLASSICALPRINTING" target="_top">classicalprinting = sysv</a>). This is illustrated in <a class="link" href="CUPS-printing.html#13small" title="Figure�22.15.�Printing via CUPS/Samba Server.">the Printing via
 CUPS/Samba Server diagram</a>.
-</p><div class="figure"><a name="f13small"></a><p class="title"><b>Figure�22.15.�Printing via CUPS/Samba Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/13small.png" alt="Printing via CUPS/Samba Server."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640622"></a>Samba Receiving Job-Files and Passing Them to CUPS</h3></div></div></div><p>
+</p><div class="figure"><a name="13small"></a><p class="title"><b>Figure�22.15.�Printing via CUPS/Samba Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/13small.png" alt="Printing via CUPS/Samba Server."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640713"></a>Samba Receiving Job-Files and Passing Them to CUPS</h3></div></div></div><p>
 Samba <span class="emphasis"><em>must</em></span> use its own spool directory (it is set by a line similar to <a class="link" href="smb.conf.5.html#PATH" target="_top">path = /var/spool/samba</a>, in the <em class="parameter"><code>[printers]</code></em> or <em class="parameter"><code>[printername]</code></em> section of <code class="filename">smb.conf</code>). Samba receives the job in its own spool space and passes it
 into the spool directory of CUPS (the CUPS spool directory is set by the <em class="parameter"><code>RequestRoot</code></em>
 directive in a line that defaults to <em class="parameter"><code>RequestRoot /var/spool/cups</code></em>). CUPS checks the
@@ -1351,13 +1351,13 @@ A Windows user authenticates only to Samba (by whatever means is
 configured). If Samba runs on the same host as CUPS, you only need to
 allow &#8220;<span class="quote">localhost</span>&#8221; to print. If it runs on different machines, you
 need to make sure the Samba host gets access to printing on CUPS.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640702"></a>Network PostScript RIP</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640792"></a>Network PostScript RIP</h2></div></div></div><p>
 This section discusses the use of CUPS filters on the server  configuration where
 clients make use of a PostScript driver with CUPS-PPDs.
 </p><p>
-<a class="indexterm" name="id2640718"></a>
-<a class="indexterm" name="id2640725"></a>
-<a class="indexterm" name="id2640731"></a>
+<a class="indexterm" name="id2640809"></a>
+<a class="indexterm" name="id2640815"></a>
+<a class="indexterm" name="id2640822"></a>
 PPDs can control all print device options. They are usually provided by the manufacturer  if you own
 a PostScript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or
 Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate
@@ -1370,8 +1370,8 @@ and handle the options. There is a Web browser interface to the print options (s
 lpoptions</code> or see if you have <code class="literal">lphelp</code> on your system). There are also some
 different GUI front-ends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant
 to be evaluated by the PostScript RIP on the real PostScript printer.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640792"></a>PPDs for Non-PS Printers on UNIX</h3></div></div></div><p>
-<a class="indexterm" name="id2640800"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640882"></a>PPDs for Non-PS Printers on UNIX</h3></div></div></div><p>
+<a class="indexterm" name="id2640891"></a>
 CUPS does not limit itself to &#8220;<span class="quote">real</span>&#8221; PostScript printers in its use of PPDs. The CUPS developers
 have extended the scope of the PPD concept to also describe available device and driver options for
 non-PostScript printers through CUPS-PPDs.
@@ -1383,8 +1383,8 @@ All CUPS-PPDs geared to non-PostScript printers contain an additional line, star
 for the interpretation of the supplied PostScript. Thus CUPS lets all its printers appear as PostScript
 devices to its clients, because it can act as a PostScript RIP for those printers, processing the received
 PostScript code into a proper raster print format.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640836"></a>PPDs for Non-PS Printers on Windows</h3></div></div></div><p>
-<a class="indexterm" name="id2640845"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640927"></a>PPDs for Non-PS Printers on Windows</h3></div></div></div><p>
+<a class="indexterm" name="id2640935"></a>
 CUPS-PPDs can also be used on Windows clients, on top of a &#8220;<span class="quote">core</span>&#8221; PostScript driver (now
 recommended is the CUPS PostScript Driver for Windows NT/200x/XP; you can also use the Adobe one, with
 limitations). This feature enables CUPS to do a few tricks no other spooler can do:
@@ -1398,11 +1398,11 @@ limitations). This feature enables CUPS to do a few tricks no other spooler can
 	Enable clients to consolidate on a single PostScript driver, even for many different target printers.
 	</p></li></ul></div><p>
 Using CUPS PPDs on Windows clients enables them to control all print job settings just as a UNIX client can do.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640904"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640995"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div></div><p>
 This setup may be of special interest to people experiencing major problems in WTS environments. WTS often
 need a multitude of non-PostScript drivers installed to run their clients' variety of different printer
 models. This often imposes the price of much increased instability.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640919"></a>Printer Drivers Running in &#8220;<span class="quote">Kernel Mode</span>&#8221; Cause Many
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641009"></a>Printer Drivers Running in &#8220;<span class="quote">Kernel Mode</span>&#8221; Cause Many
 Problems</h3></div></div></div><p>
 Windows NT printer drivers, which run in &#8220;<span class="quote">kernel mode</span>&#8221;, introduce a high risk for the stability
 of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out
@@ -1414,14 +1414,14 @@ PostScript drivers are generally well-tested. They are not known to cause any pr
 run in kernel mode. This might be because until now there have been only two different PostScript drivers: the
 one from Adobe and the one from Microsoft. Both are well-tested and are as stable as you can imagine on
 Windows. The CUPS driver is derived from the Microsoft one.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640957"></a>Workarounds Impose Heavy Limitations</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641048"></a>Workarounds Impose Heavy Limitations</h3></div></div></div><p>
 In an attempt to work around problems, site administrators have resorted to restricting the
 allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts
 the number of printer options available for clients to use. Often they can't get out more than simplex
 prints from one standard paper tray, while their devices could do much better if driven by a different driver!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640975"></a>CUPS: A &#8220;<span class="quote">Magical Stone</span>&#8221;?</h3></div></div></div><p>
-<a class="indexterm" name="id2640986"></a>
-<a class="indexterm" name="id2640993"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641066"></a>CUPS: A &#8220;<span class="quote">Magical Stone</span>&#8221;?</h3></div></div></div><p>
+<a class="indexterm" name="id2641077"></a>
+<a class="indexterm" name="id2641083"></a>
 Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these
 shortcomings. There are, depending on the version of Windows OS you use, up to three different PostScript
 drivers now available: Adobe, Microsoft, and CUPS PostScript drivers. None of them is known to cause major
@@ -1430,14 +1430,14 @@ paper trays, duplex printing, and other settings. However, there is a certain pr
 server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as a
 &#8220;<span class="quote">raw spooling</span>&#8221; device. Plus, this setup is not yet widely tested, although the first feedbacks
 look very promising.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641018"></a>PostScript Drivers with No Major Problems, Even in Kernel
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641109"></a>PostScript Drivers with No Major Problems, Even in Kernel
 Mode</h3></div></div></div><p>
-<a class="indexterm" name="id2641027"></a>
-<a class="indexterm" name="id2641034"></a>
-<a class="indexterm" name="id2641040"></a>
-<a class="indexterm" name="id2641047"></a>
-<a class="indexterm" name="id2641054"></a>
-<a class="indexterm" name="id2641061"></a>
+<a class="indexterm" name="id2641117"></a>
+<a class="indexterm" name="id2641124"></a>
+<a class="indexterm" name="id2641131"></a>
+<a class="indexterm" name="id2641138"></a>
+<a class="indexterm" name="id2641145"></a>
+<a class="indexterm" name="id2641152"></a>
 More recent printer drivers on W200x and XP no longer run in kernel mode (unlike Windows NT). However, both
 operating systems can still use the NT drivers, running in kernel mode (you can roughly tell which is which as
 the drivers in subdirectory &#8220;<span class="quote">2</span>&#8221; of &#8220;<span class="quote">W32X86</span>&#8221; are &#8220;<span class="quote">old</span>&#8221; ones). As was
@@ -1449,13 +1449,13 @@ it for their own driver development efforts. This is what the CUPS people have d
 allow them to publish the whole of the source code.  However, they have released the &#8220;<span class="quote">diff</span>&#8221; under
 the GPL, and if you are the owner of an &#8220;<span class="quote">MS DDK for Windows NT,</span>&#8221; you can check the driver
 yourself.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2641105"></a>Configuring CUPS for Driver Download</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2641196"></a>Configuring CUPS for Driver Download</h2></div></div></div><p>
 As we have said before, all previously known methods to prepare client printer drivers on the Samba server for
 download and Point'n'Print convenience of Windows workstations are working with CUPS, too. These methods were
 described in <a class="link" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support">Classical Printing</a>. In reality, this is a pure Samba
 business and relates only to the Samba-Windows client relationship.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641128"></a><span class="emphasis"><em>cupsaddsmb</em></span>: The Unknown Utility</h3></div></div></div><p>
-<a class="indexterm" name="id2641138"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641218"></a><span class="emphasis"><em>cupsaddsmb</em></span>: The Unknown Utility</h3></div></div></div><p>
+<a class="indexterm" name="id2641229"></a>
 The <em class="parameter"><code>cupsaddsmb</code></em> utility (shipped with all current CUPS versions) is an alternative
 method to transfer printer drivers into the Samba <em class="parameter"><code>[print$]</code></em> share. Remember, this
 share is where clients expect drivers deposited and set up for download and installation. It makes the sharing
@@ -1472,11 +1472,11 @@ number of advantages:
 However, currently only Windows NT, 2000, and XP are supported by the
 CUPS drivers. You will also need to get the respective part of the Adobe driver
 if you need to support Windows 95, 98, and Me clients.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641226"></a>Prepare Your <code class="filename">smb.conf</code> for <code class="literal">cupsaddsmb</code></h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641316"></a>Prepare Your <code class="filename">smb.conf</code> for <code class="literal">cupsaddsmb</code></h3></div></div></div><p>
 Prior to running <code class="literal">cupsaddsmb</code>, you need the settings in
 <code class="filename">smb.conf</code> as shown in <a class="link" href="CUPS-printing.html#cupsadd-ex" title="Example�22.3.�smb.conf for cupsaddsmb Usage">the <code class="filename">smb.conf</code> for cupsaddsmb Usage</a>.
-</p><div class="example"><a name="cupsadd-ex"></a><p class="title"><b>Example�22.3.�smb.conf for cupsaddsmb Usage</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2641295"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641307"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2641319"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2641340"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2641351"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2641363"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><a class="indexterm" name="id2641379"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641390"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641402"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641413"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2641435"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641446"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641458"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641470"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641481"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641493"></a><em class="parameter"><code>write list = root, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641507"></a>CUPS &#8220;<span class="quote">PostScript Driver for Windows NT/200x/XP</span>&#8221;</h3></div></div></div><p>
-<a class="indexterm" name="id2641518"></a>
+</p><div class="example"><a name="cupsadd-ex"></a><p class="title"><b>Example�22.3.�smb.conf for cupsaddsmb Usage</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2641386"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641398"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2641409"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2641430"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2641442"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2641454"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><a class="indexterm" name="id2641469"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641481"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641492"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641504"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2641525"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641537"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641549"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641560"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641572"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641584"></a><em class="parameter"><code>write list = root, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641598"></a>CUPS &#8220;<span class="quote">PostScript Driver for Windows NT/200x/XP</span>&#8221;</h3></div></div></div><p>
+<a class="indexterm" name="id2641608"></a>
 CUPS users may get the exact same package from <a class="ulink" href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>.  It is a separate package
 from the CUPS-based software files, tagged as CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba (tar.gz,
 192k). The filename to download is <code class="filename">cups-samba-1.1.x.tar.gz</code>. Upon untar and unzipping, it
@@ -1489,8 +1489,8 @@ cups-samba.readme
 cups-samba.remove
 cups-samba.ss
 </pre><p>
-<a class="indexterm" name="id2641564"></a>
-<a class="indexterm" name="id2641573"></a>
+<a class="indexterm" name="id2641655"></a>
+<a class="indexterm" name="id2641664"></a>
 These have been packaged with the ESP meta-packager software EPM. The <code class="filename">*.install</code> and
 <code class="filename">*.remove</code> files are simple shell scripts, which untar the <code class="filename">*.ss</code> (the
 <code class="filename">*.ss</code> is nothing else but a tar archive, which can be untarred by &#8220;<span class="quote">tar</span>&#8221; too).
@@ -1522,32 +1522,32 @@ into<code class="filename">/usr/share/drivers/</code> instead of <code class="fi
 around this, copy/move the file (after running the <code class="literal">./cups-samba.install</code> script) manually to
 the correct place.
 </p></div><p>
-<a class="indexterm" name="id2641726"></a>
+<a class="indexterm" name="id2641816"></a>
 This new CUPS PostScript driver is currently binary only, but free of charge. No complete source code is
 provided (yet). The reason is that it has been developed with the help of the Microsoft DDK and compiled with
 Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of the source code as
 free software. However, CUPS developers released the &#8220;<span class="quote">diff</span>&#8221; in source code under the GPL, so
 anybody with a license for Visual Studio and a DDK will be able to compile for himself or herself.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641746"></a>Recognizing Different Driver Files</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641837"></a>Recognizing Different Driver Files</h3></div></div></div><p>
 The CUPS drivers do not support the older Windows 95/98/Me, but only the Windows NT/2000/XP client.
 </p><p>Windows NT, 2000, and XP are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>cups.hlp</p></li><li><p>cupsdrvr.dll</p></li><li><p>cupsui.dll</p></li></ul></div><p>
 Adobe drivers are available for the older Windows 95/98/Me as well as
 for Windows NT/2000/XP clients. The set of files is different from the
 different platforms.
 </p><p>Windows 95, 98, and ME are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>ADFONTS.MFM</p></li><li><p>ADOBEPS4.DRV</p></li><li><p>ADOBEPS4.HLP</p></li><li><p>DEFPRTR2.PPD</p></li><li><p>ICONLIB.DLL</p></li><li><p>PSMON.DLL</p></li></ul></div><p>Windows NT, 2000, and XP are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>ADOBEPS5.DLL</p></li><li><p>ADOBEPSU.DLL</p></li><li><p>ADOBEPSU.HLP</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2641844"></a>
+<a class="indexterm" name="id2641934"></a>
 If both the Adobe driver files and the CUPS driver files for the support of Windows NT/200x/XP are presently
 installed on the server, the Adobe files will be ignored and the CUPS files will be used. If you prefer
  for whatever reason  to use Adobe-only drivers, move away the three CUPS driver files.
 The Windows 9x/Me clients use the Adobe drivers in any case.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641865"></a>Acquiring the Adobe Driver Files</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641956"></a>Acquiring the Adobe Driver Files</h3></div></div></div><p>
 Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on
 the Adobe Web site as single files, and the self-extracting and/or self-installing Windows-.exe is not easy to
 locate either. You probably need to use the included native installer and run the installation process on one
 client once. This will install the drivers (and one generic PostScript printer) locally on the client. When
 they are installed, share the generic PostScript printer. After this, the client's <em class="parameter"><code>[print$]</code></em> share holds the Adobe files, which you can get with smbclient from the CUPS host.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641890"></a>ESP Print Pro PostScript Driver for Windows NT/200x/XP</h3></div></div></div><p>
-<a class="indexterm" name="id2641899"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641981"></a>ESP Print Pro PostScript Driver for Windows NT/200x/XP</h3></div></div></div><p>
+<a class="indexterm" name="id2641990"></a>
 Users of the ESP Print Pro software are able to install the ESP print drivers package as an alternative to the
 Adobe PostScript drivers.  To do so, retrieve the driver files from the normal download area of the ESP Print
 Pro software at <a class="ulink" href="http://www.easysw.com/software.html" target="_top">Easy Software</a> web site.
@@ -1557,19 +1557,19 @@ highlighting the printer in the Printer Manager GUI and selecting <span class="g
 the menu. Of course, you need to have prepared Samba beforehand to handle the driver files; that is, set up
 the <em class="parameter"><code>[print$]</code></em> share, and so on. The ESP Print Pro package includes the CUPS driver
 files as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641953"></a>Caveats to Be Considered</h3></div></div></div><p>
-<a class="indexterm" name="id2641961"></a>
-<a class="indexterm" name="id2641968"></a>
-<a class="indexterm" name="id2641974"></a>
-<a class="indexterm" name="id2641981"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642043"></a>Caveats to Be Considered</h3></div></div></div><p>
+<a class="indexterm" name="id2642051"></a>
+<a class="indexterm" name="id2642058"></a>
+<a class="indexterm" name="id2642065"></a>
+<a class="indexterm" name="id2642072"></a>
 Once you have run the install script (and possibly manually moved the <code class="filename">cups.hlp</code> file to
 <code class="filename">/usr/share/cups/drivers/</code>), the driver is ready to be put into Samba's <em class="parameter"><code>[print$]</code></em> share (which often maps to <code class="filename">/etc/samba/drivers/</code> and contains a
 subdirectory tree with <span class="emphasis"><em>WIN40</em></span> and <span class="emphasis"><em>W32X86</em></span> branches). You do this by
 running <code class="literal">cupsaddsmb</code> (see also <code class="literal">man cupsaddsmb</code> for CUPS since release
 1.1.16).
 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2642040"></a>
-<a class="indexterm" name="id2642047"></a>
+<a class="indexterm" name="id2642131"></a>
+<a class="indexterm" name="id2642138"></a>
 You may need to put root into the smbpasswd file by running <code class="literal">smbpasswd</code>; this is especially
 important if you should run this whole procedure for the first time and are not working in an environment
 where everything is configured for <span class="emphasis"><em>single sign-on</em></span> to a Windows Domain Controller.
@@ -1584,8 +1584,8 @@ It is not harmful if you still have the <code class="filename">ADOBE*.*</code> d
 in the <code class="filename">/usr/share/cups/drivers/</code> directory. The new <code class="literal">cupsaddsmb</code> (from
 1.1.16) will automatically prefer its own drivers if it finds both.
 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2642123"></a>
-<a class="indexterm" name="id2642130"></a>
+<a class="indexterm" name="id2642213"></a>
+<a class="indexterm" name="id2642220"></a>
 Should your Windows clients have had the old <code class="filename">ADOBE*.*</code> files for the Adobe PostScript
 driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/200x/XP will
 fail at first. You need to wipe the old driver from the clients first. It is not enough to
@@ -1599,43 +1599,43 @@ there is not one single printer left that uses that particular driver. You need
 printers using this driver in the <span class="guilabel">Printers</span> folder first. You will need Administrator
 privileges to do this.
 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2642205"></a>
-<a class="indexterm" name="id2642214"></a>
+<a class="indexterm" name="id2642295"></a>
+<a class="indexterm" name="id2642305"></a>
 Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all
 printers to this one by proceeding as described in <a class="link" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support">Classical Printing
 Support</a>. Either change a driver for an existing printer by running the <span class="guilabel">Printer
 Properties</span> dialog, or use <code class="literal">rpcclient</code> with the <code class="literal">setdriver</code>
 subcommand.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642253"></a>Windows CUPS PostScript Driver Versus Adobe Driver</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642343"></a>Windows CUPS PostScript Driver Versus Adobe Driver</h3></div></div></div><p>
 Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes, these
 are the most important items that weigh in favor of CUPS:
 </p><div class="itemizedlist"><ul type="disc"><li><p>No hassle with the Adobe EULA.</p></li><li><p>No hassle with the question, &#8220;<span class="quote">Where do I
 	get the ADOBE*.* driver files?</span>&#8221;</p></li><li><p>
-	<a class="indexterm" name="id2642283"></a>
+	<a class="indexterm" name="id2642374"></a>
 	The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the
 	main PostScript part of the print file. Thus, the print file starts with <em class="parameter"><code>&lt;1B
 	&gt;%-12345X</code></em> or <em class="parameter"><code>&lt;escape&gt;%-12345X</code></em> instead of
 	<em class="parameter"><code>%!PS</code></em>. This leads to the CUPS daemon autotyping the incoming file as a print-ready file,
 	not initiating a pass through the <em class="parameter"><code>pstops</code></em> filter (to speak more technically, it is not
-	regarded as the generic MIME-type <a class="indexterm" name="id2642321"></a>
+	regarded as the generic MIME-type <a class="indexterm" name="id2642412"></a>
 	<em class="parameter"><code>application/postscript</code></em>, but as the more special MIME type
-	<a class="indexterm" name="id2642335"></a>
+	<a class="indexterm" name="id2642426"></a>
 	<em class="parameter"><code>application/cups.vnd-postscript</code></em>), which therefore also leads to the page accounting in
 	<em class="parameter"><code>/var/log/cups/page_log</code></em> not receiving the exact number of pages; instead the dummy page
 	number of &#8220;<span class="quote">1</span>&#8221; is logged in a standard setup).
 	</p></li><li><p>The Adobe driver has more options to misconfigure the
-<a class="indexterm" name="id2642366"></a>
+<a class="indexterm" name="id2642457"></a>
 	PostScript generated by it (like setting it inadvertently to
 	<span class="guilabel">Optimize for Speed</span> instead of
 	<span class="guilabel">Optimize for Portability</span>, which
 	could lead to CUPS being unable to process it).</p></li><li><p>The CUPS PostScript driver output sent by Windows
-<a class="indexterm" name="id2642393"></a>
+<a class="indexterm" name="id2642484"></a>
 	clients to the CUPS server is guaranteed to autotype 
 	as the generic MIME type <em class="parameter"><code>application/postscript</code></em>,
 	thus passing through the CUPS <em class="parameter"><code>pstops</code></em> filter and logging the
 	correct number of pages in the <code class="filename">page_log</code> for
 	accounting and quota purposes.</p></li><li><p>
-	<a class="indexterm" name="id2642426"></a>
+	<a class="indexterm" name="id2642516"></a>
 	The CUPS PostScript driver supports the sending of additional standard (IPP) print options by Windows
 	NT/200x/XP clients. Such additional print options are naming the CUPS standard <span class="emphasis"><em>banner
 	pages</em></span> (or the custom ones, should they be installed at the time of driver download), using the CUPS
@@ -1648,9 +1648,9 @@ are the most important items that weigh in favor of CUPS:
 	not disturb any other applications because they will regard it as a comment
 	and simply ignore it).</p></li><li><p>The CUPS PostScript driver will be the heart of the
 	fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon
-	(probably alongside the first beta release for CUPS 1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642470"></a>Run cupsaddsmb (Quiet Mode)</h3></div></div></div><p>
-<a class="indexterm" name="id2642478"></a>
-<a class="indexterm" name="id2642485"></a>
+	(probably alongside the first beta release for CUPS 1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642561"></a>Run cupsaddsmb (Quiet Mode)</h3></div></div></div><p>
+<a class="indexterm" name="id2642569"></a>
+<a class="indexterm" name="id2642576"></a>
 The <code class="literal">cupsaddsmb</code> command copies the needed files into your <em class="parameter"><code>[print$]</code></em>
 share. Additionally, the PPD associated with this printer is copied from <code class="filename">/etc/cups/ppd/</code>
 to <em class="parameter"><code>[print$]</code></em>. There the files wait for convenient Windows client installations via
@@ -1658,26 +1658,26 @@ Point'n'Print. Before we can run the command successfully, we need to be sure th
 Samba. If you have a small network, you are probably using user-level security (<a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>).
 </p><p>
 Here is an example of a successfully run <code class="literal">cupsaddsmb</code> command: 
-<a class="indexterm" name="id2642543"></a>
-<a class="indexterm" name="id2642550"></a>
+<a class="indexterm" name="id2642634"></a>
+<a class="indexterm" name="id2642641"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -U root infotec_IS2027</code></strong>
 Password for root required to access localhost via Samba: <strong class="userinput"><code>['secret']</code></strong>
 </pre><p>
-<a class="indexterm" name="id2642582"></a>
+<a class="indexterm" name="id2642673"></a>
 To share <span class="emphasis"><em>all</em></span> printers and drivers, use the
 <code class="option">-a</code> parameter instead of a printer name. Since
 <code class="literal">cupsaddsmb</code> &#8220;<span class="quote">exports</span>&#8221; the printer drivers to Samba, it should be
 obvious that it only works for queues with a CUPS driver associated.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642611"></a>Run cupsaddsmb with Verbose Output</h3></div></div></div><p>
-<a class="indexterm" name="id2642619"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642701"></a>Run cupsaddsmb with Verbose Output</h3></div></div></div><p>
+<a class="indexterm" name="id2642709"></a>
 Probably you want to see what's going on. Use the
 <code class="option">-v</code> parameter to get a more verbose output. The
 output below was edited for better readability: all &#8220;<span class="quote">\</span>&#8221; at the end of
 a line indicate that I inserted an artificial line break plus some
 indentation here:
-<a class="indexterm" name="id2642636"></a>
-<a class="indexterm" name="id2642646"></a>
+<a class="indexterm" name="id2642727"></a>
+<a class="indexterm" name="id2642736"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -U root -v infotec_2105</code></strong>
 Password for root required to access localhost via GANDALF:
@@ -1746,17 +1746,17 @@ If you look closely, you'll discover your root password was transferred unencryp
 Also, if you look further, you may discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in the output.
 This will occur when the directories WIN40 and W32X86 already existed in the <em class="parameter"><code>[print$]</code></em>
 driver download share (from a previous driver installation). These are harmless warning messages.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642748"></a>Understanding cupsaddsmb</h3></div></div></div><p>
-<a class="indexterm" name="id2642756"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642893"></a>Understanding cupsaddsmb</h3></div></div></div><p>
+<a class="indexterm" name="id2642901"></a>
 What has happened? What did <code class="literal">cupsaddsmb</code> do? There are five stages of the procedure:
 </p><div class="orderedlist"><ol type="1"><li><p>
-	<a class="indexterm" name="id2642781"></a>
+	<a class="indexterm" name="id2642926"></a>
 	Call the CUPS server via IPP and request the driver files and the PPD file for the named printer.</p></li><li><p>Store the files temporarily in the local TEMPDIR (as defined in <code class="filename">cupsd.conf</code>).</p></li><li><p>Connect via smbclient to the Samba server's <em class="parameter"><code>[print$]</code></em> share and put the files into the
 	 share's WIN40 (for Windows 9x/Me) and W32X86 (for Windows NT/200x/XP) subdirectories.</p></li><li><p>
-	<a class="indexterm" name="id2642818"></a>
+	<a class="indexterm" name="id2642963"></a>
 	Connect via rpcclient to the Samba server and execute the <code class="literal">adddriver</code> command with the correct parameters.
 	</p></li><li><p>
-	<a class="indexterm" name="id2642839"></a>
+	<a class="indexterm" name="id2642984"></a>
 	Connect via rpcclient to the Samba server a second time and execute the <code class="literal">setdriver</code> command.</p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 You can run the <code class="literal">cupsaddsmb</code> utility with parameters to specify one remote host as Samba host
 and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a good idea
@@ -1765,7 +1765,7 @@ Samba servers run on the same host):
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -H sambaserver -h cupsserver -v printer</code></strong>
 </pre><p>
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642892"></a>How to Recognize If cupsaddsmb Completed Successfully</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643037"></a>How to Recognize If cupsaddsmb Completed Successfully</h3></div></div></div><p>
 You <span class="emphasis"><em>must</em></span> always check if the utility completed
 successfully in all fields. You need at minimum these three messages
 among the output:
@@ -1794,9 +1794,9 @@ the <em class="parameter"><code>use client driver</code></em>.
 It is impossible to see any diagnostic output if you do not run <code class="literal">cupsaddsmb</code> in verbose mode.
 Therefore, we strongly recommend against use of the default quiet mode. It will hide any problems from you that
 might occur.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643014"></a>cupsaddsmb with a Samba PDC</h3></div></div></div><p>
-<a class="indexterm" name="id2643022"></a>
-<a class="indexterm" name="id2643029"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643159"></a>cupsaddsmb with a Samba PDC</h3></div></div></div><p>
+<a class="indexterm" name="id2643167"></a>
+<a class="indexterm" name="id2643174"></a>
 Can't get the standard <code class="literal">cupsaddsmb</code> command to run on a Samba PDC?  Are you asked for the
 password credential again and again, and the command just will not take off at all? Try one of these
 variations:
@@ -1806,20 +1806,20 @@ variations:
 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -H SAURON -U MIDEARTH\\root -h cups-server -v printername</code></strong>
 </pre><p>
 (Note the two backslashes: the first one is required to &#8220;<span class="quote">escape</span>&#8221; the second one).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643095"></a>cupsaddsmb Flowchart</h3></div></div></div><p>
-<a class="indexterm" name="id2643103"></a>
-<a class="indexterm" name="id2643110"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643240"></a>cupsaddsmb Flowchart</h3></div></div></div><p>
+<a class="indexterm" name="id2643248"></a>
+<a class="indexterm" name="id2643255"></a>
 <a class="link" href="CUPS-printing.html#small14" title="Figure�22.16.�cupsaddsmb Flowchart.">The cupsaddsmb Flowchart</a> shows a chart about the procedures, command flows, and
 data flows of the <code class="literal">cupaddsmb</code> command. Note again: cupsaddsmb is
 not intended to, and does not work with, raw print queues!
-</p><div class="figure"><a name="small14"></a><p class="title"><b>Figure�22.16.�cupsaddsmb Flowchart.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/14small.png" alt="cupsaddsmb Flowchart."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643176"></a>Installing the PostScript Driver on a Client</h3></div></div></div><p>
-<a class="indexterm" name="id2643185"></a>
-<a class="indexterm" name="id2643192"></a>
+</p><div class="figure"><a name="small14"></a><p class="title"><b>Figure�22.16.�cupsaddsmb Flowchart.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/14small.png" alt="cupsaddsmb Flowchart."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643321"></a>Installing the PostScript Driver on a Client</h3></div></div></div><p>
+<a class="indexterm" name="id2643329"></a>
+<a class="indexterm" name="id2643336"></a>
 After <code class="literal">cupsaddsmb</code> is completed, your driver is prepared for the clients to use. Here are the
 steps you must perform to download and install it via Point'n'Print. From a Windows client, browse to the
 CUPS/Samba server:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2643214"></a>
+	<a class="indexterm" name="id2643359"></a>
 	Open the <span class="guilabel">Printers</span> share of Samba in Network Neighborhood.</p></li><li><p>Right-click on the printer in question.</p></li><li><p>From the opening context menu select
 	<span class="guimenuitem">Install...</span> or 
 	<span class="guimenuitem">Connect...</span> (depending on the Windows version you use).</p></li></ul></div><p>
@@ -1830,9 +1830,9 @@ you want to test it and send your first job from an application like Microsoft W
 the new printer appears in a
 <code class="filename">\\SambaServer\PrinterName</code> entry in the drop-down list of available printers.
 </p><p>
-<a class="indexterm" name="id2643284"></a>
-<a class="indexterm" name="id2643290"></a>
-<a class="indexterm" name="id2643297"></a>
+<a class="indexterm" name="id2643429"></a>
+<a class="indexterm" name="id2643435"></a>
+<a class="indexterm" name="id2643442"></a>
 <code class="literal">cupsaddsmb</code> will only reliably work with CUPS version 1.1.15 or higher and with Samba
 version 2.2.4, or later. If it does not work, or if the automatic printer driver download to the clients does
 not succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on
@@ -1861,34 +1861,34 @@ with the output your client driver settings produce. Treat it well:
 	Sometimes you can choose PostScript Language Level: in case of problems try 2
 	instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe).
 	</p></li><li><p>
-	Say Yes to PostScript Error Handler (Adobe).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2643411"></a>Installing PostScript Driver Files Manually Using rpcclient</h2></div></div></div><p>
+	Say Yes to PostScript Error Handler (Adobe).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2643556"></a>Installing PostScript Driver Files Manually Using rpcclient</h2></div></div></div><p>
 Of course, you can run all the commands that are embedded into the
 cupsaddsmb convenience utility yourself, one by one, and upload
 and prepare the driver files for future client downloads.
 </p><div class="orderedlist"><ol type="1"><li><p>Prepare Samba (a CUPS print queue with the name of the
 	printer should be there. We are providing the driver now).</p></li><li><p>Copy all files to <em class="parameter"><code>[print$]</code></em>.</p></li><li><p>
-	<a class="indexterm" name="id2643450"></a>
+	<a class="indexterm" name="id2643595"></a>
 	Run <code class="literal">rpcclient adddriver</code>
 	(for each client architecture you want to support).</p></li><li><p>
-	<a class="indexterm" name="id2643471"></a>
+	<a class="indexterm" name="id2643616"></a>
 	Run <code class="literal">rpcclient setdriver.</code></p></li></ol></div><p>
-<a class="indexterm" name="id2643490"></a>
-<a class="indexterm" name="id2643499"></a>
-<a class="indexterm" name="id2643508"></a>
-<a class="indexterm" name="id2643517"></a>
-<a class="indexterm" name="id2643527"></a>
+<a class="indexterm" name="id2643634"></a>
+<a class="indexterm" name="id2643644"></a>
+<a class="indexterm" name="id2643653"></a>
+<a class="indexterm" name="id2643662"></a>
+<a class="indexterm" name="id2643671"></a>
 We are going to do this now. First, read the man page on <em class="parameter"><code>rpcclient</code></em> to get a first idea.
 Look at all the printing-related subcommands: <code class="literal">enumprinters</code>, <code class="literal">enumdrivers</code>,
 <code class="literal">enumports</code>, <code class="literal">adddriver</code>, and <code class="literal">setdriver</code> are among the
 most interesting ones. <em class="parameter"><code>rpcclient</code></em> implements an important part of the MS-RPC protocol.
 You can use it to query (and command) a Windows NT (or 200x/XP) PC, too. MS-RPC is used by Windows clients,
 among other things, to benefit from the Point'n'Print features. Samba can now mimic this as well.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643585"></a>A Check of the rpcclient man Page</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643730"></a>A Check of the rpcclient man Page</h3></div></div></div><p>
 First let's check the <em class="parameter"><code>rpcclient</code></em> man page. Here are two relevant passages:
 </p><p>
-<a class="indexterm" name="id2643604"></a>
-<a class="indexterm" name="id2643610"></a>
-<a class="indexterm" name="id2643617"></a>
+<a class="indexterm" name="id2643748"></a>
+<a class="indexterm" name="id2643755"></a>
+<a class="indexterm" name="id2643762"></a>
 <code class="literal">adddriver &lt;arch&gt; &lt;config&gt;</code> Execute an <code class="literal">AddPrinterDriver()</code> RPC
 to install the printer driver information on the server. The driver files should already exist in the
 directory returned by <code class="literal">getdriverdir</code>. Possible values for <em class="parameter"><code>arch</code></em> are the
@@ -1911,18 +1911,18 @@ drivers can use a bidirectional link for communication. This field should be &#8
 NT print server, the print monitor for a driver must already be installed before adding the driver or else the
 RPC will fail.
 </p><p>
-<a class="indexterm" name="id2643695"></a>
-<a class="indexterm" name="id2643702"></a>
+<a class="indexterm" name="id2643840"></a>
+<a class="indexterm" name="id2643847"></a>
 <code class="literal">setdriver &lt;printername&gt; &lt;drivername&gt;</code> Execute a <code class="literal">SetPrinter()</code>
 command to update the printer driver associated with an installed printer. The printer driver must already be
 correctly installed on the print server.
 </p><p>
-<a class="indexterm" name="id2643728"></a>
-<a class="indexterm" name="id2643734"></a>
+<a class="indexterm" name="id2643872"></a>
+<a class="indexterm" name="id2643879"></a>
 See also the <code class="literal">enumprinters</code> and <code class="literal">enumdrivers</code> commands to
 obtain a list of installed printers and drivers.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643757"></a>Understanding the rpcclient man Page</h3></div></div></div><p>
-<a class="indexterm" name="id2643765"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643902"></a>Understanding the rpcclient man Page</h3></div></div></div><p>
+<a class="indexterm" name="id2643910"></a>
 The <span class="emphasis"><em>exact</em></span> format isn't made too clear by the man page, since you have to deal with some
 parameters containing spaces. Here is a better description for it. We have line-broken the command and
 indicated the breaks with &#8220;<span class="quote">\</span>&#8221;. Usually you would type the command in one line without the line
@@ -1946,9 +1946,9 @@ printer presents the files to us. Remember that this whole procedure has to be d
 listening to the traffic caused by Windows computers on the wire. We may as well turn to a Windows box now and
 access it from a UNIX workstation. We will query it with <code class="literal">rpcclient</code> to see what it tells us
 and try to understand the man page more clearly.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643862"></a>Producing an Example by Querying a Windows Box</h3></div></div></div><p>
-<a class="indexterm" name="id2643870"></a>
-<a class="indexterm" name="id2643879"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644007"></a>Producing an Example by Querying a Windows Box</h3></div></div></div><p>
+<a class="indexterm" name="id2644015"></a>
+<a class="indexterm" name="id2644024"></a>
 We could run <code class="literal">rpcclient</code> with a <code class="literal">getdriver</code> or a
 <code class="literal">getprinter</code> subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or Linux
 workstation with the Samba utilities installed, then type the following command:
@@ -1956,7 +1956,7 @@ workstation with the Samba utilities installed, then type the following command:
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -U'user%secret' NT-SERVER -c 'getdriver printername 3'</code></strong>
 </pre><p>
 From the result it should become clear which is which. Here is an example from my installation:
-<a class="indexterm" name="id2643930"></a>
+<a class="indexterm" name="id2644075"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -U'Danka%xxxx' W200xSERVER \
     -c'getdriver "DANKA InfoStream Virtual Printer" 3'</code></strong>
@@ -1987,10 +1987,10 @@ Some printer drivers list additional files under the label <em class="parameter"
 would go into the last field <em class="parameter"><code>ListOfFiles,Comma-separated</code></em>. For the CUPS PostScript
 drivers, we do not need any (nor would we for the Adobe PostScript driver); therefore, the field will get a
 &#8220;<span class="quote">NULL</span>&#8221; entry.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643994"></a>Requirements for adddriver and setdriver to Succeed</h3></div></div></div><p>
-<a class="indexterm" name="id2644002"></a>
-<a class="indexterm" name="id2644012"></a>
-<a class="indexterm" name="id2644018"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644139"></a>Requirements for adddriver and setdriver to Succeed</h3></div></div></div><p>
+<a class="indexterm" name="id2644147"></a>
+<a class="indexterm" name="id2644156"></a>
+<a class="indexterm" name="id2644163"></a>
 From the man page (and from the quoted output of <code class="literal">cupsaddsmb</code> above) it becomes clear that
 you need to have certain conditions in order to make the manual uploading and initializing of the driver files
 succeed. The two <code class="literal">rpcclient</code> subcommands (<code class="literal">adddriver</code> and
@@ -2007,19 +2007,19 @@ succeed. The two <code class="literal">rpcclient</code> subcommands (<code class
 	the <em class="parameter"><code>[print$]</code></em> share and create
 	subdirectories.</p></li><li><p>The printer you are going to set up for the Windows
 	clients needs to be installed in CUPS already.</p></li><li><p>
-	<a class="indexterm" name="id2644172"></a>
-	<a class="indexterm" name="id2644181"></a>
+	<a class="indexterm" name="id2644316"></a>
+	<a class="indexterm" name="id2644326"></a>
 	The CUPS printer must be known to Samba; otherwise the <code class="literal">setdriver</code> subcommand fails with an
 	NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by Samba, you may use the
 	<code class="literal">enumprinters</code> subcommand to <code class="literal">rpcclient</code>. A long-standing bug prevented a
 	proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember
 	this in case you've created the CUPS printer just recently and encounter problems: try restarting Samba.
-	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644219"></a>Manual Driver Installation in 15 Steps</h3></div></div></div><p>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644363"></a>Manual Driver Installation in 15 Steps</h3></div></div></div><p>
 We are going to install a printer driver now by manually executing all
 required commands. Because this may seem a rather complicated process at
 first, we go through the procedure step by step, explaining every
 single action item as it comes up.
-</p><div class="procedure"><a name="id2644232"></a><p class="title"><b>Procedure�22.2.�Manual Driver Installation</b></p><ol type="1"><li><p class="title"><b>Install the printer on CUPS.</b></p><pre class="screen">
+</p><div class="procedure"><a name="id2644377"></a><p class="title"><b>Procedure�22.2.�Manual Driver Installation</b></p><ol type="1"><li><p class="title"><b>Install the printer on CUPS.</b></p><pre class="screen">
 	<code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \
 				-P canonIR85.ppd</code></strong>
 	</pre><p>
@@ -2028,7 +2028,7 @@ single action item as it comes up.
 	(a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 	for this step.
 	</p></li><li><p class="title"><b>(Optional.) Check if the printer is recognized by Samba.</b></p><p>
-	<a class="indexterm" name="id2644289"></a>
+	<a class="indexterm" name="id2644434"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
   | grep -C2 mysmbtstprn</code></strong>
@@ -2048,8 +2048,8 @@ comment:[mysmbtstprn]
 	of the following steps. Alternatively, you can authenticate as one of the users from the &#8220;<span class="quote">write
 	list</span>&#8221; as defined in <code class="filename">smb.conf</code> for <em class="parameter"><code>[print$]</code></em>.
 	</p></li><li><p class="title"><b>(Optional.) Check if Samba knows a driver for the printer.</b></p><p>
-	<a class="indexterm" name="id2644387"></a>
-	<a class="indexterm" name="id2644396"></a>
+	<a class="indexterm" name="id2644531"></a>
+	<a class="indexterm" name="id2644541"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2'\
  localhost | grep driver </code></strong>
@@ -2105,7 +2105,7 @@ drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
 The driver files now are in the W32X86 architecture &#8220;<span class="quote">root</span>&#8221; of
 <em class="parameter"><code>[print$]</code></em>.
 </p></li><li><p class="title"><b>Tell Samba that these are driver files (<code class="literal">adddriver</code>).</b></p><p>
-<a class="indexterm" name="id2644584"></a>
+<a class="indexterm" name="id2644729"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
 	"mydrivername:cupsdrvr.dll:mysmbtstprn.PPD: \
@@ -2136,7 +2136,7 @@ total 5039
 Notice how step 6 also moved the driver files to the appropriate
 subdirectory. Compare this with the situation after step 5.
 </p></li><li><p class="title"><b>(Optional.) Verify if Samba now recognizes the driver.</b></p><p>
-<a class="indexterm" name="id2644692"></a>
+<a class="indexterm" name="id2644837"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'enumdrivers 3' \
 	localhost | grep -B2 -A5 mydrivername</code></strong>
@@ -2152,7 +2152,7 @@ Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 Remember, this command greps for the name you chose for the
 driver in step 6. This command must succeed before you can proceed.
 </p></li><li><p class="title"><b>Tell Samba which printer should use these driver files (<code class="literal">setdriver</code>).</b></p><p>
-<a class="indexterm" name="id2644747"></a>
+<a class="indexterm" name="id2644892"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \
 	localhost</code></strong>
@@ -2163,9 +2163,9 @@ queues that use the same driver. You do not need to repeat all the previous step
 succeed. The only preconditions are that <code class="literal">enumdrivers</code> must find the driver and
 <code class="literal">enumprinters</code> must find the printer.
 </p></li><li><p class="title"><b>(Optional) Verify if Samba has recognized this association.</b></p><p>
-<a class="indexterm" name="id2644806"></a>
-<a class="indexterm" name="id2644815"></a>
-<a class="indexterm" name="id2644825"></a>
+<a class="indexterm" name="id2644951"></a>
+<a class="indexterm" name="id2644960"></a>
+<a class="indexterm" name="id2644969"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
   | grep driver</code></strong>
@@ -2205,13 +2205,13 @@ Printer Driver Info 3:
      comment:[mysmbtstprn]
 
 </pre><p>
-<a class="indexterm" name="id2644902"></a>
+<a class="indexterm" name="id2645047"></a>
 Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even
 the <code class="literal">enumprinters</code> command now lists the driver
 on the &#8220;<span class="quote">description</span>&#8221; line.
 </p></li><li><p class="title"><b>(Optional.) Tickle the driver into a correct
 device mode.</b></p><p>
-<a class="indexterm" name="id2644937"></a>
+<a class="indexterm" name="id2645082"></a>
 You certainly know how to install the driver on the client. In case
 you are not particularly familiar with Windows, here is a short
 recipe: Browse the Network Neighborhood, go to the Samba server, and look
@@ -2234,12 +2234,12 @@ into the &#8220;<span class="quote">DOS box</span>&#8221; (type root's smbpasswo
 Change any printer setting once (like changing <span class="emphasis"><em><span class="guilabel">portrait</span> to
 <span class="guilabel">landscape</span></em></span>), click on <span class="guibutton">Apply</span>, and change the setting back.
 </p></li><li><p class="title"><b>Install the printer on a client (Point'n'Print).</b></p><p>
-<a class="indexterm" name="id2645056"></a>
+<a class="indexterm" name="id2645200"></a>
 </p><pre class="screen">
 <code class="prompt">C:\&gt; </code><strong class="userinput"><code>rundll32 printui.dll,PrintUIEntry /in /n "\\sambaserver\mysmbtstprn"</code></strong>
 </pre><p>
 If it does not work, it could be a permissions problem with the <em class="parameter"><code>[print$]</code></em> share.
-</p></li><li><p class="title"><b>(Optional) Print a test page.</b></p><a class="indexterm" name="id2645097"></a><pre class="screen">
+</p></li><li><p class="title"><b>(Optional) Print a test page.</b></p><a class="indexterm" name="id2645242"></a><pre class="screen">
 <code class="prompt">C:\&gt; </code><strong class="userinput"><code>rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"</code></strong>
 </pre><p>
 Then hit [TAB] five times, [ENTER] twice, [TAB] once, and [ENTER] again, and march to the printer.
@@ -2249,8 +2249,8 @@ Just put it in a frame and bolt it to the wall with the heading "MY FIRST RPCCLI
  why not just throw it away!
 </p></li><li><p class="title"><b>(Obligatory.) Enjoy. Jump. Celebrate your success.</b></p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>echo "Cheeeeerioooooo! Success..." &gt;&gt; /var/log/samba/log.smbd</code></strong>
-</pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645177"></a>Troubleshooting Revisited</h3></div></div></div><p>
-<a class="indexterm" name="id2645185"></a>
+</pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645322"></a>Troubleshooting Revisited</h3></div></div></div><p>
+<a class="indexterm" name="id2645330"></a>
 The setdriver command will fail if in Samba's mind the queue is not
 already there. A successful installation displys the promising message that the:
 </p><pre class="screen">
@@ -2261,20 +2261,20 @@ a disappointing message like this one:
 <code class="computeroutput">
 result was NT_STATUS_UNSUCCESSFUL
 </code></p><p>
-<a class="indexterm" name="id2645217"></a>
-<a class="indexterm" name="id2645224"></a>
+<a class="indexterm" name="id2645362"></a>
+<a class="indexterm" name="id2645369"></a>
 It is not good enough that you can see the queue in CUPS, using the <code class="literal">lpstat -p ir85wm</code>
 command. A bug in most recent versions of Samba prevents the proper update of the queue list. The recognition
 of newly installed CUPS printers fails unless you restart Samba or send a HUP to all smbd processes. To verify
 if this is the reason why Samba does not execute the <code class="literal">setdriver</code> command successfully, check
 if Samba &#8220;<span class="quote">sees</span>&#8221; the printer:
-<a class="indexterm" name="id2645253"></a>
+<a class="indexterm" name="id2645398"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm</code></strong>
         printername:[ir85wm]
 </pre><p>
 An alternate command could be this: 
-<a class="indexterm" name="id2645283"></a>
+<a class="indexterm" name="id2645428"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </code></strong>
         cmd = getprinter ir85wm
@@ -2284,28 +2284,28 @@ An alternate command could be this:
         comment:[CUPS PostScript-Treiber for Windows NT/200x/XP]
 </pre><p>
 By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too!
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645320"></a>The Printing <code class="filename">*.tdb</code> Files</h2></div></div></div><p>
-<a class="indexterm" name="id2645334"></a>
-<a class="indexterm" name="id2645341"></a>
-<a class="indexterm" name="id2645350"></a>
-<a class="indexterm" name="id2645359"></a>
-<a class="indexterm" name="id2645368"></a>
-<a class="indexterm" name="id2645377"></a>
-<a class="indexterm" name="id2645386"></a>
-<a class="indexterm" name="id2645395"></a>
-<a class="indexterm" name="id2645404"></a>
-<a class="indexterm" name="id2645413"></a>
-<a class="indexterm" name="id2645422"></a>
-<a class="indexterm" name="id2645431"></a>
-<a class="indexterm" name="id2645440"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645465"></a>The Printing <code class="filename">*.tdb</code> Files</h2></div></div></div><p>
+<a class="indexterm" name="id2645479"></a>
+<a class="indexterm" name="id2645486"></a>
+<a class="indexterm" name="id2645495"></a>
+<a class="indexterm" name="id2645504"></a>
+<a class="indexterm" name="id2645513"></a>
+<a class="indexterm" name="id2645522"></a>
+<a class="indexterm" name="id2645531"></a>
+<a class="indexterm" name="id2645540"></a>
+<a class="indexterm" name="id2645549"></a>
+<a class="indexterm" name="id2645558"></a>
+<a class="indexterm" name="id2645567"></a>
+<a class="indexterm" name="id2645576"></a>
+<a class="indexterm" name="id2645585"></a>
 Some mystery is associated with the series of files with a tdb suffix appearing in every Samba installation.
 They are <code class="filename">connections.tdb</code>, <code class="filename">printing.tdb</code>,
 <code class="filename">share_info.tdb</code>, <code class="filename">ntdrivers.tdb</code>, <code class="filename">unexpected.tdb</code>,
 <code class="filename">brlock.tdb</code>, <code class="filename">locking.tdb</code>, <code class="filename">ntforms.tdb</code>,
 <code class="filename">messages.tdb</code> , <code class="filename">ntprinters.tdb</code>, <code class="filename">sessionid.tdb</code>,
 and <code class="filename">secrets.tdb</code>. What is their purpose?
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645523"></a>Trivial Database Files</h3></div></div></div><p>
-<a class="indexterm" name="id2645531"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645668"></a>Trivial Database Files</h3></div></div></div><p>
+<a class="indexterm" name="id2645676"></a>
 A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by
 storing entries in the Windows registry. Client queries are answered by reading from the registry,
 Administrator or user configuration settings that are saved by writing into the registry. Samba and UNIX
@@ -2314,7 +2314,7 @@ of <code class="filename">*.tdb</code> files. (TDB stands for trivial data base)
 <code class="filename">/var/lib/samba/</code> or <code class="filename">/var/lock/samba/</code>. The printing-related files are
 <code class="filename">ntprinters.tdb</code>, <code class="filename">printing.tdb</code>,<code class="filename">ntforms.tdb</code>, and
 <code class="filename">ntdrivers.tdb</code>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645591"></a>Binary Format</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645735"></a>Binary Format</h3></div></div></div><p>
 <code class="filename">*.tdb</code> files are not human readable. They are written in a binary format. &#8220;<span class="quote">Why not
 ASCII?</span>&#8221;, you may ask. &#8220;<span class="quote">After all, ASCII configuration files are a good and proven tradition on
 UNIX.</span>&#8221; The reason for this design decision by the Samba Team is mainly performance. Samba needs to be
@@ -2323,16 +2323,16 @@ thousands of them. Some of these <code class="literal">smbds</code> might need t
 <code class="filename">*.tdb</code> file <span class="emphasis"><em>at the same time</em></span>. The file format of Samba's
 <code class="filename">*.tdb</code> files allows for this provision. Many smbd processes may write to the same
 <code class="filename">*.tdb</code> file at the same time. This wouldn't be possible with pure ASCII files.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645657"></a>Losing <code class="filename">*.tdb</code> Files</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645802"></a>Losing <code class="filename">*.tdb</code> Files</h3></div></div></div><p>
 It is very important that all <code class="filename">*.tdb</code> files remain consistent over all write and read
 accesses. However, it may happen that these files <span class="emphasis"><em>do</em></span> get corrupted. (A <code class="literal">kill -9
 `pidof smbd'</code> while a write access is in progress could do the damage, as could a power interruption,
 etc.). In cases of trouble, a deletion of the old printing-related <code class="filename">*.tdb</code> files may be the
 only option. After that, you need to re-create all print-related setups unless you have made a backup of the
 <code class="filename">*.tdb</code> files in time.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645708"></a>Using <code class="literal">tdbbackup</code></h3></div></div></div><p>
-<a class="indexterm" name="id2645720"></a>
-<a class="indexterm" name="id2645731"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645852"></a>Using <code class="literal">tdbbackup</code></h3></div></div></div><p>
+<a class="indexterm" name="id2645865"></a>
+<a class="indexterm" name="id2645876"></a>
 Samba ships with a little utility that helps the root user of your system to backup your
 <code class="filename">*.tdb</code> files. If you run it with no argument, it prints a usage message:
 </p><pre class="screen">
@@ -2359,10 +2359,10 @@ ntprinters.tdb sessionid.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb.bak
 
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645827"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div></div><p>
-<a class="indexterm" name="id2645836"></a>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645972"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div></div><p>
+<a class="indexterm" name="id2645980"></a>
 CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows:
-<a class="indexterm" name="id2645845"></a>
+<a class="indexterm" name="id2645989"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</code></strong>
 </pre><p>
@@ -2378,9 +2378,9 @@ excellent recommendations about which driver is best used for each printer. Its
 the tireless work of Till Kamppeter from Mandrakesoft, who is also the principal author of the
 <code class="literal">foomatic-rip</code> utility.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2645934"></a>
-<a class="indexterm" name="id2645941"></a>
-<a class="indexterm" name="id2645948"></a>
+<a class="indexterm" name="id2646079"></a>
+<a class="indexterm" name="id2646086"></a>
+<a class="indexterm" name="id2646092"></a>
 The former <code class="literal">cupsomatic</code> concept is now being replaced by the new successor, a much more
 powerful <code class="literal">foomatic-rip</code>.  <code class="literal">cupsomatic</code> is no longer maintained. Here is the
 new URL to the <a class="ulink" href="http://www.linuxprinting.org/driver_list.cgi" target="_top">Foomatic-3.0</a>
@@ -2389,9 +2389,9 @@ for your Foomatic-driven printers. foomatic-rip will not work with PPDs generate
 <code class="literal">cupsomatic</code>. The new-style PPDs are 100% compliant with the Adobe PPD specification. They
 are also intended to be used by Samba and the cupsaddsmb utility, to provide the driver files for the Windows
 clients!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646003"></a>foomatic-rip and Foomatic Explained</h3></div></div></div><p>
-<a class="indexterm" name="id2646011"></a>
-<a class="indexterm" name="id2646018"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646148"></a>foomatic-rip and Foomatic Explained</h3></div></div></div><p>
+<a class="indexterm" name="id2646156"></a>
+<a class="indexterm" name="id2646162"></a>
 Nowadays, most Linux distributions rely on the utilities from the <a class="ulink" href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a> to create their printing-related software
 (which, by the way, works on all UNIXes and on Mac OS X and Darwin, too).  The utilities from this sire have a
 very end-user-friendly interface that allows for an easy update of drivers and PPDs for all supported models,
@@ -2402,8 +2402,8 @@ Recently, Foomatic has achieved the astonishing milestone of <a class="ulink" hr
 Linuxprinting.org keeps all the important facts about printer drivers, supported models, and which options are
 available for the various driver/printer combinations in its <a class="ulink" href="http://www.linuxprinting.org/foomatic.html" target="_top">Foomatic</a> database. Currently there are <a class="ulink" href="http://www.linuxprinting.org/driver_list.cgi" target="_top">245 drivers</a> in the database. Many drivers support
 various models, and many models may be driven by different drivers  its your choice!
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646072"></a>690 &#8220;<span class="quote">Perfect</span>&#8221; Printers</h4></div></div></div><p>
-<a class="indexterm" name="id2646084"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646217"></a>690 &#8220;<span class="quote">Perfect</span>&#8221; Printers</h4></div></div></div><p>
+<a class="indexterm" name="id2646228"></a>
 At present, there are 690 devices dubbed as working perfectly: 181 are <span class="emphasis"><em>mostly</em></span> perfect, 96
 are <span class="emphasis"><em>partially</em></span> perfect, and 46 are paperweights. Keeping in mind that most of these are
 non-PostScript models (PostScript printers are automatically supported by CUPS to perfection by using their
@@ -2411,7 +2411,7 @@ own manufacturer-provided Windows PPD), and that a multifunctional device never
 if it does not also scan and copy and fax under GNU/Linux  then this is a truly astonishing
 achievement! Three years ago the number was not more than 500, and Linux or UNIX printing at the time wasn't
 anywhere near the quality it is today.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646113"></a>How the Printing HOWTO Started It All</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646258"></a>How the Printing HOWTO Started It All</h4></div></div></div><p>
 A few years ago <a class="ulink" href="http://www2.picante.com/" target="_top">Grant Taylor</a> started it all. The
 roots of today's Linuxprinting.org are in the first <a class="ulink" href="http://www.linuxprinting.org/foomatic2.9/howto/" target="_top">Linux Printing HOWTO</a> that he authored. As a
 side-project to this document, which served many Linux users and admins to guide their first steps in this
@@ -2420,8 +2420,8 @@ distinct patterns of ink or toner particles on paper substrates</span>&#8221;),
 Postgres database with information about the hardware and driver zoo that made up Linux printing of the time.
 This database became the core component of today's Foomatic collection of tools and data. In the meantime, it
 has moved to an XML representation of the data.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646151"></a>Foomatic's Strange Name</h4></div></div></div><p>
-<a class="indexterm" name="id2646159"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646296"></a>Foomatic's Strange Name</h4></div></div></div><p>
+<a class="indexterm" name="id2646304"></a>
 &#8220;<span class="quote">Why the funny name?</span>&#8221; you ask. When it really took off, around spring 2000, CUPS was far less
 popular than today, and most systems used LPD, LPRng, or even PDQ to print. CUPS shipped with a few generic
 drivers (good for a few hundred different printer models). These didn't support many device-specific options.
@@ -2439,10 +2439,10 @@ several birds with one stone:
 	to CUPS users (because often the traditional Ghostscript way of
 	printing was the only one available).</p></li><li><p>It gave all the advanced CUPS options (Web interface,
 	GUI driver configurations) to users wanting (or needing) to use
-	Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646226"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div></div><p>
-<a class="indexterm" name="id2646234"></a>
-<a class="indexterm" name="id2646241"></a>
-<a class="indexterm" name="id2646248"></a>
+	Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646371"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div></div><p>
+<a class="indexterm" name="id2646379"></a>
+<a class="indexterm" name="id2646386"></a>
+<a class="indexterm" name="id2646393"></a>
 CUPS worked through a quickly hacked-up filter script named <a class="ulink" href="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&amp;show=0" target="_top">cupsomatic</a>.  cupsomatic
 ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed.
 It just needed to be copied into the CUPS system to make it work. To configure the way cupsomatic controls the
@@ -2463,8 +2463,8 @@ So, to answer your question, &#8220;<span class="quote">Foomatic</span>&#8221; i
 behind the &#8220;<span class="quote">*omatic</span>&#8221; scripts.  Foomatic, up to versions 2.0.x, required (ugly) Perl data
 structures attached to Linuxprinting.org PPDs for CUPS. It had a different &#8220;<span class="quote">*omatic</span>&#8221; script for
 every spooler, as well as different printer configuration files.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646382"></a>The <span class="emphasis"><em>Grand Unification</em></span> Achieved</h4></div></div></div><p>
-<a class="indexterm" name="id2646393"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646526"></a>The <span class="emphasis"><em>Grand Unification</em></span> Achieved</h4></div></div></div><p>
+<a class="indexterm" name="id2646538"></a>
 This has all changed in Foomatic versions 2.9 (beta) and released as &#8220;<span class="quote">stable</span>&#8221; 3.0. It has now
 achieved the convergence of all *omatic scripts and is called the <a class="ulink" href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=0" target="_top">foomatic-rip</a>.
 This single script is the unification of the previously different spooler-specific *omatic scripts.
@@ -2473,18 +2473,18 @@ PostScript printer PPDs and the Linuxprinting.org-generated ones), all of a sudd
 have the power of PPDs at their disposal. Users only need to plug foomatic-rip into their system. For users
 there is improved media type and source support  paper sizes and trays are easier to configure.
 </p><p>
-<a class="indexterm" name="id2646429"></a>
-<a class="indexterm" name="id2646435"></a>
-<a class="indexterm" name="id2646442"></a>
+<a class="indexterm" name="id2646574"></a>
+<a class="indexterm" name="id2646580"></a>
+<a class="indexterm" name="id2646587"></a>
 Also, the new generation of Linuxprinting.org PPDs no longer contains Perl data structures. If you are a
 distro maintainer and have used the previous version of Foomatic, you may want to give the new one a spin, but
 remember to generate a new-version set of PPDs via the new <a class="ulink" href="http://www.linuxprinting.org/download/foomatic/foomatic-db-engine-3.0.0beta1.tar.gz" target="_top">foomatic-db-engine!</a>.
 Individual users just need to generate a single new PPD specific to their model by <a class="ulink" href="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/II.Foomatic-User/II.tutorial-handout-foomatic-user.html" target="_top">following
 the steps</a> outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing.
 </p><p>
-<a class="indexterm" name="id2646475"></a>
-<a class="indexterm" name="id2646482"></a>
-<a class="indexterm" name="id2646489"></a>
+<a class="indexterm" name="id2646620"></a>
+<a class="indexterm" name="id2646627"></a>
+<a class="indexterm" name="id2646634"></a>
 foomatic-rip is a very clever wrapper around the need to run Ghostscript with a different syntax, options,
 device selections, and/or filters for each different printer or spooler. At the same time, it can read the PPD
 associated with a print queue and modify the print job according to the user selections. Together with this
@@ -2492,8 +2492,8 @@ comes the 100% compliance of the new Foomatic PPDs with the Adobe spec. Some inn
 Foomatic concept may surprise users. It will support custom paper sizes for many printers and will support
 printing on media drawn from different paper trays within the same job (in both cases, even where there is no
 support for this from Windows-based vendor printer drivers).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646510"></a>Driver Development Outside</h4></div></div></div><p>
-<a class="indexterm" name="id2646518"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646655"></a>Driver Development Outside</h4></div></div></div><p>
+<a class="indexterm" name="id2646663"></a>
 Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent
 maintainers.  Linuxprinting.org just pools all the information and stores it in its database. In addition, it
 also provides the Foomatic glue to integrate the many drivers into any modern (or legacy) printing system
@@ -2501,25 +2501,25 @@ known to the world.
 </p><p>
 Speaking of the different driver development groups, most of the work is currently done in three projects:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2646542"></a>
+<a class="indexterm" name="id2646687"></a>
 	<a class="ulink" href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">Omni</a>
 	 a free software project by IBM that tries to convert its printer
 	driver knowledge from good-ol' OS/2 times into a modern, modular,
 	universal driver architecture for Linux/UNIX (still beta). This
 	currently supports 437 models.</p></li><li><p>
-<a class="indexterm" name="id2646567"></a>
+<a class="indexterm" name="id2646712"></a>
 	<a class="ulink" href="http://hpinkjet.sf.net/" target="_top">HPIJS</a> 
 	a free software project by HP to provide the support for its own
 	range of models (very mature, printing in most cases is perfect and
 	provides true photo quality). This currently supports 369
 	models.</p></li><li><p>
-<a class="indexterm" name="id2646590"></a>
+<a class="indexterm" name="id2646735"></a>
 	<a class="ulink" href="http://gimp-print.sourceforge.net/" target="_top">Gutenprint</a>  a free software
 	effort, started by Michael Sweet (also lead developer for CUPS), now
 	directed by Robert Krawitz, which has achieved an amazing level of
 	photo print quality (many Epson users swear that its quality is
 	better than the vendor drivers provided by Epson for the Microsoft
-	platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646614"></a>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</h4></div></div></div><p>
+	platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646759"></a>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</h4></div></div></div><p>
 Linuxprinting.org today is the one-stop shop to download printer drivers. Look for printer information and
 <a class="ulink" href="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/" target="_top">tutorials</a> or solve
 printing problems in its popular <a class="ulink" href="http://www.linuxprinting.org/newsportal/" target="_top">forums</a>. This
@@ -2528,9 +2528,9 @@ commercial UNIX systems</a> are also going there, and the relatively new
 <a class="ulink" href="http://www.linuxprinting.org/newsportal/thread.php3?name=linuxprinting.macosx.general" target="_top">Mac OS X
 forum</a> has turned out to be one of the most frequented forums after only a few weeks.
 </p><p>
-<a class="indexterm" name="id2646659"></a>
-<a class="indexterm" name="id2646666"></a>
-<a class="indexterm" name="id2646673"></a>
+<a class="indexterm" name="id2646804"></a>
+<a class="indexterm" name="id2646811"></a>
+<a class="indexterm" name="id2646818"></a>
 Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard tool-chain for
 printing on all the important distros. Most of them also have CUPS underneath. While in recent years most
 printer data had been added by Kamppeter, many additional contributions came from engineers with SuSE, Red
@@ -2539,16 +2539,16 @@ and Conectiva have merged and are now called Mandriva.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Till Kamppeter from Mandrakesoft is doing an excellent job in his spare time to maintain Linuxprinting.org and
 Foomatic. So if you use it often, please send him a note showing your appreciation.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646698"></a>Foomatic Database-Generated PPDs</h4></div></div></div><p>
-<a class="indexterm" name="id2646706"></a>
-<a class="indexterm" name="id2646713"></a>
-<a class="indexterm" name="id2646720"></a>
-<a class="indexterm" name="id2646726"></a>
-<a class="indexterm" name="id2646733"></a>
-<a class="indexterm" name="id2646740"></a>
-<a class="indexterm" name="id2646747"></a>
-<a class="indexterm" name="id2646754"></a>
-<a class="indexterm" name="id2646761"></a>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646842"></a>Foomatic Database-Generated PPDs</h4></div></div></div><p>
+<a class="indexterm" name="id2646850"></a>
+<a class="indexterm" name="id2646857"></a>
+<a class="indexterm" name="id2646864"></a>
+<a class="indexterm" name="id2646871"></a>
+<a class="indexterm" name="id2646878"></a>
+<a class="indexterm" name="id2646884"></a>
+<a class="indexterm" name="id2646891"></a>
+<a class="indexterm" name="id2646898"></a>
+<a class="indexterm" name="id2646905"></a>
 The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver
 information, but it is organized in a way that it can generate PPD files on the fly from its internal
 XML-based datasets. While these PPDs are modeled to the Adobe specification of PPDs, the
@@ -2563,7 +2563,7 @@ ask from Ghostscript to convert the PostScript print job into a raster format re
 This usage of PPDs to describe the options of non-PostScript printers was the invention of the CUPS
 developers. The rest is easy.  GUI tools (like KDE's marvelous <a class="ulink" href="http://printing.kde.org/overview/kprinter.phtml" target="_top">kprinter</a> or the GNOME <a class="ulink" href="http://gtklp.sourceforge.net/" target="_top">gtklp</a> xpp and the CUPS Web interface) read the PPD as well and use
 this information to present the available settings to the user as an intuitive menu selection.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646814"></a>foomatic-rip and Foomatic PPD Download and Installation</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646969"></a>foomatic-rip and Foomatic PPD Download and Installation</h3></div></div></div><p>
 Here are the steps to install a foomatic-rip-driven LaserJet 4 Plus-compatible
 printer in CUPS (note that recent distributions of SuSE, UnitedLinux and
 Mandrake may ship with a complete package of Foomatic-PPDs plus the
@@ -2656,8 +2656,8 @@ how the resulting raster data should look and which printer commands to embed in
 	fit for your printer model's consumption.</p></li><li><p>Ghostscript <span class="emphasis"><em>must</em></span> (depending on
 	the driver/model) contain support for a certain device representing
 	the selected driver for your model (as shown by <code class="literal">gs -h</code>).</p></li><li><p>foomatic-rip needs a new version of PPDs (PPD versions
-	produced for cupsomatic do not work with foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647287"></a>Page Accounting with CUPS</h2></div></div></div><p>
-<a class="indexterm" name="id2647295"></a>
+	produced for cupsomatic do not work with foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647442"></a>Page Accounting with CUPS</h2></div></div></div><p>
+<a class="indexterm" name="id2647450"></a>
 Often there are questions regarding print quotas where Samba users (that is, Windows clients) should not be
 able to print beyond a certain number of pages or data volume per day, week, or month. This feature is
 dependent on the real print subsystem you're using.  Samba's part is always to receive the job files from the
@@ -2665,18 +2665,18 @@ clients (filtered <span class="emphasis"><em>or</em></span> unfiltered) and hand
 </p><p>
 Of course one could hack things with one's own scripts. But then there is CUPS. CUPS supports quotas that can
 be based on the size of jobs or on the number of pages or both, and can span any time period you want.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647322"></a>Setting Up Quotas</h3></div></div></div><p>
-<a class="indexterm" name="id2647330"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647478"></a>Setting Up Quotas</h3></div></div></div><p>
+<a class="indexterm" name="id2647486"></a>
 This is an example command of how root would set a print quota in CUPS, assuming an existing printer named
 &#8220;<span class="quote">quotaprinter</span>&#8221;:
-<a class="indexterm" name="id2647345"></a>
+<a class="indexterm" name="id2647500"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p quotaprinter -o job-quota-period=604800 \
 	-o job-k-limit=1024 -o job-page-limit=100</code></strong>
 </pre><p>
 This would limit every single user to print no more than 100 pages or 1024 KB of
 data (whichever comes first) within the last 604,800 seconds ( = 1 week).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647376"></a>Correct and Incorrect Accounting</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647532"></a>Correct and Incorrect Accounting</h3></div></div></div><p>
 For CUPS to count correctly, the printfile needs to pass the CUPS pstops filter; otherwise it uses a dummy
 count of &#8220;<span class="quote">one</span>&#8221;. Some print files do not pass it (e.g., image files), but then those are mostly
 one-page jobs anyway. This also means that proprietary drivers for the target printer running on the client
@@ -2687,12 +2687,12 @@ You need to send PostScript from the clients (i.e., run a PostScript driver ther
 accounting done. If the printer is a non-PostScript model, you need to let CUPS do the job to convert the file
 to a print-ready format for the target printer. This is currently working for about a thousand different
 printer models.  Linuxprinting.org has a driver <a class="ulink" href="http://www.linuxprinting.org/printer_list.cgi" target="_top">list</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647417"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div></div><p>
-<a class="indexterm" name="id2647426"></a>
-<a class="indexterm" name="id2647432"></a>
-<a class="indexterm" name="id2647439"></a>
-<a class="indexterm" name="id2647446"></a>
-<a class="indexterm" name="id2647453"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647572"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div></div><p>
+<a class="indexterm" name="id2647581"></a>
+<a class="indexterm" name="id2647588"></a>
+<a class="indexterm" name="id2647595"></a>
+<a class="indexterm" name="id2647601"></a>
+<a class="indexterm" name="id2647608"></a>
 Before CUPS 1.1.16, your only option was to use the Adobe PostScript driver on the Windows clients. The output
 of this driver was not always passed through the <code class="literal">pstops</code> filter on the CUPS/Samba side, and
 therefore was not counted correctly (the reason is that it often, depending on the PPD being used, wrote a
@@ -2703,13 +2703,13 @@ From CUPS 1.1.16 and later releases, you can use the CUPS PostScript driver for
 clients (which is tagged in the download area of <code class="filename">http://www.cups.org/</code> as the
 <code class="filename">cups-samba-1.1.16.tar.gz</code> package). It does <span class="emphasis"><em>not</em></span> work for Windows
 9x/Me clients, but it guarantees:
-</p><div class="itemizedlist"><ul type="disc"><li><p> <a class="indexterm" name="id2647513"></a> To not write a PJL-header.</p></li><li><p>To still read and support all PJL-options named in the
+</p><div class="itemizedlist"><ul type="disc"><li><p> <a class="indexterm" name="id2647668"></a> To not write a PJL-header.</p></li><li><p>To still read and support all PJL-options named in the
 	driver PPD with its own means.</p></li><li><p>That the file will pass through the <code class="literal">pstops</code> filter
 	on the CUPS/Samba server.</p></li><li><p>To page-count correctly the print file.</p></li></ul></div><p>
 You can read more about the setup of this combination in the man page for <code class="literal">cupsaddsmb</code> (which
 is only present with CUPS installed, and only current from CUPS 1.1.16).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647558"></a>The page_log File Syntax</h3></div></div></div><p>
-<a class="indexterm" name="id2647566"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647713"></a>The page_log File Syntax</h3></div></div></div><p>
+<a class="indexterm" name="id2647721"></a>
 These are the items CUPS logs in the <code class="filename">page_log</code> for every page of a job:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Printer name</p></li><li><p>User name</p></li><li><p>Job ID</p></li><li><p>Time of printing</p></li><li><p>Page number</p></li><li><p>Number of copies</p></li><li><p>A billing information string (optional)</p></li><li><p>The host that sent the job (included since version 1.1.19)</p></li></ul></div><p>
 Here is an extract of my CUPS server's <code class="filename">page_log</code> file to illustrate the
@@ -2727,7 +2727,7 @@ by user <em class="parameter"><code>kurt</code></em>, a 64-page job printed in t
  The next job had ID <em class="parameter"><code>402</code></em>, was sent by user <em class="parameter"><code>boss</code></em>
 from IP address <code class="constant">10.160.51.33</code>, printed from one page 440 copies, and
 is set to be billed to <em class="parameter"><code>finance-dep</code></em>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647709"></a>Possible Shortcomings</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647858"></a>Possible Shortcomings</h3></div></div></div><p>
 What flaws or shortcomings are there with this quota system?
 </p><div class="itemizedlist"><ul type="disc"><li><p>The ones named above (wrongly logged job in case of
 	printer hardware failure, and so on).</p></li><li><p>In reality, CUPS counts the job pages that are being
@@ -2741,7 +2741,7 @@ What flaws or shortcomings are there with this quota system?
 	&#8220;<span class="quote">used-up</span>&#8221; number of current quota.</p></li><li><p>A user having used up 99 sheets of a 100 quota will
 	still be able to send and print a 1,000 sheet job.</p></li><li><p>A user being denied a job because of a filled-up quota
 	does not get a meaningful error message from CUPS other than
-	&#8220;<span class="quote">client-error-not-possible</span>&#8221;.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647775"></a>Future Developments</h3></div></div></div><p>
+	&#8220;<span class="quote">client-error-not-possible</span>&#8221;.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647924"></a>Future Developments</h3></div></div></div><p>
 This is the best system currently available, and there are huge
 improvements under development for CUPS 1.2:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Page counting will go into the backends (these talk
@@ -2749,10 +2749,10 @@ improvements under development for CUPS 1.2:
 	actual printing process; thus, a jam at the fifth sheet will lead to a
 	stop in the counting).</p></li><li><p>Quotas will be handled more flexibly.</p></li><li><p>Probably there will be support for users to inquire
 	about their accounts in advance.</p></li><li><p>Probably there will be support for some other tools
-	around this topic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647815"></a>Other Accounting Tools</h3></div></div></div><p>
+	around this topic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647964"></a>Other Accounting Tools</h3></div></div></div><p>
 Other accounting tools that can be used includes: PrintAnalyzer, pyKota, printbill, LogReport.
 For more information regarding these tools you can try a Google search.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647829"></a>Additional Material</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647978"></a>Additional Material</h2></div></div></div><p>
 A printer queue with <span class="emphasis"><em>no</em></span> PPD associated to it is a
 &#8220;<span class="quote">raw</span>&#8221; printer, and all files will go directly there as received by the
 spooler. The exceptions are file types <em class="parameter"><code>application/octet-stream</code></em>
@@ -2831,15 +2831,15 @@ the jobs of hundreds of users on some big machine, where no user is
 allowed to have direct access (such as when the operators often need
 to load the proper paper type before running the 10,000 page job
 requested by marketing for the mailing, and so on).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648046"></a>Autodeletion or Preservation of CUPS Spool Files</h2></div></div></div><p>
-<a class="indexterm" name="id2648055"></a>
-<a class="indexterm" name="id2648062"></a>
-<a class="indexterm" name="id2648068"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648195"></a>Autodeletion or Preservation of CUPS Spool Files</h2></div></div></div><p>
+<a class="indexterm" name="id2648203"></a>
+<a class="indexterm" name="id2648210"></a>
+<a class="indexterm" name="id2648217"></a>
 Samba print files pass through two spool directories. One is the incoming directory managed by Samba (set in
 the <a class="link" href="smb.conf.5.html#PATH" target="_top">path = /var/spool/samba</a> directive in the <em class="parameter"><code>[printers]</code></em> section of <code class="filename">smb.conf</code>). The other is the spool directory of your UNIX print subsystem. For
 CUPS it is normally <code class="filename">/var/spool/cups/</code>, as set by the <code class="filename">cupsd.conf</code>
 directive <code class="filename">RequestRoot /var/spool/cups</code>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648122"></a>CUPS Configuration Settings Explained</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648271"></a>CUPS Configuration Settings Explained</h3></div></div></div><p>
 Some important parameter settings in the CUPS configuration file
 <code class="filename">cupsd.conf</code> are:
 </p><div class="variablelist"><dl><dt><span class="term">PreserveJobHistory Yes</span></dt><dd><p>
@@ -2863,7 +2863,7 @@ Some important parameter settings in the CUPS configuration file
 	</p></dd></dl></div><p>
 (There are also additional settings for <em class="parameter"><code>MaxJobsPerUser</code></em> and
 <em class="parameter"><code>MaxJobsPerPrinter</code></em>.)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648207"></a>Preconditions</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648356"></a>Preconditions</h3></div></div></div><p>
 For everything to work as it should, you need to have three things:
 </p><div class="itemizedlist"><ul type="disc"><li><p>A Samba smbd that is compiled against <code class="filename">libcups</code> (check
 	on Linux by running <strong class="userinput"><code>ldd `which smbd'</code></strong>).</p></li><li><p>A Samba-<code class="filename">smb.conf</code> setting of
@@ -2876,14 +2876,14 @@ In this case, all other manually set printing-related commands (like
 <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" target="_top">lppause command</a>, and
 <a class="link" href="smb.conf.5.html#LPRESUMECOMMAND" target="_top">lpresume command</a>) are ignored, and they should normally have no
 influence whatsoever on your printing.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648346"></a>Manual Configuration</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648495"></a>Manual Configuration</h3></div></div></div><p>
 If you want to do things manually, replace the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = cups</a>
 by <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd</a>. Then your manually set commands may work
 (I haven't tested this), and a <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command = lp -d %P %s; rm %s</a>
 may do what you need.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648394"></a>Printing from CUPS to Windows-Attached Printers</h2></div></div></div><p>
-<a class="indexterm" name="id2648402"></a>
-<a class="indexterm" name="id2648408"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648542"></a>Printing from CUPS to Windows-Attached Printers</h2></div></div></div><p>
+<a class="indexterm" name="id2648551"></a>
+<a class="indexterm" name="id2648557"></a>
 From time to time the question arises, how can you print <span class="emphasis"><em>to</em></span> a Windows-attached printer
 <span class="emphasis"><em>from</em></span> Samba? Normally the local connection from Windows host to printer would be done by
 USB or parallel cable, but this does not matter to Samba. From here only an SMB connection needs to be opened
@@ -2918,8 +2918,8 @@ If this symlink does not exist, create it:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s `which smbspool` /usr/lib/cups/backend/smb</code></strong>
 </pre><p>
-<a class="indexterm" name="id2648538"></a>
-<a class="indexterm" name="id2648545"></a>
+<a class="indexterm" name="id2648687"></a>
+<a class="indexterm" name="id2648694"></a>
 <code class="literal">smbspool</code> was written by Mike Sweet from the CUPS folks. It is included and ships with
 Samba. It may also be used with print subsystems other than CUPS, to spool jobs to Windows printer shares. To
 set up printer <em class="replaceable"><code>winprinter</code></em> on CUPS, you need to have a driver for it. Essentially
@@ -2934,9 +2934,9 @@ To install a printer with the <em class="parameter"><code>smb</code></em> backen
 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \
   -P /path/to/PPD</code></strong>
 </pre><p>
-<a class="indexterm" name="id2648615"></a>
-<a class="indexterm" name="id2648622"></a>
-<a class="indexterm" name="id2648628"></a>
+<a class="indexterm" name="id2648754"></a>
+<a class="indexterm" name="id2648761"></a>
+<a class="indexterm" name="id2648768"></a>
 The PPD must be able to direct CUPS to generate the print data for the target model. For PostScript printers,
 just use the PPD that would be used with the Windows NT PostScript driver. But what can you do if the printer
 is only accessible with a password? Or if the printer's host is part of another workgroup? This is provided
@@ -2949,10 +2949,10 @@ if you want to protect your passwords. Better share the printer in a way that do
 Printing will only work if you have a working NetBIOS name resolution up and running. Note that this is a
 feature of CUPS and you do not necessarily need to have smbd running.
 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648699"></a>More CUPS Filtering Chains</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648838"></a>More CUPS Filtering Chains</h2></div></div></div><p>
 The diagrams in <a class="link" href="CUPS-printing.html#cups1" title="Figure�22.17.�Filtering Chain 1.">Filtering Chain 1</a> and <a class="link" href="CUPS-printing.html#cups2" title="Figure�22.18.�Filtering Chain with cupsomatic">Filtering Chain with
 cupsomatic</a> show how CUPS handles print jobs.
-</p><div class="figure"><a name="cups1"></a><p class="title"><b>Figure�22.17.�Filtering Chain 1.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups1.png" alt="Filtering Chain 1."></div></div></div><br class="figure-break"><div class="figure"><a name="cups2"></a><p class="title"><b>Figure�22.18.�Filtering Chain with cupsomatic</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups2.png" width="243" alt="Filtering Chain with cupsomatic"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648810"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648816"></a>Windows 9x/Me Client Can't Install Driver</h3></div></div></div><p>For Windows 9x/Me, clients require the printer names to be eight
+</p><div class="figure"><a name="cups1"></a><p class="title"><b>Figure�22.17.�Filtering Chain 1.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups1.png" alt="Filtering Chain 1."></div></div></div><br class="figure-break"><div class="figure"><a name="cups2"></a><p class="title"><b>Figure�22.18.�Filtering Chain with cupsomatic</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups2.png" width="243" alt="Filtering Chain with cupsomatic"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648950"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648956"></a>Windows 9x/Me Client Can't Install Driver</h3></div></div></div><p>For Windows 9x/Me, clients require the printer names to be eight
 	characters (or &#8220;<span class="quote">8 plus 3 chars suffix</span>&#8221;) max; otherwise, the driver files
 	will not get transferred when you want to download them from Samba.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="root-ask-loop"></a>&#8220;<span class="quote">cupsaddsmb</span>&#8221; Keeps Asking for Root Password in Never-ending Loop</h3></div></div></div><p>Have you set <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>? Have
 	you used <code class="literal">smbpasswd</code> to give root a Samba account?
@@ -2963,10 +2963,10 @@ cupsomatic</a> show how CUPS handles print jobs.
 	password).</p><p>
 	If the error is &#8220;<span class="quote">Tree connect failed: NT_STATUS_BAD_NETWORK_NAME</span>&#8221;, 
 	you may have forgotten to create the <code class="filename">/etc/samba/drivers</code> directory.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648892"></a>&#8220;<span class="quote">cupsaddsmb</span>&#8221; or &#8220;<span class="quote">rpcclient addriver</span>&#8221; Emit Error</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649032"></a>&#8220;<span class="quote">cupsaddsmb</span>&#8221; or &#8220;<span class="quote">rpcclient addriver</span>&#8221; Emit Error</h3></div></div></div><p>
 	If <code class="literal">cupsaddsmb</code>, or <code class="literal">rpcclient addriver</code> emit the error message
 	WERR_BAD_PASSWORD, refer to <a class="link" href="CUPS-printing.html#root-ask-loop" title="cupsaddsmb Keeps Asking for Root Password in Never-ending Loop">the previous common error</a>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648930"></a>&#8220;<span class="quote">cupsaddsmb</span>&#8221; Errors</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649070"></a>&#8220;<span class="quote">cupsaddsmb</span>&#8221; Errors</h3></div></div></div><p>
 	The use of &#8220;<span class="quote">cupsaddsmb</span>&#8221; gives &#8220;<span class="quote">No PPD file for printer...</span>&#8221; 
 	message while PPD file is present.  What might the problem be?
 	</p><p>
@@ -2977,10 +2977,10 @@ cupsomatic</a> show how CUPS handles print jobs.
 	<strong class="userinput"><code>cupsaddsmb -H sambaserver -h cupsserver -v printername</code></strong>.
 	</p><p>Is your <em class="parameter"><code>TempDir</code></em> directive in
 	<code class="filename">cupsd.conf</code> set to a valid value, and is it writable?
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649005"></a>Client Can't Connect to Samba Printer</h3></div></div></div><p>Use <code class="literal">smbstatus</code> to check which user
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649144"></a>Client Can't Connect to Samba Printer</h3></div></div></div><p>Use <code class="literal">smbstatus</code> to check which user
 	you are from Samba's point of view. Do you have the privileges to
 	write into the <em class="parameter"><code>[print$]</code></em>
-	share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649029"></a>New Account Reconnection from Windows 200x/XP Troubles</h3></div></div></div><p>
+	share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649169"></a>New Account Reconnection from Windows 200x/XP Troubles</h3></div></div></div><p>
 Once you are connected as the wrong user (for example, as <code class="constant">nobody</code>, which often occurs if
 you have <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest = bad user</a>), Windows Explorer will not accept an
 attempt to connect again as a different user. There will not be any bytes transferred on the wire to Samba,
@@ -2995,44 +2995,44 @@ user. The best method is to use a DOS terminal window and <span class="emphasis"
 connected under a different account. Now open the <span class="guilabel">Printers</span> folder (on the Samba server in
 the <span class="guilabel">Network Neighborhood</span>), right-click on the printer in question, and select
 <span class="guibutton">Connect....</span>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649120"></a>Avoid Being Connected to the Samba Server as the Wrong User</h3></div></div></div><p>
-<a class="indexterm" name="id2649129"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649260"></a>Avoid Being Connected to the Samba Server as the Wrong User</h3></div></div></div><p>
+<a class="indexterm" name="id2649268"></a>
 You see per <code class="literal">smbstatus</code> that you are connected as user nobody, but you want to be root or
 printer admin. This is probably due to <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest = bad user</a>, which
 silently connected you under the guest account when you gave (maybe by accident) an incorrect username. Remove
 <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest</a> if you want to prevent this.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649172"></a>Upgrading to CUPS Drivers from Adobe Drivers</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649311"></a>Upgrading to CUPS Drivers from Adobe Drivers</h3></div></div></div><p>
 This information came from a mailing list posting regarding problems experienced when
 upgrading from Adobe drivers to CUPS drivers on Microsoft Windows NT/200x/XP clients.
 </p><p>First delete all old Adobe-using printers. Then delete all old Adobe drivers. (On Windows 200x/XP, right-click in
 the background of <span class="guilabel">Printers</span> folder, select <span class="guimenuitem">Server Properties...</span>, select
-tab <span class="guilabel">Drivers</span>, and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649209"></a>Can't Use &#8220;<span class="quote">cupsaddsmb</span>&#8221; on Samba Server, Which Is a PDC</h3></div></div></div><p>Do you use the &#8220;<span class="quote">naked</span>&#8221; root user name? Try to do it
+tab <span class="guilabel">Drivers</span>, and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649349"></a>Can't Use &#8220;<span class="quote">cupsaddsmb</span>&#8221; on Samba Server, Which Is a PDC</h3></div></div></div><p>Do you use the &#8220;<span class="quote">naked</span>&#8221; root user name? Try to do it
 this way: <strong class="userinput"><code>cupsaddsmb -U <em class="replaceable"><code>DOMAINNAME</code></em>\\root -v
 <em class="replaceable"><code>printername</code></em></code></strong>&gt; (note the two backslashes: the first one is
-required to &#8220;<span class="quote">escape</span>&#8221; the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649245"></a>Deleted Windows 200x Printer Driver Is Still Shown</h3></div></div></div><p>Deleting a printer on the client will not delete the
+required to &#8220;<span class="quote">escape</span>&#8221; the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649384"></a>Deleted Windows 200x Printer Driver Is Still Shown</h3></div></div></div><p>Deleting a printer on the client will not delete the
 driver too (to verify, right-click on the white background of the
 <span class="guilabel">Printers</span> folder, select <span class="guimenuitem">Server Properties</span> and click on the
 <span class="guilabel">Drivers</span> tab). These same old drivers will be re-used when you try to
 install a printer with the same name. If you want to update to a new
 driver, delete the old ones first. Deletion is only possible if no
-other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649280"></a>Windows 200x/XP Local Security Policies</h3></div></div></div><a class="indexterm" name="id2649286"></a><a class="indexterm" name="id2649293"></a><p>Local security policies may not allow the installation of unsigned drivers  &#8220;<span class="quote">local
-security policies</span>&#8221; may not allow the installation of printer drivers at all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649313"></a>Administrator Cannot Install Printers for All Local Users</h3></div></div></div><p>
-<a class="indexterm" name="id2649321"></a>
-<a class="indexterm" name="id2649328"></a>
+other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649419"></a>Windows 200x/XP Local Security Policies</h3></div></div></div><a class="indexterm" name="id2649425"></a><a class="indexterm" name="id2649432"></a><p>Local security policies may not allow the installation of unsigned drivers  &#8220;<span class="quote">local
+security policies</span>&#8221; may not allow the installation of printer drivers at all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649452"></a>Administrator Cannot Install Printers for All Local Users</h3></div></div></div><p>
+<a class="indexterm" name="id2649461"></a>
+<a class="indexterm" name="id2649468"></a>
 Windows XP handles SMB printers on a &#8220;<span class="quote">per-user</span>&#8221; basis.
 This means every user needs to install the printer himself or herself. To have a printer available for
 everybody, you might want to use the built-in IPP client capabilities of Win XP. Add a printer with the print
 path of <em class="parameter"><code>http://cupsserver:631/printers/printername</code></em>.  We're still looking into this one.
 Maybe a logon script could automatically install printers for all users.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649354"></a>Print Change, Notify Functions on NT Clients</h3></div></div></div><p>For print change, notify functions on NT++ clients.  These need to run the <code class="literal">Server</code>
-service first (renamed to <code class="literal">File &amp; Print Sharing for MS Networks</code> in XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649379"></a>Windows XP SP1</h3></div></div></div><p>Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649493"></a>Print Change, Notify Functions on NT Clients</h3></div></div></div><p>For print change, notify functions on NT++ clients.  These need to run the <code class="literal">Server</code>
+service first (renamed to <code class="literal">File &amp; Print Sharing for MS Networks</code> in XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649519"></a>Windows XP SP1</h3></div></div></div><p>Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to
 &#8220;<span class="quote">Administrator</span>&#8221; or &#8220;<span class="quote">Power User</span>&#8221; groups of users). In Group Policy Object Editor, go
 to <span class="guimenu">User Configuration -&gt; Administrative Templates -&gt; Control Panel -&gt; Printers</span>. The policy
 is automatically set to <code class="constant">Enabled</code> and the <code class="constant">Users can only Point and Print to
 machines in their Forest</code> . You probably need to change it to <code class="constant">Disabled</code> or
 <code class="constant">Users can only Point and Print to these servers</code> to make driver downloads from Samba
 possible.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649426"></a>Print Options for All Users Can't Be Set on Windows 200x/XP</h3></div></div></div><p>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649565"></a>Print Options for All Users Can't Be Set on Windows 200x/XP</h3></div></div></div><p>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three
 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, yet only one of them does what you intend. You need to be Administrator or
 Print Administrator to do this for all users. Here is how I do it on XP:
@@ -3065,33 +3065,33 @@ all clients to get the same defaults, you need to conduct these steps <span clas
 (<a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> in <code class="filename">smb.conf</code>) <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>).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649709"></a>Most Common Blunders in Driver Settings on Windows Clients</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649848"></a>Most Common Blunders in Driver Settings on Windows Clients</h3></div></div></div><p>
 Don't use <em class="parameter"><code>Optimize for Speed</code></em>, but use <em class="parameter"><code>Optimize for Portability</code></em>
 instead (Adobe PS Driver). Don't use <em class="parameter"><code>Page Independence: No</code></em>. Always settle with
 <em class="parameter"><code>Page Independence: Yes</code></em> (Microsoft PS Driver and CUPS PS Driver for Windows NT/200x/XP).
 If there are problems with fonts, use <em class="parameter"><code>Download as Softfont into printer</code></em> (Adobe PS
 Driver). For <span class="guilabel">TrueType Download Options</span> choose <code class="constant">Outline</code>. Use
 PostScript Level 2 if you are having trouble with a non-PS printer and if there is a choice.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649764"></a><code class="literal">cupsaddsmb</code> Does Not Work with Newly Installed Printer</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649904"></a><code class="literal">cupsaddsmb</code> Does Not Work with Newly Installed Printer</h3></div></div></div><p>
 Symptom: The last command of <code class="literal">cupsaddsmb</code> does not complete successfully. If the <code class="literal">cmd
 = setdriver printername printername</code> result was NT_STATUS_UNSUCCESSFUL, then possibly the printer was
 not yet recognized by Samba. Did it show up in Network Neighborhood? Did it show up in <code class="literal">rpcclient
 hostname -c `enumprinters'</code>? Restart smbd (or send a <code class="literal">kill -HUP</code> to all processes
 listed by <code class="literal">smbstatus</code>, and try again.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649814"></a>Permissions on <code class="filename">/var/spool/samba/</code> Get Reset After Each Reboot</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649954"></a>Permissions on <code class="filename">/var/spool/samba/</code> Get Reset After Each Reboot</h3></div></div></div><p>
 Have you ever by accident set the CUPS spool directory to the same location (<em class="parameter"><code>RequestRoot
 /var/spool/samba/</code></em> in <code class="filename">cupsd.conf</code> or the other way round:
 <code class="filename">/var/spool/cups/</code> is set as <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a>&gt; in the <em class="parameter"><code>[printers]</code></em> section)? These <em class="parameter"><code>must</code></em> be different. Set <em class="parameter"><code>RequestRoot
 /var/spool/cups/</code></em> in <code class="filename">cupsd.conf</code> and <a class="link" href="smb.conf.5.html#PATH" target="_top">path = 
 /var/spool/samba</a> in the <em class="parameter"><code>[printers]</code></em> section of <code class="filename">smb.conf</code>. Otherwise,
 cupsd will sanitize permissions to its spool directory with each restart and printing will not work reliably.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649912"></a>Print Queue Called &#8220;<span class="quote">lp</span>&#8221; Mishandles Print Jobs</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650052"></a>Print Queue Called &#8220;<span class="quote">lp</span>&#8221; Mishandles Print Jobs</h3></div></div></div><p>
 In this case a print queue called &#8220;<span class="quote">lp</span>&#8221; intermittently swallows jobs and
 spits out completely different ones from what was sent.
 </p><p>
-<a class="indexterm" name="id2649933"></a>
-<a class="indexterm" name="id2649939"></a>
-<a class="indexterm" name="id2649946"></a>
+<a class="indexterm" name="id2650072"></a>
+<a class="indexterm" name="id2650079"></a>
+<a class="indexterm" name="id2650086"></a>
 It is a bad idea to name any printer &#8220;<span class="quote">lp</span>&#8221;. This is the traditional UNIX name for the default
 printer. CUPS may be set up to do an automatic creation of Implicit Classes. This means, to group all printers
 with the same name to a pool of devices and load-balance the jobs across them in a round-robin fashion.
@@ -3100,13 +3100,13 @@ jobs and send your own to his or her device unwittingly. To have tight control o
 <em class="parameter"><code>BrowseShortNames No</code></em>. It will present any printer as
 <em class="replaceable"><code>printername@cupshost</code></em>, which gives you better control over what may happen in a
 large networked environment.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649981"></a>Location of Adobe PostScript Driver Files for &#8220;<span class="quote">cupsaddsmb</span>&#8221;</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650121"></a>Location of Adobe PostScript Driver Files for &#8220;<span class="quote">cupsaddsmb</span>&#8221;</h3></div></div></div><p>
 Use <code class="literal">smbclient</code> to connect to any Windows box with a shared PostScript printer:
 <code class="literal">smbclient //windowsbox/print\$ -U guest</code>. You can navigate to the
 <code class="filename">W32X86/2</code> subdir to <code class="literal">mget ADOBE*</code> and other files or to
 <code class="filename">WIN40/0</code> to do the same.  Another option is to download the <code class="filename">*.exe</code>
 packaged files from the Adobe Web site.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650035"></a>Overview of the CUPS Printing Processes</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650175"></a>Overview of the CUPS Printing Processes</h2></div></div></div><p>
 A complete overview of the CUPS printing processes can be found in <a class="link" href="CUPS-printing.html#a_small" title="Figure�22.19.�CUPS Printing Overview.">the CUPS
 Printing Overview diagram</a>.
-</p><div class="figure"><a name="a_small"></a><p class="title"><b>Figure�22.19.�CUPS Printing Overview.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/a_small.png" width="243" alt="CUPS Printing Overview."></div></div></div><br class="figure-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2639328" href="#id2639328" class="para">6</a>] </sup>See also <a class="ulink" href="http://www.cups.org/cups-help.html" target="_top">http://www.cups.org/cups-help.html</a></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�21.�Classical Printing Support�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�23.�Stackable VFS modules</td></tr></table></div></body></html>
+</p><div class="figure"><a name="a_small"></a><p class="title"><b>Figure�22.19.�CUPS Printing Overview.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/a_small.png" width="243" alt="CUPS Printing Overview."></div></div></div><br class="figure-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2639418" href="#id2639418" class="para">6</a>] </sup>See also <a class="ulink" href="http://www.cups.org/cups-help.html" target="_top">http://www.cups.org/cups-help.html</a></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�21.�Classical Printing Support�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�23.�Stackable VFS modules</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html b/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html
index f4000bc08a..fc3516c827 100644
--- a/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html
+++ b/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="next" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="optional.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ChangeNotes"></a>Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578591">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578602">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578661">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578973">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579095">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="next" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="optional.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ChangeNotes"></a>Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578577">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578588">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578647">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578959">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579081">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></div><p>
 Please read this chapter carefully before update or upgrading Samba.  You should expect to find only critical
 or very important information here. Comprehensive change notes and guidance information can be found in the
 section <a class="link" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba">Updating and Upgrading Samba</a>.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578591"></a>Important Samba-3.2.x Change Notes</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578577"></a>Important Samba-3.2.x Change Notes</h2></div></div></div><p>
 !!!!!!!!!!!!Add all critical update notes here!!!!!!!!!!!!!
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578602"></a>Important Samba-3.0.x Change Notes</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578588"></a>Important Samba-3.0.x Change Notes</h2></div></div></div><p>
 These following notes pertain in particular to Samba 3.0.23 through Samba 3.0.25c (or more recent 3.0.25
 update).  Samba is a fluid and ever changing project. Changes throughout the 3.0.x series release are
 documented in this documention - See <a class="link" href="upgrading-to-3.0.html#oldupdatenotes" title="Upgrading from Samba-2.x to Samba-3.0.25">Upgrading from Samba-2.x to Samba-3.0.25</a>.
@@ -21,35 +21,35 @@ such time as the body of this HOWTO is restructured or modified.
 </p><p>
 This chapter is new to the release of the HOWTO for Samba 3.0.23. It includes much of the notes provided
 in the <code class="filename">WHATSNEW.txt</code> file that is included with the Samba source code release tarball.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2578661"></a>User and Group Changes</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2578647"></a>User and Group Changes</h3></div></div></div><p>
 The change documented here affects unmapped user and group accounts only.
 </p><p>
+<a class="indexterm" name="id2578660"></a>
+<a class="indexterm" name="id2578667"></a>
 <a class="indexterm" name="id2578674"></a>
-<a class="indexterm" name="id2578681"></a>
-<a class="indexterm" name="id2578688"></a>
-<a class="indexterm" name="id2578697"></a>
-<a class="indexterm" name="id2578706"></a>
+<a class="indexterm" name="id2578683"></a>
+<a class="indexterm" name="id2578692"></a>
 The user and group internal management routines have been rewritten to prevent overlaps of
 assigned Relative Identifiers (RIDs).  In the past the has been a potential problem when
 either manually mapping Unix groups with the <code class="literal">net groupmap</code> command or
 when migrating a Windows domain to a Samba domain by executing:
 <code class="literal">net rpc vampire</code>.
 </p><p>
-<a class="indexterm" name="id2578737"></a>
-<a class="indexterm" name="id2578744"></a>
-<a class="indexterm" name="id2578750"></a>
-<a class="indexterm" name="id2578757"></a>
+<a class="indexterm" name="id2578723"></a>
+<a class="indexterm" name="id2578730"></a>
+<a class="indexterm" name="id2578736"></a>
+<a class="indexterm" name="id2578743"></a>
 Unmapped users are now assigned a SID in the <code class="literal">S-1-22-1</code> domain and unmapped
 groups are assigned a SID in the <code class="literal">S-1-22-2</code> domain.  Previously they were
 assigned a RID within the SAM on the Samba server.  For a domain controller this would have been under the
 authority of the domain SID where as on a member server or standalone server, this would have
 been under the authority of the local SAM (see the man page for <code class="literal">net getlocalsid</code>).
 </p><p>
-<a class="indexterm" name="id2578794"></a>
+<a class="indexterm" name="id2578780"></a>
+<a class="indexterm" name="id2578786"></a>
+<a class="indexterm" name="id2578793"></a>
 <a class="indexterm" name="id2578800"></a>
 <a class="indexterm" name="id2578807"></a>
-<a class="indexterm" name="id2578814"></a>
-<a class="indexterm" name="id2578821"></a>
 The result is that any unmapped users or groups on an upgraded Samba domain controller may
 be assigned a new SID.  Because the SID rather than a name is stored in Windows security
 descriptors, this can cause a user to no longer have access to a resource for example if a
@@ -59,19 +59,19 @@ GID and not the SID for authorization checks.
 </p><p>
 An example helps to illustrate the change:
 </p><p>
+<a class="indexterm" name="id2578829"></a>
+<a class="indexterm" name="id2578836"></a>
 <a class="indexterm" name="id2578843"></a>
-<a class="indexterm" name="id2578850"></a>
-<a class="indexterm" name="id2578857"></a>
-<a class="indexterm" name="id2578863"></a>
+<a class="indexterm" name="id2578849"></a>
 Assume that a group named <span class="emphasis"><em>developers</em></span> exists with a UNIX GID of 782. In this
 case this group does not exist in Samba's group mapping table. It would be perfectly normal for
 this group to be appear in an ACL editor.  Prior to Samba-3.0.23, the group SID might appear as
 <code class="literal">S-1-5-21-647511796-4126122067-3123570092-2565</code>.
 </p><p>
+<a class="indexterm" name="id2578873"></a>
+<a class="indexterm" name="id2578880"></a>
 <a class="indexterm" name="id2578887"></a>
-<a class="indexterm" name="id2578894"></a>
-<a class="indexterm" name="id2578901"></a>
-<a class="indexterm" name="id2578907"></a>
+<a class="indexterm" name="id2578893"></a>
 With the release of Samba-3.0.23, the group SID would be reported as <code class="literal">S-1-22-2-782</code>.  Any
 security descriptors associated with files stored on a Windows NTFS disk partition will not allow access based
 on the group permissions if the user was not a member of the
@@ -79,13 +79,13 @@ on the group permissions if the user was not a member of the
 <code class="literal">S-1-22-2-782</code> and not reported in a user's token, Windows would fail the authorization check
 even though both SIDs in some respect refer to the same UNIX group.
 </p><p>
-<a class="indexterm" name="id2578944"></a>
-<a class="indexterm" name="id2578950"></a>
+<a class="indexterm" name="id2578930"></a>
+<a class="indexterm" name="id2578936"></a>
 The workaround for versions of Samba prior to 3.0.23, is to create a manual domain group mapping
 entry for the group <span class="emphasis"><em>developers</em></span> to point at the
 <code class="literal">S-1-5-21-647511796-4126122067-3123570092-2565</code> SID. With the release of Samba-3.0.23 this
 workaround is no longer needed.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2578973"></a>Essential Group Mappings</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2578959"></a>Essential Group Mappings</h3></div></div></div><p>
 Samba 3.0.x series  releases before 3.0.23 automatically created group mappings for the essential Windows
 domain groups <code class="literal">Domain Admins, Domain Users, Domain Guests</code>. Commencing with Samba 3.0.23
 these mappings need to be created by the Samba administrator. Failure to do this may result in a failure to
@@ -102,39 +102,39 @@ domguests</code> respectively.
 </p><p>
 For further information regarding group mappings see <a class="link" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX">Group Mapping: MS Windows
 and UNIX</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579095"></a>Passdb Changes</h3></div></div></div><p>
-<a class="indexterm" name="id2579102"></a>
-<a class="indexterm" name="id2579109"></a>
-<a class="indexterm" name="id2579115"></a>
-<a class="indexterm" name="id2579122"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579081"></a>Passdb Changes</h3></div></div></div><p>
+<a class="indexterm" name="id2579088"></a>
+<a class="indexterm" name="id2579095"></a>
+<a class="indexterm" name="id2579101"></a>
+<a class="indexterm" name="id2579108"></a>
 The <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> parameter no longer accepts multiple passdb backends in a
 chained configuration.  Also be aware that the SQL and XML based passdb modules have been
 removed in the Samba-3.0.23 release.  More information regarding external support for a SQL
 passdb module can be found on the  <a class="ulink" href="http://pdbsql.sourceforge.net/" target="_top">pdbsql</a> web site.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579155"></a>Group Mapping Changes in Samba-3.0.23</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579141"></a>Group Mapping Changes in Samba-3.0.23</h3></div></div></div><p>
+<a class="indexterm" name="id2579148"></a>
+<a class="indexterm" name="id2579155"></a>
 <a class="indexterm" name="id2579162"></a>
 <a class="indexterm" name="id2579169"></a>
 <a class="indexterm" name="id2579176"></a>
 <a class="indexterm" name="id2579183"></a>
 <a class="indexterm" name="id2579190"></a>
-<a class="indexterm" name="id2579197"></a>
-<a class="indexterm" name="id2579204"></a>
+<a class="indexterm" name="id2579196"></a>
+<a class="indexterm" name="id2579203"></a>
 <a class="indexterm" name="id2579210"></a>
-<a class="indexterm" name="id2579217"></a>
-<a class="indexterm" name="id2579224"></a>
-<a class="indexterm" name="id2579230"></a>
+<a class="indexterm" name="id2579216"></a>
 The default mapping entries for groups such as <code class="literal">Domain Admins</code> are no longer
 created when using an <code class="literal">smbpasswd</code> file or a <code class="literal">tdbsam</code> passdb
 backend.  This means that it is necessary to explicitly execute the <code class="literal">net groupmap add</code>
 to create group mappings, rather than use the <code class="literal">net groupmap modify</code> method to create the
 Windows group SID to UNIX GID mappings.  This change has no effect on winbindd's IDMAP functionality
 for domain groups.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579275"></a>LDAP Changes in Samba-3.0.23</h3></div></div></div><p>
-<a class="indexterm" name="id2579284"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2579261"></a>LDAP Changes in Samba-3.0.23</h3></div></div></div><p>
+<a class="indexterm" name="id2579270"></a>
+<a class="indexterm" name="id2579276"></a>
+<a class="indexterm" name="id2579283"></a>
 <a class="indexterm" name="id2579290"></a>
 <a class="indexterm" name="id2579297"></a>
-<a class="indexterm" name="id2579304"></a>
-<a class="indexterm" name="id2579311"></a>
 There has been a minor update the Samba LDAP schema file. A substring matching rule has been
 added to the <code class="literal">sambaSID</code> attribute definition.  For OpenLDAP servers, this
 will require the addition of <code class="literal">index sambaSID sub</code> to the
diff --git a/docs/htmldocs/Samba3-HOWTO/ClientConfig.html b/docs/htmldocs/Samba3-HOWTO/ClientConfig.html
index 3cb3163abb..a40b6bdd2b 100644
--- a/docs/htmldocs/Samba3-HOWTO/ClientConfig.html
+++ b/docs/htmldocs/Samba3-HOWTO/ClientConfig.html
@@ -1,20 +1,20 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�MS Windows Network Configuration Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="StandAloneServer.html" title="Chapter�7.�Standalone Servers"><link rel="next" href="optional.html" title="Part�III.�Advanced Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�MS Windows Network Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="optional.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�8.�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="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575508">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575568">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575612">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578353">Common Errors</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575508"></a>Features and Benefits</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�MS Windows Network Configuration Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="StandAloneServer.html" title="Chapter�7.�Standalone Servers"><link rel="next" href="optional.html" title="Part�III.�Advanced Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�MS Windows Network Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="optional.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�8.�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="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575494">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575554">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575598">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578339">Common Errors</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575494"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2575502"></a>
+<a class="indexterm" name="id2575509"></a>
 <a class="indexterm" name="id2575516"></a>
-<a class="indexterm" name="id2575523"></a>
-<a class="indexterm" name="id2575530"></a>
 Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
 correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
 to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
 servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
 </p><p>
-<a class="indexterm" name="id2575547"></a>
-<a class="indexterm" name="id2575555"></a>
+<a class="indexterm" name="id2575533"></a>
+<a class="indexterm" name="id2575541"></a>
 The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
 critical aspects of such configuration. An experienced network administrator will not be interested in the
 details of this chapter.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575568"></a>Technical Details</h2></div></div></div><p>
-<a class="indexterm" name="id2575576"></a>
-<a class="indexterm" name="id2575583"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575554"></a>Technical Details</h2></div></div></div><p>
+<a class="indexterm" name="id2575562"></a>
+<a class="indexterm" name="id2575569"></a>
 This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
 that are in common use today. These are:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -23,27 +23,27 @@ that are in common use today. These are:
 	Windows 2000 Professional
 	</p></li><li><p>
 	Windows Millennium edition (Me)
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2575612"></a>TCP/IP Configuration</h3></div></div></div><p>
-<a class="indexterm" name="id2575620"></a>
-<a class="indexterm" name="id2575627"></a>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2575598"></a>TCP/IP Configuration</h3></div></div></div><p>
+<a class="indexterm" name="id2575606"></a>
+<a class="indexterm" name="id2575613"></a>
 	The builder of a house must ensure that all construction takes place on a firm foundation.
 	The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
 	will plague all network users until they are resolved. 
 	</p><p>
-<a class="indexterm" name="id2575642"></a>
-<a class="indexterm" name="id2575649"></a>
+<a class="indexterm" name="id2575628"></a>
+<a class="indexterm" name="id2575635"></a>
 	MS Windows workstations and servers can be configured either with fixed
 	IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
 	and make only passing reference to those situations where fixed IP configuration
 	settings can be effected.
 	</p><p>
-<a class="indexterm" name="id2575663"></a>
-<a class="indexterm" name="id2575670"></a>
+<a class="indexterm" name="id2575649"></a>
+<a class="indexterm" name="id2575656"></a>
 	It is possible to use shortcuts or abbreviated keystrokes to arrive at a
 	particular configuration screen. The decision was made to base all examples in this
 	chapter on use of the <span class="guibutton">Start</span> button.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2575687"></a>MS Windows XP Professional</h4></div></div></div><p>
-<a class="indexterm" name="id2575695"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2575673"></a>MS Windows XP Professional</h4></div></div></div><p>
+<a class="indexterm" name="id2575681"></a>
 		There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
 		</p><p>
 		Click <span class="guimenu">Start -&gt; Control Panel -&gt; Network Connections</span>.
@@ -51,48 +51,48 @@ that are in common use today. These are:
 		<span class="emphasis"><em>Alternately,</em></span> click <span class="guimenu">Start -&gt;</span>, and right-click <span class="guimenu">My Network Places</span>
 		then select <span class="guimenuitem">Properties</span>.
 		</p><p>
-<a class="indexterm" name="id2575744"></a>
+<a class="indexterm" name="id2575730"></a>
 		The following procedure steps through the Windows XP Professional TCP/IP configuration process:
 		</p><div class="procedure"><ol type="1"><li><p>
+<a class="indexterm" name="id2575747"></a>
+<a class="indexterm" name="id2575754"></a>
 <a class="indexterm" name="id2575761"></a>
-<a class="indexterm" name="id2575768"></a>
-<a class="indexterm" name="id2575775"></a>
 			On some installations the interface will be called <span class="guimenu">Local Area Connection</span> and
 			on others it will be called <span class="guimenu">Network Bridge</span>. On our system it is called <span class="guimenu">Network Bridge</span>.
 			Right-click on <span class="guimenu">Network Bridge -&gt; Properties</span>. See <a class="link" href="ClientConfig.html#WXPP002" title="Figure�8.1.�Network Bridge Configuration.">&#8220;Network Bridge Configuration.&#8221;</a>.
 			</p><div class="figure"><a name="WXPP002"></a><p class="title"><b>Figure�8.1.�Network Bridge Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WXPP002.png" alt="Network Bridge Configuration."></div></div></div><p><br class="figure-break">
 			</p></li><li><p>
-<a class="indexterm" name="id2575861"></a>
-<a class="indexterm" name="id2575868"></a>
+<a class="indexterm" name="id2575847"></a>
+<a class="indexterm" name="id2575854"></a>
 			The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
 			In <span class="guimenuitem">This connection uses the following items:</span> box,
 			click on <span class="guimenu">Internet Protocol (TCP/IP)</span>, then click on <span class="guibutton">Properties</span>.
 			</p><p>
-<a class="indexterm" name="id2575900"></a>
-<a class="indexterm" name="id2575907"></a>
+<a class="indexterm" name="id2575886"></a>
+<a class="indexterm" name="id2575893"></a>
 			The default setting is DHCP-enabled operation
 			(i.e., &#8220;<span class="quote">Obtain an IP address automatically</span>&#8221;). See <a class="link" href="ClientConfig.html#WXPP003" title="Figure�8.2.�Internet Protocol (TCP/IP) Properties.">&#8220;Internet Protocol (TCP/IP) Properties.&#8221;</a>.
 			</p><div class="figure"><a name="WXPP003"></a><p class="title"><b>Figure�8.2.�Internet Protocol (TCP/IP) Properties.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WXPP003.png" alt="Internet Protocol (TCP/IP) Properties."></div></div></div><p><br class="figure-break">
 			</p><p>
-<a class="indexterm" name="id2575970"></a>
+<a class="indexterm" name="id2575956"></a>
+<a class="indexterm" name="id2575962"></a>
+<a class="indexterm" name="id2575969"></a>
 <a class="indexterm" name="id2575976"></a>
-<a class="indexterm" name="id2575983"></a>
-<a class="indexterm" name="id2575990"></a>
 			Many network administrators will want to use DHCP to configure all client TCP/IP
 			protocol stack settings. (For information on how to configure the ISC DHCP server
 			for Windows client support see <a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">the DNS and DHCP Configuration Guide</a>,
-			<a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>).
+			<a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>.
 			</p><p>
+<a class="indexterm" name="id2576005"></a>
+<a class="indexterm" name="id2576012"></a>
 <a class="indexterm" name="id2576019"></a>
-<a class="indexterm" name="id2576026"></a>
-<a class="indexterm" name="id2576033"></a>
 			If it is necessary to provide a fixed IP address, click on &#8220;<span class="quote">Use the following IP address</span>&#8221; and enter the
 			IP Address, the subnet mask, and the default gateway address in the boxes provided.
 			</p></li><li><p>
+<a class="indexterm" name="id2576039"></a>
+<a class="indexterm" name="id2576046"></a>
 <a class="indexterm" name="id2576053"></a>
 <a class="indexterm" name="id2576060"></a>
-<a class="indexterm" name="id2576067"></a>
-<a class="indexterm" name="id2576074"></a>
 			Click the <span class="guibutton">Advanced</span> button to proceed with TCP/IP configuration.
 			This opens a panel in which it is possible to create additional IP addresses for this interface.
 			The technical name for the additional addresses is <span class="emphasis"><em>IP aliases</em></span>, and additionally this
@@ -100,28 +100,28 @@ that are in common use today. These are:
 			necessary to create additional settings. See <a class="link" href="ClientConfig.html#WXPP005" title="Figure�8.3.�Advanced Network Settings">&#8220;Advanced Network Settings&#8221;</a> to see the appearance of this panel.
 			</p><div class="figure"><a name="WXPP005"></a><p class="title"><b>Figure�8.3.�Advanced Network Settings</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WXPP005.png" alt="Advanced Network Settings"></div></div></div><p><br class="figure-break">
 			</p><p>
-<a class="indexterm" name="id2576145"></a>
-<a class="indexterm" name="id2576151"></a>
-<a class="indexterm" name="id2576158"></a>
+<a class="indexterm" name="id2576131"></a>
+<a class="indexterm" name="id2576137"></a>
+<a class="indexterm" name="id2576144"></a>
 			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
 			</p></li><li><p>
-<a class="indexterm" name="id2576173"></a>
-<a class="indexterm" name="id2576180"></a>
+<a class="indexterm" name="id2576159"></a>
+<a class="indexterm" name="id2576166"></a>
 			Click the <span class="guimenu">DNS</span> tab to add DNS server settings. 
 			The example system uses manually configured DNS settings. When finished making changes, click the
 			<span class="guibutton">OK</span> to commit the settings. See <a class="link" href="ClientConfig.html#WXPP014" title="Figure�8.4.�DNS Configuration.">&#8220;DNS Configuration.&#8221;</a>.
 			</p><div class="figure"><a name="WXPP014"></a><p class="title"><b>Figure�8.4.�DNS Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WXPP014.png" alt="DNS Configuration."></div></div></div><p><br class="figure-break">
 			</p></li><li><p>
-<a class="indexterm" name="id2576255"></a>
-<a class="indexterm" name="id2576262"></a>
+<a class="indexterm" name="id2576241"></a>
+<a class="indexterm" name="id2576248"></a>
 			Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries. 
 			This step demonstrates an example system that uses manually configured WINS settings. 
 			When finished making changes, click <span class="guibutton">OK</span> to commit
                         the settings. See <a class="link" href="ClientConfig.html#WXPP009" title="Figure�8.5.�WINS Configuration">&#8220;WINS Configuration&#8221;</a>.
 			</p><div class="figure"><a name="WXPP009"></a><p class="title"><b>Figure�8.5.�WINS Configuration</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WXPP009.png" alt="WINS Configuration"></div></div></div><p><br class="figure-break">
-			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576331"></a>MS Windows 2000</h4></div></div></div><p>
-<a class="indexterm" name="id2576339"></a>
-<a class="indexterm" name="id2576346"></a>
+			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576317"></a>MS Windows 2000</h4></div></div></div><p>
+<a class="indexterm" name="id2576325"></a>
+<a class="indexterm" name="id2576332"></a>
 		There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
 		</p><p>
 		Click <span class="guimenu">Start -&gt; Control Panel -&gt; Network and Dial-up Connections</span>.
@@ -129,33 +129,33 @@ that are in common use today. These are:
 		<span class="emphasis"><em>Alternatively,</em></span> click <span class="guimenu">Start</span>, then right-click <span class="guimenu">My Network Places</span>, and
 		select <span class="guimenuitem">Properties</span>.
 		</p><p>
-<a class="indexterm" name="id2576394"></a>
+<a class="indexterm" name="id2576380"></a>
 		The following procedure steps through the Windows XP Professional TCP/IP configuration process:
 		</p><div class="procedure"><ol type="1"><li><p>
 			Right-click on <span class="guimenu">Local Area Connection</span>, then click
 			<span class="guimenuitem">Properties</span>. See <a class="link" href="ClientConfig.html#w2kp001" title="Figure�8.6.�Local Area Connection Properties.">&#8220;Local Area Connection Properties.&#8221;</a>.
 			</p><div class="figure"><a name="w2kp001"></a><p class="title"><b>Figure�8.6.�Local Area Connection Properties.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/w2kp001.png" alt="Local Area Connection Properties."></div></div></div><p><br class="figure-break">
 			</p></li><li><p>
-<a class="indexterm" name="id2576475"></a>
-<a class="indexterm" name="id2576482"></a>
+<a class="indexterm" name="id2576461"></a>
+<a class="indexterm" name="id2576468"></a>
 			The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
 			<span class="guimenu">Internet Protocol (TCP/IP)</span> in the <span class="guimenuitem">Components checked are used by this
 			connection:</span> box, then click the <span class="guibutton">Properties</span> button.
 			</p></li><li><p>
-<a class="indexterm" name="id2576517"></a>
-<a class="indexterm" name="id2576524"></a>
+<a class="indexterm" name="id2576503"></a>
+<a class="indexterm" name="id2576510"></a>
 			The default setting is DHCP-enabled operation
 			(i.e., &#8220;<span class="quote">Obtain an IP address automatically</span>&#8221;). See <a class="link" href="ClientConfig.html#w2kp002" title="Figure�8.7.�Internet Protocol (TCP/IP) Properties.">&#8220;Internet Protocol (TCP/IP) Properties.&#8221;</a>.
 			</p><div class="figure"><a name="w2kp002"></a><p class="title"><b>Figure�8.7.�Internet Protocol (TCP/IP) Properties.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/w2kp002.png" alt="Internet Protocol (TCP/IP) Properties."></div></div></div><p><br class="figure-break">
 			</p><p>
-<a class="indexterm" name="id2576583"></a>
-<a class="indexterm" name="id2576590"></a>
+<a class="indexterm" name="id2576569"></a>
+<a class="indexterm" name="id2576576"></a>
 			Many network administrators will want to use DHCP to configure all client TCP/IP
 			protocol stack settings. (For information on how to configure the ISC DHCP server
-			for Windows client support, see, <a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">&#8220;DHCP Server&#8221;</a>).
+			for Windows client support, see, <a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">&#8220;DHCP Server&#8221;</a>.
 			</p><p>
-<a class="indexterm" name="id2576609"></a>
-<a class="indexterm" name="id2576616"></a>
+<a class="indexterm" name="id2576595"></a>
+<a class="indexterm" name="id2576602"></a>
 			If it is necessary to provide a fixed IP address, click on &#8220;<span class="quote">Use the following IP address</span>&#8221; and enter the
 			IP Address, the subnet mask, and the default gateway address in the boxes provided.
 			For this example we are assuming that all network clients will be configured using DHCP.
@@ -164,92 +164,92 @@ that are in common use today. These are:
 			Refer to <a class="link" href="ClientConfig.html#w2kp003" title="Figure�8.8.�Advanced Network Settings.">&#8220;Advanced Network Settings.&#8221;</a>.
 			</p><div class="figure"><a name="w2kp003"></a><p class="title"><b>Figure�8.8.�Advanced Network Settings.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/w2kp003.png" alt="Advanced Network Settings."></div></div></div><p><br class="figure-break">
 			</p><p>
+<a class="indexterm" name="id2576678"></a>
+<a class="indexterm" name="id2576685"></a>
 <a class="indexterm" name="id2576692"></a>
-<a class="indexterm" name="id2576699"></a>
-<a class="indexterm" name="id2576706"></a>
 			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
 			</p></li><li><p>
-<a class="indexterm" name="id2576721"></a>
-<a class="indexterm" name="id2576728"></a>
+<a class="indexterm" name="id2576707"></a>
+<a class="indexterm" name="id2576714"></a>
 			Click the <span class="guimenu">DNS</span> tab to add DNS server settings. 
 			The example system uses manually configured DNS settings. When finished making changes,
 			click <span class="guibutton">OK</span> to commit the settings. See <a class="link" href="ClientConfig.html#w2kp004" title="Figure�8.9.�DNS Configuration.">&#8220;DNS Configuration.&#8221;</a>.
 			</p><div class="figure"><a name="w2kp004"></a><p class="title"><b>Figure�8.9.�DNS Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/w2kp004.png" alt="DNS Configuration."></div></div></div><p><br class="figure-break">
 			</p></li><li><p>
-<a class="indexterm" name="id2576800"></a>
-<a class="indexterm" name="id2576807"></a>
+<a class="indexterm" name="id2576786"></a>
+<a class="indexterm" name="id2576793"></a>
 			Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries. 
 			This step demonstrates an example system that uses manually configured WINS settings. 
 			When finished making changes, click <span class="guibutton">OK</span> to commit the settings.
 			See <a class="link" href="ClientConfig.html#w2kp005" title="Figure�8.10.�WINS Configuration.">&#8220;WINS Configuration.&#8221;</a>.
 			</p><div class="figure"><a name="w2kp005"></a><p class="title"><b>Figure�8.10.�WINS Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/w2kp005.png" alt="WINS Configuration."></div></div></div><p><br class="figure-break">
-			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576877"></a>MS Windows Me</h4></div></div></div><p>
+			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2576863"></a>MS Windows Me</h4></div></div></div><p>
+<a class="indexterm" name="id2576871"></a>
+<a class="indexterm" name="id2576878"></a>
 <a class="indexterm" name="id2576885"></a>
-<a class="indexterm" name="id2576892"></a>
-<a class="indexterm" name="id2576899"></a>
 		There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
 		</p><p>
 		Click <span class="guimenu">Start -&gt; Control Panel -&gt; Network Connections</span>.
 		</p><p>
-<a class="indexterm" name="id2576922"></a>
-<a class="indexterm" name="id2576929"></a>
+<a class="indexterm" name="id2576908"></a>
+<a class="indexterm" name="id2576915"></a>
 		<span class="emphasis"><em>Alternatively,</em></span> click on <span class="guimenu">Start -&gt;</span>, and right click on <span class="guimenu">My Network Places</span>
 		then select <span class="guimenuitem">Properties</span>.
 		</p><p>
-<a class="indexterm" name="id2576962"></a>
+<a class="indexterm" name="id2576948"></a>
 		The following procedure steps through the Windows Me TCP/IP configuration process:
 		</p><div class="procedure"><ol type="1"><li><p>
-<a class="indexterm" name="id2576979"></a>
+<a class="indexterm" name="id2576965"></a>
 			In the box labeled <span class="guimenuitem">The following network components are installed:</span>,
 			click on <span class="guimenu">Internet Protocol TCP/IP</span>, then click on the <span class="guibutton">Properties</span> button.
 			See <a class="link" href="ClientConfig.html#WME001" title="Figure�8.11.�The Windows Me Network Configuration Panel.">&#8220;The Windows Me Network Configuration Panel.&#8221;</a>.
 			</p><div class="figure"><a name="WME001"></a><p class="title"><b>Figure�8.11.�The Windows Me Network Configuration Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME001.png" alt="The Windows Me Network Configuration Panel."></div></div></div><p><br class="figure-break">
 			</p></li><li><p>
+<a class="indexterm" name="id2577046"></a>
+<a class="indexterm" name="id2577053"></a>
 <a class="indexterm" name="id2577060"></a>
-<a class="indexterm" name="id2577067"></a>
-<a class="indexterm" name="id2577074"></a>
 			Many network administrators will want to use DHCP to configure all client TCP/IP
 			protocol stack settings. (For information on how to configure the ISC DHCP server
 			for Windows client support see <a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">the DNS and DHCP Configuration Guide</a>,
-			<a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>). The default setting on Windows Me workstations is for DHCP-enabled operation
+			<a class="link" href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>. The default setting on Windows Me workstations is for DHCP-enabled operation
 			(i.e., <span class="guimenu">Obtain IP address automatically</span> is enabled). See <a class="link" href="ClientConfig.html#WME002" title="Figure�8.12.�IP Address.">&#8220;IP Address.&#8221;</a>.
 			</p><div class="figure"><a name="WME002"></a><p class="title"><b>Figure�8.12.�IP Address.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME002.png" alt="IP Address."></div></div></div><p><br class="figure-break">
 			</p><p>
+<a class="indexterm" name="id2577139"></a>
+<a class="indexterm" name="id2577146"></a>
 <a class="indexterm" name="id2577153"></a>
-<a class="indexterm" name="id2577160"></a>
-<a class="indexterm" name="id2577167"></a>
 			If it is necessary to provide a fixed IP address, click on <span class="guimenuitem">Specify an IP address</span> and enter the
 			IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
 			network clients will be configured using DHCP.
 			</p></li><li><p>
-<a class="indexterm" name="id2577190"></a>
-<a class="indexterm" name="id2577197"></a>
+<a class="indexterm" name="id2577176"></a>
+<a class="indexterm" name="id2577183"></a>
 			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
 			</p></li><li><p>
-<a class="indexterm" name="id2577212"></a>
+<a class="indexterm" name="id2577198"></a>
 			If necessary, click the <span class="guimenu">DNS Configuration</span> tab to add DNS server settings. 
 			Click the <span class="guibutton">WINS Configuration</span> tab to add WINS server settings. 
 			The <span class="guimenu">Gateway</span> tab allows additional gateways (router addresses) to be added to the network
 			interface settings. In most cases where DHCP is used, it will not be necessary to
 			create these manual settings.
 			</p></li><li><p>
-<a class="indexterm" name="id2577249"></a>
-<a class="indexterm" name="id2577256"></a>
+<a class="indexterm" name="id2577235"></a>
+<a class="indexterm" name="id2577242"></a>
 			The following example uses manually configured WINS settings. See <a class="link" href="ClientConfig.html#WME005" title="Figure�8.13.�DNS Configuration.">&#8220;DNS Configuration.&#8221;</a>.
 			When finished making changes, click <span class="guibutton">OK</span> to commit the settings.
 			</p><div class="figure"><a name="WME005"></a><p class="title"><b>Figure�8.13.�DNS Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME005.png" alt="DNS Configuration."></div></div></div><p><br class="figure-break">
 			</p><p>
-<a class="indexterm" name="id2577318"></a>
-<a class="indexterm" name="id2577325"></a>
+<a class="indexterm" name="id2577304"></a>
+<a class="indexterm" name="id2577311"></a>
 			This is an example of a system that uses manually configured WINS settings. One situation where
 			this might apply is on a network that has a single DHCP server that provides settings for multiple
 			Windows workgroups or domains. See <a class="link" href="ClientConfig.html#WME003" title="Figure�8.14.�WINS Configuration.">&#8220;WINS Configuration.&#8221;</a>.
 			</p><div class="figure"><a name="WME003"></a><p class="title"><b>Figure�8.14.�WINS Configuration.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME003.png" alt="WINS Configuration."></div></div></div><p><br class="figure-break">
-			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2577384"></a>Joining a Domain: Windows 2000/XP Professional</h3></div></div></div><p>
+			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2577370"></a>Joining a Domain: Windows 2000/XP Professional</h3></div></div></div><p>
+<a class="indexterm" name="id2577378"></a>
+<a class="indexterm" name="id2577385"></a>
 <a class="indexterm" name="id2577392"></a>
 <a class="indexterm" name="id2577399"></a>
-<a class="indexterm" name="id2577406"></a>
-<a class="indexterm" name="id2577413"></a>
 	Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
 	This section steps through the process for making a Windows 200x/XP Professional machine a
 	member of a domain security environment. It should be noted that this process is identical
@@ -259,18 +259,18 @@ that are in common use today. These are:
 		</p></li><li><p>
 		Right-click <span class="guimenu">My Computer</span>, then select <span class="guimenuitem">Properties</span>.
 		</p></li><li><p>
-<a class="indexterm" name="id2577467"></a>
+<a class="indexterm" name="id2577453"></a>
 		The opening panel is the same one that can be reached by clicking <span class="guimenu">System</span> on the Control Panel.
 		See <a class="link" href="ClientConfig.html#wxpp001" title="Figure�8.15.�The General Panel.">&#8220;The General Panel.&#8221;</a>.
 		</p><div class="figure"><a name="wxpp001"></a><p class="title"><b>Figure�8.15.�The General Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp001.png" alt="The General Panel."></div></div></div><p><br class="figure-break">
 		</p></li><li><p>
-<a class="indexterm" name="id2577532"></a>
+<a class="indexterm" name="id2577518"></a>
 		Click the <span class="guimenu">Computer Name</span> tab.
 		This panel shows the <span class="guimenuitem">Computer Description</span>, the <span class="guimenuitem">Full computer name</span>,
 		and the <span class="guimenuitem">Workgroup</span> or <span class="guimenuitem">Domain name</span>.
 		</p><p>
-<a class="indexterm" name="id2577574"></a>
-<a class="indexterm" name="id2577580"></a>
+<a class="indexterm" name="id2577560"></a>
+<a class="indexterm" name="id2577566"></a>
 		Clicking the <span class="guimenu">Network ID</span> button will launch the configuration wizard. Do not use this with
 		Samba-3. If you wish to change the computer name or join or leave the domain, click the <span class="guimenu">Change</span> button.
 		See <a class="link" href="ClientConfig.html#wxpp004" title="Figure�8.16.�The Computer Name Panel.">&#8220;The Computer Name Panel.&#8221;</a>.
@@ -280,38 +280,38 @@ that are in common use today. These are:
 		We will join the domain called MIDEARTH. See <a class="link" href="ClientConfig.html#wxpp006" title="Figure�8.17.�The Computer Name Changes Panel.">&#8220;The Computer Name Changes Panel.&#8221;</a>.
 		</p><div class="figure"><a name="wxpp006"></a><p class="title"><b>Figure�8.17.�The Computer Name Changes Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp006.png" alt="The Computer Name Changes Panel."></div></div></div><p><br class="figure-break">
         </p></li><li><p>
-<a class="indexterm" name="id2577712"></a>
+<a class="indexterm" name="id2577698"></a>
 		Enter the name <span class="guimenu">MIDEARTH</span> in the field below the domain radio button.
 		</p><p>
 		This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <a class="link" href="ClientConfig.html#wxpp007" title="Figure�8.18.�The Computer Name Changes Panel Domain MIDEARTH.">&#8220;The Computer Name Changes Panel  Domain MIDEARTH.&#8221;</a>.
 		</p><div class="figure"><a name="wxpp007"></a><p class="title"><b>Figure�8.18.�The Computer Name Changes Panel  Domain MIDEARTH.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp007.png" alt="The Computer Name Changes Panel Domain MIDEARTH."></div></div></div><p><br class="figure-break">
         </p></li><li><p>
-<a class="indexterm" name="id2577784"></a>
-<a class="indexterm" name="id2577791"></a>
+<a class="indexterm" name="id2577770"></a>
+<a class="indexterm" name="id2577777"></a>
 		Now click the <span class="guimenu">OK</span> button. A dialog box should appear to allow you to provide the
 		credentials (username and password) of a domain administrative account that has the rights to add machines to
 		the domain.
 		</p><p>
-<a class="indexterm" name="id2577810"></a>
+<a class="indexterm" name="id2577796"></a>
 		Enter the name &#8220;<span class="quote">root</span>&#8221; and the root password from your Samba-3 server. See <a class="link" href="ClientConfig.html#wxpp008" title="Figure�8.19.�Computer Name Changes Username and Password Panel.">&#8220;Computer Name Changes  Username and Password Panel.&#8221;</a>.
 		</p><div class="figure"><a name="wxpp008"></a><p class="title"><b>Figure�8.19.�Computer Name Changes  Username and Password Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp008.png" alt="Computer Name Changes Username and Password Panel."></div></div></div><p><br class="figure-break">
         </p></li><li><p>
 		Click on <span class="guimenu">OK</span>.
         </p><p>
-<a class="indexterm" name="id2577887"></a>
-<a class="indexterm" name="id2577894"></a>
+<a class="indexterm" name="id2577873"></a>
+<a class="indexterm" name="id2577880"></a>
 		The &#8220;<span class="quote">Welcome to the MIDEARTH domain.</span>&#8221; dialog box should appear. At this point the machine must be rebooted.
 		Joining the domain is now complete.
-        </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2577910"></a>Domain Logon Configuration: Windows 9x/Me</h3></div></div></div><p>
+        </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2577896"></a>Domain Logon Configuration: Windows 9x/Me</h3></div></div></div><p>
+<a class="indexterm" name="id2577904"></a>
+<a class="indexterm" name="id2577911"></a>
 <a class="indexterm" name="id2577918"></a>
-<a class="indexterm" name="id2577925"></a>
-<a class="indexterm" name="id2577932"></a>
 	We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
 	that these platforms can use only the LanManager network logon protocols.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+<a class="indexterm" name="id2577932"></a>
+<a class="indexterm" name="id2577940"></a>
 <a class="indexterm" name="id2577946"></a>
-<a class="indexterm" name="id2577954"></a>
-<a class="indexterm" name="id2577960"></a>
 	Windows XP Home edition cannot participate in domain or LanManager network logons.
 	</p></div><div class="procedure"><ol type="1"><li><p>
 		Right-click on the <span class="guimenu">Network Neighborhood</span> icon.
@@ -320,44 +320,44 @@ that are in common use today. These are:
                 See <a class="link" href="ClientConfig.html#WME009" title="Figure�8.20.�The Network Panel.">&#8220;The Network Panel.&#8221;</a>.
 		</p><div class="figure"><a name="WME009"></a><p class="title"><b>Figure�8.20.�The Network Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME009.png" alt="The Network Panel."></div></div></div><p><br class="figure-break">
                 </p><p>
-<a class="indexterm" name="id2578039"></a>
-<a class="indexterm" name="id2578046"></a>
+<a class="indexterm" name="id2578025"></a>
+<a class="indexterm" name="id2578032"></a>
 		Make sure that the <span class="guimenu">Client for Microsoft Networks</span> driver is installed as shown.
 		Click on the <span class="guimenu">Client for Microsoft Networks</span> entry in <span class="guimenu">The following network
 		components are installed:</span> box. Then click the <span class="guibutton">Properties</span> button.
 		</p></li><li><p>
-<a class="indexterm" name="id2578087"></a>
-<a class="indexterm" name="id2578094"></a>
+<a class="indexterm" name="id2578073"></a>
+<a class="indexterm" name="id2578080"></a>
 		The Client for Microsoft Networks Properties panel is the correct location to configure network logon
 		settings. See <a class="link" href="ClientConfig.html#WME010" title="Figure�8.21.�Client for Microsoft Networks Properties Panel.">&#8220;Client for Microsoft Networks Properties Panel.&#8221;</a>.
 		</p><div class="figure"><a name="WME010"></a><p class="title"><b>Figure�8.21.�Client for Microsoft Networks Properties Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME010.png" alt="Client for Microsoft Networks Properties Panel."></div></div></div><p><br class="figure-break">
                 </p><p>
-<a class="indexterm" name="id2578150"></a>
-<a class="indexterm" name="id2578157"></a>
+<a class="indexterm" name="id2578136"></a>
+<a class="indexterm" name="id2578143"></a>
 		Enter the Windows NT domain name, check the <span class="guimenu">Log on to Windows NT domain</span> box,
 		and click <span class="guimenu">OK</span>.
 		</p></li><li><p>
-<a class="indexterm" name="id2578184"></a>
-<a class="indexterm" name="id2578190"></a>
-<a class="indexterm" name="id2578197"></a>
+<a class="indexterm" name="id2578170"></a>
+<a class="indexterm" name="id2578176"></a>
+<a class="indexterm" name="id2578183"></a>
 		Click on the <span class="guimenu">Identification</span> button. This is the location at which the workgroup
 		(domain) name and the machine name (computer name) need to be set. See <a class="link" href="ClientConfig.html#WME013" title="Figure�8.22.�Identification Panel.">&#8220;Identification Panel.&#8221;</a>.
 		</p><div class="figure"><a name="WME013"></a><p class="title"><b>Figure�8.22.�Identification Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME013.png" alt="Identification Panel."></div></div></div><p><br class="figure-break">
                 </p></li><li><p>
-<a class="indexterm" name="id2578263"></a>
-<a class="indexterm" name="id2578270"></a>
-<a class="indexterm" name="id2578276"></a>
-<a class="indexterm" name="id2578283"></a>
+<a class="indexterm" name="id2578249"></a>
+<a class="indexterm" name="id2578256"></a>
+<a class="indexterm" name="id2578262"></a>
+<a class="indexterm" name="id2578269"></a>
 		Now click the <span class="guimenu">Access Control</span> button. If you want to be able to assign share access
 		permissions using domain user and group accounts, it is necessary to enable
 		<span class="guimenu">User-level access control</span> as shown in this panel.  See <a class="link" href="ClientConfig.html#WME014" title="Figure�8.23.�Access Control Panel.">&#8220;Access Control Panel.&#8221;</a>.
 		</p><div class="figure"><a name="WME014"></a><p class="title"><b>Figure�8.23.�Access Control Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WME014.png" alt="Access Control Panel."></div></div></div><p><br class="figure-break">
-                </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578353"></a>Common Errors</h2></div></div></div><p>
-<a class="indexterm" name="id2578361"></a>
-<a class="indexterm" name="id2578368"></a>
+                </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2578339"></a>Common Errors</h2></div></div></div><p>
+<a class="indexterm" name="id2578347"></a>
+<a class="indexterm" name="id2578354"></a>
 The most common errors that can afflict Windows networking systems include:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Incorrect IP address.</p></li><li><p>Incorrect or inconsistent netmasks.</p></li><li><p>Incorrect router address.</p></li><li><p>Incorrect DNS server address.</p></li><li><p>Incorrect WINS server address.</p></li><li><p>Use of a Network Scope setting  watch out for this one!</p></li></ul></div><p>
-<a class="indexterm" name="id2578415"></a>
-<a class="indexterm" name="id2578423"></a>
+<a class="indexterm" name="id2578401"></a>
+<a class="indexterm" name="id2578409"></a>
 The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
 </p><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">smb.conf</code> does not have correct <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> settings.</p></li><li><p>&#8220;<span class="quote">root</span>&#8221; account is not in password backend database.</p></li><li><p>Attempt to use a user account instead of the &#8220;<span class="quote">root</span>&#8221; account to join a machine to the domain.</p></li><li><p>Open connections from the workstation to the server.</p></li><li><p>Firewall or filter configurations in place on either the client or the Samba server.</p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�7.�Standalone Servers�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�III.�Advanced Configuration</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html b/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html
index 067f147e69..396d479728 100644
--- a/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html
+++ b/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�48.�DNS and DHCP Configuration Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="ch47.html" title="Chapter�47.�Samba Support"><link rel="next" href="apa.html" title="Appendix�A.� GNU General Public License version 3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�48.�DNS and DHCP Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch47.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter�48.�DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692722">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2692901">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2692992">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692722"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2692730"></a>
-<a class="indexterm" name="id2692740"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�48.�DNS and DHCP Configuration Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="ch47.html" title="Chapter�47.�Samba Support"><link rel="next" href="apa.html" title="Appendix�A.� GNU General Public License version 3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�48.�DNS and DHCP Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch47.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter�48.�DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692858">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2693042">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2693133">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692858"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2692866"></a>
+<a class="indexterm" name="id2692876"></a>
 There are few subjects in the UNIX world that might raise as much contention as
 Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP).
 Not all opinions held for or against particular implementations of DNS and DHCP
@@ -10,16 +10,16 @@ We live in a modern age where many information technology users demand mobility
 and freedom. Microsoft Windows users in particular expect to be able to plug their
 notebook computer into a network port and have things &#8220;<span class="quote">just work.</span>&#8221;
 </p><p>
-<a class="indexterm" name="id2692766"></a>
+<a class="indexterm" name="id2692902"></a>
 UNIX administrators have a point. Many of the normative practices in the Microsoft
 Windows world at best border on bad practice from a security perspective.
 Microsoft Windows networking protocols allow workstations to arbitrarily register
 themselves on a network. Windows 2000 Active Directory registers entries in the DNS namespace
 that are equally perplexing to UNIX administrators. Welcome to the new world!
 </p><p>
-<a class="indexterm" name="id2692783"></a>
-<a class="indexterm" name="id2692792"></a>
-<a class="indexterm" name="id2692801"></a>
+<a class="indexterm" name="id2692919"></a>
+<a class="indexterm" name="id2692928"></a>
+<a class="indexterm" name="id2692937"></a>
 The purpose of this chapter is to demonstrate the configuration of the Internet
 Software Consortium (ISC) DNS and DHCP servers to provide dynamic services that are
 compatible with their equivalents in the Microsoft Windows 2000 Server products.
@@ -27,26 +27,26 @@ compatible with their equivalents in the Microsoft Windows 2000 Server products.
 This chapter provides no more than a working example of configuration files for both DNS and DHCP servers. The
 examples used match configuration examples used elsewhere in this document.
 </p><p>
-<a class="indexterm" name="id2692824"></a>
-<a class="indexterm" name="id2692831"></a>
-<a class="indexterm" name="id2692838"></a>
+<a class="indexterm" name="id2692960"></a>
+<a class="indexterm" name="id2692967"></a>
+<a class="indexterm" name="id2692974"></a>
 This chapter explicitly does not provide a tutorial, nor does it pretend to be a reference guide on DNS and
 DHCP, as this is well beyond the scope and intent of this document as a whole. Anyone who wants more detailed
 reference materials on DNS or DHCP should visit the ISC Web site at <a class="ulink" href="http://www.isc.org" target="_top"> http://www.isc.org</a>.  Those wanting a written text might also be interested
 in the O'Reilly publications on DNS, see the <a class="ulink" href="http://www.oreilly.com/catalog/dns/index.htm" target="_top">O'Reilly</a> web site, and the <a class="ulink" href="http://www.bind9.net/books-dhcp" target="_top">BIND9.NET</a> web site for details.
 The books are:
-</p><div class="orderedlist"><ol type="1"><li><p>DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4</p></li><li><p>DNS &amp; Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9</p></li><li><p>The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692901"></a>Example Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2692909"></a>
-<a class="indexterm" name="id2692916"></a>
+</p><div class="orderedlist"><ol type="1"><li><p>DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4</p></li><li><p>DNS &amp; Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9</p></li><li><p>The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2693042"></a>Example Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2693050"></a>
+<a class="indexterm" name="id2693056"></a>
 The DNS is to the Internet what water is to life. Nearly all information resources (host names) are resolved
 to their Internet protocol (IP) addresses through DNS.  Windows networking tried hard to avoid the
-complexities of DNS, but alas, DNS won.  <a class="indexterm" name="id2692926"></a> The alternative to
+complexities of DNS, but alas, DNS won.  <a class="indexterm" name="id2693067"></a> The alternative to
 DNS, the Windows Internet Name Service (WINS)  an artifact of NetBIOS networking over the TCP/IP
 protocols  has demonstrated scalability problems as well as a flat, nonhierarchical namespace that
 became unmanageable as the size and complexity of information technology networks grew.
 </p><p>
-<a class="indexterm" name="id2692948"></a>
-<a class="indexterm" name="id2692954"></a>
+<a class="indexterm" name="id2693088"></a>
+<a class="indexterm" name="id2693095"></a>
 WINS is a Microsoft implementation of the RFC1001/1002 NetBIOS Name Service (NBNS).
 It allows NetBIOS clients (like Microsoft Windows machines) to register an arbitrary
 machine name that the administrator or user has chosen together with the IP
@@ -66,13 +66,13 @@ hostnames via Microsoft WINS.
 </p><p>
 The following configurations demonstrate a simple, insecure dynamic DNS server and
 a simple DHCP server that matches the DNS configuration.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2692992"></a>Dynamic DNS</h3></div></div></div><p>
-	<a class="indexterm" name="id2693000"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2693133"></a>Dynamic DNS</h3></div></div></div><p>
+	<a class="indexterm" name="id2693140"></a>
 	The example DNS configuration is for a private network in the IP address
 	space for network 192.168.1.0/24. The private class network address space
 	is set forth in RFC1918.
 	</p><p>
-	<a class="indexterm" name="id2693015"></a>
+	<a class="indexterm" name="id2693156"></a>
 	It is assumed that this network will be situated behind a secure firewall.
 	The files that follow work with ISC BIND version 9. BIND is the Berkeley
 	Internet Name Daemon.
@@ -223,8 +223,8 @@ $ORIGIN 1.168.192.in-addr.arpa.
 2                       PTR     marvel.quenya.org.
 </pre><p>
 	</p><p>
-<a class="indexterm" name="id2693159"></a>
-<a class="indexterm" name="id2693166"></a>
+<a class="indexterm" name="id2693300"></a>
+<a class="indexterm" name="id2693307"></a>
 	The configuration files shown here were copied from a fully working system. All dynamically registered
 	entries have been removed. In addition to these files, BIND version 9 will
 	create for each of the dynamic registration files a file that has a 
diff --git a/docs/htmldocs/Samba3-HOWTO/FastStart.html b/docs/htmldocs/Samba3-HOWTO/FastStart.html
index c749b0798e..8b02f92dda 100644
--- a/docs/htmldocs/Samba3-HOWTO/FastStart.html
+++ b/docs/htmldocs/Samba3-HOWTO/FastStart.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Fast Start: Cure for Impatience</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="introduction.html" title="Part�I.�General Installation"><link rel="prev" href="install.html" title="Chapter�1.�How to Install and Test SAMBA"><link rel="next" href="type.html" title="Part�II.�Server Configuration Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Fast Start: Cure for Impatience</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install.html">Prev</a>�</td><th width="60%" align="center">Part�I.�General Installation</th><td width="20%" align="right">�<a accesskey="n" href="type.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter�2.�Fast Start: Cure for Impatience</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="FastStart.html#id2554110">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554133">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554203">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554221">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555963">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556806">Domain Controller</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Fast Start: Cure for Impatience</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="introduction.html" title="Part�I.�General Installation"><link rel="prev" href="install.html" title="Chapter�1.�How to Install and Test SAMBA"><link rel="next" href="type.html" title="Part�II.�Server Configuration Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Fast Start: Cure for Impatience</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install.html">Prev</a>�</td><th width="60%" align="center">Part�I.�General Installation</th><td width="20%" align="right">�<a accesskey="n" href="type.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter�2.�Fast Start: Cure for Impatience</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="FastStart.html#id2554105">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554128">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554197">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554216">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555957">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556800">Domain Controller</a></span></dt></dl></dd></dl></div><p>
 When we first asked for suggestions for inclusion in the Samba HOWTO documentation,
 someone wrote asking for example configurations  and lots of them. That is remarkably
 difficult to do without losing a lot of value that can be derived from presenting
@@ -22,7 +22,7 @@ as the equivalent of an auto mechanic's repair guide. The book &#8220;<span clas
 equivalent of the driver's guide that explains how to drive the car. If you want complete network
 configuration examples, go to <a class="ulink" href="http://www.samba.org/samba/docs/Samba3-ByExample.pdf" target="_top">Samba-3 by
 Example</a>.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554110"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554105"></a>Features and Benefits</h2></div></div></div><p>
 Samba needs very little configuration to create a basic working system.
 In this chapter we progress from the simple to the complex, for each providing
 all steps and configuration file changes needed to make each work. Please note
@@ -32,7 +32,7 @@ features. These additional features are covered in the remainder of this documen
 The examples used here have been obtained from a number of people who made
 requests for example configurations. All identities have been obscured to protect
 the guilty, and any resemblance to unreal nonexistent sites is deliberate.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554133"></a>Description of Example Sites</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554128"></a>Description of Example Sites</h2></div></div></div><p>
 In the first set of configuration examples we consider the case of exceptionally simple system requirements.
 There is a real temptation to make something that should require little effort much too complex.
 </p><p>
@@ -53,15 +53,15 @@ network-attached storage (NAS) device and a print server.
 The later example consider more complex systems that will either integrate into existing MS Windows networks
 or replace them entirely. These cover domain member servers as well as Samba domain control (PDC/BDC) and
 finally describes in detail a large distributed network with branch offices in remote locations.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554203"></a>Worked Examples</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2554197"></a>Worked Examples</h2></div></div></div><p>
 The configuration examples are designed to cover everything necessary to get Samba 
 running. They do not cover basic operating system platform configuration, which is
 clearly beyond the scope of this text.
 </p><p>
 It is also assumed that Samba has been correctly installed, either by way of installation
 of the packages that are provided by the operating system vendor or through other means.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554221"></a>Standalone Server</h3></div></div></div><p>
-	<a class="indexterm" name="id2554229"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554216"></a>Standalone Server</h3></div></div></div><p>
+	<a class="indexterm" name="id2554223"></a>
 	A standalone server implies no more than the fact that it is not a domain controller
 	and it does not participate in domain control. It can be a simple, workgroup-like
 	server, or it can be a complex server that is a member of a domain security context.
@@ -69,7 +69,7 @@ of the packages that are provided by the operating system vendor or through othe
 	As the examples are developed, every attempt is made to progress the system toward greater capability, just as
 	one might expect would happen in a real business office as that office grows in size and its needs change.
 	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="anon-ro"></a>Anonymous Read-Only Document Server</h4></div></div></div><p>
-		<a class="indexterm" name="id2554260"></a>
+		<a class="indexterm" name="id2554254"></a>
 		The purpose of this type of server is to make available to any user
 		any documents or files that are placed on the shared resource. The
 		shared resource could be a CD-ROM drive, a CD-ROM image, or a file
@@ -82,7 +82,7 @@ of the packages that are provided by the operating system vendor or through othe
 			<span class="emphasis"><em>m0r3pa1n</em></span>  of course, that's just the example we are
 			using; do not use this in a production environment because
 			all readers of this document will know it.
-			</p></li></ul></div><div class="procedure"><a name="id2554304"></a><p class="title"><b>Procedure�2.1.�Installation Procedure: Read-Only Server</b></p><div class="example"><a name="anon-example"></a><p class="title"><b>Example�2.1.�Anonymous Read-Only Server Configuration</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554430"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554440"></a><em class="parameter"><code>netbios name = HOBBIT</code></em></td></tr><tr><td><a class="indexterm" name="id2554451"></a><em class="parameter"><code>security = share</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2554469"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2554480"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2554490"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554501"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+			</p></li></ul></div><div class="procedure"><a name="id2554299"></a><p class="title"><b>Procedure�2.1.�Installation Procedure: Read-Only Server</b></p><div class="example"><a name="anon-example"></a><p class="title"><b>Example�2.1.�Anonymous Read-Only Server Configuration</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554424"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554435"></a><em class="parameter"><code>netbios name = HOBBIT</code></em></td></tr><tr><td><a class="indexterm" name="id2554445"></a><em class="parameter"><code>security = share</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2554464"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2554474"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2554485"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554495"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 			Add user to system (with creation of the user's home directory):
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</code></strong>
@@ -151,8 +151,8 @@ Press enter to see a dump of your service definitions
 			</p></li></ol></div><p>
 		The information above (following # Global parameters) provides the complete
 		contents of the <code class="filename">/etc/samba/smb.conf</code> file.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554637"></a>Anonymous Read-Write Document Server</h4></div></div></div><p>
-		<a class="indexterm" name="id2554645"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554632"></a>Anonymous Read-Write Document Server</h4></div></div></div><p>
+		<a class="indexterm" name="id2554640"></a>
 		We should view this configuration as a progression from the previous example.
 		The difference is that shared access is now forced to the user identity of jackb
 		and to the primary group jackb belongs to. One other refinement we can make is to
@@ -169,8 +169,8 @@ Added user jackb.
 		instead of to <span class="emphasis"><em>User Unknown</em></span>.
 		</p><p>
 		The complete, modified <code class="filename">smb.conf</code> file is as shown in <a class="link" href="FastStart.html#anon-rw" title="Example�2.2.�Modified Anonymous Read-Write smb.conf">&#8220;Modified Anonymous Read-Write smb.conf&#8221;</a>.
-		</p><div class="example"><a name="anon-rw"></a><p class="title"><b>Example�2.2.�Modified Anonymous Read-Write smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554745"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554755"></a><em class="parameter"><code>netbios name = HOBBIT</code></em></td></tr><tr><td><a class="indexterm" name="id2554765"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2554784"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2554795"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2554805"></a><em class="parameter"><code>force user = jackb</code></em></td></tr><tr><td><a class="indexterm" name="id2554815"></a><em class="parameter"><code>force group = users</code></em></td></tr><tr><td><a class="indexterm" name="id2554826"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554836"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554849"></a>Anonymous Print Server</h4></div></div></div><p>
-		<a class="indexterm" name="id2554856"></a>
+		</p><div class="example"><a name="anon-rw"></a><p class="title"><b>Example�2.2.�Modified Anonymous Read-Write smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554739"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554750"></a><em class="parameter"><code>netbios name = HOBBIT</code></em></td></tr><tr><td><a class="indexterm" name="id2554760"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2554779"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2554789"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2554800"></a><em class="parameter"><code>force user = jackb</code></em></td></tr><tr><td><a class="indexterm" name="id2554810"></a><em class="parameter"><code>force group = users</code></em></td></tr><tr><td><a class="indexterm" name="id2554820"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554831"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554843"></a>Anonymous Print Server</h4></div></div></div><p>
+		<a class="indexterm" name="id2554851"></a>
 		An anonymous print server serves two purposes:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
 			It allows printing to all printers from a single location.
@@ -187,7 +187,7 @@ Added user jackb.
 		In this configuration, it is undesirable to present the Add Printer Wizard, and we do
 		not want to have automatic driver download, so we disable it in the following
 		configuration. <a class="link" href="FastStart.html#anon-print" title="Example�2.3.�Anonymous Print Server smb.conf">&#8220;Anonymous Print Server smb.conf&#8221;</a> is the resulting <code class="filename">smb.conf</code> file.
-		</p><div class="example"><a name="anon-print"></a><p class="title"><b>Example�2.3.�Anonymous Print Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554933"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554943"></a><em class="parameter"><code>netbios name = LUTHIEN</code></em></td></tr><tr><td><a class="indexterm" name="id2554954"></a><em class="parameter"><code>security = share</code></em></td></tr><tr><td><a class="indexterm" name="id2554964"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2554974"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554985"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554996"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2555015"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2555025"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2555036"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555046"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555056"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555067"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
+		</p><div class="example"><a name="anon-print"></a><p class="title"><b>Example�2.3.�Anonymous Print Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2554928"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2554938"></a><em class="parameter"><code>netbios name = LUTHIEN</code></em></td></tr><tr><td><a class="indexterm" name="id2554948"></a><em class="parameter"><code>security = share</code></em></td></tr><tr><td><a class="indexterm" name="id2554959"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2554969"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2554980"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2554991"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2555009"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2555020"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2555030"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555041"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555051"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555061"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
 		The above configuration is not ideal. It uses no smart features, and it deliberately
 		presents a less than elegant solution. But it is basic, and it does print. Samba makes
 		use of the direct printing application program interface that is provided by CUPS.
@@ -220,14 +220,14 @@ Added user jackb.
 		The purpose of setting the sticky bit is to prevent who does not own the temporary print file
 		from being able to take control of it with the potential for devious misuse.
 			</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-		<a class="indexterm" name="id2555177"></a>
-		<a class="indexterm" name="id2555185"></a>
+		<a class="indexterm" name="id2555171"></a>
+		<a class="indexterm" name="id2555180"></a>
 		On CUPS-enabled systems there is a facility to pass raw data directly to the printer without
 		intermediate processing via CUPS print filters. Where use of this mode of operation is desired,
 		it is necessary to configure a raw printing device. It is also necessary to enable the raw mime
 		handler in the <code class="filename">/etc/mime.conv</code> and <code class="filename">/etc/mime.types</code>
 		files. Refer to <a class="link" href="CUPS-printing.html#cups-raw" title="Explicitly Enable raw Printing for application/octet-stream">&#8220;Explicitly Enable raw Printing for application/octet-stream&#8221;</a>.
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555213"></a>Secure Read-Write File and Print Server</h4></div></div></div><p>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555208"></a>Secure Read-Write File and Print Server</h4></div></div></div><p>
 		We progress now from simple systems to a server that is slightly more complex.
 		</p><p>
 		Our new server will require a public data storage area in which only authenticated
@@ -250,8 +250,8 @@ Added user jackb.
 		it is not necessary to enter it into the configuration file. Note that the guest backend is
 		added to the list of active passdb backends no matter whether it specified directly in Samba configuration
 		file or not.
-		</p><div class="procedure"><a name="id2555283"></a><p class="title"><b>Procedure�2.2.�Installing the Secure Office Server</b></p><div class="example"><a name="OfficeServer"></a><p class="title"><b>Example�2.4.�Secure Office Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2555378"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2555389"></a><em class="parameter"><code>netbios name = OLORIN</code></em></td></tr><tr><td><a class="indexterm" name="id2555399"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2555410"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555420"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2555431"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2555450"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2555460"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2555471"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2555481"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2555500"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2555510"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2555521"></a><em class="parameter"><code>force user = maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2555531"></a><em class="parameter"><code>force group = users</code></em></td></tr><tr><td><a class="indexterm" name="id2555542"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2555560"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2555571"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2555581"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2555592"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2555602"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555612"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555623"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555633"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
-		<a class="indexterm" name="id2555294"></a>
+		</p><div class="procedure"><a name="id2555278"></a><p class="title"><b>Procedure�2.2.�Installing the Secure Office Server</b></p><div class="example"><a name="OfficeServer"></a><p class="title"><b>Example�2.4.�Secure Office Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2555373"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2555384"></a><em class="parameter"><code>netbios name = OLORIN</code></em></td></tr><tr><td><a class="indexterm" name="id2555394"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2555404"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555415"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2555426"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2555445"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2555455"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2555465"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2555476"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2555495"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2555505"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2555515"></a><em class="parameter"><code>force user = maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2555526"></a><em class="parameter"><code>force group = users</code></em></td></tr><tr><td><a class="indexterm" name="id2555536"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2555555"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2555565"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2555576"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2555586"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2555597"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555607"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555617"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2555628"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+		<a class="indexterm" name="id2555289"></a>
 			Add all users to the operating system:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</code></strong>
@@ -290,10 +290,10 @@ Added user ameds.
 			</p></li><li><p>
 			Start Samba using the operating system administrative interface.
 			Alternately, this can be done manually by executing:
-			<a class="indexterm" name="id2555753"></a>
+			<a class="indexterm" name="id2555748"></a>
+			<a class="indexterm" name="id2555754"></a>
 			<a class="indexterm" name="id2555760"></a>
-			<a class="indexterm" name="id2555766"></a>
-			<a class="indexterm" name="id2555774"></a>
+			<a class="indexterm" name="id2555769"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code> nmbd; smbd;</code></strong>
 </pre><p>
@@ -358,8 +358,8 @@ smb: \&gt; <strong class="userinput"><code>q</code></strong>
 			By now you should be getting the hang of configuration basics. Clearly, it is time to
 			explore slightly more complex examples. For the remainder of this chapter we abbreviate
 			instructions, since there are previous examples.
-			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555963"></a>Domain Member Server</h3></div></div></div><p>
-	<a class="indexterm" name="id2555970"></a>
+			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555957"></a>Domain Member Server</h3></div></div></div><p>
+	<a class="indexterm" name="id2555965"></a>
 	In this instance we consider the simplest server configuration we can get away with
 	to make an accounting department happy. Let's be warned, the users are accountants and they
 	do have some nasty demands. There is a budget for only one server for this department.
@@ -390,11 +390,11 @@ smb: \&gt; <strong class="userinput"><code>q</code></strong>
 	file area for each member of her team that is private to that person, but she wants full
 	access to all areas. Users must have a private home share for personal work-related files
 	and for materials not related to departmental operations.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556037"></a>Example Configuration</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556032"></a>Example Configuration</h4></div></div></div><p>
 		The server <span class="emphasis"><em>valinor</em></span> will be a member server of the company domain.
 		Accounting will have only a local server. User accounts will be on the domain controllers,
 		as will desktop profiles and all network policy files.
-		</p><div class="procedure"><div class="example"><a name="fast-member-server"></a><p class="title"><b>Example�2.5.�Member Server smb.conf (Globals)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556110"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2556121"></a><em class="parameter"><code>netbios name = VALINOR</code></em></td></tr><tr><td><a class="indexterm" name="id2556131"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2556142"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2556152"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556162"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556174"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2556184"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2556194"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556205"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="fast-memberserver-shares"></a><p class="title"><b>Example�2.6.�Member Server smb.conf (Shares and Services)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2556239"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2556249"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2556260"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556270"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[spytfull]</code></em></td></tr><tr><td><a class="indexterm" name="id2556289"></a><em class="parameter"><code>comment = Accounting Application Only</code></em></td></tr><tr><td><a class="indexterm" name="id2556300"></a><em class="parameter"><code>path = /export/spytfull</code></em></td></tr><tr><td><a class="indexterm" name="id2556310"></a><em class="parameter"><code>valid users = @Accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2556321"></a><em class="parameter"><code>admin users = maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2556331"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2556350"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2556360"></a><em class="parameter"><code>path = /export/public</code></em></td></tr><tr><td><a class="indexterm" name="id2556371"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2556390"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2556400"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2556410"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2556421"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2556431"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556442"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556452"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556462"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+		</p><div class="procedure"><div class="example"><a name="fast-member-server"></a><p class="title"><b>Example�2.5.�Member Server smb.conf (Globals)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556105"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2556116"></a><em class="parameter"><code>netbios name = VALINOR</code></em></td></tr><tr><td><a class="indexterm" name="id2556126"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2556136"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2556147"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556157"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556168"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2556179"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2556189"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556200"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="fast-memberserver-shares"></a><p class="title"><b>Example�2.6.�Member Server smb.conf (Shares and Services)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2556233"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2556244"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2556254"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2556265"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[spytfull]</code></em></td></tr><tr><td><a class="indexterm" name="id2556283"></a><em class="parameter"><code>comment = Accounting Application Only</code></em></td></tr><tr><td><a class="indexterm" name="id2556295"></a><em class="parameter"><code>path = /export/spytfull</code></em></td></tr><tr><td><a class="indexterm" name="id2556305"></a><em class="parameter"><code>valid users = @Accounts</code></em></td></tr><tr><td><a class="indexterm" name="id2556315"></a><em class="parameter"><code>admin users = maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2556326"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[public]</code></em></td></tr><tr><td><a class="indexterm" name="id2556345"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2556355"></a><em class="parameter"><code>path = /export/public</code></em></td></tr><tr><td><a class="indexterm" name="id2556365"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2556384"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2556395"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2556405"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2556415"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2556426"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556436"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556447"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2556457"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 			Do not add users to the UNIX/Linux server; all of this will run off the
 			central domain.
 			</p></li><li><p>
@@ -402,7 +402,7 @@ smb: \&gt; <strong class="userinput"><code>q</code></strong>
 			(globals)</a> and <a class="link" href="FastStart.html#fast-memberserver-shares" title="Example�2.6.�Member Server smb.conf (Shares and Services)">Member server smb.conf (shares
 			and services)</a>.
 			</p></li><li><p>
-			<a class="indexterm" name="id2556479"></a>
+			<a class="indexterm" name="id2556474"></a>
 			Join the domain. Note: Do not start Samba until this step has been completed!
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>net rpc join -Uroot%'bigsecret'</code></strong>
@@ -414,12 +414,12 @@ Joined domain MIDEARTH.
 			</p></li><li><p>
 			Start Samba following the normal method for your operating system platform.
 			If you wish to do this manually, execute as root:
-			<a class="indexterm" name="id2556531"></a>
+			<a class="indexterm" name="id2556526"></a>
+			<a class="indexterm" name="id2556532"></a>
 			<a class="indexterm" name="id2556538"></a>
-			<a class="indexterm" name="id2556544"></a>
-			<a class="indexterm" name="id2556550"></a>
-			<a class="indexterm" name="id2556558"></a>
-			<a class="indexterm" name="id2556567"></a>
+			<a class="indexterm" name="id2556545"></a>
+			<a class="indexterm" name="id2556553"></a>
+			<a class="indexterm" name="id2556562"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>nmbd; smbd; winbindd;</code></strong>
 </pre><p>
@@ -480,8 +480,8 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
 <code class="prompt">root# </code><strong class="userinput"><code>chmod ug=rwxS,o=x /export/{spytfull,public}</code></strong>
 <code class="prompt">root# </code><strong class="userinput"><code>chown maryo.Accounts /export/{spytfull,public}</code></strong>
 </pre><p>
-			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556806"></a>Domain Controller</h3></div></div></div><p>
-	<a class="indexterm" name="id2556813"></a>
+			</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556800"></a>Domain Controller</h3></div></div></div><p>
+	<a class="indexterm" name="id2556808"></a>
 	For the remainder of this chapter the focus is on the configuration of domain control.
 	The examples that follow are for two implementation strategies. Remember, our objective is
 	to create a simple but working solution. The remainder of this book should help to highlight
@@ -515,17 +515,17 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
 	in Samba-3 for Security Account Manager database [SAM] replication).
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 	If you need more than one domain controller, do not use a tdbsam authentication backend.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556885"></a>Example: Engineering Office</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2556880"></a>Example: Engineering Office</h4></div></div></div><p>
 		The engineering office network server we present here is designed to demonstrate use
 		of the new tdbsam password backend. The tdbsam
 		facility is new to Samba-3. It is designed to provide many user and machine account controls
 		that are possible with Microsoft Windows NT4. It is safe to use this in smaller networks.
-		</p><div class="procedure"><div class="example"><a name="fast-engoffice-global"></a><p class="title"><b>Example�2.7.�Engineering Office smb.conf (globals)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556955"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2556965"></a><em class="parameter"><code>netbios name = FRODO</code></em></td></tr><tr><td><a class="indexterm" name="id2556976"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2556986"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2556996"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m %u</code></em></td></tr><tr><td><a class="indexterm" name="id2557008"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r %u</code></em></td></tr><tr><td><a class="indexterm" name="id2557019"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557030"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557041"></a><em class="parameter"><code>add user to group script = /usr/sbin/groupmod -A %u %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557053"></a><em class="parameter"><code>delete user from group script = /usr/sbin/groupmod -R %u %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557065"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u</code></em></td></tr><tr><td># Note: The following specifies the default logon script.</td></tr><tr><td># Per user logon scripts can be specified in the user account using pdbedit </td></tr><tr><td><a class="indexterm" name="id2557086"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td># This sets the default profile path. Set per user paths with pdbedit</td></tr><tr><td><a class="indexterm" name="id2557101"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557112"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2557123"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557133"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557144"></a><em class="parameter"><code>os level = 35</code></em></td></tr><tr><td><a class="indexterm" name="id2557154"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557164"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557175"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2557185"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2557196"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="fast-engoffice-shares"></a><p class="title"><b>Example�2.8.�Engineering Office smb.conf (shares and services)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2557229"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2557239"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557250"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557260"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td># Printing auto-share (makes printers available thru CUPS)</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2557283"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2557294"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2557304"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2557314"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2557325"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557335"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557346"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2557364"></a><em class="parameter"><code>comment = Printer Drivers Share</code></em></td></tr><tr><td><a class="indexterm" name="id2557375"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2557386"></a><em class="parameter"><code>write list = maryo, root</code></em></td></tr><tr><td><a class="indexterm" name="id2557397"></a><em class="parameter"><code>printer admin = maryo, root</code></em></td></tr><tr><td># Needed to support domain logons</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2557420"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2557431"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2557442"></a><em class="parameter"><code>admin users = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2557452"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557462"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td># For profiles to work, create a user directory under the path</td></tr><tr><td>#  shown. i.e., mkdir -p /var/lib/samba/profiles/maryo</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[Profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2557490"></a><em class="parameter"><code>comment = Roaming Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2557501"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2557512"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557522"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td># Other resource (share/printer) definitions would follow below.</td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+		</p><div class="procedure"><div class="example"><a name="fast-engoffice-global"></a><p class="title"><b>Example�2.7.�Engineering Office smb.conf (globals)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2556950"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2556960"></a><em class="parameter"><code>netbios name = FRODO</code></em></td></tr><tr><td><a class="indexterm" name="id2556970"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2556981"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2556991"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m %u</code></em></td></tr><tr><td><a class="indexterm" name="id2557002"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r %u</code></em></td></tr><tr><td><a class="indexterm" name="id2557014"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557025"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557036"></a><em class="parameter"><code>add user to group script = /usr/sbin/groupmod -A %u %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557048"></a><em class="parameter"><code>delete user from group script = /usr/sbin/groupmod -R %u %g</code></em></td></tr><tr><td><a class="indexterm" name="id2557060"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u</code></em></td></tr><tr><td># Note: The following specifies the default logon script.</td></tr><tr><td># Per user logon scripts can be specified in the user account using pdbedit </td></tr><tr><td><a class="indexterm" name="id2557080"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td># This sets the default profile path. Set per user paths with pdbedit</td></tr><tr><td><a class="indexterm" name="id2557096"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557107"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2557117"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2557128"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557138"></a><em class="parameter"><code>os level = 35</code></em></td></tr><tr><td><a class="indexterm" name="id2557149"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557159"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557169"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2557180"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2557190"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="fast-engoffice-shares"></a><p class="title"><b>Example�2.8.�Engineering Office smb.conf (shares and services)</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2557224"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2557234"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2557244"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557255"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td># Printing auto-share (makes printers available thru CUPS)</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2557278"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2557288"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2557299"></a><em class="parameter"><code>printer admin = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2557309"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2557319"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557330"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557340"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2557359"></a><em class="parameter"><code>comment = Printer Drivers Share</code></em></td></tr><tr><td><a class="indexterm" name="id2557370"></a><em class="parameter"><code>path = /var/lib/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2557381"></a><em class="parameter"><code>write list = maryo, root</code></em></td></tr><tr><td><a class="indexterm" name="id2557392"></a><em class="parameter"><code>printer admin = maryo, root</code></em></td></tr><tr><td># Needed to support domain logons</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2557414"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2557425"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2557436"></a><em class="parameter"><code>admin users = root, maryo</code></em></td></tr><tr><td><a class="indexterm" name="id2557447"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2557457"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td># For profiles to work, create a user directory under the path</td></tr><tr><td>#  shown. i.e., mkdir -p /var/lib/samba/profiles/maryo</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[Profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2557485"></a><em class="parameter"><code>comment = Roaming Profile Share</code></em></td></tr><tr><td><a class="indexterm" name="id2557496"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2557507"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2557517"></a><em class="parameter"><code>profile acls = Yes</code></em></td></tr><tr><td># Other resource (share/printer) definitions would follow below.</td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 			A working PDC configuration using the tdbsam
 			password backend can be found in <a class="link" href="FastStart.html#fast-engoffice-global" title="Example�2.7.�Engineering Office smb.conf (globals)">Engineering Office smb.conf
 			(globals)</a> together with <a class="link" href="FastStart.html#fast-engoffice-shares" title="Example�2.8.�Engineering Office smb.conf (shares and services)">Engineering Office smb.conf
 			(shares and services)</a>:
-			<a class="indexterm" name="id2556926"></a>
+			<a class="indexterm" name="id2556920"></a>
 			</p></li><li><p>
 			Create UNIX group accounts as needed using a suitable operating system tool:
 </p><pre class="screen">
@@ -541,8 +541,8 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
 			on files, directories, printers, and as required for use in the Samba
 			environment.
 			</p></li><li><p>
-			<a class="indexterm" name="id2557605"></a>
-			<a class="indexterm" name="id2557614"></a>
+			<a class="indexterm" name="id2557600"></a>
+			<a class="indexterm" name="id2557608"></a>
 			Assign each of the UNIX groups to NT groups by executing this shell script
 			(You could name the script <code class="filename">initGroups.sh</code>):
 </p><pre class="screen">
@@ -570,13 +570,13 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
 			</p></li></ol></div><p>
 		The above configuration provides a functional PDC
 		system to which must be added file shares and printers as required.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2557685"></a>A Big Organization</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2557679"></a>A Big Organization</h4></div></div></div><p>
 		In this section we finally get to review in brief a Samba-3 configuration that
 		uses a Lightweight Directory Access (LDAP)-based authentication backend. The
 		main reasons for this choice are to provide the ability to host primary
 		and Backup Domain Control (BDC), as well as to enable a higher degree of
 		scalability to meet the needs of a very distributed environment.
-		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2557700"></a>The Primary Domain Controller</h5></div></div></div><p>
+		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2557694"></a>The Primary Domain Controller</h5></div></div></div><p>
 			This is an example of a minimal configuration to run a Samba-3 PDC
 			using an LDAP authentication backend. It is assumed that the operating system
 			has been correctly configured.
@@ -587,13 +587,13 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
 			distributions tend to install the Idealx scripts in the 
 			<code class="filename">/usr/share/doc/packages/sambaXXXXXX/examples/LDAP/smbldap-tools</code> directory.
 			Idealx scripts version <code class="constant">smbldap-tools-0.9.1</code> are known to work well.
-			</p><div class="procedure"><div class="example"><a name="fast-ldap"></a><p class="title"><b>Example�2.9.�LDAP backend smb.conf for PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2557926"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2557937"></a><em class="parameter"><code>netbios name = FRODO</code></em></td></tr><tr><td><a class="indexterm" name="id2557947"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2557958"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2557969"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2557980"></a><em class="parameter"><code>add user script = /usr/local/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2557991"></a><em class="parameter"><code>delete user script = /usr/local/sbin/smbldap-userdel %u</code></em></td></tr><tr><td><a class="indexterm" name="id2558003"></a><em class="parameter"><code>add group script = /usr/local/sbin/smbldap-groupadd -p '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558014"></a><em class="parameter"><code>delete group script = /usr/local/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558026"></a><em class="parameter"><code>add user to group script = /usr/local/sbin/smbldap-groupmod -m '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558037"></a><em class="parameter"><code>delete user from group script = /usr/local/sbin/smbldap-groupmod -x '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558050"></a><em class="parameter"><code>set primary group script = /usr/local/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2558062"></a><em class="parameter"><code>add machine script = /usr/local/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2558073"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2558084"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558095"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2558106"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558116"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558126"></a><em class="parameter"><code>os level = 35</code></em></td></tr><tr><td><a class="indexterm" name="id2558137"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558147"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558158"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558169"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558180"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558191"></a><em class="parameter"><code>ldap group suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558202"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558213"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558224"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2558235"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558245"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558255"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558266"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+			</p><div class="procedure"><div class="example"><a name="fast-ldap"></a><p class="title"><b>Example�2.9.�LDAP backend smb.conf for PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2557921"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2557931"></a><em class="parameter"><code>netbios name = FRODO</code></em></td></tr><tr><td><a class="indexterm" name="id2557942"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://localhost</code></em></td></tr><tr><td><a class="indexterm" name="id2557953"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2557964"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2557974"></a><em class="parameter"><code>add user script = /usr/local/sbin/smbldap-useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2557986"></a><em class="parameter"><code>delete user script = /usr/local/sbin/smbldap-userdel %u</code></em></td></tr><tr><td><a class="indexterm" name="id2557997"></a><em class="parameter"><code>add group script = /usr/local/sbin/smbldap-groupadd -p '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558009"></a><em class="parameter"><code>delete group script = /usr/local/sbin/smbldap-groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558020"></a><em class="parameter"><code>add user to group script = /usr/local/sbin/smbldap-groupmod -m '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558032"></a><em class="parameter"><code>delete user from group script = /usr/local/sbin/smbldap-groupmod -x '%u' '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2558044"></a><em class="parameter"><code>set primary group script = /usr/local/sbin/smbldap-usermod -g '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2558056"></a><em class="parameter"><code>add machine script = /usr/local/sbin/smbldap-useradd -w '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2558068"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2558079"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558090"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2558100"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558111"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558121"></a><em class="parameter"><code>os level = 35</code></em></td></tr><tr><td><a class="indexterm" name="id2558132"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558142"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558152"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558163"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558174"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558186"></a><em class="parameter"><code>ldap group suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558197"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558208"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558219"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2558229"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558240"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558250"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558260"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 				Obtain from the Samba sources <code class="filename">~/examples/LDAP/samba.schema</code>
 				and copy it to the <code class="filename">/etc/openldap/schema/</code> directory.
 				</p></li><li><p>
 				Set up the LDAP server. This example is suitable for OpenLDAP 2.1.x.
 				The <code class="filename">/etc/openldap/slapd.conf</code> file.
-				<a class="indexterm" name="id2557768"></a>
+				<a class="indexterm" name="id2557763"></a>
 <span style="color: red">&lt;title&gt;Example slapd.conf File&lt;/title&gt;</span>
 </p><pre class="screen">
 # Note commented out lines have been removed
@@ -629,7 +629,7 @@ index   default               sub
 </pre><p>
 				</p></li><li><p>
 				Create the following file <code class="filename">initdb.ldif</code>:
-				<a class="indexterm" name="id2557813"></a>
+				<a class="indexterm" name="id2557807"></a>
 </p><pre class="programlisting">
 # Organization for SambaXP Demo
 dn: dc=quenya,dc=org
@@ -684,11 +684,11 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb
 				Add users and groups as required. Users and groups added using Samba tools
 				will automatically be added to both the LDAP backend and the operating
 				system as required.
-				</p></li></ol></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2558316"></a>Backup Domain Controller</h5></div></div></div><p>
+				</p></li></ol></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2558311"></a>Backup Domain Controller</h5></div></div></div><p>
 			<a class="link" href="FastStart.html#fast-bdc" title="Example�2.10.�Remote LDAP BDC smb.conf">&#8220;Remote LDAP BDC smb.conf&#8221;</a> shows the example configuration for the BDC. Note that
 			the <code class="filename">smb.conf</code> file does not specify the smbldap-tools scripts  they are
 			not needed on a BDC. Add additional stanzas for shares and printers as required.
-			</p><div class="procedure"><div class="example"><a name="fast-bdc"></a><p class="title"><b>Example�2.10.�Remote LDAP BDC smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2558388"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2558398"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2558409"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2558420"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2558430"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2558441"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2558452"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558463"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2558473"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558484"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558494"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id2558505"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558515"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2558525"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558536"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558548"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558559"></a><em class="parameter"><code>ldap group suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558570"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558581"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558592"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2558602"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558613"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558623"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558634"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+			</p><div class="procedure"><div class="example"><a name="fast-bdc"></a><p class="title"><b>Example�2.10.�Remote LDAP BDC smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2558383"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2558393"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2558403"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2558415"></a><em class="parameter"><code>username map = /etc/samba/smbusers</code></em></td></tr><tr><td><a class="indexterm" name="id2558425"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2558436"></a><em class="parameter"><code>logon script = scripts\logon.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2558447"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558458"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2558468"></a><em class="parameter"><code>logon home = \\%L\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2558478"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558489"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id2558499"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558510"></a><em class="parameter"><code>domain master = No</code></em></td></tr><tr><td><a class="indexterm" name="id2558520"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558531"></a><em class="parameter"><code>ldap machine suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558542"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558553"></a><em class="parameter"><code>ldap group suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558564"></a><em class="parameter"><code>ldap idmap suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2558575"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2558587"></a><em class="parameter"><code>ldap ssl = no</code></em></td></tr><tr><td><a class="indexterm" name="id2558597"></a><em class="parameter"><code>ldap passwd sync = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2558607"></a><em class="parameter"><code>idmap uid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558618"></a><em class="parameter"><code>idmap gid = 15000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2558628"></a><em class="parameter"><code>printing = cups</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 				Decide if the BDC should have its own LDAP server or not. If the BDC is to be
 				the LDAP server, change the following <code class="filename">smb.conf</code> as indicated. The default
 				configuration in <a class="link" href="FastStart.html#fast-bdc" title="Example�2.10.�Remote LDAP BDC smb.conf">Remote LDAP BDC smb.conf</a>
diff --git a/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html b/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html
index 146db13c88..7f4ecc4dda 100644
--- a/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html
+++ b/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�19.�Interdomain Trust Relationships</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="securing-samba.html" title="Chapter�18.�Securing Samba"><link rel="next" href="msdfs.html" title="Chapter�20.�Hosting a Microsoft Distributed File System Tree"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�19.�Interdomain Trust Relationships</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="securing-samba.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="msdfs.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter�19.�Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Rafal</span> <span class="orgname">Samba Team</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:mimir@samba.org">mimir@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</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><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></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><code class="email">&lt;<a class="email" href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619731">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621195">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621208">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621254">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2619511"></a>
-<a class="indexterm" name="id2619518"></a>
-<a class="indexterm" name="id2619525"></a>
-<a class="indexterm" name="id2619532"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�19.�Interdomain Trust Relationships</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="securing-samba.html" title="Chapter�18.�Securing Samba"><link rel="next" href="msdfs.html" title="Chapter�20.�Hosting a Microsoft Distributed File System Tree"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�19.�Interdomain Trust Relationships</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="securing-samba.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="msdfs.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter�19.�Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Rafal</span> <span class="orgname">Samba Team</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:mimir@samba.org">mimir@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</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><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></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><code class="email">&lt;<a class="email" href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619759">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621231">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621243">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621289">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></div><p>
 <a class="indexterm" name="id2619539"></a>
 <a class="indexterm" name="id2619546"></a>
-<a class="indexterm" name="id2619552"></a>
-<a class="indexterm" name="id2619559"></a>
-<a class="indexterm" name="id2619566"></a>
+<a class="indexterm" name="id2619553"></a>
+<a class="indexterm" name="id2619560"></a>
+<a class="indexterm" name="id2619567"></a>
+<a class="indexterm" name="id2619574"></a>
+<a class="indexterm" name="id2619580"></a>
+<a class="indexterm" name="id2619587"></a>
+<a class="indexterm" name="id2619594"></a>
 Samba-3 supports NT4-style domain trust relationships. This is a feature that many sites
 will want to use if they migrate to Samba-3 from an NT4-style domain and do not want to
 adopt Active Directory or an LDAP-based authentication backend. This chapter explains
@@ -15,78 +15,78 @@ some background information regarding trust relationships and how to create them
 possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba-to-Samba 
 trusts.
 </p><p>
-<a class="indexterm" name="id2619584"></a>
-<a class="indexterm" name="id2619590"></a>
-<a class="indexterm" name="id2619597"></a>
-<a class="indexterm" name="id2619604"></a>
-<a class="indexterm" name="id2619611"></a>
+<a class="indexterm" name="id2619612"></a>
+<a class="indexterm" name="id2619618"></a>
+<a class="indexterm" name="id2619625"></a>
+<a class="indexterm" name="id2619632"></a>
+<a class="indexterm" name="id2619639"></a>
 The use of interdomain trusts requires use of <code class="literal">winbind</code>, so the
 <code class="literal">winbindd</code> daemon must be running. Winbind operation in this mode is
 dependent on the specification of a valid UID range and a valid GID range in the <code class="filename">smb.conf</code> file.
 These are specified respectively using:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619645"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2619657"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr></table><p>
-<a class="indexterm" name="id2619668"></a>
-<a class="indexterm" name="id2619675"></a>
-<a class="indexterm" name="id2619682"></a>
-<a class="indexterm" name="id2619689"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619673"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2619685"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr></table><p>
+<a class="indexterm" name="id2619696"></a>
+<a class="indexterm" name="id2619703"></a>
+<a class="indexterm" name="id2619710"></a>
+<a class="indexterm" name="id2619717"></a>
 The range of values specified must not overlap values used by the host operating system and must
 not overlap values used in the passdb backend for POSIX user accounts. The maximum value is
 limited by the upper-most value permitted by the host operating system. This is a UNIX kernel
 limited parameter. Linux kernel 2.6-based systems support a maximum value of 4294967295 
 (32-bit unsigned variable).
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2619707"></a>
-<a class="indexterm" name="id2619714"></a>
-<a class="indexterm" name="id2619721"></a>
+<a class="indexterm" name="id2619735"></a>
+<a class="indexterm" name="id2619742"></a>
+<a class="indexterm" name="id2619749"></a>
 The use of winbind is necessary only when Samba is the trusting domain, not when it is the
 trusted domain.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619731"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2619739"></a>
-<a class="indexterm" name="id2619746"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619759"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2619767"></a>
+<a class="indexterm" name="id2619774"></a>
 Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style
 trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4.
 </p><p>
-<a class="indexterm" name="id2619759"></a>
-<a class="indexterm" name="id2619766"></a>
-<a class="indexterm" name="id2619773"></a>
-<a class="indexterm" name="id2619780"></a>
 <a class="indexterm" name="id2619787"></a>
+<a class="indexterm" name="id2619794"></a>
+<a class="indexterm" name="id2619801"></a>
+<a class="indexterm" name="id2619808"></a>
+<a class="indexterm" name="id2619815"></a>
 Given that Samba-3 can function with a scalable backend authentication database such as LDAP, and given its
 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 trusts
 function, this system 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="id2619803"></a>Trust Relationship Background</h2></div></div></div><p>
-<a class="indexterm" name="id2619811"></a>
-<a class="indexterm" name="id2619818"></a>
-<a class="indexterm" name="id2619825"></a>
-<a class="indexterm" name="id2619832"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619831"></a>Trust Relationship Background</h2></div></div></div><p>
 <a class="indexterm" name="id2619839"></a>
 <a class="indexterm" name="id2619846"></a>
+<a class="indexterm" name="id2619853"></a>
+<a class="indexterm" name="id2619860"></a>
+<a class="indexterm" name="id2619867"></a>
+<a class="indexterm" name="id2619874"></a>
 MS Windows NT3/4-type security domains employ a nonhierarchical security structure.
 The limitations of this architecture as it effects the scalability of MS Windows networking
 in large organizations is well known. Additionally, the flat namespace that results from
 this design significantly impacts the delegation of administrative responsibilities in
 large and diverse organizations.
 </p><p>
-<a class="indexterm" name="id2619863"></a>
-<a class="indexterm" name="id2619869"></a>
-<a class="indexterm" name="id2619876"></a>
-<a class="indexterm" name="id2619883"></a>
-<a class="indexterm" name="id2619890"></a>
+<a class="indexterm" name="id2619891"></a>
+<a class="indexterm" name="id2619897"></a>
+<a class="indexterm" name="id2619904"></a>
+<a class="indexterm" name="id2619911"></a>
+<a class="indexterm" name="id2619918"></a>
 Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
 of circumventing the limitations of the older technologies. Not every organization is ready
 or willing to embrace ADS. For small companies the older NT4-style domain security paradigm
 is quite adequate, and so there remains an entrenched user base for whom there is no direct
 desire to go through a disruptive change to adopt ADS.
 </p><p>
-<a class="indexterm" name="id2619907"></a>
-<a class="indexterm" name="id2619914"></a>
-<a class="indexterm" name="id2619921"></a>
-<a class="indexterm" name="id2619928"></a>
-<a class="indexterm" name="id2619934"></a>
-<a class="indexterm" name="id2619941"></a>
-<a class="indexterm" name="id2619948"></a>
+<a class="indexterm" name="id2619935"></a>
+<a class="indexterm" name="id2619942"></a>
+<a class="indexterm" name="id2619949"></a>
+<a class="indexterm" name="id2619956"></a>
+<a class="indexterm" name="id2619962"></a>
+<a class="indexterm" name="id2619969"></a>
+<a class="indexterm" name="id2619976"></a>
 With Windows NT, Microsoft introduced the ability to allow different security domains
 to effect a mechanism so 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
@@ -97,41 +97,41 @@ is the trusting domain. With NT3.x/4.0 all trust relationships are always in one
 so if users in both domains are to have privileges and rights in each others' domain, then it is
 necessary to establish two relationships, one in each direction.
 </p><p>
-<a class="indexterm" name="id2619978"></a>
-<a class="indexterm" name="id2619985"></a>
-<a class="indexterm" name="id2619992"></a>
-<a class="indexterm" name="id2619999"></a>
-<a class="indexterm" name="id2620006"></a>
+<a class="indexterm" name="id2620014"></a>
+<a class="indexterm" name="id2620021"></a>
+<a class="indexterm" name="id2620028"></a>
+<a class="indexterm" name="id2620035"></a>
+<a class="indexterm" name="id2620041"></a>
 Further, in an NT4-style MS security domain, all trusts are nontransitive. This means that if there are three
 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.
 Relationships are explicit and not transitive.
 </p><p>
-<a class="indexterm" name="id2620022"></a>
-<a class="indexterm" name="id2620029"></a>
-<a class="indexterm" name="id2620036"></a>
-<a class="indexterm" name="id2620043"></a>
-<a class="indexterm" name="id2620050"></a>
-<a class="indexterm" name="id2620057"></a>
+<a class="indexterm" name="id2620058"></a>
 <a class="indexterm" name="id2620064"></a>
+<a class="indexterm" name="id2620071"></a>
+<a class="indexterm" name="id2620078"></a>
+<a class="indexterm" name="id2620085"></a>
+<a class="indexterm" name="id2620092"></a>
+<a class="indexterm" name="id2620099"></a>
 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, 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="id2620081"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2620088"></a>
-<a class="indexterm" name="id2620098"></a>
-<a class="indexterm" name="id2620105"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620117"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2620124"></a>
+<a class="indexterm" name="id2620133"></a>
+<a class="indexterm" name="id2620140"></a>
 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.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620117"></a>Creating an NT4 Domain Trust</h3></div></div></div><p>
-<a class="indexterm" name="id2620125"></a>
-<a class="indexterm" name="id2620132"></a>
-<a class="indexterm" name="id2620139"></a>
-<a class="indexterm" name="id2620146"></a>
-<a class="indexterm" name="id2620153"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620153"></a>Creating an NT4 Domain Trust</h3></div></div></div><p>
+<a class="indexterm" name="id2620161"></a>
+<a class="indexterm" name="id2620168"></a>
+<a class="indexterm" name="id2620175"></a>
+<a class="indexterm" name="id2620182"></a>
+<a class="indexterm" name="id2620189"></a>
 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
@@ -142,26 +142,26 @@ to enter the name of the remote domain that will be able to assign access rights
 your domain. You will also need to enter a password for this trust relationship, which the 
 trusting domain will use when authenticating users from the trusted domain.
 The password needs to be typed twice (for standard confirmation).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620214"></a>Completing an NT4 Domain Trust</h3></div></div></div><p>
-<a class="indexterm" name="id2620222"></a>
-<a class="indexterm" name="id2620229"></a>
-<a class="indexterm" name="id2620236"></a>
-<a class="indexterm" name="id2620243"></a>
-<a class="indexterm" name="id2620250"></a>
-<a class="indexterm" name="id2620257"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620250"></a>Completing an NT4 Domain Trust</h3></div></div></div><p>
+<a class="indexterm" name="id2620258"></a>
+<a class="indexterm" name="id2620265"></a>
+<a class="indexterm" name="id2620272"></a>
+<a class="indexterm" name="id2620279"></a>
+<a class="indexterm" name="id2620286"></a>
+<a class="indexterm" name="id2620292"></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 launches the
 Domain User Manager from the menu selects <span class="guilabel">Policies</span>, then select
 <span class="guilabel">Trust Relationships</span>, and clicks on the <span class="guibutton">Add</span> button
 next to the box that is labeled <span class="guilabel">Trusted Domains</span>. A panel opens 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="id2620299"></a>Interdomain Trust Facilities</h3></div></div></div><p>
-<a class="indexterm" name="id2620307"></a>
-<a class="indexterm" name="id2620314"></a>
-<a class="indexterm" name="id2620321"></a>
-<a class="indexterm" name="id2620328"></a>
-<a class="indexterm" name="id2620335"></a>
-<a class="indexterm" name="id2620342"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620335"></a>Interdomain Trust Facilities</h3></div></div></div><p>
+<a class="indexterm" name="id2620343"></a>
+<a class="indexterm" name="id2620350"></a>
+<a class="indexterm" name="id2620357"></a>
+<a class="indexterm" name="id2620364"></a>
+<a class="indexterm" name="id2620371"></a>
+<a class="indexterm" name="id2620378"></a>
 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:
@@ -201,26 +201,26 @@ DomA and DomB), the following facilities are created:
 	</p></li><li><p>
 	Global groups from the trusted domain can be made members in local groups on
 	MS Windows domain member machines.
-	</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620508"></a>Configuring Samba NT-Style Domain Trusts</h2></div></div></div><p>
-<a class="indexterm" name="id2620517"></a>
+	</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620544"></a>Configuring Samba NT-Style Domain Trusts</h2></div></div></div><p>
+<a class="indexterm" name="id2620552"></a>
 This description is meant to be a fairly short introduction about how to set up a Samba server so
 that it can participate in interdomain trust relationships. Trust relationship support in Samba
 is at an early stage, so do not be surprised if something does not function as it should.
 </p><p>
-<a class="indexterm" name="id2620532"></a>
-<a class="indexterm" name="id2620538"></a>
-<a class="indexterm" name="id2620545"></a>
-<a class="indexterm" name="id2620552"></a>
+<a class="indexterm" name="id2620567"></a>
+<a class="indexterm" name="id2620574"></a>
+<a class="indexterm" name="id2620581"></a>
+<a class="indexterm" name="id2620588"></a>
 Each of the procedures described next 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 in the following
 sections 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><p>
-<a class="indexterm" name="id2620580"></a>
-<a class="indexterm" name="id2620586"></a>
-<a class="indexterm" name="id2620593"></a>
-<a class="indexterm" name="id2620600"></a>
-<a class="indexterm" name="id2620607"></a>
+<a class="indexterm" name="id2620615"></a>
+<a class="indexterm" name="id2620622"></a>
+<a class="indexterm" name="id2620629"></a>
+<a class="indexterm" name="id2620636"></a>
+<a class="indexterm" name="id2620642"></a>
 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 <code class="literal">smbpasswd</code> utility. Creating the trusted domain account is 
@@ -239,19 +239,19 @@ where <code class="option">-a</code> means to add a new account into the
 passdb database and <code class="option">-i</code> means to &#8220;<span class="quote">create this
 account with the Interdomain trust flag</span>&#8221;.
 </p><p>
-<a class="indexterm" name="id2620676"></a>
-<a class="indexterm" name="id2620683"></a>
-<a class="indexterm" name="id2620690"></a>
-<a class="indexterm" name="id2620697"></a>
+<a class="indexterm" name="id2620712"></a>
+<a class="indexterm" name="id2620719"></a>
+<a class="indexterm" name="id2620726"></a>
+<a class="indexterm" name="id2620733"></a>
 The account name will be &#8220;<span class="quote">rumba$</span>&#8221; (the name of the remote domain).
 If this fails, you should check that the trust account has been added to the system
 password database (<code class="filename">/etc/passwd</code>). If it has not been added, you
 can add it manually and then repeat the previous step.
 </p><p>
-<a class="indexterm" name="id2620721"></a>
-<a class="indexterm" name="id2620728"></a>
-<a class="indexterm" name="id2620735"></a>
-<a class="indexterm" name="id2620742"></a>
+<a class="indexterm" name="id2620757"></a>
+<a class="indexterm" name="id2620763"></a>
+<a class="indexterm" name="id2620770"></a>
+<a class="indexterm" name="id2620777"></a>
 After issuing this command, you will 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
@@ -259,47 +259,47 @@ appropriate for your configuration) and see that the account's name is really RU
 &#8220;<span class="quote">I</span>&#8221; flag set in the flags field. Now you are ready to confirm the trust by establishing it from
 Windows NT Server.
 </p><p>
-<a class="indexterm" name="id2620764"></a>
-<a class="indexterm" name="id2620771"></a>
-<a class="indexterm" name="id2620778"></a>
-<a class="indexterm" name="id2620785"></a>
-<a class="indexterm" name="id2620792"></a>
+<a class="indexterm" name="id2620800"></a>
+<a class="indexterm" name="id2620807"></a>
+<a class="indexterm" name="id2620814"></a>
+<a class="indexterm" name="id2620821"></a>
+<a class="indexterm" name="id2620828"></a>
 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>.  Beside the <span class="guilabel">Trusted domains</span> list box,
 click 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.  Click on <span class="guibutton">OK</span> and, if everything went without incident, you
 will see the <code class="computeroutput">Trusted domain relationship successfully established</code> message.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620849"></a>Samba as the Trusting Domain</h3></div></div></div><p>
-<a class="indexterm" name="id2620858"></a>
-<a class="indexterm" name="id2620865"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620885"></a>Samba as the Trusting Domain</h3></div></div></div><p>
+<a class="indexterm" name="id2620893"></a>
+<a class="indexterm" name="id2620900"></a>
 This time activities are somewhat reversed. Again, we'll assume that your domain
 controlled by the Samba PDC is called SAMBA and the 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><p>
-<a class="indexterm" name="id2620882"></a>
-<a class="indexterm" name="id2620889"></a>
-<a class="indexterm" name="id2620896"></a>
+<a class="indexterm" name="id2620918"></a>
+<a class="indexterm" name="id2620925"></a>
+<a class="indexterm" name="id2620932"></a>
 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">Trusting 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>
-<a class="indexterm" name="id2620939"></a>
-<a class="indexterm" name="id2620945"></a>
+<a class="indexterm" name="id2620974"></a>
+<a class="indexterm" name="id2620981"></a>
 The password can be arbitrarily chosen. It is easy to change the password from the Samba server whenever you
 want. After you confirm the password, your account is ready for use. Now its Samba's turn.
 </p><p>
 Using your favorite shell while logged in as root, issue this command:
-<a class="indexterm" name="id2620960"></a>
+<a class="indexterm" name="id2620996"></a>
 </p><p>
 <code class="prompt">root# </code><strong class="userinput"><code>net rpc trustdom establish rumba</code></strong>
 </p><p>
-<a class="indexterm" name="id2620989"></a>
-<a class="indexterm" name="id2620996"></a>
-<a class="indexterm" name="id2621003"></a>
+<a class="indexterm" name="id2621024"></a>
+<a class="indexterm" name="id2621031"></a>
+<a class="indexterm" name="id2621038"></a>
 You will be prompted for the password you just typed on your Windows NT4 Server box.
 An error message, <code class="literal">"NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT,"</code>
 that may be reported periodically is of no concern and may safely be ignored.
@@ -311,20 +311,20 @@ relationship has just been established.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 You have to run this command as root because you must have write access to
 the <code class="filename">secrets.tdb</code> file.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621046"></a>NT4-Style Domain Trusts with Windows 2000</h2></div></div></div><p>
-<a class="indexterm" name="id2621054"></a>
-<a class="indexterm" name="id2621061"></a>
-<a class="indexterm" name="id2621068"></a>
-<a class="indexterm" name="id2621075"></a>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621081"></a>NT4-Style Domain Trusts with Windows 2000</h2></div></div></div><p>
+<a class="indexterm" name="id2621090"></a>
+<a class="indexterm" name="id2621097"></a>
+<a class="indexterm" name="id2621104"></a>
+<a class="indexterm" name="id2621110"></a>
 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>
-<a class="indexterm" name="id2621096"></a>
-<a class="indexterm" name="id2621103"></a>
-<a class="indexterm" name="id2621110"></a>
-<a class="indexterm" name="id2621117"></a>
+<a class="indexterm" name="id2621132"></a>
+<a class="indexterm" name="id2621139"></a>
+<a class="indexterm" name="id2621146"></a>
+<a class="indexterm" name="id2621152"></a>
 After <a class="link" href="InterdomainTrusts.html#samba-trusted-domain" title="Samba as the Trusted Domain">creating the interdomain trust account on the Samba server</a>
 as described previously, 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
@@ -338,11 +338,11 @@ Press this button and, just as with NT4, you will be prompted for the trusted do
 password. Press <span class="emphasis"><em>OK</em></span> and after a moment, Active Directory will respond with
 <code class="computeroutput">The trusted domain has been added and the trust has been verified.</code> Your
 Samba users can now be granted access 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="id2621195"></a>Common Errors</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621231"></a>Common Errors</h2></div></div></div><p>
 Interdomain trust relationships should not be attempted on networks that are unstable
 or that suffer regular outages. Network stability and integrity are key concerns with
 distributed trusted domains.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621208"></a>Browsing of Trusted Domain Fails</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621243"></a>Browsing of Trusted Domain Fails</h3></div></div></div><p>
 <span class="emphasis"><em>Browsing from a machine in a trusted Windows 200x domain to a Windows 200x member of
 a trusting Samba domain, I get the following error:</em></span>
 </p><pre class="screen">
@@ -360,7 +360,7 @@ seems to be fine. By default, when you unjoin a domain (the Windows 200x
 domain), the computer tries to automatically disable the computer account in 
 the domain.  If you are running as an account that has privileges to do this 
 when you unjoin the machine, it is done; otherwise it is not done.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621254"></a>Problems with LDAP ldapsam and Older Versions of smbldap-tools</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621289"></a>Problems with LDAP ldapsam and Older Versions of smbldap-tools</h3></div></div></div><p>
 If you use the <code class="literal">smbldap-useradd</code> script to create a trust
 account to set up interdomain trusts, the process of setting up the trust will
 fail. The account that was created in the LDAP database will have an account
diff --git a/docs/htmldocs/Samba3-HOWTO/IntroSMB.html b/docs/htmldocs/Samba3-HOWTO/IntroSMB.html
index a181d5071e..046336ffd7 100644
--- a/docs/htmldocs/Samba3-HOWTO/IntroSMB.html
+++ b/docs/htmldocs/Samba3-HOWTO/IntroSMB.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Introduction</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="TOSHpreface.html" title="Preface"><link rel="next" href="introduction.html" title="Part�I.�General Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="TOSHpreface.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="introduction.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Introduction</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 29, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="IntroSMB.html#id2551356">What Is Samba?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2498869">Why This Book?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2551652">Book Structure and Layout</a></span></dt></dl></div><p>&#8220;<span class="quote">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Introduction</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="TOSHpreface.html" title="Preface"><link rel="next" href="introduction.html" title="Part�I.�General Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="TOSHpreface.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="introduction.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Introduction</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 29, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="IntroSMB.html#id2551351">What Is Samba?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2498862">Why This Book?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2551647">Book Structure and Layout</a></span></dt></dl></div><p>&#8220;<span class="quote">
 A man's gift makes room for him before great men. Gifts are like hooks that can catch
 hold of the mind taking it beyond the reach of forces that otherwise might constrain it.
 </span>&#8221; --- Anon.
@@ -15,7 +15,7 @@ that it is hard to find the information they think they need. So if you are a
 Microsoft certified specialist, this book should meet your needs rather well.
 If you are a UNIX or Linux administrator, there is no need to feel badly  you
 should have no difficulty finding answers to your current concerns also.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551356"></a>What Is Samba?</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551351"></a>What Is Samba?</h2></div></div></div><p>
 	Samba is a big, complex project. The Samba project is ambitious and exciting.
 	The team behind Samba is a group of some thirty individuals who are spread
 	the world over and come from an interesting range of backgrounds. This team
@@ -45,7 +45,7 @@ should have no difficulty finding answers to your current concerns also.
 	be done. User feedback drives Samba development. Samba-3 in particular incorporates
 	a huge amount of work done as a result of user requests, suggestions and direct
 	code contributions.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498869"></a>Why This Book?</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2498862"></a>Why This Book?</h2></div></div></div><p>
 	There is admittedly a large number of Samba books on the market today and
 	each book has its place. Despite the apparent plethora of books, Samba
 	as a project continues to receive much criticism for failing to provide
@@ -97,7 +97,7 @@ should have no difficulty finding answers to your current concerns also.
 	are very different from that of the UNIX administrator. This book has been
 	arranged and the information presented from the perspective of someone with previous
 	Microsoft Windows network administrative training and experience.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551652"></a>Book Structure and Layout</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551647"></a>Book Structure and Layout</h2></div></div></div><p>
 	This book is presented in six parts:
 	</p><div class="variablelist"><dl><dt><span class="term">General Installation</span></dt><dd><p>
 			Designed to help you get Samba-3 running quickly.
diff --git a/docs/htmldocs/Samba3-HOWTO/NT4Migration.html b/docs/htmldocs/Samba3-HOWTO/NT4Migration.html
index 9d24ee1e26..a20e9eb07f 100644
--- a/docs/htmldocs/Samba3-HOWTO/NT4Migration.html
+++ b/docs/htmldocs/Samba3-HOWTO/NT4Migration.html
@@ -1,37 +1,37 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba"><link rel="next" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrading-to-3.0.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="SWAT.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NT4Migration.html#id2678914">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2678949">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2679885">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680120">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680206">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2678898"></a>
-<a class="indexterm" name="id2678904"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba"><link rel="next" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrading-to-3.0.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="SWAT.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NT4Migration.html#id2679067">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2679102">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680047">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680282">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680369">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2679050"></a>
+<a class="indexterm" name="id2679057"></a>
 This is a rough guide to assist those wishing to migrate from NT4 domain control to
 Samba-3-based domain control.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2678914"></a>Planning and Getting Started</h2></div></div></div><p>
-<a class="indexterm" name="id2678922"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2679067"></a>Planning and Getting Started</h2></div></div></div><p>
+<a class="indexterm" name="id2679075"></a>
 In the IT world there is often a saying that all problems are encountered because of
 poor planning. The corollary to this saying is that not all problems can be anticipated
 and planned for. Then again, good planning will anticipate most show-stopper-type situations.
 </p><p>
-<a class="indexterm" name="id2678937"></a>
+<a class="indexterm" name="id2679090"></a>
 Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
 environment would do well to develop a detailed migration plan. So here are a few pointers to
 help migration get underway.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2678949"></a>Objectives</h3></div></div></div><p>
-<a class="indexterm" name="id2678957"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2679102"></a>Objectives</h3></div></div></div><p>
+<a class="indexterm" name="id2679109"></a>
 The key objective for most organizations is to make the migration from MS Windows NT4 
 to Samba-3 domain control as painless as possible. One of the challenges you may experience
 in your migration process may well be convincing management that the new environment
 should remain in place. Many who have introduced open source technologies have experienced
 pressure to return to a Microsoft-based platform solution at the first sign of trouble. 
 </p><p>
-<a class="indexterm" name="id2678974"></a>
+<a class="indexterm" name="id2679127"></a>
 Before attempting a migration to a Samba-3-controlled network, make every possible effort to
 gain all-round commitment to the change. Know precisely <span class="emphasis"><em>why</em></span> the change
 is important for the organization. Possible motivations to make a change include:
-</p><a class="indexterm" name="id2678990"></a><a class="indexterm" name="id2678997"></a><a class="indexterm" name="id2679004"></a><a class="indexterm" name="id2679011"></a><a class="indexterm" name="id2679018"></a><div class="itemizedlist"><ul type="disc"><li><p>Improve network manageability.</p></li><li><p>Obtain better user-level functionality.</p></li><li><p>Reduce network operating costs.</p></li><li><p>Reduce exposure caused by Microsoft withdrawal of NT4 support.</p></li><li><p>Avoid MS License 6 implications.</p></li><li><p>Reduce organization's dependency on Microsoft.</p></li></ul></div><p>
-<a class="indexterm" name="id2679061"></a>
-<a class="indexterm" name="id2679068"></a>
-<a class="indexterm" name="id2679075"></a>
-<a class="indexterm" name="id2679082"></a>
-<a class="indexterm" name="id2679088"></a>
-<a class="indexterm" name="id2679095"></a>
+</p><a class="indexterm" name="id2679143"></a><a class="indexterm" name="id2679150"></a><a class="indexterm" name="id2679157"></a><a class="indexterm" name="id2679164"></a><a class="indexterm" name="id2679171"></a><div class="itemizedlist"><ul type="disc"><li><p>Improve network manageability.</p></li><li><p>Obtain better user-level functionality.</p></li><li><p>Reduce network operating costs.</p></li><li><p>Reduce exposure caused by Microsoft withdrawal of NT4 support.</p></li><li><p>Avoid MS License 6 implications.</p></li><li><p>Reduce organization's dependency on Microsoft.</p></li></ul></div><p>
+<a class="indexterm" name="id2679214"></a>
+<a class="indexterm" name="id2679221"></a>
+<a class="indexterm" name="id2679227"></a>
+<a class="indexterm" name="id2679234"></a>
+<a class="indexterm" name="id2679241"></a>
+<a class="indexterm" name="id2679248"></a>
 Make sure everyone knows that Samba-3 is not MS Windows NT4. Samba-3 offers
 an alternative solution that is both different from MS Windows NT4 and offers 
 advantages compared with it. Gain recognition that Samba-3 lacks many of the
@@ -39,32 +39,32 @@ features that Microsoft has promoted as core values in migration from MS Windows
 MS Windows 2000 and beyond (with or without Active Directory services).
 </p><p>
 What are the features that Samba-3 cannot provide?
-</p><a class="indexterm" name="id2679114"></a><a class="indexterm" name="id2679121"></a><a class="indexterm" name="id2679128"></a><a class="indexterm" name="id2679135"></a><a class="indexterm" name="id2679142"></a><div class="itemizedlist"><ul type="disc"><li><p>Active Directory Server.</p></li><li><p>Group Policy Objects (in Active Directory).</p></li><li><p>Machine Policy Objects.</p></li><li><p>Logon Scripts in Active Directory.</p></li><li><p>Software Application and Access Controls in Active Directory.</p></li></ul></div><p>
+</p><a class="indexterm" name="id2679266"></a><a class="indexterm" name="id2679273"></a><a class="indexterm" name="id2679280"></a><a class="indexterm" name="id2679288"></a><a class="indexterm" name="id2679294"></a><div class="itemizedlist"><ul type="disc"><li><p>Active Directory Server.</p></li><li><p>Group Policy Objects (in Active Directory).</p></li><li><p>Machine Policy Objects.</p></li><li><p>Logon Scripts in Active Directory.</p></li><li><p>Software Application and Access Controls in Active Directory.</p></li></ul></div><p>
 The features that Samba-3 does provide and that may be of compelling interest to your site
 include:
-</p><a class="indexterm" name="id2679182"></a><a class="indexterm" name="id2679189"></a><a class="indexterm" name="id2679196"></a><a class="indexterm" name="id2679203"></a><a class="indexterm" name="id2679210"></a><a class="indexterm" name="id2679217"></a><a class="indexterm" name="id2679224"></a><a class="indexterm" name="id2679231"></a><a class="indexterm" name="id2679237"></a><a class="indexterm" name="id2679244"></a><a class="indexterm" name="id2679251"></a><a class="indexterm" name="id2679258"></a><a class="indexterm" name="id2679265"></a><a class="indexterm" name="id2679272"></a><a class="indexterm" name="id2679279"></a><div class="itemizedlist"><ul type="disc"><li><p>Lower cost of ownership.</p></li><li><p>Global availability of support with no strings attached.</p></li><li><p>Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).</p></li><li><p>Creation of on-the-fly logon scripts.</p></li><li><p>Creation of on-the-fly policy files.</p></li><li><p>Greater stability, reliability, performance, and availability.</p></li><li><p>Manageability via an SSH connection.</p></li><li><p>Flexible choices of backend authentication technologies (tdbsam, ldapsam).</p></li><li><p>Ability to implement a full single-sign-on architecture.</p></li><li><p>Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.</p></li></ul></div><p>
-<a class="indexterm" name="id2679345"></a>
+</p><a class="indexterm" name="id2679335"></a><a class="indexterm" name="id2679342"></a><a class="indexterm" name="id2679349"></a><a class="indexterm" name="id2679356"></a><a class="indexterm" name="id2679363"></a><a class="indexterm" name="id2679370"></a><a class="indexterm" name="id2679376"></a><a class="indexterm" name="id2679383"></a><a class="indexterm" name="id2679390"></a><a class="indexterm" name="id2679397"></a><a class="indexterm" name="id2679404"></a><a class="indexterm" name="id2679411"></a><a class="indexterm" name="id2679418"></a><a class="indexterm" name="id2679425"></a><a class="indexterm" name="id2679432"></a><div class="itemizedlist"><ul type="disc"><li><p>Lower cost of ownership.</p></li><li><p>Global availability of support with no strings attached.</p></li><li><p>Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).</p></li><li><p>Creation of on-the-fly logon scripts.</p></li><li><p>Creation of on-the-fly policy files.</p></li><li><p>Greater stability, reliability, performance, and availability.</p></li><li><p>Manageability via an SSH connection.</p></li><li><p>Flexible choices of backend authentication technologies (tdbsam, ldapsam).</p></li><li><p>Ability to implement a full single-sign-on architecture.</p></li><li><p>Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.</p></li></ul></div><p>
+<a class="indexterm" name="id2679498"></a>
 Before migrating a network from MS Windows NT4 to Samba-3, consider all necessary factors. Users
 should be educated about changes they may experience so the change will be a welcome one
 and not become an obstacle to the work they need to do. The following sections explain factors that will 
 help ensure a successful migration.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679359"></a>Domain Layout</h4></div></div></div><p>
-<a class="indexterm" name="id2679367"></a>
-<a class="indexterm" name="id2679374"></a>
-<a class="indexterm" name="id2679381"></a>
-<a class="indexterm" name="id2679388"></a>
-<a class="indexterm" name="id2679395"></a>
-<a class="indexterm" name="id2679402"></a>
-<a class="indexterm" name="id2679408"></a>
-<a class="indexterm" name="id2679415"></a>
-<a class="indexterm" name="id2679422"></a>
-<a class="indexterm" name="id2679429"></a>
-<a class="indexterm" name="id2679436"></a>
-<a class="indexterm" name="id2679443"></a>
-<a class="indexterm" name="id2679450"></a>
-<a class="indexterm" name="id2679457"></a>
-<a class="indexterm" name="id2679464"></a>
-<a class="indexterm" name="id2679470"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679511"></a>Domain Layout</h4></div></div></div><p>
+<a class="indexterm" name="id2679519"></a>
+<a class="indexterm" name="id2679526"></a>
+<a class="indexterm" name="id2679533"></a>
+<a class="indexterm" name="id2679540"></a>
+<a class="indexterm" name="id2679547"></a>
+<a class="indexterm" name="id2679554"></a>
+<a class="indexterm" name="id2679561"></a>
+<a class="indexterm" name="id2679568"></a>
+<a class="indexterm" name="id2679575"></a>
+<a class="indexterm" name="id2679581"></a>
+<a class="indexterm" name="id2679588"></a>
+<a class="indexterm" name="id2679595"></a>
+<a class="indexterm" name="id2679602"></a>
+<a class="indexterm" name="id2679609"></a>
+<a class="indexterm" name="id2679616"></a>
+<a class="indexterm" name="id2679623"></a>
 Samba-3 can be configured as a domain controller, a backup domain controller (probably best called
 a secondary controller), a domain member, or a standalone server. The Windows network security
 domain context should be sized and scoped before implementation. Particular attention needs to be
@@ -74,36 +74,36 @@ authentication backend, then the same database can be used by several different
 complex organization, there can be a single LDAP database, which itself can be distributed (have
 a master server and multiple slave servers) that can simultaneously serve multiple domains.
 </p><p>
-<a class="indexterm" name="id2679494"></a>
+<a class="indexterm" name="id2679646"></a>
 From a design perspective, the number of users per server as well as the number of servers per
 domain should be scaled taking into consideration server capacity and network bandwidth.
 </p><p>
-<a class="indexterm" name="id2679507"></a>
-<a class="indexterm" name="id2679514"></a>
-<a class="indexterm" name="id2679521"></a>
-<a class="indexterm" name="id2679528"></a>
-<a class="indexterm" name="id2679535"></a>
-<a class="indexterm" name="id2679541"></a>
+<a class="indexterm" name="id2679660"></a>
+<a class="indexterm" name="id2679666"></a>
+<a class="indexterm" name="id2679674"></a>
+<a class="indexterm" name="id2679680"></a>
+<a class="indexterm" name="id2679687"></a>
+<a class="indexterm" name="id2679694"></a>
 A physical network segment may house several domains. Each may span multiple network segments.
 Where domains span routed network segments, consider and test the performance implications of
 the design and layout of a network. A centrally located domain controller that is designed to
 serve multiple routed network segments may result in severe performance problems. Check the
 response time (ping timing) between the remote segment and the PDC. If it's long (more than 100 ms),
 locate a BDC on the remote segment to serve as the local authentication and access control server.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679560"></a>Server Share and Directory Layout</h4></div></div></div><p>
-<a class="indexterm" name="id2679568"></a>
-<a class="indexterm" name="id2679575"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679713"></a>Server Share and Directory Layout</h4></div></div></div><p>
+<a class="indexterm" name="id2679721"></a>
+<a class="indexterm" name="id2679728"></a>
 There are cardinal rules to effective network design that cannot be broken with impunity.
 The most important rule: Simplicity is king in every well-controlled network. Every part of
 the infrastructure must be managed; the more complex it is, the greater will be the demand
 of keeping systems secure and functional.
 </p><p>
-<a class="indexterm" name="id2679591"></a>
-<a class="indexterm" name="id2679598"></a>
-<a class="indexterm" name="id2679604"></a>
-<a class="indexterm" name="id2679611"></a>
-<a class="indexterm" name="id2679618"></a>
-<a class="indexterm" name="id2679625"></a>
+<a class="indexterm" name="id2679743"></a>
+<a class="indexterm" name="id2679750"></a>
+<a class="indexterm" name="id2679757"></a>
+<a class="indexterm" name="id2679764"></a>
+<a class="indexterm" name="id2679771"></a>
+<a class="indexterm" name="id2679778"></a>
 Keep in mind the nature of how data must be shared. Physical disk space layout should be considered
 carefully. Some data must be backed up. The simpler the disk layout, the easier it will be to
 keep track of backup needs. Identify what backup media will meet your needs; consider backup to tape,
@@ -111,18 +111,18 @@ CD-ROM or DVD-ROM, or other offline storage medium. Plan and implement for minim
 maintenance. Leave nothing to chance in your design; above all, do not leave backups to chance:
 backup, test, and validate every backup; create a disaster recovery plan and prove that it works.
 </p><p>
-<a class="indexterm" name="id2679645"></a>
-<a class="indexterm" name="id2679652"></a>
-<a class="indexterm" name="id2679659"></a>
+<a class="indexterm" name="id2679807"></a>
+<a class="indexterm" name="id2679814"></a>
+<a class="indexterm" name="id2679821"></a>
 Users should be grouped according to data access control needs. File and directory access 
 is best controlled via group permissions, and the use of the &#8220;<span class="quote">sticky bit</span>&#8221; on group-controlled
 directories may substantially avoid file access complaints from Samba share users.
 </p><p>
-<a class="indexterm" name="id2679677"></a>
-<a class="indexterm" name="id2679684"></a>
-<a class="indexterm" name="id2679691"></a>
-<a class="indexterm" name="id2679698"></a>
-<a class="indexterm" name="id2679705"></a>
+<a class="indexterm" name="id2679839"></a>
+<a class="indexterm" name="id2679846"></a>
+<a class="indexterm" name="id2679853"></a>
+<a class="indexterm" name="id2679860"></a>
+<a class="indexterm" name="id2679867"></a>
 Inexperienced  network administrators often attempt elaborate techniques to set access
 controls on files, directories, shares, as well as in share definitions.
 Keep your design and implementation simple and document your design extensively. Have others
@@ -131,8 +131,8 @@ Remember, job security through complex design and implementation may cause loss
 and downtime to users as the new administrator learns to untangle your knots. Keep access
 controls simple and effective, and make sure that users will never be interrupted by obtuse
 complexity.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679725"></a>Logon Scripts</h4></div></div></div><p>
-<a class="indexterm" name="id2679733"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679887"></a>Logon Scripts</h4></div></div></div><p>
+<a class="indexterm" name="id2679895"></a>
 Logon scripts can help to ensure that all users gain the share and printer connections they need.
 </p><p>
 Logon scripts can be created on the fly so all commands executed are specific to the
@@ -140,55 +140,55 @@ rights and privileges granted to the user. The preferred controls should be effe
 group membership so group information can be used to create a custom logon script using
 the <a class="link" href="smb.conf.5.html#ROOTPREEXEC" target="_top">root preexec</a> parameters to the <em class="parameter"><code>NETLOGON</code></em> share.
 </p><p>
-<a class="indexterm" name="id2679771"></a>
+<a class="indexterm" name="id2679934"></a>
 Some sites prefer to use a tool such as <code class="literal">kixstart</code> to establish a controlled
 user environment. In any case, you may wish to do a Google search for logon script process controls.
 In particular, you may wish to explore the use of the Microsoft Knowledge Base article KB189105 that
 deals with how to add printers without user intervention via the logon script process.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679791"></a>Profile Migration/Creation</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679954"></a>Profile Migration/Creation</h4></div></div></div><p>
 User and group profiles may be migrated using the tools described in the section titled Desktop Profile
 Management.
 </p><p>
-<a class="indexterm" name="id2679805"></a>
-<a class="indexterm" name="id2679811"></a>
+<a class="indexterm" name="id2679967"></a>
+<a class="indexterm" name="id2679974"></a>
 Profiles may also be managed using the Samba-3 tool <code class="literal">profiles</code>. This tool allows the MS
 Windows NT-style security identifiers (SIDs) that are stored inside the profile
 <code class="filename">NTuser.DAT</code> file to be changed to the SID of the Samba-3 domain.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679836"></a>User and Group Accounts</h4></div></div></div><p>
-<a class="indexterm" name="id2679844"></a>
-<a class="indexterm" name="id2679851"></a>
-<a class="indexterm" name="id2679858"></a>
-<a class="indexterm" name="id2679865"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2679998"></a>User and Group Accounts</h4></div></div></div><p>
+<a class="indexterm" name="id2680006"></a>
+<a class="indexterm" name="id2680013"></a>
+<a class="indexterm" name="id2680020"></a>
+<a class="indexterm" name="id2680027"></a>
 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
 attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba-3 the
 groups that are present on the MS Windows NT4 domain <span class="emphasis"><em>AND</em></span> to map them to
 suitable UNIX/Linux groups. By following this simple advice, all user and group attributes
 should migrate painlessly.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2679885"></a>Steps in Migration Process</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680047"></a>Steps in Migration Process</h3></div></div></div><p>
 The approximate migration process is described below.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 	You have an NT4 PDC that has the users, groups, policies, and profiles to be migrated.
 	</p></li><li><p>
-<a class="indexterm" name="id2679906"></a>
-<a class="indexterm" name="id2679913"></a>
-<a class="indexterm" name="id2679920"></a>
+<a class="indexterm" name="id2680068"></a>
+<a class="indexterm" name="id2680075"></a>
+<a class="indexterm" name="id2680082"></a>
 	Samba-3 is set up as a domain controller with netlogon share, profile share, and so on. Configure the <code class="filename">smb.conf</code> file
 	to function as a BDC: <em class="parameter"><code>domain master = No</code></em>.
-	</p></li></ul></div><div class="procedure"><a name="id2679943"></a><p class="title"><b>Procedure�36.1.�The Account Migration Process</b></p><a class="indexterm" name="id2680031"></a><ol type="1"><li><p>
-	<a class="indexterm" name="id2679954"></a>
+	</p></li></ul></div><div class="procedure"><a name="id2680105"></a><p class="title"><b>Procedure�36.1.�The Account Migration Process</b></p><a class="indexterm" name="id2680193"></a><ol type="1"><li><p>
+	<a class="indexterm" name="id2680116"></a>
 	Create a BDC account in the old NT4 domain for the Samba server using NT Server Manager.
 	<span class="emphasis"><em>Samba must not be running.</em></span>
 	</p></li><li><p>
-	<a class="indexterm" name="id2679973"></a>
+	<a class="indexterm" name="id2680135"></a>
 	<strong class="userinput"><code>net rpc join -S <em class="replaceable"><code>NT4PDC</code></em> -w <em class="replaceable"><code>DOMNAME</code></em> -U
 	Administrator%<em class="replaceable"><code>passwd</code></em></code></strong>
 	</p></li><li><p>
-<a class="indexterm" name="id2680006"></a>
+<a class="indexterm" name="id2680169"></a>
 	<strong class="userinput"><code>net rpc vampire -S <em class="replaceable"><code>NT4PDC</code></em> -U 
 	administrator%<em class="replaceable"><code>passwd</code></em></code></strong>
 	</p></li><li><p><strong class="userinput"><code>pdbedit -L</code></strong></p><p>Note: Did the users migrate?</p></li><li><p>
-	<a class="indexterm" name="id2680058"></a>
-	<a class="indexterm" name="id2680067"></a>
+	<a class="indexterm" name="id2680220"></a>
+	<a class="indexterm" name="id2680229"></a>
 	Now assign each of the UNIX groups to NT groups:
 	(It may be useful to copy this text to a script called <code class="filename">initGroups.sh</code>)
 	</p><pre class="programlisting">
@@ -208,11 +208,11 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
 	</p></li><li><p><strong class="userinput"><code>net groupmap list</code></strong></p><p>Check that all groups are recognized.
 	</p></li></ol></div><p>
 Migrate all the profiles, then migrate all policy files.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680120"></a>Migration Options</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680282"></a>Migration Options</h2></div></div></div><p>
 Sites that wish to migrate from MS Windows NT4 domain control to a Samba-based solution
 generally fit into three basic categories. <a class="link" href="NT4Migration.html#majtypes" title="Table�36.1.�The Three Major Site Types">Following table</a> shows the possibilities.
 </p><div class="table"><a name="majtypes"></a><p class="title"><b>Table�36.1.�The Three Major Site Types</b></p><div class="table-contents"><table summary="The Three Major Site Types" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Number of Users</th><th align="justify">Description</th></tr></thead><tbody><tr><td align="left">&lt; 50</td><td align="justify"><p>Want simple conversion with no pain.</p></td></tr><tr><td align="left">50 - 250</td><td align="justify"><p>Want new features; can manage some inhouse complexity.</p></td></tr><tr><td align="left">&gt; 250</td><td align="justify"><p>Solution/implementation must scale well; complex needs.
-		Cross-departmental decision process. Local expertise in most areas.</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680206"></a>Planning for Success</h3></div></div></div><p>
+		Cross-departmental decision process. Local expertise in most areas.</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680369"></a>Planning for Success</h3></div></div></div><p>
 There are three basic choices for sites that intend to migrate from MS Windows NT4
 to Samba-3:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -233,31 +233,31 @@ Minimize downstream problems by:
 	Testing the full roll-out program, including workstation deployment.
 	</p></li></ul></div><p><a class="link" href="NT4Migration.html#natconchoices" title="Table�36.2.�Nature of the Conversion Choices">Following table</a> lists the conversion choices given the type of migration
 being contemplated.
-</p><div class="table"><a name="natconchoices"></a><p class="title"><b>Table�36.2.�Nature of the Conversion Choices</b></p><div class="table-contents"><table summary="Nature of the Conversion Choices" border="1"><colgroup><col align="justify"><col align="justify"><col align="justify"></colgroup><thead><tr><th align="justify">Simple Install</th><th align="justify">Upgrade Decisions</th><th align="justify">Redesign Decisions</th></tr></thead><tbody><tr><td align="justify"><p>Make use of minimal OS-specific features</p></td><td align="justify"><p>Translate NT4 features to new host OS features</p></td><td align="justify"><p>Improve on NT4 functionality, enhance management capabilities</p></td></tr><tr><td align="justify"><p>Move all accounts from NT4 into Samba-3</p></td><td align="justify"><p>Copy and improve</p></td><td align="justify"><p>Authentication regime (database location and access)</p></td></tr><tr><td align="justify"><p>Make least number of operational changes</p></td><td align="justify"><p>Make progressive improvements</p></td><td align="justify"><p>Desktop management methods</p></td></tr><tr><td align="justify"><p>Take least amount of time to migrate</p></td><td align="justify"><p>Minimize user impact</p></td><td align="justify"><p>Better control of Desktops/Users</p></td></tr><tr><td align="justify"><p>Live versus isolated conversion</p></td><td align="justify"><p>Maximize functionality</p></td><td align="justify"><p>Identify Needs for: <span class="emphasis"><em>Manageability, Scalability, Security, Availability</em></span></p></td></tr><tr><td align="justify"><p>Integrate Samba-3, then migrate while users are active, then change of control (swap out)</p></td><td align="justify"><p>Take advantage of lower maintenance opportunity</p></td><td align="justify"><p></p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680440"></a>Samba-3 Implementation Choices</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Authentication Database/Backend</span></dt><dd><p>
+</p><div class="table"><a name="natconchoices"></a><p class="title"><b>Table�36.2.�Nature of the Conversion Choices</b></p><div class="table-contents"><table summary="Nature of the Conversion Choices" border="1"><colgroup><col align="justify"><col align="justify"><col align="justify"></colgroup><thead><tr><th align="justify">Simple Install</th><th align="justify">Upgrade Decisions</th><th align="justify">Redesign Decisions</th></tr></thead><tbody><tr><td align="justify"><p>Make use of minimal OS-specific features</p></td><td align="justify"><p>Translate NT4 features to new host OS features</p></td><td align="justify"><p>Improve on NT4 functionality, enhance management capabilities</p></td></tr><tr><td align="justify"><p>Move all accounts from NT4 into Samba-3</p></td><td align="justify"><p>Copy and improve</p></td><td align="justify"><p>Authentication regime (database location and access)</p></td></tr><tr><td align="justify"><p>Make least number of operational changes</p></td><td align="justify"><p>Make progressive improvements</p></td><td align="justify"><p>Desktop management methods</p></td></tr><tr><td align="justify"><p>Take least amount of time to migrate</p></td><td align="justify"><p>Minimize user impact</p></td><td align="justify"><p>Better control of Desktops/Users</p></td></tr><tr><td align="justify"><p>Live versus isolated conversion</p></td><td align="justify"><p>Maximize functionality</p></td><td align="justify"><p>Identify Needs for: <span class="emphasis"><em>Manageability, Scalability, Security, Availability</em></span></p></td></tr><tr><td align="justify"><p>Integrate Samba-3, then migrate while users are active, then change of control (swap out)</p></td><td align="justify"><p>Take advantage of lower maintenance opportunity</p></td><td align="justify"><p></p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680602"></a>Samba-3 Implementation Choices</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Authentication Database/Backend</span></dt><dd><p>
 		Samba-3 can use an external authentication backend:
 		</p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind (external Samba or NT4/200x server).</p></li><li><p>External server could use Active Directory or NT4 domain.</p></li><li><p>Can use pam_mkhomedir.so to autocreate home directories.</p></li><li><p> Samba-3 can use a local authentication backend: <em class="parameter"><code>smbpasswd</code></em>,
 				<em class="parameter"><code>tdbsam</code></em>, <em class="parameter"><code>ldapsam</code></em>
 			</p></li></ul></div></dd><dt><span class="term">Access Control Points</span></dt><dd><p>
 		Samba permits Access Control points to be set:
-		</p><a class="indexterm" name="id2680513"></a><a class="indexterm" name="id2680520"></a><a class="indexterm" name="id2680527"></a><a class="indexterm" name="id2680534"></a><div class="itemizedlist"><ul type="disc"><li><p>On the share itself  using share ACLs.</p></li><li><p>On the file system  using UNIX permissions on files and directories.</p><p>Note: Can enable Posix ACLs in file system also.</p></li><li><p>Through Samba share parameters  not recommended except as last resort.</p></li></ul></div></dd><dt><span class="term">Policies (migrate or create new ones)</span></dt><dd><p>
-<a class="indexterm" name="id2680582"></a>
-<a class="indexterm" name="id2680588"></a>
+		</p><a class="indexterm" name="id2680675"></a><a class="indexterm" name="id2680682"></a><a class="indexterm" name="id2680689"></a><a class="indexterm" name="id2680696"></a><div class="itemizedlist"><ul type="disc"><li><p>On the share itself  using share ACLs.</p></li><li><p>On the file system  using UNIX permissions on files and directories.</p><p>Note: Can enable Posix ACLs in file system also.</p></li><li><p>Through Samba share parameters  not recommended except as last resort.</p></li></ul></div></dd><dt><span class="term">Policies (migrate or create new ones)</span></dt><dd><p>
+<a class="indexterm" name="id2680744"></a>
+<a class="indexterm" name="id2680750"></a>
 		Exercise great caution when making registry changes; use the right tool and be aware
 		that changes made through NT4-style <code class="filename">NTConfig.POL</code> files can leave
 		permanent changes.
-<a class="indexterm" name="id2680604"></a>
-<a class="indexterm" name="id2680611"></a>
-<a class="indexterm" name="id2680618"></a>
+<a class="indexterm" name="id2680766"></a>
+<a class="indexterm" name="id2680773"></a>
+<a class="indexterm" name="id2680780"></a>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>Using Group Policy Editor (NT4).</p></li><li><p>Watch out for tattoo effect.</p></li></ul></div></dd><dt><span class="term">User and Group Profiles</span></dt><dd><p>
-<a class="indexterm" name="id2680649"></a>
-<a class="indexterm" name="id2680656"></a>
+<a class="indexterm" name="id2680811"></a>
+<a class="indexterm" name="id2680818"></a>
 		Platform-specific, so use platform tool to change from a local to a roaming profile.
 		Can use new profiles tool to change SIDs (<code class="filename">NTUser.DAT</code>).
 		</p></dd><dt><span class="term">Logon Scripts</span></dt><dd><p>
 		Know how they work.
 		</p></dd><dt><span class="term">User and Group Mapping to UNIX/Linux</span></dt><dd><p>
-		<a class="indexterm" name="id2680694"></a>
+		<a class="indexterm" name="id2680856"></a>
 		User and group mapping code is new. Many problems have been experienced as network administrators
 		who are familiar with Samba-2.2.x migrate to Samba-3. Carefully study the chapters that document
 		the new password backend behavior and the new group mapping functionality.
@@ -274,6 +274,6 @@ being contemplated.
 				(Linux 8 chars, NT4 up to 254 chars).</p></li><li><p>Add/Delete Machines: Applied only to domain members
 				(Note: machine names may be limited to 16 characters).</p></li><li><p>Use <code class="literal">net groupmap</code> to connect NT4 groups to UNIX groups.</p></li><li><p>Add/Delete Groups: Note OS limits on size and nature.
 				Linux limit is 16 char, no spaces, and no uppercase chars (<code class="literal">groupadd</code>).</p></li></ul></div></dd><dt><span class="term">Migration Tools</span></dt><dd><p>
-				<a class="indexterm" name="id2680812"></a>
+				<a class="indexterm" name="id2680974"></a>
 				Domain Control (NT4-Style) Profiles, Policies, Access Controls, Security
 				</p><div class="itemizedlist"><ul type="disc"><li><p>Samba: <code class="literal">net, rpcclient, smbpasswd, pdbedit, profiles</code></p></li><li><p>Windows: <code class="literal">NT4 Domain User Manager, Server Manager (NEXUS)</code></p></li></ul></div></dd></dl></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrading-to-3.0.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="SWAT.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�35.�Updating and Upgrading Samba�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�37.�SWAT: The Samba Web Administration Tool</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/NetCommand.html b/docs/htmldocs/Samba3-HOWTO/NetCommand.html
index 79c92e07a1..7a0d46758f 100644
--- a/docs/htmldocs/Samba3-HOWTO/NetCommand.html
+++ b/docs/htmldocs/Samba3-HOWTO/NetCommand.html
@@ -1,16 +1,16 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�13.�Remote and Local Management: The Net Command</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX"><link rel="next" href="idmapper.html" title="Chapter�14.�Identity Mapping (IDMAP)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�13.�Remote and Local Management: The Net Command</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="groupmapping.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="idmapper.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetCommand"></a>Chapter�13.�Remote and Local Management: The Net Command</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="orgname">Samba Team</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 9, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetCommand.html#id2599025">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599319">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599559">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600921">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601133">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601181">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601250">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601678">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601693">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602062">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602518">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602563">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602751">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602781">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603404">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603657">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603676">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603742">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603858">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603875">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603919">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603955">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2598886"></a>
-<a class="indexterm" name="id2598893"></a>
-<a class="indexterm" name="id2598900"></a>
-<a class="indexterm" name="id2598907"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�13.�Remote and Local Management: The Net Command</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX"><link rel="next" href="idmapper.html" title="Chapter�14.�Identity Mapping (IDMAP)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�13.�Remote and Local Management: The Net Command</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="groupmapping.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="idmapper.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetCommand"></a>Chapter�13.�Remote and Local Management: The Net Command</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="orgname">Samba Team</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 9, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetCommand.html#id2599005">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599300">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599539">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600908">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601120">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601168">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601237">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601665">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601680">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602049">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602505">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602550">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602738">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602768">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603391">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603642">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603661">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603727">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603842">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603860">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603904">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603939">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2598866"></a>
+<a class="indexterm" name="id2598873"></a>
+<a class="indexterm" name="id2598880"></a>
+<a class="indexterm" name="id2598887"></a>
 The <code class="literal">net</code> command is one of the new features of Samba-3 and is an attempt to provide a useful
 tool for the majority of remote management operations necessary for common tasks. The <code class="literal">net</code>
 tool is flexible by design and is intended for command-line use as well as for scripted control application.
 </p><p>
-<a class="indexterm" name="id2598933"></a>
-<a class="indexterm" name="id2598939"></a>
-<a class="indexterm" name="id2598947"></a>
-<a class="indexterm" name="id2598954"></a>
+<a class="indexterm" name="id2598913"></a>
+<a class="indexterm" name="id2598920"></a>
+<a class="indexterm" name="id2598927"></a>
+<a class="indexterm" name="id2598934"></a>
 Originally introduced with the intent to mimic the Microsoft Windows command that has the same name, the
 <code class="literal">net</code> command has morphed into a very powerful instrument that has become an essential part
 of the Samba network administrator's toolbox. The Samba Team has introduced tools, such as
@@ -22,27 +22,27 @@ provided should look at the <code class="literal">net</code> command before sear
 </p><p>
 A Samba-3 administrator cannot afford to gloss over this chapter because to do so will almost certainly cause
 the infliction of self-induced pain, agony, and desperation. Be warned: this is an important chapter.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599025"></a>Overview</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599005"></a>Overview</h2></div></div></div><p>
+<a class="indexterm" name="id2599013"></a>
+<a class="indexterm" name="id2599020"></a>
+<a class="indexterm" name="id2599027"></a>
 <a class="indexterm" name="id2599033"></a>
 <a class="indexterm" name="id2599040"></a>
 <a class="indexterm" name="id2599046"></a>
-<a class="indexterm" name="id2599053"></a>
-<a class="indexterm" name="id2599060"></a>
-<a class="indexterm" name="id2599066"></a>
 	The tasks that follow the installation of a Samba-3 server, whether standalone or domain member, of a
 	domain controller (PDC or BDC) begins with the need to create administrative rights. Of course, the
 	creation of user and group accounts is essential for both a standalone server and a PDC.
 	In the case of a BDC or a Domain Member server (DMS), domain user and group accounts are obtained from
 	the central domain authentication backend.
 	</p><p>
-<a class="indexterm" name="id2599084"></a>
-<a class="indexterm" name="id2599091"></a>
+<a class="indexterm" name="id2599064"></a>
+<a class="indexterm" name="id2599071"></a>
+<a class="indexterm" name="id2599078"></a>
+<a class="indexterm" name="id2599085"></a>
+<a class="indexterm" name="id2599092"></a>
 <a class="indexterm" name="id2599098"></a>
-<a class="indexterm" name="id2599104"></a>
-<a class="indexterm" name="id2599111"></a>
-<a class="indexterm" name="id2599118"></a>
-<a class="indexterm" name="id2599124"></a>
-<a class="indexterm" name="id2599131"></a>
+<a class="indexterm" name="id2599105"></a>
+<a class="indexterm" name="id2599112"></a>
 	Regardless of the type of server being installed, local UNIX groups must be mapped to the Windows
 	networking domain global group accounts. Do you ask why? Because Samba always limits its access to
 	the resources of the host server by way of traditional UNIX UID and GID controls. This means that local
@@ -50,41 +50,41 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is
 	global groups can be given access rights based on UIDs and GIDs local to the server that is hosting
 	Samba. Such mappings are implemented using the <code class="literal">net</code> command.
 	</p><p>
+<a class="indexterm" name="id2599136"></a>
+<a class="indexterm" name="id2599143"></a>
+<a class="indexterm" name="id2599149"></a>
 <a class="indexterm" name="id2599156"></a>
 <a class="indexterm" name="id2599163"></a>
-<a class="indexterm" name="id2599169"></a>
-<a class="indexterm" name="id2599176"></a>
-<a class="indexterm" name="id2599183"></a>
-<a class="indexterm" name="id2599190"></a>
-<a class="indexterm" name="id2599197"></a>
+<a class="indexterm" name="id2599170"></a>
+<a class="indexterm" name="id2599177"></a>
 	UNIX systems that are hosting a Samba-3 server that is running as a member (PDC, BDC, or DMS) must have
 	a machine security account in the domain authentication database (or directory). The creation of such
 	security (or trust) accounts is also handled using the <code class="literal">net</code> command.
 	</p><p>
+<a class="indexterm" name="id2599197"></a>
+<a class="indexterm" name="id2599204"></a>
+<a class="indexterm" name="id2599210"></a>
 <a class="indexterm" name="id2599217"></a>
 <a class="indexterm" name="id2599224"></a>
-<a class="indexterm" name="id2599230"></a>
-<a class="indexterm" name="id2599237"></a>
-<a class="indexterm" name="id2599244"></a>
-<a class="indexterm" name="id2599251"></a>
-<a class="indexterm" name="id2599258"></a>
-<a class="indexterm" name="id2599265"></a>
-<a class="indexterm" name="id2599272"></a>
+<a class="indexterm" name="id2599231"></a>
+<a class="indexterm" name="id2599238"></a>
+<a class="indexterm" name="id2599245"></a>
+<a class="indexterm" name="id2599252"></a>
 	The establishment of interdomain trusts is achieved using the <code class="literal">net</code> command also, as
 	may a plethora of typical administrative duties such as user management, group management, share and
 	printer management, file and printer migration, security identifier management, and so on.
 	</p><p>
-<a class="indexterm" name="id2599292"></a>
-<a class="indexterm" name="id2599299"></a>
+<a class="indexterm" name="id2599273"></a>
+<a class="indexterm" name="id2599279"></a>
 	The overall picture should be clear now: the <code class="literal">net</code> command plays a central role
 	on the Samba-3 stage. This role will continue to be developed. The inclusion of this chapter is
 	evidence of its importance, one that has grown in complexity to the point that it is no longer considered
 	prudent to cover its use fully in the online UNIX man pages.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599319"></a>Administrative Tasks and Methods</h2></div></div></div><p>
-<a class="indexterm" name="id2599327"></a>
-<a class="indexterm" name="id2599334"></a>
-<a class="indexterm" name="id2599340"></a>
-<a class="indexterm" name="id2599350"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599300"></a>Administrative Tasks and Methods</h2></div></div></div><p>
+<a class="indexterm" name="id2599308"></a>
+<a class="indexterm" name="id2599314"></a>
+<a class="indexterm" name="id2599321"></a>
+<a class="indexterm" name="id2599330"></a>
 	The basic operations of the <code class="literal">net</code> command are documented here. This documentation is not
 	exhaustive, and thus it is incomplete. Since the primary focus is on migration from Windows servers to a Samba
 	server, the emphasis is on the use of the Distributed Computing Environment Remote Procedure Call (DCE RPC)
@@ -94,36 +94,36 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is
 	automatically fall back via the <code class="constant">ads</code>, <code class="constant">rpc</code>, and
 	<code class="constant">rap</code> modes.  Please refer to the man page for a more comprehensive overview of the
 	capabilities of this utility.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599400"></a>UNIX and Windows Group Management</h2></div></div></div><p>
-<a class="indexterm" name="id2599408"></a>
-<a class="indexterm" name="id2599415"></a>
-<a class="indexterm" name="id2599424"></a>
-<a class="indexterm" name="id2599433"></a>
-<a class="indexterm" name="id2599441"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2599381"></a>UNIX and Windows Group Management</h2></div></div></div><p>
+<a class="indexterm" name="id2599389"></a>
+<a class="indexterm" name="id2599396"></a>
+<a class="indexterm" name="id2599404"></a>
+<a class="indexterm" name="id2599413"></a>
+<a class="indexterm" name="id2599422"></a>
 	As stated, the focus in most of this chapter is on use of the <code class="literal">net rpc</code> family of
 	operations that are supported by Samba. Most of them are supported by the <code class="literal">net ads</code>
 	mode when used in connection with Active Directory. The <code class="literal">net rap</code> operating mode is
 	also supported for some of these operations. RAP protocols are used by IBM OS/2 and by several
 	earlier SMB servers.
 	</p><p>
-<a class="indexterm" name="id2599475"></a>
-<a class="indexterm" name="id2599481"></a>
-<a class="indexterm" name="id2599488"></a>
+<a class="indexterm" name="id2599455"></a>
+<a class="indexterm" name="id2599461"></a>
+<a class="indexterm" name="id2599468"></a>
 	Samba's <code class="literal">net</code> tool implements sufficient capability to permit all common administrative
 	tasks to be completed from the command line. In this section each of the essential user and group management
 	facilities are explored.
 	</p><p>
-<a class="indexterm" name="id2599508"></a>
-<a class="indexterm" name="id2599514"></a>
-<a class="indexterm" name="id2599524"></a>
-<a class="indexterm" name="id2599533"></a>
+<a class="indexterm" name="id2599488"></a>
+<a class="indexterm" name="id2599495"></a>
+<a class="indexterm" name="id2599504"></a>
+<a class="indexterm" name="id2599513"></a>
 	Samba-3 recognizes two types of groups: <span class="emphasis"><em>domain groups</em></span> and <span class="emphasis"><em>local
 	groups</em></span>. Domain groups can contain (have as members) only domain user accounts. Local groups
 	can contain local users, domain users, and domain groups as members.
 	</p><p>
 	The purpose of a local group is to permit file permission to be set for a group account that, like the
 	usual UNIX/Linux group, is persistent across redeployment of a Windows file server.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2599559"></a>Adding, Renaming, or Deletion of Group Accounts</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2599539"></a>Adding, Renaming, or Deletion of Group Accounts</h3></div></div></div><p>
 	Samba provides file and print services to Windows clients. The file system resources it makes available
 	to the Windows environment must, of necessity, be provided in a manner that is compatible with the
 	Windows networking environment. UNIX groups are created and deleted as required to serve operational
@@ -143,11 +143,11 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is
 	between the UNIX group account and its members to the respective Windows group accounts. It goes on to
 	show how UNIX group members automatically pass-through to Windows group membership as soon as a logical
 	mapping has been created.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599601"></a>Adding or Creating a New Group</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599581"></a>Adding or Creating a New Group</h4></div></div></div><p>
 	Before attempting to add a Windows group account, the currently available groups can be listed as shown
 	here:
-<a class="indexterm" name="id2599611"></a>
-<a class="indexterm" name="id2599622"></a>
+<a class="indexterm" name="id2599591"></a>
+<a class="indexterm" name="id2599602"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group list -Uroot%not24get
 Password:
@@ -163,7 +163,7 @@ Engineers
 	</p><p>
 	A Windows group account called &#8220;<span class="quote">SupportEngrs</span>&#8221; can be added by executing the following
 command:
-<a class="indexterm" name="id2599658"></a>
+<a class="indexterm" name="id2599638"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group add "SupportEngrs" -Uroot%not24get
 </pre><p>
@@ -183,9 +183,9 @@ Engineers
 SupportEngrs
 </pre><p>
 	</p><p>
-<a class="indexterm" name="id2599701"></a>
-<a class="indexterm" name="id2599708"></a>
-<a class="indexterm" name="id2599715"></a>
+<a class="indexterm" name="id2599681"></a>
+<a class="indexterm" name="id2599688"></a>
+<a class="indexterm" name="id2599695"></a>
 	The following demonstrates that the POSIX (UNIX/Linux system account) group has been created by calling
 	the <a class="link" href="smb.conf.5.html#ADDGROUPSCRIPT" target="_top">add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"</a> interface
 	script:
@@ -205,7 +205,7 @@ SupportEngrs:x:1003:
 	The following demonstrates that the use of the <code class="literal">net</code> command to add a group account
 results in immediate mapping of the POSIX group that has been created to the Windows group account as shown
 here:
-<a class="indexterm" name="id2599761"></a>
+<a class="indexterm" name="id2599741"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net groupmap list
 Domain Admins (S-1-5-21-72630-4128915-11681869-512) -&gt; Domain Admins
@@ -218,19 +218,19 @@ Domain Computers (S-1-5-21-72630-4128915-11681869-553) -&gt; Domain Computers
 Engineers (S-1-5-21-72630-4128915-11681869-3005) -&gt; Engineers
 SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -&gt; SupportEngrs
 </pre><p>
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599802"></a>Mapping Windows Groups to UNIX Groups</h4></div></div></div><p>
-<a class="indexterm" name="id2599810"></a>
-<a class="indexterm" name="id2599817"></a>
-<a class="indexterm" name="id2599824"></a>
-<a class="indexterm" name="id2599831"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2599783"></a>Mapping Windows Groups to UNIX Groups</h4></div></div></div><p>
+<a class="indexterm" name="id2599790"></a>
+<a class="indexterm" name="id2599797"></a>
+<a class="indexterm" name="id2599804"></a>
+<a class="indexterm" name="id2599811"></a>
 	Windows groups must be mapped to UNIX system (POSIX) groups so that file system access controls
 	can be asserted in a manner that is consistent with the methods appropriate to the operating
 	system that is hosting the Samba server.
 	</p><p>
+<a class="indexterm" name="id2599825"></a>
+<a class="indexterm" name="id2599832"></a>
+<a class="indexterm" name="id2599838"></a>
 <a class="indexterm" name="id2599845"></a>
-<a class="indexterm" name="id2599852"></a>
-<a class="indexterm" name="id2599858"></a>
-<a class="indexterm" name="id2599865"></a>
 	All file system (file and directory) access controls, within the file system of a UNIX/Linux server that is
 	hosting a Samba server, are implemented using a UID/GID identity tuple. Samba does not in any way override
 	or replace UNIX file system semantics. Thus it is necessary that all Windows networking operations that
@@ -238,22 +238,22 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -&gt; SupportEngrs
 	account. The user account must also map to a locally known UID. Note that the <code class="literal">net</code>
 	command does not call any RPC-functions here but directly accesses the passdb.
 	</p><p>
-<a class="indexterm" name="id2599890"></a>
-<a class="indexterm" name="id2599897"></a>
-<a class="indexterm" name="id2599904"></a>
-<a class="indexterm" name="id2599911"></a>
-<a class="indexterm" name="id2599918"></a>
-<a class="indexterm" name="id2599925"></a>
-<a class="indexterm" name="id2599932"></a>
+<a class="indexterm" name="id2599871"></a>
+<a class="indexterm" name="id2599878"></a>
+<a class="indexterm" name="id2599884"></a>
+<a class="indexterm" name="id2599891"></a>
+<a class="indexterm" name="id2599898"></a>
+<a class="indexterm" name="id2599905"></a>
+<a class="indexterm" name="id2599912"></a>
 	Samba depends on default mappings for the <code class="constant">Domain Admins, Domain Users</code>, and
 	<code class="constant">Domain Guests</code> global groups. Additional groups may be added as shown in the
 	examples just given. There are times when it is necessary to map an existing UNIX group account
 	to a Windows group. This operation, in effect, creates a Windows group account as a consequence
 	of creation of the mapping.
 	</p><p>
-<a class="indexterm" name="id2599955"></a>
-<a class="indexterm" name="id2599967"></a>
-<a class="indexterm" name="id2599978"></a>
+<a class="indexterm" name="id2599936"></a>
+<a class="indexterm" name="id2599947"></a>
+<a class="indexterm" name="id2599958"></a>
 	The operations that are permitted include: <code class="constant">add</code>, <code class="constant">modify</code>,
 	and <code class="constant">delete</code>. An example of each operation is shown here.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
@@ -290,15 +290,15 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -&gt; SupportEngrs
 	Supported mapping types are 'd' (domain global) and 'l' (domain local), a domain local group in Samba is
 	treated as local to the individual Samba server. Local groups can be used with Samba to enable multiple
 	nested group support.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600110"></a>Deleting a Group Account</h4></div></div></div><p>
-<a class="indexterm" name="id2600118"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600090"></a>Deleting a Group Account</h4></div></div></div><p>
+<a class="indexterm" name="id2600098"></a>
 	A group account may be deleted by executing the following command:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group delete SupportEngineers -Uroot%not24get
 </pre><p>
 	</p><p>
 	Validation of the deletion is advisable. The same commands may be executed as shown above.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600150"></a>Rename Group Accounts</h4></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600130"></a>Rename Group Accounts</h4></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 	This command is not documented in the man pages; it is implemented in the source code, but it does not
 	work at this time. The example given documents, from the source code, how it should work. Watch the
 	release notes of a future release to see when this may have been fixed.
@@ -306,7 +306,7 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -&gt; SupportEngrs
 	Sometimes it is necessary to rename a group account. Good administrators know how painful some managers'
 	demands can be if this simple request is ignored. The following command demonstrates how the Windows group
 	&#8220;<span class="quote">SupportEngrs</span>&#8221; can be renamed to &#8220;<span class="quote">CustomerSupport</span>&#8221;:
-<a class="indexterm" name="id2600179"></a>
+<a class="indexterm" name="id2600159"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group rename SupportEngrs \
     CustomerSupport -Uroot%not24get
@@ -349,7 +349,7 @@ Engineers (S-1-5-21-72630-412605-116429-3001) -&gt; Engineers
 	Given that the user <code class="constant">ajt</code> is already a member of the UNIX/Linux group and, via the
 	group mapping, a member of the Windows group, an attempt to add this account again should fail. This is
 	demonstrated here:
-<a class="indexterm" name="id2600310"></a>
+<a class="indexterm" name="id2600290"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
 Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
@@ -359,7 +359,7 @@ Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
 	</p><p>
 	To permit the user <code class="constant">ajt</code> to be added using the <code class="literal">net rpc group</code> utility,
 	this account must first be removed. The removal and confirmation of its effect is shown here:
-<a class="indexterm" name="id2600352"></a>
+<a class="indexterm" name="id2600332"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group delmem "MIDEARTH\Engineers" ajt -Uroot%not24get
 <code class="prompt">root# </code> getent group Engineers
@@ -383,7 +383,7 @@ MIDEARTH\ajt
 	In this example the members of the Windows <code class="constant">Domain Users</code> account are validated using
 	the <code class="literal">net rpc group</code> utility. Note the this contents of the UNIX/Linux group was shown
 	four paragraphs earlier. The Windows (domain) group membership is shown here:
-<a class="indexterm" name="id2600449"></a>
+<a class="indexterm" name="id2600429"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group members "Domain Users" -Uroot%not24get
 MIDEARTH\jht
@@ -440,11 +440,11 @@ DOM\jht
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group delmem demo "DOM\jht" -Uroot%not24get
 </pre><p>
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600629"></a>Managing Nest Groups on Workstations from the Samba Server</h4></div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2600610"></a>Managing Nest Groups on Workstations from the Samba Server</h4></div></div></div><p>
 	Windows network administrators often ask on the Samba mailing list how it is possible to grant everyone
 	administrative rights on their own workstation. This is of course a very bad practice, but commonly done
 	to avoid user complaints. Here is how it can be done remotely from a Samba PDC or BDC:
-<a class="indexterm" name="id2600643"></a>
+<a class="indexterm" name="id2600623"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc group addmem "Administrators" "Domain Users" \
     -S WINPC032 -Uadministrator%secret
@@ -452,19 +452,19 @@ DOM\jht
 	</p><p>
 	This can be scripted, and can therefore be performed as a user logs onto the domain from a Windows
 	workstation. Here is a simple example that shows how this can be done.
-	</p><div class="procedure"><a name="id2600675"></a><p class="title"><b>Procedure�13.1.�Automating User Addition to the Workstation Power Users Group</b></p><div class="example"><a name="autopoweruserscript"></a><p class="title"><b>Example�13.1.�Script to Auto-add Domain Users to Workstation Power Users Group</b></p><div class="example-contents"><pre class="screen">
+	</p><div class="procedure"><a name="id2600655"></a><p class="title"><b>Procedure�13.1.�Automating User Addition to the Workstation Power Users Group</b></p><div class="example"><a name="autopoweruserscript"></a><p class="title"><b>Example�13.1.�Script to Auto-add Domain Users to Workstation Power Users Group</b></p><div class="example-contents"><pre class="screen">
 #!/bin/bash
 
 /usr/bin/net rpc group addmem "Power Users" "DOMAIN_NAME\$1" \
                    -UAdministrator%secret -S $2
 
 exit 0
-</pre></div></div><br class="example-break"><div class="example"><a name="magicnetlogon"></a><p class="title"><b>Example�13.2.�A Magic Netlogon Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2600830"></a><em class="parameter"><code>comment = Netlogon Share</code></em></td></tr><tr><td><a class="indexterm" name="id2600842"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2600854"></a><em class="parameter"><code>root preexec = /etc/samba/scripts/autopoweruser.sh %U %m</code></em></td></tr><tr><td><a class="indexterm" name="id2600866"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2600878"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
+</pre></div></div><br class="example-break"><div class="example"><a name="magicnetlogon"></a><p class="title"><b>Example�13.2.�A Magic Netlogon Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2600811"></a><em class="parameter"><code>comment = Netlogon Share</code></em></td></tr><tr><td><a class="indexterm" name="id2600822"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2600834"></a><em class="parameter"><code>root preexec = /etc/samba/scripts/autopoweruser.sh %U %m</code></em></td></tr><tr><td><a class="indexterm" name="id2600846"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2600858"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><ol type="1"><li><p>
 		Create the script shown in <a class="link" href="NetCommand.html#autopoweruserscript" title="Example�13.1.�Script to Auto-add Domain Users to Workstation Power Users Group">&#8220;Script to Auto-add Domain Users to Workstation Power Users Group&#8221;</a> and locate it in
 		the directory <code class="filename">/etc/samba/scripts</code>, named as <code class="filename">autopoweruser.sh</code>.
-<a class="indexterm" name="id2600706"></a>
-<a class="indexterm" name="id2600718"></a>
-<a class="indexterm" name="id2600725"></a>
+<a class="indexterm" name="id2600687"></a>
+<a class="indexterm" name="id2600698"></a>
+<a class="indexterm" name="id2600705"></a>
 		</p></li><li><p>
 		Set the permissions on this script to permit it to be executed as part of the logon process:
 </p><pre class="screen">
@@ -473,7 +473,7 @@ exit 0
 </pre><p>
 		</p></li><li><p>
 		Modify the <code class="filename">smb.conf</code> file so the <code class="literal">NETLOGON</code> stanza contains the parameters
-		shown in <a class="link" href="NetCommand.html#magicnetlogon" title="Example�13.2.�A Magic Netlogon Share">the Netlogon Example smb.conf file</a> as shown.
+		shown in <a class="link" href="NetCommand.html#magicnetlogon" title="Example�13.2.�A Magic Netlogon Share">the Netlogon Example smb.conf file</a>.
 		</p></li><li><p>
 		Ensure that every Windows workstation Administrator account has the same password that you
 		have used in the script shown in <a class="link" href="NetCommand.html#magicnetlogon" title="Example�13.2.�A Magic Netlogon Share">the Netlogon Example smb.conf
@@ -484,15 +484,15 @@ exit 0
 	in which case there is little justification for the use of this procedure. The key justification
 	for the use of this method is that it will guarantee that all users have appropriate rights on
 	the workstation.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2600921"></a>UNIX and Windows User Management</h2></div></div></div><p>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2600908"></a>UNIX and Windows User Management</h2></div></div></div><p>
+<a class="indexterm" name="id2600917"></a>
+<a class="indexterm" name="id2600923"></a>
 <a class="indexterm" name="id2600930"></a>
-<a class="indexterm" name="id2600936"></a>
-<a class="indexterm" name="id2600943"></a>
+<a class="indexterm" name="id2600937"></a>
+<a class="indexterm" name="id2600944"></a>
 <a class="indexterm" name="id2600950"></a>
-<a class="indexterm" name="id2600957"></a>
-<a class="indexterm" name="id2600963"></a>
-<a class="indexterm" name="id2600970"></a>
-<a class="indexterm" name="id2600977"></a>
+<a class="indexterm" name="id2600958"></a>
+<a class="indexterm" name="id2600964"></a>
 	Every Windows network user account must be translated to a UNIX/Linux user account. In actual fact,
 	the only account information the UNIX/Linux Samba server needs is a UID.  The UID is available either
 	from a system (POSIX) account or from a pool (range) of UID numbers that is set aside for the purpose
@@ -516,8 +516,8 @@ net rpc password &lt;username&gt; [&lt;password&gt;] -Uadmin_username%admin_pass
 </pre><p>
 	</p><p>
 	The following demonstrates the addition of an account to the server <code class="constant">FRODO</code>:
-<a class="indexterm" name="id2601075"></a>
-<a class="indexterm" name="id2601086"></a>
+<a class="indexterm" name="id2601062"></a>
+<a class="indexterm" name="id2601073"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc user add jacko -S FRODO -Uroot%not24get
 Added user jacko
@@ -528,24 +528,24 @@ Added user jacko
 <code class="prompt">root# </code> net rpc user password jacko f4sth0rse \
     -S FRODO -Uroot%not24get
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601133"></a>Deletion of User Accounts</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601120"></a>Deletion of User Accounts</h3></div></div></div><p>
 	Deletion of a user account can be done using the following syntax:
 </p><pre class="screen">
 net [&lt;method&gt;] user DELETE &lt;name&gt; [misc. options] [targets]
 </pre><p>
 	The following command will delete the user account <code class="constant">jacko</code>:
-<a class="indexterm" name="id2601155"></a>
+<a class="indexterm" name="id2601142"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc user delete jacko -Uroot%not24get
 Deleted user account
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601181"></a>Managing User Accounts</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601168"></a>Managing User Accounts</h3></div></div></div><p>
 	Two basic user account operations are routinely used: change of password and querying which groups a user
 	is a member of. The change of password operation is shown in <a class="link" href="NetCommand.html#sbeuseraddn" title="Adding User Accounts">&#8220;Adding User Accounts&#8221;</a>.
 	</p><p>
 	The ability to query Windows group membership can be essential. Here is how a remote server may be
 	interrogated to find which groups a user is a member of:
-<a class="indexterm" name="id2601204"></a>
+<a class="indexterm" name="id2601191"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc user info jacko -S SAURON -Uroot%not24get
 net rpc user info jacko -S SAURON -Uroot%not24get
@@ -558,14 +558,14 @@ Emergency Services
 </pre><p>
 	</p><p>
 	It is also possible to rename user accounts:
-<a class="indexterm" name="id2601234"></a>oldusername newusername
+<a class="indexterm" name="id2601221"></a>oldusername newusername
 	Note that this operation does not yet work against Samba Servers. It is, however, possible to rename useraccounts on
 	Windows Servers.
 
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601250"></a>User Mapping</h3></div></div></div><p>
-<a class="indexterm" name="id2601257"></a>
-<a class="indexterm" name="id2601264"></a>
-<a class="indexterm" name="id2601271"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601237"></a>User Mapping</h3></div></div></div><p>
+<a class="indexterm" name="id2601244"></a>
+<a class="indexterm" name="id2601251"></a>
+<a class="indexterm" name="id2601258"></a>
 	In some situations it is unavoidable that a user's Windows logon name will differ from the login ID
 	that user has on the Samba server. It is possible to create a special file on the Samba server that
 	will permit the Windows user name to be mapped to a different UNIX/Linux user name. The <code class="filename">smb.conf</code>
@@ -581,22 +581,22 @@ marygee: geeringm
 	In this example the Windows user account &#8220;<span class="quote">William Parsons</span>&#8221; will be mapped to the UNIX user
 	<code class="constant">parsonsw</code>, and the Windows user account &#8220;<span class="quote">geeringm</span>&#8221; will be mapped to the
 	UNIX user <code class="constant">marygee</code>.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601333"></a>Administering User Rights and Privileges</h2></div></div></div><p>
-<a class="indexterm" name="id2601341"></a>
-<a class="indexterm" name="id2601348"></a>
-<a class="indexterm" name="id2601355"></a>
-<a class="indexterm" name="id2601362"></a>
-<a class="indexterm" name="id2601369"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601320"></a>Administering User Rights and Privileges</h2></div></div></div><p>
+<a class="indexterm" name="id2601328"></a>
+<a class="indexterm" name="id2601335"></a>
+<a class="indexterm" name="id2601342"></a>
+<a class="indexterm" name="id2601349"></a>
+<a class="indexterm" name="id2601356"></a>
 	With all versions of Samba earlier than 3.0.11 the only account on a Samba server that could
 	manage users, groups, shares, printers, and such was the <code class="constant">root</code> account. This caused
 	problems for some users and was a frequent source of scorn over the necessity to hand out the
 	credentials for the most security-sensitive account on a UNIX/Linux system.
 	</p><p>
-<a class="indexterm" name="id2601388"></a>
+<a class="indexterm" name="id2601375"></a>
+<a class="indexterm" name="id2601383"></a>
+<a class="indexterm" name="id2601389"></a>
 <a class="indexterm" name="id2601396"></a>
-<a class="indexterm" name="id2601402"></a>
-<a class="indexterm" name="id2601409"></a>
-<a class="indexterm" name="id2601416"></a>
+<a class="indexterm" name="id2601404"></a>
 	New to Samba version 3.0.11 is the ability to delegate administrative privileges as necessary to either
 	a normal user or to groups of users. The significance of the administrative privileges is documented
 	in <a class="link" href="rights.html" title="Chapter�15.�User Rights and Privileges">&#8220;User Rights and Privileges&#8221;</a>. Examples of use of the <code class="literal">net</code> for user rights and privilege
@@ -632,15 +632,15 @@ No privileges assigned
 	</p><p>
 	The <code class="literal">net</code> command can be used to obtain the currently supported capabilities for rights
 	and privileges using this method:
-<a class="indexterm" name="id2601490"></a>
-<a class="indexterm" name="id2601497"></a>
-<a class="indexterm" name="id2601504"></a>
-<a class="indexterm" name="id2601511"></a>
-<a class="indexterm" name="id2601518"></a>
-<a class="indexterm" name="id2601525"></a>
-<a class="indexterm" name="id2601532"></a>
-<a class="indexterm" name="id2601539"></a>
-<a class="indexterm" name="id2601546"></a>
+<a class="indexterm" name="id2601477"></a>
+<a class="indexterm" name="id2601484"></a>
+<a class="indexterm" name="id2601491"></a>
+<a class="indexterm" name="id2601498"></a>
+<a class="indexterm" name="id2601505"></a>
+<a class="indexterm" name="id2601512"></a>
+<a class="indexterm" name="id2601519"></a>
+<a class="indexterm" name="id2601526"></a>
+<a class="indexterm" name="id2601533"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc rights list -U root%not24get
      SeMachineAccountPrivilege  Add machines to domain
@@ -659,7 +659,7 @@ No privileges assigned
 	In this example, all rights are assigned to the <code class="constant">Domain Admins</code> group. This is a good
 	idea since members of this group are generally expected to be all-powerful. This assignment makes that
 	the reality:
-<a class="indexterm" name="id2601592"></a>
+<a class="indexterm" name="id2601579"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc rights grant "MIDEARTH\Domain Admins" \
     SeMachineAccountPrivilege SePrintOperatorPrivilege \
@@ -678,7 +678,7 @@ Successfully granted rights.
 </pre><p>
 	</p><p>
 	The following step permits validation of the changes just made:
-<a class="indexterm" name="id2601643"></a>
+<a class="indexterm" name="id2601630"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc rights list accounts -U root%not24get
 MIDEARTH\jht
@@ -712,17 +712,17 @@ SeAddUsersPrivilege
 SeRemoteShutdownPrivilege
 SeDiskOperatorPrivilege
 </pre><p>
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601678"></a>Managing Trust Relationships</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601665"></a>Managing Trust Relationships</h2></div></div></div><p>
 	There are essentially two types of trust relationships: the first is between domain controllers and domain
 	member machines (network clients), the second is between domains (called interdomain trusts). All
 	Samba servers that participate in domain security require a domain membership trust account, as do like
 	Windows NT/200x/XP workstations.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601693"></a>Machine Trust Accounts</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2601680"></a>Machine Trust Accounts</h3></div></div></div><p>
 	The net command looks in the <code class="filename">smb.conf</code> file to obtain its own configuration settings. Thus, the following
 	command 'knows' which domain to join from the <code class="filename">smb.conf</code> file.
 	</p><p>
 	A Samba server domain trust account can be validated as shown in this example:
-<a class="indexterm" name="id2601720"></a>
+<a class="indexterm" name="id2601707"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc testjoin
 Join to 'MIDEARTH' is OK
@@ -735,7 +735,7 @@ Join to domain 'WORLDOCEAN' is not valid
 </pre><p>
 	</p><p>
 	The equivalent command for joining a Samba server to a Windows ADS domain is shown here:
-<a class="indexterm" name="id2601758"></a>
+<a class="indexterm" name="id2601745"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads testjoin
 Using short domain name -- TAKEAWAY
@@ -750,7 +750,7 @@ Join to domain is not valid
 	</p><p>
 	The following demonstrates the process of creating a machine trust account in the target domain for the
 	Samba server from which the command is executed:
-<a class="indexterm" name="id2601803"></a>
+<a class="indexterm" name="id2601790"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -765,7 +765,7 @@ merlin$:1009:9B4489D6B90461FD6A3EC3AB96147E16:\
 	The S in the square brackets means this is a server (PDC/BDC) account. The domain join can be cast to join
 	purely as a workstation, in which case the S is replaced with a W (indicating a workstation account). The
 	following command can be used to affect this:
-<a class="indexterm" name="id2601847"></a>
+<a class="indexterm" name="id2601834"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join member -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -773,7 +773,7 @@ Joined domain MIDEARTH.
 	Note that the command-line parameter <code class="constant">member</code> makes this join specific. By default
 	the type is deduced from the <code class="filename">smb.conf</code> file configuration. To specifically join as a PDC or BDC, the
 	command-line parameter will be <code class="constant">[PDC | BDC]</code>. For example:
-<a class="indexterm" name="id2601888"></a>
+<a class="indexterm" name="id2601875"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc join bdc -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -781,7 +781,7 @@ Joined domain MIDEARTH.
 	It is best to let Samba figure out the domain join type from the settings in the <code class="filename">smb.conf</code> file.
 	</p><p>
 	The command to join a Samba server to a Windows ADS domain is shown here:
-<a class="indexterm" name="id2601923"></a>
+<a class="indexterm" name="id2601910"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads join -UAdministrator%not24get
 Using short domain name -- GDANSK
@@ -792,7 +792,7 @@ Joined 'FRANDIMITZ' to realm 'GDANSK.ABMAS.BIZ'
 	Windows machine is withdrawn from the domain, the domain membership account is not automatically removed
 	either. Inactive domain member accounts can be removed using any convenient tool. If necessary, the
 	machine account can be removed using the following <code class="literal">net</code> command:
-<a class="indexterm" name="id2601963"></a>
+<a class="indexterm" name="id2601950"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc user delete HERRING\$ -Uroot%not24get
 Deleted user account.
@@ -802,26 +802,26 @@ Deleted user account.
 	</p><p>
 	A Samba-3 server that is a Windows ADS domain member can execute the following command to detach from the
 	domain:
-<a class="indexterm" name="id2601996"></a>
+<a class="indexterm" name="id2601983"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads leave
 </pre><p>
 	</p><p>
 	Detailed information regarding an ADS domain can be obtained by a Samba DMS machine by executing the
 	following:
-<a class="indexterm" name="id2602024"></a>
+<a class="indexterm" name="id2602011"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads status
 </pre><p>
 	The volume of information is extensive. Please refer to the book &#8220;<span class="quote">Samba-3 by Example</span>&#8221;,
 	Chapter 7 for more information regarding its use. This book may be obtained either in print or online from
 	the <a class="ulink" href="http://www.samba.org/samba/docs/Samba3-ByExample.pdf" target="_top">Samba-3 by Example</a>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602062"></a>Interdomain Trusts</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602049"></a>Interdomain Trusts</h3></div></div></div><p>
 	Interdomain trust relationships form the primary mechanism by which users from one domain can be granted
 	access rights and privileges in another domain. 
 	</p><p>
 	To discover what trust relationships are in effect, execute this command:
-<a class="indexterm" name="id2602077"></a>
+<a class="indexterm" name="id2602064"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc trustdom list -Uroot%not24get
 Trusted domains list:
@@ -837,7 +837,7 @@ none
 	It is necessary to create a trust account in the local domain. A domain controller in a second domain can
 	create a trusted connection with this account. That means that the foreign domain is being trusted
 	to access resources in the local domain. This command creates the local trust account:
-<a class="indexterm" name="id2602111"></a>
+<a class="indexterm" name="id2602098"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc trustdom add DAMNATION f00db4r -Uroot%not24get
 </pre><p>
@@ -850,7 +850,7 @@ DAMNATION$:1016:9AC1F121DF897688AAD3B435B51404EE: \
 	A trust account will always have an I in the field within the square brackets.
 	</p><p>
 	If the trusting domain is not capable of being reached, the following command will fail:
-<a class="indexterm" name="id2602162"></a>
+<a class="indexterm" name="id2602149"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc trustdom list -Uroot%not24get
 Trusted domains list:
@@ -876,7 +876,7 @@ DAMNATION           domain controller is not responding
 	Where a trust account has been created on a foreign domain, Samba is able to establish the trust (connect with)
 	the foreign account. In the process it creates a one-way trust to the resources on the remote domain. This
 	command achieves the objective of joining the trust relationship:
-<a class="indexterm" name="id2602206"></a>
+<a class="indexterm" name="id2602193"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc trustdom establish DAMNATION
 Password: xxxxxxx	== f00db4r
@@ -897,7 +897,7 @@ DAMNATION           S-1-5-21-1385457007-882775198-1210191635
 	</p><p>
 	Sometimes it is necessary to remove the ability for local users to access a foreign domain. The trusting
 	connection can be revoked as shown here:
-<a class="indexterm" name="id2602254"></a>
+<a class="indexterm" name="id2602241"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc trustdom revoke DAMNATION -Uroot%not24get
 </pre><p>
@@ -907,21 +907,21 @@ DAMNATION           S-1-5-21-1385457007-882775198-1210191635
 <code class="prompt">root# </code> net rpc trustdom del DAMNATION -Uroot%not24get
 </pre><p>
 
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2602296"></a>Managing Security Identifiers (SIDS)</h2></div></div></div><p>
-<a class="indexterm" name="id2602304"></a>
-<a class="indexterm" name="id2602311"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2602283"></a>Managing Security Identifiers (SIDS)</h2></div></div></div><p>
+<a class="indexterm" name="id2602291"></a>
+<a class="indexterm" name="id2602298"></a>
+<a class="indexterm" name="id2602305"></a>
+<a class="indexterm" name="id2602312"></a>
 <a class="indexterm" name="id2602318"></a>
-<a class="indexterm" name="id2602324"></a>
-<a class="indexterm" name="id2602331"></a>
 	The basic security identifier that is used by all Windows networking operations is the Windows security
 	identifier (SID). All Windows network machines (servers and workstations), users, and groups are
 	identified by their respective SID. All desktop profiles are also encoded with user and group SIDs that
 	are specific to the SID of the domain to which the user belongs.
 	</p><p>
+<a class="indexterm" name="id2602335"></a>
+<a class="indexterm" name="id2602342"></a>
 <a class="indexterm" name="id2602348"></a>
 <a class="indexterm" name="id2602355"></a>
-<a class="indexterm" name="id2602361"></a>
-<a class="indexterm" name="id2602368"></a>
 	It is truly prudent to store the machine and/or domain SID in a file for safekeeping. Why? Because 
 	a change in hostname or in the domain (workgroup) name may result in a change in the SID. When you
 	have the SID on hand, it is a simple matter to restore it. The alternative is to suffer the pain of
@@ -929,7 +929,7 @@ DAMNATION           S-1-5-21-1385457007-882775198-1210191635
 	</p><p>
 	First, do not forget to store the local SID in a file. It is a good idea to put this in the directory
 	in which the <code class="filename">smb.conf</code> file is also stored. Here is a simple action to achieve this:
-<a class="indexterm" name="id2602394"></a>
+<a class="indexterm" name="id2602381"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net getlocalsid &gt; /etc/samba/my-sid
 </pre><p>
@@ -945,7 +945,7 @@ SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429
 	If ever it becomes necessary to restore the SID that has been stored in the <code class="filename">my-sid</code>
 	file, simply copy the SID (the string of characters that begins with <code class="constant">S-1-5-21</code>) to
 	the command line shown here:
-<a class="indexterm" name="id2602456"></a>
+<a class="indexterm" name="id2602443"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net setlocalsid S-1-5-21-1385457007-882775198-1210191635
 </pre><p>
@@ -956,7 +956,7 @@ SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429
 	DMS and workstation clients should have their own machine SID to avoid
 	any potential namespace collision. Here is the way that the BDC SID can be synchronized to that
 	of the PDC (this is the default NT4 domain practice also):
-<a class="indexterm" name="id2602488"></a>
+<a class="indexterm" name="id2602475"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc getsid -S FRODO -Uroot%not24get
 Storing SID S-1-5-21-726309263-4128913605-1168186429 \
@@ -964,25 +964,25 @@ Storing SID S-1-5-21-726309263-4128913605-1168186429 \
 </pre><p>
 	Usually it is not necessary to specify the target server (-S FRODO) or the administrator account
 	credentials (-Uroot%not24get).
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2602518"></a>Share Management</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2602505"></a>Share Management</h2></div></div></div><p>
 	Share management is central to all file serving operations. Typical share operations include:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Creation/change/deletion of shares</p></li><li><p>Setting/changing ACLs on shares</p></li><li><p>Moving shares from one server to another</p></li><li><p>Change of permissions of share contents</p></li></ul></div><p>
 	Each of these are dealt with here insofar as they involve the use of the <code class="literal">net</code>
 	command. Operations outside of this command are covered elsewhere in this document.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602563"></a>Creating, Editing, and Removing Shares</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602550"></a>Creating, Editing, and Removing Shares</h3></div></div></div><p>
 	A share can be added using the <code class="literal">net rpc share</code> command capabilities.
 	The target machine may be local or remote and is specified by the -S option. It must be noted
 	that the addition and deletion of shares using this tool depends on the availability of a suitable
 	interface script. The interface scripts Sambas <code class="literal">smbd</code> uses are called
 	<a class="link" href="smb.conf.5.html#ADDSHARECOMMAND" target="_top">add share command</a>, <a class="link" href="smb.conf.5.html#DELETESHARECOMMAND" target="_top">delete share command</a> and
-	<a class="link" href="smb.conf.5.html#CHANGESHARECOMMAND" target="_top">change share command</a>. A set of example scripts are provided in the Samba source
+	<a class="link" href="smb.conf.5.html#CHANGESHARECOMMAND" target="_top">change share command</a> A set of example scripts are provided in the Samba source
 	code tarball in the directory <code class="filename">~samba/examples/scripts</code>.
 	</p><p>
 	The following steps demonstrate the use of the share management capabilities of the <code class="literal">net</code>
 	utility. In the first step a share called <code class="constant">Bulge</code> is added. The sharepoint within the
 	file system is the directory <code class="filename">/data</code>. The command that can be executed to perform the
 	addition of this share is shown here:
-<a class="indexterm" name="id2602659"></a>
+<a class="indexterm" name="id2602646"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share add Bulge=/data -S MERLIN -Uroot%not24get
 </pre><p>
@@ -1003,7 +1003,7 @@ ADMIN$
 	</p><p>
 	Often it is desirable also to permit a share to be removed using a command-line tool.
 	The following step permits the share that was previously added to be removed:
-<a class="indexterm" name="id2602710"></a>
+<a class="indexterm" name="id2602698"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share delete Bulge -S MERLIN -Uroot%not24get
 </pre><p>
@@ -1019,15 +1019,15 @@ IPC$
 ADMIN$
 kyocera
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602751"></a>Creating and Changing Share ACLs</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602738"></a>Creating and Changing Share ACLs</h3></div></div></div><p>
 	At this time the <code class="literal">net</code> tool cannot be used to manage ACLs on Samba shares. In MS Windows 
 	language this is called Share Permissions.
 	</p><p>
 	It is possible to set ACLs on Samba shares using either the SRVTOOLS NT4 Domain Server Manager
 	or using the Computer Management MMC snap-in. Neither is covered here,
 	but see <a class="link" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls">&#8220;File, Directory, and Share Access Controls&#8221;</a>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602781"></a>Share, Directory, and File Migration</h3></div></div></div><p>
-<a class="indexterm" name="id2602789"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2602768"></a>Share, Directory, and File Migration</h3></div></div></div><p>
+<a class="indexterm" name="id2602776"></a>
 	Shares and files can be migrated in the same manner as user, machine, and group accounts.
 	It is possible to preserve access control settings (ACLs) as well as security settings
 	throughout the migration process. The <code class="literal">net rpc vampire</code> facility is used
@@ -1064,7 +1064,7 @@ kyocera
 		</p></li><li><p>
 		Printer settings may not be fully or may be incorrectly migrated. This might in particular happen
 		when migrating a Windows 2003 print server to Samba.
-		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2602891"></a>Share Migration</h4></div></div></div><p>
+		</p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2602878"></a>Share Migration</h4></div></div></div><p>
 	The <code class="literal">net rpc share migrate</code> command operation permits the migration of plain
 	share stanzas. A stanza contains the parameters within which a file or print share are defined.
 	The use of this migration method will create share stanzas that have as parameters the file
@@ -1091,7 +1091,7 @@ net rpc share MIGRATE SHARES &lt;share-name&gt; -S &lt;source&gt;
 	When the parameter &lt;share-name&gt; is omitted, all shares will be migrated. The potentially
 	large list of available shares on the system that is being migrated can be limited using the
 	<em class="parameter"><code>--exclude</code></em> switch. For example:
-<a class="indexterm" name="id2603004"></a>
+<a class="indexterm" name="id2602992"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share migrate shares myshare\
          -S win2k -U administrator%secret"
@@ -1104,13 +1104,13 @@ net rpc share MIGRATE SHARES &lt;share-name&gt; -S &lt;source&gt;
 	identical on both systems. One precaution worth taking before commencement of migration of shares is
 	to validate that the migrated accounts (on the Samba server) have the needed rights and privileges.
 	This can be done as shown here:
-<a class="indexterm" name="id2603059"></a>
+<a class="indexterm" name="id2603046"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc right list accounts -Uroot%not24get
 </pre><p>
 	The steps taken so far perform only the migration of shares. Directories and directory contents
 	are not migrated by the steps covered up to this point.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603087"></a>File and Directory Migration</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603074"></a>File and Directory Migration</h4></div></div></div><p>
 	Everything covered to this point has been done in preparation for the migration of file and directory
 	data. For many people preparation is potentially boring and the real excitement only begins when file
 	data can be used. The next steps demonstrate the techniques that can be used to transfer (migrate)
@@ -1161,7 +1161,7 @@ net rpc share MIGRATE FILES &lt;share-name&gt; -S &lt;source&gt;
 	</p><p>
 	An example for migration of files from a machine called <code class="constant">nt4box</code> to the Samba server
 	from which the process will be handled is shown here:
-<a class="indexterm" name="id2603263"></a>
+<a class="indexterm" name="id2603250"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share migrate files -S nt4box --acls \
     --attrs -U administrator%secret
@@ -1170,17 +1170,17 @@ net rpc share MIGRATE FILES &lt;share-name&gt; -S &lt;source&gt;
 	This command  will migrate all files and directories from all file shares on the Windows server called
 	<code class="constant">nt4box</code> to the Samba server from which migration is initiated. Files that are group-owned
 	will be owned by the user account <code class="constant">administrator</code>.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603302"></a>Share-ACL Migration</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603290"></a>Share-ACL Migration</h4></div></div></div><p>
 	It is possible to have share-ACLs (security descriptors) that won't allow you, even as Administrator, to
 	copy any files or directories into it. Therefor the migration of the share-ACLs has been put into a separate
 	function:
-<a class="indexterm" name="id2603314"></a>
+<a class="indexterm" name="id2603301"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share migrate security -S nt4box -U administrator%secret
 </pre><p>
 	</p><p>
 	This command will only copy the share-ACL of each share on nt4box to your local samba-system.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603345"></a>Simultaneous Share and File Migration</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2603332"></a>Simultaneous Share and File Migration</h4></div></div></div><p>
 	The operating mode shown here is just a combination of the previous three. It first migrates
 	share definitions and then all shared files and directories and finally migrates the share-ACLs:
 </p><pre class="screen">
@@ -1189,12 +1189,12 @@ net rpc share MIGRATE ALL &lt;share-name&gt; -S &lt;source&gt;
 </pre><p>
 	</p><p>
 	An example of simultaneous migration is shown here:
-<a class="indexterm" name="id2603370"></a>
+<a class="indexterm" name="id2603357"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc share migrate all -S w2k3server -U administrator%secret
 </pre><p>
 	This will generate a complete server clone of the <em class="parameter"><code>w2k3server</code></em> server.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603404"></a>Printer Migration</h3></div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603391"></a>Printer Migration</h3></div></div></div><p>
 	The installation of a new server, as with the migration to a new network environment, often is similar to
 	building a house; progress is very rapid from the laying of foundations up to the stage at which
 	the house can be locked up, but the finishing off appears to take longer and longer as building
@@ -1203,7 +1203,7 @@ net rpc share MIGRATE ALL &lt;share-name&gt; -S &lt;source&gt;
 	Printing needs vary greatly depending on the network environment and may be very simple or complex. If
 	the need is very simple, the best solution to the implementation of printing support may well be to
 	re-install everything from a clean slate instead of migrating older configurations. On the other hand,
-	a complex network that is integrated with many international offices and a complex arrangement of local branch
+	a complex network that is integrated with many international offices and a multiplexity of local branch
 	offices, each of which form an inter-twined maze of printing possibilities, the ability to migrate all
 	printer configurations is decidedly beneficial. To manually re-establish a complex printing network
 	will take much time and frustration. Often it will not be possible to find driver files that are
@@ -1219,7 +1219,7 @@ net rpc share MIGRATE ALL &lt;share-name&gt; -S &lt;source&gt;
 	the application that receives the network requests to create the necessary services must call out
 	to the operating system in order to create the underlying printers. The call-out is implemented
 	by way of an interface script that can be specified by the <code class="filename">smb.conf</code> file parameter
-	<a class="link" href="smb.conf.5.html#ADDPRINTERSCRIPT" target="_top">add printer script</a>. This script is essential to the migration process.
+	<a class="link" href="smb.conf.5.html#" target="_top"></a>. This script is essential to the migration process.
 	A suitable example script may be obtained from the <code class="filename">$SAMBA_SOURCES/examples/scripts</code>
 	directory. Take note that this script must be customized to suit the operating system environment
 	and may use its tools to create a print queue.
@@ -1231,29 +1231,29 @@ net rpc share MIGRATE ALL &lt;share-name&gt; -S &lt;source&gt;
 	</p><p>
 	Printer migration from a Windows print server (NT4 or 200x) is shown. This instruction causes the
 	printer share to be created together with the underlying print queue:
-<a class="indexterm" name="id2603542"></a>
+<a class="indexterm" name="id2603526"></a>
 </p><pre class="screen">
 net rpc printer MIGRATE PRINTERS [printer] [misc. options] [targets]
 </pre><p>
 	Printer drivers can be migrated from the Windows print server to the Samba server using this
 	command-line instruction:
-<a class="indexterm" name="id2603562"></a>
+<a class="indexterm" name="id2603547"></a>
 </p><pre class="screen">
 net rpc printer MIGRATE DRIVERS [printer] [misc. options] [targets]
 </pre><p>
 	Printer forms can be migrated with the following operation:
-<a class="indexterm" name="id2603581"></a>
+<a class="indexterm" name="id2603566"></a>
 </p><pre class="screen">
 net rpc printer MIGRATE FORMS [printer] [misc. options] [targets]
 </pre><p>
 	Printer security settings (ACLs) can be migrated from the Windows server to the Samba server using this command:
-<a class="indexterm" name="id2603602"></a>
+<a class="indexterm" name="id2603586"></a>
 </p><pre class="screen">
 net rpc printer MIGRATE SECURITY [printer] [misc. options] [targets]
 </pre><p>
 	Printer configuration settings include factors such as paper size and default paper orientation.
 	These can be migrated from the Windows print server to the Samba server with this command:
-<a class="indexterm" name="id2603623"></a>
+<a class="indexterm" name="id2603608"></a>
 </p><pre class="screen">
 net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets]
 </pre><p>
@@ -1263,14 +1263,14 @@ net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets]
 </p><pre class="screen">
 net rpc printer MIGRATE ALL [printer] [misc. options] [targets]
 </pre><p>
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603657"></a>Controlling Open Files</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603642"></a>Controlling Open Files</h2></div></div></div><p>
 	The man page documents the <code class="literal">net file</code> function suite, which provides the tools to
 	close open files using either RAP or RPC function calls. Please refer to the man page for specific
 	usage information.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603676"></a>Session and Connection Management</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603661"></a>Session and Connection Management</h2></div></div></div><p>
 	The session management interface of the <code class="literal">net session</code> command uses the old RAP
 	method to obtain the list of connections to the Samba server, as shown here:
-<a class="indexterm" name="id2603692"></a>
+<a class="indexterm" name="id2603677"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rap session -S MERLIN -Uroot%not24get
 Computer             User name            Client Type        Opens Idle time
@@ -1285,11 +1285,11 @@ Computer             User name            Client Type        Opens Idle time
 </p><pre class="screen">
 <code class="prompt">root# </code> net rap session close marvel -Uroot%not24get
 </pre><p>
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603742"></a>Printers and ADS</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603727"></a>Printers and ADS</h2></div></div></div><p>
 	When Samba-3 is used within an MS Windows ADS environment, printers shared via Samba will not be browseable
 	until they have been published to the ADS domain. Information regarding published printers may be obtained
 	from the ADS server by executing the <code class="literal">net ads print info</code> command following this syntax:
-<a class="indexterm" name="id2603761"></a>
+<a class="indexterm" name="id2603745"></a>
 </p><pre class="screen">
 net ads printer info &lt;printer_name&gt; &lt;server_name&gt; -Uadministrator%secret
 </pre><p>
@@ -1297,26 +1297,26 @@ net ads printer info &lt;printer_name&gt; &lt;server_name&gt; -Uadministrator%se
 	returned.
 	</p><p>
 	To publish (make available) a printer to ADS, execute the following command:
-<a class="indexterm" name="id2603786"></a>
+<a class="indexterm" name="id2603771"></a>
 </p><pre class="screen">
 net ads printer publish &lt;printer_name&gt; -Uadministrator%secret
 </pre><p>
 	This publishes a printer from the local Samba server to ADS.
 	</p><p>
 	Removal of a Samba printer from ADS is achieved by executing this command:
-<a class="indexterm" name="id2603812"></a>
+<a class="indexterm" name="id2603796"></a>
 </p><pre class="screen">
 net ads printer remove &lt;printer_name&gt; -Uadministrator%secret
 </pre><p>
 	</p><p>
 	A generic search (query) can also be made to locate a printer across the entire ADS domain by executing:
-<a class="indexterm" name="id2603836"></a>
+<a class="indexterm" name="id2603821"></a>
 </p><pre class="screen">
 net ads printer search &lt;printer_name&gt; -Uadministrator%secret
 </pre><p>
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603858"></a>Manipulating the Samba Cache</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603842"></a>Manipulating the Samba Cache</h2></div></div></div><p>
 	Please refer to the <code class="literal">net</code> command man page for information regarding cache management.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603875"></a>Managing IDMAP UID/SID Mappings</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2603860"></a>Managing IDMAP UID/SID Mappings</h2></div></div></div><p>
 	The IDMAP UID to SID, and SID to UID, mappings that are created by <code class="literal">winbindd</code> can be
 	backed up to a text file. The text file can be manually edited, although it is highly recommended that
 	you attempt this only if you know precisely what you are doing.
@@ -1327,7 +1327,7 @@ net ads printer search &lt;printer_name&gt; -Uadministrator%secret
 	</p><p>
 	Winbind must be shut down to dump the IDMAP file. Before restoring a dump file, shut down
 	<code class="literal">winbindd</code> and delete the old <code class="filename">winbindd_idmap.tdb</code> file.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603919"></a>Creating an IDMAP Database Dump File</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603904"></a>Creating an IDMAP Database Dump File</h3></div></div></div><p>
 	The IDMAP database can be dumped to a text file as shown here:
 </p><pre class="screen">
 net idmap dump &lt;full_path_and_tdb_filename&gt; &gt; dumpfile.txt
@@ -1337,7 +1337,7 @@ net idmap dump &lt;full_path_and_tdb_filename&gt; &gt; dumpfile.txt
 </p><pre class="screen">
 net idmap dump /var/lib/samba/winbindd_idmap.tdb &gt; idmap_dump.txt
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603955"></a>Restoring the IDMAP Database Dump File</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603939"></a>Restoring the IDMAP Database Dump File</h3></div></div></div><p>
 	The IDMAP dump file can be restored using the following command:
 </p><pre class="screen">
 net idmap restore idmap_dump.txt
@@ -1350,7 +1350,7 @@ net idmap restore /var/lib/samba/winbindd_idmap.tdb &lt; idmap_dump.txt
 	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="netmisc1"></a>Other Miscellaneous Operations</h2></div></div></div><p>
 	The following command is useful for obtaining basic statistics regarding a Samba domain. This command does
 	not work with current Windows XP Professional clients.
-<a class="indexterm" name="id2604004"></a>
+<a class="indexterm" name="id2603989"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc info
 Domain Name: RAPIDFLY
@@ -1363,7 +1363,7 @@ Num local groups: 6
 	</p><p>
 	Another useful tool is the <code class="literal">net time</code> tool set. This tool may be used to query the
 	current time on the target server as shown here:
-<a class="indexterm" name="id2604041"></a>
+<a class="indexterm" name="id2604025"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net time -S SAURON
 Tue May 17 00:50:43 2005
@@ -1371,19 +1371,19 @@ Tue May 17 00:50:43 2005
 	In the event that it is the intent to pass the time information obtained to the UNIX
 	<code class="literal">/bin/time</code>, it is a good idea to obtain the time from the target server in a format
 	that is ready to be passed through. This may be done by executing:
-<a class="indexterm" name="id2604072"></a>
+<a class="indexterm" name="id2604056"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net time system -S FRODO
 051700532005.16
 </pre><p>
 	The time can be set on a target server by executing:
-<a class="indexterm" name="id2604096"></a>
+<a class="indexterm" name="id2604081"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net time set -S MAGGOT -U Administrator%not24get
 Tue May 17 00:55:30 MDT 2005
 </pre><p>
 	It is possible to obtain the time zone of a server by executing the following command against it:
-<a class="indexterm" name="id2604122"></a>
+<a class="indexterm" name="id2604107"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net time zone -S SAURON
 -0600
diff --git a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html b/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
index db2602b41a..6f62cfdf00 100644
--- a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
+++ b/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
@@ -1,36 +1,36 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�Network Browsing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="ChangeNotes.html" title="Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series"><link rel="next" href="passdb.html" title="Chapter�11.�Account Information Databases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�Network Browsing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChangeNotes.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="passdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter�10.�Network Browsing</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jonathan</span> <span class="orgname">Sutinen Consulting, Inc.</span> <span class="surname">Johnson</span></h3><div class="affiliation"><span class="orgname">Sutinen Consulting, Inc.<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jon@sutinen.com">jon@sutinen.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: September 20, 2006</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579538">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583156">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583364">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584196">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584481">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585120">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586391">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586491">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586539">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�10.�Network Browsing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="ChangeNotes.html" title="Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series"><link rel="next" href="passdb.html" title="Chapter�11.�Account Information Databases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�10.�Network Browsing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChangeNotes.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="passdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter�10.�Network Browsing</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jonathan</span> <span class="orgname">Sutinen Consulting, Inc.</span> <span class="surname">Johnson</span></h3><div class="affiliation"><span class="orgname">Sutinen Consulting, Inc.<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jon@sutinen.com">jon@sutinen.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: September 20, 2006</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579524">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583131">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583338">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584164">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584448">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585087">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586352">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586451">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586500">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2579435"></a>
+<a class="indexterm" name="id2579442"></a>
 <a class="indexterm" name="id2579449"></a>
 <a class="indexterm" name="id2579456"></a>
-<a class="indexterm" name="id2579463"></a>
-<a class="indexterm" name="id2579470"></a>
 This chapter 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; however, 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>
-<a class="indexterm" name="id2579486"></a>
+<a class="indexterm" name="id2579472"></a>
 What is WINS?
 </p><p>
 WINS is a facility that provides resolution of a NetBIOS name to its IP address. WINS is like a
 Dynamic-DNS service for NetBIOS networking names.
 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2579504"></a>
+<a class="indexterm" name="id2579490"></a>
+<a class="indexterm" name="id2579496"></a>
+<a class="indexterm" name="id2579503"></a>
 <a class="indexterm" name="id2579510"></a>
-<a class="indexterm" name="id2579517"></a>
-<a class="indexterm" name="id2579524"></a>
 MS Windows 2000 and later versions can be configured to operate with no NetBIOS
 over TCP/IP. Samba-3 and later versions also support this mode of operation.
 When the use of NetBIOS over TCP/IP has been disabled, 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="id2579538"></a>Features and Benefits</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579524"></a>Features and Benefits</h2></div></div></div><p>
 Charles Dickens once referred to the past in these words: &#8220;<span class="quote"><span class="emphasis"><em>It was the best of times,
 it was the worst of times.</em></span></span>&#8221; The more we look back, the more we long for what was and
 hope it never returns.
 </p><p>
+<a class="indexterm" name="id2579543"></a>
+<a class="indexterm" name="id2579550"></a>
 <a class="indexterm" name="id2579557"></a>
-<a class="indexterm" name="id2579564"></a>
-<a class="indexterm" name="id2579571"></a>
 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
@@ -43,40 +43,40 @@ thousands of seeds per square meter, a seed longevity of more than 7 years, and
 ability to germinate at any time of year, given the right conditions, are some of the
 features that make it such a persistent weed.
 </p><p>
-<a class="indexterm" name="id2579601"></a>
+<a class="indexterm" name="id2579587"></a>
+<a class="indexterm" name="id2579596"></a>
+<a class="indexterm" name="id2579603"></a>
 <a class="indexterm" name="id2579610"></a>
-<a class="indexterm" name="id2579617"></a>
-<a class="indexterm" name="id2579624"></a>
-<a class="indexterm" name="id2579630"></a>
+<a class="indexterm" name="id2579616"></a>
 In this chapter we explore vital aspects of Server Message Block (SMB) 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>
-<a class="indexterm" name="id2579648"></a>
-<a class="indexterm" name="id2579655"></a>
+<a class="indexterm" name="id2579634"></a>
+<a class="indexterm" name="id2579641"></a>
 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 effect stable WINS operations beyond the normal scope of MS WINS.
 </p><p>
+<a class="indexterm" name="id2579655"></a>
+<a class="indexterm" name="id2579662"></a>
 <a class="indexterm" name="id2579669"></a>
-<a class="indexterm" name="id2579676"></a>
-<a class="indexterm" name="id2579683"></a>
 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 operate with
 support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
 </p><p>
-<a class="indexterm" name="id2579697"></a>
-<a class="indexterm" name="id2579704"></a>
-<a class="indexterm" name="id2579710"></a>
+<a class="indexterm" name="id2579683"></a>
+<a class="indexterm" name="id2579690"></a>
+<a class="indexterm" name="id2579696"></a>
 For those networks on which NetBIOS has been disabled (i.e., WINS is not required),
 the use of DNS is necessary for hostname resolution.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579722"></a>What Is Browsing?</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579708"></a>What Is Browsing?</h2></div></div></div><p>
+<a class="indexterm" name="id2579716"></a>
+<a class="indexterm" name="id2579722"></a>
 <a class="indexterm" name="id2579730"></a>
 <a class="indexterm" name="id2579736"></a>
-<a class="indexterm" name="id2579744"></a>
-<a class="indexterm" name="id2579750"></a>
 To most people, browsing means 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.
@@ -84,9 +84,9 @@ clicked, it opens up and shows the shares and printers available on the target s
 What seems so simple is in fact a complex interaction of different technologies.
 The technologies (or methods) employed in making all of this work include:
 </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 machines on the network collate 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>
+<a class="indexterm" name="id2579793"></a>
+<a class="indexterm" name="id2579800"></a>
 <a class="indexterm" name="id2579807"></a>
-<a class="indexterm" name="id2579814"></a>
-<a class="indexterm" name="id2579821"></a>
 The Samba application that controls browse list management and name resolution is
 called <code class="filename">nmbd</code>. The configuration parameters involved in nmbd's operation are:
 </p><p>
@@ -99,33 +99,33 @@ WINS options:
 Those marked with an (*) are the only options that commonly may need to be modified. Even if none of these
 parameters is set, <code class="filename">nmbd</code> will still do its job.
 </p><p>
-<a class="indexterm" name="id2580060"></a>
+<a class="indexterm" name="id2580046"></a>
+<a class="indexterm" name="id2580052"></a>
+<a class="indexterm" name="id2580059"></a>
 <a class="indexterm" name="id2580066"></a>
 <a class="indexterm" name="id2580073"></a>
-<a class="indexterm" name="id2580080"></a>
-<a class="indexterm" name="id2580087"></a>
 For Samba, the WINS Server and WINS Support are mutually exclusive options. When <code class="literal">nmbd</code> is
 started it will fail to execute if both options are set in the <code class="filename">smb.conf</code> file. The <code class="literal">nmbd</code>
 understands that when it spawns an instance of itself to run as a WINS server that it has to use its own WINS
 server also.
 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="netdiscuss"></a>Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2580115"></a>
+<a class="indexterm" name="id2580122"></a>
 <a class="indexterm" name="id2580129"></a>
 <a class="indexterm" name="id2580136"></a>
-<a class="indexterm" name="id2580143"></a>
-<a class="indexterm" name="id2580150"></a>
 All MS Windows networking uses SMB-based messaging.  SMB messaging may be implemented with or without NetBIOS.
 MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing
 out NetBIOS support.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580162"></a>NetBIOS over TCP/IP</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580148"></a>NetBIOS over TCP/IP</h3></div></div></div><p>
+<a class="indexterm" name="id2580156"></a>
+<a class="indexterm" name="id2580163"></a>
 <a class="indexterm" name="id2580170"></a>
-<a class="indexterm" name="id2580177"></a>
-<a class="indexterm" name="id2580184"></a>
-<a class="indexterm" name="id2580190"></a>
+<a class="indexterm" name="id2580176"></a>
 Samba implements NetBIOS, as does MS Windows NT/200x/XP, by encapsulating it over TCP/IP.
 NetBIOS-based networking uses broadcast messaging to effect browse list management. When running NetBIOS over
 TCP/IP, this uses UDP-based messaging.  UDP messages can be broadcast or unicast.
 </p><p>
-<a class="indexterm" name="id2580205"></a>
+<a class="indexterm" name="id2580191"></a>
 Normally, only unicast UDP messaging can be forwarded by routers. The <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a>
 parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP.
 Similarly, the <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameter of <code class="filename">smb.conf</code> implements browse list
@@ -133,54 +133,54 @@ collation using unicast UDP.
 </p><p>
 The methods used by MS Windows to perform name lookup requests (name resolution) is determined by a
 configuration parameter called the NetBIOS node-type. There are four basic NetBIOS node types:
-</p><a class="indexterm" name="id2580254"></a><a class="indexterm" name="id2580261"></a><a class="indexterm" name="id2580267"></a><a class="indexterm" name="id2580274"></a><a class="indexterm" name="id2580281"></a><a class="indexterm" name="id2580288"></a><a class="indexterm" name="id2580295"></a><a class="indexterm" name="id2580301"></a><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>b-node (type 0x01):</em></span> The Windows client will use only
+</p><a class="indexterm" name="id2580240"></a><a class="indexterm" name="id2580247"></a><a class="indexterm" name="id2580253"></a><a class="indexterm" name="id2580260"></a><a class="indexterm" name="id2580267"></a><a class="indexterm" name="id2580274"></a><a class="indexterm" name="id2580281"></a><a class="indexterm" name="id2580287"></a><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>b-node (type 0x01):</em></span> The Windows client will use only
 	NetBIOS broadcast requests using UDP broadcast.</p></li><li><p><span class="emphasis"><em>p-node (type 0x02):</em></span> The Windows client will use point-to-point
 	(NetBIOS unicast) requests using UDP unicast directed to a WINS server.</p></li><li><p><span class="emphasis"><em>m-node (type 0x04):</em></span> The Windows client will first use
 	NetBIOS broadcast requests using UDP broadcast, then it will use (NetBIOS unicast)
 	requests using UDP unicast directed to a WINS server.</p></li><li><p><span class="emphasis"><em>h-node (type 0x08):</em></span> The Windows client will use
 	(NetBIOS unicast) requests using UDP unicast directed to a WINS server, then it will use
 	NetBIOS broadcast requests using UDP broadcast.</p></li></ul></div><p>
+<a class="indexterm" name="id2580336"></a>
+<a class="indexterm" name="id2580343"></a>
 <a class="indexterm" name="id2580350"></a>
 <a class="indexterm" name="id2580357"></a>
 <a class="indexterm" name="id2580364"></a>
 <a class="indexterm" name="id2580371"></a>
-<a class="indexterm" name="id2580378"></a>
-<a class="indexterm" name="id2580385"></a>
 The default Windows network client (or server) network configuration enables NetBIOS over TCP/IP
 and b-node configuration. The use of WINS makes most sense with h-node (hybrid mode) operation so that
 in the event of a WINS breakdown or non-availability, the client can use broadcast-based name resolution.
 </p><p>
-<a class="indexterm" name="id2580400"></a>
+<a class="indexterm" name="id2580386"></a>
+<a class="indexterm" name="id2580395"></a>
+<a class="indexterm" name="id2580402"></a>
 <a class="indexterm" name="id2580409"></a>
 <a class="indexterm" name="id2580416"></a>
-<a class="indexterm" name="id2580423"></a>
+<a class="indexterm" name="id2580422"></a>
 <a class="indexterm" name="id2580430"></a>
-<a class="indexterm" name="id2580436"></a>
-<a class="indexterm" name="id2580444"></a>
 In those networks where Samba is the only SMB server technology, wherever possible <code class="filename">nmbd</code>
 should be configured on one machine as the WINS server. This makes it easy to manage the browsing environment.
 If each network segment is configured with its own Samba WINS server, then the only way to get cross-segment
 browsing to work is by using the <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a> and the <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameters to your <code class="filename">smb.conf</code> file.
 </p><p>
-<a class="indexterm" name="id2580495"></a>
+<a class="indexterm" name="id2580481"></a>
 If only one WINS server is used for an entire multisegment network, then
 the use of the <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a> and the
 <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameters should not be necessary.
 </p><p>
-<a class="indexterm" name="id2580529"></a>
+<a class="indexterm" name="id2580515"></a>
 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.20 release. Hopefully, this will become a
 supported feature of one of the Samba-3 release series. The delay is caused by the fact that this feature has
 not been of sufficient significance to inspire someone to pay a developer to complete it.
 </p><p>
+<a class="indexterm" name="id2580534"></a>
+<a class="indexterm" name="id2580541"></a>
 <a class="indexterm" name="id2580548"></a>
 <a class="indexterm" name="id2580555"></a>
-<a class="indexterm" name="id2580562"></a>
-<a class="indexterm" name="id2580569"></a>
+<a class="indexterm" name="id2580561"></a>
+<a class="indexterm" name="id2580568"></a>
 <a class="indexterm" name="id2580575"></a>
 <a class="indexterm" name="id2580582"></a>
-<a class="indexterm" name="id2580589"></a>
-<a class="indexterm" name="id2580596"></a>
 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 <code class="filename">nmbd</code> 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
@@ -194,15 +194,15 @@ based networking is a life of compromise and trade-offs. WINS stores information
 DNS; consequently, DNS is a poor substitute for WINS given that when NetBIOS over TCP/IP is used, Windows
 clients are designed to use WINS.
 </p><p>
-<a class="indexterm" name="id2580658"></a>
-<a class="indexterm" name="id2580664"></a>
-<a class="indexterm" name="id2580671"></a>
+<a class="indexterm" name="id2580644"></a>
+<a class="indexterm" name="id2580650"></a>
+<a class="indexterm" name="id2580657"></a>
 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 stabilize, particularly across network segments.
 </p><p>
-<a class="indexterm" name="id2580686"></a>
+<a class="indexterm" name="id2580672"></a>
 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 <code class="filename">hosts</code> file. It is located in <code class="filename">%SystemRoot%\System32\Drivers\etc</code>.
@@ -217,46 +217,46 @@ When an MS Windows 200x/XP system attempts to resolve a host name to an IP addre
 	</p></li><li><p>
 	Looks up entries in LMHOSTS, located in <code class="filename">%SystemRoot%\System32\Drivers\etc</code>.
 	</p></li></ol></div><p>
-<a class="indexterm" name="id2580754"></a>
+<a class="indexterm" name="id2580740"></a>
+<a class="indexterm" name="id2580746"></a>
+<a class="indexterm" name="id2580753"></a>
 <a class="indexterm" name="id2580760"></a>
-<a class="indexterm" name="id2580767"></a>
-<a class="indexterm" name="id2580774"></a>
 Given the nature of how the NetBIOS over TCP/IP protocol is implemented, only WINS is capable of resolving
 with any reliability name lookups for service-oriented names such as TEMPTATION&lt;1C&gt;  a NetBIOS
 name query that seeks to find network logon servers. DNS has no concept of service-oriented names such as
 this. In fact, the Microsoft ADS implementation specifically manages a whole range of extended
 service-oriented DNS entries. This type of facility is not implemented and is not supported for the NetBIOS
 over TCP/IP protocol namespace.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580798"></a>TCP/IP without NetBIOS</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580784"></a>TCP/IP without NetBIOS</h3></div></div></div><p>
+<a class="indexterm" name="id2580792"></a>
+<a class="indexterm" name="id2580799"></a>
 <a class="indexterm" name="id2580806"></a>
-<a class="indexterm" name="id2580813"></a>
-<a class="indexterm" name="id2580820"></a>
 All TCP/IP-enabled systems use various forms of hostname resolution. The primary
 methods for TCP/IP hostname resolution involve either a static file (<code class="filename">/etc/hosts</code>)
 or the Domain Name System (DNS). DNS is the technology that makes
 the Internet usable. DNS-based hostname resolution is supported by nearly all
 TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
 </p><p>
-<a class="indexterm" name="id2580842"></a>
+<a class="indexterm" name="id2580828"></a>
+<a class="indexterm" name="id2580834"></a>
+<a class="indexterm" name="id2580841"></a>
 <a class="indexterm" name="id2580848"></a>
-<a class="indexterm" name="id2580855"></a>
-<a class="indexterm" name="id2580862"></a>
 Windows 200x/XP can register its hostname with a Dynamic DNS server (DDNS). It is possible to force register with a
 dynamic DNS server in Windows 200x/XP using <code class="literal">ipconfig /registerdns</code>.
 </p><p>
-<a class="indexterm" name="id2580883"></a>
-<a class="indexterm" name="id2580889"></a>
-<a class="indexterm" name="id2580896"></a>
+<a class="indexterm" name="id2580869"></a>
+<a class="indexterm" name="id2580875"></a>
+<a class="indexterm" name="id2580882"></a>
 With Active Directory, 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 unable to locate each
 other, so network services consequently will be severely impaired.
 </p><p>
+<a class="indexterm" name="id2580897"></a>
+<a class="indexterm" name="id2580904"></a>
 <a class="indexterm" name="id2580911"></a>
 <a class="indexterm" name="id2580918"></a>
 <a class="indexterm" name="id2580925"></a>
-<a class="indexterm" name="id2580932"></a>
-<a class="indexterm" name="id2580939"></a>
-<a class="indexterm" name="id2580945"></a>
+<a class="indexterm" name="id2580931"></a>
 Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an
 Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same
 time <span class="emphasis"><em>not</em></span> use NetBIOS. Where Samba is used as an Active Directory domain member server
@@ -265,11 +265,11 @@ an Active Directory domain, however, if NetBIOS over TCP/IP is disabled, it is n
 appropriate DNS entries for the Samba DMS because they will not be automatically generated either by Samba, or
 by the ADS environment.
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="adsdnstech"></a>DNS and Active Directory</h3></div></div></div><p>
-<a class="indexterm" name="id2580980"></a>
-<a class="indexterm" name="id2580989"></a>
-<a class="indexterm" name="id2580996"></a>
-<a class="indexterm" name="id2581002"></a>
-<a class="indexterm" name="id2581009"></a>
+<a class="indexterm" name="id2580966"></a>
+<a class="indexterm" name="id2580975"></a>
+<a class="indexterm" name="id2580982"></a>
+<a class="indexterm" name="id2580988"></a>
+<a class="indexterm" name="id2580995"></a>
 Occasionally we hear from UNIX network administrators who want to use a UNIX-based DDNS server in place
 of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is
 autoconfigured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost
@@ -277,9 +277,9 @@ certainly be necessary to create service records (SRV records) so MS Active Dire
 hostnames to locate essential network services.  The following are some of the default service records that
 Active Directory requires:
 </p><p>
-<a class="indexterm" name="id2581031"></a>
-<a class="indexterm" name="id2581038"></a>
-<a class="indexterm" name="id2581044"></a>
+<a class="indexterm" name="id2581017"></a>
+<a class="indexterm" name="id2581024"></a>
+<a class="indexterm" name="id2581030"></a>
 The use of DDNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for
 its ability to adequately support the SRV (service) records that are needed for Active Directory. Of course,
 when running ADS, it makes sense to use Microsoft's own DDNS server because of the natural affinity between ADS
@@ -370,40 +370,40 @@ noldor.quenya.org. 1200  IN      A       10.1.1.17
 ;; WHEN: Wed Oct  7 14:39:31 2004
 ;; MSG SIZE  rcvd: 171
 </pre><p>
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2581357"></a>How Browsing Functions</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2581343"></a>How Browsing Functions</h2></div></div></div><p>
+<a class="indexterm" name="id2581351"></a>
+<a class="indexterm" name="id2581358"></a>
 <a class="indexterm" name="id2581365"></a>
 <a class="indexterm" name="id2581372"></a>
-<a class="indexterm" name="id2581379"></a>
-<a class="indexterm" name="id2581386"></a>
-<a class="indexterm" name="id2581392"></a>
+<a class="indexterm" name="id2581378"></a>
 MS Windows machines register their NetBIOS names (i.e., the machine name for each service type in operation)
 on startup.  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,
 whether or not DNS for NetBIOS name resolution is enabled, and so on.
 </p><p>
+<a class="indexterm" name="id2581395"></a>
+<a class="indexterm" name="id2581402"></a>
 <a class="indexterm" name="id2581409"></a>
-<a class="indexterm" name="id2581416"></a>
-<a class="indexterm" name="id2581423"></a>
 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="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a>
 parameter).
 </p><p>
-<a class="indexterm" name="id2581452"></a>
-<a class="indexterm" name="id2581459"></a>
-<a class="indexterm" name="id2581465"></a>
+<a class="indexterm" name="id2581438"></a>
+<a class="indexterm" name="id2581445"></a>
+<a class="indexterm" name="id2581451"></a>
 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>
-<a class="indexterm" name="id2581479"></a>
-<a class="indexterm" name="id2581485"></a>
+<a class="indexterm" name="id2581465"></a>
+<a class="indexterm" name="id2581471"></a>
+<a class="indexterm" name="id2581480"></a>
+<a class="indexterm" name="id2581487"></a>
 <a class="indexterm" name="id2581494"></a>
 <a class="indexterm" name="id2581501"></a>
-<a class="indexterm" name="id2581508"></a>
-<a class="indexterm" name="id2581515"></a>
-<a class="indexterm" name="id2581521"></a>
-<a class="indexterm" name="id2581528"></a>
+<a class="indexterm" name="id2581507"></a>
+<a class="indexterm" name="id2581514"></a>
 During the startup process, an election takes place to create a local master browser (LMB) if one does not
 already exist. On each NetBIOS network one machine will be elected to function as the domain master browser
 (DMB). This domain browsing has nothing to do with MS security Domain Control.  Instead, the DMB serves the
@@ -413,14 +413,14 @@ way every master browser will eventually obtain a complete list of all machines
 the election criteria used, the machine with the highest uptime, or the most senior protocol version or other
 criteria, will win the election as DMB.
 </p><p>
+<a class="indexterm" name="id2581551"></a>
+<a class="indexterm" name="id2581558"></a>
 <a class="indexterm" name="id2581565"></a>
 <a class="indexterm" name="id2581572"></a>
-<a class="indexterm" name="id2581579"></a>
-<a class="indexterm" name="id2581586"></a>
+<a class="indexterm" name="id2581578"></a>
+<a class="indexterm" name="id2581585"></a>
 <a class="indexterm" name="id2581592"></a>
 <a class="indexterm" name="id2581599"></a>
-<a class="indexterm" name="id2581606"></a>
-<a class="indexterm" name="id2581613"></a>
 Where a WINS server is used, the DMB registers its IP address with the WINS server using the name of the
 domain and the NetBIOS name type 1B (e.g., DOMAIN&lt;1B&gt;). All LMBs register their IP addresses with the WINS
 server, also with the name of the domain and the NetBIOS name type of 1D. The 1B name is unique to one
@@ -428,20 +428,20 @@ server within the domain security context, and only one 1D name is registered fo
 Machines that have registered the 1D name will be authoritive browse list maintainers for the network segment
 they are on. The DMB is responsible for synchronizing the browse lists it obtains from the LMBs.
 </p><p>
-<a class="indexterm" name="id2581649"></a>
+<a class="indexterm" name="id2581635"></a>
 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 or addresses.
 </p><p>
-<a class="indexterm" name="id2581662"></a>
+<a class="indexterm" name="id2581648"></a>
 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>
+<a class="indexterm" name="id2581661"></a>
+<a class="indexterm" name="id2581668"></a>
 <a class="indexterm" name="id2581675"></a>
 <a class="indexterm" name="id2581682"></a>
 <a class="indexterm" name="id2581689"></a>
 <a class="indexterm" name="id2581696"></a>
-<a class="indexterm" name="id2581703"></a>
-<a class="indexterm" name="id2581710"></a>
 Samba supports a feature that allows forced synchronization of browse lists across routed networks using the
 <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameter in the <code class="filename">smb.conf</code> file. This causes Samba to contact the
 LMB on a remote network and to request browse list synchronization. This effectively bridges two networks that
@@ -451,12 +451,12 @@ browse list synchronization  and that is distinct from name-to-address resolutio
 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, <code class="filename">/etc/hosts</code>, and so on.
 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="DMB"></a>Configuring Workgroup Browsing</h3></div></div></div><p>
-<a class="indexterm" name="id2581779"></a>
-<a class="indexterm" name="id2581785"></a>
-<a class="indexterm" name="id2581792"></a>
+<a class="indexterm" name="id2581765"></a>
+<a class="indexterm" name="id2581771"></a>
+<a class="indexterm" name="id2581778"></a>
+<a class="indexterm" name="id2581784"></a>
+<a class="indexterm" name="id2581791"></a>
 <a class="indexterm" name="id2581798"></a>
-<a class="indexterm" name="id2581805"></a>
-<a class="indexterm" name="id2581812"></a>
 To configure cross-subnet browsing on a network containing machines in a workgroup, not an NT domain, you need
 to set up one Samba server to be the DMB (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 DMB is to collate the browse lists
@@ -464,86 +464,86 @@ from LMB on all the subnets that have a machine participating in the workgroup.
 as a DMB, each subnet would be an isolated workgroup unable to see any machines on another subnet. It is the
 presence of a DMB that makes cross-subnet browsing possible for a workgroup.
 </p><p>
-<a class="indexterm" name="id2581832"></a>
+<a class="indexterm" name="id2581818"></a>
 In a workgroup environment the DMB must be a Samba server, and there must only be one DMB per workgroup name.
 To set up a Samba server as a DMB, set the following option in the <em class="parameter"><code>[global]</code></em> section
 of the <code class="filename">smb.conf</code> file:
 </p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2581862"></a><em class="parameter"><code>domain master = yes</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2581848"></a><em class="parameter"><code>domain master = yes</code></em></td></tr></table><p>
 </p><p>
-<a class="indexterm" name="id2581877"></a>
-<a class="indexterm" name="id2581884"></a>
+<a class="indexterm" name="id2581863"></a>
+<a class="indexterm" name="id2581870"></a>
 The DMB should preferably be the LMB for its own subnet. In order to achieve this, set the following options
 in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#dmbexample" title="Example�10.1.�Domain Master Browser smb.conf">Domain Master Browser smb.conf</a>
-</p><div class="example"><a name="dmbexample"></a><p class="title"><b>Example�10.1.�Domain Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2581938"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581950"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581962"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581973"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2581988"></a>
-<a class="indexterm" name="id2581995"></a>
+</p><div class="example"><a name="dmbexample"></a><p class="title"><b>Example�10.1.�Domain Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2581924"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581936"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581948"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2581959"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2581974"></a>
+<a class="indexterm" name="id2581981"></a>
 The DMB may be the same machine as the WINS server, if necessary.
 </p><p>
-<a class="indexterm" name="id2582006"></a>
-<a class="indexterm" name="id2582013"></a>
-<a class="indexterm" name="id2582019"></a>
+<a class="indexterm" name="id2581992"></a>
+<a class="indexterm" name="id2581999"></a>
+<a class="indexterm" name="id2582005"></a>
 Next, you should ensure that each of the subnets contains a machine that can act as an LMB for the workgroup.
 Any MS Windows NT/200x/XP machine should be able to do this, as will Windows 9x/Me machines (although these
 tend to get rebooted more often, so it is not such a good idea to use them). To make a Samba server an LMB,
 set the following options in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in
 <a class="link" href="NetworkBrowsing.html#lmbexample" title="Example�10.2.�Local master browser smb.conf">Local master browser smb.conf</a>
-</p><div class="example"><a name="lmbexample"></a><p class="title"><b>Example�10.2.�Local master browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582077"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582089"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582100"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582112"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2582127"></a>
+</p><div class="example"><a name="lmbexample"></a><p class="title"><b>Example�10.2.�Local master browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582063"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582075"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582086"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582098"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2582113"></a>
 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 LMB.
 </p><p>
-<a class="indexterm" name="id2582139"></a>
-<a class="indexterm" name="id2582146"></a>
+<a class="indexterm" name="id2582125"></a>
+<a class="indexterm" name="id2582132"></a>
 The <a class="link" href="smb.conf.5.html#LOCALMASTER" target="_top">local master</a> parameter allows Samba to act as a
 LMB. The <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master</a> causes <code class="literal">nmbd</code>
 to force a browser election on startup and the <a class="link" href="smb.conf.5.html#OSLEVEL" target="_top">os level</a>
 parameter sets Samba high enough so it should win any browser elections.
 </p><p>
-<a class="indexterm" name="id2582199"></a>
+<a class="indexterm" name="id2582185"></a>
 If you have an NT machine on the subnet that you wish to be the LMB, you can disable Samba from
 becoming an LMB by setting the following options in the <em class="parameter"><code>[global]</code></em> section of the
 <code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#nombexample" title="Example�10.3.�smb.conf for Not Being a Master Browser">smb.conf for Not Being a Master Browser</a>.
 </p><p>
-</p><div class="example"><a name="nombexample"></a><p class="title"><b>Example�10.3.�smb.conf for Not Being a Master Browser</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582254"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582266"></a><em class="parameter"><code>local master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582278"></a><em class="parameter"><code>preferred master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582290"></a><em class="parameter"><code>os level = 0</code></em></td></tr></table></div></div><p><br class="example-break">
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582304"></a>Domain Browsing Configuration</h3></div></div></div><p>
+</p><div class="example"><a name="nombexample"></a><p class="title"><b>Example�10.3.�smb.conf for Not Being a Master Browser</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582240"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582252"></a><em class="parameter"><code>local master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582264"></a><em class="parameter"><code>preferred master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582276"></a><em class="parameter"><code>os level = 0</code></em></td></tr></table></div></div><p><br class="example-break">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582290"></a>Domain Browsing Configuration</h3></div></div></div><p>
+<a class="indexterm" name="id2582298"></a>
+<a class="indexterm" name="id2582305"></a>
 <a class="indexterm" name="id2582312"></a>
-<a class="indexterm" name="id2582319"></a>
-<a class="indexterm" name="id2582326"></a>
-<a class="indexterm" name="id2582332"></a>
+<a class="indexterm" name="id2582318"></a>
 If you are adding Samba servers to a Windows NT domain, then you must not set up a Samba server as a DMB.  By
 default, a Windows NT PDC for a domain is also the DMB for that domain. Network browsing may break if a Samba
 server other than the PDC registers the DMB NetBIOS name (<em class="replaceable"><code>DOMAIN</code></em>&lt;1B&gt;) with
 WINS.
 </p><p>
-<a class="indexterm" name="id2582351"></a>
+<a class="indexterm" name="id2582337"></a>
 For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as LMBs as
 described. To make a Samba server a Local Master Browser, set the following options in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#remsmb" title="Example�10.4.�Local Master Browser smb.conf">Local Master Browser
 smb.conf</a>
-</p><div class="example"><a name="remsmb"></a><p class="title"><b>Example�10.4.�Local Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582407"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582419"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582431"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582442"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2582457"></a>
-<a class="indexterm" name="id2582464"></a>
+</p><div class="example"><a name="remsmb"></a><p class="title"><b>Example�10.4.�Local Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582393"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582405"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582417"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2582428"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2582443"></a>
+<a class="indexterm" name="id2582450"></a>
 If you wish to have a Samba server fight the election with machines on the same subnet, you may set the
 <a class="link" href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> parameter to lower levels.  By doing this you can tune the order of machines
 that will become LMBs if they are running. For more details on this, refer to <a class="link" href="NetworkBrowsing.html#browse-force-master" title="Forcing Samba to Be the Master">Forcing Samba to Be the Master</a>.
 </p><p>
-<a class="indexterm" name="id2582499"></a>
-<a class="indexterm" name="id2582505"></a>
-<a class="indexterm" name="id2582512"></a>
+<a class="indexterm" name="id2582485"></a>
+<a class="indexterm" name="id2582491"></a>
+<a class="indexterm" name="id2582498"></a>
 If you have Windows NT machines that are members of the domain on all subnets and you are sure they will
 always be running, you can disable Samba from taking part in browser elections and ever becoming an LMB by
 setting the following options in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown
 in <a class="link" href="NetworkBrowsing.html#xremmb" title="Example�10.5.�smb.conf for Not Being a master browser"><code class="filename">smb.conf</code> for Not Being a master browser</a>
 </p><p>
-</p><div class="example"><a name="xremmb"></a><p class="title"><b>Example�10.5.�<code class="filename">smb.conf</code> for Not Being a master browser</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2582579"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582591"></a><em class="parameter"><code>local master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582602"></a><em class="parameter"><code>preferred master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2582614"></a><em class="parameter"><code>os level = 0</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="xremmb"></a><p class="title"><b>Example�10.5.�<code class="filename">smb.conf</code> for Not Being a master browser</b></p><div class="example-contents"><em class="parameter"><code>[global]</code></em><a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = no</a><a class="link" href="smb.conf.5.html#LOCALMASTER" target="_top">local master = no</a><a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master = no</a><a class="link" href="smb.conf.5.html#OSLEVEL" target="_top">os level = 0</a></div></div><p><br class="example-break">
 </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><p>
-<a class="indexterm" name="id2582641"></a>
-<a class="indexterm" name="id2582647"></a>
-<a class="indexterm" name="id2582654"></a>
-<a class="indexterm" name="id2582661"></a>
-<a class="indexterm" name="id2582668"></a>
-<a class="indexterm" name="id2582675"></a>
-<a class="indexterm" name="id2582682"></a>
+<a class="indexterm" name="id2582616"></a>
+<a class="indexterm" name="id2582622"></a>
+<a class="indexterm" name="id2582629"></a>
+<a class="indexterm" name="id2582636"></a>
+<a class="indexterm" name="id2582643"></a>
+<a class="indexterm" name="id2582649"></a>
+<a class="indexterm" name="id2582656"></a>
 Who becomes the master browser is determined by an election process using broadcasts. Each election packet
 contains a number of parameters that determine what precedence (bias) a host should have in the election. By
 default Samba uses a low precedence and thus loses elections to just about every Windows network server or
@@ -557,10 +557,10 @@ An <a class="link" href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> of
 not MS Windows NT/200x Server. An MS Windows NT/200x Server domain controller uses level 32. The maximum os
 level is 255.
 </p><p>
-<a class="indexterm" name="id2582738"></a>
-<a class="indexterm" name="id2582745"></a>
-<a class="indexterm" name="id2582752"></a>
-<a class="indexterm" name="id2582759"></a>
+<a class="indexterm" name="id2582713"></a>
+<a class="indexterm" name="id2582720"></a>
+<a class="indexterm" name="id2582727"></a>
+<a class="indexterm" name="id2582734"></a>
 If you want Samba to force an election on startup, set the <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master</a> global
 option in <code class="filename">smb.conf</code> to <code class="constant">yes</code>.  Samba will then have a slight advantage over other
 potential master browsers that are not preferred master browsers.  Use this parameter with care, because if
@@ -568,34 +568,34 @@ you have two hosts (whether they are Windows 9x/Me or NT/200x/XP or Samba) on th
 with <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master</a> to <code class="constant">yes</code>, then periodically and continually
 they will force an election in order to become the LMB.
 </p><p>
-<a class="indexterm" name="id2582812"></a>
-<a class="indexterm" name="id2582819"></a>
-<a class="indexterm" name="id2582826"></a>
-<a class="indexterm" name="id2582832"></a>
-<a class="indexterm" name="id2582839"></a>
+<a class="indexterm" name="id2582787"></a>
+<a class="indexterm" name="id2582793"></a>
+<a class="indexterm" name="id2582800"></a>
+<a class="indexterm" name="id2582807"></a>
+<a class="indexterm" name="id2582814"></a>
 If you want Samba to be a <span class="emphasis"><em>DMB</em></span>, then it is recommended that you also set <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master</a> to <code class="constant">yes</code>, because Samba will not become a DMB for the whole of
 your LAN or WAN if it is not also a LMB on its own broadcast isolated subnet.
 </p><p>
-<a class="indexterm" name="id2582871"></a>
-<a class="indexterm" name="id2582877"></a>
-<a class="indexterm" name="id2582884"></a>
-<a class="indexterm" name="id2582891"></a>
-<a class="indexterm" name="id2582898"></a>
+<a class="indexterm" name="id2582846"></a>
+<a class="indexterm" name="id2582852"></a>
+<a class="indexterm" name="id2582859"></a>
+<a class="indexterm" name="id2582866"></a>
+<a class="indexterm" name="id2582872"></a>
 It is possible to configure two Samba servers to attempt to become the DMB for a domain. The first server that
 comes up will be the DMB. All other Samba servers will attempt to become the DMB every 5 minutes. They will
 find that another Samba server is already the DMB and will fail. This provides automatic redundancy should the
 current DMB fail. The network bandwidth overhead of browser elections is relatively small, requiring
 approximately four UDP packets per machine per election. The maximum size of a UDP packet is 576 bytes.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582916"></a>Making Samba the Domain Master</h3></div></div></div><p>
-<a class="indexterm" name="id2582924"></a>
-<a class="indexterm" name="id2582930"></a>
-<a class="indexterm" name="id2582937"></a>
-<a class="indexterm" name="id2582944"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2582891"></a>Making Samba the Domain Master</h3></div></div></div><p>
+<a class="indexterm" name="id2582898"></a>
+<a class="indexterm" name="id2582905"></a>
+<a class="indexterm" name="id2582911"></a>
+<a class="indexterm" name="id2582918"></a>
 The domain master browser is responsible for collating the browse lists of multiple subnets so browsing can
 occur between subnets. You can make Samba act as the domain master browser by setting <a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = yes</a> in <code class="filename">smb.conf</code>. By default it will not be a domain master browser.
 </p><p>
-<a class="indexterm" name="id2582976"></a>
-<a class="indexterm" name="id2582983"></a>
+<a class="indexterm" name="id2582951"></a>
+<a class="indexterm" name="id2582958"></a>
 Do not set Samba to be the domain master for a workgroup that has the same name as an NT/200x domain.  If
 Samba is configured to be the domain master for a workgroup that is present on the same network as a Windows
 NT/200x domain that has the same name, network browsing problems will certainly be experienced.
@@ -603,26 +603,26 @@ NT/200x domain that has the same name, network browsing problems will certainly
 When Samba is the domain master and the master browser, it will listen for master announcements (made roughly
 every 12 minutes) from LMBs on other subnets and then contact them to synchronize browse lists.
 </p><p>
-<a class="indexterm" name="id2583005"></a>
-<a class="indexterm" name="id2583012"></a>
+<a class="indexterm" name="id2582980"></a>
+<a class="indexterm" name="id2582987"></a>
 If you want Samba to be the domain master, you should also set the <a class="link" href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> high
 enough to make sure it wins elections, and set <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master</a> to
 <code class="constant">yes</code>, to get Samba to force an election on startup.
 </p><p>
-<a class="indexterm" name="id2583051"></a>
-<a class="indexterm" name="id2583058"></a>
+<a class="indexterm" name="id2583026"></a>
+<a class="indexterm" name="id2583032"></a>
 All 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>
-<a class="indexterm" name="id2583080"></a>
-<a class="indexterm" name="id2583087"></a>
+<a class="indexterm" name="id2583055"></a>
+<a class="indexterm" name="id2583062"></a>
 	LMBs will be unable to find a DMB because they will be looking only on the local subnet.
 	</p></li><li><p>
-<a class="indexterm" name="id2583102"></a>
+<a class="indexterm" name="id2583076"></a>
 	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>
-<a class="indexterm" name="id2583117"></a>
+<a class="indexterm" name="id2583092"></a>
 If, however, both Samba and your clients are using a WINS server, then:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	LMBs will contact the WINS server and, as long as Samba has registered that it is a DMB with the WINS
@@ -631,44 +631,44 @@ If, however, both Samba and your clients are using a WINS server, then:
 	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="id2583156"></a>Note about Broadcast Addresses</h3></div></div></div><p>
-<a class="indexterm" name="id2583164"></a>
+	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583131"></a>Note about Broadcast Addresses</h3></div></div></div><p>
+<a class="indexterm" name="id2583139"></a>
 If your network uses a zero-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 zeros broadcast, and you will probably find that
 browsing and name lookups will not work.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583178"></a>Multiple Interfaces</h3></div></div></div><p>
-<a class="indexterm" name="id2583186"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583152"></a>Multiple Interfaces</h3></div></div></div><p>
+<a class="indexterm" name="id2583160"></a>
 Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will
 need to use the <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to configure them. For example, the
 machine you are working with has 4 network interfaces; <code class="literal">eth0</code>, <code class="literal">eth1</code>,
 <code class="literal">eth2</code>, <code class="literal">eth3</code> and only interfaces <code class="literal">eth1</code> and
 <code class="literal">eth4</code> should be used by Samba. In this case, the following <code class="filename">smb.conf</code> file entries would
 permit that intent:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583262"></a><em class="parameter"><code>interfaces = eth1, eth4</code></em></td></tr><tr><td><a class="indexterm" name="id2583274"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table><p>
-<a class="indexterm" name="id2583286"></a>
-<a class="indexterm" name="id2583293"></a>
-<a class="indexterm" name="id2583300"></a>
-<a class="indexterm" name="id2583306"></a>
-<a class="indexterm" name="id2583313"></a>
-<a class="indexterm" name="id2583320"></a>
-<a class="indexterm" name="id2583326"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583237"></a><em class="parameter"><code>interfaces = eth1, eth4</code></em></td></tr><tr><td><a class="indexterm" name="id2583248"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table><p>
+<a class="indexterm" name="id2583260"></a>
+<a class="indexterm" name="id2583267"></a>
+<a class="indexterm" name="id2583274"></a>
+<a class="indexterm" name="id2583281"></a>
+<a class="indexterm" name="id2583288"></a>
+<a class="indexterm" name="id2583294"></a>
+<a class="indexterm" name="id2583301"></a>
 The <a class="link" href="smb.conf.5.html#BINDINTERFACESONLY" target="_top">bind interfaces only = Yes</a> is necessary to exclude TCP/IP session
 services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that
 <code class="literal">nmbd</code> will listen for incoming UDP port 137 packets on the unlisted interfaces, but it will
 not answer them. It will, however, send its broadcast packets over the unlisted interfaces. Total isolation of
 ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and
 445 (TCP) on all network interfaces that must not be able to access the Samba server.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583364"></a>Use of the Remote Announce Parameter</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583338"></a>Use of the Remote Announce Parameter</h3></div></div></div><p>
 The <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a> parameter of <code class="filename">smb.conf</code> 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="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a> parameter is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583409"></a><em class="parameter"><code>remote announce = 192.168.12.23 [172.16.21.255] ...</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583384"></a><em class="parameter"><code>remote announce = 192.168.12.23 [172.16.21.255] ...</code></em></td></tr></table><p>
 <span class="emphasis"><em>or</em></span>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583430"></a><em class="parameter"><code>remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583404"></a><em class="parameter"><code>remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</code></em></td></tr></table><p>
 
 where:
 </p><div class="variablelist"><dl><dt><span class="term"><em class="replaceable"><code>192.168.12.23</code></em> and <em class="replaceable"><code>172.16.21.255</code></em></span></dt><dd><p>
-<a class="indexterm" name="id2583458"></a>
-<a class="indexterm" name="id2583467"></a>
+<a class="indexterm" name="id2583432"></a>
+<a class="indexterm" name="id2583441"></a>
 		is either the LMB IP address or the broadcast address of the remote network.
 		That is, the LMB is at 192.168.1.23, or the address could be given as 172.16.21.255 where the netmask
 		is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast
@@ -678,24 +678,24 @@ where:
 		workgroup name of the remote network, 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="id2583504"></a>Use of the Remote Browse Sync Parameter</h3></div></div></div><p>
-<a class="indexterm" name="id2583511"></a>
-<a class="indexterm" name="id2583518"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583478"></a>Use of the Remote Browse Sync Parameter</h3></div></div></div><p>
+<a class="indexterm" name="id2583486"></a>
+<a class="indexterm" name="id2583492"></a>
 The <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameter of <code class="filename">smb.conf</code> is used to announce to another LMB that
 it must synchronize its NetBIOS name list with our Samba LMB. This 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="link" href="smb.conf.5.html#REMOTEBROWSESYNC" target="_top">remote browse sync</a> parameter is:
 
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583568"></a></td></tr></table><p>
-<a class="indexterm" name="id2583574"></a>
-<a class="indexterm" name="id2583581"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583542"></a></td></tr></table><p>
+<a class="indexterm" name="id2583549"></a>
+<a class="indexterm" name="id2583555"></a>
 where <em class="replaceable"><code>192.168.10.40</code></em> is either the IP address of the
 remote LMB or 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="id2583597"></a>WINS: The Windows Internetworking Name Server</h2></div></div></div><p>
-<a class="indexterm" name="id2583605"></a>
-<a class="indexterm" name="id2583612"></a>
-<a class="indexterm" name="id2583619"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2583571"></a>WINS: The Windows Internetworking Name Server</h2></div></div></div><p>
+<a class="indexterm" name="id2583580"></a>
+<a class="indexterm" name="id2583586"></a>
+<a class="indexterm" name="id2583593"></a>
 Use of WINS (either Samba WINS or 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.
@@ -704,18 +704,18 @@ 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>
-<a class="indexterm" name="id2583637"></a>
-<a class="indexterm" name="id2583644"></a>
+<a class="indexterm" name="id2583612"></a>
+<a class="indexterm" name="id2583618"></a>
 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. Thus, all NetBIOS names are 16 characters long (including the
 name_type information).
 </p><p>
-<a class="indexterm" name="id2583659"></a>
-<a class="indexterm" name="id2583666"></a>
-<a class="indexterm" name="id2583673"></a>
-<a class="indexterm" name="id2583680"></a>
+<a class="indexterm" name="id2583634"></a>
+<a class="indexterm" name="id2583641"></a>
+<a class="indexterm" name="id2583648"></a>
+<a class="indexterm" name="id2583654"></a>
 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
@@ -725,21 +725,21 @@ information can only be provided via WINS or via a statically configured
 <code class="filename">lmhosts</code> file that must reside on all clients in the
 absence of WINS.
 </p><p>
-<a class="indexterm" name="id2583704"></a>
-<a class="indexterm" name="id2583711"></a>
-<a class="indexterm" name="id2583718"></a>
-<a class="indexterm" name="id2583724"></a>
-<a class="indexterm" name="id2583731"></a>
+<a class="indexterm" name="id2583679"></a>
+<a class="indexterm" name="id2583686"></a>
+<a class="indexterm" name="id2583692"></a>
+<a class="indexterm" name="id2583699"></a>
+<a class="indexterm" name="id2583706"></a>
 WINS also forces browse list synchronization by all LMBs. LMBs must synchronize their browse list with the
 DMB, and WINS helps the LMB to identify its DMB. By definition this will work only within a single workgroup.
 Note that the DMB has nothing to do with what is referred to as an MS Windows NT domain. The latter is a
 reference to a security environment, while the DMB refers to the master controller for browse list information
 only.
 </p><p>
-<a class="indexterm" name="id2583749"></a>
-<a class="indexterm" name="id2583755"></a>
-<a class="indexterm" name="id2583762"></a>
-<a class="indexterm" name="id2583769"></a>
+<a class="indexterm" name="id2583723"></a>
+<a class="indexterm" name="id2583730"></a>
+<a class="indexterm" name="id2583737"></a>
+<a class="indexterm" name="id2583744"></a>
 WINS will work correctly only if every client TCP/IP protocol stack
 is configured to use the WINS servers. Any client that is not
 configured to use the WINS server will continue to use only broadcast-based
@@ -756,16 +756,16 @@ To configure Samba to register with a WINS server, just add <a class="link" href
 </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
 Never use <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a> together with <a class="link" href="smb.conf.5.html#WINSSERVER" target="_top">wins server = 10.0.0.18</a> particularly not using its 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="id2583876"></a>WINS Server Configuration</h3></div></div></div><p>
-<a class="indexterm" name="id2583884"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2583843"></a>WINS Server Configuration</h3></div></div></div><p>
+<a class="indexterm" name="id2583851"></a>
 Either a Samba server or a Windows NT server machine may be set up
 as a WINS server. To configure a Samba server to be a WINS server, you must
 add to the <code class="filename">smb.conf</code> file on the selected Server the following line to
 the <em class="parameter"><code>[global]</code></em> section:
 </p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583915"></a><em class="parameter"><code>wins support = yes</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2583882"></a><em class="parameter"><code>wins support = yes</code></em></td></tr></table><p>
 </p><p>
-<a class="indexterm" name="id2583930"></a>
+<a class="indexterm" name="id2583897"></a>
 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
@@ -774,14 +774,14 @@ least set the parameter to &#8220;<span class="quote">no</span>&#8221; on all th
 Machines configured with <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a> will keep a list of
 all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
 </p><p>
-<a class="indexterm" name="id2583964"></a>
+<a class="indexterm" name="id2583931"></a>
 It is strongly recommended to set up only one WINS server. Do not set the <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a> option on more than one Samba server on a network.
 </p><p>
-<a class="indexterm" name="id2583988"></a>
-<a class="indexterm" name="id2583996"></a>
-<a class="indexterm" name="id2584003"></a>
-<a class="indexterm" name="id2584010"></a>
-<a class="indexterm" name="id2584017"></a>
+<a class="indexterm" name="id2583955"></a>
+<a class="indexterm" name="id2583963"></a>
+<a class="indexterm" name="id2583970"></a>
+<a class="indexterm" name="id2583977"></a>
+<a class="indexterm" name="id2583984"></a>
 To configure Windows NT/200x Server as a WINS server, install and configure the WINS service. See the Windows
 NT/200x documentation for details.  Windows NT/200x WINS servers can replicate to each other, allowing more
 than one to be set up in a complex subnet environment. Because Microsoft refuses to document the replication
@@ -789,14 +789,14 @@ protocols, Samba cannot currently participate in these replications. It is possi
 replication protocol may be defined in the future, in which case more than one Samba machine could be set up
 as a WINS server.  Currently only one Samba server should have the <a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a> parameter set.
 </p><p>
-<a class="indexterm" name="id2584049"></a>
-<a class="indexterm" name="id2584056"></a>
+<a class="indexterm" name="id2584016"></a>
+<a class="indexterm" name="id2584023"></a>
 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-&gt;Network-&gt;Protocols-&gt;TCP-&gt;WINS Server</span> dialogs in Windows 9x/Me or Windows NT/200x. To tell a
 Samba server the IP address of the WINS server, add the following line to the <em class="parameter"><code>[global]</code></em> section of all <code class="filename">smb.conf</code> files:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584100"></a><em class="parameter"><code>wins server = &lt;name or IP address&gt;</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584067"></a><em class="parameter"><code>wins server = &lt;name or IP address&gt;</code></em></td></tr></table><p>
 where &lt;name or IP address&gt; is either the DNS name of the WINS server
 machine or its IP address.
 </p><p>
@@ -806,18 +806,18 @@ server acting as the WINS server itself. If you set both the
 <a class="link" href="smb.conf.5.html#WINSSERVER" target="_top">wins server = &lt;name&gt;</a> option then
 <code class="literal">nmbd</code> will fail to start.
 </p><p>
-<a class="indexterm" name="id2584161"></a>
-<a class="indexterm" name="id2584167"></a>
-<a class="indexterm" name="id2584174"></a>
-<a class="indexterm" name="id2584181"></a>
+<a class="indexterm" name="id2584128"></a>
+<a class="indexterm" name="id2584135"></a>
+<a class="indexterm" name="id2584142"></a>
+<a class="indexterm" name="id2584149"></a>
 There are two possible scenarios for setting up cross-subnet browsing.
 The first details setting up cross-subnet browsing on a network containing
 Windows 9x/Me, Samba, and Windows NT/200x 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="id2584196"></a>WINS Replication</h3></div></div></div><p>
-<a class="indexterm" name="id2584204"></a>
-<a class="indexterm" name="id2584213"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584164"></a>WINS Replication</h3></div></div></div><p>
+<a class="indexterm" name="id2584172"></a>
+<a class="indexterm" name="id2584181"></a>
 Samba-3 does not support native WINS replication. There was an approach to implement it, called
 <code class="filename">wrepld</code>, but it was never ready for action and the development is now discontinued.
 </p><p>
@@ -825,11 +825,11 @@ Meanwhile, there is a project named <code class="filename">samba4WINS</code>, wh
 run the Samba-4 WINS server parallel to Samba-3 since version 3.0.21. More information about
 <code class="filename">samba4WINS</code> are available at http://ftp.sernet.de/pub/samba4WINS.
 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584250"></a>Static WINS Entries</h3></div></div></div><p>
-<a class="indexterm" name="id2584258"></a>
-<a class="indexterm" name="id2584264"></a>
-<a class="indexterm" name="id2584271"></a>
-<a class="indexterm" name="id2584278"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584217"></a>Static WINS Entries</h3></div></div></div><p>
+<a class="indexterm" name="id2584225"></a>
+<a class="indexterm" name="id2584232"></a>
+<a class="indexterm" name="id2584238"></a>
+<a class="indexterm" name="id2584245"></a>
 Adding static entries to your Samba WINS server is actually fairly easy.  All you have to do is add a line to
 <code class="filename">wins.dat</code>, typically located in <code class="filename">/usr/local/samba/var/locks</code> or <code class="filename">/var/run/samba</code>.
 </p><p>
@@ -837,8 +837,8 @@ Entries in <code class="filename">wins.dat</code> take the form of:
 </p><pre class="programlisting">
 "NAME#TYPE" TTL ADDRESS+ FLAGS
 </pre><p>
-<a class="indexterm" name="id2584324"></a>
-<a class="indexterm" name="id2584331"></a>
+<a class="indexterm" name="id2584291"></a>
+<a class="indexterm" name="id2584298"></a>
 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.
@@ -856,47 +856,47 @@ To make a NetBIOS name static (permanent), simply set the TTL to 0, like this:
 "MADMAN#03" 0 192.168.1.2 66R
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2584403"></a>
-<a class="indexterm" name="id2584410"></a>
-<a class="indexterm" name="id2584417"></a>
-<a class="indexterm" name="id2584424"></a>
-<a class="indexterm" name="id2584431"></a>
-<a class="indexterm" name="id2584438"></a>
-<a class="indexterm" name="id2584445"></a>
+<a class="indexterm" name="id2584370"></a>
+<a class="indexterm" name="id2584377"></a>
+<a class="indexterm" name="id2584384"></a>
+<a class="indexterm" name="id2584391"></a>
+<a class="indexterm" name="id2584398"></a>
+<a class="indexterm" name="id2584405"></a>
+<a class="indexterm" name="id2584412"></a>
 The NetBIOS flags may be interpreted as additive hexadecimal values: 00 - Broadcast node registration, 20 -
 Peer node registration, 40 - Meta node registration, 60 - Hybrid node registration, 02 - Permanent name, 04 -
 Active name, 80 - Group name. The 'R' indicates this is a registration record. Thus 66R means: Hybrid node
 active and permanent NetBIOS name. These values may be found in the <code class="filename">nameserv.h</code> header
 file from the Samba source code repository. These are the values for the NB flags.
 </p><p>
-<a class="indexterm" name="id2584469"></a>
+<a class="indexterm" name="id2584436"></a>
 Though this method works with early Samba-3 versions, there is 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="id2584481"></a>Helpful Hints</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2584448"></a>Helpful Hints</h2></div></div></div><p>
 The following hints should be carefully considered because 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="id2584492"></a>Windows Networking Protocols</h3></div></div></div><p>
-<a class="indexterm" name="id2584500"></a>
-<a class="indexterm" name="id2584507"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584459"></a>Windows Networking Protocols</h3></div></div></div><p>
+<a class="indexterm" name="id2584468"></a>
+<a class="indexterm" name="id2584474"></a>
 A common cause of browsing problems results from the installation of more than one protocol on an MS Windows
 machine.
 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 Do not use more than one protocol on MS Windows clients.
 </p></div><p>
-<a class="indexterm" name="id2584525"></a>
-<a class="indexterm" name="id2584532"></a>
+<a class="indexterm" name="id2584492"></a>
+<a class="indexterm" name="id2584499"></a>
 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 the most suitable machine will predictably
 win and thus retain its role.
 </p><p>
-<a class="indexterm" name="id2584547"></a>
-<a class="indexterm" name="id2584554"></a>
-<a class="indexterm" name="id2584561"></a>
-<a class="indexterm" name="id2584568"></a>
-<a class="indexterm" name="id2584574"></a>
-<a class="indexterm" name="id2584581"></a>
+<a class="indexterm" name="id2584514"></a>
+<a class="indexterm" name="id2584521"></a>
+<a class="indexterm" name="id2584528"></a>
+<a class="indexterm" name="id2584535"></a>
+<a class="indexterm" name="id2584542"></a>
+<a class="indexterm" name="id2584548"></a>
 The election process is <span class="emphasis"><em>fought out, so to speak</em></span> over every NetBIOS network interface. In
 the case of a Windows 9x/Me 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/Me machine is
@@ -904,8 +904,8 @@ the only one with both protocols, then the LMB may be won on the NetBIOS interfa
 Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then
 cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail.
 </p><p>
-<a class="indexterm" name="id2584606"></a>
-<a class="indexterm" name="id2584612"></a>
+<a class="indexterm" name="id2584573"></a>
+<a class="indexterm" name="id2584580"></a>
 Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me.  The Windows NT4, 200x, and XP use
 common protocols. These are roughly referred to as the Windows NT family, but it should be recognized that
 2000 and XP/2003 introduce new protocol extensions that cause them to behave differently from MS Windows NT4.
@@ -913,31 +913,31 @@ Generally, where a server does not support the newer or extended protocol, these
 protocols.
 </p><p>
 The safest rule of all to follow is: Use only one protocol!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584634"></a>Name Resolution Order</h3></div></div></div><p>
-<a class="indexterm" name="id2584642"></a>
-<a class="indexterm" name="id2584648"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584601"></a>Name Resolution Order</h3></div></div></div><p>
+<a class="indexterm" name="id2584609"></a>
+<a class="indexterm" name="id2584616"></a>
 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  static and hard to maintain.</p></li><li><p>Broadcast  uses UDP and cannot resolve names across remote segments.</p></li></ul></div><p>
 Alternative means of name resolution include:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Static <code class="filename">/etc/hosts</code>   hard to maintain and lacks name_type info.</p></li><li><p>DNS  is a good choice but lacks essential NetBIOS name_type information.</p></li></ul></div><p>
-<a class="indexterm" name="id2584717"></a>
-<a class="indexterm" name="id2584724"></a>
+<a class="indexterm" name="id2584684"></a>
+<a class="indexterm" name="id2584691"></a>
 Many sites want to restrict DNS lookups and avoid broadcast name
 resolution traffic. The <em class="parameter"><code>name resolve order</code></em> parameter is of great help here.
 The syntax of the <em class="parameter"><code>name resolve order</code></em> parameter is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584751"></a><em class="parameter"><code>name resolve order = wins lmhosts bcast host</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584718"></a><em class="parameter"><code>name resolve order = wins lmhosts bcast host</code></em></td></tr></table><p>
 <span class="emphasis"><em>or</em></span>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584772"></a><em class="parameter"><code>name resolve order = wins lmhosts  	(eliminates bcast and host)</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584739"></a><em class="parameter"><code>name resolve order = wins lmhosts  	(eliminates bcast and host)</code></em></td></tr></table><p>
 The default is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584790"></a><em class="parameter"><code>name resolve order = host lmhost wins bcast</code></em></td></tr></table><p>
-<a class="indexterm" name="id2584802"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2584757"></a><em class="parameter"><code>name resolve order = host lmhost wins bcast</code></em></td></tr></table><p>
+<a class="indexterm" name="id2584769"></a>
 where &#8220;<span class="quote">host</span>&#8221; refers to the native methods used by the UNIX system to implement the
 gethostbyname() function call. This is normally controlled by <code class="filename">/etc/host.conf</code>,
 <code class="filename">/etc/nsswitch.conf</code> and <code class="filename">/etc/resolv.conf</code>.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2584837"></a>Technical Overview of Browsing</h2></div></div></div><p>
-<a class="indexterm" name="id2584845"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2584804"></a>Technical Overview of Browsing</h2></div></div></div><p>
+<a class="indexterm" name="id2584812"></a>
 SMB networking provides a mechanism by which clients can access a list
 of machines in a network called <a class="link" href="smb.conf.5.html#BROWSELIST" target="_top">browse list</a>. This list
 contains machines that are ready to offer file and/or print services
@@ -947,48 +947,48 @@ list is heavily used by all SMB clients. Configuration of SMB
 browsing has been problematic for some Samba users, hence this
 document.
 </p><p>
-<a class="indexterm" name="id2584874"></a>
-<a class="indexterm" name="id2584881"></a>
-<a class="indexterm" name="id2584888"></a>
+<a class="indexterm" name="id2584841"></a>
+<a class="indexterm" name="id2584848"></a>
+<a class="indexterm" name="id2584855"></a>
 MS Windows 2000 and later versions, as with Samba-3 and later versions, 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>
-<a class="indexterm" name="id2584904"></a>
-<a class="indexterm" name="id2584911"></a>
+<a class="indexterm" name="id2584871"></a>
+<a class="indexterm" name="id2584878"></a>
 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 cannot 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="id2584924"></a>Browsing Support in Samba</h3></div></div></div><p>
-<a class="indexterm" name="id2584932"></a>
-<a class="indexterm" name="id2584938"></a>
-<a class="indexterm" name="id2584945"></a>
-<a class="indexterm" name="id2584952"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2584891"></a>Browsing Support in Samba</h3></div></div></div><p>
+<a class="indexterm" name="id2584899"></a>
+<a class="indexterm" name="id2584905"></a>
+<a class="indexterm" name="id2584912"></a>
+<a class="indexterm" name="id2584919"></a>
 Samba facilitates browsing. The browsing is supported by <span class="application">nmbd</span>
 and is also controlled by options in the <code class="filename">smb.conf</code> file.
 Samba can act as an LMB for a workgroup, and the ability
 to support domain logons and scripts is now available.
 </p><p>
-<a class="indexterm" name="id2584976"></a>
-<a class="indexterm" name="id2584983"></a>
-<a class="indexterm" name="id2584990"></a>
+<a class="indexterm" name="id2584944"></a>
+<a class="indexterm" name="id2584950"></a>
+<a class="indexterm" name="id2584957"></a>
 Samba can also act as a DMB for a workgroup. This
 means that it will collate lists from LMBs 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>
-<a class="indexterm" name="id2585005"></a>
+<a class="indexterm" name="id2584972"></a>
 Do 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
 DMB 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>
-<a class="indexterm" name="id2585021"></a>
-<a class="indexterm" name="id2585028"></a>
+<a class="indexterm" name="id2584988"></a>
+<a class="indexterm" name="id2584995"></a>
 <code class="literal">nmbd</code> 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 200x can be configured as
@@ -997,40 +997,40 @@ a WAN, 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 the WINS server.
 </p></div><p>
-<a class="indexterm" name="id2585051"></a>
+<a class="indexterm" name="id2585018"></a>
 To get browsing to work, you need to run <code class="literal">nmbd</code> as usual, but must
 use the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> option in <code class="filename">smb.conf</code>
 to control what workgroup Samba becomes a part of.
 </p><p>
-<a class="indexterm" name="id2585086"></a>
+<a class="indexterm" name="id2585053"></a>
 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 used only for &#8220;<span class="quote">unusual</span>&#8221; purposes: announcements over the
 Internet, for example. See <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE" target="_top">remote announce</a> in the <code class="filename">smb.conf</code> man page.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585120"></a>Problem Resolution</h3></div></div></div><p>
-<a class="indexterm" name="id2585128"></a>
-<a class="indexterm" name="id2585135"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585087"></a>Problem Resolution</h3></div></div></div><p>
+<a class="indexterm" name="id2585095"></a>
+<a class="indexterm" name="id2585102"></a>
 If something does not work, the <code class="filename">log.nmbd</code> file will help
 to track down the problem. Try a <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> of 2 or 3 for finding
 problems. Also note that the current browse list usually gets stored
 in text form in a file called <code class="filename">browse.dat</code>.
 </p><p>
-<a class="indexterm" name="id2585171"></a>
-<a class="indexterm" name="id2585178"></a>
+<a class="indexterm" name="id2585138"></a>
+<a class="indexterm" name="id2585145"></a>
 If it does not work, you should still be able to
 type the server name as <code class="filename">\\SERVER</code> in <code class="literal">filemanager</code>, then
 press enter, and <code class="literal">filemanager</code> should display the list of available shares.
 </p><p>
-<a class="indexterm" name="id2585208"></a>
-<a class="indexterm" name="id2585215"></a>
+<a class="indexterm" name="id2585175"></a>
+<a class="indexterm" name="id2585182"></a>
 Some people find browsing fails because they do not have the global
 <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a> set to a valid account. Remember that the
 IPC$ connection that lists the shares is done as guest and so you must have a valid guest account.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2585242"></a>
-<a class="indexterm" name="id2585248"></a>
-<a class="indexterm" name="id2585255"></a>
-<a class="indexterm" name="id2585262"></a>
-<a class="indexterm" name="id2585269"></a>
+<a class="indexterm" name="id2585209"></a>
+<a class="indexterm" name="id2585215"></a>
+<a class="indexterm" name="id2585222"></a>
+<a class="indexterm" name="id2585229"></a>
+<a class="indexterm" name="id2585236"></a>
 The <code class="literal">IPC$</code> share is used by all SMB/CIFS clients to obtain the list of resources that is
 available on the server. This is the source of the list of shares and printers when browsing an SMB/CIFS
 server (also Windows machines) using the Windows Explorer to browse resources through the Windows Network
@@ -1038,10 +1038,10 @@ Neighborhood (also called My Network Places) through to a Windows server. At thi
 a connection to the <code class="literal">\\server\IPC4</code> resource.  Clicking on a share will then open up a
 connection to the <code class="literal">\\server\share</code>.
 </p></div><p>
-<a class="indexterm" name="id2585306"></a>
-<a class="indexterm" name="id2585313"></a>
-<a class="indexterm" name="id2585320"></a>
-<a class="indexterm" name="id2585326"></a>
+<a class="indexterm" name="id2585273"></a>
+<a class="indexterm" name="id2585280"></a>
+<a class="indexterm" name="id2585287"></a>
+<a class="indexterm" name="id2585293"></a>
 MS Windows 2000 and later (as with Samba) can be configured to disallow
 anonymous (i.e., 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
@@ -1049,22 +1049,22 @@ name of the currently logged-in user to query the IPC$ share. MS Windows
 9x/Me clients are not able to do this and thus will not be able to browse
 server resources.
 </p><p>
-<a class="indexterm" name="id2585350"></a>
+<a class="indexterm" name="id2585310"></a>
 The other big problem people have is that their broadcast address,
 netmask, or IP address is wrong (specified with the <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option
 in <code class="filename">smb.conf</code>)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585378"></a>Cross-Subnet Browsing</h3></div></div></div><p>
-<a class="indexterm" name="id2585386"></a>
-<a class="indexterm" name="id2585395"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2585339"></a>Cross-Subnet Browsing</h3></div></div></div><p>
+<a class="indexterm" name="id2585347"></a>
+<a class="indexterm" name="id2585356"></a>
 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>
-<a class="indexterm" name="id2585409"></a>
-<a class="indexterm" name="id2585416"></a>
-<a class="indexterm" name="id2585423"></a>
-<a class="indexterm" name="id2585429"></a>
-<a class="indexterm" name="id2585436"></a>
-<a class="indexterm" name="id2585443"></a>
+<a class="indexterm" name="id2585370"></a>
+<a class="indexterm" name="id2585377"></a>
+<a class="indexterm" name="id2585384"></a>
+<a class="indexterm" name="id2585390"></a>
+<a class="indexterm" name="id2585397"></a>
+<a class="indexterm" name="id2585404"></a>
 To see browse lists that span TCP/IP subnets (i.e., networks separated by routers that do not pass broadcast
 traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names. This will
 allow NetBIOS name-to-IP address translation to be completed by a direct query of the WINS server. This is
@@ -1076,33 +1076,33 @@ announce</code></em> are designed to get around the natural limitations that pre
 propagation. The hacks are not a universal solution and they should not be used in place of WINS, they are
 considered last resort methods.
 </p><p>
-<a class="indexterm" name="id2585480"></a>
-<a class="indexterm" name="id2585487"></a>
-<a class="indexterm" name="id2585494"></a>
-<a class="indexterm" name="id2585501"></a>
+<a class="indexterm" name="id2585441"></a>
+<a class="indexterm" name="id2585448"></a>
+<a class="indexterm" name="id2585455"></a>
+<a class="indexterm" name="id2585462"></a>
 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 Windows 9x/Me and Windows NT/200x/XP, this is in the TCP/IP Properties, under Network
 settings; for Samba, this is in the <code class="filename">smb.conf</code> file.
 </p><p>
-<a class="indexterm" name="id2585523"></a>
-<a class="indexterm" name="id2585530"></a>
-<a class="indexterm" name="id2585536"></a>
+<a class="indexterm" name="id2585484"></a>
+<a class="indexterm" name="id2585491"></a>
+<a class="indexterm" name="id2585497"></a>
 It is possible to operate Samba-3 without NetBIOS over TCP/IP. If you do this, be warned that if used outside
 of MS ADS, this will forgo network browsing support. ADS permits network browsing support through DNS,
 providing appropriate DNS records are inserted for all Samba servers.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2585549"></a>Behavior of Cross-Subnet Browsing</h4></div></div></div><p>
-<a class="indexterm" name="id2585557"></a>
-<a class="indexterm" name="id2585564"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2585510"></a>Behavior of Cross-Subnet Browsing</h4></div></div></div><p>
+<a class="indexterm" name="id2585518"></a>
+<a class="indexterm" name="id2585525"></a>
 Cross-subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several
 years to get the code that correctly achieves this, 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 in <a class="link" href="NetworkBrowsing.html#browsing1" title="Figure�10.1.�Cross-Subnet Browsing Example.">Cross-Subnet Browsing Example</a>.
 </p><div class="figure"><a name="browsing1"></a><p class="title"><b>Figure�10.1.�Cross-Subnet Browsing Example.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/browsing1.png" width="216" alt="Cross-Subnet Browsing Example."></div></div></div><br class="figure-break"><p>
-<a class="indexterm" name="id2585632"></a>
-<a class="indexterm" name="id2585638"></a>
-<a class="indexterm" name="id2585645"></a>
+<a class="indexterm" name="id2585592"></a>
+<a class="indexterm" name="id2585599"></a>
+<a class="indexterm" name="id2585606"></a>
 This consists of three subnets (1, 2, 3) connected by two routers (R1, R2), which do not pass broadcasts.
 Subnet 1 has five machines on it, subnet 2 has four machines, and subnet 3 has four machines. Assume for the
 moment that all machines are configured to be in the same workgroup (for simplicity's sake). Machine N1_C on
@@ -1110,9 +1110,9 @@ subnet 1 is configured as the DMB (i.e., it will collate the browse lists for th
 configured as a WINS server, and all the other machines are configured to register their NetBIOS names with
 it.
 </p><p>
-<a class="indexterm" name="id2585664"></a>
-<a class="indexterm" name="id2585671"></a>
-<a class="indexterm" name="id2585678"></a>
+<a class="indexterm" name="id2585625"></a>
+<a class="indexterm" name="id2585632"></a>
+<a class="indexterm" name="id2585638"></a>
 As these machines are booted up, elections for master browsers
 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
@@ -1120,19 +1120,19 @@ subnet 3. These machines are known as LMBs for
 their particular subnet. N1_C has an advantage in winning as the
 LMB on subnet 1 because it is set up as DMB.
 </p><p>
-<a class="indexterm" name="id2585693"></a>
-<a class="indexterm" name="id2585700"></a>
+<a class="indexterm" name="id2585654"></a>
+<a class="indexterm" name="id2585660"></a>
 On each of the three networks, machines that are configured to offer sharing services will broadcast that they
 are offering these services. The LMB 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>
-<a class="indexterm" name="id2585717"></a>
-<a class="indexterm" name="id2585724"></a>
-<a class="indexterm" name="id2585731"></a>
-<a class="indexterm" name="id2585738"></a>
-<a class="indexterm" name="id2585744"></a>
+<a class="indexterm" name="id2585678"></a>
+<a class="indexterm" name="id2585684"></a>
+<a class="indexterm" name="id2585691"></a>
+<a class="indexterm" name="id2585698"></a>
+<a class="indexterm" name="id2585705"></a>
 For each network, the LMB on that network is
 considered <span class="emphasis"><em>authoritative</em></span> for all the names it receives via
 local broadcast. This is because a machine seen by the LMB
@@ -1143,7 +1143,7 @@ the LMBs learn about when collating their
 browse lists have not been directly seen. These records are
 called <span class="emphasis"><em>non-authoritative.</em></span>
 </p><p>
-<a class="indexterm" name="id2585776"></a>
+<a class="indexterm" name="id2585736"></a>
 At this point the browse lists appear as shown in <a class="link" href="NetworkBrowsing.html#browsubnet" title="Table�10.1.�Browse Subnet Example 1">Browse Subnet Example 1</a>
 (these are the machines you would see in your network neighborhood if you looked in it on a particular network
 right now).
@@ -1152,19 +1152,19 @@ right now).
 </p><p>
 At this point all the subnets are separate, and no machine is seen across any of the subnets.
 </p><p>
-<a class="indexterm" name="id2585870"></a>
-<a class="indexterm" name="id2585877"></a>
-<a class="indexterm" name="id2585883"></a>
-<a class="indexterm" name="id2585890"></a>
+<a class="indexterm" name="id2585831"></a>
+<a class="indexterm" name="id2585837"></a>
+<a class="indexterm" name="id2585844"></a>
+<a class="indexterm" name="id2585851"></a>
 Now examine subnet 2 in <a class="link" href="NetworkBrowsing.html#brsbex" title="Table�10.2.�Browse Subnet Example 2">Browse Subnet Example 2</a>.  As soon as N2_B has become the
 LMB, it looks for a DMB with which to synchronize its browse list. It does this by querying the WINS server
 (N2_D) for the IP address associated with the NetBIOS name WORKGROUP&lt;1B&gt;. This name was registered by
 the DMB (N1_C) with the WINS server as soon as it was started.
 </p><p>
-<a class="indexterm" name="id2585916"></a>
-<a class="indexterm" name="id2585922"></a>
-<a class="indexterm" name="id2585929"></a>
-<a class="indexterm" name="id2585936"></a>
+<a class="indexterm" name="id2585876"></a>
+<a class="indexterm" name="id2585883"></a>
+<a class="indexterm" name="id2585890"></a>
+<a class="indexterm" name="id2585897"></a>
 Once N2_B knows the address of the DMB, it tells the DMB that it is the LMB
 for subnet 2 by sending the DMB a
 <span class="emphasis"><em>MasterAnnouncement</em></span> packet to UDP port 138.  It then
@@ -1177,14 +1177,14 @@ lists look like those in <a class="link" href="NetworkBrowsing.html#brsbex" titl
 </p><div class="table"><a name="brsbex"></a><p class="title"><b>Table�10.2.�Browse Subnet Example 2</b></p><div class="table-contents"><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></div><br class="table-break"><p>
-<a class="indexterm" name="id2586051"></a>
+<a class="indexterm" name="id2586011"></a>
 Servers with an (*) after them are non-authoritative names.
 </p><p>
-<a class="indexterm" name="id2586062"></a>
+<a class="indexterm" name="id2586023"></a>
 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 see only the servers on their own subnet.
 </p><p>
-<a class="indexterm" name="id2586076"></a>
+<a class="indexterm" name="id2586036"></a>
 The same sequence of events that occurred for N2_B now occurs for the LMB on subnet 3 (N3_D). When it
 synchronizes browse lists with the DMB (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 will appear as shown in <a class="link" href="NetworkBrowsing.html#brsex2" title="Table�10.3.�Browse Subnet Example 3">Browse Subnet Example 3</a>
@@ -1198,9 +1198,9 @@ At this point, users looking in their Network Neighborhood on
 subnets 1 or 3 will see all the servers on all subnets, while users on
 subnet 2 will still see only the servers on subnets 1 and 2, but not 3.
 </p><p>
-<a class="indexterm" name="id2586192"></a>
-<a class="indexterm" name="id2586199"></a>
-<a class="indexterm" name="id2586205"></a>
+<a class="indexterm" name="id2586153"></a>
+<a class="indexterm" name="id2586160"></a>
+<a class="indexterm" name="id2586166"></a>
 Finally, the LMB for subnet 2 (N2_B) will sync again
 with the DMB (N1_C) and will receive the missing
 server entries. Finally, as when a steady state (if no machines
@@ -1221,7 +1221,7 @@ steady-state operation.
 </p><p>
 If either router R1 or R2 fails, the following will occur:
 </p><div class="orderedlist"><ol type="1"><li><p>
-<a class="indexterm" name="id2586335"></a>
+<a class="indexterm" name="id2586296"></a>
 	Names of computers on each side of the inaccessible network fragments
 	will be maintained for as long as 36 minutes in the Network Neighborhood
 	lists.
@@ -1229,26 +1229,26 @@ If either router R1 or R2 fails, the following will occur:
 	Attempts to connect to these inaccessible computers will fail, but the
 	names will not be removed from the Network Neighborhood lists.
 	</p></li><li><p>
-<a class="indexterm" name="id2586360"></a>
-<a class="indexterm" name="id2586367"></a>
-<a class="indexterm" name="id2586374"></a>
+<a class="indexterm" name="id2586321"></a>
+<a class="indexterm" name="id2586328"></a>
+<a class="indexterm" name="id2586335"></a>
 	If one of the fragments is cut off from the WINS server, it will only
 	be able to access servers on its local subnet using subnet-isolated
 	broadcast NetBIOS name resolution. The effect is 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="id2586391"></a>Common Errors</h2></div></div></div><p>
-<a class="indexterm" name="id2586399"></a>
-<a class="indexterm" name="id2586406"></a>
+	</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="id2586352"></a>Common Errors</h2></div></div></div><p>
+<a class="indexterm" name="id2586360"></a>
+<a class="indexterm" name="id2586367"></a>
 Many questions are asked on the mailing lists regarding browsing. The majority of browsing
 problems originate from 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="id2586418"></a>Flushing the Samba NetBIOS Name Cache</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586378"></a>Flushing the Samba NetBIOS Name Cache</h3></div></div></div><p>
 How Can One Flush the Samba NetBIOS Name Cache without Restarting Samba?
 </p><p>
-<a class="indexterm" name="id2586430"></a>
-<a class="indexterm" name="id2586437"></a>
-<a class="indexterm" name="id2586444"></a>
-<a class="indexterm" name="id2586451"></a>
+<a class="indexterm" name="id2586391"></a>
+<a class="indexterm" name="id2586398"></a>
+<a class="indexterm" name="id2586405"></a>
+<a class="indexterm" name="id2586412"></a>
 Samba's <code class="literal">nmbd</code> process controls all browse list handling. Under normal circumstances it is
 safe to restart <code class="literal">nmbd</code>. This will effectively flush the Samba NetBIOS name cache and cause it
 to be rebuilt. This does not make certain that a rogue machine name will not reappear
@@ -1258,47 +1258,47 @@ want to clear a rogue machine from the list, every machine on the network must b
 shut down and restarted 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 (perhaps months).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586491"></a>Server Resources Cannot Be Listed</h3></div></div></div><p>&#8220;<span class="quote">My Client Reports "&#8216;<span class="quote">This server is not configured to list shared resources."</span>&#8217;</span>&#8221;</p><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586451"></a>Server Resources Cannot Be Listed</h3></div></div></div><p>&#8220;<span class="quote">My Client Reports "&#8216;<span class="quote">This server is not configured to list shared resources."</span>&#8217;</span>&#8221;</p><p>
 Your guest account is probably invalid for some reason. Samba uses the
 guest account for browsing in <code class="literal">smbd</code>. Check that your guest account is
 valid.
-</p><p>Also see <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a> in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586539"></a>I Get an "<span class="errorname">Unable to browse the network</span>" Error</h3></div></div></div><p>This error can have multiple causes:
-<a class="indexterm" name="id2586551"></a>
+</p><p>Also see <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a> in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586500"></a>I Get an "<span class="errorname">Unable to browse the network</span>" Error</h3></div></div></div><p>This error can have multiple causes:
+<a class="indexterm" name="id2586511"></a>
 	</p><div class="itemizedlist"><ul type="disc"><li><p>There is no LMB. Configure <span class="application">nmbd</span>
 			or any other machine to serve as LMB.</p></li><li><p>You cannot log onto the machine that is the LMB.
 			Can you log on to it as a guest user? </p></li><li><p>There is no IP connectivity to the LMB.
-			Can you reach it by broadcast?</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586586"></a>Browsing of Shares and Directories is Very Slow</h3></div></div></div><p>&#8220;<span class="quote">
-<a class="indexterm" name="id2586595"></a>
+			Can you reach it by broadcast?</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586546"></a>Browsing of Shares and Directories is Very Slow</h3></div></div></div><p>&#8220;<span class="quote">
+<a class="indexterm" name="id2586556"></a>
 There are only two machines on a test network. One is a Samba server, the other a Windows XP machine.
 Authentication and logons work perfectly, but when I try to explore shares on the Samba server, the
 Windows XP client becomes unresponsive. Sometimes it does not respond for some minutes. Eventually,
 Windows Explorer will respond and displays files and directories without problem.
 </span>&#8221;
 </p><p>&#8220;<span class="quote">
-<a class="indexterm" name="id2586614"></a>
+<a class="indexterm" name="id2586575"></a>
 But, the share is immediately available from a command shell (<code class="literal">cmd</code>, followed by
 exploration with DOS command. Is this a Samba problem, or is it a Windows problem? How can I solve this?
 </span>&#8221;</p><p>
 Here are a few possibilities:
 </p><div class="variablelist"><dl><dt><span class="term">Bad Networking Hardware</span></dt><dd><p>
-<a class="indexterm" name="id2586646"></a>
-<a class="indexterm" name="id2586652"></a>
-<a class="indexterm" name="id2586659"></a>
-<a class="indexterm" name="id2586666"></a>
-<a class="indexterm" name="id2586673"></a>
+<a class="indexterm" name="id2586606"></a>
+<a class="indexterm" name="id2586613"></a>
+<a class="indexterm" name="id2586620"></a>
+<a class="indexterm" name="id2586627"></a>
+<a class="indexterm" name="id2586634"></a>
 		Most common defective hardware problems center around low cost or defective hubs, routers,
 		network interface controllers (NICs), and bad wiring. If one piece of hardware is defective,
 		the whole network may suffer. Bad networking hardware can cause data corruption. Most bad
 		networking hardware problems are accompanied by an increase in apparent network traffic,
 		but not all.
 		</p></dd><dt><span class="term">The Windows XP WebClient</span></dt><dd><p>
-<a class="indexterm" name="id2586698"></a>
+<a class="indexterm" name="id2586659"></a>
 		A number of sites have reported similar slow network browsing problems and found that when
 		the WebClient service is turned off, the problem disappears. This is certainly something
 		that should be explored because it is a simple solution  if it works.
 		</p></dd><dt><span class="term">Inconsistent WINS Configuration</span></dt><dd><p>
-<a class="indexterm" name="id2586724"></a>
-<a class="indexterm" name="id2586730"></a>
+<a class="indexterm" name="id2586684"></a>
+<a class="indexterm" name="id2586691"></a>
 		This type of problem is common when one client is configured to use a WINS server (that is
 		a TCP/IP configuration setting) and there is no WINS server on the network. Alternatively,
 		this will happen if there is a WINS server and Samba is not configured to use it. The use of
@@ -1306,14 +1306,14 @@ Here are a few possibilities:
 		of NetBIOS over TCP/IP is disabled on all clients, Samba should not be configured as a WINS
 		server, nor should it be configured to use one.
 		</p></dd><dt><span class="term">Incorrect DNS Configuration</span></dt><dd><p>
-<a class="indexterm" name="id2586757"></a>
-<a class="indexterm" name="id2586764"></a>
+<a class="indexterm" name="id2586718"></a>
+<a class="indexterm" name="id2586725"></a>
 		If use of NetBIOS over TCP/IP is disabled, Active Directory is in use and the DNS server
 		has been incorrectly configured. For further information refer to
 		<a class="link" href="NetworkBrowsing.html#adsdnstech" title="DNS and Active Directory">DNS and Active Directory</a>.
-		</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586786"></a>Invalid Cached Share References Affects Network Browsing</h3></div></div></div><p>
-<a class="indexterm" name="id2586794"></a>
-<a class="indexterm" name="id2586801"></a>
+		</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2586746"></a>Invalid Cached Share References Affects Network Browsing</h3></div></div></div><p>
+<a class="indexterm" name="id2586755"></a>
+<a class="indexterm" name="id2586762"></a>
 Cached references on your MS Windows client (workstation or server) to shares or servers that no longer exist
 can cause MS Windows Explorer to appear unresponsive as it tries to connect to these shares. After a delay
 (can take a long time) it times out and browsing will appear to be mostly normal again.
@@ -1331,7 +1331,7 @@ Removal of stale network links needs to be done on a per-user basis. Alternately
 shortcuts from the MS Windows Explorer in <code class="literal">My Network Places</code> just by right-clicking them and
 selecting <span class="emphasis"><em>Delete.</em></span>
 </p></div><p>
-<a class="indexterm" name="id2586874"></a>
+<a class="indexterm" name="id2586835"></a>
 Samba users have reported that these stale references negatively affect network browsing with Windows, Samba,
 and Novell servers. It is suspected to be a universal problem not directly related to the Samba
 server. Samba users may experience this more often due to Samba being somewhat viewed as an experimenter's
diff --git a/docs/htmldocs/Samba3-HOWTO/Other-Clients.html b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html
index ef02bd3339..f02db6be62 100644
--- a/docs/htmldocs/Samba3-HOWTO/Other-Clients.html
+++ b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html
@@ -1,17 +1,17 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�44.�Samba and Other CIFS Clients</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Portability.html" title="Chapter�43.�Portability"><link rel="next" href="speed.html" title="Chapter�45.�Samba Performance Tuning"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�44.�Samba and Other CIFS Clients</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Portability.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="speed.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter�44.�Samba and Other CIFS Clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="orgname">IBM</span> <span class="surname">McDonough</span></h3><span class="contrib">OS/2</span>�<div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689543">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689627">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689633">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689752">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689809">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2689902">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689908">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689991">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690017">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690075">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690107">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690164">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690233">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690254">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690450">Windows NT 3.1</a></span></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689543"></a>Macintosh Clients</h2></div></div></div><p>
-<a class="indexterm" name="id2689551"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�44.�Samba and Other CIFS Clients</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Portability.html" title="Chapter�43.�Portability"><link rel="next" href="speed.html" title="Chapter�45.�Samba Performance Tuning"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�44.�Samba and Other CIFS Clients</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Portability.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="speed.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter�44.�Samba and Other CIFS Clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="orgname">IBM</span> <span class="surname">McDonough</span></h3><span class="contrib">OS/2</span>�<div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689679">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689763">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689769">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689888">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689945">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690038">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690044">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690127">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690153">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690211">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690243">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690300">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690369">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690390">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690586">Windows NT 3.1</a></span></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689679"></a>Macintosh Clients</h2></div></div></div><p>
+<a class="indexterm" name="id2689687"></a>
 Yes. <a class="ulink" href="http://www.thursby.com/" target="_top">Thursby</a> has a CIFS client/server called <a class="ulink" href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a>.  They test it against Windows 95, Windows
 NT/200x/XP, and Samba for compatibility issues. At the time of this writing, DAVE was at version 5.1. Please
 refer to Thursby's Web site for more information regarding this product.
 </p><p> 
-<a class="indexterm" name="id2689578"></a>
-<a class="indexterm" name="id2689585"></a>
+<a class="indexterm" name="id2689714"></a>
+<a class="indexterm" name="id2689721"></a>
 Alternatives include two free implementations of AppleTalk for several kinds of UNIX machines and several more
 commercial ones.  These products allow you to run file services and print services natively to Macintosh
 users, with no additional support required on the Macintosh. The two free implementations are <a class="ulink" href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk</a> and <a class="ulink" href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP</a>.  What Samba offers MS Windows users, these
 packages offer to Macs.  For more info on these packages, Samba, and Linux (and other UNIX-based systems), see
 <a class="ulink" href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html.</a>
-</p><p>Newer versions of the Macintosh (Mac OS X) include Samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689627"></a>OS2 Client</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689633"></a>Configuring OS/2 Warp Connect or OS/2 Warp 4</h3></div></div></div><p>Basically, you need three components:</p><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client (IBM peer)</p></li><li><p>TCP/IP (Internet support) </p></li><li><p>The &#8220;<span class="quote">NetBIOS over TCP/IP</span>&#8221; driver (TCPBEUI)</p></li></ul></div><p>Installing the first two together with the base operating 
+</p><p>Newer versions of the Macintosh (Mac OS X) include Samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689763"></a>OS2 Client</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689769"></a>Configuring OS/2 Warp Connect or OS/2 Warp 4</h3></div></div></div><p>Basically, you need three components:</p><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client (IBM peer)</p></li><li><p>TCP/IP (Internet support) </p></li><li><p>The &#8220;<span class="quote">NetBIOS over TCP/IP</span>&#8221; driver (TCPBEUI)</p></li></ul></div><p>Installing the first two together with the base operating 
 		system on a blank system is explained in the Warp manual. If Warp 
 		has already been installed, but you now want to install the 
 		networking support, use the &#8220;<span class="quote">Selective Install for Networking</span>&#8221; 
@@ -26,7 +26,7 @@ packages offer to Macs.  For more info on these packages, Samba, and Linux (and
 		to the <span class="guimenu">Names List</span> or specify a  WINS server (NetBIOS 
 		Nameserver in IBM and RFC terminology). For Warp Connect, you 
 		may need to download an update for <code class="constant">IBM Peer</code> to bring it on 
-		the same level as Warp 4. See the IBM OS/2 Warp Web page</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689752"></a>Configuring Other Versions of OS/2</h3></div></div></div><p>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</p><p>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is
+		the same level as Warp 4. See the IBM OS/2 Warp Web page</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689888"></a>Configuring Other Versions of OS/2</h3></div></div></div><p>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</p><p>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is
 		available from 
 		<a class="ulink" href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top">
 		ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>. In a nutshell, edit
@@ -37,7 +37,7 @@ packages offer to Macs.  For more info on these packages, Samba, and Linux (and
 		</pre><p>before you install the client. Also, do not use the included NE2000 driver because it is buggy.
 		Try the NE2000 or NS2000 driver from <a class="ulink" href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top">
  		ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689809"></a>Printer Driver Download for OS/2 Clients</h3></div></div></div><p>Create a share called <em class="parameter"><code>[PRINTDRV]</code></em> that is 
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689945"></a>Printer Driver Download for OS/2 Clients</h3></div></div></div><p>Create a share called <em class="parameter"><code>[PRINTDRV]</code></em> that is 
 		world-readable. Copy your OS/2 driver files there. The <code class="filename">.EA_</code>
 		files must still be separate, so you will need to use the original install files
 		and not copy an installed driver from an OS/2 system.</p><p>Install the NT driver first for that printer. Then, add to your <code class="filename">smb.conf</code> a parameter,
@@ -50,7 +50,7 @@ packages offer to Macs.  For more info on these packages, Samba, and Linux (and
 		you the driver is not available. On the second attempt, it 
 		will work. This is fixed simply by adding the device name
   		 to the mapping, after which it will work on the first attempt.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689902"></a>Windows for Workgroups</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689908"></a>Latest TCP/IP Stack from Microsoft</h3></div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690038"></a>Windows for Workgroups</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690044"></a>Latest TCP/IP Stack from Microsoft</h3></div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
 for Workgroups. The early TCP/IP stacks had lots of bugs.</p><p> 
 Microsoft has released an incremental upgrade to its TCP/IP 32-bit VxD drivers. The latest release can be
 found at ftp.microsoft.com, located in <code class="filename">/Softlib/MSLFILES/TCP32B.EXE</code>.  There is an
@@ -60,7 +60,7 @@ update.txt file there that describes the problems that were fixed. New files inc
 <code class="filename">NETSTAT.EXE</code>, and <code class="filename">NBTSTAT.EXE</code>.
 </p><p>
 More information about this patch is available in <a class="ulink" href="http://support.microsoft.com/kb/q99891/" target="_top">Knowledge Base article 99891</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689991"></a>Delete .pwl Files After Password Change</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690127"></a>Delete .pwl Files After Password Change</h3></div></div></div><p>
 Windows for Workgroups does a lousy job with passwords. When you change passwords on either
 the UNIX box or the PC, the safest thing to do is delete the .pwl files in the Windows
 directory. The PC will complain about not finding the files, but will soon get over it,
@@ -70,16 +70,16 @@ If you do not do this, you may find that Windows for Workgroups remembers and us
 password, even if you told it a new one.
 </p><p> 
 Often Windows for Workgroups will totally ignore a password you give it in a dialog box.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690017"></a>Configuring Windows for Workgroups Password Handling</h3></div></div></div><p>
-<a class="indexterm" name="id2690026"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690153"></a>Configuring Windows for Workgroups Password Handling</h3></div></div></div><p>
+<a class="indexterm" name="id2690162"></a>
 There is a program call <code class="filename">admincfg.exe</code> on the last disk (disk 8) of the WFW 3.11 disk set.
 To install it, type <strong class="userinput"><code>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</code></strong>.  Then add an icon
 for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> menu.  This program allows
 you to control how WFW handles passwords, Disable Password Caching and so on, for use with <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690075"></a>Password Case Sensitivity</h3></div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server.
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690211"></a>Password Case Sensitivity</h3></div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server.
 UNIX passwords can be case-sensitive though. Check the <code class="filename">smb.conf</code> information on
 <a class="link" href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> to specify what characters
-Samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690107"></a>Use TCP/IP as Default Protocol</h3></div></div></div><p>To support print queue reporting, you may find
+Samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690243"></a>Use TCP/IP as Default Protocol</h3></div></div></div><p>To support print queue reporting, you may find
 that you have to use TCP/IP as the default protocol under
 Windows for Workgroups. For some reason, if you leave NetBEUI as the default,
 it may break the print queue reporting on some systems.
@@ -94,7 +94,7 @@ performance with a large value (16384 or larger). Other people have
 reported that anything over 3072 slows things down enormously. One
 person even reported a speed drop of a factor of 30 when he went from
 3072 to 8192.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690164"></a>Windows 95/98</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690300"></a>Windows 95/98</h2></div></div></div><p>
 When using Windows 95 OEM SR2, the following updates are recommended where Samba
 is being used. Please note that the changes documented in 
 <a class="link" href="Other-Clients.html#speedimpr" title="Speed Improvement">Speed Improvement</a> will affect you once these
@@ -109,11 +109,11 @@ install the <code class="literal">OLEUPD.EXE</code> fix. This
 fix may stop your machine from hanging for an extended period when exiting
 Outlook, and you may notice a significant speedup when accessing network
 neighborhood services.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690233"></a>Speed Improvement</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690369"></a>Speed Improvement</h3></div></div></div><p>
 Configure the Windows 95 TCP/IP registry settings to give better
 performance. I use a program called <code class="literal">MTUSPEED.exe</code> that I got off the
 Internet. There are various other utilities of this type freely available.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690254"></a>Windows 2000 Service Pack 2</h2></div></div></div><p> 
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690390"></a>Windows 2000 Service Pack 2</h2></div></div></div><p> 
 There are several annoyances with Windows 2000 SP2, one of which
 only appears when using a Samba server to host user profiles
 to Windows 2000 SP2 clients in a Windows domain. This assumes
@@ -133,7 +133,7 @@ for more details on this option. Also note that the
 releases prior to Samba 2.2.2.
 </p><p> 
 <a class="link" href="Other-Clients.html#minimalprofile" title="Example�44.1.�Minimal Profile Share">Following example</a> provides a minimal profile share.
-</p><div class="example"><a name="minimalprofile"></a><p class="title"><b>Example�44.1.�Minimal Profile Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[profile]</code></em></td></tr><tr><td><a class="indexterm" name="id2690345"></a><em class="parameter"><code>path = /export/profile</code></em></td></tr><tr><td><a class="indexterm" name="id2690357"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2690368"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr><tr><td><a class="indexterm" name="id2690380"></a><em class="parameter"><code>nt acl support = no</code></em></td></tr><tr><td><a class="indexterm" name="id2690392"></a><em class="parameter"><code>read only = no</code></em></td></tr></table></div></div><br class="example-break"><p>
+</p><div class="example"><a name="minimalprofile"></a><p class="title"><b>Example�44.1.�Minimal Profile Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[profile]</code></em></td></tr><tr><td><a class="indexterm" name="id2690481"></a><em class="parameter"><code>path = /export/profile</code></em></td></tr><tr><td><a class="indexterm" name="id2690493"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2690504"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr><tr><td><a class="indexterm" name="id2690516"></a><em class="parameter"><code>nt acl support = no</code></em></td></tr><tr><td><a class="indexterm" name="id2690528"></a><em class="parameter"><code>read only = no</code></em></td></tr></table></div></div><br class="example-break"><p>
 The reason for this bug is that the Windows 200x SP2 client copies
 the security descriptor for the profile that contains
 the Samba server's SID, and not the domain SID. The client
@@ -145,7 +145,7 @@ When the <a class="link" href="smb.conf.5.html#NTACLSUPPORT" target="_top">nt ac
 the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client
 to set a default ACL for the profile. This default ACL includes:
 </p><p><span class="emphasis"><em>DOMAIN\user 	&#8220;<span class="quote">Full Control</span>&#8221;</em></span>&gt;</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This bug does not occur when using Winbind to
-create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690450"></a>Windows NT 3.1</h2></div></div></div><p>If you have problems communicating across routers with Windows 
+create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690586"></a>Windows NT 3.1</h2></div></div></div><p>If you have problems communicating across routers with Windows 
 NT 3.1 workstations, read <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;Q103765" target="_top">this Microsoft Knowledge Base article:</a>.
 
 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Portability.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="speed.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�43.�Portability�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�45.�Samba Performance Tuning</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html b/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html
index ac72b3d845..e2c4aaec17 100644
--- a/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html
+++ b/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html
@@ -1,24 +1,24 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�26.�System and Account Policies</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="AdvancedNetworkManagement.html" title="Chapter�25.�Advanced Network Management"><link rel="next" href="ProfileMgmt.html" title="Chapter�27.�Desktop Profile Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�26.�System and Account Policies</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="AdvancedNetworkManagement.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="ProfileMgmt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter�26.�System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658637">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2659980">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660075">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660115">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660180">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660338">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660349">Policy Does Not Work</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2658623"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�26.�System and Account Policies</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="AdvancedNetworkManagement.html" title="Chapter�25.�Advanced Network Management"><link rel="next" href="ProfileMgmt.html" title="Chapter�27.�Desktop Profile Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�26.�System and Account Policies</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="AdvancedNetworkManagement.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="ProfileMgmt.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter�26.�System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658770">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660100">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660194">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660235">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660299">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660457">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660469">Policy Does Not Work</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2658757"></a>
 This chapter summarizes the current state of knowledge derived from personal
 practice and knowledge from Samba mailing list subscribers. Before reproduction
 of posted information, every effort has been made to validate the information given.
 Where additional information was uncovered through this validation, it is provided
 also.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658637"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2658645"></a>
-<a class="indexterm" name="id2658652"></a>
-<a class="indexterm" name="id2658659"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658770"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2658778"></a>
+<a class="indexterm" name="id2658785"></a>
+<a class="indexterm" name="id2658792"></a>
 When MS Windows NT 3.5 was introduced, the hot new topic was the ability to implement
 Group Policies for users and groups. Then along came MS Windows NT4 and a few sites
 started to adopt this capability. How do we know that? By the number of &#8220;<span class="quote">boo-boos</span>&#8221;
 (or mistakes) administrators made and then requested help to resolve.
 </p><p>
-<a class="indexterm" name="id2658678"></a>
-<a class="indexterm" name="id2658685"></a>
-<a class="indexterm" name="id2658694"></a>
-<a class="indexterm" name="id2658701"></a>
-<a class="indexterm" name="id2658707"></a>
+<a class="indexterm" name="id2658811"></a>
+<a class="indexterm" name="id2658818"></a>
+<a class="indexterm" name="id2658827"></a>
+<a class="indexterm" name="id2658834"></a>
+<a class="indexterm" name="id2658841"></a>
 By the time that MS Windows 2000 and Active Directory was released, administrators
 got the message: Group Policies are a good thing! They can help reduce administrative
 costs and actually make happier users. But adoption of the true
@@ -27,16 +27,16 @@ and machines were picked up on rather slowly. This was obvious from the Samba
 mailing list back in 2000 and 2001 when there were few postings regarding GPOs and
 how to replicate them in a Samba environment.
 </p><p>
-<a class="indexterm" name="id2658729"></a>
+<a class="indexterm" name="id2658862"></a>
 Judging by the traffic volume since mid 2002, GPOs have become a standard part of
 the deployment in many sites. This chapter reviews techniques and methods that can
 be used to exploit opportunities for automation of control over user desktops and
 network client workstations.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658743"></a>Creating and Managing System Policies</h2></div></div></div><p>
-<a class="indexterm" name="id2658751"></a>
-<a class="indexterm" name="id2658758"></a>
-<a class="indexterm" name="id2658765"></a>
-<a class="indexterm" name="id2658772"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658876"></a>Creating and Managing System Policies</h2></div></div></div><p>
+<a class="indexterm" name="id2658884"></a>
+<a class="indexterm" name="id2658891"></a>
+<a class="indexterm" name="id2658898"></a>
+<a class="indexterm" name="id2658905"></a>
 Under MS Windows platforms, particularly those following the release of MS Windows
 NT4 and MS Windows 95, it is possible to create a type of file that would be placed
 in the NETLOGON share of a domain controller. As the client logs onto the network,
@@ -44,9 +44,9 @@ this file is read and the contents initiate changes to the registry of the clien
 machine. This file allows changes to be made to those parts of the registry that
 affect users, groups of users, or machines.
 </p><p>
-<a class="indexterm" name="id2658789"></a>
-<a class="indexterm" name="id2658796"></a>
-<a class="indexterm" name="id2658803"></a>
+<a class="indexterm" name="id2658923"></a>
+<a class="indexterm" name="id2658930"></a>
+<a class="indexterm" name="id2658936"></a>
 For MS Windows 9x/Me, this file must be called <code class="filename">Config.POL</code> and may
 be generated using a tool called <code class="filename">poledit.exe</code>, better known as the
 Policy Editor. The policy editor was provided on the Windows 98 installation CD-ROM, but
@@ -54,12 +54,12 @@ disappeared again with the introduction of MS Windows Me. From
 comments of MS Windows network administrators, it would appear that this tool became
 a part of the MS Windows Me Resource Kit.
 </p><p>
-<a class="indexterm" name="id2658832"></a>
+<a class="indexterm" name="id2658965"></a>
 MS Windows NT4 server products include the <span class="emphasis"><em>System Policy Editor</em></span>
 under <span class="guimenu">Start -&gt; Programs -&gt; Administrative Tools</span>.
 For MS Windows NT4 and later clients, this file must be called <code class="filename">NTConfig.POL</code>.
 </p><p>
-<a class="indexterm" name="id2658860"></a>
+<a class="indexterm" name="id2658994"></a>
 New with the introduction of MS Windows 2000 was the Microsoft Management Console
 or MMC. This tool is the new wave in the ever-changing landscape of Microsoft
 methods for management of network access and security. Every new Microsoft product
@@ -67,10 +67,10 @@ or technology seems to make the old rules obsolete and introduces newer and more
 complex tools and methods. To Microsoft's credit, the MMC does appear to
 be a step forward, but improved functionality comes at a great price.
 </p><p>
-<a class="indexterm" name="id2658878"></a>
-<a class="indexterm" name="id2658885"></a>
-<a class="indexterm" name="id2658892"></a>
-<a class="indexterm" name="id2658899"></a>
+<a class="indexterm" name="id2659012"></a>
+<a class="indexterm" name="id2659018"></a>
+<a class="indexterm" name="id2659025"></a>
+<a class="indexterm" name="id2659032"></a>
 Before embarking on the configuration of network and system policies, it is highly
 advisable to read the documentation available from Microsoft's Web site regarding
 <a class="ulink" href="http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp" target="_top">
@@ -80,16 +80,16 @@ be read and understood. Try searching on the Microsoft Web site for &#8220;<span
 </p><p>
 What follows is a brief discussion with some helpful notes. The information provided
 here is incomplete  you are warned.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658932"></a>Windows 9x/ME Policies</h3></div></div></div><p>
-<a class="indexterm" name="id2658940"></a>
-<a class="indexterm" name="id2658946"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659065"></a>Windows 9x/ME Policies</h3></div></div></div><p>
+<a class="indexterm" name="id2659073"></a>
+<a class="indexterm" name="id2659080"></a>
 	You need the Windows 98 Group Policy Editor to set up Group Profiles under Windows 9x/Me.
 	It can be found on the original full-product Windows 98 installation CD-ROM under
 	<code class="filename">tools\reskit\netadmin\poledit</code>. Install this using the
 	Add/Remove Programs facility, and then click on <span class="guiicon">Have Disk</span>.
 	</p><p>
-<a class="indexterm" name="id2658973"></a>
-<a class="indexterm" name="id2658980"></a>
+<a class="indexterm" name="id2659106"></a>
+<a class="indexterm" name="id2659113"></a>
 	Use the Group Policy Editor to create a policy file that specifies the location of
 	user profiles and/or <code class="filename">My Documents</code>, and so on. Then save these
 	settings in a file called <code class="filename">Config.POL</code> that needs to be placed in the
@@ -99,25 +99,25 @@ here is incomplete  you are warned.
 	</p><p>
 	Further details are covered in the Windows 98 Resource Kit documentation.
 	</p><p>
-<a class="indexterm" name="id2659019"></a>
+<a class="indexterm" name="id2659152"></a>
 	If you do not take the correct steps, then every so often Windows 9x/Me will check the
 	integrity of the registry and restore its settings from the backup
 	copy of the registry it stores on each Windows 9x/Me machine. So, you will
 	occasionally notice things changing back to the original settings.
 	</p><p>
-<a class="indexterm" name="id2659034"></a>
-<a class="indexterm" name="id2659041"></a>
+<a class="indexterm" name="id2659168"></a>
+<a class="indexterm" name="id2659174"></a>
 	Install the Group Policy handler for Windows 9x/Me to pick up Group Policies. Look on the
 	Windows 98 CD-ROM in <code class="filename">\tools\reskit\netadmin\poledit</code>.
 	Install Group Policies on a Windows 9x/Me client by double-clicking on
 	<code class="filename">grouppol.inf</code>. Log off and on again a couple of times and see
 	if Windows 98 picks up Group Policies. Unfortunately, this needs to be done on every
 	Windows 9x/Me machine that uses Group Policies.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659069"></a>Windows NT4-Style Policy Files</h3></div></div></div><p>
-<a class="indexterm" name="id2659077"></a>
-<a class="indexterm" name="id2659084"></a>
-<a class="indexterm" name="id2659090"></a>
-<a class="indexterm" name="id2659097"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659202"></a>Windows NT4-Style Policy Files</h3></div></div></div><p>
+<a class="indexterm" name="id2659210"></a>
+<a class="indexterm" name="id2659217"></a>
+<a class="indexterm" name="id2659224"></a>
+<a class="indexterm" name="id2659231"></a>
 	To create or edit <code class="filename">ntconfig.pol</code>, you must use the NT Server
 	Policy Editor, <code class="literal">poledit.exe</code>, which is included with NT4 Server
 	but not with NT workstation. There is a Policy Editor on an NT4
@@ -126,19 +126,19 @@ here is incomplete  you are warned.
 	workstation/server, it will not work with NT clients. However, the files from
 	the NT Server will run happily enough on an NT4 workstation.
 	</p><p>
-<a class="indexterm" name="id2659134"></a>
-<a class="indexterm" name="id2659140"></a>
-<a class="indexterm" name="id2659147"></a>
-<a class="indexterm" name="id2659154"></a>
+<a class="indexterm" name="id2659261"></a>
+<a class="indexterm" name="id2659268"></a>
+<a class="indexterm" name="id2659274"></a>
+<a class="indexterm" name="id2659281"></a>
 	You need <code class="filename">poledit.exe</code>, <code class="filename">common.adm</code>, and <code class="filename">winnt.adm</code>.
 	It is convenient to put the two <code class="filename">*.adm</code> files in  the <code class="filename">c:\winnt\inf</code> 
 	directory, which is where the binary will look for them unless told otherwise. This
 	directory is normally &#8220;<span class="quote">hidden.</span>&#8221;
 	</p><p>
-<a class="indexterm" name="id2659200"></a>
-<a class="indexterm" name="id2659207"></a>
-<a class="indexterm" name="id2659214"></a>
-<a class="indexterm" name="id2659221"></a>
+<a class="indexterm" name="id2659327"></a>
+<a class="indexterm" name="id2659334"></a>
+<a class="indexterm" name="id2659341"></a>
+<a class="indexterm" name="id2659348"></a>
 	The Windows NT Policy Editor is also included with the Service Pack 3 (and
 	later) for Windows NT 4.0. Extract the files using <code class="literal">servicepackname /x</code>
 	 that's <code class="literal">Nt4sp6ai.exe /x</code> for Service Pack 6a. The Policy Editor,
@@ -146,17 +146,17 @@ here is incomplete  you are warned.
 	be extracted as well. It is also possible to download the policy template
 	files for Office97 and get a copy of the Policy Editor. Another possible
 	location is with the Zero Administration Kit available for download from Microsoft.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659257"></a>Registry Spoiling</h4></div></div></div><p>
-<a class="indexterm" name="id2659265"></a>
-<a class="indexterm" name="id2659272"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659384"></a>Registry Spoiling</h4></div></div></div><p>
+<a class="indexterm" name="id2659392"></a>
+<a class="indexterm" name="id2659399"></a>
 			With NT4-style registry-based policy changes, a large number of settings are not
 			automatically reversed as the user logs off. The settings that were in the
 			<code class="filename">NTConfig.POL</code> file were applied to the client machine registry and apply to the
 			hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
 			as tattooing. It can have serious consequences downstream, and the administrator must
 			be extremely careful not to lock out the ability to manage the machine at a later date.
-			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659297"></a>MS Windows 200x/XP Professional Policies</h3></div></div></div><p>
-<a class="indexterm" name="id2659305"></a>
+			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659424"></a>MS Windows 200x/XP Professional Policies</h3></div></div></div><p>
+<a class="indexterm" name="id2659432"></a>
 	Windows NT4 system policies allow the setting of registry parameters specific to
 	users, groups, and computers (client workstations) that are members of the NT4-style
 	domain. Such policy files will work with MS Windows 200x/XP clients also.
@@ -165,8 +165,8 @@ here is incomplete  you are warned.
 	a superset of capabilities compared with NT4-style policies. Obviously, the tool used
 	to create them is different, and the mechanism for implementing them is much improved.
 	</p><p>
-	<a class="indexterm" name="id2659327"></a>
-<a class="indexterm" name="id2659334"></a>
+	<a class="indexterm" name="id2659454"></a>
+<a class="indexterm" name="id2659461"></a>
 	The older NT4-style registry-based policies are known as <span class="emphasis"><em>Administrative Templates</em></span>
 	in MS Windows 2000/XP GPOs. The latter includes the ability to set various security
 	configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
@@ -175,23 +175,23 @@ here is incomplete  you are warned.
 	feature is the ability to make available particular software Windows applications to particular
 	users and/or groups.
 	</p><p>
-<a class="indexterm" name="id2659362"></a>
-<a class="indexterm" name="id2659369"></a>
-<a class="indexterm" name="id2659376"></a>
+<a class="indexterm" name="id2659490"></a>
+<a class="indexterm" name="id2659496"></a>
+<a class="indexterm" name="id2659503"></a>
 	Remember, NT4 policy files are named <code class="filename">NTConfig.POL</code> and are stored in the root
 	of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username and password
 	and selects the domain name to which the logon will attempt to take place. During the logon process,
 	the client machine reads the <code class="filename">NTConfig.POL</code> file from the NETLOGON share on
 	the authenticating server and modifies the local registry values according to the settings in this file.
 	</p><p>
-<a class="indexterm" name="id2659406"></a>
-<a class="indexterm" name="id2659413"></a>
-<a class="indexterm" name="id2659420"></a>
-<a class="indexterm" name="id2659426"></a>
-<a class="indexterm" name="id2659433"></a>
-<a class="indexterm" name="id2659440"></a>
-<a class="indexterm" name="id2659450"></a>
-<a class="indexterm" name="id2659459"></a>
+<a class="indexterm" name="id2659533"></a>
+<a class="indexterm" name="id2659540"></a>
+<a class="indexterm" name="id2659547"></a>
+<a class="indexterm" name="id2659554"></a>
+<a class="indexterm" name="id2659560"></a>
+<a class="indexterm" name="id2659567"></a>
+<a class="indexterm" name="id2659577"></a>
+<a class="indexterm" name="id2659586"></a>
 	Windows 200x GPOs are feature-rich. They are not stored in the NETLOGON share, but rather part of
 	a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
 	in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
@@ -199,7 +199,7 @@ here is incomplete  you are warned.
 	Group Policy Container (GPC), and the part that is stored in the replicated share called SYSVOL is
 	known as the Group Policy Template (GPT).
 	</p><p>
-<a class="indexterm" name="id2659478"></a>
+<a class="indexterm" name="id2659606"></a>
 	With NT4 clients, the policy file is read and executed only as each user logs onto the network.
 	MS Windows 200x policies are much more complex  GPOs are processed and applied at client machine
 	startup (machine specific part), and when the user logs onto the network, the user-specific part
@@ -207,19 +207,19 @@ here is incomplete  you are warned.
 	to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows
 	the administrator to also set filters over the policy settings. No such equivalent capability
 	exists with NT4-style policy files.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659500"></a>Administration of Windows 200x/XP Policies</h4></div></div></div><p>
-		<a class="indexterm" name="id2659508"></a>
-		<a class="indexterm" name="id2659515"></a>
-<a class="indexterm" name="id2659522"></a>
-<a class="indexterm" name="id2659528"></a>
-<a class="indexterm" name="id2659535"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659627"></a>Administration of Windows 200x/XP Policies</h4></div></div></div><p>
+		<a class="indexterm" name="id2659635"></a>
+		<a class="indexterm" name="id2659642"></a>
+<a class="indexterm" name="id2659649"></a>
+<a class="indexterm" name="id2659656"></a>
+<a class="indexterm" name="id2659662"></a>
 		Instead of using the tool called <span class="application">the System Policy Editor</span>, commonly called Poledit (from the
 		executable name <code class="literal">poledit.exe</code>), <acronym class="acronym">GPOs</acronym> are created and managed using a 
 		<span class="application">Microsoft Management Console</span> <acronym class="acronym">(MMC)</acronym> snap-in as follows:</p><div class="procedure"><ol type="1"><li><p>
 			Go to the Windows 200x/XP menu <span class="guimenu">Start-&gt;Programs-&gt;Administrative Tools</span>
 			and select the MMC snap-in called <span class="guimenuitem">Active Directory Users and Computers</span>
 			</p></li><li><p>
-<a class="indexterm" name="id2659599"></a>
+<a class="indexterm" name="id2659726"></a>
 			Select the domain or organizational unit (OU) that you wish to manage, then right-click
 			to open the context menu for that object, and select the <span class="guibutton">Properties</span>.
 			</p></li><li><p>
@@ -237,13 +237,13 @@ here is incomplete  you are warned.
 		refer to the Microsoft Windows Resource Kit for your particular
 		version of MS Windows.
 		</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2659665"></a>
-<a class="indexterm" name="id2659672"></a>
-<a class="indexterm" name="id2659679"></a>
+<a class="indexterm" name="id2659792"></a>
+<a class="indexterm" name="id2659799"></a>
+<a class="indexterm" name="id2659806"></a>
 		The MS Windows 2000 Resource Kit contains a tool called <code class="literal">gpolmig.exe</code>. This tool can be used
 		to migrate an NT4 <code class="filename">NTConfig.POL</code> file into a Windows 200x style GPO. Be VERY careful how you
 		use this powerful tool. Please refer to the resource kit manuals for specific usage information.
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659705"></a>Custom System Policy Templates</h4></div></div></div><p>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659832"></a>Custom System Policy Templates</h4></div></div></div><p>
 		Over the past year, there has been a bit of talk regarding the creation of customized
 		templates for the Windows Sytem Policy Editor. A recent announcement on the Samba mailing
 		list is worthy of mention.
@@ -256,15 +256,15 @@ here is incomplete  you are warned.
 		</p><p>
 		For further information please see the <a class="ulink" href="http://www.pcc-services.com/custom_poledit.html" target="_top">Petersen</a> Computer Consulting web site. There is
 		a download link for the template file.
-		</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2659746"></a>Managing Account/User Policies</h2></div></div></div><p>
-<a class="indexterm" name="id2659754"></a>
-<a class="indexterm" name="id2659761"></a>
-<a class="indexterm" name="id2659768"></a>
+		</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2659873"></a>Managing Account/User Policies</h2></div></div></div><p>
+<a class="indexterm" name="id2659881"></a>
+<a class="indexterm" name="id2659888"></a>
+<a class="indexterm" name="id2659895"></a>
 Policies can define a specific user's settings or the settings for a group of users. The resulting
 policy file contains the registry settings for all users, groups, and computers that will be using
 the policy file. Separate policy files for each user, group, or computer are not necessary.
 </p><p>
-<a class="indexterm" name="id2659783"></a>
+<a class="indexterm" name="id2659910"></a>
 If you create a policy that will be automatically downloaded from validating domain controllers,
 you should name the file <code class="filename">NTConfig.POL</code>. As system administrator, you have the option of renaming the
 policy file and, by modifying the Windows NT-based workstation, directing the computer to update
@@ -272,46 +272,46 @@ the policy from a manual path. You can do this by either manually changing the r
 the System Policy Editor. This can even be a local path such that each machine has its own policy file,
 but if a change is necessary to all machines, it must be made individually to each workstation.
 </p><p>
-<a class="indexterm" name="id2659816"></a>
-<a class="indexterm" name="id2659823"></a>
+<a class="indexterm" name="id2659936"></a>
+<a class="indexterm" name="id2659943"></a>
 When a Windows NT4/200x/XP machine logs onto the network, the client looks in the NETLOGON share on
 the authenticating domain controller for the presence of the <code class="filename">NTConfig.POL</code> file. If one exists, it is 
 downloaded, parsed, and then applied to the user's part of the registry.
 </p><p>
-<a class="indexterm" name="id2659844"></a>
-<a class="indexterm" name="id2659851"></a>
-<a class="indexterm" name="id2659857"></a>
-<a class="indexterm" name="id2659864"></a>
+<a class="indexterm" name="id2659963"></a>
+<a class="indexterm" name="id2659970"></a>
+<a class="indexterm" name="id2659977"></a>
+<a class="indexterm" name="id2659984"></a>
 MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally
 acquire policy settings through GPOs that are defined and stored in Active Directory
 itself. The key benefit of using AD GPOs is that they impose no registry <span class="emphasis"><em>spoiling</em></span> effect.
 This has considerable advantage compared with the use of <code class="filename">NTConfig.POL</code> (NT4) style policy updates.
 </p><p>
-<a class="indexterm" name="id2659890"></a>
-<a class="indexterm" name="id2659897"></a>
+<a class="indexterm" name="id2660010"></a>
+<a class="indexterm" name="id2660017"></a>
 In addition to user access controls that may be imposed or applied via system and/or group policies
 in a manner that works in conjunction with user profiles, the user management environment under
 MS Windows NT4/200x/XP allows per-domain as well as per-user account restrictions to be applied.
 Common restrictions that are frequently used include:
 </p><p>
-<a class="indexterm" name="id2659913"></a>
+<a class="indexterm" name="id2660033"></a>
 </p><div class="itemizedlist"><ul type="disc"><li><p>Logon hours</p></li><li><p>Password aging</p></li><li><p>Permitted logon from certain machines only</p></li><li><p>Account type (local or global)</p></li><li><p>User rights</p></li></ul></div><p>
 </p><p>
-<a class="indexterm" name="id2659950"></a>
-<a class="indexterm" name="id2659957"></a>
+<a class="indexterm" name="id2660070"></a>
+<a class="indexterm" name="id2660077"></a>
 Samba-3.0.20 does not yet implement all account controls that are common to MS Windows NT4/200x/XP.
 While it is possible to set many controls using the Domain User Manager for MS Windows NT4, only password
 expiry is functional today. Most of the remaining controls at this time have only stub routines
 that may eventually be completed to provide actual control. Do not be misled by the fact that a
 parameter can be set using the NT4 Domain User Manager or in the <code class="filename">NTConfig.POL</code>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2659980"></a>Management Tools</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660100"></a>Management Tools</h2></div></div></div><p>
 Anyone who wishes to create or manage Group Policies will need to be familiar with a number of tools.
 The following sections describe a few key tools that will help you to create a low-maintenance user
 environment.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659993"></a>Samba Editreg Toolset</h3></div></div></div><p>
-	<a class="indexterm" name="id2660001"></a>
-	<a class="indexterm" name="id2660008"></a>
-	<a class="indexterm" name="id2660014"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660112"></a>Samba Editreg Toolset</h3></div></div></div><p>
+	<a class="indexterm" name="id2660120"></a>
+	<a class="indexterm" name="id2660127"></a>
+	<a class="indexterm" name="id2660134"></a>
 	A new tool called <code class="literal">editreg</code> is under development. This tool can be used
 	to edit registry files (called <code class="filename">NTUser.DAT</code>) that are stored in user
 	and group profiles. <code class="filename">NTConfig.POL</code> files have the same structure as the
@@ -320,33 +320,33 @@ environment.
 	permit the building of new <code class="filename">NTConfig.POL</code> files with extended capabilities. It is proving difficult
 	to realize this capability, so do not be surprised if this feature does not materialize. Formal
 	capabilities will be announced at the time that this tool is released for production use.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660075"></a>Windows NT4/200x</h3></div></div></div><p>
-<a class="indexterm" name="id2660083"></a>
-<a class="indexterm" name="id2660090"></a>
-<a class="indexterm" name="id2660097"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660194"></a>Windows NT4/200x</h3></div></div></div><p>
+<a class="indexterm" name="id2660202"></a>
+<a class="indexterm" name="id2660209"></a>
+<a class="indexterm" name="id2660216"></a>
 	The tools that may be used to configure these types of controls from the MS Windows environment are
 	the NT4 User Manager for Domains, the NT4 System and Group Policy Editor, and the Registry Editor (regedt32.exe).
 	Under MS Windows 200x/XP, this is done using the MMC with appropriate
 	&#8220;<span class="quote">snap-ins,</span>&#8221; the registry editor, and potentially also the NT4 System and Group Policy Editor.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660115"></a>Samba PDC</h3></div></div></div><p>
-<a class="indexterm" name="id2660123"></a>
-<a class="indexterm" name="id2660130"></a>
-<a class="indexterm" name="id2660137"></a>
-<a class="indexterm" name="id2660143"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660235"></a>Samba PDC</h3></div></div></div><p>
+<a class="indexterm" name="id2660242"></a>
+<a class="indexterm" name="id2660249"></a>
+<a class="indexterm" name="id2660256"></a>
+<a class="indexterm" name="id2660263"></a>
 	With a Samba domain controller, the new tools for managing user account and policy information include:
 	<code class="literal">smbpasswd</code>, <code class="literal">pdbedit</code>, <code class="literal">net</code>, and <code class="literal">rpcclient</code>. 
 	The administrator should read the man pages for these tools and become familiar with their use.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660180"></a>System Startup and Logon Processing Overview</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660299"></a>System Startup and Logon Processing Overview</h2></div></div></div><p>
 The following attempts to document the order of processing the system and user policies following a system
 reboot and as part of the user logon:
 </p><div class="orderedlist"><ol type="1"><li><p>
-<a class="indexterm" name="id2660202"></a>
-<a class="indexterm" name="id2660211"></a>
+<a class="indexterm" name="id2660321"></a>
+<a class="indexterm" name="id2660331"></a>
 	Network starts, then Remote Procedure Call System Service (RPCSS) and multiple universal naming
 	convention provider (MUP) start.
 	</p></li><li><p>
-<a class="indexterm" name="id2660228"></a>
-<a class="indexterm" name="id2660235"></a>
+<a class="indexterm" name="id2660348"></a>
+<a class="indexterm" name="id2660354"></a>
 	Where Active Directory is involved, an ordered list of GPOs is downloaded
 	and applied. The list may include GPOs that:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Apply to the location of machines in a directory.</p></li><li><p>Apply only when settings have changed.</p></li><li><p>Depend on configuration of the scope of applicability: local,
@@ -371,10 +371,10 @@ reboot and as part of the user logon:
 	</p></li><li><p>
 	The user interface as determined from the GPOs is presented. Note: In a Samba domain (like an NT4
 	domain), machine (system) policies are applied at startup; user policies are applied at logon.
-	</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660338"></a>Common Errors</h2></div></div></div><p>
+	</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660457"></a>Common Errors</h2></div></div></div><p>
 Policy-related problems can be quite difficult to diagnose and even more difficult to rectify. The following
 collection demonstrates only basic issues.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660349"></a>Policy Does Not Work</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660469"></a>Policy Does Not Work</h3></div></div></div><p>
 &#8220;<span class="quote">We have created the <code class="filename">Config.POL</code> file and put it in the <span class="emphasis"><em>NETLOGON</em></span> share.
 It has made no difference to our Win XP Pro machines, they just do not see it. It worked fine with Win 98 but does not
 work any longer since we upgraded to Win XP Pro. Any hints?</span>&#8221;
diff --git a/docs/htmldocs/Samba3-HOWTO/Portability.html b/docs/htmldocs/Samba3-HOWTO/Portability.html
index f57032ff89..6e6c94ea07 100644
--- a/docs/htmldocs/Samba3-HOWTO/Portability.html
+++ b/docs/htmldocs/Samba3-HOWTO/Portability.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�43.�Portability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="compiling.html" title="Chapter�42.�How to Compile Samba"><link rel="next" href="Other-Clients.html" title="Chapter�44.�Samba and Other CIFS Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�43.�Portability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="compiling.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="Other-Clients.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter�43.�Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Portability.html#id2688963">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689067">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689106">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689248">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689291">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689353">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689358">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2688946"></a>
-<a class="indexterm" name="id2688952"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�43.�Portability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="compiling.html" title="Chapter�42.�How to Compile Samba"><link rel="next" href="Other-Clients.html" title="Chapter�44.�Samba and Other CIFS Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�43.�Portability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="compiling.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="Other-Clients.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter�43.�Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Portability.html#id2689108">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689212">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689251">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689392">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689436">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689498">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689503">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2689090"></a>
+<a class="indexterm" name="id2689097"></a>
 Samba works on a wide range of platforms, but the interface all the 
 platforms provide is not always compatible. This chapter contains 
-platform-specific information about compiling and using Samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2688963"></a>HPUX</h2></div></div></div><p>
-<a class="indexterm" name="id2688971"></a>
-<a class="indexterm" name="id2688978"></a>
+platform-specific information about compiling and using Samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689108"></a>HPUX</h2></div></div></div><p>
+<a class="indexterm" name="id2689116"></a>
+<a class="indexterm" name="id2689123"></a>
 Hewlett-Packard's implementation of supplementary groups is nonstandard (for
 historical reasons). There are two group files, <code class="filename">/etc/group</code> and
 <code class="filename">/etc/logingroup</code>; the system maps UIDs to numbers using the former, but
@@ -23,11 +23,11 @@ allowed range.
 </p><p>
 This is documented in the HP manual pages under setgroups(2) and passwd(4).
 </p><p>
-<a class="indexterm" name="id2689049"></a>
-<a class="indexterm" name="id2689056"></a>
+<a class="indexterm" name="id2689194"></a>
+<a class="indexterm" name="id2689200"></a>
 On HP-UX you must use gcc or the HP ANSI compiler. The free compiler
 that comes with HP-UX is not ANSI compliant and cannot compile Samba.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689067"></a>SCO UNIX</h2></div></div></div><p> 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689212"></a>SCO UNIX</h2></div></div></div><p> 
 If you run an old version of SCO UNIX, you may need to get important 
 TCP/IP patches for Samba to work correctly. Without the patch, you may 
 encounter corrupt data transfers using Samba.
@@ -43,7 +43,7 @@ binary packages you will install. This is important if you wish to avoid data co
 problems with your installation. To build Samba for SCO UNIX products  may
 require significant patching of Samba source code. It is much easier to obtain binary
 packages directly from SCO.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689106"></a>DNIX</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689251"></a>DNIX</h2></div></div></div><p>
 DNIX has a problem with seteuid() and setegid(). These routines are
 needed for Samba to work correctly, but they were left out of the DNIX
 C library for some reason.
@@ -100,14 +100,14 @@ LIBSM = setegid.o seteuid.o -ln
 You should then remove the line:
 </p><pre class="programlisting">
 #define NO_EID
-</pre><p>from the DNIX section of <code class="filename">includes.h</code>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689248"></a>Red Hat Linux</h2></div></div></div><p>
+</pre><p>from the DNIX section of <code class="filename">includes.h</code>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689392"></a>Red Hat Linux</h2></div></div></div><p>
 By default during installation, some versions of Red Hat Linux add an
 entry to <code class="filename">/etc/hosts</code> as follows:
 </p><pre class="programlisting">
 127.0.0.1 loopback "hostname"."domainname"
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2689273"></a>
+<a class="indexterm" name="id2689418"></a>
 This causes Samba to loop back onto the loopback interface.
 The result is that Samba fails to communicate correctly with
 the world and therefore may fail to correctly negotiate who
@@ -115,7 +115,7 @@ is the master browse list holder and who is the master browser.
 </p><p>
 Corrective action: Delete the entry after the word "loopback"
 in the line starting 127.0.0.1.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689291"></a>AIX: Sequential Read Ahead</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689436"></a>AIX: Sequential Read Ahead</h2></div></div></div><p>
 Disabling sequential read ahead can improve Samba performance significantly
 when there is a relatively high level of multiprogramming (many smbd processes
 or mixed with another workload), not an abundance of physical memory or slower
@@ -134,7 +134,7 @@ For AIX 5.2 and later jfs2 filesystems: <strong class="userinput"><code>ioo -o j
 </p><p>
 If you have a mix of jfs and jfs2 filesystems on the same host, simply use both
 ioo commands.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689353"></a>Solaris</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689358"></a>Locking Improvements</h3></div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689498"></a>Solaris</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689503"></a>Locking Improvements</h3></div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl 
 when running Samba on Solaris. The built-in file-locking mechanism was
 not scalable. Performance would degrade to the point where processes would
 get into loops of trying to lock a file. It would try a lock, then fail,
diff --git a/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html b/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html
index ce64b2c04a..f759c6f6b9 100644
--- a/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html
+++ b/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html
@@ -1,42 +1,42 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�27.�Desktop Profile Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"><link rel="next" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�27.�Desktop Profile Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="pam.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�27.�Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660434">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660484">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660538">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661143">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662488">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662631">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663192">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664442">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664453">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664514">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664685">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664849">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660434"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2660442"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�27.�Desktop Profile Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"><link rel="next" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�27.�Desktop Profile Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="pam.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�27.�Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660554">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660603">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660657">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661267">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662612">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662744">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663314">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664569">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664580">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664641">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664813">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664976">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660554"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2660562"></a>
 Roaming profiles are feared by some, hated by a few, loved by many, and a godsend for
 some administrators.
 </p><p>
-<a class="indexterm" name="id2660454"></a>
+<a class="indexterm" name="id2660574"></a>
 Roaming profiles allow an administrator to make available a consistent user desktop
 as the user moves from one machine to another. This chapter provides much information
 regarding how to configure and manage roaming profiles.
 </p><p>
-<a class="indexterm" name="id2660468"></a>
+<a class="indexterm" name="id2660588"></a>
 While roaming profiles might sound like nirvana to some, they are a real and tangible
 problem to others. In particular, users of mobile computing tools, where often there may not
 be a sustained network connection, are often better served by purely local profiles.
 This chapter provides information to help the Samba administrator deal with those
 situations.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660484"></a>Roaming Profiles</h2></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660603"></a>Roaming Profiles</h2></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 Roaming profiles support is different for Windows 9x/Me and Windows NT4/200x.
 </p></div><p>
 Before discussing how to configure roaming profiles, it is useful to see how
 Windows 9x/Me and Windows NT4/200x clients implement these features.
 </p><p>
-<a class="indexterm" name="id2660505"></a>
+<a class="indexterm" name="id2660624"></a>
 Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's
 profiles location. However, the response does not have room for a separate
 profiles location field, only the user's home share. This means that Windows 9x/Me
 profiles are restricted to being stored in the user's home directory.
 </p><p>
-<a class="indexterm" name="id2660520"></a>
-<a class="indexterm" name="id2660527"></a>
+<a class="indexterm" name="id2660640"></a>
+<a class="indexterm" name="id2660647"></a>
 Windows NT4/200x  clients send a NetSAMLogon RPC request, which contains many fields
 including a separate field for the location of the user's profiles.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660538"></a>Samba Configuration for Profile Handling</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660657"></a>Samba Configuration for Profile Handling</h3></div></div></div><p>
 This section documents how to configure Samba for MS Windows client profile support.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660548"></a>NT4/200x User Profiles</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660668"></a>NT4/200x User Profiles</h4></div></div></div><p>
 For example, to support Windows NT4/200x clients, set the following in the [global] section of the <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660571"></a><em class="parameter"><code>logon path =  \\profileserver\profileshare\profilepath\%U\moreprofilepath</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660690"></a><em class="parameter"><code>logon path =  \\profileserver\profileshare\profilepath\%U\moreprofilepath</code></em></td></tr></table><p>
 This is typically implemented like:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660592"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660711"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr></table><p>
 where &#8220;<span class="quote">%L</span>&#8221; translates to the name of the Samba server and &#8220;<span class="quote">%U</span>&#8221; translates to the username.
 </p><p>
 The default for this option is <code class="filename">\\%N\%U\profile</code>, namely, <code class="filename">\\sambaserver\username\profile</code>. 
@@ -45,55 +45,55 @@ a Samba server for the profiles, you must make the share that is specified in th
 browseable. Please refer to the man page for <code class="filename">smb.conf</code> regarding the different
 semantics of &#8220;<span class="quote">%L</span>&#8221; and &#8220;<span class="quote">%N</span>&#8221;, as well as &#8220;<span class="quote">%U</span>&#8221; and &#8220;<span class="quote">%u</span>&#8221;.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2660663"></a>
-<a class="indexterm" name="id2660670"></a>
+<a class="indexterm" name="id2660782"></a>
+<a class="indexterm" name="id2660789"></a>
 MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended
 to not use the <em class="parameter"><code>homes</code></em> metaservice name as part of the profile share path.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660688"></a>Windows 9x/Me User Profiles</h4></div></div></div><p>
-<a class="indexterm" name="id2660696"></a>
-<a class="indexterm" name="id2660703"></a>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660807"></a>Windows 9x/Me User Profiles</h4></div></div></div><p>
+<a class="indexterm" name="id2660815"></a>
+<a class="indexterm" name="id2660822"></a>
 To support Windows 9x/Me clients, you must use the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>
 parameter. Samba has been fixed so <strong class="userinput"><code>net use /home</code></strong> now works as well and it, too, relies
 on the <em class="parameter"><code>logon home</code></em> parameter.
 </p><p>
-<a class="indexterm" name="id2660738"></a>
-<a class="indexterm" name="id2660745"></a>
-<a class="indexterm" name="id2660752"></a>
+<a class="indexterm" name="id2660858"></a>
+<a class="indexterm" name="id2660864"></a>
+<a class="indexterm" name="id2660871"></a>
 By using the <em class="parameter"><code>logon home</code></em> parameter, you are restricted to putting Windows 9x/Me profiles
 in the user's home directory.  But wait! There is a trick you can use. If you set the following in the
 <em class="parameter"><code>[global]</code></em> section of your <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660785"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660905"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr></table><p>
 then your Windows 9x/Me clients will dutifully put their clients in a subdirectory
 of your home directory called <code class="filename">.profiles</code> (making them hidden).
 </p><p>
-<a class="indexterm" name="id2660809"></a>
+<a class="indexterm" name="id2660928"></a>
 Not only that, but <strong class="userinput"><code>net use /home</code></strong> will also work because of a feature in
 Windows 9x/Me. It removes any directory stuff off the end of the home directory area
 and only uses the server and share portion. That is, it looks like you
 specified <code class="filename">\\%L\%U</code> for <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660846"></a>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660965"></a>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</h4></div></div></div><p>
 You can support profiles for Windows 9x and Windows NT clients by setting both the
 <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> and <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> parameters. For example,
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2660885"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2660897"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr></table><p>
-<a class="indexterm" name="id2660911"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2661005"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2661016"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr></table><p>
+<a class="indexterm" name="id2661030"></a>
 Windows 9x/Me and NT4 and later profiles should not be stored in the same location because
 Windows NT4 and later will experience problems with mixed profile environments.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660923"></a>Disabling Roaming Profile Support</h4></div></div></div><p>
-<a class="indexterm" name="id2660931"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2661043"></a>Disabling Roaming Profile Support</h4></div></div></div><p>
+<a class="indexterm" name="id2661051"></a>
 The question often asked is, &#8220;<span class="quote">How may I enforce use of local profiles?</span>&#8221; or
 &#8220;<span class="quote">How do I disable roaming profiles?</span>&#8221;
 </p><p>
-<a class="indexterm" name="id2660950"></a>
+<a class="indexterm" name="id2661069"></a>
 There are three ways of doing this:
-</p><a class="indexterm" name="id2660958"></a><div class="variablelist"><dl><dt><span class="term">In <code class="filename">smb.conf</code></span></dt><dd><p>
+</p><a class="indexterm" name="id2661078"></a><div class="variablelist"><dl><dt><span class="term">In <code class="filename">smb.conf</code></span></dt><dd><p>
 		Affect the following settings and ALL clients will be forced to use a local profile:
 		<a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home =  </a> and <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path =  </a>
 		</p><p>
 		The arguments to these parameters must be left blank. It is necessary to include the <code class="constant">=</code> sign
 		to specifically assign the empty value.
 		</p></dd><dt><span class="term">MS Windows Registry:</span></dt><dd><p>
-<a class="indexterm" name="id2661028"></a>
-<a class="indexterm" name="id2661035"></a>
+<a class="indexterm" name="id2661148"></a>
+<a class="indexterm" name="id2661154"></a>
 		Use the Microsoft Management Console (MMC) <code class="literal">gpedit.msc</code> to instruct your MS Windows XP
 		machine to use only a local profile. This, of course, modifies registry settings. The full
 		path to the option is:
@@ -116,11 +116,11 @@ Disable: Prevent Roaming Profile Change from Propagating to the Server
 Consult the MS Windows registry guide for your particular MS Windows version for more information
 about which registry keys to change to enforce use of only local user profiles.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2661128"></a>
+<a class="indexterm" name="id2661248"></a>
 The specifics of how to convert a local profile to a roaming profile, or a roaming profile
 to a local one, vary according to the version of MS Windows you are running. Consult the Microsoft MS
 Windows Resource Kit for your version of Windows for specific information.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2661143"></a>Windows Client Profile Configuration Information</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2661150"></a>Windows 9x/Me Profile Setup</h4></div></div></div><p>
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2661267"></a>Windows Client Profile Configuration Information</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2661273"></a>Windows 9x/Me Profile Setup</h4></div></div></div><p>
 When a user first logs in on Windows 9x, the file user.DAT is created, as are folders <code class="filename">Start
 Menu</code>, <code class="filename">Desktop</code>, <code class="filename">Programs</code>, and
 <code class="filename">Nethood</code>. These directories and their contents will be merged with the local versions
@@ -128,8 +128,8 @@ stored in <code class="filename">c:\windows\profiles\username</code> on subseque
 each.	You will need to use the <em class="parameter"><code>[global]</code></em> options <a class="link" href="smb.conf.5.html#PRESERVECASE" target="_top">preserve case = yes</a>, <a class="link" href="smb.conf.5.html#SHORTPRESERVECASE" target="_top">short preserve case = yes</a>, and <a class="link" href="smb.conf.5.html#CASESENSITIVE" target="_top">case sensitive = no</a> in order to maintain capital letters in shortcuts in any of the
 profile folders.
 </p><p>
-<a class="indexterm" name="id2661239"></a>
-<a class="indexterm" name="id2661245"></a>
+<a class="indexterm" name="id2661363"></a>
+<a class="indexterm" name="id2661369"></a>
 The <code class="filename">user.DAT</code> file contains all the user's preferences. If you wish to enforce a set of preferences,
 rename their <code class="filename">user.DAT</code> file to <code class="filename">user.MAN</code>, and deny them write access to this file.
 </p><div class="orderedlist"><ol type="1"><li><p>
@@ -144,16 +144,16 @@ rename their <code class="filename">user.DAT</code> file to <code class="filenam
 	ensure that the Primary Logon is <span class="guilabel">Client for Microsoft Networks</span>. Press
 	<span class="guibutton">OK</span>, and this time allow the computer to reboot.
 	</p></li></ol></div><p>
-<a class="indexterm" name="id2661367"></a>
-<a class="indexterm" name="id2661374"></a>
-<a class="indexterm" name="id2661381"></a>
-<a class="indexterm" name="id2661388"></a>
+<a class="indexterm" name="id2661491"></a>
+<a class="indexterm" name="id2661498"></a>
+<a class="indexterm" name="id2661505"></a>
+<a class="indexterm" name="id2661511"></a>
 Under Windows 9x/Me, profiles are downloaded from the Primary Logon. If you have the Primary Logon
 as &#8220;<span class="quote">Client for Novell Networks</span>&#8221;, then the profiles and logon script will be downloaded from
 your Novell server. If you have the Primary Logon as &#8220;<span class="quote">Windows Logon</span>&#8221;, then the profiles will
 be loaded from the local machine  a bit against the concept of roaming profiles, it would seem! 
 </p><p>
-<a class="indexterm" name="id2661414"></a>
+<a class="indexterm" name="id2661538"></a>
 You will now find that the Microsoft Networks Login box contains <code class="constant">[user, password, domain]</code> instead
 of just <code class="constant">[user, password]</code>. Type in the Samba server's domain name (or any other domain known to exist,
 but bear in mind that the user will be authenticated against this domain and profiles downloaded from it
@@ -168,28 +168,28 @@ contents of the directory specified in the <a class="link" href="smb.conf.5.html
 the Samba server and verify that the <code class="filename">Desktop</code>, <code class="filename">Start Menu</code>,
 <code class="filename">Programs</code>, and <code class="filename">Nethood</code> folders have been created.
 </p><p>
-<a class="indexterm" name="id2661501"></a>
-<a class="indexterm" name="id2661508"></a>
-<a class="indexterm" name="id2661515"></a>
+<a class="indexterm" name="id2661625"></a>
+<a class="indexterm" name="id2661632"></a>
+<a class="indexterm" name="id2661639"></a>
 These folders will be cached locally on the client and updated when the user logs off (if
 you haven't made them read-only by then). You will find that if the user creates further folders or
 shortcuts, the client will merge the profile contents downloaded with the contents of the profile
 directory already on the local client, taking the newest folders and shortcut from each set.
 </p><p>
-<a class="indexterm" name="id2661532"></a>
-<a class="indexterm" name="id2661538"></a>
-<a class="indexterm" name="id2661545"></a>
-<a class="indexterm" name="id2661552"></a>
+<a class="indexterm" name="id2661655"></a>
+<a class="indexterm" name="id2661662"></a>
+<a class="indexterm" name="id2661669"></a>
+<a class="indexterm" name="id2661676"></a>
 If you have made the folders/files read-only on the Samba server, then you will get errors from
 the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile.
 Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions
 and ownership rights on the profile directory contents, on the Samba server.
 </p><p>
-<a class="indexterm" name="id2661569"></a>
-<a class="indexterm" name="id2661576"></a>
-<a class="indexterm" name="id2661583"></a>
-<a class="indexterm" name="id2661590"></a>
-<a class="indexterm" name="id2661597"></a>
+<a class="indexterm" name="id2661693"></a>
+<a class="indexterm" name="id2661700"></a>
+<a class="indexterm" name="id2661707"></a>
+<a class="indexterm" name="id2661714"></a>
+<a class="indexterm" name="id2661721"></a>
 If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below.
 When this user next logs in, the user will be told that he/she is logging in &#8220;<span class="quote">for the first
 time</span>&#8221;.
@@ -214,7 +214,7 @@ time</span>&#8221;.
 	described above) and delete the <code class="filename">user.DAT</code> or <code class="filename">user.MAN</code>
 	file for the user, making a backup if required. 
 	</p></li></ol></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2661728"></a>
+<a class="indexterm" name="id2661852"></a>
 Before deleting the contents of the directory listed in the <em class="parameter"><code>ProfilePath</code></em>
 (this is likely to be <code class="filename">c:\windows\profiles\username)</code>, ask whether the owner has
 any important files stored on his or her desktop or start menu. Delete the contents of the
@@ -224,19 +224,19 @@ This will have the effect of removing the local (read-only hidden system file) <
 in their profile directory, as well as the local &#8220;<span class="quote">desktop,</span>&#8221; &#8220;<span class="quote">nethood,</span>&#8221;
 &#8220;<span class="quote">start menu,</span>&#8221; and &#8220;<span class="quote">programs</span>&#8221; folders.
 </p></div><p>
-<a class="indexterm" name="id2661786"></a>
-<a class="indexterm" name="id2661793"></a>
-<a class="indexterm" name="id2661800"></a>
-<a class="indexterm" name="id2661807"></a>
+<a class="indexterm" name="id2661910"></a>
+<a class="indexterm" name="id2661917"></a>
+<a class="indexterm" name="id2661924"></a>
+<a class="indexterm" name="id2661931"></a>
 If all else fails, increase Samba's debug log levels to between 3 and 10, and/or run a packet
 sniffer program such as ethereal or <code class="literal">netmon.exe</code>, and look for error messages.
 </p><p>
-<a class="indexterm" name="id2661825"></a>
-<a class="indexterm" name="id2661832"></a>
+<a class="indexterm" name="id2661949"></a>
+<a class="indexterm" name="id2661956"></a>
 If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or
 netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces
 provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2661846"></a>Windows NT4 Workstation</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2661970"></a>Windows NT4 Workstation</h4></div></div></div><p>
 When a user first logs in to a Windows NT workstation, the profile NTuser.DAT is created. The profile
 location can be now specified through the <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> parameter.
 </p><p>
@@ -244,22 +244,22 @@ There is a parameter that is now available for use with NT Profiles: <a class="l
 This should be set to <code class="filename">H:</code> or any other drive, and should be used in conjunction with
 the new <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> parameter.
 </p><p>
-<a class="indexterm" name="id2661907"></a>
-<a class="indexterm" name="id2661913"></a>
+<a class="indexterm" name="id2662030"></a>
+<a class="indexterm" name="id2662037"></a>
 The entry for the NT4 profile is a directory, not a file. The NT help on profiles mentions that a
 directory is also created with a .PDS extension. The user, while logging in, must have write permission
 to create the full profile path (and the folder with the .PDS extension for those situations where it
 might be created). 
 </p><p>
-<a class="indexterm" name="id2661929"></a>
+<a class="indexterm" name="id2662053"></a>
 In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates
 <code class="filename">Application Data</code> and others, as well as <code class="filename">Desktop</code>,
 <code class="filename">Nethood</code>, <code class="filename">Start Menu,</code> and <code class="filename">Programs</code>.
 The profile itself is stored in a file <code class="filename">NTuser.DAT</code>. Nothing appears to be stored
 in the .PDS directory, and its purpose is currently unknown.
 </p><p>
-<a class="indexterm" name="id2661978"></a>
-<a class="indexterm" name="id2661984"></a>
+<a class="indexterm" name="id2662102"></a>
+<a class="indexterm" name="id2662108"></a>
 You can use the <span class="application">System Control Panel</span> to copy a local profile onto
 a Samba server (see NT help on profiles; it is also capable of firing up the correct location in the
 <span class="application">System Control Panel</span> for you). The NT help file also mentions that renaming
@@ -267,7 +267,7 @@ a Samba server (see NT help on profiles; it is also capable of firing up the cor
 </p><p>
 The case of the profile is significant.	The file must be called <code class="filename">NTuser.DAT</code>
 or, for a mandatory profile, <code class="filename">NTuser.MAN</code>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662038"></a>Windows 2000/XP Professional</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662162"></a>Windows 2000/XP Professional</h4></div></div></div><p>
 You must first convert the profile from a local profile to a domain profile on the MS Windows
 workstation as follows: </p><div class="procedure"><ol type="1"><li><p> Log on as the <span class="emphasis"><em>local</em></span> workstation administrator. </p></li><li><p> Right-click on the <span class="guiicon">My Computer</span> icon, and select
 	<span class="guimenuitem">Properties</span>.</p></li><li><p> Click on the <span class="guilabel">User Profiles</span> tab.</p></li><li><p> Select the profile you wish to convert (click it once).</p></li><li><p> Click on the <span class="guibutton">Copy To</span> button.</p></li><li><p> In the <span class="guilabel">Permitted to use</span> box, click on the
@@ -280,7 +280,7 @@ Done. You now have a profile that can be edited using the Samba <code class="lit
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Under Windows NT/200x, the use of mandatory profiles forces the use of MS Exchange storage of mail
 data and keeps it out of the desktop profile. That keeps desktop profiles from becoming unusable.
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2662220"></a>Windows XP Service Pack 1</h5></div></div></div><p>
+</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2662344"></a>Windows XP Service Pack 1</h5></div></div></div><p>
 	There is a security check new to Windows XP (or maybe only Windows XP service pack 1).
 	It can be disabled via a group policy in the Active Directory. The policy is called:
 </p><pre class="screen">
@@ -296,18 +296,18 @@ Computer Configuration\Administrative Templates\System\User Profiles\
 	</p><div class="procedure"><ol type="1"><li><p>On the XP workstation, log in with an administrative account.</p></li><li><p>Click on <span class="guimenu">Start</span> -&gt; <span class="guimenuitem">Run</span>.</p></li><li><p>Type <code class="literal">mmc</code>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click on <span class="guimenu">File</span> -&gt; <span class="guimenuitem">Add/Remove Snap-in</span> -&gt; <span class="guimenuitem">Add</span>.</p></li><li><p>Double-click on <span class="guiicon">Group Policy</span>.</p></li><li><p>Click on <span class="guibutton">Finish</span> -&gt; <span class="guibutton">Close</span>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>In the &#8220;<span class="quote">Console Root</span>&#8221; window expand <span class="guiicon">Local Computer Policy</span> -&gt;
 		<span class="guiicon">Computer Configuration</span> -&gt; <span class="guiicon">Administrative Templates</span> -&gt; 
 		<span class="guiicon">System</span> -&gt; <span class="guiicon">User Profiles</span>.</p></li><li><p>Double-click on <span class="guilabel">Do not check for user ownership of Roaming Profile Folders</span>.</p></li><li><p>Select <span class="guilabel">Enabled</span>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>Close the whole console. You do not need to save the settings (this refers to the
-	console settings rather than the policies you have changed).</p></li><li><p>Reboot.</p></li></ol></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662488"></a>User Profile Hive Cleanup Service</h3></div></div></div><p>
+	console settings rather than the policies you have changed).</p></li><li><p>Reboot.</p></li></ol></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662612"></a>User Profile Hive Cleanup Service</h3></div></div></div><p>
 There are certain situations that cause a cached local copy of roaming profile not to be deleted on exit, even if
 the policy to force such deletion is set. To deal with that situation, a special service was created. The application 
 <code class="literal">UPHClean</code> (User Profile Hive Cleanup) can be installed as a service on Windows NT4/2000/XP Professional
 and Windows 2003.
 </p><p>
 The UPHClean software package can be downloaded from the User Profile Hive Cleanup
-Service<sup>[<a name="id2662512" href="#ftn.id2662512" class="footnote">7</a>]</sup>
+Service<sup>[<a name="id2662636" href="#ftn.id2662636" class="footnote">7</a>]</sup>
 web site.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662522"></a>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</h3></div></div></div><p>
-<a class="indexterm" name="id2662531"></a>
-<a class="indexterm" name="id2662538"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662645"></a>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</h3></div></div></div><p>
+<a class="indexterm" name="id2662654"></a>
+<a class="indexterm" name="id2662661"></a>
 Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an
 evolving phenomenon, and profiles for later versions of MS Windows clients add features that may interfere
 with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is
@@ -319,20 +319,20 @@ If you then want to share the same Start Menu and Desktop with Windows 9x/Me, yo
 location for the profiles. The <code class="filename">smb.conf</code> parameters that need to be common are 
 <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> and <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>.
 </p><p>
-<a class="indexterm" name="id2662602"></a>
-<a class="indexterm" name="id2662609"></a>
+<a class="indexterm" name="id2662716"></a>
+<a class="indexterm" name="id2662722"></a>
 If you have this set up correctly, you will find separate <code class="filename">user.DAT</code> and
 <code class="filename">NTuser.DAT</code> files in the same profile directory.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662631"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div></div><p>
-<a class="indexterm" name="id2662639"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2662744"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div></div><p>
+<a class="indexterm" name="id2662752"></a>
 There is nothing to stop you from specifying any path that you like for the location of users' profiles.
 Therefore, you could specify that the profile be stored on a Samba server or any other SMB server,
 as long as that SMB server supports encrypted passwords.
 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="profilemigrn"></a>Windows NT4 Profile Management Tools</h4></div></div></div><p>
-<a class="indexterm" name="id2662664"></a>
+<a class="indexterm" name="id2662777"></a>
 Unfortunately, the resource kit information is specific to the version of MS Windows NT4/200x. The
 correct resource kit is required for each platform.
-</p><p>Here is a quick guide:</p><div class="procedure"><a name="id2662678"></a><p class="title"><b>Procedure�27.1.�Profile Migration Procedure</b></p><ol type="1"><li><p> On your NT4 domain controller, right-click on <span class="guiicon">My Computer</span>, then select 
+</p><p>Here is a quick guide:</p><div class="procedure"><a name="id2662791"></a><p class="title"><b>Procedure�27.1.�Profile Migration Procedure</b></p><ol type="1"><li><p> On your NT4 domain controller, right-click on <span class="guiicon">My Computer</span>, then select 
 	<span class="guilabel">Properties</span>, then the tab labeled <span class="guilabel">User Profiles</span>. </p></li><li><p> Select a user profile you want to migrate and click on it. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term &#8220;<span class="quote">migrate</span>&#8221; loosely. You can copy a profile to create a group
 	profile. You can give the user <em class="parameter"><code>Everyone</code></em> rights to the profile you copy this to. That
 	is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4
@@ -340,21 +340,21 @@ correct resource kit is required for each platform.
 	<code class="filename">c:\temp\foobar</code></p></li><li><p>Click on <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li><p>Click on the group &#8220;<span class="quote">Everyone</span>&#8221;, click on <span class="guibutton">OK</span>. This
 	closes the &#8220;<span class="quote">choose user</span>&#8221; box.</p></li><li><p>Now click on <span class="guibutton">OK</span>.</p></li></ol></div><p>
 Follow these steps for every profile you need to migrate.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662825"></a>Side Bar Notes</h4></div></div></div><p>
-<a class="indexterm" name="id2662833"></a>
-<a class="indexterm" name="id2662839"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662938"></a>Side Bar Notes</h4></div></div></div><p>
+<a class="indexterm" name="id2662946"></a>
+<a class="indexterm" name="id2662952"></a>
 You should obtain the SID of your NT4 domain. You can use the <code class="literal">net rpc info</code> to do this.
 See <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">The Net Command Chapter</a>, <a class="link" href="NetCommand.html#netmisc1" title="Other Miscellaneous Operations">Other Miscellaneous Operations</a> for more information.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662876"></a>moveuser.exe</h4></div></div></div><p>
-<a class="indexterm" name="id2662884"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662989"></a>moveuser.exe</h4></div></div></div><p>
+<a class="indexterm" name="id2662997"></a>
 The Windows 200x professional resource kit has <code class="literal">moveuser.exe</code>.
 <code class="literal">moveuser.exe</code> changes the security of a profile from one user to another. This allows the
 account domain to change and/or the username to change.
 </p><p>
 This command is like the Samba <code class="literal">profiles</code> tool.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2662917"></a>Get SID</h4></div></div></div><p>
-<a class="indexterm" name="id2662925"></a>
-<a class="indexterm" name="id2662932"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2663030"></a>Get SID</h4></div></div></div><p>
+<a class="indexterm" name="id2663038"></a>
+<a class="indexterm" name="id2663045"></a>
 You can identify the SID by using <code class="literal">GetSID.exe</code> from the Windows NT Server 4.0 Resource Kit.
 </p><p>
 Windows NT 4.0 stores the local profile information in the registry under the following key:
@@ -364,60 +364,60 @@ Under the ProfileList key, there will be subkeys named with the SIDs of the user
 on to this computer. (To find the profile information for the user whose locally cached profile you want
 to move, find the SID for the user with the <code class="literal">GetSID.exe</code> utility.) Inside the appropriate user's subkey,
 you will see a string value named <em class="parameter"><code>ProfileImagePath</code></em>.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2662982"></a>Mandatory Profiles</h2></div></div></div><p>
-<a class="indexterm" name="id2662990"></a>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663095"></a>Mandatory Profiles</h2></div></div></div><p>
+<a class="indexterm" name="id2663103"></a>
 A mandatory profile is a profile that the user does not have the ability to overwrite. During the
 user's session, it may be possible to change the desktop environment; however, as the user logs out, all changes
 made will be lost. If it is desired to not allow the user any ability to change the desktop environment,
 then this must be done through policy settings. See <a class="link" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies">System and Account
 Policies</a>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 
-<a class="indexterm" name="id2663015"></a>
-<a class="indexterm" name="id2663022"></a>
-<a class="indexterm" name="id2663028"></a>
+<a class="indexterm" name="id2663128"></a>
+<a class="indexterm" name="id2663135"></a>
+<a class="indexterm" name="id2663142"></a>
 Under NO circumstances should the profile directory (or its contents) be made read-only because this may
 render the profile unusable.  Where it is essential to make a profile read-only within the UNIX file system,
 this can be done, but then you absolutely must use the <code class="literal">fake-permissions</code> VFS module to
 instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user.  See <a class="link" href="VFS.html#fakeperms" title="fake_perms">fake_perms VFS module</a>.
 </p></div><p>
-<a class="indexterm" name="id2663059"></a>
-<a class="indexterm" name="id2663066"></a>
+<a class="indexterm" name="id2663172"></a>
+<a class="indexterm" name="id2663179"></a>
 For MS Windows NT4/200x/XP, the procedure shown in <a class="link" href="ProfileMgmt.html#profilemigrn" title="Windows NT4 Profile Management Tools">Profile Migration from Windows
 NT4/200x Server to Samba</a> can also be used to create mandatory profiles. To convert a group profile into
 a mandatory profile, simply locate the <code class="filename">NTUser.DAT</code> file in the copied profile and rename
 it to <code class="filename">NTUser.MAN</code>.
 </p><p>
-<a class="indexterm" name="id2663100"></a>
+<a class="indexterm" name="id2663213"></a>
 For MS Windows 9x/Me, it is the <code class="filename">User.DAT</code> file that must be renamed to
 <code class="filename">User.MAN</code> to effect a mandatory profile.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663122"></a>Creating and Managing Group Profiles</h2></div></div></div><p>
-<a class="indexterm" name="id2663131"></a>
-<a class="indexterm" name="id2663137"></a>
-<a class="indexterm" name="id2663144"></a>
-<a class="indexterm" name="id2663151"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663236"></a>Creating and Managing Group Profiles</h2></div></div></div><p>
+<a class="indexterm" name="id2663244"></a>
+<a class="indexterm" name="id2663250"></a>
+<a class="indexterm" name="id2663257"></a>
+<a class="indexterm" name="id2663264"></a>
 Most organizations are arranged into departments. There is a nice benefit in this fact, since usually
 most users in a department require the same desktop applications and the same desktop layout. MS
 Windows NT4/200x/XP will allow the use of group profiles. A group profile is a profile that is created
 first using a template (example) user. Then using the profile migration tool (see above), the profile is
 assigned access rights for the user group that needs to be given access to the group profile.
 </p><p>
-<a class="indexterm" name="id2663170"></a>
+<a class="indexterm" name="id2663291"></a>
 The next step is rather important. Instead of assigning a group profile to users (Using User Manager)
 on a &#8220;<span class="quote">per-user</span>&#8221; basis, the group itself is assigned the now modified profile.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Be careful with group profiles. If the user who is a member of a group also has a personal
 profile, then the result will be a fusion (merge) of the two.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663192"></a>Default Profile for Windows Users</h2></div></div></div><p>
-<a class="indexterm" name="id2663201"></a>
-<a class="indexterm" name="id2663208"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2663314"></a>Default Profile for Windows Users</h2></div></div></div><p>
+<a class="indexterm" name="id2663322"></a>
+<a class="indexterm" name="id2663329"></a>
 MS Windows 9x/Me and NT4/200x/XP will use a default profile for any user for whom a profile
 does not already exist. Armed with a knowledge of where the default profile is located on the Windows
 workstation, and knowing which registry keys affect the path from which the default profile is created,
 it is possible to modify the default profile to one that has been optimized for the site. This has
 significant administrative advantages.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2663223"></a>MS Windows 9x/Me</h3></div></div></div><p>
-<a class="indexterm" name="id2663231"></a>
-<a class="indexterm" name="id2663238"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2663345"></a>MS Windows 9x/Me</h3></div></div></div><p>
+<a class="indexterm" name="id2663352"></a>
+<a class="indexterm" name="id2663360"></a>
 To enable default per-use profiles in Windows 9x/Me, you can either use the <span class="application">Windows
 98 System Policy Editor</span> or change the registry directly.
 </p><p>
@@ -427,12 +427,12 @@ Next click on the <span class="guiicon">Local Computer</span> icon, click on <sp
 select <span class="guilabel">User Profiles</span>, and click on the enable box. Remember to save the registry
 changes.
 </p><p>
-<a class="indexterm" name="id2663299"></a>
+<a class="indexterm" name="id2663421"></a>
 To modify the registry directly, launch the <span class="application">Registry Editor</span>
 (<code class="literal">regedit.exe</code>) and select the hive <code class="filename">HKEY_LOCAL_MACHINE\Network\Logon</code>.
 Now add a DWORD type key with the name &#8220;<span class="quote">User Profiles.</span>&#8221; To enable user profiles to set the value
 to 1; to disable user profiles set it to 0.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2663332"></a>User Profile Handling with Windows 9x/Me</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2663454"></a>User Profile Handling with Windows 9x/Me</h4></div></div></div><p>
 When a user logs on to a Windows 9x/Me machine, the local profile path,
 <code class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</code>, is checked
 for an existing entry for that user.
@@ -448,7 +448,7 @@ If a user profile is not found in either location, the default user profile from
 9x/Me machine is used and copied to a newly created folder for the logged on user. At log off, any
 changes that the user made are written to the user's local profile. If the user has a roaming profile,
 the changes are written to the user's profile on the server.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2663374"></a>MS Windows NT4 Workstation</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2663502"></a>MS Windows NT4 Workstation</h3></div></div></div><p>
 On MS Windows NT4, the default user profile is obtained from the location
 <code class="filename">%SystemRoot%\Profiles</code>, which in a default installation will translate to
 <code class="filename">C:\Windows NT\Profiles</code>. Under this directory on a clean install, there will be three
@@ -462,7 +462,7 @@ per user depending on the profile settings chosen/created.
 </p><p>
 When a new user first logs onto an MS Windows NT4 machine, a new profile is created from:
 </p><div class="itemizedlist"><ul type="disc"><li><p>All Users settings.</p></li><li><p>Default User settings (contains the default <code class="filename">NTUser.DAT</code> file).</p></li></ul></div><p>
-<a class="indexterm" name="id2663462"></a>
+<a class="indexterm" name="id2663589"></a>
 When a user logs on to an MS Windows NT4 machine that is a member of a Microsoft security domain,
 the following steps are followed for profile handling: 
 </p><div class="procedure"><ol type="1"><li><p> The user's account information that is obtained during the logon process
@@ -474,11 +474,11 @@ the following steps are followed for profile handling:
 	location. </p></li><li><p> If the user account has a profile path, but at its location a profile does not
 	exist, then a new profile is created in the <code class="filename">%SystemRoot%\Profiles\%USERNAME%</code>
 	directory from reading the <code class="filename">Default User</code> profile. </p></li><li><p>
-<a class="indexterm" name="id2663539"></a>
-<a class="indexterm" name="id2663546"></a>
-<a class="indexterm" name="id2663553"></a>
-<a class="indexterm" name="id2663560"></a>
-<a class="indexterm" name="id2663567"></a>
+<a class="indexterm" name="id2663666"></a>
+<a class="indexterm" name="id2663673"></a>
+<a class="indexterm" name="id2663680"></a>
+<a class="indexterm" name="id2663687"></a>
+<a class="indexterm" name="id2663694"></a>
 	If the NETLOGON share on the authenticating server (logon server) contains
 	a policy file (<code class="filename">NTConfig.POL</code>), then its contents are applied to the
 	<code class="filename">NTUser.DAT</code>, which is applied to the <code class="filename">HKEY_CURRENT_USER</code>
@@ -500,7 +500,7 @@ winlogon\"DeleteRoamingCache"=dword:0000000
 In this case, the local copy (in <code class="filename">%SystemRoot%\Profiles\%USERNAME%</code>) will be deleted
 on logout.
 </p><p>
-<a class="indexterm" name="id2663674"></a>
+<a class="indexterm" name="id2663802"></a>
 Under MS Windows NT4, default locations for common resources like <code class="filename">My Documents</code>
 may be redirected to a network share by modifying the following registry keys. These changes may be
 made via use of the System Policy Editor. To do so may require that you create your own template
@@ -519,7 +519,7 @@ HKEY_CURRENT_USER
 					\Explorer
 						\User Shell Folders
 </pre><p>
-<a class="indexterm" name="id2663714"></a>
+<a class="indexterm" name="id2663842"></a>
 </p><p>  The above hive key contains a list of automatically managed
 folders. The default entries are shown in <a class="link" href="ProfileMgmt.html#ProfileLocs" title="Table�27.1.�User Shell Folder Registry Keys Default Values">the next table</a>.
 </p><div class="table"><a name="ProfileLocs"></a><p class="title"><b>Table�27.1.�User Shell Folder Registry Keys Default Values</b></p><div class="table-contents"><table summary="User Shell Folder Registry Keys Default Values" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="left">Default Value</th></tr></thead><tbody><tr><td align="left">AppData</td><td align="left">%USERPROFILE%\Application Data</td></tr><tr><td align="left">Desktop</td><td align="left">%USERPROFILE%\Desktop</td></tr><tr><td align="left">Favorites</td><td align="left">%USERPROFILE%\Favorites</td></tr><tr><td align="left">NetHood</td><td align="left">%USERPROFILE%\NetHood</td></tr><tr><td align="left">PrintHood</td><td align="left">%USERPROFILE%\PrintHood</td></tr><tr><td align="left">Programs</td><td align="left">%USERPROFILE%\Start Menu\Programs</td></tr><tr><td align="left">Recent</td><td align="left">%USERPROFILE%\Recent</td></tr><tr><td align="left">SendTo</td><td align="left">%USERPROFILE%\SendTo</td></tr><tr><td align="left">Start Menu </td><td align="left">%USERPROFILE%\Start Menu</td></tr><tr><td align="left">Startup</td><td align="left">%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div></div><br class="table-break"><p> The registry key that contains the location of the default profile settings is:
@@ -529,24 +529,24 @@ User Shell Folders
 </pre><p>
 </p><p>
 The default entries are shown in <a class="link" href="ProfileMgmt.html#regkeys" title="Table�27.2.�Defaults of Profile Settings Registry Keys">Defaults of Profile Settings Registry Keys</a>.
-</p><div class="table"><a name="regkeys"></a><p class="title"><b>Table�27.2.�Defaults of Profile Settings Registry Keys</b></p><div class="table-contents"><table summary="Defaults of Profile Settings Registry Keys" border="1"><colgroup><col align="left"><col align="left"></colgroup><tbody><tr><td align="left">Common Desktop</td><td align="left">%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td align="left">Common Programs</td><td align="left">%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td align="left">Common Start Menu</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td align="left">Common Startup</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2663936"></a>MS Windows 200x/XP</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2663945"></a>
-<a class="indexterm" name="id2663952"></a>
-<a class="indexterm" name="id2663959"></a>
-<a class="indexterm" name="id2663966"></a>
+</p><div class="table"><a name="regkeys"></a><p class="title"><b>Table�27.2.�Defaults of Profile Settings Registry Keys</b></p><div class="table-contents"><table summary="Defaults of Profile Settings Registry Keys" border="1"><colgroup><col align="left"><col align="left"></colgroup><tbody><tr><td align="left">Common Desktop</td><td align="left">%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td align="left">Common Programs</td><td align="left">%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td align="left">Common Start Menu</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td align="left">Common Startup</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664064"></a>MS Windows 200x/XP</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+<a class="indexterm" name="id2664073"></a>
+<a class="indexterm" name="id2664080"></a>
+<a class="indexterm" name="id2664087"></a>
+<a class="indexterm" name="id2664093"></a>
 MS Windows XP Home Edition does use default per-user profiles, but cannot participate
 in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only
 from itself. While there are benefits in doing this, the beauty of those MS Windows clients that
 can participate in domain logon processes is that they allow the administrator to create a global default
 profile and enforce it through the use of Group Policy Objects (GPOs).
 </p></div><p>
-<a class="indexterm" name="id2663984"></a>
+<a class="indexterm" name="id2664111"></a>
 When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from
 <code class="filename">C:\Documents and Settings\Default User</code>. The administrator can modify or change the
 contents of this location, and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement,
 since it will involve copying a new default profile to every MS Windows 200x/XP client workstation.
 </p><p>
-<a class="indexterm" name="id2664006"></a>
+<a class="indexterm" name="id2664134"></a>
 When MS Windows 200x/XP participates in a domain security context, and if the default user profile is not
 found, then the client will search for a default profile in the NETLOGON share of the authenticating server.
 In MS Windows parlance, it is <code class="filename">%LOGONSERVER%\NETLOGON\Default User,</code>
@@ -568,7 +568,7 @@ profile are controlled by entries on Windows 200x/XP is: </p><p> <code class="fi
 Folders\</code> </p><p>
 This hive key contains a list of automatically managed folders. The default entries are shown
 in <a class="link" href="ProfileMgmt.html#defregpthkeys" title="Table�27.3.�Defaults of Default User Profile Paths Registry Keys">the next table</a>
-<a class="indexterm" name="id2664143"></a>
+<a class="indexterm" name="id2664271"></a>
 </p><div class="table"><a name="defregpthkeys"></a><p class="title"><b>Table�27.3.�Defaults of Default User Profile Paths Registry Keys</b></p><div class="table-contents"><table summary="Defaults of Default User Profile Paths Registry Keys" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="left">Default Value</th></tr></thead><tbody><tr><td align="left">AppData</td><td align="left">%USERPROFILE%\Application Data</td></tr><tr><td align="left">Cache</td><td align="left">%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td align="left">Cookies</td><td align="left">%USERPROFILE%\Cookies</td></tr><tr><td align="left">Desktop</td><td align="left">%USERPROFILE%\Desktop</td></tr><tr><td align="left">Favorites</td><td align="left">%USERPROFILE%\Favorites</td></tr><tr><td align="left">History</td><td align="left">%USERPROFILE%\Local Settings\History</td></tr><tr><td align="left">Local AppData</td><td align="left">%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td align="left">Local Settings</td><td align="left">%USERPROFILE%\Local Settings</td></tr><tr><td align="left">My Pictures</td><td align="left">%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td align="left">NetHood</td><td align="left">%USERPROFILE%\NetHood</td></tr><tr><td align="left">Personal</td><td align="left">%USERPROFILE%\My Documents</td></tr><tr><td align="left">PrintHood</td><td align="left">%USERPROFILE%\PrintHood</td></tr><tr><td align="left">Programs</td><td align="left">%USERPROFILE%\Start Menu\Programs</td></tr><tr><td align="left">Recent</td><td align="left">%USERPROFILE%\Recent</td></tr><tr><td align="left">SendTo</td><td align="left">%USERPROFILE%\SendTo</td></tr><tr><td align="left">Start Menu</td><td align="left">%USERPROFILE%\Start Menu</td></tr><tr><td align="left">Startup</td><td align="left">%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td align="left">Templates</td><td align="left">%USERPROFILE%\Templates</td></tr></tbody></table></div></div><br class="table-break"><p> There is also an entry called &#8220;<span class="quote">Default</span>&#8221; that has no value set. The default entry is
 of type <code class="constant">REG_SZ</code>; all the others are of type <code class="constant">REG_EXPAND_SZ</code>. </p><p> It makes a huge difference to the speed of handling roaming user profiles if all the folders are
 stored on a dedicated location on a network server. This means that it will not be necessary to write
@@ -589,13 +589,13 @@ MS Windows user as seen by the Linux/UNIX file system.	</p><p> Please note that
 (default or custom) to it. </p><p> MS Windows 200x/XP profiles may be <span class="emphasis"><em>local</em></span> or <span class="emphasis"><em>roaming</em></span>.
 	A roaming profile is cached locally unless the following registry key is created: 
 
-<a class="indexterm" name="id2664417"></a>
+<a class="indexterm" name="id2664545"></a>
 </p><p> </p><pre class="programlisting"> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
 	winlogon\"DeleteRoamingCache"=dword:00000001</pre><p>
 In this case, the local cache copy is deleted on logout.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2664442"></a>Common Errors</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2664569"></a>Common Errors</h2></div></div></div><p>
 The following are some typical errors, problems, and questions that have been asked on the Samba mailing lists.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664453"></a>Configuring Roaming Profiles for a Few Users or Groups</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664580"></a>Configuring Roaming Profiles for a Few Users or Groups</h3></div></div></div><p>
 With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a
 global-only setting. The default is to have roaming profiles, and the default path will locate them in
 the user's home directory.
@@ -605,7 +605,7 @@ to apply only to certain machines, then on those machines on which roaming profi
 it is necessary to disable roaming profile handling in the registry of each such machine.
 </p><p>
 With Samba-3, you can have a global profile setting in <code class="filename">smb.conf</code>, and you can override this by
-per-user settings using the Domain User Manager (as with MS Windows NT4/200x). </p><p> In any case, you can configure only one profile per user. That profile can be either: </p><div class="itemizedlist"><ul type="disc"><li><p>A profile unique to that user.</p></li><li><p>A mandatory profile (one the user cannot change).</p></li><li><p>A group profile (really should be mandatory  that is, unchangable).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664514"></a>Cannot Use Roaming Profiles</h3></div></div></div><p> A user requested the following: &#8220;<span class="quote"> I do not want roaming profiles to be implemented. I want
+per-user settings using the Domain User Manager (as with MS Windows NT4/200x). </p><p> In any case, you can configure only one profile per user. That profile can be either: </p><div class="itemizedlist"><ul type="disc"><li><p>A profile unique to that user.</p></li><li><p>A mandatory profile (one the user cannot change).</p></li><li><p>A group profile (really should be mandatory  that is, unchangable).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664641"></a>Cannot Use Roaming Profiles</h3></div></div></div><p> A user requested the following: &#8220;<span class="quote"> I do not want roaming profiles to be implemented. I want
 to give users a local profile alone. I am totally lost with this error. For the past
 two days I tried everything, I googled around but found no useful pointers. Please help me. </span>&#8221;</p><p> The choices are: </p><div class="variablelist"><dl><dt><span class="term">Local profiles</span></dt><dd><p> I know of no registry keys that will allow
 		autodeletion of LOCAL profiles on log out.</p></dd><dt><span class="term">Roaming profiles</span></dt><dd><p> As a user logs onto the network, a centrally
@@ -625,20 +625,20 @@ workstation, but they harvest the fruits of folly (and ignorance). </p><p> The p
 changed as well as good discipline make for a problem-free site. </p><p> Microsoft's answer to the PST problem is to store all email in an MS Exchange Server backend. This
 removes the need for a PST file. </p><p>Local profiles mean: </p><div class="itemizedlist"><ul type="disc"><li><p>If each machine is used by many users, then much local disk storage is needed
 	for local profiles.</p></li><li><p>Every workstation the user logs into has
-	its own profile; these can be very different from machine to machine.</p></li></ul></div><p> On the other hand, use of roaming profiles means: </p><div class="itemizedlist"><ul type="disc"><li><p>The network administrator can control the desktop environment of all users.</p></li><li><p>Use of mandatory profiles drastically reduces network management overheads.</p></li><li><p>In the long run, users will experience fewer problems.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664685"></a>Changing the Default Profile</h3></div></div></div><p>&#8220;<span class="quote">When the client logs onto the domain controller, it searches
+	its own profile; these can be very different from machine to machine.</p></li></ul></div><p> On the other hand, use of roaming profiles means: </p><div class="itemizedlist"><ul type="disc"><li><p>The network administrator can control the desktop environment of all users.</p></li><li><p>Use of mandatory profiles drastically reduces network management overheads.</p></li><li><p>In the long run, users will experience fewer problems.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664813"></a>Changing the Default Profile</h3></div></div></div><p>&#8220;<span class="quote">When the client logs onto the domain controller, it searches
 for a profile to download. Where do I put this default profile?</span>&#8221;</p><p>
-<a class="indexterm" name="id2664700"></a>
+<a class="indexterm" name="id2664827"></a>
 First, the Samba server needs to be configured as a domain controller. This can be done by
-setting in <code class="filename">smb.conf</code>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2664721"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2664732"></a><em class="parameter"><code>os level = 32 (or more)</code></em></td></tr><tr><td><a class="indexterm" name="id2664744"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr></table><p> There must be a <em class="parameter"><code>[netlogon]</code></em> share that is world readable. It is
+setting in <code class="filename">smb.conf</code>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2664848"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2664860"></a><em class="parameter"><code>os level = 32 (or more)</code></em></td></tr><tr><td><a class="indexterm" name="id2664872"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr></table><p> There must be a <em class="parameter"><code>[netlogon]</code></em> share that is world readable. It is
 a good idea to add a logon script to preset printer and drive connections. There is also a facility
 for automatically synchronizing the workstation time clock with that of the logon server (another good
 thing to do). </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> To invoke autodeletion of roaming profiles from the local workstation cache (disk storage), use
 the <span class="application">Group Policy Editor</span> to create a file called <code class="filename">NTConfig.POL</code>
 with the appropriate entries. This file needs to be located in the <em class="parameter"><code>netlogon</code></em>
 share root directory.</p></div><p> Windows clients need to be members of the domain. Workgroup machines do not use network logons,
-so they do not interoperate with domain profiles. </p><p> For roaming profiles, add to <code class="filename">smb.conf</code>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2664816"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><a class="indexterm" name="id2664832"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664849"></a>Debugging Roaming Profiles and NT4-style Domain Policies</h3></div></div></div><p>
+so they do not interoperate with domain profiles. </p><p> For roaming profiles, add to <code class="filename">smb.conf</code>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2664944"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><a class="indexterm" name="id2664960"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2664976"></a>Debugging Roaming Profiles and NT4-style Domain Policies</h3></div></div></div><p>
 Roaming profiles and domain policies are implemented via <code class="literal">USERENV.DLL</code>. 
 Microsoft Knowledge Base articles <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;221833" target="_top">221833</a> and 
 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;154120" target="_top">154120</a>
  describe how to instruct that DLL to debug the login process.
-</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2662512" href="#id2662512" class="para">7</a>] </sup>http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&amp;displaylang=en</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="pam.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�26.�System and Account Policies�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�28.�PAM-Based Distributed Authentication</td></tr></table></div></body></html>
+</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="pam.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�26.�System and Account Policies�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�28.�PAM-Based Distributed Authentication</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/SWAT.html b/docs/htmldocs/Samba3-HOWTO/SWAT.html
index c932609e2b..417815cb84 100644
--- a/docs/htmldocs/Samba3-HOWTO/SWAT.html
+++ b/docs/htmldocs/Samba3-HOWTO/SWAT.html
@@ -1,27 +1,27 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�37.�SWAT: The Samba Web Administration Tool</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="NT4Migration.html" title="Chapter�36.�Migration from NT4 PDC to Samba-3 PDC"><link rel="next" href="troubleshooting.html" title="Part�V.�Troubleshooting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�37.�SWAT: The Samba Web Administration Tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter�37.�SWAT: The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SWAT.html#id2680929">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681054">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681073">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681711">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682061">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682074">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682135">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682237">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682293">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682349">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682412">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682456">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682475">The Password Change Page</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2680893"></a>
-<a class="indexterm" name="id2680900"></a>
-<a class="indexterm" name="id2680907"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�37.�SWAT: The Samba Web Administration Tool</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="NT4Migration.html" title="Chapter�36.�Migration from NT4 PDC to Samba-3 PDC"><link rel="next" href="troubleshooting.html" title="Part�V.�Troubleshooting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�37.�SWAT: The Samba Web Administration Tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter�37.�SWAT: The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SWAT.html#id2681092">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681216">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681236">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681873">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682223">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682236">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682297">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682399">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682455">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682511">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682574">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682618">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682637">The Password Change Page</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2681056"></a>
+<a class="indexterm" name="id2681062"></a>
+<a class="indexterm" name="id2681069"></a>
 There are many and varied opinions regarding the usefulness of SWAT.  No matter how hard one tries to produce
 the perfect configuration tool, it remains an object of personal taste. SWAT is a tool that allows Web-based
 configuration of Samba. It has a wizard that may help to get Samba configured quickly, it has
 context-sensitive help on each <code class="filename">smb.conf</code> parameter, it provides for monitoring of current state of connection
 information, and it allows networkwide MS Windows network password management.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680929"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2680937"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2681092"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2681100"></a>
 SWAT is a facility that is part of the Samba suite. The main executable is called
 <code class="literal">swat</code> and is invoked by the internetworking super daemon.
 See <a class="link" href="SWAT.html#xinetd" title="Enabling SWAT for Use">appropriate section</a> for details.
 </p><p>
-<a class="indexterm" name="id2680965"></a>
+<a class="indexterm" name="id2681127"></a>
 SWAT uses integral Samba components to locate parameters supported by the particular
 version of Samba. Unlike tools and utilities that are external to Samba, SWAT is always
 up to date as known Samba parameters change. SWAT provides context-sensitive help for each
 configuration parameter, directly from <code class="literal">man</code> page entries.
 </p><p>
-<a class="indexterm" name="id2680986"></a>
-<a class="indexterm" name="id2680993"></a>
-<a class="indexterm" name="id2681000"></a>
+<a class="indexterm" name="id2681148"></a>
+<a class="indexterm" name="id2681155"></a>
+<a class="indexterm" name="id2681162"></a>
 Some network administrators believe that it is a good idea to write systems
 documentation inside configuration files, and for them SWAT will always be a nasty tool. SWAT
 does not store the configuration file in any intermediate form; rather, it stores only the
@@ -30,38 +30,38 @@ those parameters that are at other than the default settings. The result is that
 as well as parameters that are no longer supported, will be lost from the <code class="filename">smb.conf</code> file.
 Additionally, the parameters will be written back in internal ordering.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2681033"></a>
+<a class="indexterm" name="id2681195"></a>
 Before using SWAT, please be warned  SWAT will completely replace your <code class="filename">smb.conf</code> with
 a fully optimized file that has been stripped of all comments you might have placed there
 and only nondefault settings will be written to the file.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2681054"></a>Guidelines and Technical Tips</h2></div></div></div><p>
-<a class="indexterm" name="id2681062"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2681216"></a>Guidelines and Technical Tips</h2></div></div></div><p>
+<a class="indexterm" name="id2681224"></a>
 This section aims to unlock the dark secrets behind how SWAT may be made to work,
 how it can be made more secure, and how to solve internationalization support problems.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681073"></a>Validate SWAT Installation</h3></div></div></div><p>
-<a class="indexterm" name="id2681081"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681236"></a>Validate SWAT Installation</h3></div></div></div><p>
+<a class="indexterm" name="id2681244"></a>
 The very first step that should be taken before attempting to configure a host
 system for SWAT operation is to check that it is installed. This may seem a trivial
 point to some, but several Linux distributions do not install SWAT by default,
 even though they do ship an installable binary support package containing SWAT
 on the distribution media.
 </p><p>
-<a class="indexterm" name="id2681098"></a>
+<a class="indexterm" name="id2681260"></a>
 When you have confirmed that SWAT is installed, it is necessary to validate
 that the installation includes the binary <code class="literal">swat</code> file as well
 as all the supporting text and Web files. A number of operating system distributions
 in the past have failed to include the necessary support files, even though the
 <code class="literal">swat</code> binary executable file was installed. 
 </p><p>
-<a class="indexterm" name="id2681125"></a>
-<a class="indexterm" name="id2681132"></a>
+<a class="indexterm" name="id2681287"></a>
+<a class="indexterm" name="id2681294"></a>
 Finally, when you are sure that SWAT has been fully installed, please check that SWAT
 is enabled in the control file for the internetworking super-daemon (inetd or xinetd)
 that is used on your operating system platform. 
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681144"></a>Locating the <code class="literal">SWAT</code> File</h4></div></div></div><p>
-<a class="indexterm" name="id2681157"></a>
-<a class="indexterm" name="id2681164"></a>
-<a class="indexterm" name="id2681171"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681306"></a>Locating the <code class="literal">SWAT</code> File</h4></div></div></div><p>
+<a class="indexterm" name="id2681320"></a>
+<a class="indexterm" name="id2681327"></a>
+<a class="indexterm" name="id2681334"></a>
 To validate that SWAT is installed, first locate the <code class="literal">swat</code> binary
 file on the system. It may be found under the following directories:</p><table class="simplelist" border="0" summary="Simple list"><tr><td><code class="filename">/usr/local/samba/bin</code>  the default Samba location</td></tr><tr><td><code class="filename">/usr/sbin</code>  the default location on most Linux systems</td></tr><tr><td><code class="filename">/opt/samba/bin</code></td></tr></table><p>
 </p><p>
@@ -71,9 +71,9 @@ by the administrator who compiled and installed Samba.
 There are a number of methods that may be used to locate the <code class="literal">swat</code> binary file.
 The following methods may be helpful.
 </p><p>
-<a class="indexterm" name="id2681244"></a>
-<a class="indexterm" name="id2681250"></a>
-<a class="indexterm" name="id2681258"></a>
+<a class="indexterm" name="id2681406"></a>
+<a class="indexterm" name="id2681413"></a>
+<a class="indexterm" name="id2681420"></a>
 If <code class="literal">swat</code> is in your current operating system search path, it will be easy to 
 find it. You can ask what are the command-line options for <code class="literal">swat</code> as shown here:
 </p><pre class="screen">
@@ -91,7 +91,7 @@ Common samba options:
   -l, --log-basename=LOGFILEBASE       Basename for log/debug files
   -V, --version                        Print version
 </pre><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681296"></a>Locating the SWAT Support Files</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681458"></a>Locating the SWAT Support Files</h4></div></div></div><p>
 Now that you have found that <code class="literal">swat</code> is in the search path, it is easy
 to identify where the file is located. Here is another simple way this may be done:
 </p><pre class="screen">
@@ -173,7 +173,7 @@ implementation. The control file (or files) can be located in the file
 or in a similar location.
 </p><p>
 The control entry for the older style file might be:
-<a class="indexterm" name="id2681488"></a>
+<a class="indexterm" name="id2681651"></a>
 </p><pre class="programlisting">
 	# swat is the Samba Web Administration Tool
 	swat stream tcp nowait.400 root /usr/sbin/swat swat
@@ -201,10 +201,10 @@ In the above, the default setting for <em class="parameter"><code>disable</code>
 This means that SWAT is disabled. To enable use of SWAT, set this parameter to <code class="constant">no</code>
 as shown.
 </p><p>
-<a class="indexterm" name="id2681544"></a>
-<a class="indexterm" name="id2681551"></a>
-<a class="indexterm" name="id2681557"></a>
-<a class="indexterm" name="id2681564"></a>
+<a class="indexterm" name="id2681706"></a>
+<a class="indexterm" name="id2681713"></a>
+<a class="indexterm" name="id2681720"></a>
+<a class="indexterm" name="id2681727"></a>
 Both of the previous examples assume that the <code class="literal">swat</code> binary has been
 located in the <code class="filename">/usr/sbin</code> directory. In addition to the above,
 SWAT will use a directory access point from which it will load its Help files
@@ -212,8 +212,8 @@ as well as other control information. The default location for this on most Linu
 systems is in the directory <code class="filename">/usr/share/samba/swat</code>. The default
 location using Samba defaults will be <code class="filename">/usr/local/samba/swat</code>.
 </p><p>
-<a class="indexterm" name="id2681605"></a>
-<a class="indexterm" name="id2681612"></a>
+<a class="indexterm" name="id2681767"></a>
+<a class="indexterm" name="id2681774"></a>
 Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user,
 the only permission allowed is to view certain aspects of configuration as well as
 access to the password change facility. The buttons that will be exposed to the non-root
@@ -225,21 +225,21 @@ As long as you log onto SWAT as the user <span class="emphasis"><em>root</em></s
 full change and commit ability. The buttons that will be exposed include
 <span class="guibutton">HOME</span>, <span class="guibutton">GLOBALS</span>, <span class="guibutton">SHARES</span>, <span class="guibutton">PRINTERS</span>, 
 <span class="guibutton">WIZARD</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, and <span class="guibutton">PASSWORD</span>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681711"></a>Securing SWAT through SSL</h3></div></div></div><p>
-<a class="indexterm" name="id2681719"></a>
-<a class="indexterm" name="id2681726"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681873"></a>Securing SWAT through SSL</h3></div></div></div><p>
+<a class="indexterm" name="id2681881"></a>
+<a class="indexterm" name="id2681888"></a>
 Many people have asked about how to set up SWAT with SSL to allow for secure remote
 administration of Samba. Here is a method that works, courtesy of Markus Krieger.
 </p><p>
 Modifications to the SWAT setup are as follows: 
 </p><div class="procedure"><ol type="1"><li><p>
-<a class="indexterm" name="id2681751"></a>
+<a class="indexterm" name="id2681913"></a>
 	Install OpenSSL.
 	</p></li><li><p>
-<a class="indexterm" name="id2681765"></a>
-<a class="indexterm" name="id2681772"></a>
+<a class="indexterm" name="id2681927"></a>
+<a class="indexterm" name="id2681934"></a>
 	Generate certificate and private key.
-<a class="indexterm" name="id2681779"></a>
+<a class="indexterm" name="id2681941"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>/usr/bin/openssl req -new -x509 -days 365 -nodes -config \
 	/usr/share/doc/packages/stunnel/stunnel.cnf \
@@ -247,7 +247,7 @@ Modifications to the SWAT setup are as follows:
 </pre></li><li><p>
 	Remove SWAT entry from [x]inetd.
 	</p></li><li><p>
-<a class="indexterm" name="id2681818"></a>
+<a class="indexterm" name="id2681980"></a>
 	Start <code class="literal">stunnel</code>.
 
 </p><pre class="screen">
@@ -255,7 +255,7 @@ Modifications to the SWAT setup are as follows:
 	 -l /usr/local/samba/bin/swat swat </code></strong>
 </pre></li></ol></div><p>
 Afterward, simply connect to SWAT by using the URL <a class="ulink" href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate, and the SSL connection is up.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681863"></a>Enabling SWAT Internationalization Support</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682025"></a>Enabling SWAT Internationalization Support</h3></div></div></div><p>
 SWAT can be configured to display its messages to match the settings of
 the language configurations of your Web browser. It will be passed to SWAT 
 in the Accept-Language header of the HTTP request.
@@ -267,14 +267,14 @@ To enable this feature:
 	</p></li><li><p>
 	Set your browsers language setting.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2681907"></a>
-<a class="indexterm" name="id2681914"></a>
-<a class="indexterm" name="id2681921"></a>
-<a class="indexterm" name="id2681927"></a>
+<a class="indexterm" name="id2682069"></a>
+<a class="indexterm" name="id2682076"></a>
+<a class="indexterm" name="id2682083"></a>
+<a class="indexterm" name="id2682090"></a>
 The name of the <code class="literal">msg</code> file is the same as the language ID sent by the browser. For
 example, <span class="emphasis"><em>en</em></span> means English, <span class="emphasis"><em>ja</em></span> means Japanese, <span class="emphasis"><em>fr</em></span> means French.
 </p><p>
-<a class="indexterm" name="id2681956"></a>
+<a class="indexterm" name="id2682118"></a>
 If you do not like some of messages, or there are no <code class="literal">msg</code> files for
 your locale, you can create them simply by copying the <code class="literal">en.msg</code> files
 to the directory for &#8220;<span class="quote">your language ID.msg</span>&#8221; and filling in proper strings
@@ -284,20 +284,20 @@ to each &#8220;<span class="quote">msgstr</span>&#8221;. For example, in <code c
 msgid "Set Default"
 msgstr "Imposta Default"
 </pre><p>
-<a class="indexterm" name="id2682004"></a>
+<a class="indexterm" name="id2682167"></a>
 and so on. If you find a mistake or create a new <code class="literal">msg</code> file, please email it
 to us so we will consider it in the next release of Samba. The <code class="literal">msg</code> file should be encoded in UTF-8.
 </p><p>
-<a class="indexterm" name="id2682028"></a>
+<a class="indexterm" name="id2682190"></a>
 Note that if you enable this feature and the <a class="link" href="smb.conf.5.html#DISPLAYCHARSET" target="_top">display charset</a> is not
 matched to your browser's setting, the SWAT display may be corrupted.  In a future version of
 Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set
 this <code class="filename">smb.conf</code> file parameter.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682061"></a>Overview and Quick Tour</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682223"></a>Overview and Quick Tour</h2></div></div></div><p>
 SWAT is a tool that may be used to configure Samba or just to obtain useful links
 to important reference materials such as the contents of this book as well as other
 documents that have been found useful for solving Windows networking problems.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682074"></a>The SWAT Home Page</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682236"></a>The SWAT Home Page</h3></div></div></div><p>
 The SWAT title page provides access to the latest Samba documentation. The manual page for
 each Samba component is accessible from this page, as are the Samba3-HOWTO (this 
 document) as well as the O'Reilly book &#8220;<span class="quote">Using Samba.</span>&#8221;
@@ -312,7 +312,7 @@ because it runs SWAT without authentication and with full administrative ability
 changes to <code class="filename">smb.conf</code> as well as general operation with root privileges. The option that
 creates this ability is the <code class="option">-a</code> flag to SWAT. <span class="emphasis"><em>Do not use this in a
 production environment.</em></span>
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682135"></a>Global Settings</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682297"></a>Global Settings</h3></div></div></div><p>
 The <span class="guibutton">GLOBALS</span> button exposes a page that allows configuration of the global parameters
 in <code class="filename">smb.conf</code>. There are two levels of exposure of the parameters:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -332,7 +332,7 @@ your changes will be lost.
 SWAT has context-sensitive help. To find out what each parameter is
 for, simply click on the
 <span class="guibutton">Help</span> link to the left of the configuration parameter.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682237"></a>Share Settings</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682399"></a>Share Settings</h3></div></div></div><p>
 To affect a currently configured share, simply click on the pull-down button between the
 <span class="guibutton">Choose Share</span> and the <span class="guibutton">Delete Share</span> buttons and
 select the share you wish to operate on. To edit the settings,
@@ -343,7 +343,7 @@ click on the
 To create a new share, next to the button labeled <span class="guibutton">Create Share</span>, enter
 into the text field the name of the share to be created, then click on the 
 <span class="guibutton">Create Share</span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682293"></a>Printers Settings</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682455"></a>Printers Settings</h3></div></div></div><p>
 To affect a currently configured printer, simply click on the pull-down button between the
 <span class="guibutton">Choose Printer</span> and the <span class="guibutton">Delete Printer</span> buttons and
 select the printer you wish to operate on. To edit the settings,
@@ -354,7 +354,7 @@ click on the
 To create a new printer, next to the button labeled <span class="guibutton">Create Printer</span>, enter
 into the text field the name of the share to be created, then click on the 
 <span class="guibutton">Create Printer</span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682349"></a>The SWAT Wizard</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682511"></a>The SWAT Wizard</h3></div></div></div><p>
 The purpose of the SWAT Wizard is to help the Microsoft-knowledgeable network administrator
 to configure Samba with a minimum of effort.
 </p><p>
@@ -370,7 +370,7 @@ Finally, there are a limited set of options that determine what type of server S
 will be configured for, whether it will be a WINS server, participate as a WINS client, or
 operate with no WINS support. By clicking one button, you can elect to expose (or not) user
 home directories.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682412"></a>The Status Page</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682574"></a>The Status Page</h3></div></div></div><p>
 The status page serves a limited purpose. First, it allows control of the Samba daemons.
 The key daemons that create the Samba server environment are <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span>.
 </p><p>
@@ -381,11 +381,11 @@ conditions with minimal effort.
 </p><p>
 Finally, the status page may be used to terminate specific smbd client connections in order to
 free files that may be locked.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682456"></a>The View Page</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682618"></a>The View Page</h3></div></div></div><p>
 The view page allows you to view the optimized <code class="filename">smb.conf</code> file and, if you are
 particularly masochistic, permits you also to see all possible global configuration
 parameters and their settings.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682475"></a>The Password Change Page</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2682637"></a>The Password Change Page</h3></div></div></div><p>
 The password change page is a popular tool that allows the creation, deletion, deactivation,
 and reactivation of MS Windows networking users on the local machine. You can also use
 this tool to change a local password for a user account.
diff --git a/docs/htmldocs/Samba3-HOWTO/SambaHA.html b/docs/htmldocs/Samba3-HOWTO/SambaHA.html
index 6bf8229996..e914f77eef 100644
--- a/docs/htmldocs/Samba3-HOWTO/SambaHA.html
+++ b/docs/htmldocs/Samba3-HOWTO/SambaHA.html
@@ -1,17 +1,17 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�32.�High Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="Backup.html" title="Chapter�31.�Backup Techniques"><link rel="next" href="largefile.html" title="Chapter�33.�Handling Large Directories"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�32.�High Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Backup.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="largefile.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter�32.�High Availability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SambaHA.html#id2671868">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2671989">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672023">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672152">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672866">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672946">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673086">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673123">Conclusions</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671868"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2671876"></a>
-<a class="indexterm" name="id2671883"></a>
-<a class="indexterm" name="id2671890"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�32.�High Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="Backup.html" title="Chapter�31.�Backup Techniques"><link rel="next" href="largefile.html" title="Chapter�33.�Handling Large Directories"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�32.�High Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Backup.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="largefile.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter�32.�High Availability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SambaHA.html#id2672006">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2672127">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672161">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672290">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673010">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673091">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673231">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673268">Conclusions</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2672006"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2672014"></a>
+<a class="indexterm" name="id2672021"></a>
+<a class="indexterm" name="id2672028"></a>
 Network administrators are often concerned about the availability of file and print
 services. Network users are inclined toward intolerance of the services they depend
 on to perform vital task responsibilities.
 </p><p>
 A sign in a computer room served to remind staff of their responsibilities. It read:
 </p><div class="blockquote"><blockquote class="blockquote"><p>
-<a class="indexterm" name="id2671910"></a>
-<a class="indexterm" name="id2671917"></a>
-<a class="indexterm" name="id2671924"></a>
-<a class="indexterm" name="id2671931"></a>
+<a class="indexterm" name="id2672048"></a>
+<a class="indexterm" name="id2672055"></a>
+<a class="indexterm" name="id2672062"></a>
+<a class="indexterm" name="id2672069"></a>
 All humans fail, in both great and small ways we fail continually. Machines fail too.
 Computers are machines that are managed by humans, the fallout from failure
 can be spectacular. Your responsibility is to deal with failure, to anticipate it
@@ -21,9 +21,9 @@ Are your actions part of the problem or part of the solution?
 If we are to deal with failure in a planned and productive manner, then first we must
 understand the problem. That is the purpose of this chapter.
 </p><p>
-<a class="indexterm" name="id2671955"></a>
-<a class="indexterm" name="id2671962"></a>
-<a class="indexterm" name="id2671968"></a>
+<a class="indexterm" name="id2672093"></a>
+<a class="indexterm" name="id2672100"></a>
+<a class="indexterm" name="id2672106"></a>
 Parenthetically, in the following discussion there are seeds of information on how to
 provision a network infrastructure against failure. Our purpose here is not to provide
 a lengthy dissertation on the subject of high availability. Additionally, we have made
@@ -32,37 +32,37 @@ solutions; instead we present an overview of the issues in the hope that someone
 rise to the challenge of providing a detailed document that is focused purely on
 presentation of the current state of knowledge and practice in high availability as it
 applies to the deployment of Samba and other CIFS/SMB technologies.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671989"></a>Technical Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2671997"></a>
-<a class="indexterm" name="id2672004"></a>
-<a class="indexterm" name="id2672010"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2672127"></a>Technical Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2672135"></a>
+<a class="indexterm" name="id2672142"></a>
+<a class="indexterm" name="id2672148"></a>
 The following summary was part of a presentation by Jeremy Allison at the SambaXP 2003
 conference that was held at Goettingen, Germany, in April 2003. Material has been added
 from other sources, but it was Jeremy who inspired the structure that follows.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672023"></a>The Ultimate Goal</h3></div></div></div><p>
-<a class="indexterm" name="id2672031"></a>
-<a class="indexterm" name="id2672038"></a>
-<a class="indexterm" name="id2672045"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672161"></a>The Ultimate Goal</h3></div></div></div><p>
+<a class="indexterm" name="id2672169"></a>
+<a class="indexterm" name="id2672176"></a>
+<a class="indexterm" name="id2672183"></a>
 	All clustering technologies aim to achieve one or more of the following:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Obtain the maximum affordable computational power.</p></li><li><p>Obtain faster program execution.</p></li><li><p>Deliver unstoppable services.</p></li><li><p>Avert points of failure.</p></li><li><p>Exact most effective utilization of resources.</p></li></ul></div><p>
 	A clustered file server ideally has the following properties:
-<a class="indexterm" name="id2672086"></a>
-<a class="indexterm" name="id2672093"></a>
-<a class="indexterm" name="id2672100"></a>
-<a class="indexterm" name="id2672107"></a>
-	</p><div class="itemizedlist"><ul type="disc"><li><p>All clients can connect transparently to any server.</p></li><li><p>A server can fail and clients are transparently reconnected to another server.</p></li><li><p>All servers serve out the same set of files.</p></li><li><p>All file changes are immediately seen on all servers.</p><div class="itemizedlist"><ul type="circle"><li><p>Requires a distributed file system.</p></li></ul></div></li><li><p>Infinite ability to scale by adding more servers or disks.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672152"></a>Why Is This So Hard?</h3></div></div></div><p>
+<a class="indexterm" name="id2672224"></a>
+<a class="indexterm" name="id2672231"></a>
+<a class="indexterm" name="id2672238"></a>
+<a class="indexterm" name="id2672245"></a>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>All clients can connect transparently to any server.</p></li><li><p>A server can fail and clients are transparently reconnected to another server.</p></li><li><p>All servers serve out the same set of files.</p></li><li><p>All file changes are immediately seen on all servers.</p><div class="itemizedlist"><ul type="circle"><li><p>Requires a distributed file system.</p></li></ul></div></li><li><p>Infinite ability to scale by adding more servers or disks.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672290"></a>Why Is This So Hard?</h3></div></div></div><p>
 	In short, the problem is one of <span class="emphasis"><em>state</em></span>.
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2672172"></a>
+<a class="indexterm" name="id2672310"></a>
 			All TCP/IP connections are dependent on state information.
 			</p><p>
-<a class="indexterm" name="id2672183"></a>
+<a class="indexterm" name="id2672321"></a>
 			The TCP connection involves a packet sequence number. This
 			sequence number would need to be dynamically updated on all
 			machines in the cluster to effect seamless TCP failover.
 			</p></li><li><p>
-<a class="indexterm" name="id2672200"></a>
-<a class="indexterm" name="id2672207"></a>
+<a class="indexterm" name="id2672338"></a>
+<a class="indexterm" name="id2672345"></a>
 			CIFS/SMB (the Windows networking protocols) uses TCP connections.
 			</p><p>
 			This means that from a basic design perspective, failover is not
@@ -71,91 +71,91 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 				All current SMB clusters are failover solutions
 				 they rely on the clients to reconnect. They provide server
 				failover, but clients can lose information due to a server failure.
-<a class="indexterm" name="id2672231"></a>
+<a class="indexterm" name="id2672369"></a>
 				</p></li></ul></div><p>
 			</p></li><li><p>
 			Servers keep state information about client connections.
-			</p><div class="itemizedlist"><a class="indexterm" name="id2672250"></a><ul type="circle"><li><p>CIFS/SMB involves a lot of state.</p></li><li><p>Every file open must be compared with other open files
+			</p><div class="itemizedlist"><a class="indexterm" name="id2672388"></a><ul type="circle"><li><p>CIFS/SMB involves a lot of state.</p></li><li><p>Every file open must be compared with other open files
 						to check share modes.</p></li></ul></div><p>
-			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672271"></a>The Front-End Challenge</h4></div></div></div><p>
-<a class="indexterm" name="id2672279"></a>
-<a class="indexterm" name="id2672286"></a>
-<a class="indexterm" name="id2672293"></a>
-<a class="indexterm" name="id2672300"></a>
-<a class="indexterm" name="id2672307"></a>
-<a class="indexterm" name="id2672314"></a>
-<a class="indexterm" name="id2672321"></a>
+			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672409"></a>The Front-End Challenge</h4></div></div></div><p>
+<a class="indexterm" name="id2672417"></a>
+<a class="indexterm" name="id2672424"></a>
+<a class="indexterm" name="id2672431"></a>
+<a class="indexterm" name="id2672438"></a>
+<a class="indexterm" name="id2672445"></a>
+<a class="indexterm" name="id2672452"></a>
+<a class="indexterm" name="id2672459"></a>
 		To make it possible for a cluster of file servers to appear as a single server that has one
 		name and one IP address, the incoming TCP data streams from clients must be processed by the
 		front-end virtual server. This server must de-multiplex the incoming packets at the SMB protocol
 		layer level and then feed the SMB packet to different servers in the cluster.
 		</p><p>
-<a class="indexterm" name="id2672337"></a>
-<a class="indexterm" name="id2672344"></a>
+<a class="indexterm" name="id2672475"></a>
+<a class="indexterm" name="id2672482"></a>
 		One could split all IPC$ connections and RPC calls to one server to handle printing and user
 		lookup requirements. RPC printing handles are shared between different IPC4 sessions  it is
 		hard to split this across clustered servers!
 		</p><p>
 		Conceptually speaking, all other servers would then provide only file services. This is a simpler
 		problem to concentrate on.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672366"></a>Demultiplexing SMB Requests</h4></div></div></div><p>
-<a class="indexterm" name="id2672373"></a>
-<a class="indexterm" name="id2672380"></a>
-<a class="indexterm" name="id2672387"></a>
-<a class="indexterm" name="id2672394"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672504"></a>Demultiplexing SMB Requests</h4></div></div></div><p>
+<a class="indexterm" name="id2672511"></a>
+<a class="indexterm" name="id2672518"></a>
+<a class="indexterm" name="id2672525"></a>
+<a class="indexterm" name="id2672532"></a>
 		De-multiplexing of SMB requests requires knowledge of SMB state information,
 		all of which must be held by the front-end <span class="emphasis"><em>virtual</em></span> server.
 		This is a perplexing and complicated problem to solve.
 		</p><p>
-<a class="indexterm" name="id2672412"></a>
-<a class="indexterm" name="id2672418"></a>
-<a class="indexterm" name="id2672425"></a>
+<a class="indexterm" name="id2672550"></a>
+<a class="indexterm" name="id2672556"></a>
+<a class="indexterm" name="id2672563"></a>
 		Windows XP and later have changed semantics so state information (vuid, tid, fid)
 		must match for a successful operation. This makes things simpler than before and is a
 		positive step forward.
 		</p><p>
-<a class="indexterm" name="id2672438"></a>
-<a class="indexterm" name="id2672445"></a>
+<a class="indexterm" name="id2672576"></a>
+<a class="indexterm" name="id2672583"></a>
 		SMB requests are sent by vuid to their associated server. No code exists today to
 		effect this solution. This problem is conceptually similar to the problem of
 		correctly handling requests from multiple requests from Windows 2000
 		Terminal Server in Samba.
 		</p><p>
-<a class="indexterm" name="id2672460"></a>
+<a class="indexterm" name="id2672598"></a>
 		One possibility is to start by exposing the server pool to clients directly.
 		This could eliminate the de-multiplexing step.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672471"></a>The Distributed File System Challenge</h4></div></div></div><p>
-<a class="indexterm" name="id2672480"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672609"></a>The Distributed File System Challenge</h4></div></div></div><p>
+<a class="indexterm" name="id2672618"></a>
 		There exists many distributed file systems for UNIX and Linux.
 		</p><p>
-<a class="indexterm" name="id2672491"></a>
-<a class="indexterm" name="id2672498"></a>
-<a class="indexterm" name="id2672505"></a>
-<a class="indexterm" name="id2672512"></a>
-<a class="indexterm" name="id2672519"></a>
-<a class="indexterm" name="id2672525"></a>
+<a class="indexterm" name="id2672629"></a>
+<a class="indexterm" name="id2672636"></a>
+<a class="indexterm" name="id2672643"></a>
+<a class="indexterm" name="id2672650"></a>
+<a class="indexterm" name="id2672657"></a>
+<a class="indexterm" name="id2672663"></a>
 		Many could be adopted to backend our cluster, so long as awareness of SMB
 		semantics is kept in mind (share modes, locking, and oplock issues in particular).
 		Common free distributed file systems include:
-<a class="indexterm" name="id2672536"></a>
-<a class="indexterm" name="id2672543"></a>
-<a class="indexterm" name="id2672550"></a>
-<a class="indexterm" name="id2672556"></a>
+<a class="indexterm" name="id2672674"></a>
+<a class="indexterm" name="id2672681"></a>
+<a class="indexterm" name="id2672688"></a>
+<a class="indexterm" name="id2672694"></a>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>NFS</p></li><li><p>AFS</p></li><li><p>OpenGFS</p></li><li><p>Lustre</p></li></ul></div><p>
-<a class="indexterm" name="id2672587"></a>
+<a class="indexterm" name="id2672725"></a>
 		The server pool (cluster) can use any distributed file system backend if all SMB
 		semantics are performed within this pool.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672598"></a>Restrictive Constraints on Distributed File Systems</h4></div></div></div><p>
-<a class="indexterm" name="id2672607"></a>
-<a class="indexterm" name="id2672614"></a>
-<a class="indexterm" name="id2672621"></a>
-<a class="indexterm" name="id2672627"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672736"></a>Restrictive Constraints on Distributed File Systems</h4></div></div></div><p>
+<a class="indexterm" name="id2672745"></a>
+<a class="indexterm" name="id2672752"></a>
+<a class="indexterm" name="id2672759"></a>
+<a class="indexterm" name="id2672765"></a>
 		Where a clustered server provides purely SMB services, oplock handling
 		may be done within the server pool without imposing a need for this to
 		be passed to the backend file system pool.
 		</p><p>
-<a class="indexterm" name="id2672641"></a>
-<a class="indexterm" name="id2672648"></a>
+<a class="indexterm" name="id2672779"></a>
+<a class="indexterm" name="id2672786"></a>
 		On the other hand, where the server pool also provides NFS or other file services,
 		it will be essential that the implementation be oplock-aware so it can
 		interoperate with SMB services. This is a significant challenge today. A failure
@@ -163,25 +163,25 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 		sorely noted by users of Microsoft Windows clients.
 		</p><p>
 		Last, all state information must be shared across the server pool.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672668"></a>Server Pool Communications</h4></div></div></div><p>
-<a class="indexterm" name="id2672676"></a>
-<a class="indexterm" name="id2672683"></a>
-<a class="indexterm" name="id2672689"></a>
-<a class="indexterm" name="id2672696"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672812"></a>Server Pool Communications</h4></div></div></div><p>
+<a class="indexterm" name="id2672820"></a>
+<a class="indexterm" name="id2672827"></a>
+<a class="indexterm" name="id2672834"></a>
+<a class="indexterm" name="id2672841"></a>
 		Most backend file systems support POSIX file semantics. This makes it difficult
 		to push SMB semantics back into the file system. POSIX locks have different properties
 		and semantics from SMB locks.
 		</p><p>
-<a class="indexterm" name="id2672710"></a>
-<a class="indexterm" name="id2672716"></a>
-<a class="indexterm" name="id2672723"></a>
+<a class="indexterm" name="id2672854"></a>
+<a class="indexterm" name="id2672861"></a>
+<a class="indexterm" name="id2672868"></a>
 		All <code class="literal">smbd</code> processes in the server pool must of necessity communicate
 		very quickly. For this, the current <em class="parameter"><code>tdb</code></em> file structure that Samba
 		uses is not suitable for use across a network. Clustered <code class="literal">smbd</code>s must use something else.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672753"></a>Server Pool Communications Demands</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672898"></a>Server Pool Communications Demands</h4></div></div></div><p>
 		High-speed interserver communications in the server pool is a design prerequisite
 		for a fully functional system. Possibilities for this include:
-		</p><div class="itemizedlist"><a class="indexterm" name="id2672767"></a><a class="indexterm" name="id2672774"></a><ul type="disc"><li><p>
+		</p><div class="itemizedlist"><a class="indexterm" name="id2672912"></a><a class="indexterm" name="id2672919"></a><ul type="disc"><li><p>
 			Proprietary shared memory bus (example: Myrinet or SCI [scalable coherent interface]).
 			These are high-cost items.
 			</p></li><li><p>
@@ -191,7 +191,7 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 			</p></li></ul></div><p>
 		We have yet to identify metrics for  performance demands to enable this to happen
 		effectively.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672808"></a>Required Modifications to Samba</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2672953"></a>Required Modifications to Samba</h4></div></div></div><p>
 		Samba needs to be significantly modified to work with a high-speed server interconnect
 		system to permit transparent failover clustering.
 		</p><p>
@@ -200,8 +200,8 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 			The locking database, oplock notifications,
 			and the share mode database.
 			</p></li><li><p>
-<a class="indexterm" name="id2672835"></a>
-<a class="indexterm" name="id2672842"></a>
+<a class="indexterm" name="id2672980"></a>
+<a class="indexterm" name="id2672987"></a>
 			Failure semantics need to be defined. Samba behaves the same way as Windows.
 			When oplock messages fail, a file open request is allowed, but this is 
 			potentially dangerous in a clustered environment. So how should interserver
@@ -209,58 +209,58 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 			</p></li><li><p>
 			Should this be implemented using a point-to-point lock manager, or can this
 			be done using multicast techniques?
-			</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672866"></a>A Simple Solution</h3></div></div></div><p>
-<a class="indexterm" name="id2672873"></a>
-<a class="indexterm" name="id2672880"></a>
-<a class="indexterm" name="id2672887"></a>
+			</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673010"></a>A Simple Solution</h3></div></div></div><p>
+<a class="indexterm" name="id2673018"></a>
+<a class="indexterm" name="id2673025"></a>
+<a class="indexterm" name="id2673032"></a>
 	Allowing failover servers to handle different functions within the exported file system
 	removes the problem of requiring a distributed locking protocol.
 	</p><p>
-<a class="indexterm" name="id2672901"></a>
-<a class="indexterm" name="id2672908"></a>
+<a class="indexterm" name="id2673045"></a>
+<a class="indexterm" name="id2673052"></a>
 	If only one server is active in a pair, the need for high-speed server interconnect is avoided.
 	This allows the use of existing high-availability solutions, instead of inventing a new one.
 	This simpler solution comes at a price  the cost of which is the need to manage a more
 	complex file name space. Since there is now not a single file system, administrators
 	must remember where all services are located  a complexity not easily dealt with.
 	</p><p>
-<a class="indexterm" name="id2672932"></a>
+<a class="indexterm" name="id2673077"></a>
 	The <span class="emphasis"><em>virtual server</em></span> is still needed to redirect requests to backend
 	servers. Backend file space integrity is the responsibility of the administrator.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2672946"></a>High-Availability Server Products</h3></div></div></div><p>
-<a class="indexterm" name="id2672954"></a>
-<a class="indexterm" name="id2672961"></a>
-<a class="indexterm" name="id2672968"></a>
-<a class="indexterm" name="id2672975"></a>
-<a class="indexterm" name="id2672982"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673091"></a>High-Availability Server Products</h3></div></div></div><p>
+<a class="indexterm" name="id2673099"></a>
+<a class="indexterm" name="id2673106"></a>
+<a class="indexterm" name="id2673113"></a>
+<a class="indexterm" name="id2673120"></a>
+<a class="indexterm" name="id2673127"></a>
 	Failover servers must communicate in order to handle resource failover. This is essential
 	for high-availability services. The use of a dedicated heartbeat is a common technique to
 	introduce some intelligence into the failover process. This is often done over a dedicated
 	link (LAN or serial).
 	</p><p>
-<a class="indexterm" name="id2672997"></a>
-<a class="indexterm" name="id2673004"></a>
-<a class="indexterm" name="id2673011"></a>
-<a class="indexterm" name="id2673018"></a>
-<a class="indexterm" name="id2673025"></a>
+<a class="indexterm" name="id2673142"></a>
+<a class="indexterm" name="id2673149"></a>
+<a class="indexterm" name="id2673156"></a>
+<a class="indexterm" name="id2673163"></a>
+<a class="indexterm" name="id2673170"></a>
 	Many failover solutions (like Red Hat Cluster Manager and Microsoft Wolfpack)
 	can use a shared SCSI of Fiber Channel disk storage array for failover communication.
 	Information regarding Red Hat high availability solutions for Samba may be obtained from
 	<a class="ulink" href="http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/cluster-manager/s1-service-samba.html" target="_top">www.redhat.com</a>.
 	</p><p>
-<a class="indexterm" name="id2673047"></a>
+<a class="indexterm" name="id2673192"></a>
 	The Linux High Availability project is a resource worthy of consultation if your desire is
 	to build a highly available Samba file server solution. Please consult the home page at
 	<a class="ulink" href="http://www.linux-ha.org/" target="_top">www.linux-ha.org/</a>.
 	</p><p>
-<a class="indexterm" name="id2673067"></a>
-<a class="indexterm" name="id2673074"></a>
+<a class="indexterm" name="id2673211"></a>
+<a class="indexterm" name="id2673218"></a>
 	Front-end server complexity remains a challenge for high availability because it must deal
 	gracefully with backend failures, while at the same time providing continuity of service
 	to all network clients.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673086"></a>MS-DFS: The Poor Man's Cluster</h3></div></div></div><p>
-<a class="indexterm" name="id2673095"></a>
-<a class="indexterm" name="id2673101"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673231"></a>MS-DFS: The Poor Man's Cluster</h3></div></div></div><p>
+<a class="indexterm" name="id2673239"></a>
+<a class="indexterm" name="id2673246"></a>
 	MS-DFS links can be used to redirect clients to disparate backend servers. This pushes
 	complexity back to the network client, something already included by Microsoft.
 	MS-DFS creates the illusion of a simple, continuous file system name space that works even
@@ -268,4 +268,4 @@ from other sources, but it was Jeremy who inspired the structure that follows.
 	</p><p>
 	Above all, at the cost of complexity of management, a distributed system (pseudo-cluster) can
 	be created using existing Samba functionality.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673123"></a>Conclusions</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Transparent SMB clustering is hard to do!</p></li><li><p>Client failover is the best we can do today.</p></li><li><p>Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible.</p></li><li><p>MS-DFS can be used to create the illusion of a single transparent cluster.</p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Backup.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="largefile.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�31.�Backup Techniques�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�33.�Handling Large Directories</td></tr></table></div></body></html>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673268"></a>Conclusions</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Transparent SMB clustering is hard to do!</p></li><li><p>Client failover is the best we can do today.</p></li><li><p>Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible.</p></li><li><p>MS-DFS can be used to create the illusion of a single transparent cluster.</p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Backup.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="largefile.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�31.�Backup Techniques�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�33.�Handling Large Directories</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/ServerType.html b/docs/htmldocs/Samba3-HOWTO/ServerType.html
index 464d9ed98a..d8e0624e74 100644
--- a/docs/htmldocs/Samba3-HOWTO/ServerType.html
+++ b/docs/htmldocs/Samba3-HOWTO/ServerType.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Server Types and Security Modes</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="next" href="samba-pdc.html" title="Chapter�4.�Domain Control"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Server Types and Security Modes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="type.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="samba-pdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter�3.�Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ServerType.html#id2558810">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558970">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559114">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559276">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559439">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560266">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560541">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560728">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560758">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560791">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560828">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560854">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560912">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2558771"></a>
-<a class="indexterm" name="id2558777"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Server Types and Security Modes</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="next" href="samba-pdc.html" title="Chapter�4.�Domain Control"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Server Types and Security Modes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="type.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="samba-pdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter�3.�Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ServerType.html#id2558805">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558964">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559109">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559271">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559434">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560264">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560539">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560726">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560756">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560788">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560825">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560852">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560910">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2558766"></a>
+<a class="indexterm" name="id2558772"></a>
 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 use Samba will want to know the meaning, within a
 Samba context, of terms familiar to the MS Windows administrator. This means that it is essential also to
@@ -14,7 +14,7 @@ A question often asked is, &#8220;<span class="quote">Why would I want to use Sa
 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 toward Samba. 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="id2558810"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558805"></a>Features and Benefits</h2></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 befitting his anguish. The other looked at the stone and said, &#8220;<span class="quote">This is a garnet.
@@ -25,8 +25,8 @@ Like it or not, Samba is like that stone. Treat it the right way and it can brin
 pleasure, but if you are forced to use it and have no time for its secrets, then it can be
 a source of discomfort.
 </p><p>
-<a class="indexterm" name="id2558839"></a>
-<a class="indexterm" name="id2558847"></a>
+<a class="indexterm" name="id2558833"></a>
+<a class="indexterm" name="id2558842"></a>
 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
@@ -34,41 +34,41 @@ like this one, we tell of both.
 </p><p>
 So, what are the benefits of the features mentioned in this chapter?
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2558870"></a>
+	<a class="indexterm" name="id2558864"></a>
 	Samba-3 can replace an MS Windows NT4 domain controller.
 	</p></li><li><p>
-	<a class="indexterm" name="id2558883"></a>
+	<a class="indexterm" name="id2558878"></a>
 	Samba-3 offers excellent interoperability with MS Windows NT4-style
 	domains as well as natively with Microsoft Active Directory domains.
 	</p></li><li><p>
-	<a class="indexterm" name="id2558896"></a>
+	<a class="indexterm" name="id2558891"></a>
 	Samba-3 permits full NT4-style interdomain trusts.
 	</p></li><li><p>
-	<a class="indexterm" name="id2558910"></a>
-	<a class="indexterm" name="id2558916"></a>
+	<a class="indexterm" name="id2558905"></a>
+	<a class="indexterm" name="id2558911"></a>
 	Samba has security modes that permit more flexible authentication
 	than is possible with MS Windows NT4 domain controllers.
 	</p></li><li><p>
-	<a class="indexterm" name="id2558931"></a>
-	<a class="indexterm" name="id2558942"></a>
+	<a class="indexterm" name="id2558926"></a>
+	<a class="indexterm" name="id2558937"></a>
 	Samba-3 permits use of multiple concurrent account database backends.
 	(Encrypted passwords that are stored in the account database are in
 	formats that are unique to Windows networking).
 	</p></li><li><p>
-	<a class="indexterm" name="id2558956"></a>
+	<a class="indexterm" name="id2558950"></a>
 	The account 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="id2558970"></a>Server Types</h2></div></div></div><p>
-<a class="indexterm" name="id2558977"></a>
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2558964"></a>Server Types</h2></div></div></div><p>
+<a class="indexterm" name="id2558972"></a>
 Administrators of Microsoft networks often refer to three different types 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 (PDC)</p></li><li><p>Backup Domain Controller (BDC)</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>Standalone Server</p></li></ul></div><p>
-<a class="indexterm" name="id2559037"></a>
-<a class="indexterm" name="id2559045"></a>
-<a class="indexterm" name="id2559054"></a>
-<a class="indexterm" name="id2559062"></a>
+<a class="indexterm" name="id2559031"></a>
+<a class="indexterm" name="id2559040"></a>
+<a class="indexterm" name="id2559048"></a>
+<a class="indexterm" name="id2559057"></a>
 The chapters covering domain control (<a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Domain Control</a>), 
 backup domain control (<a class="link" href="samba-bdc.html" title="Chapter�5.�Backup Domain Control">Backup Domain Control</a>), and 
 domain membership (<a class="link" href="domain-member.html" title="Chapter�6.�Domain Membership">Domain Membership</a>) provide
@@ -76,27 +76,27 @@ pertinent information regarding Samba configuration for each of these server rol
 You are strongly encouraged to become intimately familiar with these chapters because
 they lay the foundation for deployment of Samba domain security.
 </p><p>
-<a class="indexterm" name="id2559094"></a>
+<a class="indexterm" name="id2559089"></a>
 A Standalone server is autonomous in respect of the source of its account backend.
 Refer to <a class="link" href="StandAloneServer.html" title="Chapter�7.�Standalone Servers">Standalone Servers</a> to gain a wider appreciation
 of what is meant by a server being configured as a <span class="emphasis"><em>standalone</em></span> server.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559114"></a>Samba Security Modes</h2></div></div></div><p>
-<a class="indexterm" name="id2559122"></a>
-<a class="indexterm" name="id2559128"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2559109"></a>Samba Security Modes</h2></div></div></div><p>
+<a class="indexterm" name="id2559116"></a>
+<a class="indexterm" name="id2559123"></a>
 In this section, the function and purpose of Samba's security 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>
-<a class="indexterm" name="id2559142"></a>
-<a class="indexterm" name="id2559151"></a>
+<a class="indexterm" name="id2559137"></a>
+<a class="indexterm" name="id2559145"></a>
 Microsoft Windows networking uses a protocol that was originally called the Server Message Block (SMB)
 protocol. Since some time around 1996 the protocol has been better known as the Common Internet Filesystem
 (CIFS) protocol.
 </p><p>
-<a class="indexterm" name="id2559166"></a>
-<a class="indexterm" name="id2559173"></a>
-<a class="indexterm" name="id2559179"></a>
-<a class="indexterm" name="id2559185"></a>
+<a class="indexterm" name="id2559161"></a>
+<a class="indexterm" name="id2559167"></a>
+<a class="indexterm" name="id2559174"></a>
+<a class="indexterm" name="id2559180"></a>
 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 security levels, Samba provides flexibilities that are not available with MS Windows
@@ -116,43 +116,43 @@ available and whether an action is allowed.
 The term <code class="literal">client</code> refers to all agents whether it is a Windows workstation, a Windows server,
 another Samba server, or any vanilla SMB or CIFS client application (e.g., <code class="literal">smbclient</code>) that
 make use of services provided by an SMB/CIFS server.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559276"></a>User Level Security</h3></div></div></div><p>
-<a class="indexterm" name="id2559284"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559271"></a>User Level Security</h3></div></div></div><p>
+<a class="indexterm" name="id2559278"></a>
 We describe user-level security first because its simpler.  In user-level security, the client sends a session
 setup request directly following protocol negotiation.  This request provides a username and password. The
 server can either accept or reject that username/password combination. 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>
-<a class="indexterm" name="id2559320"></a>
+<a class="indexterm" name="id2559314"></a>
 If the server accepts the username/password credentials, the client expects to be able to mount shares (using
 a <span class="emphasis"><em>tree connection</em></span>) without further specifying a password. It expects that all access
 rights will be as the username/password credentials set that was specified in the initial <span class="emphasis"><em>session
 setup</em></span>.
 </p><p>
-<a class="indexterm" name="id2559340"></a>
+<a class="indexterm" name="id2559335"></a>
 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><p>
+<a class="indexterm" name="id2559356"></a>
 <a class="indexterm" name="id2559362"></a>
-<a class="indexterm" name="id2559368"></a>
-<a class="indexterm" name="id2559374"></a>
-<a class="indexterm" name="id2559380"></a>
-<a class="indexterm" name="id2559387"></a>
+<a class="indexterm" name="id2559369"></a>
+<a class="indexterm" name="id2559375"></a>
+<a class="indexterm" name="id2559381"></a>
 Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters
 in the account name are considered equivalent. They are said to be case-preserving, but not case significant.
 Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were
 not necessarily case-preserving. All Windows NT family systems treat passwords as case-preserving and
 case-sensitive.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559402"></a>Example Configuration</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559396"></a>Example Configuration</h4></div></div></div><p>
 The <code class="filename">smb.conf</code> parameter that sets user-level security is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559422"></a><em class="parameter"><code>security = user</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559417"></a><em class="parameter"><code>security = user</code></em></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="id2559439"></a>Share-Level Security</h3></div></div></div><p>
-<a class="indexterm" name="id2559447"></a>
-<a class="indexterm" name="id2559453"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559434"></a>Share-Level Security</h3></div></div></div><p>
+<a class="indexterm" name="id2559441"></a>
+<a class="indexterm" name="id2559448"></a>
 In share-level security, the client authenticates itself separately for each share. It sends a password along
 with each tree connection request (share mount), but 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
@@ -171,9 +171,9 @@ home directories) and any users listed in the <a class="link" href="smb.conf.5.h
 The password is then checked in turn against these possible usernames. If a match is found, then the client is
 authenticated as that user.
 </p><p>
-<a class="indexterm" name="id2559516"></a>
-<a class="indexterm" name="id2559524"></a>
-<a class="indexterm" name="id2559531"></a>
+<a class="indexterm" name="id2559514"></a>
+<a class="indexterm" name="id2559522"></a>
+<a class="indexterm" name="id2559528"></a>
 Where the list of possible user names is not provided, Samba makes a UNIX system call to find the user
 account that has a password that matches the one provided from the standard account database. On a system that
 has no name service switch (NSS) facility, such lookups will be from the <code class="filename">/etc/passwd</code>
@@ -184,21 +184,21 @@ passwd: files nis ldap
 shadow: files nis ldap
 group: files nis ldap
 </pre><p>
-<a class="indexterm" name="id2559562"></a>
-<a class="indexterm" name="id2559568"></a>
-<a class="indexterm" name="id2559575"></a>
+<a class="indexterm" name="id2559560"></a>
+<a class="indexterm" name="id2559566"></a>
+<a class="indexterm" name="id2559572"></a>
 In the example shown here (not likely to be used in practice) the lookup will check
 <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code>, if not found it will check NIS, then
 LDAP.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559595"></a>Example Configuration</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559593"></a>Example Configuration</h4></div></div></div><p>
 The <code class="filename">smb.conf</code> parameter that sets share-level security is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559616"></a><em class="parameter"><code>security = share</code></em></td></tr></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559628"></a>Domain Security Mode (User-Level Security)</h3></div></div></div><p>
-<a class="indexterm" name="id2559636"></a>
-<a class="indexterm" name="id2559644"></a>
-<a class="indexterm" name="id2559653"></a>
-<a class="indexterm" name="id2559659"></a>
-<a class="indexterm" name="id2559665"></a>
-<a class="indexterm" name="id2559671"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559614"></a><em class="parameter"><code>security = share</code></em></td></tr></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559626"></a>Domain Security Mode (User-Level Security)</h3></div></div></div><p>
+<a class="indexterm" name="id2559634"></a>
+<a class="indexterm" name="id2559642"></a>
+<a class="indexterm" name="id2559650"></a>
+<a class="indexterm" name="id2559657"></a>
+<a class="indexterm" name="id2559663"></a>
+<a class="indexterm" name="id2559669"></a>
 Domain security provides a mechanism for storing all user and group accounts in a central, shared, account
 repository. The centralized account repository is shared between domain (security) controllers. Servers that
 act as domain controllers provide authentication and validation services to all machines that participate in
@@ -207,21 +207,21 @@ maintaining the integrity of the security account database. Backup domain contro
 logon and authentication services. Usually, BDCs will answer network logon requests more responsively than
 will a PDC.
 </p><p>
-<a class="indexterm" name="id2559703"></a>
-<a class="indexterm" name="id2559709"></a>
-<a class="indexterm" name="id2559716"></a>
-<a class="indexterm" name="id2559724"></a>
-<a class="indexterm" name="id2559732"></a>
+<a class="indexterm" name="id2559701"></a>
+<a class="indexterm" name="id2559707"></a>
+<a class="indexterm" name="id2559713"></a>
+<a class="indexterm" name="id2559722"></a>
+<a class="indexterm" name="id2559730"></a>
 When Samba is operating in <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a> mode, the Samba server has a
 domain security trust account (a machine account) and causes all authentication requests to be passed through
 to the domain controllers.  In other words, this configuration makes the Samba server a domain member server,
 even when it is in fact acting as a domain controller. All machines that participate in domain security must
 have a machine account in the security database.
 </p><p>
-<a class="indexterm" name="id2559760"></a>
-<a class="indexterm" name="id2559769"></a>
-<a class="indexterm" name="id2559777"></a>
-<a class="indexterm" name="id2559786"></a>
+<a class="indexterm" name="id2559758"></a>
+<a class="indexterm" name="id2559766"></a>
+<a class="indexterm" name="id2559775"></a>
+<a class="indexterm" name="id2559783"></a>
 Within the domain security environment, the underlying security architecture uses user-level security. Even
 machines that are domain members must authenticate on startup. The machine account consists of an account
 entry in the accounts database, the name of which is the NetBIOS name of the machine and of which the password
@@ -231,30 +231,30 @@ it cannot be trusted. The machine account is referred to as a machine trust acco
 </p><p>
 There are three possible domain member configurations:
 </p><div class="orderedlist"><ol type="1"><li><p>Primary domain controller (PDC) - of which there is one per domain.</p></li><li><p>Backup domain controller (BDC) - of which there can be any number per domain.</p></li><li><p>Domain member server (DMS) - of which there can be any number per domain.</p></li></ol></div><p>
-<a class="indexterm" name="id2559834"></a>
+<a class="indexterm" name="id2559832"></a>
 We will discuss each of these in separate chapters. For now, we are most interested in basic DMS
 configuration.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559843"></a>Example Configuration</h4></div></div></div><p><span class="emphasis"><em>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559841"></a>Example Configuration</h4></div></div></div><p><span class="emphasis"><em>
 Samba as a Domain Member Server
 </em></span></p><p>
-<a class="indexterm" name="id2559855"></a>
+<a class="indexterm" name="id2559853"></a>
 This method involves addition of the following parameters in the <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559875"></a><em class="parameter"><code>security = domain</code></em></td></tr><tr><td><a class="indexterm" name="id2559885"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559873"></a><em class="parameter"><code>security = domain</code></em></td></tr><tr><td><a class="indexterm" name="id2559883"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
 </p><p>
 In order for this method to work, the Samba server needs to join the MS Windows NT
 security domain. This is done as follows:
-<a class="indexterm" name="id2559901"></a>
-<a class="indexterm" name="id2559910"></a>
+<a class="indexterm" name="id2559899"></a>
+<a class="indexterm" name="id2559907"></a>
 </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>On the UNIX/Linux system execute:</p><pre class="screen"><code class="prompt">root# </code><strong class="userinput"><code>net rpc join -U administrator%password</code></strong></pre></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2559956"></a>
+<a class="indexterm" name="id2559954"></a>
 Samba-2.2.4 and later Samba 2.2.x series releases can autojoin a Windows NT4-style domain just by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -j <em class="replaceable"><code>DOMAIN_NAME</code></em> -r <em class="replaceable"><code>PDC_NAME</code></em> \
 	 -U Administrator%<em class="replaceable"><code>password</code></em></code></strong>
 </pre><p>
-<a class="indexterm" name="id2559988"></a>
+<a class="indexterm" name="id2559985"></a>
 Samba-3 can do the same by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>net rpc join -U Administrator%<em class="replaceable"><code>password</code></em></code></strong>
@@ -262,26 +262,26 @@ Samba-3 can do the same by executing:
 It is not necessary with Samba-3 to specify the <em class="replaceable"><code>DOMAIN_NAME</code></em> or the
 <em class="replaceable"><code>PDC_NAME</code></em>, as it figures this out from the <code class="filename">smb.conf</code> file settings.
 </p></div><p>
-<a class="indexterm" name="id2560033"></a>
-<a class="indexterm" name="id2560039"></a>
-<a class="indexterm" name="id2560045"></a>
+<a class="indexterm" name="id2560030"></a>
+<a class="indexterm" name="id2560037"></a>
+<a class="indexterm" name="id2560043"></a>
 Use of this mode of authentication requires there to be a standard UNIX account for each user in order to
 assign a UID once the account has been authenticated by the Windows domain controller. This account can be
 blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in
 the <code class="filename">/etc/passwd</code> entry. The best way to allocate an invalid shell to a user account is to
 set the shell to the file <code class="filename">/bin/false</code>.
 </p><p>
-<a class="indexterm" name="id2560073"></a>
-<a class="indexterm" name="id2560079"></a>
+<a class="indexterm" name="id2560070"></a>
+<a class="indexterm" name="id2560077"></a>
 Domain controllers can be located anywhere that is convenient. The best advice is to have a BDC on every
 physical network segment, and if the PDC is on a remote network segment the use of WINS (see <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a> for more information) is almost essential.
 </p><p>
 An alternative to assigning UIDs to Windows users on a Samba member server is presented in <a class="link" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts">Winbind</a>, <a class="link" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>.
 </p><p>
 For more information regarding domain membership, <a class="link" href="domain-member.html" title="Chapter�6.�Domain Membership">Domain Membership</a>.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560123"></a>ADS Security Mode (User-Level Security)</h3></div></div></div><p>
-<a class="indexterm" name="id2560132"></a>
-<a class="indexterm" name="id2560138"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560121"></a>ADS Security Mode (User-Level Security)</h3></div></div></div><p>
+<a class="indexterm" name="id2560129"></a>
+<a class="indexterm" name="id2560136"></a>
 Both Samba-2.2, and Samba-3 can join an Active Directory domain using NT4 style RPC based security.  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.
@@ -292,24 +292,24 @@ your machines are running Windows 2000 and above and all use Kerberos. In this c
 domain, would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos
 tickets.
 </p><p>
-<a class="indexterm" name="id2560162"></a>
-<a class="indexterm" name="id2560169"></a>
+<a class="indexterm" name="id2560160"></a>
+<a class="indexterm" name="id2560166"></a>
 Sites that use Microsoft Windows active directory services (ADS) should be aware of the significance of the
 terms: <code class="literal">native mode</code> and <code class="literal">mixed mode</code> ADS operation. The term
 <code class="literal">realm</code> is used to describe a Kerberos-based security architecture (such as is used by
 Microsoft ADS).
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560196"></a>Example Configuration</h4></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560207"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2560218"></a><em class="parameter"><code>security = ADS</code></em></td></tr></table><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560193"></a>Example Configuration</h4></div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560205"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2560215"></a><em class="parameter"><code>security = ADS</code></em></td></tr></table><p>
 The following parameter may be required:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560238"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560236"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
 Please refer to <a class="link" href="domain-member.html" title="Chapter�6.�Domain Membership">Domain Membership</a>, and <a class="link" href="domain-member.html#ads-member" title="Samba ADS Domain Membership">Samba
 ADS 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="id2560266"></a>Server Security (User Level Security)</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560264"></a>Server Security (User Level Security)</h3></div></div></div><p>
 Server security mode is 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 drawbacks that 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, which is 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>
-<a class="indexterm" name="id2560320"></a>
-<a class="indexterm" name="id2560326"></a>
+<a class="indexterm" name="id2560317"></a>
+<a class="indexterm" name="id2560324"></a>
 In server security mode the Samba server reports to the client that it is in user-level security. The client
 then does a session setup as described earlier.  The Samba server takes the username/password that the client
 sends and attempts to log into the <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> by sending exactly the same
@@ -317,8 +317,8 @@ username/password that it got from the client. If that server is in user-level s
 password, then Samba accepts the client's connection. This parameter allows the Samba server to use another
 SMB server as the <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a>.
 </p><p>
-<a class="indexterm" name="id2560362"></a>
-<a class="indexterm" name="id2560368"></a>
+<a class="indexterm" name="id2560360"></a>
+<a class="indexterm" name="id2560366"></a>
 You should also note that at the start of all this, when the server tells the client
 what security level it is in, it also tells the client if it supports encryption. If it
 does, it supplies the client with a random cryptkey. The client will then send all
@@ -330,24 +330,24 @@ user mode server. This requires an additional parameter <a class="link" href="sm
 the real authentication server.  The real authentication server can be another Samba server, or it can be a
 Windows NT server, the latter being 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>
-<a class="indexterm" name="id2560414"></a>
-<a class="indexterm" name="id2560420"></a>
+<a class="indexterm" name="id2560412"></a>
+<a class="indexterm" name="id2560418"></a>
 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 cannot determine this from NetBIOS name lookups because the choice of the target authentication
 server is arbitrary and cannot 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="id2560443"></a>Example Configuration</h4></div></div></div><p><span class="emphasis"><em>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560441"></a>Example Configuration</h4></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 <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560470"></a><em class="parameter"><code>encrypt passwords = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560480"></a><em class="parameter"><code>security = server</code></em></td></tr><tr><td><a class="indexterm" name="id2560491"></a><em class="parameter"><code>password server = "NetBIOS_name_of_a_DC"</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560468"></a><em class="parameter"><code>encrypt passwords = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560478"></a><em class="parameter"><code>security = server</code></em></td></tr><tr><td><a class="indexterm" name="id2560488"></a><em class="parameter"><code>password server = "NetBIOS_name_of_a_DC"</code></em></td></tr></table><p>
 There are two ways of identifying whether or not a username and password pair is valid.
 One uses the reply information provided as part of the authentication messaging
 process, the other uses just an error code.
 </p><p>
-<a class="indexterm" name="id2560511"></a>
-<a class="indexterm" name="id2560517"></a>
+<a class="indexterm" name="id2560509"></a>
+<a class="indexterm" name="id2560515"></a>
 The downside of this mode of configuration is 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 bogus username and password pair, then an alternative mode of
@@ -356,15 +356,15 @@ certain number of failed authentication attempts, this will result in user locko
 </p><p>
 Use of this mode of authentication requires a standard UNIX account for the user.
 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="id2560541"></a>Password Checking</h2></div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560539"></a>Password Checking</h2></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 plaintext or encrypted, but
 not both in the same authentication request.
 </p><p>
-<a class="indexterm" name="id2560558"></a>
-<a class="indexterm" name="id2560564"></a>
+<a class="indexterm" name="id2560556"></a>
+<a class="indexterm" name="id2560562"></a>
 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
@@ -375,12 +375,12 @@ is encrypted in two ways:
         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>
-<a class="indexterm" name="id2560594"></a>
+<a class="indexterm" name="id2560592"></a>
 MS Windows 95 pre-service pack 1 and 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>
-<a class="indexterm" name="id2560610"></a>
+<a class="indexterm" name="id2560608"></a>
 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
@@ -396,13 +396,13 @@ a good idea to re-enable plaintext password support in such clients.
 The following parameters can be used to work around the issue of Windows 9x/Me clients
 uppercasing usernames and passwords before transmitting them to the SMB server
 when using clear-text authentication:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560650"></a></td></tr><tr><td><a class="indexterm" name="id2560656"></a></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560648"></a></td></tr><tr><td><a class="indexterm" name="id2560654"></a></td></tr></table><p>
 By default Samba will convert to lowercase the username before attempting to lookup the user
 in the database of local system accounts. Because UNIX usernames conventionally
 only contain lowercase characters, the <a class="link" href="smb.conf.5.html#USERNAME-LEVEL" target="_top">username-level</a> parameter
 is rarely needed.
 </p><p>
-<a class="indexterm" name="id2560681"></a>
+<a class="indexterm" name="id2560679"></a>
 However, passwords on UNIX systems often make use of mixed-case characters.  This means that in order for a
 user on a Windows 9x/Me client to connect to a Samba server using clear-text authentication, the
 <a class="link" href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> must be set to the maximum number of uppercase letters that
@@ -414,7 +414,7 @@ of the password string and try them one by one until a match is located (or all
 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 plaintext
 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="id2560728"></a>Common Errors</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2560726"></a>Common Errors</h2></div></div></div><p>
 We all make mistakes. It is okay to make mistakes, as long as they are made in the right places
 and at the right time. A mistake that causes lost productivity is seldom tolerated; however, a mistake
 made in a developmental test lab is expected.
@@ -424,7 +424,7 @@ on the Samba mailing lists. Many of these are avoidable by doing your homework b
 a Samba implementation. Some are the result of a misunderstanding of the English language,
 which has many phrases 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="id2560758"></a>What Makes Samba a Server?</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560756"></a>What Makes Samba a Server?</h3></div></div></div><p>
 To some, the nature of the Samba security mode is obvious, but entirely
 wrong all the same. It is assumed that <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a> means that Samba
 will act as a server. Not so! This setting means that Samba will <span class="emphasis"><em>try</em></span>
@@ -433,15 +433,15 @@ to use another SMB server as its source for user authentication alone.
 Samba is a server regardless of which security mode is chosen. When Samba is used outside of a domain security
 context, it is best to leave the security mode at the default setting. By default Samba-3 uses user-mode
 security.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560791"></a>What Makes Samba a Domain Controller?</h3></div></div></div><p>
-<a class="indexterm" name="id2560798"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560788"></a>What Makes Samba a Domain Controller?</h3></div></div></div><p>
+<a class="indexterm" name="id2560796"></a>
 The <code class="filename">smb.conf</code> parameter <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a> does not really make Samba behave
 as a domain controller. This setting means we want Samba to be a domain member. See <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Samba as a PDC</a> for more information.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560828"></a>What Makes Samba a Domain Member?</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560825"></a>What Makes Samba a Domain Member?</h3></div></div></div><p>
 Guess! So many others do. But whatever you do, do not think that <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>
 makes Samba act as a domain member. Read the manufacturer's manual before the warranty expires. See 
 <a class="link" href="domain-member.html" title="Chapter�6.�Domain Membership">Domain Membership</a>, for more information.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560854"></a>Constantly Losing Connections to Password Server</h3></div></div></div><p>&#8220;<span class="quote">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560852"></a>Constantly Losing Connections to Password Server</h3></div></div></div><p>&#8220;<span class="quote">
 Why does server_validate() simply give up rather than re-establish 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
@@ -451,7 +451,7 @@ connection whose session key would be different. So server_validate() must give
 Indeed. That's why <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>
 is at best a nasty hack. Please use <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>;
 <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a> mode is also known as pass-through authentication.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560912"></a>Stand-alone Server is converted to Domain Controller  Now User accounts don't work</h3></div></div></div><p>&#8220;<span class="quote">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560910"></a>Stand-alone Server is converted to Domain Controller  Now User accounts don't work</h3></div></div></div><p>&#8220;<span class="quote">
 When I try to log in to the DOMAIN, the eventlog shows <span class="emphasis"><em>tried credentials DOMAIN/username; effective
 credentials SERVER/username</em></span>
 </span>&#8221;</p><p>
diff --git a/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html b/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html
index 3481d4eb43..143e830a9a 100644
--- a/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html
+++ b/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html
@@ -1,49 +1,49 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�7.�Standalone Servers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="domain-member.html" title="Chapter�6.�Domain Membership"><link rel="next" href="ClientConfig.html" title="Chapter�8.�MS Windows Network Configuration Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�7.�Standalone Servers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="domain-member.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="ClientConfig.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter�7.�Standalone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574171">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574265">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574457">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575441">Common Errors</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2574144"></a>
-<a class="indexterm" name="id2574150"></a>
-<a class="indexterm" name="id2574157"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�7.�Standalone Servers</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="domain-member.html" title="Chapter�6.�Domain Membership"><link rel="next" href="ClientConfig.html" title="Chapter�8.�MS Windows Network Configuration Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�7.�Standalone Servers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="domain-member.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="ClientConfig.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter�7.�Standalone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574148">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574242">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574443">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575426">Common Errors</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2574121"></a>
+<a class="indexterm" name="id2574128"></a>
+<a class="indexterm" name="id2574135"></a>
 Standalone servers are independent of domain controllers on the network.
 They are not domain members and function more like workgroup servers. In many
 cases a standalone 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="id2574171"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2574179"></a>
-<a class="indexterm" name="id2574186"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2574148"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2574156"></a>
+<a class="indexterm" name="id2574163"></a>
 Standalone 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 common installation.
 </p><p>
-<a class="indexterm" name="id2574199"></a>
-<a class="indexterm" name="id2574206"></a>
-<a class="indexterm" name="id2574213"></a>
-<a class="indexterm" name="id2574220"></a>
+<a class="indexterm" name="id2574176"></a>
+<a class="indexterm" name="id2574183"></a>
+<a class="indexterm" name="id2574190"></a>
+<a class="indexterm" name="id2574197"></a>
 If all that is needed is a server for read-only files, or for
 printers alone, it may not make sense to effect a complex installation.
 For example, a drafting office needs to store old drawings and reference
-standards. Nobody can write files to the server because it is legislatively
+standards. Noone can write files to the server because it is legislatively
 important that all documents remain unaltered. A share-mode read-only standalone
 server is an ideal solution.
 </p><p>
-<a class="indexterm" name="id2574236"></a>
-<a class="indexterm" name="id2574243"></a>
-<a class="indexterm" name="id2574250"></a>
+<a class="indexterm" name="id2574214"></a>
+<a class="indexterm" name="id2574221"></a>
+<a class="indexterm" name="id2574227"></a>
 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 effect any access controls, and no files will
 be served from the print server. Again, a share-mode standalone 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="id2574265"></a>Background</h2></div></div></div><p>
-<a class="indexterm" name="id2574273"></a>
-<a class="indexterm" name="id2574280"></a>
-<a class="indexterm" name="id2574287"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2574242"></a>Background</h2></div></div></div><p>
+<a class="indexterm" name="id2574250"></a>
+<a class="indexterm" name="id2574257"></a>
+<a class="indexterm" name="id2574264"></a>
 The term <span class="emphasis"><em>standalone server</em></span> means that it 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 resources on the machine will be made available in either
 <span class="emphasis"><em>share</em></span> mode or in <span class="emphasis"><em>user</em></span> mode.
 </p><p>
-<a class="indexterm" name="id2574313"></a>
-<a class="indexterm" name="id2574320"></a>
-<a class="indexterm" name="id2574327"></a>
+<a class="indexterm" name="id2574290"></a>
+<a class="indexterm" name="id2574297"></a>
+<a class="indexterm" name="id2574304"></a>
 No special action is needed other than to create user accounts. Standalone
 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
@@ -52,51 +52,51 @@ necessary to accommodate any network user so the logon name he or she uses will
 be translated (mapped) locally on the standalone server to a locally known
 user name. There are several ways this can be done.
 </p><p>
-<a class="indexterm" name="id2574346"></a>
-<a class="indexterm" name="id2574353"></a>
-<a class="indexterm" name="id2574359"></a>
+<a class="indexterm" name="id2574332"></a>
+<a class="indexterm" name="id2574339"></a>
+<a class="indexterm" name="id2574345"></a>
 Samba tends to blur the distinction a little in defining
 a standalone server. This is because the authentication database may be
 local or on a remote server, even if from the SMB protocol perspective
 the Samba server is not a member of a domain security context.
 </p><p>
+<a class="indexterm" name="id2574360"></a>
+<a class="indexterm" name="id2574367"></a>
 <a class="indexterm" name="id2574373"></a>
 <a class="indexterm" name="id2574380"></a>
-<a class="indexterm" name="id2574386"></a>
-<a class="indexterm" name="id2574393"></a>
-<a class="indexterm" name="id2574400"></a>
-<a class="indexterm" name="id2574407"></a>
-<a class="indexterm" name="id2574414"></a>
-<a class="indexterm" name="id2574421"></a>
+<a class="indexterm" name="id2574387"></a>
+<a class="indexterm" name="id2574394"></a>
+<a class="indexterm" name="id2574401"></a>
+<a class="indexterm" name="id2574408"></a>
 Through the use of Pluggable Authentication Modules (PAM) (see <a class="link" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication">the chapter on PAM</a>)
 and the name service switcher (NSS), 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 (<code class="filename">/etc/passwd</code> or
 <code class="filename">/etc/shadow</code>), may use a local smbpasswd file, or may use an LDAP backend, 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="id2574457"></a>Example Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2574465"></a>
-<a class="indexterm" name="id2574472"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2574443"></a>Example Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2574451"></a>
+<a class="indexterm" name="id2574458"></a>
 <a class="link" href="StandAloneServer.html#simplynice" title="Example�7.1.�smb.conf for Reference Documentation Server">The example Reference Documentation Server</a> and <a class="link" href="StandAloneServer.html#SimplePrintServer" title="Central Print Serving">Central Print Serving</a> 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><p>
+<a class="indexterm" name="id2574495"></a>
+<a class="indexterm" name="id2574502"></a>
 <a class="indexterm" name="id2574509"></a>
-<a class="indexterm" name="id2574516"></a>
-<a class="indexterm" name="id2574523"></a>
-<a class="indexterm" name="id2574530"></a>
+<a class="indexterm" name="id2574515"></a>
 Configuration of a read-only data server that everyone can access is very simple. By default, all shares are
 read-only, unless set otherwise in the <code class="filename">smb.conf</code> file. <a class="link" href="StandAloneServer.html#simplynice" title="Example�7.1.�smb.conf for Reference Documentation Server">The example - Reference
 Documentation Server</a> is the <code class="filename">smb.conf</code> file that will do this. Assume that all the reference documents
 are stored in the directory <code class="filename">/export</code>, and the documents are owned by a user other than
 nobody. No home directories are shared, and there are no users in the <code class="filename">/etc/passwd</code> UNIX
 system database. This is a simple system to administer.
-</p><div class="example"><a name="simplynice"></a><p class="title"><b>Example�7.1.�smb.conf for Reference Documentation Server</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2574603"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2574615"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2574627"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2574638"></a><em class="parameter"><code>passdb backend = guest</code></em></td></tr><tr><td><a class="indexterm" name="id2574650"></a><em class="parameter"><code>wins server = 192.168.1.1</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2574671"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2574683"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2574694"></a><em class="parameter"><code>guest only = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="blockquote"><table border="0" width="100%" cellspacing="0" cellpadding="0" class="blockquote" summary="Block quote"><tr><td width="10%" valign="top">�</td><td width="80%" valign="top"><p>
+</p><div class="example"><a name="simplynice"></a><p class="title"><b>Example�7.1.�smb.conf for Reference Documentation Server</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2574589"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2574601"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2574613"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2574624"></a><em class="parameter"><code>passdb backend = guest</code></em></td></tr><tr><td><a class="indexterm" name="id2574636"></a><em class="parameter"><code>wins server = 192.168.1.1</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[data]</code></em></td></tr><tr><td><a class="indexterm" name="id2574657"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2574668"></a><em class="parameter"><code>path = /export</code></em></td></tr><tr><td><a class="indexterm" name="id2574680"></a><em class="parameter"><code>guest only = Yes</code></em></td></tr></table></div></div><br class="example-break"><div class="blockquote"><table border="0" width="100%" cellspacing="0" cellpadding="0" class="blockquote" summary="Block quote"><tr><td width="10%" valign="top">�</td><td width="80%" valign="top"><p>
 I would have spoken more briefly, if I'd had more time to prepare.
 </p></td><td width="10%" valign="top">�</td></tr><tr><td width="10%" valign="top">�</td><td colspan="2" align="right" valign="top">--<span class="attribution">Mark Twain</span></td></tr></table></div><p>
+<a class="indexterm" name="id2574706"></a>
+<a class="indexterm" name="id2574713"></a>
 <a class="indexterm" name="id2574720"></a>
 <a class="indexterm" name="id2574727"></a>
-<a class="indexterm" name="id2574734"></a>
-<a class="indexterm" name="id2574741"></a>
 In <a class="link" href="StandAloneServer.html#simplynice" title="Example�7.1.�smb.conf for Reference Documentation Server">this example</a>, the machine name is set to GANDALF, and the
 workgroup is set to the name of the local workgroup (MIDEARTH) so the machine will appear together
 with systems with which users are familiar. The only password backend required is the &#8220;<span class="quote">guest</span>&#8221;
@@ -107,8 +107,8 @@ A US Air Force Colonel was renowned for saying: &#8220;<span class="quote">Bette
 sound reasons for avoiding complexity as well as for avoiding a technically perfect solution. Unfortunately,
 many network administrators still need to learn the art of doing just enough to keep out of trouble.
 </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><p>
-<a class="indexterm" name="id2574790"></a>
-<a class="indexterm" name="id2574797"></a>
+<a class="indexterm" name="id2574776"></a>
+<a class="indexterm" name="id2574783"></a>
 Configuration of a simple print server is easy 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.
@@ -122,17 +122,17 @@ Configuration of a simple print server is easy if you have all the right tools o
 	All workstations will use only PostScript drivers. The printer driver
 	of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.
 	</p></li></ol></div><p>
-<a class="indexterm" name="id2574854"></a>
-<a class="indexterm" name="id2574860"></a>
-<a class="indexterm" name="id2574867"></a>
+<a class="indexterm" name="id2574839"></a>
+<a class="indexterm" name="id2574846"></a>
+<a class="indexterm" name="id2574853"></a>
 In this example our print server will spool all incoming print jobs to
 <code class="filename">/var/spool/samba</code> 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 to enable anonymous printing.
 </p><div class="itemizedlist"><p class="title"><b>Enabling Anonymous Printing</b></p><ul type="disc"><li><p>
-<a class="indexterm" name="id2574895"></a>
-<a class="indexterm" name="id2574902"></a>
-<a class="indexterm" name="id2574908"></a>
+<a class="indexterm" name="id2574881"></a>
+<a class="indexterm" name="id2574888"></a>
+<a class="indexterm" name="id2574894"></a>
 	The UNIX/Linux system must have a <code class="literal">guest</code> account.
 	The default for this is usually the account <code class="literal">nobody</code>.
 	To find the correct name to use for your version of Samba, do the 
@@ -140,13 +140,13 @@ the anonymous (guest) user, two things will be required to enable anonymous prin
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>testparm -s -v | grep "guest account"</code></strong>
 </pre><p>
-<a class="indexterm" name="id2574946"></a>
+<a class="indexterm" name="id2574932"></a>
 	Make sure that this account exists in your system password
 	database (<code class="filename">/etc/passwd</code>).
 	</p><p>
-<a class="indexterm" name="id2574964"></a>
-<a class="indexterm" name="id2574971"></a>
-<a class="indexterm" name="id2574978"></a>
+<a class="indexterm" name="id2574950"></a>
+<a class="indexterm" name="id2574956"></a>
+<a class="indexterm" name="id2574963"></a>
 	It is a good idea either to set a password on this account, or else to lock it
 	from UNIX use. Assuming that the guest account is called <code class="literal">pcguest</code>,
 	it can be locked by executing:
@@ -155,12 +155,12 @@ the anonymous (guest) user, two things will be required to enable anonymous prin
 </pre><p>
 	The exact command may vary depending on your UNIX/Linux distribution.
 	</p></li><li><p>
+<a class="indexterm" name="id2574996"></a>
+<a class="indexterm" name="id2575003"></a>
 <a class="indexterm" name="id2575010"></a>
 <a class="indexterm" name="id2575017"></a>
 <a class="indexterm" name="id2575024"></a>
-<a class="indexterm" name="id2575031"></a>
-<a class="indexterm" name="id2575038"></a>
-<a class="indexterm" name="id2575045"></a>
+<a class="indexterm" name="id2575030"></a>
 	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:
@@ -171,31 +171,31 @@ the anonymous (guest) user, two things will be required to enable anonymous prin
 </pre><p>
 	</p></li></ul></div><p>
 The contents of the <code class="filename">smb.conf</code> file is shown in <a class="link" href="StandAloneServer.html#AnonPtrSvr" title="Example�7.2.�smb.conf for Anonymous Printing">the Anonymous Printing example</a>.
-</p><div class="example"><a name="AnonPtrSvr"></a><p class="title"><b>Example�7.2.�<code class="filename">smb.conf</code> for Anonymous Printing</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2575144"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2575156"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2575168"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2575179"></a><em class="parameter"><code>passdb backend = guest</code></em></td></tr><tr><td><a class="indexterm" name="id2575191"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2575203"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2575224"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2575235"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2575247"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2575259"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575271"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575282"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575294"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2575310"></a>
+</p><div class="example"><a name="AnonPtrSvr"></a><p class="title"><b>Example�7.2.�<code class="filename">smb.conf</code> for Anonymous Printing</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2575130"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2575142"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2575154"></a><em class="parameter"><code>security = SHARE</code></em></td></tr><tr><td><a class="indexterm" name="id2575165"></a><em class="parameter"><code>passdb backend = guest</code></em></td></tr><tr><td><a class="indexterm" name="id2575177"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2575189"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2575210"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2575221"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2575233"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td><a class="indexterm" name="id2575245"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575256"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575268"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2575280"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+<a class="indexterm" name="id2575296"></a>
+<a class="indexterm" name="id2575305"></a>
+<a class="indexterm" name="id2575312"></a>
 <a class="indexterm" name="id2575319"></a>
 <a class="indexterm" name="id2575326"></a>
-<a class="indexterm" name="id2575333"></a>
-<a class="indexterm" name="id2575340"></a>
 On CUPS-enabled systems there is a facility to pass raw data directly to the printer without intermediate
 processing via CUPS print filters. Where use of this mode of operation is desired, it is necessary to
 configure a raw printing device. It is also necessary to enable the raw mime handler in the
 <code class="filename">/etc/mime.conv</code> and <code class="filename">/etc/mime.types</code> files. Refer to <a class="link" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support">CUPS Printing Support</a>, <a class="link" href="CUPS-printing.html#cups-raw" title="Explicitly Enable raw Printing for application/octet-stream">Explicitly Enable raw Printing
 for application/octet-stream</a>.
 </p></div><p>
+<a class="indexterm" name="id2575368"></a>
+<a class="indexterm" name="id2575375"></a>
 <a class="indexterm" name="id2575382"></a>
 <a class="indexterm" name="id2575389"></a>
-<a class="indexterm" name="id2575396"></a>
-<a class="indexterm" name="id2575403"></a>
 The example in <a class="link" href="StandAloneServer.html#AnonPtrSvr" title="Example�7.2.�smb.conf for Anonymous Printing">the Anonymous Printing example</a> uses CUPS for direct printing
 via the CUPS libarary API. This means that all printers will be exposed to Windows users without need to
 configure a printcap file. If there is necessity to expose only a sub-set of printers, or to define a special
 type of printer (for example, a PDF filter) the <em class="parameter"><code>printcap name = cups</code></em> can be replaced
 with the entry <em class="parameter"><code>printcap name = /etc/samba/myprintcap</code></em>. In this case the file specified
 should contain a list of the printer names that should be exposed to Windows network users.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575441"></a>Common Errors</h2></div></div></div><p>
-<a class="indexterm" name="id2575448"></a>
-<a class="indexterm" name="id2575455"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575426"></a>Common Errors</h2></div></div></div><p>
+<a class="indexterm" name="id2575434"></a>
+<a class="indexterm" name="id2575441"></a>
 The greatest mistake so often made is to make a network configuration too complex.
 It pays to use the simplest solution that will meet the needs of the moment.
 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="domain-member.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="ClientConfig.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�6.�Domain Membership�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�8.�MS Windows Network Configuration Guide</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html b/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html
index 5fc2f25521..d7d35c2f40 100644
--- a/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html
+++ b/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="pr03.html" title="Foreword"><link rel="next" href="IntroSMB.html" title="Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr03.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="IntroSMB.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="TOSHpreface"></a>Preface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="TOSHpreface.html#id2551173">Conventions Used</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="pr03.html" title="Foreword"><link rel="next" href="IntroSMB.html" title="Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Preface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr03.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="IntroSMB.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="TOSHpreface"></a>Preface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="TOSHpreface.html#id2551169">Conventions Used</a></span></dt></dl></div><p>
 The editors wish to thank you for your decision to purchase this book.
 The Official Samba-3 HOWTO and Reference Guide is the result of many years
 of accumulation of information, feedback, tips, hints, and happy solutions.
@@ -28,7 +28,7 @@ to any one of the following:
 We wish to advise that only original and unencumbered material can be published. Please do not submit
 content that is not your own work unless proof of consent from the copyright holder accompanies your
 submission.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551173"></a>Conventions Used</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551169"></a>Conventions Used</h2></div></div></div><p>
     The following notation conventions are used throughout this book:
     </p><div class="itemizedlist"><ul type="disc"><li><p>
 	TOSHARG2 is used as an abbreviation for the book, &#8220;<span class="quote">The Official Samba-3
diff --git a/docs/htmldocs/Samba3-HOWTO/VFS.html b/docs/htmldocs/Samba3-HOWTO/VFS.html
index a525230131..ddadb34744 100644
--- a/docs/htmldocs/Samba3-HOWTO/VFS.html
+++ b/docs/htmldocs/Samba3-HOWTO/VFS.html
@@ -1,51 +1,51 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�23.�Stackable VFS modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support"><link rel="next" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�23.�Stackable VFS modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="winbind.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter�23.�Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="orgname">Samba Team</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tpot@samba.org">tpot@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Simo</span> <span class="surname">Sorce</span></h3><span class="contrib">original vfs_skel README</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><span class="contrib">original vfs_netatalk docs</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><span class="contrib">Update for multiple modules</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Ed</span> <span class="surname">Riddle</span></h3><span class="contrib">original shadow_copy docs</span>�</div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="VFS.html#id2650223">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650261">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650657">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650662">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650703">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650921">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651247">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651644">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651694">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652604">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652629">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652689">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652728">vscan-clamav</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650223"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2650231"></a>
-<a class="indexterm" name="id2650240"></a>
-<a class="indexterm" name="id2650247"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�23.�Stackable VFS modules</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support"><link rel="next" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�23.�Stackable VFS modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="winbind.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter�23.�Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="orgname">Samba Team</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tpot@samba.org">tpot@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Simo</span> <span class="surname">Sorce</span></h3><span class="contrib">original vfs_skel README</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><span class="contrib">original vfs_netatalk docs</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><span class="contrib">Update for multiple modules</span>�</div></div><div><div class="author"><h3 class="author"><span class="firstname">Ed</span> <span class="surname">Riddle</span></h3><span class="contrib">original shadow_copy docs</span>�</div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="VFS.html#id2650363">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650401">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650796">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650802">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650843">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651060">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651387">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651783">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651833">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652736">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652762">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652821">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652861">vscan-clamav</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650363"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2650371"></a>
+<a class="indexterm" name="id2650380"></a>
+<a class="indexterm" name="id2650387"></a>
 Stackable VFS (Virtual File System) modules support was new to Samba-3 and has proven quite popular. Samba
 passes each request to access the UNIX file system through the loaded VFS modules. This chapter covers the
 modules that come with the Samba source and provides references to some external modules.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650261"></a>Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2650269"></a>
-<a class="indexterm" name="id2650276"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650401"></a>Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2650409"></a>
+<a class="indexterm" name="id2650416"></a>
 If not supplied with your platform distribution binary Samba package, you may have problems compiling these
 modules, as shared libraries are compiled and linked in different ways on different systems. They currently
 have been tested against GNU/Linux and IRIX.
 </p><p>
-<a class="indexterm" name="id2650290"></a>
-<a class="indexterm" name="id2650297"></a>
-<a class="indexterm" name="id2650304"></a>
+<a class="indexterm" name="id2650430"></a>
+<a class="indexterm" name="id2650437"></a>
+<a class="indexterm" name="id2650444"></a>
 To use the VFS modules, create a share similar to the one below. The important parameter is the <a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects</a> parameter where you can list one or more VFS modules by name. For example, to log all
 access to files and put deleted files in a recycle bin, see <a class="link" href="VFS.html#vfsrecyc" title="Example�23.1.�smb.conf with VFS modules">the smb.conf with VFS
 modules example</a>:
-</p><div class="example"><a name="vfsrecyc"></a><p class="title"><b>Example�23.1.�smb.conf with VFS modules</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[audit]</code></em></td></tr><tr><td><a class="indexterm" name="id2650359"></a><em class="parameter"><code>comment = Audited /data directory</code></em></td></tr><tr><td><a class="indexterm" name="id2650371"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2650383"></a><em class="parameter"><code>vfs objects = audit recycle</code></em></td></tr><tr><td><a class="indexterm" name="id2650394"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650406"></a><em class="parameter"><code>browseable = yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2650421"></a>
-<a class="indexterm" name="id2650428"></a>
-<a class="indexterm" name="id2650435"></a>
+</p><div class="example"><a name="vfsrecyc"></a><p class="title"><b>Example�23.1.�smb.conf with VFS modules</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[audit]</code></em></td></tr><tr><td><a class="indexterm" name="id2650499"></a><em class="parameter"><code>comment = Audited /data directory</code></em></td></tr><tr><td><a class="indexterm" name="id2650511"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2650522"></a><em class="parameter"><code>vfs objects = audit recycle</code></em></td></tr><tr><td><a class="indexterm" name="id2650534"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650546"></a><em class="parameter"><code>browseable = yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2650561"></a>
+<a class="indexterm" name="id2650568"></a>
+<a class="indexterm" name="id2650574"></a>
 The modules are used in the order in which they are specified.  Let's say that you want to both have a virus
 scanner module and a recycle bin module. It is wise to put the virus scanner module as the first one so that
 it is the first to get run and may detect a virus immediately, before any action is performed on that file.
 <a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = vscan-clamav recycle</a>
 </p><p>
-<a class="indexterm" name="id2650463"></a>
-<a class="indexterm" name="id2650470"></a>
+<a class="indexterm" name="id2650602"></a>
+<a class="indexterm" name="id2650609"></a>
 Samba will attempt to load modules from the <code class="filename">/lib</code> directory in the root directory of the
 Samba installation (usually <code class="filename">/usr/lib/samba/vfs</code> or
 <code class="filename">/usr/local/samba/lib/vfs</code>).
 </p><p>
-<a class="indexterm" name="id2650500"></a>
-<a class="indexterm" name="id2650506"></a>
-<a class="indexterm" name="id2650513"></a>
-<a class="indexterm" name="id2650520"></a>
+<a class="indexterm" name="id2650639"></a>
+<a class="indexterm" name="id2650646"></a>
+<a class="indexterm" name="id2650653"></a>
+<a class="indexterm" name="id2650660"></a>
 Some modules can be used twice for the same share.  This can be done using a configuration similar to the one
 shown in <a class="link" href="VFS.html#multimodule" title="Example�23.2.�smb.conf with multiple VFS modules">the smb.conf with multiple VFS modules</a>.
 
-</p><div class="example"><a name="multimodule"></a><p class="title"><b>Example�23.2.�smb.conf with multiple VFS modules</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[test]</code></em></td></tr><tr><td><a class="indexterm" name="id2650559"></a><em class="parameter"><code>comment = VFS TEST</code></em></td></tr><tr><td><a class="indexterm" name="id2650571"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2650582"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650594"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650606"></a><em class="parameter"><code>vfs objects = example:example1 example example:test</code></em></td></tr><tr><td><a class="indexterm" name="id2650618"></a><em class="parameter"><code>example1: parameter = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2650630"></a><em class="parameter"><code>example:  parameter = 5</code></em></td></tr><tr><td><a class="indexterm" name="id2650642"></a><em class="parameter"><code>test:     parameter = 7</code></em></td></tr></table></div></div><p><br class="example-break">
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650657"></a>Included Modules</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650662"></a>audit</h3></div></div></div><p>
-<a class="indexterm" name="id2650670"></a>
+</p><div class="example"><a name="multimodule"></a><p class="title"><b>Example�23.2.�smb.conf with multiple VFS modules</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[test]</code></em></td></tr><tr><td><a class="indexterm" name="id2650699"></a><em class="parameter"><code>comment = VFS TEST</code></em></td></tr><tr><td><a class="indexterm" name="id2650711"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2650722"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650734"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2650745"></a><em class="parameter"><code>vfs objects = example:example1 example example:test</code></em></td></tr><tr><td><a class="indexterm" name="id2650758"></a><em class="parameter"><code>example1: parameter = 1</code></em></td></tr><tr><td><a class="indexterm" name="id2650769"></a><em class="parameter"><code>example:  parameter = 5</code></em></td></tr><tr><td><a class="indexterm" name="id2650781"></a><em class="parameter"><code>test:     parameter = 7</code></em></td></tr></table></div></div><p><br class="example-break">
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650796"></a>Included Modules</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650802"></a>audit</h3></div></div></div><p>
+<a class="indexterm" name="id2650810"></a>
 		A simple module to audit file access to the syslog facility. The following operations are logged:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>share</p></li><li><p>connect/disconnect</p></li><li><p>directory opens/create/remove</p></li><li><p>file open/close/rename/unlink/chmod</p></li></ul></div><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650703"></a>default_quota</h3></div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650843"></a>default_quota</h3></div></div></div><p>
 	This module allows the default quota values, in the windows explorer GUI, to be stored on a Samba-3 server.
 	The challenge is that linux filesystems only store quotas for users and groups, but no default quotas.
 	</p><p>
@@ -117,17 +117,17 @@ quotasettings:	gid = 65534
 quotasettings:	gid nolimit = no
 ...
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650921"></a>extd_audit</h3></div></div></div><p>
-<a class="indexterm" name="id2650928"></a>
-<a class="indexterm" name="id2650935"></a>
-<a class="indexterm" name="id2650942"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651060"></a>extd_audit</h3></div></div></div><p>
+<a class="indexterm" name="id2651068"></a>
+<a class="indexterm" name="id2651075"></a>
+<a class="indexterm" name="id2651082"></a>
 		This module is identical with the <code class="literal">audit</code> module above except
 		that it sends audit logs to both syslog as well as the <code class="literal">smbd</code> log files. The 
 		<a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> for this module is set in the <code class="filename">smb.conf</code> file. 
 		</p><p>
 		Valid settings and the information that will be recorded are shown in <a class="link" href="VFS.html#xtdaudit" title="Table�23.1.�Extended Auditing Log Information">the next table</a>.
-		</p><div class="table"><a name="xtdaudit"></a><p class="title"><b>Table�23.1.�Extended Auditing Log Information</b></p><div class="table-contents"><table summary="Extended Auditing Log Information" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Log Level</th><th align="center">Log Details - File and Directory Operations</th></tr></thead><tbody><tr><td align="center">0</td><td align="left">Make Directory, Remove Directory, Unlink</td></tr><tr><td align="center">1</td><td align="left">Open Directory, Rename File, Change Permissions/ACLs</td></tr><tr><td align="center">2</td><td align="left">Open &amp; Close File</td></tr><tr><td align="center">10</td><td align="left">Maximum Debug Level</td></tr></tbody></table></div></div><br class="table-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2651078"></a>Configuration of Auditing</h4></div></div></div><p>
-<a class="indexterm" name="id2651086"></a>
+		</p><div class="table"><a name="xtdaudit"></a><p class="title"><b>Table�23.1.�Extended Auditing Log Information</b></p><div class="table-contents"><table summary="Extended Auditing Log Information" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Log Level</th><th align="center">Log Details - File and Directory Operations</th></tr></thead><tbody><tr><td align="center">0</td><td align="left">Make Directory, Remove Directory, Unlink</td></tr><tr><td align="center">1</td><td align="left">Open Directory, Rename File, Change Permissions/ACLs</td></tr><tr><td align="center">2</td><td align="left">Open &amp; Close File</td></tr><tr><td align="center">10</td><td align="left">Maximum Debug Level</td></tr></tbody></table></div></div><br class="table-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2651218"></a>Configuration of Auditing</h4></div></div></div><p>
+<a class="indexterm" name="id2651226"></a>
 		This auditing tool is more flexible than most people will readily recognize. There are a number of ways
 		by which useful logging information can be recorded.
 		</p><div class="itemizedlist"><ul type="disc"><li><p>Syslog can be used to record all transaction. This can be disabled by setting
@@ -145,26 +145,26 @@ quotasettings:	gid nolimit = no
 		it is essential that the <a class="link" href="smb.conf.5.html#MAXLOGSIZE" target="_top">max log size = 0</a> be set
 		in the <code class="filename">smb.conf</code> file.
 		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="fakeperms"></a>fake_perms</h3></div></div></div><p>
-<a class="indexterm" name="id2651211"></a>
-<a class="indexterm" name="id2651218"></a>
-<a class="indexterm" name="id2651225"></a>
-<a class="indexterm" name="id2651232"></a>
+<a class="indexterm" name="id2651351"></a>
+<a class="indexterm" name="id2651358"></a>
+<a class="indexterm" name="id2651365"></a>
+<a class="indexterm" name="id2651371"></a>
 		This module was created to allow Roaming Profile files and directories to be set (on the Samba server
 		under UNIX) as read only. This module will, if installed on the Profiles share, report to the client
 		that the Profile files and directories are writeable. This satisfies the client even though the files
 		will never be overwritten as the client logs out or shuts down.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651247"></a>recycle</h3></div></div></div><p>
-<a class="indexterm" name="id2651255"></a>
-<a class="indexterm" name="id2651262"></a>
-<a class="indexterm" name="id2651269"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651387"></a>recycle</h3></div></div></div><p>
+<a class="indexterm" name="id2651395"></a>
+<a class="indexterm" name="id2651401"></a>
+<a class="indexterm" name="id2651408"></a>
 		A Recycle Bin-like module. Where used, unlink calls will be intercepted and files moved
 		to the recycle directory instead of being deleted. This gives the same effect as the
 		<span class="guiicon">Recycle Bin</span> on Windows computers.
 		</p><p>
-<a class="indexterm" name="id2651288"></a>
-<a class="indexterm" name="id2651295"></a>
-<a class="indexterm" name="id2651302"></a>
-<a class="indexterm" name="id2651309"></a>
+<a class="indexterm" name="id2651428"></a>
+<a class="indexterm" name="id2651435"></a>
+<a class="indexterm" name="id2651442"></a>
+<a class="indexterm" name="id2651448"></a>
 		The <span class="guiicon">Recycle Bin</span> will not appear in
 		<span class="application">Windows Explorer</span> views of the network
 		file system (share) nor on any mapped drive. Instead, a directory
@@ -179,10 +179,10 @@ quotasettings:	gid nolimit = no
 		file was deleted.
 		</p><p>Supported options for the <code class="literal">recycle</code> module are as follow:
 		</p><div class="variablelist"><dl><dt><span class="term">recycle:repository</span></dt><dd><p>
-<a class="indexterm" name="id2651386"></a>
+<a class="indexterm" name="id2651526"></a>
 				Path of the directory where deleted files should be moved.
 				</p></dd><dt><span class="term">recycle:directory_mode</span></dt><dd><p>
-<a class="indexterm" name="id2651406"></a>
+<a class="indexterm" name="id2651546"></a>
 				Set it to the octal mode you want for the recycle directory. With
 				this mode the recycle directory	will be created if it not
 				exists and the first file is deleted.
@@ -191,7 +191,7 @@ quotasettings:	gid nolimit = no
 				If <em class="parameter"><code>directory_mode</code></em> not exists, the default
 				mode 0700 is used.
 				</p></dd><dt><span class="term">recycle:subdir_mode</span></dt><dd><p>
-<a class="indexterm" name="id2651441"></a>
+<a class="indexterm" name="id2651581"></a>
 				Set it to the octal mode you want for the sub directories of
 				the recycle directory. With this mode	the sub directories will
 				be created.
@@ -199,48 +199,48 @@ quotasettings:	gid nolimit = no
 				sub directories will be created with the mode from
 				<em class="parameter"><code>directory_mode</code></em>.
 				</p></dd><dt><span class="term">recycle:keeptree</span></dt><dd><p>
-<a class="indexterm" name="id2651475"></a>
+<a class="indexterm" name="id2651615"></a>
 				Specifies whether the directory structure should be kept or if the files in the directory that is being 
 				deleted should be kept separately in the recycle bin.
 				</p></dd><dt><span class="term">recycle:versions</span></dt><dd><p>
-<a class="indexterm" name="id2651497"></a>
+<a class="indexterm" name="id2651636"></a>
 				If this option is set, two files 
 				with the same name that are deleted will both 
 				be kept in the recycle bin. Newer deleted versions 
 				of a file will be called &#8220;<span class="quote">Copy #x of <em class="replaceable"><code>filename</code></em></span>&#8221;.
 				</p></dd><dt><span class="term">recycle:touch</span></dt><dd><p>
-<a class="indexterm" name="id2651524"></a>
+<a class="indexterm" name="id2651664"></a>
 				Specifies whether a file's access date should be touched when the file is moved to the recycle bin.
 				</p></dd><dt><span class="term">recycle:touch_mtime</span></dt><dd><p>
-<a class="indexterm" name="id2651544"></a>
+<a class="indexterm" name="id2651684"></a>
 				Specifies whether a file's last modify date date should be touched when the file is moved to the recycle bin.
 				</p></dd><dt><span class="term">recycle:maxsize</span></dt><dd><p>
-<a class="indexterm" name="id2651564"></a>
+<a class="indexterm" name="id2651703"></a>
 				Files that are larger than the number of bytes specified by this parameter will not be put into the recycle bin.
 				</p></dd><dt><span class="term">recycle:exclude</span></dt><dd><p>
-<a class="indexterm" name="id2651584"></a>
+<a class="indexterm" name="id2651723"></a>
 				List of files that should not be put into the recycle bin when deleted, but deleted in the regular way.
 				</p></dd><dt><span class="term">recycle:exclude_dir</span></dt><dd><p>
-<a class="indexterm" name="id2651604"></a>
+<a class="indexterm" name="id2651743"></a>
 				Contains a list of directories. When files from these directories are
 				deleted, they are not put into the
 				recycle bin but are deleted in the
 				regular way.
 				</p></dd><dt><span class="term">recycle:noversions</span></dt><dd><p>
-<a class="indexterm" name="id2651625"></a>
+<a class="indexterm" name="id2651764"></a>
 				Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning
 				should be used. Only useful when <span class="emphasis"><em>recycle:versions</em></span> is enabled.
 				</p></dd></dl></div><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651644"></a>netatalk</h3></div></div></div><p>
-<a class="indexterm" name="id2651652"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651783"></a>netatalk</h3></div></div></div><p>
+<a class="indexterm" name="id2651791"></a>
 		A netatalk module will ease co-existence of Samba and netatalk file sharing services.
 		</p><p>Advantages compared to the old netatalk module:
-		</p><div class="itemizedlist"><a class="indexterm" name="id2651666"></a><ul type="disc"><li><p>Does not care about creating .AppleDouble forks, just keeps them in sync.</p></li><li><p>If a share in <code class="filename">smb.conf</code> does not contain .AppleDouble item in hide or veto list, it will be added automatically.</p></li></ul></div><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651694"></a>shadow_copy</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2651703"></a>
+		</p><div class="itemizedlist"><a class="indexterm" name="id2651805"></a><ul type="disc"><li><p>Does not care about creating .AppleDouble forks, just keeps them in sync.</p></li><li><p>If a share in <code class="filename">smb.conf</code> does not contain .AppleDouble item in hide or veto list, it will be added automatically.</p></li></ul></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651833"></a>shadow_copy</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
+<a class="indexterm" name="id2651842"></a>
 	<span class="emphasis"><em>THIS IS NOT A BACKUP, ARCHIVAL, OR VERSION CONTROL SOLUTION!</em></span>
 	</p><p>
-<a class="indexterm" name="id2651717"></a>
+<a class="indexterm" name="id2651856"></a>
 	With Samba or Windows servers, shadow_copy is designed to be an end-user tool only.  It does not replace or
 	enhance your backup and archival solutions and should in no way be considered as such.  Additionally, if you
 	need version control, implement a version control system.  You have been warned.
@@ -251,12 +251,12 @@ quotasettings:	gid nolimit = no
 	additional requirements for pre-Windows XP clients.  I did not test this functionality with any pre-Windows XP
 	clients.  You should be able to get more information about MS Shadow Copy <a class="ulink" href="http://www.microsoft.com/windowsserver2003/techinfo/overview/scr.mspx" target="_top">from the Microsoft's site</a>.
 	</p><p>
-<a class="indexterm" name="id2651762"></a>
-<a class="indexterm" name="id2651768"></a>
-<a class="indexterm" name="id2651775"></a>
-<a class="indexterm" name="id2651782"></a>
-<a class="indexterm" name="id2651789"></a>
-<a class="indexterm" name="id2651796"></a>
+<a class="indexterm" name="id2651901"></a>
+<a class="indexterm" name="id2651908"></a>
+<a class="indexterm" name="id2651915"></a>
+<a class="indexterm" name="id2651922"></a>
+<a class="indexterm" name="id2651929"></a>
+<a class="indexterm" name="id2651936"></a>
 	The shadow_copy VFS module requires some underlying file system setup with some sort of Logical Volume Manager
 	(LVM) such as LVM1, LVM2, or EVMS.  Setting up LVM is beyond the scope of this document; however, we will
 	outline the steps we took to test this functionality for <span class="emphasis"><em>example purposes only.</em></span> You need
@@ -269,9 +269,9 @@ quotasettings:	gid nolimit = no
 	      See <a class="ulink" href="http://www-106.ibm.com/developerworks/linux/library/l-lvm/" target="_top">Learning
 	      Linux LVM, Part 1</a> and <a class="ulink" href="http://www-106.ibm.com/developerworks/library/l-lvm2.html" target="_top">Learning
 	      Linux LWM, Part 2</a> for Daniel Robbins' well-written, two part tutorial on Linux and LVM using LVM
-	      source code and reiserfs.</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2651883"></a>Shadow Copy Setup</h4></div></div></div><p>
-<a class="indexterm" name="id2651890"></a>
-<a class="indexterm" name="id2651897"></a>
+	      source code and reiserfs.</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2652022"></a>Shadow Copy Setup</h4></div></div></div><p>
+<a class="indexterm" name="id2652030"></a>
+<a class="indexterm" name="id2652037"></a>
 	At the time of this writing, not much testing has been done.  I tested the shadow copy VFS module with a
 	specific scenario which was not deployed in a production environment, but more as a proof of concept.  The
 	scenario involved a Samba-3 file server on Debian Sarge with an XFS file system and LVM1.  I do NOT recommend
@@ -286,8 +286,8 @@ quotasettings:	gid nolimit = no
 		It doesn't matter if it is a Domain Controller or Member File Server, but it is assumed that you have a
 		working Samba 3.0.3 or later server running.
 		</p></li><li><p><b>Install &amp; Configure LVM.�</b>
-<a class="indexterm" name="id2651977"></a>
-<a class="indexterm" name="id2651983"></a>
+<a class="indexterm" name="id2652117"></a>
+<a class="indexterm" name="id2652123"></a>
 		Before you can make shadow copies available to the client, you have to create the shadow copies.  This is
 		done by taking some sort of file system snapshot.  Snapshots are a typical feature of Logical Volume
 		Managers such as LVM, so we first need to have that setup.
@@ -295,69 +295,69 @@ quotasettings:	gid nolimit = no
 		The following is provided as an example and will be most helpful for Debian users.  Again, this was tested
 		using the "testing" or "Sarge" distribution.
 		</p><ul type="disc"><li><p>
-<a class="indexterm" name="id2652008"></a>
-<a class="indexterm" name="id2652015"></a>
-<a class="indexterm" name="id2652022"></a>
-<a class="indexterm" name="id2652029"></a>
-<a class="indexterm" name="id2652036"></a>
+<a class="indexterm" name="id2652148"></a>
+<a class="indexterm" name="id2652155"></a>
+<a class="indexterm" name="id2652162"></a>
+<a class="indexterm" name="id2652169"></a>
+<a class="indexterm" name="id2652176"></a>
 			Install lvm10 and devfsd packages if you have not done so already.  On Debian systems, you are warned of the
 			interaction of devfs and lvm1 which requires the use of devfs filenames.  Running <code class="literal">apt-get update
 			&amp;&amp; apt-get install lvm10 devfsd xfsprogs</code> should do the trick for this example.
 			</p></li><li><p>
-<a class="indexterm" name="id2652059"></a>
-<a class="indexterm" name="id2652066"></a>
-<a class="indexterm" name="id2652073"></a>
-<a class="indexterm" name="id2652080"></a>
-<a class="indexterm" name="id2652087"></a>
+<a class="indexterm" name="id2652199"></a>
+<a class="indexterm" name="id2652206"></a>
+<a class="indexterm" name="id2652213"></a>
+<a class="indexterm" name="id2652220"></a>
+<a class="indexterm" name="id2652227"></a>
 			Now you need to create a volume.  You will need to create a partition (or partitions) to add to your volume.
 			Use your favorite partitioning tool (e.g., Linux fdisk, cfdisk, etc.).  The partition type should be set to
 			0x8e for "Linux LVM."  In this example, we will use /dev/hdb1.
 			</p><p>
-<a class="indexterm" name="id2652102"></a>
-<a class="indexterm" name="id2652109"></a>
-<a class="indexterm" name="id2652116"></a>
+<a class="indexterm" name="id2652242"></a>
+<a class="indexterm" name="id2652249"></a>
+<a class="indexterm" name="id2652255"></a>
 			Once you have the Linux LVM partition (type 0x8e), you can run a series of commands to create the LVM volume.
 			You can use several disks and/or partitions, but we will use only one in this example.  You may also need to
 			load the kernel module with something like <code class="literal">modprobe lvm-mod</code> and set your system up to load
 			it on reboot by adding it to (<code class="filename">/etc/modules</code>).
 			</p></li><li><p>
-<a class="indexterm" name="id2652144"></a>
+<a class="indexterm" name="id2652284"></a>
 			Create the physical volume with <code class="literal">pvcreate /dev/hdb1</code>
 			</p></li><li><p>
-<a class="indexterm" name="id2652162"></a>
-<a class="indexterm" name="id2652169"></a>
+<a class="indexterm" name="id2652302"></a>
+<a class="indexterm" name="id2652309"></a>
 			Create the volume group and add /dev/hda1 to it with <code class="literal">vgcreate shadowvol /dev/hdb1</code>
 			</p><p>
-<a class="indexterm" name="id2652186"></a>
+<a class="indexterm" name="id2652326"></a>
 			You can use <code class="literal">vgdisplay</code> to review information about the volume group.
 			</p></li><li><p>
-<a class="indexterm" name="id2652204"></a>
+<a class="indexterm" name="id2652344"></a>
 			Now you can create the logical volume with something like <code class="literal">lvcreate -L400M -nsh_test shadowvol</code>
 			</p><p>
-<a class="indexterm" name="id2652222"></a>
+<a class="indexterm" name="id2652362"></a>
 			This creates the logical volume of 400 MBs named "sh_test" in the volume group we created called shadowvol.
 			If everything is working so far, you should see them in <code class="filename">/dev/shadowvol</code>.
 			</p></li><li><p>
-<a class="indexterm" name="id2652242"></a>
+<a class="indexterm" name="id2652382"></a>
 			Now we should be ready to format the logical volume we named sh_test with <code class="literal">mkfs.xfs
 			/dev/shadowvol/sh_test</code>
 			</p><p>
-<a class="indexterm" name="id2652260"></a>
-<a class="indexterm" name="id2652267"></a>
-<a class="indexterm" name="id2652273"></a>
-<a class="indexterm" name="id2652280"></a>
-<a class="indexterm" name="id2652287"></a>
+<a class="indexterm" name="id2652400"></a>
+<a class="indexterm" name="id2652406"></a>
+<a class="indexterm" name="id2652413"></a>
+<a class="indexterm" name="id2652420"></a>
+<a class="indexterm" name="id2652427"></a>
 			You can format the logical volume with any file system you choose, but make sure to use one that allows you to
 			take advantage of the additional features of LVM such as freezing, resizing, and growing your file systems.
 			</p><p>
-<a class="indexterm" name="id2652301"></a>
-<a class="indexterm" name="id2652308"></a>
-<a class="indexterm" name="id2652314"></a>
+<a class="indexterm" name="id2652441"></a>
+<a class="indexterm" name="id2652447"></a>
+<a class="indexterm" name="id2652454"></a>
 			Now we have an LVM volume where we can play with the shadow_copy VFS module.
 			</p></li><li><p>
-<a class="indexterm" name="id2652327"></a>
-<a class="indexterm" name="id2652334"></a>
-<a class="indexterm" name="id2652341"></a>
+<a class="indexterm" name="id2652467"></a>
+<a class="indexterm" name="id2652474"></a>
+<a class="indexterm" name="id2652480"></a>
 			Now we need to prepare the directory with something like
 </p><pre class="screen">
 <code class="prompt">root# </code> mkdir -p /data/shadow_share
@@ -366,19 +366,19 @@ quotasettings:	gid nolimit = no
 			you can use it.  If in doubt, use <code class="literal">chmod 777 /data/shadow_share</code> and tighten the permissions
 			once you get things working.
 			</p></li><li><p>
-<a class="indexterm" name="id2652375"></a>
+<a class="indexterm" name="id2652515"></a>
 			Mount the LVM volume using something like <code class="literal">mount /dev/shadowvol/sh_test /data/shadow_share</code>
 			</p><p>
-<a class="indexterm" name="id2652392"></a>
+<a class="indexterm" name="id2652532"></a>
 			You may also want to edit your <code class="filename">/etc/fstab</code> so that this partition mounts during the system boot.
 			</p></li></ul></div></li><li><p><b>Install &amp; Configure the shadow_copy VFS Module.�</b>
 		Finally we get to the actual shadow_copy VFS module.  The shadow_copy VFS module should be available in Samba
 		3.0.3 and higher.  The smb.conf configuration is pretty standard.  Here is our example of a share configured
 		with the shadow_copy VFS module:
-		</p><div class="example"><a name="vfsshadow"></a><p class="title"><b>Example�23.3.�Share With shadow_copy VFS</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[shadow_share]</code></em></td></tr><tr><td><a class="indexterm" name="id2652450"></a><em class="parameter"><code>comment = Shadow Copy Enabled Share</code></em></td></tr><tr><td><a class="indexterm" name="id2652462"></a><em class="parameter"><code>path = /data/shadow_share</code></em></td></tr><tr><td><a class="indexterm" name="id2652473"></a><em class="parameter"><code>vfs objects = shadow_copy</code></em></td></tr><tr><td><a class="indexterm" name="id2652485"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2652497"></a><em class="parameter"><code>browseable = yes</code></em></td></tr></table></div></div><br class="example-break"></li><li><p><b>Create Snapshots and Make Them Available to shadow_copy.so.�</b>
-<a class="indexterm" name="id2652520"></a>
-<a class="indexterm" name="id2652527"></a>
-<a class="indexterm" name="id2652534"></a>
+		</p><div class="example"><a name="vfsshadow"></a><p class="title"><b>Example�23.3.�Share With shadow_copy VFS</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[shadow_share]</code></em></td></tr><tr><td><a class="indexterm" name="id2652590"></a><em class="parameter"><code>comment = Shadow Copy Enabled Share</code></em></td></tr><tr><td><a class="indexterm" name="id2652601"></a><em class="parameter"><code>path = /data/shadow_share</code></em></td></tr><tr><td><a class="indexterm" name="id2652613"></a><em class="parameter"><code>vfs objects = shadow_copy</code></em></td></tr><tr><td><a class="indexterm" name="id2652625"></a><em class="parameter"><code>writeable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2652636"></a><em class="parameter"><code>browseable = yes</code></em></td></tr></table></div></div><br class="example-break"></li><li><p><b>Create Snapshots and Make Them Available to shadow_copy.so.�</b>
+<a class="indexterm" name="id2652660"></a>
+<a class="indexterm" name="id2652667"></a>
+<a class="indexterm" name="id2652674"></a>
 		Before you can browse the shadow copies, you must create them and mount them.  This will most likely be done
 		with a script that runs as a cron job.  With this particular solution, the shadow_copy VFS module is used to
 		browse LVM snapshots.  Those snapshots are not created by the module.  They are not made available by the
@@ -404,15 +404,15 @@ mount /dev/shadowvol/$SNAPNAME \
 		your XP client you can right-click on specific files or in the empty space of the shadow_share and view the
 		"properties."  If anything has changed, then you will see it on the "Previous Versions" tab of the properties
 		window.
-		</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="id2652604"></a>VFS Modules Available Elsewhere</h2></div></div></div><p>
-<a class="indexterm" name="id2652612"></a>
+		</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="id2652736"></a>VFS Modules Available Elsewhere</h2></div></div></div><p>
+<a class="indexterm" name="id2652745"></a>
 This section contains a listing of various other VFS modules that have been posted but do not currently reside
 in the Samba CVS tree for one reason or another (e.g., it is easy for the maintainer to have his or her own
 CVS tree).
 </p><p>
 No statements about the stability or functionality of any module should be implied due to its presence here.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652629"></a>DatabaseFS</h3></div></div></div><p>
-<a class="indexterm" name="id2652637"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652762"></a>DatabaseFS</h3></div></div></div><p>
+<a class="indexterm" name="id2652769"></a>
 URL: <a class="ulink" href="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" target="_top">
 Taylors University DatabaeFS</a>
 </p><p>By <a class="ulink" href="mailto:elorimer@css.tayloru.edu" target="_top">Eric Lorimer.</a></p><p>
@@ -425,13 +425,13 @@ beyond the table it requires to run.
 </p><p>
 Any feedback would be appreciated: comments, suggestions, patches, and so on. If nothing else, it
 might prove useful for someone else who wishes to create a virtual filesystem.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652689"></a>vscan</h3></div></div></div><a class="indexterm" name="id2652695"></a><p>URL: <a class="ulink" href="http://www.openantivirus.org/projects.php#samba-vscan" target="_top">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652821"></a>vscan</h3></div></div></div><a class="indexterm" name="id2652827"></a><p>URL: <a class="ulink" href="http://www.openantivirus.org/projects.php#samba-vscan" target="_top">
 Open Anti-Virus vscan</a>
 </p><p>
-<a class="indexterm" name="id2652716"></a>
+<a class="indexterm" name="id2652848"></a>
 samba-vscan is a proof-of-concept module for Samba, which provides on-access anti-virus support for files
 shared using Samba.  samba-vscan supports various virus scanners and is maintained by Rainer Link.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652728"></a>vscan-clamav</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652861"></a>vscan-clamav</h3></div></div></div><p>
 Samba users have been using the RPMS from SerNet without a problem.
 OpenSUSE Linux users have also used the vscan scanner for quite some time
 with excellent results. It does impact overall write performance though.
diff --git a/docs/htmldocs/Samba3-HOWTO/apa.html b/docs/htmldocs/Samba3-HOWTO/apa.html
index 74385b36cc..d5346c2ff9 100644
--- a/docs/htmldocs/Samba3-HOWTO/apa.html
+++ b/docs/htmldocs/Samba3-HOWTO/apa.html
@@ -1,50 +1,50 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix�A.� GNU General Public License version 3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="DNSDHCP.html" title="Chapter�48.�DNS and DHCP Configuration Guide"><link rel="next" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix�A.�
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix�A.� GNU General Public License version 3</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="DNSDHCP.html" title="Chapter�48.�DNS and DHCP Configuration Guide"><link rel="next" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix�A.�
     GNU General Public License version 3
-  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DNSDHCP.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2693262"></a>Appendix�A.�
+  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DNSDHCP.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="go01.html">Next</a></td></tr></table><hr></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2693402"></a>Appendix�A.�
     <acronym class="acronym">GNU</acronym> General Public License version 3
-  </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="bridgehead"><a href="apa.html#id2693290">A. 
+  </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="bridgehead"><a href="apa.html#id2693431">A. 
     Preamble
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693435">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693576">A. 
     TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693439">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693580">A. 
     0. Definitions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693532">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693672">A. 
     1. Source Code.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693630">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693771">A. 
     2. Basic Permissions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693681">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693809">A. 
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693716">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693845">A. 
     4. Conveying Verbatim Copies.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693743">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693872">A. 
     5. Conveying Modified Source Versions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693839">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693968">A. 
     6. Conveying Non-Source Forms.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694028">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694157">A. 
      7. Additional Terms.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694164">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694293">A. 
      8. Termination.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694208">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694342">A. 
      9. Acceptance Not Required for Having Copies.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694227">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694362">A. 
      10. Automatic Licensing of Downstream Recipients.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694279">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694414">A. 
     11. Patents.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694425">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694559">A. 
     12. No Surrender of Others&#8217; Freedom.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694447">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694581">A. 
     13. Use with the ???TITLE??? Affero General Public License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694476">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694610">A. 
     14. Revised Versions of this License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694538">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694672">A. 
     15. Disclaimer of Warranty.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694564">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694698">A. 
     16. Limitation of Liability.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694584">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694719">A. 
     17. Interpretation of Sections 15 and 16.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694601">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694735">A. 
     END OF TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694605">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694739">A. 
     How to Apply These Terms to Your New Programs
   </a></span></dt></dl></div><p>
     Version 3, 29 June 2007
@@ -54,7 +54,7 @@
   </p><p>
     Everyone is permitted to copy and distribute verbatim copies of this license
     document, but changing it is not allowed.
-  </p><h2><a name="id2693290"></a>
+  </p><h2><a name="id2693431"></a>
     Preamble
   </h2><p>
     The <acronym class="acronym">GNU</acronym> General Public License is a free, copyleft
@@ -118,9 +118,9 @@
   </p><p>
     The precise terms and conditions for copying, distribution and modification
     follow.
-  </p><h2><a name="id2693435"></a>
+  </p><h2><a name="id2693576"></a>
     TERMS AND CONDITIONS
-  </h2><h2><a name="id2693439"></a>
+  </h2><h2><a name="id2693580"></a>
     0. Definitions.
   </h2><p>
     &#8220;This License&#8221; refers to version 3 of the <acronym class="acronym">GNU</acronym>
@@ -162,7 +162,7 @@
     License, and how to view a copy of this License.  If the interface presents
     a list of user commands or options, such as a menu, a prominent item in the
     list meets this criterion.
-  </p><h2><a name="id2693532"></a>
+  </p><h2><a name="id2693672"></a>
     1. Source Code.
   </h2><p>
     The &#8220;source code&#8221; for a work means the preferred form of the
@@ -202,7 +202,7 @@
     automatically from other parts of the Corresponding Source.
   </p><p>
     The Corresponding Source for a work in source code form is that same work.
-  </p><h2><a name="id2693630"></a>
+  </p><h2><a name="id2693771"></a>
     2. Basic Permissions.
   </h2><p>
     All rights granted under this License are granted for the term of copyright
@@ -227,7 +227,7 @@
     Conveying under any other circumstances is permitted solely under the
     conditions stated below.  Sublicensing is not allowed; section 10 makes it
     unnecessary.
-  </p><h2><a name="id2693681"></a>
+  </p><h2><a name="id2693809"></a>
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
   </h2><p>
     No covered work shall be deemed part of an effective technological measure
@@ -242,7 +242,7 @@
     the work as a means of enforcing, against the work&#8217;s users, your or
     third parties&#8217; legal rights to forbid circumvention of technological
     measures.
-  </p><h2><a name="id2693716"></a>
+  </p><h2><a name="id2693845"></a>
     4. Conveying Verbatim Copies.
   </h2><p>
     You may convey verbatim copies of the Program&#8217;s source code as you
@@ -255,7 +255,7 @@
   </p><p>
     You may charge any price or no price for each copy that you convey, and you
     may offer support or warranty protection for a fee.
-  </p><h2><a name="id2693743"></a>
+  </p><h2><a name="id2693872"></a>
     5. Conveying Modified Source Versions.
   </h2><p>
     You may convey a work based on the Program, or the modifications to produce
@@ -291,7 +291,7 @@
     or legal rights of the compilation&#8217;s users beyond what the individual works
     permit.  Inclusion of a covered work in an aggregate does not cause
     this License to apply to the other parts of the aggregate.
-  </p><h2><a name="id2693839"></a>
+  </p><h2><a name="id2693968"></a>
     6. Conveying Non-Source Forms.
   </h2><p>
     You may convey a covered work in object code form under the terms of
@@ -386,7 +386,7 @@
     (and with an implementation available to the public in source code form),
     and must require no special password or key for unpacking, reading or
     copying.
-  </p><h2><a name="id2694028"></a>
+  </p><h2><a name="id2694157"></a>
      7. Additional Terms.
    </h2><p>
      &#8220;Additional permissions&#8221; are terms that supplement the terms of
@@ -450,7 +450,7 @@
      Additional terms, permissive or non-permissive, may be stated in the form
      of a separately written license, or stated as exceptions; the above
      requirements apply either way.
-   </p><h2><a name="id2694164"></a>
+   </p><h2><a name="id2694293"></a>
      8. Termination.
    </h2><p>
      You may not propagate or modify a covered work except as expressly provided
@@ -476,7 +476,7 @@
      License.  If your rights have been terminated and not permanently
      reinstated, you do not qualify to receive new licenses for the same
      material under section 10.
-   </p><h2><a name="id2694208"></a>
+   </p><h2><a name="id2694342"></a>
      9. Acceptance Not Required for Having Copies.
    </h2><p>
      You are not required to accept this License in order to receive or run a
@@ -487,7 +487,7 @@
      These actions infringe copyright if you do not accept this License.
      Therefore, by modifying or propagating a covered work, you indicate your
      acceptance of this License to do so.
-   </p><h2><a name="id2694227"></a>
+   </p><h2><a name="id2694362"></a>
      10. Automatic Licensing of Downstream Recipients.
    </h2><p>
      Each time you convey a covered work, the recipient automatically receives a
@@ -512,7 +512,7 @@
      or counterclaim in a lawsuit) alleging that any patent claim is infringed
      by making, using, selling, offering for sale, or importing the Program or
      any portion of it.
-   </p><h2><a name="id2694279"></a>
+   </p><h2><a name="id2694414"></a>
     11. Patents.
   </h2><p>
     A &#8220;contributor&#8221; is a copyright holder who authorizes use under
@@ -579,7 +579,7 @@
     Nothing in this License shall be construed as excluding or limiting any
     implied license or other defenses to infringement that may otherwise be
     available to you under applicable patent law.
-  </p><h2><a name="id2694425"></a>
+  </p><h2><a name="id2694559"></a>
     12. No Surrender of Others&#8217; Freedom.
   </h2><p>
     If conditions are imposed on you (whether by court order, agreement or
@@ -591,7 +591,7 @@
     to collect a royalty for further conveying from those to whom you convey the
     Program, the only way you could satisfy both those terms and this License
     would be to refrain entirely from conveying the Program.
-  </p><h2><a name="id2694447"></a>
+  </p><h2><a name="id2694581"></a>
     13. Use with the <acronym class="acronym">GNU</acronym> Affero General Public License.
   </h2><p>
     Notwithstanding any other provision of this License, you have permission to
@@ -602,7 +602,7 @@
     requirements of the <acronym class="acronym">GNU</acronym> Affero General Public License,
     section 13, concerning interaction through a network will apply to the
     combination as such.
-  </p><h2><a name="id2694476"></a>
+  </p><h2><a name="id2694610"></a>
     14. Revised Versions of this License.
   </h2><p>
     The Free Software Foundation may publish revised and/or new versions of the
@@ -627,7 +627,7 @@
     Later license versions may give you additional or different permissions.
     However, no additional obligations are imposed on any author or copyright
     holder as a result of your choosing to follow a later version.
-  </p><h2><a name="id2694538"></a>
+  </p><h2><a name="id2694672"></a>
     15. Disclaimer of Warranty.
   </h2><p>
     THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
@@ -638,7 +638,7 @@
     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
     YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
     NECESSARY SERVICING, REPAIR OR CORRECTION.
-  </p><h2><a name="id2694564"></a>
+  </p><h2><a name="id2694698"></a>
     16. Limitation of Liability.
   </h2><p>
     IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
@@ -650,7 +650,7 @@
     PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
     EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
     SUCH DAMAGES.
-  </p><h2><a name="id2694584"></a>
+  </p><h2><a name="id2694719"></a>
     17. Interpretation of Sections 15 and 16.
   </h2><p>
     If the disclaimer of warranty and limitation of liability provided above
@@ -659,9 +659,9 @@
     waiver of all civil liability in connection with the Program, unless a
     warranty or assumption of liability accompanies a copy of the Program in
     return for a fee.
-  </p><h2><a name="id2694601"></a>
+  </p><h2><a name="id2694735"></a>
     END OF TERMS AND CONDITIONS
-  </h2><h2><a name="id2694605"></a>
+  </h2><h2><a name="id2694739"></a>
     How to Apply These Terms to Your New Programs
   </h2><p>
     If you develop a new program, and you want it to be of the greatest possible
diff --git a/docs/htmldocs/Samba3-HOWTO/bugreport.html b/docs/htmldocs/Samba3-HOWTO/bugreport.html
index fa3f320c8d..2df1696dc6 100644
--- a/docs/htmldocs/Samba3-HOWTO/bugreport.html
+++ b/docs/htmldocs/Samba3-HOWTO/bugreport.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�40.�Reporting Bugs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="problems.html" title="Chapter�39.�Analyzing and Solving Samba Problems"><link rel="next" href="tdb.html" title="Chapter�41.�Managing TDB Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�40.�Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="tdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter�40.�Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="bugreport.html#id2685866">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2685956">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686191">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686393">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686526">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686652">Patches</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685866"></a>Introduction</h2></div></div></div><p>
-<a class="indexterm" name="id2685874"></a>
-<a class="indexterm" name="id2685881"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�40.�Reporting Bugs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="problems.html" title="Chapter�39.�Analyzing and Solving Samba Problems"><link rel="next" href="tdb.html" title="Chapter�41.�Managing TDB Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�40.�Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="tdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter�40.�Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="bugreport.html#id2686022">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686111">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686347">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686549">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686682">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686807">Patches</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686022"></a>Introduction</h2></div></div></div><p>
+<a class="indexterm" name="id2686030"></a>
+<a class="indexterm" name="id2686036"></a>
 Please report bugs using Samba's <a class="ulink" href="https://bugzilla.samba.org/" target="_top">Bugzilla</a> facilities and take
 the time to read this file before you submit a bug report. Also, check to see if it has changed between
 releases, as we may be changing the bug reporting mechanism at some point.
@@ -12,9 +12,9 @@ we can possibly answer, so you have a much higher chance of a response
 and a fix if you send us a &#8220;<span class="quote">developer-friendly</span>&#8221; bug report that lets
 us fix it fast. 
 </p><p>
-<a class="indexterm" name="id2685914"></a>
-<a class="indexterm" name="id2685921"></a>
-<a class="indexterm" name="id2685927"></a>
+<a class="indexterm" name="id2686069"></a>
+<a class="indexterm" name="id2686076"></a>
+<a class="indexterm" name="id2686083"></a>
 If you post the bug to the comp.protocols.smb
 newsgroup or the mailing list, do not assume that we will read it. If you suspect that your 
 problem is not a bug but a configuration problem, it is better to send 
@@ -24,7 +24,7 @@ that list who may be able to help you.
 You may also like to look though the recent mailing list archives,
 which are conveniently accessible on the Samba Web pages
 at <a class="ulink" href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685956"></a>General Information</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686111"></a>General Information</h2></div></div></div><p>
 Before submitting a bug report, check your config for silly
 errors. Look in your log files for obvious messages that tell
 you've misconfigured something. Run testparm to check your config
@@ -42,13 +42,13 @@ be quite useful. Depending on the problem, a log level of between 3 and
 10 showing the problem may be appropriate. A higher level gives more
 detail but may use too much disk space.
 </p><p>
-<a class="indexterm" name="id2686007"></a>
-<a class="indexterm" name="id2686014"></a>
+<a class="indexterm" name="id2686163"></a>
+<a class="indexterm" name="id2686169"></a>
 To set the debug level, use the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> in your 
 <code class="filename">smb.conf</code>. You may also find it useful to set the log 
 level higher for just one machine and keep separate logs for each machine. 
 To do this, add the following lines to your main <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2686054"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id2686066"></a><em class="parameter"><code>log file = /usr/local/samba/lib/log.%m</code></em></td></tr><tr><td><a class="indexterm" name="id2686077"></a><em class="parameter"><code>include = /usr/local/samba/lib/smb.conf.%m</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2686210"></a><em class="parameter"><code>log level = 10</code></em></td></tr><tr><td><a class="indexterm" name="id2686221"></a><em class="parameter"><code>log file = /usr/local/samba/lib/log.%m</code></em></td></tr><tr><td><a class="indexterm" name="id2686233"></a><em class="parameter"><code>include = /usr/local/samba/lib/smb.conf.%m</code></em></td></tr></table><p>
 and create a file <code class="filename">/usr/local/samba/lib/smb.conf.<em class="replaceable"><code>machine</code></em></code> where
 <em class="replaceable"><code>machine</code></em> is the name of the client you wish to debug. In that file put any
 <code class="filename">smb.conf</code> commands you want; for example, <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> may be useful. This also allows
@@ -61,23 +61,23 @@ As the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</
 debugging information. For most debugging operations, you may not need a setting higher than
 <code class="constant">3</code>. Nearly all bugs can be tracked at a setting of <code class="constant">10</code>, but be
 prepared for a large volume of log data.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2686191"></a>Debugging-Specific Operations</h3></div></div></div><p>
-<a class="indexterm" name="id2686199"></a>
-<a class="indexterm" name="id2686206"></a>
-<a class="indexterm" name="id2686213"></a>
-<a class="indexterm" name="id2686220"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2686347"></a>Debugging-Specific Operations</h3></div></div></div><p>
+<a class="indexterm" name="id2686355"></a>
+<a class="indexterm" name="id2686361"></a>
+<a class="indexterm" name="id2686368"></a>
+<a class="indexterm" name="id2686375"></a>
 	Samba-3.x permits debugging (logging) of specific functional components without unnecessarily
 	cluttering the log files with detailed logs for all operations. An example configuration to 
 	achieve this is shown in:
 	</p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2686239"></a><em class="parameter"><code>log level = 0 tdb:3 passdb:5 auth:4 vfs:2</code></em></td></tr><tr><td><a class="indexterm" name="id2686250"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2686262"></a><em class="parameter"><code>log file = /var/log/samba/%U.%m.log</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2686394"></a><em class="parameter"><code>log level = 0 tdb:3 passdb:5 auth:4 vfs:2</code></em></td></tr><tr><td><a class="indexterm" name="id2686406"></a><em class="parameter"><code>max log size = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2686417"></a><em class="parameter"><code>log file = /var/log/samba/%U.%m.log</code></em></td></tr></table><p>
 </p><p>
 	This will cause the level of detail to be expanded to the debug class (log level) passed to
 	each functional area per the value shown above. The first value passed to the <em class="parameter"><code>log level</code></em>
 	of <code class="constant">0</code> means turn off all unnecessary debugging except the debug classes set for
 	the functional areas as specified. The table shown in <a class="link" href="bugreport.html#dbgclass" title="Table�40.1.�Debuggable Functions">Debuggable Functions</a>
 	may be used to attain very precise analysis of each SMB operation Samba is conducting.
-	</p><div class="table"><a name="dbgclass"></a><p class="title"><b>Table�40.1.�Debuggable Functions</b></p><div class="table-contents"><table summary="Debuggable Functions" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Function Name</th><th align="center">Function Name</th></tr></thead><tbody><tr><td align="center">all</td><td align="center">passdb</td></tr><tr><td align="center">tdb</td><td align="center">sam</td></tr><tr><td align="center">printdrivers</td><td align="center">auth</td></tr><tr><td align="center">lanman</td><td align="center">winbind</td></tr><tr><td align="center">smb</td><td align="center">vfs</td></tr><tr><td align="center">rpc_parse</td><td align="center">idmap</td></tr><tr><td align="center">rpc_srv</td><td align="center">quota</td></tr><tr><td align="center">rpc_cli</td><td align="center">acls</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686393"></a>Internal Errors</h2></div></div></div><p>
+	</p><div class="table"><a name="dbgclass"></a><p class="title"><b>Table�40.1.�Debuggable Functions</b></p><div class="table-contents"><table summary="Debuggable Functions" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Function Name</th><th align="center">Function Name</th></tr></thead><tbody><tr><td align="center">all</td><td align="center">passdb</td></tr><tr><td align="center">tdb</td><td align="center">sam</td></tr><tr><td align="center">printdrivers</td><td align="center">auth</td></tr><tr><td align="center">lanman</td><td align="center">winbind</td></tr><tr><td align="center">smb</td><td align="center">vfs</td></tr><tr><td align="center">rpc_parse</td><td align="center">idmap</td></tr><tr><td align="center">rpc_srv</td><td align="center">quota</td></tr><tr><td align="center">rpc_cli</td><td align="center">acls</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686549"></a>Internal Errors</h2></div></div></div><p>
 If you get the message &#8220;<span class="quote"><span class="errorname">INTERNAL ERROR</span></span>&#8221; in your log files, 
 it means that Samba got an unexpected signal while running. It is probably a
 segmentation fault and almost certainly means a bug in Samba (unless
@@ -91,35 +91,35 @@ include it in your bug report.
 You should also detail how to reproduce the problem, if
 possible. Please make this reasonably detailed.
 </p><p>
-<a class="indexterm" name="id2686426"></a>
+<a class="indexterm" name="id2686581"></a>
 You may also find that a core file appeared in a <code class="filename">corefiles</code>
 subdirectory of the directory where you keep your Samba log
 files. This file is the most useful tool for tracking down the bug. To
 use it, you do this:
-<a class="indexterm" name="id2686442"></a>
-<a class="indexterm" name="id2686448"></a>
+<a class="indexterm" name="id2686597"></a>
+<a class="indexterm" name="id2686604"></a>
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>gdb smbd core</code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2686474"></a>
-<a class="indexterm" name="id2686481"></a>
+<a class="indexterm" name="id2686630"></a>
+<a class="indexterm" name="id2686636"></a>
 adding appropriate paths to smbd and core so gdb can find them. If you
 do not have gdb, try <strong class="userinput"><code>dbx</code></strong>. Then within the debugger,
 use the command <code class="literal">where</code> to give a stack trace of where the
 problem occurred. Include this in your report.
 </p><p>
-<a class="indexterm" name="id2686506"></a>
+<a class="indexterm" name="id2686661"></a>
 If you know any assembly language, do a <code class="literal">disass</code> of the routine
 where the problem occurred (if it's in a library routine, then
 disassemble the routine that called it) and try to work out exactly
 where the problem is by looking at the surrounding code. Even if you
 do not know assembly, including this information in the bug report can be
 useful. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686526"></a>Attaching to a Running Process</h2></div></div></div><p>
-<a class="indexterm" name="id2686535"></a>
-<a class="indexterm" name="id2686542"></a>
-<a class="indexterm" name="id2686548"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686682"></a>Attaching to a Running Process</h2></div></div></div><p>
+<a class="indexterm" name="id2686690"></a>
+<a class="indexterm" name="id2686697"></a>
+<a class="indexterm" name="id2686704"></a>
 Unfortunately, some UNIXes (in particular some recent Linux kernels)
 refuse to dump a core file if the task has changed UID (which smbd
 does often). To debug with this sort of system, you could try to attach
@@ -145,12 +145,12 @@ of the spinning process and type:
 </p><pre class="screen">
 <code class="prompt">root# </code> gdb /usr/local/samba/sbin/smbd
 </pre><p>
-<a class="indexterm" name="id2686634"></a>
+<a class="indexterm" name="id2686789"></a>
 then &#8220;<span class="quote">attach `pid'</span>&#8221; (of the spinning process), then type &#8220;<span class="quote">bt</span>&#8221; to
 get a backtrace to see where the smbd is in the call path.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686652"></a>Patches</h2></div></div></div><p>
-<a class="indexterm" name="id2686659"></a>
-<a class="indexterm" name="id2686666"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686807"></a>Patches</h2></div></div></div><p>
+<a class="indexterm" name="id2686815"></a>
+<a class="indexterm" name="id2686822"></a>
 The best sort of bug report is one that includes a fix! If you send us
 patches, please use <strong class="userinput"><code>diff -u</code></strong> format if your version of 
 diff supports it; otherwise, use <strong class="userinput"><code>diff -c4</code></strong>. Make sure 
diff --git a/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html b/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html
index 4046f39a38..0469976fd3 100644
--- a/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html
+++ b/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html
@@ -1,52 +1,52 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�34.�Advanced Configuration Techniques</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="largefile.html" title="Chapter�33.�Handling Large Directories"><link rel="next" href="migration.html" title="Part�IV.�Migration and Updating"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�34.�Advanced Configuration Techniques</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="cfgsmarts"></a>Chapter�34.�Advanced Configuration Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 30, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673754">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2673598"></a>
-<a class="indexterm" name="id2673605"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�34.�Advanced Configuration Techniques</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="largefile.html" title="Chapter�33.�Handling Large Directories"><link rel="next" href="migration.html" title="Part�IV.�Migration and Updating"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�34.�Advanced Configuration Techniques</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="cfgsmarts"></a>Chapter�34.�Advanced Configuration Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 30, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673899">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2673743"></a>
+<a class="indexterm" name="id2673750"></a>
 Since the release of the first edition of this book there have been repeated requests to better document
 configuration techniques that may help a network administrator to get more out of Samba. Some users have asked
 for documentation regarding the use of the <a class="link" href="smb.conf.5.html#INCLUDE" target="_top">include = file-name</a> parameter.
 </p><p>
-<a class="indexterm" name="id2673633"></a>
-<a class="indexterm" name="id2673640"></a>
+<a class="indexterm" name="id2673778"></a>
+<a class="indexterm" name="id2673784"></a>
 Commencing around mid-2004 there has been increasing interest in the ability to host multiple Samba servers on
 one machine. There has also been an interest in the hosting of multiple Samba server personalities on one
 server.
 </p><p>
-<a class="indexterm" name="id2673654"></a>
-<a class="indexterm" name="id2673661"></a>
+<a class="indexterm" name="id2673798"></a>
+<a class="indexterm" name="id2673805"></a>
 Feedback from technical reviewers made the inclusion of this chapter a necessity. So, here is an 
 answer the questions that have to date not been adequately addressed. Additional user input is welcome as
 it will help this chapter to mature. What is presented here is just a small beginning.
 </p><p>
-<a class="indexterm" name="id2673676"></a>
-<a class="indexterm" name="id2673683"></a>
-<a class="indexterm" name="id2673690"></a>
+<a class="indexterm" name="id2673820"></a>
+<a class="indexterm" name="id2673827"></a>
+<a class="indexterm" name="id2673834"></a>
 There are a number of ways in which multiple servers can be hosted on a single Samba server. Multiple server
 hosting makes it possible to host multiple domain controllers on one machine. Each such machine is
 independent, and each can be stopped or started without affecting another.
 </p><p>
-<a class="indexterm" name="id2673705"></a>
-<a class="indexterm" name="id2673712"></a>
-<a class="indexterm" name="id2673718"></a>
+<a class="indexterm" name="id2673849"></a>
+<a class="indexterm" name="id2673856"></a>
+<a class="indexterm" name="id2673863"></a>
 Sometimes it is desirable to host multiple servers, each with its own security mode. For example, a single
 UNIX/Linux host may be a domain member server (DMS) as well as a generic anonymous print server. In this case,
 only domain member machines and domain users can access the DMS, but even guest users can access the generic
 print server. Another example of a situation where it may be beneficial to host a generic (anonymous) server
 is to host a CDROM server.
 </p><p>
-<a class="indexterm" name="id2673736"></a>
-<a class="indexterm" name="id2673743"></a>
+<a class="indexterm" name="id2673881"></a>
+<a class="indexterm" name="id2673888"></a>
 Some environments dictate the need to have separate servers, each with their own resources, each of which are
 accessible only by certain users or groups. This is one of the simple, but highly effective, ways that Samba
 can replace many physical Windows servers in one Samba installation.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2673754"></a>Implementation</h2></div></div></div><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673763"></a>Multiple Server Hosting</h3></div></div></div><p>
-<a class="indexterm" name="id2673771"></a>
-<a class="indexterm" name="id2673778"></a>
-<a class="indexterm" name="id2673785"></a>
-<a class="indexterm" name="id2673792"></a>
-<a class="indexterm" name="id2673799"></a>
-<a class="indexterm" name="id2673806"></a>
-<a class="indexterm" name="id2673813"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2673899"></a>Implementation</h2></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673908"></a>Multiple Server Hosting</h3></div></div></div><p>
+<a class="indexterm" name="id2673916"></a>
+<a class="indexterm" name="id2673923"></a>
+<a class="indexterm" name="id2673930"></a>
+<a class="indexterm" name="id2673937"></a>
+<a class="indexterm" name="id2673944"></a>
+<a class="indexterm" name="id2673950"></a>
+<a class="indexterm" name="id2673957"></a>
 The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own
 configuration file. This method is complicated by the fact that each instance of <span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span>
 must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by
@@ -54,58 +54,58 @@ must have write access to entirely separate TDB files. The ability to keep separ
 own default TDB directories, or by configuring these in the <code class="filename">smb.conf</code> file, in which case each instance of
 <span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span> must be told to start up with its own <code class="filename">smb.conf</code> configuration file.
 </p><p>
-<a class="indexterm" name="id2673895"></a>
-<a class="indexterm" name="id2673902"></a>
-<a class="indexterm" name="id2673909"></a>
-<a class="indexterm" name="id2673916"></a>
+<a class="indexterm" name="id2674040"></a>
+<a class="indexterm" name="id2674047"></a>
+<a class="indexterm" name="id2674054"></a>
+<a class="indexterm" name="id2674060"></a>
 Each instance should operate on its own IP address (that independent IP address can be an IP Alias).
 Each instance of <span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span> should listen only on its own IP socket. This can be secured
 using the <a class="link" href="smb.conf.5.html#SOCKETADDRESS" target="_top">socket address</a> parameter. Each instance of the Samba server will have its
 own SID also, this means that the servers are discrete and independent of each other.
 </p><p>
-<a class="indexterm" name="id2673962"></a>
-<a class="indexterm" name="id2673969"></a>
-<a class="indexterm" name="id2673975"></a>
-<a class="indexterm" name="id2673982"></a>
-<a class="indexterm" name="id2673989"></a>
-<a class="indexterm" name="id2673996"></a>
-<a class="indexterm" name="id2674003"></a>
-<a class="indexterm" name="id2674010"></a>
-<a class="indexterm" name="id2674017"></a>
+<a class="indexterm" name="id2674107"></a>
+<a class="indexterm" name="id2674114"></a>
+<a class="indexterm" name="id2674120"></a>
+<a class="indexterm" name="id2674127"></a>
+<a class="indexterm" name="id2674134"></a>
+<a class="indexterm" name="id2674141"></a>
+<a class="indexterm" name="id2674148"></a>
+<a class="indexterm" name="id2674155"></a>
+<a class="indexterm" name="id2674162"></a>
 The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of
 process management and start up. The <code class="filename">smb.conf</code> parameters that must be carefully configured includes:
 <a class="link" href="smb.conf.5.html#PRIVATEDIR" target="_top">private dir</a>, <a class="link" href="smb.conf.5.html#PIDDIRECTORY" target="_top">pid directory</a>,<a class="link" href="smb.conf.5.html#LOCKDIRECTORY" target="_top">lock directory</a>, <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a>, <a class="link" href="smb.conf.5.html#BINDINTERFACESONLY" target="_top">bind interfaces only</a>, <a class="link" href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a>, <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a>, <a class="link" href="smb.conf.5.html#SOCKETADDRESS" target="_top">socket address</a>.
 </p><p>
-<a class="indexterm" name="id2674129"></a>
-<a class="indexterm" name="id2674135"></a>
-<a class="indexterm" name="id2674142"></a>
+<a class="indexterm" name="id2674273"></a>
+<a class="indexterm" name="id2674280"></a>
+<a class="indexterm" name="id2674287"></a>
 Those who elect to create multiple Samba servers should have the ability to read and follow
 the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of
 this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and
 if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting
 of multiple samba servers on a single host is considered not supported for Samba-3 by the Samba Team.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2674160"></a>Multiple Virtual Server Personalities</h3></div></div></div><p>
-<a class="indexterm" name="id2674168"></a>
-<a class="indexterm" name="id2674175"></a>
-<a class="indexterm" name="id2674182"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2674305"></a>Multiple Virtual Server Personalities</h3></div></div></div><p>
+<a class="indexterm" name="id2674312"></a>
+<a class="indexterm" name="id2674319"></a>
+<a class="indexterm" name="id2674326"></a>
 Samba has the ability to host multiple virtual servers, each of which have their own personality.  This is
 achieved by configuring an <code class="filename">smb.conf</code> file that is common to all personalities hosted.  Each server
 personality is hosted using its own <a class="link" href="smb.conf.5.html#NETBIOSALIAS" target="_top">netbios alias</a> name, and each has its own distinct
 <a class="link" href="smb.conf.5.html#%5BGLOBAL%5D" target="_top">[global]</a> section. Each server may have its own stanzas for services and meta-services.
 </p><p>
-<a class="indexterm" name="id2674229"></a>
-<a class="indexterm" name="id2674236"></a>
-<a class="indexterm" name="id2674243"></a>
+<a class="indexterm" name="id2674374"></a>
+<a class="indexterm" name="id2674380"></a>
+<a class="indexterm" name="id2674387"></a>
 When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup.
 Only the primary server can be a domain member or a domain controller. The personality is defined by the
 combination of the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> mode it is operating in, the <a class="link" href="smb.conf.5.html#NETBIOSALIASES" target="_top">netbios aliases</a> it has, and the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> that is defined for it.
 </p><p>
-<a class="indexterm" name="id2674292"></a>
-<a class="indexterm" name="id2674299"></a>
-<a class="indexterm" name="id2674306"></a>
-<a class="indexterm" name="id2674313"></a>
-<a class="indexterm" name="id2674320"></a>
-<a class="indexterm" name="id2674326"></a>
+<a class="indexterm" name="id2674437"></a>
+<a class="indexterm" name="id2674443"></a>
+<a class="indexterm" name="id2674450"></a>
+<a class="indexterm" name="id2674457"></a>
+<a class="indexterm" name="id2674464"></a>
+<a class="indexterm" name="id2674471"></a>
 This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services.
 If run using NetBIOS mode (the most common method) it is important that the parameter <a class="link" href="smb.conf.5.html#SMBPORTS" target="_top">smb ports = 139</a> should be specified in the primary <code class="filename">smb.conf</code> file. Failure to do this will result
 in Samba operating over TCP port 445 and problematic operation at best, and at worst only being able to obtain
@@ -114,10 +114,10 @@ TCP port 139 means that the use of the <code class="literal">%L</code> macro is
 the value of this parameter is set at <em class="parameter"><code>139 445</code></em> then the <code class="literal">%L</code> macro
 is not serviceable.
 </p><p>
-<a class="indexterm" name="id2674405"></a>
-<a class="indexterm" name="id2674412"></a>
-<a class="indexterm" name="id2674419"></a>
-<a class="indexterm" name="id2674426"></a>
+<a class="indexterm" name="id2674550"></a>
+<a class="indexterm" name="id2674557"></a>
+<a class="indexterm" name="id2674564"></a>
+<a class="indexterm" name="id2674571"></a>
 It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB
 port), in which case the <code class="literal">%i</code> macro can be used to provide separate server identities (by
 IP Address). Each can have its own <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> mode. It will be necessary to use the
@@ -125,7 +125,7 @@ IP Address). Each can have its own <a class="link" href="smb.conf.5.html#SECURIT
 the <a class="link" href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a> parameters to create the virtual servers. This method is considerably
 more complex than that using NetBIOS names only using TCP port 139.
 </p><p>
-<a class="indexterm" name="id2674494"></a>
+<a class="indexterm" name="id2674638"></a>
 Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only
 Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it
 is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here
@@ -135,46 +135,46 @@ The Samba server is called <code class="literal">ELASTIC</code>, its workgroup n
 The CDROM server is called <code class="literal">CDSERVER</code> and its workgroup is <code class="literal">ARTSDEPT</code>. A
 possible implementation is shown here:
 </p><p>
-<a class="indexterm" name="id2674538"></a>
-<a class="indexterm" name="id2674545"></a>
-<a class="indexterm" name="id2674551"></a>
-<a class="indexterm" name="id2674558"></a>
+<a class="indexterm" name="id2674682"></a>
+<a class="indexterm" name="id2674689"></a>
+<a class="indexterm" name="id2674696"></a>
+<a class="indexterm" name="id2674703"></a>
 The <code class="filename">smb.conf</code> file for the master server is shown in <a class="link" href="cfgsmarts.html#elastic" title="Example�34.1.�Elastic smb.conf File">Elastic smb.conf File</a>.
 This file is placed in the <code class="filename">/etc/samba</code> directory. Only the <span class="application">nmbd</span> and the <span class="application">smbd</span> daemons
 are needed. When started the server will appear in Windows Network Neighborhood as the machine
 <code class="literal">ELASTIC</code> under the workgroup <code class="literal">ROBINSNEST</code>. It is helpful if the Windows
 clients that must access this server are also in the workgroup <code class="literal">ROBINSNEST</code> as this will make
 browsing much more reliable.
-</p><div class="example"><a name="elastic"></a><p class="title"><b>Example�34.1.�Elastic smb.conf File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2674649"></a><em class="parameter"><code>workgroup = ROBINSNEST</code></em></td></tr><tr><td><a class="indexterm" name="id2674660"></a><em class="parameter"><code>netbios name = ELASTIC</code></em></td></tr><tr><td><a class="indexterm" name="id2674672"></a><em class="parameter"><code>netbios aliases = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2674684"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2674696"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674708"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674719"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674732"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674743"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2674764"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2674776"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2674787"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674799"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2674819"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2674831"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2674843"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2674863"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2674875"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2674887"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2674898"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674910"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674921"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674933"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2674948"></a>
+</p><div class="example"><a name="elastic"></a><p class="title"><b>Example�34.1.�Elastic smb.conf File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2674793"></a><em class="parameter"><code>workgroup = ROBINSNEST</code></em></td></tr><tr><td><a class="indexterm" name="id2674805"></a><em class="parameter"><code>netbios name = ELASTIC</code></em></td></tr><tr><td><a class="indexterm" name="id2674817"></a><em class="parameter"><code>netbios aliases = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2674829"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2674840"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674852"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674864"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674876"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674888"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2674908"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2674920"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2674932"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674943"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2674964"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2674976"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2674987"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2675008"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2675019"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2675031"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2675043"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675054"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675066"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675078"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2675093"></a>
 The configuration file for the CDROM server is listed in <a class="link" href="cfgsmarts.html#cdserver" title="Example�34.2.�CDROM Server smb-cdserver.conf file">CDROM Server
 smb-cdserver.conf file</a>. This file is called <code class="filename">smb-cdserver.conf</code> and it should be
 located in the <code class="filename">/etc/samba</code> directory. Machines that are in the workgroup
 <code class="literal">ARTSDEPT</code> will be able to browse this server freely.
-</p><div class="example"><a name="cdserver"></a><p class="title"><b>Example�34.2.�CDROM Server smb-cdserver.conf file</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675014"></a><em class="parameter"><code>workgroup = ARTSDEPT</code></em></td></tr><tr><td><a class="indexterm" name="id2675025"></a><em class="parameter"><code>netbios name = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2675037"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2675049"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[carousel]</code></em></td></tr><tr><td><a class="indexterm" name="id2675070"></a><em class="parameter"><code>comment = CDROM Share</code></em></td></tr><tr><td><a class="indexterm" name="id2675081"></a><em class="parameter"><code>path = /export/cddata</code></em></td></tr><tr><td><a class="indexterm" name="id2675093"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675105"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2675120"></a>
-<a class="indexterm" name="id2675126"></a>
-<a class="indexterm" name="id2675133"></a>
-<a class="indexterm" name="id2675140"></a>
+</p><div class="example"><a name="cdserver"></a><p class="title"><b>Example�34.2.�CDROM Server smb-cdserver.conf file</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675158"></a><em class="parameter"><code>workgroup = ARTSDEPT</code></em></td></tr><tr><td><a class="indexterm" name="id2675170"></a><em class="parameter"><code>netbios name = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2675182"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2675194"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[carousel]</code></em></td></tr><tr><td><a class="indexterm" name="id2675214"></a><em class="parameter"><code>comment = CDROM Share</code></em></td></tr><tr><td><a class="indexterm" name="id2675226"></a><em class="parameter"><code>path = /export/cddata</code></em></td></tr><tr><td><a class="indexterm" name="id2675238"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675249"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2675264"></a>
+<a class="indexterm" name="id2675271"></a>
+<a class="indexterm" name="id2675278"></a>
+<a class="indexterm" name="id2675285"></a>
 The two servers have different resources and are in separate workgroups. The server <code class="literal">ELASTIC</code>
 can only be accessed by uses who have an appropriate account on the host server. All users will be able to
 access the CDROM data that is stored in the <code class="filename">/export/cddata</code> directory. File system
 permissions should set so that the <code class="literal">others</code> user has read-only access to the directory and its
 contents. The files can be owned by root (any user other than the nobody account).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2675174"></a>Multiple Virtual Server Hosting</h3></div></div></div><p>
-<a class="indexterm" name="id2675183"></a>
-<a class="indexterm" name="id2675190"></a>
-<a class="indexterm" name="id2675197"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2675319"></a>Multiple Virtual Server Hosting</h3></div></div></div><p>
+<a class="indexterm" name="id2675327"></a>
+<a class="indexterm" name="id2675334"></a>
+<a class="indexterm" name="id2675341"></a>
 In this example, the requirement is for a primary domain controller for the domain called
 <code class="literal">MIDEARTH</code>. The PDC will be called <code class="literal">MERLIN</code>. An extra machine called
 <code class="literal">SAURON</code> is required. Each machine will have only its own shares. Both machines belong to the
 same domain/workgroup.
 </p><p>
-<a class="indexterm" name="id2675229"></a>
-<a class="indexterm" name="id2675236"></a>
-<a class="indexterm" name="id2675242"></a>
+<a class="indexterm" name="id2675373"></a>
+<a class="indexterm" name="id2675380"></a>
+<a class="indexterm" name="id2675387"></a>
 The master <code class="filename">smb.conf</code> file is shown in <a class="link" href="cfgsmarts.html#mastersmbc" title="Example�34.3.�Master smb.conf File Global Section">the Master smb.conf File Global Section</a>.
 The two files that specify the share information for each server are shown in <a class="link" href="cfgsmarts.html#merlinsmbc" title="Example�34.4.�MERLIN smb-merlin.conf File Share Section">the
 smb-merlin.conf File Share Section</a>, and <a class="link" href="cfgsmarts.html#sauronsmbc" title="Example�34.5.�SAURON smb-sauron.conf File Share Section">the smb-sauron.conf File Share
 Section</a>. All three files are locate in the <code class="filename">/etc/samba</code> directory.
-</p><div class="example"><a name="mastersmbc"></a><p class="title"><b>Example�34.3.�Master smb.conf File Global Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675318"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675330"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2675341"></a><em class="parameter"><code>netbios aliases = SAURON</code></em></td></tr><tr><td><a class="indexterm" name="id2675353"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2675365"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2675377"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2675388"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675400"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675412"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675424"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675437"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675449"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675461"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675474"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675486"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2675498"></a><em class="parameter"><code>logon path =  </code></em></td></tr><tr><td><a class="indexterm" name="id2675510"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2675522"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675533"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675545"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675557"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675568"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="merlinsmbc"></a><p class="title"><b>Example�34.4.�MERLIN smb-merlin.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675609"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675621"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2675642"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2675653"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2675665"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675677"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2675697"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2675709"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2675720"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2675741"></a><em class="parameter"><code>comment = NETLOGON</code></em></td></tr><tr><td><a class="indexterm" name="id2675752"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2675764"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675776"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2675796"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2675808"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2675820"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675832"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675843"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sauronsmbc"></a><p class="title"><b>Example�34.5.�SAURON smb-sauron.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675884"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675896"></a><em class="parameter"><code>netbios name = SAURON</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[www]</code></em></td></tr><tr><td><a class="indexterm" name="id2675916"></a><em class="parameter"><code>comment = Web Pages</code></em></td></tr><tr><td><a class="indexterm" name="id2675928"></a><em class="parameter"><code>path = /srv/www/htdocs</code></em></td></tr><tr><td><a class="indexterm" name="id2675940"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�33.�Handling Large Directories�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�IV.�Migration and Updating</td></tr></table></div></body></html>
+</p><div class="example"><a name="mastersmbc"></a><p class="title"><b>Example�34.3.�Master smb.conf File Global Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675462"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675474"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2675486"></a><em class="parameter"><code>netbios aliases = SAURON</code></em></td></tr><tr><td><a class="indexterm" name="id2675498"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2675510"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2675521"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2675533"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675545"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675557"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675569"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675581"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675593"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675606"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675618"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675631"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2675643"></a><em class="parameter"><code>logon path =  </code></em></td></tr><tr><td><a class="indexterm" name="id2675654"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2675666"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675678"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675690"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675701"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675713"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="merlinsmbc"></a><p class="title"><b>Example�34.4.�MERLIN smb-merlin.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675754"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675765"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2675786"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2675798"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2675810"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675821"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2675842"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2675853"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2675865"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2675885"></a><em class="parameter"><code>comment = NETLOGON</code></em></td></tr><tr><td><a class="indexterm" name="id2675897"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2675909"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675920"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2675941"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2675953"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2675964"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675976"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675988"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sauronsmbc"></a><p class="title"><b>Example�34.5.�SAURON smb-sauron.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2676028"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2676040"></a><em class="parameter"><code>netbios name = SAURON</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[www]</code></em></td></tr><tr><td><a class="indexterm" name="id2676061"></a><em class="parameter"><code>comment = Web Pages</code></em></td></tr><tr><td><a class="indexterm" name="id2676072"></a><em class="parameter"><code>path = /srv/www/htdocs</code></em></td></tr><tr><td><a class="indexterm" name="id2676084"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�33.�Handling Large Directories�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�IV.�Migration and Updating</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html b/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html
index a4816e3203..463505791e 100644
--- a/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html
+++ b/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html
@@ -1,40 +1,40 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�46.�LDAP and Transport Layer Security</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="speed.html" title="Chapter�45.�Samba Performance Tuning"><link rel="next" href="ch47.html" title="Chapter�47.�Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�46.�LDAP and Transport Layer Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="speed.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch47.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ch-ldap-tls"></a>Chapter�46.�LDAP and Transport Layer Security</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gavin</span> <span class="orgname">Suretec Systems Limited, UK</span> <span class="surname">Henry</span></h3><div class="affiliation"><span class="orgname">Suretec Systems Limited, UK<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:ghenry@suretecsystems.com">ghenry@suretecsystems.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 8, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="s1-intro-ldap-tls"></a>Introduction</h2></div></div></div><p>
-	<a class="indexterm" name="id2691290"></a>
-<a class="indexterm" name="id2691299"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�46.�LDAP and Transport Layer Security</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="speed.html" title="Chapter�45.�Samba Performance Tuning"><link rel="next" href="ch47.html" title="Chapter�47.�Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�46.�LDAP and Transport Layer Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="speed.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch47.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ch-ldap-tls"></a>Chapter�46.�LDAP and Transport Layer Security</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gavin</span> <span class="orgname">Suretec Systems Limited, UK</span> <span class="surname">Henry</span></h3><div class="affiliation"><span class="orgname">Suretec Systems Limited, UK<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:ghenry@suretecsystems.com">ghenry@suretecsystems.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 8, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="s1-intro-ldap-tls"></a>Introduction</h2></div></div></div><p>
+	<a class="indexterm" name="id2691426"></a>
+<a class="indexterm" name="id2691435"></a>
 	Up until now, we have discussed the straightforward configuration of <span class="trademark">OpenLDAP</span>&#8482;,
 	with some advanced features such as ACLs. This does not however, deal with the fact that the network
 	transmissions are still in plain text. This is where <em class="firstterm">Transport Layer Security (TLS)</em>
 	comes in.
 	</p><p>
-<a class="indexterm" name="id2691323"></a>
+<a class="indexterm" name="id2691459"></a>
 	<span class="trademark">OpenLDAP</span>&#8482; clients and servers are capable of using the Transport Layer Security (TLS)
 	framework to provide integrity and confidentiality protections in accordance with <a class="ulink" href="http://rfc.net/rfc2830.html" target="_top">RFC 2830</a>; <span class="emphasis"><em>Lightweight Directory Access Protocol (v3):
 	Extension for Transport Layer Security.</em></span>
 	</p><p>
-<a class="indexterm" name="id2691353"></a>
+<a class="indexterm" name="id2691489"></a>
 	TLS uses X.509 certificates. All servers are required to have valid certificates, whereas client certificates
 	are optional. We will only be discussing server certificates.
 	</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2691367"></a>
-<a class="indexterm" name="id2691373"></a>
-<a class="indexterm" name="id2691380"></a>
+<a class="indexterm" name="id2691503"></a>
+<a class="indexterm" name="id2691509"></a>
+<a class="indexterm" name="id2691516"></a>
 	The DN of a server certificate must use the CN attribute to name the server, and the CN must carry the
 	server's fully qualified domain name (FQDN). Additional alias names and wildcards may be present in the
 	<code class="option">subjectAltName</code> certificate extension. More details on server certificate names are in <a class="ulink" href="http://rfc.net/rfc2830.html" target="_top">RFC2830</a>.
 	</p></div><p>
 	We will discuss this more in the next sections.
 	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="s1-config-ldap-tls"></a>Configuring</h2></div></div></div><p>
-	<a class="indexterm" name="id2691420"></a>
+	<a class="indexterm" name="id2691556"></a>
 	Now on to the good bit.
 	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="s1-config-ldap-tls-certs"></a>Generating the Certificate Authority</h3></div></div></div><p>
-<a class="indexterm" name="id2691443"></a>
+<a class="indexterm" name="id2691579"></a>
 	In order to create the relevant certificates, we need to become our own Certificate Authority (CA).
-	<sup>[<a name="id2691454" href="#ftn.id2691454" class="footnote">8</a>]</sup> This is necessary, so we can sign the server certificate.
+	<sup>[<a name="id2691590" href="#ftn.id2691590" class="footnote">8</a>]</sup> This is necessary, so we can sign the server certificate.
 	</p><p>
-<a class="indexterm" name="id2691483"></a>
-	We will be using the <a class="ulink" href="http://www.openssl.org" target="_top">OpenSSL</a> <sup>[<a name="id2691496" href="#ftn.id2691496" class="footnote">9</a>]</sup> software for this, which is included with every great <span class="trademark">Linux</span>� distribution.
+<a class="indexterm" name="id2691619"></a>
+	We will be using the <a class="ulink" href="http://www.openssl.org" target="_top">OpenSSL</a> <sup>[<a name="id2691632" href="#ftn.id2691632" class="footnote">9</a>]</sup> software for this, which is included with every great <span class="trademark">Linux</span>� distribution.
 	</p><p>
-	TLS is used for many types of servers, but the instructions<sup>[<a name="id2691515" href="#ftn.id2691515" class="footnote">10</a>]</sup> presented here, are tailored for <span class="application">OpenLDAP</span>.
+	TLS is used for many types of servers, but the instructions<sup>[<a name="id2691651" href="#ftn.id2691651" class="footnote">10</a>]</sup> presented here, are tailored for <span class="application">OpenLDAP</span>.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 	The <span class="emphasis"><em>Common Name (CN)</em></span>, in the following example, <span class="emphasis"><em>MUST</em></span> be
 	the fully qualified domain name (FQDN) of your ldap server.
@@ -51,7 +51,7 @@
 <code class="prompt">root# </code> cd myCA
 </code>
 </pre><p>
-	Now generate the CA:<sup>[<a name="id2691591" href="#ftn.id2691591" class="footnote">11</a>]</sup>
+	Now generate the CA:<sup>[<a name="id2691727" href="#ftn.id2691727" class="footnote">11</a>]</sup>
 </p><pre class="screen">
 <code class="computeroutput">
 <code class="prompt">root# </code> /usr/share/ssl/misc/CA.pl -newca
@@ -209,7 +209,7 @@ TLS_CACERT /etc/openldap/cacert.pem
 	</p><p>
 	That's all there is to it. Now on to <a class="xref" href="ch-ldap-tls.html#s1-test-ldap-tls" title="Testing">the section called &#8220;Testing&#8221;</a>
 	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="s1-test-ldap-tls"></a>Testing</h2></div></div></div><p>
-<a class="indexterm" name="id2691999"></a>
+<a class="indexterm" name="id2692135"></a>
 This is the easy part. Restart the server:
 </p><pre class="screen">
 <code class="computeroutput">
@@ -220,7 +220,7 @@ Starting slapd:                                            [  OK  ]
 </code>
 </pre><p>
 	Then, using <code class="literal">ldapsearch</code>, test an anonymous search with the
-	<code class="option">-ZZ</code><sup>[<a name="id2692041" href="#ftn.id2692041" class="footnote">12</a>]</sup> option:
+	<code class="option">-ZZ</code><sup>[<a name="id2692177" href="#ftn.id2692177" class="footnote">12</a>]</sup> option:
 </p><pre class="screen">
 <code class="computeroutput">
 <code class="prompt">root# </code> ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
@@ -265,7 +265,7 @@ sambaNextGroupRid: 67109863
 </pre><p>
 	If you have any problems, please read <a class="xref" href="ch-ldap-tls.html#s1-int-ldap-tls" title="Troubleshooting">the section called &#8220;Troubleshooting&#8221;</a>
 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="s1-int-ldap-tls"></a>Troubleshooting</h2></div></div></div><p>
-<a class="indexterm" name="id2692139"></a>
+<a class="indexterm" name="id2692275"></a>
 The most common error when configuring TLS, as I have already mentioned numerous times, is that the
 <span class="emphasis"><em>Common Name (CN)</em></span> you entered in <a class="xref" href="ch-ldap-tls.html#s1-config-ldap-tls-server" title="Generating the Server Certificate">the section called &#8220;Generating the Server Certificate&#8221;</a> is
 <span class="emphasis"><em>NOT</em></span> the Fully Qualified Domain Name (FQDN) of your ldap server.
@@ -275,13 +275,13 @@ your have the wrong permissions on the <code class="filename">servercrt.pem</cod
 files. They should be set with <code class="literal">chmod 640</code>, as per <a class="xref" href="ch-ldap-tls.html#s1-config-ldap-tls-install" title="Installing the Certificates">the section called &#8220;Installing the Certificates&#8221;</a>.
 </p><p>
 For anything else, it's best to read through your ldap logfile or join the <span class="application">OpenLDAP</span> mailing list.
-</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2691454" href="#id2691454" class="para">8</a>] </sup>We could however, get our generated server certificate signed by proper CAs, like <a class="ulink" href="http://www.thawte.com/" target="_top">Thawte</a> and <a class="ulink" href="http://www.verisign.com/" target="_top">VeriSign</a>, which
+</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2691590" href="#id2691590" class="para">8</a>] </sup>We could however, get our generated server certificate signed by proper CAs, like <a class="ulink" href="http://www.thawte.com/" target="_top">Thawte</a> and <a class="ulink" href="http://www.verisign.com/" target="_top">VeriSign</a>, which
 	you pay for, or the free ones, via <a class="ulink" href="http://www.cacert.org/" target="_top">CAcert</a>
-	</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691496" href="#id2691496" class="para">9</a>] </sup>The downside to
+	</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691632" href="#id2691632" class="para">9</a>] </sup>The downside to
 	making our own CA, is that the certificate is not automatically recognized by clients, like the commercial
-	ones are.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691515" href="#id2691515" class="para">10</a>] </sup>For information straight from the
+	ones are.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691651" href="#id2691651" class="para">10</a>] </sup>For information straight from the
 	horse's mouth, please visit <a class="ulink" href="http://www.openssl.org/docs/HOWTO/" target="_top">http://www.openssl.org/docs/HOWTO/</a>; the main OpenSSL
-	site.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691591" href="#id2691591" class="para">11</a>] </sup>Your <code class="filename">CA.pl</code> or <code class="filename">CA.sh</code> might not be
+	site.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2691727" href="#id2691727" class="para">11</a>] </sup>Your <code class="filename">CA.pl</code> or <code class="filename">CA.sh</code> might not be
 	in the same location as mine is, you can find it by using the <code class="literal">locate</code> command, i.e.,
 	<code class="literal">locate CA.pl</code>.  If the command complains about the database being too old, run
-	<code class="literal">updatedb</code> as <span class="emphasis"><em>root</em></span> to update it.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2692041" href="#id2692041" class="para">12</a>] </sup>See <code class="literal">man ldapsearch</code></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="speed.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="ch47.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�45.�Samba Performance Tuning�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�47.�Samba Support</td></tr></table></div></body></html>
+	<code class="literal">updatedb</code> as <span class="emphasis"><em>root</em></span> to update it.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2692177" href="#id2692177" class="para">12</a>] </sup>See <code class="literal">man ldapsearch</code></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="speed.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="ch47.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�45.�Samba Performance Tuning�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�47.�Samba Support</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/ch47.html b/docs/htmldocs/Samba3-HOWTO/ch47.html
index 380fed8615..9f4bb75868 100644
--- a/docs/htmldocs/Samba3-HOWTO/ch47.html
+++ b/docs/htmldocs/Samba3-HOWTO/ch47.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�47.�Samba Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="ch-ldap-tls.html" title="Chapter�46.�LDAP and Transport Layer Security"><link rel="next" href="DNSDHCP.html" title="Chapter�48.�DNS and DHCP Configuration Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�47.�Samba Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch-ldap-tls.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="DNSDHCP.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2692220"></a>Chapter�47.�Samba Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch47.html#id2692350">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692569">Commercial Support</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2692230"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�47.�Samba Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="ch-ldap-tls.html" title="Chapter�46.�LDAP and Transport Layer Security"><link rel="next" href="DNSDHCP.html" title="Chapter�48.�DNS and DHCP Configuration Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�47.�Samba Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch-ldap-tls.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="DNSDHCP.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2692356"></a>Chapter�47.�Samba Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ch47.html#id2692487">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692705">Commercial Support</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2692366"></a>
 One of the most difficult to answer questions in the information technology industry is, &#8220;<span class="quote">What is
 support?</span>&#8221;. That question irritates some folks, as much as common answers may annoy others.
 </p><p>
-<a class="indexterm" name="id2692246"></a>
+<a class="indexterm" name="id2692382"></a>
 The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
 an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
 &#8220;<span class="quote">Oh, Linux? We do not support Linux!</span>&#8221;. It has happened to me, and similar situations happen
@@ -15,50 +15,50 @@ One way to consider support is to view it as consisting of the right answer, in
 at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
 inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
 </p><p>
-<a class="indexterm" name="id2692277"></a>
-<a class="indexterm" name="id2692284"></a>
-<a class="indexterm" name="id2692291"></a>
+<a class="indexterm" name="id2692413"></a>
+<a class="indexterm" name="id2692420"></a>
+<a class="indexterm" name="id2692427"></a>
 One of the forces that has become a driving force for the adoption of open source software is the fact that
 many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
 that have been found wanting for other reasons.
 </p><p>
-<a class="indexterm" name="id2692306"></a>
-<a class="indexterm" name="id2692312"></a>
+<a class="indexterm" name="id2692442"></a>
+<a class="indexterm" name="id2692449"></a>
 In recognition of the need for needs satisfaction as the primary experience an information technology user or
 consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
 in respect of problem resolution.
 </p><p>
-<a class="indexterm" name="id2692327"></a>
-<a class="indexterm" name="id2692334"></a>
-<a class="indexterm" name="id2692340"></a>
+<a class="indexterm" name="id2692463"></a>
+<a class="indexterm" name="id2692470"></a>
+<a class="indexterm" name="id2692477"></a>
 In the open source software arena there are two support options: free support and paid-for (commercial)
 support.
-</p><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692350"></a>Free Support</h2></div></div></div><p>
-<a class="indexterm" name="id2692358"></a>
-<a class="indexterm" name="id2692365"></a>
-<a class="indexterm" name="id2692372"></a>
-<a class="indexterm" name="id2692379"></a>
-<a class="indexterm" name="id2692386"></a>
-<a class="indexterm" name="id2692393"></a>
+</p><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692487"></a>Free Support</h2></div></div></div><p>
+<a class="indexterm" name="id2692495"></a>
+<a class="indexterm" name="id2692502"></a>
+<a class="indexterm" name="id2692509"></a>
+<a class="indexterm" name="id2692516"></a>
+<a class="indexterm" name="id2692522"></a>
+<a class="indexterm" name="id2692529"></a>
 	Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
 	facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
 	supported mutual assistance.
 	</p><p>
-<a class="indexterm" name="id2692407"></a>
-<a class="indexterm" name="id2692414"></a>
-<a class="indexterm" name="id2692421"></a>
-<a class="indexterm" name="id2692428"></a>
-<a class="indexterm" name="id2692435"></a>
+<a class="indexterm" name="id2692544"></a>
+<a class="indexterm" name="id2692550"></a>
+<a class="indexterm" name="id2692557"></a>
+<a class="indexterm" name="id2692564"></a>
+<a class="indexterm" name="id2692571"></a>
 	The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
 	Information regarding subscription to the Samba mailing list can be found on the Samba <a class="ulink" href="https://lists.samba.org/mailman/" target="_top">web</a> site. The public mailing list that can be used to obtain
 	free, user contributed, support is called the <code class="literal">samba</code> list. The email address for this list
 	is at <code class="literal">mail:samba@samba.org</code>.  Information regarding the Samba IRC channels may be found on
 	the Samba <a class="ulink" href="http://www.samba.org/samba.irc.html" target="_top">IRC</a> web page.
 	</p><p>
-<a class="indexterm" name="id2692476"></a>
-<a class="indexterm" name="id2692483"></a>
-<a class="indexterm" name="id2692490"></a>
-<a class="indexterm" name="id2692497"></a>
+<a class="indexterm" name="id2692612"></a>
+<a class="indexterm" name="id2692619"></a>
+<a class="indexterm" name="id2692626"></a>
+<a class="indexterm" name="id2692633"></a>
 	As a general rule, it is considered poor net behavior to contact a Samba Team member directly
 	for free support. Most active members of the Samba Team work exceptionally long hours to assist
 	users who have demonstrated a qualified problem. Some team members may respond to direct email
@@ -66,9 +66,9 @@ support.
 	Team members actually provide professional paid-for Samba support and it is therefore wise
 	to show appropriate discretion and reservation in all direct contact.
 	</p><p>
-<a class="indexterm" name="id2692516"></a>
-<a class="indexterm" name="id2692523"></a>
-<a class="indexterm" name="id2692530"></a>
+<a class="indexterm" name="id2692652"></a>
+<a class="indexterm" name="id2692659"></a>
+<a class="indexterm" name="id2692666"></a>
 	When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
 	a bug <a class="ulink" href="https://bugzilla.samba.org/" target="_top">report</a>. All such reports are mailed to
 	the responsible code maintainer for action. The better the report, and the more serious it is,
@@ -76,16 +76,16 @@ support.
 	the reported bug it is likely to be rejected. It is up to you to provide sufficient information
 	that will permit the problem to be reproduced.
 	</p><p>
-<a class="indexterm" name="id2692555"></a>
+<a class="indexterm" name="id2692691"></a>
 	We all recognize that sometimes free support does not provide the answer that is sought within
 	the time-frame required. At other times the problem is elusive and you may lack the experience
 	necessary to isolate the problem and thus to resolve it. This is a situation where is may be
 	prudent to purchase paid-for support.
-	</p></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692569"></a>Commercial Support</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2692705"></a>Commercial Support</h2></div></div></div><p>
 	There are six basic support oriented services that are most commonly sought by Samba sites:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Assistance with network design</p></li><li><p>Staff Training</p></li><li><p>Assistance with Samba network deployment and installation</p></li><li><p>Priority telephone or email Samba configuration assistance</p></li><li><p>Trouble-shooting and diagnostic assistance</p></li><li><p>Provision of quality assured ready-to-install Samba binary packages</p></li></ul></div><p>
-<a class="indexterm" name="id2692616"></a>
-<a class="indexterm" name="id2692623"></a>
+<a class="indexterm" name="id2692752"></a>
+<a class="indexterm" name="id2692759"></a>
 	Information regarding companies that provide professional Samba support can be obtained by performing a Google
 	search, as well as by reference to the Samba <a class="ulink" href="http://www.samba.org/samba/support.html" target="_top">Support</a> web page. Companies who notify the Samba Team
 	that they provide commercial support are given a free listing that is sorted by the country of origin.
@@ -93,13 +93,13 @@ support.
 	provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
 	them.
 	</p><p>
-<a class="indexterm" name="id2692649"></a>
+<a class="indexterm" name="id2692785"></a>
 	The policy within the Samba Team is to treat all commercial support providers equally and to show no
 	preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
 	You are encouraged to obtain the services needed from a company in your local area. The open source movement
 	is pro-community; so do what you can to help a local business to prosper.
 	</p><p>
-<a class="indexterm" name="id2692666"></a>
+<a class="indexterm" name="id2692802"></a>
 	Open source software support can be found in any quality, at any price and in any place you can
 	to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
 	suffering in the mistaken belief that Samba is unsupported software  it is supported.
diff --git a/docs/htmldocs/Samba3-HOWTO/classicalprinting.html b/docs/htmldocs/Samba3-HOWTO/classicalprinting.html
index 542cfaef3b..139b3001e3 100644
--- a/docs/htmldocs/Samba3-HOWTO/classicalprinting.html
+++ b/docs/htmldocs/Samba3-HOWTO/classicalprinting.html
@@ -1,22 +1,22 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�21.�Classical Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="msdfs.html" title="Chapter�20.�Hosting a Microsoft Distributed File System Tree"><link rel="next" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�21.�Classical Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="classicalprinting"></a>Chapter�21.�Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="orgname">Danka Deutschland GmbH</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622075">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622298">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622450">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622610">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623480">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623935">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626941">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627479">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627627">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627720">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629667">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629683">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630248">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630366">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630540">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630560">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630928">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631184">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631444">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631557">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631819">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631928">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2631965">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632011">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632045">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632061">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632078">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632212">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632486">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632524">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632673">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632702">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632708">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632749">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622075"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2622083"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�21.�Classical Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="msdfs.html" title="Chapter�20.�Hosting a Microsoft Distributed File System Tree"><link rel="next" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�21.�Classical Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="classicalprinting"></a>Chapter�21.�Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="orgname">Danka Deutschland GmbH</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622118">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622341">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622493">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622653">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623534">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623989">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626995">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627533">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627675">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627768">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629701">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629717">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630283">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630401">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630574">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630595">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630963">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631219">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631479">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631592">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631902">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632011">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632048">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632094">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632128">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632144">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632162">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632295">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632569">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632608">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632756">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632786">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632791">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632833">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622118"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2622126"></a>
 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 class="indexterm" name="id2622096"></a>
-<a class="indexterm" name="id2622103"></a>
-<a class="indexterm" name="id2622110"></a>
-<a class="indexterm" name="id2622117"></a>
-<a class="indexterm" name="id2622124"></a>
-<a class="indexterm" name="id2622131"></a>
-<a class="indexterm" name="id2622138"></a>
-<a class="indexterm" name="id2622145"></a>
-<a class="indexterm" name="id2622152"></a>
-<a class="indexterm" name="id2622159"></a>
-<a class="indexterm" name="id2622166"></a>
-<a class="indexterm" name="id2622173"></a>
-<a class="indexterm" name="id2622180"></a>
-<a class="indexterm" name="id2622187"></a>
+<a class="indexterm" name="id2622139"></a>
+<a class="indexterm" name="id2622146"></a>
+<a class="indexterm" name="id2622153"></a>
+<a class="indexterm" name="id2622160"></a>
+<a class="indexterm" name="id2622167"></a>
+<a class="indexterm" name="id2622174"></a>
+<a class="indexterm" name="id2622181"></a>
+<a class="indexterm" name="id2622188"></a>
+<a class="indexterm" name="id2622195"></a>
+<a class="indexterm" name="id2622202"></a>
+<a class="indexterm" name="id2622209"></a>
+<a class="indexterm" name="id2622216"></a>
+<a class="indexterm" name="id2622223"></a>
+<a class="indexterm" name="id2622230"></a>
 A Samba print service may be run on a standalone or domain member server, side by side with file serving
 functions, or on a dedicated print server.  It can be made as tightly or as loosely secured as needs dictate.
 Configurations may be simple or complex. Available authentication schemes are essentially the same as
@@ -30,23 +30,23 @@ efficient in case of large numbers of printers. If a central accounting of print
 page and supplying the raw data for all sorts of statistical reports) is required, this function is best
 supported by the newer Common UNIX Printing System (CUPS) as the print subsystem underneath the Samba hood.
 </p><p>
-<a class="indexterm" name="id2622238"></a>
-<a class="indexterm" name="id2622244"></a>
+<a class="indexterm" name="id2622280"></a>
+<a class="indexterm" name="id2622287"></a>
 This chapter outlines the fundamentals of Samba printing as implemented by the more traditional UNIX
 BSD- and System V-style printing systems. Much of the information in this chapter applies also to CUPS.  If
 you use CUPS, you may be tempted to jump to the next chapter, but you will certainly miss a few things if you
 do. For further information refer to <a class="link" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support">CUPS Printing Support</a>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2622270"></a>
-<a class="indexterm" name="id2622277"></a>
-<a class="indexterm" name="id2622284"></a>
+<a class="indexterm" name="id2622313"></a>
+<a class="indexterm" name="id2622320"></a>
+<a class="indexterm" name="id2622326"></a>
 Most of the following examples have been verified on Windows XP Professional clients. Where this document
 describes the responses to commands given, bear in mind that Windows 200x/XP clients are quite similar but may
 differ in minor details. Windows NT4 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="id2622298"></a>Technical Introduction</h2></div></div></div><p>
-<a class="indexterm" name="id2622306"></a>
-<a class="indexterm" name="id2622313"></a>
-<a class="indexterm" name="id2622320"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622341"></a>Technical Introduction</h2></div></div></div><p>
+<a class="indexterm" name="id2622349"></a>
+<a class="indexterm" name="id2622356"></a>
+<a class="indexterm" name="id2622363"></a>
 Samba's printing support always relies on the installed print subsystem of the UNIX OS it runs on. Samba is a
 <code class="literal">middleman.</code> It takes print files from Windows (or other SMB) clients and passes them to the real
 printing system for further processing; therefore, it needs to communicate with both sides: the Windows print
@@ -54,42 +54,42 @@ clients and the UNIX printing system. Hence, we must differentiate between the v
 of which behave differently, as well as the various UNIX print subsystems, which themselves have different
 features and are accessed differently.
 </p><p>
-<a class="indexterm" name="id2622346"></a>
-<a class="indexterm" name="id2622353"></a>
+<a class="indexterm" name="id2622388"></a>
+<a class="indexterm" name="id2622395"></a>
 This chapter deals with the traditional way of UNIX printing. The next chapter covers in great detail the more
 modern CUPS.
 </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
-<a class="indexterm" name="id2622366"></a>
+<a class="indexterm" name="id2622409"></a>
 CUPS users, be warned: do not just jump on to the next chapter. You might miss important information only found here!
 </p></div><p>
-<a class="indexterm" name="id2622378"></a>
-<a class="indexterm" name="id2622385"></a>
-<a class="indexterm" name="id2622392"></a>
-<a class="indexterm" name="id2622399"></a>
+<a class="indexterm" name="id2622421"></a>
+<a class="indexterm" name="id2622428"></a>
+<a class="indexterm" name="id2622435"></a>
+<a class="indexterm" name="id2622442"></a>
 It is apparent from postings on the Samba mailing list that print configuration is one of the most problematic
 aspects of Samba administration today. Many new Samba administrators have the impression that Samba performs
 some sort of print processing. Rest assured, Samba does not perform any type of print processing. It does not
 do any form of print filtering.
 </p><p>
-<a class="indexterm" name="id2622415"></a>
-<a class="indexterm" name="id2622422"></a>
-<a class="indexterm" name="id2622429"></a>
-<a class="indexterm" name="id2622436"></a>
+<a class="indexterm" name="id2622458"></a>
+<a class="indexterm" name="id2622465"></a>
+<a class="indexterm" name="id2622472"></a>
+<a class="indexterm" name="id2622479"></a>
 Samba obtains from its clients a data stream (print job) that it spools to a local spool area. When the entire
 print job has been received, Samba invokes a local UNIX/Linux print command and passes the spooled file to it.
 It is up to the local system printing subsystems to correctly process the print job and to submit it to the
 printer.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622450"></a>Client to Samba Print Job Processing</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622493"></a>Client to Samba Print Job Processing</h3></div></div></div><p>
 Successful printing from a Windows client via a Samba print server to a UNIX
 printer involves six (potentially seven) 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 print file over the network
 	into Samba's spooling area.</p></li><li><p>Windows closes the connection.</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 print file may need to be explicitly deleted
 	from the Samba spooling area. This item depends on your print spooler
-	configuration settings.</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622509"></a>Printing-Related Configuration Parameters</h3></div></div></div><p>
-<a class="indexterm" name="id2622518"></a>
-<a class="indexterm" name="id2622524"></a>
-<a class="indexterm" name="id2622531"></a>
+	configuration settings.</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622552"></a>Printing-Related Configuration Parameters</h3></div></div></div><p>
+<a class="indexterm" name="id2622560"></a>
+<a class="indexterm" name="id2622567"></a>
+<a class="indexterm" name="id2622574"></a>
 There are a number of configuration parameters to control Samba's printing behavior. Please refer to the man
 page for <code class="filename">smb.conf</code> for an overview of 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.
@@ -103,20 +103,20 @@ page for <code class="filename">smb.conf</code> for an overview of these. As wit
 		or service-level shares (provided they do not have a different
 		setting defined for the same parameter, thus overriding the
 		global default).
-		</p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622610"></a>Simple Print Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2622618"></a>
-<a class="indexterm" name="id2622625"></a>
-<a class="indexterm" name="id2622632"></a>
-<a class="indexterm" name="id2622639"></a>
+		</p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622653"></a>Simple Print Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2622661"></a>
+<a class="indexterm" name="id2622668"></a>
+<a class="indexterm" name="id2622675"></a>
+<a class="indexterm" name="id2622682"></a>
 <a class="link" href="classicalprinting.html#simpleprc" title="Example�21.1.�Simple Configuration with BSD Printing">Simple Configuration with BSD Printing</a> shows a simple printing configuration.
 If you compare this with your own, you may find additional parameters that have been preconfigured by your OS
 vendor. Following is a discussion and explanation of the parameters. This example does not use many
 parameters.  However, in many environments these are enough to provide a valid <code class="filename">smb.conf</code> file that enables
 all clients to print.
-</p><div class="example"><a name="simpleprc"></a><p class="title"><b>Example�21.1.�Simple Configuration with BSD Printing</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2622691"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id2622702"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2622723"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2622735"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2622746"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2622758"></a><em class="parameter"><code>writable = no</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2622773"></a>
-<a class="indexterm" name="id2622779"></a>
-<a class="indexterm" name="id2622786"></a>
+</p><div class="example"><a name="simpleprc"></a><p class="title"><b>Example�21.1.�Simple Configuration with BSD Printing</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2622733"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id2622745"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2622766"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2622777"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2622789"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2622800"></a><em class="parameter"><code>writable = no</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2622815"></a>
+<a class="indexterm" name="id2622822"></a>
+<a class="indexterm" name="id2622829"></a>
 This is only an example configuration. Samba assigns default values to all configuration parameters. The
 defaults are conservative and sensible. When a parameter is specified in the <code class="filename">smb.conf</code> file, this overwrites
 the default value. The <code class="literal">testparm</code> utility when run as root is capable of reporting all
@@ -124,26 +124,26 @@ settings, both default as well as <code class="filename">smb.conf</code> file se
 misconfigured settings. The complete output is easily 360 lines and more, so you may want to pipe it through a
 pager program.
 </p><p>  
-<a class="indexterm" name="id2622829"></a>
-<a class="indexterm" name="id2622836"></a>
-<a class="indexterm" name="id2622843"></a>
+<a class="indexterm" name="id2622871"></a>
+<a class="indexterm" name="id2622878"></a>
+<a class="indexterm" name="id2622886"></a>
 The syntax for the configuration file is easy to grasp. You should know that  is not very picky about its
 syntax. As has been explained elsewhere in this book, Samba tolerates some spelling errors (such as
 <a class="link" href="smb.conf.5.html#BROWSEABLE" target="_top">browseable</a> instead of <a class="link" href="smb.conf.5.html#BROWSABLE" target="_top">browsable</a>), and spelling is
 case-insensitive. It is permissible to use <em class="parameter"><code>Yes/No</code></em> or <em class="parameter"><code>True/False</code></em>
 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="id2622894"></a>Verifying Configuration with <code class="literal">testparm</code></h3></div></div></div><p>
-<a class="indexterm" name="id2622907"></a>
-<a class="indexterm" name="id2622914"></a>
-<a class="indexterm" name="id2622920"></a>
-<a class="indexterm" name="id2622927"></a>
-<a class="indexterm" name="id2622934"></a>
-<a class="indexterm" name="id2622941"></a>
-<a class="indexterm" name="id2622948"></a>
-<a class="indexterm" name="id2622954"></a>
-<a class="indexterm" name="id2622961"></a>
-<a class="indexterm" name="id2622968"></a>
-<a class="indexterm" name="id2622975"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622937"></a>Verifying Configuration with <code class="literal">testparm</code></h3></div></div></div><p>
+<a class="indexterm" name="id2622949"></a>
+<a class="indexterm" name="id2622956"></a>
+<a class="indexterm" name="id2622963"></a>
+<a class="indexterm" name="id2622970"></a>
+<a class="indexterm" name="id2622977"></a>
+<a class="indexterm" name="id2622983"></a>
+<a class="indexterm" name="id2622990"></a>
+<a class="indexterm" name="id2622997"></a>
+<a class="indexterm" name="id2623004"></a>
+<a class="indexterm" name="id2623011"></a>
+<a class="indexterm" name="id2623018"></a>
 To see all (or at least most) printing-related settings in Samba, including the implicitly used ones, try the
 command outlined below. This command greps for all occurrences of <code class="constant">lp</code>,
 <code class="constant">print</code>, <code class="constant">spool</code>, <code class="constant">driver</code>,
@@ -194,11 +194,11 @@ may be important in your future dealings with Samba.</em></span>
 The <code class="literal">testparm</code> in Samba-3 behaves differently from that in 2.2.x: used without the
 &#8220;<span class="quote">-v</span>&#8221; switch, it only shows you the settings actually written into! To see the complete
 configuration used, add the &#8220;<span class="quote">-v</span>&#8221; parameter to testparm.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2623091"></a>Rapid Configuration Validation</h3></div></div></div><p> 
-<a class="indexterm" name="id2623100"></a>
-<a class="indexterm" name="id2623107"></a>
-<a class="indexterm" name="id2623113"></a>
-<a class="indexterm" name="id2623120"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2623134"></a>Rapid Configuration Validation</h3></div></div></div><p> 
+<a class="indexterm" name="id2623142"></a>
+<a class="indexterm" name="id2623149"></a>
+<a class="indexterm" name="id2623156"></a>
+<a class="indexterm" name="id2623163"></a>
 Should you need to troubleshoot at any stage, please always come back to this point first and verify if
 <code class="literal">testparm</code> shows the parameters you expect. To give you a warning from personal experience,
 try to just comment out the <a class="link" href="smb.conf.5.html#LOADPRINTERS" target="_top">load printers</a> parameter. If your 2.2.x system behaves like
@@ -211,8 +211,8 @@ mine, you'll see this:
 <code class="prompt">root# </code>testparm -v /etc/samba/smb.conf | egrep "(load printers)"
         load printers = Yes
 </pre><p>
-<a class="indexterm" name="id2623176"></a>
-<a class="indexterm" name="id2623183"></a>
+<a class="indexterm" name="id2623219"></a>
+<a class="indexterm" name="id2623226"></a>
 I assumed that commenting out of this setting should prevent Samba from
 publishing my printers, but it still did. It took some time to figure out
 the reason. But I am no longer fooled ... at least not by this.
@@ -226,7 +226,7 @@ the reason. But I am no longer fooled ... at least not by this.
 <code class="prompt">root# </code><strong class="userinput"><code>testparm -s -v smb.conf.simpleprinting | egrep "(load printers)"</code></strong>
         load printers = No
 </pre><p>
-<a class="indexterm" name="id2623227"></a>
+<a class="indexterm" name="id2623270"></a>
 Only when the parameter is explicitly set to <a class="link" href="smb.conf.5.html#LOADPRINTERS" target="_top">load printers = No</a> would
 Samba conform with 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 parameters explicitly as you intend them to
@@ -237,8 +237,8 @@ The following is the most minimal configuration file:
 <code class="prompt">root# </code><strong class="userinput"><code>cat /etc/samba/smb.conf-minimal</code></strong>
         [printers]
 </pre><p>
-<a class="indexterm" name="id2623295"></a>
-<a class="indexterm" name="id2623302"></a>
+<a class="indexterm" name="id2623338"></a>
+<a class="indexterm" name="id2623345"></a>
 This example should show that you can use <code class="literal">testparm</code> to test any Samba configuration file.
 Actually, we encourage you <span class="emphasis"><em>not</em></span> to change your working system (unless you know exactly
 what you are doing). Don't rely on the assumption that changes will only take effect after you restart smbd!
@@ -276,10 +276,10 @@ be if you used this minimalistic configuration. Here is what you can expect to f
 </pre><p>
 <code class="literal">testparm</code> issued two warnings:
 </p><div class="itemizedlist"><ul type="disc"><li><p>We did not specify the <em class="parameter"><code>[printers]</code></em> section as printable.</p></li><li><p>We did not tell Samba which spool directory to use.</p></li></ul></div><p>
-<a class="indexterm" name="id2623395"></a>
-<a class="indexterm" name="id2623402"></a>
-<a class="indexterm" name="id2623407"></a>
-<a class="indexterm" name="id2623413"></a>
+<a class="indexterm" name="id2623449"></a>
+<a class="indexterm" name="id2623456"></a>
+<a class="indexterm" name="id2623461"></a>
+<a class="indexterm" name="id2623467"></a>
 However, this was not fatal, and Samba will default to values that will work. Please, do not rely on this and
 do not use this example. This was included to encourage you to be careful to design and specify your setup to
 do precisely what you require. The outcome on your system may vary for some parameters given, since Samba may
@@ -288,15 +288,15 @@ have been built with  different compile-time options. <span class="emphasis"><em
 put the comment sign at the front). At first I regarded this as a bug in my Samba versions. But the man page
 clearly says: <code class="literal">Internal whitespace in a parameter value is retained verbatim.</code> 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><a class="indexterm" name="id2623453"></a><em class="parameter"><code>printing =  lprng</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td># This defines LPRng as the printing system</td></tr><tr><td><a class="indexterm" name="id2623507"></a><em class="parameter"><code>printing =  lprng</code></em></td></tr></table><p>
 </p><p>
 will regard the whole of the string after the <code class="literal">=</code> sign as the value you want to define. This
 is an invalid value that will be ignored, and a default value will be used in its place.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2623480"></a>Extended Printing Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2623488"></a>
-<a class="indexterm" name="id2623495"></a>
-<a class="indexterm" name="id2623502"></a>
-<a class="indexterm" name="id2623508"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2623534"></a>Extended Printing Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2623542"></a>
+<a class="indexterm" name="id2623549"></a>
+<a class="indexterm" name="id2623556"></a>
+<a class="indexterm" name="id2623563"></a>
 <a class="link" href="classicalprinting.html#extbsdpr" title="Example�21.2.�Extended BSD Printing Configuration">Extended BSD Printing Configuration</a> shows a more verbose configuration for
 print-related settings in a BSD-style printing environment. What follows is a discussion and explanation of
 the various parameters. We chose to use BSD-style printing here because it is still the most commonly used
@@ -304,22 +304,22 @@ system on legacy UNIX/Linux installations. New installations predominantly use C
 separate chapter. The example explicitly names many parameters that do not need to be specified because they
 are set by default. You could use a much leaner <code class="filename">smb.conf</code> file, or you can use <code class="literal">testparm</code> or
 <code class="literal">SWAT</code> to optimize the <code class="filename">smb.conf</code> file to remove all parameters that are set at default.
-</p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example�21.2.�Extended BSD Printing Configuration</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2623582"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id2623594"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623606"></a><em class="parameter"><code>show add printer wizard = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623618"></a><em class="parameter"><code>printcap name = /etc/printcap</code></em></td></tr><tr><td><a class="indexterm" name="id2623630"></a><em class="parameter"><code>printer admin = @ntadmin, root</code></em></td></tr><tr><td><a class="indexterm" name="id2623642"></a><em class="parameter"><code>max print jobs = 100</code></em></td></tr><tr><td><a class="indexterm" name="id2623654"></a><em class="parameter"><code>lpq cache time = 20</code></em></td></tr><tr><td><a class="indexterm" name="id2623665"></a><em class="parameter"><code>use client driver = no</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2623686"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2623698"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623710"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2623721"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2623733"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623744"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623756"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623768"></a><em class="parameter"><code>writable = no       </code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[my_printer_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2623788"></a><em class="parameter"><code>comment = Printer with Restricted Access</code></em></td></tr><tr><td><a class="indexterm" name="id2623800"></a><em class="parameter"><code>path = /var/spool/samba_my_printer</code></em></td></tr><tr><td><a class="indexterm" name="id2623812"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2623824"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623836"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623847"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2623859"></a><em class="parameter"><code>hosts allow = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2623871"></a><em class="parameter"><code>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr><tr><td><a class="indexterm" name="id2623883"></a><em class="parameter"><code>guest ok = no</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2623897"></a>
-<a class="indexterm" name="id2623902"></a>
-<a class="indexterm" name="id2623908"></a>
+</p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example�21.2.�Extended BSD Printing Configuration</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2623636"></a><em class="parameter"><code>printing = bsd</code></em></td></tr><tr><td><a class="indexterm" name="id2623648"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623660"></a><em class="parameter"><code>show add printer wizard = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623672"></a><em class="parameter"><code>printcap name = /etc/printcap</code></em></td></tr><tr><td><a class="indexterm" name="id2623684"></a><em class="parameter"><code>printer admin = @ntadmin, root</code></em></td></tr><tr><td><a class="indexterm" name="id2623696"></a><em class="parameter"><code>max print jobs = 100</code></em></td></tr><tr><td><a class="indexterm" name="id2623708"></a><em class="parameter"><code>lpq cache time = 20</code></em></td></tr><tr><td><a class="indexterm" name="id2623720"></a><em class="parameter"><code>use client driver = no</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2623740"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2623752"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623764"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2623775"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2623787"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623799"></a><em class="parameter"><code>public = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623810"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623822"></a><em class="parameter"><code>writable = no       </code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[my_printer_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2623843"></a><em class="parameter"><code>comment = Printer with Restricted Access</code></em></td></tr><tr><td><a class="indexterm" name="id2623855"></a><em class="parameter"><code>path = /var/spool/samba_my_printer</code></em></td></tr><tr><td><a class="indexterm" name="id2623866"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2623878"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623890"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2623902"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2623913"></a><em class="parameter"><code>hosts allow = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2623925"></a><em class="parameter"><code>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr><tr><td><a class="indexterm" name="id2623937"></a><em class="parameter"><code>guest ok = no</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2623951"></a>
+<a class="indexterm" name="id2623956"></a>
+<a class="indexterm" name="id2623962"></a>
 This is an example configuration. You may not find all the settings that are in the configuration file that
 was provided by the OS vendor. Samba configuration parameters, if not explicitly set, default to a sensible
 value.  To see all settings, as <code class="constant">root</code> use the <code class="literal">testparm</code> utility.
 <code class="literal">testparm</code> gives warnings for misconfigured settings.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2623935"></a>Detailed Explanation Settings</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2623989"></a>Detailed Explanation Settings</h3></div></div></div><p>
 The following is a discussion of the settings from <a class="link" href="classicalprinting.html#extbsdpr" title="Example�21.2.�Extended BSD Printing Configuration">Extended BSD Printing
 Configuration</a> <a class="link" href="classicalprinting.html#extbsdpr" title="Example�21.2.�Extended BSD Printing Configuration">Extended BSD Printing Configuration</a>.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2623959"></a>The [global] Section</h4></div></div></div><p>
-<a class="indexterm" name="id2623967"></a>
-<a class="indexterm" name="id2623974"></a>
-<a class="indexterm" name="id2623981"></a>
-<a class="indexterm" name="id2623988"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2624014"></a>The [global] Section</h4></div></div></div><p>
+<a class="indexterm" name="id2624022"></a>
+<a class="indexterm" name="id2624028"></a>
+<a class="indexterm" name="id2624035"></a>
+<a class="indexterm" name="id2624042"></a>
 The <em class="parameter"><code>[global]</code></em> section is one of four special sections (along with <em class="parameter"><code>[homes]</code></em>, <em class="parameter"><code>[printers]</code></em>, and <em class="parameter"><code>[print$]</code></em>). The
 <em class="parameter"><code>[global]</code></em> contains all parameters that apply to the server as a whole. It is the place
 for parameters that have only a global meaning. It may also contain service-level parameters that define
@@ -327,33 +327,33 @@ default settings for all other sections and shares. This way you can simplify th
 setting the same value repeatedly. (Within each individual section or share, you may, however, override these
 globally set share settings and specify other values).
 </p><div class="variablelist"><dl><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd </a></span></dt><dd><p>
-<a class="indexterm" name="id2624055"></a>
-<a class="indexterm" name="id2624062"></a>
-<a class="indexterm" name="id2624068"></a>
-<a class="indexterm" name="id2624075"></a>
-<a class="indexterm" name="id2624082"></a>
-<a class="indexterm" name="id2624089"></a>
-<a class="indexterm" name="id2624096"></a>
-<a class="indexterm" name="id2624103"></a>
 <a class="indexterm" name="id2624109"></a>
 <a class="indexterm" name="id2624116"></a>
 <a class="indexterm" name="id2624123"></a>
-<a class="indexterm" name="id2624130"></a>
+<a class="indexterm" name="id2624129"></a>
+<a class="indexterm" name="id2624136"></a>
+<a class="indexterm" name="id2624143"></a>
+<a class="indexterm" name="id2624150"></a>
+<a class="indexterm" name="id2624157"></a>
+<a class="indexterm" name="id2624164"></a>
+<a class="indexterm" name="id2624170"></a>
+<a class="indexterm" name="id2624177"></a>
+<a class="indexterm" name="id2624184"></a>
 		Causes Samba to use default print commands applicable for the BSD (also known as RFC 1179 style or LPR/LPD)
 		printing system. In general, the <em class="parameter"><code>printing</code></em> 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="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> (and other queue control commands).
 		</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>
-<a class="indexterm" name="id2624166"></a>
-<a class="indexterm" name="id2624172"></a>
+<a class="indexterm" name="id2624220"></a>
+<a class="indexterm" name="id2624226"></a>
 		The <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> parameter is normally a service-level parameter. Since it is included
 		here in the <em class="parameter"><code>[global]</code></em> 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="link" href="smb.conf.5.html#LOADPRINTERS" target="_top">load printers = yes </a></span></dt><dd><p>
-<a class="indexterm" name="id2624220"></a>
-<a class="indexterm" name="id2624227"></a>
-<a class="indexterm" name="id2624233"></a>
-<a class="indexterm" name="id2624240"></a>
+<a class="indexterm" name="id2624275"></a>
+<a class="indexterm" name="id2624281"></a>
+<a class="indexterm" name="id2624287"></a>
+<a class="indexterm" name="id2624294"></a>
 		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
@@ -361,11 +361,11 @@ globally set share settings and specify other values).
 		<em class="parameter"><code>load printers = no</code></em> setting will allow you to specify each UNIX printer you want to
 		share separately, leaving out some you do not want to be publicly visible and available).
 		</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#SHOWADDPRINTERWIZARD" target="_top">show add printer wizard = yes </a></span></dt><dd><p>
-<a class="indexterm" name="id2624289"></a>
-<a class="indexterm" name="id2624295"></a>
-<a class="indexterm" name="id2624302"></a>
-<a class="indexterm" name="id2624308"></a>
-<a class="indexterm" name="id2624315"></a>
+<a class="indexterm" name="id2624343"></a>
+<a class="indexterm" name="id2624349"></a>
+<a class="indexterm" name="id2624356"></a>
+<a class="indexterm" name="id2624362"></a>
+<a class="indexterm" name="id2624369"></a>
 		Setting is normally enabled by default (even if the parameter is not specified in <code class="filename">smb.conf</code>).  It causes the
 		<span class="guiicon">Add Printer Wizard</span> icon to appear in the <span class="guiicon">Printers</span> folder of the Samba
 		host's share listing (as shown in <span class="guiicon">Network Neighborhood</span> or by the <code class="literal">net
@@ -374,23 +374,23 @@ globally set share settings and specify other values).
 		the <em class="parameter"><code>[print$]</code></em> share and associate it with a printer (if the respective queue exists
 		before the action), or exchange a printer's driver for any other previously uploaded driver.
 		</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#MAXPRINTJOBS" target="_top">max print jobs = 100 </a></span></dt><dd><p>
-<a class="indexterm" name="id2624398"></a>
+<a class="indexterm" name="id2624452"></a>
 		Sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client
 		submit a job that exceeds this number, a "no more space available on server" type of error message will be
 		returned by Samba to the client. A setting of zero (the default) means there is <span class="emphasis"><em>no</em></span> limit
 		at all.
 		</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTCAPNAME" target="_top">printcap name = /etc/printcap </a></span></dt><dd><p>
-<a class="indexterm" name="id2624434"></a>
-<a class="indexterm" name="id2624440"></a>
-<a class="indexterm" name="id2624446"></a>
+<a class="indexterm" name="id2624488"></a>
+<a class="indexterm" name="id2624494"></a>
+<a class="indexterm" name="id2624500"></a>
 		Tells Samba where to look for a list of available printer names. Where CUPS is used, make sure that a printcap
 		file is written. This is controlled by the <code class="constant">Printcap</code> directive in the
 		<code class="filename">cupsd.conf</code> file.
 	</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin = @ntadmin </a></span></dt><dd><p>
-<a class="indexterm" name="id2624485"></a>
-<a class="indexterm" name="id2624491"></a>
-<a class="indexterm" name="id2624498"></a>
-<a class="indexterm" name="id2624504"></a>
+<a class="indexterm" name="id2624539"></a>
+<a class="indexterm" name="id2624545"></a>
+<a class="indexterm" name="id2624552"></a>
+<a class="indexterm" name="id2624558"></a>
 		Members of the ntadmin group should be able to add drivers and set printer properties
 		(<code class="constant">ntadmin</code> is only an example name; it needs to be a valid UNIX group name); root is
 		implicitly always a <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a>. The <code class="literal">@</code> sign precedes group names
@@ -399,20 +399,20 @@ globally set share settings and specify other values).
 		Samba-2.2</a>).  In larger installations, the <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> parameter is normally a
 		per-share parameter. This permits different groups to administer each printer share.
 	</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#LPQCACHETIME" target="_top">lpq cache time = 20 </a></span></dt><dd><p>
-<a class="indexterm" name="id2624585"></a>
-<a class="indexterm" name="id2624591"></a>
+<a class="indexterm" name="id2624639"></a>
+<a class="indexterm" name="id2624645"></a>
 		Controls the cache time for the results of the lpq command. It prevents the lpq command being called too often
 		and reduces the load on a heavily used print server.
 	</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#USECLIENTDRIVER" target="_top">use client driver = no </a></span></dt><dd><p>
-<a class="indexterm" name="id2624620"></a>
+<a class="indexterm" name="id2624675"></a>
 		If set to <code class="constant">yes</code>, only takes effect for Windows NT/200x/XP clients (and not for Win
 		95/98/ME). Its default value is <code class="constant">No</code> (or <code class="constant">False</code>).  It must
 		<span class="emphasis"><em>not</em></span> be enabled on print shares (with a <code class="constant">yes</code> or
 		<code class="constant">true</code> setting) that have valid drivers installed on the Samba server. For more detailed
 		explanations, see the <code class="filename">smb.conf</code> man page.
 	</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="ptrsect"></a>The [printers] Section</h4></div></div></div><p>
-<a class="indexterm" name="id2624672"></a>
-<a class="indexterm" name="id2624679"></a>
+<a class="indexterm" name="id2624726"></a>
+<a class="indexterm" name="id2624733"></a>
 The printers section is the second special section. If a section with this name appears in the <code class="filename">smb.conf</code>,
 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 printer name it finds in the printcap file. You could regard this
@@ -468,9 +468,9 @@ Settings inside this container must be share-level parameters.
 		connection), but only via print spooling operations. Normal write operations are not permitted.
 		</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#WRITABLE" target="_top">writable = no </a></span></dt><dd><p>
 		Is a synonym for <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only = yes</a>.
-		</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625066"></a>Any [my_printer_name] Section</h4></div></div></div><p>
-<a class="indexterm" name="id2625074"></a>
-<a class="indexterm" name="id2625081"></a>
+		</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625120"></a>Any [my_printer_name] Section</h4></div></div></div><p>
+<a class="indexterm" name="id2625128"></a>
+<a class="indexterm" name="id2625135"></a>
 If a <em class="parameter"><code>[my_printer_name]</code></em> section appears in the <code class="filename">smb.conf</code> file, which includes the
 parameter <a class="link" href="smb.conf.5.html#PRINTABLE" target="_top">printable = yes</a> Samba will configure it as a printer share.
 Windows 9x/Me clients may have problems with connecting or loading printer drivers if the share name has more
@@ -502,11 +502,11 @@ finds one, it will connect to this and will not connect to a printer with the sa
 		you can see, you could name IP addresses as well as NetBIOS hostnames here.
 		</p></dd><dt><span class="term"><a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok = no </a></span></dt><dd><p>
 		This printer is not open for the guest account.
-		</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625360"></a>Print Commands</h4></div></div></div><p>
-<a class="indexterm" name="id2625368"></a>
-<a class="indexterm" name="id2625375"></a>
-<a class="indexterm" name="id2625381"></a>
-<a class="indexterm" name="id2625388"></a>
+		</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625414"></a>Print Commands</h4></div></div></div><p>
+<a class="indexterm" name="id2625422"></a>
+<a class="indexterm" name="id2625429"></a>
+<a class="indexterm" name="id2625436"></a>
+<a class="indexterm" name="id2625442"></a>
 In each section defining a printer (or in the <em class="parameter"><code>[printers]</code></em> section),
 a <em class="parameter"><code>print command</code></em> parameter may be defined. It sets a command to process the files
 that have been placed into the Samba print spool directory for that printer. (That spool directory was,
@@ -518,8 +518,8 @@ command that just copies the print file to a temporary location for further inve
 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="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625436"></a>Default UNIX System Printing Commands</h4></div></div></div><p>
-<a class="indexterm" name="id2625444"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625491"></a>Default UNIX System Printing Commands</h4></div></div></div><p>
+<a class="indexterm" name="id2625498"></a>
 You learned earlier that Samba, in most cases, uses its built-in settings for many parameters if it cannot
 find an explicitly stated one in its configuration file. The same is true for the <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a>. The default print command varies depending on the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> parameter
 setting. In the commands listed in <a class="link" href="classicalprinting.html#printOptions" title="Table�21.1.�Default Printing Settings">Default Printing Settings</a> , you will
@@ -528,29 +528,29 @@ J</em></span>, and so on. These letters stand for printer name, spool file, and
 explained in more detail in <a class="link" href="classicalprinting.html#printOptions" title="Table�21.1.�Default Printing Settings">Default Printing Settings</a> presents an overview
 of key printing options but excludes the special case of CUPS, is discussed in <a class="link" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support">CUPS Printing Support</a>.
 </p><div class="table"><a name="printOptions"></a><p class="title"><b>Table�21.1.�Default Printing Settings</b></p><div class="table-contents"><table summary="Default Printing Settings" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Setting</th><th align="left">Default Printing Commands</th></tr></thead><tbody><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">print command is <code class="literal">lpr -r -P%p %s</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">print command is <code class="literal">lp -c -P%p %s; rm %s</code></td></tr><tr><td align="left"> <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">print command is <code class="literal">lp -r -P%p -s %s</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lpq command is <code class="literal">lpq -P%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lpq command is <code class="literal">lpstat -o%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lpq command is <code class="literal">lpq -P%p</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lprm command is <code class="literal">lprm -P%p %j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lprm command is <code class="literal">cancel %p-%j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lprm command is <code class="literal">cancel %p-%j</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lppause command is <code class="literal">lp -i %p-%j -H hold</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd|aix|lprng|plp</a></td><td align="left">lpresume command is <code class="literal">lp -i %p-%j -H resume</code></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv|hpux</a></td><td align="left">lpresume command   (...is empty)</td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = qnx</a></td><td align="left">lpresume command   (...is empty)</td></tr></tbody></table></div></div><br class="table-break"><p>
-<a class="indexterm" name="id2625908"></a>
-<a class="indexterm" name="id2625914"></a>
-<a class="indexterm" name="id2625921"></a>
-<a class="indexterm" name="id2625928"></a>
+<a class="indexterm" name="id2625962"></a>
+<a class="indexterm" name="id2625969"></a>
+<a class="indexterm" name="id2625975"></a>
+<a class="indexterm" name="id2625982"></a>
 For <em class="parameter"><code>printing = CUPS</code></em>, if Samba is compiled against libcups, it uses the CUPS API to
 submit jobs. (It is a good idea also to set <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a> in case your
 <code class="filename">cupsd.conf</code> 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; that is, it uses
 <code class="literal">lp -c -d%p -oraw; rm %s</code>. With <em class="parameter"><code>printing = cups</code></em>, and if Samba is
 compiled against libcups, any manually set print command will be ignored!
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2625981"></a>Custom Print Commands</h4></div></div></div><p>
-<a class="indexterm" name="id2625989"></a>
-<a class="indexterm" name="id2625996"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2626035"></a>Custom Print Commands</h4></div></div></div><p>
+<a class="indexterm" name="id2626043"></a>
+<a class="indexterm" name="id2626050"></a>
 After a print job has finished spooling to a service, the <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> will be used
 by Samba via a system() 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 may not remove the spool file on its own, so whatever command you specify, you should ensure
 that the spool file is deleted after it has been processed.
 </p><p>
-<a class="indexterm" name="id2626025"></a>
-<a class="indexterm" name="id2626032"></a>
-<a class="indexterm" name="id2626039"></a>
-<a class="indexterm" name="id2626046"></a>
+<a class="indexterm" name="id2626079"></a>
+<a class="indexterm" name="id2626086"></a>
+<a class="indexterm" name="id2626093"></a>
+<a class="indexterm" name="id2626100"></a>
 There is no difficulty with using your own customized print commands with the traditional printing systems.
 However, if you do not wish to roll your own, you should be well informed about the default built-in commands
 that Samba uses for each printing subsystem (see <a class="link" href="classicalprinting.html#printOptions" title="Table�21.1.�Default Printing Settings">Default Printing
@@ -560,28 +560,28 @@ names of real objects. At the time of running a command with such a placeholder,
 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><em class="parameter"><code>%s, %f</code></em>  the path to the spool file name.</p></li><li><p><em class="parameter"><code>%p</code></em>  the appropriate printer name.</p></li><li><p><em class="parameter"><code>%J</code></em>  the job name as transmitted by the client.</p></li><li><p><em class="parameter"><code>%c</code></em>  the number of printed pages of the spooled job (if known).</p></li><li><p><em class="parameter"><code>%z</code></em>  the size of the spooled print job (in bytes).</p></li></ul></div><p>
-<a class="indexterm" name="id2626145"></a>
+<a class="indexterm" name="id2626199"></a>
 The print command must contain at least one occurrence of <em class="parameter"><code>%s</code></em> or
 <em class="parameter"><code>%f</code></em>. The <em class="parameter"><code>%p</code></em> is optional. If no printer name is supplied,
 the <em class="parameter"><code>%p</code></em> will be silently removed from the print command. In this case, the job is
 sent to the default printer.
 </p><p>
-<a class="indexterm" name="id2626181"></a>
-<a class="indexterm" name="id2626188"></a>
+<a class="indexterm" name="id2626235"></a>
+<a class="indexterm" name="id2626242"></a>
 If specified in the <em class="parameter"><code>[global]</code></em> 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! Most importantly, print files will not be removed, so they will consume disk space.
 </p><p>
-<a class="indexterm" name="id2626210"></a>
-<a class="indexterm" name="id2626217"></a>
+<a class="indexterm" name="id2626264"></a>
+<a class="indexterm" name="id2626271"></a>
 Printing may fail on some UNIX systems when using the <span class="emphasis"><em>nobody</em></span> account. If this happens, create an
 alternative guest account and give it the privilege to print. Set up this guest account in the
 <em class="parameter"><code>[global]</code></em> section with the <em class="parameter"><code>guest account</code></em> parameter.
 </p><p>
-<a class="indexterm" name="id2626246"></a>
-<a class="indexterm" name="id2626254"></a>
-<a class="indexterm" name="id2626260"></a>
+<a class="indexterm" name="id2626301"></a>
+<a class="indexterm" name="id2626308"></a>
+<a class="indexterm" name="id2626315"></a>
 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 <em class="parameter"><code>$variable</code></em>
@@ -589,15 +589,15 @@ in the Samba print command is <em class="parameter"><code>%$variable</code></em>
 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> example, the following will log a print job
 to <code class="filename">/tmp/print.log</code>, print the file, then remove it. The semicolon (&#8220;<span class="quote">;</span>&#8221;
 is the usual separator for commands in shell scripts:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2626316"></a><em class="parameter"><code>print command = echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2626370"></a><em class="parameter"><code>print command = echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</code></em></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="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a>
 parameter varies depending on the setting of the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a>
 parameter. Another example is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2626366"></a><em class="parameter"><code>print command = /usr/local/samba/bin/myprintscript %p %s</code></em></td></tr></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cups-msrpc"></a>Printing Developments Since Samba-2.2</h2></div></div></div><p>
-<a class="indexterm" name="id2626393"></a>
-<a class="indexterm" name="id2626399"></a>
-<a class="indexterm" name="id2626406"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2626421"></a><em class="parameter"><code>print command = /usr/local/samba/bin/myprintscript %p %s</code></em></td></tr></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cups-msrpc"></a>Printing Developments Since Samba-2.2</h2></div></div></div><p>
+<a class="indexterm" name="id2626447"></a>
+<a class="indexterm" name="id2626454"></a>
+<a class="indexterm" name="id2626460"></a>
 Prior to Samba-2.2.x, print server support for Windows clients was limited to <span class="emphasis"><em>LanMan</em></span>
 printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers.
 Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These
@@ -606,67 +606,67 @@ MS-RPCs use the <span class="emphasis"><em>SPOOLSS</em></span> named pipe for al
 </p><p>
 The additional functionality provided by the new SPOOLSS support includes:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2626441"></a>
+<a class="indexterm" name="id2626496"></a>
 	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>
-<a class="indexterm" name="id2626458"></a>
+<a class="indexterm" name="id2626512"></a>
 	Uploading of printer drivers via the Windows NT <span class="emphasis"><em>Add Printer Wizard</em></span> (APW)
 	or the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> tool set.
 	</p></li><li><p>	
-<a class="indexterm" name="id2626481"></a>
-<a class="indexterm" name="id2626488"></a>
-<a class="indexterm" name="id2626495"></a>
-<a class="indexterm" name="id2626502"></a>
-<a class="indexterm" name="id2626509"></a>
+<a class="indexterm" name="id2626536"></a>
+<a class="indexterm" name="id2626542"></a>
+<a class="indexterm" name="id2626549"></a>
+<a class="indexterm" name="id2626556"></a>
+<a class="indexterm" name="id2626563"></a>
 	Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), and so on. (See the
 	<a class="ulink" href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a> for more information on the
 	Win32 printing API).
 	</p></li><li><p>
-<a class="indexterm" name="id2626529"></a>
-<a class="indexterm" name="id2626536"></a>
+<a class="indexterm" name="id2626583"></a>
+<a class="indexterm" name="id2626590"></a>
 	Support for NT Access Control Lists (ACL) on printer objects.
 	</p></li><li><p>
-<a class="indexterm" name="id2626548"></a>
+<a class="indexterm" name="id2626602"></a>
 	Improved support for printer queue manipulation through the use of internal databases for spooled
 	job information (implemented by various <code class="filename">*.tdb</code> files).
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2626568"></a>
-<a class="indexterm" name="id2626574"></a>
+<a class="indexterm" name="id2626622"></a>
+<a class="indexterm" name="id2626628"></a>
 A benefit of updating is that Samba-3 is able to publish its printers to Active Directory (or LDAP).
 </p><p>
-<a class="indexterm" name="id2626586"></a>
+<a class="indexterm" name="id2626640"></a>
 A fundamental difference exists between MS Windows NT print servers and Samba operation. Windows NT
 permits the installation of local printers that are not shared. This is an artifact of the fact that
 any Windows NT machine (server or client) may be used by a user as a workstation. Samba will publish all
 printers that are made available, either by default or by specific declaration via printer-specific shares.
 </p><p>
-<a class="indexterm" name="id2626603"></a>
-<a class="indexterm" name="id2626610"></a>
-<a class="indexterm" name="id2626617"></a>
-<a class="indexterm" name="id2626624"></a>
-<a class="indexterm" name="id2626630"></a>
+<a class="indexterm" name="id2626658"></a>
+<a class="indexterm" name="id2626664"></a>
+<a class="indexterm" name="id2626671"></a>
+<a class="indexterm" name="id2626678"></a>
+<a class="indexterm" name="id2626685"></a>
 Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can
 print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that
 the client has the necessary privileges on the remote host that serves the printer resource. 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 Windows 9x/Me can only print to shared
 printers.)
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626650"></a>Point'n'Print Client Drivers on Samba Servers</h3></div></div></div><p>
-<a class="indexterm" name="id2626659"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626705"></a>Point'n'Print Client Drivers on Samba Servers</h3></div></div></div><p>
+<a class="indexterm" name="id2626713"></a>
 There is much confusion about what all this means. The question is often asked, &#8220;<span class="quote">Is it or is
 it not necessary for printer drivers to be installed on a Samba host in order to support printing from
 Windows clients?</span>&#8221; The answer to this is no, it is not necessary.
 </p><p>
-<a class="indexterm" name="id2626677"></a>
-<a class="indexterm" name="id2626684"></a>
+<a class="indexterm" name="id2626731"></a>
+<a class="indexterm" name="id2626738"></a>
 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 used by Windows 9x/Me
 clients. (However, a bug existed in Samba 2.2.0 that 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>
-<a class="indexterm" name="id2626703"></a>
-<a class="indexterm" name="id2626710"></a>
+<a class="indexterm" name="id2626758"></a>
+<a class="indexterm" name="id2626765"></a>
 But it is a new capability to install the printer drivers into the <em class="parameter"><code>[print$]</code></em>
 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
@@ -682,16 +682,16 @@ Samba printer share can be achieved by different means:
 	</p></li><li><p>
 	Using <span class="emphasis"><em>cupsaddsmb</em></span> (only works for the CUPS printing system, not for LPR/LPD, LPRng, and so on).
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2626792"></a>
-<a class="indexterm" name="id2626799"></a>
+<a class="indexterm" name="id2626846"></a>
+<a class="indexterm" name="id2626853"></a>
 Samba does not use these uploaded drivers in any way to process spooled files. These drivers are utilized
 entirely by the clients who download and install them via the &#8220;<span class="quote">Point'n'Print</span>&#8221; 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, as needed.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626819"></a>The Obsoleted [printer$] Section</h3></div></div></div><p>
-<a class="indexterm" name="id2626828"></a>
-<a class="indexterm" name="id2626834"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626874"></a>The Obsoleted [printer$] Section</h3></div></div></div><p>
+<a class="indexterm" name="id2626882"></a>
+<a class="indexterm" name="id2626889"></a>
 	Versions of Samba prior to 2.2 made it possible to use a share named <em class="parameter"><code>[printer$]</code></em>. This
 	name was taken from the same named service created by Windows 9x/Me clients when a printer was shared by them.
 	Windows 9x/Me printer servers always have a <em class="parameter"><code>[printer$]</code></em> service that provides
@@ -701,9 +701,9 @@ system, which is responsible for all further processing, as needed.
 	parameter named <em class="parameter"><code>printer driver</code></em> provided a means of defining the printer driver name to
 	be sent to the client.
 	</p><p>
-<a class="indexterm" name="id2626879"></a>
-<a class="indexterm" name="id2626886"></a>
-<a class="indexterm" name="id2626893"></a>
+<a class="indexterm" name="id2626933"></a>
+<a class="indexterm" name="id2626940"></a>
+<a class="indexterm" name="id2626947"></a>
 	These parameters, including the <em class="parameter"><code>printer driver file</code></em> parameter,
 	are now removed and cannot be used in installations of Samba-3. The share name
 	<em class="parameter"><code>[print$]</code></em> is now used for the location of downloadable printer
@@ -713,8 +713,8 @@ system, which is responsible for all further processing, as needed.
 	of its ACLs) to support printer driver downloads and uploads. This does not mean Windows
 	9x/Me clients are now thrown aside. They can use Samba's <em class="parameter"><code>[print$]</code></em>
 	share support just fine.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626941"></a>Creating the [print$] Share</h3></div></div></div><p>
-<a class="indexterm" name="id2626949"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2626995"></a>Creating the [print$] Share</h3></div></div></div><p>
+<a class="indexterm" name="id2627003"></a>
 In order to support the uploading and downloading of printer driver files, you must first configure a
 file share named <em class="parameter"><code>[print$]</code></em>. The public name of this share is hard coded
 in the MS Windows clients. It cannot be renamed, since Windows clients are programmed to search for a
@@ -724,15 +724,15 @@ You should modify the server's file to add the global parameters and create the
 <em class="parameter"><code>[print$]</code></em> file share (of course, some of the parameter values, such
 as <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a>, are arbitrary and should be replaced with appropriate values for your
 site). See <a class="link" href="classicalprinting.html#prtdollar" title="Example�21.3.�[print$] Example">[print\$] Example</a>.
-</p><div class="example"><a name="prtdollar"></a><p class="title"><b>Example�21.3.�[print$] Example</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></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><a class="indexterm" name="id2627033"></a><em class="parameter"><code>printer admin = @ntadmin</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2627070"></a><em class="parameter"><code>comment = Printer Driver Download Area</code></em></td></tr><tr><td><a class="indexterm" name="id2627081"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2627093"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627104"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627116"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627128"></a><em class="parameter"><code>write list = @ntadmin, root</code></em></td></tr></table></div></div><br class="example-break"><p>
+</p><div class="example"><a name="prtdollar"></a><p class="title"><b>Example�21.3.�[print$] Example</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></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><a class="indexterm" name="id2627087"></a><em class="parameter"><code>printer admin = @ntadmin</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td># ...</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2627124"></a><em class="parameter"><code>comment = Printer Driver Download Area</code></em></td></tr><tr><td><a class="indexterm" name="id2627135"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2627147"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627159"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627170"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627182"></a><em class="parameter"><code>write list = @ntadmin, root</code></em></td></tr></table></div></div><br class="example-break"><p>
 Of course, you also need to ensure that the directory named by the
 <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a> parameter exists on the UNIX file system.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627158"></a>[print$] Stanza Parameters</h3></div></div></div><p>
-<a class="indexterm" name="id2627166"></a>
-<a class="indexterm" name="id2627172"></a>
-<a class="indexterm" name="id2627179"></a>
-<a class="indexterm" name="id2627186"></a>
-<a class="indexterm" name="id2627193"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627212"></a>[print$] Stanza Parameters</h3></div></div></div><p>
+<a class="indexterm" name="id2627220"></a>
+<a class="indexterm" name="id2627227"></a>
+<a class="indexterm" name="id2627234"></a>
+<a class="indexterm" name="id2627240"></a>
+<a class="indexterm" name="id2627247"></a>
 The <em class="parameter"><code>[print$]</code></em> is a special section in <code class="filename">smb.conf</code>. It contains settings relevant to
 potential printer driver download and is used by Windows clients for local print driver installation.
 The following parameters are frequently needed in this share section:
@@ -777,7 +777,7 @@ The following parameters are frequently needed in this share section:
 		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="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a>
 		parameter. See the <code class="filename">smb.conf</code> 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="id2627479"></a>The [print$] Share Directory</h3></div></div></div><p>
+		</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627533"></a>The [print$] Share Directory</h3></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 <em class="parameter"><code>[print$]</code></em>
 service (i.e., the UNIX directory named by the <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a>
@@ -812,7 +812,7 @@ associated subdirectories, go to a Windows NT 4.0/200x/XP client workstation. Op
 Neighborhood</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="id2627627"></a>Installing Drivers into [print$]</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2627675"></a>Installing Drivers into [print$]</h2></div></div></div><p>
 Have you successfully created the <em class="parameter"><code>[print$]</code></em> share in <code class="filename">smb.conf</code>, and have you forced
 Samba to reread its <code class="filename">smb.conf</code> file? Good. But you are not yet ready to use the new facility. The client
 driver files need to be installed into this share. So far, it is still an empty share. Unfortunately, it is
@@ -828,7 +828,7 @@ ways to install the drivers into <em class="parameter"><code>[print$]</code></em
 	from any Windows NT/200x/XP client workstation.
 	</p></li></ul></div><p>
 The latter option is probably the easier one (even if the process may seem a little bit weird at first).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627720"></a>Add Printer Wizard Driver Installation</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2627768"></a>Add Printer Wizard Driver Installation</h3></div></div></div><p>
 The printers initially listed 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="guiicon">Add Printer Wizard</span> (APW), run from
@@ -879,10 +879,10 @@ up in a valid way is to do it from the UNIX command line. This involves four dis
 	Run <code class="literal">rpcclient</code> a second time with the <code class="literal">setdriver</code> subcommand.
 	</p></li></ol></div><p>
 We provide detailed hints for each of these steps in the paragraphs that follow.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2627996"></a>Identifying Driver Files</h4></div></div></div><p>
-<a class="indexterm" name="id2628004"></a>
-<a class="indexterm" name="id2628011"></a>
-<a class="indexterm" name="id2628018"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628044"></a>Identifying Driver Files</h4></div></div></div><p>
+<a class="indexterm" name="id2628052"></a>
+<a class="indexterm" name="id2628059"></a>
+<a class="indexterm" name="id2628066"></a>
 To find out about the driver files, you have two options. You can check the contents of the driver
 CDROM that came with your printer. Study the <code class="filename">*.inf</code> files located on the CD-ROM. This
 may not be possible, since the <code class="filename">*.inf</code> file might be missing. Unfortunately, vendors have now started
@@ -890,14 +890,14 @@ to use their own installation programs. These installations packages are often i
 archive format. Additionally, the files may be re-named during the installation process. This makes it
 extremely difficult to identify the driver files required.
 </p><p>
-<a class="indexterm" name="id2628054"></a>
+<a class="indexterm" name="id2628097"></a>
 Then you have the second option. Install the driver locally on a Windows client and
 investigate which filenames and paths it uses after they are installed. (You need to repeat
 this procedure for every client platform you want to support. We show it here for the
 <span class="application">W32X86</span> platform only, a name used by Microsoft for all Windows NT/200x/XP
 clients.)
 </p><p>
-<a class="indexterm" name="id2628076"></a>
+<a class="indexterm" name="id2628119"></a>
 A good method to recognize the driver files 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
@@ -905,9 +905,9 @@ driver files named on the printout. You'll need to recognize what Windows (and S
 <span class="guilabel">Help File</span>, and (optionally) <span class="guilabel">Dependent Driver Files</span>
 (this may vary slightly for Windows NT). You need to note all filenames for the next steps.
 </p><p>
-<a class="indexterm" name="id2628133"></a>
-<a class="indexterm" name="id2628139"></a>
-<a class="indexterm" name="id2628146"></a>
+<a class="indexterm" name="id2628176"></a>
+<a class="indexterm" name="id2628182"></a>
+<a class="indexterm" name="id2628189"></a>
 Another method to quickly test the driver filenames and related paths is provided by the
 <code class="literal">rpcclient</code> utility. Run it with <code class="literal">enumdrivers</code> or with the
 <code class="literal">getdriver</code> subcommand, each at the <code class="filename">3</code> info level. In the following example,
@@ -948,10 +948,10 @@ Printer Driver Info 3:
   Monitorname: []
   Defaultdatatype: []
 </pre><p>
-<a class="indexterm" name="id2628284"></a>
-<a class="indexterm" name="id2628290"></a>
-<a class="indexterm" name="id2628297"></a>
-<a class="indexterm" name="id2628304"></a>
+<a class="indexterm" name="id2628305"></a>
+<a class="indexterm" name="id2628312"></a>
+<a class="indexterm" name="id2628319"></a>
+<a class="indexterm" name="id2628325"></a>
 You may notice that this driver has quite a large number of <span class="guilabel">Dependent files</span>
 (there are worse cases, however). Also, strangely, the
 <span class="guilabel">Driver File</span> is tagged here
@@ -961,9 +961,9 @@ You may notice that this driver has quite a large number of <span class="guilabe
 addition to those for <span class="application">W32X86</span> (i.e., the Windows NT 2000/XP clients) onto a
 Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000, or XP.
 </p><p>
-<a class="indexterm" name="id2628352"></a>
-<a class="indexterm" name="id2628359"></a>
-<a class="indexterm" name="id2628366"></a>
+<a class="indexterm" name="id2628374"></a>
+<a class="indexterm" name="id2628381"></a>
+<a class="indexterm" name="id2628388"></a>
 Since the <em class="parameter"><code>[print$]</code></em> share is usually accessible through the <span class="guiicon">Network
 Neighborhood</span>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows
 9x/Me driver files will end up in subdirectory <code class="filename">0</code> of the <code class="filename">WIN40</code>
@@ -974,7 +974,7 @@ instead of the &#8220;<span class="quote">2</span>&#8221;. The version 2 of driv
 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 purpose. These types of drivers install into the &#8220;<span class="quote">3</span>&#8221; subdirectory.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628430"></a>Obtaining Driver Files from Windows Client [print$] Shares</h4></div></div></div><p>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628451"></a>Obtaining Driver Files from Windows Client [print$] Shares</h4></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 <em class="parameter"><code>[print$]</code></em>
 share that we investigated in our last step to identify the files? We can use <code class="literal">smbclient</code>
@@ -999,12 +999,12 @@ that this time we passed several commands to the <code class="option">-c</code>
 This ensures that all commands are executed in sequence on the remote Windows server before
 <code class="literal">smbclient</code> exits again.
 </p><p>
-<a class="indexterm" name="id2628538"></a>
+<a class="indexterm" name="id2628560"></a>
 Remember to repeat the procedure for the <span class="application">WIN40</span> architecture should you need to
 support Windows 9x/Me/XP clients. Remember too, the files for these architectures are in the
 <code class="filename">WIN40/0/</code> subdirectory. Once this is complete, we can run <code class="literal">smbclient. .
 .put</code> to store the collected files on the Samba server's <em class="parameter"><code>[print$]</code></em> share.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628576"></a>Installing Driver Files into [print$]</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628597"></a>Installing Driver Files into [print$]</h4></div></div></div><p>
 We are now going to locate the driver files into the <em class="parameter"><code>[print$]</code></em> share. Remember, the
 UNIX path to this share has been defined previously in your <code class="filename">smb.conf</code> file. You also have created
 subdirectories for the different Windows client types you want to support. If, for example, your
@@ -1017,8 +1017,8 @@ driver files should now go here:
 	For all Windows 95, 98, and Me clients, <code class="filename">/etc/samba/drivers/WIN40/</code> but not
 	(yet) into the <code class="filename">0</code> subdirectory.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2628655"></a>
-<a class="indexterm" name="id2628661"></a>
+<a class="indexterm" name="id2628676"></a>
+<a class="indexterm" name="id2628683"></a>
 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 <code class="literal">getdriver</code> against the original
 <span class="emphasis"><em>Windows</em></span> install. However, now we are going to store the files into a
@@ -1055,18 +1055,18 @@ 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>
-<a class="indexterm" name="id2628752"></a>
-<a class="indexterm" name="id2628759"></a>
-<a class="indexterm" name="id2628766"></a>
+<a class="indexterm" name="id2628755"></a>
+<a class="indexterm" name="id2628762"></a>
+<a class="indexterm" name="id2628769"></a>
 Whew  that was a lot of typing! Most drivers are a lot smaller  many have only three generic
 PostScript driver files plus one PPD. While we did retrieve the files from the <code class="filename">2</code>
 subdirectory of the <code class="filename">W32X86</code> directory from the Windows box, we do not put them
 (for now) in this same subdirectory of the Samba box. This relocation will automatically be done by the
 <code class="literal">adddriver</code> command, which we will run shortly (and do not forget to also put the files
 for the Windows 9x/Me architecture into the <code class="filename">WIN40/</code> subdirectory should you need them).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628812"></a><code class="literal">smbclient</code> to Confirm Driver Installation</h4></div></div></div><p>
-<a class="indexterm" name="id2628825"></a>
-<a class="indexterm" name="id2628832"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628816"></a><code class="literal">smbclient</code> to Confirm Driver Installation</h4></div></div></div><p>
+<a class="indexterm" name="id2628828"></a>
+<a class="indexterm" name="id2628835"></a>
 For now we verify that our files are there. This can be done with <code class="literal">smbclient</code>, too
 (but, of course, you can log in via SSH also and do this through a standard UNIX shell access):
 </p><pre class="screen">
@@ -1107,9 +1107,9 @@ 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>
-<a class="indexterm" name="id2628906"></a>
-<a class="indexterm" name="id2628913"></a>
-<a class="indexterm" name="id2628920"></a>
+<a class="indexterm" name="id2628910"></a>
+<a class="indexterm" name="id2628917"></a>
+<a class="indexterm" name="id2628924"></a>
 Notice that there are already driver files present in the <code class="filename">2</code> subdirectory (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 retrieve them from a client just
@@ -1117,10 +1117,10 @@ like you retrieve ordinary files from a file share, by opening print$ in Windows
 install them per Point'n'Print. The reason is that Samba does not yet know that these files are something
 special, namely <span class="emphasis"><em>printer driver files</em></span>, and it does not know 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="id2628949"></a>Running <code class="literal">rpcclient</code> with <code class="literal">adddriver</code></h4></div></div></div><p>
-<a class="indexterm" name="id2628968"></a>
-<a class="indexterm" name="id2628974"></a>
-<a class="indexterm" name="id2628981"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628952"></a>Running <code class="literal">rpcclient</code> with <code class="literal">adddriver</code></h4></div></div></div><p>
+<a class="indexterm" name="id2628971"></a>
+<a class="indexterm" name="id2628978"></a>
+<a class="indexterm" name="id2628985"></a>
 Next, you must tell Samba about the special category of the files you just uploaded into the
 <em class="parameter"><code>[print$]</code></em> share. This is done by the <code class="literal">adddriver</code>
 command. It will prompt Samba to register the driver files into its internal TDB database files. The
@@ -1144,16 +1144,16 @@ cmd = adddriver "Windows NT x86" \
 
 Printer Driver dm9110 successfully installed.
 </pre><p>
-<a class="indexterm" name="id2629036"></a>
-<a class="indexterm" name="id2629043"></a>
-<a class="indexterm" name="id2629050"></a>
+<a class="indexterm" name="id2629039"></a>
+<a class="indexterm" name="id2629046"></a>
+<a class="indexterm" name="id2629053"></a>
 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
 an <code class="computeroutput">NT_STATUS_UNSUCCESSFUL</code> 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. 
 provides a more detailed description, should you need it.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629073"></a>Checking <code class="literal">adddriver</code> Completion</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629076"></a>Checking <code class="literal">adddriver</code> Completion</h4></div></div></div><p>
 One indication for Samba's recognition of the files as driver files is the <code class="computeroutput">successfully
 installed</code> message. Another one is the fact that our files have been moved by the
 <code class="literal">adddriver</code> command into the <code class="filename">2</code> subdirectory. You can check this
@@ -1198,17 +1198,17 @@ again with <code class="literal">smbclient</code>:
 </pre><p>
 Another verification is that the timestamp of the printing TDB files is now updated
 (and possibly their file size has increased).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629176"></a>Check Samba for Driver Recognition</h4></div></div></div><p>
-<a class="indexterm" name="id2629185"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629218"></a>Check Samba for Driver Recognition</h4></div></div></div><p>
+<a class="indexterm" name="id2629226"></a>
 Now the driver should be registered with Samba. We can easily verify this and will do so in a
 moment. However, this driver is not yet associated with a particular printer. We may check the driver
 status of the files by at least three methods:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2629202"></a>
-<a class="indexterm" name="id2629209"></a>
-<a class="indexterm" name="id2629216"></a>
-<a class="indexterm" name="id2629223"></a>
-<a class="indexterm" name="id2629230"></a>
+<a class="indexterm" name="id2629244"></a>
+<a class="indexterm" name="id2629251"></a>
+<a class="indexterm" name="id2629258"></a>
+<a class="indexterm" name="id2629265"></a>
+<a class="indexterm" name="id2629272"></a>
 	From any Windows client browse Network Neighborhood, 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 the <span class="guilabel">Advanced</span>
@@ -1218,7 +1218,7 @@ status of the files by at least three methods:
 	see only its own architecture's list. If you do not have every driver installed for each platform,
 	the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.)
 	</p></li><li><p>
-<a class="indexterm" name="id2629277"></a>
+<a class="indexterm" name="id2629312"></a>
 	From a Windows 200x/XP client (not Windows NT) browse <span class="guiicon">Network Neighborhood</span>,
 	search for the Samba server, open the server's <span class="guiicon">Printers</span> folder,
 	and right-click on the white background (with no printer highlighted). Select <span class="guimenuitem">Server
@@ -1247,8 +1247,8 @@ status of the files by at least three methods:
 	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="id2629412"></a>Specific Driver Name Flexibility</h4></div></div></div><p>
-<a class="indexterm" name="id2629420"></a>
+	</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629446"></a>Specific Driver Name Flexibility</h4></div></div></div><p>
+<a class="indexterm" name="id2629454"></a>
 You can name the driver as you like. If you repeat the <code class="literal">adddriver</code> step with the same
 files as before but with a different driver name, it will work the same:
 </p><pre class="screen">
@@ -1271,18 +1271,18 @@ cmd = adddriver "Windows NT x86" \
 
 Printer Driver mydrivername successfully installed.
 </pre><p>
-<a class="indexterm" name="id2629467"></a>
-<a class="indexterm" name="id2629474"></a>
-<a class="indexterm" name="id2629481"></a>
+<a class="indexterm" name="id2629501"></a>
+<a class="indexterm" name="id2629508"></a>
+<a class="indexterm" name="id2629515"></a>
 You will be able to bind that driver to any print queue (however, you are responsible that
 you associate drivers to queues that make sense with respect to target printers). You cannot run the
 <code class="literal">rpcclient</code> <code class="literal">adddriver</code> command repeatedly. Each run consumes the
 files you had put into the <em class="parameter"><code>[print$]</code></em> share by moving them into the
 respective subdirectories, so you must execute an <code class="literal">smbclient ... put</code> command before
 each <code class="literal">rpcclient ... adddriver</code> command.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629526"></a>Running <code class="literal">rpcclient</code> with <code class="literal">setdriver</code></h4></div></div></div><p> 
-<a class="indexterm" name="id2629544"></a>
-<a class="indexterm" name="id2629551"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2629560"></a>Running <code class="literal">rpcclient</code> with <code class="literal">setdriver</code></h4></div></div></div><p> 
+<a class="indexterm" name="id2629578"></a>
+<a class="indexterm" name="id2629585"></a>
 Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and
 store this information in Samba's memory, the TDB files. The <code class="literal">rpcclient setdriver</code> command
 achieves exactly this:
@@ -1309,11 +1309,11 @@ The <code class="literal">setdriver</code> command will only succeed if the prin
 bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba,
 or at least send an HUP signal to all running smbd processes to work around this: <strong class="userinput"><code>kill -HUP
 `pidof smbd`</code></strong>.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2629667"></a>Client Driver Installation Procedure</h2></div></div></div><p>
+</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2629701"></a>Client Driver Installation Procedure</h2></div></div></div><p>
 As Don Quixote said, &#8220;<span class="quote">The proof of the pudding is in the eating.</span>&#8221; The proof
 for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is
 not as straightforward as it may seem. Read on.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2629683"></a>First Client Driver Installation</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2629717"></a>First Client Driver Installation</h3></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 set up and shouldn't need further
 attention. What follows is a description for the recommended first procedure. You now work from a client
@@ -1347,7 +1347,7 @@ appeared in your <span class="emphasis"><em>local</em></span> Printer folder (ch
 <span class="guimenuitem">Settings</span> -&gt; <span class="guimenuitem">Control Panel</span> -&gt; <span class="guiicon">Printers
 and Faxes</span>).
 </p><p>
-<a class="indexterm" name="id2629862"></a>
+<a class="indexterm" name="id2629888"></a>
 Most likely you are tempted to try to print a test page. After all, you now can open the printer
 properties, and on the <span class="guimenu">General</span> tab there is a button offering to do just that. But
 chances are that you get an error message saying "<code class="literal">Unable to print Test Page</code>." The
@@ -1359,18 +1359,18 @@ driver. We now explain what that means.
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="prt-modeset"></a>Setting Device Modes on New Printers</h3></div></div></div><p>
 For a printer to be truly usable by a Windows NT/200x/XP client, it must possess:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2629922"></a>
+<a class="indexterm" name="id2629949"></a>
 	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).
 	</p></li><li><p>
-<a class="indexterm" name="id2629939"></a>
+<a class="indexterm" name="id2629966"></a>
 	A complete set of <span class="emphasis"><em>printer driver data</em></span> generated by the driver.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2629955"></a>
-<a class="indexterm" name="id2629962"></a>
-<a class="indexterm" name="id2629969"></a>
-<a class="indexterm" name="id2629976"></a>
 <a class="indexterm" name="id2629982"></a>
+<a class="indexterm" name="id2629988"></a>
+<a class="indexterm" name="id2629995"></a>
+<a class="indexterm" name="id2630002"></a>
+<a class="indexterm" name="id2630009"></a>
 If either 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 it produces a harvest of
 error messages when attempting to print. Samba stores the named values and all printing-related information in
@@ -1396,7 +1396,7 @@ to set it on the Samba server. The easiest means of doing so is to simply change
 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/200x/XP printer properties page from a Window client for this:
-</p><div class="procedure"><a name="id2630072"></a><p class="title"><b>Procedure�21.1.�Procedure to Initialize the Printer Driver Settings</b></p><ol type="1"><li><p>
+</p><div class="procedure"><a name="id2630107"></a><p class="title"><b>Procedure�21.1.�Procedure to Initialize the Printer Driver Settings</b></p><ol type="1"><li><p>
 	Browse the <span class="guiicon">Network Neighborhood</span>.
 	</p></li><li><p>
 	Find the Samba server.
@@ -1426,13 +1426,13 @@ device mode to Samba, which now stores it in its TDB files. Once the driver is i
 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>
-<a class="indexterm" name="id2630226"></a>
+<a class="indexterm" name="id2630261"></a>
 Samba includes a service-level parameter name <em class="parameter"><code>default devmode</code></em> for generating a default
 device mode for a printer. Some drivers 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="id2630248"></a>Additional Client Driver Installation</h3></div></div></div><p>
-<a class="indexterm" name="id2630256"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630283"></a>Additional Client Driver Installation</h3></div></div></div><p>
+<a class="indexterm" name="id2630291"></a>
 Every additional driver may be installed in the same way as just described.  Browse <code class="literal">Network
 Neighborhood</code>, open the <span class="guiicon">Printers</span> folder on Samba server, right-click on
 <span class="guiicon">Printer</span>, and choose <span class="guimenuitem">Connect...</span>. Once this completes (should be
@@ -1445,14 +1445,14 @@ using this command on Windows 200x/XP Professional workstations:
 <strong class="userinput"><code>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder</code></strong>
 </pre><p>
 or this command on Windows NT 4.0 workstations:
-<a class="indexterm" name="id2630323"></a>
+<a class="indexterm" name="id2630358"></a>
 </p><pre class="screen">
 <strong class="userinput"><code>rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2</code></strong>
 </pre><p>
 </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="id2630366"></a>Always Make First Client Connection as root or &#8220;<span class="quote">printer admin</span>&#8221;</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630401"></a>Always Make First Client Connection as root or &#8220;<span class="quote">printer admin</span>&#8221;</h3></div></div></div><p>
 After you installed the driver on the Samba server (in its <em class="parameter"><code>[print$]</code></em> share), you
 should always make sure that your first client installation completes correctly. Make it a habit for yourself
 to build the very first connection from a client as <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a>. This is to make
@@ -1467,7 +1467,7 @@ back again. Next, modify the other settings (for example, you do not want the de
 <span class="guiicon">Letter</span> when you are all using <span class="guiicon">A4</span>, right? You may want to set the
 printer for <span class="guiicon">duplex</span> as the default, and so on).
 </p><p>
-<a class="indexterm" name="id2630461"></a>
+<a class="indexterm" name="id2630496"></a>
 To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt:
 </p><pre class="screen">
 <code class="prompt">C:\&gt; </code><strong class="userinput"><code>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
@@ -1481,13 +1481,13 @@ by all clients. Alternatively, instead of root you can name one other member of
 Now all the other users downloading and installing the driver the same way (using
 <code class="literal">Point'n'Print</code>) will have the same defaults set for them. If you miss this step, you'll get a
 lot of help desk 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="id2630540"></a>Other Gotchas</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2630574"></a>Other Gotchas</h2></div></div></div><p>
 Your driver is installed. It is now ready for Point'n'Print installation by the clients. You may have tried to
 download and use it on your first client machine, but wait. Let's make sure you are acquainted first with a
 few tips and tricks you may find useful. For example, suppose you did not set the defaults on the printer, as
 advised in the preceding paragraphs. Your users complain about various issues (such as, &#8220;<span class="quote">We need to set
 the paper size for each job from Letter to A4 and it will not store it</span>&#8221;).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630560"></a>Setting Default Print Options for Client Drivers</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630595"></a>Setting Default Print Options for Client Drivers</h3></div></div></div><p>
 The last sentence might be viewed with mixed feelings by some users and Admins. They have struggled for hours
 and could not arrive at a point where their settings seemed to be saved. It is not their fault. The confusing
 thing is that in the multitabbed dialog that pops up when you right-click on the printer name and select
@@ -1536,7 +1536,7 @@ days of Windows NT, so it is only natural to try the same way with Windows 200x/
 there is now a different path to arrive at an identical-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 Windows 200x/XP) to run this command (as a user with the right privileges):
-<a class="indexterm" name="id2630854"></a>
+<a class="indexterm" name="id2630889"></a>
 </p><p><strong class="userinput"><code>
 rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<em class="replaceable"><code>SAMBA-SERVER</code></em>\<em class="replaceable"><code>printersharename</code></em>
 </code></strong></p><p>
@@ -1547,7 +1547,7 @@ rundll32 printui.dll,PrintUIEntry /p /t0 /n\\<em class="replaceable"><code>SAMBA
 To see the tab with the <span class="guilabel">Printing Preferences</span>
 button (the one that does not set systemwide defaults), you can
 start the commands from inside a DOS box or from <span class="guimenu">Start</span> -&gt; <span class="guimenuitem">Run</span>.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630928"></a>Supporting Large Numbers of Printers</h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2630963"></a>Supporting Large Numbers of Printers</h3></div></div></div><p>
 One issue that has arisen during the recent development phase of Samba is the need to support driver
 downloads for hundreds of printers. Using Windows NT APW for this task is somewhat awkward (to say the least). If
 you do not want to acquire RSS pains from the printer installation clicking orgy alone, you need
@@ -1630,7 +1630,7 @@ It may not be easy to recognize that the first call to <code class="literal">enu
 &#8220;<span class="quote">dm9110</span>&#8221; printer with an empty string where the driver should have been listed (between
 the two commas in the description field). After the <code class="literal">setdriver</code> command
 succeeds, all is well.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631184"></a>Adding New Printers with the Windows NT APW</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631219"></a>Adding New Printers with the Windows NT APW</h3></div></div></div><p>
 By default, Samba exhibits all printer shares defined in <code class="filename">smb.conf</code> 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>
@@ -1670,11 +1670,11 @@ share is still not defined, an error of "<span class="errorname">Access Denied"<
 necessarily a root account. A <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest = bad user</a> may have connected
 you unwittingly under the wrong privilege. You should check it by using the <code class="literal">smbstatus</code>
 command.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631444"></a>Error Message: &#8220;<span class="quote">Cannot connect under a different Name</span>&#8221;</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631479"></a>Error Message: &#8220;<span class="quote">Cannot connect under a different Name</span>&#8221;</h3></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>
-<a class="indexterm" name="id2631463"></a>
+<a class="indexterm" name="id2631498"></a>
 	The <code class="literal">net use \\SAMBA-SERVER\sharename /user:root</code> gives you an error message:
 	&#8220;<span class="quote">Multiple connections to a server or a shared resource by the same user utilizing
 	several user names are not allowed. Disconnect all previous connections to the server,
@@ -1700,7 +1700,7 @@ The easiest way to forcefully terminate all connections from your client to a se
 <code class="prompt">C:\&gt; </code> net use * /delete
 </pre><p>
 This will also disconnect all mapped drives and will allow you create fresh connection as required.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631557"></a>Take Care When Assembling Driver Files</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631592"></a>Take Care When Assembling Driver Files</h3></div></div></div><p>
 You need to be extremely careful when you take notes about the files belonging to a particular
 driver. Don't confuse the files for driver version &#8220;<span class="quote">0</span>&#8221; (for Windows 9x/Me, going into
 <code class="filename">[print$]/WIN/0/</code>), driver version <code class="filename">2</code> (kernel mode driver for Windows NT,
@@ -1831,11 +1831,11 @@ comparison:
 In my example were even more differences than shown here. Conclusion: you must be careful to select the
 correct driver files for each driver version. Don't rely on the names alone, and 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="id2631819"></a>Samba and Printer Ports</h3></div></div></div><p>
-<a class="indexterm" name="id2631827"></a>
-<a class="indexterm" name="id2631833"></a>
-<a class="indexterm" name="id2631840"></a>
-<a class="indexterm" name="id2631847"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2631902"></a>Samba and Printer Ports</h3></div></div></div><p>
+<a class="indexterm" name="id2631910"></a>
+<a class="indexterm" name="id2631917"></a>
+<a class="indexterm" name="id2631924"></a>
+<a class="indexterm" name="id2631930"></a>
 Windows NT/2000 print servers associate a port with each printer. These normally take the form of
 <code class="filename">LPT1:</code>, <code class="filename">COM1:</code>, <code class="filename">FILE:</code>, and so on. Samba must also
 support the concept of ports associated with a printer. By default, only one printer port, named &#8220;<span class="quote">Samba
@@ -1844,22 +1844,22 @@ print; rather it is a requirement of Windows clients. They insist on being told
 they request this information; otherwise, they throw an error message at you. So Samba fakes the port
 information to keep the Windows clients happy.
 </p><p>
-<a class="indexterm" name="id2631891"></a>
+<a class="indexterm" name="id2631974"></a>
 Samba does not support the concept of <code class="constant">Printer Pooling</code> internally either. Printer
 pooling assigns a logical printer to multiple ports as a form of load balancing or failover.
 </p><p>
 If you require multiple ports to be defined for some reason or another (my users and my boss should not know
 that they are working with Samba), configure the <a class="link" href="smb.conf.5.html#ENUMPORTSCOMMAND" target="_top">enumports command</a>,
 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="id2631928"></a>Avoiding Common Client Driver Misconfiguration</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632011"></a>Avoiding Common Client Driver Misconfiguration</h3></div></div></div><p>
 So now the printing works, but there are still problems. Most jobs print well, some do not print at
 all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some
 are dead-slow. We cannot cover it all, but we want to encourage you to read the brief paragraph about
 &#8220;<span class="quote">Avoiding the Wrong PostScript Driver Settings</span>&#8221; in <a class="link" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support">CUPS Printing
 Chapter</a>, <a class="link" href="CUPS-printing.html#cups-avoidps1" title="Avoiding Critical PostScript Driver Settings on the Client">Avoiding Critical PostScript Driver Settings on the
 Client</a>.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2631965"></a>The Imprints Toolset</h2></div></div></div><p>
-<a class="indexterm" name="id2631973"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632048"></a>The Imprints Toolset</h2></div></div></div><p>
+<a class="indexterm" name="id2632056"></a>
 The Imprints tool set provides a UNIX equivalent of the Windows NT APW.  For complete information, please
 refer to the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> Web site as well as the
 documentation included with the Imprints source distribution. This section provides only a brief introduction
@@ -1871,7 +1871,7 @@ printing used in Samba. If you wish to volunteer, please coordinate your efforts
 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. Information regarding the Imprints toolset can be obtained from the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> home page.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632011"></a>What Is Imprints?</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632094"></a>What Is Imprints?</h3></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 of information regarding Windows NT and 95/98 printer driver packages.
@@ -1880,19 +1880,19 @@ Imprints is a collection of tools for supporting these goals:
 	</p></li><li><p>
 	Providing an installation client that 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="id2632045"></a>Creating Printer Driver Packages</h3></div></div></div><p>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632128"></a>Creating Printer Driver Packages</h3></div></div></div><p>
 The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt,
 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="id2632061"></a>The Imprints Server</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632144"></a>The Imprints Server</h3></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
 the package downloaded is actually
 the one referred in the Imprints database. It is strongly recommended that this security check
 not be disabled.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632078"></a>The Installation Client</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632162"></a>The Installation Client</h3></div></div></div><p>
 More information regarding the Imprints installation client is available from the documentation file
 <code class="filename">Imprints-Client-HOWTO.ps</code> that is included with the Imprints source package. The Imprints
 installation client comes in two forms:
@@ -1922,7 +1922,7 @@ requirement internally; therefore, &#8220;<span class="quote">How can you use th
 </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 the 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="id2632212"></a>Adding Network Printers without User Interaction</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632295"></a>Adding Network Printers without User Interaction</h2></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 class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105" target="_top">Microsoft KB 189105</a>).  It also
 applies to Windows XP Professional clients.  The ideas sketched out in this section are inspired by this
@@ -1981,7 +1981,7 @@ Since network printers are installed per user, this much simplifies the process
 up to date. The few extra 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 from 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="id2632486"></a>The <code class="literal">addprinter</code> Command</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632569"></a>The <code class="literal">addprinter</code> Command</h2></div></div></div><p>
 The <code class="literal">addprinter</code> 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,
@@ -1989,7 +1989,7 @@ and so on). These parameters are passed on to Samba by the APW. If the addprinte
 way that it can create a new printer (through writing correct printcap entries on legacy systems or
 by executing the <code class="literal">lpadmin</code> command on more modern systems) and create the associated share,
 then the APW will in effect really create a new printer on Samba and the UNIX print subsystem!
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632524"></a>Migration of Classical Printing to Samba</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632608"></a>Migration of Classical Printing to Samba</h2></div></div></div><p>
 The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases
 (apart from many small improvements). Here migration should be quite easy, especially if you followed
 previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x
@@ -2019,11 +2019,11 @@ follow several paths. Here are possible scenarios for migration:
 	solution is to use the Windows NT APW to install the NT drivers and the 9x/Me drivers. This can be scripted
 	using smbclient and rpcclient. See the Imprints installation client on the <a class="ulink" href="http://imprints.sourceforge.net/" target="_top">Imprints</a> web site for example. See also the discussion of
 	rpcclient usage in <a class="link" href="CUPS-printing.html" title="Chapter�22.�CUPS Printing Support">CUPS Printing</a>.
-	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632673"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div></div><p>
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632756"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div></div><p>
 This topic has also been addressed in <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">Remote and Local Management  The
 Net Command</a>. If you wish to volunteer your services to help document this further, please contact 
 <a class="ulink" href="mail://jht@samba.org" target="_top">John H. Terpstra</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632702"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632708"></a>I Give My Root Password but I Do Not Get Access</h3></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632786"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632791"></a>I Give My Root Password but I Do Not Get Access</h3></div></div></div><p>
 Do not confuse the root password, which is valid for the UNIX system (and in most cases stored in the
 form of a one-way hash in a file named <code class="filename">/etc/shadow</code>), with the password used to
 authenticate against Samba. Samba does not know the UNIX password. Root access to Samba resources
@@ -2034,7 +2034,7 @@ command as follows:
 New SMB password: secret
 Retype new SMB password: secret
 </pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632749"></a>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632833"></a>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</h3></div></div></div><p>
 Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem
 convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux
 system print spool directory (e.g., <code class="filename">/var/spool/cups</code>) is typically owned by a
diff --git a/docs/htmldocs/Samba3-HOWTO/compiling.html b/docs/htmldocs/Samba3-HOWTO/compiling.html
index 4394252a78..e2260a4b0f 100644
--- a/docs/htmldocs/Samba3-HOWTO/compiling.html
+++ b/docs/htmldocs/Samba3-HOWTO/compiling.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�42.�How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="next" href="Portability.html" title="Chapter�43.�Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�42.�How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�42.�How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2687392">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687398">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687440">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687637">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687711">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687849">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688088">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688359">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688579">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�42.�How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="next" href="Portability.html" title="Chapter�43.�Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�42.�How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�42.�How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2687543">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687549">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687590">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687994">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688233">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688504">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688724">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p>
 You can obtain the Samba source file from the
 <a class="ulink" href="http://samba.org/" target="_top">Samba Web site</a>. To obtain a development version, 
 you can download Samba from Subversion or using <code class="literal">rsync</code>.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687392"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687398"></a>Introduction</h3></div></div></div><p>
-<a class="indexterm" name="id2687406"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687543"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687549"></a>Introduction</h3></div></div></div><p>
+<a class="indexterm" name="id2687557"></a>
 Samba is developed in an open environment. Developers use a
 Subversion to &#8220;<span class="quote">checkin</span>&#8221; (also known as 
 &#8220;<span class="quote">commit</span>&#8221;) new source code. Samba's various Subversion branches can
@@ -12,13 +12,13 @@ detailed in this chapter.
 </p><p>
 This chapter is a modified version of the instructions found at the
 <a class="ulink" href="http://samba.org/samba/subversion.html" target="_top">Samba</a> Web site.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687440"></a>Subversion Access to samba.org</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687590"></a>Subversion Access to samba.org</h3></div></div></div><p>
 The machine samba.org runs a publicly accessible Subversion
 repository for access to the source code of several packages, 
 including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways
 of accessing the Subversion server on this host.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687453"></a>Access via ViewCVS</h4></div></div></div><p>
-<a class="indexterm" name="id2687461"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687603"></a>Access via ViewCVS</h4></div></div></div><p>
+<a class="indexterm" name="id2687611"></a>
 You can access the source code via your favorite WWW browser. This allows you to access
 the contents of individual files in the repository and also to look at the revision 
 history and commit logs of individual files. You can also ask for a diff 
@@ -26,8 +26,8 @@ listing between any two versions on the repository.
 </p><p>
 Use the URL
 <a class="ulink" href="http://viewcvs.samba.org/" target="_top">http://viewcvs.samba.org/</a>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687489"></a>Access via Subversion</h4></div></div></div><p>
-<a class="indexterm" name="id2687497"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687639"></a>Access via Subversion</h4></div></div></div><p>
+<a class="indexterm" name="id2687647"></a>
 You can also access the source code via a normal Subversion client. This gives you much more control over what
 you can do with the repository and allows you to check out whole source trees and keep them up to date via
 normal Subversion commands. This is the preferred method of access if you are a developer and not just a
@@ -37,7 +37,7 @@ a Subversion client. Your distribution might include one, or you can download th
 sources from <a class="ulink" href="http://subversion.tigris.org/" target="_top">http://subversion.tigris.org/</a>.
 </p><p>
 To gain access via anonymous Subversion, use the following steps. 
-</p><div class="procedure"><a name="id2687536"></a><p class="title"><b>Procedure�42.1.�Retrieving Samba using Subversion</b></p><ol type="1"><li><p>
+</p><div class="procedure"><a name="id2687680"></a><p class="title"><b>Procedure�42.1.�Retrieving Samba using Subversion</b></p><ol type="1"><li><p>
 	Install a recent copy of Subversion. All you really need is a 
 	copy of the Subversion client binary. 
 	</p></li><li><p>
@@ -62,9 +62,9 @@ To gain access via anonymous Subversion, use the following steps.
 	</p><pre class="screen">
 	<strong class="userinput"><code>svn update</code></strong>
 	</pre><p>
-	</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687637"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>
-	<a class="indexterm" name="id2687645"></a>
-	<a class="indexterm" name="id2687652"></a>
+	</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="id2687781"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>
+	<a class="indexterm" name="id2687790"></a>
+	<a class="indexterm" name="id2687796"></a>
 	<em class="parameter"><code>pserver.samba.org</code></em> also exports unpacked copies of most parts of the Subversion tree
 	at the Samba <a class="ulink" href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a> location and also
 	via anonymous rsync at the Samba <a class="ulink" href="rsync://pserver.samba.org/ftp/unpacked/" target="_top">rsync</a> server location.  I recommend using rsync rather
@@ -74,9 +74,9 @@ To gain access via anonymous Subversion, use the following steps.
 	The disadvantage of the unpacked trees is that they do not support automatic
 	merging of local changes as Subversion does. <code class="literal">rsync</code> access is most convenient 
 	for an initial install.                      
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687711"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>
-<a class="indexterm" name="id2687719"></a>
-<a class="indexterm" name="id2687726"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687856"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>
+<a class="indexterm" name="id2687864"></a>
+<a class="indexterm" name="id2687870"></a>
 It is strongly recommended that you verify the PGP signature for any source file before
 installing it. Even if you're not downloading from a mirror site, verifying PGP signatures
 should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP.
@@ -87,7 +87,7 @@ With that said, go ahead and download the following files:
 <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-3.0.20.tar.asc</code></strong>
 <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</code></strong>
 </pre><p>
-<a class="indexterm" name="id2687774"></a>
+<a class="indexterm" name="id2687919"></a>
 The first file is the PGP signature for the Samba source file; the other is the Samba public
 PGP key itself. Import the public PGP key with:
 </p><pre class="screen">
@@ -105,9 +105,9 @@ example of what you would not want to see would be:
 </p><pre class="screen">
 gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verification Key</span>&#8221;
 </pre><p>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687849"></a>Building the Binaries</h2></div></div></div><p>
-	<a class="indexterm" name="id2687857"></a>
-<a class="indexterm" name="id2687864"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687994"></a>Building the Binaries</h2></div></div></div><p>
+	<a class="indexterm" name="id2688002"></a>
+<a class="indexterm" name="id2688009"></a>
 	After the source tarball has been unpacked, the next step involves
 	configuration to match Samba to your operating system platform.
 	If your source directory does not contain the <code class="literal">configure</code> script,
@@ -122,7 +122,7 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 <code class="prompt">root# </code> ./autogen.sh
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2687907"></a>
+	<a class="indexterm" name="id2688052"></a>
 	To build the binaries, run the program <strong class="userinput"><code>./configure
 	</code></strong> in the source directory. This should automatically 
 	configure Samba for your operating system. If you have unusual 
@@ -137,7 +137,7 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 <code class="prompt">root# </code><strong class="userinput"><code>./configure <em class="replaceable"><code>[... arguments ...]</code></em></code></strong>
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2687973"></a>
+	<a class="indexterm" name="id2688117"></a>
 	Execute the following create the binaries:
 </p><pre class="screen">
 <code class="prompt">root# </code> <strong class="userinput"><code>make</code></strong>
@@ -166,7 +166,7 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 </pre><p>
 	As you can see from this, building and installing Samba does not need to
 	result in disaster!
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688088"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688233"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>
 	In order to compile Samba with ADS support, you need to have installed
 	on your system:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -189,13 +189,13 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 	If it does not, configure did not find your KRB5 libraries or
 	your LDAP libraries. Look in <code class="filename">config.log</code> to figure
 	out why and fix it.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688154"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688298"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p>
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688181"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688325"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>krb5-workstation (for kinit)</p></li><li><p>krb5-libs (for linking with)</p></li><li><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p>
 	</p><p>in addition to the standard development environment.</p><p>If these files are not installed on your system, you should check the installation
 	CDs to find which has them and install the files using your tool of choice. If in doubt
-	about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688225"></a>SuSE Linux Package Requirements</h4></div></div></div><p>
+	about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688370"></a>SuSE Linux Package Requirements</h4></div></div></div><p>
 	SuSE Linux installs Heimdal packages that may be required to allow you to build
 	binary packages. You should verify that the development libraries have been installed on
 	your system.
@@ -206,7 +206,7 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 	the maximum capabilities that are available. You should consider using SuSE-provided
 	packages where they are available.
 	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="startingSamba"></a>Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></h2></div></div></div><p>
-	<a class="indexterm" name="id2688279"></a>
+	<a class="indexterm" name="id2688424"></a>
 	You must choose to start <span class="application">smbd</span>, <span class="application">winbindd</span>  and <span class="application">nmbd</span> either as daemons or from
 	<span class="application">inetd</span>. Don't try to do both!  Either you can put
 	them in <code class="filename"> inetd.conf</code> and have them started on demand by
@@ -218,7 +218,7 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 	</p><p>
 	The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method
 	is that they will respond slightly more quickly to an initial connection request.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688359"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688365"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if 
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688504"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688509"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if 
 	you use NIS, NIS+, or LDAP to distribute services maps.</p></div><p>Look at your <code class="filename">/etc/services</code>. 
 	What is defined at port 139/tcp? If nothing is defined, 
 	then add a line like this:</p><pre class="programlisting">netbios-ssn     139/tcp</pre><p>Similarly for 137/udp, you should have an entry like:</p><pre class="programlisting">netbios-ns	137/udp</pre><p>
@@ -227,12 +227,12 @@ gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verificati
 netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd 
 netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 
 </pre><p>
-	</p><a class="indexterm" name="id2688427"></a><p>
+	</p><a class="indexterm" name="id2688572"></a><p>
 	The exact syntax of <code class="filename">/etc/inetd.conf</code> 
 	varies between UNIXes. Look at the other entries in inetd.conf 
 	for a guide.
 	</p><p>
-	<a class="indexterm" name="id2688448"></a>
+	<a class="indexterm" name="id2688592"></a>
 	Some distributions use xinetd instead of inetd. Consult the 
 	xinetd manual for configuration information.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some UNIXes already have entries like netbios_ns 
@@ -240,7 +240,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 	You must edit <code class="filename">/etc/services</code> or
 	<code class="filename">/etc/inetd.conf</code> to make them consistent.
 	</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2688485"></a>
+	<a class="indexterm" name="id2688630"></a>
 	On many systems you may need to use the
 	<a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to specify
 	the IP address and netmask of your interfaces. Run 
@@ -255,13 +255,13 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 	</p></div><p>
 	Restart <span class="application">inetd</span>, perhaps just send it a HUP,
 	like this:
-<a class="indexterm" name="id2688554"></a>
+<a class="indexterm" name="id2688698"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>killall -HUP inetd</code></strong>
 </pre><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688579"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>
-	<a class="indexterm" name="id2688593"></a>
-<a class="indexterm" name="id2688600"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688724"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>
+	<a class="indexterm" name="id2688738"></a>
+<a class="indexterm" name="id2688744"></a>
 	To start the server as a daemon, you should create a script something
 	like this one, perhaps calling it <code class="filename">startsmb</code>.
 	</p><pre class="programlisting">
@@ -280,7 +280,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 	If you use the SVR4-style init system, you may like to look at the
 	<code class="filename">examples/svr4-startup</code> script to make Samba fit
 	into that system.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688678"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688822"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>
 	Red Hat Linux has not always included all Samba components in the standard installation.
 	So versions of Red Hat Linux do not install the winbind utility, even though it is present
 	on the installation CDROM media. Check to see if the <code class="literal">winbindd</code> is present
@@ -313,7 +313,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 <code class="prompt">root# </code> chkconfig winbind on
 </pre><p>
 	Samba will be started automatically at every system reboot.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688800"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688945"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>
 	Novell SUSE Linux products automatically install all essential Samba components in a default installation.
 	Configure your <code class="filename">smb.conf</code> file, then execute the following to start Samba:
 </p><pre class="screen">
diff --git a/docs/htmldocs/Samba3-HOWTO/diagnosis.html b/docs/htmldocs/Samba3-HOWTO/diagnosis.html
index a9ce038cce..cb718946e5 100644
--- a/docs/htmldocs/Samba3-HOWTO/diagnosis.html
+++ b/docs/htmldocs/Samba3-HOWTO/diagnosis.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�38.�The Samba Checklist</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="next" href="problems.html" title="Chapter�39.�Analyzing and Solving Samba Problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�38.�The Samba Checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter�38.�The Samba Checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="diagnosis.html#id2682610">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682648">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682941">The Tests</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682610"></a>Introduction</h2></div></div></div><p>
-<a class="indexterm" name="id2682617"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�38.�The Samba Checklist</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="next" href="problems.html" title="Chapter�39.�Analyzing and Solving Samba Problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�38.�The Samba Checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter�38.�The Samba Checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="diagnosis.html#id2682772">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682811">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2683103">The Tests</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682772"></a>Introduction</h2></div></div></div><p>
+<a class="indexterm" name="id2682780"></a>
 This file contains a list of tests you can perform to validate your
 Samba server. It also tells you what the likely cause of the problem
 is if it fails any one of these steps. If it passes all these tests,
@@ -14,7 +14,7 @@ to solve a problem.
 If you send one of the Samba mailing lists  an email saying, &#8220;<span class="quote">It does not work,</span>&#8221;
 and you have not followed this test procedure, you should not be surprised
 if your email is ignored.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682648"></a>Assumptions</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682811"></a>Assumptions</h2></div></div></div><p>
 In all of the tests, it is assumed you have a Samba server called 
 BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.
 </p><p>
@@ -24,31 +24,31 @@ It is also assumed you know the name of an available share in your
 <code class="filename">smb.conf</code>. I for our examples this share is called <em class="parameter"><code>tmp</code></em>.
 You can add a <em class="parameter"><code>tmp</code></em> share like this by adding the
 lines shown in <a class="link" href="diagnosis.html#tmpshare" title="Example�38.1.�smb.conf with [tmp] Share">the next example</a>.
-</p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example�38.1.�smb.conf with [tmp] Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[tmp]</code></em></td></tr><tr><td><a class="indexterm" name="id2682719"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id2682731"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id2682743"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+</p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example�38.1.�smb.conf with [tmp] Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[tmp]</code></em></td></tr><tr><td><a class="indexterm" name="id2682882"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id2682893"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id2682905"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 These tests assume version 3.0.0 or later of the Samba suite.
 Some commands shown did not exist in earlier versions. 
 </p></div><p>
-<a class="indexterm" name="id2682764"></a>
-<a class="indexterm" name="id2682771"></a>
-<a class="indexterm" name="id2682778"></a>
+<a class="indexterm" name="id2682926"></a>
+<a class="indexterm" name="id2682933"></a>
+<a class="indexterm" name="id2682940"></a>
 Please pay attention to the error messages you receive. If any error message
 reports that your server is being unfriendly, you should first check that your
 IP name resolution is correctly set up. Make sure your <code class="filename">/etc/resolv.conf</code>
 file points to name servers that really do exist.
 </p><p>
-<a class="indexterm" name="id2682798"></a>
-<a class="indexterm" name="id2682805"></a>
-<a class="indexterm" name="id2682812"></a>
-<a class="indexterm" name="id2682819"></a>
+<a class="indexterm" name="id2682961"></a>
+<a class="indexterm" name="id2682968"></a>
+<a class="indexterm" name="id2682974"></a>
+<a class="indexterm" name="id2682981"></a>
 Also, if you do not have DNS server access for name resolution, please check
 that the settings for your <code class="filename">smb.conf</code> file results in <em class="parameter"><code>dns proxy = no</code></em>. The
 best way to check this is with <code class="literal">testparm smb.conf</code>.
 </p><p>
-<a class="indexterm" name="id2682850"></a>
-<a class="indexterm" name="id2682856"></a>
-<a class="indexterm" name="id2682863"></a>
-<a class="indexterm" name="id2682870"></a>
-<a class="indexterm" name="id2682877"></a>
+<a class="indexterm" name="id2683012"></a>
+<a class="indexterm" name="id2683019"></a>
+<a class="indexterm" name="id2683025"></a>
+<a class="indexterm" name="id2683032"></a>
+<a class="indexterm" name="id2683039"></a>
 It is helpful to monitor the log files during testing by using the
 <code class="literal">tail -F log_file_name</code> in a separate
 terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). 
@@ -59,36 +59,36 @@ depending on how or if you specified logging in your <code class="filename">smb.
 </p><p>
 If you make changes to your <code class="filename">smb.conf</code> file while going through these test,
 remember to restart <span class="application">smbd</span> and <span class="application">nmbd</span>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2682941"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id2682947"></a><p class="title"><b>Procedure�38.1.�Diagnosing Your Samba Server</b></p><ol type="1"><li><p>
-<a class="indexterm" name="id2682959"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2683103"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id2683109"></a><p class="title"><b>Procedure�38.1.�Diagnosing Your Samba Server</b></p><ol type="1"><li><p>
+<a class="indexterm" name="id2683122"></a>
 In the directory in which you store your <code class="filename">smb.conf</code> file, run the command
 <code class="literal">testparm smb.conf</code>. If it reports any errors, then your <code class="filename">smb.conf</code>
 configuration file is faulty.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2682990"></a>
-<a class="indexterm" name="id2682997"></a>
+<a class="indexterm" name="id2683153"></a>
+<a class="indexterm" name="id2683160"></a>
 Your <code class="filename">smb.conf</code> file may be located in <code class="filename">/etc/samba</code>
 or in <code class="filename">/usr/local/samba/lib</code>.
 </p></div></li><li><p>
-<a class="indexterm" name="id2683032"></a>
+<a class="indexterm" name="id2683194"></a>
 Run the command <code class="literal">ping BIGSERVER</code> from the PC and
 <code class="literal">ping ACLIENT</code> from the UNIX box. If you do not get a valid response,
 then your TCP/IP software is not correctly installed. 
 </p><p>
 You will need to start a &#8220;<span class="quote">DOS prompt</span>&#8221; window on the PC to run ping.
 </p><p>
-<a class="indexterm" name="id2683064"></a>
-<a class="indexterm" name="id2683071"></a>
-<a class="indexterm" name="id2683077"></a>
+<a class="indexterm" name="id2683226"></a>
+<a class="indexterm" name="id2683233"></a>
+<a class="indexterm" name="id2683240"></a>
 If you get a message saying &#8220;<span class="quote"><span class="errorname">host not found</span></span>&#8221; or a similar message, then
 your DNS software or <code class="filename">/etc/hosts</code> file is not correctly set up.  If using DNS, check that
 the <code class="filename">/etc/resolv.conf</code> has correct, current, entries in it. It is possible to run
 Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the
 remainder of these tests.
 </p><p>
-<a class="indexterm" name="id2683110"></a>
-<a class="indexterm" name="id2683117"></a>
-<a class="indexterm" name="id2683123"></a>
+<a class="indexterm" name="id2683272"></a>
+<a class="indexterm" name="id2683279"></a>
+<a class="indexterm" name="id2683286"></a>
 Another reason why ping might fail is if your host is running firewall 
 software. You will need to relax the rules to let in the workstation
 in question, perhaps by allowing access from another subnet (on Linux
@@ -98,8 +98,8 @@ or <code class="literal">iptables</code>).
 Modern Linux distributions install ipchains/iptables by default. 
 This is a common problem that is often overlooked.
 </p></div><p>
-<a class="indexterm" name="id2683158"></a>
-<a class="indexterm" name="id2683165"></a>
+<a class="indexterm" name="id2683321"></a>
+<a class="indexterm" name="id2683327"></a>
 If you wish to check what firewall rules may be present in a system under test, simply run
 <code class="literal">iptables -L -v</code>, or if <em class="parameter"><code>ipchains</code></em>-based firewall rules are in use,
 <code class="literal">ipchains -L -v</code>.
@@ -133,12 +133,12 @@ Chain reject_func (0 references)
 Run the command <code class="literal">smbclient -L BIGSERVER</code>
 on the UNIX box. You should get back a list of available shares. 
 </p><p>
-<a class="indexterm" name="id2683240"></a>
-<a class="indexterm" name="id2683247"></a>
-<a class="indexterm" name="id2683254"></a>
-<a class="indexterm" name="id2683261"></a>
-<a class="indexterm" name="id2683268"></a>
-<a class="indexterm" name="id2683275"></a>
+<a class="indexterm" name="id2683403"></a>
+<a class="indexterm" name="id2683410"></a>
+<a class="indexterm" name="id2683416"></a>
+<a class="indexterm" name="id2683423"></a>
+<a class="indexterm" name="id2683430"></a>
+<a class="indexterm" name="id2683437"></a>
 If you get an error message containing the string &#8220;<span class="quote">bad password</span>&#8221;, then
 you probably have either an incorrect <em class="parameter"><code>hosts allow</code></em>, 
 <em class="parameter"><code>hosts deny</code></em>, or <em class="parameter"><code>valid users</code></em> line in your 
@@ -146,15 +146,15 @@ you probably have either an incorrect <em class="parameter"><code>hosts allow</c
 temporarily remove any <em class="parameter"><code>hosts allow</code></em>, <em class="parameter"><code>hosts deny</code></em>,
 <em class="parameter"><code>valid users</code></em>, or <em class="parameter"><code>invalid users</code></em> lines.
 </p><p>
-<a class="indexterm" name="id2683345"></a>
+<a class="indexterm" name="id2683508"></a>
 If you get a message <code class="literal">connection refused</code> response, then the <code class="literal">smbd</code> server may
 not be running. If you installed it in <code class="filename">inetd.conf</code>, then you probably edited
 that file incorrectly. If you installed it as a daemon, then check that
 it is running and check that the netbios-ssn port is in a LISTEN
 state using <code class="literal">netstat -a</code>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2683384"></a>
-<a class="indexterm" name="id2683391"></a>
+<a class="indexterm" name="id2683547"></a>
+<a class="indexterm" name="id2683554"></a>
 Some UNIX/Linux systems use <code class="literal">xinetd</code> in place of
 <code class="literal">inetd</code>. Check your system documentation for the location
 of the control files for your particular system implementation of
@@ -171,36 +171,36 @@ files exist.
 There are a number of reasons for which smbd may refuse or decline
 a session request. The most common of these involve one or more of
 the <code class="filename">smb.conf</code> file entries as shown in <a class="link" href="diagnosis.html#modif1" title="Example�38.2.�Configuration for Allowing Connections Only from a Certain Subnet">the next example</a>.
-</p><div class="example"><a name="modif1"></a><p class="title"><b>Example�38.2.�Configuration for Allowing Connections Only from a Certain Subnet</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2683504"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683515"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id2683527"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id2683539"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2683554"></a>
+</p><div class="example"><a name="modif1"></a><p class="title"><b>Example�38.2.�Configuration for Allowing Connections Only from a Certain Subnet</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2683666"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683678"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id2683689"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id2683701"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2683716"></a>
 In <a class="link" href="diagnosis.html#modif1" title="Example�38.2.�Configuration for Allowing Connections Only from a Certain Subnet">Configuration for Allowing Connections Only from a Certain Subnet</a>, no
 allowance has been made for any session requests that will automatically translate to the loopback adapter
 address 127.0.0.1.  To solve this problem, change these lines as shown in <a class="link" href="diagnosis.html#modif2" title="Example�38.3.�Configuration for Allowing Connections from a Certain Subnet and localhost">the following
 example</a>.
-</p><div class="example"><a name="modif2"></a><p class="title"><b>Example�38.3.�Configuration for Allowing Connections from a Certain Subnet and localhost</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2683606"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683618"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2683630"></a><em class="parameter"><code>interfaces = eth0 lo</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2683645"></a>
-<a class="indexterm" name="id2683651"></a>
+</p><div class="example"><a name="modif2"></a><p class="title"><b>Example�38.3.�Configuration for Allowing Connections from a Certain Subnet and localhost</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2683768"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683780"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2683792"></a><em class="parameter"><code>interfaces = eth0 lo</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2683807"></a>
+<a class="indexterm" name="id2683814"></a>
 Another common cause of these two errors is having something already running on port <code class="constant">139</code>,
 such as Samba (<span class="application">smbd</span> is running from <span class="application">inetd</span> already) or Digital's Pathworks. Check
 your <code class="filename">inetd.conf</code> file before trying to start <span class="application">smbd</span> as a daemon  it can avoid a
 lot of frustration!
 </p><p>
-<a class="indexterm" name="id2683696"></a>
-<a class="indexterm" name="id2683702"></a>
-<a class="indexterm" name="id2683709"></a>
-<a class="indexterm" name="id2683716"></a>
-<a class="indexterm" name="id2683723"></a>
+<a class="indexterm" name="id2683858"></a>
+<a class="indexterm" name="id2683865"></a>
+<a class="indexterm" name="id2683872"></a>
+<a class="indexterm" name="id2683878"></a>
+<a class="indexterm" name="id2683885"></a>
 And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address
 settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask
 settings are correct and that Samba has correctly noted these in the <code class="filename">log.nmbd</code> file.
 </p></li><li><p>
-<a class="indexterm" name="id2683749"></a>
+<a class="indexterm" name="id2683912"></a>
 Run the command <code class="literal">nmblookup -B BIGSERVER __SAMBA__</code>.
 You should get back the IP address of your Samba server.
 </p><p>
-<a class="indexterm" name="id2683767"></a>
-<a class="indexterm" name="id2683774"></a>
-<a class="indexterm" name="id2683781"></a>
+<a class="indexterm" name="id2683929"></a>
+<a class="indexterm" name="id2683936"></a>
+<a class="indexterm" name="id2683943"></a>
 If you do not, then <span class="application">nmbd</span> is incorrectly installed. Check your <code class="filename">inetd.conf</code>
 if you run it from there, or that the daemon is running and listening to UDP port 137.
 </p><p>
@@ -209,7 +209,7 @@ parameters on the command line. If this is the case, then create a
 one-line script that contains the right parameters and run that from
 inetd.
 </p></li><li><p>
-<a class="indexterm" name="id2683817"></a>
+<a class="indexterm" name="id2683980"></a>
 Run the command <code class="literal">nmblookup -B ACLIENT `*'</code>.
 </p><p>
 You should get the PC's IP address back. If you do not, then the client
@@ -228,7 +228,7 @@ not catch all of the responses in the short time it listens. You
 should see the <code class="literal">got a positive name query response</code>
 messages from several hosts.
 </p><p>
-<a class="indexterm" name="id2683875"></a>
+<a class="indexterm" name="id2684037"></a>
 If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your
 broadcast address through its automatic mechanism. In this case you should experiment with the <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask.
 </p><p>
@@ -238,7 +238,7 @@ If your PC and server aren't on the same subnet, then you will need to use the
 This test will probably fail if your subnet mask and broadcast address are
 not correct. (Refer to test 3 notes above).
 </p></li><li><p>
-<a class="indexterm" name="id2683927"></a>
+<a class="indexterm" name="id2684090"></a>
 Run the command <code class="literal">smbclient //BIGSERVER/TMP</code>. You should 
 then be prompted for a password. You should use the password of the account
 with which you are logged into the UNIX box. If you want to test with
@@ -266,20 +266,20 @@ If it says &#8220;<span class="quote"><span class="errorname">bad password,</spa
 	You enabled password encryption but didn't map UNIX to Samba users. Run
 	<code class="literal">smbpasswd -a username</code>
 	</p></li></ol></div><p>
-<a class="indexterm" name="id2684112"></a>
-<a class="indexterm" name="id2684119"></a>
-<a class="indexterm" name="id2684126"></a>
-<a class="indexterm" name="id2684132"></a>
+<a class="indexterm" name="id2684274"></a>
+<a class="indexterm" name="id2684281"></a>
+<a class="indexterm" name="id2684288"></a>
+<a class="indexterm" name="id2684294"></a>
 Once connected, you should be able to use the commands <code class="literal">dir</code>, <code class="literal">get</code>,
 <code class="literal">put</code>, and so on. Type <code class="literal">help command</code> for instructions. You should
 especially check that the amount of free disk space shown is correct when you type <code class="literal">dir</code>.
 </p></li><li><p>
-<a class="indexterm" name="id2684179"></a>
+<a class="indexterm" name="id2684341"></a>
 On the PC, type the command <code class="literal">net view \\BIGSERVER</code>. You will 
 need to do this from within a DOS prompt window. You should get back a 
 list of shares available on the server.
 </p><p>
-<a class="indexterm" name="id2684198"></a>
+<a class="indexterm" name="id2684360"></a>
 If you get a message <code class="literal">network name not found</code> or similar error, then NetBIOS
 name resolution is not working. This is usually caused by a problem in <code class="literal">nmbd</code>.
 To overcome it, you could do one of the following (you only need to choose one of them):
diff --git a/docs/htmldocs/Samba3-HOWTO/domain-member.html b/docs/htmldocs/Samba3-HOWTO/domain-member.html
index 08bfd53677..74124d0879 100644
--- a/docs/htmldocs/Samba3-HOWTO/domain-member.html
+++ b/docs/htmldocs/Samba3-HOWTO/domain-member.html
@@ -1,14 +1,14 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�6.�Domain Membership</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter�5.�Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter�7.�Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�6.�Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter�6.�Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="domain-member.html#id2569109">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570619">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572129">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573414">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573692">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2569052"></a>
-<a class="indexterm" name="id2569059"></a>
-<a class="indexterm" name="id2569066"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�6.�Domain Membership</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter�5.�Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter�7.�Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�6.�Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter�6.�Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="domain-member.html#id2569108">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570618">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572100">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573385">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573664">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2569050"></a>
+<a class="indexterm" name="id2569057"></a>
+<a class="indexterm" name="id2569064"></a>
 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 able to offer a viable option for many users.
 </p><p>
-<a class="indexterm" name="id2569086"></a>
-<a class="indexterm" name="id2569093"></a>
+<a class="indexterm" name="id2569084"></a>
+<a class="indexterm" name="id2569091"></a>
 This chapter covers background information pertaining to domain membership,
 the 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
@@ -16,10 +16,10 @@ within the current MS Windows networking world, and particularly in the
 UNIX/Linux networking and administration world, a considerable level of
 misinformation, incorrect understanding, and 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="id2569109"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2569117"></a>
-<a class="indexterm" name="id2569124"></a>
-<a class="indexterm" name="id2569131"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2569108"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2569116"></a>
+<a class="indexterm" name="id2569123"></a>
+<a class="indexterm" name="id2569130"></a>
 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 <acronym class="acronym">SSO</acronym> for short. This
@@ -27,68 +27,68 @@ 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>
-<a class="indexterm" name="id2569163"></a>
-<a class="indexterm" name="id2569170"></a>
-<a class="indexterm" name="id2569176"></a>
-<a class="indexterm" name="id2569183"></a>
+<a class="indexterm" name="id2569161"></a>
+<a class="indexterm" name="id2569168"></a>
+<a class="indexterm" name="id2569175"></a>
+<a class="indexterm" name="id2569182"></a>
 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. Domain membership has many advantages:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2569203"></a>
+	<a class="indexterm" name="id2569201"></a>
 	MS Windows workstation users get the benefit of SSO.
 	</p></li><li><p>
-	<a class="indexterm" name="id2569215"></a>
-	<a class="indexterm" name="id2569222"></a>
-	<a class="indexterm" name="id2569229"></a>
-	<a class="indexterm" name="id2569236"></a>
+	<a class="indexterm" name="id2569213"></a>
+	<a class="indexterm" name="id2569220"></a>
+	<a class="indexterm" name="id2569227"></a>
+	<a class="indexterm" name="id2569234"></a>
 	Domain user access rights and file ownership/access controls can be set
 	from the single Domain Security Account Manager (SAM) database 
 	(works with domain member servers as well as with MS Windows workstations
 	that are domain members).
 	</p></li><li><p>
-	<a class="indexterm" name="id2569250"></a>
-	<a class="indexterm" name="id2569257"></a>
+	<a class="indexterm" name="id2569249"></a>
+	<a class="indexterm" name="id2569256"></a>
 	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>
-	<a class="indexterm" name="id2569276"></a>
-	<a class="indexterm" name="id2569283"></a>
-	<a class="indexterm" name="id2569290"></a>
-	<a class="indexterm" name="id2569297"></a>
+	<a class="indexterm" name="id2569275"></a>
+	<a class="indexterm" name="id2569282"></a>
+	<a class="indexterm" name="id2569288"></a>
+	<a class="indexterm" name="id2569295"></a>
 	Domain member workstations can be better controlled through the use of
 	policy files (<code class="filename">NTConfig.POL</code>) and desktop profiles.
 	</p></li><li><p>
-	<a class="indexterm" name="id2569316"></a>
-	<a class="indexterm" name="id2569323"></a>
-	<a class="indexterm" name="id2569330"></a>
+	<a class="indexterm" name="id2569315"></a>
+	<a class="indexterm" name="id2569322"></a>
+	<a class="indexterm" name="id2569328"></a>
 	Through the use of logon scripts, users can be given transparent access to network
 	applications that run off application servers.
 	</p></li><li><p>
-	<a class="indexterm" name="id2569344"></a>
-	<a class="indexterm" name="id2569351"></a>
-	<a class="indexterm" name="id2569357"></a>
-	<a class="indexterm" name="id2569364"></a>
+	<a class="indexterm" name="id2569342"></a>
+	<a class="indexterm" name="id2569349"></a>
+	<a class="indexterm" name="id2569356"></a>
+	<a class="indexterm" name="id2569362"></a>
 	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 backend-ed 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><p>
-<a class="indexterm" name="id2569393"></a>
-<a class="indexterm" name="id2569399"></a>
-<a class="indexterm" name="id2569406"></a>
-<a class="indexterm" name="id2569413"></a>
+<a class="indexterm" name="id2569391"></a>
+<a class="indexterm" name="id2569397"></a>
+<a class="indexterm" name="id2569404"></a>
+<a class="indexterm" name="id2569411"></a>
 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 &#8220;<span class="quote">computer account.</span>&#8221; The
 purpose of the machine trust account is to prevent a rogue user and domain controller from colluding to gain
 access to a domain member workstation.
 </p><p>
-<a class="indexterm" name="id2569432"></a>
-<a class="indexterm" name="id2569442"></a>
-<a class="indexterm" name="id2569449"></a>
-<a class="indexterm" name="id2569456"></a>
-<a class="indexterm" name="id2569463"></a>
+<a class="indexterm" name="id2569431"></a>
+<a class="indexterm" name="id2569440"></a>
+<a class="indexterm" name="id2569447"></a>
+<a class="indexterm" name="id2569454"></a>
+<a class="indexterm" name="id2569461"></a>
 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, participating in domain security operations, and gaining access to domain user/group
@@ -96,10 +96,10 @@ accounts. Windows NT/200x/XP Professional clients use machine trust accounts, bu
 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 class="indexterm" name="id2569484"></a>
-<a class="indexterm" name="id2569491"></a>
-<a class="indexterm" name="id2569497"></a>
-<a class="indexterm" name="id2569504"></a>
+<a class="indexterm" name="id2569482"></a>
+<a class="indexterm" name="id2569489"></a>
+<a class="indexterm" name="id2569496"></a>
+<a class="indexterm" name="id2569502"></a>
 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. A Samba PDC, however, stores
@@ -107,69 +107,69 @@ each Machine Trust Account in two parts,
 as follows:
 
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2569521"></a>
-	<a class="indexterm" name="id2569528"></a>
-	<a class="indexterm" name="id2569535"></a>
+	<a class="indexterm" name="id2569519"></a>
+	<a class="indexterm" name="id2569526"></a>
+	<a class="indexterm" name="id2569533"></a>
 	A domain security account (stored in the <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>) that has been configured in
 	the <code class="filename">smb.conf</code> file. The precise nature of the account information that is stored depends on the type of
 	backend database that has been chosen.
 	</p><p>
-	<a class="indexterm" name="id2569567"></a>
-	<a class="indexterm" name="id2569574"></a>
-	<a class="indexterm" name="id2569581"></a>
-	<a class="indexterm" name="id2569587"></a>
-	<a class="indexterm" name="id2569594"></a>
-	<a class="indexterm" name="id2569601"></a>
+	<a class="indexterm" name="id2569565"></a>
+	<a class="indexterm" name="id2569572"></a>
+	<a class="indexterm" name="id2569579"></a>
+	<a class="indexterm" name="id2569585"></a>
+	<a class="indexterm" name="id2569592"></a>
+	<a class="indexterm" name="id2569599"></a>
 	The older format of this data is the <code class="filename">smbpasswd</code> database
 	that 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>
-	<a class="indexterm" name="id2569623"></a>
-	<a class="indexterm" name="id2569630"></a>
-	<a class="indexterm" name="id2569637"></a>
-	<a class="indexterm" name="id2569643"></a>
+	<a class="indexterm" name="id2569621"></a>
+	<a class="indexterm" name="id2569628"></a>
+	<a class="indexterm" name="id2569635"></a>
+	<a class="indexterm" name="id2569642"></a>
 	The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older
 	<code class="filename">smbpasswd</code> file did. The extra information enables new user account controls to be
 	implemented.
 	</p></li><li><p>
-	<a class="indexterm" name="id2569664"></a>
-	<a class="indexterm" name="id2569671"></a>
+	<a class="indexterm" name="id2569662"></a>
+	<a class="indexterm" name="id2569669"></a>
 	A corresponding UNIX account, typically stored in <code class="filename">/etc/passwd</code>. Work is in progress to
 	allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature
 	of the early releases of Samba-3, and is not currently planned for release either.
 	</p></li></ul></div><p>
 </p><p>
-<a class="indexterm" name="id2569697"></a>
+<a class="indexterm" name="id2569695"></a>
 There are three ways to create Machine Trust Accounts:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2569713"></a>
+	<a class="indexterm" name="id2569711"></a>
 	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="id2569727"></a>
-	<a class="indexterm" name="id2569734"></a>
+	<a class="indexterm" name="id2569725"></a>
+	<a class="indexterm" name="id2569732"></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 as long as the user is
 	logged on as the administrator account.
 	</p></li><li><p>
-	<a class="indexterm" name="id2569750"></a>
-	<a class="indexterm" name="id2569757"></a>
+	<a class="indexterm" name="id2569748"></a>
+	<a class="indexterm" name="id2569755"></a>
 	&#8220;<span class="quote">On-the-fly</span>&#8221; 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><p>
-<a class="indexterm" name="id2569776"></a>
-<a class="indexterm" name="id2569782"></a>
+<a class="indexterm" name="id2569774"></a>
+<a class="indexterm" name="id2569781"></a>
 Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine
 trust account creation. This is a matter of the administrator's choice.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569796"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
-<a class="indexterm" name="id2569804"></a>
-<a class="indexterm" name="id2569811"></a>
-<a class="indexterm" name="id2569817"></a>
-<a class="indexterm" name="id2569823"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569794"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
+<a class="indexterm" name="id2569803"></a>
+<a class="indexterm" name="id2569809"></a>
+<a class="indexterm" name="id2569815"></a>
+<a class="indexterm" name="id2569822"></a>
 The first step in manually creating a Machine Trust Account is to manually
 create the corresponding UNIX account in <code class="filename">/etc/passwd</code>. 
 This can be done using <code class="literal">vipw</code> or another &#8220;<span class="quote">adduser</span>&#8221; command
@@ -183,25 +183,25 @@ a Linux-based Samba server:
 <code class="prompt">root# </code><strong class="userinput"><code>passwd -l <em class="replaceable"><code>machine_name</code></em>$</code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2569892"></a>
-<a class="indexterm" name="id2569899"></a>
-<a class="indexterm" name="id2569906"></a>
+<a class="indexterm" name="id2569890"></a>
+<a class="indexterm" name="id2569897"></a>
+<a class="indexterm" name="id2569904"></a>
 In the example above there is an existing system group &#8220;<span class="quote">machines</span>&#8221; which is used
 as the primary group for all machine accounts. In the following examples the &#8220;<span class="quote">machines</span>&#8221; group
 numeric GID is 100.
 </p><p>
-<a class="indexterm" name="id2569926"></a>
-<a class="indexterm" name="id2569933"></a>
+<a class="indexterm" name="id2569924"></a>
+<a class="indexterm" name="id2569931"></a>
 On *BSD systems, this can be done using the <code class="literal">chpass</code> utility:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>chpass -a \
 '<em class="replaceable"><code>machine_name</code></em>$:*:101:100::0:0:Windows <em class="replaceable"><code>machine_name</code></em>:/dev/null:/sbin/nologin'</code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2569974"></a>
-<a class="indexterm" name="id2569981"></a>
-<a class="indexterm" name="id2569987"></a>
-<a class="indexterm" name="id2569994"></a>
+<a class="indexterm" name="id2569972"></a>
+<a class="indexterm" name="id2569979"></a>
+<a class="indexterm" name="id2569985"></a>
+<a class="indexterm" name="id2569992"></a>
 The <code class="filename">/etc/passwd</code> entry will list the machine name 
 with a &#8220;<span class="quote">$</span>&#8221; appended, and will not have a password, will have a null shell and no 
 home directory. For example, a machine named &#8220;<span class="quote">doppy</span>&#8221; would have an 
@@ -210,9 +210,9 @@ home directory. For example, a machine named &#8220;<span class="quote">doppy</s
 doppy$:x:505:100:<em class="replaceable"><code>machine_nickname</code></em>:/dev/null:/bin/false
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2570036"></a>
-<a class="indexterm" name="id2570043"></a>
-<a class="indexterm" name="id2570050"></a>
+<a class="indexterm" name="id2570035"></a>
+<a class="indexterm" name="id2570042"></a>
+<a class="indexterm" name="id2570048"></a>
 in which <em class="replaceable"><code>machine_nickname</code></em> can be any
 descriptive name for the client, such as BasementComputer.
 <em class="replaceable"><code>machine_name</code></em> absolutely must be the NetBIOS
@@ -220,9 +220,9 @@ name of the client to be joined to the domain. The &#8220;<span class="quote">$<
 appended to the NetBIOS name of the client or Samba will not recognize
 this as a Machine Trust Account.
 </p><p>
-<a class="indexterm" name="id2570076"></a>
-<a class="indexterm" name="id2570083"></a>
-<a class="indexterm" name="id2570090"></a>
+<a class="indexterm" name="id2570074"></a>
+<a class="indexterm" name="id2570081"></a>
+<a class="indexterm" name="id2570088"></a>
 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 
@@ -232,48 +232,48 @@ as shown here:
 <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -a -m <em class="replaceable"><code>machine_name</code></em></code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2570131"></a>
-<a class="indexterm" name="id2570138"></a>
-<a class="indexterm" name="id2570145"></a>
-<a class="indexterm" name="id2570152"></a>
+<a class="indexterm" name="id2570129"></a>
+<a class="indexterm" name="id2570136"></a>
+<a class="indexterm" name="id2570143"></a>
+<a class="indexterm" name="id2570150"></a>
 where <em class="replaceable"><code>machine_name</code></em> 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>
-<a class="indexterm" name="id2570174"></a>
-<a class="indexterm" name="id2570181"></a>
-<a class="indexterm" name="id2570187"></a>
-<a class="indexterm" name="id2570194"></a>
-<a class="indexterm" name="id2570201"></a>
+<a class="indexterm" name="id2570172"></a>
+<a class="indexterm" name="id2570179"></a>
+<a class="indexterm" name="id2570185"></a>
+<a class="indexterm" name="id2570192"></a>
+<a class="indexterm" name="id2570199"></a>
 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="id2570210"></a>
+<a class="indexterm" name="id2570209"></a>
 the <span class="application">Server Manager</span>. From the time at which the 
 account is created to the time 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="id2570233"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
-<a class="indexterm" name="id2570241"></a>
-<a class="indexterm" name="id2570248"></a>
-<a class="indexterm" name="id2570256"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570231"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
+<a class="indexterm" name="id2570240"></a>
+<a class="indexterm" name="id2570247"></a>
+<a class="indexterm" name="id2570254"></a>
 A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> is essential
 for machine trust accounts to be automatically created. This applies no matter whether
 you use automatic account creation or the NT4 Domain Server Manager.
 </p><p>
-<a class="indexterm" name="id2570281"></a>
-<a class="indexterm" name="id2570288"></a>
-<a class="indexterm" name="id2570295"></a>
-<a class="indexterm" name="id2570301"></a>
+<a class="indexterm" name="id2570280"></a>
+<a class="indexterm" name="id2570286"></a>
+<a class="indexterm" name="id2570293"></a>
+<a class="indexterm" name="id2570300"></a>
 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>,
 the tool of choice is the package called <code class="literal">SRVTOOLS.EXE</code>. 
 When executed in the target directory it will unpack <code class="literal">SrvMgr.exe</code>
 and <code class="literal">UsrMgr.exe</code> (both are domain management tools for MS Windows NT4 workstation).
 </p><p>
-<a class="indexterm" name="id2570340"></a>
-<a class="indexterm" name="id2570346"></a>
+<a class="indexterm" name="id2570338"></a>
+<a class="indexterm" name="id2570345"></a>
 If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product,
  you should download the <code class="literal">Nexus.exe</code> package from the Microsoft Web site.
 When executed from the target directory, it will unpack the same tools but for use on 
@@ -283,10 +283,10 @@ Further information about these tools may be obtained from Knowledge Base articl
 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">173673</a>, and
 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a>
 </p><p>
-<a class="indexterm" name="id2570391"></a>
-<a class="indexterm" name="id2570398"></a>
+<a class="indexterm" name="id2570389"></a>
+<a class="indexterm" name="id2570396"></a>
 Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps:
-</p><div class="procedure"><a name="id2570413"></a><p class="title"><b>Procedure�6.1.�Server Manager Account Machine Account Management</b></p><ol type="1"><li><p>
+</p><div class="procedure"><a name="id2570411"></a><p class="title"><b>Procedure�6.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 <span class="guimenuitem">Select Domain</span>.
@@ -303,84 +303,82 @@ Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains)
 	<span class="guilabel">Add NT Workstation of Server</span>, then
 	enter the machine name in the field provided, and 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="id2570513"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
-<a class="indexterm" name="id2570522"></a>
+	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570512"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
+<a class="indexterm" name="id2570520"></a>
 The third (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>
-<a class="indexterm" name="id2570537"></a>
-<a class="indexterm" name="id2570547"></a>
-<a class="indexterm" name="id2570554"></a>
+<a class="indexterm" name="id2570536"></a>
+<a class="indexterm" name="id2570545"></a>
+<a class="indexterm" name="id2570552"></a>
 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 <code class="filename">smb.conf</code>. This method is not required; however, corresponding UNIX
 accounts may also be created manually.
 </p><p>
-<a class="indexterm" name="id2570575"></a>
-<a class="indexterm" name="id2570582"></a>
+<a class="indexterm" name="id2570574"></a>
+<a class="indexterm" name="id2570580"></a>
 Here is an example for a Red Hat Linux system:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2570604"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</code></em></td></tr></table><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570619"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2570603"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</code></em></td></tr></table><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570618"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>
 The procedure for making an MS Windows workstation or 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="id2570630"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
-<a class="indexterm" name="id2570638"></a>
-<a class="indexterm" name="id2570645"></a>
-<a class="indexterm" name="id2570655"></a>
-<a class="indexterm" name="id2570662"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570628"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
+<a class="indexterm" name="id2570636"></a>
+<a class="indexterm" name="id2570643"></a>
+<a class="indexterm" name="id2570653"></a>
+<a class="indexterm" name="id2570660"></a>
 	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.
+	an account and password that has privileges to create  machine accounts in the domain.
+	A Samba administrator account (i.e., a Samba account that has <code class="constant">root</code> privileges on the
+	Samba server) must be entered here; the operation will fail if an ordinary user
+	account is given. 
 	</p><p>
-	A Samba administrator account (i.e., a Samba account that has <code class="literal">root</code> privileges on the
-	Samba server) must be entered here; the operation will fail if an ordinary user account is given.
-	The necessary privilege can be assured by creating a Samba SAM account for <code class="literal">root</code> or
-	by granting the <code class="literal">SeMachineAccountPrivilege</code> privilege to the user account.
-	</p><p>
-<a class="indexterm" name="id2570701"></a>
-<a class="indexterm" name="id2570708"></a>
+<a class="indexterm" name="id2570679"></a>
+<a class="indexterm" name="id2570686"></a>
 	For security reasons, the password for this administrator account should be set
 	to a password that is other than that used for the root user in <code class="filename">/etc/passwd</code>.
 	</p><p>
-<a class="indexterm" name="id2570726"></a>
-<a class="indexterm" name="id2570733"></a>
-<a class="indexterm" name="id2570740"></a>
-<a class="indexterm" name="id2570747"></a>
+<a class="indexterm" name="id2570705"></a>
+<a class="indexterm" name="id2570712"></a>
+<a class="indexterm" name="id2570719"></a>
+<a class="indexterm" name="id2570725"></a>
 	The name of the account that is used to create domain member machine trust accounts can be
 	anything the network administrator may choose. If it is other than <code class="constant">root</code>,
 	then this is easily mapped to <code class="constant">root</code> in the file named in the <code class="filename">smb.conf</code> parameter
 	<a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map = /etc/samba/smbusers</a>.
 	</p><p>
-<a class="indexterm" name="id2570787"></a>
-<a class="indexterm" name="id2570794"></a>
-<a class="indexterm" name="id2570801"></a>
+<a class="indexterm" name="id2570766"></a>
+<a class="indexterm" name="id2570772"></a>
+<a class="indexterm" name="id2570779"></a>
 	The session key of the Samba administrator 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="id2570814"></a>Windows NT4 Client</h4></div></div></div><p>
-<a class="indexterm" name="id2570822"></a>
-<a class="indexterm" name="id2570829"></a>
-<a class="indexterm" name="id2570836"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570792"></a>Windows NT4 Client</h4></div></div></div><p>
+<a class="indexterm" name="id2570800"></a>
+<a class="indexterm" name="id2570807"></a>
+<a class="indexterm" name="id2570814"></a>
 	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>
+<a class="indexterm" name="id2570834"></a>
+<a class="indexterm" name="id2570841"></a>
+<a class="indexterm" name="id2570848"></a>
 <a class="indexterm" name="id2570855"></a>
-<a class="indexterm" name="id2570862"></a>
-<a class="indexterm" name="id2570869"></a>
-<a class="indexterm" name="id2570876"></a>
 	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 administrator account when
 	prompted).
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570897"></a>Samba Client</h4></div></div></div><p>
-<a class="indexterm" name="id2570904"></a>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570875"></a>Samba Client</h4></div></div></div><p>
+<a class="indexterm" name="id2570883"></a>
 	Joining a Samba client to a domain is documented in <a class="link" href="domain-member.html#domain-member-server" title="Domain Member Server">the next section</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><p>
+<a class="indexterm" name="id2570914"></a>
+<a class="indexterm" name="id2570921"></a>
+<a class="indexterm" name="id2570928"></a>
 <a class="indexterm" name="id2570935"></a>
-<a class="indexterm" name="id2570942"></a>
-<a class="indexterm" name="id2570949"></a>
-<a class="indexterm" name="id2570956"></a>
 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. 
@@ -389,106 +387,106 @@ 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>
-<a class="indexterm" name="id2570982"></a>
-<a class="indexterm" name="id2570991"></a>
-<a class="indexterm" name="id2570998"></a>
-<a class="indexterm" name="id2571005"></a>
-<a class="indexterm" name="id2571012"></a>
-<a class="indexterm" name="id2571019"></a>
-<a class="indexterm" name="id2571025"></a>
-<a class="indexterm" name="id2571032"></a>
+<a class="indexterm" name="id2570953"></a>
+<a class="indexterm" name="id2570963"></a>
+<a class="indexterm" name="id2570970"></a>
+<a class="indexterm" name="id2570977"></a>
+<a class="indexterm" name="id2570983"></a>
+<a class="indexterm" name="id2570990"></a>
+<a class="indexterm" name="id2570997"></a>
+<a class="indexterm" name="id2571004"></a>
 Of course it should be clear that the authentication backend itself could be
 from any distributed directory architecture server that is supported by Samba.
 This can be LDAP (from OpenLDAP), or Sun's iPlanet, or Novell e-Directory
 Server, and so on.
 </em></span>
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2571048"></a>
-<a class="indexterm" name="id2571055"></a>
-<a class="indexterm" name="id2571062"></a>
+<a class="indexterm" name="id2571020"></a>
+<a class="indexterm" name="id2571027"></a>
+<a class="indexterm" name="id2571034"></a>
 When Samba is configured to use an LDAP or other identity management and/or
 directory service, it is Samba that continues to perform user and machine
 authentication. It should be noted that the LDAP server does not perform
 authentication handling in place of what Samba is designed to do.
 </p></div><p>
-<a class="indexterm" name="id2571077"></a>
-<a class="indexterm" name="id2571084"></a>
-<a class="indexterm" name="id2571092"></a>
+<a class="indexterm" name="id2571049"></a>
+<a class="indexterm" name="id2571056"></a>
+<a class="indexterm" name="id2571063"></a>
 Please refer to <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Domain Control</a>, for more information regarding
 how to create a domain machine account for a domain member server as well as for
 information on how to enable the Samba domain member machine to join the domain
 and be fully trusted by it.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571111"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><a class="link" href="domain-member.html#assumptions" title="Table�6.1.�Assumptions">Assumptions</a> lists names that are used in the remainder of this chapter.</p><div class="table"><a name="assumptions"></a><p class="title"><b>Table�6.1.�Assumptions</b></p><div class="table-contents"><table summary="Assumptions" border="1"><colgroup><col align="right"><col align="left"></colgroup><tbody><tr><td align="right">Samba DMS NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="right">Windows 200x/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="right">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="right">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div></div><br class="table-break"><p>
-<a class="indexterm" name="id2571195"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571082"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><a class="link" href="domain-member.html#assumptions" title="Table�6.1.�Assumptions">Assumptions</a> lists names that are used in the remainder of this chapter.</p><div class="table"><a name="assumptions"></a><p class="title"><b>Table�6.1.�Assumptions</b></p><div class="table-contents"><table summary="Assumptions" border="1"><colgroup><col align="right"><col align="left"></colgroup><tbody><tr><td align="right">Samba DMS NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="right">Windows 200x/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="right">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="right">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div></div><br class="table-break"><p>
+<a class="indexterm" name="id2571167"></a>
 First, you must edit your <code class="filename">smb.conf</code> file to tell Samba it should now use domain security.
 </p><p>
-<a class="indexterm" name="id2571211"></a>
-<a class="indexterm" name="id2571218"></a>
-<a class="indexterm" name="id2571225"></a>
-<a class="indexterm" name="id2571232"></a>
+<a class="indexterm" name="id2571183"></a>
+<a class="indexterm" name="id2571190"></a>
+<a class="indexterm" name="id2571197"></a>
+<a class="indexterm" name="id2571204"></a>
 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> line in the [global] section 
 of your <code class="filename">smb.conf</code> to read:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571263"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571234"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p>
 Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a
 standalone server and not as a domain member server. Domain security mode causes Samba to work within the
 domain security context.
 </p><p>
 Next change the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> line in the <em class="parameter"><code>[global]</code></em>
 section to read: 
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571311"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571282"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
 This is the name of the domain we are joining.
 </p><p>
-<a class="indexterm" name="id2571327"></a>
-<a class="indexterm" name="id2571334"></a>
+<a class="indexterm" name="id2571298"></a>
+<a class="indexterm" name="id2571305"></a>
 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a>
 set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC.
 This is the default setting if this parameter is not specified. There is no need to specify this
 parameter, but if it is specified in the <code class="filename">smb.conf</code> file, it must be set to <code class="constant">Yes</code>.
 </p><p>
-<a class="indexterm" name="id2571373"></a>
-<a class="indexterm" name="id2571379"></a>
-<a class="indexterm" name="id2571386"></a>
-<a class="indexterm" name="id2571393"></a>
+<a class="indexterm" name="id2571344"></a>
+<a class="indexterm" name="id2571351"></a>
+<a class="indexterm" name="id2571358"></a>
+<a class="indexterm" name="id2571364"></a>
 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> line in the [global]
 section to read: 
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571417"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571389"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>
 These are the PDC and BDCs 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>
-<a class="indexterm" name="id2571437"></a>
-<a class="indexterm" name="id2571444"></a>
-<a class="indexterm" name="id2571451"></a>
-<a class="indexterm" name="id2571458"></a>
+<a class="indexterm" name="id2571409"></a>
+<a class="indexterm" name="id2571416"></a>
+<a class="indexterm" name="id2571422"></a>
+<a class="indexterm" name="id2571430"></a>
 Alternatively, if you want smbd to determine automatically the list of domain controllers to use for
 authentication, you may set this line to be:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571473"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>
-<a class="indexterm" name="id2571485"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571445"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>
+<a class="indexterm" name="id2571456"></a>
 This method allows Samba to use exactly the same mechanism that NT does. The 
 method either uses broadcast-based name resolution, performs a WINS database
 lookup in order to find a domain controller against which to authenticate,
 or locates the domain controller using DNS name resolution.
 </p><p>
 To join the domain, run this command:
-<a class="indexterm" name="id2571500"></a>
+<a class="indexterm" name="id2571472"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>net rpc join -S DOMPDC -U<em class="replaceable"><code>Administrator%password</code></em></code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2571534"></a>
-<a class="indexterm" name="id2571541"></a>
-<a class="indexterm" name="id2571547"></a>
-<a class="indexterm" name="id2571554"></a>
+<a class="indexterm" name="id2571505"></a>
+<a class="indexterm" name="id2571512"></a>
+<a class="indexterm" name="id2571519"></a>
+<a class="indexterm" name="id2571526"></a>
 If the <code class="option">-S DOMPDC</code> argument is not given, the domain name will be obtained from <code class="filename">smb.conf</code> and
 the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name
 look up.
 </p><p>
-<a class="indexterm" name="id2571577"></a>
-<a class="indexterm" name="id2571584"></a>
-<a class="indexterm" name="id2571590"></a>
-<a class="indexterm" name="id2571597"></a>
+<a class="indexterm" name="id2571548"></a>
+<a class="indexterm" name="id2571555"></a>
+<a class="indexterm" name="id2571562"></a>
+<a class="indexterm" name="id2571569"></a>
 The machine is joining the domain DOM, and the PDC for that domain (the only machine
 that has write access to the domain SAM database) is DOMPDC; therefore, use the <code class="option">-S</code>
 option. The <em class="replaceable"><code>Administrator%password</code></em> is the login name and
@@ -499,9 +497,9 @@ Where the older NT4-style domain architecture is used:
 <code class="computeroutput">Joined domain DOM.</code>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2571634"></a>
-<a class="indexterm" name="id2571645"></a>
-<a class="indexterm" name="id2571652"></a>
+<a class="indexterm" name="id2571606"></a>
+<a class="indexterm" name="id2571617"></a>
+<a class="indexterm" name="id2571624"></a>
 Where Active Directory is used, the command used to join the ADS domain is:
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads join -U<em class="replaceable"><code>Administrator%password</code></em>
@@ -514,64 +512,64 @@ And the following output is indicative of a successful outcome:
 Refer to the <code class="literal">net</code> man page and to <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">the chapter on remote
 administration</a> for further information.
 </p><p>
-<a class="indexterm" name="id2571709"></a>
-<a class="indexterm" name="id2571716"></a>
-<a class="indexterm" name="id2571723"></a>
+<a class="indexterm" name="id2571681"></a>
+<a class="indexterm" name="id2571688"></a>
+<a class="indexterm" name="id2571695"></a>
 This process joins the server to the domain without separately having to create the machine
 trust account on the PDC beforehand.
 </p><p>
-<a class="indexterm" name="id2571735"></a>
-<a class="indexterm" name="id2571745"></a>
-<a class="indexterm" name="id2571752"></a>
-<a class="indexterm" name="id2571759"></a>
+<a class="indexterm" name="id2571707"></a>
+<a class="indexterm" name="id2571716"></a>
+<a class="indexterm" name="id2571724"></a>
+<a class="indexterm" name="id2571731"></a>
 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 a smbpasswd file would be
 normally stored. The trust account information that is needed by the DMS is written into the file
 <code class="filename">/usr/local/samba/private/secrets.tdb</code> or <code class="filename">/etc/samba/secrets.tdb</code>.
 </p><p>
-<a class="indexterm" name="id2571788"></a>
-<a class="indexterm" name="id2571795"></a>
+<a class="indexterm" name="id2571759"></a>
+<a class="indexterm" name="id2571766"></a>
 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>
-<a class="indexterm" name="id2571808"></a>
-<a class="indexterm" name="id2571815"></a>
-<a class="indexterm" name="id2571822"></a>
+<a class="indexterm" name="id2571780"></a>
+<a class="indexterm" name="id2571787"></a>
+<a class="indexterm" name="id2571794"></a>
 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 the following will suffice:
 </p><pre class="screen">
 <code class="prompt">root# </code>/etc/init.d/samba restart
 </pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571847"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>
-<a class="indexterm" name="id2571861"></a>
-<a class="indexterm" name="id2571868"></a>
-<a class="indexterm" name="id2571875"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571819"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>
+<a class="indexterm" name="id2571832"></a>
+<a class="indexterm" name="id2571839"></a>
+<a class="indexterm" name="id2571846"></a>
 Currently, domain security in Samba does not free you from having to create local UNIX users to represent the
 users attaching to your server. This means that if domain user <code class="constant">DOM\fred</code> attaches to your
 domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX file
 system. This is similar to the older Samba security mode <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, where Samba would pass through the authentication request to a Windows
 NT server in the same way as a Windows 95 or Windows 98 server would.
 </p><p>
-<a class="indexterm" name="id2571909"></a>
-<a class="indexterm" name="id2571915"></a>
-<a class="indexterm" name="id2571922"></a>
+<a class="indexterm" name="id2571881"></a>
+<a class="indexterm" name="id2571887"></a>
+<a class="indexterm" name="id2571894"></a>
 Please refer to <a class="link" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for information on a system
 to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups.
 </p><p>
-<a class="indexterm" name="id2571941"></a>
-<a class="indexterm" name="id2571948"></a>
-<a class="indexterm" name="id2571955"></a>
+<a class="indexterm" name="id2571913"></a>
+<a class="indexterm" name="id2571920"></a>
+<a class="indexterm" name="id2571927"></a>
 The advantage of 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>
-<a class="indexterm" name="id2571973"></a>
-<a class="indexterm" name="id2571979"></a>
-<a class="indexterm" name="id2571986"></a>
+<a class="indexterm" name="id2571944"></a>
+<a class="indexterm" name="id2571951"></a>
+<a class="indexterm" name="id2571957"></a>
 In addition, with <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, 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
@@ -579,10 +577,10 @@ connection resources on a Microsoft NT server and cause it to run out of availab
 only for as long as is necessary to authenticate the user and then drop the connection, thus conserving PDC
 connection resources.
 </p><p>
-<a class="indexterm" name="id2572026"></a>
-<a class="indexterm" name="id2572032"></a>
-<a class="indexterm" name="id2572039"></a>
-<a class="indexterm" name="id2572046"></a>
+<a class="indexterm" name="id2571998"></a>
+<a class="indexterm" name="id2572004"></a>
+<a class="indexterm" name="id2572011"></a>
+<a class="indexterm" name="id2572017"></a>
 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, and so on.
@@ -591,58 +589,58 @@ Much of the text of this document was first published in the Web magazine
 <a class="ulink" href="http://www.linuxworld.com" target="_top"><span class="emphasis"><em>LinuxWorld</em></span></a> as the article <a class="ulink" href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html</a>
 <span class="emphasis"><em>Doing the NIS/NT Samba</em></span>.
 </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><p>
-<a class="indexterm" name="id2572096"></a>
-<a class="indexterm" name="id2572102"></a>
-<a class="indexterm" name="id2572112"></a>
-<a class="indexterm" name="id2572118"></a>
+<a class="indexterm" name="id2572067"></a>
+<a class="indexterm" name="id2572074"></a>
+<a class="indexterm" name="id2572083"></a>
+<a class="indexterm" name="id2572090"></a>
 This is a rough guide to setting up Samba-3 with Kerberos authentication against a
 Windows 200x KDC. A familiarity with Kerberos is assumed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572129"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572100"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p>
 You must use at least the following three options in <code class="filename">smb.conf</code>:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572155"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572166"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td># The following parameter need only be specified if present.</td></tr><tr><td># The default setting if not present is Yes.</td></tr><tr><td><a class="indexterm" name="id2572186"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>
-<a class="indexterm" name="id2572200"></a>
-<a class="indexterm" name="id2572207"></a>
-<a class="indexterm" name="id2572214"></a>
-<a class="indexterm" name="id2572220"></a>
-<a class="indexterm" name="id2572227"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572126"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572138"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td># The following parameter need only be specified if present.</td></tr><tr><td># The default setting if not present is Yes.</td></tr><tr><td><a class="indexterm" name="id2572158"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>
+<a class="indexterm" name="id2572172"></a>
+<a class="indexterm" name="id2572179"></a>
+<a class="indexterm" name="id2572185"></a>
+<a class="indexterm" name="id2572192"></a>
+<a class="indexterm" name="id2572199"></a>
 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 
 <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> option in <code class="filename">smb.conf</code>:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572258"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572230"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
 The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of
 sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS
 infrastructure. There is no harm in specifying a preferred ADS domain controller using the <em class="parameter"><code>password
 server</code></em>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2572285"></a>
-<a class="indexterm" name="id2572292"></a>
+<a class="indexterm" name="id2572257"></a>
+<a class="indexterm" name="id2572264"></a>
 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 
 if <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, although it will not do any harm and 
 allows you to have local users not in the domain.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572320"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>
-<a class="indexterm" name="id2572332"></a>
-<a class="indexterm" name="id2572338"></a>
-<a class="indexterm" name="id2572348"></a>
-<a class="indexterm" name="id2572355"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572291"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>
+<a class="indexterm" name="id2572303"></a>
+<a class="indexterm" name="id2572310"></a>
+<a class="indexterm" name="id2572319"></a>
+<a class="indexterm" name="id2572326"></a>
 With both MIT and Heimdal Kerberos, it is unnecessary to configure the <code class="filename">/etc/krb5.conf</code>,
 and it may be detrimental.
 </p><p>
-<a class="indexterm" name="id2572373"></a>
-<a class="indexterm" name="id2572379"></a>
-<a class="indexterm" name="id2572386"></a>
-<a class="indexterm" name="id2572393"></a>
-<a class="indexterm" name="id2572399"></a>
+<a class="indexterm" name="id2572344"></a>
+<a class="indexterm" name="id2572351"></a>
+<a class="indexterm" name="id2572358"></a>
+<a class="indexterm" name="id2572364"></a>
+<a class="indexterm" name="id2572371"></a>
 Microsoft ADS automatically create SRV records in the DNS zone 
 <em class="parameter"><code>_kerberos._tcp.REALM.NAME</code></em> for each KDC in the realm. This is part
 of the installation and configuration process used to create an Active Directory domain.
 A KDC is a Kerberos Key Distribution Center and forms an integral part of the Microsoft
 active directory infrastructure.
 </p><p>
-<a class="indexterm" name="id2572421"></a>
-<a class="indexterm" name="id2572428"></a>
-<a class="indexterm" name="id2572435"></a>
-<a class="indexterm" name="id2572441"></a>
-<a class="indexterm" name="id2572448"></a>
-<a class="indexterm" name="id2572455"></a>
+<a class="indexterm" name="id2572393"></a>
+<a class="indexterm" name="id2572399"></a>
+<a class="indexterm" name="id2572406"></a>
+<a class="indexterm" name="id2572413"></a>
+<a class="indexterm" name="id2572420"></a>
+<a class="indexterm" name="id2572427"></a>
 UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows
 2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the
 Microsoft Windows 2000 Kerberos <a class="ulink" href="http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp" target="_top">Interoperability</a>
@@ -650,18 +648,18 @@ guide. Another very useful document that may be referred to for general informat
 interoperability is <a class="ulink" href="http://www.ietf.org/rfc/rfc1510.txt?number=1510" target="_top">RFC1510</a>. This RFC
 explains much of the magic behind the operation of Kerberos.
 </p><p>
-<a class="indexterm" name="id2572487"></a>
-<a class="indexterm" name="id2572493"></a>
-<a class="indexterm" name="id2572500"></a>
-<a class="indexterm" name="id2572507"></a>
-<a class="indexterm" name="id2572514"></a>
-<a class="indexterm" name="id2572520"></a>
+<a class="indexterm" name="id2572458"></a>
+<a class="indexterm" name="id2572465"></a>
+<a class="indexterm" name="id2572472"></a>
+<a class="indexterm" name="id2572478"></a>
+<a class="indexterm" name="id2572485"></a>
+<a class="indexterm" name="id2572492"></a>
 MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will 
 automatically find the KDCs. In addition, <code class="filename">krb5.conf</code> only allows specifying 
 a single KDC, even there if there may be more than one. Using the DNS lookup allows the KRB5 
 libraries to use whichever KDCs are available.
 </p><p>
-<a class="indexterm" name="id2572542"></a>
+<a class="indexterm" name="id2572513"></a>
 When manually configuring <code class="filename">krb5.conf</code>, the minimal configuration is:
 </p><pre class="screen">
 [libdefaults]
@@ -676,7 +674,7 @@ When manually configuring <code class="filename">krb5.conf</code>, the minimal c
 	.kerberos.server = YOUR.KERBEROS.REALM
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2572567"></a>
+<a class="indexterm" name="id2572539"></a>
 When using Heimdal versions before 0.6, use the following configuration settings:
 </p><pre class="screen">
 [libdefaults]
@@ -693,16 +691,16 @@ When using Heimdal versions before 0.6, use the following configuration settings
         .kerberos.server = YOUR.KERBEROS.REALM
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2572589"></a>
-<a class="indexterm" name="id2572596"></a>
+<a class="indexterm" name="id2572561"></a>
+<a class="indexterm" name="id2572567"></a>
 Test your config by doing a <strong class="userinput"><code>kinit
 <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong> and
 making sure that your password is accepted by the Win2000 KDC.
 </p><p>
-<a class="indexterm" name="id2572619"></a>
-<a class="indexterm" name="id2572626"></a>
-<a class="indexterm" name="id2572633"></a>
-<a class="indexterm" name="id2572639"></a>
+<a class="indexterm" name="id2572591"></a>
+<a class="indexterm" name="id2572598"></a>
+<a class="indexterm" name="id2572604"></a>
+<a class="indexterm" name="id2572611"></a>
 With Heimdal versions earlier than 0.6.x you can use only newly created accounts
 in ADS or accounts that have had the password changed once after migration, or
 in case of <code class="constant">Administrator</code> after installation. At the
@@ -710,50 +708,50 @@ moment, a Windows 2003 KDC can only be used with Heimdal releases later than 0.6
 (and no default etypes in krb5.conf). Unfortunately, this whole area is still
 in a state of flux.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2572661"></a>
-<a class="indexterm" name="id2572668"></a>
-<a class="indexterm" name="id2572674"></a>
+<a class="indexterm" name="id2572632"></a>
+<a class="indexterm" name="id2572639"></a>
+<a class="indexterm" name="id2572646"></a>
 The realm must be in uppercase or you will get a &#8220;<span class="quote"><span class="errorname">Cannot find KDC for
 requested realm while getting initial credentials</span></span>&#8221; 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>
-<a class="indexterm" name="id2572692"></a>
-<a class="indexterm" name="id2572698"></a>
-<a class="indexterm" name="id2572705"></a>
-<a class="indexterm" name="id2572712"></a>
+<a class="indexterm" name="id2572663"></a>
+<a class="indexterm" name="id2572670"></a>
+<a class="indexterm" name="id2572677"></a>
+<a class="indexterm" name="id2572684"></a>
 Time between the two servers must be synchronized. You will get a &#8220;<span class="quote"><span class="errorname">kinit(v5): Clock skew too
 great while getting initial credentials</span></span>&#8221; if the time difference (clock skew) is more than five minutes.
 </p></div><p>
-<a class="indexterm" name="id2572730"></a>
-<a class="indexterm" name="id2572737"></a>
+<a class="indexterm" name="id2572702"></a>
+<a class="indexterm" name="id2572708"></a>
 Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes.
 </p><p>
-<a class="indexterm" name="id2572749"></a>
-<a class="indexterm" name="id2572755"></a>
-<a class="indexterm" name="id2572762"></a>
-<a class="indexterm" name="id2572769"></a>
+<a class="indexterm" name="id2572720"></a>
+<a class="indexterm" name="id2572727"></a>
+<a class="indexterm" name="id2572733"></a>
+<a class="indexterm" name="id2572740"></a>
 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 (i.e., the hostname with no domain
 attached) or it can be the NetBIOS name followed by the realm.
 </p><p>
-<a class="indexterm" name="id2572783"></a>
-<a class="indexterm" name="id2572790"></a>
-<a class="indexterm" name="id2572797"></a>
+<a class="indexterm" name="id2572755"></a>
+<a class="indexterm" name="id2572762"></a>
+<a class="indexterm" name="id2572768"></a>
 The easiest way to ensure you get this right is to add a <code class="filename">/etc/hosts</code> entry mapping the IP
 address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a <span class="errorname">local
 error</span> when you try to join the realm.
 </p><p>
-<a class="indexterm" name="id2572820"></a>
-<a class="indexterm" name="id2572826"></a>
-<a class="indexterm" name="id2572834"></a>
-<a class="indexterm" name="id2572841"></a>
+<a class="indexterm" name="id2572791"></a>
+<a class="indexterm" name="id2572798"></a>
+<a class="indexterm" name="id2572805"></a>
+<a class="indexterm" name="id2572812"></a>
 If all you want is Kerberos support in <span class="application">smbclient</span>, then you can skip directly to <a class="link" href="domain-member.html#ads-test-smbclient" title="Testing with smbclient">Testing with <span class="application">smbclient</span></a> now.  <a class="link" href="domain-member.html#ads-create-machine-account" title="Create the Computer Account">Create the Computer Account</a> and <a class="link" href="domain-member.html#ads-test-server" title="Testing Server Setup">Testing Server Setup</a> are needed only 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><p>
-<a class="indexterm" name="id2572911"></a>
-<a class="indexterm" name="id2572918"></a>
-<a class="indexterm" name="id2572925"></a>
-<a class="indexterm" name="id2572932"></a>
+<a class="indexterm" name="id2572883"></a>
+<a class="indexterm" name="id2572889"></a>
+<a class="indexterm" name="id2572896"></a>
+<a class="indexterm" name="id2572903"></a>
 As a user who has write permission on the Samba private directory (usually root), run:
 </p><pre class="screen">
 <code class="prompt">root# </code> <strong class="userinput"><code>net ads join -U Administrator%password</code></strong>
@@ -762,12 +760,12 @@ The Administrator account can be any account that has been designated in the ADS
 permission to add machines to the ADS domain. It is, of course, a good idea to use an account other than Administrator.
 On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root).
 </p><p>
-<a class="indexterm" name="id2572966"></a>
-<a class="indexterm" name="id2572973"></a>
-<a class="indexterm" name="id2572980"></a>
-<a class="indexterm" name="id2572987"></a>
-<a class="indexterm" name="id2572994"></a>
-<a class="indexterm" name="id2573001"></a>
+<a class="indexterm" name="id2572938"></a>
+<a class="indexterm" name="id2572944"></a>
+<a class="indexterm" name="id2572952"></a>
+<a class="indexterm" name="id2572958"></a>
+<a class="indexterm" name="id2572965"></a>
+<a class="indexterm" name="id2572972"></a>
 When making a Windows client a member of an ADS domain within a complex organization, you
 may want to create the machine trust account within a particular organizational unit. Samba-3 permits
 this to be done using the following syntax:
@@ -777,10 +775,10 @@ this to be done using the following syntax:
 </pre><p>
 Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter.
 </p><p>
-<a class="indexterm" name="id2573051"></a>
-<a class="indexterm" name="id2573058"></a>
-<a class="indexterm" name="id2573065"></a>
-<a class="indexterm" name="id2573072"></a>
+<a class="indexterm" name="id2573022"></a>
+<a class="indexterm" name="id2573029"></a>
+<a class="indexterm" name="id2573036"></a>
+<a class="indexterm" name="id2573043"></a>
 For example, you may want to create the machine trust account in a container called &#8220;<span class="quote">Servers</span>&#8221;
 under the organizational directory &#8220;<span class="quote">Computers/BusinessUnit/Department,</span>&#8221; like this:
 </p><pre class="screen">
@@ -791,90 +789,90 @@ This command will place the Samba server machine trust account in the container
 before executing this command.  Please note that forward slashes must be used, because backslashes are both
 valid characters in an OU name and used as escapes for other characters.  If you need a backslash in an OU 
 name, it may need to be quadrupled to pass through the shell escape and ldap escape.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2573121"></a>Possible Errors</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2573092"></a>Possible Errors</h4></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>
-	<a class="indexterm" name="id2573140"></a>
-	<a class="indexterm" name="id2573147"></a>
-	<a class="indexterm" name="id2573154"></a>
+	<a class="indexterm" name="id2573111"></a>
+	<a class="indexterm" name="id2573118"></a>
+	<a class="indexterm" name="id2573125"></a>
 	Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the
 	Kerberos libraries and headers files are installed.
 	</p></dd><dt><span class="term"><span class="errorname">net ads join prompts for user name</span></span></dt><dd><p>
-	<a class="indexterm" name="id2573174"></a>
-	<a class="indexterm" name="id2573180"></a>
-	You need to login to the domain using <strong class="userinput"><code>kinit
+	<a class="indexterm" name="id2573145"></a>
+	<a class="indexterm" name="id2573152"></a>
+	You need to log in to the domain using <strong class="userinput"><code>kinit
 	<em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong>.
 	<em class="replaceable"><code>USERNAME</code></em> must be a user who has rights to add a machine to the domain.
 	</p></dd><dt><span class="term">Unsupported encryption/or checksum types</span></dt><dd><p>
-	<a class="indexterm" name="id2573214"></a>
-	<a class="indexterm" name="id2573220"></a>
-	<a class="indexterm" name="id2573228"></a>
+	<a class="indexterm" name="id2573185"></a>
+	<a class="indexterm" name="id2573192"></a>
+	<a class="indexterm" name="id2573199"></a>
 	Make sure that the <code class="filename">/etc/krb5.conf</code> is correctly configured
 	for the type and version of Kerberos installed on the system.
 	</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>Testing Server Setup</h3></div></div></div><p>
-<a class="indexterm" name="id2573259"></a>
-<a class="indexterm" name="id2573266"></a>
-<a class="indexterm" name="id2573273"></a>
+<a class="indexterm" name="id2573231"></a>
+<a class="indexterm" name="id2573237"></a>
+<a class="indexterm" name="id2573244"></a>
 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 &#8220;<span class="quote">Computers</span>&#8221;
 folder under Users and Computers.
 </p><p>
-<a class="indexterm" name="id2573289"></a>
-<a class="indexterm" name="id2573296"></a>
-<a class="indexterm" name="id2573305"></a>
-On a Windows 2000 client, try <strong class="userinput"><code>net use * \\server\share</code></strong>. It should be possible
-to login with Kerberos without needing to know a password. If this fails, then run
+<a class="indexterm" name="id2573261"></a>
+<a class="indexterm" name="id2573268"></a>
+<a class="indexterm" name="id2573277"></a>
+On a Windows 2000 client, try <strong class="userinput"><code>net use * \\server\share</code></strong>. You should
+be logged in with Kerberos without needing to know a password. If this fails, then run
 <strong class="userinput"><code>klist tickets</code></strong>. Did you get a ticket for the server? Does it have
-an encryption type of DES-CBC-MD5?
+an encryption type of DES-CBC-MD5? 
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2573332"></a>
-<a class="indexterm" name="id2573339"></a>
-<a class="indexterm" name="id2573346"></a>
+<a class="indexterm" name="id2573304"></a>
+<a class="indexterm" name="id2573310"></a>
+<a class="indexterm" name="id2573317"></a>
 Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding.
 </p></div></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><p>
-<a class="indexterm" name="id2573373"></a>
-<a class="indexterm" name="id2573380"></a>
-<a class="indexterm" name="id2573386"></a>
-On your Samba server try to login to a Windows 2000 server or your Samba
+<a class="indexterm" name="id2573344"></a>
+<a class="indexterm" name="id2573351"></a>
+<a class="indexterm" name="id2573358"></a>
+On your Samba server try to log in to a Windows 2000 server or your Samba
 server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but
 specify the <code class="option">-k</code> option to choose Kerberos authentication.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573414"></a>Notes</h3></div></div></div><p>
-<a class="indexterm" name="id2573422"></a>
-<a class="indexterm" name="id2573429"></a>
-<a class="indexterm" name="id2573436"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573385"></a>Notes</h3></div></div></div><p>
+<a class="indexterm" name="id2573393"></a>
+<a class="indexterm" name="id2573400"></a>
+<a class="indexterm" name="id2573407"></a>
 You must change the administrator password at least once after installing a domain controller, 
 to create the right encryption types.
 </p><p>
-<a class="indexterm" name="id2573448"></a>
-<a class="indexterm" name="id2573455"></a>
-<a class="indexterm" name="id2573462"></a>
+<a class="indexterm" name="id2573420"></a>
+<a class="indexterm" name="id2573427"></a>
+<a class="indexterm" name="id2573433"></a>
 Windows 200x does not seem to create the <em class="parameter"><code>_kerberos._udp</code></em> and
 <em class="parameter"><code>_ldap._tcp</code></em> in the default DNS setup. Perhaps 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="id2573486"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>
-<a class="indexterm" name="id2573495"></a>
-<a class="indexterm" name="id2573502"></a>
-<a class="indexterm" name="id2573508"></a>
-<a class="indexterm" name="id2573515"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573458"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>
+<a class="indexterm" name="id2573466"></a>
+<a class="indexterm" name="id2573473"></a>
+<a class="indexterm" name="id2573480"></a>
+<a class="indexterm" name="id2573486"></a>
 Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs).
 These mappings are done by the <em class="parameter"><code>idmap</code></em> subsystem of Samba.
 </p><p>
-<a class="indexterm" name="id2573533"></a>
-<a class="indexterm" name="id2573540"></a>
-<a class="indexterm" name="id2573547"></a>
+<a class="indexterm" name="id2573505"></a>
+<a class="indexterm" name="id2573512"></a>
+<a class="indexterm" name="id2573518"></a>
 In some cases it is useful to share these mappings between Samba domain members,
 so <span class="emphasis"><em>name-&gt;id</em></span> mapping is identical on all machines.
 This may be needed in particular when sharing files over both CIFS and NFS.
 </p><p>
-<a class="indexterm" name="id2573564"></a>
-<a class="indexterm" name="id2573571"></a>
+<a class="indexterm" name="id2573536"></a>
+<a class="indexterm" name="id2573543"></a>
 To use the <span class="emphasis"><em>LDAP</em></span> <em class="parameter"><code>ldap idmap suffix</code></em>, set:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2573595"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2573566"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>
 See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX" target="_top">ldap idmap suffix</a>
 parameter for further information.
 </p><p>
-<a class="indexterm" name="id2573631"></a>
-<a class="indexterm" name="id2573637"></a>
-<a class="indexterm" name="id2573644"></a>
+<a class="indexterm" name="id2573602"></a>
+<a class="indexterm" name="id2573609"></a>
+<a class="indexterm" name="id2573616"></a>
 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a>
 and to make certain to set the LDAP administrative password into the <code class="filename">secrets.tdb</code> using:
 </p><pre class="screen">
@@ -882,9 +880,9 @@ and to make certain to set the LDAP administrative password into the <code class
 </pre><p>
 In place of <code class="literal">ldap-admin-password</code>, substitute the LDAP administration password for your
 system.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573692"></a>Common Errors</h2></div></div></div><p>
-<a class="indexterm" name="id2573700"></a>
-<a class="indexterm" name="id2573707"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573664"></a>Common Errors</h2></div></div></div><p>
+<a class="indexterm" name="id2573672"></a>
+<a class="indexterm" name="id2573679"></a>
 In the process of adding/deleting/re-adding domain member machine trust accounts, there are
 many traps for the unwary player and many &#8220;<span class="quote">little</span>&#8221; things that can go wrong.
 It is particularly interesting how often subscribers on the Samba mailing list have concluded
@@ -892,16 +890,16 @@ after repeated failed attempts to add a machine account that it is necessary to
 MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type
 of problem. The real solution is often quite simple, and with an understanding of how MS Windows
 networking functions, it is easy to overcome.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573732"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>
-<a class="indexterm" name="id2573740"></a>
-<a class="indexterm" name="id2573748"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573704"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>
+<a class="indexterm" name="id2573712"></a>
+<a class="indexterm" name="id2573719"></a>
 &#8220;<span class="quote">A Windows workstation was reinstalled. The original domain machine trust
 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 does not. Why is this failing?</span>&#8221;
 </p><p>
-<a class="indexterm" name="id2573769"></a>
-<a class="indexterm" name="id2573775"></a>
+<a class="indexterm" name="id2573740"></a>
+<a class="indexterm" name="id2573747"></a>
 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 add the machine with a new name. Alternately, the name cache can be flushed and
@@ -909,14 +907,14 @@ reloaded with current data using the <code class="literal">nbtstat</code> comman
 </p><pre class="screen">
 <code class="prompt">C:\&gt; </code> nbtstat -R
 </pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573808"></a>Adding Machine to Domain Fails</h3></div></div></div><p>
-<a class="indexterm" name="id2573816"></a>
-<a class="indexterm" name="id2573822"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573779"></a>Adding Machine to Domain Fails</h3></div></div></div><p>
+<a class="indexterm" name="id2573787"></a>
+<a class="indexterm" name="id2573794"></a>
 &#8220;<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
 message that says, <span class="errorname">"The machine could not be added at this time, there is a network problem.
 Please try again later."</span> Why?</span>&#8221;
 </p><p>
-<a class="indexterm" name="id2573843"></a>
+<a class="indexterm" name="id2573814"></a>
 You should check that there is an <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> in your <code class="filename">smb.conf</code>
 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 its operation. Increase the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a>
@@ -925,38 +923,38 @@ operation is failing.
 </p><p>
 Possible causes include:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2573901"></a>
-<a class="indexterm" name="id2573908"></a>
+<a class="indexterm" name="id2573872"></a>
+<a class="indexterm" name="id2573879"></a>
 	The script does not actually exist, or could not be located in the path specified.
 	</p><p>
-<a class="indexterm" name="id2573919"></a>
-<a class="indexterm" name="id2573926"></a>
+<a class="indexterm" name="id2573891"></a>
+<a class="indexterm" name="id2573898"></a>
 	<span class="emphasis"><em>Corrective action:</em></span> Fix it. Make sure when run manually
 	that the script will add both the UNIX system account and the Samba SAM account.
 	</p></li><li><p>
-<a class="indexterm" name="id2573943"></a>
-<a class="indexterm" name="id2573950"></a>
+<a class="indexterm" name="id2573915"></a>
+<a class="indexterm" name="id2573922"></a>
 	The machine could not be added to the UNIX system accounts file <code class="filename">/etc/passwd</code>.
 	</p><p>
-<a class="indexterm" name="id2573967"></a>
-<a class="indexterm" name="id2573974"></a>
+<a class="indexterm" name="id2573938"></a>
+<a class="indexterm" name="id2573946"></a>
 	<span class="emphasis"><em>Corrective action:</em></span> Check that the machine name is a legal UNIX
 	system account name. If the UNIX utility <code class="literal">useradd</code> is called,
 	then make sure that the machine name you are trying to add can be added using this
 	tool. <code class="literal">Useradd</code> on some systems will not allow any uppercase characters
 	nor will it allow spaces in the name.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2574006"></a>
-<a class="indexterm" name="id2574012"></a>
-<a class="indexterm" name="id2574019"></a>
+<a class="indexterm" name="id2573977"></a>
+<a class="indexterm" name="id2573984"></a>
+<a class="indexterm" name="id2573991"></a>
 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> does not create the
 machine account in the Samba backend database; it is there only to create a UNIX system
 account to which the Samba backend database account can be mapped.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574044"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>
-<a class="indexterm" name="id2574052"></a>
-<a class="indexterm" name="id2574058"></a>
-<a class="indexterm" name="id2574065"></a>
-<a class="indexterm" name="id2574072"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574015"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>
+<a class="indexterm" name="id2574023"></a>
+<a class="indexterm" name="id2574030"></a>
+<a class="indexterm" name="id2574036"></a>
+<a class="indexterm" name="id2574043"></a>
 	Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0.
 	Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO" target="_top">client use spnego = yes</a> when communicating 
 	with a Windows 2003 server. This will not interfere with other Windows clients that do not
diff --git a/docs/htmldocs/Samba3-HOWTO/go01.html b/docs/htmldocs/Samba3-HOWTO/go01.html
index 0cfd1a5a3d..a5f58652c4 100644
--- a/docs/htmldocs/Samba3-HOWTO/go01.html
+++ b/docs/htmldocs/Samba3-HOWTO/go01.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="apa.html" title="Appendix�A.� GNU General Public License version 3"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id2694792"></a>Glossary</h2></div></div></div><dl><dt>Access Control List</dt><dd><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="apa.html" title="Appendix�A.� GNU General Public License version 3"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id2694927"></a>Glossary</h2></div></div></div><dl><dt>Access Control List</dt><dd><p>
 		A detailed list of permissions granted to users or groups with respect to file and network resource access.
 		 See <a class="link" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls">&#8220;File, Directory, and Share Access Controls&#8221;</a>, 
 		for details.</p></dd><dt>Active Directory Service</dt><dd><p>
diff --git a/docs/htmldocs/Samba3-HOWTO/groupmapping.html b/docs/htmldocs/Samba3-HOWTO/groupmapping.html
index 53184713e9..6fe7d2914b 100644
--- a/docs/htmldocs/Samba3-HOWTO/groupmapping.html
+++ b/docs/htmldocs/Samba3-HOWTO/groupmapping.html
@@ -1,38 +1,38 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Group Mapping: MS Windows and UNIX</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="passdb.html" title="Chapter�11.�Account Information Databases"><link rel="next" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Group Mapping: MS Windows and UNIX</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="NetCommand.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter�12.�Group Mapping: MS Windows and UNIX</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></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="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="groupmapping.html#id2595892">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596308">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597278">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598144">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598220">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598404">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598531">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598544">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598630">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2595766"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�12.�Group Mapping: MS Windows and UNIX</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="passdb.html" title="Chapter�11.�Account Information Databases"><link rel="next" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�12.�Group Mapping: MS Windows and UNIX</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="NetCommand.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter�12.�Group Mapping: MS Windows and UNIX</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></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="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="groupmapping.html#id2595872">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596288">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597258">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598124">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598201">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598384">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598511">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598524">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598611">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2595746"></a>
+<a class="indexterm" name="id2595755"></a>
+<a class="indexterm" name="id2595762"></a>
+<a class="indexterm" name="id2595768"></a>
 <a class="indexterm" name="id2595775"></a>
-<a class="indexterm" name="id2595781"></a>
-<a class="indexterm" name="id2595788"></a>
-<a class="indexterm" name="id2595795"></a>
-<a class="indexterm" name="id2595802"></a>
+<a class="indexterm" name="id2595782"></a>
 	Starting with Samba-3, new group mapping functionality is available to create associations
 	between Windows group SIDs and UNIX group GIDs. The <code class="literal">groupmap</code> subcommand
 	included with the <span class="application">net</span> tool can be used to manage these associations.
 	</p><p>
-<a class="indexterm" name="id2595827"></a>
-<a class="indexterm" name="id2595834"></a>
+<a class="indexterm" name="id2595807"></a>
+<a class="indexterm" name="id2595814"></a>
 	The new facility for mapping NT groups to UNIX system groups allows the administrator to decide
 	which NT domain groups are to be exposed to MS Windows clients. Only those NT groups that map
 	to a UNIX group that has a value other than the default (<code class="constant">-1</code>) will be exposed
 	in group selection lists in tools that access domain users and groups.
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-	<a class="indexterm" name="id2595856"></a>
-<a class="indexterm" name="id2595862"></a>
+	<a class="indexterm" name="id2595836"></a>
+<a class="indexterm" name="id2595843"></a>
 	The <em class="parameter"><code>domain admin group</code></em> parameter has been removed in Samba-3 and should no longer
 	be specified in <code class="filename">smb.conf</code>. In Samba-2.2.x, this parameter was used to give the listed users membership in the
 	<code class="constant">Domain Admins</code> 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="id2595892"></a>Features and Benefits</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595872"></a>Features and Benefits</h2></div></div></div><p>
 	Samba allows the administrator to create MS Windows NT4/200x group accounts and to
 	arbitrarily associate them with UNIX/Linux group accounts.
 	</p><p>
-	<a class="indexterm" name="id2595906"></a>
-	<a class="indexterm" name="id2595912"></a>
-	<a class="indexterm" name="id2595919"></a>
-<a class="indexterm" name="id2595925"></a>
-<a class="indexterm" name="id2595932"></a>
-<a class="indexterm" name="id2595939"></a>
-<a class="indexterm" name="id2595946"></a>
+	<a class="indexterm" name="id2595886"></a>
+	<a class="indexterm" name="id2595892"></a>
+	<a class="indexterm" name="id2595899"></a>
+<a class="indexterm" name="id2595906"></a>
+<a class="indexterm" name="id2595912"></a>
+<a class="indexterm" name="id2595919"></a>
+<a class="indexterm" name="id2595926"></a>
 	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 <code class="filename">smb.conf</code> 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
@@ -41,19 +41,19 @@
 	<a class="link" href="smb.conf.5.html#IDMAPUID" target="_top">idmap uid</a>/<a class="link" href="smb.conf.5.html#IDMAPGID" target="_top">idmap gid</a>
 	parameters in the <code class="filename">smb.conf</code> file.
 	</p><div class="figure"><a name="idmap-sid2gid"></a><p class="title"><b>Figure�12.1.�IDMAP: Group SID-to-GID Resolution.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2gid.png" width="270" alt="IDMAP: Group SID-to-GID Resolution."></div></div></div><br class="figure-break"><div class="figure"><a name="idmap-gid2sid"></a><p class="title"><b>Figure�12.2.�IDMAP: GID Resolution to Matching SID.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-gid2sid.png" width="270" alt="IDMAP: GID Resolution to Matching SID."></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2596088"></a>
-<a class="indexterm" name="id2596095"></a>
-<a class="indexterm" name="id2596102"></a>
-<a class="indexterm" name="id2596111"></a>
+	<a class="indexterm" name="id2596069"></a>
+<a class="indexterm" name="id2596076"></a>
+<a class="indexterm" name="id2596082"></a>
+<a class="indexterm" name="id2596091"></a>
 	In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to
 	<a class="link" href="groupmapping.html#idmap-sid2gid" title="Figure�12.1.�IDMAP: Group SID-to-GID Resolution.">IDMAP: Group SID-to-GID Resolution</a> and <a class="link" href="groupmapping.html#idmap-gid2sid" title="Figure�12.2.�IDMAP: GID Resolution to Matching SID.">IDMAP: GID Resolution to Matching SID</a>.  The <code class="literal">net groupmap</code> is
 	used to establish UNIX group to NT SID mappings as shown in <a class="link" href="groupmapping.html#idmap-store-gid2sid" title="Figure�12.3.�IDMAP Storing Group Mappings.">IDMAP: storing
 	group mappings</a>.
 	</p><div class="figure"><a name="idmap-store-gid2sid"></a><p class="title"><b>Figure�12.3.�IDMAP Storing Group Mappings.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-store-gid2sid.png" width="270" alt="IDMAP Storing Group Mappings."></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2596197"></a>
-	<a class="indexterm" name="id2596204"></a>
-<a class="indexterm" name="id2596211"></a>
-<a class="indexterm" name="id2596217"></a>
+	<a class="indexterm" name="id2596177"></a>
+	<a class="indexterm" name="id2596184"></a>
+<a class="indexterm" name="id2596191"></a>
+<a class="indexterm" name="id2596198"></a>
 	Administrators should be aware that where <code class="filename">smb.conf</code> group interface scripts make
 	direct calls to the UNIX/Linux system tools (the shadow utilities, <code class="literal">groupadd</code>,
 	<code class="literal">groupdel</code>, and <code class="literal">groupmod</code>), the resulting UNIX/Linux group names will be subject
@@ -62,48 +62,48 @@
 	<code class="literal">Engineering Managers</code> will attempt to create an identically named
 	UNIX/Linux group, an attempt that will of course fail.
 	</p><p>
-	<a class="indexterm" name="id2596265"></a>
-	<a class="indexterm" name="id2596272"></a>
+	<a class="indexterm" name="id2596246"></a>
+	<a class="indexterm" name="id2596252"></a>
 	There are several possible workarounds 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 workaround solution.
 	</p><p>
-<a class="indexterm" name="id2596288"></a>
+<a class="indexterm" name="id2596268"></a>
 	Another workaround 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 <code class="literal">net groupmap</code>
 	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="id2596308"></a>Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2596316"></a>
-<a class="indexterm" name="id2596323"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596288"></a>Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2596296"></a>
+<a class="indexterm" name="id2596303"></a>
 	When you install <span class="application">MS Windows NT4/200x</span> on a computer, the installation
 	program creates default users and groups, notably the <code class="constant">Administrators</code> group,
 	and gives that group privileges necessary to perform essential system tasks,
 	such as the ability to change the date and time or to kill (or close) any process running on the
 	local machine.
 	</p><p>
-	<a class="indexterm" name="id2596348"></a>
+	<a class="indexterm" name="id2596328"></a>
 	The <code class="constant">Administrator</code> user is a member of the <code class="constant">Administrators</code> group, and thus inherits
 	<code class="constant">Administrators</code> group privileges. If a <code class="constant">joe</code> user is created to be a member of the
 	<code class="constant">Administrators</code> group, <code class="constant">joe</code> has exactly the same rights as the user
 	<code class="constant">Administrator</code>.
 	</p><p>
-<a class="indexterm" name="id2596386"></a>
-<a class="indexterm" name="id2596393"></a>
-<a class="indexterm" name="id2596400"></a>
-<a class="indexterm" name="id2596407"></a>
+<a class="indexterm" name="id2596367"></a>
+<a class="indexterm" name="id2596374"></a>
+<a class="indexterm" name="id2596380"></a>
+<a class="indexterm" name="id2596387"></a>
 	When an MS Windows NT4/200x/XP machine is made a domain member, the &#8220;<span class="quote">Domain Admins</span>&#8221; group of the
 	PDC is added to the local <code class="constant">Administrators</code> group of the workstation. Every member of the
 	<code class="constant">Domain Admins</code> group inherits the rights of the local <code class="constant">Administrators</code> group when
 	logging on the workstation.
 	</p><p>
-<a class="indexterm" name="id2596436"></a>
-<a class="indexterm" name="id2596443"></a>
+<a class="indexterm" name="id2596416"></a>
+<a class="indexterm" name="id2596423"></a>
 	The following steps describe how to make Samba PDC users members of the <code class="constant">Domain Admins</code> group.
 	</p><div class="orderedlist"><ol type="1"><li><p>
 		Create a UNIX group (usually in <code class="filename">/etc/group</code>); let's call it <code class="constant">domadm</code>.
 		</p></li><li><p>
-<a class="indexterm" name="id2596480"></a>
+<a class="indexterm" name="id2596461"></a>
 		Add to this group the users that must be &#8220;<span class="quote">Administrators</span>&#8221;. For example,
 		if you want <code class="constant">joe, john</code>, and <code class="constant">mary</code> to be administrators,
 		your entry in <code class="filename">/etc/group</code> will look like this:
@@ -117,13 +117,13 @@
 <code class="prompt">root# </code><strong class="userinput"><code>net groupmap add ntgroup="Domain Admins" unixgroup=domadm rid=512 type=d</code></strong>
 </pre><p>
 		</p><p>
-		<a class="indexterm" name="id2596548"></a>
+		<a class="indexterm" name="id2596528"></a>
 		The quotes around &#8220;<span class="quote">Domain Admins</span>&#8221; are necessary due to the space in the group name.
 		Also make sure to leave no white space surrounding the equal character (=).
 		</p></li></ol></div><p>
 	Now <code class="constant">joe, john</code>, and <code class="constant">mary</code> are domain administrators.
 	</p><p>
-	<a class="indexterm" name="id2596577"></a>
+	<a class="indexterm" name="id2596557"></a>
 	It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as
 	to make any UNIX group a Windows domain group. For example, if you wanted to include a
 	UNIX group (e.g., acct) in an ACL on a local file or printer on a Domain Member machine,
@@ -135,54 +135,54 @@
 	The <code class="literal">ntgroup</code> value must be in quotes if it contains space characters to prevent
 	the space from being interpreted as a command delimiter.
 	</p><p>
-<a class="indexterm" name="id2596624"></a>
-<a class="indexterm" name="id2596630"></a>
+<a class="indexterm" name="id2596604"></a>
+<a class="indexterm" name="id2596610"></a>
 	Be aware that the RID parameter is an unsigned 32-bit integer that should
 	normally start at 1000. However, this RID must not overlap with any RID assigned
 	to a user. Verification for 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="id2596644"></a>Warning: User Private Group Problems</h3></div></div></div><p>
-<a class="indexterm" name="id2596653"></a>
-<a class="indexterm" name="id2596660"></a>
-<a class="indexterm" name="id2596667"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596625"></a>Warning: User Private Group Problems</h3></div></div></div><p>
+<a class="indexterm" name="id2596633"></a>
+<a class="indexterm" name="id2596640"></a>
+<a class="indexterm" name="id2596647"></a>
 	Windows does not permit user and group accounts to have the same name.
 	This has serious implications for all sites that use private group accounts.
 	A private group account is an administrative practice whereby users are each
 	given their own group account. Red Hat Linux, as well as several free distributions
 	of Linux, by default create private groups.
 	</p><p>
-<a class="indexterm" name="id2596683"></a>
-<a class="indexterm" name="id2596690"></a>
+<a class="indexterm" name="id2596663"></a>
+<a class="indexterm" name="id2596670"></a>
 	When mapping a UNIX/Linux group to a Windows group account, all conflict can
 	be avoided by assuring that the Windows domain group name does not overlap
 	with any user account name.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596702"></a>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</h3></div></div></div><a class="indexterm" name="id2596709"></a><p>
-<a class="indexterm" name="id2596720"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596682"></a>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</h3></div></div></div><a class="indexterm" name="id2596689"></a><p>
+<a class="indexterm" name="id2596700"></a>
 	This functionality is known as <code class="constant">nested groups</code> and was first added to
 	Samba-3.0.3.
 	</p><p>
-<a class="indexterm" name="id2596735"></a>
+<a class="indexterm" name="id2596715"></a>
 	All MS Windows products since the release of Windows NT 3.10 support the use of nested groups.
 	Many Windows network administrators depend on this capability because it greatly simplifies security
 	administration.
 	</p><p>
-<a class="indexterm" name="id2596749"></a>
-<a class="indexterm" name="id2596756"></a>
-<a class="indexterm" name="id2596763"></a>
-<a class="indexterm" name="id2596770"></a>
-<a class="indexterm" name="id2596777"></a>
-<a class="indexterm" name="id2596784"></a>
-<a class="indexterm" name="id2596791"></a>
+<a class="indexterm" name="id2596729"></a>
+<a class="indexterm" name="id2596736"></a>
+<a class="indexterm" name="id2596743"></a>
+<a class="indexterm" name="id2596750"></a>
+<a class="indexterm" name="id2596757"></a>
+<a class="indexterm" name="id2596764"></a>
+<a class="indexterm" name="id2596771"></a>
 	The nested group architecture was designed with the premise that day-to-day user and group membership
 	management should be performed on the domain security database. The application of group security
 	should be implemented on domain member servers using only local groups. On the domain member server,
 	all file system security controls are then limited to use of the local groups, which will contain
 	domain global groups and domain global users.
 	</p><p>
-<a class="indexterm" name="id2596809"></a>
-<a class="indexterm" name="id2596816"></a>
-<a class="indexterm" name="id2596823"></a>
+<a class="indexterm" name="id2596789"></a>
+<a class="indexterm" name="id2596796"></a>
+<a class="indexterm" name="id2596803"></a>
 	You may ask, What are the benefits of this arrangement? The answer is obvious to those who have plumbed
 	the dark depths of Windows networking architecture. Consider for a moment a server on which are stored
 	200,000 files, each with individual domain user and domain group settings. The company that owns the
@@ -190,10 +190,10 @@
 	it is made a member of a different domain. Who would you think now owns all the files and directories?
 	Answer: Account Unknown.
 	</p><p>
-<a class="indexterm" name="id2596842"></a>
-<a class="indexterm" name="id2596849"></a>
-<a class="indexterm" name="id2596856"></a>
-<a class="indexterm" name="id2596863"></a>
+<a class="indexterm" name="id2596823"></a>
+<a class="indexterm" name="id2596830"></a>
+<a class="indexterm" name="id2596837"></a>
+<a class="indexterm" name="id2596843"></a>
 	Unraveling the file ownership mess is an unenviable administrative task that can be avoided simply
 	by using local groups to control all file and directory access control. In this case, only the members
 	of the local groups will have been lost. The files and directories in the storage subsystem will still
@@ -201,14 +201,14 @@
 	to delete the <code class="constant">Account Unknown</code> membership entries inside local groups with appropriate
 	entries for domain global groups in the new domain that the server has been made a member of.
 	</p><p>
-<a class="indexterm" name="id2596886"></a>
-<a class="indexterm" name="id2596893"></a>
-<a class="indexterm" name="id2596900"></a>
-<a class="indexterm" name="id2596908"></a>
-<a class="indexterm" name="id2596915"></a>
-<a class="indexterm" name="id2596922"></a>
-<a class="indexterm" name="id2596928"></a>
-<a class="indexterm" name="id2596935"></a>
+<a class="indexterm" name="id2596867"></a>
+<a class="indexterm" name="id2596874"></a>
+<a class="indexterm" name="id2596881"></a>
+<a class="indexterm" name="id2596888"></a>
+<a class="indexterm" name="id2596895"></a>
+<a class="indexterm" name="id2596902"></a>
+<a class="indexterm" name="id2596909"></a>
+<a class="indexterm" name="id2596916"></a>
 	Another prominent example of the use of nested groups involves implementation of administrative privileges
 	on domain member workstations and servers. Administrative privileges are given to all members of the
 	built-in local group <code class="constant">Administrators</code> on each domain member machine. To ensure that all domain
@@ -217,10 +217,10 @@
 	logged into the domain as a member of the Domain Admins group is also granted local administrative
 	privileges on each domain member.
 	</p><p>
-<a class="indexterm" name="id2596963"></a>
-<a class="indexterm" name="id2596970"></a>
-<a class="indexterm" name="id2596977"></a>
-<a class="indexterm" name="id2596984"></a>
+<a class="indexterm" name="id2596944"></a>
+<a class="indexterm" name="id2596950"></a>
+<a class="indexterm" name="id2596957"></a>
+<a class="indexterm" name="id2596964"></a>
 	UNIX/Linux has no concept of support for nested groups, and thus Samba has for a long time not supported
 	them either. The problem is that you would have to enter UNIX groups as auxiliary members of a group in
 	<code class="filename">/etc/group</code>. This does not work because it was not a design requirement at the time
@@ -228,11 +228,11 @@
 	<code class="filename">/etc/group</code> entries on demand by obtaining user and group information from the domain
 	controller that the Samba server is a member of.
 	</p><p>
-<a class="indexterm" name="id2597014"></a>
-<a class="indexterm" name="id2597021"></a>
-<a class="indexterm" name="id2597028"></a>
-<a class="indexterm" name="id2597035"></a>
-<a class="indexterm" name="id2597042"></a>
+<a class="indexterm" name="id2596995"></a>
+<a class="indexterm" name="id2597002"></a>
+<a class="indexterm" name="id2597008"></a>
+<a class="indexterm" name="id2597015"></a>
+<a class="indexterm" name="id2597022"></a>
 	In effect, Samba supplements the <code class="filename">/etc/group</code> data via the dynamic
 	<code class="literal">libnss_winbind</code> mechanism. Beginning with Samba-3.0.3, this facility is used to provide
 	local groups in the same manner as Windows. It works by expanding the local groups on the
@@ -242,13 +242,13 @@
 	group. By definition, it can only contain user objects, which can then be faked to be member of the
 	UNIX/Linux group <code class="constant">demo</code>.
 	</p><p>
-<a class="indexterm" name="id2597088"></a>
-<a class="indexterm" name="id2597095"></a>
-<a class="indexterm" name="id2597102"></a>
-<a class="indexterm" name="id2597109"></a>
-<a class="indexterm" name="id2597115"></a>
-<a class="indexterm" name="id2597122"></a>
-<a class="indexterm" name="id2597129"></a>
+<a class="indexterm" name="id2597069"></a>
+<a class="indexterm" name="id2597076"></a>
+<a class="indexterm" name="id2597082"></a>
+<a class="indexterm" name="id2597089"></a>
+<a class="indexterm" name="id2597096"></a>
+<a class="indexterm" name="id2597103"></a>
+<a class="indexterm" name="id2597110"></a>
 	To enable the use of nested groups, <code class="literal">winbindd</code> must be used with NSS winbind.
 	Creation and administration of the local groups is done best via the Windows Domain User Manager or its
 	Samba equivalent, the utility <code class="literal">net rpc group</code>. Creating the local group
@@ -256,8 +256,8 @@
 	</p><pre class="screen">
 	<code class="prompt">root# </code> net rpc group add demo -L -Uroot%not24get
 	</pre><p>
-<a class="indexterm" name="id2597173"></a>
-<a class="indexterm" name="id2597180"></a>
+<a class="indexterm" name="id2597153"></a>
+<a class="indexterm" name="id2597160"></a>
 	Here the -L switch means that you want to create a local group. It may be necessary to add -S and -U
 	switches for accessing the correct host with appropriate user or root privileges. Adding and removing
 	group members can be done via the <code class="constant">addmem</code> and <code class="constant">delmem</code> subcommands of
@@ -266,10 +266,10 @@
 	</p><pre class="screen">
 	net rpc group addmem demo "DOM\Domain Users"
 	</pre><p>
-<a class="indexterm" name="id2597219"></a>
-<a class="indexterm" name="id2597226"></a>
-<a class="indexterm" name="id2597233"></a>
-<a class="indexterm" name="id2597240"></a>
+<a class="indexterm" name="id2597200"></a>
+<a class="indexterm" name="id2597206"></a>
+<a class="indexterm" name="id2597213"></a>
+<a class="indexterm" name="id2597220"></a>
 	Having completed these two steps, the execution of <code class="literal">getent group demo</code> will show demo
 	members of the global <code class="constant">Domain Users</code> group as members of  the group
 	<code class="constant">demo</code>.  This also works with any local or domain user. In case the domain DOM trusts
@@ -277,46 +277,46 @@
 	<code class="constant">demo</code>. The users from the foreign domain who are members of the group that has been
 	added to the <code class="constant">demo</code> group now have the same local access permissions as local domain
 	users have. 
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597278"></a>Important Administrative Information</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597258"></a>Important Administrative Information</h3></div></div></div><p>
 	Administrative rights are necessary in two specific forms:
 	</p><div class="orderedlist"><ol type="1"><li><p>For Samba-3 domain controllers and domain member servers/clients.</p></li><li><p>To manage domain member Windows workstations.</p></li></ol></div><p>
-<a class="indexterm" name="id2597309"></a>
-<a class="indexterm" name="id2597316"></a>
-<a class="indexterm" name="id2597323"></a>
+<a class="indexterm" name="id2597289"></a>
+<a class="indexterm" name="id2597296"></a>
+<a class="indexterm" name="id2597304"></a>
 	Versions of Samba up to and including 3.0.10 do not provide a means for assigning rights and privileges
 	that are necessary for system administration tasks from a Windows domain member client machine, so
 	domain administration tasks such as adding, deleting, and changing user and group account information, and
 	managing workstation domain membership accounts, can be handled by any account other than root.
 	</p><p>
-<a class="indexterm" name="id2597340"></a>
-<a class="indexterm" name="id2597348"></a>
-<a class="indexterm" name="id2597354"></a>
+<a class="indexterm" name="id2597321"></a>
+<a class="indexterm" name="id2597328"></a>
+<a class="indexterm" name="id2597335"></a>
 	Samba-3.0.11 introduced a new privilege management interface (see <a class="link" href="rights.html" title="Chapter�15.�User Rights and Privileges">User Rights and Privileges</a>)
 	that permits these tasks to be delegated to non-root (i.e., accounts other than the equivalent of the
 	MS Windows Administrator) accounts.
 	</p><p>
-<a class="indexterm" name="id2597376"></a>
-<a class="indexterm" name="id2597382"></a>
+<a class="indexterm" name="id2597356"></a>
+<a class="indexterm" name="id2597362"></a>
 	Administrative tasks on a Windows domain member workstation can be done by anyone who is a member of the
 	<code class="constant">Domain Admins</code> group. This group can be mapped to any convenient UNIX group.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2597397"></a>Applicable Only to Versions Earlier than 3.0.11</h4></div></div></div><p>
-<a class="indexterm" name="id2597405"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2597377"></a>Applicable Only to Versions Earlier than 3.0.11</h4></div></div></div><p>
+<a class="indexterm" name="id2597386"></a>
 	Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires
 	<code class="constant">root</code>-level privilege. The addition of a Windows client to a Samba domain involves the
 	addition of a user account for the Windows client.
 	</p><p>
-<a class="indexterm" name="id2597423"></a>
-<a class="indexterm" name="id2597430"></a>
+<a class="indexterm" name="id2597403"></a>
+<a class="indexterm" name="id2597410"></a>
 	Many UNIX administrators continue to request that the Samba Team make it possible to add Windows workstations, or 
 	the ability to add, delete, or modify user accounts, without requiring <code class="constant">root</code> privileges. 
 	Such a request violates every understanding of basic UNIX system security.
 	</p><p>
-<a class="indexterm" name="id2597448"></a>
-<a class="indexterm" name="id2597455"></a>
-<a class="indexterm" name="id2597462"></a>
-<a class="indexterm" name="id2597469"></a>
-<a class="indexterm" name="id2597476"></a>
-<a class="indexterm" name="id2597483"></a>
+<a class="indexterm" name="id2597428"></a>
+<a class="indexterm" name="id2597435"></a>
+<a class="indexterm" name="id2597442"></a>
+<a class="indexterm" name="id2597449"></a>
+<a class="indexterm" name="id2597456"></a>
+<a class="indexterm" name="id2597463"></a>
 	There is no safe way to provide access on a UNIX/Linux system without providing
 	<code class="constant">root</code>-level privileges. Provision of <code class="constant">root</code> privileges can be done
 	either by logging on to the Domain as the user <code class="constant">root</code> or by permitting particular users to
@@ -324,15 +324,15 @@
 	can use tools like the NT4 Domain User Manager and the NT4 Domain Server Manager to manage user and group
 	accounts as well as domain member server and client accounts. This level of privilege is also needed to manage
 	share-level ACLs.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597519"></a>Default Users, Groups, and Relative Identifiers</h3></div></div></div><p>
-	<a class="indexterm" name="id2597527"></a>
-	<a class="indexterm" name="id2597536"></a>
-<a class="indexterm" name="id2597543"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597499"></a>Default Users, Groups, and Relative Identifiers</h3></div></div></div><p>
+	<a class="indexterm" name="id2597507"></a>
+	<a class="indexterm" name="id2597516"></a>
+<a class="indexterm" name="id2597523"></a>
+<a class="indexterm" name="id2597530"></a>
+<a class="indexterm" name="id2597537"></a>
+<a class="indexterm" name="id2597544"></a>
 <a class="indexterm" name="id2597550"></a>
-<a class="indexterm" name="id2597556"></a>
-<a class="indexterm" name="id2597563"></a>
-<a class="indexterm" name="id2597570"></a>
-<a class="indexterm" name="id2597577"></a>
+<a class="indexterm" name="id2597557"></a>
 	When first installed, Windows NT4/200x/XP are preconfigured with certain user, group, and
 	alias entities. Each has a well-known RID. These must be preserved for continued
 	integrity of operation. Samba must be provisioned with certain essential domain groups that require
@@ -340,23 +340,23 @@
 	domain groups are automatically created. It is the LDAP administrator's responsibility to create
 	(provision) the default NT groups.
 	</p><p>
-<a class="indexterm" name="id2597599"></a>
-<a class="indexterm" name="id2597606"></a>
-<a class="indexterm" name="id2597613"></a>
-<a class="indexterm" name="id2597620"></a>
+<a class="indexterm" name="id2597579"></a>
+<a class="indexterm" name="id2597586"></a>
+<a class="indexterm" name="id2597593"></a>
+<a class="indexterm" name="id2597600"></a>
 	Each essential domain group must be assigned its respective well-known RID. The default users, groups,
 	aliases, and RIDs are shown in <a class="link" href="groupmapping.html#WKURIDS" title="Table�12.1.�Well-Known User Default RIDs">Well-Known User Default RIDs</a>.
 	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2597641"></a>
-<a class="indexterm" name="id2597648"></a>
-<a class="indexterm" name="id2597655"></a>
-<a class="indexterm" name="id2597661"></a>
-<a class="indexterm" name="id2597668"></a>
+<a class="indexterm" name="id2597621"></a>
+<a class="indexterm" name="id2597628"></a>
+<a class="indexterm" name="id2597635"></a>
+<a class="indexterm" name="id2597642"></a>
+<a class="indexterm" name="id2597649"></a>
 	It is the administrator's responsibility to create the essential domain groups and to assign each
 	its default RID.
 	</p></div><p>
-<a class="indexterm" name="id2597680"></a>
-<a class="indexterm" name="id2597687"></a>
+<a class="indexterm" name="id2597660"></a>
+<a class="indexterm" name="id2597667"></a>
 	It is permissible to create any domain group that may be necessary; just make certain that the essential
 	domain groups (well known) have been created and assigned their default RIDs. Other groups you create may
 	be assigned any arbitrary RID you care to use.
@@ -365,12 +365,12 @@
 	will be available for use as an NT domain group.
 	</p><p>
 	</p><div class="table"><a name="WKURIDS"></a><p class="title"><b>Table�12.1.�Well-Known User Default RIDs</b></p><div class="table-contents"><table summary="Well-Known User Default RIDs" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="center"></colgroup><thead><tr><th align="left">Well-Known Entity</th><th align="left">RID</th><th align="left">Type</th><th align="center">Essential</th></tr></thead><tbody><tr><td align="left">Domain Administrator</td><td align="left">500</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain Guest</td><td align="left">501</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain KRBTGT</td><td align="left">502</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain Admins</td><td align="left">512</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Users</td><td align="left">513</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Guests</td><td align="left">514</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Computers</td><td align="left">515</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Controllers</td><td align="left">516</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Certificate Admins</td><td align="left">517</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Schema Admins</td><td align="left">518</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Enterprise Admins</td><td align="left">519</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Policy Admins</td><td align="left">520</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Builtin Admins</td><td align="left">544</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin users</td><td align="left">545</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Guests</td><td align="left">546</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Power Users</td><td align="left">547</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Account Operators</td><td align="left">548</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin System Operators</td><td align="left">549</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Print Operators</td><td align="left">550</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Backup Operators</td><td align="left">551</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Replicator</td><td align="left">552</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin RAS Servers</td><td align="left">553</td><td align="left">Alias</td><td align="center">No</td></tr></tbody></table></div></div><p><br class="table-break">
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598144"></a>Example Configuration</h3></div></div></div><p>
-<a class="indexterm" name="id2598152"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598124"></a>Example Configuration</h3></div></div></div><p>
+<a class="indexterm" name="id2598132"></a>
 		You can list the various groups in the mapping database by executing
 		<code class="literal">net groupmap list</code>. Here is an example:
 		</p><p>
-<a class="indexterm" name="id2598174"></a>
+<a class="indexterm" name="id2598154"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> <strong class="userinput"><code>net groupmap list</code></strong>
 Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -&gt; domadmin
@@ -379,15 +379,15 @@ Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -&gt; domguest
 </pre><p>
 		</p><p>
 		For complete details on <code class="literal">net groupmap</code>, 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="id2598220"></a>Configuration Scripts</h2></div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598201"></a>Configuration Scripts</h2></div></div></div><p>
 	Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
 	(i.e., prepared by someone else for general use). 
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598232"></a>Sample <code class="filename">smb.conf</code> Add Group Script</h3></div></div></div><p>
-		<a class="indexterm" name="id2598246"></a>
-		<a class="indexterm" name="id2598253"></a>
-		<a class="indexterm" name="id2598260"></a>
-<a class="indexterm" name="id2598267"></a>
-<a class="indexterm" name="id2598274"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598212"></a>Sample <code class="filename">smb.conf</code> Add Group Script</h3></div></div></div><p>
+		<a class="indexterm" name="id2598226"></a>
+		<a class="indexterm" name="id2598233"></a>
+		<a class="indexterm" name="id2598240"></a>
+<a class="indexterm" name="id2598247"></a>
+<a class="indexterm" name="id2598254"></a>
 		A script to create complying group names for use by the Samba group interfaces
 		is provided in <a class="link" href="groupmapping.html#smbgrpadd.sh" title="Example�12.1.�smbgrpadd.sh">smbgrpadd.sh</a>. This script
 		adds a temporary entry in the <code class="filename">/etc/group</code> file and then renames
@@ -415,15 +415,15 @@ exit 0
 		The <code class="filename">smb.conf</code> entry for the above script shown in <a class="link" href="groupmapping.html#smbgrpadd" title="Example�12.2.�Configuration of smb.conf for the add group Script">the configuration of
 		<code class="filename">smb.conf</code> for the add group Script</a> demonstrates how it may be used.
 
-</p><div class="example"><a name="smbgrpadd"></a><p class="title"><b>Example�12.2.�Configuration of <code class="filename">smb.conf</code> for the add group Script</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2598388"></a><em class="parameter"><code>add group script = /path_to_tool/smbgrpadd.sh "%g"</code></em></td></tr></table></div></div><p><br class="example-break">
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598404"></a>Script to Configure Group Mapping</h3></div></div></div><p>
-<a class="indexterm" name="id2598412"></a>
+</p><div class="example"><a name="smbgrpadd"></a><p class="title"><b>Example�12.2.�Configuration of <code class="filename">smb.conf</code> for the add group Script</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2598369"></a><em class="parameter"><code>add group script = /path_to_tool/smbgrpadd.sh "%g"</code></em></td></tr></table></div></div><p><br class="example-break">
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598384"></a>Script to Configure Group Mapping</h3></div></div></div><p>
+<a class="indexterm" name="id2598392"></a>
 	In our example we have created a UNIX/Linux group called <code class="literal">ntadmin</code>.
 	Our script will create the additional groups <code class="literal">Orks</code>, <code class="literal">Elves</code>, and <code class="literal">Gnomes</code>.
 	It is a good idea to save this shell script for later use just in case you ever need to rebuild your mapping database.
 	For the sake of convenience we elect to save this script as a file called <code class="filename">initGroups.sh</code>.
 	This script is given in <a class="link" href="groupmapping.html#set-group-map" title="Example�12.3.�Script to Set Group Mapping">intGroups.sh</a>.
-<a class="indexterm" name="id2598462"></a>
+<a class="indexterm" name="id2598442"></a>
 </p><div class="example"><a name="set-group-map"></a><p class="title"><b>Example�12.3.�Script to Set Group Mapping</b></p><div class="example-contents"><pre class="programlisting">
 #!/bin/bash
 
@@ -447,35 +447,35 @@ net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
 	Versions of Samba-3 prior to 3.0.23 automatically create default group mapping for the
 	<code class="literal">Domain Admins, Domain Users</code> and <code class="literal">Domain Guests</code> Windows
 	groups, but do not map them to UNIX GIDs. This was a cause of administrative confusion and 
-	trouble. Commencing with Samba-3.0.23 this anomaly has been fixed - thus all Windows groups
+	trouble. Commencing with Samba-3.0.23 this annomaly has been fixed - thus all Windows groups
 	must now be manually and explicitly created and mapped to a valid UNIX GID by the Samba 
 	administrator.
-	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598531"></a>Common Errors</h2></div></div></div><p>
+	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598511"></a>Common Errors</h2></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 be carefully tested
 manually before putting it into active service.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598544"></a>Adding Groups Fails</h3></div></div></div><p>
-<a class="indexterm" name="id2598552"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598524"></a>Adding Groups Fails</h3></div></div></div><p>
+<a class="indexterm" name="id2598532"></a>
 		This is a common problem when the <code class="literal">groupadd</code> is called directly
 		by the Samba interface script for the <a class="link" href="smb.conf.5.html#ADDGROUPSCRIPT" target="_top">add group script</a> in
 		the <code class="filename">smb.conf</code> file.
 		</p><p>
-<a class="indexterm" name="id2598589"></a>
-<a class="indexterm" name="id2598596"></a>
+<a class="indexterm" name="id2598569"></a>
+<a class="indexterm" name="id2598576"></a>
 		The most common cause of failure is an attempt to add an MS Windows group account
 		that has an uppercase character and/or a space character in it.
 		</p><p>
-<a class="indexterm" name="id2598608"></a>
+<a class="indexterm" name="id2598589"></a>
 		There are three possible workarounds. First, use only group names that comply
 		with the limitations of the UNIX/Linux <code class="literal">groupadd</code> system tool.
 		Second, it involves the use of the script mentioned earlier in this chapter, and
 		third is the 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="id2598630"></a>Adding Domain Users to the Workstation Power Users Group</h3></div></div></div><p>&#8220;<span class="quote">
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598611"></a>Adding Domain Users to the Workstation Power Users Group</h3></div></div></div><p>&#8220;<span class="quote">
 		What must I do to add domain users to the Power Users group?
 		</span>&#8221;</p><p>
-<a class="indexterm" name="id2598644"></a>
+<a class="indexterm" name="id2598625"></a>
 		The Power Users group is a group that is local to each Windows 200x/XP Professional workstation.
 		You cannot add the Domain Users group to the Power Users group automatically, it must be done on
 		each workstation by logging in as the local workstation <span class="emphasis"><em>administrator</em></span> and
diff --git a/docs/htmldocs/Samba3-HOWTO/idmapper.html b/docs/htmldocs/Samba3-HOWTO/idmapper.html
index 95f3599512..6a10d3a389 100644
--- a/docs/htmldocs/Samba3-HOWTO/idmapper.html
+++ b/docs/htmldocs/Samba3-HOWTO/idmapper.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�14.�Identity Mapping (IDMAP)</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command"><link rel="next" href="rights.html" title="Chapter�15.�User Rights and Privileges"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�14.�Identity Mapping (IDMAP)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="rights.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="idmapper"></a>Chapter�14.�Identity Mapping (IDMAP)</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="idmapper.html#id2604465">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604490">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605504">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605739">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605874">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2604190"></a>
-<a class="indexterm" name="id2604196"></a>
-<a class="indexterm" name="id2604203"></a>
-<a class="indexterm" name="id2604210"></a>
-<a class="indexterm" name="id2604220"></a>
-<a class="indexterm" name="id2604226"></a>
-<a class="indexterm" name="id2604233"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�14.�Identity Mapping (IDMAP)</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command"><link rel="next" href="rights.html" title="Chapter�15.�User Rights and Privileges"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�14.�Identity Mapping (IDMAP)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="rights.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="idmapper"></a>Chapter�14.�Identity Mapping (IDMAP)</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="idmapper.html#id2604449">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604474">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605493">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605727">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605862">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2604174"></a>
+<a class="indexterm" name="id2604181"></a>
+<a class="indexterm" name="id2604188"></a>
+<a class="indexterm" name="id2604195"></a>
+<a class="indexterm" name="id2604204"></a>
+<a class="indexterm" name="id2604211"></a>
+<a class="indexterm" name="id2604217"></a>
 The Microsoft Windows operating system has a number of features that impose specific challenges
 to interoperability with the operating systems on which Samba is implemented. This chapter deals
 explicitly with the mechanisms Samba-3 (version 3.0.8 and later) uses to overcome one of the
@@ -16,24 +16,24 @@ to UNIX UIDs and GIDs.
 To ensure sufficient coverage, each possible Samba deployment type is discussed.
 This is followed by an overview of how the IDMAP facility may be implemented.
 </p><p>
-<a class="indexterm" name="id2604257"></a>
-<a class="indexterm" name="id2604264"></a>
-<a class="indexterm" name="id2604270"></a>
-<a class="indexterm" name="id2604278"></a>
+<a class="indexterm" name="id2604241"></a>
+<a class="indexterm" name="id2604248"></a>
+<a class="indexterm" name="id2604255"></a>
+<a class="indexterm" name="id2604262"></a>
 The IDMAP facility is of concern where more than one Samba server (or Samba network client)
 is installed in a domain. Where there is a single Samba server, do not be too concerned regarding
 the IDMAP infrastructure  the default behavior of Samba is nearly always sufficient.
-Where multiple Samba servers are used it is often necessary to move data off one server and onto
+Where mulitple Samba servers are used it is often necessary to move data off one server and onto
 another, and that is where the fun begins!
 </p><p>
-<a class="indexterm" name="id2604298"></a>
-<a class="indexterm" name="id2604304"></a>
-<a class="indexterm" name="id2604310"></a>
-<a class="indexterm" name="id2604317"></a>
-<a class="indexterm" name="id2604324"></a>
-<a class="indexterm" name="id2604331"></a>
-<a class="indexterm" name="id2604338"></a>
-<a class="indexterm" name="id2604344"></a>
+<a class="indexterm" name="id2604283"></a>
+<a class="indexterm" name="id2604289"></a>
+<a class="indexterm" name="id2604295"></a>
+<a class="indexterm" name="id2604302"></a>
+<a class="indexterm" name="id2604308"></a>
+<a class="indexterm" name="id2604315"></a>
+<a class="indexterm" name="id2604322"></a>
+<a class="indexterm" name="id2604329"></a>
 Where user and group account information is stored in an LDAP directory every server can have the same
 consistent UID and GID for users and groups. This is achieved using NSS and the nss_ldap tool. Samba
 can be configured to use only local accounts, in which case the scope of the IDMAP problem is somewhat
@@ -41,75 +41,75 @@ reduced. This works reasonably well if the servers belong to a single domain, an
 are not needed. On the other hand, if the Samba servers are NT4 domain members, or ADS  domain members,
 or if there is a need to keep the security name-space separate (i.e., the user
 <code class="literal">DOMINICUS\FJones</code> must not be given access to the account resources of the user 
-<code class="literal">FRANCISCUS\FJones</code><sup>[<a name="id2604373" href="#ftn.id2604373" class="footnote">4</a>]</sup> free from inadvertent cross-over, close attention should be given
+<code class="literal">FRANCISCUS\FJones</code><sup>[<a name="id2604358" href="#ftn.id2604358" class="footnote">4</a>]</sup> free from inadvertent cross-over, close attention should be given
 to the way that the IDMAP facility is configured.
 </p><p>
-<a class="indexterm" name="id2604402"></a>
-<a class="indexterm" name="id2604409"></a>
-<a class="indexterm" name="id2604416"></a>
-<a class="indexterm" name="id2604422"></a>
-<a class="indexterm" name="id2604429"></a>
-<a class="indexterm" name="id2604435"></a>
+<a class="indexterm" name="id2604386"></a>
+<a class="indexterm" name="id2604392"></a>
+<a class="indexterm" name="id2604399"></a>
+<a class="indexterm" name="id2604406"></a>
+<a class="indexterm" name="id2604412"></a>
+<a class="indexterm" name="id2604419"></a>
 The use of IDMAP is important where the Samba server will be accessed by workstations or servers from
 more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping)
 of foreign SIDs to local UNIX UIDs and GIDs.
 </p><p>
-<a class="indexterm" name="id2604450"></a>
+<a class="indexterm" name="id2604433"></a>
 The use of the IDMAP facility requires the execution of the <code class="literal">winbindd</code> upon Samba startup.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2604465"></a>Samba Server Deployment Types and IDMAP</h2></div></div></div><p>
-<a class="indexterm" name="id2604473"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2604449"></a>Samba Server Deployment Types and IDMAP</h2></div></div></div><p>
+<a class="indexterm" name="id2604457"></a>
 There are four basic server deployment types, as documented in <a class="link" href="ServerType.html" title="Chapter�3.�Server Types and Security Modes">the chapter
 on Server Types and Security Modes</a>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604490"></a>Standalone Samba Server</h3></div></div></div><p>
-	<a class="indexterm" name="id2604498"></a>
-	<a class="indexterm" name="id2604505"></a>
-	<a class="indexterm" name="id2604512"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604474"></a>Standalone Samba Server</h3></div></div></div><p>
+	<a class="indexterm" name="id2604482"></a>
+	<a class="indexterm" name="id2604488"></a>
+	<a class="indexterm" name="id2604495"></a>
 	A standalone Samba server is an implementation that is not a member of a Windows NT4 domain,
 	a Windows 200X Active Directory domain, or a Samba domain.
 	</p><p>
-	<a class="indexterm" name="id2604525"></a>
-	<a class="indexterm" name="id2604531"></a>
-	<a class="indexterm" name="id2604538"></a>
+	<a class="indexterm" name="id2604508"></a>
+	<a class="indexterm" name="id2604515"></a>
+	<a class="indexterm" name="id2604522"></a>
 	By definition, this means that users and groups will be created and controlled locally, and
 	the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility
 	is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility
 	will not be relevant or of interest.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604553"></a>Domain Member Server or Domain Member Client</h3></div></div></div><p>
-	<a class="indexterm" name="id2604561"></a>
-	<a class="indexterm" name="id2604568"></a>
-	<a class="indexterm" name="id2604574"></a>
-	<a class="indexterm" name="id2604581"></a>
-	<a class="indexterm" name="id2604588"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604536"></a>Domain Member Server or Domain Member Client</h3></div></div></div><p>
+	<a class="indexterm" name="id2604545"></a>
+	<a class="indexterm" name="id2604551"></a>
+	<a class="indexterm" name="id2604558"></a>
+	<a class="indexterm" name="id2604565"></a>
+	<a class="indexterm" name="id2604571"></a>
 	Samba-3 can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that
 	are compatible with Windows NT4. Samba-3 file and print sharing protocols are compatible with
 	all versions of MS Windows products. Windows NT4, as with MS Active Directory,
 	extensively makes use of Windows SIDs.
 	</p><p>
-	<a class="indexterm" name="id2604603"></a>
-	<a class="indexterm" name="id2604610"></a>
-	<a class="indexterm" name="id2604616"></a>
+	<a class="indexterm" name="id2604592"></a>
+	<a class="indexterm" name="id2604599"></a>
+	<a class="indexterm" name="id2604605"></a>
 	Samba-3 domain member servers and clients must interact correctly with MS Windows SIDs. Incoming
 	Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba
 	server must provide to MS Windows clients and servers appropriate SIDs.
 	</p><p>
-	<a class="indexterm" name="id2604631"></a>
-	<a class="indexterm" name="id2604637"></a>
+	<a class="indexterm" name="id2604620"></a>
+	<a class="indexterm" name="id2604626"></a>
 	A Samba member of a Windows networking domain (NT4-style or ADS) can be configured to handle 
 	identity mapping in a variety of ways. The mechanism it uses depends on whether or not
 	the <code class="literal">winbindd</code> daemon is used and how the winbind functionality is configured.
 	The configuration options are briefly described here:
 	</p><div class="variablelist"><dl><dt><span class="term">Winbind is not used; users and groups are local: </span></dt><dd><p>
-				<a class="indexterm" name="id2604668"></a>
-				<a class="indexterm" name="id2604675"></a>
-				<a class="indexterm" name="id2604682"></a>
-				<a class="indexterm" name="id2604689"></a>
-				<a class="indexterm" name="id2604695"></a>
-				<a class="indexterm" name="id2604702"></a>
-				<a class="indexterm" name="id2604709"></a>
-				<a class="indexterm" name="id2604716"></a>
-				<a class="indexterm" name="id2604722"></a>
-				<a class="indexterm" name="id2604729"></a>
-				<a class="indexterm" name="id2604736"></a>
+				<a class="indexterm" name="id2604657"></a>
+				<a class="indexterm" name="id2604664"></a>
+				<a class="indexterm" name="id2604670"></a>
+				<a class="indexterm" name="id2604677"></a>
+				<a class="indexterm" name="id2604684"></a>
+				<a class="indexterm" name="id2604691"></a>
+				<a class="indexterm" name="id2604698"></a>
+				<a class="indexterm" name="id2604704"></a>
+				<a class="indexterm" name="id2604711"></a>
+				<a class="indexterm" name="id2604718"></a>
+				<a class="indexterm" name="id2604725"></a>
 				Where <code class="literal">winbindd</code> is not used Samba (<code class="literal">smbd</code>)
 				uses the underlying UNIX/Linux mechanisms to resolve the identity of incoming
 				network traffic. This is done using the LoginID (account name) in the
@@ -119,51 +119,51 @@ on Server Types and Security Modes</a>.
 				we are implying that they are stored only on the local system, in the
 				<code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> respectively.
 				</p><p>
-				<a class="indexterm" name="id2604778"></a>
-				<a class="indexterm" name="id2604785"></a>
+				<a class="indexterm" name="id2604767"></a>
+				<a class="indexterm" name="id2604774"></a>
 				For example, when the user <code class="literal">BERYLIUM\WambatW</code> tries to open a
 				connection to a Samba server the incoming SessionSetupAndX request will make a 
 				system call to look up the user <code class="literal">WambatW</code> in the
 				<code class="filename">/etc/passwd</code> file.
 				</p><p>
-				<a class="indexterm" name="id2604816"></a>
-				<a class="indexterm" name="id2604823"></a>
-				<a class="indexterm" name="id2604830"></a>
-				<a class="indexterm" name="id2604837"></a>
-				<a class="indexterm" name="id2604843"></a>
-				<a class="indexterm" name="id2604850"></a>
-				<a class="indexterm" name="id2604857"></a>
-				<a class="indexterm" name="id2604864"></a>
+				<a class="indexterm" name="id2604805"></a>
+				<a class="indexterm" name="id2604812"></a>
+				<a class="indexterm" name="id2604819"></a>
+				<a class="indexterm" name="id2604826"></a>
+				<a class="indexterm" name="id2604832"></a>
+				<a class="indexterm" name="id2604839"></a>
+				<a class="indexterm" name="id2604846"></a>
+				<a class="indexterm" name="id2604852"></a>
 				This configuration may be used with standalone Samba servers, domain member
 				servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
 				or a tdbsam-based Samba passdb backend.
 				</p></dd><dt><span class="term">Winbind is not used; users and groups resolved via NSS: </span></dt><dd><p>
-				<a class="indexterm" name="id2604887"></a>
-				<a class="indexterm" name="id2604894"></a>
-				<a class="indexterm" name="id2604901"></a>
-				<a class="indexterm" name="id2604908"></a>
-				<a class="indexterm" name="id2604914"></a>
-				<a class="indexterm" name="id2604921"></a>
+				<a class="indexterm" name="id2604876"></a>
+				<a class="indexterm" name="id2604882"></a>
+				<a class="indexterm" name="id2604889"></a>
+				<a class="indexterm" name="id2604896"></a>
+				<a class="indexterm" name="id2604903"></a>
+				<a class="indexterm" name="id2604910"></a>
 				In this situation user and group accounts are treated as if they are local
 				accounts. The only way in which this differs from having local accounts is
 				that the accounts are stored in a repository that can be shared. In practice
 				this means that they will reside in either an NIS-type database or else in LDAP.
 				</p><p>
-				<a class="indexterm" name="id2604936"></a>
-				<a class="indexterm" name="id2604943"></a>
-				<a class="indexterm" name="id2604950"></a>
-				<a class="indexterm" name="id2604957"></a>
-				<a class="indexterm" name="id2604963"></a>
-				<a class="indexterm" name="id2604970"></a>
-				<a class="indexterm" name="id2604977"></a>
+				<a class="indexterm" name="id2604925"></a>
+				<a class="indexterm" name="id2604932"></a>
+				<a class="indexterm" name="id2604939"></a>
+				<a class="indexterm" name="id2604946"></a>
+				<a class="indexterm" name="id2604952"></a>
+				<a class="indexterm" name="id2604959"></a>
+				<a class="indexterm" name="id2604966"></a>
 				This configuration may be used with standalone Samba servers, domain member
 				servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
 				or a tdbsam-based Samba passdb backend.
 				</p></dd><dt><span class="term">Winbind/NSS with the default local IDMAP table: </span></dt><dd><p>
-				<a class="indexterm" name="id2605000"></a>
-				<a class="indexterm" name="id2605006"></a>
-				<a class="indexterm" name="id2605013"></a>
-				<a class="indexterm" name="id2605020"></a>
+				<a class="indexterm" name="id2604988"></a>
+				<a class="indexterm" name="id2604995"></a>
+				<a class="indexterm" name="id2605002"></a>
+				<a class="indexterm" name="id2605009"></a>
 				There are many sites that require only a simple Samba server or a single Samba
 				server that is a member of a Windows NT4 domain or an ADS domain. A typical example
 				is an appliance like file server on which no local accounts are configured and
@@ -171,21 +171,21 @@ on Server Types and Security Modes</a>.
 				domain. The domain control can be provided by Samba-3, MS Windows NT4, or MS Windows
 				Active Directory.
 				</p><p>
-				<a class="indexterm" name="id2605038"></a>
-				<a class="indexterm" name="id2605045"></a>
-				<a class="indexterm" name="id2605052"></a>
-				<a class="indexterm" name="id2605058"></a>
-				<a class="indexterm" name="id2605065"></a>
+				<a class="indexterm" name="id2605027"></a>
+				<a class="indexterm" name="id2605034"></a>
+				<a class="indexterm" name="id2605040"></a>
+				<a class="indexterm" name="id2605047"></a>
+				<a class="indexterm" name="id2605054"></a>
 				Winbind is a great convenience in this situation. All that is needed is a range of
 				UID numbers and GID numbers that can be defined in the <code class="filename">smb.conf</code> file. The
 				<code class="filename">/etc/nsswitch.conf</code> file is configured to use <code class="literal">winbind</code>,
 				which does all the difficult work of mapping incoming SIDs to appropriate UIDs and GIDs.
 				The SIDs are allocated a UID/GID in the order in which winbind receives them.
 				</p><p>
-				<a class="indexterm" name="id2605099"></a>
-				<a class="indexterm" name="id2605106"></a>
-				<a class="indexterm" name="id2605112"></a>
-				<a class="indexterm" name="id2605119"></a>
+				<a class="indexterm" name="id2605088"></a>
+				<a class="indexterm" name="id2605094"></a>
+				<a class="indexterm" name="id2605101"></a>
+				<a class="indexterm" name="id2605108"></a>
 				This configuration is not convenient or practical in sites that have more than one
 				Samba server and that require the same UID or GID for the same user or group across
 				all servers. One of the hazards of this method is that in the event that the winbind
@@ -194,10 +194,10 @@ on Server Types and Security Modes</a>.
 				result that MS Windows files that are stored on the Samba server may now not belong to
 				the rightful owners.
 				</p></dd><dt><span class="term">Winbind/NSS uses RID based IDMAP: </span></dt><dd><p>
-				<a class="indexterm" name="id2605148"></a>
-				<a class="indexterm" name="id2605154"></a>
-				<a class="indexterm" name="id2605161"></a>
-				<a class="indexterm" name="id2605168"></a>
+				<a class="indexterm" name="id2605136"></a>
+				<a class="indexterm" name="id2605143"></a>
+				<a class="indexterm" name="id2605150"></a>
+				<a class="indexterm" name="id2605156"></a>
 				The IDMAP_RID facility is new to Samba version 3.0.8. It was added to make life easier
 				for a number of sites that are committed to use of MS ADS, that do not apply
 				an ADS schema extension, and that do not have an installed an LDAP directory server just for
@@ -205,14 +205,14 @@ on Server Types and Security Modes</a>.
 				domains, and not multiple domain trees) and you want a simple cookie-cutter solution to the
 				IDMAP table problem, then IDMAP_RID is an obvious choice.
 				</p><p>
-				<a class="indexterm" name="id2605186"></a>
-				<a class="indexterm" name="id2605193"></a>
-				<a class="indexterm" name="id2605200"></a>
-				<a class="indexterm" name="id2605207"></a>
-				<a class="indexterm" name="id2605213"></a>
-				<a class="indexterm" name="id2605220"></a>
-				<a class="indexterm" name="id2605226"></a>
-				<a class="indexterm" name="id2605233"></a>
+				<a class="indexterm" name="id2605175"></a>
+				<a class="indexterm" name="id2605182"></a>
+				<a class="indexterm" name="id2605189"></a>
+				<a class="indexterm" name="id2605196"></a>
+				<a class="indexterm" name="id2605202"></a>
+				<a class="indexterm" name="id2605209"></a>
+				<a class="indexterm" name="id2605215"></a>
+				<a class="indexterm" name="id2605222"></a>
 				This facility requires the allocation of the <em class="parameter"><code>idmap uid</code></em> and the
 				<em class="parameter"><code>idmap gid</code></em> ranges, and within the <em class="parameter"><code>idmap uid</code></em>
 				it is possible to allocate a subset of this range for automatic mapping of the relative
@@ -222,23 +222,23 @@ on Server Types and Security Modes</a>.
 				a SID is encountered that has the value <code class="constant">S-1-5-21-34567898-12529001-32973135-1234</code>,
 				the resulting UID will be <code class="constant">1000 + 1234 = 2234</code>.
 				</p></dd><dt><span class="term">Winbind with an NSS/LDAP backend-based IDMAP facility: </span></dt><dd><p>
-				<a class="indexterm" name="id2605302"></a>
-				<a class="indexterm" name="id2605309"></a>
-				<a class="indexterm" name="id2605315"></a>
-				<a class="indexterm" name="id2605322"></a>
-				<a class="indexterm" name="id2605328"></a>
-				<a class="indexterm" name="id2605335"></a>
-				<a class="indexterm" name="id2605342"></a>
-				<a class="indexterm" name="id2605349"></a>
+				<a class="indexterm" name="id2605290"></a>
+				<a class="indexterm" name="id2605297"></a>
+				<a class="indexterm" name="id2605304"></a>
+				<a class="indexterm" name="id2605311"></a>
+				<a class="indexterm" name="id2605317"></a>
+				<a class="indexterm" name="id2605324"></a>
+				<a class="indexterm" name="id2605331"></a>
+				<a class="indexterm" name="id2605337"></a>
 				In this configuration <code class="literal">winbind</code> resolved SIDs to UIDs and GIDs from
 				the <em class="parameter"><code>idmap uid</code></em> and <em class="parameter"><code>idmap gid</code></em> ranges specified
 				in the <code class="filename">smb.conf</code> file, but instead of using a local winbind IDMAP table, it is stored
 				in an LDAP directory so that all domain member machines (clients and servers) can share
 				a common IDMAP table.
 				</p><p>
-				<a class="indexterm" name="id2605387"></a>
-				<a class="indexterm" name="id2605394"></a>
-				<a class="indexterm" name="id2605401"></a>
+				<a class="indexterm" name="id2605376"></a>
+				<a class="indexterm" name="id2605383"></a>
+				<a class="indexterm" name="id2605390"></a>
 				It is important that all LDAP IDMAP clients use only the master LDAP server because the
 				<em class="parameter"><code>idmap backend</code></em> facility in the <code class="filename">smb.conf</code> file does not correctly
 				handle LDAP redirects.
@@ -247,17 +247,17 @@ on Server Types and Security Modes</a>.
 				domain member servers. It is a neat method for assuring that UIDs, GIDs, and the matching
 				SIDs are consistent across all servers.
 				</p><p>
-				<a class="indexterm" name="id2605443"></a>
-				<a class="indexterm" name="id2605449"></a>
+				<a class="indexterm" name="id2605431"></a>
+				<a class="indexterm" name="id2605438"></a>
 				The use of the LDAP-based passdb backend requires use of the PADL nss_ldap utility or
 				an equivalent. In this situation winbind is used to handle foreign SIDs, that is, SIDs from
 				standalone Windows clients (i.e., not a member of our domain) as well as SIDs from 
 				another domain. The foreign UID/GID is mapped from allocated ranges (idmap uid and idmap gid)
 				in precisely the same manner as when using winbind with a local IDMAP table.
 				</p><p>
-				<a class="indexterm" name="id2605467"></a>
-				<a class="indexterm" name="id2605474"></a>
-				<a class="indexterm" name="id2605481"></a>
+				<a class="indexterm" name="id2605456"></a>
+				<a class="indexterm" name="id2605463"></a>
+				<a class="indexterm" name="id2605470"></a>
 				The nss_ldap tool set can be used to access UIDs and GIDs via LDAP as well as via Active
 				Directory. In order to use Active Directory, it is necessary to modify the ADS schema by
 				installing either the AD4UNIX schema extension or using the Microsoft Services for UNIX
@@ -266,11 +266,11 @@ on Server Types and Security Modes</a>.
 				installed to permit the UNIX credentials to be set and managed from the ADS User and Computer
 				Management tool. Each account must be separately UNIX-enabled before the UID and GID data can
 				be used by Samba.
-				</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605504"></a>Primary Domain Controller</h3></div></div></div><p>
-	<a class="indexterm" name="id2605512"></a>
-	<a class="indexterm" name="id2605519"></a>
-	<a class="indexterm" name="id2605526"></a>
-	<a class="indexterm" name="id2605532"></a>
+				</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605493"></a>Primary Domain Controller</h3></div></div></div><p>
+	<a class="indexterm" name="id2605501"></a>
+	<a class="indexterm" name="id2605508"></a>
+	<a class="indexterm" name="id2605514"></a>
+	<a class="indexterm" name="id2605521"></a>
 	Microsoft Windows domain security systems generate the user and group SID as part
 	of the process of creation of an account. Windows does not have a concept of the UNIX UID or a GID; rather,
 	it has its own type of security descriptor. When Samba is used as a domain controller, it provides a method
@@ -278,50 +278,50 @@ on Server Types and Security Modes</a>.
 	adds an RID that is calculated algorithmically from a base value that can be specified
 	in the <code class="filename">smb.conf</code> file, plus twice (2x) the UID or GID. This method is called &#8220;<span class="quote">algorithmic mapping</span>&#8221;.
 	</p><p>
-	<a class="indexterm" name="id2605561"></a>
+	<a class="indexterm" name="id2605550"></a>
 	For example, if a user has a UID of 4321, and the algorithmic RID base has a value of 1000, the RID will
 	be <code class="literal">1000 + (2 x 4321) = 9642</code>. Thus, if the domain SID is
 	<code class="literal">S-1-5-21-89238497-92787123-12341112</code>, the resulting SID is
 	<code class="literal">S-1-5-21-89238497-92787123-12341112-9642</code>.
 	</p><p>
-	<a class="indexterm" name="id2605593"></a>
-	<a class="indexterm" name="id2605600"></a>
-	<a class="indexterm" name="id2605606"></a>
-	<a class="indexterm" name="id2605613"></a>
+	<a class="indexterm" name="id2605582"></a>
+	<a class="indexterm" name="id2605589"></a>
+	<a class="indexterm" name="id2605595"></a>
+	<a class="indexterm" name="id2605602"></a>
 	The foregoing type of SID is produced by Samba as an automatic function and is either produced on the fly
 	(as is the case when using a <em class="parameter"><code>passdb backend = [tdbsam | smbpasswd]</code></em>), or may be stored
 	as a permanent part of an account in an LDAP-based ldapsam.
 	</p><p>
-	<a class="indexterm" name="id2605633"></a>
-	<a class="indexterm" name="id2605640"></a>
-	<a class="indexterm" name="id2605647"></a>
-	<a class="indexterm" name="id2605654"></a>
-	<a class="indexterm" name="id2605661"></a>
-	<a class="indexterm" name="id2605667"></a>
-	<a class="indexterm" name="id2605674"></a>
-	<a class="indexterm" name="id2605680"></a>
-	<a class="indexterm" name="id2605687"></a>
+	<a class="indexterm" name="id2605622"></a>
+	<a class="indexterm" name="id2605629"></a>
+	<a class="indexterm" name="id2605636"></a>
+	<a class="indexterm" name="id2605642"></a>
+	<a class="indexterm" name="id2605649"></a>
+	<a class="indexterm" name="id2605656"></a>
+	<a class="indexterm" name="id2605662"></a>
+	<a class="indexterm" name="id2605669"></a>
+	<a class="indexterm" name="id2605676"></a>
 	ADS uses a directory schema that can be extended to accommodate additional
 	account attributes such as UIDs and GIDs. The installation of Microsoft Service for UNIX 3.5 will expand
 	the normal ADS schema to include UNIX account attributes. These must of course be managed separately
 	through a snap-in module to the normal ADS account management MMC interface.
 	</p><p>
-	<a class="indexterm" name="id2605703"></a>
-	<a class="indexterm" name="id2605710"></a>
-	<a class="indexterm" name="id2605717"></a>
-	<a class="indexterm" name="id2605723"></a>
-	Security identifiers used within a domain must be managed to avoid conflict and to preserve integrity.
+	<a class="indexterm" name="id2605692"></a>
+	<a class="indexterm" name="id2605699"></a>
+	<a class="indexterm" name="id2605706"></a>
+	<a class="indexterm" name="id2605712"></a>
+	Security identifiers used within a domain must be managed to avoid conflict and to preserve itegrity.
 	In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup
 	domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable
 	for such information is an LDAP backend.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605739"></a>Backup Domain Controller</h3></div></div></div><p>
-	<a class="indexterm" name="id2605747"></a>
-	<a class="indexterm" name="id2605753"></a>
-	<a class="indexterm" name="id2605760"></a>
-	<a class="indexterm" name="id2605767"></a>
-	<a class="indexterm" name="id2605774"></a>
-	<a class="indexterm" name="id2605781"></a>
-	<a class="indexterm" name="id2605788"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605727"></a>Backup Domain Controller</h3></div></div></div><p>
+	<a class="indexterm" name="id2605735"></a>
+	<a class="indexterm" name="id2605742"></a>
+	<a class="indexterm" name="id2605749"></a>
+	<a class="indexterm" name="id2605756"></a>
+	<a class="indexterm" name="id2605763"></a>
+	<a class="indexterm" name="id2605770"></a>
+	<a class="indexterm" name="id2605777"></a>
 	BDCs have read-only access to security credentials that are stored in LDAP.
 	Changes in user or group account information are passed by the BDC to the PDC. Only the PDC can write
 	changes to the directory.
@@ -330,27 +330,27 @@ on Server Types and Security Modes</a>.
 	have access to the master (writable) LDAP server. Samba-3 at this time does not handle LDAP redirects
 	in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with
 	the IDMAP facility.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605810"></a>Examples of IDMAP Backend Usage</h2></div></div></div><p>
-<a class="indexterm" name="id2605818"></a>
-<a class="indexterm" name="id2605827"></a>
-<a class="indexterm" name="id2605837"></a>
-<a class="indexterm" name="id2605844"></a>
-<a class="indexterm" name="id2605850"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605799"></a>Examples of IDMAP Backend Usage</h2></div></div></div><p>
+<a class="indexterm" name="id2605807"></a>
+<a class="indexterm" name="id2605816"></a>
+<a class="indexterm" name="id2605826"></a>
+<a class="indexterm" name="id2605832"></a>
+<a class="indexterm" name="id2605839"></a>
 Anyone who wishes to use <code class="literal">winbind</code> will find the following example configurations helpful.
 Remember that in the majority of cases <code class="literal">winbind</code> is of primary interest for use with
 domain member servers (DMSs) and domain member clients (DMCs).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605874"></a>Default Winbind TDB</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605862"></a>Default Winbind TDB</h3></div></div></div><p>
 	Two common configurations are used:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 		Networks that have an NT4 PDC (with or without BDCs) or a Samba PDC (with or without BDCs).
 		</p></li><li><p>
 		Networks that use MS Windows 200x ADS.
-		</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2605898"></a>NT4-Style Domains (Includes Samba Domains)</h4></div></div></div><p>
+		</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2605886"></a>NT4-Style Domains (Includes Samba Domains)</h4></div></div></div><p>
 	<a class="link" href="idmapper.html#idmapnt4dms" title="Example�14.1.�NT4 Domain Member Server smb.conf">NT4 Domain Member Server smb.con</a> is a simple example of an NT4 DMS
 	<code class="filename">smb.conf</code> file that shows only the global section.
-	</p><div class="example"><a name="idmapnt4dms"></a><p class="title"><b>Example�14.1.�NT4 Domain Member Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2605950"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2605962"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2605974"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2605986"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2605997"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2606010"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2606025"></a>
-	<a class="indexterm" name="id2606031"></a>
+	</p><div class="example"><a name="idmapnt4dms"></a><p class="title"><b>Example�14.1.�NT4 Domain Member Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2605939"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id2605951"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id2605963"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2605974"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2605986"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id2605998"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2606013"></a>
+	<a class="indexterm" name="id2606020"></a>
 	The use of <code class="literal">winbind</code> requires configuration of NSS. Edit the <code class="filename">/etc/nsswitch.conf</code>
 	so it includes the following entries:
 </p><pre class="screen">
@@ -373,37 +373,37 @@ hosts:  files [dns] wins
 <code class="prompt">root# </code> net rpc join -UAdministrator%password
 Joined domain MEGANET2.
 </pre><p>
-	<a class="indexterm" name="id2606100"></a>
+	<a class="indexterm" name="id2606089"></a>
 	The success of the join can be confirmed with the following command:
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc testjoin
 Join to 'MIDEARTH' is OK
 </pre><p>
 		A failed join would report an error message like the following:
-		<a class="indexterm" name="id2606122"></a>
+		<a class="indexterm" name="id2606111"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc testjoin
 [2004/11/05 16:34:12, 0] utils/net_rpc_join.c:net_rpc_join_ok(66)
 Join to domain 'MEGANET2' is not valid
 </pre><p>
 		</p></li><li><p>
-		<a class="indexterm" name="id2606149"></a>
-		<a class="indexterm" name="id2606156"></a>
-		<a class="indexterm" name="id2606162"></a>
+		<a class="indexterm" name="id2606138"></a>
+		<a class="indexterm" name="id2606144"></a>
+		<a class="indexterm" name="id2606151"></a>
 		Start the <code class="literal">nmbd, winbind,</code> and <code class="literal">smbd</code> daemons in the order shown.
-		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606185"></a>ADS Domains</h4></div></div></div><p>
-	<a class="indexterm" name="id2606193"></a>
-	<a class="indexterm" name="id2606200"></a>
+		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606174"></a>ADS Domains</h4></div></div></div><p>
+	<a class="indexterm" name="id2606182"></a>
+	<a class="indexterm" name="id2606189"></a>
 	The procedure for joining an ADS domain is similar to the NT4 domain join, except the <code class="filename">smb.conf</code> file
 	will have the contents shown in <a class="link" href="idmapper.html#idmapadsdms" title="Example�14.2.�ADS Domain Member Server smb.conf">ADS Domain Member Server smb.conf</a>
-	</p><div class="example"><a name="idmapadsdms"></a><p class="title"><b>Example�14.2.�ADS Domain Member Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2606251"></a><em class="parameter"><code>workgroup = BUTTERNET</code></em></td></tr><tr><td><a class="indexterm" name="id2606263"></a><em class="parameter"><code>netbios name = GARGOYLE</code></em></td></tr><tr><td><a class="indexterm" name="id2606275"></a><em class="parameter"><code>realm = BUTTERNET.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2606287"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2606298"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2606310"></a><em class="parameter"><code>idmap uid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606322"></a><em class="parameter"><code>idmap gid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606334"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606346"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606358"></a><em class="parameter"><code>printer admin = "BUTTERNET\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2606373"></a>
-	<a class="indexterm" name="id2606380"></a>
-	<a class="indexterm" name="id2606387"></a>
-	<a class="indexterm" name="id2606394"></a>
-	<a class="indexterm" name="id2606400"></a>
-	<a class="indexterm" name="id2606407"></a>
-	<a class="indexterm" name="id2606414"></a>
+	</p><div class="example"><a name="idmapadsdms"></a><p class="title"><b>Example�14.2.�ADS Domain Member Server smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2606240"></a><em class="parameter"><code>workgroup = BUTTERNET</code></em></td></tr><tr><td><a class="indexterm" name="id2606252"></a><em class="parameter"><code>netbios name = GARGOYLE</code></em></td></tr><tr><td><a class="indexterm" name="id2606264"></a><em class="parameter"><code>realm = BUTTERNET.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id2606276"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2606287"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2606299"></a><em class="parameter"><code>idmap uid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606311"></a><em class="parameter"><code>idmap gid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606322"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606335"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606347"></a><em class="parameter"><code>printer admin = "BUTTERNET\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2606362"></a>
+	<a class="indexterm" name="id2606369"></a>
+	<a class="indexterm" name="id2606376"></a>
+	<a class="indexterm" name="id2606383"></a>
+	<a class="indexterm" name="id2606389"></a>
+	<a class="indexterm" name="id2606396"></a>
+	<a class="indexterm" name="id2606403"></a>
 	ADS DMS operation requires use of kerberos (KRB). For this to work, the <code class="filename">krb5.conf</code>
 	must be configured. The exact requirements depends on which version of MIT or Heimdal Kerberos is being
 	used. It is sound advice to use only the latest version, which at this time are MIT Kerberos version
@@ -416,7 +416,7 @@ Join to domain 'MEGANET2' is not valid
 		Edit the <code class="filename">/etc/nsswitch.conf</code> file as shown above.
 		</p></li><li><p>
 		Execute:
-		<a class="indexterm" name="id2606472"></a>
+		<a class="indexterm" name="id2606461"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads join -UAdministrator%password
 Joined domain BUTTERNET.
@@ -436,30 +436,30 @@ GARGOYLE$@'s password:
   ads_connect: No results returned
 Join to domain is not valid
 </pre><p>
-		<a class="indexterm" name="id2606529"></a>
-		<a class="indexterm" name="id2606536"></a>
-		<a class="indexterm" name="id2606543"></a>
-		<a class="indexterm" name="id2606549"></a>
+		<a class="indexterm" name="id2606518"></a>
+		<a class="indexterm" name="id2606525"></a>
+		<a class="indexterm" name="id2606531"></a>
+		<a class="indexterm" name="id2606538"></a>
 		The specific error message may differ from the above because it depends on the type of failure that
 		may have occurred. Increase the <em class="parameter"><code>log level</code></em> to 10, repeat the test,
 		and then examine the log files produced to identify the nature of the failure.
 		</p></li><li><p>
 		Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown.
-		</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606596"></a>IDMAP_RID with Winbind</h3></div></div></div><p>
-	<a class="indexterm" name="id2606604"></a>
-	<a class="indexterm" name="id2606610"></a>
-	<a class="indexterm" name="id2606617"></a>
-	<a class="indexterm" name="id2606624"></a>
+		</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606584"></a>IDMAP_RID with Winbind</h3></div></div></div><p>
+	<a class="indexterm" name="id2606592"></a>
+	<a class="indexterm" name="id2606599"></a>
+	<a class="indexterm" name="id2606606"></a>
+	<a class="indexterm" name="id2606612"></a>
 	The <code class="literal">idmap_rid</code> facility is a new tool that, unlike native winbind, creates a
 	predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
 	of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
 	in a central place. The downside is that it can be used only within a single ADS domain and
 	is not compatible with trusted domain implementations.
 	</p><p>
-	<a class="indexterm" name="id2606646"></a>
-	<a class="indexterm" name="id2606653"></a>
-	<a class="indexterm" name="id2606660"></a>
-	<a class="indexterm" name="id2606667"></a>
+	<a class="indexterm" name="id2606635"></a>
+	<a class="indexterm" name="id2606642"></a>
+	<a class="indexterm" name="id2606649"></a>
+	<a class="indexterm" name="id2606656"></a>
 	This alternate method of SID to UID/GID  mapping can be achieved using the idmap_rid
         plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
         RID to a base value specified. This utility requires that the parameter
@@ -467,19 +467,19 @@ Join to domain is not valid
         with multiple domain environments. The <em class="parameter"><code>idmap uid</code></em> and 
 	<em class="parameter"><code>idmap gid</code></em> ranges must be specified.
 	</p><p>
-	<a class="indexterm" name="id2606699"></a>
-	<a class="indexterm" name="id2606706"></a>
+	<a class="indexterm" name="id2606688"></a>
+	<a class="indexterm" name="id2606695"></a>
 	The idmap_rid facility can be used both for NT4/Samba-style domains and Active Directory.
 	To use this with an NT4 domain, do not include the <em class="parameter"><code>realm</code></em> parameter; additionally, the
 	method used to join the domain uses the <code class="constant">net rpc join</code> process.
 	</p><p>
 	An example <code class="filename">smb.conf</code> file for and ADS domain environment is shown in <a class="link" href="idmapper.html#idmapadsridDMS" title="Example�14.3.�ADS Domain Member smb.conf using idmap_rid">ADS
 	Domain Member smb.conf using idmap_rid</a>.
-	</p><div class="example"><a name="idmapadsridDMS"></a><p class="title"><b>Example�14.3.�ADS Domain Member smb.conf using idmap_rid</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2606774"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id2606785"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id2606797"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2606809"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id2606821"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2606832"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606844"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606857"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606868"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606880"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2606892"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606904"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606916"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606928"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606940"></a><em class="parameter"><code>printer admin = "Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2606955"></a>
-	<a class="indexterm" name="id2606962"></a>
-	<a class="indexterm" name="id2606969"></a>
-	<a class="indexterm" name="id2606976"></a>
+	</p><div class="example"><a name="idmapadsridDMS"></a><p class="title"><b>Example�14.3.�ADS Domain Member smb.conf using idmap_rid</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2606762"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id2606774"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id2606786"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2606798"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id2606810"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2606821"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606833"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606845"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606857"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id2606869"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2606881"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606893"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606905"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id2606917"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2606929"></a><em class="parameter"><code>printer admin = "Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2606944"></a>
+	<a class="indexterm" name="id2606951"></a>
+	<a class="indexterm" name="id2606958"></a>
+	<a class="indexterm" name="id2606964"></a>
 	In a large domain with many users it is imperative to disable enumeration of users and groups.
 	For example, at a site that has 22,000 users in Active Directory the winbind-based user and
 	group resolution is unavailable for nearly 12 minutes following first startup of 
@@ -488,8 +488,8 @@ Join to domain is not valid
 	or groups using the <code class="literal">getent passwd</code> and <code class="literal">getent group</code>
 	commands. It will be possible to perform the lookup for individual users, as shown in the following procedure.
 	</p><p>
-	<a class="indexterm" name="id2607013"></a>
-	<a class="indexterm" name="id2607020"></a>
+	<a class="indexterm" name="id2607002"></a>
+	<a class="indexterm" name="id2607008"></a>
 	The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
 	<code class="filename">/etc/nsswitch.conf</code> so it has the following parameters:
 </p><pre class="screen">
@@ -515,7 +515,7 @@ Using short domain name -- KPAK
 Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
 </pre><p>
 		</p><p>
-		<a class="indexterm" name="id2607099"></a>
+		<a class="indexterm" name="id2607088"></a>
 		An invalid or failed join can be detected by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code> net ads testjoin
@@ -531,14 +531,14 @@ Join to domain is not valid
 		Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown.
 		</p></li><li><p>
 		Validate the operation of this configuration by executing:
-		<a class="indexterm" name="id2607164"></a>
+		<a class="indexterm" name="id2607153"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> getent passwd administrator
 administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
 </pre><p>
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607186"></a>IDMAP Storage in LDAP Using Winbind</h3></div></div></div><p>
-	<a class="indexterm" name="id2607194"></a>
-	<a class="indexterm" name="id2607201"></a>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607175"></a>IDMAP Storage in LDAP Using Winbind</h3></div></div></div><p>
+	<a class="indexterm" name="id2607183"></a>
+	<a class="indexterm" name="id2607190"></a>
 	The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains and
 	ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any
 	standards-complying LDAP server can be used. It is therefore possible to deploy this IDMAP
@@ -547,15 +547,15 @@ administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
 	</p><p>
 	An example is for an ADS domain is shown in <a class="link" href="idmapper.html#idmapldapDMS" title="Example�14.4.�ADS Domain Member Server using LDAP">ADS Domain Member Server using
 	LDAP</a>.
-	</p><div class="example"><a name="idmapldapDMS"></a><p class="title"><b>Example�14.4.�ADS Domain Member Server using LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607255"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id2607266"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id2607278"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607290"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2607302"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2607314"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id2607326"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607338"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2607350"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607362"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id2607374"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607386"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607398"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2607409"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2607425"></a>
+	</p><div class="example"><a name="idmapldapDMS"></a><p class="title"><b>Example�14.4.�ADS Domain Member Server using LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607244"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id2607255"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id2607267"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607279"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id2607291"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2607302"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id2607314"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607327"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2607339"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607351"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id2607363"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607375"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607386"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2607398"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2607414"></a>
 	In the case of an NT4 or Samba-3-style domain the <em class="parameter"><code>realm</code></em> is not used, and the
 	command used to join the domain is <code class="literal">net rpc join</code>. The above example also demonstrates
 	advanced error-reporting techniques that are documented in <a class="link" href="bugreport.html#dbglvl" title="Debug Levels">Reporting Bugs</a>.
 	</p><p>
-	<a class="indexterm" name="id2607459"></a>
-	<a class="indexterm" name="id2607465"></a>
-	<a class="indexterm" name="id2607472"></a>
+	<a class="indexterm" name="id2607448"></a>
+	<a class="indexterm" name="id2607454"></a>
+	<a class="indexterm" name="id2607461"></a>
 	Where MIT kerberos is installed (version 1.3.4 or later), edit the <code class="filename">/etc/krb5.conf</code> 
 	file so it has the following contents:
 </p><pre class="screen">
@@ -610,8 +610,8 @@ hosts:  files wins
 ...
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2607556"></a>
-	<a class="indexterm" name="id2607563"></a>
+	<a class="indexterm" name="id2607545"></a>
+	<a class="indexterm" name="id2607551"></a>
 	You will need the <a class="ulink" href="http://www.padl.com" target="_top">PADL</a> <code class="literal">nss_ldap</code> 
 	tool set for this solution. Configure the <code class="filename">/etc/ldap.conf</code> file so it has 
 	the information needed. The following is an example of a working file:
@@ -674,21 +674,21 @@ Joined 'GOODELF' to realm 'SNOWSHOW.COM'
 		</p></li><li><p>
 		Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown.
 		</p></li></ol></div><p>
-	<a class="indexterm" name="id2607758"></a>
+	<a class="indexterm" name="id2607747"></a>
 	Follow the diagnositic procedures shown earlier in this chapter to identify success or failure of the join.
 	In many cases a failure is indicated by a silent return to the command prompt with no indication of the
 	reason for failure.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607771"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h3></div></div></div><p>
-	<a class="indexterm" name="id2607780"></a>
-	<a class="indexterm" name="id2607787"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607760"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h3></div></div></div><p>
+	<a class="indexterm" name="id2607769"></a>
+	<a class="indexterm" name="id2607776"></a>
 	The use of this method is messy. The information provided in the following is for guidance only
 	and is very definitely not complete. This method does work; it is used in a number of large sites
 	and has an acceptable level of performance.
 	</p><p>
 	An example <code class="filename">smb.conf</code> file is shown in <a class="link" href="idmapper.html#idmaprfc2307" title="Example�14.5.�ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS">ADS Domain Member Server using
 RFC2307bis Schema Extension Date via NSS</a>.
-	</p><div class="example"><a name="idmaprfc2307"></a><p class="title"><b>Example�14.5.�ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607846"></a><em class="parameter"><code>workgroup = BOBBY</code></em></td></tr><tr><td><a class="indexterm" name="id2607858"></a><em class="parameter"><code>realm = BOBBY.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607870"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2607881"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607893"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607905"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2607917"></a><em class="parameter"><code>winbind cache time = 5</code></em></td></tr><tr><td><a class="indexterm" name="id2607928"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607941"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607953"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2607968"></a>
+	</p><div class="example"><a name="idmaprfc2307"></a><p class="title"><b>Example�14.5.�ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2607835"></a><em class="parameter"><code>workgroup = BOBBY</code></em></td></tr><tr><td><a class="indexterm" name="id2607847"></a><em class="parameter"><code>realm = BOBBY.COM</code></em></td></tr><tr><td><a class="indexterm" name="id2607858"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id2607870"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607882"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id2607894"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id2607905"></a><em class="parameter"><code>winbind cache time = 5</code></em></td></tr><tr><td><a class="indexterm" name="id2607917"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607929"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2607942"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2607957"></a>
 	The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
 	to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
 	following:
@@ -697,7 +697,7 @@ RFC2307bis Schema Extension Date via NSS</a>.
 make install
 </pre><p> 
 	</p><p>
-	<a class="indexterm" name="id2607988"></a>
+	<a class="indexterm" name="id2607977"></a>
 	The following <code class="filename">/etc/nsswitch.conf</code> file contents are required:
 </p><pre class="screen">
 ...
@@ -709,23 +709,21 @@ hosts:  files wins
 ...
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2608013"></a>
-	<a class="indexterm" name="id2608020"></a>
+	<a class="indexterm" name="id2608002"></a>
+	<a class="indexterm" name="id2608008"></a>
 	The <code class="filename">/etc/ldap.conf</code> file must be configured also. Refer to the PADL documentation
 	and source code for nss_ldap to specific instructions.
 	</p><p>
 	The next step involves preparation of the ADS schema. This is briefly discussed in the remaining
 	part of this chapter.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2608041"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h4></div></div></div><p>
-		<a class="indexterm" name="id2608050"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2608030"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h4></div></div></div><p>
+		<a class="indexterm" name="id2608038"></a>
 		The Microsoft Windows Service for UNIX (SFU) version 3.5 is available for free 
 		<a class="ulink" href="http://www.microsoft.com/windows/sfu/" target="_top">download</a>
 		from the Microsoft Web site. You will need to download this tool and install it following
 		Microsoft instructions.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2608069"></a>IDMAP, Active Directory and AD4UNIX</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2608058"></a>IDMAP, Active Directory and AD4UNIX</h4></div></div></div><p>
 		Instructions for obtaining and installing the AD4UNIX tool set can be found from the
 		<a class="ulink" href="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach" target="_top">
 		Geekcomix</a> Web site.
-		</p></div></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2604373" href="#id2604373" class="para">4</a>] </sup>Samba local account mode results in both
-<code class="literal">DOMINICUS\FJones</code> and <code class="literal">FRANCISCUS\FJones</code> mapping to the UNIX user
-<code class="literal">FJones</code>.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="rights.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�13.�Remote and Local Management: The Net Command�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�15.�User Rights and Privileges</td></tr></table></div></body></html>
+		</p></div></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><code class="literal"><sup>[<a name="ftn.id2604358" href="#id2604358" class="literal">4</a>] </sup>DOMINICUS\FJones</code><code class="literal">FRANCISCUS\FJones</code><code class="literal">FJones</code></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="rights.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�13.�Remote and Local Management: The Net Command�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�15.�User Rights and Privileges</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/images/10small.png b/docs/htmldocs/Samba3-HOWTO/images/10small.png
new file mode 100644
index 0000000000..56a9b0cd67
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/10small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/11small.png b/docs/htmldocs/Samba3-HOWTO/images/11small.png
new file mode 100644
index 0000000000..18f5d9e4dd
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/11small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/12small.png b/docs/htmldocs/Samba3-HOWTO/images/12small.png
new file mode 100644
index 0000000000..5bdf809c1b
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/12small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/13small.png b/docs/htmldocs/Samba3-HOWTO/images/13small.png
new file mode 100644
index 0000000000..536b2fc2c2
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/13small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/14small.png b/docs/htmldocs/Samba3-HOWTO/images/14small.png
new file mode 100644
index 0000000000..89054249c0
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/14small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/1small.png b/docs/htmldocs/Samba3-HOWTO/images/1small.png
new file mode 100644
index 0000000000..c4905163c9
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/1small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/2small.png b/docs/htmldocs/Samba3-HOWTO/images/2small.png
new file mode 100644
index 0000000000..5fd9071349
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/2small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/3small.png b/docs/htmldocs/Samba3-HOWTO/images/3small.png
new file mode 100644
index 0000000000..22a39bae52
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/3small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/4small.png b/docs/htmldocs/Samba3-HOWTO/images/4small.png
new file mode 100644
index 0000000000..6b7f1b1fd4
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/4small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/5small.png b/docs/htmldocs/Samba3-HOWTO/images/5small.png
new file mode 100644
index 0000000000..b23e1fc2c7
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/5small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/6small.png b/docs/htmldocs/Samba3-HOWTO/images/6small.png
new file mode 100644
index 0000000000..35a646d826
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/6small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/7small.png b/docs/htmldocs/Samba3-HOWTO/images/7small.png
new file mode 100644
index 0000000000..d182677510
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/7small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/8small.png b/docs/htmldocs/Samba3-HOWTO/images/8small.png
new file mode 100644
index 0000000000..08aca66386
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/8small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/9small.png b/docs/htmldocs/Samba3-HOWTO/images/9small.png
new file mode 100644
index 0000000000..90c2cde327
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/9small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME001.png b/docs/htmldocs/Samba3-HOWTO/images/WME001.png
new file mode 100644
index 0000000000..c5db7570bc
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME001.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME002.png b/docs/htmldocs/Samba3-HOWTO/images/WME002.png
new file mode 100644
index 0000000000..641f2179a0
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME002.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME003.png b/docs/htmldocs/Samba3-HOWTO/images/WME003.png
new file mode 100644
index 0000000000..073c58eddd
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME003.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME005.png b/docs/htmldocs/Samba3-HOWTO/images/WME005.png
new file mode 100644
index 0000000000..5e4e72e498
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME005.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME009.png b/docs/htmldocs/Samba3-HOWTO/images/WME009.png
new file mode 100644
index 0000000000..f851876cee
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME009.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME010.png b/docs/htmldocs/Samba3-HOWTO/images/WME010.png
new file mode 100644
index 0000000000..589be02b22
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME010.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME013.png b/docs/htmldocs/Samba3-HOWTO/images/WME013.png
new file mode 100644
index 0000000000..0f0a70d062
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME013.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WME014.png b/docs/htmldocs/Samba3-HOWTO/images/WME014.png
new file mode 100644
index 0000000000..73f1dde37c
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WME014.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WXPP002.png b/docs/htmldocs/Samba3-HOWTO/images/WXPP002.png
new file mode 100644
index 0000000000..b87001bca4
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WXPP002.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WXPP003.png b/docs/htmldocs/Samba3-HOWTO/images/WXPP003.png
new file mode 100644
index 0000000000..a60d6c413a
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WXPP003.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WXPP005.png b/docs/htmldocs/Samba3-HOWTO/images/WXPP005.png
new file mode 100644
index 0000000000..4aa091767b
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WXPP005.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WXPP009.png b/docs/htmldocs/Samba3-HOWTO/images/WXPP009.png
new file mode 100644
index 0000000000..b540e238b8
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WXPP009.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/WXPP014.png b/docs/htmldocs/Samba3-HOWTO/images/WXPP014.png
new file mode 100644
index 0000000000..f1e02d3ce3
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/WXPP014.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/a_small.png b/docs/htmldocs/Samba3-HOWTO/images/a_small.png
new file mode 100644
index 0000000000..a6622ef6cf
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/a_small.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/access1.png b/docs/htmldocs/Samba3-HOWTO/images/access1.png
new file mode 100644
index 0000000000..ae63d37260
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/access1.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/browsing1.png b/docs/htmldocs/Samba3-HOWTO/images/browsing1.png
new file mode 100644
index 0000000000..b6bb26e875
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/browsing1.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/cups1.png b/docs/htmldocs/Samba3-HOWTO/images/cups1.png
new file mode 100644
index 0000000000..43c3645c40
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/cups1.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/cups2.png b/docs/htmldocs/Samba3-HOWTO/images/cups2.png
new file mode 100644
index 0000000000..4095484dc5
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/cups2.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/domain.png b/docs/htmldocs/Samba3-HOWTO/images/domain.png
new file mode 100644
index 0000000000..b1e372f07a
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/domain.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/ethereal1.png b/docs/htmldocs/Samba3-HOWTO/images/ethereal1.png
new file mode 100644
index 0000000000..c8655389d0
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/ethereal1.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/ethereal2.png b/docs/htmldocs/Samba3-HOWTO/images/ethereal2.png
new file mode 100644
index 0000000000..f366772d3b
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/ethereal2.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap-gid2sid.png b/docs/htmldocs/Samba3-HOWTO/images/idmap-gid2sid.png
new file mode 100644
index 0000000000..1a8a3c4d48
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap-gid2sid.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2gid.png b/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2gid.png
new file mode 100644
index 0000000000..67d8703983
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2gid.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2uid.png b/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2uid.png
new file mode 100644
index 0000000000..e083ad8d9f
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap-sid2uid.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap-store-gid2sid.png b/docs/htmldocs/Samba3-HOWTO/images/idmap-store-gid2sid.png
new file mode 100644
index 0000000000..7893af599c
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap-store-gid2sid.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap-uid2sid.png b/docs/htmldocs/Samba3-HOWTO/images/idmap-uid2sid.png
new file mode 100644
index 0000000000..4895eb73d7
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap-uid2sid.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/idmap_winbind_no_loop.png b/docs/htmldocs/Samba3-HOWTO/images/idmap_winbind_no_loop.png
new file mode 100644
index 0000000000..5393f6a192
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/idmap_winbind_no_loop.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/pdftoepsonusb.png b/docs/htmldocs/Samba3-HOWTO/images/pdftoepsonusb.png
new file mode 100644
index 0000000000..4aa6150e0a
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/pdftoepsonusb.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/pdftosocket.png b/docs/htmldocs/Samba3-HOWTO/images/pdftosocket.png
new file mode 100644
index 0000000000..6b606c7191
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/pdftosocket.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/trusts1.png b/docs/htmldocs/Samba3-HOWTO/images/trusts1.png
new file mode 100644
index 0000000000..53a9ce2fc3
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/trusts1.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/w2kp001.png b/docs/htmldocs/Samba3-HOWTO/images/w2kp001.png
new file mode 100644
index 0000000000..43adf23463
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/w2kp001.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/w2kp002.png b/docs/htmldocs/Samba3-HOWTO/images/w2kp002.png
new file mode 100644
index 0000000000..13bb029f53
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/w2kp002.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/w2kp003.png b/docs/htmldocs/Samba3-HOWTO/images/w2kp003.png
new file mode 100644
index 0000000000..c7b779900e
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/w2kp003.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/w2kp004.png b/docs/htmldocs/Samba3-HOWTO/images/w2kp004.png
new file mode 100644
index 0000000000..d0e005a36e
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/w2kp004.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/w2kp005.png b/docs/htmldocs/Samba3-HOWTO/images/w2kp005.png
new file mode 100644
index 0000000000..a729b40cd7
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/w2kp005.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/wxpp001.png b/docs/htmldocs/Samba3-HOWTO/images/wxpp001.png
new file mode 100644
index 0000000000..2e689a17e2
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/wxpp001.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/wxpp004.png b/docs/htmldocs/Samba3-HOWTO/images/wxpp004.png
new file mode 100644
index 0000000000..656f67942e
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/wxpp004.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/wxpp006.png b/docs/htmldocs/Samba3-HOWTO/images/wxpp006.png
new file mode 100644
index 0000000000..a20b3ed583
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/wxpp006.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/wxpp007.png b/docs/htmldocs/Samba3-HOWTO/images/wxpp007.png
new file mode 100644
index 0000000000..cf41352220
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/wxpp007.png
diff --git a/docs/htmldocs/Samba3-HOWTO/images/wxpp008.png b/docs/htmldocs/Samba3-HOWTO/images/wxpp008.png
new file mode 100644
index 0000000000..9958c7c873
--- /dev/null
+++ b/docs/htmldocs/Samba3-HOWTO/images/wxpp008.png
diff --git a/docs/htmldocs/Samba3-HOWTO/index.html b/docs/htmldocs/Samba3-HOWTO/index.html
index 9c2debb797..9954b0c6eb 100644
--- a/docs/htmldocs/Samba3-HOWTO/index.html
+++ b/docs/htmldocs/Samba3-HOWTO/index.html
@@ -1,50 +1,50 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Official Samba 3.5.x HOWTO and Reference Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="next" href="pr01.html" title="About the Cover Artwork"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Official Samba 3.5.x HOWTO and Reference Guide</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>The Official Samba 3.5.x HOWTO and Reference Guide</h1></div><div><div class="authorgroup"><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div><div><p class="pubdate"></p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">About the Cover Artwork</a></span></dt><dt><span class="preface"><a href="pr02.html">Attribution</a></span></dt><dt><span class="preface"><a href="pr03.html">Foreword</a></span></dt><dt><span class="preface"><a href="TOSHpreface.html">Preface</a></span></dt><dd><dl><dt><span class="sect1"><a href="TOSHpreface.html#id2551173">Conventions Used</a></span></dt></dl></dd><dt><span class="preface"><a href="IntroSMB.html">Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="IntroSMB.html#id2551356">What Is Samba?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2498869">Why This Book?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2551652">Book Structure and Layout</a></span></dt></dl></dd><dt><span class="part"><a href="introduction.html">I. General Installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="install.html">1. How to Install and Test SAMBA</a></span></dt><dd><dl><dt><span class="sect1"><a href="install.html#id2551914">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551954">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551996">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552898">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553078">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553482">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553540">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553592">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553683">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553764">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553805">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553838">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553848">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553935">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553968">The network name cannot be found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="FastStart.html">2. Fast Start: Cure for Impatience</a></span></dt><dd><dl><dt><span class="sect1"><a href="FastStart.html#id2554110">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554133">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554203">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554221">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555963">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556806">Domain Controller</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="type.html">II. Server Configuration Basics</a></span></dt><dd><dl><dt><span class="chapter"><a href="ServerType.html">3. Server Types and Security Modes</a></span></dt><dd><dl><dt><span class="sect1"><a href="ServerType.html#id2558810">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558970">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559114">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559276">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559439">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560266">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560541">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560728">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560758">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560791">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560828">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560854">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560912">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-pdc.html">4. Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561237">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562461">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562480">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562984">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564237">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564290">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564309">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565181">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565287">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565352">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565428">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565548">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565575">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565594">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-bdc.html">5. Backup Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565778">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566184">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567306">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568138">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568602">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568861">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="domain-member.html">6. Domain Membership</a></span></dt><dd><dl><dt><span class="sect1"><a href="domain-member.html#id2569109">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570619">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572129">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573414">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573692">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="StandAloneServer.html">7. Standalone Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574171">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574265">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574457">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575441">Common Errors</a></span></dt></dl></dd><dt><span class="chapter"><a href="ClientConfig.html">8. MS Windows Network Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575508">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575568">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575612">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578353">Common Errors</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="optional.html">III. Advanced Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ChangeNotes.html">9. Important and Critical Change Notes for the Samba 3.x Series</a></span></dt><dd><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578591">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578602">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578661">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578973">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579095">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetworkBrowsing.html">10. Network Browsing</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579538">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583156">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583364">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584196">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584481">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585120">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586391">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586491">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586539">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="passdb.html">11. Account Information Databases</a></span></dt><dd><dl><dt><span class="sect1"><a href="passdb.html#id2587269">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587489">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588057">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589125">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589979">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592519">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592573">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592915">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593073">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595597">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595603">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595641">Configuration of auth methods</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="groupmapping.html">12. Group Mapping: MS Windows and UNIX</a></span></dt><dd><dl><dt><span class="sect1"><a href="groupmapping.html#id2595892">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596308">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597278">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598144">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598220">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598404">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598531">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598544">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598630">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetCommand.html">13. Remote and Local Management: The Net Command</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetCommand.html#id2599025">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599319">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599559">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600921">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601133">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601181">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601250">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601678">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601693">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602062">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602518">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602563">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602751">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602781">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603404">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603657">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603676">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603742">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603858">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603875">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603919">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603955">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></dd><dt><span class="chapter"><a href="idmapper.html">14. Identity Mapping (IDMAP)</a></span></dt><dd><dl><dt><span class="sect1"><a href="idmapper.html#id2604465">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604490">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605504">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605739">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605874">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="rights.html">15. User Rights and Privileges</a></span></dt><dd><dl><dt><span class="sect1"><a href="rights.html#id2608440">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608715">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609060">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609882">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610059">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AccessControls.html">16. File, Directory, and Share Access Controls</a></span></dt><dd><dl><dt><span class="sect1"><a href="AccessControls.html#id2610562">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610748">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611105">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611229">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611888">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611921">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612289">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612626">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612964">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613112">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613459">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613465">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613512">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613583">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613726">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613942">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614099">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614468">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614541">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614954">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614965">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615288">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615334">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="locking.html">17. File and Record Locking</a></span></dt><dd><dl><dt><span class="sect1"><a href="locking.html#id2615570">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615667">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615926">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616903">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2616998">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617411">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617598">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617620">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617686">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617712">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617779">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617810">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617834">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617866">Additional Reading</a></span></dt></dl></dd><dt><span class="chapter"><a href="securing-samba.html">18. Securing Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="securing-samba.html#id2618040">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618151">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618297">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618313">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618467">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618527">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619021">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619076">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619119">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619142">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="InterdomainTrusts.html">19. Interdomain Trust Relationships</a></span></dt><dd><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619731">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621195">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621208">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621254">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="msdfs.html">20. Hosting a Microsoft Distributed File System Tree</a></span></dt><dd><dl><dt><span class="sect1"><a href="msdfs.html#id2621432">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621844">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621877">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="classicalprinting.html">21. Classical Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622075">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622298">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622450">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622610">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623480">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623935">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626941">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627479">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627627">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627720">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629667">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629683">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630248">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630366">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630540">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630560">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630928">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631184">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631444">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631557">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631819">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631928">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2631965">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632011">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632045">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632061">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632078">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632212">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632486">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632524">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632673">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632702">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632708">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632749">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="CUPS-printing.html">22. CUPS Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632896">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632902">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632962">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633679">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634056">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634359">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634646">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636764">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636922">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637109">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637277">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637547">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637850">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638424">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638437">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638506">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639941">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640064">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640159">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640176">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640238">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640414">Network Printing (Windows Clients and UNIX/Samba Print
-Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640432">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640622">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640702">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640792">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640836">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640904">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640919">Printer Drivers Running in Kernel Mode Cause Many
-Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640957">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640975">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641105">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641128">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641226">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641746">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641865">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641890">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642892">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643014">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643095">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643757">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643862">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645523">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645591">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645657">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645708">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646003">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646814">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647287">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647322">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647376">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647558">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647709">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647775">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647815">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647829">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648122">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648207">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648346">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648699">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648810">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648816">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648892">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648930">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649005">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649029">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649120">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649172">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649209">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649245">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649280">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649313">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649354">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649379">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649426">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649709">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649764">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649814">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649981">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650035">Overview of the CUPS Printing Processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="VFS.html">23. Stackable VFS modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="VFS.html#id2650223">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650261">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650657">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650662">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650703">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650921">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651247">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651644">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651694">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652604">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652629">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652689">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652728">vscan-clamav</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="winbind.html">24. Winbind: Use of Domain Accounts</a></span></dt><dd><dl><dt><span class="sect1"><a href="winbind.html#id2652992">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653341">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653431">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653584">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653629">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653755">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653892">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653940">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654172">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654327">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654403">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654460">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654466">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654580">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654732">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657151">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657199">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657241">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657278">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AdvancedNetworkManagement.html">25. Advanced Network Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657466">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657636">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658226">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658451">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658494">Limiting Logon Connections</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="PolicyMgmt.html">26. System and Account Policies</a></span></dt><dd><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658637">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2659980">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660075">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660115">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660180">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660338">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660349">Policy Does Not Work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ProfileMgmt.html">27. Desktop Profile Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660434">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660484">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660538">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661143">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662488">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662631">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663192">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664442">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664453">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664514">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664685">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664849">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="pam.html">28. PAM-Based Distributed Authentication</a></span></dt><dd><dl><dt><span class="sect1"><a href="pam.html#id2665025">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665655">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665709">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666709">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667015">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667096">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667199">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667593">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667604">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667702">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="integrate-ms-networks.html">29. Integrating MS Windows Networks with Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667924">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667945">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668147">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668326">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668362">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669058">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669245">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669273">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669301">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669438">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669452">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669483">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669525">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="unicode.html">30. Unicode/Charsets</a></span></dt><dd><dl><dt><span class="sect1"><a href="unicode.html#id2669736">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669787">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669921">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670056">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670088">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670218">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670859">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670982">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671128">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671134">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Backup.html">31. Backup Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="Backup.html#id2671241">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671286">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671383">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671554">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671724">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671772">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SambaHA.html">32. High Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="SambaHA.html#id2671868">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2671989">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672023">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672152">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672866">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672946">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673086">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673123">Conclusions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="largefile.html">33. Handling Large Directories</a></span></dt><dt><span class="chapter"><a href="cfgsmarts.html">34. Advanced Configuration Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673754">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="migration.html">IV. Migration and Updating</a></span></dt><dd><dl><dt><span class="chapter"><a href="upgrading-to-3.0.html">35. Updating and Upgrading Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676070">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676098">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676299">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676308">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677518">New Functionality</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NT4Migration.html">36. Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><dl><dt><span class="sect1"><a href="NT4Migration.html#id2678914">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2678949">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2679885">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680120">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680206">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SWAT.html">37. SWAT: The Samba Web Administration Tool</a></span></dt><dd><dl><dt><span class="sect1"><a href="SWAT.html#id2680929">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681054">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681073">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681711">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682061">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682074">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682135">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682237">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682293">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682349">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682412">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682456">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682475">The Password Change Page</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="troubleshooting.html">V. Troubleshooting</a></span></dt><dd><dl><dt><span class="chapter"><a href="diagnosis.html">38. The Samba Checklist</a></span></dt><dd><dl><dt><span class="sect1"><a href="diagnosis.html#id2682610">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682648">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682941">The Tests</a></span></dt></dl></dd><dt><span class="chapter"><a href="problems.html">39. Analyzing and Solving Samba Problems</a></span></dt><dd><dl><dt><span class="sect1"><a href="problems.html#id2684689">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684741">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2684997">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685047">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685190">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685523">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685560">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685735">How to Get Off the Mailing Lists</a></span></dt></dl></dd><dt><span class="chapter"><a href="bugreport.html">40. Reporting Bugs</a></span></dt><dd><dl><dt><span class="sect1"><a href="bugreport.html#id2685866">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2685956">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686191">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686393">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686526">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686652">Patches</a></span></dt></dl></dd><dt><span class="chapter"><a href="tdb.html">41. Managing TDB Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="tdb.html#id2686735">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687197">Managing TDB Files</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="Appendix.html">VI. Reference Section</a></span></dt><dd><dl><dt><span class="chapter"><a href="compiling.html">42. How to Compile Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="compiling.html#id2687392">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687398">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687440">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687637">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687711">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687849">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688088">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688359">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688579">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Portability.html">43. Portability</a></span></dt><dd><dl><dt><span class="sect1"><a href="Portability.html#id2688963">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689067">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689106">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689248">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689291">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689353">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689358">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Other-Clients.html">44. Samba and Other CIFS Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689543">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689627">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689633">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689752">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689809">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2689902">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689908">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689991">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690017">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690075">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690107">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690164">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690233">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690254">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690450">Windows NT 3.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="speed.html">45. Samba Performance Tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="speed.html#id2690558">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690596">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690693">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690737">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690785">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690809">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690876">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690928">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690952">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691160">Samba Performance is Very Slow</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-ldap-tls.html">46. LDAP and Transport Layer Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch47.html">47. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch47.html#id2692350">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692569">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="DNSDHCP.html">48. DNS and DHCP Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692722">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2692901">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2692992">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Official Samba 3.4.x HOWTO and Reference Guide</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="next" href="pr01.html" title="About the Cover Artwork"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Official Samba 3.4.x HOWTO and Reference Guide</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>The Official Samba 3.4.x HOWTO and Reference Guide</h1></div><div><div class="authorgroup"><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div></div><div><p class="pubdate"></p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">About the Cover Artwork</a></span></dt><dt><span class="preface"><a href="pr02.html">Attribution</a></span></dt><dt><span class="preface"><a href="pr03.html">Foreword</a></span></dt><dt><span class="preface"><a href="TOSHpreface.html">Preface</a></span></dt><dd><dl><dt><span class="sect1"><a href="TOSHpreface.html#id2551169">Conventions Used</a></span></dt></dl></dd><dt><span class="preface"><a href="IntroSMB.html">Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="IntroSMB.html#id2551351">What Is Samba?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2498862">Why This Book?</a></span></dt><dt><span class="sect1"><a href="IntroSMB.html#id2551647">Book Structure and Layout</a></span></dt></dl></dd><dt><span class="part"><a href="introduction.html">I. General Installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="install.html">1. How to Install and Test SAMBA</a></span></dt><dd><dl><dt><span class="sect1"><a href="install.html#id2551909">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551950">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551991">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552892">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553073">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553476">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553534">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553587">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553678">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553759">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553800">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553832">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553842">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553930">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553962">The network name cannot be found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="FastStart.html">2. Fast Start: Cure for Impatience</a></span></dt><dd><dl><dt><span class="sect1"><a href="FastStart.html#id2554105">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554128">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554197">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554216">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555957">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556800">Domain Controller</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="type.html">II. Server Configuration Basics</a></span></dt><dd><dl><dt><span class="chapter"><a href="ServerType.html">3. Server Types and Security Modes</a></span></dt><dd><dl><dt><span class="sect1"><a href="ServerType.html#id2558805">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558964">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559109">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559271">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559434">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560264">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560539">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560726">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560756">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560788">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560825">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560852">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560910">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-pdc.html">4. Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561235">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562458">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562478">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562982">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564236">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564289">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564308">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565179">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565286">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565350">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565427">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565546">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565573">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565592">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-bdc.html">5. Backup Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565776">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566182">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567305">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568136">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568600">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568859">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="domain-member.html">6. Domain Membership</a></span></dt><dd><dl><dt><span class="sect1"><a href="domain-member.html#id2569108">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570618">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572100">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573385">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573664">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="StandAloneServer.html">7. Standalone Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574148">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574242">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574443">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575426">Common Errors</a></span></dt></dl></dd><dt><span class="chapter"><a href="ClientConfig.html">8. MS Windows Network Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575494">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575554">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575598">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578339">Common Errors</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="optional.html">III. Advanced Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ChangeNotes.html">9. Important and Critical Change Notes for the Samba 3.x Series</a></span></dt><dd><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578577">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578588">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578647">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578959">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579081">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetworkBrowsing.html">10. Network Browsing</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579524">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583131">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583338">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584164">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584448">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585087">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586352">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586451">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586500">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="passdb.html">11. Account Information Databases</a></span></dt><dd><dl><dt><span class="sect1"><a href="passdb.html#id2587230">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587457">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588025">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589094">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589947">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592500">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592553">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592895">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593053">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595578">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595583">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595621">Configuration of auth methods</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="groupmapping.html">12. Group Mapping: MS Windows and UNIX</a></span></dt><dd><dl><dt><span class="sect1"><a href="groupmapping.html#id2595872">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596288">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597258">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598124">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598201">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598384">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598511">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598524">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598611">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetCommand.html">13. Remote and Local Management: The Net Command</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetCommand.html#id2599005">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599300">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599539">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600908">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601120">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601168">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601237">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601665">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601680">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602049">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602505">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602550">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602738">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602768">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603391">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603642">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603661">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603727">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603842">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603860">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603904">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603939">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></dd><dt><span class="chapter"><a href="idmapper.html">14. Identity Mapping (IDMAP)</a></span></dt><dd><dl><dt><span class="sect1"><a href="idmapper.html#id2604449">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604474">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605493">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605727">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605862">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="rights.html">15. User Rights and Privileges</a></span></dt><dd><dl><dt><span class="sect1"><a href="rights.html#id2608437">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608712">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609058">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609884">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610061">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AccessControls.html">16. File, Directory, and Share Access Controls</a></span></dt><dd><dl><dt><span class="sect1"><a href="AccessControls.html#id2610564">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610751">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611102">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611225">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611896">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611929">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612297">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612634">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612972">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613120">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613466">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613473">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613520">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613591">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613735">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613950">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614107">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614477">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614550">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614968">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614980">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615303">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615348">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="locking.html">17. File and Record Locking</a></span></dt><dd><dl><dt><span class="sect1"><a href="locking.html#id2615585">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615682">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615940">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616945">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617040">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617453">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617640">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617662">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617728">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617754">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617821">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617852">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617876">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617908">Additional Reading</a></span></dt></dl></dd><dt><span class="chapter"><a href="securing-samba.html">18. Securing Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="securing-samba.html#id2618082">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618181">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618327">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618343">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618497">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618557">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619056">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619110">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619154">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619170">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="InterdomainTrusts.html">19. Interdomain Trust Relationships</a></span></dt><dd><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619759">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621231">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621243">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621289">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="msdfs.html">20. Hosting a Microsoft Distributed File System Tree</a></span></dt><dd><dl><dt><span class="sect1"><a href="msdfs.html#id2621467">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621887">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621920">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="classicalprinting.html">21. Classical Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622118">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622341">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622493">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622653">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623534">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623989">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626995">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627533">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627675">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627768">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629701">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629717">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630283">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630401">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630574">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630595">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630963">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631219">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631479">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631592">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631902">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632011">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632048">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632094">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632128">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632144">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632162">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632295">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632569">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632608">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632756">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632786">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632791">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632833">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="CUPS-printing.html">22. CUPS Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632975">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632981">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633040">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633768">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634145">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634448">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634735">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636855">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637012">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637200">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637368">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637637">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637941">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638515">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638528">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638596">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640032">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640155">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640249">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640266">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640328">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640504">Network Printing (Windows Clients and UNIX/Samba Print
+Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640522">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640713">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640792">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640882">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640927">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640995">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641009">Printer Drivers Running in Kernel Mode Cause Many
+Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641048">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641066">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641196">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641218">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641316">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641837">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641956">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641981">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643037">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643159">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643240">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643902">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644007">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645668">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645735">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645802">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645852">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646148">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646969">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647442">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647478">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647532">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647713">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647858">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647924">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647964">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647978">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648271">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648356">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648495">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648838">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648950">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648956">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649032">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649070">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649144">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649169">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649260">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649311">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649349">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649384">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649419">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649452">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649493">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649519">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649565">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649848">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649904">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649954">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650121">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650175">Overview of the CUPS Printing Processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="VFS.html">23. Stackable VFS modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="VFS.html#id2650363">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650401">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650796">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650802">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650843">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651060">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651387">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651783">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651833">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652736">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652762">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652821">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652861">vscan-clamav</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="winbind.html">24. Winbind: Use of Domain Accounts</a></span></dt><dd><dl><dt><span class="sect1"><a href="winbind.html#id2653125">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653468">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653558">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653711">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653756">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653882">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654026">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654073">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654305">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654460">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654536">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654593">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654599">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654713">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654865">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657284">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657333">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657374">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657411">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AdvancedNetworkManagement.html">25. Advanced Network Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657600">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657770">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658359">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658585">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658628">Limiting Logon Connections</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="PolicyMgmt.html">26. System and Account Policies</a></span></dt><dd><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658770">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660100">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660194">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660235">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660299">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660457">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660469">Policy Does Not Work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ProfileMgmt.html">27. Desktop Profile Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660554">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660603">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660657">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661267">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662612">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662744">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663314">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664569">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664580">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664641">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664813">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664976">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="pam.html">28. PAM-Based Distributed Authentication</a></span></dt><dd><dl><dt><span class="sect1"><a href="pam.html#id2665152">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665783">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665836">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666843">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667149">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667230">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667333">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667727">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667738">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667836">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="integrate-ms-networks.html">29. Integrating MS Windows Networks with Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668059">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668079">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668281">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668470">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668506">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669202">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669380">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669408">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669435">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669573">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669586">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669617">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669659">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="unicode.html">30. Unicode/Charsets</a></span></dt><dd><dl><dt><span class="sect1"><a href="unicode.html#id2669864">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669916">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670049">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670185">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670216">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670356">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670996">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2671120">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671266">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671272">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Backup.html">31. Backup Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="Backup.html#id2671379">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671424">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671521">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671692">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671862">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671910">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SambaHA.html">32. High Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="SambaHA.html#id2672006">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2672127">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672161">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672290">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673010">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673091">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673231">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673268">Conclusions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="largefile.html">33. Handling Large Directories</a></span></dt><dt><span class="chapter"><a href="cfgsmarts.html">34. Advanced Configuration Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673899">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="migration.html">IV. Migration and Updating</a></span></dt><dd><dl><dt><span class="chapter"><a href="upgrading-to-3.0.html">35. Updating and Upgrading Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676214">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676251">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676451">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676460">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677671">New Functionality</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NT4Migration.html">36. Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><dl><dt><span class="sect1"><a href="NT4Migration.html#id2679067">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2679102">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680047">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680282">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680369">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SWAT.html">37. SWAT: The Samba Web Administration Tool</a></span></dt><dd><dl><dt><span class="sect1"><a href="SWAT.html#id2681092">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681216">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681236">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681873">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682223">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682236">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682297">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682399">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682455">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682511">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682574">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682618">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682637">The Password Change Page</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="troubleshooting.html">V. Troubleshooting</a></span></dt><dd><dl><dt><span class="chapter"><a href="diagnosis.html">38. The Samba Checklist</a></span></dt><dd><dl><dt><span class="sect1"><a href="diagnosis.html#id2682772">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682811">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2683103">The Tests</a></span></dt></dl></dd><dt><span class="chapter"><a href="problems.html">39. Analyzing and Solving Samba Problems</a></span></dt><dd><dl><dt><span class="sect1"><a href="problems.html#id2684851">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684903">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685159">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685209">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685353">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685678">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685716">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685890">How to Get Off the Mailing Lists</a></span></dt></dl></dd><dt><span class="chapter"><a href="bugreport.html">40. Reporting Bugs</a></span></dt><dd><dl><dt><span class="sect1"><a href="bugreport.html#id2686022">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686111">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686347">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686549">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686682">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686807">Patches</a></span></dt></dl></dd><dt><span class="chapter"><a href="tdb.html">41. Managing TDB Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="tdb.html#id2686891">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687352">Managing TDB Files</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="Appendix.html">VI. Reference Section</a></span></dt><dd><dl><dt><span class="chapter"><a href="compiling.html">42. How to Compile Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="compiling.html#id2687543">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687549">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687590">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687994">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688233">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688504">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688724">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Portability.html">43. Portability</a></span></dt><dd><dl><dt><span class="sect1"><a href="Portability.html#id2689108">HPUX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689212">SCO UNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689251">DNIX</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689392">Red Hat Linux</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689436">AIX: Sequential Read Ahead</a></span></dt><dt><span class="sect1"><a href="Portability.html#id2689498">Solaris</a></span></dt><dd><dl><dt><span class="sect2"><a href="Portability.html#id2689503">Locking Improvements</a></span></dt><dt><span class="sect2"><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Other-Clients.html">44. Samba and Other CIFS Clients</a></span></dt><dd><dl><dt><span class="sect1"><a href="Other-Clients.html#id2689679">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2689763">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2689769">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689888">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2689945">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690038">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690044">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690127">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690153">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690211">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2690243">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690300">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2690369">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2690390">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2690586">Windows NT 3.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="speed.html">45. Samba Performance Tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="speed.html#id2690694">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690732">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690829">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690873">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690921">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690945">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691012">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691088">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691200">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691296">Samba Performance is Very Slow</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-ldap-tls.html">46. LDAP and Transport Layer Security</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-server">Generating the Server Certificate</a></span></dt><dt><span class="sect2"><a href="ch-ldap-tls.html#s1-config-ldap-tls-install">Installing the Certificates</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></span></dt><dt><span class="sect1"><a href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch47.html">47. Samba Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch47.html#id2692487">Free Support</a></span></dt><dt><span class="sect1"><a href="ch47.html#id2692705">Commercial Support</a></span></dt></dl></dd><dt><span class="chapter"><a href="DNSDHCP.html">48. DNS and DHCP Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="DNSDHCP.html#id2692858">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="DNSDHCP.html#id2693042">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="DNSDHCP.html#id2693133">Dynamic DNS</a></span></dt><dt><span class="sect2"><a href="DNSDHCP.html#DHCP">DHCP Server</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="apa.html">A. 
     GNU General Public License version 3
-  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2693290">A. 
+  </a></span></dt><dd><dl><dt><span class="bridgehead"><a href="apa.html#id2693431">A. 
     Preamble
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693435">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693576">A. 
     TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693439">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693580">A. 
     0. Definitions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693532">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693672">A. 
     1. Source Code.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693630">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693771">A. 
     2. Basic Permissions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693681">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693809">A. 
     3. Protecting Users&#8217; Legal Rights From Anti-Circumvention Law.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693716">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693845">A. 
     4. Conveying Verbatim Copies.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693743">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693872">A. 
     5. Conveying Modified Source Versions.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693839">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2693968">A. 
     6. Conveying Non-Source Forms.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694028">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694157">A. 
      7. Additional Terms.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694164">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694293">A. 
      8. Termination.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694208">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694342">A. 
      9. Acceptance Not Required for Having Copies.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694227">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694362">A. 
      10. Automatic Licensing of Downstream Recipients.
-   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694279">A. 
+   </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694414">A. 
     11. Patents.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694425">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694559">A. 
     12. No Surrender of Others&#8217; Freedom.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694447">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694581">A. 
     13. Use with the ???TITLE??? Affero General Public License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694476">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694610">A. 
     14. Revised Versions of this License.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694538">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694672">A. 
     15. Disclaimer of Warranty.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694564">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694698">A. 
     16. Limitation of Liability.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694584">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694719">A. 
     17. Interpretation of Sections 15 and 16.
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694601">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694735">A. 
     END OF TERMS AND CONDITIONS
-  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694605">A. 
+  </a></span></dt><dt><span class="bridgehead"><a href="apa.html#id2694739">A. 
     How to Apply These Terms to Your New Programs
-  </a></span></dt></dl></dd><dt><span class="glossary"><a href="go01.html">Glossary</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>4.1. <a href="samba-pdc.html#domain-example">An Example Domain.</a></dt><dt>8.1. <a href="ClientConfig.html#WXPP002">Network Bridge Configuration.</a></dt><dt>8.2. <a href="ClientConfig.html#WXPP003">Internet Protocol (TCP/IP) Properties.</a></dt><dt>8.3. <a href="ClientConfig.html#WXPP005">Advanced Network Settings</a></dt><dt>8.4. <a href="ClientConfig.html#WXPP014">DNS Configuration.</a></dt><dt>8.5. <a href="ClientConfig.html#WXPP009">WINS Configuration</a></dt><dt>8.6. <a href="ClientConfig.html#w2kp001">Local Area Connection Properties.</a></dt><dt>8.7. <a href="ClientConfig.html#w2kp002">Internet Protocol (TCP/IP) Properties.</a></dt><dt>8.8. <a href="ClientConfig.html#w2kp003">Advanced Network Settings.</a></dt><dt>8.9. <a href="ClientConfig.html#w2kp004">DNS Configuration.</a></dt><dt>8.10. <a href="ClientConfig.html#w2kp005">WINS Configuration.</a></dt><dt>8.11. <a href="ClientConfig.html#WME001">The Windows Me Network Configuration Panel.</a></dt><dt>8.12. <a href="ClientConfig.html#WME002">IP Address.</a></dt><dt>8.13. <a href="ClientConfig.html#WME005">DNS Configuration.</a></dt><dt>8.14. <a href="ClientConfig.html#WME003">WINS Configuration.</a></dt><dt>8.15. <a href="ClientConfig.html#wxpp001">The General Panel.</a></dt><dt>8.16. <a href="ClientConfig.html#wxpp004">The Computer Name Panel.</a></dt><dt>8.17. <a href="ClientConfig.html#wxpp006">The Computer Name Changes Panel.</a></dt><dt>8.18. <a href="ClientConfig.html#wxpp007">The Computer Name Changes Panel  Domain MIDEARTH.</a></dt><dt>8.19. <a href="ClientConfig.html#wxpp008">Computer Name Changes  Username and Password Panel.</a></dt><dt>8.20. <a href="ClientConfig.html#WME009">The Network Panel.</a></dt><dt>8.21. <a href="ClientConfig.html#WME010">Client for Microsoft Networks Properties Panel.</a></dt><dt>8.22. <a href="ClientConfig.html#WME013">Identification Panel.</a></dt><dt>8.23. <a href="ClientConfig.html#WME014">Access Control Panel.</a></dt><dt>10.1. <a href="NetworkBrowsing.html#browsing1">Cross-Subnet Browsing Example.</a></dt><dt>11.1. <a href="passdb.html#idmap-sid2uid">IDMAP: Resolution of SIDs to UIDs.</a></dt><dt>11.2. <a href="passdb.html#idmap-uid2sid">IDMAP: Resolution of UIDs to SIDs.</a></dt><dt>12.1. <a href="groupmapping.html#idmap-sid2gid">IDMAP: Group SID-to-GID Resolution.</a></dt><dt>12.2. <a href="groupmapping.html#idmap-gid2sid">IDMAP: GID Resolution to Matching SID.</a></dt><dt>12.3. <a href="groupmapping.html#idmap-store-gid2sid">IDMAP Storing Group Mappings.</a></dt><dt>16.1. <a href="AccessControls.html#access1">Overview of UNIX permissions field.</a></dt><dt>19.1. <a href="InterdomainTrusts.html#trusts1">Trusts overview.</a></dt><dt>22.1. <a href="CUPS-printing.html#f1small">Windows Printing to a Local Printer.</a></dt><dt>22.2. <a href="CUPS-printing.html#f2small">Printing to a PostScript Printer.</a></dt><dt>22.3. <a href="CUPS-printing.html#f3small">Ghostscript as a RIP for Non-PostScript Printers.</a></dt><dt>22.4. <a href="CUPS-printing.html#f4small">Prefiltering in CUPS to Form PostScript.</a></dt><dt>22.5. <a href="CUPS-printing.html#f5small">Adding Device-Specific Print Options.</a></dt><dt>22.6. <a href="CUPS-printing.html#cups-raster">PostScript to Intermediate Raster Format.</a></dt><dt>22.7. <a href="CUPS-printing.html#cups-raster2">CUPS-Raster Production Using Ghostscript.</a></dt><dt>22.8. <a href="CUPS-printing.html#small8">Image Format to CUPS-Raster Format Conversion.</a></dt><dt>22.9. <a href="CUPS-printing.html#small9">Raster to Printer-Specific Formats.</a></dt><dt>22.10. <a href="CUPS-printing.html#cupsomatic-dia">cupsomatic/foomatic Processing Versus Native CUPS.</a></dt><dt>22.11. <a href="CUPS-printing.html#pdftosocket">PDF to Socket Chain.</a></dt><dt>22.12. <a href="CUPS-printing.html#pdftoepsonusb">PDF to USB Chain.</a></dt><dt>22.13. <a href="CUPS-printing.html#small11">Print Driver Execution on the Client.</a></dt><dt>22.14. <a href="CUPS-printing.html#small12">Print Driver Execution on the Server.</a></dt><dt>22.15. <a href="CUPS-printing.html#f13small">Printing via CUPS/Samba Server.</a></dt><dt>22.16. <a href="CUPS-printing.html#small14">cupsaddsmb Flowchart.</a></dt><dt>22.17. <a href="CUPS-printing.html#cups1">Filtering Chain 1.</a></dt><dt>22.18. <a href="CUPS-printing.html#cups2">Filtering Chain with cupsomatic</a></dt><dt>22.19. <a href="CUPS-printing.html#a_small">CUPS Printing Overview.</a></dt><dt>24.1. <a href="winbind.html#winbind_idmap">Winbind Idmap</a></dt><dt>39.1. <a href="problems.html#ethereal1">Starting a Capture.</a></dt><dt>39.2. <a href="problems.html#ethereal2">Main Ethereal Data Window.</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="install.html#tdbpermfiledesc">Persistent TDB File Descriptions</a></dt><dt>1.2. <a href="install.html#tdbtempfiledesc">Temporary TDB File Descriptions</a></dt><dt>5.1. <a href="samba-bdc.html#pdc-bdc-table">Domain Backend Account Distribution Options</a></dt><dt>6.1. <a href="domain-member.html#assumptions">Assumptions</a></dt><dt>9.1. <a href="ChangeNotes.html#TOSH-domgroups">Essential Domain Group Mappings</a></dt><dt>10.1. <a href="NetworkBrowsing.html#browsubnet">Browse Subnet Example 1</a></dt><dt>10.2. <a href="NetworkBrowsing.html#brsbex">Browse Subnet Example 2</a></dt><dt>10.3. <a href="NetworkBrowsing.html#brsex2">Browse Subnet Example 3</a></dt><dt>10.4. <a href="NetworkBrowsing.html#brsex3">Browse Subnet Example 4</a></dt><dt>11.1. <a href="passdb.html#policycontrols">NT4 Domain v's Samba Policy Controls</a></dt><dt>11.2. <a href="passdb.html#accountflags">Samba SAM Account Control Block Flags</a></dt><dt>11.3. <a href="passdb.html#attribobjclPartA">Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</a></dt><dt>11.4. <a href="passdb.html#attribobjclPartB">Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</a></dt><dt>11.5. <a href="passdb.html#ldappwsync">Possible ldap passwd sync Values</a></dt><dt>12.1. <a href="groupmapping.html#WKURIDS">Well-Known User Default RIDs</a></dt><dt>15.1. <a href="rights.html#rp-privs">Current Privilege Capabilities</a></dt><dt>16.1. <a href="AccessControls.html#TOSH-Accesstbl">Managing Directories with UNIX and Windows</a></dt><dt>16.2. <a href="AccessControls.html#ugbc">User- and Group-Based Controls</a></dt><dt>16.3. <a href="AccessControls.html#fdpbc">File and Directory Permission-Based Controls</a></dt><dt>16.4. <a href="AccessControls.html#mcoc">Other Controls</a></dt><dt>16.5. <a href="AccessControls.html#fdsacls">How Windows File ACLs Map to UNIX POSIX File ACLs</a></dt><dt>21.1. <a href="classicalprinting.html#printOptions">Default Printing Settings</a></dt><dt>22.1. <a href="CUPS-printing.html#cups-ppds">PPDs Shipped with CUPS</a></dt><dt>23.1. <a href="VFS.html#xtdaudit">Extended Auditing Log Information</a></dt><dt>27.1. <a href="ProfileMgmt.html#ProfileLocs">User Shell Folder Registry Keys Default Values</a></dt><dt>27.2. <a href="ProfileMgmt.html#regkeys">Defaults of Profile Settings Registry Keys</a></dt><dt>27.3. <a href="ProfileMgmt.html#defregpthkeys">Defaults of Default User Profile Paths Registry Keys</a></dt><dt>28.1. <a href="pam.html#smbpassoptions">Options recognized by pam_smbpass</a></dt><dt>29.1. <a href="integrate-ms-networks.html#uniqnetbiosnames">Unique NetBIOS Names</a></dt><dt>29.2. <a href="integrate-ms-networks.html#netbiosnamesgrp">Group Names</a></dt><dt>30.1. <a href="unicode.html#japancharsets">Japanese Character Sets in Samba-2.2 and Samba-3</a></dt><dt>35.1. <a href="upgrading-to-3.0.html#oldtdbfiledesc">Samba-2.2.x TDB File Descriptions</a></dt><dt>36.1. <a href="NT4Migration.html#majtypes">The Three Major Site Types</a></dt><dt>36.2. <a href="NT4Migration.html#natconchoices">Nature of the Conversion Choices</a></dt><dt>40.1. <a href="bugreport.html#dbgclass">Debuggable Functions</a></dt><dt>41.1. <a href="tdb.html#TOSH-TDB">Samba's Trivial Database Files</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>1.1. <a href="install.html#smbconfminimal">A minimal smb.conf</a></dt><dt>1.2. <a href="install.html#simple-example">Another simple smb.conf File</a></dt><dt>2.1. <a href="FastStart.html#anon-example">Anonymous Read-Only Server Configuration</a></dt><dt>2.2. <a href="FastStart.html#anon-rw">Modified Anonymous Read-Write smb.conf</a></dt><dt>2.3. <a href="FastStart.html#anon-print">Anonymous Print Server smb.conf</a></dt><dt>2.4. <a href="FastStart.html#OfficeServer">Secure Office Server smb.conf</a></dt><dt>2.5. <a href="FastStart.html#fast-member-server">Member Server smb.conf (Globals)</a></dt><dt>2.6. <a href="FastStart.html#fast-memberserver-shares">Member Server smb.conf (Shares and Services)</a></dt><dt>2.7. <a href="FastStart.html#fast-engoffice-global">Engineering Office smb.conf (globals)</a></dt><dt>2.8. <a href="FastStart.html#fast-engoffice-shares">Engineering Office smb.conf (shares and services)</a></dt><dt>2.9. <a href="FastStart.html#fast-ldap">LDAP backend smb.conf for PDC</a></dt><dt>2.10. <a href="FastStart.html#fast-bdc">Remote LDAP BDC smb.conf</a></dt><dt>4.1. <a href="samba-pdc.html#pdc-example">smb.conf for being a PDC</a></dt><dt>4.2. <a href="samba-pdc.html#PDC-config">smb.conf for being a PDC</a></dt><dt>5.1. <a href="samba-bdc.html#minimalPDC">Minimal smb.conf for a PDC in Use with a BDC  LDAP Server on PDC</a></dt><dt>5.2. <a href="samba-bdc.html#mulitldapcfg">Multiple LDAP Servers in smb.conf</a></dt><dt>5.3. <a href="samba-bdc.html#minim-bdc">Minimal Setup for Being a BDC</a></dt><dt>7.1. <a href="StandAloneServer.html#simplynice">smb.conf for Reference Documentation Server</a></dt><dt>7.2. <a href="StandAloneServer.html#AnonPtrSvr">smb.conf for Anonymous Printing</a></dt><dt>10.1. <a href="NetworkBrowsing.html#dmbexample">Domain Master Browser smb.conf</a></dt><dt>10.2. <a href="NetworkBrowsing.html#lmbexample">Local master browser smb.conf</a></dt><dt>10.3. <a href="NetworkBrowsing.html#nombexample">smb.conf for Not Being a Master Browser</a></dt><dt>10.4. <a href="NetworkBrowsing.html#remsmb">Local Master Browser smb.conf</a></dt><dt>10.5. <a href="NetworkBrowsing.html#xremmb">smb.conf for Not Being a master browser</a></dt><dt>11.1. <a href="passdb.html#idmapbackendexample">Example Configuration with the LDAP idmap Backend</a></dt><dt>11.2. <a href="passdb.html#confldapex">Configuration with LDAP</a></dt><dt>12.1. <a href="groupmapping.html#smbgrpadd.sh">smbgrpadd.sh</a></dt><dt>12.2. <a href="groupmapping.html#smbgrpadd">Configuration of smb.conf for the add group Script</a></dt><dt>12.3. <a href="groupmapping.html#set-group-map">Script to Set Group Mapping</a></dt><dt>13.1. <a href="NetCommand.html#autopoweruserscript">Script to Auto-add Domain Users to Workstation Power Users Group</a></dt><dt>13.2. <a href="NetCommand.html#magicnetlogon">A Magic Netlogon Share</a></dt><dt>14.1. <a href="idmapper.html#idmapnt4dms">NT4 Domain Member Server smb.conf</a></dt><dt>14.2. <a href="idmapper.html#idmapadsdms">ADS Domain Member Server smb.conf</a></dt><dt>14.3. <a href="idmapper.html#idmapadsridDMS">ADS Domain Member smb.conf using idmap_rid</a></dt><dt>14.4. <a href="idmapper.html#idmapldapDMS">ADS Domain Member Server using LDAP</a></dt><dt>14.5. <a href="idmapper.html#idmaprfc2307">ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</a></dt><dt>16.1. <a href="AccessControls.html#access2">Example File</a></dt><dt>17.1. <a href="locking.html#far1">Share with Some Files Oplocked</a></dt><dt>17.2. <a href="locking.html#far3">Configuration with Oplock Break Contention Limit</a></dt><dt>20.1. <a href="msdfs.html#dfscfg">smb.conf with DFS Configured</a></dt><dt>21.1. <a href="classicalprinting.html#simpleprc">Simple Configuration with BSD Printing</a></dt><dt>21.2. <a href="classicalprinting.html#extbsdpr">Extended BSD Printing Configuration</a></dt><dt>21.3. <a href="classicalprinting.html#prtdollar">[print$] Example</a></dt><dt>22.1. <a href="CUPS-printing.html#cups-exam-simple">Simplest Printing-Related smb.conf</a></dt><dt>22.2. <a href="CUPS-printing.html#overridesettings">Overriding Global CUPS Settings for One Printer</a></dt><dt>22.3. <a href="CUPS-printing.html#cupsadd-ex">smb.conf for cupsaddsmb Usage</a></dt><dt>23.1. <a href="VFS.html#vfsrecyc">smb.conf with VFS modules</a></dt><dt>23.2. <a href="VFS.html#multimodule">smb.conf with multiple VFS modules</a></dt><dt>23.3. <a href="VFS.html#vfsshadow">Share With shadow_copy VFS</a></dt><dt>24.1. <a href="winbind.html#winbindcfg">smb.conf for Winbind Setup</a></dt><dt>25.1. <a href="AdvancedNetworkManagement.html#Tpees">Script to Enforce Single Resource Logon</a></dt><dt>30.1. <a href="unicode.html#vfscap-intl">VFS CAP</a></dt><dt>34.1. <a href="cfgsmarts.html#elastic">Elastic smb.conf File</a></dt><dt>34.2. <a href="cfgsmarts.html#cdserver">CDROM Server smb-cdserver.conf file</a></dt><dt>34.3. <a href="cfgsmarts.html#mastersmbc">Master smb.conf File Global Section</a></dt><dt>34.4. <a href="cfgsmarts.html#merlinsmbc">MERLIN smb-merlin.conf File Share Section</a></dt><dt>34.5. <a href="cfgsmarts.html#sauronsmbc">SAURON smb-sauron.conf File Share Section</a></dt><dt>38.1. <a href="diagnosis.html#tmpshare">smb.conf with [tmp] Share</a></dt><dt>38.2. <a href="diagnosis.html#modif1">Configuration for Allowing Connections Only from a Certain Subnet</a></dt><dt>38.3. <a href="diagnosis.html#modif2">Configuration for Allowing Connections from a Certain Subnet and localhost</a></dt><dt>44.1. <a href="Other-Clients.html#minimalprofile">Minimal Profile Share</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�About the Cover Artwork</td></tr></table></div></body></html>
+  </a></span></dt></dl></dd><dt><span class="glossary"><a href="go01.html">Glossary</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>4.1. <a href="samba-pdc.html#domain-example">An Example Domain.</a></dt><dt>8.1. <a href="ClientConfig.html#WXPP002">Network Bridge Configuration.</a></dt><dt>8.2. <a href="ClientConfig.html#WXPP003">Internet Protocol (TCP/IP) Properties.</a></dt><dt>8.3. <a href="ClientConfig.html#WXPP005">Advanced Network Settings</a></dt><dt>8.4. <a href="ClientConfig.html#WXPP014">DNS Configuration.</a></dt><dt>8.5. <a href="ClientConfig.html#WXPP009">WINS Configuration</a></dt><dt>8.6. <a href="ClientConfig.html#w2kp001">Local Area Connection Properties.</a></dt><dt>8.7. <a href="ClientConfig.html#w2kp002">Internet Protocol (TCP/IP) Properties.</a></dt><dt>8.8. <a href="ClientConfig.html#w2kp003">Advanced Network Settings.</a></dt><dt>8.9. <a href="ClientConfig.html#w2kp004">DNS Configuration.</a></dt><dt>8.10. <a href="ClientConfig.html#w2kp005">WINS Configuration.</a></dt><dt>8.11. <a href="ClientConfig.html#WME001">The Windows Me Network Configuration Panel.</a></dt><dt>8.12. <a href="ClientConfig.html#WME002">IP Address.</a></dt><dt>8.13. <a href="ClientConfig.html#WME005">DNS Configuration.</a></dt><dt>8.14. <a href="ClientConfig.html#WME003">WINS Configuration.</a></dt><dt>8.15. <a href="ClientConfig.html#wxpp001">The General Panel.</a></dt><dt>8.16. <a href="ClientConfig.html#wxpp004">The Computer Name Panel.</a></dt><dt>8.17. <a href="ClientConfig.html#wxpp006">The Computer Name Changes Panel.</a></dt><dt>8.18. <a href="ClientConfig.html#wxpp007">The Computer Name Changes Panel  Domain MIDEARTH.</a></dt><dt>8.19. <a href="ClientConfig.html#wxpp008">Computer Name Changes  Username and Password Panel.</a></dt><dt>8.20. <a href="ClientConfig.html#WME009">The Network Panel.</a></dt><dt>8.21. <a href="ClientConfig.html#WME010">Client for Microsoft Networks Properties Panel.</a></dt><dt>8.22. <a href="ClientConfig.html#WME013">Identification Panel.</a></dt><dt>8.23. <a href="ClientConfig.html#WME014">Access Control Panel.</a></dt><dt>10.1. <a href="NetworkBrowsing.html#browsing1">Cross-Subnet Browsing Example.</a></dt><dt>11.1. <a href="passdb.html#idmap-sid2uid">IDMAP: Resolution of SIDs to UIDs.</a></dt><dt>11.2. <a href="passdb.html#idmap-uid2sid">IDMAP: Resolution of UIDs to SIDs.</a></dt><dt>12.1. <a href="groupmapping.html#idmap-sid2gid">IDMAP: Group SID-to-GID Resolution.</a></dt><dt>12.2. <a href="groupmapping.html#idmap-gid2sid">IDMAP: GID Resolution to Matching SID.</a></dt><dt>12.3. <a href="groupmapping.html#idmap-store-gid2sid">IDMAP Storing Group Mappings.</a></dt><dt>16.1. <a href="AccessControls.html#access1">Overview of UNIX permissions field.</a></dt><dt>19.1. <a href="InterdomainTrusts.html#trusts1">Trusts overview.</a></dt><dt>22.1. <a href="CUPS-printing.html#1small">Windows Printing to a Local Printer.</a></dt><dt>22.2. <a href="CUPS-printing.html#2small">Printing to a PostScript Printer.</a></dt><dt>22.3. <a href="CUPS-printing.html#3small">Ghostscript as a RIP for Non-PostScript Printers.</a></dt><dt>22.4. <a href="CUPS-printing.html#4small">Prefiltering in CUPS to Form PostScript.</a></dt><dt>22.5. <a href="CUPS-printing.html#5small">Adding Device-Specific Print Options.</a></dt><dt>22.6. <a href="CUPS-printing.html#cups-raster">PostScript to Intermediate Raster Format.</a></dt><dt>22.7. <a href="CUPS-printing.html#cups-raster2">CUPS-Raster Production Using Ghostscript.</a></dt><dt>22.8. <a href="CUPS-printing.html#small8">Image Format to CUPS-Raster Format Conversion.</a></dt><dt>22.9. <a href="CUPS-printing.html#small9">Raster to Printer-Specific Formats.</a></dt><dt>22.10. <a href="CUPS-printing.html#cupsomatic-dia">cupsomatic/foomatic Processing Versus Native CUPS.</a></dt><dt>22.11. <a href="CUPS-printing.html#pdftosocket">PDF to Socket Chain.</a></dt><dt>22.12. <a href="CUPS-printing.html#pdftoepsonusb">PDF to USB Chain.</a></dt><dt>22.13. <a href="CUPS-printing.html#small11">Print Driver Execution on the Client.</a></dt><dt>22.14. <a href="CUPS-printing.html#small12">Print Driver Execution on the Server.</a></dt><dt>22.15. <a href="CUPS-printing.html#13small">Printing via CUPS/Samba Server.</a></dt><dt>22.16. <a href="CUPS-printing.html#small14">cupsaddsmb Flowchart.</a></dt><dt>22.17. <a href="CUPS-printing.html#cups1">Filtering Chain 1.</a></dt><dt>22.18. <a href="CUPS-printing.html#cups2">Filtering Chain with cupsomatic</a></dt><dt>22.19. <a href="CUPS-printing.html#a_small">CUPS Printing Overview.</a></dt><dt>24.1. <a href="winbind.html#winbind_idmap">Winbind Idmap</a></dt><dt>39.1. <a href="problems.html#ethereal1">Starting a Capture.</a></dt><dt>39.2. <a href="problems.html#ethereal2">Main Ethereal Data Window.</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="install.html#tdbpermfiledesc">Persistent TDB File Descriptions</a></dt><dt>1.2. <a href="install.html#tdbtempfiledesc">Temporary TDB File Descriptions</a></dt><dt>5.1. <a href="samba-bdc.html#pdc-bdc-table">Domain Backend Account Distribution Options</a></dt><dt>6.1. <a href="domain-member.html#assumptions">Assumptions</a></dt><dt>9.1. <a href="ChangeNotes.html#TOSH-domgroups">Essential Domain Group Mappings</a></dt><dt>10.1. <a href="NetworkBrowsing.html#browsubnet">Browse Subnet Example 1</a></dt><dt>10.2. <a href="NetworkBrowsing.html#brsbex">Browse Subnet Example 2</a></dt><dt>10.3. <a href="NetworkBrowsing.html#brsex2">Browse Subnet Example 3</a></dt><dt>10.4. <a href="NetworkBrowsing.html#brsex3">Browse Subnet Example 4</a></dt><dt>11.1. <a href="passdb.html#policycontrols">NT4 Domain v's Samba Policy Controls</a></dt><dt>11.2. <a href="passdb.html#accountflags">Samba SAM Account Control Block Flags</a></dt><dt>11.3. <a href="passdb.html#attribobjclPartA">Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</a></dt><dt>11.4. <a href="passdb.html#attribobjclPartB">Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</a></dt><dt>11.5. <a href="passdb.html#ldappwsync">Possible ldap passwd sync Values</a></dt><dt>12.1. <a href="groupmapping.html#WKURIDS">Well-Known User Default RIDs</a></dt><dt>15.1. <a href="rights.html#rp-privs">Current Privilege Capabilities</a></dt><dt>16.1. <a href="AccessControls.html#TOSH-Accesstbl">Managing Directories with UNIX and Windows</a></dt><dt>16.2. <a href="AccessControls.html#ugbc">User- and Group-Based Controls</a></dt><dt>16.3. <a href="AccessControls.html#fdpbc">File and Directory Permission-Based Controls</a></dt><dt>16.4. <a href="AccessControls.html#mcoc">Other Controls</a></dt><dt>16.5. <a href="AccessControls.html#fdsacls">How Windows File ACLs Map to UNIX POSIX File ACLs</a></dt><dt>21.1. <a href="classicalprinting.html#printOptions">Default Printing Settings</a></dt><dt>22.1. <a href="CUPS-printing.html#cups-ppds">PPDs Shipped with CUPS</a></dt><dt>23.1. <a href="VFS.html#xtdaudit">Extended Auditing Log Information</a></dt><dt>27.1. <a href="ProfileMgmt.html#ProfileLocs">User Shell Folder Registry Keys Default Values</a></dt><dt>27.2. <a href="ProfileMgmt.html#regkeys">Defaults of Profile Settings Registry Keys</a></dt><dt>27.3. <a href="ProfileMgmt.html#defregpthkeys">Defaults of Default User Profile Paths Registry Keys</a></dt><dt>28.1. <a href="pam.html#smbpassoptions">Options recognized by pam_smbpass</a></dt><dt>29.1. <a href="integrate-ms-networks.html#uniqnetbiosnames">Unique NetBIOS Names</a></dt><dt>29.2. <a href="integrate-ms-networks.html#netbiosnamesgrp">Group Names</a></dt><dt>30.1. <a href="unicode.html#japancharsets">Japanese Character Sets in Samba-2.2 and Samba-3</a></dt><dt>35.1. <a href="upgrading-to-3.0.html#oldtdbfiledesc">Samba-2.2.x TDB File Descriptions</a></dt><dt>36.1. <a href="NT4Migration.html#majtypes">The Three Major Site Types</a></dt><dt>36.2. <a href="NT4Migration.html#natconchoices">Nature of the Conversion Choices</a></dt><dt>40.1. <a href="bugreport.html#dbgclass">Debuggable Functions</a></dt><dt>41.1. <a href="tdb.html#TOSH-TDB">Samba's Trivial Database Files</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>1.1. <a href="install.html#smbconfminimal">A minimal smb.conf</a></dt><dt>1.2. <a href="install.html#simple-example">Another simple smb.conf File</a></dt><dt>2.1. <a href="FastStart.html#anon-example">Anonymous Read-Only Server Configuration</a></dt><dt>2.2. <a href="FastStart.html#anon-rw">Modified Anonymous Read-Write smb.conf</a></dt><dt>2.3. <a href="FastStart.html#anon-print">Anonymous Print Server smb.conf</a></dt><dt>2.4. <a href="FastStart.html#OfficeServer">Secure Office Server smb.conf</a></dt><dt>2.5. <a href="FastStart.html#fast-member-server">Member Server smb.conf (Globals)</a></dt><dt>2.6. <a href="FastStart.html#fast-memberserver-shares">Member Server smb.conf (Shares and Services)</a></dt><dt>2.7. <a href="FastStart.html#fast-engoffice-global">Engineering Office smb.conf (globals)</a></dt><dt>2.8. <a href="FastStart.html#fast-engoffice-shares">Engineering Office smb.conf (shares and services)</a></dt><dt>2.9. <a href="FastStart.html#fast-ldap">LDAP backend smb.conf for PDC</a></dt><dt>2.10. <a href="FastStart.html#fast-bdc">Remote LDAP BDC smb.conf</a></dt><dt>4.1. <a href="samba-pdc.html#pdc-example">smb.conf for being a PDC</a></dt><dt>4.2. <a href="samba-pdc.html#PDC-config">smb.conf for being a PDC</a></dt><dt>5.1. <a href="samba-bdc.html#minimalPDC">Minimal smb.conf for a PDC in Use with a BDC  LDAP Server on PDC</a></dt><dt>5.2. <a href="samba-bdc.html#mulitldapcfg">Multiple LDAP Servers in smb.conf</a></dt><dt>5.3. <a href="samba-bdc.html#minim-bdc">Minimal Setup for Being a BDC</a></dt><dt>7.1. <a href="StandAloneServer.html#simplynice">smb.conf for Reference Documentation Server</a></dt><dt>7.2. <a href="StandAloneServer.html#AnonPtrSvr">smb.conf for Anonymous Printing</a></dt><dt>10.1. <a href="NetworkBrowsing.html#dmbexample">Domain Master Browser smb.conf</a></dt><dt>10.2. <a href="NetworkBrowsing.html#lmbexample">Local master browser smb.conf</a></dt><dt>10.3. <a href="NetworkBrowsing.html#nombexample">smb.conf for Not Being a Master Browser</a></dt><dt>10.4. <a href="NetworkBrowsing.html#remsmb">Local Master Browser smb.conf</a></dt><dt>10.5. <a href="NetworkBrowsing.html#xremmb">smb.conf for Not Being a master browser</a></dt><dt>11.1. <a href="passdb.html#idmapbackendexample">Example Configuration with the LDAP idmap Backend</a></dt><dt>11.2. <a href="passdb.html#confldapex">Configuration with LDAP</a></dt><dt>12.1. <a href="groupmapping.html#smbgrpadd.sh">smbgrpadd.sh</a></dt><dt>12.2. <a href="groupmapping.html#smbgrpadd">Configuration of smb.conf for the add group Script</a></dt><dt>12.3. <a href="groupmapping.html#set-group-map">Script to Set Group Mapping</a></dt><dt>13.1. <a href="NetCommand.html#autopoweruserscript">Script to Auto-add Domain Users to Workstation Power Users Group</a></dt><dt>13.2. <a href="NetCommand.html#magicnetlogon">A Magic Netlogon Share</a></dt><dt>14.1. <a href="idmapper.html#idmapnt4dms">NT4 Domain Member Server smb.conf</a></dt><dt>14.2. <a href="idmapper.html#idmapadsdms">ADS Domain Member Server smb.conf</a></dt><dt>14.3. <a href="idmapper.html#idmapadsridDMS">ADS Domain Member smb.conf using idmap_rid</a></dt><dt>14.4. <a href="idmapper.html#idmapldapDMS">ADS Domain Member Server using LDAP</a></dt><dt>14.5. <a href="idmapper.html#idmaprfc2307">ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</a></dt><dt>16.1. <a href="AccessControls.html#access2">Example File</a></dt><dt>17.1. <a href="locking.html#far1">Share with Some Files Oplocked</a></dt><dt>17.2. <a href="locking.html#far3">Configuration with Oplock Break Contention Limit</a></dt><dt>20.1. <a href="msdfs.html#dfscfg">smb.conf with DFS Configured</a></dt><dt>21.1. <a href="classicalprinting.html#simpleprc">Simple Configuration with BSD Printing</a></dt><dt>21.2. <a href="classicalprinting.html#extbsdpr">Extended BSD Printing Configuration</a></dt><dt>21.3. <a href="classicalprinting.html#prtdollar">[print$] Example</a></dt><dt>22.1. <a href="CUPS-printing.html#cups-exam-simple">Simplest Printing-Related smb.conf</a></dt><dt>22.2. <a href="CUPS-printing.html#overridesettings">Overriding Global CUPS Settings for One Printer</a></dt><dt>22.3. <a href="CUPS-printing.html#cupsadd-ex">smb.conf for cupsaddsmb Usage</a></dt><dt>23.1. <a href="VFS.html#vfsrecyc">smb.conf with VFS modules</a></dt><dt>23.2. <a href="VFS.html#multimodule">smb.conf with multiple VFS modules</a></dt><dt>23.3. <a href="VFS.html#vfsshadow">Share With shadow_copy VFS</a></dt><dt>24.1. <a href="winbind.html#winbindcfg">smb.conf for Winbind Setup</a></dt><dt>25.1. <a href="AdvancedNetworkManagement.html#Tpees">Script to Enforce Single Resource Logon</a></dt><dt>30.1. <a href="unicode.html#vfscap-intl">VFS CAP</a></dt><dt>34.1. <a href="cfgsmarts.html#elastic">Elastic smb.conf File</a></dt><dt>34.2. <a href="cfgsmarts.html#cdserver">CDROM Server smb-cdserver.conf file</a></dt><dt>34.3. <a href="cfgsmarts.html#mastersmbc">Master smb.conf File Global Section</a></dt><dt>34.4. <a href="cfgsmarts.html#merlinsmbc">MERLIN smb-merlin.conf File Share Section</a></dt><dt>34.5. <a href="cfgsmarts.html#sauronsmbc">SAURON smb-sauron.conf File Share Section</a></dt><dt>38.1. <a href="diagnosis.html#tmpshare">smb.conf with [tmp] Share</a></dt><dt>38.2. <a href="diagnosis.html#modif1">Configuration for Allowing Connections Only from a Certain Subnet</a></dt><dt>38.3. <a href="diagnosis.html#modif2">Configuration for Allowing Connections from a Certain Subnet and localhost</a></dt><dt>44.1. <a href="Other-Clients.html#minimalprofile">Minimal Profile Share</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�About the Cover Artwork</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/install.html b/docs/htmldocs/Samba3-HOWTO/install.html
index e7a0ba8102..facd11c95c 100644
--- a/docs/htmldocs/Samba3-HOWTO/install.html
+++ b/docs/htmldocs/Samba3-HOWTO/install.html
@@ -1,32 +1,32 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�How to Install and Test SAMBA</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="introduction.html" title="Part�I.�General Installation"><link rel="prev" href="introduction.html" title="Part�I.�General Installation"><link rel="next" href="FastStart.html" title="Chapter�2.�Fast Start: Cure for Impatience"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�How to Install and Test SAMBA</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="introduction.html">Prev</a>�</td><th width="60%" align="center">Part�I.�General Installation</th><td width="20%" align="right">�<a accesskey="n" href="FastStart.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter�1.�How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Karl</span> <span class="orgname">Samba Team</span> <span class="surname">Auer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kauer@biplane.com.au">kauer@biplane.com.au</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="install.html#id2551914">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551954">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551996">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552898">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553078">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553482">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553540">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553592">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553683">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553764">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553805">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553838">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553848">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553935">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553968">The network name cannot be found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551914"></a>Obtaining and Installing Samba</h2></div></div></div><p>
-	<a class="indexterm" name="id2551922"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�How to Install and Test SAMBA</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="introduction.html" title="Part�I.�General Installation"><link rel="prev" href="introduction.html" title="Part�I.�General Installation"><link rel="next" href="FastStart.html" title="Chapter�2.�Fast Start: Cure for Impatience"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�How to Install and Test SAMBA</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="introduction.html">Prev</a>�</td><th width="60%" align="center">Part�I.�General Installation</th><td width="20%" align="right">�<a accesskey="n" href="FastStart.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter�1.�How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Karl</span> <span class="orgname">Samba Team</span> <span class="surname">Auer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:kauer@biplane.com.au">kauer@biplane.com.au</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="install.html#id2551909">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551950">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551991">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552892">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553073">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553476">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553534">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553587">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553678">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553759">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553800">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553832">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553842">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553930">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553962">The network name cannot be found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551909"></a>Obtaining and Installing Samba</h2></div></div></div><p>
+	<a class="indexterm" name="id2551917"></a>
 	Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some
 	packages available at <a class="ulink" href="http://samba.org/" target="_top">the Samba home page</a>. Refer to the manual of your
 	operating system for details on installing packages for your specific operating system.
 	</p><p>
-	<a class="indexterm" name="id2551940"></a>
+	<a class="indexterm" name="id2551935"></a>
 	If you need to compile Samba from source, check <a class="link" href="compiling.html" title="Chapter�42.�How to Compile Samba">How to Compile Samba</a>.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551954"></a>Configuring Samba (smb.conf)</h2></div></div></div><p>
-	<a class="indexterm" name="id2551962"></a>
-	<a class="indexterm" name="id2551968"></a>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2551950"></a>Configuring Samba (smb.conf)</h2></div></div></div><p>
+	<a class="indexterm" name="id2551957"></a>
+	<a class="indexterm" name="id2551963"></a>
 	Samba's configuration is stored in the <code class="filename">smb.conf</code> file, which usually resides in
 	<code class="filename">/etc/samba/smb.conf</code> or <code class="filename">/usr/local/samba/lib/smb.conf</code>. 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="id2551996"></a>Configuration File Syntax</h3></div></div></div><p>
-	<a class="indexterm" name="id2552004"></a>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551991"></a>Configuration File Syntax</h3></div></div></div><p>
+	<a class="indexterm" name="id2551999"></a>
 	The <code class="filename">smb.conf</code> file uses the same syntax as the various old <code class="filename">.ini</code> files in Windows
 	3.1: Each file consists of various sections, which are started by putting the section name between brackets
 	(<code class="literal">[]</code>) on a new line. Each contains zero or more key/value pairs separated by an equality
 	sign (<code class="literal">=</code>). The file is just a plaintext file, so you can open and edit it with your favorite
 	editing tool.
 	</p><p>
-	<a class="indexterm" name="id2552041"></a>
-	<a class="indexterm" name="id2552047"></a>
-	<a class="indexterm" name="id2552055"></a>
-	<a class="indexterm" name="id2552062"></a>
-	<a class="indexterm" name="id2552068"></a>
-	<a class="indexterm" name="id2552076"></a>
+	<a class="indexterm" name="id2552036"></a>
+	<a class="indexterm" name="id2552042"></a>
+	<a class="indexterm" name="id2552051"></a>
+	<a class="indexterm" name="id2552057"></a>
+	<a class="indexterm" name="id2552063"></a>
+	<a class="indexterm" name="id2552072"></a>
 	Each section in the <code class="filename">smb.conf</code> file represents either a share or a meta-service on the Samba server. The
 	section <code class="literal">[global]</code> is special, since it contains settings that apply to the whole Samba
 	server.  Samba supports a number of meta-services, each of which serves its own purpose. For example, the
@@ -35,12 +35,12 @@
 	and that specifies the location of the intermediate spool directory into which print jobs are received
 	from Windows clients prior to being dispatched to the UNIX/Linux print spooler.
 	</p><p>
-<a class="indexterm" name="id2552119"></a>
-<a class="indexterm" name="id2552126"></a>
-<a class="indexterm" name="id2552132"></a>
-<a class="indexterm" name="id2552138"></a>
-<a class="indexterm" name="id2552144"></a>
-<a class="indexterm" name="id2552151"></a>
+<a class="indexterm" name="id2552115"></a>
+<a class="indexterm" name="id2552121"></a>
+<a class="indexterm" name="id2552127"></a>
+<a class="indexterm" name="id2552133"></a>
+<a class="indexterm" name="id2552140"></a>
+<a class="indexterm" name="id2552146"></a>
 	The <code class="literal">printers</code> meta-service will cause every printer that is either specified in a
 	<code class="literal">printcap</code> file, via the <code class="literal">lpstat</code>,  or via the CUPS API, to be
 	published as a shared print queue. The <code class="literal">printers</code> stanza in the <code class="filename">smb.conf</code> file can
@@ -49,20 +49,20 @@
 	available as Windows print queues. If a <code class="literal">comment</code> parameter is specified, the value
 	of it will be displayed as part of the printer name in Windows Explorer browse lists.
 	</p><p>
-	<a class="indexterm" name="id2552201"></a>
+	<a class="indexterm" name="id2552196"></a>
 	Each section of the <code class="filename">smb.conf</code> file that specifies a share, or a meta-service, is called a stanza.
 	The <code class="literal">global</code> stanza specifies settings that affect all the other stanzas in the
 	<code class="filename">smb.conf</code> file. Configuration parameters are documented in the <code class="filename">smb.conf</code> man page. Some parameters
 	can be used only in the <code class="literal">global</code> stanza, some only in share or meta-service stanzas,
 	and some can be used globally or just within a share or meta-service stanza.
 	</p><p>
-	<a class="indexterm" name="id2552243"></a>
+	<a class="indexterm" name="id2552238"></a>
 	<a class="link" href="install.html#smbconfminimal" title="Example�1.1.�A minimal smb.conf">A minimal smb.conf</a> contains a very minimal <code class="filename">smb.conf</code>.
-	<a class="indexterm" name="id2552262"></a>
-	</p><div class="example"><a name="smbconfminimal"></a><p class="title"><b>Example�1.1.�A minimal smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552290"></a><em class="parameter"><code>workgroup = WKG</code></em></td></tr><tr><td><a class="indexterm" name="id2552301"></a><em class="parameter"><code>netbios name = MYNAME</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share1]</code></em></td></tr><tr><td><a class="indexterm" name="id2552320"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share2]</code></em></td></tr><tr><td><a class="indexterm" name="id2552338"></a><em class="parameter"><code>path = /my_shared_folder</code></em></td></tr><tr><td><a class="indexterm" name="id2552349"></a><em class="parameter"><code>comment = Some random files</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="tdbdocs"></a>TDB Database File Information</h3></div></div></div><p>
+	<a class="indexterm" name="id2552257"></a>
+	</p><div class="example"><a name="smbconfminimal"></a><p class="title"><b>Example�1.1.�A minimal smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2552286"></a><em class="parameter"><code>workgroup = WKG</code></em></td></tr><tr><td><a class="indexterm" name="id2552296"></a><em class="parameter"><code>netbios name = MYNAME</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share1]</code></em></td></tr><tr><td><a class="indexterm" name="id2552315"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share2]</code></em></td></tr><tr><td><a class="indexterm" name="id2552334"></a><em class="parameter"><code>path = /my_shared_folder</code></em></td></tr><tr><td><a class="indexterm" name="id2552344"></a><em class="parameter"><code>comment = Some random files</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="tdbdocs"></a>TDB Database File Information</h3></div></div></div><p>
 	This section contains brief descriptions of the databases that are used by Samba-3.
 	</p><p>
-<a class="indexterm" name="id2552376"></a>
+<a class="indexterm" name="id2552371"></a>
 	The directory in which Samba stores the tdb files is determined by compile-time directives. Samba-3 stores
 	tdb files in two locations. The best way to determine these locations is to execute the following
 	command:
@@ -80,7 +80,7 @@
 	Therefore the remaining control files will, in the example shown, be stored in the
 	<code class="filename">/var/lib/samba</code> directory.
 	</p><p>
-<a class="indexterm" name="id2552428"></a>
+<a class="indexterm" name="id2552423"></a>
 	The persistent tdb files are described in <a class="link" href="install.html#tdbpermfiledesc" title="Table�1.1.�Persistent TDB File Descriptions">the Persistent TDB File
 	Descriptions table</a>. All persistent tdb files should be regularly backed up. Use the
 	<code class="literal">tdbbackup</code> utility to backup the tdb files. All persistent tdb files must be
@@ -92,7 +92,7 @@
 	</p><div class="table"><a name="tdbpermfiledesc"></a><p class="title"><b>Table�1.1.�Persistent TDB File Descriptions</b></p><div class="table-contents"><table summary="Persistent TDB File Descriptions" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Name</th><th align="justify">Description</th></tr></thead><tbody><tr><td align="left">account_policy</td><td align="justify"><p>Samba/NT account policy settings, includes password expiration settings.</p></td></tr><tr><td align="left">group_mapping</td><td align="justify"><p>Mapping table from Windows groups/SID to UNIX groups.</p></td></tr><tr><td align="left">ntdrivers</td><td align="justify"><p>Stores per-printer installed driver information.</p></td></tr><tr><td align="left">ntforms</td><td align="justify"><p>Stores per-printer installed forms information.</p></td></tr><tr><td align="left">ntprinters</td><td align="justify"><p>Stores the per-printer devmode configuration settings.</p></td></tr><tr><td align="left">passdb</td><td align="justify"><p>
 				Exists only when the tdbsam passwd backend is used. This file stores the
 				SambaSAMAccount information. Note: This file requires that user POSIX account information is
-				available from either the /etc/passwd file, or from an alternative system source.
+				availble from either the /etc/passwd file, or from an alternative system source.
 			</p></td></tr><tr><td align="left">registry</td><td align="justify"><p>
 				Read-only Samba database of a Windows registry skeleton that provides support for exporting 
 				various database tables via the winreg RPCs.
@@ -106,27 +106,27 @@
 				information so that clients that have temporarily disconnected can reconnect without
 				needing to renegotiate the connection setup process.
 			</p></td><td align="left">no</td></tr><tr><td align="left">sessionid</td><td align="justify"><p>Temporary cache for miscellaneous session information and for utmp handling.</p></td><td align="left">no</td></tr><tr><td align="left">unexpected</td><td align="justify"><p>Stores packets received for which no process is actively listening.</p></td><td align="left">no</td></tr><tr><td align="left">winbindd_cache</td><td align="justify"><p>Cache of Identity information received from an NT4 domain or from ADS. Includes user
-				lists, etc.</p></td><td align="left">yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552898"></a>Starting Samba</h3></div></div></div><p>
-	<a class="indexterm" name="id2552905"></a>
+				lists, etc.</p></td><td align="left">yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552892"></a>Starting Samba</h3></div></div></div><p>
+	<a class="indexterm" name="id2552900"></a>
 	Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
 	An example of a service is the Apache Web server for which the daemon is called <code class="literal">httpd</code>. In the case of Samba there
 	are three daemons, two of which are needed as a minimum.
 	</p><p>
 	The Samba server is made up of the following daemons:
 	</p><div class="variablelist"><dl><dt><span class="term">nmbd</span></dt><dd><p>
-			<a class="indexterm" name="id2552937"></a>
-			<a class="indexterm" name="id2552943"></a>
+			<a class="indexterm" name="id2552931"></a>
+			<a class="indexterm" name="id2552938"></a>
 			This daemon handles all name registration and resolution requests. It is the primary vehicle involved
 			in network browsing. It handles all UDP-based protocols. The <code class="literal">nmbd</code> daemon should
 			be the first command started as part of the Samba startup process.
 			</p></dd><dt><span class="term">smbd</span></dt><dd><p>
-			<a class="indexterm" name="id2552971"></a>
-			<a class="indexterm" name="id2552977"></a>
+			<a class="indexterm" name="id2552965"></a>
+			<a class="indexterm" name="id2552972"></a>
 			This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
 			manages local authentication. It should be started immediately following the startup of <code class="literal">nmbd</code>.
 			</p></dd><dt><span class="term">winbindd</span></dt><dd><p>
-			<a class="indexterm" name="id2553004"></a>
-			<a class="indexterm" name="id2553010"></a>
+			<a class="indexterm" name="id2552998"></a>
+			<a class="indexterm" name="id2553005"></a>
 			This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
 			Samba has trust relationships with another domain. The <code class="literal">winbindd</code> daemon will check the
 			<code class="filename">smb.conf</code> file for the presence of the <em class="parameter"><code>idmap uid</code></em> and <em class="parameter"><code>idmap gid</code></em>
@@ -134,36 +134,36 @@
 			for UID and GID allocation. If these parameters are not specified, <code class="literal">winbindd</code>
 			will start but it will not be able to allocate UIDs or GIDs.
 			</p></dd></dl></div><p>
-	<a class="indexterm" name="id2553062"></a>
+	<a class="indexterm" name="id2553057"></a>
 	When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
 	integration into the platform as a whole. Please refer to your operating system platform administration manuals for
 	specific information pertaining to correct management of Samba startup.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553078"></a>Example Configuration</h3></div></div></div><p>
-	<a class="indexterm" name="id2553086"></a>
-	<a class="indexterm" name="id2553092"></a>
-	<a class="indexterm" name="id2553098"></a>
-	<a class="indexterm" name="id2553105"></a>
-	<a class="indexterm" name="id2553111"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553073"></a>Example Configuration</h3></div></div></div><p>
+	<a class="indexterm" name="id2553080"></a>
+	<a class="indexterm" name="id2553087"></a>
+	<a class="indexterm" name="id2553093"></a>
+	<a class="indexterm" name="id2553099"></a>
+	<a class="indexterm" name="id2553106"></a>
 	There are sample configuration files in the examples subdirectory in the source code distribution tarball
 	package. It is suggested you read them carefully so you can see how the options go together in practice. See
 	the man page for all the options.  It might be worthwhile to start out with the
 	<code class="filename">smb.conf.default</code> configuration file and adapt it to your needs. It contains plenty of comments.
 	</p><p>
-	<a class="indexterm" name="id2553132"></a>
+	<a class="indexterm" name="id2553127"></a>
 	The simplest useful configuration file would contain something like that shown in
 	<a class="link" href="install.html#simple-example" title="Example�1.2.�Another simple smb.conf File">Another simple smb.conf File</a>.
-	<a class="indexterm" name="id2553148"></a>
-	</p><div class="example"><a name="simple-example"></a><p class="title"><b>Example�1.2.�Another simple smb.conf File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2553177"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2553196"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2553206"></a><em class="parameter"><code>read only = no</code></em></td></tr></table></div></div><br class="example-break"><p>
-	<a class="indexterm" name="id2553220"></a>
-	<a class="indexterm" name="id2553226"></a>
-	<a class="indexterm" name="id2553232"></a>
-	<a class="indexterm" name="id2553239"></a>
+	<a class="indexterm" name="id2553143"></a>
+	</p><div class="example"><a name="simple-example"></a><p class="title"><b>Example�1.2.�Another simple smb.conf File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2553172"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2553190"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2553201"></a><em class="parameter"><code>read only = no</code></em></td></tr></table></div></div><br class="example-break"><p>
+	<a class="indexterm" name="id2553214"></a>
+	<a class="indexterm" name="id2553221"></a>
+	<a class="indexterm" name="id2553227"></a>
+	<a class="indexterm" name="id2553233"></a>
 	This will allow connections by anyone with an account on the server, using either
 	their login name or <em class="parameter"><code>homes</code></em> as the service name.
 	(Note: The workgroup that Samba should appear in must also be set. The default
 	workgroup name is WORKGROUP.)
 	</p><p>
-	<a class="indexterm" name="id2553258"></a>
+	<a class="indexterm" name="id2553252"></a>
 	Make sure you put the <code class="filename">smb.conf</code> file in the correct place. Note, the correct location of this file
 	depends on how the binary files were built. You can discover the correct location by executing from
 	the directory that contains the <code class="literal">smbd</code> command file:
@@ -171,13 +171,13 @@
 <code class="prompt">root# </code> smbd -b | grep smb.conf
 </pre><p>
 	</p><p>
-	<a class="indexterm" name="id2553291"></a>
+	<a class="indexterm" name="id2553286"></a>
 	For more information about security settings for the <em class="parameter"><code>[homes]</code></em> share, please refer to 
 	<a class="link" href="securing-samba.html" title="Chapter�18.�Securing Samba">Securing Samba</a>.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553312"></a>Test Your Config File with <code class="literal">testparm</code></h4></div></div></div><p>
-	<a class="indexterm" name="id2553324"></a>
-	<a class="indexterm" name="id2553330"></a>
-	<a class="indexterm" name="id2553336"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2553307"></a>Test Your Config File with <code class="literal">testparm</code></h4></div></div></div><p>
+	<a class="indexterm" name="id2553318"></a>
+	<a class="indexterm" name="id2553325"></a>
+	<a class="indexterm" name="id2553331"></a>
 	It's important to validate the contents of the <code class="filename">smb.conf</code> file using the <span class="application">testparm</span> program.
 	If testparm runs correctly, it will list the loaded services. If not, it will give an error message.
 	Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command: 
@@ -189,10 +189,10 @@
 	</p><p>
 	Always run testparm again whenever the <code class="filename">smb.conf</code> file is changed!
 	</p><p>
-	<a class="indexterm" name="id2553385"></a>
-	<a class="indexterm" name="id2553391"></a>
-	<a class="indexterm" name="id2553397"></a>
-	<a class="indexterm" name="id2553403"></a>
+	<a class="indexterm" name="id2553379"></a>
+	<a class="indexterm" name="id2553386"></a>
+	<a class="indexterm" name="id2553392"></a>
+	<a class="indexterm" name="id2553398"></a>
 	The <code class="filename">smb.conf</code> file is constantly checked by the Samba daemons <code class="literal">smbd</code> and every instance of
 	itself that it spawns, <code class="literal">nmbd</code> and <code class="literal">winbindd</code>. It is good practice to
 	keep this file as small as possible. Many administrators prefer to document Samba configuration settings
@@ -205,8 +205,8 @@
 </pre><p>
 	This administrative method makes it possible to maintain detailed configuration change records while at
 	the same time keeping the working <code class="filename">smb.conf</code> file size to the minimum necessary.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553482"></a>SWAT</h3></div></div></div><p>
-	<a class="indexterm" name="id2553489"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553476"></a>SWAT</h3></div></div></div><p>
+	<a class="indexterm" name="id2553484"></a>
 	SWAT is a Web-based interface that can be used to facilitate the configuration of Samba.  SWAT might not
 	be available in the Samba package that shipped with your platform, but in a separate package. If you need to build SWAT please read the SWAT man page regarding compilation, installation, and
 	configuration of SWAT from the source code.
@@ -222,7 +222,7 @@
 	Please note that re-writing the configuration file using SWAT will
 	remove all comments!
 	More information about SWAT can be found in <a class="link" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool">The Samba Web Administration Tool</a>.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553540"></a>List Shares Available on the Server</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553534"></a>List Shares Available on the Server</h2></div></div></div><p>
 	To list shares that are available from the configured Samba server, execute the
 	following command:
 	</p><pre class="screen">
@@ -236,7 +236,7 @@
 	before it will list the shares. See the <code class="literal">smbclient</code> man page for details.
 	You can force it to list the shares without a password by adding the option
 	<code class="option">-N</code> to the command line. 
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553592"></a>Connect with a UNIX Client</h2></div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553587"></a>Connect with a UNIX Client</h2></div></div></div><p>
 	Enter the following command:
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>smbclient <em class="replaceable"><code> //yourhostname/aservice</code></em></code></strong>
@@ -245,7 +245,7 @@
 	file. Try your username if you just have a <em class="parameter"><code>[homes]</code></em> section in the <code class="filename">smb.conf</code> file.</p><p>Example: If the UNIX host is called <em class="replaceable"><code>bambi</code></em> and a valid login name
 	is <em class="replaceable"><code>fred</code></em>, you would type:</p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>smbclient //<em class="replaceable"><code>bambi</code></em>/<em class="replaceable"><code>fred</code></em></code></strong>
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553683"></a>Connect from a Remote SMB Client</h2></div></div></div><p>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553678"></a>Connect from a Remote SMB Client</h2></div></div></div><p>
 	Now that Samba is working correctly locally, you can try to access it from other clients. Within a few
 	minutes, the Samba host should be listed in the Network Neighborhood on all Windows clients of its subnet.
 	Try browsing the server from another client or "mounting" it.
@@ -266,7 +266,7 @@
 	be sent to the printer that owns the spoolservice that has been specified.
 	</p><p>
 </p><pre class="screen"><code class="prompt">C:\&gt; </code><strong class="userinput"><code>print filename</code></strong>
-</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553764"></a>What If Things Don't Work?</h3></div></div></div><p>
+</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553759"></a>What If Things Don't Work?</h3></div></div></div><p>
 	You might want to read <a class="link" href="diagnosis.html" title="Chapter�38.�The Samba Checklist">The Samba Checklist</a>.  If you are still
 	stuck, refer to <a class="link" href="problems.html" title="Chapter�39.�Analyzing and Solving Samba Problems">Analyzing and Solving Samba Problems</a>.  Samba has
 	been successfully installed at thousands of sites worldwide.  It is unlikely that your particular problem is
@@ -278,7 +278,7 @@
 	Simply choose from the first five chapters the network design that most closely matches site needs,
 	then follow the simple step-by-step procedure to deploy it. Later, when you have a working network
 	you may well want to refer back to this book for further insight into opportunities for improvement.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553805"></a>Still Stuck?</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553800"></a>Still Stuck?</h3></div></div></div><p>
 	The best advice under the stress of abject frustration is to cool down! That may be challenging
 	of itself, but while you are angry or annoyed your ability to seek out a solution is somewhat
 	undermined. A cool head clears the way to finding the answer you are looking for. Just remember,
@@ -287,9 +287,9 @@
 	</p><p>
 	Now that you have cooled down a bit, please refer to <a class="link" href="diagnosis.html" title="Chapter�38.�The Samba Checklist">the Samba Checklist</a>
 	for a process that can be followed to identify the cause of your problem.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553838"></a>Common Errors</h2></div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553832"></a>Common Errors</h2></div></div></div><p>
 The following questions and issues are raised repeatedly on the Samba mailing list.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553848"></a>Large Number of smbd Processes</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553842"></a>Large Number of smbd Processes</h3></div></div></div><p>
 	Samba consists of three core programs: <span class="application">nmbd</span>, <span class="application">smbd</span>, and <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, and <span class="application">winbindd</span> is the daemon that handles communication with domain controllers.
 	</p><p>
@@ -302,14 +302,14 @@ The following questions and issues are raised repeatedly on the Samba mailing li
 	</p><p>
 	<span class="application">winbindd</span> will run as one or two daemons, depending on whether or not it is being
 	run in <span class="emphasis"><em>split mode</em></span> (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="id2553935"></a>Error Message: open_oplock_ipc</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553930"></a>Error Message: open_oplock_ipc</h3></div></div></div><p>
 	An error message is observed in the log files when <span class="application">smbd</span> is started: &#8220;<span class="quote">open_oplock_ipc: Failed to
 	get local UDP socket for address 100007f. Error was Cannot assign requested.</span>&#8221;
 	</p><p>
 	Your loopback device isn't working correctly. Make sure it is configured correctly. The loopback
 	device is an internal (virtual) network device with the IP address <span class="emphasis"><em>127.0.0.1</em></span>.
 	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="id2553968"></a>&#8220;<span class="quote"><span class="errorname">The network name cannot be found</span></span>&#8221;</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553962"></a>&#8220;<span class="quote"><span class="errorname">The network name cannot be found</span></span>&#8221;</h3></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 a nonexisting path
 			for the share in <code class="filename">smb.conf</code>.</p></li><li><p>The user you are trying to access the share with does not 
diff --git a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html
index 9ec860a16d..0c779c135a 100644
--- a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html
+++ b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html
@@ -1,18 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�29.�Integrating MS Windows Networks with Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication"><link rel="next" href="unicode.html" title="Chapter�30.�Unicode/Charsets"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�29.�Integrating MS Windows Networks with Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pam.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="unicode.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter�29.�Integrating MS Windows Networks with Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667924">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667945">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668147">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668326">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668362">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669058">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669245">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669273">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669301">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669438">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669452">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669483">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669525">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2667882"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�29.�Integrating MS Windows Networks with Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication"><link rel="next" href="unicode.html" title="Chapter�30.�Unicode/Charsets"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�29.�Integrating MS Windows Networks with Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pam.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="unicode.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter�29.�Integrating MS Windows Networks with Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668059">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668079">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668281">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668470">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668506">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669202">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669380">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669408">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669435">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669573">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669586">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669617">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669659">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2668017"></a>
 This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If
 your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this
 section does not apply to your installation. If your installation involves the use of
 NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2667900"></a>
-<a class="indexterm" name="id2667907"></a>
+<a class="indexterm" name="id2668034"></a>
+<a class="indexterm" name="id2668041"></a>
 NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
 over Logical Link Control (LLC). On modern networks it is highly advised
 to not run NetBEUI at all. Note also that there is no such thing as
 NetBEUI over TCP/IP  the existence of such a protocol is a complete
 and utter misapprehension.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667924"></a>Features and Benefits</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668059"></a>Features and Benefits</h2></div></div></div><p>
 Many MS Windows network administrators have never been exposed to basic TCP/IP
 networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and
 Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP-based
@@ -20,12 +20,12 @@ networking (and may have no desire to be, either).
 </p><p>
 This chapter gives a short introduction to the basics of how a name can be resolved to 
 its IP address for each operating system environment.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667945"></a>Background Information</h2></div></div></div><p>
-<a class="indexterm" name="id2667953"></a>
-<a class="indexterm" name="id2667960"></a>
-<a class="indexterm" name="id2667966"></a>
-<a class="indexterm" name="id2667973"></a>
-<a class="indexterm" name="id2667980"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668079"></a>Background Information</h2></div></div></div><p>
+<a class="indexterm" name="id2668087"></a>
+<a class="indexterm" name="id2668094"></a>
+<a class="indexterm" name="id2668101"></a>
+<a class="indexterm" name="id2668108"></a>
+<a class="indexterm" name="id2668114"></a>
 Since the introduction of MS Windows 2000, it is possible to run MS Windows networking
 without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
 name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
@@ -36,43 +36,43 @@ When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled
 the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
 Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic).
 </p></div><p>
-<a class="indexterm" name="id2668008"></a>
-<a class="indexterm" name="id2668015"></a>
-<a class="indexterm" name="id2668022"></a>
-<a class="indexterm" name="id2668028"></a>
-<a class="indexterm" name="id2668035"></a>
-<a class="indexterm" name="id2668042"></a>
+<a class="indexterm" name="id2668143"></a>
+<a class="indexterm" name="id2668149"></a>
+<a class="indexterm" name="id2668156"></a>
+<a class="indexterm" name="id2668162"></a>
+<a class="indexterm" name="id2668169"></a>
+<a class="indexterm" name="id2668176"></a>
 When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS
 over TCP/IP today use MS Active Directory Service (ADS). ADS requires
-<a class="indexterm" name="id2668052"></a> dynamic DNS with Service Resource
-Records (SRV RR) and with Incremental Zone Transfers (IXFR).  <a class="indexterm" name="id2668062"></a>
+<a class="indexterm" name="id2668186"></a> dynamic DNS with Service Resource
+Records (SRV RR) and with Incremental Zone Transfers (IXFR).  <a class="indexterm" name="id2668197"></a>
 Use of DHCP with ADS is recommended as a further means of maintaining central control over the client
 workstation network configuration.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668074"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668208"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p>
 The key configuration files covered in this section are:
-</p><a class="indexterm" name="id2668084"></a><a class="indexterm" name="id2668091"></a><a class="indexterm" name="id2668098"></a><a class="indexterm" name="id2668105"></a><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">/etc/hosts</code></p></li><li><p><code class="filename">/etc/resolv.conf</code></p></li><li><p><code class="filename">/etc/host.conf</code></p></li><li><p><code class="filename">/etc/nsswitch.conf</code></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668147"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p>
+</p><a class="indexterm" name="id2668218"></a><a class="indexterm" name="id2668225"></a><a class="indexterm" name="id2668232"></a><a class="indexterm" name="id2668239"></a><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">/etc/hosts</code></p></li><li><p><code class="filename">/etc/resolv.conf</code></p></li><li><p><code class="filename">/etc/host.conf</code></p></li><li><p><code class="filename">/etc/nsswitch.conf</code></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668281"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p>
 This file contains a static list of IP addresses and names.
 </p><pre class="programlisting">
 127.0.0.1	localhost localhost.localdomain
 192.168.1.1	bigbox.quenya.org	bigbox	alias4box
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2668170"></a>
-<a class="indexterm" name="id2668177"></a>
+<a class="indexterm" name="id2668304"></a>
+<a class="indexterm" name="id2668311"></a>
 The purpose of <code class="filename">/etc/hosts</code> is to provide a 
 name resolution mechanism so users do not need to remember 
 IP addresses.
 </p><p>
-<a class="indexterm" name="id2668195"></a>
-<a class="indexterm" name="id2668202"></a>
-<a class="indexterm" name="id2668208"></a>
+<a class="indexterm" name="id2668329"></a>
+<a class="indexterm" name="id2668336"></a>
+<a class="indexterm" name="id2668342"></a>
 Network packets that are sent over the physical network transport 
 layer communicate not via IP addresses but rather using the Media 
 Access Control address, or MAC address. IP addresses are currently 
 32 bits in length and are typically presented as four decimal 
 numbers that are separated by a dot (or period)  for example, 168.192.1.1.
 </p><p>
-<a class="indexterm" name="id2668227"></a>
+<a class="indexterm" name="id2668361"></a>
 MAC addresses use 48 bits (or 6 bytes) and are typically represented 
 as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56.
 </p><p>
@@ -84,14 +84,14 @@ interface, the assignment of an IP address makes sense from a network management
 address can be assigned per MAC address. One address must be the primary IP address  this is the
 address that will be returned in the Address Resolution Protocol (ARP) reply.
 </p><p>
-<a class="indexterm" name="id2668258"></a>
+<a class="indexterm" name="id2668392"></a>
 When a user or a process wants to communicate with another machine, 
 the protocol implementation ensures that the &#8220;<span class="quote">machine name</span>&#8221; or &#8220;<span class="quote">host 
 name</span>&#8221; is resolved to an IP address in a manner that is controlled 
 by the TCP/IP configuration control files. The file 
 <code class="filename">/etc/hosts</code> is one such file.
 </p><p>
-<a class="indexterm" name="id2668285"></a>
+<a class="indexterm" name="id2668419"></a>
 When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to
 identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram
 Protocol (UDP) to send a request to all interfaces on the local network segment using the all 1s MAC address.
@@ -99,7 +99,7 @@ Network interfaces are programmed to respond to two MAC addresses only; their ow
 address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary
 IP address for each interface.
 </p><p>
-<a class="indexterm" name="id2668305"></a>
+<a class="indexterm" name="id2668448"></a>
 The <code class="filename">/etc/hosts</code> file is foundational to all 
 UNIX/Linux TCP/IP installations and as a minimum will contain 
 the localhost and local network interface IP addresses and the 
@@ -107,7 +107,7 @@ primary names by which they are known within the local machine.
 This file helps to prime the pump so a basic level of name 
 resolution can exist before any other method of name resolution 
 becomes available.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668326"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668470"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p>
 This file tells the name resolution libraries:
 </p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine 
 	belongs.
@@ -117,8 +117,8 @@ This file tells the name resolution libraries:
 	</p></li><li><p>The name or IP address of available domain 
 	name servers that may be asked to perform name-to-address 
 	translation lookups.
-	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668362"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p>
-<a class="indexterm" name="id2668373"></a>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668506"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p>
+<a class="indexterm" name="id2668517"></a>
 <code class="filename">/etc/host.conf</code> is the primary means by which the setting in
 <code class="filename">/etc/resolv.conf</code> may be effected. It is a critical configuration file. This file controls
 the order by which name resolution may proceed. The typical structure is:
@@ -127,8 +127,8 @@ order hosts,bind
 multi on
 </pre><p>Both addresses should be returned. Please refer to the 
 man page for <code class="filename">host.conf</code> for further details.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668413"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p>
-<a class="indexterm" name="id2668425"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668557"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p>
+<a class="indexterm" name="id2668568"></a>
 This file controls the actual name resolution targets. The 
 file typically has resolver object specifications as follows:
 </p><pre class="programlisting">
@@ -160,11 +160,11 @@ It should be noted that unless a network request/message must be
 sent, TCP/IP networks are silent. All TCP/IP communications assume a 
 principal of speaking only when necessary.
 </p><p>
-<a class="indexterm" name="id2668461"></a>
-<a class="indexterm" name="id2668468"></a>
-<a class="indexterm" name="id2668474"></a>
-<a class="indexterm" name="id2668481"></a>
-<a class="indexterm" name="id2668488"></a>
+<a class="indexterm" name="id2668604"></a>
+<a class="indexterm" name="id2668611"></a>
+<a class="indexterm" name="id2668618"></a>
+<a class="indexterm" name="id2668625"></a>
+<a class="indexterm" name="id2668632"></a>
 Starting with version 2.2.0, Samba has Linux support for extensions to 
 the name service switch infrastructure so Linux clients will 
 be able to obtain resolution of MS Windows NetBIOS names to IP 
@@ -177,11 +177,11 @@ the <code class="filename">/etc/nsswitch.conf</code> file. At this point, it
 will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, as long as that machine is within the workgroup to 
 which both the Samba machine and the MS Windows machine belong.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668537"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p>
-<a class="indexterm" name="id2668546"></a>
-<a class="indexterm" name="id2668553"></a>
-<a class="indexterm" name="id2668560"></a>
-<a class="indexterm" name="id2668567"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668681"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p>
+<a class="indexterm" name="id2668689"></a>
+<a class="indexterm" name="id2668696"></a>
+<a class="indexterm" name="id2668703"></a>
+<a class="indexterm" name="id2668710"></a>
 MS Windows networking is predicated on the name each machine is given. This name is known variously (and
 inconsistently) as the &#8220;<span class="quote">computer name,</span>&#8221; &#8220;<span class="quote">machine name,</span>&#8221; &#8220;<span class="quote">networking
 name,</span>&#8221; &#8220;<span class="quote">NetBIOS name,</span>&#8221; or &#8220;<span class="quote">SMB name.</span>&#8221; All terms mean the same thing with the
@@ -195,16 +195,16 @@ registered for each service type that is provided by the client/server.
 <a class="link" href="integrate-ms-networks.html#uniqnetbiosnames" title="Table�29.1.�Unique NetBIOS Names">Unique NetBIOS names</a> and <a class="link" href="integrate-ms-networks.html#netbiosnamesgrp" title="Table�29.2.�Group Names">group names</a> tables 
 list typical NetBIOS name/service type registrations.
 </p><div class="table"><a name="uniqnetbiosnames"></a><p class="title"><b>Table�29.1.�Unique NetBIOS Names</b></p><div class="table-contents"><table summary="Unique NetBIOS Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">MACHINENAME&lt;00&gt;</td><td align="justify">Server Service is running on MACHINENAME</td></tr><tr><td align="left">MACHINENAME&lt;03&gt;</td><td align="justify">Generic machine name (NetBIOS name)</td></tr><tr><td align="left">MACHINENAME&lt;20&gt;</td><td align="justify">LanMan server service is running on MACHINENAME</td></tr><tr><td align="left">WORKGROUP&lt;1b&gt;</td><td align="justify">Domain master browser</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="netbiosnamesgrp"></a><p class="title"><b>Table�29.2.�Group Names</b></p><div class="table-contents"><table summary="Group Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">WORKGROUP&lt;03&gt;</td><td align="justify">Generic name registered by all members of WORKGROUP</td></tr><tr><td align="left">WORKGROUP&lt;1c&gt;</td><td align="justify">Domain cntrollers/netlogon servers</td></tr><tr><td align="left">WORKGROUP&lt;1d&gt;</td><td align="justify">Local master browsers</td></tr><tr><td align="left">WORKGROUP&lt;1e&gt;</td><td align="justify">Browser election service</td></tr></tbody></table></div></div><br class="table-break"><p>
-<a class="indexterm" name="id2668762"></a>
+<a class="indexterm" name="id2668907"></a>
 It should be noted that all NetBIOS machines register their own 
 names as per <a class="link" href="integrate-ms-networks.html#uniqnetbiosnames" title="Table�29.1.�Unique NetBIOS Names">Unique NetBIOS names</a> and <a class="link" href="integrate-ms-networks.html#netbiosnamesgrp" title="Table�29.2.�Group Names">group names</a>. This is in vast contrast to TCP/IP 
 installations where the system administrator traditionally 
 determines in the <code class="filename">/etc/hosts</code> or in the DNS database what names 
 are associated with each IP address.
 </p><p>
-<a class="indexterm" name="id2668798"></a>
-<a class="indexterm" name="id2668804"></a>
-<a class="indexterm" name="id2668811"></a>
+<a class="indexterm" name="id2668942"></a>
+<a class="indexterm" name="id2668948"></a>
+<a class="indexterm" name="id2668955"></a>
 One further point of clarification should be noted. The <code class="filename">/etc/hosts</code> 
 file and the DNS records do not provide the NetBIOS name information 
 that MS Windows clients depend on to locate the type of service that may 
@@ -216,8 +216,8 @@ registered the name type *&lt;1C&gt;. A logon request is then sent to each
 IP address that is returned in the enumerated list of IP addresses.
 Whichever machine first replies, it then ends up providing the logon services.
 </p><p>
-<a class="indexterm" name="id2668843"></a>
-<a class="indexterm" name="id2668850"></a>
+<a class="indexterm" name="id2668987"></a>
+<a class="indexterm" name="id2668994"></a>
 The name &#8220;<span class="quote">workgroup</span>&#8221; or &#8220;<span class="quote">domain</span>&#8221; really can be confusing, since these 
 have the added significance of indicating what is the security 
 architecture of the MS Windows network. The term &#8220;<span class="quote">workgroup</span>&#8221; indicates 
@@ -230,14 +230,14 @@ will simply opt to have no security at all. It is possible to have
 user-level security in a workgroup environment, thus requiring the use 
 of a username and a matching password.
 </p><p>
-<a class="indexterm" name="id2668882"></a>
-<a class="indexterm" name="id2668889"></a>
-<a class="indexterm" name="id2668898"></a>
-<a class="indexterm" name="id2668908"></a>
-<a class="indexterm" name="id2668917"></a>
-<a class="indexterm" name="id2668927"></a>
-<a class="indexterm" name="id2668934"></a>
-<a class="indexterm" name="id2668940"></a>
+<a class="indexterm" name="id2669026"></a>
+<a class="indexterm" name="id2669033"></a>
+<a class="indexterm" name="id2669043"></a>
+<a class="indexterm" name="id2669052"></a>
+<a class="indexterm" name="id2669062"></a>
+<a class="indexterm" name="id2669071"></a>
+<a class="indexterm" name="id2669078"></a>
+<a class="indexterm" name="id2669084"></a>
 MS Windows networking is thus predetermined to use machine names 
 for all local and remote machine message passing. The protocol used is 
 called Server Message Block (SMB), and this is implemented using 
@@ -252,10 +252,10 @@ NBT or NetBT, the NetBIOS over TCP/IP.
 MS Windows machines use a complex array of name resolution mechanisms. 
 Since we are primarily concerned with TCP/IP, this demonstration is 
 limited to this area.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668972"></a>The NetBIOS Name Cache</h3></div></div></div><p>
-<a class="indexterm" name="id2668979"></a>
-<a class="indexterm" name="id2668986"></a>
-<a class="indexterm" name="id2668992"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669116"></a>The NetBIOS Name Cache</h3></div></div></div><p>
+<a class="indexterm" name="id2669123"></a>
+<a class="indexterm" name="id2669130"></a>
+<a class="indexterm" name="id2669137"></a>
 All MS Windows machines employ an in-memory buffer in which is 
 stored the NetBIOS names and IP addresses for all external 
 machines that machine has communicated with over the 
@@ -263,7 +263,7 @@ past 10 to 15 minutes. It is more efficient to obtain an IP address
 for a machine from the local cache than it is to go through all the 
 configured name resolution mechanisms.
 </p><p>
-<a class="indexterm" name="id2669007"></a>
+<a class="indexterm" name="id2669151"></a>
 If a machine whose name is in the local name cache is shut 
 down before the name is expired and flushed from the cache, then 
 an attempt to exchange a message with that machine will be subject 
@@ -271,14 +271,14 @@ to timeout delays. Its name is in the cache, so a name resolution
 lookup will succeed, but the machine cannot respond. This can be 
 frustrating for users but is a characteristic of the protocol.
 </p><p>
-<a class="indexterm" name="id2669024"></a>
-<a class="indexterm" name="id2669031"></a>
-<a class="indexterm" name="id2669038"></a>
+<a class="indexterm" name="id2669168"></a>
+<a class="indexterm" name="id2669175"></a>
+<a class="indexterm" name="id2669182"></a>
 The MS Windows utility that allows examination of the NetBIOS 
 name cache is called &#8220;<span class="quote">nbtstat.</span>&#8221; The Samba equivalent
 is called <code class="literal">nmblookup</code>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669058"></a>The LMHOSTS File</h3></div></div></div><p>
-<a class="indexterm" name="id2669066"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669202"></a>The LMHOSTS File</h3></div></div></div><p>
+<a class="indexterm" name="id2669210"></a>
 This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory
 <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains the IP address
 and the machine name in matched pairs. The <code class="filename">LMHOSTS</code> file
@@ -363,15 +363,15 @@ It typically looks like this:
 # so keeping the number of comments to a minimum will improve performance.
 # Therefore it is not advisable to simply add lmhosts file entries onto the
 # end of this file.
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669245"></a>HOSTS File</h3></div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669380"></a>HOSTS File</h3></div></div></div><p>
 This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in 
 the directory <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains 
 the IP address and the IP hostname in matched pairs. It can be 
 used by the name resolution infrastructure in MS Windows, depending 
 on how the TCP/IP environment is configured. This file is in 
 every way the equivalent of the UNIX/Linux <code class="filename">/etc/hosts</code> file.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669273"></a>DNS Lookup</h3></div></div></div><p>
-<a class="indexterm" name="id2669281"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669408"></a>DNS Lookup</h3></div></div></div><p>
+<a class="indexterm" name="id2669415"></a>
 This capability is configured in the TCP/IP setup area in the network 
 configuration facility. If enabled, an elaborate name resolution sequence 
 is followed, the precise nature of which is dependent on how the NetBIOS 
@@ -382,10 +382,10 @@ cache. If that fails, then DNS, HOSTS, and LMHOSTS are checked. If set to
 Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the 
 WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast 
 lookup is used.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669301"></a>WINS Lookup</h3></div></div></div><p>
-<a class="indexterm" name="id2669308"></a>
-<a class="indexterm" name="id2669315"></a>
-<a class="indexterm" name="id2669325"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669435"></a>WINS Lookup</h3></div></div></div><p>
+<a class="indexterm" name="id2669443"></a>
+<a class="indexterm" name="id2669449"></a>
+<a class="indexterm" name="id2669459"></a>
 A WINS (Windows Internet Name Server) service is the equivalent of the 
 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores 
 the names and IP addresses that are registered by a Windows client 
@@ -393,19 +393,19 @@ if the TCP/IP setup has been given at least one WINS server IP address.
 </p><p>
 To configure Samba to be a WINS server, the following parameter needs 
 to be added to the <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669358"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p>
-<a class="indexterm" name="id2669371"></a>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669492"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p>
+<a class="indexterm" name="id2669506"></a>
 To configure Samba to use a WINS server, the following parameters are 
 needed in the <code class="filename">smb.conf</code> file:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669393"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id2669405"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669528"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id2669539"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p>
 where <em class="replaceable"><code>xxx.xxx.xxx.xxx</code></em> is the IP address 
 of the WINS server.
 </p><p>For information about setting up Samba as a WINS server, read 
-<a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669438"></a>Common Errors</h2></div></div></div><p>
+<a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669573"></a>Common Errors</h2></div></div></div><p>
 TCP/IP network configuration problems find every network administrator sooner or later.
 The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to
 carelessness. Of course, no one is ever deliberately careless!
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669452"></a>Pinging Works Only One Way</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669586"></a>Pinging Works Only One Way</h3></div></div></div><p>
 	&#8220;<span class="quote">I can ping my Samba server from Windows, but I cannot ping my Windows
 	machine from the Samba server.</span>&#8221;
 	</p><p>
@@ -415,10 +415,10 @@ carelessness. Of course, no one is ever deliberately careless!
 	</p><p>
 	Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while
 	the Samba server was on network 192.168.1.128/25  logically a different network.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669483"></a>Very Slow Network Connections</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669617"></a>Very Slow Network Connections</h3></div></div></div><p>
 	A common cause of slow network response includes:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>Client is configured to use DNS and the DNS server is down.</p></li><li><p>Client is configured to use remote DNS server, but the
-		remote connection is down.</p></li><li><p>Client is configured to use a WINS server, but there is no WINS server.</p></li><li><p>Client is not configured to use a WINS server, but there is a WINS server.</p></li><li><p>Firewall is filtering out DNS or WINS traffic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669525"></a>Samba Server Name-Change Problem</h3></div></div></div><p>
+		remote connection is down.</p></li><li><p>Client is configured to use a WINS server, but there is no WINS server.</p></li><li><p>Client is not configured to use a WINS server, but there is a WINS server.</p></li><li><p>Firewall is filtering out DNS or WINS traffic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669659"></a>Samba Server Name-Change Problem</h3></div></div></div><p>
 	&#8220;<span class="quote">The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be
 	pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using
 	the old name. Why?</span>&#8221;
diff --git a/docs/htmldocs/Samba3-HOWTO/introduction.html b/docs/htmldocs/Samba3-HOWTO/introduction.html
index 443227537d..3479cb1238 100644
--- a/docs/htmldocs/Samba3-HOWTO/introduction.html
+++ b/docs/htmldocs/Samba3-HOWTO/introduction.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�General Installation</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="IntroSMB.html" title="Introduction"><link rel="next" href="install.html" title="Chapter�1.�How to Install and Test SAMBA"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�General Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="install.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>Part�I.�General Installation</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2551774"></a>Preparing Samba for Configuration</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�I.�General Installation</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="IntroSMB.html" title="Introduction"><link rel="next" href="install.html" title="Chapter�1.�How to Install and Test SAMBA"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�I.�General Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="install.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>Part�I.�General Installation</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2551769"></a>Preparing Samba for Configuration</h1></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><span class="chapter"><a href="install.html">1. How to Install and Test SAMBA</a></span></dt><dd><dl><dt><span class="sect1"><a href="install.html#id2551914">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551954">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551996">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552898">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553078">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553482">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553540">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553592">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553683">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553764">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553805">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553838">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553848">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553935">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553968">The network name cannot be found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="FastStart.html">2. Fast Start: Cure for Impatience</a></span></dt><dd><dl><dt><span class="sect1"><a href="FastStart.html#id2554110">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554133">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554203">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554221">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555963">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556806">Domain Controller</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="install.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Introduction�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�How to Install and Test SAMBA</td></tr></table></div></body></html>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="install.html">1. How to Install and Test SAMBA</a></span></dt><dd><dl><dt><span class="sect1"><a href="install.html#id2551909">Obtaining and Installing Samba</a></span></dt><dt><span class="sect1"><a href="install.html#id2551950">Configuring Samba (smb.conf)</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2551991">Configuration File Syntax</a></span></dt><dt><span class="sect2"><a href="install.html#tdbdocs">TDB Database File Information</a></span></dt><dt><span class="sect2"><a href="install.html#id2552892">Starting Samba</a></span></dt><dt><span class="sect2"><a href="install.html#id2553073">Example Configuration</a></span></dt><dt><span class="sect2"><a href="install.html#id2553476">SWAT</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553534">List Shares Available on the Server</a></span></dt><dt><span class="sect1"><a href="install.html#id2553587">Connect with a UNIX Client</a></span></dt><dt><span class="sect1"><a href="install.html#id2553678">Connect from a Remote SMB Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553759">What If Things Don't Work?</a></span></dt><dt><span class="sect2"><a href="install.html#id2553800">Still Stuck?</a></span></dt></dl></dd><dt><span class="sect1"><a href="install.html#id2553832">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="install.html#id2553842">Large Number of smbd Processes</a></span></dt><dt><span class="sect2"><a href="install.html#id2553930">Error Message: open_oplock_ipc</a></span></dt><dt><span class="sect2"><a href="install.html#id2553962">The network name cannot be found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="FastStart.html">2. Fast Start: Cure for Impatience</a></span></dt><dd><dl><dt><span class="sect1"><a href="FastStart.html#id2554105">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554128">Description of Example Sites</a></span></dt><dt><span class="sect1"><a href="FastStart.html#id2554197">Worked Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="FastStart.html#id2554216">Standalone Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2555957">Domain Member Server</a></span></dt><dt><span class="sect2"><a href="FastStart.html#id2556800">Domain Controller</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="install.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Introduction�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�1.�How to Install and Test SAMBA</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/ix01.html b/docs/htmldocs/Samba3-HOWTO/ix01.html
index 9db1ecaf4b..56eef13813 100644
--- a/docs/htmldocs/Samba3-HOWTO/ix01.html
+++ b/docs/htmldocs/Samba3-HOWTO/ix01.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2695328"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>"Printers" folder, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt><dt>$, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>%i macro, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>%L, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>%PDF, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>%SystemRoot%\System32\config, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>../source/nsswitch, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a></dt><dt>.ai, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>.AppleDouble, <a class="indexterm" href="VFS.html#id2651644">netatalk</a></dt><dt>.eps, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>.pdf, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>.PDS extension, <a class="indexterm" href="ProfileMgmt.html#id2661846">Windows NT4 Workstation</a></dt><dt>.profiles, <a class="indexterm" href="ProfileMgmt.html#id2660688">Windows 9x/Me User Profiles</a></dt><dt>.ps, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>.recycle, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>/bin/false, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>/dev/null, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>/dev/shadowvol, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>/etc/cups/, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>/etc/cups/mime.convs, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>/etc/cups/mime.types, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>/etc/fstab, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>/etc/group, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a>, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="Portability.html#id2688963">HPUX</a></dt><dt>/etc/groups, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>/etc/host.conf, <a class="indexterm" href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668362">/etc/host.conf</a></dt><dt>/etc/hosts, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>/etc/hosts&gt;, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>/etc/inetd.conf, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="compiling.html#id2688359">Starting from inetd.conf</a></dt><dt>/etc/init.d/samba, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="winbind.html#id2656126">Linux</a></dt><dt>/etc/init.d/samba.server, <a class="indexterm" href="winbind.html#id2656332">Solaris</a></dt><dt>/etc/init.d/smb, <a class="indexterm" href="winbind.html#id2656126">Linux</a></dt><dt>/etc/krb5.conf, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>/etc/ldap.conf, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>/etc/logingroup, <a class="indexterm" href="Portability.html#id2688963">HPUX</a></dt><dt>/etc/mime.conv, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>/etc/mime.types, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>/etc/nsswitch.conf, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></dt><dt>/etc/openldap/slapd.conf, <a class="indexterm" href="FastStart.html#id2557700">The Primary Domain Controller</a></dt><dt>/etc/openldap/sldap.conf, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a></dt><dt>/etc/pam.conf, <a class="indexterm" href="winbind.html#id2657034">Solaris-Specific Configuration</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="pam.html#id2665655">Technical Discussion</a>, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>/etc/pam.d, <a class="indexterm" href="winbind.html#id2654580">Requirements</a>, <a class="indexterm" href="winbind.html#id2654732">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>/etc/pam.d/, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a>, <a class="indexterm" href="pam.html#id2665655">Technical Discussion</a></dt><dt>/etc/pam.d/ftp, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/pam.d/login, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/pam.d/samba, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/passwd, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a>, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a>, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>/etc/printcap, <a class="indexterm" href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></dt><dt>/etc/resolv.conf, <a class="indexterm" href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>/etc/samba, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>/etc/samba/scripts, <a class="indexterm" href="NetCommand.html#id2600629">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>/etc/samba/secrets.tdb, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>/etc/samba/smb.conf, <a class="indexterm" href="install.html#id2551954">Configuring Samba (smb.conf)</a></dt><dt>/etc/samba/smbpasswd, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a></dt><dt>/etc/samba/smbusers, <a class="indexterm" href="NetCommand.html#id2601250">User Mapping</a></dt><dt>/etc/shadow, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>/etc/smbpasswd, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a></dt><dt>/etc/ssl/certs/slapd.pem, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>/etc/xinetd.d, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/xinetd.d/telnet, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/export, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>/lib/libnss_example.so, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>/lib/libnss_files.so, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>/lib/security, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665709">PAM Configuration Syntax</a></dt><dt>/lib/security/, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>/opt/samba/bin, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a></dt><dt>/tmp, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>/usr/bin/openssl, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt><dt>/usr/lib/samba/vfs, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>/usr/lib/security, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a></dt><dt>/usr/lib/security/methods.cfg, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a></dt><dt>/usr/local/lib, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>/usr/local/samba, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>/usr/local/samba/bin, <a class="indexterm" href="winbind.html#id2656126">Linux</a>, <a class="indexterm" href="winbind.html#id2656332">Solaris</a>, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a></dt><dt>/usr/local/samba/lib, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>/usr/local/samba/lib/vfs, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>/usr/local/samba/private/secrets.tdb, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>/usr/local/samba/swat, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/usr/local/samba/var, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a>, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>/usr/local/samba/var/locks, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>/usr/sbin, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a>, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/usr/share/samba/swat, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/var/locks/*.tdb, <a class="indexterm" href="speed.html#id2691064">Corrupt tdb Files</a></dt><dt>/var/log/samba, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>/var/run/samba, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>/var/spool/cups/, <a class="indexterm" href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>/var/spool/samba, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>250-user limit, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a></dt><dt>3.0.11, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>4,500 user accounts, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a></dt><dt>4294967295, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>8.3 file names, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>&gt;Domain User Manager, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></dt><dt>\\%L\%U\.profiles, <a class="indexterm" href="ProfileMgmt.html#id2660688">Windows 9x/Me User Profiles</a></dt><dt>\\SERVER, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>_kerberos.REALM.NAME, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>_kerberos._udp, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>_ldap._tcp, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>_ldap._tcp.pdc._msdcs.quenya.org, <a class="indexterm" href="samba-bdc.html#id2567578">NetBIOS Over TCP/IP Disabled</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt>, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="install.html#id2553078">Example Configuration</a>, <a class="indexterm" href="FastStart.html#anon-ro">Anonymous Read-Only Document Server</a>, <a class="indexterm" href="FastStart.html#id2554637">Anonymous Read-Write Document Server</a>, <a class="indexterm" href="FastStart.html#id2554849">Anonymous Print Server</a>, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="FastStart.html#id2556885">Example: Engineering Office</a>, <a class="indexterm" href="FastStart.html#id2557700">The Primary Domain Controller</a>, <a class="indexterm" href="FastStart.html#id2558316">Backup Domain Controller</a>, <a class="indexterm" href="ServerType.html#id2559402">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559595">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560196">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560443">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564357">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566690">Example PDC Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570897">Samba Client</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583364">Use of the Remote Announce Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2594059">Configuring Samba</a>, <a class="indexterm" href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="NetCommand.html#id2600629">Managing Nest Groups on Workstations from the Samba Server</a>, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2614099">Interaction with the Standard Samba create mask Parameters</a>, <a class="indexterm" href="AccessControls.html#id2614965">Users Cannot Write to a Public Share</a>, <a class="indexterm" href="AccessControls.html#id2615334">MS Word with Samba Changes Owner of File</a>, <a class="indexterm" href="locking.html#id2617008">Disabling Oplocks</a>, <a class="indexterm" href="locking.html#id2617103">Disabling Kernel Oplocks</a>, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618467">User-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a>, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a>, <a class="indexterm" href="msdfs.html#id2621877">MSDFS UNIX Path Is Case-Critical</a>, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a>, <a class="indexterm" href="classicalprinting.html#id2623480">Extended Printing Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a>, <a class="indexterm" href="classicalprinting.html#id2626941">Creating the [print$] Share</a>, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2633679">More Complex CUPS smb.conf Settings</a>, <a class="indexterm" href="CUPS-printing.html#id2640432">From Windows Clients to a CUPS/Samba Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2641226">Prepare Your smb.conf for cupsaddsmb</a>, <a class="indexterm" href="VFS.html#id2650261">Discussion</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a>, <a class="indexterm" href="winbind.html#id2655330">Configure smb.conf</a>, <a class="indexterm" href="winbind.html#id2656126">Linux</a>, <a class="indexterm" href="winbind.html#id2657034">Solaris-Specific Configuration</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="ProfileMgmt.html#id2660548">NT4/200x User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2660688">Windows 9x/Me User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2660846">Mixed Windows Windows 9x/Me and NT4/200x User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2664685">Changing the Default Profile</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669301">WINS Lookup</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a>, <a class="indexterm" href="unicode.html#id2670859">Individual Implementations</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678746">IdMap LDAP Support</a>, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a>, <a class="indexterm" href="bugreport.html#id2686191">Debugging-Specific Operations</a>, <a class="indexterm" href="Other-Clients.html#id2690254">Windows 2000 Service Pack 2</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>abbreviated keystrokes, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a></dt><dt>aborting shutdown, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>accept connections, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>access, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a></dt><dt>Access, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>access authentication, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>access control, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a>, <a class="indexterm" href="AdvancedNetworkManagement.html">Advanced Network Management</a></dt><dt>Access Control, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Access Control Entries (see ACE)</dt><dt>Access Control List, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>access control needs, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>access controls, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a>, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>Access Controls, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>access denied, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>access policies, <a class="indexterm" href="passdb.html#id2592233">Domain Account Policy Managment</a></dt><dt>access rights, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>account, <a class="indexterm" href="install.html#id2553078">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dd><dl><dt>backend, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>database, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt><dd><dl><dt>backends, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a></dt></dl></dd></dl></dd><dt>account access controls, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>account attributes, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>account backends, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>account containers, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a></dt><dt>account control block (see ACB)</dt><dt>account control flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account controls, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Account Controls, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>account database, <a class="indexterm" href="passdb.html#id2592519">Password Backends</a></dt><dt>account deleted, <a class="indexterm" href="passdb.html#id2591488">Deleting Accounts</a></dt><dt>account encode_bits, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account flag order, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>Account Flags, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>account flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account import/export, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2592394">Account Import/Export</a></dt><dt>account information, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dt>account information database, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>account management, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>account name, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>account policies, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt><dt>account policy, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>account restrictions, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>account security, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>account storage backends, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a></dt><dt>account storage mechanisms, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>account storage system, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>Account Unknown, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>accountability, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>accounts, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>ACL, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>ACLs, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></dt><dd><dl><dt>File System, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>POSIX, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>share, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>Windows, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt></dl></dd><dt>ACLs on share, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>ACLs on shares, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>across network segments, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>active directory, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564237">Samba ADS Domain Control</a></dt><dt>Active Directory, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a>, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a>, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>Active Directory Server, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>AD4UNIX, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>ADAM, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>add a user account, <a class="indexterm" href="passdb.html#id2591400">Adding User Accounts</a></dt><dt>add client machines, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>add domain users and groups to a local group, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>add drivers, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>add machine script, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677897">Changes in Behavior</a></dt><dt>Add Printer Wizard, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>add printer wizard, <a class="indexterm" href="CUPS-printing.html#id2634646">Driver Upload Methods</a></dt><dt>add user script, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677897">Changes in Behavior</a></dt><dt>add/delete/change share, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>adddriver, <a class="indexterm" href="classicalprinting.html#id2628576">Installing Driver Files into [print$]</a>, <a class="indexterm" href="classicalprinting.html#id2628949">Running rpcclient with adddriver</a>, <a class="indexterm" href="classicalprinting.html#id2629412">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></dt><dt>additional driver, <a class="indexterm" href="classicalprinting.html#id2630248">Additional Client Driver Installation</a></dt><dt>additional privileges, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>addmem, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>AddPrinterDriver(), <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></dt><dt>admincfg.exe, <a class="indexterm" href="Other-Clients.html#id2690017">Configuring Windows for Workgroups Password Handling</a></dt><dt>administrative actions, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>administrative duties, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>administrative privileges, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>administrative responsibilities, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>administrative rights, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>administrative rights and privileges, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Administrative Templates, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></dt><dt>Administrator, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>administrator account, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dt>Administrator account, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>administrator password, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>Administrator%password, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>Adobe, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>Adobe driver, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>Adobe driver files, <a class="indexterm" href="CUPS-printing.html#id2641746">Recognizing Different Driver Files</a></dt><dt>Adobe PostScript, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>Adobe PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></dt><dt>Adobe PPD, <a class="indexterm" href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a></dt><dt>Adobe specifications, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>ADS, <a class="indexterm" href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a>, <a class="indexterm" href="NetCommand.html#id2599319">Administrative Tasks and Methods</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2654403">Result Caching</a>, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660180">System Startup and Logon Processing Overview</a>, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a>, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a> (see Active Directory)</dt><dt>ADS DC, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a></dt><dt>ADS domain, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>ADS domain members, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>ADS manager, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>ADS schema, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>Advanced TCP/IP configuration, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>advantages, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>affect users, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></dt><dt>affordable power, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>AFPL, <a class="indexterm" href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dt>AFPL Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>AFS, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>AIX, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a></dt><dt>algorithmic mapping, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>alias group, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>allow access, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>allow trusted domains, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>already exists, <a class="indexterm" href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></dt><dt>alternative solution, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>Amanda, <a class="indexterm" href="Backup.html#id2671724">Amanda</a></dt><dt>analyzes data, <a class="indexterm" href="problems.html#id2684689">Diagnostics Tools</a></dt><dt>anonymous, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dd><dl><dt>print server, <a class="indexterm" href="FastStart.html#id2554849">Anonymous Print Server</a></dt><dt>read-write server, <a class="indexterm" href="FastStart.html#id2554637">Anonymous Read-Write Document Server</a></dt></dl></dd><dt>anonymous access, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>anonymous file server, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>anonymous server, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>ANSI compiler, <a class="indexterm" href="Portability.html#id2688963">HPUX</a></dt><dt>anticipate failure, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>API, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>Appliances, <a class="indexterm" href="winbind.html#id2653584">Target Uses</a></dt><dt>application servers, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>application/cups.vnd-postscript, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>application/octet-stream, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>application/pdf, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>application/postscript, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>application/vnd.cups-postscript, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a></dt><dt>application/vnd.cups-raster, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>application/vnd.cups-raw, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt><dt>application/x-shell, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>apt-get, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>ARCFOUR-HMAC-MD5, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>architecture, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>ARP/RARP, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>ASCII, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a>, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a></dt><dt>ASCII text, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a></dt><dt>assign rights, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>assigned RID, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>assistance, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>associations, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>attach gdb, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>attribute, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>attributes, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>audit file access, <a class="indexterm" href="VFS.html#id2650662">audit</a></dt><dt>audit module, <a class="indexterm" href="VFS.html#id2650921">extd_audit</a></dt><dt>auth, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>authenticate, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>authenticate users, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>authenticated, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a></dt><dt>authenticating server, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></dt><dt>authentication, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2592394">Account Import/Export</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dd><dl><dt>backend, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt></dl></dd><dt>authentication agents, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>authentication architecture, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>authentication backend, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>authentication control, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>authentication database, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a></dt><dt>authentication management, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>authentication mechanisms, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>authentication methods, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>authentication module API, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a></dt><dt>authentication regime, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>authentication reply, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></dt><dt>authentication server, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>authentication service, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>authentication system, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>authenticatior, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>authoritative, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>authoritive, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>authorization, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>auto-reconnect, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>autogen.sh, <a class="indexterm" href="compiling.html#id2687849">Building the Binaries</a></dt><dt>autogenerated printcap, <a class="indexterm" href="classicalprinting.html#id2625436">Default UNIX System Printing Commands</a></dt><dt>automatic account creation, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>automatic mapping, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>automatic reconnects, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>automatic redundancy, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>autopoweruser.sh, <a class="indexterm" href="NetCommand.html#id2600629">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>autotyping, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>AUXILIARY, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>auxiliary members, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>availability, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>available, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>available port, <a class="indexterm" href="classicalprinting.html#id2631819">Samba and Printer Ports</a></dt><dt>available printerd, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>available rights, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>average print run, <a class="indexterm" href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>b-node, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>back up, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>backed up, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>backend, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>backend authentication, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>backend database, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>backend failures, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>backend file system pool, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a></dt><dt>backends, <a class="indexterm" href="ChangeNotes.html#id2579095">Passdb Changes</a>, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dt>backup, <a class="indexterm" href="Backup.html#id2671241">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a>, <a class="indexterm" href="tdb.html#id2686735">Features and Benefits</a></dt><dt>backup domain controller, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>backup solution, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>BackupPC, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>bad hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>bad logon attempts, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>Bad networking hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>bad password, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>banner pages, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a>, <a class="indexterm" href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a></dt><dt>barriers, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a></dt><dt>Batch Oplock, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>BDC, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dt>BDCs, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>behavior approximately same, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></dt><dt>between domains, <a class="indexterm" href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></dt><dt>bias, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>binary format TDB, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>BIND, <a class="indexterm" href="DNSDHCP.html#id2692992">Dynamic DNS</a></dt><dt>bind interfaces only, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>BIND9, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>BIND9.NET, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a></dt><dt>bindery-enabled, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>block device, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>block incoming packets, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>BOBS, <a class="indexterm" href="Backup.html#id2671772">BOBS: Browseable Online Backup System</a></dt><dt>bogus, <a class="indexterm" href="ServerType.html#id2560443">Example Configuration</a></dt><dt>boot disk`, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>bridge, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>bridges networks, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>brlock.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>broadcast, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>broadcast address, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>broadcast isolated subnet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>broadcast messages, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>broadcast messaging, <a class="indexterm" href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a></dt><dt>Broadcast node, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>broadcast request, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>broadcast traffic, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>broadcast-based, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>broadcast-based name resolution, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>broadcasts, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>browse across subnet, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>browse list, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>browse list handling, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a></dt><dt>browse list maintainers, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>browse list management, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>browse lists, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>browse resources, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>browse server resources, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>browse shares, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>browse.dat, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>browseable, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>browser election, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>browser elections, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>BrowseShortNames, <a class="indexterm" href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>browsing, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></dt><dt>browsing across subnets, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>browsing another subnet, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></dt><dt>browsing intrinsics, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>browsing problems, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586391">Common Errors</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586539">I Get an "Unable to browse the network" Error</a></dt><dt>BSD, <a class="indexterm" href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>BSD Printing, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>BSD-style printing, <a class="indexterm" href="classicalprinting.html#id2623480">Extended Printing Configuration</a></dt><dt>bug report, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>bug reports, <a class="indexterm" href="bugreport.html#id2685866">Introduction</a></dt><dt>Bugzilla, <a class="indexterm" href="bugreport.html#id2685866">Introduction</a></dt><dt>built-in commands, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>bypasses privilege, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>byte ranges, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>byte-range lock, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>byte-range locking, <a class="indexterm" href="locking.html#id2615667">Discussion</a>, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>c:\winnt\inf, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>C:\WinNT\System32\config, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>cached</dt><dd><dl><dt>password, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a></dt></dl></dd><dt>cached encrypted password, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>cached in memory, <a class="indexterm" href="passdb.html#id2588513">Advantages of Non-Encrypted Passwords</a></dt><dt>cached local file, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>cached locally, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>cached references, <a class="indexterm" href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></dt><dt>caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>caching reads, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>caching scheme, <a class="indexterm" href="winbind.html#id2654403">Result Caching</a></dt><dt>caching writes, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>called name, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>cannot join domain, <a class="indexterm" href="ClientConfig.html#id2578353">Common Errors</a></dt><dt>canonicalize files, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>CAP, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a>, <a class="indexterm" href="Other-Clients.html#id2689543">Macintosh Clients</a></dt><dt>cap-share, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>capability to delete, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>CAP_LINUX_IMMUTABLE, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>case options, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>case sensitivity, <a class="indexterm" href="pam.html#id2665709">PAM Configuration Syntax</a></dt><dt>case-insensitive, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a>, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>case-preserving, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a></dt><dt>central environment, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>centralized</dt><dd><dl><dt>authentication, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt></dl></dd><dt>centralized identity management, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>centrally managed, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>certificate, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt><dt>Certificate Authority (see CA)</dt><dt>cfdisk, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>challenge/response mechanism, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>change capabilities, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt><dt>change motivations, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>change password, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>change passwords, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt><dt>changed parameters, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>changes password, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>character device, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>character set, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>character sets, <a class="indexterm" href="unicode.html#id2669921">Samba and Charsets</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>charset, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>charset conversion, <a class="indexterm" href="unicode.html#id2670056">Conversion from Old Names</a></dt><dt>chattr, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>check for locks, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>check logs, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>checksum-search, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>chmod, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>chown, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="AccessControls.html#id2613583">Viewing File Ownership</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>chpass, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>CIFS, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>CIFS function calls, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>CIFS/SMB, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a>, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>Citrix, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>clear purpose preferred, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>clear-text, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>clear-text passwords, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>Client for Microsoft Networks, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Client for Novell Networks, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>client instructions, <a class="indexterm" href="ClientConfig.html#id2575508">Features and Benefits</a></dt><dt>client-server mode, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt><dt>client-side caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>client-side data caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a>, <a class="indexterm" href="locking.html#id2616609">PDM Data Shares</a></dt><dt>clock skew, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>cluster servers, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>clustered file server, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>Clustered smbds, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a></dt><dt>clustering technologies, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>cluttering, <a class="indexterm" href="bugreport.html#id2686191">Debugging-Specific Operations</a></dt><dt>cmd, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a>, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>cmd shell, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>CN, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>code maintainer, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>codepages, <a class="indexterm" href="unicode.html#id2669736">Features and Benefits</a></dt><dt>collating, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></dt><dt>collisions, <a class="indexterm" href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>color, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>COM1:, <a class="indexterm" href="classicalprinting.html#id2631819">Samba and Printer Ports</a></dt><dt>command-line, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>command-line utility, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>commenting out setting, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>commercial Linux products, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>commercial support, <a class="indexterm" href="ch47.html">Samba Support</a>, <a class="indexterm" href="ch47.html#id2692569">Commercial Support</a></dt><dt>commit the settings, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>Common Internet Filesystem (see CIFS)</dt><dt>Common restrictions, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>Common UNIX Printing System (see CUPS)</dt><dt>common.adm, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>comp.protocols.smb, <a class="indexterm" href="bugreport.html#id2685866">Introduction</a></dt><dt>compatible, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="Portability.html">Portability</a></dt><dt>compile, <a class="indexterm" href="install.html#id2551914">Obtaining and Installing Samba</a></dt><dt>compile-time options, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>complex file name space, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>complex organization, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>complexity, <a class="indexterm" href="StandAloneServer.html#id2574457">Example Configuration</a></dt><dt>compliance, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>complicated, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>complicated problem, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>comprehensive documentation, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>Computer Account, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dt>computer account, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>computer accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Computer Management, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a>, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>Computer Name, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>computer name, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>concurrent access, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Conectiva, <a class="indexterm" href="CUPS-printing.html#id2646614">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>config.cache, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a></dt><dt>CONFIG.POL, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>Config.POL, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></dt><dt>configuration</dt><dd><dl><dt>documentation, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a></dt></dl></dd><dt>configuration files, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a></dt><dt>configuration problem, <a class="indexterm" href="bugreport.html#id2685866">Introduction</a></dt><dt>configuration syntax, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>configuration techniques, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>configuration too complex, <a class="indexterm" href="StandAloneServer.html#id2575441">Common Errors</a></dt><dt>configuration tool, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>configuration wizard, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>configure, <a class="indexterm" href="compiling.html#id2687849">Building the Binaries</a></dt><dt>configuring a firewall, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>confirm address, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>confirm the password, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></dt><dt>confirm the trust, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>connect transparently, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>connection resources, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></dt><dt>connections, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>connections.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>consistent case, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>console, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>consumer expects, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>container, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>continuity of service, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>contribute, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>Control Panel, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>controls, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>convert</dt><dd><dl><dt>domain member server, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt></dl></dd><dt>converted, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>copy'n'paste, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>core files, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a></dt><dt>core graphic engine, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a></dt><dt>core values, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>corrupted file, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>cosine.schema, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>country of origin, <a class="indexterm" href="ch47.html#id2692569">Commercial Support</a></dt><dt>CP850, <a class="indexterm" href="unicode.html#id2669921">Samba and Charsets</a></dt><dt>CP932, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>cracker, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>create, <a class="indexterm" href="AccessControls.html#id2611105">Managing Directories</a></dt><dt>Create a Computer Account, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dt>create a domain machine account, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>create domain member, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a></dt><dt>create machine trust account, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>create partition, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>Create the Computer Account, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>create user accounts, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>create volume, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>credentials, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>credentials validation, <a class="indexterm" href="samba-bdc.html#id2567512">NetBIOS Over TCP/IP Enabled</a></dt><dt>critical aspects of configuration, <a class="indexterm" href="ClientConfig.html#id2575508">Features and Benefits</a></dt><dt>crle, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>cron, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></dt><dt>cross post, <a class="indexterm" href="problems.html#id2685560">Getting Mailing List Help</a></dt><dt>cross-segment browsing, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>cross-subnet browsing, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>CUPS, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2623480">Extended Printing Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="CUPS-printing.html#id2632902">Features and Benefits</a>, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a>, <a class="indexterm" href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a>, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a></dt><dd><dl><dt>Page Accounting, <a class="indexterm" href="CUPS-printing.html#id2647287">Page Accounting with CUPS</a></dt><dt>quotas, <a class="indexterm" href="CUPS-printing.html#id2647322">Setting Up Quotas</a></dt></dl></dd><dt>CUPS API, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="classicalprinting.html#id2625436">Default UNIX System Printing Commands</a></dt><dt>CUPS backends, <a class="indexterm" href="CUPS-printing.html#id2637850">CUPS Backends</a></dt><dt>CUPS filtering, <a class="indexterm" href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>CUPS filtering chain, <a class="indexterm" href="CUPS-printing.html#id2637850">CUPS Backends</a></dt><dt>CUPS libarary API, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>CUPS PostScript, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>CUPS PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>CUPS print filters, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>CUPS raster, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>CUPS-PPD, <a class="indexterm" href="CUPS-printing.html#id2646226">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>cups.hlp, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>cupsaddsmb, <a class="indexterm" href="CUPS-printing.html#id2634646">Driver Upload Methods</a>, <a class="indexterm" href="CUPS-printing.html#id2641128">cupsaddsmb: The Unknown Utility</a>, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a>, <a class="indexterm" href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643014">cupsaddsmb with a Samba PDC</a>, <a class="indexterm" href="CUPS-printing.html#id2643095">cupsaddsmb Flowchart</a>, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a></dt><dt>cupsd.conf, <a class="indexterm" href="classicalprinting.html#id2625436">Default UNIX System Printing Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a>, <a class="indexterm" href="CUPS-printing.html#id2638437">mime.convs</a>, <a class="indexterm" href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>cupsomatic, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646226">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>currupted, <a class="indexterm" href="tdb.html#id2686735">Features and Benefits</a></dt><dt>custom scripts, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>customer expected, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>customers, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>customized print commands, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2654580">Requirements</a>, <a class="indexterm" href="compiling.html#id2688579">Alternative: Starting smbd as a Daemon</a></dt><dt>daemon running, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>daemons, <a class="indexterm" href="winbind.html#id2656476">Restarting</a></dt><dt>damaged data, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>data caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>data corruption, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a>, <a class="indexterm" href="locking.html#id2616485">UNIX or NFS Client-Accessed Files</a></dt><dt>data interchange, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>data stream, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>database, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></dt><dt>DatabaseFS, <a class="indexterm" href="VFS.html#id2652629">DatabaseFS</a></dt><dt>DAVE, <a class="indexterm" href="Other-Clients.html#id2689543">Macintosh Clients</a></dt><dt>dbx, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a></dt><dt>DCE RPC, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>DDK, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dt>DDNS, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a>, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a></dt><dt>de-multiplex, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>de-multiplexing, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>Debian, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>Debian Sarge, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>debug, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a></dt><dt>debug level, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a></dt><dt>debugging, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#id2686191">Debugging-Specific Operations</a></dt><dt>debugging passwords, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>debugging problems, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>dedicated heartbeat, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>dedicated print server, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>default accounts, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>default aliases, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>default behavior, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>default devmode, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>default DNS setup, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>default gateways, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>default groups, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>default mapping, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a></dt><dt>default mappings, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>default print command, <a class="indexterm" href="classicalprinting.html#id2625436">Default UNIX System Printing Commands</a></dt><dt>default print commands, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>default printer, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>default printing, <a class="indexterm" href="CUPS-printing.html#id2632902">Features and Benefits</a></dt><dt>default profile, <a class="indexterm" href="ProfileMgmt.html#id2663192">Default Profile for Windows Users</a>, <a class="indexterm" href="ProfileMgmt.html#id2664685">Changing the Default Profile</a></dt><dt>default settings, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>default shells, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>Default User, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>default users, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>defective hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>deferred open, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>defined shares, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>delegate administrative privileges, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>delegated, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a></dt><dt>delegation, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>delete, <a class="indexterm" href="AccessControls.html#id2611105">Managing Directories</a></dt><dt>delete a file, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>delete roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>delete user script, <a class="indexterm" href="passdb.html#id2591488">Deleting Accounts</a></dt><dt>deleted files, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>deleted parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2676647">Removed Parameters</a></dt><dt>delmem, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>demote, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>demoted, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>denial of service, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>deny, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>deny access, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>deny modes, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>deny-none, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>DENY_ALL, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>DENY_DOS, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>DENY_FCB, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>DENY_NONE, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>DENY_READ, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>DENY_WRITE, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>deployment, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>deployment guidelines, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>DES-CBC-CRC, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>DES-CBC-MD5, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>desirable solution, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>desktop cache, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>desktop profile, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>desktop profiles, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>deterents, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a></dt><dt>development libraries, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>devfsd package, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>device mode, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>device-specific commands, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>DFS, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a> (see MS-DFS, Distributed File Systems)</dt><dt>DFS junction, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS links, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS root, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS server, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS tree, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS-aware, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DFS-aware clients, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>DHCP, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a>, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a></dt><dt>DHCP servers, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>DHCP-enabled, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>DHCP-enabled operation, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>diagnostic, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>diagnostic tools, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>diff, <a class="indexterm" href="bugreport.html#id2686652">Patches</a></dt><dt>differences, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>different resources, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>differently encrypted passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>differing protocol, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></dt><dt>dir, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>direct internet access, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a></dt><dt>directory, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a></dt><dt>directory access control, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>directory access permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>directory controls, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>Directory Information Tree (see DIT)</dt><dt>directory permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>directory schema, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>Directory Separators, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>directory server, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>directory_mode, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>disable LMB, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>disable locking, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a></dt><dt>disable roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a></dt><dt>disabling oplocks, <a class="indexterm" href="locking.html#id2616609">PDM Data Shares</a></dt><dt>disass, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a></dt><dt>disaster recovery, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>disconnect a connection, <a class="indexterm" href="ProfileMgmt.html#id2660548">NT4/200x User Profiles</a></dt><dt>disk, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>disk space, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>disparate information systems, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>display PostScript, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>displayName, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>distort, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>distribute authentication systems, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>distributed, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>distributed account, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>Distributed Computing Environment (see DCE)</dt><dt>distributed directory, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>distributed file system, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a> (see DFS)</dt><dt>Distributed File Systems, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>distributed file systems, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>distributed locking protocol, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>distribution, <a class="indexterm" href="install.html#id2553078">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>dithering algorithm, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>DMB, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>DMB for a workgroup, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></dt><dt>DMC, <a class="indexterm" href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a></dt><dt>DMS, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>DN, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>DNS, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a>, <a class="indexterm" href="samba-bdc.html#id2567578">NetBIOS Over TCP/IP Disabled</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a>, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669273">DNS Lookup</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a>, <a class="indexterm" href="DNSDHCP.html#id2692901">Example Configuration</a></dt><dd><dl><dt>Active Directory, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>Dynamic, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="DNSDHCP.html#id2692992">Dynamic DNS</a></dt><dt>SRV records, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt></dl></dd><dt>DNS Configuration, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>DNS lookup, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>DNS name resolution, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>dns proxy, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>DNS server, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>DNS server access, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>DNS server settings, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>DNS servers, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>DNS zon, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>DNS/LDAP/ADS, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a></dt><dt>document design, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>documentation, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a>, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>domain, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="passdb.html#id2591400">Adding User Accounts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dd><dl><dt>control, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a></dt><dd><dl><dt>role, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt></dl></dd><dt>controller, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html">Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dd><dl><dt>convert, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>hierarchy, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt></dl></dd><dt>controllers, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt><dt>groups, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>master</dt><dd><dl><dt>browser, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt></dl></dd><dt>member, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dd><dl><dt>server, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt></dl></dd><dt>member server, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>security, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt><dd><dl><dt>protocols, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt></dl></dd><dt>trust account, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt></dl></dd><dt>domain access, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>domain account access policies, <a class="indexterm" href="passdb.html#id2592233">Domain Account Policy Managment</a></dt><dt>domain admin group, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>domain Administrator, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>Domain Admins, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>Domain Admins group, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>domain authentication, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>domain context, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>domain control, <a class="indexterm" href="samba-pdc.html#id2562461">Basics of Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2568602">Common Errors</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="NT4Migration.html">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt>backup, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a></dt><dt>primary, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a></dt></dl></dd><dt>domain control database (see SAM)</dt><dt>domain controller, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567512">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dt>Domain Controller, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>domain controllers, <a class="indexterm" href="samba-pdc.html#id2564237">Samba ADS Domain Control</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>domain environment, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>domain global, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global group, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global groups, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain global user, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global users, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain group, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>domain group settings, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain groups, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>Domain Groups, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a></dt><dt>Domain Guests, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>domain information, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>domain join, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>domain joining, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>domain logon, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564290">Domain and Network Logon Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564309">Domain Network Logon Service</a>, <a class="indexterm" href="samba-bdc.html#id2566690">Example PDC Configuration</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>domain logon server, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>domain logons, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>domain management tools, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>domain master, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></dt><dt>domain member, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2573692">Common Errors</a>, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>Domain Member, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dd><dl><dt>joining, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a></dt></dl></dd><dt>domain member client, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a></dt><dt>Domain Member Client (see DMC)</dt><dt>domain member server, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>Domain Member Server (see DMS)</dt><dt>domain member servers, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>domain member workstations, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain members, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>domain membership, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a></dt><dt>domain name, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Domain Name System (see DNS)</dt><dt>domain non-member, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a></dt><dt>domain policies, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>domain radio button, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>domain security, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>domain security account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Domain Server Manager, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>domain SID, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>domain trust, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></dt><dt>domain user, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>domain user accounts, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>domain user manager, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a></dt><dt>Domain User Manager, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>Domain Users, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>domain users, <a class="indexterm" href="winbind.html#id2654580">Requirements</a>, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="winbind.html#id2657151">Conclusion</a></dt><dt>Domain Users group, <a class="indexterm" href="groupmapping.html#id2598630">Adding Domain Users to the Workstation Power Users Group</a></dt><dt>domain-level, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></dt><dt>domain-level security, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>domain-wide browse list, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></dt><dt>DOMAIN&lt;1B&gt;, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>DOMAIN&lt;1C&gt;, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>DOMAIN&lt;1D&gt;, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>draft, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>Drive Identification, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>driver, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dt>driver CDROM, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>driver download, <a class="indexterm" href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></dt><dt>Driver File, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>driver files, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>Driver Path, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>dual-daemon winbindd, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>due diligence, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>duplex, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>duplex printing, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>duplicate, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>duplication of information, <a class="indexterm" href="winbind.html#id2653341">Introduction</a></dt><dt>DVI, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a></dt><dt>Dynamic DNS (see DDNS)</dt><dt>Dynamic Host Configuration Protocol (see DHCP)</dt><dt>dynamic link loader, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>dynamic registration files, <a class="indexterm" href="DNSDHCP.html#id2692992">Dynamic DNS</a></dt><dt>Dynamic SMB servers, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>dynamically loadable library modules, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>e-Directory, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>EAs, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>economically wise, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>eDirectory, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>editreg, <a class="indexterm" href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a></dt><dt>efficient authentication, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>election, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>election criteria, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>election packet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>election process, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>EMF, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2640176">From Windows Clients to an NT Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></dt><dt>enables clients to print, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>enables NetBIOS over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>encapsulating, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>encoding, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>encryped password, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>encrypted, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>encrypted password, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>encrypted passwords, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a>, <a class="indexterm" href="passdb.html#id2587269">Features and Benefits</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="ProfileMgmt.html#id2662631">Profile Migration from Windows NT4/200x Server to Samba</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a></dt><dt>encrypted session, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>encryption, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a></dt><dt>encryption key, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a></dt><dt>encryption types, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573414">Notes</a></dt><dt>enforcing, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>English, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a>, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>Enhanced MetaFile (see EMF)</dt><dt>enterprise, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>enumdrivers, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></dt><dt>enumerate domain groups, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></dt><dt>enumerate domain users, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></dt><dt>EnumJobs(), <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>enumprinters, <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></dt><dt>environment variables, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>EPM (see ESP meta packager)</dt><dt>Epson Stylus, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>Epson Stylus inkjet, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>equivalence, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>equivalent rights and privileges, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>error message, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="classicalprinting.html#id2628949">Running rpcclient with adddriver</a></dt><dt>error messages, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>errors that can afflict, <a class="indexterm" href="ClientConfig.html#id2578353">Common Errors</a></dt><dt>ESC/P, <a class="indexterm" href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></dt><dt>ESP, <a class="indexterm" href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dd><dl><dt>Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>meta packager, <a class="indexterm" href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dt>Print Pro, <a class="indexterm" href="CUPS-printing.html#id2639941">Sources of CUPS Drivers/PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2641890">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></dt></dl></dd><dt>ESP Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>established, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>ethereal, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="problems.html#id2684997">Tcpdump</a>, <a class="indexterm" href="problems.html#id2685047">Ethereal</a>, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>Ethernet adapters, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>EUC-JP, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>eucJP-ms locale, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Event Viewer, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>Everyone - Full Control, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>Everyone group, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>EVMS, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a></dt><dt>examples, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>examples/LDAP, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>execute, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>existing LDAP DIT, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>expands control abilities, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>expired password, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>explicit trust, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>explicitly set, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>exploit opportunities, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a></dt><dt>exploitation, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>exported file system, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>exposed, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>extd_audit module, <a class="indexterm" href="VFS.html#id2650921">extd_audit</a></dt><dt>Extended Attributes, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>extended attributes, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>Extended BSD Printing, <a class="indexterm" href="classicalprinting.html#id2623480">Extended Printing Configuration</a></dt><dt>extended characters, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>extended protocol, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>extended SAM, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>extra machine, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fail, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>failed join, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>failed logins, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>failover communication, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>failover process, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>failover servers, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>fails, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>failure, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>failure semantics, <a class="indexterm" href="SambaHA.html#id2672808">Required Modifications to Samba</a></dt><dt>fake-permissions module, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>fake_permissions, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>fake_perms, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a>, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>fdisk, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>Federated Identity Management (see FIM)</dt><dt>federated organizations, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>federated-identity, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>Fiber Channel, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>fickle, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a></dt><dt>fid, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>file access permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>File Naming Conventions, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>file ownership, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>file serving, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>File System, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dd><dl><dt>case sensitivity, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>feature comparison, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>UNIX, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>Windows, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>file system capabilities, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>FILE:, <a class="indexterm" href="classicalprinting.html#id2631819">Samba and Printer Ports</a></dt><dt>filemanager, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>filename mangling, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>filter, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>Filter Oplock, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>FilterLimit, <a class="indexterm" href="CUPS-printing.html#id2638437">mime.convs</a></dt><dt>filters, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>FIM, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>firewall, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a>, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>firewall active, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>firewall setups, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>fixed IP address, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>fixed IP addresses, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a></dt><dt>flush local locks, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>flush name cache, <a class="indexterm" href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></dt><dt>foomatic, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2646003">foomatic-rip and Foomatic Explained</a>, <a class="indexterm" href="CUPS-printing.html#id2646151">Foomatic's Strange Name</a></dt><dt>Foomatic database, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>Foomatic Printer, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>Foomatic tutorial, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>foomatic-rip, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646003">foomatic-rip and Foomatic Explained</a>, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>Foomatic/cupsomatic, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>force an election, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>force election, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></dt><dt>forced synchronization, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>foreign domain, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>foreign SID, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a></dt><dt>foreign user, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a></dt><dt>FQDN, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>framing error, <a class="indexterm" href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>free support, <a class="indexterm" href="ch47.html">Samba Support</a>, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>FreeBSD, <a class="indexterm" href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>freezing, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>French, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>front-end virtual server, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>frustrating experience, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dt>FTP, <a class="indexterm" href="passdb.html#id2588513">Advantages of Non-Encrypted Passwords</a></dt><dt>ftp, <a class="indexterm" href="Backup.html#id2671554">Rsync</a>, <a class="indexterm" href="compiling.html#id2687637">Accessing the Samba Sources via rsync and ftp</a></dt><dt>ftp access, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftp service, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftp services, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftpd, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>full rights, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>functional components, <a class="indexterm" href="bugreport.html#id2686191">Debugging-Specific Operations</a></dt><dt>functionality, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gateway address, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>gcc, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="Portability.html#id2688963">HPUX</a></dt><dt>gdb, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a>, <a class="indexterm" href="bugreport.html#id2686526">Attaching to a Running Process</a></dt><dt>GDI, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2640176">From Windows Clients to an NT Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></dt><dt>general security service application programming interface (see GSSAPI)</dt><dt>generic PostScript, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>generic raster, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>generic raster format, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>genlogon.pl, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658226">Network Logon Script Magic</a></dt><dt>Gentoo, <a class="indexterm" href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>Germany, <a class="indexterm" href="SambaHA.html#id2671989">Technical Discussion</a></dt><dt>get, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>getdriver, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2628576">Installing Driver Files into [print$]</a></dt><dt>getdriverdir, <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></dt><dt>getent, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>getent group demo, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>gethostbyname() function call, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></dt><dt>getpwnam, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>getpwnam() call, <a class="indexterm" href="upgrading-to-3.0.html#id2677897">Changes in Behavior</a></dt><dt>GetSID.exe, <a class="indexterm" href="ProfileMgmt.html#id2662917">Get SID</a></dt><dt>GhostScript, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dd><dl><dt>(see also PostScript)</dt></dl></dd><dt>Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dd><dl><dt>ESP (see ESP
-	GhostScript)</dt></dl></dd><dt>GID, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579095">Passdb Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>GID numbers, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>GID range, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>GIF, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>global print command, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>global right, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>global section, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>Global support, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>global-level, <a class="indexterm" href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a></dt><dt>GNOME, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>GNU Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>GNU GPL, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>GNU tar, <a class="indexterm" href="Backup.html#id2671724">Amanda</a></dt><dt>GNU/Linux, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>GPG, <a class="indexterm" href="compiling.html#id2687711">Verifying Samba's PGP Signature</a></dt><dt>GPL, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>gpolmig.exe, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a></dt><dt>GPOs, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660180">System Startup and Logon Processing Overview</a>, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>grace time, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>grant rights, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>graphical objects, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>graphically illustrated client configuration, <a class="indexterm" href="ClientConfig.html#id2575508">Features and Benefits</a></dt><dt>grayscale, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>greater scalability, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>greatest mistake, <a class="indexterm" href="StandAloneServer.html#id2575441">Common Errors</a></dt><dt>grep, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>group, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dd><dl><dt>account, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>mapping, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt></dl></dd><dt>group account, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a></dt><dt>group accounts, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2596644">Warning: User Private Group Problems</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>group management, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>group mapping, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>group mappings, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>group membership, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>group ownership, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>group permissions, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>Group Policies, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a></dt><dt>group policies, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a></dt><dt>group policy, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>Group Policy, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></dt><dt>Group Policy Container (see GPC)</dt><dt>Group Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660075">Windows NT4/200x</a>, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>Group Policy Objects, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a> (see GPO)</dt><dt>group policy objects (see GPOs)</dt><dt>Group Policy Template (see GPT)</dt><dt>group privileges, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>group profiles, <a class="indexterm" href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></dt><dt>group SID, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>groupadd, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="groupmapping.html#id2598544">Adding Groups Fails</a></dt><dt>groupadd limitations, <a class="indexterm" href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a></dt><dt>groupdel, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>groupmap, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>groupmod, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>grouppol.inf, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></dt><dt>groups, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a>, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a></dt><dd><dl><dt>domain, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>mapping, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>nested, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt></dl></dd><dt>groups of users, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>growing, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>GSSAPI, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>gtklp, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>guest, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>guest account, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>GUI, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>Gutenprint, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a>, <a class="indexterm" href="CUPS-printing.html#id2646510">Driver Development Outside</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>h-node, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>harvesting password hashes, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>hashed password equivalent, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>headers files, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a></dt><dt>Heimdal, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>Heimdal kerberos, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>help, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>help command, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>heterogeneous computing, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>HEX, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a></dt><dt>hi-res photo, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>high availability, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>high order ports, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>high-availability, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>high-availability services, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>high-speed server interconnect, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>higher availability, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>HKEY_CURRENT_USER, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></dt><dt>HKEY_LOCAL_MACHINE, <a class="indexterm" href="PolicyMgmt.html#id2659257">Registry Spoiling</a></dt><dt>holy grail, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>home directories, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>home directory, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>home directory template, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>home drive, <a class="indexterm" href="samba-bdc.html#id2566690">Example PDC Configuration</a></dt><dt>host multiple servers, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>host security, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>host-based protection, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>hostname, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>hosts allow, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>hosts deny, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>house-keeping, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>HOWTO documents, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>HP JetDirect, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>HP Photosmart, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>HP-GL, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>HP-GL., <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a></dt><dt>hpgltops, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>HPIJS, <a class="indexterm" href="CUPS-printing.html#id2646510">Driver Development Outside</a></dt><dt>HPUX, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>http, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>hybrid, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>Hybrid node, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>IANA, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>ID mapping, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>ID mapping database, <a class="indexterm" href="winbind.html#id2654327">User and Group ID Allocation</a></dt><dt>ID range, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>IDEALX, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>Identification, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>identify, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>identity, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a></dt><dt>identity information, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>identity management, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dd><dl><dt>centralized, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt></dl></dd><dt>identity resolution, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>IDMAP, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>idmap, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>idmap backend, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678746">IdMap LDAP Support</a></dt><dt>IDMAP backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>idmap gid, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>idmap GID, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>IDMAP infrastructure, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>idmap uid, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>idmap UID, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>idmap_ad, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>idmap_ldap module, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>idmap_rid, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>IETF, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>ifconfig, <a class="indexterm" href="compiling.html#id2688359">Starting from inetd.conf</a>, <a class="indexterm" href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>ignore connection, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>imagetoraster, <a class="indexterm" href="CUPS-printing.html#id2637547">imagetops and imagetoraster</a></dt><dt>immutible, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>impersonate, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>implementing oplocks, <a class="indexterm" href="locking.html#id2616767">Advanced Samba Oplocks Parameters</a></dt><dt>Implicit Classes, <a class="indexterm" href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>important announcements, <a class="indexterm" href="securing-samba.html#id2619076">Upgrading Samba</a></dt><dt>Imprints, <a class="indexterm" href="classicalprinting.html#id2631965">The Imprints Toolset</a></dt><dt>imprints, <a class="indexterm" href="CUPS-printing.html#id2634646">Driver Upload Methods</a></dt><dt>include, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>independent, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>individual domain user, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>individual section, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>inetd, <a class="indexterm" href="SWAT.html#id2681073">Validate SWAT Installation</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a>, <a class="indexterm" href="compiling.html#id2688359">Starting from inetd.conf</a></dt><dt>inetd.conf, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>inetorgperson.schema, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>inf file, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>infrastructure, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="winbind.html#id2653584">Target Uses</a></dt><dt>inheritance, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>inherits rights, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>initdb.ldif, <a class="indexterm" href="FastStart.html#id2557700">The Primary Domain Controller</a></dt><dt>initGroups.sh, <a class="indexterm" href="FastStart.html#id2556885">Example: Engineering Office</a>, <a class="indexterm" href="groupmapping.html#id2598404">Script to Configure Group Mapping</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dt>inktype, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>insecure, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a>, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>inspire simplicity, <a class="indexterm" href="StandAloneServer.html#id2574457">Example Configuration</a></dt><dt>inspired structure, <a class="indexterm" href="SambaHA.html#id2671989">Technical Discussion</a></dt><dt>install drivers, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>interactive help, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>interdomain</dt><dd><dl><dt>trust</dt><dd><dl><dt>account, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt></dl></dd><dt>trustrs, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a></dt></dl></dd><dt>interdomain connection, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></dt><dt>interdomain trust, <a class="indexterm" href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>interdomain trust accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>interdomain trusts, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a></dt><dt>Interdomain Trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dd><dl><dt>Completing, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></dt><dt>creating, <a class="indexterm" href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a></dt><dt>Facilities, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></dt></dl></dd><dt>interface, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>interface scripts, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a></dt><dt>interface-based exclusion, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>interfaces, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>intermediate information, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>intermediate tools, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>internal ordering, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a></dt><dt>internationalization support, <a class="indexterm" href="SWAT.html#id2681054">Guidelines and Technical Tips</a></dt><dt>Internet, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>Internet Engineering Task Force (see IETF)</dt><dt>Internet Printing Protocol (see IPP)</dt><dt>Internet Protocol TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>Internetworking Packet Exchange (see IPX)</dt><dt>internetworking super daemon, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a></dt><dt>interoperability, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a></dt><dt>intolerance, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>invalid shell, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a></dt><dt>invalid users, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>IP address, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>IP address automatically, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>IP addresses, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>IP aliases, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>IPC$, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>IPC$ connections, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>ipchains, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>ipconfig, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></dt><dt>iPlanet, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>IPP, <a class="indexterm" href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a></dt><dt>IPP client, <a class="indexterm" href="CUPS-printing.html#id2649313">Administrator Cannot Install Printers for All Local Users</a></dt><dt>iptables, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>IPX, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>IRC, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>IRIX, <a class="indexterm" href="VFS.html#id2650261">Discussion</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>ISC</dt><dd><dl><dt>DHCP, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a></dt><dt>DNS, <a class="indexterm" href="DNSDHCP.html#id2692722">Features and Benefits</a></dt></dl></dd><dt>ISC DHCP server, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>isolated workgroup, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>IXFR, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a></dt></dl></div><div class="indexdiv"><h3>J</h3><dl><dt>Japanese, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a>, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>Japanese locale, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Japanese UNIX, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Java, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>JIS X 0208, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a></dt><dt>join, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a></dt><dt>join client, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>join domain, <a class="indexterm" href="samba-pdc.html#id2565287">Joining Domain Fails Because of Existing Machine Account</a></dt><dt>join the ADS domain, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>join the domain, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>join the machine, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dt>joined client, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Joined domain, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>joining domain, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>joining the domain, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>JPEG, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KB 129202, <a class="indexterm" href="locking.html#id2617866">Additional Reading</a></dt><dt>KB 224992, <a class="indexterm" href="locking.html#id2617866">Additional Reading</a></dt><dt>KB 296264, <a class="indexterm" href="locking.html#id2617866">Additional Reading</a></dt><dt>KB 811492, <a class="indexterm" href="locking.html#id2617834">Long Delays Deleting Files over Network with XP SP1</a></dt><dt>KB 812937, <a class="indexterm" href="locking.html#id2617810">Problems Saving Files in MS Office on Windows XP</a></dt><dt>KDC, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>KDE, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>KDE konqueror, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>KDE session, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>KDEPrint, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>kerberos, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>Kerberos, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a>, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="winbind.html#id2653892">Microsoft Active Directory Services</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a></dt><dd><dl><dt>/etc/krb5.conf, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt></dl></dd><dt>Kerberos authentication, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></dt><dt>killall, <a class="indexterm" href="compiling.html#id2688359">Starting from inetd.conf</a></dt><dt>kinit, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a></dt><dt>kixstart, <a class="indexterm" href="NT4Migration.html#id2679725">Logon Scripts</a></dt><dt>kprinter, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>KRB, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>KRB5, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>krb5.conf, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LAN, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a>, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a>, <a class="indexterm" href="problems.html#id2684689">Diagnostics Tools</a></dt><dt>LanMan, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>LanMan logon service, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt><dt>LanMan passwords, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>LanManager, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>LanManager-compatible, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>LanManger password, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>laptops, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>large directory, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>large domain, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>large numbers of files, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>large organizations, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>last change time, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>latency, <a class="indexterm" href="locking.html#id2616521">Slow and/or Unreliable Networks</a></dt><dt>laws, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>LCT (see last change time)</dt><dt>LDAP, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="samba-bdc.html#id2568861">Can I Do This All with LDAP?</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593320">Supported LDAP Servers</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="passdb.html#id2594059">Configuring Samba</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653892">Microsoft Active Directory Services</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dd><dl><dt>directories, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>master, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>server, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>slave, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt></dl></dd><dt>LDAP administration password, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></dt><dt>LDAP administrative password, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>LDAP backend, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></dt><dt>LDAP backends, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>LDAP database, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>LDAP deployment, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>LDAP directory, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>ldap group suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>LDAP idmap Backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>ldap idmap suffix, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>ldap machine suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>LDAP queries, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>LDAP redirects, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>LDAP schema, <a class="indexterm" href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></dt><dt>LDAP server, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>ldap suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>ldap user suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>LDAP-based, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>LDAP., <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dt>LDAP/Kerberos, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>LDAPS, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>ldapsam, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593320">Supported LDAP Servers</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>ldapsam_compat, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>ldapsearch, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>LDAPv3, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>ldconfig, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>ldd, <a class="indexterm" href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></dt><dt>LDIF, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>LDIF file, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a></dt><dt>legacy systems, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>legal UNIX system account name, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>Level1 Oplock, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Level1 oplock, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Level2 Oplock, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>LGPL, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>libcups, <a class="indexterm" href="classicalprinting.html#id2625436">Default UNIX System Printing Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></dt><dt>libcups.so, <a class="indexterm" href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></dt><dt>libcups.so.2, <a class="indexterm" href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></dt><dt>Liberty Alliance, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>libiconv, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>libnss_winbind, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>libnss_winbind.so, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>libnss_wins.so, <a class="indexterm" href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></dt><dt>libraries, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>licensing, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>limitations, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>linewidth, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>link loader configuration, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>Links</dt><dd><dl><dt>hard, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>soft, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>Linux, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Linux High Availability project, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>Linux LVM, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>Linux LVM partition, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>LinuxKongress2002, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>Linuxprinting.org, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646510">Driver Development Outside</a></dt><dt>list of domain controllers, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>listen for connections, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>listen own socket, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>LLC, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a></dt><dt>LM/NT password hashes, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>LMB, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a> (see Local Master Browser)</dt><dt>LMHOSTS, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669058">The LMHOSTS File</a></dt><dt>lmhosts, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>load balancing, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>loaded modules, <a class="indexterm" href="VFS.html#id2650223">Features and Benefits</a></dt><dt>loading printer drivers, <a class="indexterm" href="classicalprinting.html#id2625066">Any [my_printer_name] Section</a></dt><dt>local</dt><dd><dl><dt>groups, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>master</dt><dd><dl><dt>browser, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt></dl></dd></dl></dd><dt>local access permissions, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>local accounts, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>local administrative privileges, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>Local Area Connection, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>Local Area Connection Properties, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>local authentication, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>local authentication database, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>local cache, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></dt><dt>local disk, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>local domain, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a></dt><dt>local group, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>local groups, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>Local Machine Trust Account, <a class="indexterm" href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a></dt><dt>Local Master Browser, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583364">Use of the Remote Announce Parameter</a></dt><dt>local master browser (see LMB)</dt><dt>local names, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>local print driver, <a class="indexterm" href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></dt><dt>local profile, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>local profiles, <a class="indexterm" href="ProfileMgmt.html#id2660434">Features and Benefits</a></dt><dt>local registry values, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></dt><dt>Local security policies, <a class="indexterm" href="CUPS-printing.html#id2649280">Windows 200x/XP Local Security Policies</a></dt><dt>local smbpasswd file, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>local spool area, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>local subnet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>local system printing, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>local UNIX groups, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>local user, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a>, <a class="indexterm" href="winbind.html#id2656476">Restarting</a></dt><dt>local user account, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>local users, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>locale, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>localhost, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>locally known UID, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>locate domain controller, <a class="indexterm" href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a></dt><dt>Lock caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>lock directory, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>lock password, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>lock the account, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>locking, <a class="indexterm" href="locking.html">File and Record Locking</a>, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615667">Discussion</a>, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>locking protocol, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a></dt><dt>locking semantics, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>locking.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>lockout, <a class="indexterm" href="ServerType.html#id2560443">Example Configuration</a></dt><dt>log files, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dd><dl><dt>monitoring, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt></dl></dd><dt>log level, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a></dt><dt>log.nmbd, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>logging, <a class="indexterm" href="VFS.html#id2651078">Configuration of Auditing</a>, <a class="indexterm" href="bugreport.html#id2686191">Debugging-Specific Operations</a></dt><dt>logical directories, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>Logical Link Control (see LLC)</dt><dt>logical volume, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>Logical Volume Manager (see LVM)</dt><dt>Login, <a class="indexterm" href="passdb.html#id2588513">Advantages of Non-Encrypted Passwords</a></dt><dt>login, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>login id, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>login name, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>login shells, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>LoginID, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>logon, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt><dt>logon authentication, <a class="indexterm" href="samba-bdc.html#id2567578">NetBIOS Over TCP/IP Disabled</a></dt><dt>logon drive, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>logon home, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2660688">Windows 9x/Me User Profiles</a></dt><dt>logon name, <a class="indexterm" href="NetCommand.html#id2601250">User Mapping</a></dt><dt>logon path, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>logon processing, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>logon requests, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a>, <a class="indexterm" href="samba-bdc.html#id2567512">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></dt><dt>logon script, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>Logon Scripts, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>Logon scripts, <a class="indexterm" href="NT4Migration.html#id2679725">Logon Scripts</a></dt><dt>logon server, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></dt><dt>logons, <a class="indexterm" href="ProfileMgmt.html#id2660548">NT4/200x User Profiles</a></dt><dt>lookups, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>loopback adapter, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>loopback interface, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="Portability.html#id2689248">Red Hat Linux</a></dt><dt>lower-case, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a></dt><dt>lowercase filenames, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>lp, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a>, <a class="indexterm" href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>lpadmin, <a class="indexterm" href="CUPS-printing.html#id2638506">Raw Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2640064">Printing with Interface Scripts</a>, <a class="indexterm" href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2647322">Setting Up Quotas</a></dt><dt>LPD, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>lpinfo, <a class="indexterm" href="CUPS-printing.html#id2637850">CUPS Backends</a></dt><dt>lpq cache time, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>lpq command, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>LPRNG, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>lpstat, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></dt><dt>LPT1:, <a class="indexterm" href="classicalprinting.html#id2631819">Samba and Printer Ports</a></dt><dt>LsaEnumTrustedDomains, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>LTSP, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>Lustre, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>lvcreate, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>LVM, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>LVM snapshots, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>LVM volume, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>lvm10 package, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>m-node, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>MAC address, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>MAC Addresses, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>Mac OS X , <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>machine, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dd><dl><dt>account, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>machine account, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>machine account password</dt><dd><dl><dt>change protocol, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt></dl></dd><dt>machine accounts, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>machine accounts database, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>machine authentication, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>machine name, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>Machine Policy Objects, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>machine SID, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>machine trust account, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></dt><dd><dl><dt>create privilege, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a></dt><dt>creation, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>password, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>Machine Trust Account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dd><dl><dt>creation, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>password, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>UNIX account, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></dt></dl></dd><dt>Machine Trust Accounts, <a class="indexterm" href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt>creating, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>machine trust accounts, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="domain-member.html#id2573692">Common Errors</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>machine_name, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>machine_nickname, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>Macintosh, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>macros, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>mail, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>mailing list, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>mailing lists, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>maintaining ids, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>major changes, <a class="indexterm" href="upgrading-to-3.0.html#id2677518">New Functionality</a></dt><dt>make, <a class="indexterm" href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a>, <a class="indexterm" href="compiling.html#id2687849">Building the Binaries</a></dt><dt>man, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a></dt><dt>man page, <a class="indexterm" href="winbind.html#id2655330">Configure smb.conf</a></dt><dt>man pages, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>man-in-the-middle, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>manage accounts, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>manage drivers, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>manage groups, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>manage printers, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>manage privileges, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a></dt><dt>manage roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2660434">Features and Benefits</a></dt><dt>manage share permissions, <a class="indexterm" href="AccessControls.html#id2613123">Windows NT4 Workstation/Server</a></dt><dt>manage share-level ACL, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>manage shares, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>manage users, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>manageability, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>Manageability, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>managed by humans, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>management bottleneck, <a class="indexterm" href="locking.html#id2616568">Multiuser Databases</a></dt><dt>management costs, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>management overheads, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>management procedures, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>management tools, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>managing rights, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>mandatory profiles, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>Mandrake, <a class="indexterm" href="CUPS-printing.html#id2646614">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>Mandriva, <a class="indexterm" href="CUPS-printing.html#id2646614">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>manual UNIX account creation, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>manual WINS server entries, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>manually configured, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>manually configured DNS settings, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>map, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="NT4Migration.html#id2679836">User and Group Accounts</a></dt><dt>mapped, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>mapping, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>mapping home directory, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>mapping printer driver, <a class="indexterm" href="classicalprinting.html#id2629526">Running rpcclient with setdriver</a></dt><dt>mappings, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>maps UNIX users and groups, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>master browser, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>master browsers, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>master server, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>master smb.conf, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></dt><dt>MasterAnnouncement, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>match case, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>maximum value, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>mbd kept spawning, <a class="indexterm" href="speed.html#id2691064">Corrupt tdb Files</a></dt><dt>Meccano set, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>mechanism, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>media type, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>member, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>member machine, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>memory, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>messages.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>messaging systems, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>Meta node, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>meta-directory, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>meta-service, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>meta-services, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>Microsoft Active Directory, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>Microsoft Developer Network CDs, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>Microsoft driver, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a></dt><dt>Microsoft management console (see MMC)</dt><dt>Microsoft Remote Procedure Call (see MSRPC)</dt><dt>Microsoft Windows 9x/Me, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>Microsoft Wolfpack, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>middle-ware, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>migrate, <a class="indexterm" href="ServerType.html">Server Types and Security Modes</a>, <a class="indexterm" href="NT4Migration.html">Migration from NT4 PDC to Samba-3 PDC</a></dt><dt>migrate account settings, <a class="indexterm" href="NT4Migration.html#id2679836">User and Group Accounts</a></dt><dt>migrate group, <a class="indexterm" href="NT4Migration.html#id2679836">User and Group Accounts</a></dt><dt>migrate user, <a class="indexterm" href="NT4Migration.html#id2679836">User and Group Accounts</a></dt><dt>migrating, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>migration, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>migration plan, <a class="indexterm" href="NT4Migration.html#id2678914">Planning and Getting Started</a></dt><dt>migration process, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>MIME, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2636764">Filtering  Overview</a>, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dd><dl><dt>filters, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>raw, <a class="indexterm" href="FastStart.html#id2554849">Anonymous Print Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt></dl></dd><dt>MIME conversion rules, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>MIME recognition, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>MIME type, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>mime.types, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>minimal</dt><dd><dl><dt>configuration, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt></dl></dd><dt>minimal configuration, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>minimum security control, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a></dt><dt>misconfigurations, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a></dt><dt>misconfigured settings, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>misinformation, <a class="indexterm" href="domain-member.html">Domain Membership</a></dt><dt>mission-critical, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>MIT, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>MIT kerberos, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>MIT Kerberos, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>mixed mode, <a class="indexterm" href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>mixed profile, <a class="indexterm" href="ProfileMgmt.html#id2660846">Mixed Windows Windows 9x/Me and NT4/200x User Profiles</a></dt><dt>mkdir, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>mkfs.xfs, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>MMC, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a>, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a>, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660075">Windows NT4/200x</a>, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a></dt><dt>MMC snap-in, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a></dt><dt>modem/ISDN, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>moderately secure, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>modprobe, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>module, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>modules, <a class="indexterm" href="VFS.html#id2650223">Features and Benefits</a>, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>more than one protocol, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>mount, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>mouse-over, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>moveuser.exe, <a class="indexterm" href="ProfileMgmt.html#id2662876">moveuser.exe</a></dt><dt>MS DCE RPC, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>MS Windows 2000, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a></dt><dt>MS Windows NT4/200x, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>MS Windows SID, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>MS WINS, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a></dt><dt>MS-DFS, <a class="indexterm" href="SambaHA.html#id2673086">MS-DFS: The Poor Man's Cluster</a></dt><dt>MS-RPC, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>MS-WINS replication, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>msdfs links, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>msg, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>msg file, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt><dt>MSRPC, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>multibyte character sets, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>multibyte charsets, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>multiple backends, <a class="indexterm" href="passdb.html#id2592519">Password Backends</a></dt><dt>multiple domains, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>multiple hosting, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>multiple modules, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>multiple network interfaces, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></dt><dt>multiple network segments, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>multiple personality, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>multiple server hosting, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>multiple server personalities, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>multiple servers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>multiple universal naming convention provider (see MUP)</dt><dt>multiple VFS, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>multiple virtual servers, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>multiple Windows workgroups or domains, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>multiple WINS servers, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>Multiuser databases, <a class="indexterm" href="locking.html#id2616568">Multiuser Databases</a></dt><dt>mutual assistance, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>mutually exclusive options, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>My Network Places, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a></dt><dt>Myrinet, <a class="indexterm" href="SambaHA.html#id2672753">Server Pool Communications Demands</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>n security context, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>n-memory buffer, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></dt><dt>name conflict, <a class="indexterm" href="classicalprinting.html#id2625066">Any [my_printer_name] Section</a></dt><dt>name lookup, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></dt><dt>name lookups, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>name registration, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a></dt><dt>name resolution, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586391">Common Errors</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a>, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>name resolution across routed networks, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>name resolve order, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></dt><dt>name service switch (see NSS)</dt><dt>name-to-address, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>nameserv.h, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>name_type, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></dt><dt>native ACLs, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>native dump, <a class="indexterm" href="Backup.html#id2671724">Amanda</a></dt><dt>native member, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>native mode, <a class="indexterm" href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="winbind.html#id2653892">Microsoft Active Directory Services</a></dt><dt>NBT, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>nbtstat, <a class="indexterm" href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></dt><dt>necessary rights, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>negotiate, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>negotiating the charset, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>nested group, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>Nested Group Support, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>nested groups, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>net, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599319">Administrative Tasks and Methods</a>, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a>, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dd><dl><dt>ads, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dd><dl><dt>join, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a>, <a class="indexterm" href="idmapper.html#id2606185">ADS Domains</a></dt><dt>leave, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>printer info, <a class="indexterm" href="NetCommand.html#id2603742">Printers and ADS</a></dt><dt>printer publish, <a class="indexterm" href="NetCommand.html#id2603742">Printers and ADS</a></dt><dt>printer remove, <a class="indexterm" href="NetCommand.html#id2603742">Printers and ADS</a></dt><dt>printer search, <a class="indexterm" href="NetCommand.html#id2603742">Printers and ADS</a></dt><dt>status, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>testjoin, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt></dl></dd><dt>getlocalsid, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>groupmap, <a class="indexterm" href="FastStart.html#id2556885">Example: Engineering Office</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2598144">Example Configuration</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dd><dl><dt>add, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>delete, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>list, <a class="indexterm" href="groupmapping.html#id2598144">Example Configuration</a>, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>modify, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt></dl></dd><dt>localgroup, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>rap, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dd><dl><dt>session, <a class="indexterm" href="NetCommand.html#id2603676">Session and Connection Management</a></dt></dl></dd><dt>rpc, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dd><dl><dt>getsid, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>group, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>group add, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>group addmem, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a>, <a class="indexterm" href="NetCommand.html#id2600629">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>group delete, <a class="indexterm" href="NetCommand.html#id2600110">Deleting a Group Account</a></dt><dt>group delmem, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></dt><dt>group list, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>group members, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></dt><dt>group rename, <a class="indexterm" href="NetCommand.html#id2600150">Rename Group Accounts</a></dt><dt>info, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a>, <a class="indexterm" href="ProfileMgmt.html#id2662825">Side Bar Notes</a></dt><dt>join, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dt>join bdc, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>join member, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>list, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>printer migrate drivers, <a class="indexterm" href="NetCommand.html#id2603404">Printer Migration</a></dt><dt>printer migrate forms, <a class="indexterm" href="NetCommand.html#id2603404">Printer Migration</a></dt><dt>printer migrate printers, <a class="indexterm" href="NetCommand.html#id2603404">Printer Migration</a></dt><dt>printer migrate security, <a class="indexterm" href="NetCommand.html#id2603404">Printer Migration</a></dt><dt>printer migrate settings, <a class="indexterm" href="NetCommand.html#id2603404">Printer Migration</a></dt><dt>right list accounts, <a class="indexterm" href="NetCommand.html#id2602891">Share Migration</a></dt><dt>rights grant, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>rights list, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>rights list accounts, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>share add, <a class="indexterm" href="NetCommand.html#id2602563">Creating, Editing, and Removing Shares</a></dt><dt>share delete, <a class="indexterm" href="NetCommand.html#id2602563">Creating, Editing, and Removing Shares</a></dt><dt>share migrate, <a class="indexterm" href="NetCommand.html#id2602891">Share Migration</a></dt><dt>share migrate all, <a class="indexterm" href="NetCommand.html#id2603345">Simultaneous Share and File Migration</a></dt><dt>share migrate files, <a class="indexterm" href="NetCommand.html#id2603087">File and Directory Migration</a></dt><dt>share migrate security, <a class="indexterm" href="NetCommand.html#id2603302">Share-ACL Migration</a></dt><dt>testjoin, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>trustdom add, <a class="indexterm" href="NetCommand.html#id2602062">Interdomain Trusts</a></dt><dt>trustdom establish, <a class="indexterm" href="NetCommand.html#id2602062">Interdomain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></dt><dt>trustdom list, <a class="indexterm" href="NetCommand.html#id2602062">Interdomain Trusts</a></dt><dt>trustdom revoke, <a class="indexterm" href="NetCommand.html#id2602062">Interdomain Trusts</a></dt><dt>user add, <a class="indexterm" href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></dt><dt>user delete, <a class="indexterm" href="NetCommand.html#id2601133">Deletion of User Accounts</a>, <a class="indexterm" href="NetCommand.html#id2601693">Machine Trust Accounts</a></dt><dt>user info, <a class="indexterm" href="NetCommand.html#id2601181">Managing User Accounts</a></dt><dt>user password, <a class="indexterm" href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></dt><dt>user rename, <a class="indexterm" href="NetCommand.html#id2601181">Managing User Accounts</a></dt><dt>vampire, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="NetCommand.html#id2602781">Share, Directory, and File Migration</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt></dl></dd><dt>setlocalsid, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>time, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dd><dl><dt>set, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dt>system, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dt>zone, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt></dl></dd><dt>use, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt></dl></dd><dt>NET, <a class="indexterm" href="PolicyMgmt.html#id2660115">Samba PDC</a></dt><dt>net command, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>net getlocalsid, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>net groupmap, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>net rpc user add, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>net tool, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a></dt><dt>net use, <a class="indexterm" href="classicalprinting.html#id2631444">Error Message: Cannot connect under a different Name</a></dt><dt>net use /home, <a class="indexterm" href="ProfileMgmt.html#id2660688">Windows 9x/Me User Profiles</a></dt><dt>net use lpt1:, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></dt><dt>net view, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>netatalk, <a class="indexterm" href="VFS.html#id2651644">netatalk</a></dt><dt>NetAtalk, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Netatalk, <a class="indexterm" href="Other-Clients.html#id2689543">Macintosh Clients</a></dt><dt>NetBEUI, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a></dt><dt>NetBIOS, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></dt><dd><dl><dt>brooadcast, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt><dt>name, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>netbios alias, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>netbios aliases, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>NetBIOS broadcast, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>NetBIOS disabled, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a></dt><dt>NetBIOS flags, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>NetBIOS name, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>netbios name, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>NetBIOS name cache, <a class="indexterm" href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></dt><dt>NetBIOS name length, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>NetBIOS name resolution, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>NetBIOS Name Server (see NBNS)</dt><dt>NetBIOS name type, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></dt><dt>NetBIOS network interface, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>NetBIOS networking, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a></dt><dt>NetBIOS over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a></dt><dt>NetBIOS over TCP/IP disabled, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>NetBIOS-less, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>NetBIOS-less SMB, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>NetBIOSless SMB over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>NetBT, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>netlogon, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>NETLOGON, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>Netlogon, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a></dt><dt>NetLogon service, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>netlogon share, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a></dt><dt>Netmon, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>Netmon., <a class="indexterm" href="problems.html#id2685250">Installing Network Monitor on an NT Workstation</a></dt><dt>netmon.exe, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>NetSAMLogon, <a class="indexterm" href="ProfileMgmt.html#id2660484">Roaming Profiles</a></dt><dt>Netscape's Directory Server, <a class="indexterm" href="passdb.html#id2593320">Supported LDAP Servers</a></dt><dt>NetServerEnum2, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>NetUserGetInfo, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ProfileMgmt.html#id2660484">Roaming Profiles</a></dt><dt>NetWare, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>NetWare Bindery, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>NetWare Core Protocol-based server, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>NetWkstaUserLogon, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>network</dt><dd><dl><dt>browsing, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>logon, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dd><dl><dt>service, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a></dt></dl></dd><dt>performance, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>wide-area, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt></dl></dd><dt>network access controls, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>network access profile, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>network administrator, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>network administrator's toolbox, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>network administrators, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>network analyzer, <a class="indexterm" href="problems.html#id2684689">Diagnostics Tools</a></dt><dt>network bandwidth, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>Network Basic Extended User Interface (see NetBEUI)</dt><dt>Network Basic Input/Output System (see NetBIOS)</dt><dt>Network Bridge, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>Network Bridge Configuration, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>network browsing problems, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>network client, <a class="indexterm" href="ClientConfig.html#id2575508">Features and Benefits</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>network clients, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>network configuration problems, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a></dt><dt>network difficulty, <a class="indexterm" href="ClientConfig.html#id2575508">Features and Benefits</a></dt><dt>network environment, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657636">Remote Desktop Management</a></dt><dt>Network ID, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>network interface, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>network logon, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>network logon services, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>network membership, <a class="indexterm" href="ClientConfig.html#id2575568">Technical Details</a></dt><dt>Network Monitor, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>Network Monitor Tools and Agent, <a class="indexterm" href="problems.html#id2685250">Installing Network Monitor on an NT Workstation</a></dt><dt>Network Neighborhood, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>network neighborhood, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>network policies, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></dt><dt>network security, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>network segment, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>Network settings, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>network sniffer, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>network storage, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>network traffic, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>networked workstation, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>networking advocates, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>networking environment, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>networking systems, <a class="indexterm" href="ClientConfig.html#id2578353">Common Errors</a></dt><dt>networks access, <a class="indexterm" href="speed.html#id2691160">Samba Performance is Very Slow</a></dt><dt>Networks Properties, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>new account, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>new parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2676818">New Parameters</a></dt><dt>newsgroup, <a class="indexterm" href="bugreport.html#id2685866">Introduction</a></dt><dt>Nexus toolkit, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Nexus.exe, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>NFS, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a>, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678746">IdMap LDAP Support</a></dt><dt>NFS clients, <a class="indexterm" href="locking.html#id2616485">UNIX or NFS Client-Accessed Files</a></dt><dt>NIS, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>NIS database, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>nmbd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a>, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="winbind.html#id2654732">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2656126">Linux</a>, <a class="indexterm" href="winbind.html#id2656332">Solaris</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a>, <a class="indexterm" href="speed.html#id2691064">Corrupt tdb Files</a></dt><dt>nmblookup, <a class="indexterm" href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>No NetBIOS layer, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></dt><dt>no network logon service, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>no printcap file, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>nobody, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>nobody account, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>node-type, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>NoMachine, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>NoMachine.Com, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>non-authentication-based account management, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>non-authoritative, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>non-LDAP</dt><dd><dl><dt>backend, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt></dl></dd><dt>non-member Windows client, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>non-PostScript, <a class="indexterm" href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>non-PostScript printers, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>nonhierarchical, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>nontransitive, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>normal color, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>normal user, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>not domain member, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>not domain members, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a></dt><dt>not part of domain, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>not stored anywhere, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>not transitive, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>Novell, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>Novell eDirectory server, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>NSS, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a>, <a class="indexterm" href="winbind.html#id2653755">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2657151">Conclusion</a></dt><dt>nsswitch.conf, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a></dt><dt>nss_ldap, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>nss_winbind.so.1, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>NT domain, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>NT groups, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>NT migration scripts, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>NT password, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>NT Server Manager, <a class="indexterm" href="AccessControls.html#id2613123">Windows NT4 Workstation/Server</a></dt><dt>NT-controlled domain, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></dt><dt>NT-encrypted password, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>NT-encrypted passwords, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>NT4, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>NT4 Domain, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a></dt><dt>NT4 domain, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt><dt>NT4 domain members, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>NT4 style policy updates, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>NT4 User Manager for Domains, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>NT4-style, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>NT4-style domain, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>NT4-style domains, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>Nt4sp6ai.exe, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>NTConfig.POL, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659257">Registry Spoiling</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a>, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a>, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>ntconfig.pol, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>ntdrivers.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>ntforms.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTFS, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>NTLMv2, <a class="indexterm" href="securing-samba.html#id2619021">NTLMv2 Security</a></dt><dt>ntlm_auth, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>ntprinters.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTUser.DAT, <a class="indexterm" href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a>, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a>, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>NTuser.DAT, <a class="indexterm" href="ProfileMgmt.html#id2661846">Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a>, <a class="indexterm" href="NT4Migration.html#id2679791">Profile Migration/Creation</a></dt><dt>NTuser.MAN, <a class="indexterm" href="ProfileMgmt.html#id2661846">Windows NT4 Workstation</a></dt><dt>NTUser.MAN, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>NT_STATUS_LOGON_FAILURE, <a class="indexterm" href="upgrading-to-3.0.html#id2677897">Changes in Behavior</a></dt><dt>NT_STATUS_UNSUCCESSFUL, <a class="indexterm" href="classicalprinting.html#id2628949">Running rpcclient with adddriver</a></dt><dt>null shell, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>NX, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>object class, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>object class declaration, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>object module dependencies, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>ObjectClass, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>ObjectClasses, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>obtuse complexity, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>office server, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a></dt><dt>OID, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>old sambaAccount, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>Omni, <a class="indexterm" href="CUPS-printing.html#id2646510">Driver Development Outside</a></dt><dt>on the fly, <a class="indexterm" href="domain-member.html#id2570814">Windows NT4 Client</a></dt><dt>on-the-fly, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>on-the-fly logon scripts, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>on-the-fly policy files, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>one direction, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>one domain, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>one-way trust, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></dt><dt>only one WINS server, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>OpenGFS, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>OpenLDAP, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2593320">Supported LDAP Servers</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>OpenLDAP backend, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>OpenSSL, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></dt><dt>operating costs, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>operating system search path, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a></dt><dt>oplock, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>oplock break, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a>, <a class="indexterm" href="locking.html#id2616679">Beware of Force User</a></dt><dt>oplock handling, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a></dt><dt>oplock mechanism, <a class="indexterm" href="locking.html#id2616767">Advanced Samba Oplocks Parameters</a></dt><dt>oplock messages, <a class="indexterm" href="SambaHA.html#id2672808">Required Modifications to Samba</a></dt><dt>oplock parameters, <a class="indexterm" href="locking.html#id2616767">Advanced Samba Oplocks Parameters</a></dt><dt>oplocks, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>oplocks disabled, <a class="indexterm" href="locking.html#id2616568">Multiuser Databases</a></dt><dt>oplocks management, <a class="indexterm" href="locking.html#id2616609">PDM Data Shares</a></dt><dt>opportunistic locking, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Opportunistic locking, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>optional, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>ordinary connection, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></dt><dt>Organization for the Advancement of Structured Information Standards (see OASIS)</dt><dt>organizational directory, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>organizational unit, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a> (see OU)</dt><dt>os level, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>OSS/Free Software, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>other, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>output duplexing, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a></dt><dt>outside threat, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>own home directory, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>ownership, <a class="indexterm" href="AccessControls.html#id2613583">Viewing File Ownership</a></dt><dt>ownership cost, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>ownership rights, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>p-node, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>package, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>packages, <a class="indexterm" href="install.html#id2551914">Obtaining and Installing Samba</a></dt><dt>packet sniffer, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>packet trace, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>PADL, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>PADL Software, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>page description languages (see PDL)</dt><dt>pager program, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>page_log, <a class="indexterm" href="CUPS-printing.html#id2647558">The page_log File Syntax</a></dt><dt>paid-for support, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>PAM, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="winbind.html#id2653755">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654580">Requirements</a>, <a class="indexterm" href="winbind.html#id2654732">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2657151">Conclusion</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="pam.html#id2665655">Technical Discussion</a></dt><dt>PAM authentication module, <a class="indexterm" href="pam.html#id2665709">PAM Configuration Syntax</a></dt><dt>PAM configuration, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>PAM management, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a></dt><dt>PAM module, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a></dt><dt>PAM modules, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>PAM-capable, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam-devel, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>PAM-enabled, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>PAM-specific tokens, <a class="indexterm" href="pam.html#id2665709">PAM Configuration Syntax</a></dt><dt>pam_krb5.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_ldap, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>pam_ldap.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_mkhomedir, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>pam_ncp_auth.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_pwdb.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_securetty.so, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>pam_smbpass.so, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_smbpasswd.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_smb_auth.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_unix.so, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_unix2.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_userdb.so, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>pam_winbind.so, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>parameters, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>paranoid, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>passdb, <a class="indexterm" href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a></dt><dt>passdb backend, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591488">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>passdb backends, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>passed across the network, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>passwd, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>password, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a>, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dd><dl><dt>plaintext, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt></dl></dd><dt>password aging, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>password assigned, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></dt><dt>password backend, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>password backends, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>password change facility, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>password database, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>password encryption, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a></dt><dt>password expiration, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>password expired, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>password history, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>password management, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a></dt><dt>password prompt, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>password scheme, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>password server, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a></dt><dt>password uniqueness, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>passwords, <a class="indexterm" href="winbind.html#id2653341">Introduction</a></dt><dt>patch, <a class="indexterm" href="bugreport.html#id2686652">Patches</a></dt><dt>path specified, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>pauses, <a class="indexterm" href="speed.html#id2691160">Samba Performance is Very Slow</a></dt><dt>PBM, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>PCL, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a>, <a class="indexterm" href="CUPS-printing.html#id2640064">Printing with Interface Scripts</a>, <a class="indexterm" href="CUPS-printing.html#id2640309">Driver Execution on the Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640702">Network PostScript RIP</a></dt><dt>pdbedit, <a class="indexterm" href="FastStart.html#id2556885">Example: Engineering Office</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a>, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a>, <a class="indexterm" href="passdb.html#id2591400">Adding User Accounts</a>, <a class="indexterm" href="passdb.html#id2591488">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592394">Account Import/Export</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a>, <a class="indexterm" href="PolicyMgmt.html#id2660115">Samba PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2679885">Steps in Migration Process</a>, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>pdb_ldap, <a class="indexterm" href="samba-bdc.html#id2568861">Can I Do This All with LDAP?</a></dt><dt>PDC, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566690">Example PDC Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a>, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a>, <a class="indexterm" href="CUPS-printing.html#id2643014">cupsaddsmb with a Samba PDC</a>, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a>, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654403">Result Caching</a>, <a class="indexterm" href="winbind.html#id2654466">Introduction</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a>, <a class="indexterm" href="problems.html#id2685560">Getting Mailing List Help</a>, <a class="indexterm" href="speed.html#id2691064">Corrupt tdb Files</a></dt><dt>PDF, <a class="indexterm" href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>pdf, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>PDF distilling, <a class="indexterm" href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a></dt><dt>PDF filter, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>pdftops, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>pdftosocket, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>PDL, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a></dt><dt>PDM, <a class="indexterm" href="locking.html#id2616609">PDM Data Shares</a></dt><dt>peer domain, <a class="indexterm" href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></dt><dt>Peer node, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>per-share access control, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>performance, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>performance advantage, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a></dt><dt>performance degradation, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>performance enhancement, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>performance improvement, <a class="indexterm" href="locking.html#id2616521">Slow and/or Unreliable Networks</a></dt><dt>performance-based, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a></dt><dt>performed as root, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>perimeter firewall, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>permanent changes, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>Permanent name, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>permissions, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dd><dl><dt>file/directory ACLs, <a class="indexterm" href="AccessControls.html#id2613465">Managing UNIX Permissions Using NT Security Dialogs</a></dt><dt>share, <a class="indexterm" href="AccessControls.html#id2611888">Share Definition Access Controls</a></dt><dt>share ACLs, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>UNIX file and directory, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt></dl></dd><dt>Permissions, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>permissions and controls, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>PGP, <a class="indexterm" href="compiling.html#id2687711">Verifying Samba's PGP Signature</a></dt><dt>phasing out NetBIOS, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a></dt><dt>Photo-CD, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>physical locations, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>physical network transport layer, <a class="indexterm" href="integrate-ms-networks.html#id2668147">/etc/hosts</a></dt><dt>PID, <a class="indexterm" href="bugreport.html#id2686526">Attaching to a Running Process</a></dt><dt>pid directory, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>ping, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>pipe device, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>PJL, <a class="indexterm" href="CUPS-printing.html#id2640702">Network PostScript RIP</a>, <a class="indexterm" href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a>, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>PJL-header, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>plague network users, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a></dt><dt>plain-text</dt><dd><dl><dt>passwords, <a class="indexterm" href="ServerType.html#id2560541">Password Checking</a></dt></dl></dd><dt>plaintext, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>plaintext authentication, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>plaintext password, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a></dt><dt>plaintext passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>platforms, <a class="indexterm" href="Portability.html">Portability</a></dt><dt>PLP, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>Pluggable Authentication Modules (see PAM)</dt><dt>PNG, <a class="indexterm" href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>PNM, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>point 'n' print, <a class="indexterm" href="CUPS-printing.html#id2634359">Installation of Windows Client Drivers</a>, <a class="indexterm" href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt><dt>Point'n'Print, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="classicalprinting.html#id2628812">smbclient to Confirm Driver Installation</a></dt><dt>point'n'print, <a class="indexterm" href="CUPS-printing.html#id2634646">Driver Upload Methods</a>, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></dt><dt>Poledit, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a></dt><dt>poledit.exe, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a>, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a></dt><dt>Policies, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>policies, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>policy editor, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></dt><dt>Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>policy file , <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>policy files, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>policy settings, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>port 135, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></dt><dt>Port 135/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 137, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>Port 137/UDP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 138, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></dt><dt>Port 138/UDP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 139, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></dt><dt>Port 139/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 445, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></dt><dt>Port 445/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>ports, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a>, <a class="indexterm" href="problems.html#id2685047">Ethereal</a></dt><dt>POSIX, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a>, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>POSIX account, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a>, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dt>POSIX ACLs, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a>, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>POSIX ACLS, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>POSIX identity, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>POSIX locks, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a></dt><dt>POSIX semantics, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a></dt><dt>POSIX user accounts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>posixAccount, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>posixGroup, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a></dt><dt>PostScript, <a class="indexterm" href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a>, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a>, <a class="indexterm" href="CUPS-printing.html#id2640309">Driver Execution on the Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640702">Network PostScript RIP</a>, <a class="indexterm" href="CUPS-printing.html#id2640975">CUPS: A Magical Stone?</a>, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dd><dl><dt>(see also Ghostscript)</dt><dt>RIP, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt></dl></dd><dt>PostScript driver, <a class="indexterm" href="classicalprinting.html#id2628576">Installing Driver Files into [print$]</a></dt><dt>PostScript interpreter, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PostScript Printer Description (see PPD)</dt><dt>PostScript printers, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dt>potential master browsers, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>potential printer, <a class="indexterm" href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></dt><dt>Power Users, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>powerful, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>PPD, <a class="indexterm" href="classicalprinting.html#id2628576">Installing Driver Files into [print$]</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2638506">Raw Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2640792">PPDs for Non-PS Printers on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2640836">PPDs for Non-PS Printers on Windows</a>, <a class="indexterm" href="CUPS-printing.html#id2640975">CUPS: A Magical Stone?</a>, <a class="indexterm" href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dd><dl><dt>CUPS (see CUPS-PPD)</dt></dl></dd><dt>PPD-aware, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PPDs, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>PPP, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>precedence, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>preferred master, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></dt><dt>prefilter, <a class="indexterm" href="CUPS-printing.html#id2637547">imagetops and imagetoraster</a></dt><dt>prefilters, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a></dt><dt>primary domain controller, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></dt><dt>primary group, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>Primary Logon, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>Primary WINS Server, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>print, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dd><dl><dt>queue, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>spooler, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt></dl></dd><dt>print accounting, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>print command, <a class="indexterm" href="classicalprinting.html#id2625360">Print Commands</a></dt><dt>print commands, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>print configuration, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dt>print environment, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>print filtering, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>print job, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>print jobs, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>print processing, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>print queue, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="classicalprinting.html#id2628812">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="classicalprinting.html#id2629412">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2637850">CUPS Backends</a></dt><dt>print quota, <a class="indexterm" href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></dt><dt>print server, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>print service, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>print spooling, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></dt><dt>print spooling system, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>print statistics, <a class="indexterm" href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></dt><dt>print subsystem, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2625360">Print Commands</a></dt><dt>print test page, <a class="indexterm" href="classicalprinting.html#id2629683">First Client Driver Installation</a></dt><dt>printcap, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#ptrsect">The [printers] Section</a></dt><dt>Printcap, <a class="indexterm" href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></dt><dt>printcap name, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>PrintcapFormat, <a class="indexterm" href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></dt><dt>printer attributes publishing, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>printer default permissions, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printer driver, <a class="indexterm" href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a>, <a class="indexterm" href="classicalprinting.html#id2626941">Creating the [print$] Share</a>, <a class="indexterm" href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a></dt><dt>printer driver data, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>printer driver file, <a class="indexterm" href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></dt><dt>printer driver files, <a class="indexterm" href="classicalprinting.html#id2628812">smbclient to Confirm Driver Installation</a></dt><dt>printer drivers, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="CUPS-printing.html#id2646382">The Grand Unification Achieved</a></dt><dt>printer icon, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>printer management, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>printer management system, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>printer migration, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>printer monitor, <a class="indexterm" href="speed.html#id2691160">Samba Performance is Very Slow</a></dt><dt>printer objects, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>Printer Pooling, <a class="indexterm" href="classicalprinting.html#id2631819">Samba and Printer Ports</a></dt><dt>printer queue, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printer share, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>printer shares , <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>printer$ share, <a class="indexterm" href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></dt><dt>printers, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>Printers, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>printers admin, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>Printers and Faxes, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>printers available, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>printers section, <a class="indexterm" href="classicalprinting.html#ptrsect">The [printers] Section</a></dt><dt>printing, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>printing behavior, <a class="indexterm" href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a></dt><dt>printing calls, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printing now, <a class="indexterm" href="speed.html#id2691160">Samba Performance is Very Slow</a></dt><dt>printing support, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>printing system, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>printing systems, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>printing-related settings, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dt>printing.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>PrintPro (see ESP Print Pro)</dt><dt>private dir, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>private groups, <a class="indexterm" href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></dt><dt>private key, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt><dt>private network, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a></dt><dt>private networks, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>private/MACHINE.SID, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></dt><dt>private/secrets.tdb, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></dt><dt>privilege, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>privilege management, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>privilege model, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a></dt><dt>privilege-granting applications, <a class="indexterm" href="pam.html#id2665655">Technical Discussion</a></dt><dt>privileged accounts, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>privileges, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>privileges assigned, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>problem report, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>problem resolution, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>problematic print, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>Process data management, <a class="indexterm" href="locking.html#id2616609">PDM Data Shares</a></dt><dt>professional support, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>profile, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>profile access rights, <a class="indexterm" href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></dt><dt>profile contents, <a class="indexterm" href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>profile directory, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>profile migration tool, <a class="indexterm" href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></dt><dt>profile path, <a class="indexterm" href="samba-bdc.html#id2566690">Example PDC Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="ProfileMgmt.html#id2661846">Windows NT4 Workstation</a></dt><dt>profile sharing, <a class="indexterm" href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>Profile Type, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a></dt><dt>ProfilePath, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>profiles, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>Profiles, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></dt><dt>project, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>promiscuous mode, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>promote, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a></dt><dt>promoted, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>propagate, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt><dt>Properties, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>protect directories, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>protect files, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>protection against attackers, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>protocol stack settings, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>provided services, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>provisioned, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>pstops, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a>, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>pstoraster, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>publish printers, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>publishing printers, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>PulseAudio, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>punching, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a></dt><dt>purchase support, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>put, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>pvcreate, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>QNX, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>qualified problem, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>queue control, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>quota controls, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>random machine account password, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>range, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dt>range of hosts, <a class="indexterm" href="securing-samba.html#id2618313">Using Host-Based Protection</a></dt><dt>RAP, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>raster, <a class="indexterm" href="CUPS-printing.html#id2636922">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>raster driver, <a class="indexterm" href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></dt><dt>raster drivers, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>raster image processor (see RIP)</dt><dt>raster images, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>rasterization, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a>, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>rastertoalps, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertobj, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertoepson, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a>, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>rastertoescp, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertohp, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertopcl, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertoprinter, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>rastertosomething, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>rastertoturboprint, <a class="indexterm" href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></dt><dt>raw mode, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>raw print, <a class="indexterm" href="CUPS-printing.html#id2643095">cupsaddsmb Flowchart</a></dt><dt>raw printers, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>raw printing, <a class="indexterm" href="FastStart.html#id2554849">Anonymous Print Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt><dt>raw SMB, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>raw SMB over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></dt><dt>rawprinter, <a class="indexterm" href="CUPS-printing.html#id2638506">Raw Printing</a></dt><dt>rcp, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>rdesktop, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>rdesktop/RDP, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>read, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>read directory into memory, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>read only, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dd><dl><dt>server, <a class="indexterm" href="FastStart.html#anon-ro">Anonymous Read-Only Document Server</a></dt></dl></dd><dt>Read-ahead, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>read-only, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>read-only access, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>read-only files, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>read-write access, <a class="indexterm" href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></dt><dt>realm, <a class="indexterm" href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-bdc.html#id2567578">NetBIOS Over TCP/IP Disabled</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></dt><dt>rebooted, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>rebooting server, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>recompiling, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>reconfiguration, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>record locking, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>recycle, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle bin, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>recycle directory, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:exclude, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:exclude_dir, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:keeptree, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:maxsize, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:noversions, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:repository, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:subdir_mode, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:touch, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>recycle:versions, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>Red Hat Cluster Manager, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>Red Hat Linux, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></dt><dt>redirect, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a></dt><dt>redirection, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>redirector, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>redundancy, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>reference documents, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>refusing connection, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a></dt><dt>regedit.exe, <a class="indexterm" href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></dt><dt>regedt32, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></dt><dt>regedt32.exe, <a class="indexterm" href="PolicyMgmt.html#id2660075">Windows NT4/200x</a></dt><dt>register driver files, <a class="indexterm" href="classicalprinting.html#id2628949">Running rpcclient with adddriver</a></dt><dt>register NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>registered, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>registers, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a></dt><dt>registry, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="locking.html#id2615570">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></dt><dt>registry change, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>registry keys, <a class="indexterm" href="ProfileMgmt.html#id2663192">Default Profile for Windows Users</a></dt><dt>registry settings, <a class="indexterm" href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></dt><dt>regulations, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>rejoin, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>relationship password, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>relative identifier, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a> (see RID)</dt><dt>Relative Identifier (see RID)</dt><dt>Relative Identifiers (see RID)</dt><dt>reliability, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>Remote Access Dial-In User Service (see RADIUS)</dt><dt>remote announce, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>remote browse sync, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>remote desktop capabilities, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>remote desktop management, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657636">Remote Desktop Management</a></dt><dt>remote domain, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>remote login, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>remote management, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></dt><dt>Remote Procedure Call (see RPC)</dt><dt>Remote Procedure Call System Service (see RPCSS)</dt><dt>remote profile, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>remote segment, <a class="indexterm" href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>Remote X, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>Remote X protocol, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>remote-update protocol, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>rename, <a class="indexterm" href="AccessControls.html#id2611105">Managing Directories</a></dt><dt>render, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>rendering, <a class="indexterm" href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>repeated intervals, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>replicate, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>replicated, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2567306">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></dt><dt>replicated SYSVOL, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></dt><dt>replication, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dd><dl><dt>browse lists, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>SAM, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a></dt><dt>WINS, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584196">WINS Replication</a></dt></dl></dd><dt>replication protocols, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>repository, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>requesting payment, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>required, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>requisite, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>research, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>resizing, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>resolution, <a class="indexterm" href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></dt><dt>resolution of NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a></dt><dt>resolve NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></dt><dt>resolver functions, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>resource failover, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>resource kit, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="ProfileMgmt.html#profilemigrn">Windows NT4 Profile Management Tools</a></dt><dt>resource-based exclusion, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>response, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></dt><dt>restore, <a class="indexterm" href="tdb.html#id2686735">Features and Benefits</a></dt><dt>restrict DNS, <a class="indexterm" href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></dt><dt>reviewers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>revoke privileges, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>RFC 1001, <a class="indexterm" href="DNSDHCP.html#id2692901">Example Configuration</a></dt><dt>RFC 1002, <a class="indexterm" href="DNSDHCP.html#id2692901">Example Configuration</a></dt><dt>RFC 1179, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>RFC 2307, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>RFC 2307., <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>RFC 2830, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>rfc2307bis, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>RFC2830, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>RFCs, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>rich database backend, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>rich directory backend, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>RID, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a>, <a class="indexterm" href="winbind.html#id2654327">User and Group ID Allocation</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>RID 500, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>RID base, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>right to join domain, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>rights, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a></dt><dt>rights and privilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></dt><dt>rights and privileges, <a class="indexterm" href="groupmapping.html#id2597278">Important Administrative Information</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>rights assigned, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>RIP, <a class="indexterm" href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>rlogind, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>Roaming Profile, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dt>roaming profiles, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="ProfileMgmt.html#id2660434">Features and Benefits</a>, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>rogue machine, <a class="indexterm" href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></dt><dt>rogue user, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>root, <a class="indexterm" href="domain-member.html#id2570630">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>root account, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>root user, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>rotate, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>RPC, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="ProfileMgmt.html#id2660484">Roaming Profiles</a></dt><dt>RPC calls, <a class="indexterm" href="winbind.html#id2657151">Conclusion</a>, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>RPC modules, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>rpc.lockd, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>rpcclient, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2629412">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a>, <a class="indexterm" href="PolicyMgmt.html#id2660115">Samba PDC</a></dt><dd><dl><dt>adddriver, <a class="indexterm" href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2643757">Understanding the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt><dt>enumdrivers, <a class="indexterm" href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt><dt>enumports, <a class="indexterm" href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a></dt><dt>enumprinters, <a class="indexterm" href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></dt><dt>getdriver, <a class="indexterm" href="CUPS-printing.html#id2643862">Producing an Example by Querying a Windows Box</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt><dt>getprinter, <a class="indexterm" href="CUPS-printing.html#id2643862">Producing an Example by Querying a Windows Box</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></dt><dt>setdriver, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></dt></dl></dd><dt>rsh, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>rsync, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a>, <a class="indexterm" href="Backup.html#id2671554">Rsync</a>, <a class="indexterm" href="compiling.html#id2687637">Accessing the Samba Sources via rsync and ftp</a></dt><dt>rsyncd, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>runas, <a class="indexterm" href="classicalprinting.html#id2630366">Always Make First Client Connection as root or printer admin</a></dt><dt>rundll32, <a class="indexterm" href="classicalprinting.html#id2630248">Additional Client Driver Installation</a>, <a class="indexterm" href="classicalprinting.html#id2630560">Setting Default Print Options for Client Drivers</a>, <a class="indexterm" href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658451">Adding Printers without User Intervention</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>SAM, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a>, <a class="indexterm" href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="winbind.html#id2654403">Result Caching</a></dt><dd><dl><dt>delta file, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>replication, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt></dl></dd><dt>SAM backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dd><dl><dt>LDAP, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt><dt>ldapsam, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>ldapsam_compat, <a class="indexterm" href="passdb.html#id2587269">Features and Benefits</a></dt><dt>non-LDAP, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt><dt>smbpasswd, <a class="indexterm" href="passdb.html#id2587269">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>tdbsam, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a></dt></dl></dd><dt>Samba 1.9.17, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>Samba account, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>Samba administrator, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>Samba backend database, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>Samba daemons, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>Samba differences, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>Samba mailing lists, <a class="indexterm" href="Backup.html#id2671241">Features and Benefits</a></dt><dt>Samba private directory, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>Samba SAM, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>Samba SAM account, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>Samba SAM account flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>Samba schema, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>Samba security, <a class="indexterm" href="securing-samba.html#id2618151">Features and Benefits</a></dt><dt>Samba-2.2.x LDAP schema, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></dt><dt>Samba-3-compatible LDAP backend, <a class="indexterm" href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></dt><dt>Samba-PDC-LDAP-HOWTO, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>samba-to-samba trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>samba-vscan, <a class="indexterm" href="VFS.html#id2652689">vscan</a></dt><dt>samba.schema, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>sambaDomain, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>sambaGroupMapping, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>sambaHomeDrive, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>sambaHomePath, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>sambaIdmapEntry, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>sambaLogonScript, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>SambaNTPassword, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>sambaProfilePath, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>SambaSAMAccount, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#id2591400">Adding User Accounts</a>, <a class="indexterm" href="passdb.html#id2591488">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a></dt><dt>sambaSamAccount, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a>, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>sambaSAMAccount, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>sambaSID, <a class="indexterm" href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></dt><dt>sambaUNIXIdPool, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>SambaXP conference, <a class="indexterm" href="SambaHA.html#id2671989">Technical Discussion</a></dt><dt>samdb interface, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>same domain/workgroup, <a class="indexterm" href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></dt><dt>Sarbanes-Oxley, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>scalability, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a></dt><dt>scalable, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>scalable backend, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a></dt><dt>scalable coherent interface (see SCI)</dt><dt>scale, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>scanner module, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>schannel, <a class="indexterm" href="samba-pdc.html#id2565594">Cannot Log onto Domain Member Workstation After Joining Domain</a></dt><dt>schema, <a class="indexterm" href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>schema file, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>scp, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>script, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>scripted control, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>scripts, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>SCSI, <a class="indexterm" href="SambaHA.html#id2672946">High-Availability Server Products</a></dt><dt>SeAddUsersPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>SeAssignPrimaryTokenPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeAuditPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeBackupPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeChangeNotifyPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>Seclib, <a class="indexterm" href="AccessControls.html#id2613583">Viewing File Ownership</a></dt><dt>secondary controller, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>SeCreateGlobalPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreatePagefilePrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreatePermanentPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreateTokenPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>secret, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>secrets.tdb, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>section name, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>secure, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>secure access, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>secure authentication, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>secure communications, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>secured networks, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a></dt><dt>security, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="securing-samba.html#id2618040">Introduction</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dd><dl><dt>controllers, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt><dt>modes, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a></dt><dt>settings, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt></dl></dd><dt>security = user, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>security account, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>Security Account Manager (see SAM)</dt><dt>Security Assertion Markup Language (see SAML)</dt><dt>security context, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>security contexts, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>security credentials, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a></dt><dt>security domain, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>security domains, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>security flaw, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>security hole, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>security identifier, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a> (see SID)</dt><dt>security level, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a></dt><dt>security levels, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a></dt><dt>security mode, <a class="indexterm" href="ServerType.html">Server Types and Security Modes</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>Security Mode, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a></dt><dt>security modes, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a></dt><dt>security name-space, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>security policies, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>security settings, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>security structure, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>security vulnerability, <a class="indexterm" href="securing-samba.html#id2619076">Upgrading Samba</a></dt><dt>security-aware, <a class="indexterm" href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></dt><dt>SeDebugPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeDiskOperatorPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>SeEnableDelegationPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeImpersonatePrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeIncreaseBasePriorityPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeIncreaseQuotaPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeLoadDriverPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeLockMemoryPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeMachineAccountPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeManageVolumePrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>separate instances, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>separate servers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>separate shares, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>separate workgroups, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>SePrintOperatorPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>SeProfileSingleProcessPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeRemoteShutdownPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeRestorePrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>server failure, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>Server Manager, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>Server Manager for Domains, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>Server Message Block (see SMB)</dt><dt>server pool, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a></dt><dt>Server Type, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a></dt><dd><dl><dt>Domain Controller, <a class="indexterm" href="FastStart.html#id2556806">Domain Controller</a></dt><dt>Domain Member, <a class="indexterm" href="FastStart.html#id2555963">Domain Member Server</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>Stand-alone, <a class="indexterm" href="FastStart.html#id2554221">Standalone Server</a></dt></dl></dd><dt>server type, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dd><dl><dt>domain member, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a></dt></dl></dd><dt>Server Types, <a class="indexterm" href="idmapper.html#id2604465">Samba Server Deployment Types and IDMAP</a></dt><dt>server-mode, <a class="indexterm" href="ServerType.html#id2560791">What Makes Samba a Domain Controller?</a></dt><dt>service name, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>service-level, <a class="indexterm" href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>services provided, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>SeSecurityPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeShutdownPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>session, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>session services, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>session setup, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a>, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a></dt><dt>sessionid.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>SessionSetupAndX, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>SeSyncAgentPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemEnvironmentPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemProfilePrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemtimePrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>set a password, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>set group id (see SGID)</dt><dt>set printer properties, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>set user id (see SUID)</dt><dt>SeTakeOwnershipPrivilege, <a class="indexterm" href="NetCommand.html#id2601333">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeTcbPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>setdriver, <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a></dt><dt>SetPrinter(), <a class="indexterm" href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></dt><dt>setting up directories, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>SeUndockPrivilege, <a class="indexterm" href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>severely impaired, <a class="indexterm" href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></dt><dt>SFU, <a class="indexterm" href="idmapper.html#id2608041">IDMAP, Active Directory, and MS Services for UNIX 3.5</a></dt><dt>SFU 3.5, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a></dt><dt>SGI-RGB, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>SGID, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>shadow, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dt>shadow copies, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>shadow password file, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>shadow utilities, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>shadow_copy, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a>, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>shadow_copy module, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a></dt><dt>share, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>share access, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>share ACLs, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>share management, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>share modes, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>share permissions, <a class="indexterm" href="AccessControls.html#id2613123">Windows NT4 Workstation/Server</a></dt><dt>Share Permissions, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>share settings, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>share stanza controls, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>share-level, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a>, <a class="indexterm" href="ServerType.html#id2559439">Share-Level Security</a>, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>share-level ACLs, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>share-mode, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>share-mode security, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>share-mode server, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>shared secret, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>shares, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>shares and files, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>share_info.tdb, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>Sharing, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>shell scripts, <a class="indexterm" href="classicalprinting.html#id2625360">Print Commands</a></dt><dt>shift, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>Shift_JIS, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>shortcuts, <a class="indexterm" href="ClientConfig.html#id2575612">TCP/IP Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>Shortcuts, <a class="indexterm" href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>show-stopper-type, <a class="indexterm" href="NT4Migration.html#id2678914">Planning and Getting Started</a></dt><dt>SID, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2565352">The System Cannot Log You On (C000019B)</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2606596">IDMAP_RID with Winbind</a>, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a>, <a class="indexterm" href="ProfileMgmt.html#id2662825">Side Bar Notes</a>, <a class="indexterm" href="ProfileMgmt.html#id2662917">Get SID</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a>, <a class="indexterm" href="NT4Migration.html#id2679791">Profile Migration/Creation</a></dt><dt>SID management, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>SID-to-GID, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a></dt><dt>SIDs, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>signing, <a class="indexterm" href="samba-pdc.html#id2565594">Cannot Log onto Domain Member Workstation After Joining Domain</a></dt><dt>simple access controls, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>simple configuration, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>simple guide, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>Simple Object Access Protocol (see SOAP)</dt><dt>simple operation, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>simple print server, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>simple printing, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>simplest</dt><dd><dl><dt>configuration, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt></dl></dd><dt>simplicity, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a></dt><dt>Simplicity is king, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>single DHCP server, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>single repository, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>single server, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>single sign-on, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a> (see SSO)</dt><dt>Single Sign-On, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>single-byte charsets, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>single-logon, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>single-sign-on, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>single-user mode, <a class="indexterm" href="winbind.html#id2654580">Requirements</a></dt><dt>slapadd, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a></dt><dt>slapd, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>slapd.conf, <a class="indexterm" href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>slapd.pem, <a class="indexterm" href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></dt><dt>slapindex, <a class="indexterm" href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></dt><dt>slappasswd, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a></dt><dt>slave servers, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>slow browsing, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>slow network, <a class="indexterm" href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>slow network browsing, <a class="indexterm" href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></dt><dt>slow performance, <a class="indexterm" href="speed.html#id2691160">Samba Performance is Very Slow</a></dt><dt>smart printers, <a class="indexterm" href="CUPS-printing.html#id2632962">Overview</a></dt><dt>SMB, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a>, <a class="indexterm" href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a>, <a class="indexterm" href="securing-samba.html#id2618527">Using Interface Protection</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a>, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a>, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>SMB encryption, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>SMB locks, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a></dt><dt>SMB name, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></dt><dt>SMB networking, <a class="indexterm" href="problems.html#id2684689">Diagnostics Tools</a></dt><dt>SMB password, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt><dt>SMB Password, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>SMB password encryption, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>smb ports, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>SMB printers, <a class="indexterm" href="CUPS-printing.html#id2649313">Administrator Cannot Install Printers for All Local Users</a></dt><dt>SMB requests, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>SMB semantics, <a class="indexterm" href="SambaHA.html#id2672471">The Distributed File System Challenge</a></dt><dt>SMB server, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>SMB Server, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>SMB services, <a class="indexterm" href="SambaHA.html#id2672598">Restrictive Constraints on Distributed File Systems</a></dt><dt>SMB signing, <a class="indexterm" href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>SMB state information, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>SMB-based messaging, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a></dt><dt>smb-cdserver.conf, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>smb.conf, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>SMB/CIFS, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a>, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>SMB/CIFS server, <a class="indexterm" href="passdb.html#id2592519">Password Backends</a></dt><dt>smbclient, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a>, <a class="indexterm" href="classicalprinting.html#id2628576">Installing Driver Files into [print$]</a>, <a class="indexterm" href="classicalprinting.html#id2628812">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>smbd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="install.html#id2553078">Example Configuration</a>, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2594059">Configuring Samba</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a>, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a>, <a class="indexterm" href="VFS.html#id2650921">extd_audit</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2654732">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="winbind.html#id2656126">Linux</a>, <a class="indexterm" href="winbind.html#id2656332">Solaris</a>, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>smbgroupedit, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>smbgrpadd.sh, <a class="indexterm" href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a></dt><dt>smbHome, <a class="indexterm" href="passdb.html#id2594833">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>smbldap-groupadd, <a class="indexterm" href="NetCommand.html#id2599601">Adding or Creating a New Group</a></dt><dt>smbldap-tools, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a></dt><dt>smbpasswd, <a class="indexterm" href="ServerType.html#id2559843">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2572129">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a>, <a class="indexterm" href="passdb.html#id2592394">Account Import/Export</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593073">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593375">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="PolicyMgmt.html#id2660115">Samba PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677993">Passdb Backends and Authentication</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678188">New Schema</a></dt><dt>smbpasswd format, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a></dt><dt>smbpasswd plaintext database, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>SMBsessetupX, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>smbspool, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dt>smbstatus, <a class="indexterm" href="CUPS-printing.html#id2649120">Avoid Being Connected to the Samba Server as the Wrong User</a>, <a class="indexterm" href="bugreport.html#id2686526">Attaching to a Running Process</a></dt><dt>SMBtconX, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a></dt><dt>smbusers, <a class="indexterm" href="securing-samba.html#id2618467">User-Based Protection</a></dt><dt>SMS, <a class="indexterm" href="problems.html#id2685190">The Windows Network Monitor</a></dt><dt>Snapshots, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>sniffer, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="problems.html#id2684689">Diagnostics Tools</a></dt><dt>socket, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>socket address, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>SOFTQ printing system, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>Solaris, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Solaris 9, <a class="indexterm" href="winbind.html#id2656332">Solaris</a></dt><dt>source code, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>space character, <a class="indexterm" href="groupmapping.html#id2598544">Adding Groups Fails</a></dt><dt>special account, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>special section, <a class="indexterm" href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></dt><dt>special sections, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>special stanza, <a class="indexterm" href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></dt><dt>specific restrictions, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>Specify an IP address, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>spinning process, <a class="indexterm" href="bugreport.html#id2686526">Attaching to a Running Process</a></dt><dt>spool, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dd><dl><dt>directory, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt></dl></dd><dt>spool files, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>spooled file, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>spooler., <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a></dt><dt>spooling, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></dt><dd><dl><dt>central, <a class="indexterm" href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></dt><dt>peer-to-peer, <a class="indexterm" href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></dt></dl></dd><dt>spooling path, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></dt><dt>spooling-only, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>SPOOLSS, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>SQL, <a class="indexterm" href="ChangeNotes.html#id2579095">Passdb Changes</a></dt><dt>SQUID, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>SRV records, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>SRV RR, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a></dt><dt>SrvMgr.exe, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>srvmgr.exe, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>SRVTOOLS.EXE, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>ssh, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>SSH, <a class="indexterm" href="classicalprinting.html#id2628812">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>SSL, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt><dt>SSO, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589125">Comments Regarding LDAP</a></dt><dt>stability, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>stack trace, <a class="indexterm" href="bugreport.html#id2686393">Internal Errors</a></dt><dt>stale network links, <a class="indexterm" href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></dt><dt>stand-alone server, <a class="indexterm" href="idmapper.html#id2604490">Standalone Samba Server</a></dt><dt>standalone, <a class="indexterm" href="ServerType.html#id2558970">Server Types</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>standalone filter, <a class="indexterm" href="CUPS-printing.html#id2637277">pstoraster</a></dt><dt>standalone server, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a>, <a class="indexterm" href="StandAloneServer.html#id2574171">Features and Benefits</a>, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="passdb.html#id2591400">Adding User Accounts</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679359">Domain Layout</a></dt><dt>standard confirmation, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></dt><dt>stanza, <a class="indexterm" href="install.html#id2551996">Configuration File Syntax</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>stapling, <a class="indexterm" href="CUPS-printing.html#id2637109">pstops</a></dt><dt>StartDocPrinter, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>starting samba</dt><dd><dl><dt>nmbd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a></dt><dt>smbd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2555213">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a></dt><dt>winbindd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a></dt></dl></dd><dt>startsmb, <a class="indexterm" href="compiling.html#id2688579">Alternative: Starting smbd as a Daemon</a></dt><dt>StartTLS, <a class="indexterm" href="passdb.html#id2594597">Security and sambaSamAccount</a></dt><dt>startup</dt><dd><dl><dt>process, <a class="indexterm" href="install.html#id2552898">Starting Samba</a></dt></dl></dd><dt>startup script, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>state, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>state information, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>state of knowledge, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>static WINS entries, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>status32 codes, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>sticky bit, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a>, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>storage mechanism, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>storage methods, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt><dt>stphoto2.ppd, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>strange delete semantics, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>stripped of comments, <a class="indexterm" href="SWAT.html#id2680929">Features and Benefits</a></dt><dt>strptime, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>stunnel, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt><dt>su, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>subnet mask, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>subnets, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>subscription, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>subsuffix parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2678581">New Suffix for Searching</a></dt><dt>Subversion, <a class="indexterm" href="compiling.html#id2687398">Introduction</a>, <a class="indexterm" href="compiling.html#id2687489">Access via Subversion</a></dt><dt>successful join, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>successful migration, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>sufficient, <a class="indexterm" href="pam.html#id2665788">Anatomy of /etc/pam.d Entries</a></dt><dt>suffixes, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>SUID, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>Sun, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>Sun ONE iDentity server, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>Sun Solaris, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>SUN-Raster, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>support, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>support exposure, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>SVN</dt><dd><dl><dt>web, <a class="indexterm" href="compiling.html#id2687453">Access via ViewCVS</a></dt></dl></dd><dt>SVRTOOLS.EXE, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>SWAT, <a class="indexterm" href="install.html#id2551954">Configuring Samba (smb.conf)</a>, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>swat, <a class="indexterm" href="install.html#id2553482">SWAT</a>, <a class="indexterm" href="SWAT.html#id2681073">Validate SWAT Installation</a>, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a>, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dd><dl><dt>enable, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>security, <a class="indexterm" href="SWAT.html#id2681711">Securing SWAT through SSL</a></dt></dl></dd><dt>SWAT binary support, <a class="indexterm" href="SWAT.html#id2681073">Validate SWAT Installation</a></dt><dt>swat command-line options, <a class="indexterm" href="SWAT.html#id2681144">Locating the SWAT File</a></dt><dt>SWAT permission allowed, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>symbolic links, <a class="indexterm" href="msdfs.html#id2621432">Features and Benefits</a></dt><dt>synchronization, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>synchronization problems, <a class="indexterm" href="winbind.html#id2653341">Introduction</a></dt><dt>synchronize, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>synchronized, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></dt><dt>syntax tolerates spelling errors, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a></dt><dt>system access controls, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a></dt><dt>system accounts, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a></dt><dt>system administrator, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>system groups, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>system interface scripts, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>system policies, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></dt><dt>System Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659500">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></dt><dt>system security, <a class="indexterm" href="groupmapping.html#id2597397">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>system tools, <a class="indexterm" href="Backup.html#id2671241">Features and Benefits</a></dt><dt>SYSV, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>SYSVOL, <a class="indexterm" href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>tail, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a></dt><dt>take ownership, <a class="indexterm" href="rights.html#id2609060">Description of Privileges</a></dt><dt>Take Ownership, <a class="indexterm" href="AccessControls.html#id2613583">Viewing File Ownership</a></dt><dt>tape, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>tar, <a class="indexterm" href="Backup.html#id2671383">BackupPC</a></dt><dt>tarball, <a class="indexterm" href="install.html#id2553078">Example Configuration</a></dt><dt>tattoo effect, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>TCP, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a>, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>TCP data streams, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a></dt><dt>TCP failover, <a class="indexterm" href="SambaHA.html#id2672152">Why Is This So Hard?</a></dt><dt>TCP port, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>TCP port 139, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>TCP port 445, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dt>tcp ports, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>TCP/IP, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>TCP/IP configuration, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>TCP/IP configuration panel, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>TCP/IP protocol configuration, <a class="indexterm" href="ClientConfig.html#id2575568">Technical Details</a></dt><dt>TCP/IP protocol settings, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>TCP/IP protocol stack, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>TCP/IP-only, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></dt><dt>tcpdump, <a class="indexterm" href="problems.html#id2684997">Tcpdump</a></dt><dt>TDB, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a>, <a class="indexterm" href="classicalprinting.html#id2629526">Running rpcclient with setdriver</a>, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a>, <a class="indexterm" href="CUPS-printing.html#id2645523">Trivial Database Files</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dd><dl><dt>backing up (see tdbbackup)</dt></dl></dd><dt>tdb, <a class="indexterm" href="winbind.html#id2654327">User and Group ID Allocation</a>, <a class="indexterm" href="SambaHA.html#id2672668">Server Pool Communications</a>, <a class="indexterm" href="tdb.html#id2686735">Features and Benefits</a></dt><dt>tdb data files, <a class="indexterm" href="upgrading-to-3.0.html#id2677545">TDB Data Files</a></dt><dt>TDB database, <a class="indexterm" href="classicalprinting.html#id2628949">Running rpcclient with adddriver</a></dt><dt>TDB database files, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>tdb file backup, <a class="indexterm" href="upgrading-to-3.0.html#id2677545">TDB Data Files</a></dt><dt>tdb file descriptions, <a class="indexterm" href="install.html#tdbdocs">TDB Database File Information</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677545">TDB Data Files</a></dt><dt>tdb file locations, <a class="indexterm" href="install.html#tdbdocs">TDB Database File Information</a></dt><dt>tdb files, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>tdbbackup, <a class="indexterm" href="CUPS-printing.html#id2645708">Using tdbbackup</a>, <a class="indexterm" href="speed.html#id2691064">Corrupt tdb Files</a></dt><dt>tdbdump, <a class="indexterm" href="AccessControls.html#id2612964">Access Controls on Shares</a></dt><dt>tdbsam, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2592915">tdbsam</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>tdbsam databases, <a class="indexterm" href="passdb.html#id2592519">Password Backends</a></dt><dt>technical reviewers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>Telnet, <a class="indexterm" href="passdb.html#id2588513">Advantages of Non-Encrypted Passwords</a></dt><dt>telnet logins, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>template, <a class="indexterm" href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></dt><dt>temporary location, <a class="indexterm" href="classicalprinting.html#id2625360">Print Commands</a></dt><dt>terminal server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>Terminal Server, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>Testing Server Setup, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>testparm, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="classicalprinting.html#id2622610">Simple Print Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a>, <a class="indexterm" href="classicalprinting.html#id2623480">Extended Printing Configuration</a>, <a class="indexterm" href="diagnosis.html#id2682648">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a>, <a class="indexterm" href="problems.html#id2684741">Debugging with Samba Itself</a></dt><dt>tethereal, <a class="indexterm" href="problems.html#id2684997">Tcpdump</a></dt><dt>text/plain, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>texttops, <a class="indexterm" href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></dt><dt>thin client, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>ThinLinc, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>tid, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt><dt>TIFF, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>TightVNC, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>time difference, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></dt><dt>time format, <a class="indexterm" href="passdb.html#id2591572">Changing User Accounts</a></dt><dt>time-to-live (see TTL)</dt><dt>tool, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>tools, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a></dt><dt>tools\reskit\netadmin\poledit, <a class="indexterm" href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></dt><dt>traditional printing, <a class="indexterm" href="classicalprinting.html#id2625981">Custom Print Commands</a></dt><dt>training course, <a class="indexterm" href="Backup.html#id2671286">Discussion of Backup Solutions</a></dt><dt>transfer differences, <a class="indexterm" href="Backup.html#id2671554">Rsync</a></dt><dt>transformation, <a class="indexterm" href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></dt><dt>transitive, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>transparent access, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>transparently reconnected, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>transport connection loss, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Transport Layer Seccurity, TLS</dt><dd><dl><dt>Configuring, <a class="indexterm" href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></dt><dt>Introduction, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt></dl></dd><dt>transport layer security (see TLS)</dt><dt>Transport Layer Security, TLS</dt><dd><dl><dt>Testing, <a class="indexterm" href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></dt><dt>Troubleshooting, <a class="indexterm" href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></dt></dl></dd><dt>trigger, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>trivial database, <a class="indexterm" href="passdb.html#id2587489">New Account Storage Systems</a> (see TDB)</dt><dt>Trivial Database, <a class="indexterm" href="tdb.html#id2686735">Features and Benefits</a></dt><dt>troubleshoot, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>troubleshooting, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dt>Tru64 UNIX, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>trust, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dd><dl><dt>account, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>trust account, <a class="indexterm" href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dd><dl><dt>interdomain, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt><dt>machine, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a></dt></dl></dd><dt>trust account password, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt><dt>trust accounts, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a></dt><dt>trust established, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></dt><dt>trust relationship, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>trust relationships, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619731">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>trusted, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>trusted domain, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a>, <a class="indexterm" href="winbind.html#id2653940">Name Service Switch</a></dt><dt>trusted domain name, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusted party, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusting domain, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></dt><dt>trusting party, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>TTL, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>turn oplocks off, <a class="indexterm" href="locking.html#id2616767">Advanced Samba Oplocks Parameters</a></dt><dt>turnkey solution, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dt>two-up, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>two-way</dt><dd><dl><dt>propagation, <a class="indexterm" href="samba-bdc.html#id2565778">Features and Benefits</a></dt></dl></dd><dt>two-way trust, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UCS-2, <a class="indexterm" href="unicode.html#id2670088">Japanese Charsets</a></dt><dt>UDP, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></dt><dt>UDP port 137, <a class="indexterm" href="integrate-ms-networks.html#id2667945">Background Information</a></dt><dt>udp ports, <a class="indexterm" href="winbind.html#id2655528">Join the Samba Server to the PDC Domain</a></dt><dt>UDP unicast, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>UID, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2591165">Listing User and Machine Accounts</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605504">Primary Domain Controller</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653629">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>uid, <a class="indexterm" href="passdb.html#id2593602">OpenLDAP Configuration</a></dt><dt>UID numbers, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></dt><dt>UID range, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>unauthorized, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>unauthorized access, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>UNC notation, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>unexpected.tdb, <a class="indexterm" href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>unicast, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></dt><dt>unicode, <a class="indexterm" href="unicode.html#id2669787">What Are Charsets and Unicode?</a></dt><dt>Unicode, <a class="indexterm" href="unicode.html#id2669921">Samba and Charsets</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>Unicode UTF-8, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>unified logon, <a class="indexterm" href="winbind.html#id2653341">Introduction</a></dt><dt>UNIX, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dd><dl><dt>server, <a class="indexterm" href="ServerType.html#id2558810">Features and Benefits</a></dt></dl></dd><dt>UNIX account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>unix charset, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>UNIX Domain Socket, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>UNIX domain socket, <a class="indexterm" href="winbind.html#id2653755">How Winbind Works</a></dt><dt>UNIX file system access controls, <a class="indexterm" href="AccessControls.html#id2610562">Features and Benefits</a></dt><dt>UNIX group, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>UNIX groups, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>UNIX home directories, <a class="indexterm" href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></dt><dt>UNIX host system, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>UNIX ID, <a class="indexterm" href="winbind.html#id2654327">User and Group ID Allocation</a></dt><dt>UNIX locking, <a class="indexterm" href="locking.html#id2615667">Discussion</a></dt><dt>UNIX login ID, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>UNIX permissions, <a class="indexterm" href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></dt><dt>UNIX printer, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>UNIX printing, <a class="indexterm" href="classicalprinting.html#id2622298">Technical Introduction</a></dt><dt>UNIX system account, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></dt><dt>UNIX system accounts, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>UNIX system files, <a class="indexterm" href="Backup.html#id2671241">Features and Benefits</a></dt><dt>UNIX user identifier (see UID)</dt><dt>UNIX users, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>UNIX-style encrypted passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>UNIX-user database, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a></dt><dt>UNIX/Linux group, <a class="indexterm" href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></dt><dt>UNIX/Linux user account, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dt>unlink calls, <a class="indexterm" href="VFS.html#id2651247">recycle</a></dt><dt>unlinked, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>unmapped groups, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a></dt><dt>unmapped users, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a></dt><dt>unprivileged account names, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>unsigned drivers, <a class="indexterm" href="CUPS-printing.html#id2649280">Windows 200x/XP Local Security Policies</a></dt><dt>unstoppable services, <a class="indexterm" href="SambaHA.html#id2672023">The Ultimate Goal</a></dt><dt>unsupported encryption, <a class="indexterm" href="domain-member.html#id2573121">Possible Errors</a></dt><dt>unsupported software, <a class="indexterm" href="ch47.html#id2692569">Commercial Support</a></dt><dt>updates, <a class="indexterm" href="securing-samba.html#id2619076">Upgrading Samba</a></dt><dt>upload drivers, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>uploaded driver, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>uploaded drivers, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>uploading, <a class="indexterm" href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>upper-case, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a></dt><dt>uppercase, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573808">Adding Machine to Domain Fails</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>uppercase character, <a class="indexterm" href="groupmapping.html#id2598544">Adding Groups Fails</a></dt><dt>USB, <a class="indexterm" href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></dt><dt>use computer anywhere, <a class="indexterm" href="unicode.html#id2669736">Features and Benefits</a></dt><dt>user, <a class="indexterm" href="ChangeNotes.html#id2578661">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>user access management, <a class="indexterm" href="domain-member.html#id2569109">Features and Benefits</a></dt><dt>user account, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2591049">User Account Management</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dd><dl><dt>Adding/Deleting, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt></dl></dd><dt>user account database, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>user accounts, <a class="indexterm" href="passdb.html#id2589401">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>User Accounts</dt><dd><dl><dt>Adding/Deleting, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a></dt></dl></dd><dt>user and group, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>user and trust accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>user attributes, <a class="indexterm" href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></dt><dt>user authentication, <a class="indexterm" href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></dt><dt>user database, <a class="indexterm" href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2592573">Plaintext</a></dt><dt>user encoded, <a class="indexterm" href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></dt><dt>user groups, <a class="indexterm" href="ch47.html#id2692350">Free Support</a></dt><dt>user logons, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>user management, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a>, <a class="indexterm" href="NetCommand.html#id2599025">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></dt><dt>User Management, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2594484">Accounts and Groups Management</a></dt><dt>User Manager, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a>, <a class="indexterm" href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></dt><dt>User Manager for Domains, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>user or group, <a class="indexterm" href="rights.html#id2608715">Using the net rpc rights Utility</a></dt><dt>user profiles, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>User Rights and Privileges, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>user-level, <a class="indexterm" href="ServerType.html#id2559114">Samba Security Modes</a>, <a class="indexterm" href="ServerType.html#id2559276">User Level Security</a></dt><dt>User-level access control, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>user-level security, <a class="indexterm" href="passdb.html#id2588373">Advantages of Encrypted Passwords</a></dt><dt>user-mode security, <a class="indexterm" href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></dt><dt>user.DAT, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>user.MAN, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>User.MAN, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>useradd, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>username, <a class="indexterm" href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></dt><dt>username and password, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>username map, <a class="indexterm" href="NetCommand.html#id2601250">User Mapping</a></dt><dt>userPassword, <a class="indexterm" href="passdb.html#id2593874">Initialize the LDAP Database</a></dt><dt>users, <a class="indexterm" href="PolicyMgmt.html#id2658637">Features and Benefits</a></dt><dt>UsrMgr.exe, <a class="indexterm" href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>UTF-8, <a class="indexterm" href="unicode.html#id2669921">Samba and Charsets</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>UTF-8 encoding, <a class="indexterm" href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid username/password, <a class="indexterm" href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></dt><dt>valid users, <a class="indexterm" href="diagnosis.html#id2682941">The Tests</a></dt><dt>validate, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a>, <a class="indexterm" href="diagnosis.html#id2682610">Introduction</a></dt><dt>validate every backup, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>validation, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a>, <a class="indexterm" href="PolicyMgmt.html">System and Account Policies</a></dt><dt>vendor-provided drivers, <a class="indexterm" href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>verifiable, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a></dt><dt>verify, <a class="indexterm" href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></dt><dt>version control, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a></dt><dt>VFS, <a class="indexterm" href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a>, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>VFS module, <a class="indexterm" href="VFS.html#id2651694">shadow_copy</a>, <a class="indexterm" href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></dt><dt>VFS modules, <a class="indexterm" href="VFS.html#id2650261">Discussion</a>, <a class="indexterm" href="VFS.html#id2652604">VFS Modules Available Elsewhere</a></dt><dt>vgcreate, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>vgdisplay, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>vipw, <a class="indexterm" href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></dt><dt>Virtual File System (see VFS)</dt><dt>virtual server, <a class="indexterm" href="SambaHA.html#id2672271">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672866">A Simple Solution</a></dt><dt>virus scanner, <a class="indexterm" href="VFS.html#id2650261">Discussion</a></dt><dt>Visual Studio, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a></dt><dt>vital task, <a class="indexterm" href="SambaHA.html#id2671868">Features and Benefits</a></dt><dt>VNC/RFB, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>volume group, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>volunteers, <a class="indexterm" href="problems.html#id2685560">Getting Mailing List Help</a></dt><dt>vscan, <a class="indexterm" href="VFS.html#id2652689">vscan</a></dt><dt>vuid, <a class="indexterm" href="SambaHA.html#id2672366">Demultiplexing SMB Requests</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>W32X86, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>W32X86/2, <a class="indexterm" href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a></dt><dt>WAN, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="locking.html#id2616521">Slow and/or Unreliable Networks</a></dt><dt>wbinfo, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>Web-based configuration, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>WebClient, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>Welcome, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>well known RID, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>well-controlled network, <a class="indexterm" href="NT4Migration.html#id2679560">Server Share and Directory Layout</a></dt><dt>well-known RID, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></dt><dt>wide-area network bandwidth, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>win election, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></dt><dt>Win32 printing API, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>WIN40, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2628430">Obtaining Driver Files from Windows Client [print$] Shares</a>, <a class="indexterm" href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></dt><dt>winbind, <a class="indexterm" href="domain-member.html#id2571847">Why Is This Better Than security = server?</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a>, <a class="indexterm" href="idmapper.html#id2605898">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655330">Configure smb.conf</a></dt><dt>Winbind, <a class="indexterm" href="StandAloneServer.html#id2574265">Background</a>, <a class="indexterm" href="winbind.html#id2653584">Target Uses</a>, <a class="indexterm" href="winbind.html#id2653892">Microsoft Active Directory Services</a>, <a class="indexterm" href="winbind.html#id2654172">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654327">User and Group ID Allocation</a>, <a class="indexterm" href="winbind.html#id2654403">Result Caching</a>, <a class="indexterm" href="winbind.html#id2654466">Introduction</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2655217">NSS Winbind on AIX</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="winbind.html#id2656687">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="winbind.html#id2657151">Conclusion</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt><dt>Winbind architecture, <a class="indexterm" href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></dt><dt>Winbind hooks, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>Winbind services, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a></dt><dt>Winbind-based authentication, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a></dt><dt>winbind.so, <a class="indexterm" href="winbind.html#id2657034">Solaris-Specific Configuration</a></dt><dt>winbindd, <a class="indexterm" href="install.html#id2552898">Starting Samba</a>, <a class="indexterm" href="install.html#id2553312">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2556037">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568138">Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="groupmapping.html#id2595892">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2652992">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653755">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2654580">Requirements</a>, <a class="indexterm" href="winbind.html#id2654732">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2654819">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2655330">Configure smb.conf</a>, <a class="indexterm" href="winbind.html#id2655765">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="winbind.html#id2656332">Solaris</a>, <a class="indexterm" href="winbind.html#id2656521">Configure Winbind and PAM</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></dt><dt>winbindd daemon, <a class="indexterm" href="winbind.html#id2656126">Linux</a></dt><dt>Windows, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="unicode.html#id2670218">Basic Parameter Setting</a></dt><dt>Windows 2000, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></dt><dt>Windows 2000 Professional TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>Windows 2000 server, <a class="indexterm" href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>Windows 2003, <a class="indexterm" href="domain-member.html#id2572320">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a></dt><dt>Windows 200x/XP, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>Windows 9x/Me, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></dt><dt>Windows 9x/Me/XP Home, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Windows account management, <a class="indexterm" href="winbind.html#id2653431">What Winbind Provides</a></dt><dt>Windows client, <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Windows client failover, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>Windows domain, <a class="indexterm" href="upgrading-to-3.0.html#id2677897">Changes in Behavior</a></dt><dt>Windows Explorer, <a class="indexterm" href="NetworkBrowsing.html#id2585120">Problem Resolution</a>, <a class="indexterm" href="classicalprinting.html#id2627996">Identifying Driver Files</a></dt><dt>Windows group, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2596644">Warning: User Private Group Problems</a>, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows group account, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>Windows groups, <a class="indexterm" href="NetCommand.html#id2599802">Mapping Windows Groups to UNIX Groups</a></dt><dt>Windows Internet Name Server (see WINS)</dt><dt>Windows Logon, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>Windows Me TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>Windows Millennium, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>Windows Millennium edition (Me) TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>Windows network clients, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a></dt><dt>Windows NT domain name, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Windows NT PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></dt><dt>Windows NT Server, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>Windows NT/2000/XP, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>Windows NT/200x, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="winbind.html#id2654466">Introduction</a></dt><dt>Windows NT/200x/XP, <a class="indexterm" href="classicalprinting.html#id2623959">The [global] Section</a></dt><dt>Windows NT/200x/XP Professional, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2578353">Common Errors</a></dt><dt>Windows NT3.10, <a class="indexterm" href="samba-bdc.html#id2566184">Essential Background Information</a></dt><dt>Windows NT4, <a class="indexterm" href="AccessControls.html#id2613123">Windows NT4 Workstation/Server</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>Windows NT4 domains, <a class="indexterm" href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></dt><dt>Windows NT4 Server, <a class="indexterm" href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></dt><dt>Windows NT4/200X, <a class="indexterm" href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></dt><dt>Windows NT4/200x, <a class="indexterm" href="groupmapping.html#id2596308">Discussion</a></dt><dt>Windows NT4/200x/XP, <a class="indexterm" href="samba-bdc.html#id2567512">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="AccessControls.html#id2613228">Windows 200x/XP</a></dt><dt>Windows NT4/2kX/XPPro, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows PPD, <a class="indexterm" href="CUPS-printing.html#id2646072">690 Perfect Printers</a></dt><dt>Windows privilege model, <a class="indexterm" href="rights.html#id2608440">Rights Management Capabilities</a></dt><dt>Windows Registry, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>windows registry settings, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dd><dl><dt>default profile locations, <a class="indexterm" href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>profile path, <a class="indexterm" href="ProfileMgmt.html#id2661150">Windows 9x/Me Profile Setup</a></dt><dt>roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a></dt></dl></dd><dt>Windows Resource Kit, <a class="indexterm" href="ProfileMgmt.html#id2660923">Disabling Roaming Profile Support</a></dt><dt>Windows Security Identifiers (see SID)</dt><dt>Windows Terminal server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></dt><dt>Windows Terminal Server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></dt><dt>Windows user, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows user accounts, <a class="indexterm" href="NetCommand.html#id2600921">UNIX and Windows User Management</a></dt><dt>Windows workstation., <a class="indexterm" href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Windows XP Home, <a class="indexterm" href="passdb.html#id2588057">Important Notes About Security</a></dt><dt>Windows XP Home edition, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2564467">The Special Case of MS Windows XP Home Edition</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Windows XP Home Edition, <a class="indexterm" href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></dt><dt>Windows XP Professional, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="classicalprinting.html#id2622075">Features and Benefits</a></dt><dt>Windows XP Professional TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a></dt><dt>Windows XP TCP/IP, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a></dt><dt>Windows95/98/ME, <a class="indexterm" href="classicalprinting.html#id2629176">Check Samba for Driver Recognition</a></dt><dt>winnt.adm, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>WINS, <a class="indexterm" href="samba-pdc.html#id2561237">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562480">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="ClientConfig.html#id2575687">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576331">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579538">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585549">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669301">WINS Lookup</a>, <a class="indexterm" href="DNSDHCP.html#id2692901">Example Configuration</a></dt><dt>wins, <a class="indexterm" href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></dt><dt>WINS Configuration, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>WINS lookup, <a class="indexterm" href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></dt><dt>WINS replication, <a class="indexterm" href="NetworkBrowsing.html#id2584196">WINS Replication</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>WINS Server, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>WINS server, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></dt><dt>WINS server address, <a class="indexterm" href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></dt><dt>WINS server settings, <a class="indexterm" href="ClientConfig.html#id2576877">MS Windows Me</a></dt><dt>WINS servers, <a class="indexterm" href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></dt><dt>WINS service, <a class="indexterm" href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></dt><dt>WINS Support, <a class="indexterm" href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></dt><dt>wins.dat, <a class="indexterm" href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></dt><dt>without Administrator account, <a class="indexterm" href="rights.html#id2609882">The Administrator Domain SID</a></dt><dt>without ADS, <a class="indexterm" href="NT4Migration.html#id2678949">Objectives</a></dt><dt>work-flow protocol, <a class="indexterm" href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></dt><dt>workgroup, <a class="indexterm" href="ServerType.html#id2560266">Server Security (User Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564506">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="cfgsmarts.html#id2673763">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></dt><dd><dl><dt>membership, <a class="indexterm" href="samba-pdc.html#id2562984">Preparing for Domain Control</a></dt></dl></dd><dt>workstations, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>world-writable, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>write, <a class="indexterm" href="AccessControls.html#id2611229">File and Directory Access Control</a></dt><dt>write access, <a class="indexterm" href="AccessControls.html#id2611627">Protecting Directories and Files from Deletion</a></dt><dt>Write caching, <a class="indexterm" href="locking.html#id2615926">Opportunistic Locking Overview</a></dt><dt>write changes, <a class="indexterm" href="idmapper.html#id2605739">Backup Domain Controller</a></dt><dt>write permission, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>writeable, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dt>WYSIWYG, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X Window
-	System, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>X.509 certificates, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>XFS file system, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>xfsprogs, <a class="indexterm" href="VFS.html#id2651883">Shadow Copy Setup</a></dt><dt>xinetd, <a class="indexterm" href="SWAT.html#id2681073">Validate SWAT Installation</a>, <a class="indexterm" href="compiling.html#id2688359">Starting from inetd.conf</a> (see inetd)</dt><dt>XML, <a class="indexterm" href="ChangeNotes.html#id2579095">Passdb Changes</a></dt><dt>XML-based datasets, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>xpp, <a class="indexterm" href="CUPS-printing.html#id2646698">Foomatic Database-Generated PPDs</a></dt><dt>Xprint, <a class="indexterm" href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></dt><dt>xxxxBSD, <a class="indexterm" href="pam.html#id2665025">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>yppasswd, <a class="indexterm" href="passdb.html#id2589979">The smbpasswd Tool</a></dt></dl></div><div class="indexdiv"><h3>Z</h3><dl><dt>Zero Administration Kit, <a class="indexterm" href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></dt><dt>zero-based broadcast, <a class="indexterm" href="NetworkBrowsing.html#id2583156">Note about Broadcast Addresses</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�</td></tr><tr><td width="40%" align="left" valign="top">Glossary�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="go01.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2695463"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>"Printers" folder, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt><dt>$, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>%i macro, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>%L, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>%PDF, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>%SystemRoot%\System32\config, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>../source/nsswitch, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a></dt><dt>.ai, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>.AppleDouble, <a class="indexterm" href="VFS.html#id2651783">netatalk</a></dt><dt>.eps, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>.pdf, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>.PDS extension, <a class="indexterm" href="ProfileMgmt.html#id2661970">Windows NT4 Workstation</a></dt><dt>.profiles, <a class="indexterm" href="ProfileMgmt.html#id2660807">Windows 9x/Me User Profiles</a></dt><dt>.ps, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>.recycle, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>/bin/false, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>/dev/null, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>/dev/shadowvol, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>/etc/cups/, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>/etc/cups/mime.convs, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>/etc/cups/mime.types, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>/etc/fstab, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>/etc/group, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a>, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="Portability.html#id2689108">HPUX</a></dt><dt>/etc/groups, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>/etc/host.conf, <a class="indexterm" href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668506">/etc/host.conf</a></dt><dt>/etc/hosts, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>/etc/hosts&gt;, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>/etc/inetd.conf, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="compiling.html#id2688504">Starting from inetd.conf</a></dt><dt>/etc/init.d/samba, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="winbind.html#id2656259">Linux</a></dt><dt>/etc/init.d/samba.server, <a class="indexterm" href="winbind.html#id2656465">Solaris</a></dt><dt>/etc/init.d/smb, <a class="indexterm" href="winbind.html#id2656259">Linux</a></dt><dt>/etc/krb5.conf, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>/etc/ldap.conf, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>/etc/logingroup, <a class="indexterm" href="Portability.html#id2689108">HPUX</a></dt><dt>/etc/mime.conv, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>/etc/mime.types, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>/etc/nsswitch.conf, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></dt><dt>/etc/openldap/slapd.conf, <a class="indexterm" href="FastStart.html#id2557694">The Primary Domain Controller</a></dt><dt>/etc/openldap/sldap.conf, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a></dt><dt>/etc/pam.conf, <a class="indexterm" href="winbind.html#id2657167">Solaris-Specific Configuration</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="pam.html#id2665783">Technical Discussion</a>, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>/etc/pam.d, <a class="indexterm" href="winbind.html#id2654713">Requirements</a>, <a class="indexterm" href="winbind.html#id2654865">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>/etc/pam.d/, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a>, <a class="indexterm" href="pam.html#id2665783">Technical Discussion</a></dt><dt>/etc/pam.d/ftp, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/pam.d/login, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/pam.d/samba, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/passwd, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a>, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a>, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>/etc/printcap, <a class="indexterm" href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></dt><dt>/etc/resolv.conf, <a class="indexterm" href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a>, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>/etc/samba, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>/etc/samba/scripts, <a class="indexterm" href="NetCommand.html#id2600610">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>/etc/samba/secrets.tdb, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>/etc/samba/smb.conf, <a class="indexterm" href="install.html#id2551950">Configuring Samba (smb.conf)</a></dt><dt>/etc/samba/smbpasswd, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a></dt><dt>/etc/samba/smbusers, <a class="indexterm" href="NetCommand.html#id2601237">User Mapping</a></dt><dt>/etc/shadow, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>/etc/smbpasswd, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a></dt><dt>/etc/ssl/certs/slapd.pem, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>/etc/xinetd.d, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/etc/xinetd.d/telnet, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>/export, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>/lib/libnss_example.so, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>/lib/libnss_files.so, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>/lib/security, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665836">PAM Configuration Syntax</a></dt><dt>/lib/security/, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>/opt/samba/bin, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a></dt><dt>/tmp, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>/usr/bin/openssl, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt><dt>/usr/lib/samba/vfs, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>/usr/lib/security, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a></dt><dt>/usr/lib/security/methods.cfg, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a></dt><dt>/usr/local/lib, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>/usr/local/samba, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>/usr/local/samba/bin, <a class="indexterm" href="winbind.html#id2656259">Linux</a>, <a class="indexterm" href="winbind.html#id2656465">Solaris</a>, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a></dt><dt>/usr/local/samba/lib, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>/usr/local/samba/lib/vfs, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>/usr/local/samba/private/secrets.tdb, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>/usr/local/samba/swat, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/usr/local/samba/var, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a>, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>/usr/local/samba/var/locks, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>/usr/sbin, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a>, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/usr/share/samba/swat, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>/var/locks/*.tdb, <a class="indexterm" href="speed.html#id2691200">Corrupt tdb Files</a></dt><dt>/var/log/samba, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>/var/run/samba, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>/var/spool/cups/, <a class="indexterm" href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>/var/spool/samba, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>250-user limit, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a></dt><dt>3.0.11, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>4,500 user accounts, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a></dt><dt>4294967295, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>8.3 file names, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>&gt;Domain User Manager, <a class="indexterm" href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></dt><dt>\\%L\%U\.profiles, <a class="indexterm" href="ProfileMgmt.html#id2660807">Windows 9x/Me User Profiles</a></dt><dt>\\SERVER, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>_kerberos.REALM.NAME, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>_kerberos._udp, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>_ldap._tcp, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>_ldap._tcp.pdc._msdcs.quenya.org, <a class="indexterm" href="samba-bdc.html#id2567576">NetBIOS Over TCP/IP Disabled</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt>, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="install.html#id2553073">Example Configuration</a>, <a class="indexterm" href="FastStart.html#anon-ro">Anonymous Read-Only Document Server</a>, <a class="indexterm" href="FastStart.html#id2554632">Anonymous Read-Write Document Server</a>, <a class="indexterm" href="FastStart.html#id2554843">Anonymous Print Server</a>, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="FastStart.html#id2556880">Example: Engineering Office</a>, <a class="indexterm" href="FastStart.html#id2557694">The Primary Domain Controller</a>, <a class="indexterm" href="FastStart.html#id2558311">Backup Domain Controller</a>, <a class="indexterm" href="ServerType.html#id2559396">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559593">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560193">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560441">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564355">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566688">Example PDC Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570875">Samba Client</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583338">Use of the Remote Announce Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2594040">Configuring Samba</a>, <a class="indexterm" href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="NetCommand.html#id2600610">Managing Nest Groups on Workstations from the Samba Server</a>, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2614107">Interaction with the Standard Samba create mask Parameters</a>, <a class="indexterm" href="AccessControls.html#id2614980">Users Cannot Write to a Public Share</a>, <a class="indexterm" href="AccessControls.html#id2615348">MS Word with Samba Changes Owner of File</a>, <a class="indexterm" href="locking.html#id2617050">Disabling Oplocks</a>, <a class="indexterm" href="locking.html#id2617145">Disabling Kernel Oplocks</a>, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a>, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618497">User-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a>, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a>, <a class="indexterm" href="msdfs.html#id2621920">MSDFS UNIX Path Is Case-Critical</a>, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a>, <a class="indexterm" href="classicalprinting.html#id2623534">Extended Printing Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a>, <a class="indexterm" href="classicalprinting.html#id2626995">Creating the [print$] Share</a>, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2633768">More Complex CUPS smb.conf Settings</a>, <a class="indexterm" href="CUPS-printing.html#id2640522">From Windows Clients to a CUPS/Samba Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2641316">Prepare Your smb.conf for cupsaddsmb</a>, <a class="indexterm" href="VFS.html#id2650401">Discussion</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655464">Configure smb.conf</a>, <a class="indexterm" href="winbind.html#id2656259">Linux</a>, <a class="indexterm" href="winbind.html#id2657167">Solaris-Specific Configuration</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="ProfileMgmt.html#id2660668">NT4/200x User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2660807">Windows 9x/Me User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2660965">Mixed Windows Windows 9x/Me and NT4/200x User Profiles</a>, <a class="indexterm" href="ProfileMgmt.html#id2664813">Changing the Default Profile</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669435">WINS Lookup</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a>, <a class="indexterm" href="unicode.html#id2670996">Individual Implementations</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678899">IdMap LDAP Support</a>, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a>, <a class="indexterm" href="bugreport.html#id2686347">Debugging-Specific Operations</a>, <a class="indexterm" href="Other-Clients.html#id2690390">Windows 2000 Service Pack 2</a> (see SSO)</dt><dd><dl><dt>backend, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>logon</dt><dd><dl><dt>service, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>abbreviated keystrokes, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a></dt><dt>aborting shutdown, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>accept connections, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>access, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a></dt><dt>Access, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>access authentication, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>access control, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a>, <a class="indexterm" href="AdvancedNetworkManagement.html">Advanced Network Management</a></dt><dt>Access Control, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Access Control Entries (see ACE)</dt><dt>Access Control List, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>access control needs, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>access controls, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a>, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>Access Controls, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>access denied, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>access policies, <a class="indexterm" href="passdb.html#id2592213">Domain Account Policy Managment</a></dt><dt>access rights, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>account, <a class="indexterm" href="install.html#id2553073">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dd><dl><dt>backend, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>database, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt><dd><dl><dt>backends, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a></dt></dl></dd></dl></dd><dt>account access controls, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>account attributes, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>account backends, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>account containers, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a></dt><dt>account control block (see ACB)</dt><dt>account control flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account controls, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Account Controls, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>account database, <a class="indexterm" href="passdb.html#id2592500">Password Backends</a></dt><dt>account deleted, <a class="indexterm" href="passdb.html#id2591462">Deleting Accounts</a></dt><dt>account encode_bits, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account flag order, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>Account Flags, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>account flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>account import/export, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2592375">Account Import/Export</a></dt><dt>account information, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dt>account information database, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>account management, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>account name, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>account policies, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt><dt>account policy, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>account restrictions, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>account security, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>account storage backends, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a></dt><dt>account storage mechanisms, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>account storage system, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>Account Unknown, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>accountability, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>accounts, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>ACL, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>ACLs, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></dt><dd><dl><dt>File System, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>POSIX, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>share, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>Windows, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt></dl></dd><dt>ACLs on share, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>ACLs on shares, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>across network segments, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>active directory, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564236">Samba ADS Domain Control</a></dt><dt>Active Directory, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a>, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a>, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>Active Directory Server, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>AD4UNIX, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>ADAM, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>add a user account, <a class="indexterm" href="passdb.html#id2591374">Adding User Accounts</a></dt><dt>add client machines, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>add domain users and groups to a local group, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>add drivers, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>add machine script, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678050">Changes in Behavior</a></dt><dt>Add Printer Wizard, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>add printer wizard, <a class="indexterm" href="CUPS-printing.html#id2634735">Driver Upload Methods</a></dt><dt>add user script, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678050">Changes in Behavior</a></dt><dt>add/delete/change share, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>adddriver, <a class="indexterm" href="classicalprinting.html#id2628597">Installing Driver Files into [print$]</a>, <a class="indexterm" href="classicalprinting.html#id2628952">Running rpcclient with adddriver</a>, <a class="indexterm" href="classicalprinting.html#id2629446">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></dt><dt>additional driver, <a class="indexterm" href="classicalprinting.html#id2630283">Additional Client Driver Installation</a></dt><dt>additional privileges, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>addmem, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>AddPrinterDriver(), <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></dt><dt>admincfg.exe, <a class="indexterm" href="Other-Clients.html#id2690153">Configuring Windows for Workgroups Password Handling</a></dt><dt>administrative actions, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>administrative duties, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>administrative privileges, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>administrative responsibilities, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>administrative rights, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>administrative rights and privileges, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Administrative Templates, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></dt><dt>Administrator, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>administrator account, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dt>Administrator account, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>administrator password, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>Administrator%password, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>Adobe, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>Adobe driver, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>Adobe driver files, <a class="indexterm" href="CUPS-printing.html#id2641837">Recognizing Different Driver Files</a></dt><dt>Adobe PostScript, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>Adobe PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></dt><dt>Adobe PPD, <a class="indexterm" href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a></dt><dt>Adobe specifications, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>ADS, <a class="indexterm" href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a>, <a class="indexterm" href="NetCommand.html#id2599300">Administrative Tasks and Methods</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2654536">Result Caching</a>, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660299">System Startup and Logon Processing Overview</a>, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a>, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a> (see Active Directory)</dt><dt>ADS DC, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a></dt><dt>ADS domain, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>ADS domain members, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>ADS manager, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>ADS schema, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>Advanced TCP/IP configuration, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>advantages, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>affect users, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></dt><dt>affordable power, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>AFPL, <a class="indexterm" href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dt>AFPL Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>AFS, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>AIX, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a></dt><dt>algorithmic mapping, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>alias group, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>allow access, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>allow trusted domains, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>already exists, <a class="indexterm" href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></dt><dt>alternative solution, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>Amanda, <a class="indexterm" href="Backup.html#id2671862">Amanda</a></dt><dt>analyzes data, <a class="indexterm" href="problems.html#id2684851">Diagnostics Tools</a></dt><dt>anonymous, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dd><dl><dt>print server, <a class="indexterm" href="FastStart.html#id2554843">Anonymous Print Server</a></dt><dt>read-write server, <a class="indexterm" href="FastStart.html#id2554632">Anonymous Read-Write Document Server</a></dt></dl></dd><dt>anonymous access, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>anonymous file server, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>anonymous server, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>ANSI compiler, <a class="indexterm" href="Portability.html#id2689108">HPUX</a></dt><dt>anticipate failure, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>API, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>Appliances, <a class="indexterm" href="winbind.html#id2653711">Target Uses</a></dt><dt>application servers, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>application/cups.vnd-postscript, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>application/octet-stream, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>application/pdf, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>application/postscript, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>application/vnd.cups-postscript, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a></dt><dt>application/vnd.cups-raster, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>application/vnd.cups-raw, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt><dt>application/x-shell, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>apt-get, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>ARCFOUR-HMAC-MD5, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>architecture, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>ARP/RARP, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>ASCII, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a>, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a></dt><dt>ASCII text, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a></dt><dt>assign rights, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>assigned RID, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>assistance, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>associations, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>attach gdb, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>attribute, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>attributes, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>audit file access, <a class="indexterm" href="VFS.html#id2650802">audit</a></dt><dt>audit module, <a class="indexterm" href="VFS.html#id2651060">extd_audit</a></dt><dt>auth, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>authenticate, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>authenticate users, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>authenticated, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a></dt><dt>authenticating server, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></dt><dt>authentication, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2592375">Account Import/Export</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dd><dl><dt>backend, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt></dl></dd><dt>authentication agents, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>authentication architecture, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>authentication backend, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>authentication control, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>authentication database, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a></dt><dt>authentication management, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>authentication mechanisms, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>authentication methods, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>authentication module API, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a></dt><dt>authentication regime, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>authentication reply, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></dt><dt>authentication server, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>authentication service, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>authentication system, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>authenticatior, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>authoritative, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>authoritive, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>authorization, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>auto-reconnect, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>autogen.sh, <a class="indexterm" href="compiling.html#id2687994">Building the Binaries</a></dt><dt>autogenerated printcap, <a class="indexterm" href="classicalprinting.html#id2625491">Default UNIX System Printing Commands</a></dt><dt>automatic account creation, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>automatic mapping, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>automatic reconnects, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>automatic redundancy, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>autopoweruser.sh, <a class="indexterm" href="NetCommand.html#id2600610">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>autotyping, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>AUXILIARY, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>auxiliary members, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>availability, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>available, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>available port, <a class="indexterm" href="classicalprinting.html#id2631902">Samba and Printer Ports</a></dt><dt>available printerd, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>available rights, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>average print run, <a class="indexterm" href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>b-node, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>back up, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>backed up, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>backend, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>backend authentication, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>backend database, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>backend failures, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>backend file system pool, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a></dt><dt>backends, <a class="indexterm" href="ChangeNotes.html#id2579081">Passdb Changes</a>, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dt>backup, <a class="indexterm" href="Backup.html#id2671379">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a>, <a class="indexterm" href="tdb.html#id2686891">Features and Benefits</a></dt><dt>backup domain controller, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>backup solution, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>BackupPC, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>bad hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>bad logon attempts, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>Bad networking hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>bad password, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>banner pages, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a>, <a class="indexterm" href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a></dt><dt>barriers, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a></dt><dt>Batch Oplock, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>BDC, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dt>BDCs, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>behavior approximately same, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></dt><dt>between domains, <a class="indexterm" href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></dt><dt>bias, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>binary format TDB, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>BIND, <a class="indexterm" href="DNSDHCP.html#id2693133">Dynamic DNS</a></dt><dt>bind interfaces only, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>BIND9, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>BIND9.NET, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a></dt><dt>bindery-enabled, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>block device, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>block incoming packets, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>BOBS, <a class="indexterm" href="Backup.html#id2671910">BOBS: Browseable Online Backup System</a></dt><dt>bogus, <a class="indexterm" href="ServerType.html#id2560441">Example Configuration</a></dt><dt>boot disk`, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>bridge, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>bridges networks, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>brlock.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>broadcast, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>broadcast address, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>broadcast isolated subnet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>broadcast messages, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>broadcast messaging, <a class="indexterm" href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a></dt><dt>Broadcast node, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>broadcast request, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>broadcast traffic, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>broadcast-based, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>broadcast-based name resolution, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>broadcasts, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>browse across subnet, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>browse list, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>browse list handling, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a></dt><dt>browse list maintainers, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>browse list management, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>browse lists, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>browse resources, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>browse server resources, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>browse shares, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>browse.dat, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>browseable, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>browser election, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>browser elections, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>BrowseShortNames, <a class="indexterm" href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>browsing, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></dt><dt>browsing across subnets, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>browsing another subnet, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></dt><dt>browsing intrinsics, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>browsing problems, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586352">Common Errors</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586500">I Get an "Unable to browse the network" Error</a></dt><dt>BSD, <a class="indexterm" href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>BSD Printing, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>BSD-style printing, <a class="indexterm" href="classicalprinting.html#id2623534">Extended Printing Configuration</a></dt><dt>bug report, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>bug reports, <a class="indexterm" href="bugreport.html#id2686022">Introduction</a></dt><dt>Bugzilla, <a class="indexterm" href="bugreport.html#id2686022">Introduction</a></dt><dt>built-in commands, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>bypasses privilege, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>byte ranges, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>byte-range lock, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>byte-range locking, <a class="indexterm" href="locking.html#id2615682">Discussion</a>, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>c:\winnt\inf, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>C:\WinNT\System32\config, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>cached</dt><dd><dl><dt>password, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a></dt></dl></dd><dt>cached encrypted password, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>cached in memory, <a class="indexterm" href="passdb.html#id2588481">Advantages of Non-Encrypted Passwords</a></dt><dt>cached local file, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>cached locally, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>cached references, <a class="indexterm" href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></dt><dt>caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>caching reads, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>caching scheme, <a class="indexterm" href="winbind.html#id2654536">Result Caching</a></dt><dt>caching writes, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>called name, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>cannot join domain, <a class="indexterm" href="ClientConfig.html#id2578339">Common Errors</a></dt><dt>canonicalize files, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>CAP, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a>, <a class="indexterm" href="Other-Clients.html#id2689679">Macintosh Clients</a></dt><dt>cap-share, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>capability to delete, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>CAP_LINUX_IMMUTABLE, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>case options, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>case sensitivity, <a class="indexterm" href="pam.html#id2665836">PAM Configuration Syntax</a></dt><dt>case-insensitive, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a>, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>case-preserving, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a></dt><dt>central environment, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>centralized</dt><dd><dl><dt>authentication, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt></dl></dd><dt>centralized identity management, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>centrally managed, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>certificate, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt><dt>Certificate Authority (see CA)</dt><dt>cfdisk, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>challenge/response mechanis, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>change capabilities, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt><dt>change motivations, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>change password, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>change passwords, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt><dt>changed parameters, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>changes password, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>character device, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>character set, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>character sets, <a class="indexterm" href="unicode.html#id2670049">Samba and Charsets</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>charset, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>charset conversion, <a class="indexterm" href="unicode.html#id2670185">Conversion from Old Names</a></dt><dt>chattr, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>check for locks, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>check logs, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>checksum-search, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>chmod, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>chown, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="AccessControls.html#id2613591">Viewing File Ownership</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>chpass, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>CIFS, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>CIFS function calls, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>CIFS/SMB, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a>, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>Citrix, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>clear purpose preferred, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>clear-text, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>clear-text passwords, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>client client instructions, <a class="indexterm" href="ClientConfig.html#id2575494">Features and Benefits</a></dt><dt>Client for Microsoft Networks, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Client for Novell Networks, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>client-server mode, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt><dt>client-side caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>client-side data caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a>, <a class="indexterm" href="locking.html#id2616642">PDM Data Shares</a></dt><dt>clock skew, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>cluster servers, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>clustered file server, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>Clustered smbds, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a></dt><dt>clustering technologies, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>cluttering, <a class="indexterm" href="bugreport.html#id2686347">Debugging-Specific Operations</a></dt><dt>cmd, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a>, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>cmd shell, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>CN, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>code maintainer, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>codepages, <a class="indexterm" href="unicode.html#id2669864">Features and Benefits</a></dt><dt>collating, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></dt><dt>collisions, <a class="indexterm" href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>color, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>COM1:, <a class="indexterm" href="classicalprinting.html#id2631902">Samba and Printer Ports</a></dt><dt>command-line, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>command-line utility, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>commenting out setting, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>commercial Linux products, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>commercial support, <a class="indexterm" href="ch47.html">Samba Support</a>, <a class="indexterm" href="ch47.html#id2692705">Commercial Support</a></dt><dt>commit the settings, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>Common Internet Filesystem (see CIFS)</dt><dt>Common restrictions, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>Common UNIX Printing System (see CUPS)</dt><dt>common.adm, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>comp.protocols.smb, <a class="indexterm" href="bugreport.html#id2686022">Introduction</a></dt><dt>compatible, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="Portability.html">Portability</a></dt><dt>compile, <a class="indexterm" href="install.html#id2551909">Obtaining and Installing Samba</a></dt><dt>compile-time options, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>complex file name space, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>complex organization, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>complexity, <a class="indexterm" href="StandAloneServer.html#id2574443">Example Configuration</a></dt><dt>compliance, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>complicated, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>complicated problem, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>comprehensive documentation, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>Computer Account, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dt>computer account, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>computer accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Computer Management, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a>, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>Computer Name, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>computer name, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>concurrent access, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Conectiva, <a class="indexterm" href="CUPS-printing.html#id2646759">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>config.cache, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a></dt><dt>CONFIG.POL, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>Config.POL, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></dt><dt>configuration</dt><dd><dl><dt>documentation, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a></dt></dl></dd><dt>configuration files, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a></dt><dt>configuration problem, <a class="indexterm" href="bugreport.html#id2686022">Introduction</a></dt><dt>configuration syntax, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>configuration techniques, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>configuration too complex, <a class="indexterm" href="StandAloneServer.html#id2575426">Common Errors</a></dt><dt>configuration tool, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>configuration wizard, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>configure, <a class="indexterm" href="compiling.html#id2687994">Building the Binaries</a></dt><dt>configuring a firewall, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>confirm address, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>confirm the password, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></dt><dt>confirm the trust, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>connect transparently, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>connection resources, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></dt><dt>connections, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>connections.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>consistent case, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>console, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>consumer expects, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>container, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>continuity of service, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>contribute, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>Control Panel, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>convert</dt><dd><dl><dt>domain member server, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt></dl></dd><dt>converted, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>copy'n'paste, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>core files, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a></dt><dt>core graphic engine, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a></dt><dt>core values, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>corrupted file, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>cosine.schema, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>country of origin, <a class="indexterm" href="ch47.html#id2692705">Commercial Support</a></dt><dt>CP850, <a class="indexterm" href="unicode.html#id2670049">Samba and Charsets</a></dt><dt>CP932, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>cracker, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>create, <a class="indexterm" href="AccessControls.html#id2611102">Managing Directories</a></dt><dt>Create a Computer Account, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dt>create a domain machine account, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>create domain member, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a></dt><dt>create machine trust account, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>create partition, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>Create the Computer Account, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>create user accounts, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>create volume, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>credentials, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>credentials validation, <a class="indexterm" href="samba-bdc.html#id2567510">NetBIOS Over TCP/IP Enabled</a></dt><dt>critical aspects of configuration, <a class="indexterm" href="ClientConfig.html#id2575494">Features and Benefits</a></dt><dt>crle, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>cron, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></dt><dt>cross post, <a class="indexterm" href="problems.html#id2685716">Getting Mailing List Help</a></dt><dt>cross-segment browsing, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>cross-subnet browsing, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>CUPS, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2623534">Extended Printing Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="CUPS-printing.html#id2632981">Features and Benefits</a>, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a>, <a class="indexterm" href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a>, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a></dt><dd><dl><dt>Page Accounting, <a class="indexterm" href="CUPS-printing.html#id2647442">Page Accounting with CUPS</a></dt><dt>quotas, <a class="indexterm" href="CUPS-printing.html#id2647478">Setting Up Quotas</a></dt></dl></dd><dt>CUPS API, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="classicalprinting.html#id2625491">Default UNIX System Printing Commands</a></dt><dt>CUPS backends, <a class="indexterm" href="CUPS-printing.html#id2637941">CUPS Backends</a></dt><dt>CUPS filtering, <a class="indexterm" href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>CUPS filtering chain, <a class="indexterm" href="CUPS-printing.html#id2637941">CUPS Backends</a></dt><dt>CUPS libarary API, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>CUPS PostScript, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>CUPS PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></dt><dt>CUPS print filters, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>CUPS raster, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>CUPS-PPD, <a class="indexterm" href="CUPS-printing.html#id2646371">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>cups.hlp, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>cupsaddsmb, <a class="indexterm" href="CUPS-printing.html#id2634735">Driver Upload Methods</a>, <a class="indexterm" href="CUPS-printing.html#id2641218">cupsaddsmb: The Unknown Utility</a>, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a>, <a class="indexterm" href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643159">cupsaddsmb with a Samba PDC</a>, <a class="indexterm" href="CUPS-printing.html#id2643240">cupsaddsmb Flowchart</a>, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a></dt><dt>cupsd.conf, <a class="indexterm" href="classicalprinting.html#id2625491">Default UNIX System Printing Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a>, <a class="indexterm" href="CUPS-printing.html#id2638528">mime.convs</a>, <a class="indexterm" href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></dt><dt>cupsomatic, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646371">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>currupted, <a class="indexterm" href="tdb.html#id2686891">Features and Benefits</a></dt><dt>custom scripts, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>customer expected, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>customers, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>customized print commands, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2654713">Requirements</a>, <a class="indexterm" href="compiling.html#id2688724">Alternative: Starting smbd as a Daemon</a></dt><dt>daemon running, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>daemons, <a class="indexterm" href="winbind.html#id2656610">Restarting</a></dt><dt>damaged data, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>data caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>data corruption, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a>, <a class="indexterm" href="locking.html#id2616518">UNIX or NFS Client-Accessed Files</a></dt><dt>data interchange, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>data stream, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>database, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></dt><dt>DatabaseFS, <a class="indexterm" href="VFS.html#id2652762">DatabaseFS</a></dt><dt>DAVE, <a class="indexterm" href="Other-Clients.html#id2689679">Macintosh Clients</a></dt><dt>dbx, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a></dt><dt>DCE RPC, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>DDK, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dt>DDNS, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a></dt><dt>de-multiplex, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>de-multiplexing, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>Debian, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>Debian Sarge, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>debug, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a></dt><dt>debug level, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a></dt><dt>debugging, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#id2686347">Debugging-Specific Operations</a></dt><dt>debugging passwords, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>debugging problems, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>dedicated heartbeat, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>dedicated print server, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>default accounts, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>default aliases, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>default behavior, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>default devmode, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>default DNS setup, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>default gateways, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>default groups, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>default mapping, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a></dt><dt>default mappings, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>default print command, <a class="indexterm" href="classicalprinting.html#id2625491">Default UNIX System Printing Commands</a></dt><dt>default print commands, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>default printer, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>default printing, <a class="indexterm" href="CUPS-printing.html#id2632981">Features and Benefits</a></dt><dt>default profile, <a class="indexterm" href="ProfileMgmt.html#id2663314">Default Profile for Windows Users</a>, <a class="indexterm" href="ProfileMgmt.html#id2664813">Changing the Default Profile</a></dt><dt>default settings, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>default shells, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>Default User, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>default users, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>defective hardware, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>deferred open, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>defined shares, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>delegate administrative privileges, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>delegated, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a></dt><dt>delegation, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>delete, <a class="indexterm" href="AccessControls.html#id2611102">Managing Directories</a></dt><dt>delete a file, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>delete roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>delete user script, <a class="indexterm" href="passdb.html#id2591462">Deleting Accounts</a></dt><dt>deleted files, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>deleted parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2676800">Removed Parameters</a></dt><dt>delmem, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>demote, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>demoted, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>denial of service, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>deny, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>deny access, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>deny modes, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>deny-none, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>DENY_ALL, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>DENY_DOS, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>DENY_FCB, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>DENY_NONE, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>DENY_READ, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>DENY_WRITE, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>deployment, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>deployment guidelines, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>DES-CBC-CRC, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>DES-CBC-MD5, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>desirable solution, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>desktop cache, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>desktop profile, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>desktop profiles, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>deterents, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a></dt><dt>development libraries, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>devfsd package, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>device mode, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>device-specific commands, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>DFS, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a> (see MS-DFS, Distributed File Systems)</dt><dt>DFS junction, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS links, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS root, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS server, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS tree, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS-aware, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DFS-aware clients, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>DHCP, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a>, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a></dt><dt>DHCP servers, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>DHCP-enabled, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>DHCP-enabled operation, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>diagnostic, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>diagnostic tools, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>diff, <a class="indexterm" href="bugreport.html#id2686807">Patches</a></dt><dt>differences, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>different resources, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>differently encrypted passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>differing protocol, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></dt><dt>dir, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>direct internet access, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a></dt><dt>directory, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a></dt><dt>directory access control, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>directory access permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>directory controls, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>Directory Information Tree (see DIT)</dt><dt>directory permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>directory schema, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>Directory Separators, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>directory server, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>directory_mode, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>disable LMB, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>disable locking, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a></dt><dt>disable roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a></dt><dt>disabling oplocks, <a class="indexterm" href="locking.html#id2616642">PDM Data Shares</a></dt><dt>disass, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a></dt><dt>disaster recovery, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>disconnect a connection, <a class="indexterm" href="ProfileMgmt.html#id2660668">NT4/200x User Profiles</a></dt><dt>disk, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>disk space, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>disparate information systems, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>display PostScript, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>displayName, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>distort, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>distribute authentication systems, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>distributed, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>distributed account, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>Distributed Computing Environment (see DCE)</dt><dt>distributed directory, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>distributed file system, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a> (see DFS)</dt><dt>Distributed File Systems, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>distributed file systems, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>distributed locking protocol, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>distribution, <a class="indexterm" href="install.html#id2553073">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>dithering algorithm, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>DMB, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>DMB for a workgroup, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></dt><dt>DMC, <a class="indexterm" href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a></dt><dt>DMS, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>DN, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>DNS, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a>, <a class="indexterm" href="samba-bdc.html#id2567576">NetBIOS Over TCP/IP Disabled</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669408">DNS Lookup</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a>, <a class="indexterm" href="DNSDHCP.html#id2693042">Example Configuration</a></dt><dd><dl><dt>Active Directory, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>Dynamic, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="DNSDHCP.html#id2693133">Dynamic DNS</a></dt><dt>SRV records, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt></dl></dd><dt>DNS Configuration, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>DNS lookup, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>DNS name resolution, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>dns proxy, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>DNS server, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>DNS server access, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>DNS server settings, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>DNS servers, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>DNS zon, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>DNS/LDAP/ADS, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a></dt><dt>document design, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>documentation, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a>, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>domain, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="passdb.html#id2591374">Adding User Accounts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dd><dl><dt>control, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a></dt><dd><dl><dt>role, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt></dl></dd><dt>controller, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html">Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dd><dl><dt>convert, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>hierarchy, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt></dl></dd><dt>controllers, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt><dt>groups, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>master</dt><dd><dl><dt>browser, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt></dl></dd><dt>member, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dd><dl><dt>server, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt></dl></dd><dt>member server, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>security, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt><dd><dl><dt>protocols, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt></dl></dd><dt>trust account, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt></dl></dd><dt>domain access, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>domain account access policies, <a class="indexterm" href="passdb.html#id2592213">Domain Account Policy Managment</a></dt><dt>domain admin group, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>domain Administrator, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>Domain Admins, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>Domain Admins group, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>domain authentication, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>domain context, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>domain control, <a class="indexterm" href="samba-pdc.html#id2562458">Basics of Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2568600">Common Errors</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="NT4Migration.html">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt>backup, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a></dt><dt>primary, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a></dt></dl></dd><dt>domain control database (see SAM)</dt><dt>domain controller, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567510">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dt>Domain Controller, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>domain controllers, <a class="indexterm" href="samba-pdc.html#id2564236">Samba ADS Domain Control</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>domain environment, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>domain global, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global group, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global groups, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain global user, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>domain global users, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain group, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>domain group settings, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain groups, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>Domain Groups, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a></dt><dt>Domain Guests, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>domain information, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>domain join, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>domain joining, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>domain logon, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564289">Domain and Network Logon Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564308">Domain Network Logon Service</a>, <a class="indexterm" href="samba-bdc.html#id2566688">Example PDC Configuration</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>domain logon server, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>domain logons, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>domain management tools, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>domain master, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></dt><dt>domain member, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#id2573664">Common Errors</a>, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>Domain Member, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dd><dl><dt>joining, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a></dt></dl></dd><dt>domain member client, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a></dt><dt>Domain Member Client (see DMC)</dt><dt>domain member server, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>Domain Member Server (see DMS)</dt><dt>domain member servers, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>domain member workstations, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>domain members, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>domain membership, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a></dt><dt>domain name, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Domain Name System (see DNS)</dt><dt>domain non-member, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a></dt><dt>domain policies, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>domain radio button, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>domain security, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>domain security account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Domain Server Manager, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>domain SID, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>domain trust, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></dt><dt>domain user, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>domain user accounts, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>domain user manager, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a></dt><dt>Domain User Manager, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>Domain Users, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>domain users, <a class="indexterm" href="winbind.html#id2654713">Requirements</a>, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="winbind.html#id2657284">Conclusion</a></dt><dt>Domain Users group, <a class="indexterm" href="groupmapping.html#id2598611">Adding Domain Users to the Workstation Power Users Group</a></dt><dt>domain-level, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></dt><dt>domain-level security, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>domain-wide browse list, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></dt><dt>DOMAIN&lt;1B&gt;, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>DOMAIN&lt;1C&gt;, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>DOMAIN&lt;1D&gt;, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>draft, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>Drive Identification, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>driver, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dt>driver CDROM, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>driver download, <a class="indexterm" href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></dt><dt>Driver File, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>driver files, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>Driver Path, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>dual-daemon winbindd, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>due diligence, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>duplex, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>duplex printing, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>duplicate, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>duplication of information, <a class="indexterm" href="winbind.html#id2653468">Introduction</a></dt><dt>DVI, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a></dt><dt>Dynamic DNS (see DDNS)</dt><dt>Dynamic Host Configuration Protocol (see DHCP)</dt><dt>dynamic link loader, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>dynamic registration files, <a class="indexterm" href="DNSDHCP.html#id2693133">Dynamic DNS</a></dt><dt>Dynamic SMB servers, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>dynamically loadable library modules, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>e-Directory, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>EAs, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>economically wise, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>eDirectory, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>editreg, <a class="indexterm" href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a></dt><dt>efficient authentication, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>election, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>election criteria, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>election packet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>election process, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>EMF, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2640266">From Windows Clients to an NT Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></dt><dt>enables clients to print, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>enables NetBIOS over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>encapsulating, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>encoding, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>encryped password, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>encrypted, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>encrypted password, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>encrypted passwords, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a>, <a class="indexterm" href="passdb.html#id2587230">Features and Benefits</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="ProfileMgmt.html#id2662744">Profile Migration from Windows NT4/200x Server to Samba</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a></dt><dt>encrypted session, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>encryption, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a></dt><dt>encryption key, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a></dt><dt>encryption types, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573385">Notes</a></dt><dt>enforcing, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>English, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a>, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>Enhanced MetaFile (see EMF)</dt><dt>enterprise, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>enumdrivers, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></dt><dt>enumerate domain groups, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></dt><dt>enumerate domain users, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></dt><dt>EnumJobs(), <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>enumprinters, <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></dt><dt>environment variables, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>EPM (see ESP meta packager)</dt><dt>Epson Stylus, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>Epson Stylus inkjet, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>equivalence, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>equivalent rights and privileges, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>error message, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="classicalprinting.html#id2628952">Running rpcclient with adddriver</a></dt><dt>error messages, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>errors that can afflict, <a class="indexterm" href="ClientConfig.html#id2578339">Common Errors</a></dt><dt>ESC/P, <a class="indexterm" href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></dt><dt>ESP, <a class="indexterm" href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dd><dl><dt>Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>meta packager, <a class="indexterm" href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dt>Print Pro, <a class="indexterm" href="CUPS-printing.html#id2640032">Sources of CUPS Drivers/PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2641981">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></dt></dl></dd><dt>ESP Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>established, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>ethereal, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="problems.html#id2685159">Tcpdump</a>, <a class="indexterm" href="problems.html#id2685209">Ethereal</a>, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>Ethernet adapters, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>EUC-JP, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>eucJP-ms locale, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Event Viewer, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>Everyone - Full Control, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>Everyone group, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>EVMS, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a></dt><dt>examples, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>examples/LDAP, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>execute, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>existing LDAP DIT, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>expands control abilities, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>expired password, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>explicit trust, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>explicitly set, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>exploit opportunities, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a></dt><dt>exploitation, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>exported file system, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>exposed, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>extd_audit module, <a class="indexterm" href="VFS.html#id2651060">extd_audit</a></dt><dt>Extended Attributes, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>extended attributes, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>Extended BSD Printing, <a class="indexterm" href="classicalprinting.html#id2623534">Extended Printing Configuration</a></dt><dt>extended characters, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>extended protocol, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>extended SAM, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>extra machine, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fail, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>failed join, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>failed logins, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>failover communication, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>failover process, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>failover servers, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>fails, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>failure, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>failure semantics, <a class="indexterm" href="SambaHA.html#id2672953">Required Modifications to Samba</a></dt><dt>fake-permissions module, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>fake_permissions, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>fake_perms, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a>, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>fdisk, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>Federated Identity Management (see FIM)</dt><dt>federated organizations, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>federated-identity, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>Fiber Channel, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>fickle, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a></dt><dt>fid, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>file access permissions, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>File Naming Conventions, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>file ownership, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>file serving, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>File System, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dd><dl><dt>case sensitivity, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>feature comparison, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>UNIX, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>Windows, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>file system capabilities, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>FILE:, <a class="indexterm" href="classicalprinting.html#id2631902">Samba and Printer Ports</a></dt><dt>filemanager, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>filename mangling, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>filter, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>Filter Oplock, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>FilterLimit, <a class="indexterm" href="CUPS-printing.html#id2638528">mime.convs</a></dt><dt>filters, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>FIM, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>firewall, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a>, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>firewall active, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>firewall setups, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>fixed IP address, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>fixed IP addresses, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a></dt><dt>flush local locks, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>flush name cache, <a class="indexterm" href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></dt><dt>foomatic, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2646148">foomatic-rip and Foomatic Explained</a>, <a class="indexterm" href="CUPS-printing.html#id2646296">Foomatic's Strange Name</a></dt><dt>Foomatic database, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>Foomatic Printer, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>Foomatic tutorial, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>foomatic-rip, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646148">foomatic-rip and Foomatic Explained</a>, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>Foomatic/cupsomatic, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>force an election, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>force election, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></dt><dt>forced synchronization, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>foreign domain, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>foreign SID, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a></dt><dt>foreign user, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a></dt><dt>FQDN, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>framing error, <a class="indexterm" href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>free support, <a class="indexterm" href="ch47.html">Samba Support</a>, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>FreeBSD, <a class="indexterm" href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>freezing, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>French, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>front-end virtual server, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>frustrating experience, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dt>FTP, <a class="indexterm" href="passdb.html#id2588481">Advantages of Non-Encrypted Passwords</a></dt><dt>ftp, <a class="indexterm" href="Backup.html#id2671692">Rsync</a>, <a class="indexterm" href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></dt><dt>ftp access, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftp service, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftp services, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>ftpd, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>full rights, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>functional components, <a class="indexterm" href="bugreport.html#id2686347">Debugging-Specific Operations</a></dt><dt>functionality, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gateway address, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>gcc, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="Portability.html#id2689108">HPUX</a></dt><dt>gdb, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a>, <a class="indexterm" href="bugreport.html#id2686682">Attaching to a Running Process</a></dt><dt>GDI, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2640266">From Windows Clients to an NT Print Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></dt><dt>general security service application programming interface (see GSSAPI)</dt><dt>generic PostScript, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>generic raster, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>generic raster format, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>genlogon.pl, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658359">Network Logon Script Magic</a></dt><dt>Gentoo, <a class="indexterm" href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>Germany, <a class="indexterm" href="SambaHA.html#id2672127">Technical Discussion</a></dt><dt>get, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>getdriver, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2628597">Installing Driver Files into [print$]</a></dt><dt>getdriverdir, <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></dt><dt>getent, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>getent group demo, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>gethostbyname() function call, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></dt><dt>getpwnam, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>getpwnam() call, <a class="indexterm" href="upgrading-to-3.0.html#id2678050">Changes in Behavior</a></dt><dt>GetSID.exe, <a class="indexterm" href="ProfileMgmt.html#id2663030">Get SID</a></dt><dt>GhostScript, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></dt><dd><dl><dt>(see also PostScript)</dt></dl></dd><dt>Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dd><dl><dt>ESP (see ESP
+	GhostScript)</dt></dl></dd><dt>GID, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579081">Passdb Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>GID numbers, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>GID range, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>GIF, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>global print command, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>global right, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>global section, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>Global support, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>global-level, <a class="indexterm" href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a></dt><dt>GNOME, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>GNU Ghostscript, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>GNU GPL, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>GNU tar, <a class="indexterm" href="Backup.html#id2671862">Amanda</a></dt><dt>GNU/Linux, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>GPG, <a class="indexterm" href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></dt><dt>GPL, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>gpolmig.exe, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a></dt><dt>GPOs, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660299">System Startup and Logon Processing Overview</a>, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>grace time, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>grant rights, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>graphical objects, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>graphically illustrated client configuration, <a class="indexterm" href="ClientConfig.html#id2575494">Features and Benefits</a></dt><dt>grayscale, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>greater scalability, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>greatest mistake, <a class="indexterm" href="StandAloneServer.html#id2575426">Common Errors</a></dt><dt>grep, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>group, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dd><dl><dt>account, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>mapping, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt></dl></dd><dt>group account, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a></dt><dt>group accounts, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2596625">Warning: User Private Group Problems</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>group management, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>group mapping, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>group mappings, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>group membership, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>group ownership, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>group permissions, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>Group Policies, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a></dt><dt>group policies, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a></dt><dt>group policy, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>Group Policy, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></dt><dt>Group Policy Container (see GPC)</dt><dt>Group Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660194">Windows NT4/200x</a>, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>Group Policy Objects, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a> (see GPO)</dt><dt>group policy objects (see GPOs)</dt><dt>Group Policy Template (see GPT)</dt><dt>group privileges, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>group profiles, <a class="indexterm" href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></dt><dt>group SID, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>groupadd, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a>, <a class="indexterm" href="groupmapping.html#id2598524">Adding Groups Fails</a></dt><dt>groupadd limitations, <a class="indexterm" href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a></dt><dt>groupdel, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>groupmap, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>groupmod, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>grouppol.inf, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></dt><dt>groups, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a>, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a></dt><dd><dl><dt>domain, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>mapping, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a></dt><dt>nested, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt></dl></dd><dt>groups of users, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>growing, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>GSSAPI, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>gtklp, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>guest, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>guest account, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>GUI, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>Gutenprint, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a>, <a class="indexterm" href="CUPS-printing.html#id2646655">Driver Development Outside</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>h-node, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>harvesting password hashes, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>hashed password equivalent, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>headers files, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a></dt><dt>Heimdal, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>Heimdal kerberos, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>help, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>help command, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>heterogeneous computing, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>HEX, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a></dt><dt>hi-res photo, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>high availability, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>high order ports, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>high-availability, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>high-availability services, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>high-speed server interconnect, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>higher availability, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>HKEY_CURRENT_USER, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></dt><dt>HKEY_LOCAL_MACHINE, <a class="indexterm" href="PolicyMgmt.html#id2659384">Registry Spoiling</a></dt><dt>holy grail, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>home directories, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>home directory, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>home directory template, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>home drive, <a class="indexterm" href="samba-bdc.html#id2566688">Example PDC Configuration</a></dt><dt>host multiple servers, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>host security, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>host-based protection, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>hostname, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>hosts allow, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>hosts deny, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>house-keeping, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>HOWTO documents, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>HP JetDirect, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>HP Photosmart, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>HP-GL, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>HP-GL., <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a></dt><dt>hpgltops, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>HPIJS, <a class="indexterm" href="CUPS-printing.html#id2646655">Driver Development Outside</a></dt><dt>HPUX, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>http, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>hybrid, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>Hybrid node, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>IANA, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>ID mapping, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>ID mapping database, <a class="indexterm" href="winbind.html#id2654460">User and Group ID Allocation</a></dt><dt>ID range, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>IDEALX, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>Identification, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>identify, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>identity, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a></dt><dt>identity information, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>identity management, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dd><dl><dt>centralized, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt></dl></dd><dt>identity resolution, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>IDMAP, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>idmap, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>idmap backend, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678899">IdMap LDAP Support</a></dt><dt>IDMAP backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>idmap gid, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>idmap GID, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>IDMAP infrastructure, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>idmap uid, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>idmap UID, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>idmap_ad, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>idmap_ldap module, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>idmap_rid, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>IETF, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>ifconfig, <a class="indexterm" href="compiling.html#id2688504">Starting from inetd.conf</a>, <a class="indexterm" href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>ignore connection, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>imagetoraster, <a class="indexterm" href="CUPS-printing.html#id2637637">imagetops and imagetoraster</a></dt><dt>immutible, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>impersonate, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>implementing oplocks, <a class="indexterm" href="locking.html#id2616799">Advanced Samba Oplocks Parameters</a></dt><dt>Implicit Classes, <a class="indexterm" href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>important announcements, <a class="indexterm" href="securing-samba.html#id2619110">Upgrading Samba</a></dt><dt>Imprints, <a class="indexterm" href="classicalprinting.html#id2632048">The Imprints Toolset</a></dt><dt>imprints, <a class="indexterm" href="CUPS-printing.html#id2634735">Driver Upload Methods</a></dt><dt>include, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>independent, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>individual domain user, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>individual section, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>inetd, <a class="indexterm" href="SWAT.html#id2681236">Validate SWAT Installation</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a>, <a class="indexterm" href="compiling.html#id2688504">Starting from inetd.conf</a></dt><dt>inetd.conf, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>inetorgperson.schema, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>inf file, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>infrastructure, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="winbind.html#id2653711">Target Uses</a></dt><dt>inheritance, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>inherits rights, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>initdb.ldif, <a class="indexterm" href="FastStart.html#id2557694">The Primary Domain Controller</a></dt><dt>initGroups.sh, <a class="indexterm" href="FastStart.html#id2556880">Example: Engineering Office</a>, <a class="indexterm" href="groupmapping.html#id2598384">Script to Configure Group Mapping</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dt>inktype, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>insecure, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a>, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>inspire simplicity, <a class="indexterm" href="StandAloneServer.html#id2574443">Example Configuration</a></dt><dt>inspired structure, <a class="indexterm" href="SambaHA.html#id2672127">Technical Discussion</a></dt><dt>install drivers, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>interactive help, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>interdomain</dt><dd><dl><dt>trust</dt><dd><dl><dt>account, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt></dl></dd><dt>trustrs, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a></dt></dl></dd><dt>interdomain connection, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></dt><dt>interdomain trust, <a class="indexterm" href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>interdomain trust accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>interdomain trusts, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a></dt><dt>Interdomain Trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dd><dl><dt>Completing, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></dt><dt>creating, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a></dt><dt>Facilities, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></dt></dl></dd><dt>interface, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>interface scripts, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a></dt><dt>interface-based exclusion, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>interfaces, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>intermediate information, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>intermediate tools, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>internal ordering, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a></dt><dt>internationalization support, <a class="indexterm" href="SWAT.html#id2681216">Guidelines and Technical Tips</a></dt><dt>Internet, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a>, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>Internet Engineering Task Force (see IETF)</dt><dt>Internet Printing Protocol (see IPP)</dt><dt>Internet Protocol TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>Internetworking Packet Exchange (see IPX)</dt><dt>internetworking super daemon, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a></dt><dt>interoperability, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a></dt><dt>intolerance, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>invalid shell, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a></dt><dt>invalid users, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>IP address, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>IP address automatically, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>IP addresses, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>IP aliases, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>IPC$, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>IPC$ connections, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>ipchains, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>ipconfig, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></dt><dt>iPlanet, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>IPP, <a class="indexterm" href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a></dt><dt>IPP client, <a class="indexterm" href="CUPS-printing.html#id2649452">Administrator Cannot Install Printers for All Local Users</a></dt><dt>iptables, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>IPX, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>IRC, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>IRIX, <a class="indexterm" href="VFS.html#id2650401">Discussion</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>ISC</dt><dd><dl><dt>DHCP, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a></dt><dt>DNS, <a class="indexterm" href="DNSDHCP.html#id2692858">Features and Benefits</a></dt></dl></dd><dt>ISC DHCP server, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>isolated workgroup, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>IXFR, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a></dt></dl></div><div class="indexdiv"><h3>J</h3><dl><dt>Japanese, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a>, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>Japanese locale, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Japanese UNIX, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Java, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>JIS X 0208, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a></dt><dt>join, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a></dt><dt>join client, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>join domain, <a class="indexterm" href="samba-pdc.html#id2565286">Joining Domain Fails Because of Existing Machine Account</a></dt><dt>join the ADS domain, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>join the domain, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>join the machine, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dt>joined client, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Joined domain, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>joining domain, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>joining the domain, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>JPEG, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KB 129202, <a class="indexterm" href="locking.html#id2617908">Additional Reading</a></dt><dt>KB 224992, <a class="indexterm" href="locking.html#id2617908">Additional Reading</a></dt><dt>KB 296264, <a class="indexterm" href="locking.html#id2617908">Additional Reading</a></dt><dt>KB 811492, <a class="indexterm" href="locking.html#id2617876">Long Delays Deleting Files over Network with XP SP1</a></dt><dt>KB 812937, <a class="indexterm" href="locking.html#id2617852">Problems Saving Files in MS Office on Windows XP</a></dt><dt>KDC, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>KDE, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>KDE konqueror, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>KDE session, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>KDEPrint, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>kerberos, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>Kerberos, <a class="indexterm" href="domain-member.html#ads-member">Samba ADS Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a>, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="winbind.html#id2654026">Microsoft Active Directory Services</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a></dt><dd><dl><dt>/etc/krb5.conf, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt></dl></dd><dt>Kerberos authentication, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></dt><dt>killall, <a class="indexterm" href="compiling.html#id2688504">Starting from inetd.conf</a></dt><dt>kinit, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a></dt><dt>kixstart, <a class="indexterm" href="NT4Migration.html#id2679887">Logon Scripts</a></dt><dt>kprinter, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>KRB, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>KRB5, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>krb5.conf, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LAN, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a>, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a>, <a class="indexterm" href="problems.html#id2684851">Diagnostics Tools</a></dt><dt>LanMan, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>LanMan logon service, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt><dt>LanMan passwords, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>LanManager, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>LanManager-compatible, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>LanManger password, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>laptops, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>large directory, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>large domain, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>large numbers of files, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>large organizations, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>last change time, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>latency, <a class="indexterm" href="locking.html#id2616553">Slow and/or Unreliable Networks</a></dt><dt>laws, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>LCT (see last change time)</dt><dt>LDAP, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="samba-bdc.html#id2568859">Can I Do This All with LDAP?</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593301">Supported LDAP Servers</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="passdb.html#id2594040">Configuring Samba</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="winbind.html#id2654026">Microsoft Active Directory Services</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dd><dl><dt>directories, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>master, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>server, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>slave, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt></dl></dd><dt>LDAP administration password, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></dt><dt>LDAP administrative password, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>LDAP backend, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></dt><dt>LDAP backends, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>LDAP database, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>LDAP deployment, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>LDAP directory, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>ldap group suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>LDAP idmap Backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>ldap idmap suffix, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>ldap machine suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>LDAP queries, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>LDAP redirects, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>LDAP schema, <a class="indexterm" href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></dt><dt>LDAP server, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>ldap suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>ldap user suffix, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>LDAP-based, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>LDAP., <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dt>LDAP/Kerberos, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>LDAPS, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>ldapsam, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593301">Supported LDAP Servers</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>ldapsam_compat, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>ldapsearch, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>LDAPv3, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>ldconfig, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>ldd, <a class="indexterm" href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></dt><dt>LDIF, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>LDIF file, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a></dt><dt>legacy systems, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>legal UNIX system account name, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>Level1 Oplock, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Level1 oplock, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Level2 Oplock, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>LGPL, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>libcups, <a class="indexterm" href="classicalprinting.html#id2625491">Default UNIX System Printing Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></dt><dt>libcups.so, <a class="indexterm" href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></dt><dt>libcups.so.2, <a class="indexterm" href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></dt><dt>Liberty Alliance, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>libiconv, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>libnss_winbind, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>libnss_winbind.so, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>libnss_wins.so, <a class="indexterm" href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></dt><dt>libraries, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>licensing, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>limitations, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>linewidth, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>link loader configuration, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>Links</dt><dd><dl><dt>hard, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>soft, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>Linux, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Linux High Availability project, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>Linux LVM, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>Linux LVM partition, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>LinuxKongress2002, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>Linuxprinting.org, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2646655">Driver Development Outside</a></dt><dt>list of domain controllers, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>listen for connections, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>listen own socket, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>LLC, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a></dt><dt>LM/NT password hashes, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>LMB, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a> (see Local Master Browser)</dt><dt>LMHOSTS, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669202">The LMHOSTS File</a></dt><dt>lmhosts, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>load balancing, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>loaded modules, <a class="indexterm" href="VFS.html#id2650363">Features and Benefits</a></dt><dt>loading printer drivers, <a class="indexterm" href="classicalprinting.html#id2625120">Any [my_printer_name] Section</a></dt><dt>local</dt><dd><dl><dt>groups, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>master</dt><dd><dl><dt>browser, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt></dl></dd></dl></dd><dt>local access permissions, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>local accounts, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>local administrative privileges, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>Local Area Connection, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>Local Area Connection Properties, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>local authentication, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>local authentication database, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>local cache, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></dt><dt>local disk, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>local domain, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a></dt><dt>local group, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>local groups, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>Local Machine Trust Account, <a class="indexterm" href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a></dt><dt>Local Master Browser, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583338">Use of the Remote Announce Parameter</a></dt><dt>local master browser (see LMB)</dt><dt>local names, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>local print driver, <a class="indexterm" href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></dt><dt>local profile, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>local profiles, <a class="indexterm" href="ProfileMgmt.html#id2660554">Features and Benefits</a></dt><dt>local registry values, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></dt><dt>Local security policies, <a class="indexterm" href="CUPS-printing.html#id2649419">Windows 200x/XP Local Security Policies</a></dt><dt>local smbpasswd file, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>local spool area, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>local subnet, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>local system printing, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>local UNIX groups, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>local user, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a>, <a class="indexterm" href="winbind.html#id2656610">Restarting</a></dt><dt>local user account, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>local users, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>locale, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>localhost, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>locally known UID, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>locate domain controller, <a class="indexterm" href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a></dt><dt>Lock caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>lock directory, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>lock password, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>lock the account, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>locking, <a class="indexterm" href="locking.html">File and Record Locking</a>, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615682">Discussion</a>, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>locking protocol, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a></dt><dt>locking semantics, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>locking.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>lockout, <a class="indexterm" href="ServerType.html#id2560441">Example Configuration</a></dt><dt>log files, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dd><dl><dt>monitoring, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt></dl></dd><dt>log level, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="bugreport.html#dbglvl">Debug Levels</a></dt><dt>log.nmbd, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>logging, <a class="indexterm" href="VFS.html#id2651218">Configuration of Auditing</a>, <a class="indexterm" href="bugreport.html#id2686347">Debugging-Specific Operations</a></dt><dt>logical directories, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>Logical Link Control (see LLC)</dt><dt>logical volume, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>Logical Volume Manager (see LVM)</dt><dt>Login, <a class="indexterm" href="passdb.html#id2588481">Advantages of Non-Encrypted Passwords</a></dt><dt>login, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>login id, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>login name, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>login shells, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>LoginID, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>logon, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt><dt>logon authentication, <a class="indexterm" href="samba-bdc.html#id2567576">NetBIOS Over TCP/IP Disabled</a></dt><dt>logon drive, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>logon home, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2660807">Windows 9x/Me User Profiles</a></dt><dt>logon name, <a class="indexterm" href="NetCommand.html#id2601237">User Mapping</a></dt><dt>logon path, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>logon processing, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>logon requests, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a>, <a class="indexterm" href="samba-bdc.html#id2567510">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></dt><dt>logon script, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>Logon Scripts, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>Logon scripts, <a class="indexterm" href="NT4Migration.html#id2679887">Logon Scripts</a></dt><dt>logon server, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></dt><dt>logons, <a class="indexterm" href="ProfileMgmt.html#id2660668">NT4/200x User Profiles</a></dt><dt>lookups, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>loopback adapter, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>loopback interface, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="Portability.html#id2689392">Red Hat Linux</a></dt><dt>lower-case, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a></dt><dt>lowercase filenames, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>lp, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a>, <a class="indexterm" href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></dt><dt>lpadmin, <a class="indexterm" href="CUPS-printing.html#id2638596">Raw Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2640155">Printing with Interface Scripts</a>, <a class="indexterm" href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a>, <a class="indexterm" href="CUPS-printing.html#id2647478">Setting Up Quotas</a></dt><dt>LPD, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>lpinfo, <a class="indexterm" href="CUPS-printing.html#id2637941">CUPS Backends</a></dt><dt>lpq cache time, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>lpq command, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>LPRNG, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>lpstat, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></dt><dt>LPT1:, <a class="indexterm" href="classicalprinting.html#id2631902">Samba and Printer Ports</a></dt><dt>LsaEnumTrustedDomains, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>LTSP, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>Lustre, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>lvcreate, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>LVM, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>LVM snapshots, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>LVM volume, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>lvm10 package, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>m-node, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>MAC address, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>MAC Addresses, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>Mac OS X , <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>machine, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dd><dl><dt>account, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>machine account, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>machine account password</dt><dd><dl><dt>change protocol, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt></dl></dd><dt>machine accounts, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>machine accounts database, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>machine authentication, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>machine name, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>Machine Policy Objects, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>machine SID, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>machine trust account, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html">Domain Membership</a>, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></dt><dd><dl><dt>create privilege, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a></dt><dt>creation, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>password, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>Machine Trust Account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dd><dl><dt>creation, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>password, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>UNIX account, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></dt></dl></dd><dt>Machine Trust Accounts, <a class="indexterm" href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt>creating, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>machine trust accounts, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="domain-member.html#id2573664">Common Errors</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>machine_name, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>machine_nickname, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>Macintosh, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>macros, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>mail, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>mailing list, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>mailing lists, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>maintaining ids, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>major changes, <a class="indexterm" href="upgrading-to-3.0.html#id2677671">New Functionality</a></dt><dt>make, <a class="indexterm" href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a>, <a class="indexterm" href="compiling.html#id2687994">Building the Binaries</a></dt><dt>man, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a></dt><dt>man page, <a class="indexterm" href="winbind.html#id2655464">Configure smb.conf</a></dt><dt>man pages, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>man-in-the-middle, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>manage accounts, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>manage drivers, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>manage groups, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>manage printers, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>manage privileges, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a></dt><dt>manage roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2660554">Features and Benefits</a></dt><dt>manage share permissions, <a class="indexterm" href="AccessControls.html#id2613132">Windows NT4 Workstation/Server</a></dt><dt>manage share-level ACL, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>manage shares, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>manage users, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>manageability, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>Manageability, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>managed by humans, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>management bottleneck, <a class="indexterm" href="locking.html#id2616601">Multiuser Databases</a></dt><dt>management costs, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>management overheads, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>management procedures, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>management tools, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>managing rights, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>mandatory profiles, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>Mandrake, <a class="indexterm" href="CUPS-printing.html#id2646759">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>Mandriva, <a class="indexterm" href="CUPS-printing.html#id2646759">Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</a></dt><dt>manual UNIX account creation, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>manual WINS server entries, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>manually configured, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>manually configured DNS settings, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>map, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="NT4Migration.html#id2679998">User and Group Accounts</a></dt><dt>mapped, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>mapping, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>mapping home directory, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>mapping printer driver, <a class="indexterm" href="classicalprinting.html#id2629560">Running rpcclient with setdriver</a></dt><dt>mappings, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>maps UNIX users and groups, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></dt><dt>master browser, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>master browsers, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>master server, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>master smb.conf, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></dt><dt>MasterAnnouncement, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>match case, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>maximum value, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>mbd kept spawning, <a class="indexterm" href="speed.html#id2691200">Corrupt tdb Files</a></dt><dt>Meccano set, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>mechanism, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>media type, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>member, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>member machine, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>memory, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>messages.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>messaging systems, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>Meta node, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>meta-directory, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>meta-service, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>meta-services, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>Microsoft Active Directory, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>Microsoft Developer Network CDs, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>Microsoft driver, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a></dt><dt>Microsoft management console (see MMC)</dt><dt>Microsoft Remote Procedure Call (see MSRPC)</dt><dt>Microsoft Windows 9x/Me, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>Microsoft Wolfpack, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>middle-ware, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>migrate, <a class="indexterm" href="ServerType.html">Server Types and Security Modes</a>, <a class="indexterm" href="NT4Migration.html">Migration from NT4 PDC to Samba-3 PDC</a></dt><dt>migrate account settings, <a class="indexterm" href="NT4Migration.html#id2679998">User and Group Accounts</a></dt><dt>migrate group, <a class="indexterm" href="NT4Migration.html#id2679998">User and Group Accounts</a></dt><dt>migrate user, <a class="indexterm" href="NT4Migration.html#id2679998">User and Group Accounts</a></dt><dt>migrating, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>migration, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>migration plan, <a class="indexterm" href="NT4Migration.html#id2679067">Planning and Getting Started</a></dt><dt>migration process, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>MIME, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2636855">Filtering  Overview</a>, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dd><dl><dt>filters, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>raw, <a class="indexterm" href="FastStart.html#id2554843">Anonymous Print Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt></dl></dd><dt>MIME conversion rules, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>MIME recognition, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>MIME type, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a>, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a>, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>mime.types, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>minimal</dt><dd><dl><dt>configuration, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt></dl></dd><dt>minimal configuration, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>minimum security control, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a></dt><dt>misconfigurations, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a></dt><dt>misconfigured settings, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>misinformation, <a class="indexterm" href="domain-member.html">Domain Membership</a></dt><dt>mission-critical, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>MIT, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>MIT kerberos, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>MIT Kerberos, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>mixed mode, <a class="indexterm" href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>mixed profile, <a class="indexterm" href="ProfileMgmt.html#id2660965">Mixed Windows Windows 9x/Me and NT4/200x User Profiles</a></dt><dt>mkdir, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>mkfs.xfs, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>MMC, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a>, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a>, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660194">Windows NT4/200x</a>, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a></dt><dt>MMC snap-in, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a></dt><dt>modem/ISDN, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>moderately secure, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>modprobe, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>module, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>modules, <a class="indexterm" href="VFS.html#id2650363">Features and Benefits</a>, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>more than one protocol, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>mount, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>mouse-over, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>moveuser.exe, <a class="indexterm" href="ProfileMgmt.html#id2662989">moveuser.exe</a></dt><dt>MS DCE RPC, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>MS Windows 2000, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a></dt><dt>MS Windows NT4/200x, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>MS Windows SID, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>MS WINS, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a></dt><dt>MS-DFS, <a class="indexterm" href="SambaHA.html#id2673231">MS-DFS: The Poor Man's Cluster</a></dt><dt>MS-RPC, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>MS-WINS replication, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>msdfs links, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>msg, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>msg file, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt><dt>MSRPC, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>multibyte character sets, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>multibyte charsets, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>multiple backends, <a class="indexterm" href="passdb.html#id2592500">Password Backends</a></dt><dt>multiple domains, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>multiple hosting, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>multiple modules, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>multiple network interfaces, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></dt><dt>multiple network segments, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>multiple personality, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>multiple server hosting, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>multiple server personalities, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>multiple servers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>multiple universal naming convention provider (see MUP)</dt><dt>multiple VFS, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>multiple virtual servers, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>multiple Windows workgroups or domains, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>multiple WINS servers, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>Multiuser databases, <a class="indexterm" href="locking.html#id2616601">Multiuser Databases</a></dt><dt>mutual assistance, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>mutually exclusive options, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>My Network Places, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a></dt><dt>Myrinet, <a class="indexterm" href="SambaHA.html#id2672898">Server Pool Communications Demands</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>n security context, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>n-memory buffer, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></dt><dt>name conflict, <a class="indexterm" href="classicalprinting.html#id2625120">Any [my_printer_name] Section</a></dt><dt>name lookup, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></dt><dt>name lookups, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>name registration, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a></dt><dt>name resolution, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586352">Common Errors</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a>, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>name resolution across routed networks, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>name resolve order, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></dt><dt>name service switch (see NSS)</dt><dt>name-to-address, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>nameserv.h, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>name_type, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></dt><dt>native ACLs, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>native dump, <a class="indexterm" href="Backup.html#id2671862">Amanda</a></dt><dt>native member, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>native mode, <a class="indexterm" href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="winbind.html#id2654026">Microsoft Active Directory Services</a></dt><dt>NBT, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>nbtstat, <a class="indexterm" href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></dt><dt>necessary rights, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>negotiate, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>negotiating the charset, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>nested group, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>Nested Group Support, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>nested groups, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></dt><dt>net, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599300">Administrative Tasks and Methods</a>, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a>, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dd><dl><dt>ads, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dd><dl><dt>join, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a>, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a>, <a class="indexterm" href="idmapper.html#id2606174">ADS Domains</a></dt><dt>leave, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>printer info, <a class="indexterm" href="NetCommand.html#id2603727">Printers and ADS</a></dt><dt>printer publish, <a class="indexterm" href="NetCommand.html#id2603727">Printers and ADS</a></dt><dt>printer remove, <a class="indexterm" href="NetCommand.html#id2603727">Printers and ADS</a></dt><dt>printer search, <a class="indexterm" href="NetCommand.html#id2603727">Printers and ADS</a></dt><dt>status, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>testjoin, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt></dl></dd><dt>getlocalsid, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>groupmap, <a class="indexterm" href="FastStart.html#id2556880">Example: Engineering Office</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2598124">Example Configuration</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dd><dl><dt>add, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>delete, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>list, <a class="indexterm" href="groupmapping.html#id2598124">Example Configuration</a>, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>modify, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt></dl></dd><dt>localgroup, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>rap, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dd><dl><dt>session, <a class="indexterm" href="NetCommand.html#id2603661">Session and Connection Management</a></dt></dl></dd><dt>rpc, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dd><dl><dt>getsid, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>group, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>group add, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>group addmem, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a>, <a class="indexterm" href="NetCommand.html#id2600610">Managing Nest Groups on Workstations from the Samba Server</a></dt><dt>group delete, <a class="indexterm" href="NetCommand.html#id2600090">Deleting a Group Account</a></dt><dt>group delmem, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></dt><dt>group list, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>group members, <a class="indexterm" href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></dt><dt>group rename, <a class="indexterm" href="NetCommand.html#id2600130">Rename Group Accounts</a></dt><dt>info, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a>, <a class="indexterm" href="ProfileMgmt.html#id2662938">Side Bar Notes</a></dt><dt>join, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dt>join bdc, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>join member, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>list, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>printer migrate drivers, <a class="indexterm" href="NetCommand.html#id2603391">Printer Migration</a></dt><dt>printer migrate forms, <a class="indexterm" href="NetCommand.html#id2603391">Printer Migration</a></dt><dt>printer migrate printers, <a class="indexterm" href="NetCommand.html#id2603391">Printer Migration</a></dt><dt>printer migrate security, <a class="indexterm" href="NetCommand.html#id2603391">Printer Migration</a></dt><dt>printer migrate settings, <a class="indexterm" href="NetCommand.html#id2603391">Printer Migration</a></dt><dt>right list accounts, <a class="indexterm" href="NetCommand.html#id2602878">Share Migration</a></dt><dt>rights grant, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>rights list, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>rights list accounts, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>share add, <a class="indexterm" href="NetCommand.html#id2602550">Creating, Editing, and Removing Shares</a></dt><dt>share delete, <a class="indexterm" href="NetCommand.html#id2602550">Creating, Editing, and Removing Shares</a></dt><dt>share migrate, <a class="indexterm" href="NetCommand.html#id2602878">Share Migration</a></dt><dt>share migrate all, <a class="indexterm" href="NetCommand.html#id2603332">Simultaneous Share and File Migration</a></dt><dt>share migrate files, <a class="indexterm" href="NetCommand.html#id2603074">File and Directory Migration</a></dt><dt>share migrate security, <a class="indexterm" href="NetCommand.html#id2603290">Share-ACL Migration</a></dt><dt>testjoin, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>trustdom add, <a class="indexterm" href="NetCommand.html#id2602049">Interdomain Trusts</a></dt><dt>trustdom establish, <a class="indexterm" href="NetCommand.html#id2602049">Interdomain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></dt><dt>trustdom list, <a class="indexterm" href="NetCommand.html#id2602049">Interdomain Trusts</a></dt><dt>trustdom revoke, <a class="indexterm" href="NetCommand.html#id2602049">Interdomain Trusts</a></dt><dt>user add, <a class="indexterm" href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></dt><dt>user delete, <a class="indexterm" href="NetCommand.html#id2601120">Deletion of User Accounts</a>, <a class="indexterm" href="NetCommand.html#id2601680">Machine Trust Accounts</a></dt><dt>user info, <a class="indexterm" href="NetCommand.html#id2601168">Managing User Accounts</a></dt><dt>user password, <a class="indexterm" href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></dt><dt>user rename, <a class="indexterm" href="NetCommand.html#id2601168">Managing User Accounts</a></dt><dt>vampire, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="NetCommand.html#id2602768">Share, Directory, and File Migration</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt></dl></dd><dt>setlocalsid, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>time, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dd><dl><dt>set, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dt>system, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt><dt>zone, <a class="indexterm" href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></dt></dl></dd><dt>use, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt></dl></dd><dt>NET, <a class="indexterm" href="PolicyMgmt.html#id2660235">Samba PDC</a></dt><dt>net command, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>net getlocalsid, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>net groupmap, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>net rpc user add, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>net tool, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a></dt><dt>net use, <a class="indexterm" href="classicalprinting.html#id2631479">Error Message: Cannot connect under a different Name</a></dt><dt>net use /home, <a class="indexterm" href="ProfileMgmt.html#id2660807">Windows 9x/Me User Profiles</a></dt><dt>net use lpt1:, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></dt><dt>net view, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>netatalk, <a class="indexterm" href="VFS.html#id2651783">netatalk</a></dt><dt>NetAtalk, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Netatalk, <a class="indexterm" href="Other-Clients.html#id2689679">Macintosh Clients</a></dt><dt>NetBEUI, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a></dt><dt>NetBIOS, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html">Integrating MS Windows Networks with Samba</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></dt><dd><dl><dt>brooadcast, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt><dt>name, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>netbios alias, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>netbios aliases, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>NetBIOS broadcast, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>NetBIOS disabled, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a></dt><dt>NetBIOS flags, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>NetBIOS name, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>netbios name, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>NetBIOS name cache, <a class="indexterm" href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></dt><dt>NetBIOS name length, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>NetBIOS name resolution, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>NetBIOS Name Server (see NBNS)</dt><dt>NetBIOS name type, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></dt><dt>NetBIOS network interface, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>NetBIOS networking, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a></dt><dt>NetBIOS over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a></dt><dt>NetBIOS over TCP/IP disabled, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>NetBIOS-less, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>NetBIOS-less SMB, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>NetBIOSless SMB over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>NetBT, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>netlogon, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>NETLOGON, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>Netlogon, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a></dt><dt>NetLogon service, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>netlogon share, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a></dt><dt>Netmon, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>Netmon., <a class="indexterm" href="problems.html#id2685412">Installing Network Monitor on an NT Workstation</a></dt><dt>netmon.exe, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>NetSAMLogon, <a class="indexterm" href="ProfileMgmt.html#id2660603">Roaming Profiles</a></dt><dt>Netscape's Directory Server, <a class="indexterm" href="passdb.html#id2593301">Supported LDAP Servers</a></dt><dt>NetServerEnum2, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>NetUserGetInfo, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ProfileMgmt.html#id2660603">Roaming Profiles</a></dt><dt>NetWare, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>NetWare Bindery, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>NetWare Core Protocol-based server, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>NetWkstaUserLogon, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>network</dt><dd><dl><dt>browsing, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>logon, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dd><dl><dt>service, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt></dl></dd><dt>performance, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>wide-area, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt></dl></dd><dt>network access controls, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>network access profile, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>network administrator, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>network administrator's toolbox, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>network administrators, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>network analyzer, <a class="indexterm" href="problems.html#id2684851">Diagnostics Tools</a></dt><dt>network bandwidth, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>Network Basic Extended User Interface (see NetBEUI)</dt><dt>Network Basic Input/Output System (see NetBIOS)</dt><dt>Network Bridge, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>Network Bridge Configuration, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>network browsing problems, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>network client, <a class="indexterm" href="ClientConfig.html#id2575494">Features and Benefits</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>network clients, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>network configuration problems, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a></dt><dt>network difficulty, <a class="indexterm" href="ClientConfig.html#id2575494">Features and Benefits</a></dt><dt>network environment, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657770">Remote Desktop Management</a></dt><dt>Network ID, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>network interface, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>network logon, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>network logon services, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>network membership, <a class="indexterm" href="ClientConfig.html#id2575554">Technical Details</a></dt><dt>Network Monitor, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>Network Monitor Tools and Agent, <a class="indexterm" href="problems.html#id2685412">Installing Network Monitor on an NT Workstation</a></dt><dt>Network Neighborhood, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>network neighborhood, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>network policies, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></dt><dt>network security, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>network segment, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>Network settings, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>network sniffer, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>network storage, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>network traffic, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>networked workstation, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>networking advocates, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>networking environment, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>networking systems, <a class="indexterm" href="ClientConfig.html#id2578339">Common Errors</a></dt><dt>networks access, <a class="indexterm" href="speed.html#id2691296">Samba Performance is Very Slow</a></dt><dt>Networks Properties, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>new account, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>new parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2676970">New Parameters</a></dt><dt>newsgroup, <a class="indexterm" href="bugreport.html#id2686022">Introduction</a></dt><dt>Nexus toolkit, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Nexus.exe, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>NFS, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a>, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678899">IdMap LDAP Support</a></dt><dt>NFS clients, <a class="indexterm" href="locking.html#id2616518">UNIX or NFS Client-Accessed Files</a></dt><dt>NIS, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>NIS database, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>nmbd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a>, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="winbind.html#id2654865">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2656259">Linux</a>, <a class="indexterm" href="winbind.html#id2656465">Solaris</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a>, <a class="indexterm" href="speed.html#id2691200">Corrupt tdb Files</a></dt><dt>nmblookup, <a class="indexterm" href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>No NetBIOS layer, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></dt><dt>no network logon service, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>no printcap file, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>nobody, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>nobody account, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>node-type, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>NoMachine, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>NoMachine.Com, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>non-authentication-based account management, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>non-authoritative, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>non-LDAP</dt><dd><dl><dt>backend, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt></dl></dd><dt>non-member Windows client, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>non-PostScript, <a class="indexterm" href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>non-PostScript printers, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>nonhierarchical, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>nontransitive, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>normal color, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>normal user, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>not domain member, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>not domain members, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a></dt><dt>not part of domain, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>not stored anywhere, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>not transitive, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>Novell, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>Novell eDirectory server, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>NSS, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a>, <a class="indexterm" href="winbind.html#id2653882">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2657284">Conclusion</a></dt><dt>nsswitch.conf, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a></dt><dt>nss_ldap, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>nss_winbind.so.1, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>NT domain, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>NT groups, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>NT migration scripts, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>NT password, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>NT Server Manager, <a class="indexterm" href="AccessControls.html#id2613132">Windows NT4 Workstation/Server</a></dt><dt>NT-controlled domain, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></dt><dt>NT-encrypted password, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>NT-encrypted passwords, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>NT4, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>NT4 Domain, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a></dt><dt>NT4 domain, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt><dt>NT4 domain members, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>NT4 style policy updates, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>NT4 User Manager for Domains, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>NT4-style, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>NT4-style domain, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>NT4-style domains, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>Nt4sp6ai.exe, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>NTConfig.POL, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659384">Registry Spoiling</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a>, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a>, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>ntconfig.pol, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>ntdrivers.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>ntforms.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTFS, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>NTLMv2, <a class="indexterm" href="securing-samba.html#id2619056">NTLMv2 Security</a></dt><dt>ntlm_auth, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>ntprinters.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTUser.DAT, <a class="indexterm" href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a>, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a>, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>NTuser.DAT, <a class="indexterm" href="ProfileMgmt.html#id2661970">Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a>, <a class="indexterm" href="NT4Migration.html#id2679954">Profile Migration/Creation</a></dt><dt>NTuser.MAN, <a class="indexterm" href="ProfileMgmt.html#id2661970">Windows NT4 Workstation</a></dt><dt>NTUser.MAN, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>NT_STATUS_LOGON_FAILURE, <a class="indexterm" href="upgrading-to-3.0.html#id2678050">Changes in Behavior</a></dt><dt>NT_STATUS_UNSUCCESSFUL, <a class="indexterm" href="classicalprinting.html#id2628952">Running rpcclient with adddriver</a></dt><dt>null shell, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>NX, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>object class, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>object class declaration, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>object module dependencies, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>ObjectClass, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>ObjectClasses, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>obtuse complexity, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>office server, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a></dt><dt>OID, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>old sambaAccount, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>Omni, <a class="indexterm" href="CUPS-printing.html#id2646655">Driver Development Outside</a></dt><dt>on the fly, <a class="indexterm" href="domain-member.html#id2570792">Windows NT4 Client</a></dt><dt>on-the-fly, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>on-the-fly logon scripts, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>on-the-fly policy files, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>one direction, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>one domain, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>one-way trust, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></dt><dt>only one WINS server, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>OpenGFS, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>OpenLDAP, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a>, <a class="indexterm" href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2593301">Supported LDAP Servers</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>OpenLDAP backend, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>OpenSSL, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a>, <a class="indexterm" href="ch-ldap-tls.html#s1-config-ldap-tls-certs">Generating the Certificate Authority</a></dt><dt>operating costs, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>operating system search path, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a></dt><dt>oplock, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>oplock break, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a>, <a class="indexterm" href="locking.html#id2616711">Beware of Force User</a></dt><dt>oplock handling, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a></dt><dt>oplock mechanism, <a class="indexterm" href="locking.html#id2616799">Advanced Samba Oplocks Parameters</a></dt><dt>oplock messages, <a class="indexterm" href="SambaHA.html#id2672953">Required Modifications to Samba</a></dt><dt>oplock parameters, <a class="indexterm" href="locking.html#id2616799">Advanced Samba Oplocks Parameters</a></dt><dt>oplocks, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>oplocks disabled, <a class="indexterm" href="locking.html#id2616601">Multiuser Databases</a></dt><dt>oplocks management, <a class="indexterm" href="locking.html#id2616642">PDM Data Shares</a></dt><dt>opportunistic locking, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a>, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Opportunistic locking, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>optional, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>ordinary connection, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></dt><dt>Organization for the Advancement of Structured Information Standards (see OASIS)</dt><dt>organizational directory, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>organizational unit, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a> (see OU)</dt><dt>os level, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>OSS/Free Software, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>other, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>output duplexing, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a></dt><dt>outside threat, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>own home directory, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>ownership, <a class="indexterm" href="AccessControls.html#id2613591">Viewing File Ownership</a></dt><dt>ownership cost, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>ownership rights, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>p-node, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>package, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>packages, <a class="indexterm" href="install.html#id2551909">Obtaining and Installing Samba</a></dt><dt>packet sniffer, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>packet trace, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>PADL, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>PADL Software, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>page description languages (see PDL)</dt><dt>pager program, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>page_log, <a class="indexterm" href="CUPS-printing.html#id2647713">The page_log File Syntax</a></dt><dt>paid-for support, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>PAM, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="winbind.html#id2653882">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654713">Requirements</a>, <a class="indexterm" href="winbind.html#id2654865">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2657284">Conclusion</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="pam.html#id2665783">Technical Discussion</a></dt><dt>PAM authentication module, <a class="indexterm" href="pam.html#id2665836">PAM Configuration Syntax</a></dt><dt>PAM configuration, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>PAM management, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a></dt><dt>PAM module, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a></dt><dt>PAM modules, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>PAM-capable, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam-devel, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a></dt><dt>PAM-enabled, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>PAM-specific tokens, <a class="indexterm" href="pam.html#id2665836">PAM Configuration Syntax</a></dt><dt>pam_krb5.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_ldap, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>pam_ldap.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_mkhomedir, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>pam_ncp_auth.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_pwdb.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_securetty.so, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>pam_smbpass.so, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_smbpasswd.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_smb_auth.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_unix.so, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_unix2.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_userdb.so, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>pam_winbind.so, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>parameters, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>paranoid, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>passdb, <a class="indexterm" href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a></dt><dt>passdb backend, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a>, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591462">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>passdb backends, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>passed across the network, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>passwd, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>password, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a>, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dd><dl><dt>plaintext, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt></dl></dd><dt>password aging, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>password assigned, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></dt><dt>password backend, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>password backends, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>password change facility, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>password database, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>password encryption, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a></dt><dt>password expiration, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>password expired, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>password history, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>password management, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a></dt><dt>password prompt, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>password scheme, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>password server, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a></dt><dt>password uniqueness, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>passwords, <a class="indexterm" href="winbind.html#id2653468">Introduction</a></dt><dt>patch, <a class="indexterm" href="bugreport.html#id2686807">Patches</a></dt><dt>path specified, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>pauses, <a class="indexterm" href="speed.html#id2691296">Samba Performance is Very Slow</a></dt><dt>PBM, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>PCL, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a>, <a class="indexterm" href="CUPS-printing.html#id2640155">Printing with Interface Scripts</a>, <a class="indexterm" href="CUPS-printing.html#id2640399">Driver Execution on the Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640792">Network PostScript RIP</a></dt><dt>pdbedit, <a class="indexterm" href="FastStart.html#id2556880">Example: Engineering Office</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a>, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a>, <a class="indexterm" href="passdb.html#id2591374">Adding User Accounts</a>, <a class="indexterm" href="passdb.html#id2591462">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592375">Account Import/Export</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a>, <a class="indexterm" href="PolicyMgmt.html#id2660235">Samba PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a>, <a class="indexterm" href="NT4Migration.html#id2680047">Steps in Migration Process</a>, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>pdb_ldap, <a class="indexterm" href="samba-bdc.html#id2568859">Can I Do This All with LDAP?</a></dt><dt>PDC, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566688">Example PDC Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a>, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a>, <a class="indexterm" href="CUPS-printing.html#id2643159">cupsaddsmb with a Samba PDC</a>, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a>, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654536">Result Caching</a>, <a class="indexterm" href="winbind.html#id2654599">Introduction</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a>, <a class="indexterm" href="problems.html#id2685716">Getting Mailing List Help</a>, <a class="indexterm" href="speed.html#id2691200">Corrupt tdb Files</a></dt><dt>PDF, <a class="indexterm" href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>pdf, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>PDF distilling, <a class="indexterm" href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a></dt><dt>PDF filter, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>pdftops, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a>, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>pdftosocket, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>PDL, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a></dt><dt>PDM, <a class="indexterm" href="locking.html#id2616642">PDM Data Shares</a></dt><dt>peer domain, <a class="indexterm" href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></dt><dt>Peer node, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>per-share access control, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>performance, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>performance advantage, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a></dt><dt>performance degradation, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>performance enhancement, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>performance improvement, <a class="indexterm" href="locking.html#id2616553">Slow and/or Unreliable Networks</a></dt><dt>performance-based, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a></dt><dt>performed as root, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>perimeter firewall, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>permanent changes, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>Permanent name, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>permissions, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dd><dl><dt>file/directory ACLs, <a class="indexterm" href="AccessControls.html#id2613473">Managing UNIX Permissions Using NT Security Dialogs</a></dt><dt>share, <a class="indexterm" href="AccessControls.html#id2611896">Share Definition Access Controls</a></dt><dt>share ACLs, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>UNIX file and directory, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt></dl></dd><dt>Permissions, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>permissions and controls, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>PGP, <a class="indexterm" href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></dt><dt>phasing out NetBIOS, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a></dt><dt>Photo-CD, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>physical locations, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>physical network transport layer, <a class="indexterm" href="integrate-ms-networks.html#id2668281">/etc/hosts</a></dt><dt>PID, <a class="indexterm" href="bugreport.html#id2686682">Attaching to a Running Process</a></dt><dt>pid directory, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>ping, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>pipe device, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>PJL, <a class="indexterm" href="CUPS-printing.html#id2640792">Network PostScript RIP</a>, <a class="indexterm" href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a>, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>PJL-header, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>plague network users, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a></dt><dt>plain-text</dt><dd><dl><dt>passwords, <a class="indexterm" href="ServerType.html#id2560539">Password Checking</a></dt></dl></dd><dt>plaintext, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>plaintext authentication, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>plaintext password, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a></dt><dt>plaintext passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>platforms, <a class="indexterm" href="Portability.html">Portability</a></dt><dt>PLP, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>Pluggable Authentication Modules (see PAM)</dt><dt>PNG, <a class="indexterm" href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>PNM, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>point 'n' print, <a class="indexterm" href="CUPS-printing.html#id2634448">Installation of Windows Client Drivers</a>, <a class="indexterm" href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt><dt>Point'n'Print, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="classicalprinting.html#id2628816">smbclient to Confirm Driver Installation</a></dt><dt>point'n'print, <a class="indexterm" href="CUPS-printing.html#id2634735">Driver Upload Methods</a>, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></dt><dt>Poledit, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a></dt><dt>poledit.exe, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a>, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a></dt><dt>Policies, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>policies, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>policy editor, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></dt><dt>Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>policy file , <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>policy files, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>policy settings, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>port 135, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></dt><dt>Port 135/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 137, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>Port 137/UDP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 138, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></dt><dt>Port 138/UDP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 139, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></dt><dt>Port 139/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>port 445, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></dt><dt>Port 445/TCP, <a class="indexterm" href="securing-samba.html#firewallports">Using a Firewall</a></dt><dt>ports, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a>, <a class="indexterm" href="problems.html#id2685209">Ethereal</a></dt><dt>POSIX, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a>, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>POSIX account, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a>, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dt>POSIX ACLs, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a>, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>POSIX ACLS, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>POSIX identity, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>POSIX locks, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a></dt><dt>POSIX semantics, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a></dt><dt>POSIX user accounts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>posixAccount, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>posixGroup, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a></dt><dt>PostScript, <a class="indexterm" href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a>, <a class="indexterm" href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a>, <a class="indexterm" href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a>, <a class="indexterm" href="CUPS-printing.html#id2640399">Driver Execution on the Server</a>, <a class="indexterm" href="CUPS-printing.html#id2640792">Network PostScript RIP</a>, <a class="indexterm" href="CUPS-printing.html#id2641066">CUPS: A Magical Stone?</a>, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></dt><dd><dl><dt>(see also Ghostscript)</dt><dt>RIP, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt></dl></dd><dt>PostScript driver, <a class="indexterm" href="classicalprinting.html#id2628597">Installing Driver Files into [print$]</a></dt><dt>PostScript interpreter, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PostScript Printer Description (see PPD)</dt><dt>PostScript printers, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dt>potential master browsers, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>potential printer, <a class="indexterm" href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></dt><dt>Power Users, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>powerful, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>PPD, <a class="indexterm" href="classicalprinting.html#id2628597">Installing Driver Files into [print$]</a>, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a class="indexterm" href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a>, <a class="indexterm" href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a>, <a class="indexterm" href="CUPS-printing.html#id2638596">Raw Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2640882">PPDs for Non-PS Printers on UNIX</a>, <a class="indexterm" href="CUPS-printing.html#id2640927">PPDs for Non-PS Printers on Windows</a>, <a class="indexterm" href="CUPS-printing.html#id2641066">CUPS: A Magical Stone?</a>, <a class="indexterm" href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a>, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dd><dl><dt>CUPS (see CUPS-PPD)</dt></dl></dd><dt>PPD-aware, <a class="indexterm" href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PPDs, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a>, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a>, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>PPP, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>precedence, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></dt><dt>preferred master, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></dt><dt>prefilter, <a class="indexterm" href="CUPS-printing.html#id2637637">imagetops and imagetoraster</a></dt><dt>prefilters, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a></dt><dt>primary domain controller, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></dt><dt>primary group, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>Primary Logon, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>Primary WINS Server, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>print, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dd><dl><dt>queue, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>spooler, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt></dl></dd><dt>print accounting, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>print command, <a class="indexterm" href="classicalprinting.html#id2625414">Print Commands</a></dt><dt>print commands, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>print configuration, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dt>print environment, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>print filtering, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>print job, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>print jobs, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>print processing, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>print queue, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="classicalprinting.html#id2628816">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="classicalprinting.html#id2629446">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2637941">CUPS Backends</a></dt><dt>print quota, <a class="indexterm" href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></dt><dt>print server, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>print service, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>print spooling, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></dt><dt>print spooling system, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>print statistics, <a class="indexterm" href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></dt><dt>print subsystem, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a>, <a class="indexterm" href="classicalprinting.html#id2625414">Print Commands</a></dt><dt>print test page, <a class="indexterm" href="classicalprinting.html#id2629717">First Client Driver Installation</a></dt><dt>printcap, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a>, <a class="indexterm" href="classicalprinting.html#ptrsect">The [printers] Section</a></dt><dt>Printcap, <a class="indexterm" href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></dt><dt>printcap name, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>PrintcapFormat, <a class="indexterm" href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></dt><dt>printer attributes publishing, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>printer default permissions, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printer driver, <a class="indexterm" href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a>, <a class="indexterm" href="classicalprinting.html#id2626995">Creating the [print$] Share</a>, <a class="indexterm" href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a></dt><dt>printer driver data, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>printer driver file, <a class="indexterm" href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></dt><dt>printer driver files, <a class="indexterm" href="classicalprinting.html#id2628816">smbclient to Confirm Driver Installation</a></dt><dt>printer drivers, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a>, <a class="indexterm" href="CUPS-printing.html#id2646526">The Grand Unification Achieved</a></dt><dt>printer icon, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>printer management, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>printer management system, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>printer migration, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>printer monitor, <a class="indexterm" href="speed.html#id2691296">Samba Performance is Very Slow</a></dt><dt>printer objects, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>Printer Pooling, <a class="indexterm" href="classicalprinting.html#id2631902">Samba and Printer Ports</a></dt><dt>printer queue, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printer share, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>printer shares , <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>printer$ share, <a class="indexterm" href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></dt><dt>printers, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>Printers, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>printers admin, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>Printers and Faxes, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>printers available, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>printers section, <a class="indexterm" href="classicalprinting.html#ptrsect">The [printers] Section</a></dt><dt>printing, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>printing behavior, <a class="indexterm" href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a></dt><dt>printing calls, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>printing now, <a class="indexterm" href="speed.html#id2691296">Samba Performance is Very Slow</a></dt><dt>printing support, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>printing system, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>printing systems, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>printing-related settings, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dt>printing.tdb, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>PrintPro (see ESP Print Pro)</dt><dt>private dir, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>private groups, <a class="indexterm" href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></dt><dt>private key, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt><dt>private network, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a></dt><dt>private networks, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>private/MACHINE.SID, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></dt><dt>private/secrets.tdb, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></dt><dt>privilege, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>privilege management, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>privilege model, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a></dt><dt>privilege-granting applications, <a class="indexterm" href="pam.html#id2665783">Technical Discussion</a></dt><dt>privileged accounts, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>privileges, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>privileges assigned, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>problem report, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>problem resolution, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>problematic print, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>Process data management, <a class="indexterm" href="locking.html#id2616642">PDM Data Shares</a></dt><dt>professional support, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>profile, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>profile access rights, <a class="indexterm" href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></dt><dt>profile contents, <a class="indexterm" href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>profile directory, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>profile migration tool, <a class="indexterm" href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></dt><dt>profile path, <a class="indexterm" href="samba-bdc.html#id2566688">Example PDC Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="ProfileMgmt.html#id2661970">Windows NT4 Workstation</a></dt><dt>profile sharing, <a class="indexterm" href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>Profile Type, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a></dt><dt>ProfilePath, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>profiles, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>Profiles, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></dt><dt>project, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>promiscuous mode, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>promote, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a></dt><dt>promoted, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>propagate, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt><dt>Properties, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>protect directories, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>protect files, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>protection against attackers, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>protocol stack settings, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>provided services, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>provisioned, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>pstops, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a>, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a>, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>pstoraster, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a>, <a class="indexterm" href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>publish printers, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>publishing printers, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>PulseAudio, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>punching, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a></dt><dt>purchase support, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>put, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>pvcreate, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>QNX, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>qualified problem, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>queue control, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>quota controls, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>random machine account password, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>range, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dt>range of hosts, <a class="indexterm" href="securing-samba.html#id2618343">Using Host-Based Protection</a></dt><dt>RAP, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>raster, <a class="indexterm" href="CUPS-printing.html#id2637012">Prefilters</a>, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>raster driver, <a class="indexterm" href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></dt><dt>raster drivers, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>raster image processor (see RIP)</dt><dt>raster images, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>rasterization, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a>, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>rastertoalps, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertobj, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertoepson, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a>, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>rastertoescp, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertohp, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertopcl, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertoprinter, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>rastertosomething, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>rastertoturboprint, <a class="indexterm" href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></dt><dt>raw mode, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>raw print, <a class="indexterm" href="CUPS-printing.html#id2643240">cupsaddsmb Flowchart</a></dt><dt>raw printers, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>raw printing, <a class="indexterm" href="FastStart.html#id2554843">Anonymous Print Server</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a>, <a class="indexterm" href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></dt><dt>raw SMB, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>raw SMB over TCP/IP, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></dt><dt>rawprinter, <a class="indexterm" href="CUPS-printing.html#id2638596">Raw Printing</a></dt><dt>rcp, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>rdesktop, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>rdesktop/RDP, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>read, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>read directory into memory, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>read only, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dd><dl><dt>server, <a class="indexterm" href="FastStart.html#anon-ro">Anonymous Read-Only Document Server</a></dt></dl></dd><dt>Read-ahead, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>read-only, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>read-only access, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>read-only files, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>read-write access, <a class="indexterm" href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></dt><dt>realm, <a class="indexterm" href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a>, <a class="indexterm" href="samba-bdc.html#id2567576">NetBIOS Over TCP/IP Disabled</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></dt><dt>rebooted, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>rebooting server, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>recompiling, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>reconfiguration, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>record locking, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>recycle, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle bin, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>recycle directory, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:exclude, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:exclude_dir, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:keeptree, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:maxsize, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:noversions, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:repository, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:subdir_mode, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:touch, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>recycle:versions, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>Red Hat Cluster Manager, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>Red Hat Linux, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a>, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a>, <a class="indexterm" href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></dt><dt>redirect, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a></dt><dt>redirection, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>redirector, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>redundancy, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>reference documents, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>refusing connection, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a></dt><dt>regedit.exe, <a class="indexterm" href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></dt><dt>regedt32, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></dt><dt>regedt32.exe, <a class="indexterm" href="PolicyMgmt.html#id2660194">Windows NT4/200x</a></dt><dt>register driver files, <a class="indexterm" href="classicalprinting.html#id2628952">Running rpcclient with adddriver</a></dt><dt>register NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>registered, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>registers, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a></dt><dt>registry, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="locking.html#id2615585">Features and Benefits</a>, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></dt><dt>registry change, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>registry keys, <a class="indexterm" href="ProfileMgmt.html#id2663314">Default Profile for Windows Users</a></dt><dt>registry settings, <a class="indexterm" href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></dt><dt>regulations, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>rejoin, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>relationship password, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>relative identifier, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a> (see RID)</dt><dt>Relative Identifier (see RID)</dt><dt>Relative Identifiers (see RID)</dt><dt>reliability, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>Remote Access Dial-In User Service (see RADIUS)</dt><dt>remote announce, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>remote browse sync, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>remote desktop capabilities, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>remote desktop management, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657770">Remote Desktop Management</a></dt><dt>remote domain, <a class="indexterm" href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>remote login, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>remote management, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></dt><dt>Remote Procedure Call (see RPC)</dt><dt>Remote Procedure Call System Service (see RPCSS)</dt><dt>remote profile, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>remote segment, <a class="indexterm" href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>Remote X, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>Remote X protocol, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>remote-update protocol, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>rename, <a class="indexterm" href="AccessControls.html#id2611102">Managing Directories</a></dt><dt>render, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>rendering, <a class="indexterm" href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></dt><dt>repeated intervals, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>replicate, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>replicated, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2567305">Active Directory Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></dt><dt>replicated SYSVOL, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></dt><dt>replication, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dd><dl><dt>browse lists, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>SAM, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a></dt><dt>WINS, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584164">WINS Replication</a></dt></dl></dd><dt>replication protocols, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>repository, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>requesting payment, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>required, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>requisite, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>research, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>resizing, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>resolution, <a class="indexterm" href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></dt><dt>resolution of NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a></dt><dt>resolve NetBIOS names, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></dt><dt>resolver functions, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>resource failover, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>resource kit, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="ProfileMgmt.html#profilemigrn">Windows NT4 Profile Management Tools</a></dt><dt>resource-based exclusion, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>response, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></dt><dt>restore, <a class="indexterm" href="tdb.html#id2686891">Features and Benefits</a></dt><dt>restrict DNS, <a class="indexterm" href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></dt><dt>reviewers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>revoke privileges, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>RFC 1001, <a class="indexterm" href="DNSDHCP.html#id2693042">Example Configuration</a></dt><dt>RFC 1002, <a class="indexterm" href="DNSDHCP.html#id2693042">Example Configuration</a></dt><dt>RFC 1179, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>RFC 2307, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt><dt>RFC 2307., <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt>RFC 2830, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>rfc2307bis, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>RFC2830, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>RFCs, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>rich database backend, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>rich directory backend, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>RID, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a>, <a class="indexterm" href="winbind.html#id2654460">User and Group ID Allocation</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>RID 500, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>RID base, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>right to join domain, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>rights, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a></dt><dt>rights and privilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></dt><dt>rights and privileges, <a class="indexterm" href="groupmapping.html#id2597258">Important Administrative Information</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>rights assigned, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>RIP, <a class="indexterm" href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></dt><dt>rlogind, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>Roaming Profile, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dt>roaming profiles, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="ProfileMgmt.html#id2660554">Features and Benefits</a>, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>rogue machine, <a class="indexterm" href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></dt><dt>rogue user, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>root, <a class="indexterm" href="domain-member.html#id2570628">Windows 200x/XP Professional Client</a>, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>root account, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>root user, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>rotate, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>RPC, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="ProfileMgmt.html#id2660603">Roaming Profiles</a></dt><dt>RPC calls, <a class="indexterm" href="winbind.html#id2657284">Conclusion</a>, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>RPC modules, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>rpc.lockd, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>rpcclient, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a>, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2629446">Specific Driver Name Flexibility</a>, <a class="indexterm" href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a>, <a class="indexterm" href="PolicyMgmt.html#id2660235">Samba PDC</a></dt><dd><dl><dt>adddriver, <a class="indexterm" href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2643902">Understanding the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt><dt>enumdrivers, <a class="indexterm" href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt><dt>enumports, <a class="indexterm" href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a></dt><dt>enumprinters, <a class="indexterm" href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></dt><dt>getdriver, <a class="indexterm" href="CUPS-printing.html#id2644007">Producing an Example by Querying a Windows Box</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt><dt>getprinter, <a class="indexterm" href="CUPS-printing.html#id2644007">Producing an Example by Querying a Windows Box</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></dt><dt>setdriver, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a>, <a class="indexterm" href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a>, <a class="indexterm" href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a>, <a class="indexterm" href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a>, <a class="indexterm" href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></dt></dl></dd><dt>rsh, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>rsync, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a>, <a class="indexterm" href="Backup.html#id2671692">Rsync</a>, <a class="indexterm" href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></dt><dt>rsyncd, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>runas, <a class="indexterm" href="classicalprinting.html#id2630401">Always Make First Client Connection as root or printer admin</a></dt><dt>rundll32, <a class="indexterm" href="classicalprinting.html#id2630283">Additional Client Driver Installation</a>, <a class="indexterm" href="classicalprinting.html#id2630595">Setting Default Print Options for Client Drivers</a>, <a class="indexterm" href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658585">Adding Printers without User Intervention</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>SAM, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a>, <a class="indexterm" href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="winbind.html#id2654536">Result Caching</a></dt><dd><dl><dt>delta file, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>replication, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt></dl></dd><dt>SAM backend, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dd><dl><dt>LDAP, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt><dt>ldapsam, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>ldapsam_compat, <a class="indexterm" href="passdb.html#id2587230">Features and Benefits</a></dt><dt>non-LDAP, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt><dt>smbpasswd, <a class="indexterm" href="passdb.html#id2587230">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>tdbsam, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a></dt></dl></dd><dt>Samba 1.9.17, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>Samba account, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>Samba administrator, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>Samba backend database, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>Samba daemons, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>Samba differences, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>Samba mailing lists, <a class="indexterm" href="Backup.html#id2671379">Features and Benefits</a></dt><dt>Samba private directory, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>Samba SAM, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>Samba SAM account, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>Samba SAM account flags, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a></dt><dt>Samba schema, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>Samba security, <a class="indexterm" href="securing-samba.html#id2618181">Features and Benefits</a></dt><dt>Samba-2.2.x LDAP schema, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></dt><dt>Samba-3-compatible LDAP backend, <a class="indexterm" href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></dt><dt>Samba-PDC-LDAP-HOWTO, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>samba-to-samba trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>samba-vscan, <a class="indexterm" href="VFS.html#id2652821">vscan</a></dt><dt>samba.schema, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>sambaDomain, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>sambaGroupMapping, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>sambaHomeDrive, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>sambaHomePath, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>sambaIdmapEntry, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>sambaLogonScript, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>SambaNTPassword, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>sambaProfilePath, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>SambaSAMAccount, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#id2591374">Adding User Accounts</a>, <a class="indexterm" href="passdb.html#id2591462">Deleting Accounts</a>, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a></dt><dt>sambaSamAccount, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a>, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>sambaSAMAccount, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>sambaSID, <a class="indexterm" href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></dt><dt>sambaUNIXIdPool, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>SambaXP conference, <a class="indexterm" href="SambaHA.html#id2672127">Technical Discussion</a></dt><dt>samdb interface, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>same domain/workgroup, <a class="indexterm" href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></dt><dt>Sarbanes-Oxley, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a></dt><dt>scalability, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a></dt><dt>scalable, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>scalable backend, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a></dt><dt>scalable coherent interface (see SCI)</dt><dt>scale, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>scanner module, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>schannel, <a class="indexterm" href="samba-pdc.html#id2565592">Cannot Log onto Domain Member Workstation After Joining Domain</a></dt><dt>schema, <a class="indexterm" href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></dt><dt>schema file, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>scp, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>script, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>scripted control, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>scripts, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>SCSI, <a class="indexterm" href="SambaHA.html#id2673091">High-Availability Server Products</a></dt><dt>SeAddUsersPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>SeAssignPrimaryTokenPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeAuditPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeBackupPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeChangeNotifyPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>Seclib, <a class="indexterm" href="AccessControls.html#id2613591">Viewing File Ownership</a></dt><dt>secondary controller, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>SeCreateGlobalPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreatePagefilePrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreatePermanentPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeCreateTokenPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>secret, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>secrets.tdb, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>section name, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>secure, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>secure access, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>secure authentication, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>secure communications, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>secured networks, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a></dt><dt>security, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="securing-samba.html#id2618082">Introduction</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dd><dl><dt>controllers, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt><dt>modes, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a></dt><dt>settings, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt></dl></dd><dt>security = user, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>security account, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>Security Account Manager (see SAM)</dt><dt>Security Assertion Markup Language (see SAML)</dt><dt>security context, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>security contexts, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>security credentials, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a></dt><dt>security domain, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>security domains, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>security flaw, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>security hole, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>security identifier, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a> (see SID)</dt><dt>security level, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a></dt><dt>security levels, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a></dt><dt>security mode, <a class="indexterm" href="ServerType.html">Server Types and Security Modes</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>Security Mode, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a></dt><dt>security modes, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a></dt><dt>security name-space, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a></dt><dt>security policies, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>security settings, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>security structure, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>security vulnerability, <a class="indexterm" href="securing-samba.html#id2619110">Upgrading Samba</a></dt><dt>security-aware, <a class="indexterm" href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></dt><dt>SeDebugPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeDiskOperatorPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>SeEnableDelegationPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeImpersonatePrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeIncreaseBasePriorityPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeIncreaseQuotaPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeLoadDriverPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeLockMemoryPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeMachineAccountPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeManageVolumePrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>separate instances, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>separate servers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>separate shares, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>separate workgroups, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>SePrintOperatorPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>SeProfileSingleProcessPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeRemoteShutdownPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeRestorePrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>server failure, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>Server Manager, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>Server Manager for Domains, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>Server Message Block (see SMB)</dt><dt>server pool, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a></dt><dt>Server Type, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a></dt><dd><dl><dt>Domain Controller, <a class="indexterm" href="FastStart.html#id2556800">Domain Controller</a></dt><dt>Domain Member, <a class="indexterm" href="FastStart.html#id2555957">Domain Member Server</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>Stand-alone, <a class="indexterm" href="FastStart.html#id2554216">Standalone Server</a></dt></dl></dd><dt>server type, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dd><dl><dt>domain member, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a></dt></dl></dd><dt>Server Types, <a class="indexterm" href="idmapper.html#id2604449">Samba Server Deployment Types and IDMAP</a></dt><dt>server-mode, <a class="indexterm" href="ServerType.html#id2560788">What Makes Samba a Domain Controller?</a></dt><dt>service name, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>service-level, <a class="indexterm" href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>services provided, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>SeSecurityPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeShutdownPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>session, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>session services, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>session setup, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a>, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a></dt><dt>sessionid.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>SessionSetupAndX, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>SeSyncAgentPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemEnvironmentPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemProfilePrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeSystemtimePrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>set a password, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>set group id (see SGID)</dt><dt>set printer properties, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>set user id (see SUID)</dt><dt>SeTakeOwnershipPrivilege, <a class="indexterm" href="NetCommand.html#id2601320">Administering User Rights and Privileges</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>SeTcbPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>setdriver, <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a>, <a class="indexterm" href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a></dt><dt>SetPrinter(), <a class="indexterm" href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></dt><dt>setting up directories, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>SeUndockPrivilege, <a class="indexterm" href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></dt><dt>severely impaired, <a class="indexterm" href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></dt><dt>SFU, <a class="indexterm" href="idmapper.html#id2608030">IDMAP, Active Directory, and MS Services for UNIX 3.5</a></dt><dt>SFU 3.5, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a></dt><dt>SGI-RGB, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>SGID, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>shadow, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dt>shadow copies, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>shadow password file, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>shadow utilities, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>shadow_copy, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a>, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>shadow_copy module, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a></dt><dt>share, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a>, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>share access, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>share ACLs, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>share management, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>share modes, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>share permissions, <a class="indexterm" href="AccessControls.html#id2613132">Windows NT4 Workstation/Server</a></dt><dt>Share Permissions, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>share settings, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>share stanza controls, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>share-level, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a>, <a class="indexterm" href="ServerType.html#id2559434">Share-Level Security</a>, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>share-level ACLs, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>share-mode, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>share-mode security, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>share-mode server, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>shared secret, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>shares, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>shares and files, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>share_info.tdb, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>Sharing, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>shell scripts, <a class="indexterm" href="classicalprinting.html#id2625414">Print Commands</a></dt><dt>shift, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>Shift_JIS, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>shortcuts, <a class="indexterm" href="ClientConfig.html#id2575598">TCP/IP Configuration</a>, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>Shortcuts, <a class="indexterm" href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>show-stopper-type, <a class="indexterm" href="NT4Migration.html#id2679067">Planning and Getting Started</a></dt><dt>SID, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2565350">The System Cannot Log You On (C000019B)</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="idmapper.html#id2606584">IDMAP_RID with Winbind</a>, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a>, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a>, <a class="indexterm" href="ProfileMgmt.html#id2662938">Side Bar Notes</a>, <a class="indexterm" href="ProfileMgmt.html#id2663030">Get SID</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a>, <a class="indexterm" href="NT4Migration.html#id2679954">Profile Migration/Creation</a></dt><dt>SID management, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>SID-to-GID, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a></dt><dt>SIDs, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>signing, <a class="indexterm" href="samba-pdc.html#id2565592">Cannot Log onto Domain Member Workstation After Joining Domain</a></dt><dt>simple access controls, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>simple configuration, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>simple guide, <a class="indexterm" href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></dt><dt>Simple Object Access Protocol (see SOAP)</dt><dt>simple operation, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>simple print server, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt><dt>simple printing, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>simplest</dt><dd><dl><dt>configuration, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt></dl></dd><dt>simplicity, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a></dt><dt>Simplicity is king, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>single DHCP server, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>single repository, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>single server, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>single sign-on, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a> (see SSO)</dt><dt>Single Sign-On, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>single-byte charsets, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>single-logon, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>single-sign-on, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>single-user mode, <a class="indexterm" href="winbind.html#id2654713">Requirements</a></dt><dt>slapadd, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a></dt><dt>slapd, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>slapd.conf, <a class="indexterm" href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a>, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>slapd.pem, <a class="indexterm" href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></dt><dt>slapindex, <a class="indexterm" href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></dt><dt>slappasswd, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a></dt><dt>slave servers, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>slow browsing, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>slow network, <a class="indexterm" href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></dt><dt>slow network browsing, <a class="indexterm" href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></dt><dt>slow performance, <a class="indexterm" href="speed.html#id2691296">Samba Performance is Very Slow</a></dt><dt>smart printers, <a class="indexterm" href="CUPS-printing.html#id2633040">Overview</a></dt><dt>SMB, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a>, <a class="indexterm" href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a>, <a class="indexterm" href="securing-samba.html#id2618557">Using Interface Protection</a>, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a>, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a>, <a class="indexterm" href="problems.html">Analyzing and Solving Samba Problems</a></dt><dt>SMB encryption, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>SMB locks, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a></dt><dt>SMB name, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></dt><dt>SMB networking, <a class="indexterm" href="problems.html#id2684851">Diagnostics Tools</a></dt><dt>SMB password, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt><dt>SMB Password, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>SMB password encryption, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>smb ports, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>SMB printers, <a class="indexterm" href="CUPS-printing.html#id2649452">Administrator Cannot Install Printers for All Local Users</a></dt><dt>SMB requests, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>SMB semantics, <a class="indexterm" href="SambaHA.html#id2672609">The Distributed File System Challenge</a></dt><dt>SMB server, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>SMB Server, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>SMB services, <a class="indexterm" href="SambaHA.html#id2672736">Restrictive Constraints on Distributed File Systems</a></dt><dt>SMB signing, <a class="indexterm" href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>SMB state information, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>SMB-based messaging, <a class="indexterm" href="NetworkBrowsing.html#netdiscuss">Discussion</a></dt><dt>smb-cdserver.conf, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>smb.conf, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>SMB/CIFS, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a>, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a>, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>SMB/CIFS server, <a class="indexterm" href="passdb.html#id2592500">Password Backends</a></dt><dt>smbclient, <a class="indexterm" href="domain-member.html#ads-test-smbclient">Testing with smbclient</a>, <a class="indexterm" href="classicalprinting.html#id2628597">Installing Driver Files into [print$]</a>, <a class="indexterm" href="classicalprinting.html#id2628816">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>smbd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="install.html#id2553073">Example Configuration</a>, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2594040">Configuring Samba</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a>, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a>, <a class="indexterm" href="VFS.html#id2651060">extd_audit</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2654865">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a>, <a class="indexterm" href="winbind.html#id2656259">Linux</a>, <a class="indexterm" href="winbind.html#id2656465">Solaris</a>, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a>, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>smbgroupedit, <a class="indexterm" href="NetCommand.html">Remote and Local Management: The Net Command</a></dt><dt>smbgrpadd.sh, <a class="indexterm" href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a></dt><dt>smbHome, <a class="indexterm" href="passdb.html#id2594813">LDAP Special Attributes for sambaSamAccounts</a></dt><dt>smbldap-groupadd, <a class="indexterm" href="NetCommand.html#id2599581">Adding or Creating a New Group</a></dt><dt>smbldap-tools, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a></dt><dt>smbpasswd, <a class="indexterm" href="ServerType.html#id2559841">Example Configuration</a>, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2572100">Configure smb.conf</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a>, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a>, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a>, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a>, <a class="indexterm" href="passdb.html#id2592375">Account Import/Export</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2593053">ldapsam</a>, <a class="indexterm" href="passdb.html#id2593356">Schema and Relationship to the RFC 2307 posixAccount</a>, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="PolicyMgmt.html#id2660235">Samba PDC</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678146">Passdb Backends and Authentication</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2678340">New Schema</a></dt><dt>smbpasswd format, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a></dt><dt>smbpasswd plaintext database, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>SMBsessetupX, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>smbspool, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dt>smbstatus, <a class="indexterm" href="CUPS-printing.html#id2649260">Avoid Being Connected to the Samba Server as the Wrong User</a>, <a class="indexterm" href="bugreport.html#id2686682">Attaching to a Running Process</a></dt><dt>SMBtconX, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a></dt><dt>smbusers, <a class="indexterm" href="securing-samba.html#id2618497">User-Based Protection</a></dt><dt>SMS, <a class="indexterm" href="problems.html#id2685353">The Windows Network Monitor</a></dt><dt>Snapshots, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>sniffer, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="problems.html#id2684851">Diagnostics Tools</a></dt><dt>socket, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>socket address, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>SOFTQ printing system, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>Solaris, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Solaris 9, <a class="indexterm" href="winbind.html#id2656465">Solaris</a></dt><dt>source code, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>space character, <a class="indexterm" href="groupmapping.html#id2598524">Adding Groups Fails</a></dt><dt>special account, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>special section, <a class="indexterm" href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></dt><dt>special sections, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>special stanza, <a class="indexterm" href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></dt><dt>specific restrictions, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>Specify an IP address, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>spinning process, <a class="indexterm" href="bugreport.html#id2686682">Attaching to a Running Process</a></dt><dt>spool, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dd><dl><dt>directory, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt></dl></dd><dt>spool files, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>spooled file, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>spooler., <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a></dt><dt>spooling, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a>, <a class="indexterm" href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></dt><dd><dl><dt>central, <a class="indexterm" href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></dt><dt>peer-to-peer, <a class="indexterm" href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></dt></dl></dd><dt>spooling path, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></dt><dt>spooling-only, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>SPOOLSS, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>SQL, <a class="indexterm" href="ChangeNotes.html#id2579081">Passdb Changes</a></dt><dt>SQUID, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>SRV records, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></dt><dt>SRV RR, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a></dt><dt>SrvMgr.exe, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>srvmgr.exe, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>SRVTOOLS.EXE, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>ssh, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>SSH, <a class="indexterm" href="classicalprinting.html#id2628816">smbclient to Confirm Driver Installation</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>SSL, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt><dt>SSO, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589094">Comments Regarding LDAP</a></dt><dt>stability, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>stack trace, <a class="indexterm" href="bugreport.html#id2686549">Internal Errors</a></dt><dt>stale network links, <a class="indexterm" href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></dt><dt>stand-alone server, <a class="indexterm" href="idmapper.html#id2604474">Standalone Samba Server</a></dt><dt>standalone, <a class="indexterm" href="ServerType.html#id2558964">Server Types</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>standalone filter, <a class="indexterm" href="CUPS-printing.html#id2637368">pstoraster</a></dt><dt>standalone server, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="StandAloneServer.html">Standalone Servers</a>, <a class="indexterm" href="StandAloneServer.html#id2574148">Features and Benefits</a>, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="passdb.html#id2591374">Adding User Accounts</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a>, <a class="indexterm" href="NT4Migration.html#id2679511">Domain Layout</a></dt><dt>standard confirmation, <a class="indexterm" href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></dt><dt>stanza, <a class="indexterm" href="install.html#id2551991">Configuration File Syntax</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>stapling, <a class="indexterm" href="CUPS-printing.html#id2637200">pstops</a></dt><dt>StartDocPrinter, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>starting samba</dt><dd><dl><dt>nmbd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a></dt><dt>smbd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2555208">Secure Read-Write File and Print Server</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a></dt><dt>winbindd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a></dt></dl></dd><dt>startsmb, <a class="indexterm" href="compiling.html#id2688724">Alternative: Starting smbd as a Daemon</a></dt><dt>StartTLS, <a class="indexterm" href="passdb.html#id2594577">Security and sambaSamAccount</a></dt><dt>startup</dt><dd><dl><dt>process, <a class="indexterm" href="install.html#id2552892">Starting Samba</a></dt></dl></dd><dt>startup script, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>state, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>state information, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>state of knowledge, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>static WINS entries, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>status32 codes, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>sticky bit, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a>, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>storage mechanism, <a class="indexterm" href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dt>storage methods, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt><dt>stphoto2.ppd, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>strange delete semantics, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>stripped of comments, <a class="indexterm" href="SWAT.html#id2681092">Features and Benefits</a></dt><dt>strptime, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>stunnel, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt><dt>su, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>subnet mask, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>subnets, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></dt><dt>subscription, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>subsuffix parameters, <a class="indexterm" href="upgrading-to-3.0.html#id2678733">New Suffix for Searching</a></dt><dt>Subversion, <a class="indexterm" href="compiling.html#id2687549">Introduction</a>, <a class="indexterm" href="compiling.html#id2687639">Access via Subversion</a></dt><dt>successful join, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a></dt><dt>successful migration, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>sufficient, <a class="indexterm" href="pam.html#id2665915">Anatomy of /etc/pam.d Entries</a></dt><dt>suffixes, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>SUID, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>Sun, <a class="indexterm" href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dt>Sun ONE iDentity server, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>Sun Solaris, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>SUN-Raster, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>support, <a class="indexterm" href="ch47.html">Samba Support</a></dt><dt>support exposure, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>SVN</dt><dd><dl><dt>web, <a class="indexterm" href="compiling.html#id2687603">Access via ViewCVS</a></dt></dl></dd><dt>SVRTOOLS.EXE, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>SWAT, <a class="indexterm" href="install.html#id2551950">Configuring Samba (smb.conf)</a>, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>swat, <a class="indexterm" href="install.html#id2553476">SWAT</a>, <a class="indexterm" href="SWAT.html#id2681236">Validate SWAT Installation</a>, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a>, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dd><dl><dt>enable, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>security, <a class="indexterm" href="SWAT.html#id2681873">Securing SWAT through SSL</a></dt></dl></dd><dt>SWAT binary support, <a class="indexterm" href="SWAT.html#id2681236">Validate SWAT Installation</a></dt><dt>swat command-line options, <a class="indexterm" href="SWAT.html#id2681306">Locating the SWAT File</a></dt><dt>SWAT permission allowed, <a class="indexterm" href="SWAT.html#xinetd">Enabling SWAT for Use</a></dt><dt>symbolic links, <a class="indexterm" href="msdfs.html#id2621467">Features and Benefits</a></dt><dt>synchronization, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>synchronization problems, <a class="indexterm" href="winbind.html#id2653468">Introduction</a></dt><dt>synchronize, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>synchronized, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></dt><dt>syntax tolerates spelling errors, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a></dt><dt>system access controls, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a></dt><dt>system accounts, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a></dt><dt>system administrator, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>system groups, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>system interface scripts, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>system policies, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></dt><dt>System Policy Editor, <a class="indexterm" href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a>, <a class="indexterm" href="PolicyMgmt.html#id2659627">Administration of Windows 200x/XP Policies</a>, <a class="indexterm" href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></dt><dt>system security, <a class="indexterm" href="groupmapping.html#id2597377">Applicable Only to Versions Earlier than 3.0.11</a></dt><dt>system tools, <a class="indexterm" href="Backup.html#id2671379">Features and Benefits</a></dt><dt>SYSV, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>SYSVOL, <a class="indexterm" href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>tail, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a></dt><dt>take ownership, <a class="indexterm" href="rights.html#id2609058">Description of Privileges</a></dt><dt>Take Ownership, <a class="indexterm" href="AccessControls.html#id2613591">Viewing File Ownership</a></dt><dt>tape, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>tar, <a class="indexterm" href="Backup.html#id2671521">BackupPC</a></dt><dt>tarball, <a class="indexterm" href="install.html#id2553073">Example Configuration</a></dt><dt>tattoo effect, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>TCP, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a>, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>TCP data streams, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a></dt><dt>TCP failover, <a class="indexterm" href="SambaHA.html#id2672290">Why Is This So Hard?</a></dt><dt>TCP port, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>TCP port 139, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>TCP port 445, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dt>tcp ports, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>TCP/IP, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>TCP/IP configuration, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>TCP/IP configuration panel, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>TCP/IP protocol configuration, <a class="indexterm" href="ClientConfig.html#id2575554">Technical Details</a></dt><dt>TCP/IP protocol settings, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>TCP/IP protocol stack, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>TCP/IP-only, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></dt><dt>tcpdump, <a class="indexterm" href="problems.html#id2685159">Tcpdump</a></dt><dt>TDB, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a>, <a class="indexterm" href="classicalprinting.html#id2629560">Running rpcclient with setdriver</a>, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a>, <a class="indexterm" href="CUPS-printing.html#id2645668">Trivial Database Files</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dd><dl><dt>backing up (see tdbbackup)</dt></dl></dd><dt>tdb, <a class="indexterm" href="winbind.html#id2654460">User and Group ID Allocation</a>, <a class="indexterm" href="SambaHA.html#id2672812">Server Pool Communications</a>, <a class="indexterm" href="tdb.html#id2686891">Features and Benefits</a></dt><dt>tdb data files, <a class="indexterm" href="upgrading-to-3.0.html#id2677698">TDB Data Files</a></dt><dt>TDB database, <a class="indexterm" href="classicalprinting.html#id2628952">Running rpcclient with adddriver</a></dt><dt>TDB database files, <a class="indexterm" href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></dt><dt>tdb file backup, <a class="indexterm" href="upgrading-to-3.0.html#id2677698">TDB Data Files</a></dt><dt>tdb file descriptions, <a class="indexterm" href="install.html#tdbdocs">TDB Database File Information</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2677698">TDB Data Files</a></dt><dt>tdb file locations, <a class="indexterm" href="install.html#tdbdocs">TDB Database File Information</a></dt><dt>tdb files, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>tdbbackup, <a class="indexterm" href="CUPS-printing.html#id2645852">Using tdbbackup</a>, <a class="indexterm" href="speed.html#id2691200">Corrupt tdb Files</a></dt><dt>tdbdump, <a class="indexterm" href="AccessControls.html#id2612972">Access Controls on Shares</a></dt><dt>tdbsam, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html">Account Information Databases</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="passdb.html#id2592895">tdbsam</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>tdbsam databases, <a class="indexterm" href="passdb.html#id2592500">Password Backends</a></dt><dt>technical reviewers, <a class="indexterm" href="cfgsmarts.html">Advanced Configuration Techniques</a></dt><dt>Telnet, <a class="indexterm" href="passdb.html#id2588481">Advantages of Non-Encrypted Passwords</a></dt><dt>telnet logins, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a></dt><dt>template, <a class="indexterm" href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></dt><dt>temporary location, <a class="indexterm" href="classicalprinting.html#id2625414">Print Commands</a></dt><dt>terminal server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>Terminal Server, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>Testing Server Setup, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>testparm, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a>, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="classicalprinting.html#id2622653">Simple Print Configuration</a>, <a class="indexterm" href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a>, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a>, <a class="indexterm" href="classicalprinting.html#id2623534">Extended Printing Configuration</a>, <a class="indexterm" href="diagnosis.html#id2682811">Assumptions</a>, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a>, <a class="indexterm" href="problems.html#id2684903">Debugging with Samba Itself</a></dt><dt>tethereal, <a class="indexterm" href="problems.html#id2685159">Tcpdump</a></dt><dt>text/plain, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>texttops, <a class="indexterm" href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></dt><dt>thin client, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>ThinLinc, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>tid, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt><dt>TIFF, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>TightVNC, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>time difference, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></dt><dt>time format, <a class="indexterm" href="passdb.html#id2591546">Changing User Accounts</a></dt><dt>time-to-live (see TTL)</dt><dt>tool, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>tools, <a class="indexterm" href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a>, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a></dt><dt>tools\reskit\netadmin\poledit, <a class="indexterm" href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></dt><dt>traditional printing, <a class="indexterm" href="classicalprinting.html#id2626035">Custom Print Commands</a></dt><dt>training course, <a class="indexterm" href="Backup.html#id2671424">Discussion of Backup Solutions</a></dt><dt>transfer differences, <a class="indexterm" href="Backup.html#id2671692">Rsync</a></dt><dt>transformation, <a class="indexterm" href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></dt><dt>transitive, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>transparent access, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>transparently reconnected, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>transport connection loss, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Transport Layer Seccurity, TLS</dt><dd><dl><dt>Configuring, <a class="indexterm" href="ch-ldap-tls.html#s1-config-ldap-tls">Configuring</a></dt><dt>Introduction, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt></dl></dd><dt>transport layer security (see TLS)</dt><dt>Transport Layer Security, TLS</dt><dd><dl><dt>Testing, <a class="indexterm" href="ch-ldap-tls.html#s1-test-ldap-tls">Testing</a></dt><dt>Troubleshooting, <a class="indexterm" href="ch-ldap-tls.html#s1-int-ldap-tls">Troubleshooting</a></dt></dl></dd><dt>trigger, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>trivial database, <a class="indexterm" href="passdb.html#id2587457">New Account Storage Systems</a> (see TDB)</dt><dt>Trivial Database, <a class="indexterm" href="tdb.html#id2686891">Features and Benefits</a></dt><dt>troubleshoot, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>troubleshooting, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dt>Tru64 UNIX, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>trust, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dd><dl><dt>account, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></dt></dl></dd><dt>trust account, <a class="indexterm" href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dd><dl><dt>interdomain, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt><dt>machine, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a></dt></dl></dd><dt>trust account password, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt><dt>trust accounts, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a></dt><dt>trust established, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></dt><dt>trust relationship, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a>, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>trust relationships, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619759">Features and Benefits</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>trusted, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>trusted domain, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a>, <a class="indexterm" href="winbind.html#id2654073">Name Service Switch</a></dt><dt>trusted domain name, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusted party, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusting domain, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></dt><dt>trusting party, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>trusts, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>TTL, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>turn oplocks off, <a class="indexterm" href="locking.html#id2616799">Advanced Samba Oplocks Parameters</a></dt><dt>turnkey solution, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dt>two-up, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>two-way</dt><dd><dl><dt>propagation, <a class="indexterm" href="samba-bdc.html#id2565776">Features and Benefits</a></dt></dl></dd><dt>two-way trust, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UCS-2, <a class="indexterm" href="unicode.html#id2670216">Japanese Charsets</a></dt><dt>UDP, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></dt><dt>UDP port 137, <a class="indexterm" href="integrate-ms-networks.html#id2668079">Background Information</a></dt><dt>udp ports, <a class="indexterm" href="winbind.html#id2655661">Join the Samba Server to the PDC Domain</a></dt><dt>UDP unicast, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>UID, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a>, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a>, <a class="indexterm" href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a>, <a class="indexterm" href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2591139">Listing User and Machine Accounts</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605493">Primary Domain Controller</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653756">Handling of Foreign SIDs</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>uid, <a class="indexterm" href="passdb.html#id2593582">OpenLDAP Configuration</a></dt><dt>UID numbers, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></dt><dt>UID range, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dt>unauthorized, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>unauthorized access, <a class="indexterm" href="AccessControls.html">File, Directory, and Share Access Controls</a></dt><dt>UNC notation, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>unexpected.tdb, <a class="indexterm" href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>unicast, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></dt><dt>unicode, <a class="indexterm" href="unicode.html#id2669916">What Are Charsets and Unicode?</a></dt><dt>Unicode, <a class="indexterm" href="unicode.html#id2670049">Samba and Charsets</a>, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>Unicode UTF-8, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>unified logon, <a class="indexterm" href="winbind.html#id2653468">Introduction</a></dt><dt>UNIX, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dd><dl><dt>server, <a class="indexterm" href="ServerType.html#id2558805">Features and Benefits</a></dt></dl></dd><dt>UNIX account, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>unix charset, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>UNIX Domain Socket, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>UNIX domain socket, <a class="indexterm" href="winbind.html#id2653882">How Winbind Works</a></dt><dt>UNIX file system access controls, <a class="indexterm" href="AccessControls.html#id2610564">Features and Benefits</a></dt><dt>UNIX group, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>UNIX groups, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>UNIX home directories, <a class="indexterm" href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></dt><dt>UNIX host system, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>UNIX ID, <a class="indexterm" href="winbind.html#id2654460">User and Group ID Allocation</a></dt><dt>UNIX locking, <a class="indexterm" href="locking.html#id2615682">Discussion</a></dt><dt>UNIX login ID, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>UNIX permissions, <a class="indexterm" href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></dt><dt>UNIX printer, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>UNIX printing, <a class="indexterm" href="classicalprinting.html#id2622341">Technical Introduction</a></dt><dt>UNIX system account, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></dt><dt>UNIX system accounts, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>UNIX system files, <a class="indexterm" href="Backup.html#id2671379">Features and Benefits</a></dt><dt>UNIX user identifier (see UID)</dt><dt>UNIX users, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>UNIX-style encrypted passwords, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>UNIX-user database, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a></dt><dt>UNIX/Linux group, <a class="indexterm" href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></dt><dt>UNIX/Linux user account, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dt>unlink calls, <a class="indexterm" href="VFS.html#id2651387">recycle</a></dt><dt>unlinked, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>unmapped groups, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a></dt><dt>unmapped users, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a></dt><dt>unprivileged account names, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt>unsigned drivers, <a class="indexterm" href="CUPS-printing.html#id2649419">Windows 200x/XP Local Security Policies</a></dt><dt>unstoppable services, <a class="indexterm" href="SambaHA.html#id2672161">The Ultimate Goal</a></dt><dt>unsupported encryption, <a class="indexterm" href="domain-member.html#id2573092">Possible Errors</a></dt><dt>unsupported software, <a class="indexterm" href="ch47.html#id2692705">Commercial Support</a></dt><dt>updates, <a class="indexterm" href="securing-samba.html#id2619110">Upgrading Samba</a></dt><dt>upload drivers, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>uploaded driver, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>uploaded drivers, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>uploading, <a class="indexterm" href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></dt><dt>upper-case, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a></dt><dt>uppercase, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2573779">Adding Machine to Domain Fails</a>, <a class="indexterm" href="largefile.html">Handling Large Directories</a></dt><dt>uppercase character, <a class="indexterm" href="groupmapping.html#id2598524">Adding Groups Fails</a></dt><dt>USB, <a class="indexterm" href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></dt><dt>use computer anywhere, <a class="indexterm" href="unicode.html#id2669864">Features and Benefits</a></dt><dt>user, <a class="indexterm" href="ChangeNotes.html#id2578647">User and Group Changes</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>user access management, <a class="indexterm" href="domain-member.html#id2569108">Features and Benefits</a></dt><dt>user account, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="passdb.html#id2591023">User Account Management</a>, <a class="indexterm" href="passdb.html#TOSHARG-acctflags">Account Flags Management</a>, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a>, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dd><dl><dt>Adding/Deleting, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt></dl></dd><dt>user account database, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>user accounts, <a class="indexterm" href="passdb.html#id2589369">Caution Regarding LDAP and Samba</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>User Accounts</dt><dd><dl><dt>Adding/Deleting, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a></dt></dl></dd><dt>user and group, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>user and trust accounts, <a class="indexterm" href="passdb.html">Account Information Databases</a></dt><dt>user attributes, <a class="indexterm" href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></dt><dt>user authentication, <a class="indexterm" href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></dt><dt>user database, <a class="indexterm" href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a>, <a class="indexterm" href="passdb.html#id2592553">Plaintext</a></dt><dt>user encoded, <a class="indexterm" href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></dt><dt>user groups, <a class="indexterm" href="ch47.html#id2692487">Free Support</a></dt><dt>user logons, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>user management, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a>, <a class="indexterm" href="NetCommand.html#id2599005">Overview</a>, <a class="indexterm" href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></dt><dt>User Management, <a class="indexterm" href="passdb.html#pdbeditthing">The pdbedit Tool</a>, <a class="indexterm" href="passdb.html#id2594464">Accounts and Groups Management</a></dt><dt>User Manager, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a class="indexterm" href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a>, <a class="indexterm" href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></dt><dt>User Manager for Domains, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>user or group, <a class="indexterm" href="rights.html#id2608712">Using the net rpc rights Utility</a></dt><dt>user profiles, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>User Rights and Privileges, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>user-level, <a class="indexterm" href="ServerType.html#id2559109">Samba Security Modes</a>, <a class="indexterm" href="ServerType.html#id2559271">User Level Security</a></dt><dt>User-level access control, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>user-level security, <a class="indexterm" href="passdb.html#id2588340">Advantages of Encrypted Passwords</a></dt><dt>user-mode security, <a class="indexterm" href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></dt><dt>user.DAT, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a>, <a class="indexterm" href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></dt><dt>user.MAN, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>User.MAN, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>useradd, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a>, <a class="indexterm" href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></dt><dt>username, <a class="indexterm" href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></dt><dt>username and password, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>username map, <a class="indexterm" href="NetCommand.html#id2601237">User Mapping</a></dt><dt>userPassword, <a class="indexterm" href="passdb.html#id2593854">Initialize the LDAP Database</a></dt><dt>users, <a class="indexterm" href="PolicyMgmt.html#id2658770">Features and Benefits</a></dt><dt>UsrMgr.exe, <a class="indexterm" href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></dt><dt>UTF-8, <a class="indexterm" href="unicode.html#id2670049">Samba and Charsets</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>UTF-8 encoding, <a class="indexterm" href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid username/password, <a class="indexterm" href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></dt><dt>valid users, <a class="indexterm" href="diagnosis.html#id2683103">The Tests</a></dt><dt>validate, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a>, <a class="indexterm" href="diagnosis.html#id2682772">Introduction</a></dt><dt>validate every backup, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>validation, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a>, <a class="indexterm" href="PolicyMgmt.html">System and Account Policies</a></dt><dt>vendor-provided drivers, <a class="indexterm" href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></dt><dt>verifiable, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a></dt><dt>verify, <a class="indexterm" href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></dt><dt>version control, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a></dt><dt>VFS, <a class="indexterm" href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a>, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>VFS module, <a class="indexterm" href="VFS.html#id2651833">shadow_copy</a>, <a class="indexterm" href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></dt><dt>VFS modules, <a class="indexterm" href="VFS.html#id2650401">Discussion</a>, <a class="indexterm" href="VFS.html#id2652736">VFS Modules Available Elsewhere</a></dt><dt>vgcreate, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>vgdisplay, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>vipw, <a class="indexterm" href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a>, <a class="indexterm" href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></dt><dt>Virtual File System (see VFS)</dt><dt>virtual server, <a class="indexterm" href="SambaHA.html#id2672409">The Front-End Challenge</a>, <a class="indexterm" href="SambaHA.html#id2673010">A Simple Solution</a></dt><dt>virus scanner, <a class="indexterm" href="VFS.html#id2650401">Discussion</a></dt><dt>Visual Studio, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a></dt><dt>vital task, <a class="indexterm" href="SambaHA.html#id2672006">Features and Benefits</a></dt><dt>VNC/RFB, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>volume group, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>volunteers, <a class="indexterm" href="problems.html#id2685716">Getting Mailing List Help</a></dt><dt>vscan, <a class="indexterm" href="VFS.html#id2652821">vscan</a></dt><dt>vuid, <a class="indexterm" href="SambaHA.html#id2672504">Demultiplexing SMB Requests</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>W32X86, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a>, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>W32X86/2, <a class="indexterm" href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a></dt><dt>WAN, <a class="indexterm" href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a>, <a class="indexterm" href="locking.html#id2616553">Slow and/or Unreliable Networks</a></dt><dt>wbinfo, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>Web-based configuration, <a class="indexterm" href="SWAT.html">SWAT: The Samba Web Administration Tool</a></dt><dt>WebClient, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>Welcome, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></dt><dt>well known RID, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>well-controlled network, <a class="indexterm" href="NT4Migration.html#id2679713">Server Share and Directory Layout</a></dt><dt>well-known RID, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></dt><dt>wide-area network bandwidth, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>win election, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></dt><dt>Win32 printing API, <a class="indexterm" href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></dt><dt>WIN40, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a>, <a class="indexterm" href="classicalprinting.html#id2628451">Obtaining Driver Files from Windows Client [print$] Shares</a>, <a class="indexterm" href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></dt><dt>winbind, <a class="indexterm" href="domain-member.html#id2571819">Why Is This Better Than security = server?</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a>, <a class="indexterm" href="idmapper.html#id2605886">NT4-Style Domains (Includes Samba Domains)</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2655464">Configure smb.conf</a></dt><dt>Winbind, <a class="indexterm" href="StandAloneServer.html#id2574242">Background</a>, <a class="indexterm" href="winbind.html#id2653711">Target Uses</a>, <a class="indexterm" href="winbind.html#id2654026">Microsoft Active Directory Services</a>, <a class="indexterm" href="winbind.html#id2654305">Pluggable Authentication Modules</a>, <a class="indexterm" href="winbind.html#id2654460">User and Group ID Allocation</a>, <a class="indexterm" href="winbind.html#id2654536">Result Caching</a>, <a class="indexterm" href="winbind.html#id2654599">Introduction</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2655350">NSS Winbind on AIX</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="winbind.html#id2656821">Linux/FreeBSD-Specific PAM Configuration</a>, <a class="indexterm" href="winbind.html#id2657284">Conclusion</a>, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a>, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt><dt>Winbind architecture, <a class="indexterm" href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></dt><dt>Winbind hooks, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>Winbind services, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a></dt><dt>Winbind-based authentication, <a class="indexterm" href="pam.html">PAM-Based Distributed Authentication</a></dt><dt>winbind.so, <a class="indexterm" href="winbind.html#id2657167">Solaris-Specific Configuration</a></dt><dt>winbindd, <a class="indexterm" href="install.html#id2552892">Starting Samba</a>, <a class="indexterm" href="install.html#id2553307">Test Your Config File with testparm</a>, <a class="indexterm" href="FastStart.html#id2556032">Example Configuration</a>, <a class="indexterm" href="samba-bdc.html#id2568136">Example Configuration</a>, <a class="indexterm" href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a>, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a>, <a class="indexterm" href="groupmapping.html#id2595872">Features and Benefits</a>, <a class="indexterm" href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a>, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a>, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a>, <a class="indexterm" href="InterdomainTrusts.html">Interdomain Trust Relationships</a>, <a class="indexterm" href="winbind.html#id2653125">Features and Benefits</a>, <a class="indexterm" href="winbind.html#id2653882">How Winbind Works</a>, <a class="indexterm" href="winbind.html#id2654713">Requirements</a>, <a class="indexterm" href="winbind.html#id2654865">Testing Things Out</a>, <a class="indexterm" href="winbind.html#id2654952">Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris</a>, <a class="indexterm" href="winbind.html#id2655464">Configure smb.conf</a>, <a class="indexterm" href="winbind.html#id2655899">Starting and Testing the winbindd Daemon</a>, <a class="indexterm" href="winbind.html#id2656465">Solaris</a>, <a class="indexterm" href="winbind.html#id2656654">Configure Winbind and PAM</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></dt><dt>winbindd daemon, <a class="indexterm" href="winbind.html#id2656259">Linux</a></dt><dt>Windows, <a class="indexterm" href="idmapper.html">Identity Mapping (IDMAP)</a>, <a class="indexterm" href="unicode.html#id2670356">Basic Parameter Setting</a></dt><dt>Windows 2000, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#ads-test-server">Testing Server Setup</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></dt><dt>Windows 2000 Professional TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>Windows 2000 server, <a class="indexterm" href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></dt><dt>Windows 2003, <a class="indexterm" href="domain-member.html#id2572291">Configure /etc/krb5.conf</a>, <a class="indexterm" href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a></dt><dt>Windows 200x/XP, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>Windows 9x/Me, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a>, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></dt><dt>Windows 9x/Me/XP Home, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>Windows account management, <a class="indexterm" href="winbind.html#id2653558">What Winbind Provides</a></dt><dt>Windows client, <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Windows client failover, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>Windows domain, <a class="indexterm" href="upgrading-to-3.0.html#id2678050">Changes in Behavior</a></dt><dt>Windows Explorer, <a class="indexterm" href="NetworkBrowsing.html#id2585087">Problem Resolution</a>, <a class="indexterm" href="classicalprinting.html#id2628044">Identifying Driver Files</a></dt><dt>Windows group, <a class="indexterm" href="groupmapping.html">Group Mapping: MS Windows and UNIX</a>, <a class="indexterm" href="groupmapping.html#id2596625">Warning: User Private Group Problems</a>, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a>, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows group account, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>Windows groups, <a class="indexterm" href="NetCommand.html#id2599783">Mapping Windows Groups to UNIX Groups</a></dt><dt>Windows Internet Name Server (see WINS)</dt><dt>Windows Logon, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>Windows Me TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>Windows Millennium, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>Windows Millennium edition (Me) TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>Windows network clients, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a></dt><dt>Windows NT domain name, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Windows NT PostScript driver, <a class="indexterm" href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></dt><dt>Windows NT Server, <a class="indexterm" href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt>Windows NT/2000/XP, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>Windows NT/200x, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="winbind.html#id2654599">Introduction</a></dt><dt>Windows NT/200x/XP, <a class="indexterm" href="classicalprinting.html#id2624014">The [global] Section</a></dt><dt>Windows NT/200x/XP Professional, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a class="indexterm" href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2578339">Common Errors</a></dt><dt>Windows NT3.10, <a class="indexterm" href="samba-bdc.html#id2566182">Essential Background Information</a></dt><dt>Windows NT4, <a class="indexterm" href="AccessControls.html#id2613132">Windows NT4 Workstation/Server</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>Windows NT4 domains, <a class="indexterm" href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></dt><dt>Windows NT4 Server, <a class="indexterm" href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></dt><dt>Windows NT4/200X, <a class="indexterm" href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></dt><dt>Windows NT4/200x, <a class="indexterm" href="groupmapping.html#id2596288">Discussion</a></dt><dt>Windows NT4/200x/XP, <a class="indexterm" href="samba-bdc.html#id2567510">NetBIOS Over TCP/IP Enabled</a>, <a class="indexterm" href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a>, <a class="indexterm" href="AccessControls.html#id2613237">Windows 200x/XP</a></dt><dt>Windows NT4/2kX/XPPro, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows PPD, <a class="indexterm" href="CUPS-printing.html#id2646217">690 Perfect Printers</a></dt><dt>Windows privilege model, <a class="indexterm" href="rights.html#id2608437">Rights Management Capabilities</a></dt><dt>Windows Registry, <a class="indexterm" href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dt>windows registry settings, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dd><dl><dt>default profile locations, <a class="indexterm" href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a>, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>profile path, <a class="indexterm" href="ProfileMgmt.html#id2661273">Windows 9x/Me Profile Setup</a></dt><dt>roaming profiles, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a></dt></dl></dd><dt>Windows Resource Kit, <a class="indexterm" href="ProfileMgmt.html#id2661043">Disabling Roaming Profile Support</a></dt><dt>Windows Security Identifiers (see SID)</dt><dt>Windows Terminal server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></dt><dt>Windows Terminal Server, <a class="indexterm" href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></dt><dt>Windows user, <a class="indexterm" href="rights.html">User Rights and Privileges</a></dt><dt>Windows user accounts, <a class="indexterm" href="NetCommand.html#id2600908">UNIX and Windows User Management</a></dt><dt>Windows workstation., <a class="indexterm" href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></dt><dt>Windows XP Home, <a class="indexterm" href="passdb.html#id2588025">Important Notes About Security</a></dt><dt>Windows XP Home edition, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2564466">The Special Case of MS Windows XP Home Edition</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></dt><dt>Windows XP Home Edition, <a class="indexterm" href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></dt><dt>Windows XP Professional, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="classicalprinting.html#id2622118">Features and Benefits</a></dt><dt>Windows XP Professional TCP/IP, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a></dt><dt>Windows XP TCP/IP, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a></dt><dt>Windows95/98/ME, <a class="indexterm" href="classicalprinting.html#id2629218">Check Samba for Driver Recognition</a></dt><dt>winnt.adm, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>WINS, <a class="indexterm" href="samba-pdc.html#id2561235">Features and Benefits</a>, <a class="indexterm" href="samba-pdc.html#id2562478">Domain Controller Types</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a>, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a>, <a class="indexterm" href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a>, <a class="indexterm" href="ClientConfig.html#id2575673">MS Windows XP Professional</a>, <a class="indexterm" href="ClientConfig.html#id2576317">MS Windows 2000</a>, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a>, <a class="indexterm" href="NetworkBrowsing.html">Network Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579524">Features and Benefits</a>, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a>, <a class="indexterm" href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a>, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2585510">Behavior of Cross-Subnet Browsing</a>, <a class="indexterm" href="integrate-ms-networks.html#id2669435">WINS Lookup</a>, <a class="indexterm" href="DNSDHCP.html#id2693042">Example Configuration</a></dt><dt>wins, <a class="indexterm" href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></dt><dt>WINS Configuration, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>WINS lookup, <a class="indexterm" href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></dt><dt>WINS replication, <a class="indexterm" href="NetworkBrowsing.html#id2584164">WINS Replication</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>WINS Server, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>WINS server, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a>, <a class="indexterm" href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a>, <a class="indexterm" href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></dt><dt>WINS server address, <a class="indexterm" href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></dt><dt>WINS server settings, <a class="indexterm" href="ClientConfig.html#id2576863">MS Windows Me</a></dt><dt>WINS servers, <a class="indexterm" href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></dt><dt>WINS service, <a class="indexterm" href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></dt><dt>WINS Support, <a class="indexterm" href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></dt><dt>wins.dat, <a class="indexterm" href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></dt><dt>without Administrator account, <a class="indexterm" href="rights.html#id2609884">The Administrator Domain SID</a></dt><dt>without ADS, <a class="indexterm" href="NT4Migration.html#id2679102">Objectives</a></dt><dt>work-flow protocol, <a class="indexterm" href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></dt><dt>workgroup, <a class="indexterm" href="ServerType.html#id2560264">Server Security (User Level Security)</a>, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a>, <a class="indexterm" href="samba-pdc.html#id2564504">The Special Case of Windows 9x/Me</a>, <a class="indexterm" href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a>, <a class="indexterm" href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a>, <a class="indexterm" href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a>, <a class="indexterm" href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a>, <a class="indexterm" href="cfgsmarts.html#id2673908">Multiple Server Hosting</a>, <a class="indexterm" href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></dt><dd><dl><dt>membership, <a class="indexterm" href="samba-pdc.html#id2562982">Preparing for Domain Control</a></dt></dl></dd><dt>workstations, <a class="indexterm" href="passdb.html#passdbtech">Technical Information</a></dt><dt>world-writable, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>write, <a class="indexterm" href="AccessControls.html#id2611225">File and Directory Access Control</a></dt><dt>write access, <a class="indexterm" href="AccessControls.html#id2611642">Protecting Directories and Files from Deletion</a></dt><dt>Write caching, <a class="indexterm" href="locking.html#id2615940">Opportunistic Locking Overview</a></dt><dt>write changes, <a class="indexterm" href="idmapper.html#id2605727">Backup Domain Controller</a></dt><dt>write permission, <a class="indexterm" href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></dt><dt>writeable, <a class="indexterm" href="VFS.html#fakeperms">fake_perms</a></dt><dt>WYSIWYG, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X Window
+	System, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>X.509 certificates, <a class="indexterm" href="ch-ldap-tls.html#s1-intro-ldap-tls">Introduction</a></dt><dt>XFS file system, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>xfsprogs, <a class="indexterm" href="VFS.html#id2652022">Shadow Copy Setup</a></dt><dt>xinetd, <a class="indexterm" href="SWAT.html#id2681236">Validate SWAT Installation</a>, <a class="indexterm" href="compiling.html#id2688504">Starting from inetd.conf</a> (see inetd)</dt><dt>XML, <a class="indexterm" href="ChangeNotes.html#id2579081">Passdb Changes</a></dt><dt>XML-based datasets, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>xpp, <a class="indexterm" href="CUPS-printing.html#id2646842">Foomatic Database-Generated PPDs</a></dt><dt>Xprint, <a class="indexterm" href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a>, <a class="indexterm" href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></dt><dt>xxxxBSD, <a class="indexterm" href="pam.html#id2665152">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>yppasswd, <a class="indexterm" href="passdb.html#id2589947">The smbpasswd Tool</a></dt></dl></div><div class="indexdiv"><h3>Z</h3><dl><dt>Zero Administration Kit, <a class="indexterm" href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></dt><dt>zero-based broadcast, <a class="indexterm" href="NetworkBrowsing.html#id2583131">Note about Broadcast Addresses</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="go01.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�</td></tr><tr><td width="40%" align="left" valign="top">Glossary�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/largefile.html b/docs/htmldocs/Samba3-HOWTO/largefile.html
index d27737e24d..8aa8619631 100644
--- a/docs/htmldocs/Samba3-HOWTO/largefile.html
+++ b/docs/htmldocs/Samba3-HOWTO/largefile.html
@@ -1,39 +1,39 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�33.�Handling Large Directories</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="SambaHA.html" title="Chapter�32.�High Availability"><link rel="next" href="cfgsmarts.html" title="Chapter�34.�Advanced Configuration Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�33.�Handling Large Directories</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SambaHA.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="cfgsmarts.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="largefile"></a>Chapter�33.�Handling Large Directories</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">March 5, 2005</p></div></div></div><p>
-<a class="indexterm" name="id2673225"></a>
-<a class="indexterm" name="id2673232"></a>
-<a class="indexterm" name="id2673239"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�33.�Handling Large Directories</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="SambaHA.html" title="Chapter�32.�High Availability"><link rel="next" href="cfgsmarts.html" title="Chapter�34.�Advanced Configuration Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�33.�Handling Large Directories</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SambaHA.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="cfgsmarts.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="largefile"></a>Chapter�33.�Handling Large Directories</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">March 5, 2005</p></div></div></div><p>
+<a class="indexterm" name="id2673369"></a>
+<a class="indexterm" name="id2673376"></a>
+<a class="indexterm" name="id2673384"></a>
 Samba-3.0.12 and later implements a solution for sites that have experienced performance degradation due to the
 problem of using Samba-3 with applications that need large numbers of files (100,000 or more) per directory.
 </p><p>
-<a class="indexterm" name="id2673253"></a>
-<a class="indexterm" name="id2673260"></a>
+<a class="indexterm" name="id2673398"></a>
+<a class="indexterm" name="id2673405"></a>
 The key was fixing the directory handling to read only the current list requested instead of the old
 (up to samba-3.0.11) behavior of reading the entire directory into memory before doling out names.
 Normally this would have broken OS/2 applications, which have very strange delete semantics, but by
 stealing logic from Samba4 (thanks, Tridge), the current code in 3.0.12 handles this correctly.
 </p><p>
-<a class="indexterm" name="id2673277"></a>
-<a class="indexterm" name="id2673284"></a>
+<a class="indexterm" name="id2673422"></a>
+<a class="indexterm" name="id2673429"></a>
 To set up an application that needs large numbers of files per directory in a way that does not
 damage performance unduly, follow these steps:
 </p><p>
-<a class="indexterm" name="id2673296"></a>
+<a class="indexterm" name="id2673441"></a>
 First, you need to canonicalize all the files in the directory to have one case, upper or lower  take your
 pick (I chose upper because all my files were already uppercase names). Then set up a new custom share for the
 application as follows:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[bigshare]</code></em></td></tr><tr><td><a class="indexterm" name="id2673325"></a><em class="parameter"><code>path = /data/manyfilesdir</code></em></td></tr><tr><td><a class="indexterm" name="id2673336"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id2673348"></a><em class="parameter"><code>case sensitive = True</code></em></td></tr><tr><td><a class="indexterm" name="id2673360"></a><em class="parameter"><code>default case = upper</code></em></td></tr><tr><td><a class="indexterm" name="id2673372"></a><em class="parameter"><code>preserve case = no</code></em></td></tr><tr><td><a class="indexterm" name="id2673383"></a><em class="parameter"><code>short preserve case = no</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[bigshare]</code></em></td></tr><tr><td><a class="indexterm" name="id2673469"></a><em class="parameter"><code>path = /data/manyfilesdir</code></em></td></tr><tr><td><a class="indexterm" name="id2673481"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id2673493"></a><em class="parameter"><code>case sensitive = True</code></em></td></tr><tr><td><a class="indexterm" name="id2673504"></a><em class="parameter"><code>default case = upper</code></em></td></tr><tr><td><a class="indexterm" name="id2673516"></a><em class="parameter"><code>preserve case = no</code></em></td></tr><tr><td><a class="indexterm" name="id2673528"></a><em class="parameter"><code>short preserve case = no</code></em></td></tr></table><p>
 </p><p>
-<a class="indexterm" name="id2673398"></a>
-<a class="indexterm" name="id2673405"></a>
-<a class="indexterm" name="id2673412"></a>
+<a class="indexterm" name="id2673543"></a>
+<a class="indexterm" name="id2673550"></a>
+<a class="indexterm" name="id2673557"></a>
 Of course, use your own path and settings, but set the case options to match the case of all the files in your
 directory. The path should point at the large directory needed for the application  any new files created in
 there and in any paths under it will be forced by smbd into uppercase, but smbd will no longer have to scan
 the directory for names: it knows that if a file does not exist in uppercase, then it doesn't exist at all.
 </p><p>
-<a class="indexterm" name="id2673433"></a>
-<a class="indexterm" name="id2673439"></a>
-<a class="indexterm" name="id2673446"></a>
+<a class="indexterm" name="id2673577"></a>
+<a class="indexterm" name="id2673584"></a>
+<a class="indexterm" name="id2673591"></a>
 The secret to this is really in the <a class="link" href="smb.conf.5.html#CASESENSITIVE" target="_top">case sensitive = True</a>
 line. This tells smbd never to scan for case-insensitive versions of names. So if an application asks for a file
 called <code class="filename">FOO</code>, and it cannot be found by a simple stat call, then smbd will return file not
@@ -41,9 +41,9 @@ found immediately without scanning the containing directory for a version of a d
 <code class="filename">xxx case xxx</code> lines make this work by forcing a consistent case on all files created by
 <span class="application">smbd</span>.
 </p><p>
-<a class="indexterm" name="id2673493"></a>
-<a class="indexterm" name="id2673499"></a>
-<a class="indexterm" name="id2673506"></a>
+<a class="indexterm" name="id2673637"></a>
+<a class="indexterm" name="id2673644"></a>
+<a class="indexterm" name="id2673651"></a>
 Remember, all files and directories under the <em class="parameter"><code>path</code></em> directory must be in uppercase
 with this <code class="filename">smb.conf</code> stanza because <span class="application">smbd</span> will not be able to find lowercase filenames with these settings. Also
 note that this is done on a per-share basis, allowing this parameter to be set only for a share servicing an application with
diff --git a/docs/htmldocs/Samba3-HOWTO/locking.html b/docs/htmldocs/Samba3-HOWTO/locking.html
index fb13aa29c9..aa814f4ef9 100644
--- a/docs/htmldocs/Samba3-HOWTO/locking.html
+++ b/docs/htmldocs/Samba3-HOWTO/locking.html
@@ -1,19 +1,19 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�17.�File and Record Locking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls"><link rel="next" href="securing-samba.html" title="Chapter�18.�Securing Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�17.�File and Record Locking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="securing-samba.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter�17.�File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="orgname">HP Oplocks Usage Recommendations Whitepaper</span> <span class="surname">Roseme</span></h3><div class="affiliation"><span class="orgname">HP Oplocks Usage Recommendations Whitepaper<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="locking.html#id2615570">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615667">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615926">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616903">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2616998">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617411">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617598">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617620">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617686">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617712">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617779">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617810">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617834">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617866">Additional Reading</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2615560"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�17.�File and Record Locking</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls"><link rel="next" href="securing-samba.html" title="Chapter�18.�Securing Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�17.�File and Record Locking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="securing-samba.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter�17.�File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="orgname">HP Oplocks Usage Recommendations Whitepaper</span> <span class="surname">Roseme</span></h3><div class="affiliation"><span class="orgname">HP Oplocks Usage Recommendations Whitepaper<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="locking.html#id2615585">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615682">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615940">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616945">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617040">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617453">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617640">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617662">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617728">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617754">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617821">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617852">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617876">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617908">Additional Reading</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2615574"></a>
 One area that 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="id2615570"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2615578"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2615585"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2615593"></a>
 Samba provides all the same locking semantics that MS Windows clients expect
 and that MS Windows NT4/200x servers also provide.
 </p><p>
-<a class="indexterm" name="id2615591"></a>
+<a class="indexterm" name="id2615605"></a>
 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>
-<a class="indexterm" name="id2615607"></a>
-<a class="indexterm" name="id2615614"></a>
 <a class="indexterm" name="id2615621"></a>
+<a class="indexterm" name="id2615628"></a>
+<a class="indexterm" name="id2615635"></a>
 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
@@ -23,27 +23,27 @@ 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>
-<a class="indexterm" name="id2615639"></a>
+<a class="indexterm" name="id2615654"></a>
 The MS Windows network administrator needs to be aware that file and record
 locking semantics (behavior) 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>
-<a class="indexterm" name="id2615655"></a>
+<a class="indexterm" name="id2615670"></a>
 Sometimes it is necessary to disable locking control settings 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="id2615667"></a>Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2615675"></a>
-<a class="indexterm" name="id2615682"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2615682"></a>Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2615690"></a>
+<a class="indexterm" name="id2615696"></a>
 There are two types of locking that need to be performed by an SMB server.
 The first is <span class="emphasis"><em>record locking</em></span> that allows a client to lock
 a range of bytes in an open file. The second is the <span class="emphasis"><em>deny modes</em></span>
 that are specified when a file is open.
 </p><p>
-<a class="indexterm" name="id2615703"></a>
-<a class="indexterm" name="id2615710"></a>
 <a class="indexterm" name="id2615717"></a>
 <a class="indexterm" name="id2615724"></a>
-<a class="indexterm" name="id2615730"></a>
+<a class="indexterm" name="id2615731"></a>
+<a class="indexterm" name="id2615738"></a>
+<a class="indexterm" name="id2615745"></a>
 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.
@@ -53,15 +53,15 @@ depending on the client OS. The UNIX locking only supports byte ranges up to 2^3
 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>
-<a class="indexterm" name="id2615751"></a>
-<a class="indexterm" name="id2615758"></a>
+<a class="indexterm" name="id2615765"></a>
+<a class="indexterm" name="id2615772"></a>
 Samba 2.2 and above implement record locking completely independently of the
 underlying UNIX system. If a byte-range lock that the client requests happens
 to fall into the range of 0 to 2^31, Samba hands this request down to the UNIX system.
 No other locks can be seen by UNIX, anyway.
 </p><p>
-<a class="indexterm" name="id2615773"></a>
-<a class="indexterm" name="id2615780"></a>
+<a class="indexterm" name="id2615787"></a>
+<a class="indexterm" name="id2615794"></a>
 Strictly speaking, 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 overstress
 the <code class="literal">rpc.lockd</code>. This is almost always unnecessary because clients are 
@@ -70,57 +70,57 @@ important to them. By default, Samba only makes locking calls when explicitly as
 to by a client, but if you set <a class="link" href="smb.conf.5.html#STRICTLOCKING" target="_top">strict locking = yes</a>, it
 will make lock checking calls on <span class="emphasis"><em>every</em></span> read and write call.
 </p><p>
-<a class="indexterm" name="id2615821"></a>
+<a class="indexterm" name="id2615836"></a>
 You can also disable byte-range locking completely by using
 <a class="link" href="smb.conf.5.html#LOCKING" target="_top">locking = no</a>.
 This is useful for those shares that do not support locking or do not need it
 (such as CD-ROMs). In this case, Samba fakes the return codes of locking calls to
 tell clients that everything is okay.
 </p><p>
-<a class="indexterm" name="id2615848"></a>
-<a class="indexterm" name="id2615855"></a>
-<a class="indexterm" name="id2615862"></a>
-<a class="indexterm" name="id2615868"></a>
-<a class="indexterm" name="id2615875"></a>
-<a class="indexterm" name="id2615882"></a>
-<a class="indexterm" name="id2615889"></a>
+<a class="indexterm" name="id2615863"></a>
+<a class="indexterm" name="id2615869"></a>
+<a class="indexterm" name="id2615876"></a>
+<a class="indexterm" name="id2615883"></a>
+<a class="indexterm" name="id2615890"></a>
+<a class="indexterm" name="id2615896"></a>
+<a class="indexterm" name="id2615903"></a>
 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
 <code class="constant">DENY_NONE</code>, <code class="constant">DENY_READ</code>, 
 <code class="constant">DENY_WRITE</code>, or <code class="constant">DENY_ALL</code>. There are also special compatibility
 modes called <code class="constant">DENY_FCB</code> and <code class="constant">DENY_DOS</code>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615926"></a>Opportunistic Locking Overview</h3></div></div></div><p>
-<a class="indexterm" name="id2615934"></a>
-<a class="indexterm" name="id2615941"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615940"></a>Opportunistic Locking Overview</h3></div></div></div><p>
 <a class="indexterm" name="id2615948"></a>
+<a class="indexterm" name="id2615955"></a>
+<a class="indexterm" name="id2615962"></a>
 Opportunistic locking (oplocks) is invoked by the Windows file system
 (as opposed to an API) via registry entries (on the server and the 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 that allows the following:
 </p><div class="variablelist"><dl><dt><span class="term">Read-ahead:</span></dt><dd><p>
-<a class="indexterm" name="id2615971"></a>
+<a class="indexterm" name="id2615986"></a>
 		The client reads the local copy of the file, eliminating network latency.
 		</p></dd><dt><span class="term">Write caching:</span></dt><dd><p>
-<a class="indexterm" name="id2615989"></a>
+<a class="indexterm" name="id2616004"></a>
 		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>
-<a class="indexterm" name="id2616008"></a>
+<a class="indexterm" name="id2616022"></a>
 		The client caches application locks locally, eliminating network latency.
 		</p></dd></dl></div><p>
-<a class="indexterm" name="id2616022"></a>
-<a class="indexterm" name="id2616029"></a>
-<a class="indexterm" name="id2616035"></a>
+<a class="indexterm" name="id2616036"></a>
+<a class="indexterm" name="id2616043"></a>
+<a class="indexterm" name="id2616050"></a>
 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 Four Kinds of Oplocks:</b></p><dl><dt><span class="term">Level1 Oplock</span></dt><dd><p>
-<a class="indexterm" name="id2616067"></a>
-<a class="indexterm" name="id2616073"></a>
-<a class="indexterm" name="id2616080"></a>
-<a class="indexterm" name="id2616087"></a>
+<a class="indexterm" name="id2616081"></a>
+<a class="indexterm" name="id2616088"></a>
+<a class="indexterm" name="id2616094"></a>
+<a class="indexterm" name="id2616101"></a>
 			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
@@ -128,10 +128,10 @@ other processes.
 			access to the file. The client now performs
 			operations on the cached local file.
 			</p><p>
-<a class="indexterm" name="id2616102"></a>
-<a class="indexterm" name="id2616109"></a>
-<a class="indexterm" name="id2616116"></a>
-<a class="indexterm" name="id2616123"></a>
+<a class="indexterm" name="id2616117"></a>
+<a class="indexterm" name="id2616124"></a>
+<a class="indexterm" name="id2616131"></a>
+<a class="indexterm" name="id2616138"></a>
 			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
@@ -145,31 +145,31 @@ other processes.
 			second process is granted limited or no access, despite
 			the oplock break.
 			</p></dd><dt><span class="term">Level2 Oplock</span></dt><dd><p>
-<a class="indexterm" name="id2616151"></a>
-<a class="indexterm" name="id2616158"></a>
-<a class="indexterm" name="id2616165"></a>
+<a class="indexterm" name="id2616177"></a>
+<a class="indexterm" name="id2616184"></a>
+<a class="indexterm" name="id2616190"></a>
 				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>
-<a class="indexterm" name="id2616185"></a>
+<a class="indexterm" name="id2616211"></a>
 				Does not allow write or delete file access.
                 </p></dd><dt><span class="term">Batch Oplock</span></dt><dd><p>
-<a class="indexterm" name="id2616204"></a>
+<a class="indexterm" name="id2616229"></a>
 				Manipulates file openings and closings and allows caching
                 of file attributes.
                 </p></dd></dl></div><p>
-<a class="indexterm" name="id2616218"></a>
+<a class="indexterm" name="id2616243"></a>
 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>
-<a class="indexterm" name="id2616234"></a>
-<a class="indexterm" name="id2616241"></a>
-<a class="indexterm" name="id2616248"></a>
-<a class="indexterm" name="id2616255"></a>
+<a class="indexterm" name="id2616259"></a>
+<a class="indexterm" name="id2616266"></a>
+<a class="indexterm" name="id2616273"></a>
+<a class="indexterm" name="id2616280"></a>
 <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
@@ -179,7 +179,7 @@ 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>
-<a class="indexterm" name="id2616277"></a>
+<a class="indexterm" name="id2616302"></a>
 The actual decision that a user or administrator should consider is
 whether it is sensible to share among multiple users data that will
 be cached locally on a client. In many cases the answer is no.
@@ -189,15 +189,15 @@ caching. Turn it &#8220;<span class="quote">on</span>&#8221; when client-side ca
 reliable. Turn it &#8220;<span class="quote">off</span>&#8221; when client-side caching is redundant,
 unreliable, or counterproductive.
 </p><p>
-<a class="indexterm" name="id2616302"></a>
+<a class="indexterm" name="id2616327"></a>
 Oplocks is by default set to &#8220;<span class="quote">on</span>&#8221; 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 oplocks may be effectively configured.
 </p><p>
-<a class="indexterm" name="id2616320"></a>
-<a class="indexterm" name="id2616327"></a>
+<a class="indexterm" name="id2616346"></a>
+<a class="indexterm" name="id2616352"></a>
 Windows oplocks is a lightweight performance-enhancing
 feature. It is not a robust and reliable protocol. Every
 implementation of oplocks should be evaluated as a
@@ -208,7 +208,7 @@ South Pacific atoll, on a high-availability server, serving a
 mission-critical multiuser corporate database during a tropical
 storm. This configuration will likely encounter problems with oplocks.
 </p><p>
-<a class="indexterm" name="id2616347"></a>
+<a class="indexterm" name="id2616372"></a>
 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
@@ -222,8 +222,8 @@ 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>
-<a class="indexterm" name="id2616369"></a>
-<a class="indexterm" name="id2616376"></a>
+<a class="indexterm" name="id2616395"></a>
+<a class="indexterm" name="id2616402"></a>
 Windows client failover behavior is more at risk of application
 interruption than other platforms because it is dependent upon an
 established TCP transport connection. If the connection is interrupted
@@ -233,9 +233,9 @@ correctly from a transport connection loss; therefore, most applications
 will experience some sort of interruption  at worst, abort and
 require restarting.
 </p><p>
-<a class="indexterm" name="id2616404"></a>
-<a class="indexterm" name="id2616410"></a>
-<a class="indexterm" name="id2616416"></a>
+<a class="indexterm" name="id2616429"></a>
+<a class="indexterm" name="id2616435"></a>
+<a class="indexterm" name="id2616442"></a>
 If a client session has been caching writes and reads locally due to
 oplocks, it is likely that the data will be lost when the
 application restarts or recovers from the TCP interrupt. When the TCP
@@ -250,7 +250,7 @@ In mission-critical, high-availability environments, careful attention
 should be given to oplocks. 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="id2616441"></a>Exclusively Accessed Shares</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616466"></a>Exclusively Accessed Shares</h4></div></div></div><p>
 Oplocks 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 oplocks is the local
@@ -259,7 +259,7 @@ mechanism will cause a delay.
 </p><p>
 Home directories are the most obvious examples of where the performance
 benefit of oplocks can be safely realized.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616461"></a>Multiple-Accessed Shares or Files</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616487"></a>Multiple-Accessed Shares or Files</h4></div></div></div><p>
 As each additional user accesses a file in a share with oplocks
 enabled, the potential for delays and resulting perceived poor
 performance increases. When multiple users are accessing a file on a
@@ -271,9 +271,9 @@ of the caching user.
 As each additional client attempts to access a file with oplocks set,
 the potential performance improvement is negated and eventually results
 in a performance bottleneck.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616485"></a>UNIX or NFS Client-Accessed Files</h4></div></div></div><p>
-<a class="indexterm" name="id2616493"></a>
-<a class="indexterm" name="id2616500"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616518"></a>UNIX or NFS Client-Accessed Files</h4></div></div></div><p>
+<a class="indexterm" name="id2616526"></a>
+<a class="indexterm" name="id2616532"></a>
 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
@@ -283,10 +283,10 @@ exposes the file to likely data corruption.
 </p><p>
 If files are shared between Windows clients and either local UNIX 
 or NFS users, turn oplocks off.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616521"></a>Slow and/or Unreliable Networks</h4></div></div></div><p>
-<a class="indexterm" name="id2616529"></a>
-<a class="indexterm" name="id2616536"></a>
-<a class="indexterm" name="id2616542"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616553"></a>Slow and/or Unreliable Networks</h4></div></div></div><p>
+<a class="indexterm" name="id2616561"></a>
+<a class="indexterm" name="id2616568"></a>
+<a class="indexterm" name="id2616575"></a>
 The biggest potential performance improvement for oplocks
 occurs when the client-side caching of reads and writes delivers the
 most differential over sending those reads and writes over the wire.
@@ -301,20 +301,20 @@ the most advantageous scenario in which to utilize oplocks.
 If the network is slow, unreliable, or a WAN, then do not configure
 oplocks 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="id2616568"></a>Multiuser Databases</h4></div></div></div><p>
-<a class="indexterm" name="id2616576"></a>
-<a class="indexterm" name="id2616583"></a>
-<a class="indexterm" name="id2616590"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616601"></a>Multiuser Databases</h4></div></div></div><p>
+<a class="indexterm" name="id2616608"></a>
+<a class="indexterm" name="id2616615"></a>
+<a class="indexterm" name="id2616622"></a>
 Multiuser databases clearly pose a risk due to their very nature  they are typically heavily
 accessed by numerous users at random intervals. Placing a multiuser database on a share with oplocks 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 oplocks disabled.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616609"></a>PDM Data Shares</h4></div></div></div><p>
-<a class="indexterm" name="id2616617"></a>
-<a class="indexterm" name="id2616624"></a>
-<a class="indexterm" name="id2616631"></a>
-<a class="indexterm" name="id2616638"></a>
-<a class="indexterm" name="id2616645"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616642"></a>PDM Data Shares</h4></div></div></div><p>
+<a class="indexterm" name="id2616649"></a>
+<a class="indexterm" name="id2616656"></a>
+<a class="indexterm" name="id2616663"></a>
+<a class="indexterm" name="id2616670"></a>
+<a class="indexterm" name="id2616677"></a>
 Process data management (PDM) applications such as IMAN, Enovia, and Clearcase are increasing in usage with
 Windows client platforms and therefore with SMB datastores. PDM applications manage multiuser environments for
 critical data security and access. The typical PDM environment is usually associated with sophisticated client
@@ -322,8 +322,8 @@ design applications that will load data locally as demanded. In addition, the PD
 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 oplocks management, by disabling oplocks on the share.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616679"></a>Beware of Force User</h4></div></div></div><p>
-<a class="indexterm" name="id2616687"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616711"></a>Beware of Force User</h4></div></div></div><p>
+<a class="indexterm" name="id2616719"></a>
 Samba includes an <code class="filename">smb.conf</code> parameter called <a class="link" href="smb.conf.5.html#FORCEUSER" target="_top">force user</a> that changes the user
 accessing a share from the incoming user to whatever user is defined by the <code class="filename">smb.conf</code> variable. If oplocks is
 enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the
@@ -338,10 +338,10 @@ Avoid the combination of the following:
 	Slow or unreliable networks.
 	</p></li><li><p>
 	Oplocks enabled.
-	</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616767"></a>Advanced Samba Oplocks Parameters</h4></div></div></div><p>
-<a class="indexterm" name="id2616775"></a>
-<a class="indexterm" name="id2616782"></a>
-<a class="indexterm" name="id2616789"></a>
+	</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616799"></a>Advanced Samba Oplocks Parameters</h4></div></div></div><p>
+<a class="indexterm" name="id2616807"></a>
+<a class="indexterm" name="id2616814"></a>
+<a class="indexterm" name="id2616821"></a>
 Samba provides oplock parameters that allow the
 administrator to adjust various properties of the oplock mechanism to
 account for timing and usage levels. These parameters provide good
@@ -350,13 +350,13 @@ likely cause problems. The parameters are
 <a class="link" href="smb.conf.5.html#OPLOCKBREAKWAITTIME" target="_top">oplock break wait time</a>, and
 <a class="link" href="smb.conf.5.html#OPLOCKCONTENTIONLIMIT" target="_top">oplock contention limit</a>.
 </p><p>
-<a class="indexterm" name="id2616828"></a>
+<a class="indexterm" name="id2616861"></a>
 For most users, administrators, and environments, if these parameters
 are required, then the better option is simply to turn oplocks off.
 The Samba SWAT help text for both parameters reads: &#8220;<span class="quote">Do not change
 this parameter unless you have read and understood the Samba oplock code.</span>&#8221;
 This is good advice.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616846"></a>Mission-Critical, High-Availability</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2616878"></a>Mission-Critical, High-Availability</h4></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
@@ -386,7 +386,7 @@ In mission-critical, high-availability environments, careful attention
 should be given to oplocks. 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="id2616903"></a>Samba Oplocks Control</h2></div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2616945"></a>Samba Oplocks Control</h2></div></div></div><p>
 Oplocks 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.
@@ -436,23 +436,23 @@ of your client sending oplock breaks and will instead want to disable oplocks fo
 </p><p>
 Another factor to consider is the perceived performance of file access. If oplocks provide no
 measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2616998"></a>Example Configuration</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617040"></a>Example Configuration</h3></div></div></div><p>
 In the following section 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="id2617008"></a>Disabling Oplocks</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617050"></a>Disabling Oplocks</h4></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><em class="parameter"><code>[acctdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2617035"></a><em class="parameter"><code>oplocks = False</code></em></td></tr><tr><td><a class="indexterm" name="id2617047"></a><em class="parameter"><code>level2 oplocks = False</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[acctdata]</code></em></td></tr><tr><td><a class="indexterm" name="id2617077"></a><em class="parameter"><code>oplocks = False</code></em></td></tr><tr><td><a class="indexterm" name="id2617089"></a><em class="parameter"><code>level2 oplocks = False</code></em></td></tr></table><p>
 </p><p>
 The default oplock type is Level1. Level2 oplocks are enabled on a per-share basis
 in the <code class="filename">smb.conf</code> 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><a class="indexterm" name="id2617083"></a><em class="parameter"><code>veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2617125"></a><em class="parameter"><code>veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/</code></em></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="id2617103"></a>Disabling Kernel Oplocks</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2617145"></a>Disabling Kernel Oplocks</h4></div></div></div><p>
 Kernel oplocks is an <code class="filename">smb.conf</code> 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
@@ -465,7 +465,7 @@ 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 <code class="filename">smb.conf</code> file.
 </p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2617143"></a><em class="parameter"><code>kernel oplocks = yes</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2617185"></a><em class="parameter"><code>kernel oplocks = yes</code></em></td></tr></table><p>
 The default is no.
 </p><p>
 <span class="emphasis"><em>Veto oplocks</em></span> is an <code class="filename">smb.conf</code> parameter that identifies specific files for
@@ -480,14 +480,14 @@ 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
 <code class="filename">smb.conf</code> file as shown in <a class="link" href="locking.html#far1" title="Example�17.1.�Share with Some Files Oplocked">&#8220;Share with Some Files Oplocked&#8221;</a>.
 </p><p>
-</p><div class="example"><a name="far1"></a><p class="title"><b>Example�17.1.�Share with Some Files Oplocked</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617220"></a><em class="parameter"><code>veto oplock files = /filename.htm/*.txt/</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2617241"></a><em class="parameter"><code>veto oplock files = /*.exe/filename.ext/</code></em></td></tr></table></div></div><p><br class="example-break">
+</p><div class="example"><a name="far1"></a><p class="title"><b>Example�17.1.�Share with Some Files Oplocked</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617262"></a><em class="parameter"><code>veto oplock files = /filename.htm/*.txt/</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2617283"></a><em class="parameter"><code>veto oplock files = /*.exe/filename.ext/</code></em></td></tr></table></div></div><p><br class="example-break">
 </p><p>
 <a class="link" href="smb.conf.5.html#OPLOCKBREAKWAITTIME" target="_top">oplock break wait time</a> is an <code class="filename">smb.conf</code> parameter
 that adjusts the time interval for Samba to reply to an oplock break request. Samba recommends:
 &#8220;<span class="quote">Do not change this parameter unless you have read and understood the Samba oplock code.</span>&#8221;
 Oplock break wait time can only be configured globally in the <code class="filename">smb.conf</code> file as shown:
 </p><p>
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2617298"></a><em class="parameter"><code>oplock break wait time =  0 (default)</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2617340"></a><em class="parameter"><code>oplock break wait time =  0 (default)</code></em></td></tr></table><p>
 </p><p>
 <span class="emphasis"><em>Oplock break contention limit</em></span> is an <code class="filename">smb.conf</code> parameter that limits the
 response of the Samba server to grant an oplock if the configured
@@ -496,8 +496,8 @@ number of contending clients reaches the limit specified by the parameter. Samba
 Oplock break contention limit can be enabled on a per-share basis, or globally for
 the entire server, in the <code class="filename">smb.conf</code> file as shown in <a class="link" href="locking.html#far3" title="Example�17.2.�Configuration with Oplock Break Contention Limit">&#8220;Configuration with Oplock Break Contention Limit&#8221;</a>.
 </p><p>
-</p><div class="example"><a name="far3"></a><p class="title"><b>Example�17.2.�Configuration with Oplock Break Contention Limit</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617372"></a><em class="parameter"><code>oplock break contention limit =  2 (default)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2617394"></a><em class="parameter"><code>oplock break contention limit =  2 (default)</code></em></td></tr></table></div></div><p><br class="example-break">
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617411"></a>MS Windows Oplocks and Caching Controls</h2></div></div></div><p>
+</p><div class="example"><a name="far3"></a><p class="title"><b>Example�17.2.�Configuration with Oplock Break Contention Limit</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2617414"></a><em class="parameter"><code>oplock break contention limit =  2 (default)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[share_name]</code></em></td></tr><tr><td><a class="indexterm" name="id2617435"></a><em class="parameter"><code>oplock break contention limit =  2 (default)</code></em></td></tr></table></div></div><p><br class="example-break">
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617453"></a>MS Windows Oplocks and Caching Controls</h2></div></div></div><p>
 There is a known issue when running applications (like Norton Antivirus) 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
@@ -512,7 +512,7 @@ All Windows operating systems in the NT family that act as database servers for
 (meaning that data files are stored there and accessed by other Windows PCs) may need to
 have oplocks disabled in order to minimize the risk of data file corruption.
 This includes Windows 9x/Me, Windows NT, Windows 200x, and Windows XP.
-<sup>[<a name="id2617444" href="#ftn.id2617444" class="footnote">5</a>]</sup>
+<sup>[<a name="id2617485" href="#ftn.id2617485" class="footnote">5</a>]</sup>
 </p><p>
 If you are using a Windows NT family workstation in place of a server, you must also
 disable oplocks on that workstation. For example, if you use a
@@ -590,7 +590,7 @@ An illustration of how Level2 oplocks work follows:
 	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="id2617598"></a>Workstation Service Entries</h3></div></div></div><pre class="programlisting">
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617640"></a>Workstation Service Entries</h3></div></div></div><pre class="programlisting">
 	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanWorkstation\Parameters
 
@@ -599,7 +599,7 @@ An illustration of how Level2 oplocks work follows:
 </pre><p>
 This indicates whether the redirector should use oplocks 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="id2617620"></a>Server Service Entries</h3></div></div></div><pre class="programlisting">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617662"></a>Server Service Entries</h3></div></div></div><pre class="programlisting">
 	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanServer\Parameters
 
@@ -628,7 +628,7 @@ the server disables raw I/O and oplocks for this connection.
 This 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="id2617686"></a>Persistent Data Corruption</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617728"></a>Persistent Data Corruption</h2></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>
@@ -639,7 +639,7 @@ rebuild the data files in question. This involves creating a new data file with
 same definition as the file to be rebuilt and transferring the data from the old file
 to the new one. There are several known methods for doing this that can be found in
 our knowledge base.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617712"></a>Common Errors</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617754"></a>Common Errors</h2></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.
@@ -669,7 +669,7 @@ so far:
 	report on Samba <a class="ulink" href="https://bugzilla.samba.org" target="_top">Bugzilla</a> without delay.
 	Make sure that you give as much information as you possibly can to help isolate the
 	cause and to allow replication 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="id2617779"></a>locking.tdb Error Messages</h3></div></div></div><p>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617821"></a>locking.tdb Error Messages</h3></div></div></div><p>
 		&#8220;<span class="quote">
 			We are seeing lots of errors in the Samba logs, like:
 		</span>&#8221;
@@ -683,29 +683,29 @@ tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
 		</span>&#8221;
 	</p><p>
 	This error indicates a corrupted tdb. Stop all instances of smbd, delete locking.tdb, and restart smbd.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617810"></a>Problems Saving Files in MS Office on Windows XP</h3></div></div></div><a class="indexterm" name="id2617816"></a><p>This is a bug in Windows XP. More information can be 
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617852"></a>Problems Saving Files in MS Office on Windows XP</h3></div></div></div><a class="indexterm" name="id2617858"></a><p>This is a bug in Windows XP. More information can be 
 		found in <a class="ulink" 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="id2617834"></a>Long Delays Deleting Files over Network with XP SP1</h3></div></div></div><p>&#8220;<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.</span>&#8221;</p><a class="indexterm" name="id2617847"></a><p>This is a bug in Windows XP. More information can be found in <a class="ulink" href="http://support.microsoft.com/?id=811492" target="_top">
+	</div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2617876"></a>Long Delays Deleting Files over Network with XP SP1</h3></div></div></div><p>&#8220;<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.</span>&#8221;</p><a class="indexterm" name="id2617888"></a><p>This is a bug in Windows XP. More information can be found in <a class="ulink" 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="id2617866"></a>Additional Reading</h2></div></div></div><p>
+	</div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2617908"></a>Additional Reading</h2></div></div></div><p>
 You may want to check for an updated documentation regarding file and record locking issues on the Microsoft
 <a class="ulink" href="http://support.microsoft.com/" target="_top">Support</a> web site. Additionally, search for the word
 <code class="literal">locking</code> on the Samba <a class="ulink" href="http://www.samba.org/" target="_top">web</a> site.
 </p><p>
 Section of the Microsoft MSDN Library on opportunistic locking: 
 </p><p>
-<a class="indexterm" name="id2617902"></a>
+<a class="indexterm" name="id2617944"></a>
 Microsoft Knowledge Base, &#8220;<span class="quote">Maintaining Transactional Integrity with OPLOCKS</span>&#8221;,
 Microsoft Corporation, April 1999, <a class="ulink" href="http://support.microsoft.com/?id=224992" target="_top">Microsoft
 KB Article 224992</a>.
 </p><p>
-<a class="indexterm" name="id2617926"></a>
+<a class="indexterm" name="id2617968"></a>
 Microsoft Knowledge Base, &#8220;<span class="quote">Configuring Opportunistic Locking in Windows 2000</span>&#8221;,
 Microsoft Corporation, April 2001 <a class="ulink" href="http://support.microsoft.com/?id=296264" target="_top">Microsoft KB Article 296264</a>.
 </p><p>
-<a class="indexterm" name="id2617950"></a>
+<a class="indexterm" name="id2617992"></a>
 Microsoft Knowledge Base, &#8220;<span class="quote">PC Ext: Explanation of Opportunistic Locking on Windows NT</span>&#8221;,
 Microsoft Corporation, April 1995 <a class="ulink" href="http://support.microsoft.com/?id=129202" target="_top">Microsoft
 KB Article 129202</a>.
-</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2617444" href="#id2617444" class="para">5</a>] </sup>Microsoft has documented this in Knowledge Base article 300216.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="securing-samba.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�16.�File, Directory, and Share Access Controls�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�18.�Securing Samba</td></tr></table></div></body></html>
+</p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2617485" href="#id2617485" class="para">5</a>] </sup>Microsoft has documented this in Knowledge Base article 300216.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="securing-samba.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�16.�File, Directory, and Share Access Controls�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�18.�Securing Samba</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/migration.html b/docs/htmldocs/Samba3-HOWTO/migration.html
index f29b6e4102..b91d8003d8 100644
--- a/docs/htmldocs/Samba3-HOWTO/migration.html
+++ b/docs/htmldocs/Samba3-HOWTO/migration.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�IV.�Migration and Updating</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="cfgsmarts.html" title="Chapter�34.�Advanced Configuration Techniques"><link rel="next" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�IV.�Migration and Updating</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cfgsmarts.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Part�IV.�Migration and Updating</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="upgrading-to-3.0.html">35. Updating and Upgrading Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676070">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676098">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676299">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676308">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677518">New Functionality</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NT4Migration.html">36. Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><dl><dt><span class="sect1"><a href="NT4Migration.html#id2678914">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2678949">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2679885">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680120">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680206">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680440">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SWAT.html">37. SWAT: The Samba Web Administration Tool</a></span></dt><dd><dl><dt><span class="sect1"><a href="SWAT.html#id2680929">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681054">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681073">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681711">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681863">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682061">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682074">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682135">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682237">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682293">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682349">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682412">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682456">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682475">The Password Change Page</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cfgsmarts.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�34.�Advanced Configuration Techniques�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�35.�Updating and Upgrading Samba</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�IV.�Migration and Updating</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="cfgsmarts.html" title="Chapter�34.�Advanced Configuration Techniques"><link rel="next" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�IV.�Migration and Updating</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cfgsmarts.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Part�IV.�Migration and Updating</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="upgrading-to-3.0.html">35. Updating and Upgrading Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676214">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676251">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676451">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676460">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677671">New Functionality</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NT4Migration.html">36. Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><dl><dt><span class="sect1"><a href="NT4Migration.html#id2679067">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2679102">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680047">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id2680282">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id2680369">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id2680602">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SWAT.html">37. SWAT: The Samba Web Administration Tool</a></span></dt><dd><dl><dt><span class="sect1"><a href="SWAT.html#id2681092">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2681216">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2681236">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2681873">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682025">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2682223">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2682236">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682297">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682399">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682455">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682511">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682574">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682618">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2682637">The Password Change Page</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cfgsmarts.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�34.�Advanced Configuration Techniques�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�35.�Updating and Upgrading Samba</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/msdfs.html b/docs/htmldocs/Samba3-HOWTO/msdfs.html
index 822f7fef74..614abc9d8c 100644
--- a/docs/htmldocs/Samba3-HOWTO/msdfs.html
+++ b/docs/htmldocs/Samba3-HOWTO/msdfs.html
@@ -1,27 +1,27 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�20.�Hosting a Microsoft Distributed File System Tree</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="InterdomainTrusts.html" title="Chapter�19.�Interdomain Trust Relationships"><link rel="next" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�20.�Hosting a Microsoft Distributed File System Tree</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="classicalprinting.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="msdfs"></a>Chapter�20.�Hosting a Microsoft Distributed File System Tree</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Shirish</span> <span class="orgname">Samba Team &amp; Veritas Software</span> <span class="surname">Kalele</span></h3><div class="affiliation"><span class="orgname">Samba Team &amp; Veritas Software<br></span><div class="address"><p><br>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�20.�Hosting a Microsoft Distributed File System Tree</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="InterdomainTrusts.html" title="Chapter�19.�Interdomain Trust Relationships"><link rel="next" href="classicalprinting.html" title="Chapter�21.�Classical Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�20.�Hosting a Microsoft Distributed File System Tree</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="classicalprinting.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="msdfs"></a>Chapter�20.�Hosting a Microsoft Distributed File System Tree</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Shirish</span> <span class="orgname">Samba Team &amp; Veritas Software</span> <span class="surname">Kalele</span></h3><div class="affiliation"><span class="orgname">Samba Team &amp; Veritas Software<br></span><div class="address"><p><br>
 				<code class="email">&lt;<a class="email" href="mailto:samba@samba.org">samba@samba.org</a>&gt;</code><br>
-			</p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="msdfs.html#id2621432">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621844">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621877">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621432"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2621440"></a>
-<a class="indexterm" name="id2621449"></a>
-<a class="indexterm" name="id2621456"></a>
-<a class="indexterm" name="id2621463"></a>
-<a class="indexterm" name="id2621470"></a>
+			</p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="msdfs.html#id2621467">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621887">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621920">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621467"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2621475"></a>
+<a class="indexterm" name="id2621485"></a>
+<a class="indexterm" name="id2621492"></a>
+<a class="indexterm" name="id2621499"></a>
+<a class="indexterm" name="id2621506"></a>
 	The distributed file system (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, and so on.
 	</p><p>
-<a class="indexterm" name="id2621485"></a>
-<a class="indexterm" name="id2621492"></a>
-<a class="indexterm" name="id2621498"></a>
+<a class="indexterm" name="id2621521"></a>
+<a class="indexterm" name="id2621527"></a>
+<a class="indexterm" name="id2621534"></a>
 	For information about DFS, refer to the <a class="ulink" href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top">Microsoft
 	documentation</a>.  This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients
 	to browse) using Samba.
 	</p><p>
-<a class="indexterm" name="id2621519"></a>
-<a class="indexterm" name="id2621526"></a>
-<a class="indexterm" name="id2621532"></a>
-<a class="indexterm" name="id2621539"></a>
+<a class="indexterm" name="id2621554"></a>
+<a class="indexterm" name="id2621561"></a>
+<a class="indexterm" name="id2621568"></a>
+<a class="indexterm" name="id2621575"></a>
 	A Samba server can be made a DFS server by setting the global Boolean <a class="link" href="smb.conf.5.html#HOSTMSDFS" target="_top">host msdfs</a>
 	parameter in the <code class="filename">smb.conf</code> file. You designate a share as a DFS root using the share-level Boolean
 	<a class="link" href="smb.conf.5.html#MSDFSROOT" target="_top">msdfs root</a> parameter. A DFS root directory on Samba hosts DFS links in the form of
@@ -30,10 +30,10 @@
 	DFS-aware clients attempt to access the junction link, they are redirected to the storage location (in this
 	case, <em class="parameter"><code>\\storage1\share1</code></em>).
 	</p><p>
-<a class="indexterm" name="id2621601"></a>
-<a class="indexterm" name="id2621608"></a>
-<a class="indexterm" name="id2621615"></a>
-<a class="indexterm" name="id2621621"></a>
+<a class="indexterm" name="id2621637"></a>
+<a class="indexterm" name="id2621643"></a>
+<a class="indexterm" name="id2621650"></a>
+<a class="indexterm" name="id2621657"></a>
 	DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.
 	<a class="link" href="msdfs.html#dfscfg" title="Example�20.1.�smb.conf with DFS Configured">The following sample configuration</a> shows how to setup a DFS tree on a Samba server.
 	In the <code class="filename">/export/dfsroot</code> directory, you set up your DFS links to 
@@ -45,28 +45,28 @@
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s msdfs:storageA\\shareA linka</code></strong>
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s msdfs:serverB\\share,serverC\\share linkb</code></strong>
 </pre><p>
-</p><div class="example"><a name="dfscfg"></a><p class="title"><b>Example�20.1.�smb.conf with DFS Configured</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2621731"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2621743"></a><em class="parameter"><code>host msdfs   = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[dfs]</code></em></td></tr><tr><td><a class="indexterm" name="id2621763"></a><em class="parameter"><code>path = /export/dfsroot</code></em></td></tr><tr><td><a class="indexterm" name="id2621775"></a><em class="parameter"><code>msdfs root = yes</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2621790"></a>
-<a class="indexterm" name="id2621797"></a>
-<a class="indexterm" name="id2621803"></a>
+</p><div class="example"><a name="dfscfg"></a><p class="title"><b>Example�20.1.�smb.conf with DFS Configured</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2621766"></a><em class="parameter"><code>netbios name = GANDALF</code></em></td></tr><tr><td><a class="indexterm" name="id2621778"></a><em class="parameter"><code>host msdfs   = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[dfs]</code></em></td></tr><tr><td><a class="indexterm" name="id2621799"></a><em class="parameter"><code>path = /export/dfsroot</code></em></td></tr><tr><td><a class="indexterm" name="id2621811"></a><em class="parameter"><code>msdfs root = yes</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2621825"></a>
+<a class="indexterm" name="id2621832"></a>
+<a class="indexterm" name="id2621839"></a>
 	You should set up the permissions and ownership of the directory acting as the DFS root so 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>
-<a class="indexterm" name="id2621821"></a>
-<a class="indexterm" name="id2621828"></a>
+<a class="indexterm" name="id2621863"></a>
+<a class="indexterm" name="id2621870"></a>
 	Users on DFS-aware clients can now browse the DFS tree on the Samba server at
 	<code class="constant">\\samba\dfs</code>. 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="id2621844"></a>Common Errors</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted 
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621887"></a>Common Errors</h2></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 only designated users can 
-		modify the symbolic links in the directory.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621877"></a>MSDFS UNIX Path Is Case-Critical</h3></div></div></div><p>
+		modify the symbolic links in the directory.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2621920"></a>MSDFS UNIX Path Is Case-Critical</h3></div></div></div><p>
 		A network administrator sent advice to the Samba mailing list
 		after long sessions trying to determine why DFS was not working.
 		His advice is worth noting.
@@ -78,7 +78,7 @@
 		in lowercase as well.
 		</span>&#8221;</p><p>
 		&#8220;<span class="quote">For example, I had a share defined as such:</span>&#8221;
-		</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[pub]</code></em></td></tr><tr><td><a class="indexterm" name="id2621918"></a><em class="parameter"><code>path = /export/home/Shares/public_share</code></em></td></tr><tr><td><a class="indexterm" name="id2621930"></a><em class="parameter"><code>msdfs root = yes</code></em></td></tr></table><p>
+		</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[pub]</code></em></td></tr><tr><td><a class="indexterm" name="id2621960"></a><em class="parameter"><code>path = /export/home/Shares/public_share</code></em></td></tr><tr><td><a class="indexterm" name="id2621972"></a><em class="parameter"><code>msdfs root = yes</code></em></td></tr></table><p>
 		&#8220;<span class="quote">and I could not make my Windows 9x/Me (with the dfs client installed) follow this symlink:</span>&#8221;
 		</p><pre class="screen">
 		damage1 -&gt; msdfs:damage\test-share
diff --git a/docs/htmldocs/Samba3-HOWTO/optional.html b/docs/htmldocs/Samba3-HOWTO/optional.html
index 254ab8f28e..bcf21905f3 100644
--- a/docs/htmldocs/Samba3-HOWTO/optional.html
+++ b/docs/htmldocs/Samba3-HOWTO/optional.html
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Advanced Configuration</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="ClientConfig.html" title="Chapter�8.�MS Windows Network Configuration Guide"><link rel="next" href="ChangeNotes.html" title="Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Advanced Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ChangeNotes.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Part�III.�Advanced Configuration</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2578500"></a>Valuable Nuts and Bolts Information</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�III.�Advanced Configuration</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="ClientConfig.html" title="Chapter�8.�MS Windows Network Configuration Guide"><link rel="next" href="ChangeNotes.html" title="Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�III.�Advanced Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ChangeNotes.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Part�III.�Advanced Configuration</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2578486"></a>Valuable Nuts and Bolts Information</h1></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><span class="chapter"><a href="ChangeNotes.html">9. Important and Critical Change Notes for the Samba 3.x Series</a></span></dt><dd><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578591">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578602">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578661">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578973">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579095">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579155">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579275">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetworkBrowsing.html">10. Network Browsing</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579538">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579722">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580162">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580798">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581357">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582304">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582916">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583156">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583178">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583364">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583504">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583597">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583876">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584196">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584250">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584481">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584492">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584634">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584837">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584924">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585120">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585378">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586391">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586418">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586491">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586539">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586586">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586786">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="passdb.html">11. Account Information Databases</a></span></dt><dd><dl><dt><span class="sect1"><a href="passdb.html#id2587269">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587489">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588057">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589125">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589979">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592519">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592573">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592915">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593073">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595597">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595603">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595641">Configuration of auth methods</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="groupmapping.html">12. Group Mapping: MS Windows and UNIX</a></span></dt><dd><dl><dt><span class="sect1"><a href="groupmapping.html#id2595892">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596308">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596702">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597278">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597519">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598144">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598220">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598232">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598404">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598531">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598544">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598630">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetCommand.html">13. Remote and Local Management: The Net Command</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetCommand.html#id2599025">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599319">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599400">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599559">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600921">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601133">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601181">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601250">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601333">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601678">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601693">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602062">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602296">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602518">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602563">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602751">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602781">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603404">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603657">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603676">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603742">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603858">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603875">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603919">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603955">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></dd><dt><span class="chapter"><a href="idmapper.html">14. Identity Mapping (IDMAP)</a></span></dt><dd><dl><dt><span class="sect1"><a href="idmapper.html#id2604465">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604490">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604553">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605504">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605739">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605810">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605874">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606596">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607186">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607771">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="rights.html">15. User Rights and Privileges</a></span></dt><dd><dl><dt><span class="sect1"><a href="rights.html#id2608440">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608715">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609060">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609882">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610059">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AccessControls.html">16. File, Directory, and Share Access Controls</a></span></dt><dd><dl><dt><span class="sect1"><a href="AccessControls.html#id2610562">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610748">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611105">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611229">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611888">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611921">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612289">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612626">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612964">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613112">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613459">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613465">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613512">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613583">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613726">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613942">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614099">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614468">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614541">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614954">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614965">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615288">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615334">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="locking.html">17. File and Record Locking</a></span></dt><dd><dl><dt><span class="sect1"><a href="locking.html#id2615570">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615667">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615926">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616903">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2616998">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617411">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617598">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617620">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617686">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617712">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617779">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617810">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617834">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617866">Additional Reading</a></span></dt></dl></dd><dt><span class="chapter"><a href="securing-samba.html">18. Securing Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="securing-samba.html#id2618040">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618151">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618297">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618313">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618467">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618527">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619021">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619076">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619119">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619142">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="InterdomainTrusts.html">19. Interdomain Trust Relationships</a></span></dt><dd><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619731">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619803">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620081">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620117">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620214">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620299">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620508">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620849">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621046">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621195">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621208">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621254">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="msdfs.html">20. Hosting a Microsoft Distributed File System Tree</a></span></dt><dd><dl><dt><span class="sect1"><a href="msdfs.html#id2621432">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621844">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621877">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="classicalprinting.html">21. Classical Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622075">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622298">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622450">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622509">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622610">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622894">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623091">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623480">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623935">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626650">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626819">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626941">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627158">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627479">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627627">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627720">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629667">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629683">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630248">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630366">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630540">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630560">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630928">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631184">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631444">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631557">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631819">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631928">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2631965">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632011">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632045">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632061">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632078">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632212">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632486">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632524">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632673">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632702">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632708">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632749">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="CUPS-printing.html">22. CUPS Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632896">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632902">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632962">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633081">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633196">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633445">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633679">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634056">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634073">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634124">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634359">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634646">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634767">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634960">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635137">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635495">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635650">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635733">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635852">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635892">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636128">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636556">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636764">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636922">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637109">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637277">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637547">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637631">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637850">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638189">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638424">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638437">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638506">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638614">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638893">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639176">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639513">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639941">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640064">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640159">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640176">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640238">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640309">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640414">Network Printing (Windows Clients and UNIX/Samba Print
-Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640432">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640622">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640702">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640792">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640836">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640904">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640919">Printer Drivers Running in Kernel Mode Cause Many
-Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640957">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640975">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641018">PostScript Drivers with No Major Problems, Even in Kernel
-Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641105">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641128">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641226">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641507">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641746">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641865">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641890">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641953">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642253">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642470">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642611">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642748">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642892">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643014">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643095">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643176">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643411">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643585">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643757">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643862">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643994">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644219">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645177">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645320">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645523">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645591">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645657">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645708">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645827">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646003">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646814">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647287">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647322">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647376">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647417">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647558">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647709">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647775">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647815">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647829">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648046">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648122">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648207">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648346">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648394">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648699">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648810">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648816">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648892">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648930">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649005">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649029">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649120">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649172">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649209">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649245">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649280">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649313">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649354">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649379">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649426">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649709">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649764">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649814">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649912">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649981">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650035">Overview of the CUPS Printing Processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="VFS.html">23. Stackable VFS modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="VFS.html#id2650223">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650261">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650657">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650662">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650703">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650921">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651247">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651644">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651694">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652604">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652629">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652689">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652728">vscan-clamav</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="winbind.html">24. Winbind: Use of Domain Accounts</a></span></dt><dd><dl><dt><span class="sect1"><a href="winbind.html#id2652992">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653341">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653431">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653584">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653629">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653755">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653892">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653940">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654172">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654327">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654403">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654460">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654466">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654580">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654732">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657151">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657199">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657241">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657278">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AdvancedNetworkManagement.html">25. Advanced Network Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657466">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657493">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657636">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657665">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658041">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658226">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658451">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658494">Limiting Logon Connections</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="PolicyMgmt.html">26. System and Account Policies</a></span></dt><dd><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658637">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658743">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2658932">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659069">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659297">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659746">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2659980">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659993">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660075">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660115">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660180">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660338">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660349">Policy Does Not Work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ProfileMgmt.html">27. Desktop Profile Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660434">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660484">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660538">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661143">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662488">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662522">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662631">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2662982">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663122">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663192">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663223">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663374">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663936">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664442">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664453">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664514">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664685">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664849">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="pam.html">28. PAM-Based Distributed Authentication</a></span></dt><dd><dl><dt><span class="sect1"><a href="pam.html#id2665025">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665655">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665709">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666709">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667015">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667096">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667199">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667593">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667604">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667702">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="integrate-ms-networks.html">29. Integrating MS Windows Networks with Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667924">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2667945">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668074">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668147">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668326">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668362">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668413">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668537">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668972">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669058">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669245">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669273">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669301">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669438">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669452">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669483">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669525">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="unicode.html">30. Unicode/Charsets</a></span></dt><dd><dl><dt><span class="sect1"><a href="unicode.html#id2669736">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669787">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669921">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670056">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670088">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670218">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670859">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670982">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671128">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671134">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Backup.html">31. Backup Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="Backup.html#id2671241">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671286">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671383">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671554">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671724">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671772">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SambaHA.html">32. High Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="SambaHA.html#id2671868">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2671989">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672023">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672152">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672866">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672946">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673086">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673123">Conclusions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="largefile.html">33. Handling Large Directories</a></span></dt><dt><span class="chapter"><a href="cfgsmarts.html">34. Advanced Configuration Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673754">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673763">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674160">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675174">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="ChangeNotes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�8.�MS Windows Network Configuration Guide�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</td></tr></table></div></body></html>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ChangeNotes.html">9. Important and Critical Change Notes for the Samba 3.x Series</a></span></dt><dd><dl><dt><span class="sect1"><a href="ChangeNotes.html#id2578577">Important Samba-3.2.x Change Notes</a></span></dt><dt><span class="sect1"><a href="ChangeNotes.html#id2578588">Important Samba-3.0.x Change Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ChangeNotes.html#id2578647">User and Group Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2578959">Essential Group Mappings</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579081">Passdb Changes</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579141">Group Mapping Changes in Samba-3.0.23</a></span></dt><dt><span class="sect2"><a href="ChangeNotes.html#id2579261">LDAP Changes in Samba-3.0.23</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetworkBrowsing.html">10. Network Browsing</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579524">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id2579708">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580148">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2580784">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2581343">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582290">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2582891">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583131">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583152">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583338">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583478">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2583571">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2583843">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584164">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584217">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584448">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584459">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584601">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2584804">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2584891">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585087">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2585339">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id2586352">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586378">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586451">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586500">I Get an "Unable to browse the network" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586546">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id2586746">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="passdb.html">11. Account Information Databases</a></span></dt><dd><dl><dt><span class="sect1"><a href="passdb.html#id2587230">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587457">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588025">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589094">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589947">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592500">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592553">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592895">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593053">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595578">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595583">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595621">Configuration of auth methods</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="groupmapping.html">12. Group Mapping: MS Windows and UNIX</a></span></dt><dd><dl><dt><span class="sect1"><a href="groupmapping.html#id2595872">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596288">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596625">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596682">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597258">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597499">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598124">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598201">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598212">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598384">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598511">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598524">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598611">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="NetCommand.html">13. Remote and Local Management: The Net Command</a></span></dt><dd><dl><dt><span class="sect1"><a href="NetCommand.html#id2599005">Overview</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599300">Administrative Tasks and Methods</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2599381">UNIX and Windows Group Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2599539">Adding, Renaming, or Deletion of Group Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#grpmemshipchg">Manipulating Group Memberships</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#nestedgrpmgmgt">Nested Group Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2600908">UNIX and Windows User Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#sbeuseraddn">Adding User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601120">Deletion of User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601168">Managing User Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2601237">User Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2601320">Administering User Rights and Privileges</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2601665">Managing Trust Relationships</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2601680">Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602049">Interdomain Trusts</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2602283">Managing Security Identifiers (SIDS)</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2602505">Share Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2602550">Creating, Editing, and Removing Shares</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602738">Creating and Changing Share ACLs</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2602768">Share, Directory, and File Migration</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603391">Printer Migration</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#id2603642">Controlling Open Files</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603661">Session and Connection Management</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603727">Printers and ADS</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603842">Manipulating the Samba Cache</a></span></dt><dt><span class="sect1"><a href="NetCommand.html#id2603860">Managing IDMAP UID/SID Mappings</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetCommand.html#id2603904">Creating an IDMAP Database Dump File</a></span></dt><dt><span class="sect2"><a href="NetCommand.html#id2603939">Restoring the IDMAP Database Dump File</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetCommand.html#netmisc1">Other Miscellaneous Operations</a></span></dt></dl></dd><dt><span class="chapter"><a href="idmapper.html">14. Identity Mapping (IDMAP)</a></span></dt><dd><dl><dt><span class="sect1"><a href="idmapper.html#id2604449">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2604474">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2604536">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605493">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2605727">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id2605799">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id2605862">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2606584">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607175">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id2607760">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="rights.html">15. User Rights and Privileges</a></span></dt><dd><dl><dt><span class="sect1"><a href="rights.html#id2608437">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608712">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609058">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609884">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610061">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AccessControls.html">16. File, Directory, and Share Access Controls</a></span></dt><dd><dl><dt><span class="sect1"><a href="AccessControls.html#id2610564">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610751">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610766">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611102">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611225">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611896">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611929">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612297">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612634">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612972">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613120">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613466">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613473">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613520">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613591">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613735">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613950">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614107">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614477">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614550">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614968">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614980">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615303">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615348">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="locking.html">17. File and Record Locking</a></span></dt><dd><dl><dt><span class="sect1"><a href="locking.html#id2615585">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="locking.html#id2615682">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2615940">Opportunistic Locking Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2616945">Samba Oplocks Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617040">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617453">MS Windows Oplocks and Caching Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617640">Workstation Service Entries</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617662">Server Service Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617728">Persistent Data Corruption</a></span></dt><dt><span class="sect1"><a href="locking.html#id2617754">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="locking.html#id2617821">locking.tdb Error Messages</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617852">Problems Saving Files in MS Office on Windows XP</a></span></dt><dt><span class="sect2"><a href="locking.html#id2617876">Long Delays Deleting Files over Network with XP SP1</a></span></dt></dl></dd><dt><span class="sect1"><a href="locking.html#id2617908">Additional Reading</a></span></dt></dl></dd><dt><span class="chapter"><a href="securing-samba.html">18. Securing Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="securing-samba.html#id2618082">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618181">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618327">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618343">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618497">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618557">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619056">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619110">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619154">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619170">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="InterdomainTrusts.html">19. Interdomain Trust Relationships</a></span></dt><dd><dl><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619759">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2619831">Trust Relationship Background</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620117">Native MS Windows NT4 Trusts Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620153">Creating an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620250">Completing an NT4 Domain Trust</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620335">Interdomain Trust Facilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2620544">Configuring Samba NT-Style Domain Trusts</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2620885">Samba as the Trusting Domain</a></span></dt></dl></dd><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621081">NT4-Style Domain Trusts with Windows 2000</a></span></dt><dt><span class="sect1"><a href="InterdomainTrusts.html#id2621231">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621243">Browsing of Trusted Domain Fails</a></span></dt><dt><span class="sect2"><a href="InterdomainTrusts.html#id2621289">Problems with LDAP ldapsam and Older Versions of smbldap-tools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="msdfs.html">20. Hosting a Microsoft Distributed File System Tree</a></span></dt><dd><dl><dt><span class="sect1"><a href="msdfs.html#id2621467">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="msdfs.html#id2621887">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="msdfs.html#id2621920">MSDFS UNIX Path Is Case-Critical</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="classicalprinting.html">21. Classical Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="classicalprinting.html#id2622118">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2622341">Technical Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622493">Client to Samba Print Job Processing</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2622552">Printing-Related Configuration Parameters</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2622653">Simple Print Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2622937">Verifying Configuration with testparm</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2623134">Rapid Configuration Validation</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2623534">Extended Printing Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2623989">Detailed Explanation Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#cups-msrpc">Printing Developments Since Samba-2.2</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2626705">Point'n'Print Client Drivers on Samba Servers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626874">The Obsoleted [printer$] Section</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2626995">Creating the [print$] Share</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627212">[print$] Stanza Parameters</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2627533">The [print$] Share Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2627675">Installing Drivers into [print$]</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2627768">Add Printer Wizard Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#inst-rpc">Installing Print Drivers Using rpcclient</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2629701">Client Driver Installation Procedure</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2629717">First Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#prt-modeset">Setting Device Modes on New Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630283">Additional Client Driver Installation</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630401">Always Make First Client Connection as root or printer admin</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2630574">Other Gotchas</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2630595">Setting Default Print Options for Client Drivers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2630963">Supporting Large Numbers of Printers</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631219">Adding New Printers with the Windows NT APW</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631479">Error Message: Cannot connect under a different Name</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631592">Take Care When Assembling Driver Files</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2631902">Samba and Printer Ports</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632011">Avoiding Common Client Driver Misconfiguration</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632048">The Imprints Toolset</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632094">What Is Imprints?</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632128">Creating Printer Driver Packages</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632144">The Imprints Server</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632162">The Installation Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="classicalprinting.html#id2632295">Adding Network Printers without User Interaction</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632569">The addprinter Command</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632608">Migration of Classical Printing to Samba</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632756">Publishing Printer Information in Active Directory or LDAP</a></span></dt><dt><span class="sect1"><a href="classicalprinting.html#id2632786">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="classicalprinting.html#id2632791">I Give My Root Password but I Do Not Get Access</a></span></dt><dt><span class="sect2"><a href="classicalprinting.html#id2632833">My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="CUPS-printing.html">22. CUPS Printing Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632975">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632981">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633040">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633159">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633275">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633524">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633768">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634145">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634162">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634213">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634448">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634735">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634856">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635048">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635227">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635586">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635740">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635823">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635943">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635982">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636218">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636647">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636855">Filtering  Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637012">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637200">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637368">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637637">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637722">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637941">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638279">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638515">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638528">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638596">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638704">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638984">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639267">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639604">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640032">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640155">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640249">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640266">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640328">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640399">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640504">Network Printing (Windows Clients and UNIX/Samba Print
+Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640522">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640713">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640792">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640882">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640927">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640995">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641009">Printer Drivers Running in Kernel Mode Cause Many
+Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641048">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641066">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641109">PostScript Drivers with No Major Problems, Even in Kernel
+Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641196">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641218">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641316">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641598">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641837">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641956">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641981">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642043">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642343">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642561">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642701">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642893">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643037">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643159">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643240">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643321">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643556">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643730">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643902">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644007">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644139">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644363">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645322">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645465">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645668">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645735">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645802">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645852">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645972">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646148">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646969">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647442">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647478">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647532">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647572">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647713">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647858">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647924">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647964">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647978">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648195">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648271">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648356">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648495">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648542">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648838">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648950">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648956">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649032">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649070">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649144">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649169">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649260">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649311">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649349">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649384">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649419">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649452">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649493">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649519">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649565">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649848">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649904">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649954">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650052">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650121">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650175">Overview of the CUPS Printing Processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="VFS.html">23. Stackable VFS modules</a></span></dt><dd><dl><dt><span class="sect1"><a href="VFS.html#id2650363">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650401">Discussion</a></span></dt><dt><span class="sect1"><a href="VFS.html#id2650796">Included Modules</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2650802">audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2650843">default_quota</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651060">extd_audit</a></span></dt><dt><span class="sect2"><a href="VFS.html#fakeperms">fake_perms</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651387">recycle</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651783">netatalk</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2651833">shadow_copy</a></span></dt></dl></dd><dt><span class="sect1"><a href="VFS.html#id2652736">VFS Modules Available Elsewhere</a></span></dt><dd><dl><dt><span class="sect2"><a href="VFS.html#id2652762">DatabaseFS</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652821">vscan</a></span></dt><dt><span class="sect2"><a href="VFS.html#id2652861">vscan-clamav</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="winbind.html">24. Winbind: Use of Domain Accounts</a></span></dt><dd><dl><dt><span class="sect1"><a href="winbind.html#id2653125">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653468">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653558">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653711">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653756">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653882">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654026">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654073">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654305">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654460">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654536">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654593">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654599">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654713">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654865">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657284">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657333">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657374">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657411">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="AdvancedNetworkManagement.html">25. Advanced Network Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657600">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657626">Remote Server Administration</a></span></dt><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2657770">Remote Desktop Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2657798">Remote Management from NoMachine.Com</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658174">Remote Management with ThinLinc</a></span></dt></dl></dd><dt><span class="sect1"><a href="AdvancedNetworkManagement.html#id2658359">Network Logon Script Magic</a></span></dt><dd><dl><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658585">Adding Printers without User Intervention</a></span></dt><dt><span class="sect2"><a href="AdvancedNetworkManagement.html#id2658628">Limiting Logon Connections</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="PolicyMgmt.html">26. System and Account Policies</a></span></dt><dd><dl><dt><span class="sect1"><a href="PolicyMgmt.html#id2658770">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2658876">Creating and Managing System Policies</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2659065">Windows 9x/ME Policies</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659202">Windows NT4-Style Policy Files</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2659424">MS Windows 200x/XP Professional Policies</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2659873">Managing Account/User Policies</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660100">Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660112">Samba Editreg Toolset</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660194">Windows NT4/200x</a></span></dt><dt><span class="sect2"><a href="PolicyMgmt.html#id2660235">Samba PDC</a></span></dt></dl></dd><dt><span class="sect1"><a href="PolicyMgmt.html#id2660299">System Startup and Logon Processing Overview</a></span></dt><dt><span class="sect1"><a href="PolicyMgmt.html#id2660457">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="PolicyMgmt.html#id2660469">Policy Does Not Work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ProfileMgmt.html">27. Desktop Profile Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id2660554">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2660603">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2660657">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2661267">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662612">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662645">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2662744">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2663095">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663236">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id2663314">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2663345">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2663502">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664064">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id2664569">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id2664580">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664641">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664813">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id2664976">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="pam.html">28. PAM-Based Distributed Authentication</a></span></dt><dd><dl><dt><span class="sect1"><a href="pam.html#id2665152">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665783">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665836">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666843">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667149">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667230">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667333">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667727">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667738">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667836">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="integrate-ms-networks.html">29. Integrating MS Windows Networks with Samba</a></span></dt><dd><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668059">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668079">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668208">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668281">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668470">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668506">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668557">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668681">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669116">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669202">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669380">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669408">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669435">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669573">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669586">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669617">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669659">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="unicode.html">30. Unicode/Charsets</a></span></dt><dd><dl><dt><span class="sect1"><a href="unicode.html#id2669864">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669916">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670049">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670185">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670216">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670356">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670996">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2671120">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671266">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671272">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="Backup.html">31. Backup Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="Backup.html#id2671379">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="Backup.html#id2671424">Discussion of Backup Solutions</a></span></dt><dd><dl><dt><span class="sect2"><a href="Backup.html#id2671521">BackupPC</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671692">Rsync</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671862">Amanda</a></span></dt><dt><span class="sect2"><a href="Backup.html#id2671910">BOBS: Browseable Online Backup System</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="SambaHA.html">32. High Availability</a></span></dt><dd><dl><dt><span class="sect1"><a href="SambaHA.html#id2672006">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SambaHA.html#id2672127">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="SambaHA.html#id2672161">The Ultimate Goal</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2672290">Why Is This So Hard?</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673010">A Simple Solution</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673091">High-Availability Server Products</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673231">MS-DFS: The Poor Man's Cluster</a></span></dt><dt><span class="sect2"><a href="SambaHA.html#id2673268">Conclusions</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="largefile.html">33. Handling Large Directories</a></span></dt><dt><span class="chapter"><a href="cfgsmarts.html">34. Advanced Configuration Techniques</a></span></dt><dd><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673899">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="ChangeNotes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�8.�MS Windows Network Configuration Guide�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�9.�Important and Critical Change Notes for the Samba 3.x Series</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/pam.html b/docs/htmldocs/Samba3-HOWTO/pam.html
index 3186987003..63e2f000fb 100644
--- a/docs/htmldocs/Samba3-HOWTO/pam.html
+++ b/docs/htmldocs/Samba3-HOWTO/pam.html
@@ -1,30 +1,30 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�28.�PAM-Based Distributed Authentication</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="ProfileMgmt.html" title="Chapter�27.�Desktop Profile Management"><link rel="next" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�28.�PAM-Based Distributed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter�28.�PAM-Based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></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><code class="email">&lt;<a class="email" href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pam.html#id2665025">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665655">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665709">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666709">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667015">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667096">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667199">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667593">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667604">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667702">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2664949"></a>
-<a class="indexterm" name="id2664956"></a>
-<a class="indexterm" name="id2664963"></a>
-<a class="indexterm" name="id2664969"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�28.�PAM-Based Distributed Authentication</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="ProfileMgmt.html" title="Chapter�27.�Desktop Profile Management"><link rel="next" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�28.�PAM-Based Distributed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter�28.�PAM-Based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></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><code class="email">&lt;<a class="email" href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pam.html#id2665152">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2665783">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2665836">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2666843">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667149">smb.conf PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667230">Remote CIFS Authentication Using winbindd.so</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667333">Password Synchronization Using pam_smbpass.so</a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2667727">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2667738">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2667836">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2665076"></a>
+<a class="indexterm" name="id2665083"></a>
+<a class="indexterm" name="id2665090"></a>
+<a class="indexterm" name="id2665097"></a>
 This chapter should help you to deploy Winbind-based authentication on any PAM-enabled
 UNIX/Linux system. Winbind can be used to enable user-level application access authentication
 from any MS Windows NT domain, MS Windows 200x Active Directory-based
 domain, or any Samba-based domain environment. It will also help you to configure PAM-based local host access
 controls that are appropriate to your Samba configuration.
 </p><p>
-<a class="indexterm" name="id2664987"></a>
-<a class="indexterm" name="id2664994"></a>
+<a class="indexterm" name="id2665114"></a>
+<a class="indexterm" name="id2665121"></a>
 In addition to knowing how to configure Winbind into PAM, you will learn generic PAM management
 possibilities and in particular how to deploy tools like <code class="filename">pam_smbpass.so</code> to your advantage.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 The use of Winbind requires more than PAM configuration alone.
 Please refer to <a class="link" href="winbind.html" title="Chapter�24.�Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for further information regarding Winbind.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2665025"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2665033"></a>
-<a class="indexterm" name="id2665039"></a>
-<a class="indexterm" name="id2665046"></a>
-<a class="indexterm" name="id2665053"></a>
-<a class="indexterm" name="id2665062"></a>
-<a class="indexterm" name="id2665069"></a>
-<a class="indexterm" name="id2665076"></a>
-<a class="indexterm" name="id2665083"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2665152"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2665160"></a>
+<a class="indexterm" name="id2665167"></a>
+<a class="indexterm" name="id2665174"></a>
+<a class="indexterm" name="id2665180"></a>
+<a class="indexterm" name="id2665190"></a>
+<a class="indexterm" name="id2665196"></a>
+<a class="indexterm" name="id2665203"></a>
+<a class="indexterm" name="id2665210"></a>
 A number of UNIX systems (e.g., Sun Solaris), as well as the xxxxBSD family and Linux,
 now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, 
 authorization, and resource control services. Prior to the introduction of PAM, a decision
@@ -33,17 +33,17 @@ would require the provision of alternatives for all programs that provide securi
 Such a choice would involve provision of alternatives to programs such as <code class="literal">login</code>, 
 <code class="literal">passwd</code>, <code class="literal">chown</code>, and so on.
 </p><p>
-<a class="indexterm" name="id2665124"></a>
-<a class="indexterm" name="id2665131"></a>
-<a class="indexterm" name="id2665138"></a>
-<a class="indexterm" name="id2665145"></a>
+<a class="indexterm" name="id2665252"></a>
+<a class="indexterm" name="id2665258"></a>
+<a class="indexterm" name="id2665265"></a>
+<a class="indexterm" name="id2665272"></a>
 PAM provides a mechanism that disconnects these security programs from the underlying
 authentication/authorization infrastructure. PAM is configured by making appropriate modifications to one file,
 <code class="filename">/etc/pam.conf</code> (Solaris), or by editing individual control files that are
 located in <code class="filename">/etc/pam.d</code>.
 </p><p>
-<a class="indexterm" name="id2665171"></a>
-<a class="indexterm" name="id2665178"></a>
+<a class="indexterm" name="id2665299"></a>
+<a class="indexterm" name="id2665305"></a>
 On PAM-enabled UNIX/Linux systems, it is an easy matter to configure the system to use any
 authentication backend so long as the appropriate dynamically loadable library modules
 are available for it. The backend may be local to the system or may be centralized on a
@@ -51,94 +51,94 @@ remote server.
 </p><p>
 PAM support modules are available for:
 </p><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/passwd</code></span></dt><dd><p>
-<a class="indexterm" name="id2665208"></a>
-<a class="indexterm" name="id2665215"></a>
-<a class="indexterm" name="id2665222"></a>
-<a class="indexterm" name="id2665229"></a>
-<a class="indexterm" name="id2665236"></a>
-<a class="indexterm" name="id2665242"></a>
+<a class="indexterm" name="id2665336"></a>
+<a class="indexterm" name="id2665343"></a>
+<a class="indexterm" name="id2665349"></a>
+<a class="indexterm" name="id2665356"></a>
+<a class="indexterm" name="id2665363"></a>
+<a class="indexterm" name="id2665370"></a>
 		There are several PAM modules that interact with this standard UNIX user database. The most common are called
 		<code class="filename">pam_unix.so</code>, <code class="filename">pam_unix2.so</code>, <code class="filename">pam_pwdb.so</code> and
 		<code class="filename">pam_userdb.so</code>.
 		</p></dd><dt><span class="term">Kerberos</span></dt><dd><p>
-<a class="indexterm" name="id2665285"></a>
-<a class="indexterm" name="id2665292"></a>
-<a class="indexterm" name="id2665299"></a>
-<a class="indexterm" name="id2665305"></a>
-<a class="indexterm" name="id2665312"></a>
+<a class="indexterm" name="id2665412"></a>
+<a class="indexterm" name="id2665419"></a>
+<a class="indexterm" name="id2665426"></a>
+<a class="indexterm" name="id2665433"></a>
+<a class="indexterm" name="id2665440"></a>
 		The <code class="filename">pam_krb5.so</code> module allows the use of any Kerberos-compliant server.
 		This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially
 		Microsoft Active Directory (if enabled).
 		</p></dd><dt><span class="term">LDAP</span></dt><dd><p>
-<a class="indexterm" name="id2665338"></a>
-<a class="indexterm" name="id2665345"></a>
-<a class="indexterm" name="id2665352"></a>
-<a class="indexterm" name="id2665358"></a>
-<a class="indexterm" name="id2665365"></a>
-<a class="indexterm" name="id2665372"></a>
+<a class="indexterm" name="id2665465"></a>
+<a class="indexterm" name="id2665472"></a>
+<a class="indexterm" name="id2665479"></a>
+<a class="indexterm" name="id2665486"></a>
+<a class="indexterm" name="id2665493"></a>
+<a class="indexterm" name="id2665500"></a>
 		The <code class="filename">pam_ldap.so</code> module allows the use of any LDAP v2- or v3-compatible backend
 		server. Commonly used LDAP backend servers include OpenLDAP v2.0 and v2.1,
 		Sun ONE iDentity server, Novell eDirectory server, and Microsoft Active Directory.
 		</p></dd><dt><span class="term">NetWare Bindery</span></dt><dd><p>
-<a class="indexterm" name="id2665400"></a>
-<a class="indexterm" name="id2665406"></a>
-<a class="indexterm" name="id2665413"></a>
-<a class="indexterm" name="id2665420"></a>
+<a class="indexterm" name="id2665527"></a>
+<a class="indexterm" name="id2665534"></a>
+<a class="indexterm" name="id2665541"></a>
+<a class="indexterm" name="id2665548"></a>
 		The <code class="filename">pam_ncp_auth.so</code> module allows authentication off any bindery-enabled
 		NetWare Core Protocol-based server.
 		</p></dd><dt><span class="term">SMB Password</span></dt><dd><p>
-<a class="indexterm" name="id2665445"></a>
-<a class="indexterm" name="id2665452"></a>
-<a class="indexterm" name="id2665459"></a>
+<a class="indexterm" name="id2665573"></a>
+<a class="indexterm" name="id2665580"></a>
+<a class="indexterm" name="id2665587"></a>
 		This module, called <code class="filename">pam_smbpass.so</code>, allows user authentication of
 		the passdb backend that is configured in the Samba <code class="filename">smb.conf</code> file.
 		</p></dd><dt><span class="term">SMB Server</span></dt><dd><p>
-<a class="indexterm" name="id2665490"></a>
-<a class="indexterm" name="id2665497"></a>
+<a class="indexterm" name="id2665618"></a>
+<a class="indexterm" name="id2665624"></a>
 		The <code class="filename">pam_smb_auth.so</code> module is the original MS Windows networking authentication
 		tool. This module has been somewhat outdated by the Winbind module.
 		</p></dd><dt><span class="term">Winbind</span></dt><dd><p>
-<a class="indexterm" name="id2665522"></a>
-<a class="indexterm" name="id2665529"></a>
-<a class="indexterm" name="id2665536"></a>
-<a class="indexterm" name="id2665543"></a>
+<a class="indexterm" name="id2665650"></a>
+<a class="indexterm" name="id2665656"></a>
+<a class="indexterm" name="id2665663"></a>
+<a class="indexterm" name="id2665670"></a>
 		The <code class="filename">pam_winbind.so</code> module allows Samba to obtain authentication from any
 		MS Windows domain controller. It can just as easily be used to authenticate
 		users for access to any PAM-enabled application.
 		</p></dd><dt><span class="term">RADIUS</span></dt><dd><p>
-<a class="indexterm" name="id2665569"></a>
+<a class="indexterm" name="id2665696"></a>
 		There is a PAM RADIUS (Remote Access Dial-In User Service) authentication
 		module. In most cases, administrators need to locate the source code
 		for this tool and compile and install it themselves. RADIUS protocols are
 		used by many routers and terminal servers.
 		</p></dd></dl></div><p>
-<a class="indexterm" name="id2665589"></a>
-<a class="indexterm" name="id2665596"></a>
+<a class="indexterm" name="id2665716"></a>
+<a class="indexterm" name="id2665723"></a>
 Of the modules listed, Samba provides the <code class="filename">pam_smbpasswd.so</code> and the
 <code class="filename">pam_winbind.so</code> modules alone.
 </p><p>
-<a class="indexterm" name="id2665619"></a>
-<a class="indexterm" name="id2665626"></a>
-<a class="indexterm" name="id2665633"></a>
-<a class="indexterm" name="id2665640"></a>
+<a class="indexterm" name="id2665746"></a>
+<a class="indexterm" name="id2665753"></a>
+<a class="indexterm" name="id2665760"></a>
+<a class="indexterm" name="id2665767"></a>
 Once configured, these permit a remarkable level of flexibility in the location and use
 of distributed Samba domain controllers that can provide wide-area network bandwidth,
 efficient authentication services for PAM-capable systems. In effect, this allows the
 deployment of centrally managed and maintained distributed authentication from a
 single-user account database.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2665655"></a>Technical Discussion</h2></div></div></div><p>
-<a class="indexterm" name="id2665663"></a>
-<a class="indexterm" name="id2665670"></a>
-<a class="indexterm" name="id2665677"></a>
-<a class="indexterm" name="id2665684"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2665783"></a>Technical Discussion</h2></div></div></div><p>
+<a class="indexterm" name="id2665791"></a>
+<a class="indexterm" name="id2665797"></a>
+<a class="indexterm" name="id2665804"></a>
+<a class="indexterm" name="id2665811"></a>
 PAM is designed to provide system administrators with a great deal of flexibility in
 configuration of the privilege-granting applications of their system. The local
 configuration of system security controlled by PAM is contained in one of two places:
 either the single system file <code class="filename">/etc/pam.conf</code> or the
 <code class="filename">/etc/pam.d/</code> directory.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2665709"></a>PAM Configuration Syntax</h3></div></div></div><p>
-<a class="indexterm" name="id2665717"></a>
-<a class="indexterm" name="id2665724"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2665836"></a>PAM Configuration Syntax</h3></div></div></div><p>
+<a class="indexterm" name="id2665844"></a>
+<a class="indexterm" name="id2665851"></a>
 In this section we discuss the correct syntax of and generic options respected by entries to these files.
 PAM-specific tokens in the configuration file are case insensitive. The module paths, however, are case
 sensitive, since they indicate a file's name and reflect the case dependence of typical file systems.  The
@@ -148,8 +148,8 @@ In addition to the lines described below, there are two special characters provi
 of the system administrator: comments are preceded by a &#8220;<span class="quote">#</span>&#8221; and extend to the next end-of-line; also,
 module specification lines may be extended with a &#8220;<span class="quote">\</span>&#8221;-escaped newline. 
 </p><p>
-<a class="indexterm" name="id2665755"></a>
-<a class="indexterm" name="id2665762"></a>
+<a class="indexterm" name="id2665883"></a>
+<a class="indexterm" name="id2665890"></a>
 If the PAM authentication module (loadable link library file) is located in the
 default location, then it is not necessary to specify the path. In the case of
 Linux, the default location is <code class="filename">/lib/security</code>. If the module
@@ -157,12 +157,12 @@ is located outside the default, then the path must be specified as:
 </p><pre class="programlisting">
 auth  required  /other_path/pam_strange_module.so
 </pre><p>
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2665788"></a>Anatomy of <code class="filename">/etc/pam.d</code> Entries</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2665915"></a>Anatomy of <code class="filename">/etc/pam.d</code> Entries</h4></div></div></div><p>
 The remaining information in this subsection was taken from the documentation of the Linux-PAM
 project. For more information on PAM, see 
 <a class="ulink" href="http://ftp.kernel.org/pub/linux/libs/pam/" target="_top">the Official Linux-PAM home page</a>.
 </p><p>
-<a class="indexterm" name="id2665814"></a>
+<a class="indexterm" name="id2665941"></a>
 A general configuration line of the <code class="filename">/etc/pam.conf</code> file has the following form:
 </p><pre class="programlisting">
 service-name   module-type   control-flag   module-path   args
@@ -172,9 +172,9 @@ We explain the meaning of each of these tokens. The second (and more recently ad
 way of configuring Linux-PAM is via the contents of the <code class="filename">/etc/pam.d/</code> directory.
 Once we have explained the meaning of the tokens, we describe this method.
 </p><div class="variablelist"><dl><dt><span class="term">service-name</span></dt><dd><p>
-<a class="indexterm" name="id2665859"></a>
-<a class="indexterm" name="id2665866"></a>
-<a class="indexterm" name="id2665873"></a>
+<a class="indexterm" name="id2665986"></a>
+<a class="indexterm" name="id2665993"></a>
+<a class="indexterm" name="id2666000"></a>
 		The name of the service associated with this entry. Frequently, the service-name is the conventional
 		name of the given application  for example, <code class="literal">ftpd</code>, <code class="literal">rlogind</code> and
 		<code class="literal">su</code>, and so on.
@@ -186,28 +186,28 @@ Once we have explained the meaning of the tokens, we describe this method.
 		</p></dd><dt><span class="term">module-type</span></dt><dd><p>
 		One of (currently) four types of module. The four types are as follows:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2665941"></a>
-<a class="indexterm" name="id2665947"></a>
+<a class="indexterm" name="id2666068"></a>
+<a class="indexterm" name="id2666075"></a>
 			<em class="parameter"><code>auth:</code></em> This module type provides two aspects of authenticating the user.
 			It establishes that the user is who he or she claims to be by instructing the application
 			to prompt the user for a password or other means of identification. Second, the module can
 			grant group membership (independently of the <code class="filename">/etc/groups</code> file)
 			or other privileges through its credential-granting properties.
 			</p></li><li><p>
-<a class="indexterm" name="id2665977"></a>
-<a class="indexterm" name="id2665983"></a>
+<a class="indexterm" name="id2666104"></a>
+<a class="indexterm" name="id2666111"></a>
 			<em class="parameter"><code>account:</code></em> This module performs non-authentication-based account management.
 			It is typically used to restrict/permit access to a service based on the time of day, currently
 		 	available system resources (maximum number of users), or perhaps the location of the user 
 			login. For example, the &#8220;<span class="quote">root</span>&#8221; login may be permitted only on the console.
 			</p></li><li><p>
-<a class="indexterm" name="id2666010"></a>
+<a class="indexterm" name="id2666138"></a>
 			<em class="parameter"><code>session:</code></em> Primarily, this module is associated with doing things that need
 			to be done for the user before and after he or she can be given service. Such things include logging
 			information concerning the opening and closing of some data exchange with a user, mounting
 			directories, and so on.
 			</p></li><li><p>
-<a class="indexterm" name="id2666032"></a>
+<a class="indexterm" name="id2666159"></a>
 			<em class="parameter"><code>password:</code></em> This last module type is required for updating the authentication
 			token associated with the user. Typically, there is one module for each
 			&#8220;<span class="quote">challenge/response</span>&#8221; authentication <em class="parameter"><code>(auth)</code></em> module type.
@@ -221,10 +221,10 @@ Once we have explained the meaning of the tokens, we describe this method.
 		<code class="filename">/etc/pam.conf</code> file; earlier entries are executed before later ones.
 		As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes.
 		</p><p>
-<a class="indexterm" name="id2666096"></a>
-<a class="indexterm" name="id2666103"></a>
-<a class="indexterm" name="id2666110"></a>
-<a class="indexterm" name="id2666117"></a>
+<a class="indexterm" name="id2666224"></a>
+<a class="indexterm" name="id2666231"></a>
+<a class="indexterm" name="id2666238"></a>
+<a class="indexterm" name="id2666244"></a>
 		The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the
 		severity of concern associated with the success or failure of a specific module. There are four such
 		keywords: <em class="parameter"><code>required</code></em>, <em class="parameter"><code>requisite</code></em>,
@@ -350,13 +350,13 @@ user_name=&#8220;<span class="quote">%u</span>&#8221; and password=PASSWORD(&#82
 		Any line in one of the configuration files that is not formatted correctly will generally tend (erring on the
 		side of caution) to make the authentication process fail. A corresponding error is written to the system log files
 		with a call to syslog(3). 
-		</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2666709"></a>Example System Configurations</h3></div></div></div><p>
+		</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2666843"></a>Example System Configurations</h3></div></div></div><p>
 The following is an example <code class="filename">/etc/pam.d/login</code> configuration file. 
 This example had all options uncommented and is probably not usable 
 because it stacks many conditions before allowing successful completion 
 of the login process. Essentially, all conditions can be disabled 
 by commenting them out, except the calls to <code class="filename">pam_pwdb.so</code>.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2666735"></a>PAM: Original Login Config</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2666869"></a>PAM: Original Login Config</h4></div></div></div><p>
 	</p><pre class="programlisting">
 #%PAM-1.0
 # The PAM configuration file for the &#8220;<span class="quote">login</span>&#8221; service
@@ -373,7 +373,7 @@ session      required    pam_pwdb.so
 # password   required    pam_cracklib.so retry=3
 password     required    pam_pwdb.so shadow md5
 </pre><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2666763"></a>PAM: Login Using <code class="filename">pam_smbpass</code></h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2666897"></a>PAM: Login Using <code class="filename">pam_smbpass</code></h4></div></div></div><p>
 PAM allows use of replaceable modules. Those available on a sample system include:
 </p><p><code class="prompt">$</code><strong class="userinput"><code>/bin/ls /lib/security</code></strong>
 </p><pre class="programlisting">
@@ -456,7 +456,7 @@ authentication to be configured in a single central file. The
 on the basis that it allows for easier administration. As with all issues in 
 life, though, every decision has trade-offs, so you may want to examine the 
 PAM documentation for further helpful information.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667015"></a><code class="filename">smb.conf</code> PAM Configuration</h3></div></div></div><p>
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667149"></a><code class="filename">smb.conf</code> PAM Configuration</h3></div></div></div><p>
 There is an option in <code class="filename">smb.conf</code> called <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a>.
 The following is from the online help for this option in SWAT:
 </p><div class="blockquote"><blockquote class="blockquote"><p>
@@ -466,7 +466,7 @@ is to use PAM for clear-text authentication only and to ignore any account or se
 ignores PAM for authentication in the case of <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>. 
 The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB 
 password encryption. 
-</p><p>Default: <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions = no</a></p></blockquote></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667096"></a>Remote CIFS Authentication Using <code class="filename">winbindd.so</code></h3></div></div></div><p>
+</p><p>Default: <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions = no</a></p></blockquote></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667230"></a>Remote CIFS Authentication Using <code class="filename">winbindd.so</code></h3></div></div></div><p>
 All operating systems depend on the provision of user credentials acceptable to the platform.
 UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID).
 These are both simple integer numbers that are obtained from a password backend such
@@ -493,7 +493,7 @@ the reduction of wide-area network authentication traffic.
 The RID to UNIX ID database is the only location where the user and group  mappings are 
 stored by <code class="literal">winbindd</code>. If this file is deleted or corrupted, there is no way for <code class="literal">winbindd</code>
 to determine which user and group IDs correspond to Windows NT user and group RIDs.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667199"></a>Password Synchronization Using <code class="filename">pam_smbpass.so</code></h3></div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667333"></a>Password Synchronization Using <code class="filename">pam_smbpass.so</code></h3></div></div></div><p>
 <code class="filename">pam_smbpass</code> is a PAM module that can be used on conforming systems to
 keep the <code class="filename">smbpasswd</code> (Samba password) database in sync with the UNIX
 password file. PAM is an API supported
@@ -511,7 +511,7 @@ Options recognized by this module are shown in <a class="link" href="pam.html#sm
 The following are examples of the use of <code class="filename">pam_smbpass.so</code> in the format of the Linux
 <code class="filename">/etc/pam.d/</code> files structure. Those wishing to implement this
 tool on other platforms will need to adapt this appropriately.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667418"></a>Password Synchronization Configuration</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667552"></a>Password Synchronization Configuration</h4></div></div></div><p>
 The following is a sample PAM configuration that shows the use of pam_smbpass to make
 sure <code class="filename">private/smbpasswd</code> is kept in sync when <code class="filename">/etc/passwd (/etc/shadow)</code>
 is changed. It is useful when an expired password might be changed by an
@@ -528,7 +528,7 @@ password   requisite    pam_cracklib.so retry=3
 password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
 password   required     pam_smbpass.so nullok use_authtok try_first_pass
 session    required     pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667464"></a>Password Migration Configuration</h4></div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667598"></a>Password Migration Configuration</h4></div></div></div><p>
 The following PAM configuration shows the use of <code class="filename">pam_smbpass</code> to migrate
 from plaintext to encrypted passwords for Samba. Unlike other methods,
 this can be used for users who have never connected to Samba shares:
@@ -548,7 +548,7 @@ password   requisite   pam_cracklib.so retry=3
 password   requisite   pam_unix.so shadow md5 use_authtok try_first_pass
 password   optional    pam_smbpass.so nullok use_authtok try_first_pass
 session    required    pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667512"></a>Mature Password Configuration</h4></div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667646"></a>Mature Password Configuration</h4></div></div></div><p>
 The following is a sample PAM configuration for a mature <code class="filename">smbpasswd</code> installation.
 <code class="filename">private/smbpasswd</code> is fully populated, and we consider it an error if
 the SMB password does not exist or does not match the UNIX password.
@@ -564,7 +564,7 @@ password   requisite    pam_cracklib.so retry=3
 password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
 password   required     pam_smbpass.so use_authtok use_first_pass
 session    required     pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667552"></a>Kerberos Password Integration Configuration</h4></div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2667686"></a>Kerberos Password Integration Configuration</h4></div></div></div><p>
 The following is a sample PAM configuration that shows <em class="parameter"><code>pam_smbpass</code></em> used together with
 <em class="parameter"><code>pam_krb5</code></em>. This could be useful on a Samba PDC that is also a member of
 a Kerberos realm.
@@ -581,10 +581,10 @@ password   requisite   pam_cracklib.so retry=3
 password   optional    pam_smbpass.so nullok use_authtok try_first_pass
 password   required    pam_krb5.so use_authtok try_first_pass
 session    required    pam_krb5.so
-</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667593"></a>Common Errors</h2></div></div></div><p>
+</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667727"></a>Common Errors</h2></div></div></div><p>
 PAM can be fickle and sensitive to configuration glitches. Here we look at a few cases from
 the Samba mailing list.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667604"></a>pam_winbind Problem</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667738"></a>pam_winbind Problem</h3></div></div></div><p>
 	A user reported, <span class="emphasis"><em>I have the following PAM configuration</em></span>:
 	</p><p>
 </p><pre class="programlisting">
@@ -608,7 +608,7 @@ password required /lib/security/pam_stack.so service=system-auth
 	<code class="filename">/etc/pam.d/system-auth</code> and copy only what you need from it into your
 	<code class="filename">/etc/pam.d/login</code> file. Alternatively, if you want all services to use
 	Winbind, you can put the Winbind-specific stuff in <code class="filename">/etc/pam.d/system-auth</code>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667702"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2667836"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>
 	&#8220;<span class="quote">
 	My <code class="filename">smb.conf</code> file is correctly configured. I have specified 
 	<a class="link" href="smb.conf.5.html#IDMAPUID" target="_top">idmap uid = 12000</a> 
diff --git a/docs/htmldocs/Samba3-HOWTO/passdb.html b/docs/htmldocs/Samba3-HOWTO/passdb.html
index ccade68a35..fbe1d775f1 100644
--- a/docs/htmldocs/Samba3-HOWTO/passdb.html
+++ b/docs/htmldocs/Samba3-HOWTO/passdb.html
@@ -1,18 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter�11.�Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="orgname">IDEALX</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id2587269">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587489">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588057">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589125">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589979">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592519">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592573">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592915">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593073">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595597">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595603">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595641">Configuration of auth methods</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2587072"></a>
-<a class="indexterm" name="id2587079"></a>
-<a class="indexterm" name="id2587086"></a>
-<a class="indexterm" name="id2587092"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�11.�Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�11.�Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter�11.�Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="orgname">IDEALX</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id2587230">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587266">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587457">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588025">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588545">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589094">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589506">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589947">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592500">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592553">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592629">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592895">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593053">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595578">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595583">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595621">Configuration of auth methods</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2587032"></a>
+<a class="indexterm" name="id2587039"></a>
+<a class="indexterm" name="id2587046"></a>
+<a class="indexterm" name="id2587053"></a>
 Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This
 capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to
 work with only one specified passwd backend.
 </p><p>
-<a class="indexterm" name="id2587107"></a>
-<a class="indexterm" name="id2587114"></a>
-<a class="indexterm" name="id2587120"></a>
-<a class="indexterm" name="id2587127"></a>
-<a class="indexterm" name="id2587134"></a>
-<a class="indexterm" name="id2587141"></a>
+<a class="indexterm" name="id2587067"></a>
+<a class="indexterm" name="id2587074"></a>
+<a class="indexterm" name="id2587081"></a>
+<a class="indexterm" name="id2587088"></a>
+<a class="indexterm" name="id2587095"></a>
+<a class="indexterm" name="id2587102"></a>
 The three passdb backends that are fully maintained (actively supported) by the Samba Team are:
 <code class="literal">smbpasswd</code> (being obsoleted), <code class="literal">tdbsam</code> (a tdb-based binary file format),
 and <code class="literal">ldapsam</code> (LDAP directory).  Of these, only the <code class="literal">ldapsam</code> backend
@@ -23,30 +23,30 @@ In a strict sense, there are three supported account storage and access systems.
 obsolete (smbpasswd). It is recommended to use the <code class="literal">tdbsam</code> method for all simple systems. Use
 <code class="literal">ldapsam</code> for larger and more complex networks.
 </p><p>
-<a class="indexterm" name="id2587211"></a>
-<a class="indexterm" name="id2587218"></a>
-<a class="indexterm" name="id2587225"></a>
-<a class="indexterm" name="id2587232"></a>
-<a class="indexterm" name="id2587239"></a>
-<a class="indexterm" name="id2587246"></a>
-<a class="indexterm" name="id2587253"></a>
+<a class="indexterm" name="id2587172"></a>
+<a class="indexterm" name="id2587179"></a>
+<a class="indexterm" name="id2587186"></a>
+<a class="indexterm" name="id2587193"></a>
+<a class="indexterm" name="id2587200"></a>
+<a class="indexterm" name="id2587207"></a>
+<a class="indexterm" name="id2587214"></a>
 In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice
 of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the
 nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms,
 machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like
 entities.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2587269"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2587230"></a>Features and Benefits</h2></div></div></div><p>
 Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality
 as follows:
-<a class="indexterm" name="id2587279"></a>
-<a class="indexterm" name="id2587288"></a>
-<a class="indexterm" name="id2587298"></a>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2587306"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p>
-<a class="indexterm" name="id2587323"></a>
-<a class="indexterm" name="id2587330"></a>
-<a class="indexterm" name="id2587337"></a>
-<a class="indexterm" name="id2587343"></a>
-<a class="indexterm" name="id2587350"></a>
+<a class="indexterm" name="id2587240"></a>
+<a class="indexterm" name="id2587249"></a>
+<a class="indexterm" name="id2587258"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2587266"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p>
+<a class="indexterm" name="id2587283"></a>
+<a class="indexterm" name="id2587290"></a>
+<a class="indexterm" name="id2587297"></a>
+<a class="indexterm" name="id2587304"></a>
+<a class="indexterm" name="id2587311"></a>
 			This isn't really a backend at all, but is listed here for simplicity.  Samba can be configured to pass
 			plaintext authentication requests to the traditional UNIX/Linux <code class="filename">/etc/passwd</code> and
 			<code class="filename">/etc/shadow</code>-style subsystems.  On systems that have Pluggable Authentication Modules
@@ -54,10 +54,10 @@ as follows:
 			protocol limitations imposed by MS Windows clients apply likewise. Please refer to <a class="link" href="passdb.html#passdbtech" title="Technical Information">Technical Information</a>, for more information regarding the limitations of plaintext
 			password usage.
 			</p></dd><dt><span class="term">smbpasswd</span></dt><dd><p>
-<a class="indexterm" name="id2587397"></a>
-<a class="indexterm" name="id2587404"></a>
-<a class="indexterm" name="id2587411"></a>
-<a class="indexterm" name="id2587418"></a>
+<a class="indexterm" name="id2587358"></a>
+<a class="indexterm" name="id2587365"></a>
+<a class="indexterm" name="id2587372"></a>
+<a class="indexterm" name="id2587379"></a>
 			This option allows continued use of the <code class="filename">smbpasswd</code>
 			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
@@ -69,32 +69,32 @@ as follows:
 			This backend should be used only for backward 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>
-<a class="indexterm" name="id2587457"></a>
-<a class="indexterm" name="id2587464"></a>
-<a class="indexterm" name="id2587471"></a>
+<a class="indexterm" name="id2587425"></a>
+<a class="indexterm" name="id2587432"></a>
+<a class="indexterm" name="id2587439"></a>
 			There is a password backend option that allows continued operation with
 			an 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. 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="id2587489"></a>New Account Storage Systems</h3></div></div></div><p>
+			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2587457"></a>New Account Storage Systems</h3></div></div></div><p>
 Samba-3 introduces a number of new password backend capabilities.
-<a class="indexterm" name="id2587498"></a>
-<a class="indexterm" name="id2587507"></a>
+<a class="indexterm" name="id2587466"></a>
+<a class="indexterm" name="id2587475"></a>
 </p><div class="variablelist"><dl><dt><span class="term">tdbsam</span></dt><dd><p>
-<a class="indexterm" name="id2587528"></a>
-<a class="indexterm" name="id2587536"></a>
-<a class="indexterm" name="id2587542"></a>
+<a class="indexterm" name="id2587496"></a>
+<a class="indexterm" name="id2587504"></a>
+<a class="indexterm" name="id2587510"></a>
 			This backend provides a rich database backend for local servers. This
 			backend is not suitable for multiple domain controllers (i.e., PDC + one
 			or more BDC) installations.
 			</p><p>
-<a class="indexterm" name="id2587555"></a>
-<a class="indexterm" name="id2587562"></a>
-<a class="indexterm" name="id2587569"></a>
-<a class="indexterm" name="id2587576"></a>
-<a class="indexterm" name="id2587583"></a>
-<a class="indexterm" name="id2587590"></a>
+<a class="indexterm" name="id2587523"></a>
+<a class="indexterm" name="id2587530"></a>
+<a class="indexterm" name="id2587537"></a>
+<a class="indexterm" name="id2587544"></a>
+<a class="indexterm" name="id2587551"></a>
+<a class="indexterm" name="id2587558"></a>
 			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.
@@ -102,63 +102,63 @@ Samba-3 introduces a number of new password backend capabilities.
 			to implement the same account and system access controls that are possible
 			with MS Windows NT4/200x-based systems.
 			</p><p>
-<a class="indexterm" name="id2587613"></a>
-<a class="indexterm" name="id2587620"></a>
-<a class="indexterm" name="id2587627"></a>
+<a class="indexterm" name="id2587581"></a>
+<a class="indexterm" name="id2587588"></a>
+<a class="indexterm" name="id2587595"></a>
 			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>
-<a class="indexterm" name="id2587656"></a>
-<a class="indexterm" name="id2587663"></a>
+<a class="indexterm" name="id2587624"></a>
+<a class="indexterm" name="id2587631"></a>
 			This provides a rich directory backend for distributed account installation.
 			</p><p>
-<a class="indexterm" name="id2587674"></a>
-<a class="indexterm" name="id2587681"></a>
-<a class="indexterm" name="id2587688"></a>
-<a class="indexterm" name="id2587695"></a>
-<a class="indexterm" name="id2587702"></a>
+<a class="indexterm" name="id2587642"></a>
+<a class="indexterm" name="id2587649"></a>
+<a class="indexterm" name="id2587656"></a>
+<a class="indexterm" name="id2587663"></a>
+<a class="indexterm" name="id2587670"></a>
 			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 <code class="filename">examples/LDAP</code> directory of the Samba distribution.
 			</p><p>
-<a class="indexterm" name="id2587724"></a>
-<a class="indexterm" name="id2587731"></a>
-<a class="indexterm" name="id2587738"></a>
-<a class="indexterm" name="id2587745"></a>
-<a class="indexterm" name="id2587752"></a>
+<a class="indexterm" name="id2587692"></a>
+<a class="indexterm" name="id2587699"></a>
+<a class="indexterm" name="id2587706"></a>
+<a class="indexterm" name="id2587713"></a>
+<a class="indexterm" name="id2587720"></a>
 			The new LDAP implementation significantly expands the control abilities that
 			were possible with prior versions of Samba. It is now possible to specify
 			&#8220;<span class="quote">per-user</span>&#8221; 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 greater scalability.
 			</p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="passdbtech"></a>Technical Information</h2></div></div></div><p>
-<a class="indexterm" name="id2587786"></a>
-<a class="indexterm" name="id2587793"></a>
+<a class="indexterm" name="id2587754"></a>
+<a class="indexterm" name="id2587761"></a>
 	Old Windows clients send plaintext passwords over the wire. Samba can check these
 	passwords by encrypting them and comparing them to the hash stored in the UNIX user database.
 	</p><p>
-<a class="indexterm" name="id2587806"></a>
-<a class="indexterm" name="id2587813"></a>
-<a class="indexterm" name="id2587820"></a>
-<a class="indexterm" name="id2587827"></a>
+<a class="indexterm" name="id2587774"></a>
+<a class="indexterm" name="id2587781"></a>
+<a class="indexterm" name="id2587788"></a>
+<a class="indexterm" name="id2587795"></a>
 	Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over
 	the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless
 	their registry is tweaked.
 	</p><p>
-<a class="indexterm" name="id2587841"></a>
-<a class="indexterm" name="id2587848"></a>
+<a class="indexterm" name="id2587809"></a>
+<a class="indexterm" name="id2587816"></a>
 	Many people ask why Samba cannot simply use the UNIX password database. Windows requires
 	passwords that are encrypted in its own format.  The UNIX passwords can't be converted to
-	Windows-style encrypted passwords. Because of that, you can't use the standard UNIX user
+	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>
-<a class="indexterm" name="id2587864"></a>
-<a class="indexterm" name="id2587872"></a>
-<a class="indexterm" name="id2587878"></a>
-<a class="indexterm" name="id2587885"></a>
+<a class="indexterm" name="id2587832"></a>
+<a class="indexterm" name="id2587840"></a>
+<a class="indexterm" name="id2587846"></a>
+<a class="indexterm" name="id2587853"></a>
 	In addition to differently encrypted passwords, Windows also stores certain data for each
 	user that is not stored in a UNIX user database: for example, workstations the user may logon from,
 	the location where the user's profile is stored, and so on. Samba retrieves and stores this
@@ -166,18 +166,18 @@ Samba-3 introduces a number of new password backend capabilities.
 	tdbsam, and plain text file. For more information, see the man page for <code class="filename">smb.conf</code> regarding the
 	<a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> parameter.
 	</p><div class="figure"><a name="idmap-sid2uid"></a><p class="title"><b>Figure�11.1.�IDMAP: Resolution of SIDs to UIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2uid.png" width="216" alt="IDMAP: Resolution of SIDs to UIDs."></div></div></div><br class="figure-break"><p>
-	<a class="indexterm" name="id2587975"></a>
-<a class="indexterm" name="id2587981"></a>
-<a class="indexterm" name="id2587988"></a>
+	<a class="indexterm" name="id2587943"></a>
+<a class="indexterm" name="id2587949"></a>
+<a class="indexterm" name="id2587956"></a>
 	The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd
 	is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a class="link" href="passdb.html#idmap-sid2uid" title="Figure�11.1.�IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <a class="link" href="passdb.html#idmap-uid2sid" title="Figure�11.2.�IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs
 	to SIDs</a> diagrams.
-	</p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure�11.2.�IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588057"></a>Important Notes About Security</h3></div></div></div><p>
-<a class="indexterm" name="id2588065"></a>
-<a class="indexterm" name="id2588072"></a>
-<a class="indexterm" name="id2588080"></a>
-<a class="indexterm" name="id2588087"></a>
-<a class="indexterm" name="id2588093"></a>
+	</p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure�11.2.�IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588025"></a>Important Notes About Security</h3></div></div></div><p>
+<a class="indexterm" name="id2588033"></a>
+<a class="indexterm" name="id2588040"></a>
+<a class="indexterm" name="id2588048"></a>
+<a class="indexterm" name="id2588055"></a>
+<a class="indexterm" name="id2588061"></a>
 		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
@@ -191,217 +191,217 @@ Samba-3 introduces a number of new password backend capabilities.
 		passwords of all your users. Its contents must be kept secret, and the file should
 		be protected accordingly.
 		</p><p>
-<a class="indexterm" name="id2588123"></a>
-<a class="indexterm" name="id2588129"></a>
-<a class="indexterm" name="id2588136"></a>
+<a class="indexterm" name="id2588091"></a>
+<a class="indexterm" name="id2588097"></a>
+<a class="indexterm" name="id2588104"></a>
 		Ideally, we would like a password scheme that involves neither plaintext passwords
 		on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with
 		having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).
 		</p><p>
-<a class="indexterm" name="id2588151"></a>
-<a class="indexterm" name="id2588158"></a>
+<a class="indexterm" name="id2588119"></a>
+<a class="indexterm" name="id2588126"></a>
 		Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords
 		are disabled from being sent over the wire. This mandates either the use of encrypted
 		password support or editing the Windows NT registry to re-enable plaintext passwords.
 		</p><p>
-<a class="indexterm" name="id2588173"></a>
-<a class="indexterm" name="id2588180"></a>
+<a class="indexterm" name="id2588141"></a>
+<a class="indexterm" name="id2588148"></a>
 		The following versions of Microsoft 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 [Second Edition].</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>
-<a class="indexterm" name="id2588218"></a>
-<a class="indexterm" name="id2588225"></a>
-<a class="indexterm" name="id2588232"></a>
+<a class="indexterm" name="id2588186"></a>
+<a class="indexterm" name="id2588193"></a>
+<a class="indexterm" name="id2588200"></a>
  		MS Windows XP Home does not have facilities to become a domain member, and it cannot 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>
-<a class="indexterm" name="id2588277"></a>
-<a class="indexterm" name="id2588284"></a>
-<a class="indexterm" name="id2588291"></a>
-<a class="indexterm" name="id2588298"></a>
-<a class="indexterm" name="id2588305"></a>
-<a class="indexterm" name="id2588312"></a>
+<a class="indexterm" name="id2588245"></a>
+<a class="indexterm" name="id2588252"></a>
+<a class="indexterm" name="id2588259"></a>
+<a class="indexterm" name="id2588266"></a>
+<a class="indexterm" name="id2588273"></a>
+<a class="indexterm" name="id2588280"></a>
 		All current releases 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 plaintext or encrypted password
 		handling.
 		</p><p>
-<a class="indexterm" name="id2588328"></a>
-<a class="indexterm" name="id2588335"></a>
-<a class="indexterm" name="id2588342"></a>
-<a class="indexterm" name="id2588349"></a>
-<a class="indexterm" name="id2588356"></a>
+<a class="indexterm" name="id2588296"></a>
+<a class="indexterm" name="id2588303"></a>
+<a class="indexterm" name="id2588310"></a>
+<a class="indexterm" name="id2588317"></a>
+<a class="indexterm" name="id2588324"></a>
 		MS Windows clients will cache the encrypted password alone. Where plaintext passwords
 		are re-enabled through the appropriate registry change, the plaintext 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
 		effect an auto-reconnect. If the resource server does not support encrypted passwords, the
 		auto-reconnect will fail. Use of encrypted passwords is strongly advised.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2588373"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2588384"></a>
-<a class="indexterm" name="id2588391"></a>
-<a class="indexterm" name="id2588398"></a>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2588340"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+<a class="indexterm" name="id2588352"></a>
+<a class="indexterm" name="id2588359"></a>
+<a class="indexterm" name="id2588366"></a>
 				Plaintext 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>
-<a class="indexterm" name="id2588412"></a>
-<a class="indexterm" name="id2588419"></a>
-<a class="indexterm" name="id2588425"></a>
+<a class="indexterm" name="id2588380"></a>
+<a class="indexterm" name="id2588386"></a>
+<a class="indexterm" name="id2588393"></a>
 				Plaintext passwords are not stored anywhere in memory or on disk.
 				</p></li><li><p>
-<a class="indexterm" name="id2588438"></a>
-<a class="indexterm" name="id2588445"></a>
-<a class="indexterm" name="id2588452"></a>
-<a class="indexterm" name="id2588459"></a>
+<a class="indexterm" name="id2588406"></a>
+<a class="indexterm" name="id2588413"></a>
+<a class="indexterm" name="id2588420"></a>
+<a class="indexterm" name="id2588426"></a>
 				Windows NT does not 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 thing you can do to stop this is to use SMB
 				encryption.
 				</p></li><li><p>
-<a class="indexterm" name="id2588476"></a>
-<a class="indexterm" name="id2588483"></a>
+<a class="indexterm" name="id2588444"></a>
+<a class="indexterm" name="id2588451"></a>
 				Encrypted password support allows automatic share (resource) reconnects.
 				</p></li><li><p>
-<a class="indexterm" name="id2588496"></a>
-<a class="indexterm" name="id2588502"></a>
+<a class="indexterm" name="id2588464"></a>
+<a class="indexterm" name="id2588470"></a>
 				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="id2588513"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2588525"></a>
+				</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2588481"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+<a class="indexterm" name="id2588492"></a>
 				Plaintext passwords are not kept on disk and are not cached in memory.
 				</p></li><li><p>
-<a class="indexterm" name="id2588537"></a>
-<a class="indexterm" name="id2588544"></a>
+<a class="indexterm" name="id2588505"></a>
+<a class="indexterm" name="id2588512"></a>
 				Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.
 				</p></li><li><p>
-<a class="indexterm" name="id2588557"></a>
-<a class="indexterm" name="id2588564"></a>
+<a class="indexterm" name="id2588525"></a>
+<a class="indexterm" name="id2588531"></a>
 				Use of other services (such as Telnet and FTP) that send plaintext passwords over
 				the network makes sending them for SMB not 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="id2588577"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p>
-<a class="indexterm" name="id2588586"></a>
-<a class="indexterm" name="id2588592"></a>
-<a class="indexterm" name="id2588599"></a>
+				</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588545"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p>
+<a class="indexterm" name="id2588553"></a>
+<a class="indexterm" name="id2588560"></a>
+<a class="indexterm" name="id2588566"></a>
 	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>
-<a class="indexterm" name="id2588612"></a>
-<a class="indexterm" name="id2588619"></a>
-<a class="indexterm" name="id2588626"></a>
-<a class="indexterm" name="id2588632"></a>
-<a class="indexterm" name="id2588640"></a>
+<a class="indexterm" name="id2588580"></a>
+<a class="indexterm" name="id2588587"></a>
+<a class="indexterm" name="id2588594"></a>
+<a class="indexterm" name="id2588600"></a>
+<a class="indexterm" name="id2588607"></a>
 	First, all Samba SAM 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="link" href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a>
 	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>
-	<a class="indexterm" name="id2588668"></a>
-	<a class="indexterm" name="id2588675"></a>
-	<a class="indexterm" name="id2588681"></a>
-	<a class="indexterm" name="id2588687"></a>
-	<a class="indexterm" name="id2588694"></a>
-	<a class="indexterm" name="id2588701"></a>
-	<a class="indexterm" name="id2588708"></a>
+	<a class="indexterm" name="id2588636"></a>
+	<a class="indexterm" name="id2588643"></a>
+	<a class="indexterm" name="id2588649"></a>
+	<a class="indexterm" name="id2588656"></a>
+	<a class="indexterm" name="id2588662"></a>
+	<a class="indexterm" name="id2588669"></a>
+	<a class="indexterm" name="id2588676"></a>
 	The second way to map Windows SID to UNIX UID is via the <span class="emphasis"><em>idmap uid</em></span> and
 	<span class="emphasis"><em>idmap gid</em></span> parameters in <code class="filename">smb.conf</code>.  Please refer to the man page for information about
 	these parameters.  These parameters are essential when mapping users from a remote (non-member Windows client
 	or a member of a foreign domain) 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><p>
-<a class="indexterm" name="id2588747"></a>
-<a class="indexterm" name="id2588754"></a>
-<a class="indexterm" name="id2588760"></a>
-<a class="indexterm" name="id2588767"></a>
-<a class="indexterm" name="id2588774"></a>
-<a class="indexterm" name="id2588780"></a>
+<a class="indexterm" name="id2588716"></a>
+<a class="indexterm" name="id2588722"></a>
+<a class="indexterm" name="id2588729"></a>
+<a class="indexterm" name="id2588735"></a>
+<a class="indexterm" name="id2588742"></a>
+<a class="indexterm" name="id2588749"></a>
 	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 (e.g., NFS) and where
 	users are copying files across UNIX/Linux systems using tools such as <code class="literal">rsync</code>.
 	</p><p>
-<a class="indexterm" name="id2588804"></a>
-<a class="indexterm" name="id2588810"></a>
-<a class="indexterm" name="id2588817"></a>
-<a class="indexterm" name="id2588823"></a>
-<a class="indexterm" name="id2588830"></a>
-<a class="indexterm" name="id2588837"></a>
-<a class="indexterm" name="id2588844"></a>
-	<a class="indexterm" name="id2588850"></a>
+<a class="indexterm" name="id2588772"></a>
+<a class="indexterm" name="id2588779"></a>
+<a class="indexterm" name="id2588786"></a>
+<a class="indexterm" name="id2588792"></a>
+<a class="indexterm" name="id2588799"></a>
+<a class="indexterm" name="id2588805"></a>
+<a class="indexterm" name="id2588812"></a>
+	<a class="indexterm" name="id2588819"></a>
 	The special facility is enabled using a parameter called <em class="parameter"><code>idmap backend</code></em>.
 	The default setting for this parameter is an empty string. Technically it is possible to use
 	an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for
 	network configurations that also use LDAP for the SAM backend.
 	<a class="link" href="passdb.html#idmapbackendexample" title="Example�11.1.�Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a>
 	shows that configuration.
-	</p><a class="indexterm" name="id2588880"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example�11.1.�Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2588913"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id2588929"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2588945"></a>
-<a class="indexterm" name="id2588952"></a>
+	</p><a class="indexterm" name="id2588848"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example�11.1.�Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2588882"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id2588898"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2588914"></a>
+<a class="indexterm" name="id2588920"></a>
 	A network administrator who wants to make significant use of LDAP backends will sooner or later be
 	exposed to the excellent work done by PADL Software. PADL <a class="ulink" href="http://www.padl.com" target="_top">http://www.padl.com</a> have
 	produced and released to open source an array of tools that might be of interest. These tools include:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2588976"></a>
-<a class="indexterm" name="id2588982"></a>
-<a class="indexterm" name="id2588989"></a>
-<a class="indexterm" name="id2588996"></a>
-<a class="indexterm" name="id2589003"></a>
-<a class="indexterm" name="id2589009"></a>
-<a class="indexterm" name="id2589016"></a>
-<a class="indexterm" name="id2589023"></a>
+<a class="indexterm" name="id2588944"></a>
+<a class="indexterm" name="id2588951"></a>
+<a class="indexterm" name="id2588958"></a>
+<a class="indexterm" name="id2588964"></a>
+<a class="indexterm" name="id2588971"></a>
+<a class="indexterm" name="id2588978"></a>
+<a class="indexterm" name="id2588985"></a>
+<a class="indexterm" name="id2588991"></a>
 		<span class="emphasis"><em>nss_ldap:</em></span> An LDAP name service switch (NSS) module to provide native
 		name service support for AIX, Linux, Solaris, and other operating systems. This tool
 		can be used for centralized storage and retrieval of UIDs and GIDs.
 		</p></li><li><p>
-<a class="indexterm" name="id2589043"></a>
-<a class="indexterm" name="id2589050"></a>
-<a class="indexterm" name="id2589056"></a>
-<a class="indexterm" name="id2589063"></a>
+<a class="indexterm" name="id2589012"></a>
+<a class="indexterm" name="id2589018"></a>
+<a class="indexterm" name="id2589025"></a>
+<a class="indexterm" name="id2589032"></a>
 		<span class="emphasis"><em>pam_ldap:</em></span> A PAM module that provides LDAP integration for UNIX/Linux
 		system access authentication.
 		</p></li><li><p>
-<a class="indexterm" name="id2589082"></a>
-<a class="indexterm" name="id2589088"></a>
-<a class="indexterm" name="id2589095"></a>
-<a class="indexterm" name="id2589102"></a>
+<a class="indexterm" name="id2589050"></a>
+<a class="indexterm" name="id2589057"></a>
+<a class="indexterm" name="id2589064"></a>
+<a class="indexterm" name="id2589071"></a>
 		<span class="emphasis"><em>idmap_ad:</em></span> An IDMAP backend that supports the Microsoft Services for
 		UNIX RFC 2307 schema available from the PADL Web
 		<a class="ulink" href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>.
-		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589125"></a>Comments Regarding LDAP</h3></div></div></div><p>
-<a class="indexterm" name="id2589133"></a>
-<a class="indexterm" name="id2589143"></a>
-<a class="indexterm" name="id2589150"></a>
-<a class="indexterm" name="id2589156"></a>
+		</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589094"></a>Comments Regarding LDAP</h3></div></div></div><p>
+<a class="indexterm" name="id2589102"></a>
+<a class="indexterm" name="id2589111"></a>
+<a class="indexterm" name="id2589118"></a>
+<a class="indexterm" name="id2589125"></a>
 	There is much excitement and interest in LDAP directories in the information technology world
 	today. The LDAP architecture was designed to be highly scalable. It was also designed for
 	use across a huge number of potential areas of application encompassing a wide range of operating
 	systems and platforms. LDAP technologies are at the heart of the current generations of Federated
 	Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.
 	</p><p>
-<a class="indexterm" name="id2589174"></a>
-<a class="indexterm" name="id2589181"></a>
-<a class="indexterm" name="id2589188"></a>
-<a class="indexterm" name="id2589194"></a>
+<a class="indexterm" name="id2589143"></a>
+<a class="indexterm" name="id2589150"></a>
+<a class="indexterm" name="id2589156"></a>
+<a class="indexterm" name="id2589163"></a>
 	LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft
 	Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the
 	directory services LDAP involves interaction with legacy as well as new generation applications, all of which
 	depend on some form of authentication services.
 	</p><p>
-<a class="indexterm" name="id2589211"></a>
-<a class="indexterm" name="id2589218"></a>
-<a class="indexterm" name="id2589225"></a>
-<a class="indexterm" name="id2589232"></a>
-<a class="indexterm" name="id2589238"></a>
-<a class="indexterm" name="id2589245"></a>
-<a class="indexterm" name="id2589252"></a>
-<a class="indexterm" name="id2589259"></a>
-<a class="indexterm" name="id2589266"></a>
-<a class="indexterm" name="id2589273"></a>
-<a class="indexterm" name="id2589280"></a>
-<a class="indexterm" name="id2589287"></a>
-<a class="indexterm" name="id2589294"></a>
-<a class="indexterm" name="id2589300"></a>
+<a class="indexterm" name="id2589179"></a>
+<a class="indexterm" name="id2589186"></a>
+<a class="indexterm" name="id2589193"></a>
+<a class="indexterm" name="id2589200"></a>
+<a class="indexterm" name="id2589207"></a>
+<a class="indexterm" name="id2589214"></a>
+<a class="indexterm" name="id2589221"></a>
+<a class="indexterm" name="id2589228"></a>
+<a class="indexterm" name="id2589235"></a>
+<a class="indexterm" name="id2589242"></a>
+<a class="indexterm" name="id2589248"></a>
+<a class="indexterm" name="id2589255"></a>
+<a class="indexterm" name="id2589262"></a>
+<a class="indexterm" name="id2589269"></a>
 	UNIX services can utilize LDAP directory information for authentication and access controls
 	through intermediate tools and utilities. The total environment that consists of the LDAP directory
 	and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform
@@ -410,12 +410,12 @@ Samba-3 introduces a number of new password backend capabilities.
 	shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers,
 	and also Samba.
 	</p><p>
-<a class="indexterm" name="id2589321"></a>
-<a class="indexterm" name="id2589328"></a>
-<a class="indexterm" name="id2589334"></a>
-<a class="indexterm" name="id2589341"></a>
-<a class="indexterm" name="id2589348"></a>
-<a class="indexterm" name="id2589355"></a>
+<a class="indexterm" name="id2589289"></a>
+<a class="indexterm" name="id2589296"></a>
+<a class="indexterm" name="id2589302"></a>
+<a class="indexterm" name="id2589309"></a>
+<a class="indexterm" name="id2589316"></a>
+<a class="indexterm" name="id2589323"></a>
 	Many sites are installing LDAP for the first time in order to provide a scalable passdb backend
 	for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such
 	as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be,
@@ -423,37 +423,37 @@ Samba-3 introduces a number of new password backend capabilities.
 	are of a durable nature for the site. These have far-reaching implications that affect long-term
 	information systems management costs.
 	</p><p>
-<a class="indexterm" name="id2589374"></a>
-<a class="indexterm" name="id2589381"></a>
+<a class="indexterm" name="id2589342"></a>
+<a class="indexterm" name="id2589349"></a>
 	Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory
 	Information Tree (DIT) may impact current and future site needs, as well as the ability to meet
 	them. The way that Samba SAM information should be stored within the DIT varies from site to site
 	and with each implementation new experience is gained. It is well understood by LDAP veterans that
 	first implementations create awakening, second implementations of LDAP create fear, and
 	third-generation deployments bring peace and tranquility.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2589401"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p>
-<a class="indexterm" name="id2589409"></a>
-<a class="indexterm" name="id2589416"></a>
-<a class="indexterm" name="id2589423"></a>
-<a class="indexterm" name="id2589430"></a>
-<a class="indexterm" name="id2589437"></a>
-<a class="indexterm" name="id2589444"></a>
-<a class="indexterm" name="id2589451"></a>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2589369"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p>
+<a class="indexterm" name="id2589377"></a>
+<a class="indexterm" name="id2589384"></a>
+<a class="indexterm" name="id2589391"></a>
+<a class="indexterm" name="id2589398"></a>
+<a class="indexterm" name="id2589405"></a>
+<a class="indexterm" name="id2589412"></a>
+<a class="indexterm" name="id2589419"></a>
 	Samba requires UNIX POSIX identity information as well as a place to store information that is
 	specific to Samba and the Windows networking environment. The most used information that must
 	be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain
 	trust accounts, and intermediate information specific to Samba internals.
 	</p><p>
-<a class="indexterm" name="id2589467"></a>
-<a class="indexterm" name="id2589474"></a>
-<a class="indexterm" name="id2589481"></a>
+<a class="indexterm" name="id2589435"></a>
+<a class="indexterm" name="id2589442"></a>
+<a class="indexterm" name="id2589449"></a>
 	The example deployment guidelines in this book, as well as other books and HOWTO documents
 	available from the internet may not fit with established directory designs and implementations.
 	The existing DIT may not be able to accommodate the simple information layout proposed in common
 	sources. Additionally, you may find that the common scripts and tools that are used to provision
 	the LDAP directory for use with Samba may not suit your needs.
 	</p><p>
-<a class="indexterm" name="id2589499"></a>
+<a class="indexterm" name="id2589467"></a>
 	It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a
 	set of site-specific scripts and utilities to make it possible to deploy Samba within the
 	scope of site operations. The way that user and group accounts are distributed throughout
@@ -461,63 +461,63 @@ Samba-3 introduces a number of new password backend capabilities.
 	the journey to it may be challenging. Take time to understand site needs and do not rush
 	into deployment.
 	</p><p>
-<a class="indexterm" name="id2589517"></a>
-<a class="indexterm" name="id2589524"></a>
+<a class="indexterm" name="id2589485"></a>
+<a class="indexterm" name="id2589492"></a>
 	Above all, do not blindly use scripts and tools that are not suitable for your site. Check
 	and validate all scripts before you execute them to make sure that the existing infrastructure
 	will not be damaged by inadvertent use of an inappropriate tool.
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589538"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p>
-<a class="indexterm" name="id2589547"></a>
-<a class="indexterm" name="id2589554"></a>
-<a class="indexterm" name="id2589560"></a>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589506"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p>
+<a class="indexterm" name="id2589515"></a>
+<a class="indexterm" name="id2589522"></a>
+<a class="indexterm" name="id2589528"></a>
 		Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and
 		configuration of an LDAP directory prior to integration with Samba. A working knowledge
 		of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make
 		it a frustrating experience.
 		</p><p>
-<a class="indexterm" name="id2589576"></a>
-<a class="indexterm" name="id2589583"></a>
-<a class="indexterm" name="id2589590"></a>
+<a class="indexterm" name="id2589544"></a>
+<a class="indexterm" name="id2589551"></a>
+<a class="indexterm" name="id2589558"></a>
 		Computer (machine) accounts can be placed wherever you like in an LDAP directory subject
 		to some constraints that are described in this chapter.
 		</p><p>
-<a class="indexterm" name="id2589603"></a>
-<a class="indexterm" name="id2589609"></a>
-<a class="indexterm" name="id2589616"></a>
-<a class="indexterm" name="id2589623"></a>
-<a class="indexterm" name="id2589630"></a>
-<a class="indexterm" name="id2589637"></a>
-<a class="indexterm" name="id2589644"></a>
+<a class="indexterm" name="id2589570"></a>
+<a class="indexterm" name="id2589577"></a>
+<a class="indexterm" name="id2589584"></a>
+<a class="indexterm" name="id2589591"></a>
+<a class="indexterm" name="id2589598"></a>
+<a class="indexterm" name="id2589605"></a>
+<a class="indexterm" name="id2589612"></a>
 		The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
 		Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
 		them. A user account and a machine account are indistinguishable from each other, except that
 		the machine account ends in a $ character, as do trust accounts.
 		</p><p>
-<a class="indexterm" name="id2589660"></a>
-<a class="indexterm" name="id2589667"></a>
-<a class="indexterm" name="id2589674"></a>
-<a class="indexterm" name="id2589681"></a>
-<a class="indexterm" name="id2589688"></a>
+<a class="indexterm" name="id2589628"></a>
+<a class="indexterm" name="id2589635"></a>
+<a class="indexterm" name="id2589642"></a>
+<a class="indexterm" name="id2589649"></a>
+<a class="indexterm" name="id2589655"></a>
 		The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX
 		UID is a design decision that was made a long way back in the history of Samba development. It
 		is unlikely that this decision will be reversed or changed during the remaining life of the
 		Samba-3.x series.
 		</p><p>
-<a class="indexterm" name="id2589703"></a>
-<a class="indexterm" name="id2589709"></a>
-<a class="indexterm" name="id2589716"></a>
+<a class="indexterm" name="id2589670"></a>
+<a class="indexterm" name="id2589677"></a>
+<a class="indexterm" name="id2589684"></a>
 		The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
 		must refer back to the host operating system on which Samba is running. The NSS is the preferred
 		mechanism that shields applications (like Samba) from the need to know everything about every
 		host OS it runs on.
 		</p><p>
-<a class="indexterm" name="id2589731"></a>
-<a class="indexterm" name="id2589737"></a>
-<a class="indexterm" name="id2589744"></a>
-<a class="indexterm" name="id2589751"></a>
-<a class="indexterm" name="id2589758"></a>
-<a class="indexterm" name="id2589764"></a>
-<a class="indexterm" name="id2589771"></a>
+<a class="indexterm" name="id2589699"></a>
+<a class="indexterm" name="id2589705"></a>
+<a class="indexterm" name="id2589712"></a>
+<a class="indexterm" name="id2589719"></a>
+<a class="indexterm" name="id2589726"></a>
+<a class="indexterm" name="id2589732"></a>
+<a class="indexterm" name="id2589739"></a>
 		Samba asks the host OS to provide a UID via the &#8220;<span class="quote">passwd</span>&#8221;, &#8220;<span class="quote">shadow</span>&#8221;,
 		and &#8220;<span class="quote">group</span>&#8221; facilities in the NSS control (configuration) file. The best tool
 		for achieving this is left up to the UNIX administrator to determine. It is not imposed by
@@ -525,64 +525,64 @@ Samba-3 introduces a number of new password backend capabilities.
 		possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
 		all account entities can be located in an LDAP directory.
 		</p><p>
-<a class="indexterm" name="id2589799"></a>
-<a class="indexterm" name="id2589806"></a>
-<a class="indexterm" name="id2589813"></a>
-<a class="indexterm" name="id2589820"></a>
-<a class="indexterm" name="id2589826"></a>
+<a class="indexterm" name="id2589767"></a>
+<a class="indexterm" name="id2589774"></a>
+<a class="indexterm" name="id2589781"></a>
+<a class="indexterm" name="id2589787"></a>
+<a class="indexterm" name="id2589794"></a>
 		For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
 		be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
 		is fundamentally an LDAP design question.  The information provided on the Samba list and
 		in the documentation is directed at providing working examples only. The design
 		of an LDAP directory is a complex subject that is beyond the scope of this documentation.
 		</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><p>
-<a class="indexterm" name="id2589857"></a>
-<a class="indexterm" name="id2589864"></a>
-<a class="indexterm" name="id2589870"></a>
+<a class="indexterm" name="id2589825"></a>
+<a class="indexterm" name="id2589831"></a>
+<a class="indexterm" name="id2589838"></a>
 Samba provides two tools for management of user and machine accounts:
 <code class="literal">smbpasswd</code> and <code class="literal">pdbedit</code>.
 </p><p>
-<a class="indexterm" name="id2589893"></a>
-<a class="indexterm" name="id2589900"></a>
-<a class="indexterm" name="id2589907"></a>
+<a class="indexterm" name="id2589861"></a>
+<a class="indexterm" name="id2589868"></a>
+<a class="indexterm" name="id2589875"></a>
 The <code class="literal">pdbedit</code> can be used to manage account policies in addition to
 Samba user account information. The policy management capability is used to administer
 domain default settings for password aging and management controls to handle failed login
 attempts.
 </p><p>
-<a class="indexterm" name="id2589927"></a>
-<a class="indexterm" name="id2589934"></a>
-<a class="indexterm" name="id2589941"></a>
-<a class="indexterm" name="id2589948"></a>
+<a class="indexterm" name="id2589895"></a>
+<a class="indexterm" name="id2589902"></a>
+<a class="indexterm" name="id2589909"></a>
+<a class="indexterm" name="id2589916"></a>
 Some people are confused when reference is made to <code class="literal">smbpasswd</code> because the
 name refers to a storage mechanism for SambaSAMAccount information, but it is also the name
 of a utility tool. That tool is destined to eventually be replaced by new functionality that
-is being added to the <code class="literal">net</code> toolset (see <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">the Net Command</a>).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589979"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p>
-<a class="indexterm" name="id2589993"></a>
-<a class="indexterm" name="id2589999"></a>
-<a class="indexterm" name="id2590006"></a>
-<a class="indexterm" name="id2590013"></a>
-<a class="indexterm" name="id2590020"></a>
+is being added to the <code class="literal">net</code> toolset (see <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">the Net Command</a>.
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589947"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p>
+<a class="indexterm" name="id2589960"></a>
+<a class="indexterm" name="id2589967"></a>
+<a class="indexterm" name="id2589974"></a>
+<a class="indexterm" name="id2589981"></a>
+<a class="indexterm" name="id2589988"></a>
 		The <code class="literal">smbpasswd</code> utility is similar to the <code class="literal">passwd</code>
 		and <code class="literal">yppasswd</code> programs. It maintains the two 32 byte password
 		fields in the passdb backend. This utility operates independently of the actual
 		account and password storage methods used (as specified by the <em class="parameter"><code>passdb
-		backend</code></em> in the <code class="filename">smb.conf</code> file).
+		backend</code></em> in the <code class="filename">smb.conf</code> file.
 		</p><p>
-<a class="indexterm" name="id2590064"></a>
-<a class="indexterm" name="id2590071"></a>
+<a class="indexterm" name="id2590032"></a>
+<a class="indexterm" name="id2590039"></a>
 		<code class="literal">smbpasswd</code> 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.
 		</p><p>
-<a class="indexterm" name="id2590089"></a>
-<a class="indexterm" name="id2590096"></a>
+<a class="indexterm" name="id2590057"></a>
+<a class="indexterm" name="id2590064"></a>
 		<code class="literal">smbpasswd</code> has the capability to change passwords on Windows NT
 		servers (this only works when the request is sent to the NT PDC if changing an NT
 		domain user's password).
 		</p><p>
-		<a class="indexterm" name="id2590115"></a>
-		<a class="indexterm" name="id2590122"></a>
+		<a class="indexterm" name="id2590083"></a>
+		<a class="indexterm" name="id2590090"></a>
 		<code class="literal">smbpasswd</code> 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</em></span> interdomain trust accounts.</p></li></ul></div><p>
 		To run smbpasswd as a normal user, just type:
@@ -601,56 +601,56 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li
 		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>
-<a class="indexterm" name="id2590262"></a>
+<a class="indexterm" name="id2590230"></a>
 		When invoked by an ordinary user, the command will allow only the user to change his or her own
 		SMB password.
 		</p><p>
-<a class="indexterm" name="id2590274"></a>
-<a class="indexterm" name="id2590281"></a>
+<a class="indexterm" name="id2590242"></a>
+<a class="indexterm" name="id2590249"></a>
 		When run by root, <code class="literal">smbpasswd</code> may take an optional argument specifying
 		the username whose SMB password you wish to change. When run as root, <code class="literal">smbpasswd</code>
 		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>
-<a class="indexterm" name="id2590308"></a>
-<a class="indexterm" name="id2590314"></a>
-<a class="indexterm" name="id2590321"></a>
-<a class="indexterm" name="id2590328"></a>
+<a class="indexterm" name="id2590275"></a>
+<a class="indexterm" name="id2590282"></a>
+<a class="indexterm" name="id2590289"></a>
+<a class="indexterm" name="id2590296"></a>
 		<code class="literal">smbpasswd</code> is designed to work in the way familiar to UNIX
 		users who use the <code class="literal">passwd</code> or <code class="literal">yppasswd</code> commands.
 		While designed for administrative use, this tool provides essential user-level
 		password change capabilities.
 		</p><p>
-<a class="indexterm" name="id2590359"></a>
+<a class="indexterm" name="id2590327"></a>
 		For more details on using <code class="literal">smbpasswd</code>, 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="pdbeditthing"></a>The <code class="literal">pdbedit</code> Tool</h3></div></div></div><p>
-		<a class="indexterm" name="id2590394"></a>
-		<a class="indexterm" name="id2590400"></a>
-		<a class="indexterm" name="id2590407"></a>
-		<a class="indexterm" name="id2590414"></a>
+		<a class="indexterm" name="id2590361"></a>
+		<a class="indexterm" name="id2590368"></a>
+		<a class="indexterm" name="id2590375"></a>
+		<a class="indexterm" name="id2590382"></a>
 		<code class="literal">pdbedit</code> is a tool that can be used only by root. It is used to
 		manage the passdb backend, as well as domain-wide account policy settings. <code class="literal">pdbedit</code>
 		can be used to:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>add, remove, or modify user accounts.</p></li><li><p>list user accounts.</p></li><li><p>migrate user accounts.</p></li><li><p>migrate group accounts.</p></li><li><p>manage account policies.</p></li><li><p>manage domain access policy settings.</p></li></ul></div><p>
-		<a class="indexterm" name="id2590473"></a>
+		<a class="indexterm" name="id2590441"></a>
 		Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to
 		implement a series of <code class="literal">internal controls</code> and procedures to communicate, store,
 		and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:
 		</p><div class="orderedlist"><ol type="1"><li><p>Who has access to information systems that store financial data.</p></li><li><p>How personal and financial information is treated among employees and business
 				partners.</p></li><li><p>How security vulnerabilities are managed.</p></li><li><p>Security and patch level maintenance for all information systems.</p></li><li><p>How information systems changes are documented and tracked.</p></li><li><p>How information access controls are implemented and managed.</p></li><li><p>Auditability of all information systems in respect of change and security.</p></li><li><p>Disciplinary procedures and controls to ensure privacy.</p></li></ol></div><p>
-		<a class="indexterm" name="id2590546"></a>
-		<a class="indexterm" name="id2590552"></a>
+		<a class="indexterm" name="id2590513"></a>
+		<a class="indexterm" name="id2590520"></a>
 		In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of
 		business related information systems so as to ensure the compliance of all information systems that
 		are used to store personal information and particularly for financial records processing. Similar
 		accountabilities are being demanded around the world.
 		</p><p>
-		<a class="indexterm" name="id2590569"></a>
-		<a class="indexterm" name="id2590576"></a>
-		<a class="indexterm" name="id2590582"></a>
-		<a class="indexterm" name="id2590589"></a>
-		<a class="indexterm" name="id2590596"></a>
+		<a class="indexterm" name="id2590543"></a>
+		<a class="indexterm" name="id2590549"></a>
+		<a class="indexterm" name="id2590556"></a>
+		<a class="indexterm" name="id2590563"></a>
+		<a class="indexterm" name="id2590570"></a>
 		The need to be familiar with the Samba tools and facilities that permit information systems operation
 		in compliance with government laws and regulations is clear to all. The <code class="literal">pdbedit</code> is
 		currently the only Samba tool that provides the capacity to manage account and systems access controls
@@ -660,27 +660,27 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li
 		Domain global policy controls available in Windows NT4 compared with Samba
 		is shown in <a class="link" href="passdb.html#policycontrols" title="Table�11.1.�NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>.
 		</p><div class="table"><a name="policycontrols"></a><p class="title"><b>Table�11.1.�NT4 Domain v's Samba Policy Controls</b></p><div class="table-contents"><table summary="NT4 Domain v's Samba Policy Controls" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>NT4 policy Name</p></th><th align="left"><p>Samba Policy Name</p></th><th align="center"><p>NT4 Range</p></th><th align="center"><p>Samba Range</p></th><th align="center"><p>Samba Default</p></th></tr></thead><tbody><tr><td align="left"><p>Maximum Password Age</p></td><td align="left"><p>maximum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>4294967295</p></td></tr><tr><td align="left"><p>Minimum Password Age</p></td><td align="left"><p>minimum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Minimum Password Length</p></td><td align="left"><p>min password length</p></td><td align="center"><p>1 - 14 (Chars)</p></td><td align="center"><p>0 - 4294967295 (Chars)</p></td><td align="center"><p>5</p></td></tr><tr><td align="left"><p>Password Uniqueness</p></td><td align="left"><p>password history</p></td><td align="center"><p>0 - 23 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Account Lockout - Reset count after</p></td><td align="left"><p>reset count minutes</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Lockout after bad logon attempts</p></td><td align="left"><p>bad lockout attempt</p></td><td align="center"><p>0 - 998 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Not Known ***</p></td><td align="left"><p>disconnect time</p></td><td align="center"><p>TBA</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Lockout Duration</p></td><td align="left"><p>lockout duration</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Users must log on in order to change password</p></td><td align="left"><p>user must logon to change password</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Registry Setting ***</p></td><td align="left"><p>refuse machine password change</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr></tbody></table></div></div><br class="table-break"><p>
-		<a class="indexterm" name="id2590979"></a>
-<a class="indexterm" name="id2590986"></a>
-<a class="indexterm" name="id2590993"></a>
-<a class="indexterm" name="id2591000"></a>
+		<a class="indexterm" name="id2590953"></a>
+<a class="indexterm" name="id2590960"></a>
+<a class="indexterm" name="id2590967"></a>
+<a class="indexterm" name="id2590974"></a>
 		The <code class="literal">pdbedit</code> 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 superset of them.
 		</p><p>
-		<a class="indexterm" name="id2591019"></a>
-<a class="indexterm" name="id2591026"></a>
-<a class="indexterm" name="id2591033"></a>
+		<a class="indexterm" name="id2590993"></a>
+<a class="indexterm" name="id2590999"></a>
+<a class="indexterm" name="id2591006"></a>
 		One particularly important purpose of the <code class="literal">pdbedit</code> is to allow
 		the import/export of account information from one passdb backend to another.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2591049"></a>User Account Management</h4></div></div></div><p>
-<a class="indexterm" name="id2591057"></a>
-<a class="indexterm" name="id2591064"></a>
-<a class="indexterm" name="id2591071"></a>
-<a class="indexterm" name="id2591078"></a>
-<a class="indexterm" name="id2591084"></a>
-<a class="indexterm" name="id2591091"></a>
-<a class="indexterm" name="id2591098"></a>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2591023"></a>User Account Management</h4></div></div></div><p>
+<a class="indexterm" name="id2591031"></a>
+<a class="indexterm" name="id2591038"></a>
+<a class="indexterm" name="id2591044"></a>
+<a class="indexterm" name="id2591051"></a>
+<a class="indexterm" name="id2591058"></a>
+<a class="indexterm" name="id2591065"></a>
+<a class="indexterm" name="id2591072"></a>
 		The <code class="literal">pdbedit</code> tool, like the <code class="literal">smbpasswd</code> tool, requires
 		that a POSIX user account already exists in the UNIX/Linux system accounts database (backend).
 		Neither tool will call out to the operating system to create a user account because this is
@@ -690,13 +690,13 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li
 		correctly created and changed. The use of the <code class="literal">pdbedit</code> tool does not
 		make use of these interface scripts.
 		</p><p>
-<a class="indexterm" name="id2591142"></a>
-<a class="indexterm" name="id2591149"></a>
+<a class="indexterm" name="id2591116"></a>
+<a class="indexterm" name="id2591123"></a>
 		Before attempting to use the <code class="literal">pdbedit</code> tool to manage user and machine
 		accounts, make certain that a system (POSIX) account has already been created.
-		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591165"></a>Listing User and Machine Accounts</h5></div></div></div><p>
-<a class="indexterm" name="id2591174"></a>
-<a class="indexterm" name="id2591180"></a>
+		</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591139"></a>Listing User and Machine Accounts</h5></div></div></div><p>
+<a class="indexterm" name="id2591147"></a>
+<a class="indexterm" name="id2591154"></a>
 		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">
@@ -723,7 +723,7 @@ Password can change:  Sat, 14 Dec 2002 14:37:03 GMT
 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2591222"></a>
+<a class="indexterm" name="id2591196"></a>
 		Accounts can also be listed in the older <code class="literal">smbpasswd</code> format:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -Lw</code></strong>
@@ -748,29 +748,29 @@ frodo$:1008:15891DC6B843ECA41249940C814E316B:
 marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
      C610EFE9A385A3E8AA46ADFD576E6881:[W          ]:LCT-40F07A4
 </pre><p>
-<a class="indexterm" name="id2591271"></a>
-<a class="indexterm" name="id2591278"></a>
-<a class="indexterm" name="id2591284"></a>
-<a class="indexterm" name="id2591291"></a>
-<a class="indexterm" name="id2591298"></a>
-<a class="indexterm" name="id2591305"></a>
+<a class="indexterm" name="id2591245"></a>
+<a class="indexterm" name="id2591252"></a>
+<a class="indexterm" name="id2591258"></a>
+<a class="indexterm" name="id2591265"></a>
+<a class="indexterm" name="id2591272"></a>
+<a class="indexterm" name="id2591279"></a>
 		The account information that was returned by this command in order from left to right
 		consists of the following colon separated data:
-		</p><div class="itemizedlist"><ul type="disc"><li><p>Login ID.</p></li><li><p>UNIX UID.</p></li><li><p>Microsoft LanManager password hash (password converted to upper-case then hashed).</p></li><li><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li><p>Samba SAM Account Flags.</p></li><li><p>The LCT data (password last change time).</p></li></ul></div><p>
-<a class="indexterm" name="id2591356"></a>
-<a class="indexterm" name="id2591362"></a>
+		</p><div class="itemizedlist"><ul type="disc"><li><p>Login ID.</p></li><li><p>UNIX UID.</p></li><li><p>Microsoft LanManager password hash (password converted to upper-case then hashed.</p></li><li><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li><p>Samba SAM Account Flags.</p></li><li><p>The LCT data (password last change time).</p></li></ul></div><p>
+<a class="indexterm" name="id2591329"></a>
+<a class="indexterm" name="id2591336"></a>
 		The Account Flags parameters are documented in the <code class="literal">pdbedit</code> man page, and are
 		briefly documented in <a class="link" href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>.
 		</p><p>
-<a class="indexterm" name="id2591389"></a>
+<a class="indexterm" name="id2591363"></a>
 		The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of
 		the time when the password was last changed.
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591400"></a>Adding User Accounts</h5></div></div></div><p>
-<a class="indexterm" name="id2591408"></a>
-<a class="indexterm" name="id2591415"></a>
-<a class="indexterm" name="id2591422"></a>
-<a class="indexterm" name="id2591429"></a>
-<a class="indexterm" name="id2591436"></a>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591374"></a>Adding User Accounts</h5></div></div></div><p>
+<a class="indexterm" name="id2591382"></a>
+<a class="indexterm" name="id2591389"></a>
+<a class="indexterm" name="id2591396"></a>
+<a class="indexterm" name="id2591403"></a>
+<a class="indexterm" name="id2591410"></a>
 		The <code class="literal">pdbedit</code> can be used to add a user account to a standalone server
 		or to a domain. In the example shown here the account for the user <code class="literal">vlaan</code>
 		has been created before attempting to add the SambaSAMAccount.
@@ -802,11 +802,11 @@ Last bad password   : 0
 Bad password count  : 0
 Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 </pre><p>
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591488"></a>Deleting Accounts</h5></div></div></div><p>
-<a class="indexterm" name="id2591496"></a>
-<a class="indexterm" name="id2591503"></a>
-<a class="indexterm" name="id2591510"></a>
-<a class="indexterm" name="id2591516"></a>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591462"></a>Deleting Accounts</h5></div></div></div><p>
+<a class="indexterm" name="id2591470"></a>
+<a class="indexterm" name="id2591476"></a>
+<a class="indexterm" name="id2591483"></a>
+<a class="indexterm" name="id2591490"></a>
 		An account can be deleted from the SambaSAMAccount database
 </p><pre class="screen">
 <code class="prompt">root# </code> pdbedit -x vlaan
@@ -814,16 +814,16 @@ Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 		The account is removed without further screen output. The account is removed only from the
 		SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
 		</p><p>
-<a class="indexterm" name="id2591543"></a>
-<a class="indexterm" name="id2591550"></a>
+<a class="indexterm" name="id2591517"></a>
+<a class="indexterm" name="id2591524"></a>
 		The use of the NT4 domain user manager to delete an account will trigger the <em class="parameter"><code>delete user
 		script</code></em>, but not the <code class="literal">pdbedit</code> tool.
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591572"></a>Changing User Accounts</h5></div></div></div><p>
-<a class="indexterm" name="id2591580"></a>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591546"></a>Changing User Accounts</h5></div></div></div><p>
+<a class="indexterm" name="id2591554"></a>
 		Refer to the <code class="literal">pdbedit</code> man page for a full synopsis of all operations
 		that are available with this tool.
 		</p><p>
-<a class="indexterm" name="id2591598"></a>
+<a class="indexterm" name="id2591572"></a>
 		An example of a simple change in the user account information is the change of the full name
 		information shown here:
 </p><pre class="screen">
@@ -835,9 +835,9 @@ Home Directory:       \\frodo\vlaan
 ...
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2591625"></a>
-<a class="indexterm" name="id2591632"></a>
-<a class="indexterm" name="id2591639"></a>
+<a class="indexterm" name="id2591599"></a>
+<a class="indexterm" name="id2591606"></a>
+<a class="indexterm" name="id2591613"></a>
 		Let us assume for a moment that a user's password has expired and the user is unable to
 		change the password at this time. It may be necessary to give the user additional grace time
 		so that it is possible to continue to work with the account and the original password. This
@@ -852,8 +852,8 @@ Last bad password   : Thu, 03 Jan 2002 15:08:35 GMT
 Bad password count  : 2
 ...
 </pre><p>
-<a class="indexterm" name="id2591668"></a>
-<a class="indexterm" name="id2591674"></a>
+<a class="indexterm" name="id2591641"></a>
+<a class="indexterm" name="id2591648"></a>
 		The user has recorded 2 bad logon attempts and the next will lock the account, but the
 		password is also expired. Here is how this account can be reset:
 </p><pre class="screen">
@@ -885,49 +885,49 @@ Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
 Password must change: Fri, 01 Jan 2010 00:00:00 GMT
 ...
 </pre><p>
-<a class="indexterm" name="id2591738"></a>
-<a class="indexterm" name="id2591745"></a>
+<a class="indexterm" name="id2591712"></a>
+<a class="indexterm" name="id2591719"></a>
 		Refer to the strptime man page for specific time format information.
 		</p><p>
-<a class="indexterm" name="id2591757"></a>
-<a class="indexterm" name="id2591763"></a>
+<a class="indexterm" name="id2591730"></a>
+<a class="indexterm" name="id2591737"></a>
 		Please refer to the pdbedit man page for further information relating to SambaSAMAccount
 		management.
 		</p><div class="sect5" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="TOSHARG-acctflags"></a>Account Flags Management</h6></div></div></div><p>
-<a class="indexterm" name="id2591785"></a>
-<a class="indexterm" name="id2591792"></a>
-<a class="indexterm" name="id2591801"></a>
-<a class="indexterm" name="id2591808"></a>
+<a class="indexterm" name="id2591759"></a>
+<a class="indexterm" name="id2591766"></a>
+<a class="indexterm" name="id2591775"></a>
+<a class="indexterm" name="id2591782"></a>
 		The Samba SAM account flags are properly called the ACB (account control block) within
 		the Samba source code. In some parts of the Samba source code they are referred to as the
 		account encode_bits, and also as the account control flags.
 		</p><p>
-<a class="indexterm" name="id2591823"></a>
-<a class="indexterm" name="id2591830"></a>
-<a class="indexterm" name="id2591837"></a>
-<a class="indexterm" name="id2591844"></a>
-<a class="indexterm" name="id2591850"></a>
+<a class="indexterm" name="id2591797"></a>
+<a class="indexterm" name="id2591804"></a>
+<a class="indexterm" name="id2591810"></a>
+<a class="indexterm" name="id2591817"></a>
+<a class="indexterm" name="id2591824"></a>
 		The manual adjustment of user, machine (workstation or server) or an inter-domain trust
 		account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
 		where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
 		useful. The tool of choice by which such correction can be affected is the <code class="literal">pdbedit</code> utility.
 		</p><p>
-<a class="indexterm" name="id2591873"></a>
-<a class="indexterm" name="id2591880"></a>
+<a class="indexterm" name="id2591854"></a>
+<a class="indexterm" name="id2591861"></a>
 		There have been a few requests for information regarding the account flags from developers
 		who are creating their own Samba management tools. An example of a need for information regarding
 		the proper management of the account flags is evident when developing scripts that will be used
 		to manage an LDAP directory.
 		</p><p>
-<a class="indexterm" name="id2591896"></a>
-<a class="indexterm" name="id2591903"></a>
+<a class="indexterm" name="id2591876"></a>
+<a class="indexterm" name="id2591883"></a>
 		The account flag field can contain up to 16 characters. Presently, only 11 are in use.
 		These are listed in <a class="link" href="passdb.html#accountflags" title="Table�11.2.�Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>.
 		The order in which the flags are specified to the <code class="literal">pdbedit</code> command is not important.
 		In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.
 		</p><div class="table"><a name="accountflags"></a><p class="title"><b>Table�11.2.�Samba SAM Account Control Block Flags</b></p><div class="table-contents"><table summary="Samba SAM Account Control Block Flags" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Flag</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">D</td><td align="left">Account is disabled.</td></tr><tr><td align="center">H</td><td align="left">A home directory is required.</td></tr><tr><td align="center">I</td><td align="left">An inter-domain trust account.</td></tr><tr><td align="center">L</td><td align="left">Account has been auto-locked.</td></tr><tr><td align="center">M</td><td align="left">An MNS (Microsoft network service) logon account.</td></tr><tr><td align="center">N</td><td align="left">Password not required.</td></tr><tr><td align="center">S</td><td align="left">A server trust account.</td></tr><tr><td align="center">T</td><td align="left">Temporary duplicate account entry.</td></tr><tr><td align="center">U</td><td align="left">A normal user account.</td></tr><tr><td align="center">W</td><td align="left">A workstation trust account.</td></tr><tr><td align="center">X</td><td align="left">Password does not expire.</td></tr></tbody></table></div></div><br class="table-break"><p>
-<a class="indexterm" name="id2592134"></a>
-<a class="indexterm" name="id2592140"></a>
+<a class="indexterm" name="id2592114"></a>
+<a class="indexterm" name="id2592121"></a>
 		An example of use of the <code class="literal">pdbedit</code> utility to set the account control flags
 		is shown here:
 </p><pre class="screen">
@@ -955,7 +955,7 @@ Last bad password   : 0
 Bad password count  : 0
 Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 </pre><p>
-<a class="indexterm" name="id2592196"></a>
+<a class="indexterm" name="id2592176"></a>
 	The flags can be reset to the default settings by executing:
 </p><pre class="screen">
 <code class="prompt">root# </code> pdbedit -r -c "[]" jht
@@ -982,9 +982,9 @@ Last bad password   : 0
 Bad password count  : 0
 Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 </pre><p>
-		</p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2592233"></a>Domain Account Policy Managment</h5></div></div></div><p>
-<a class="indexterm" name="id2592241"></a>
-<a class="indexterm" name="id2592248"></a>
+		</p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2592213"></a>Domain Account Policy Managment</h5></div></div></div><p>
+<a class="indexterm" name="id2592221"></a>
+<a class="indexterm" name="id2592228"></a>
 		To view the domain account access policies that may be configured execute:
 </p><pre class="screen">
 <code class="prompt">root# </code> pdbedit -P ?
@@ -1032,134 +1032,134 @@ Account policies must be set individually on each PDC and BDC. At this time (Sam
 account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
 time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations
 regarding this facility.
-</p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2592394"></a>Account Import/Export</h4></div></div></div><p>
-		<a class="indexterm" name="id2592402"></a>
-<a class="indexterm" name="id2592409"></a>
-<a class="indexterm" name="id2592416"></a>
+</p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2592375"></a>Account Import/Export</h4></div></div></div><p>
+		<a class="indexterm" name="id2592383"></a>
+<a class="indexterm" name="id2592390"></a>
+<a class="indexterm" name="id2592397"></a>
 		The <code class="literal">pdbedit</code> tool allows import/export of authentication (account)
 		databases from one backend to another. For example, to import/export accounts from an
 		old <code class="filename">smbpasswd</code> database to a <em class="parameter"><code>tdbsam</code></em>
 		backend:
 		</p><div class="procedure"><ol type="1"><li><p>
-<a class="indexterm" name="id2592453"></a>
+<a class="indexterm" name="id2592433"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong>
 </pre><p>
 			</p></li><li><p>
-<a class="indexterm" name="id2592483"></a>
+<a class="indexterm" name="id2592463"></a>
 			Replace the <em class="parameter"><code>smbpasswd</code></em> with <em class="parameter"><code>tdbsam</code></em> in the
 			<em class="parameter"><code>passdb backend</code></em> configuration in <code class="filename">smb.conf</code>.
-			</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="id2592519"></a>Password Backends</h2></div></div></div><p>
-<a class="indexterm" name="id2592527"></a>
-<a class="indexterm" name="id2592534"></a>
+			</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="id2592500"></a>Password Backends</h2></div></div></div><p>
+<a class="indexterm" name="id2592508"></a>
+<a class="indexterm" name="id2592514"></a>
 Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one
 begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend
 feature in order to simplify problems that broke some installations. This removal has made the internal
 operation of Samba-3 more consistent and predictable.
 </p><p>
-<a class="indexterm" name="id2592551"></a>
-<a class="indexterm" name="id2592558"></a>
+<a class="indexterm" name="id2592531"></a>
+<a class="indexterm" name="id2592538"></a>
 Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier
 versions of Samba-3 made it possible to specify multiple password backends, and even multiple
 backends of the same type. The multiple passdb backend capability caused many problems with name to SID and
 SID to name ID resolution.  The Samba team wrestled with the challenges and decided that this feature needed
 to be removed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592573"></a>Plaintext</h3></div></div></div><p>
-<a class="indexterm" name="id2592581"></a>
-<a class="indexterm" name="id2592588"></a>
-<a class="indexterm" name="id2592595"></a>
-<a class="indexterm" name="id2592602"></a>
-<a class="indexterm" name="id2592609"></a>
-<a class="indexterm" name="id2592615"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592553"></a>Plaintext</h3></div></div></div><p>
+<a class="indexterm" name="id2592561"></a>
+<a class="indexterm" name="id2592568"></a>
+<a class="indexterm" name="id2592575"></a>
+<a class="indexterm" name="id2592582"></a>
+<a class="indexterm" name="id2592589"></a>
+<a class="indexterm" name="id2592596"></a>
 		Older versions of Samba retrieved user information from the UNIX user database
 		and eventually some other fields from the file <code class="filename">/etc/samba/smbpasswd</code>
 		or <code class="filename">/etc/smbpasswd</code>. 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 <code class="filename">/etc/passwd</code> database.
 		On most Linux systems, for example, all user and group resolution is done via PAM.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592649"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p>
-		<a class="indexterm" name="id2592657"></a>
-<a class="indexterm" name="id2592666"></a>
-<a class="indexterm" name="id2592673"></a>
-<a class="indexterm" name="id2592680"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592629"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p>
+		<a class="indexterm" name="id2592638"></a>
+<a class="indexterm" name="id2592647"></a>
+<a class="indexterm" name="id2592654"></a>
+<a class="indexterm" name="id2592661"></a>
 		Traditionally, when configuring <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>
 		in Samba's <code class="filename">smb.conf</code> file, user account information such as username, LM/NT password hashes,
 		password change times, and account flags have been stored in the <code class="filename">smbpasswd(5)</code>
 		file. There are several disadvantages to this approach for sites with large numbers of users
 		(counted in the thousands).
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2592723"></a>
+<a class="indexterm" name="id2592704"></a>
 		The first problem is that all lookups must be performed sequentially. Given that
 		there are approximately two lookups per domain logon (one during initial logon validation
 		and one for a session connection setup, 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 that used in databases.
 		</p></li><li><p>
-<a class="indexterm" name="id2592741"></a>
+<a class="indexterm" name="id2592721"></a>
+<a class="indexterm" name="id2592728"></a>
+<a class="indexterm" name="id2592735"></a>
+<a class="indexterm" name="id2592742"></a>
 <a class="indexterm" name="id2592748"></a>
-<a class="indexterm" name="id2592755"></a>
-<a class="indexterm" name="id2592761"></a>
-<a class="indexterm" name="id2592768"></a>
 		The second problem is that administrators who desire to replicate an smbpasswd file
 		to more than one Samba server are left to use external tools such as
 		<code class="literal">rsync(1)</code> and <code class="literal">ssh(1)</code> and write custom,
 		in-house scripts.
 		</p></li><li><p>
-<a class="indexterm" name="id2592794"></a>
-<a class="indexterm" name="id2592800"></a>
-<a class="indexterm" name="id2592807"></a>
-<a class="indexterm" name="id2592814"></a>
-<a class="indexterm" name="id2592821"></a>
+<a class="indexterm" name="id2592774"></a>
+<a class="indexterm" name="id2592781"></a>
+<a class="indexterm" name="id2592788"></a>
+<a class="indexterm" name="id2592795"></a>
+<a class="indexterm" name="id2592802"></a>
 		Finally, the amount of information that 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>
-<a class="indexterm" name="id2592838"></a>
-<a class="indexterm" name="id2592845"></a>
-<a class="indexterm" name="id2592852"></a>
-<a class="indexterm" name="id2592859"></a>
+<a class="indexterm" name="id2592818"></a>
+<a class="indexterm" name="id2592825"></a>
+<a class="indexterm" name="id2592832"></a>
+<a class="indexterm" name="id2592839"></a>
 		As a result of these deficiencies, a more robust means of storing user attributes
 		used by smbd was developed. The API that 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 source code trees).
 		</p><p>
-<a class="indexterm" name="id2592874"></a>
-<a class="indexterm" name="id2592881"></a>
-<a class="indexterm" name="id2592888"></a>
-<a class="indexterm" name="id2592895"></a>
-<a class="indexterm" name="id2592902"></a>
+<a class="indexterm" name="id2592855"></a>
+<a class="indexterm" name="id2592862"></a>
+<a class="indexterm" name="id2592869"></a>
+<a class="indexterm" name="id2592876"></a>
+<a class="indexterm" name="id2592882"></a>
 		Samba provides an enhanced set of passdb backends that overcome the deficiencies
 		of the smbpasswd plaintext database. These are tdbsam and ldapsam.
 		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="id2592915"></a>tdbsam</h3></div></div></div><p>
-		<a class="indexterm" name="id2592923"></a>
-<a class="indexterm" name="id2592932"></a>
-<a class="indexterm" name="id2592941"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592895"></a>tdbsam</h3></div></div></div><p>
+		<a class="indexterm" name="id2592903"></a>
+<a class="indexterm" name="id2592912"></a>
+<a class="indexterm" name="id2592921"></a>
 		Samba can store user and machine account data in a &#8220;<span class="quote">TDB</span>&#8221; (trivial database).
 		Using this backend does not require any additional configuration. This backend is
 		recommended for new installations that do not require LDAP.
 		</p><p>
-<a class="indexterm" name="id2592958"></a>
-<a class="indexterm" name="id2592965"></a>
-<a class="indexterm" name="id2592972"></a>
-<a class="indexterm" name="id2592978"></a>
+<a class="indexterm" name="id2592939"></a>
+<a class="indexterm" name="id2592946"></a>
+<a class="indexterm" name="id2592952"></a>
+<a class="indexterm" name="id2592959"></a>
 		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 require replication of the account
 		database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
 		</p><p>
-<a class="indexterm" name="id2592994"></a>
-<a class="indexterm" name="id2593001"></a>
-<a class="indexterm" name="id2593008"></a>
+<a class="indexterm" name="id2592975"></a>
+<a class="indexterm" name="id2592982"></a>
+<a class="indexterm" name="id2592989"></a>
 		The recommendation of a 250-user limit is purely based on the notion that this
 		would generally involve a site that has routed networks, possibly spread across
 		more than one physical location. The Samba Team has not at this time established
 		the performance-based scalability limits of the tdbsam architecture.
 		</p><p>
-<a class="indexterm" name="id2593024"></a>
-<a class="indexterm" name="id2593031"></a>
-<a class="indexterm" name="id2593038"></a>
-<a class="indexterm" name="id2593044"></a>
+<a class="indexterm" name="id2593004"></a>
+<a class="indexterm" name="id2593011"></a>
+<a class="indexterm" name="id2593018"></a>
+<a class="indexterm" name="id2593025"></a>
 		There are sites that have thousands of users and yet require only one server.
 		One site recently reported having 4,500 user accounts on one UNIX system and
 		reported excellent performance with the <code class="literal">tdbsam</code> passdb backend.
@@ -1167,26 +1167,26 @@ to be removed.
 		is not one pertaining to a limitation in the TDB storage system, it is based
 		only on the need for a reliable distribution mechanism for the SambaSAMAccount
 		backend.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2593073"></a>ldapsam</h3></div></div></div><p>
-<a class="indexterm" name="id2593081"></a>
-<a class="indexterm" name="id2593087"></a>
-		<a class="indexterm" name="id2593094"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2593053"></a>ldapsam</h3></div></div></div><p>
+<a class="indexterm" name="id2593061"></a>
+<a class="indexterm" name="id2593068"></a>
+		<a class="indexterm" name="id2593074"></a>
 		There are a few points to stress that the ldapsam does not provide. The LDAP
 		support referred to in this documentation does not include:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from
 			a Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p>
+<a class="indexterm" name="id2593104"></a>
+<a class="indexterm" name="id2593110"></a>
+<a class="indexterm" name="id2593117"></a>
 <a class="indexterm" name="id2593123"></a>
-<a class="indexterm" name="id2593130"></a>
-<a class="indexterm" name="id2593137"></a>
-<a class="indexterm" name="id2593143"></a>
 		The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be
 		obtained from <a class="ulink" href="http://www.padl.com/" target="_top">PADL Software</a>.  More information about the
 		configuration of these packages may be found in <a class="ulink" href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top">
 		<span class="emphasis"><em>LDAP, System Administration</em></span> by Gerald Carter, Chapter 6, Replacing NIS"</a>.
 		</p><p>
-<a class="indexterm" name="id2593174"></a>
-<a class="indexterm" name="id2593181"></a>
-<a class="indexterm" name="id2593188"></a>
+<a class="indexterm" name="id2593154"></a>
+<a class="indexterm" name="id2593161"></a>
+<a class="indexterm" name="id2593168"></a>
 		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
@@ -1199,28 +1199,28 @@ to be removed.
 				Server</a></p></li></ul></div><p>
 		Two additional Samba resources that may prove to be helpful are:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2593268"></a>
+<a class="indexterm" name="id2593249"></a>
 			The <a class="ulink" 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>
-<a class="indexterm" name="id2593288"></a>
-<a class="indexterm" name="id2593294"></a>
-<a class="indexterm" name="id2593301"></a>
+<a class="indexterm" name="id2593268"></a>
+<a class="indexterm" name="id2593275"></a>
+<a class="indexterm" name="id2593282"></a>
 			The NT migration scripts from <a class="ulink" href="http://samba.idealx.org/" target="_top">IDEALX</a> that are
 			geared to manage users and groups in such a Samba-LDAP domain controller configuration.
 			Idealx also produced the smbldap-tools and the Interactive Console Management tool.
-			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593320"></a>Supported LDAP Servers</h4></div></div></div><p>
-<a class="indexterm" name="id2593328"></a>
-<a class="indexterm" name="id2593335"></a>
-<a class="indexterm" name="id2593342"></a>
-<a class="indexterm" name="id2593349"></a>
+			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593301"></a>Supported LDAP Servers</h4></div></div></div><p>
+<a class="indexterm" name="id2593309"></a>
+<a class="indexterm" name="id2593316"></a>
+<a class="indexterm" name="id2593322"></a>
+<a class="indexterm" name="id2593329"></a>
 			The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x 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 the process outlined in <a class="link" href="bugreport.html" title="Chapter�40.�Reporting Bugs">Reporting Bugs</a>.
 			</p><p>
 			Samba is capable of working with any standards-compliant LDAP server.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593375"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593356"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p>
 			Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the
 			<code class="filename">examples/LDAP/samba.schema</code> directory of the source code distribution
 			tarball. The schema entry for the sambaSamAccount ObjectClass is shown here:
@@ -1236,21 +1236,21 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
           sambaPrimaryGroupSID $ sambaDomainName ))
 </pre><p>
 			</p><p>
-<a class="indexterm" name="id2593412"></a>
-<a class="indexterm" name="id2593418"></a>
-<a class="indexterm" name="id2593425"></a>
+<a class="indexterm" name="id2593392"></a>
+<a class="indexterm" name="id2593399"></a>
+<a class="indexterm" name="id2593406"></a>
 			The <code class="filename">samba.schema</code> file has been formatted for OpenLDAP 2.0/2.1.
 			The Samba Team owns the OID space used by the above schema and recommends its use.
 			If you translate the schema to be used with Netscape DS, please submit the modified
 			schema file as a patch to <a class="ulink" href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>.
 			</p><p>
-<a class="indexterm" name="id2593452"></a>
-<a class="indexterm" name="id2593459"></a>
-<a class="indexterm" name="id2593466"></a>
+<a class="indexterm" name="id2593432"></a>
+<a class="indexterm" name="id2593439"></a>
+<a class="indexterm" name="id2593446"></a>
+<a class="indexterm" name="id2593453"></a>
+<a class="indexterm" name="id2593460"></a>
+<a class="indexterm" name="id2593467"></a>
 <a class="indexterm" name="id2593473"></a>
-<a class="indexterm" name="id2593480"></a>
-<a class="indexterm" name="id2593486"></a>
-<a class="indexterm" name="id2593493"></a>
 			Just as the smbpasswd file is meant to store information that provides information
 			additional to  a user's <code class="filename">/etc/passwd</code> entry, so is the sambaSamAccount
 			object meant to supplement the UNIX user account information. A sambaSamAccount is an
@@ -1259,15 +1259,15 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
 			for Samba account handling. However, there are several fields (e.g., uid) that overlap
 			with the posixAccount ObjectClass outlined in RFC 2307. This is by design.
 			</p><p>
-<a class="indexterm" name="id2593522"></a>
-<a class="indexterm" name="id2593529"></a>
-<a class="indexterm" name="id2593536"></a>
-<a class="indexterm" name="id2593543"></a>
+<a class="indexterm" name="id2593502"></a>
+<a class="indexterm" name="id2593509"></a>
+<a class="indexterm" name="id2593516"></a>
+<a class="indexterm" name="id2593523"></a>
+<a class="indexterm" name="id2593530"></a>
+<a class="indexterm" name="id2593537"></a>
+<a class="indexterm" name="id2593544"></a>
 <a class="indexterm" name="id2593550"></a>
-<a class="indexterm" name="id2593556"></a>
-<a class="indexterm" name="id2593563"></a>
-<a class="indexterm" name="id2593570"></a>
-<a class="indexterm" name="id2593577"></a>
+<a class="indexterm" name="id2593557"></a>
 			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, <code class="literal">smbd</code> will still obtain the user's UNIX account
@@ -1276,11 +1276,11 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
 			and functioning correctly. This division of information makes it possible to
 			store all Samba account information in LDAP, but still maintain UNIX account
 			information in NIS while the network is transitioning to a full LDAP infrastructure.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593602"></a>OpenLDAP Configuration</h4></div></div></div><p>
-<a class="indexterm" name="id2593610"></a>
-<a class="indexterm" name="id2593617"></a>
-<a class="indexterm" name="id2593624"></a>
-<a class="indexterm" name="id2593630"></a>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593582"></a>OpenLDAP Configuration</h4></div></div></div><p>
+<a class="indexterm" name="id2593590"></a>
+<a class="indexterm" name="id2593597"></a>
+<a class="indexterm" name="id2593604"></a>
+<a class="indexterm" name="id2593611"></a>
 		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 <code class="filename">examples/LDAP</code>
@@ -1289,14 +1289,14 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
 <code class="prompt">root# </code><strong class="userinput"><code>cp samba.schema /etc/openldap/schema/</code></strong>
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2593667"></a>
-<a class="indexterm" name="id2593674"></a>
-<a class="indexterm" name="id2593681"></a>
-<a class="indexterm" name="id2593688"></a>
-<a class="indexterm" name="id2593695"></a>
-<a class="indexterm" name="id2593702"></a>
-<a class="indexterm" name="id2593709"></a>
-<a class="indexterm" name="id2593715"></a>
+<a class="indexterm" name="id2593648"></a>
+<a class="indexterm" name="id2593655"></a>
+<a class="indexterm" name="id2593661"></a>
+<a class="indexterm" name="id2593668"></a>
+<a class="indexterm" name="id2593675"></a>
+<a class="indexterm" name="id2593682"></a>
+<a class="indexterm" name="id2593689"></a>
+<a class="indexterm" name="id2593696"></a>
 		Next, include the <code class="filename">samba.schema</code> file in <code class="filename">slapd.conf</code>.
 		The sambaSamAccount object contains two attributes that depend on other schema
 		files. The <em class="parameter"><code>uid</code></em> attribute is defined in <code class="filename">cosine.schema</code> and
@@ -1316,10 +1316,10 @@ include            /etc/openldap/schema/samba.schema
 ....
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2593783"></a>
-<a class="indexterm" name="id2593790"></a>
-<a class="indexterm" name="id2593797"></a>
-<a class="indexterm" name="id2593804"></a>
+<a class="indexterm" name="id2593764"></a>
+<a class="indexterm" name="id2593771"></a>
+<a class="indexterm" name="id2593778"></a>
+<a class="indexterm" name="id2593784"></a>
 		It is recommended that you maintain some indices on some of the most useful attributes,
 		as in the following example, to speed up searches made on sambaSamAccount ObjectClasses
 		(and possibly posixAccount and posixGroup as well):
@@ -1357,11 +1357,11 @@ index   default               sub
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>/etc/init.d/slapd restart</code></strong>
 </pre><p>
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593874"></a>Initialize the LDAP Database</h4></div></div></div><p>
-<a class="indexterm" name="id2593882"></a>
-<a class="indexterm" name="id2593889"></a>
-<a class="indexterm" name="id2593896"></a>
-<a class="indexterm" name="id2593903"></a>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593854"></a>Initialize the LDAP Database</h4></div></div></div><p>
+<a class="indexterm" name="id2593862"></a>
+<a class="indexterm" name="id2593869"></a>
+<a class="indexterm" name="id2593876"></a>
+<a class="indexterm" name="id2593883"></a>
 		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 (DNS entries, and so on):
@@ -1423,15 +1423,15 @@ objectclass: simpleSecurityObject
 userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2593945"></a>
-<a class="indexterm" name="id2593952"></a>
+<a class="indexterm" name="id2593926"></a>
+<a class="indexterm" name="id2593933"></a>
 		The userPassword shown above should be generated using <code class="literal">slappasswd</code>.
 		</p><p>
-<a class="indexterm" name="id2593969"></a>
-<a class="indexterm" name="id2593976"></a>
+<a class="indexterm" name="id2593950"></a>
+<a class="indexterm" name="id2593956"></a>
 		The following command will then load the contents of the LDIF file into the LDAP
 		database.
-<a class="indexterm" name="id2593985"></a>
+<a class="indexterm" name="id2593965"></a>
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>slapadd -v -l initldap.dif</code></strong>
 </pre><p>
@@ -1439,16 +1439,16 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 		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>
-<a class="indexterm" name="id2594017"></a>
+<a class="indexterm" name="id2593997"></a>
 		Before Samba can access the LDAP server, you need to store the LDAP admin password
 		in the Samba-3 <code class="filename">secrets.tdb</code> database by:
-<a class="indexterm" name="id2594032"></a>
+<a class="indexterm" name="id2594012"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -w <em class="replaceable"><code>secret</code></em></code></strong>
 </pre><p>
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594059"></a>Configuring Samba</h4></div></div></div><p>
-<a class="indexterm" name="id2594067"></a>
-<a class="indexterm" name="id2594074"></a>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594040"></a>Configuring Samba</h4></div></div></div><p>
+<a class="indexterm" name="id2594047"></a>
+<a class="indexterm" name="id2594054"></a>
 			The following parameters are available in <code class="filename">smb.conf</code> only if your version of Samba was built with
 			LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The
 			best method to verify that Samba was built with LDAP support is:
@@ -1467,19 +1467,19 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 			that includes <code class="literal">HAVE_LDAP_H</code> it is necessary to discover why the LDAP headers
 			and libraries were not found during compilation.
 			</p><p>LDAP-related smb.conf options include these:
-			</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2594130"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id2594142"></a></td></tr><tr><td><a class="indexterm" name="id2594149"></a></td></tr><tr><td><a class="indexterm" name="id2594156"></a></td></tr><tr><td><a class="indexterm" name="id2594163"></a></td></tr><tr><td><a class="indexterm" name="id2594170"></a></td></tr><tr><td><a class="indexterm" name="id2594177"></a></td></tr><tr><td><a class="indexterm" name="id2594184"></a></td></tr><tr><td><a class="indexterm" name="id2594191"></a></td></tr><tr><td><a class="indexterm" name="id2594198"></a></td></tr><tr><td><a class="indexterm" name="id2594204"></a></td></tr><tr><td><a class="indexterm" name="id2594211"></a></td></tr><tr><td><a class="indexterm" name="id2594218"></a></td></tr><tr><td><a class="indexterm" name="id2594225"></a></td></tr></table><p>
+			</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2594111"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id2594123"></a></td></tr><tr><td><a class="indexterm" name="id2594130"></a></td></tr><tr><td><a class="indexterm" name="id2594137"></a></td></tr><tr><td><a class="indexterm" name="id2594143"></a></td></tr><tr><td><a class="indexterm" name="id2594150"></a></td></tr><tr><td><a class="indexterm" name="id2594157"></a></td></tr><tr><td><a class="indexterm" name="id2594164"></a></td></tr><tr><td><a class="indexterm" name="id2594171"></a></td></tr><tr><td><a class="indexterm" name="id2594178"></a></td></tr><tr><td><a class="indexterm" name="id2594185"></a></td></tr><tr><td><a class="indexterm" name="id2594192"></a></td></tr><tr><td><a class="indexterm" name="id2594199"></a></td></tr><tr><td><a class="indexterm" name="id2594206"></a></td></tr></table><p>
 			</p><p>
 			These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example
 			for use with an LDAP directory is shown in <a class="link" href="passdb.html#confldapex" title="Example�11.2.�Configuration with LDAP">the Configuration with LDAP.</a>
-			</p><div class="example"><a name="confldapex"></a><p class="title"><b>Example�11.2.�Configuration with LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594277"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2594288"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594300"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id2594312"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id2594348"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id2594369"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id2594385"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id2594401"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id2594421"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2594433"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2594445"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td>#  (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id2594470"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594484"></a>Accounts and Groups Management</h4></div></div></div><p>
-			<a class="indexterm" name="id2594492"></a>
-			<a class="indexterm" name="id2594499"></a>
+			</p><div class="example"><a name="confldapex"></a><p class="title"><b>Example�11.2.�Configuration with LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594257"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2594269"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594281"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id2594292"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id2594329"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id2594349"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id2594365"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id2594382"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id2594402"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2594414"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2594426"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td>#  (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id2594450"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594464"></a>Accounts and Groups Management</h4></div></div></div><p>
+			<a class="indexterm" name="id2594472"></a>
+			<a class="indexterm" name="id2594479"></a>
 			Because user accounts are managed through the sambaSamAccount ObjectClass, you should
 			modify your existing administration tools to deal with sambaSamAccount attributes.
 			</p><p>
-<a class="indexterm" name="id2594514"></a>
-<a class="indexterm" name="id2594521"></a>
-<a class="indexterm" name="id2594528"></a>
+<a class="indexterm" name="id2594495"></a>
+<a class="indexterm" name="id2594502"></a>
+<a class="indexterm" name="id2594509"></a>
 			Machine accounts are managed with the sambaSamAccount ObjectClass, just
 			like user accounts. However, it is up to you to store those accounts
 			in a different tree of your LDAP namespace. You should use
@@ -1488,36 +1488,36 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 			NSS and PAM accordingly (usually, in the <code class="filename">/etc/openldap/sldap.conf</code>
 			configuration file).
 			</p><p>
-<a class="indexterm" name="id2594558"></a>
-<a class="indexterm" name="id2594565"></a>
-<a class="indexterm" name="id2594572"></a>
-<a class="indexterm" name="id2594579"></a>
+<a class="indexterm" name="id2594538"></a>
+<a class="indexterm" name="id2594545"></a>
+<a class="indexterm" name="id2594552"></a>
+<a class="indexterm" name="id2594559"></a>
 			In Samba-3, 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). Samba-3 knows only about <code class="constant">Domain Groups</code>
 			and, unlike MS Windows 2000 and Active Directory, Samba-3 does not
 			support nested groups.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594597"></a>Security and sambaSamAccount</h4></div></div></div><p>
-<a class="indexterm" name="id2594605"></a>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594577"></a>Security and sambaSamAccount</h4></div></div></div><p>
+<a class="indexterm" name="id2594585"></a>
 			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 SambaLMPassword or
-<a class="indexterm" name="id2594624"></a>
+<a class="indexterm" name="id2594604"></a>
 				SambaNTPassword 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 SambaLMPassword or SambaNTPassword attribute values.</p></li></ul></div><p>
-<a class="indexterm" name="id2594645"></a>
-<a class="indexterm" name="id2594651"></a>
-<a class="indexterm" name="id2594658"></a>
+<a class="indexterm" name="id2594625"></a>
+<a class="indexterm" name="id2594632"></a>
+<a class="indexterm" name="id2594638"></a>
 			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 <a class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">the
 			Account Information Database section</a>.
 			</p><p>
-<a class="indexterm" name="id2594680"></a>
-<a class="indexterm" name="id2594687"></a>
-<a class="indexterm" name="id2594694"></a>
-<a class="indexterm" name="id2594700"></a>
+<a class="indexterm" name="id2594660"></a>
+<a class="indexterm" name="id2594667"></a>
+<a class="indexterm" name="id2594674"></a>
+<a class="indexterm" name="id2594681"></a>
 			To remedy the first security issue, the <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a> <code class="filename">smb.conf</code>
 			parameter defaults to require an encrypted session (<a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap    ssl = on</a>) using the default port of <code class="constant">636</code> when
 			contacting the directory server. When using an OpenLDAP server, it
@@ -1525,16 +1525,16 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 			In either case, you are strongly encouraged to use secure communications protocols
 			(so do not set <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl = off</a>).
 			</p><p>
-<a class="indexterm" name="id2594762"></a>
-<a class="indexterm" name="id2594768"></a>
-<a class="indexterm" name="id2594775"></a>
+<a class="indexterm" name="id2594742"></a>
+<a class="indexterm" name="id2594748"></a>
+<a class="indexterm" name="id2594755"></a>
 			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>
-<a class="indexterm" name="id2594789"></a>
-<a class="indexterm" name="id2594796"></a>
-<a class="indexterm" name="id2594803"></a>
+<a class="indexterm" name="id2594769"></a>
+<a class="indexterm" name="id2594776"></a>
+<a class="indexterm" name="id2594783"></a>
 			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 <code class="filename">slapd.conf</code>:
@@ -1545,7 +1545,7 @@ access to attrs=SambaLMPassword,SambaNTPassword
      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="id2594833"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table�11.3.�Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table�11.4.�Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>.
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594813"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table�11.3.�Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table�11.4.�Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>.
 			</p><div class="table"><a name="attribobjclPartA"></a><p class="title"><b>Table�11.3.�Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</b></p><div class="table-contents"><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part A" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><code class="constant">sambaLMPassword</code></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"><code class="constant">sambaNTPassword</code></td><td align="justify">The NT password 16-byte hash stored as a character
 						representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaPwdLastSet</code></td><td align="justify">The integer time in seconds since 1970 when the
@@ -1580,16 +1580,16 @@ access to attrs=SambaLMPassword,SambaNTPassword
 				</td></tr><tr><td align="left"><code class="constant">sambaSID</code></td><td align="justify">The security identifier(SID) of the user.
 				The Windows equivalent of UNIX UIDs.</td></tr><tr><td align="left"><code class="constant">sambaPrimaryGroupSID</code></td><td align="justify">The security identifier (SID) of the primary group
 				of the user.</td></tr><tr><td align="left"><code class="constant">sambaDomainName</code></td><td align="justify">Domain the user is part of.</td></tr></tbody></table></div></div><br class="table-break"><p>
-<a class="indexterm" name="id2595181"></a>
-<a class="indexterm" name="id2595188"></a>
+<a class="indexterm" name="id2595161"></a>
+<a class="indexterm" name="id2595168"></a>
 			The majority of these parameters are only used when Samba is acting as a PDC of
 			a domain (refer to <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Domain Control</a>, for details on
 			how to configure Samba as a PDC). The following four attributes
 			are only stored with the sambaSamAccount entry if the values are non-default values:
-			</p><div class="itemizedlist"><a class="indexterm" name="id2595210"></a><a class="indexterm" name="id2595216"></a><a class="indexterm" name="id2595223"></a><a class="indexterm" name="id2595230"></a><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>
-<a class="indexterm" name="id2595259"></a>
-<a class="indexterm" name="id2595266"></a>
-<a class="indexterm" name="id2595273"></a>
+			</p><div class="itemizedlist"><a class="indexterm" name="id2595190"></a><a class="indexterm" name="id2595197"></a><a class="indexterm" name="id2595204"></a><a class="indexterm" name="id2595211"></a><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>
+<a class="indexterm" name="id2595239"></a>
+<a class="indexterm" name="id2595246"></a>
+<a class="indexterm" name="id2595253"></a>
 			These attributes are only stored with the sambaSamAccount entry if
 			the values are non-default values. For example, assume MORIA has now been
 			configured as a PDC and that <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home = \\%L\%u</a> was defined in
@@ -1600,7 +1600,7 @@ access to attrs=SambaLMPassword,SambaNTPassword
 			of the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> 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., <code class="filename">\\MOBY\becky</code>).
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595346"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595327"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p>
 			The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass:
 </p><pre class="programlisting">
 dn: uid=guest2, ou=People,dc=quenya,dc=org
@@ -1645,7 +1645,7 @@ 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="id2595394"></a>Password Synchronization</h4></div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595374"></a>Password Synchronization</h4></div></div></div><p>
 		Samba-3 and later 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="link" href="smb.conf.5.html#LDAPPASSWDSYNC" target="_top">ldap passwd sync</a> options can have the  values shown in
@@ -1654,7 +1654,7 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
 			       and the <code class="constant">password</code> fields.</p></td></tr><tr><td align="left">no</td><td align="justify"><p>Only update <code class="constant">SambaNTPassword</code> and
 					<code class="constant">SambaLMPassword</code>.</p></td></tr><tr><td align="left">only</td><td align="justify"><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 and
-			only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595546"></a>Using OpenLDAP Overlay for Password Synchronization</h4></div></div></div><p>
+			only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595526"></a>Using OpenLDAP Overlay for Password Synchronization</h4></div></div></div><p>
 		Howard Chu has written a special overlay called <code class="literal">smbk5pwd</code>. This tool  modifies the
 		<code class="literal">SambaNTPassword</code>, <code class="literal">SambaLMPassword</code> and <code class="literal">Heimdal</code>
 		hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed.
@@ -1662,8 +1662,8 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
 		The overlay is shipped with OpenLDAP-2.3 and can be found in the
 		<code class="filename">contrib/slapd-modules/smbk5pwd</code> subdirectory. This module can also be used with
 		OpenLDAP-2.2.
-		</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595597"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595603"></a>Users Cannot Logon</h3></div></div></div><p>&#8220;<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>&#8221;</p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>.
-		Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595641"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p>
+		</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595578"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595583"></a>Users Cannot Logon</h3></div></div></div><p>&#8220;<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>&#8221;</p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>.
+		Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools,</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595621"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p>
 	When explicitly setting an <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods</a> parameter,
 	<em class="parameter"><code>guest</code></em> must be specified as the first entry on the line 
 	for example, <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods = guest sam</a>.
diff --git a/docs/htmldocs/Samba3-HOWTO/pr01.html b/docs/htmldocs/Samba3-HOWTO/pr01.html
index 7c8e24e1a5..edb62f9e36 100644
--- a/docs/htmldocs/Samba3-HOWTO/pr01.html
+++ b/docs/htmldocs/Samba3-HOWTO/pr01.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>About the Cover Artwork</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="next" href="pr02.html" title="Attribution"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">About the Cover Artwork</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2500822"></a>About the Cover Artwork</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>About the Cover Artwork</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="next" href="pr02.html" title="Attribution"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">About the Cover Artwork</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a name="id2540388"></a>About the Cover Artwork</h2></div></div></div><p>
 	The cover artwork of this book continues the freedom theme of the first edition of &#8220;<span class="quote">The Official Samba-3
 	HOWTO and Reference Guide</span>&#8221;.  We may look back upon the past to question the motives of those who have
 	gone before us. Seldom do we realise that the past owes us no answer, and despite what we may think of the
@@ -27,4 +27,4 @@
 	deploy and gain mileage from the new enablement, take the time to think through what may lie ahead.
 	Above all, take stock of the freedom of choice that Samba provides in your world, and enjoy the new 
 	potential for seamless interoperability.
-	</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Official Samba 3.5.x HOWTO and Reference Guide�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Attribution</td></tr></table></div></body></html>
+	</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="pr02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Official Samba 3.4.x HOWTO and Reference Guide�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Attribution</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/pr02.html b/docs/htmldocs/Samba3-HOWTO/pr02.html
index bfd549bb33..2961110890 100644
--- a/docs/htmldocs/Samba3-HOWTO/pr02.html
+++ b/docs/htmldocs/Samba3-HOWTO/pr02.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Attribution</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="pr01.html" title="About the Cover Artwork"><link rel="next" href="pr03.html" title="Foreword"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Attribution</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr03.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2500889"></a>Attribution</h2></div></div></div><p><a class="link" href="install.html" title="Chapter�1.�How to Install and Test SAMBA">How to Install and Test SAMBA</a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Attribution</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="pr01.html" title="About the Cover Artwork"><link rel="next" href="pr03.html" title="Foreword"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Attribution</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="pr03.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2500880"></a>Attribution</h2></div></div></div><p><a class="link" href="install.html" title="Chapter�1.�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 class="ulink" href="mailto:tridge@samba.org" target="_top">mailto:tridge@samba.org</a></p></li><li><p>Jelmer R.  Vernooij<a class="ulink" href="mailto:jelmer@samba.org" target="_top">mailto:jelmer@samba.org</a></p></li><li><p>John H.  Terpstra<a class="ulink" href="mailto:jht@samba.org" target="_top">mailto:jht@samba.org</a></p></li><li><p>Karl Auer<a class="ulink" href="mailto:kauer@biplane.com.au" target="_top">mailto:kauer@biplane.com.au</a></p></li><li><p>Dan Shearer<a class="ulink" href="mailto:dan@samba.org" target="_top">mailto:dan@samba.org</a></p></li></ul></div><p>
 </p><p><a class="link" href="FastStart.html" title="Chapter�2.�Fast Start: Cure for Impatience">Fast Start: Cure for Impatience</a>
 	</p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra<a class="ulink" href="mailto:jht@samba.org" target="_top">mailto:jht@samba.org</a></p></li></ul></div><p>
diff --git a/docs/htmldocs/Samba3-HOWTO/pr03.html b/docs/htmldocs/Samba3-HOWTO/pr03.html
index e0e73db778..b3fe6c51e6 100644
--- a/docs/htmldocs/Samba3-HOWTO/pr03.html
+++ b/docs/htmldocs/Samba3-HOWTO/pr03.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Foreword</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="pr02.html" title="Attribution"><link rel="next" href="TOSHpreface.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Foreword</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr02.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="TOSHpreface.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2550920"></a>Foreword</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Foreword</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="pr02.html" title="Attribution"><link rel="next" href="TOSHpreface.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Foreword</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr02.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="TOSHpreface.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2550916"></a>Foreword</h2></div></div></div><p>
 When John first asked me to write an introductory piece for his latest book, I was somewhat mystified as to
 why he chose me. A conversation with John provided some of the rationale, and he left it to me to fill in the
 <span class="emphasis"><em>rest</em></span> of the story. So, if you are willing to endure a little bit of background, I will
diff --git a/docs/htmldocs/Samba3-HOWTO/problems.html b/docs/htmldocs/Samba3-HOWTO/problems.html
index e94ead41d5..61972a776e 100644
--- a/docs/htmldocs/Samba3-HOWTO/problems.html
+++ b/docs/htmldocs/Samba3-HOWTO/problems.html
@@ -1,40 +1,40 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�39.�Analyzing and Solving Samba Problems</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="diagnosis.html" title="Chapter�38.�The Samba Checklist"><link rel="next" href="bugreport.html" title="Chapter�40.�Reporting Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�39.�Analyzing and Solving Samba Problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="bugreport.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter�39.�Analyzing and Solving Samba Problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="orgname">Samba Team</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="problems.html#id2684689">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684741">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2684997">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685047">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685190">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685523">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685560">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685735">How to Get Off the Mailing Lists</a></span></dt></dl></div><p>
-<a class="indexterm" name="id2684663"></a>
-<a class="indexterm" name="id2684670"></a>
-<a class="indexterm" name="id2684676"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�39.�Analyzing and Solving Samba Problems</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="diagnosis.html" title="Chapter�38.�The Samba Checklist"><link rel="next" href="bugreport.html" title="Chapter�40.�Reporting Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�39.�Analyzing and Solving Samba Problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="bugreport.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter�39.�Analyzing and Solving Samba Problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="orgname">Samba Team</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="problems.html#id2684851">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684903">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685159">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685209">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685353">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685678">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685716">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685890">How to Get Off the Mailing Lists</a></span></dt></dl></div><p>
+<a class="indexterm" name="id2684825"></a>
+<a class="indexterm" name="id2684832"></a>
+<a class="indexterm" name="id2684838"></a>
 There are many sources of information available in the form of mailing lists, RFCs, and documentation. The
 documentation that comes with the Samba distribution contains good explanations of general SMB topics such as
 browsing.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2684689"></a>Diagnostics Tools</h2></div></div></div><p>
-<a class="indexterm" name="id2684696"></a>
-<a class="indexterm" name="id2684703"></a>
-<a class="indexterm" name="id2684710"></a>
-<a class="indexterm" name="id2684717"></a>
-<a class="indexterm" name="id2684724"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2684851"></a>Diagnostics Tools</h2></div></div></div><p>
+<a class="indexterm" name="id2684859"></a>
+<a class="indexterm" name="id2684866"></a>
+<a class="indexterm" name="id2684872"></a>
+<a class="indexterm" name="id2684879"></a>
+<a class="indexterm" name="id2684886"></a>
 With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself
 provides rather useful information, but in some cases you might have to fall back to using a
 <span class="emphasis"><em>sniffer</em></span>. A sniffer is a program that listens on your LAN, analyzes the data sent on it,
 and displays it on the screen.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2684741"></a>Debugging with Samba Itself</h3></div></div></div><p>
-<a class="indexterm" name="id2684749"></a>
-<a class="indexterm" name="id2684756"></a>
-<a class="indexterm" name="id2684762"></a>
-<a class="indexterm" name="id2684769"></a>
-<a class="indexterm" name="id2684776"></a>
-<a class="indexterm" name="id2684783"></a>
-<a class="indexterm" name="id2684790"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2684903"></a>Debugging with Samba Itself</h3></div></div></div><p>
+<a class="indexterm" name="id2684911"></a>
+<a class="indexterm" name="id2684918"></a>
+<a class="indexterm" name="id2684925"></a>
+<a class="indexterm" name="id2684932"></a>
+<a class="indexterm" name="id2684938"></a>
+<a class="indexterm" name="id2684945"></a>
+<a class="indexterm" name="id2684952"></a>
 One of the best diagnostic tools for debugging problems is Samba itself.  You can use the <code class="option">-d
 option</code> for both <span class="application">smbd</span> and <span class="application">nmbd</span> to specify the <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debug level</a> at which to run.
 See the man pages for <code class="literal">smbd, nmbd</code>, and <code class="filename">smb.conf</code> for more information regarding debugging
 options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords).
 </p><p>
-<a class="indexterm" name="id2684844"></a>
-<a class="indexterm" name="id2684851"></a>
-<a class="indexterm" name="id2684858"></a>
-<a class="indexterm" name="id2684865"></a>
-<a class="indexterm" name="id2684872"></a>
-<a class="indexterm" name="id2684878"></a>
-<a class="indexterm" name="id2684885"></a>
+<a class="indexterm" name="id2685006"></a>
+<a class="indexterm" name="id2685013"></a>
+<a class="indexterm" name="id2685020"></a>
+<a class="indexterm" name="id2685027"></a>
+<a class="indexterm" name="id2685034"></a>
+<a class="indexterm" name="id2685041"></a>
+<a class="indexterm" name="id2685048"></a>
 Another helpful method of debugging is to compile Samba using the <code class="literal">gcc -g </code> flag. This will
 include debug information in the binaries and allow you to attach <code class="literal">gdb</code> to the running
 <code class="literal">smbd/nmbd</code> process.  To attach <code class="literal">gdb</code> to an <code class="literal">smbd</code> process
@@ -46,52 +46,52 @@ between pressing <code class="literal">ctrl-alt-delete</code> and actually typin
 <code class="literal">gdb</code> and continue.
 </p><p>
 Some useful Samba commands worth investigating are:
-<a class="indexterm" name="id2684954"></a>
-<a class="indexterm" name="id2684961"></a>
+<a class="indexterm" name="id2685117"></a>
+<a class="indexterm" name="id2685123"></a>
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>testparm | more</code></strong>
 <code class="prompt">$ </code><strong class="userinput"><code>smbclient -L //{netbios name of server}</code></strong>
 </pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2684997"></a>Tcpdump</h3></div></div></div><p>
-<a class="indexterm" name="id2685004"></a>
-<a class="indexterm" name="id2685011"></a>
-<a class="indexterm" name="id2685018"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685159"></a>Tcpdump</h3></div></div></div><p>
+<a class="indexterm" name="id2685167"></a>
+<a class="indexterm" name="id2685173"></a>
+<a class="indexterm" name="id2685180"></a>
 <a class="ulink" href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first 
 UNIX sniffer with SMB support. It is a command-line utility and 
 now, its SMB support is somewhat lagging that of <code class="literal">ethereal</code> 
 and <code class="literal">tethereal</code>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685047"></a>Ethereal</h3></div></div></div><p>
-<a class="indexterm" name="id2685055"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685209"></a>Ethereal</h3></div></div></div><p>
+<a class="indexterm" name="id2685217"></a>
 <a class="ulink" href="http://www.ethereal.com/" target="_top">Ethereal</a> is a graphical sniffer, available for both UNIX (Gtk)
 and Windows. Ethereal's SMB support is quite good. For details on the use of <code class="literal">ethereal</code>, read
 the well-written Ethereal User Guide.
 </p><div class="figure"><a name="ethereal1"></a><p class="title"><b>Figure�39.1.�Starting a Capture.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ethereal1.png" alt="Starting a Capture."></div></div></div><br class="figure-break"><p>
-<a class="indexterm" name="id2685118"></a>
+<a class="indexterm" name="id2685280"></a>
 Listen for data on ports 137, 138, 139, and 445. For example, use the filter <strong class="userinput"><code>port 137, port 138,
 port 139, or port 445</code></strong> as seen in <a class="link" href="problems.html#ethereal1" title="Figure�39.1.�Starting a Capture.">Starting a Capture</a> snapshot.
 </p><p>
 A console version of ethereal is available as well and is called <code class="literal">tethereal</code>.
-</p><div class="figure"><a name="ethereal2"></a><p class="title"><b>Figure�39.2.�Main Ethereal Data Window.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ethereal2.png" alt="Main Ethereal Data Window."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685190"></a>The Windows Network Monitor</h3></div></div></div><p>
-<a class="indexterm" name="id2685198"></a>
-<a class="indexterm" name="id2685205"></a>
-<a class="indexterm" name="id2685212"></a>
-<a class="indexterm" name="id2685219"></a>
-<a class="indexterm" name="id2685226"></a>
-<a class="indexterm" name="id2685233"></a>
+</p><div class="figure"><a name="ethereal2"></a><p class="title"><b>Figure�39.2.�Main Ethereal Data Window.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ethereal2.png" alt="Main Ethereal Data Window."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685353"></a>The Windows Network Monitor</h3></div></div></div><p>
+<a class="indexterm" name="id2685361"></a>
+<a class="indexterm" name="id2685368"></a>
+<a class="indexterm" name="id2685374"></a>
+<a class="indexterm" name="id2685382"></a>
+<a class="indexterm" name="id2685388"></a>
+<a class="indexterm" name="id2685395"></a>
 For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer
 Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS
 allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous
 mode).  The version on the NT Server install CD will only allow monitoring of network traffic directed to the
 local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted
 files.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685250"></a>Installing Network Monitor on an NT Workstation</h4></div></div></div><p>
-<a class="indexterm" name="id2685258"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685412"></a>Installing Network Monitor on an NT Workstation</h4></div></div></div><p>
+<a class="indexterm" name="id2685420"></a>
 Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for
 installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
 Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will
 need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
 </p><p>
-<a class="indexterm" name="id2685282"></a>
+<a class="indexterm" name="id2685437"></a>
 Initially you will need to install <span class="application">Network Monitor Tools and Agent</span>
 on the NT Server to do this: 
 </p><div class="itemizedlist"><ul type="disc"><li><p>Go to <span class="guibutton">Start</span> -&gt; <span class="guibutton">Settings</span> -&gt; <span class="guibutton">Control Panel</span> -&gt; 
@@ -110,16 +110,16 @@ Network  Monitor Agent from the Workstation install CD.
 Now copy the files from the NT Server in <code class="filename">%SYSTEMROOT%\System32\netmon</code>
 to <code class="filename">%SYSTEMROOT%\System32\netmon</code> on the workstation and set permissions
 as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685500"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685655"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div></div><p>
 To install Netmon on Windows 9x/Me, install the Network Monitor Agent 
 from the Windows 9x/Me CD (<code class="filename">\admin\nettools\netmon</code>). 
 There is a readme file included with the Netmon driver files on the CD if you need 
 information on how to do this. Copy the files from a working Netmon installation.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685523"></a>Useful URLs</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at 
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685678"></a>Useful URLs</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at 
        <a class="ulink" href="http://www.skippy.net/linux/smb-howto.html" target="_top">
        http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>FTP site for older SMB specs, 
        <a class="ulink" href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top">
-       ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685560"></a>Getting Mailing List Help</h2></div></div></div><p>
+       ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685716"></a>Getting Mailing List Help</h2></div></div></div><p>
 There are a number of Samba-related mailing lists. Go to <a class="ulink" href="http://samba.org" target="_top">http://samba.org</a>, click on your nearest mirror,
 and then click on <code class="literal">Support</code>. Next, click on <code class="literal">
 Samba-related mailing lists</code>.
@@ -130,12 +130,12 @@ It has been requested that you do not post questions about Samba-TNG to the
 mainstream Samba lists.</p><p>
 If you do post a message to one of the lists, please observe the following guidelines:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2685616"></a>
+<a class="indexterm" name="id2685771"></a>
 	Always remember that the developers are volunteers; they are
 	not paid and they never guarantee to produce a particular feature at 
 	a particular time. Any timelines are &#8220;<span class="quote">best guess,</span>&#8221; and nothing more.
 	</p></li><li><p>
-<a class="indexterm" name="id2685634"></a>
+<a class="indexterm" name="id2685789"></a>
 	Always mention what version of Samba you are using and what 
 	operating system it's running under. You should list the relevant sections of
 	your <code class="filename">smb.conf</code> file, at least the options in <em class="parameter"><code>[global]</code></em>
@@ -150,7 +150,7 @@ If you do post a message to one of the lists, please observe the following guide
 	to mailing lists really irritate the thousands of people who end up having to deal
 	with such bad netiquet bahavior.
 	</p></li><li><p>
-<a class="indexterm" name="id2685687"></a>
+<a class="indexterm" name="id2685842"></a>
 	Don't cross post. Work out which is the best list to post to 
 	and see what happens. Do not post to both samba-ntdom and samba-technical.
 	Many people active on the lists subscribe to more 
@@ -163,7 +163,7 @@ If you do post a message to one of the lists, please observe the following guide
 	the pipe to the error), you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email.
 	Consider pasting the relevant parts into the body of the message. The Samba
 	mailing lists go to a huge number of people. Do they all need a copy of your 
-	<code class="filename">smb.conf</code> in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685735"></a>How to Get Off the Mailing Lists</h2></div></div></div><p>To have your name removed from a Samba mailing list, go to the same
+	<code class="filename">smb.conf</code> in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685890"></a>How to Get Off the Mailing Lists</h2></div></div></div><p>To have your name removed from a Samba mailing list, go to the same
 place where you went to
 subscribe to it, go to <a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>, 
 click on your nearest mirror, click on <code class="literal">Support</code>, and 
diff --git a/docs/htmldocs/Samba3-HOWTO/rights.html b/docs/htmldocs/Samba3-HOWTO/rights.html
index df4d94b3bf..559e4ee87c 100644
--- a/docs/htmldocs/Samba3-HOWTO/rights.html
+++ b/docs/htmldocs/Samba3-HOWTO/rights.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�User Rights and Privileges</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="idmapper.html" title="Chapter�14.�Identity Mapping (IDMAP)"><link rel="next" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�User Rights and Privileges</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="idmapper.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="AccessControls.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rights"></a>Chapter�15.�User Rights and Privileges</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="rights.html#id2608440">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608715">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609060">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609370">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609882">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610059">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610064">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></div><p>
-<a class="indexterm" name="id2608156"></a>
-<a class="indexterm" name="id2608163"></a>
-<a class="indexterm" name="id2608170"></a>
-<a class="indexterm" name="id2608177"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�15.�User Rights and Privileges</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="idmapper.html" title="Chapter�14.�Identity Mapping (IDMAP)"><link rel="next" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�15.�User Rights and Privileges</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="idmapper.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="AccessControls.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rights"></a>Chapter�15.�User Rights and Privileges</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="rights.html#id2608437">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2608712">Using the net rpc rights Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609058">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id2609373">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id2609884">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id2610061">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id2610067">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></div><p>
+<a class="indexterm" name="id2608145"></a>
+<a class="indexterm" name="id2608152"></a>
+<a class="indexterm" name="id2608159"></a>
+<a class="indexterm" name="id2608166"></a>
 The administration of Windows user, group, and machine accounts in the Samba
 domain-controlled network necessitates interfacing between the MS Windows
 networking environment and the UNIX operating system environment. The right
@@ -10,21 +10,21 @@ networking environment and the UNIX operating system environment. The right
 (set) to non-administrative users both in Windows NT4 domains and
 Active Directory domains.
 </p><p>
-<a class="indexterm" name="id2608193"></a>
-<a class="indexterm" name="id2608200"></a>
-<a class="indexterm" name="id2608207"></a>
-<a class="indexterm" name="id2608214"></a>
+<a class="indexterm" name="id2608182"></a>
+<a class="indexterm" name="id2608189"></a>
+<a class="indexterm" name="id2608196"></a>
+<a class="indexterm" name="id2608203"></a>
 The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the
 creation of a machine account for each machine added. The machine account is
 a necessity that is used to validate that the machine can be trusted to permit
 user logons.
 </p><p>
-<a class="indexterm" name="id2608228"></a>
-<a class="indexterm" name="id2608235"></a>
-<a class="indexterm" name="id2608242"></a>
-<a class="indexterm" name="id2608249"></a>
-<a class="indexterm" name="id2608256"></a>
-<a class="indexterm" name="id2608263"></a>
+<a class="indexterm" name="id2608217"></a>
+<a class="indexterm" name="id2608224"></a>
+<a class="indexterm" name="id2608231"></a>
+<a class="indexterm" name="id2608238"></a>
+<a class="indexterm" name="id2608245"></a>
+<a class="indexterm" name="id2608252"></a>
 Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is
 hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account.
 Machine accounts differ from  normal user accounts in that the account name (login ID) is terminated with a
@@ -34,11 +34,11 @@ log into the UNIX environment as a system user and therefore is set to have a sh
 account is used only to authenticate domain member machines during start-up. This security measure
 is designed to block man-in-the-middle attempts to violate network integrity.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2608303"></a>
-<a class="indexterm" name="id2608310"></a>
-<a class="indexterm" name="id2608317"></a>
-<a class="indexterm" name="id2608324"></a>
-<a class="indexterm" name="id2608331"></a>
+<a class="indexterm" name="id2608292"></a>
+<a class="indexterm" name="id2608299"></a>
+<a class="indexterm" name="id2608306"></a>
+<a class="indexterm" name="id2608313"></a>
+<a class="indexterm" name="id2608320"></a>
 Machine (computer) accounts are used in the Windows NT OS family to store security
 credentials for domain member servers and workstations. When the domain member
 starts up, it goes through a validation process that includes an exchange of
@@ -47,20 +47,20 @@ using the credentials known for it by domain controllers, the machine will be re
 all access by domain users. The computer account is essential to the way that MS 
 Windows secures authentication.
 </p></div><p>
-<a class="indexterm" name="id2608350"></a>
-<a class="indexterm" name="id2608357"></a>
-<a class="indexterm" name="id2608364"></a>
-<a class="indexterm" name="id2608371"></a>
+<a class="indexterm" name="id2608348"></a>
+<a class="indexterm" name="id2608355"></a>
+<a class="indexterm" name="id2608362"></a>
+<a class="indexterm" name="id2608369"></a>
 The creation of UNIX system accounts has traditionally been the sole right of
 the system administrator, better known as the <code class="constant">root</code> account.
 It is possible in the UNIX environment to create multiple users who have the
 same UID. Any UNIX user who has a UID=0 is inherently the same as the
 <code class="constant">root</code> account user.
 </p><p>
-<a class="indexterm" name="id2608393"></a>
-<a class="indexterm" name="id2608400"></a>
-<a class="indexterm" name="id2608407"></a>
-<a class="indexterm" name="id2608414"></a>
+<a class="indexterm" name="id2608391"></a>
+<a class="indexterm" name="id2608398"></a>
+<a class="indexterm" name="id2608405"></a>
+<a class="indexterm" name="id2608412"></a>
 All versions of Samba call system interface scripts that permit CIFS function
 calls that are used to manage users, groups, and machine accounts
 in the UNIX environment. All versions of Samba up to and including version 3.0.10
@@ -70,27 +70,27 @@ interface scripts. The requirement to do this has understandably met with some
 disdain and consternation among Samba administrators, particularly where it became
 necessary to permit people who should not possess <code class="constant">root</code>-level
 access to the UNIX host system.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608440"></a>Rights Management Capabilities</h2></div></div></div><p>
-<a class="indexterm" name="id2608448"></a>
-<a class="indexterm" name="id2608455"></a>
-<a class="indexterm" name="id2608462"></a>
-<a class="indexterm" name="id2608469"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608437"></a>Rights Management Capabilities</h2></div></div></div><p>
+<a class="indexterm" name="id2608445"></a>
+<a class="indexterm" name="id2608452"></a>
+<a class="indexterm" name="id2608459"></a>
+<a class="indexterm" name="id2608466"></a>
 Samba 3.0.11 introduced support for the Windows privilege model.  This model
 allows certain rights to be assigned to a user or group SID.  In order to enable
 this feature, <a class="link" href="smb.conf.5.html#ENABLEPRIVILEGES" target="_top">enable privileges = yes</a>
 must be defined in the <em class="parameter"><code>global</code></em> section of the <code class="filename">smb.conf</code> file.
 </p><p>
-<a class="indexterm" name="id2608507"></a>
-<a class="indexterm" name="id2608514"></a>
-<a class="indexterm" name="id2608521"></a>
+<a class="indexterm" name="id2608505"></a>
+<a class="indexterm" name="id2608512"></a>
+<a class="indexterm" name="id2608518"></a>
 Currently, the rights supported in Samba-3 are listed in <a class="link" href="rights.html#rp-privs" title="Table�15.1.�Current Privilege Capabilities">&#8220;Current Privilege Capabilities&#8221;</a>.
 The remainder of this chapter explains how to manage and use these privileges on Samba servers.
-</p><a class="indexterm" name="id2608538"></a><a class="indexterm" name="id2608545"></a><a class="indexterm" name="id2608552"></a><a class="indexterm" name="id2608559"></a><a class="indexterm" name="id2608566"></a><a class="indexterm" name="id2608573"></a><div class="table"><a name="rp-privs"></a><p class="title"><b>Table�15.1.�Current Privilege Capabilities</b></p><div class="table-contents"><table summary="Current Privilege Capabilities" border="1"><colgroup><col align="right"><col align="left"></colgroup><thead><tr><th align="left">Privilege</th><th align="left">Description</th></tr></thead><tbody><tr><td align="right"><p>SeMachineAccountPrivilege</p></td><td align="left"><p>Add machines to domain</p></td></tr><tr><td align="right"><p>SePrintOperatorPrivilege</p></td><td align="left"><p>Manage printers</p></td></tr><tr><td align="right"><p>SeAddUsersPrivilege</p></td><td align="left"><p>Add users and groups to the domain</p></td></tr><tr><td align="right"><p>SeRemoteShutdownPrivilege</p></td><td align="left"><p>Force shutdown from a remote system</p></td></tr><tr><td align="right"><p>SeDiskOperatorPrivilege</p></td><td align="left"><p>Manage disk share</p></td></tr><tr><td align="right"><p>SeTakeOwnershipPrivilege</p></td><td align="left"><p>Take ownership of files or other objects</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608715"></a>Using the &#8220;<span class="quote">net rpc rights</span>&#8221; Utility</h3></div></div></div><p>
-<a class="indexterm" name="id2608726"></a>
-<a class="indexterm" name="id2608733"></a>
-<a class="indexterm" name="id2608740"></a>
-<a class="indexterm" name="id2608747"></a>
-<a class="indexterm" name="id2608754"></a>
+</p><a class="indexterm" name="id2608536"></a><a class="indexterm" name="id2608543"></a><a class="indexterm" name="id2608550"></a><a class="indexterm" name="id2608557"></a><a class="indexterm" name="id2608564"></a><a class="indexterm" name="id2608571"></a><div class="table"><a name="rp-privs"></a><p class="title"><b>Table�15.1.�Current Privilege Capabilities</b></p><div class="table-contents"><table summary="Current Privilege Capabilities" border="1"><colgroup><col align="right"><col align="left"></colgroup><thead><tr><th align="left">Privilege</th><th align="left">Description</th></tr></thead><tbody><tr><td align="right"><p>SeMachineAccountPrivilege</p></td><td align="left"><p>Add machines to domain</p></td></tr><tr><td align="right"><p>SePrintOperatorPrivilege</p></td><td align="left"><p>Manage printers</p></td></tr><tr><td align="right"><p>SeAddUsersPrivilege</p></td><td align="left"><p>Add users and groups to the domain</p></td></tr><tr><td align="right"><p>SeRemoteShutdownPrivilege</p></td><td align="left"><p>Force shutdown from a remote system</p></td></tr><tr><td align="right"><p>SeDiskOperatorPrivilege</p></td><td align="left"><p>Manage disk share</p></td></tr><tr><td align="right"><p>SeTakeOwnershipPrivilege</p></td><td align="left"><p>Take ownership of files or other objects</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608712"></a>Using the &#8220;<span class="quote">net rpc rights</span>&#8221; Utility</h3></div></div></div><p>
+<a class="indexterm" name="id2608723"></a>
+<a class="indexterm" name="id2608730"></a>
+<a class="indexterm" name="id2608737"></a>
+<a class="indexterm" name="id2608744"></a>
+<a class="indexterm" name="id2608752"></a>
 There are two primary means of managing the rights assigned to users and groups
 on a Samba server.  The <code class="literal">NT4 User Manager for Domains</code> may be
 used from any Windows NT4, 2000, or XP Professional domain member client to
@@ -101,10 +101,10 @@ performing the necessary administrative actions.
 </p><p>
 The <code class="literal">net rpc rights</code> utility in Samba 3.0.11 has three new subcommands:
 </p><div class="variablelist"><dl><dt><span class="term">list [name|accounts]</span></dt><dd><p>
-<a class="indexterm" name="id2608797"></a>
-<a class="indexterm" name="id2608808"></a>
-<a class="indexterm" name="id2608815"></a>
-<a class="indexterm" name="id2608822"></a>
+<a class="indexterm" name="id2608794"></a>
+<a class="indexterm" name="id2608805"></a>
+<a class="indexterm" name="id2608812"></a>
+<a class="indexterm" name="id2608819"></a>
 		When called with no arguments, <code class="literal">net rpc list</code>
 		simply lists the available rights on the server.  When passed
 		a specific user or group name, the tool lists the privileges
@@ -113,10 +113,10 @@ The <code class="literal">net rpc rights</code> utility in Samba 3.0.11 has thre
 		<code class="literal">net rpc rights list</code> returns a list of all
 		privileged accounts on the server and the assigned rights.
 		</p></dd><dt><span class="term">grant &lt;user&gt; &lt;right [right ...]&gt;</span></dt><dd><p>
-<a class="indexterm" name="id2608861"></a>
-<a class="indexterm" name="id2608868"></a>
-<a class="indexterm" name="id2608875"></a>
-<a class="indexterm" name="id2608882"></a>
+<a class="indexterm" name="id2608858"></a>
+<a class="indexterm" name="id2608865"></a>
+<a class="indexterm" name="id2608872"></a>
+<a class="indexterm" name="id2608879"></a>
 		When called with no arguments, this function is used to assign
 		a list of rights to a specified user or group.  For example,
 		to grant the members of the Domain Admins group on a Samba domain controller,
@@ -126,7 +126,7 @@ The <code class="literal">net rpc rights</code> utility in Samba 3.0.11 has thre
 	 'DOMAIN\Domain Admins' SeMachineAccountPrivilege
 </pre><p>
 		The following syntax has the same result:
-<a class="indexterm" name="id2608908"></a>
+<a class="indexterm" name="id2608905"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> net rpc rights grant 'DOMAIN\Domain Admins' \
      SeMachineAccountPrivilege -S server -U domadmin
@@ -139,66 +139,66 @@ The <code class="literal">net rpc rights</code> utility in Samba 3.0.11 has thre
 		This command is similar in format to <code class="literal">net rpc rights grant</code>.  Its
 		effect is to remove an assigned right (or list of rights) from a user or group.
 		</p></dd></dl></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2608962"></a>
-<a class="indexterm" name="id2608969"></a>
-<a class="indexterm" name="id2608976"></a>
+<a class="indexterm" name="id2608960"></a>
+<a class="indexterm" name="id2608967"></a>
+<a class="indexterm" name="id2608974"></a>
 You must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned
 to an account.  This capability is inherent to the Domain Admins group and is not configurable. There are no
 default rights and privileges, except the ability for a member of the Domain Admins group to assign them.
 This means that all administrative rights and privileges (other than the ability to assign them) must be 
 explicitly assigned, even for the Domain Admins group.
 </p></div><p>
-<a class="indexterm" name="id2608995"></a>
-<a class="indexterm" name="id2609002"></a>
-<a class="indexterm" name="id2609008"></a>
-<a class="indexterm" name="id2609015"></a>
+<a class="indexterm" name="id2608992"></a>
+<a class="indexterm" name="id2608999"></a>
+<a class="indexterm" name="id2609006"></a>
+<a class="indexterm" name="id2609013"></a>
 By default, no privileges are initially assigned to any account because certain actions will be performed as
 root once smbd determines that a user has the necessary rights.  For example, when joining a client to a
 Windows domain, <em class="parameter"><code>add machine script</code></em> must be executed with superuser rights in most 
 cases.  For this reason, you should be very careful about handing out privileges to accounts.
 </p><p>
-<a class="indexterm" name="id2609036"></a>
-<a class="indexterm" name="id2609043"></a>
-<a class="indexterm" name="id2609050"></a>
+<a class="indexterm" name="id2609034"></a>
+<a class="indexterm" name="id2609041"></a>
+<a class="indexterm" name="id2609048"></a>
 Access as the root user (UID=0) bypasses all privilege checks.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2609060"></a>Description of Privileges</h3></div></div></div><p>
-<a class="indexterm" name="id2609068"></a>
-<a class="indexterm" name="id2609075"></a>
-<a class="indexterm" name="id2609082"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2609058"></a>Description of Privileges</h3></div></div></div><p>
+<a class="indexterm" name="id2609066"></a>
+<a class="indexterm" name="id2609073"></a>
+<a class="indexterm" name="id2609080"></a>
 The privileges that have been implemented in Samba-3.0.11 are shown below.  It is possible, and likely, that
 additional privileges may be implemented in later releases of Samba. It is also likely that any privileges
 currently implemented but not used may be removed from future releases as a housekeeping matter, so it is
 important that the successful as well as unsuccessful use of these facilities should be reported on the Samba
 mailing lists.
 </p><div class="variablelist"><dl><dt><span class="term">SeAddUsersPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609108"></a>
-<a class="indexterm" name="id2609115"></a>
-<a class="indexterm" name="id2609122"></a>
+<a class="indexterm" name="id2609105"></a>
+<a class="indexterm" name="id2609112"></a>
+<a class="indexterm" name="id2609119"></a>
 		This right determines whether or not smbd will allow the
 		user to create new user or group accounts via such tools
 		as <code class="literal">net rpc user add</code> or 
 		<code class="literal">NT4 User Manager for Domains.</code>
 		</p></dd><dt><span class="term">SeDiskOperatorPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609153"></a>
-<a class="indexterm" name="id2609160"></a>
-<a class="indexterm" name="id2609167"></a>
+<a class="indexterm" name="id2609151"></a>
+<a class="indexterm" name="id2609158"></a>
+<a class="indexterm" name="id2609165"></a>
 		Accounts that possess this right will be able to execute
 		scripts defined by the <code class="literal">add/delete/change</code>
 		share command in <code class="filename">smb.conf</code> file as root.  Such users will
 		also be able to modify the ACL associated with file shares
 		on the Samba server.
 		</p></dd><dt><span class="term">SeMachineAccountPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609200"></a>
-<a class="indexterm" name="id2609207"></a>
-<a class="indexterm" name="id2609214"></a>
+<a class="indexterm" name="id2609197"></a>
+<a class="indexterm" name="id2609204"></a>
+<a class="indexterm" name="id2609211"></a>
 		This right controls whether or not the user can join client
 		machines to a Samba-controlled domain.
 		</p></dd><dt><span class="term">SePrintOperatorPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609233"></a>
-<a class="indexterm" name="id2609240"></a>
-<a class="indexterm" name="id2609247"></a>
-<a class="indexterm" name="id2609254"></a>
-<a class="indexterm" name="id2609261"></a>
+<a class="indexterm" name="id2609230"></a>
+<a class="indexterm" name="id2609237"></a>
+<a class="indexterm" name="id2609244"></a>
+<a class="indexterm" name="id2609251"></a>
+<a class="indexterm" name="id2609258"></a>
 		This privilege operates identically to the <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a>
 		option in the <code class="filename">smb.conf</code> file (see section 5 man page for <code class="filename">smb.conf</code>)
 		except that it is a global right (not on a per-printer basis). 
@@ -207,44 +207,44 @@ mailing lists.
 		the security descriptor associated with the printer object in the
 		<code class="filename">ntprinters.tdb</code> file.
 		</p></dd><dt><span class="term">SeRemoteShutdownPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609315"></a>
-<a class="indexterm" name="id2609322"></a>
-<a class="indexterm" name="id2609329"></a>
+<a class="indexterm" name="id2609312"></a>
+<a class="indexterm" name="id2609319"></a>
+<a class="indexterm" name="id2609326"></a>
 		Samba provides two hooks for shutting down or rebooting
 		the server and for aborting a previously issued shutdown
 		command.  Since this is an operation normally limited by
 		the operating system to the root user, an account must possess this
 		right to be able to execute either of these hooks.
 		</p></dd><dt><span class="term">SeTakeOwnershipPrivilege</span></dt><dd><p>
-<a class="indexterm" name="id2609351"></a>
-<a class="indexterm" name="id2609358"></a>
+<a class="indexterm" name="id2609353"></a>
+<a class="indexterm" name="id2609360"></a>
 		This right permits users to take ownership of files and directories.
-		</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2609370"></a>Privileges Suppored by Windows 2000 Domain Controllers</h3></div></div></div><p>
+		</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2609373"></a>Privileges Suppored by Windows 2000 Domain Controllers</h3></div></div></div><p>
     For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following
 	privileges:
-<a class="indexterm" name="id2609381"></a>
-<a class="indexterm" name="id2609388"></a>
-<a class="indexterm" name="id2609395"></a>
-<a class="indexterm" name="id2609402"></a>
-<a class="indexterm" name="id2609410"></a>
-<a class="indexterm" name="id2609417"></a>
-<a class="indexterm" name="id2609424"></a>
-<a class="indexterm" name="id2609430"></a>
-<a class="indexterm" name="id2609438"></a>
-<a class="indexterm" name="id2609445"></a>
-<a class="indexterm" name="id2609452"></a>
-<a class="indexterm" name="id2609459"></a>
-<a class="indexterm" name="id2609466"></a>
-<a class="indexterm" name="id2609473"></a>
-<a class="indexterm" name="id2609480"></a>
-<a class="indexterm" name="id2609487"></a>
-<a class="indexterm" name="id2609494"></a>
-<a class="indexterm" name="id2609501"></a>
-<a class="indexterm" name="id2609508"></a>
-<a class="indexterm" name="id2609515"></a>
-<a class="indexterm" name="id2609522"></a>
-<a class="indexterm" name="id2609529"></a>
-<a class="indexterm" name="id2609536"></a>
+<a class="indexterm" name="id2609384"></a>
+<a class="indexterm" name="id2609391"></a>
+<a class="indexterm" name="id2609398"></a>
+<a class="indexterm" name="id2609405"></a>
+<a class="indexterm" name="id2609412"></a>
+<a class="indexterm" name="id2609419"></a>
+<a class="indexterm" name="id2609426"></a>
+<a class="indexterm" name="id2609433"></a>
+<a class="indexterm" name="id2609440"></a>
+<a class="indexterm" name="id2609447"></a>
+<a class="indexterm" name="id2609454"></a>
+<a class="indexterm" name="id2609461"></a>
+<a class="indexterm" name="id2609468"></a>
+<a class="indexterm" name="id2609476"></a>
+<a class="indexterm" name="id2609483"></a>
+<a class="indexterm" name="id2609490"></a>
+<a class="indexterm" name="id2609497"></a>
+<a class="indexterm" name="id2609504"></a>
+<a class="indexterm" name="id2609511"></a>
+<a class="indexterm" name="id2609518"></a>
+<a class="indexterm" name="id2609524"></a>
+<a class="indexterm" name="id2609532"></a>
+<a class="indexterm" name="id2609539"></a>
 </p><pre class="screen">
          SeCreateTokenPrivilege  Create a token object
   SeAssignPrimaryTokenPrivilege  Replace a process level token
@@ -271,35 +271,35 @@ SeIncreaseBasePriorityPrivilege  Increase scheduling priority
       SeRemoteShutdownPrivilege  Force shutdown from a remote system
 </pre><p>
 	And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges:
-<a class="indexterm" name="id2609597"></a>
-<a class="indexterm" name="id2609603"></a>
-<a class="indexterm" name="id2609611"></a>
-<a class="indexterm" name="id2609618"></a>
-<a class="indexterm" name="id2609625"></a>
-<a class="indexterm" name="id2609632"></a>
-<a class="indexterm" name="id2609639"></a>
-<a class="indexterm" name="id2609646"></a>
-<a class="indexterm" name="id2609653"></a>
-<a class="indexterm" name="id2609660"></a>
-<a class="indexterm" name="id2609667"></a>
-<a class="indexterm" name="id2609674"></a>
-<a class="indexterm" name="id2609681"></a>
-<a class="indexterm" name="id2609688"></a>
-<a class="indexterm" name="id2609695"></a>
-<a class="indexterm" name="id2609702"></a>
-<a class="indexterm" name="id2609709"></a>
-<a class="indexterm" name="id2609716"></a>
-<a class="indexterm" name="id2609723"></a>
-<a class="indexterm" name="id2609730"></a>
-<a class="indexterm" name="id2609737"></a>
-<a class="indexterm" name="id2609744"></a>
-<a class="indexterm" name="id2609751"></a>
-<a class="indexterm" name="id2609758"></a>
-<a class="indexterm" name="id2609765"></a>
-<a class="indexterm" name="id2609772"></a>
-<a class="indexterm" name="id2609780"></a>
-<a class="indexterm" name="id2609787"></a>
-<a class="indexterm" name="id2609794"></a>
+<a class="indexterm" name="id2609600"></a>
+<a class="indexterm" name="id2609606"></a>
+<a class="indexterm" name="id2609613"></a>
+<a class="indexterm" name="id2609620"></a>
+<a class="indexterm" name="id2609627"></a>
+<a class="indexterm" name="id2609634"></a>
+<a class="indexterm" name="id2609641"></a>
+<a class="indexterm" name="id2609648"></a>
+<a class="indexterm" name="id2609655"></a>
+<a class="indexterm" name="id2609662"></a>
+<a class="indexterm" name="id2609669"></a>
+<a class="indexterm" name="id2609676"></a>
+<a class="indexterm" name="id2609684"></a>
+<a class="indexterm" name="id2609691"></a>
+<a class="indexterm" name="id2609698"></a>
+<a class="indexterm" name="id2609705"></a>
+<a class="indexterm" name="id2609712"></a>
+<a class="indexterm" name="id2609719"></a>
+<a class="indexterm" name="id2609726"></a>
+<a class="indexterm" name="id2609733"></a>
+<a class="indexterm" name="id2609740"></a>
+<a class="indexterm" name="id2609747"></a>
+<a class="indexterm" name="id2609754"></a>
+<a class="indexterm" name="id2609761"></a>
+<a class="indexterm" name="id2609768"></a>
+<a class="indexterm" name="id2609775"></a>
+<a class="indexterm" name="id2609782"></a>
+<a class="indexterm" name="id2609789"></a>
+<a class="indexterm" name="id2609796"></a>
 </p><pre class="screen">
          SeCreateTokenPrivilege  Create a token object
   SeAssignPrimaryTokenPrivilege  Replace a process level token
@@ -332,15 +332,15 @@ SeIncreaseBasePriorityPrivilege  Increase scheduling priority
          SeImpersonatePrivilege  Impersonate a client after authentication
         SeCreateGlobalPrivilege  Create global objects
 </pre><p>
-<a class="indexterm" name="id2609868"></a>
+<a class="indexterm" name="id2609871"></a>
     The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux
     environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX.
-    </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2609882"></a>The Administrator Domain SID</h2></div></div></div><p>
-<a class="indexterm" name="id2609890"></a>
-<a class="indexterm" name="id2609897"></a>
-<a class="indexterm" name="id2609904"></a>
-<a class="indexterm" name="id2609911"></a>
-<a class="indexterm" name="id2609917"></a>
+    </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2609884"></a>The Administrator Domain SID</h2></div></div></div><p>
+<a class="indexterm" name="id2609892"></a>
+<a class="indexterm" name="id2609899"></a>
+<a class="indexterm" name="id2609906"></a>
+<a class="indexterm" name="id2609913"></a>
+<a class="indexterm" name="id2609920"></a>
 Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions
 commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges
 (see <a class="link" href="rights.html" title="Chapter�15.�User Rights and Privileges">User Rights and Privileges</a>).  An account in the server's passdb backend can
@@ -350,60 +350,60 @@ controller, run the following command:
 <code class="prompt">root# </code> net getlocalsid
 SID for domain FOO is: S-1-5-21-4294955119-3368514841-2087710299
 </pre><p>
-<a class="indexterm" name="id2609951"></a>
+<a class="indexterm" name="id2609954"></a>
 You may assign the domain administrator RID to an account using the <code class="literal">pdbedit</code>
 command as shown here:
-<a class="indexterm" name="id2609965"></a>
+<a class="indexterm" name="id2609968"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code> pdbedit -U S-1-5-21-4294955119-3368514841-2087710299-500 -u root -r
 </pre><p>
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2609989"></a>
-<a class="indexterm" name="id2609996"></a>
-<a class="indexterm" name="id2610003"></a>
-<a class="indexterm" name="id2610010"></a>
+<a class="indexterm" name="id2609992"></a>
+<a class="indexterm" name="id2609998"></a>
+<a class="indexterm" name="id2610005"></a>
+<a class="indexterm" name="id2610012"></a>
 The RID 500 is the well known standard value of the default Administrator account. It is the RID
 that confers the rights and privileges that the Administrator account has on a Windows machine
 or domain. Under UNIX/Linux the equivalent is UID=0 (the root account).
 </p></div><p>
-<a class="indexterm" name="id2610024"></a>
-<a class="indexterm" name="id2610032"></a>
-<a class="indexterm" name="id2610039"></a>
-<a class="indexterm" name="id2610046"></a>
+<a class="indexterm" name="id2610027"></a>
+<a class="indexterm" name="id2610034"></a>
+<a class="indexterm" name="id2610041"></a>
+<a class="indexterm" name="id2610048"></a>
 Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account
 provided equivalent rights and privileges have been established for a Windows user or a Windows
 group account. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610059"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2610064"></a>What Rights and Privileges Will Permit Windows Client Administration?</h3></div></div></div><p>
-<a class="indexterm" name="id2610073"></a>
-<a class="indexterm" name="id2610080"></a>
-<a class="indexterm" name="id2610087"></a>
-<a class="indexterm" name="id2610094"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610061"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2610067"></a>What Rights and Privileges Will Permit Windows Client Administration?</h3></div></div></div><p>
+<a class="indexterm" name="id2610076"></a>
+<a class="indexterm" name="id2610083"></a>
+<a class="indexterm" name="id2610089"></a>
+<a class="indexterm" name="id2610096"></a>
 	When a Windows NT4 (or later) client joins a domain, the domain global <code class="literal">Domain Admins</code> group
 	is added to the membership of the local <code class="literal">Administrators</code> group on the client. Any user who is
 	a member of the domain global <code class="literal">Domain Admins</code> group will have administrative rights on the
 	Windows client.
 	</p><p>
-<a class="indexterm" name="id2610126"></a>
-<a class="indexterm" name="id2610133"></a>
-<a class="indexterm" name="id2610141"></a>
-<a class="indexterm" name="id2610148"></a>
-<a class="indexterm" name="id2610154"></a>
+<a class="indexterm" name="id2610129"></a>
+<a class="indexterm" name="id2610136"></a>
+<a class="indexterm" name="id2610143"></a>
+<a class="indexterm" name="id2610150"></a>
+<a class="indexterm" name="id2610157"></a>
 	This is often not the most desirable solution because it means that the user will have administrative
 	rights and privileges on domain servers also. The <code class="literal">Power Users</code> group on Windows client
 	workstations permits local administration of the workstation alone. Any domain global user or domain global
 	group can be added to the membership of the local workstation group <code class="literal">Power Users</code>.
 	</p><p>
-<a class="indexterm" name="id2610182"></a>
-<a class="indexterm" name="id2610189"></a>
-<a class="indexterm" name="id2610197"></a>
-<a class="indexterm" name="id2610203"></a>
+<a class="indexterm" name="id2610185"></a>
+<a class="indexterm" name="id2610192"></a>
+<a class="indexterm" name="id2610199"></a>
+<a class="indexterm" name="id2610206"></a>
 	See <a class="link" href="NetCommand.html#nestedgrpmgmgt" title="Nested Group Support">Nested Group Support</a> for an example of how to add domain users
 	and groups to a local group that is on a Windows workstation. The use of the <code class="literal">net</code>
 	command permits this to be done from the Samba server.
 	</p><p>
-<a class="indexterm" name="id2610231"></a>
-<a class="indexterm" name="id2610238"></a>
-<a class="indexterm" name="id2610244"></a>
+<a class="indexterm" name="id2610234"></a>
+<a class="indexterm" name="id2610240"></a>
+<a class="indexterm" name="id2610247"></a>
 	Another way this can be done is to log onto the Windows workstation as the user
 	<code class="literal">Administrator</code>, then open a <code class="literal">cmd</code> shell, then execute:
 </p><pre class="screen">
diff --git a/docs/htmldocs/Samba3-HOWTO/samba-bdc.html b/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
index 8f58d2530f..9621baf534 100644
--- a/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
+++ b/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
@@ -1,18 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Backup Domain Control</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="samba-pdc.html" title="Chapter�4.�Domain Control"><link rel="next" href="domain-member.html" title="Chapter�6.�Domain Membership"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Backup Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="domain-member.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter�5.�Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="orgname">Samba Team</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565778">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566184">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567306">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568138">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568602">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568861">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Backup Domain Control</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="samba-pdc.html" title="Chapter�4.�Domain Control"><link rel="next" href="domain-member.html" title="Chapter�6.�Domain Membership"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Backup Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="domain-member.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter�5.�Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="orgname">Samba Team</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565776">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566182">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567305">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568136">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568600">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568859">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></div><p>
 Before you continue reading this section, please make sure that you are comfortable
 with configuring a Samba domain controller as described in <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Domain Control</a>.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565778"></a>Features and Benefits</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565776"></a>Features and Benefits</h2></div></div></div><p>
 This is one of the most difficult chapters to summarize. 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, please email <a class="ulink" 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>
-<a class="indexterm" name="id2565804"></a>
-<a class="indexterm" name="id2565813"></a>
-<a class="indexterm" name="id2565820"></a>
-<a class="indexterm" name="id2565826"></a>
-<a class="indexterm" name="id2565835"></a>
+<a class="indexterm" name="id2565803"></a>
+<a class="indexterm" name="id2565812"></a>
+<a class="indexterm" name="id2565818"></a>
+<a class="indexterm" name="id2565825"></a>
+<a class="indexterm" name="id2565834"></a>
 Samba-3 can act as a Backup Domain Controller (BDC) to another Samba Primary Domain Controller (PDC). 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
@@ -21,22 +21,22 @@ an effective solution for large organizations. If you use an LDAP slave server f
 ensure the master's continued availability  if the slave finds its master down at the wrong time,
 you will have stability and operational problems.
 </p><p>
-<a class="indexterm" name="id2565860"></a>
-<a class="indexterm" name="id2565869"></a>
-<a class="indexterm" name="id2565878"></a>
-<a class="indexterm" name="id2565887"></a>
+<a class="indexterm" name="id2565859"></a>
+<a class="indexterm" name="id2565867"></a>
+<a class="indexterm" name="id2565876"></a>
+<a class="indexterm" name="id2565885"></a>
 While it is possible to run a Samba-3 BDC with a non-LDAP backend, that backend must allow some form of
 "two-way" propagation of changes from the BDC to the master.  At this time only LDAP delivers the capability
 to propagate identity database changes from the BDC to the PDC. The BDC can use a slave LDAP server, while it
 is preferable for the PDC to use as its primary an LDAP master server.
 </p><p>
-<a class="indexterm" name="id2565904"></a>
-<a class="indexterm" name="id2565913"></a>
-<a class="indexterm" name="id2565922"></a>
-<a class="indexterm" name="id2565934"></a>
-<a class="indexterm" name="id2565940"></a>
-<a class="indexterm" name="id2565947"></a>
-<a class="indexterm" name="id2565954"></a>
+<a class="indexterm" name="id2565902"></a>
+<a class="indexterm" name="id2565911"></a>
+<a class="indexterm" name="id2565920"></a>
+<a class="indexterm" name="id2565932"></a>
+<a class="indexterm" name="id2565939"></a>
+<a class="indexterm" name="id2565945"></a>
+<a class="indexterm" name="id2565952"></a>
 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
@@ -46,10 +46,10 @@ PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs, this re
 overwriting the SAM that contains the updated (changed) trust account password with resulting
 breakage of the domain trust.
 </p><p>
-<a class="indexterm" name="id2565975"></a>
-<a class="indexterm" name="id2565984"></a>
-<a class="indexterm" name="id2565993"></a>
-<a class="indexterm" name="id2566002"></a>
+<a class="indexterm" name="id2565974"></a>
+<a class="indexterm" name="id2565982"></a>
+<a class="indexterm" name="id2565992"></a>
+<a class="indexterm" name="id2566001"></a>
 Considering the number of comments and questions raised concerning how to configure a BDC,
 let's consider each possible option and look at the pros and cons for each possible solution.
 <a class="link" href="samba-bdc.html#pdc-bdc-table" title="Table�5.1.�Domain Backend Account Distribution Options">The Domain Backend Account Distribution Options table below</a> lists 
@@ -70,30 +70,30 @@ possible design configurations for a PDC/BDC infrastructure.
 	Not an elegant solution due to the delays in synchronization
         and also suffers
         from the issue of domain trust breakdown.
-	</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2566184"></a>Essential Background Information</h2></div></div></div><p>
-<a class="indexterm" name="id2566192"></a>
-<a class="indexterm" name="id2566199"></a>
-<a class="indexterm" name="id2566206"></a>
-<a class="indexterm" name="id2566212"></a>
+	</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2566182"></a>Essential Background Information</h2></div></div></div><p>
+<a class="indexterm" name="id2566190"></a>
+<a class="indexterm" name="id2566197"></a>
+<a class="indexterm" name="id2566204"></a>
+<a class="indexterm" name="id2566211"></a>
 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>
-<a class="indexterm" name="id2566227"></a>
-<a class="indexterm" name="id2566238"></a>
+<a class="indexterm" name="id2566225"></a>
+<a class="indexterm" name="id2566237"></a>
 When MS Windows NT3.10 was first released, it supported a 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 complex array of
 services that are implemented over an intricate spectrum of technologies.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566253"></a>MS Windows NT4-style Domain Control</h3></div></div></div><p>
-<a class="indexterm" name="id2566262"></a>
-<a class="indexterm" name="id2566268"></a>
-<a class="indexterm" name="id2566276"></a>
-<a class="indexterm" name="id2566282"></a>
-<a class="indexterm" name="id2566289"></a>
-<a class="indexterm" name="id2566296"></a>
-<a class="indexterm" name="id2566305"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566252"></a>MS Windows NT4-style Domain Control</h3></div></div></div><p>
+<a class="indexterm" name="id2566260"></a>
+<a class="indexterm" name="id2566267"></a>
+<a class="indexterm" name="id2566274"></a>
+<a class="indexterm" name="id2566281"></a>
+<a class="indexterm" name="id2566288"></a>
+<a class="indexterm" name="id2566294"></a>
+<a class="indexterm" name="id2566303"></a>
 Whenever a user logs into a Windows NT4/200x/XP Professional workstation,
 the workstation connects to a domain controller (authentication server) to validate that
 the username and password the user entered are valid. If the information entered
@@ -101,11 +101,11 @@ does not match account information that has been stored in the domain
 control database (the SAM, or Security Account Manager database), a set of error
 codes is returned to the workstation that has made the authentication request.
 </p><p>
-<a class="indexterm" name="id2566325"></a>
-<a class="indexterm" name="id2566332"></a>
-<a class="indexterm" name="id2566339"></a>
-<a class="indexterm" name="id2566346"></a>
-<a class="indexterm" name="id2566353"></a>
+<a class="indexterm" name="id2566324"></a>
+<a class="indexterm" name="id2566331"></a>
+<a class="indexterm" name="id2566338"></a>
+<a class="indexterm" name="id2566344"></a>
+<a class="indexterm" name="id2566352"></a>
 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
@@ -117,11 +117,11 @@ network access time limits, account validity information, machine names from whi
 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>
-<a class="indexterm" name="id2566390"></a>
-<a class="indexterm" name="id2566399"></a>
-<a class="indexterm" name="id2566406"></a>
-<a class="indexterm" name="id2566413"></a>
-<a class="indexterm" name="id2566420"></a>
+<a class="indexterm" name="id2566389"></a>
+<a class="indexterm" name="id2566398"></a>
+<a class="indexterm" name="id2566405"></a>
+<a class="indexterm" name="id2566412"></a>
+<a class="indexterm" name="id2566418"></a>
 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 <code class="filename">%SystemRoot%\System32\config</code> directory. 
@@ -131,24 +131,24 @@ on the network.
 </p><p>
 There are two situations in which it is desirable to install BDCs:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2566456"></a>
-	<a class="indexterm" name="id2566462"></a>
+	<a class="indexterm" name="id2566454"></a>
+	<a class="indexterm" name="id2566461"></a>
 	On the local network that the PDC 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>
-	<a class="indexterm" name="id2566477"></a>
+	<a class="indexterm" name="id2566476"></a>
 	At each remote site, to reduce wide-area network traffic and to add stability to
 	remote network operations. The design of the network, and the strategic placement of
 	BDCs, together with an implementation that localizes as much of network to client
 	interchange as possible, will help to minimize wide-area network bandwidth needs
 	(and thus costs).
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2566497"></a>
-<a class="indexterm" name="id2566503"></a>
-<a class="indexterm" name="id2566510"></a>
-<a class="indexterm" name="id2566517"></a>
-<a class="indexterm" name="id2566523"></a>
+<a class="indexterm" name="id2566495"></a>
+<a class="indexterm" name="id2566502"></a>
+<a class="indexterm" name="id2566508"></a>
+<a class="indexterm" name="id2566515"></a>
+<a class="indexterm" name="id2566522"></a>
 The interoperation of a PDC and its BDCs in a true Windows NT4 environment is worth
 mentioning here. 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
@@ -160,50 +160,50 @@ of SAM synchronization. The PDC will then request the delta from the BDC and app
 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>
-<a class="indexterm" name="id2566547"></a>
-<a class="indexterm" name="id2566556"></a>
-<a class="indexterm" name="id2566565"></a>
-<a class="indexterm" name="id2566572"></a>
+<a class="indexterm" name="id2566546"></a>
+<a class="indexterm" name="id2566555"></a>
+<a class="indexterm" name="id2566564"></a>
+<a class="indexterm" name="id2566570"></a>
 Samba-3 cannot participate in true SAM replication and is therefore not able to
 employ precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will
 not create SAM update delta files. It will not interoperate with a PDC (NT4 or Samba)
 to synchronize the SAM from delta files that are held by BDCs.
 </p><p>
-<a class="indexterm" name="id2566587"></a>
-<a class="indexterm" name="id2566593"></a>
+<a class="indexterm" name="id2566585"></a>
+<a class="indexterm" name="id2566592"></a>
 Samba-3 cannot function as a BDC to an MS Windows NT4 PDC, and Samba-3 cannot
 function correctly as a PDC to an MS Windows NT4 BDC. Both Samba-3 and MS Windows
 NT4 can function as a BDC to its own type of PDC.
 </p><p>
-<a class="indexterm" name="id2566607"></a>
-<a class="indexterm" name="id2566613"></a>
-<a class="indexterm" name="id2566620"></a>
+<a class="indexterm" name="id2566605"></a>
+<a class="indexterm" name="id2566612"></a>
+<a class="indexterm" name="id2566618"></a>
 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 authenticate users. The BDC can
 continue to provide this service, particularly while, for example, the wide-area
 network link to the PDC is down. A BDC plays a very important role in both the
 maintenance of domain security as well as in network integrity.
 </p><p>
-<a class="indexterm" name="id2566640"></a>
-<a class="indexterm" name="id2566646"></a>
-<a class="indexterm" name="id2566653"></a>
-<a class="indexterm" name="id2566660"></a>
+<a class="indexterm" name="id2566638"></a>
+<a class="indexterm" name="id2566644"></a>
+<a class="indexterm" name="id2566651"></a>
+<a class="indexterm" name="id2566658"></a>
 In the event that the NT4 PDC should need to be taken out of service, or if it dies, one of the NT4 BDCs can
 be promoted to a PDC. If this happens while the original NT4 PDC is online, it is automatically demoted to an
 NT4 BDC. This is an important aspect of domain controller management. The tool that is used to effect a
 promotion or a demotion is the Server Manager for Domains. It should be noted that Samba-3 BDCs cannot be
 promoted in this manner because reconfiguration of Samba requires changes to the <code class="filename">smb.conf</code> file. It is easy
 enough to manuall change the <code class="filename">smb.conf</code> file and then restart relevant Samba network services.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2566690"></a>Example PDC Configuration</h4></div></div></div><p>
-<a class="indexterm" name="id2566698"></a>
-<a class="indexterm" name="id2566705"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2566688"></a>Example PDC Configuration</h4></div></div></div><p>
+<a class="indexterm" name="id2566696"></a>
+<a class="indexterm" name="id2566703"></a>
 Beginning with 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
 <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> have to be set.  Refer to <a class="link" href="samba-bdc.html#minimalPDC" title="Example�5.1.�Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC">the Minimal smb.conf for a PDC in Use with a BDC  LDAP Server on PDC
 section</a> for an example of the minimum required settings.
-</p><div class="example"><a name="minimalPDC"></a><p class="title"><b>Example�5.1.�Minimal smb.conf for a PDC in Use with a BDC  LDAP Server on PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2566758"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2566770"></a><em class="parameter"><code>passdb backend = ldapsam://localhost:389</code></em></td></tr><tr><td><a class="indexterm" name="id2566782"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566794"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566806"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2566817"></a><em class="parameter"><code>ldap user suffix = ou=Users</code></em></td></tr><tr><td><a class="indexterm" name="id2566829"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2566841"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td><a class="indexterm" name="id2566853"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2566865"></a><em class="parameter"><code>ldap admin dn = cn=sambadmin,dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2566881"></a>
-<a class="indexterm" name="id2566888"></a>
+</p><div class="example"><a name="minimalPDC"></a><p class="title"><b>Example�5.1.�Minimal smb.conf for a PDC in Use with a BDC  LDAP Server on PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2566757"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2566768"></a><em class="parameter"><code>passdb backend = ldapsam://localhost:389</code></em></td></tr><tr><td><a class="indexterm" name="id2566780"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566792"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2566804"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2566816"></a><em class="parameter"><code>ldap user suffix = ou=Users</code></em></td></tr><tr><td><a class="indexterm" name="id2566828"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2566840"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td><a class="indexterm" name="id2566852"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2566864"></a><em class="parameter"><code>ldap admin dn = cn=sambadmin,dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2566879"></a>
+<a class="indexterm" name="id2566886"></a>
 Several other things like a <em class="parameter"><code>[homes]</code></em> and a <em class="parameter"><code>[netlogon]</code></em> share
 also need to be set along with settings for the profile path, the user's home drive, and so on. This is not
 covered in this chapter; for more information please refer to <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control">Domain Control</a>.
@@ -211,34 +211,34 @@ Refer to <a class="link" href="samba-pdc.html" title="Chapter�4.�Domain Control"
 configuration. Alternately, fully documented working example network configurations using OpenLDAP and Samba
 as available in the <a class="ulink" href="http://www.samba.org/samba/docs/Samba3-ByExample" target="_top">book</a> &#8220;<span class="quote">Samba-3
 by Example</span>&#8221; that may be obtained from local and on-line book stores.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566941"></a>LDAP Configuration Notes</h3></div></div></div><p>
-<a class="indexterm" name="id2566949"></a>
-<a class="indexterm" name="id2566958"></a>
-<a class="indexterm" name="id2566968"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566940"></a>LDAP Configuration Notes</h3></div></div></div><p>
+<a class="indexterm" name="id2566948"></a>
+<a class="indexterm" name="id2566957"></a>
+<a class="indexterm" name="id2566966"></a>
 When configuring a master and a slave LDAP server, it is advisable to use the master LDAP server
 for the PDC and slave LDAP servers for the BDCs. It is not essential to use slave LDAP servers; however,
 many administrators will want to do so in order to provide redundant services. Of course, one or more BDCs
 may use any slave LDAP server. Then again, it is entirely possible to use a single LDAP server for the
 entire network.
 </p><p>
-<a class="indexterm" name="id2566985"></a>
-<a class="indexterm" name="id2566994"></a>
-<a class="indexterm" name="id2567003"></a>
-<a class="indexterm" name="id2567010"></a>
-<a class="indexterm" name="id2567016"></a>
+<a class="indexterm" name="id2566983"></a>
+<a class="indexterm" name="id2566992"></a>
+<a class="indexterm" name="id2567001"></a>
+<a class="indexterm" name="id2567008"></a>
+<a class="indexterm" name="id2567015"></a>
 When configuring a master LDAP server that will have slave LDAP servers, do not forget to configure this in
 the <code class="filename">/etc/openldap/slapd.conf</code> file. It must be noted that the DN of a server certificate
 must use the CN attribute to name the server, and the CN must carry the servers' fully qualified domain name.
 Additional alias names and wildcards may be present in the subjectAltName certificate extension. More details
 on server certificate names are in RFC2830.
 </p><p>
-<a class="indexterm" name="id2567040"></a>
-<a class="indexterm" name="id2567047"></a>
-<a class="indexterm" name="id2567053"></a>
-<a class="indexterm" name="id2567060"></a>
-<a class="indexterm" name="id2567070"></a>
-<a class="indexterm" name="id2567077"></a>
-<a class="indexterm" name="id2567084"></a>
+<a class="indexterm" name="id2567038"></a>
+<a class="indexterm" name="id2567045"></a>
+<a class="indexterm" name="id2567052"></a>
+<a class="indexterm" name="id2567059"></a>
+<a class="indexterm" name="id2567068"></a>
+<a class="indexterm" name="id2567075"></a>
+<a class="indexterm" name="id2567082"></a>
 It does not really fit within the scope of this document, but a working LDAP installation is basic to
 LDAP-enabled Samba operation. When using an OpenLDAP server with Transport Layer Security (TLS), the machine
 name in <code class="filename">/etc/ssl/certs/slapd.pem</code> must be the same as in
@@ -247,12 +247,12 @@ name in <code class="filename">/etc/ssl/certs/slapd.pem</code> must be the same
 access this LDAP server from a slave LDAP server (i.e., a Samba BDC) unless the certificate is re-created with
 a correct hostname.
 </p><p>
-<a class="indexterm" name="id2567124"></a>
-<a class="indexterm" name="id2567130"></a>
-<a class="indexterm" name="id2567137"></a>
-<a class="indexterm" name="id2567144"></a>
-<a class="indexterm" name="id2567151"></a>
-<a class="indexterm" name="id2567158"></a>
+<a class="indexterm" name="id2567122"></a>
+<a class="indexterm" name="id2567129"></a>
+<a class="indexterm" name="id2567136"></a>
+<a class="indexterm" name="id2567142"></a>
+<a class="indexterm" name="id2567149"></a>
+<a class="indexterm" name="id2567156"></a>
 Do not install a Samba PDC so that is uses an LDAP slave server. Joining client machines to the domain
 will fail in this configuration because the change to the machine account in the LDAP tree must take place on
 the master LDAP server. This is not replicated rapidly enough to the slave server that the PDC queries. It
@@ -279,23 +279,23 @@ Possible PDC/BDC plus LDAP configurations include:
 In order to have a fallback configuration (secondary) LDAP server, you would specify
 the secondary LDAP server in the <code class="filename">smb.conf</code> file as shown in <a class="link" href="samba-bdc.html#mulitldapcfg" title="Example�5.2.�Multiple LDAP Servers in smb.conf">the Multiple LDAP
 Servers in <code class="filename">smb.conf</code> example</a>.
-</p><div class="example"><a name="mulitldapcfg"></a><p class="title"><b>Example�5.2.�Multiple LDAP Servers in <code class="filename">smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2567292"></a><em class="parameter"><code>passdb backend = ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567306"></a>Active Directory Domain Control</h3></div></div></div><p>
-<a class="indexterm" name="id2567314"></a>
-<a class="indexterm" name="id2567321"></a>
-<a class="indexterm" name="id2567328"></a>
-<a class="indexterm" name="id2567335"></a>
-<a class="indexterm" name="id2567342"></a>
-<a class="indexterm" name="id2567348"></a>
+</p><div class="example"><a name="mulitldapcfg"></a><p class="title"><b>Example�5.2.�Multiple LDAP Servers in <code class="filename">smb.conf</code></b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2567290"></a><em class="parameter"><code>passdb backend = ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567305"></a>Active Directory Domain Control</h3></div></div></div><p>
+<a class="indexterm" name="id2567313"></a>
+<a class="indexterm" name="id2567320"></a>
+<a class="indexterm" name="id2567327"></a>
+<a class="indexterm" name="id2567333"></a>
+<a class="indexterm" name="id2567340"></a>
+<a class="indexterm" name="id2567347"></a>
 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 cannot be an Active Directory server. This means that Samba-3 also cannot
 act as a BDC to an Active Directory domain controller.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567364"></a>What Qualifies a Domain Controller on the Network?</h3></div></div></div><p>
-<a class="indexterm" name="id2567373"></a>
-<a class="indexterm" name="id2567379"></a>
-<a class="indexterm" name="id2567386"></a>
-<a class="indexterm" name="id2567393"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567363"></a>What Qualifies a Domain Controller on the Network?</h3></div></div></div><p>
+<a class="indexterm" name="id2567371"></a>
+<a class="indexterm" name="id2567378"></a>
+<a class="indexterm" name="id2567384"></a>
+<a class="indexterm" name="id2567391"></a>
 Every machine that is a domain controller for the domain MIDEARTH has to register the NetBIOS
 group name MIDEARTH&lt;1C&gt; with the WINS server and/or by broadcast on the local network.
 The PDC also registers the unique NetBIOS name MIDEARTH&lt;1B&gt; with the WINS server.
@@ -303,30 +303,30 @@ The name type &lt;1B&gt; name is normally reserved for the Domain Master Browser
 that has nothing to do with anything related to authentication, but the Microsoft domain
 implementation requires the DMB to be on the same machine as the PDC.
 </p><p>
-<a class="indexterm" name="id2567415"></a>
-<a class="indexterm" name="id2567421"></a>
-<a class="indexterm" name="id2567428"></a>
+<a class="indexterm" name="id2567413"></a>
+<a class="indexterm" name="id2567420"></a>
+<a class="indexterm" name="id2567427"></a>
 Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to
 <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a>,<a class="link" href="NetworkBrowsing.html#netdiscuss" title="Discussion">Discussion</a>
 for more information regarding TCP/IP network protocols and how SMB/CIFS names are handled.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567455"></a>How Does a Workstation find its Domain Controller?</h3></div></div></div><p>
-<a class="indexterm" name="id2567464"></a>
-<a class="indexterm" name="id2567471"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567454"></a>How Does a Workstation find its Domain Controller?</h3></div></div></div><p>
+<a class="indexterm" name="id2567462"></a>
+<a class="indexterm" name="id2567469"></a>
 There are two different mechanisms to locate a domain controller: one method is used when
 NetBIOS over TCP/IP is enabled and the other when it has been disabled in the TCP/IP
 network configuration.
 </p><p>
-<a class="indexterm" name="id2567484"></a>
-<a class="indexterm" name="id2567491"></a>
+<a class="indexterm" name="id2567483"></a>
+<a class="indexterm" name="id2567489"></a>
 Where NetBIOS over TCP/IP is disabled, all name resolution involves the use of DNS, broadcast
 messaging over UDP, as well as Active Directory communication technologies. In this type of
 environment all machines require appropriate DNS entries. More information may be found in
 <a class="link" href="NetworkBrowsing.html#adsdnstech" title="DNS and Active Directory">DNS and Active Directory</a>.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2567512"></a>NetBIOS Over TCP/IP Enabled</h4></div></div></div><p>
-<a class="indexterm" name="id2567520"></a>
-<a class="indexterm" name="id2567527"></a>
-<a class="indexterm" name="id2567534"></a>
-<a class="indexterm" name="id2567540"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2567510"></a>NetBIOS Over TCP/IP Enabled</h4></div></div></div><p>
+<a class="indexterm" name="id2567518"></a>
+<a class="indexterm" name="id2567525"></a>
+<a class="indexterm" name="id2567532"></a>
+<a class="indexterm" name="id2567539"></a>
 An MS Windows NT4/200x/XP Professional workstation in the domain MIDEARTH that wants a
 local user to be authenticated has to find the domain controller for MIDEARTH. It does this
 by doing a NetBIOS name query for the group name MIDEARTH&lt;1C&gt;. It assumes that each
@@ -334,46 +334,46 @@ of the machines it gets back from the queries is a domain controller and can ans
 requests. To not open security holes, both the workstation and the selected domain controller
 authenticate each other. After that the workstation sends the user's credentials (name and
 password) to the local domain controller for validation.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2567578"></a>NetBIOS Over TCP/IP Disabled</h4></div></div></div><p>
-<a class="indexterm" name="id2567586"></a>
-<a class="indexterm" name="id2567592"></a>
-<a class="indexterm" name="id2567600"></a>
-<a class="indexterm" name="id2567606"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2567576"></a>NetBIOS Over TCP/IP Disabled</h4></div></div></div><p>
+<a class="indexterm" name="id2567584"></a>
+<a class="indexterm" name="id2567591"></a>
+<a class="indexterm" name="id2567598"></a>
+<a class="indexterm" name="id2567604"></a>
 An MS Windows NT4/200x/XP Professional workstation in the realm <code class="constant">quenya.org</code>
 that has a need to affect user logon authentication will locate the domain controller by 
 re-querying DNS servers for the <code class="constant">_ldap._tcp.pdc._msdcs.quenya.org</code> record.
 More information regarding this subject may be found in <a class="link" href="NetworkBrowsing.html#adsdnstech" title="DNS and Active Directory">DNS and Active Directory</a>.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2567637"></a>Backup Domain Controller Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2567644"></a>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2567635"></a>Backup Domain Controller Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2567642"></a>
 The creation of a BDC requires some steps to prepare the Samba server before
 <span class="application">smbd</span> is executed for the first time. These steps are as follows:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2567665"></a>
-	<a class="indexterm" name="id2567672"></a>
-	<a class="indexterm" name="id2567678"></a>
-	<a class="indexterm" name="id2567685"></a>
-	<a class="indexterm" name="id2567692"></a>
-	<a class="indexterm" name="id2567699"></a>
+	<a class="indexterm" name="id2567664"></a>
+	<a class="indexterm" name="id2567670"></a>
+	<a class="indexterm" name="id2567677"></a>
+	<a class="indexterm" name="id2567683"></a>
+	<a class="indexterm" name="id2567690"></a>
+	<a class="indexterm" name="id2567697"></a>
 	The domain SID has to be the same on the PDC and the BDC. In Samba versions pre-2.2.5, the domain SID was
 	stored in the file <code class="filename">private/MACHINE.SID</code>.  For all versions of Samba released since 2.2.5
 	the domain SID is stored in the file <code class="filename">private/secrets.tdb</code>. This file is unique to each
 	server and cannot be copied from a PDC to a BDC; the BDC will generate a new SID at startup. It will overwrite
-	the PDC domain SID with the newly created BDC SID.  There is a procedure that will allow the BDC to acquire the
+	the PDC domain SID with the newly created BDC SID.  There is a procedure that will allow the BDC to aquire the
 	domain SID. This is described here.
 	</p><p>
-	<a class="indexterm" name="id2567729"></a>
-	<a class="indexterm" name="id2567736"></a>
-	<a class="indexterm" name="id2567743"></a>
-	<a class="indexterm" name="id2567749"></a>
-	<a class="indexterm" name="id2567756"></a>
+	<a class="indexterm" name="id2567728"></a>
+	<a class="indexterm" name="id2567734"></a>
+	<a class="indexterm" name="id2567741"></a>
+	<a class="indexterm" name="id2567748"></a>
+	<a class="indexterm" name="id2567754"></a>
 	To retrieve the domain SID from the PDC or an existing BDC and store it in the
 	<code class="filename">secrets.tdb</code>, execute:
 	</p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>net rpc getsid</code></strong>
 </pre></li><li><p>
-	<a class="indexterm" name="id2567796"></a>
-	<a class="indexterm" name="id2567803"></a>
-	<a class="indexterm" name="id2567810"></a>
+	<a class="indexterm" name="id2567794"></a>
+	<a class="indexterm" name="id2567801"></a>
+	<a class="indexterm" name="id2567808"></a>
 	Specification of the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> is obligatory.
 	This also requires the LDAP administration password to be set in the <code class="filename">secrets.tdb</code>
 	using the <code class="literal">smbpasswd -w <em class="replaceable"><code>mysecret</code></em></code>.
@@ -381,10 +381,10 @@ The creation of a BDC requires some steps to prepare the Samba server before
 	The <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> parameter and the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX" target="_top">ldap idmap suffix</a>
 	parameter must be specified in the <code class="filename">smb.conf</code> file.
 	</p></li><li><p>
-	<a class="indexterm" name="id2567884"></a>
-	<a class="indexterm" name="id2567893"></a>
-	<a class="indexterm" name="id2567900"></a>
-	<a class="indexterm" name="id2567907"></a>
+	<a class="indexterm" name="id2567883"></a>
+	<a class="indexterm" name="id2567892"></a>
+	<a class="indexterm" name="id2567899"></a>
+	<a class="indexterm" name="id2567906"></a>
 	The UNIX user database has to be synchronized from the PDC to the
 	BDC. This means that both the <code class="filename">/etc/passwd</code> and
 	<code class="filename">/etc/group</code> have to be replicated from the PDC
@@ -395,14 +395,14 @@ The creation of a BDC requires some steps to prepare the Samba server before
 	a PDC failure. NIS is by no means the only method to synchronize
 	passwords. An LDAP solution would also work.
 	</p></li><li><p>
-	<a class="indexterm" name="id2567940"></a>
-	<a class="indexterm" name="id2567947"></a>
-	<a class="indexterm" name="id2567954"></a>
-	<a class="indexterm" name="id2567960"></a>
-	<a class="indexterm" name="id2567967"></a>
-	<a class="indexterm" name="id2567974"></a>
-	<a class="indexterm" name="id2567980"></a>
-	<a class="indexterm" name="id2567987"></a>
+	<a class="indexterm" name="id2567938"></a>
+	<a class="indexterm" name="id2567945"></a>
+	<a class="indexterm" name="id2567952"></a>
+	<a class="indexterm" name="id2567959"></a>
+	<a class="indexterm" name="id2567965"></a>
+	<a class="indexterm" name="id2567972"></a>
+	<a class="indexterm" name="id2567979"></a>
+	<a class="indexterm" name="id2567985"></a>
 	The Samba password database must be replicated from the PDC to the BDC.
 	Although it is possible to synchronize the <code class="filename">smbpasswd</code>
 	file with <code class="literal">rsync</code> and <code class="literal">ssh</code>, this method
@@ -417,63 +417,63 @@ The creation of a BDC requires some steps to prepare the Samba server before
 	intervals  administrators are not normally aware that this is happening
 	or when it takes place.
 	</p><p>
-	<a class="indexterm" name="id2568033"></a>
-	<a class="indexterm" name="id2568039"></a>
-	<a class="indexterm" name="id2568046"></a>
-	<a class="indexterm" name="id2568053"></a>
+	<a class="indexterm" name="id2568031"></a>
+	<a class="indexterm" name="id2568038"></a>
+	<a class="indexterm" name="id2568044"></a>
+	<a class="indexterm" name="id2568051"></a>
 	The use of LDAP for both the POSIX (UNIX user and group) accounts and for the
 	SambaSAMAccount data automatically ensures that all account change information
 	will be written to the shared directory. This eliminates the need for any special
 	action to synchronize account information because LDAP will meet that requirement.
 	</p></li><li><p>
-	<a class="indexterm" name="id2568070"></a>
-	<a class="indexterm" name="id2568077"></a>
-	<a class="indexterm" name="id2568083"></a>
-	<a class="indexterm" name="id2568090"></a>
-	<a class="indexterm" name="id2568096"></a>
-	<a class="indexterm" name="id2568103"></a>
+	<a class="indexterm" name="id2568068"></a>
+	<a class="indexterm" name="id2568075"></a>
+	<a class="indexterm" name="id2568082"></a>
+	<a class="indexterm" name="id2568088"></a>
+	<a class="indexterm" name="id2568095"></a>
+	<a class="indexterm" name="id2568102"></a>
 	The 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 using a <code class="literal">cron</code> job that will replicate
 	the directory structure in this share using a tool like <code class="literal">rsync</code>. The use of
 	<code class="literal">rsync</code> for replication of the netlogon data is not critical to network security and is one
 	that can be manually managed given that the administrator will make all changes to the netlogon share as part
 	of a conscious move.
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568138"></a>Example Configuration</h3></div></div></div><p>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568136"></a>Example Configuration</h3></div></div></div><p>
 Finally, the BDC has to be capable of being found by the workstations. This can be done by configuring the
 Samba <code class="filename">smb.conf</code> file <em class="parameter"><code>[global]</code></em> section as shown in <a class="link" href="samba-bdc.html#minim-bdc" title="Example�5.3.�Minimal Setup for Being a BDC">Minimal
 Setup for Being a BDC</a>.
-</p><div class="example"><a name="minim-bdc"></a><p class="title"><b>Example�5.3.�Minimal Setup for Being a BDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2568183"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2568195"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://slave-ldap.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2568208"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2568219"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568231"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2568243"></a><em class="parameter"><code>ldap user suffix = ou=Users</code></em></td></tr><tr><td><a class="indexterm" name="id2568255"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2568267"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td><a class="indexterm" name="id2568279"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2568291"></a><em class="parameter"><code>ldap admin dn = cn=sambadmin,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2568303"></a><em class="parameter"><code>idmap backend = ldap:ldap://master-ldap.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2568315"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2568327"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr></table></div></div><br class="example-break"><p>
+</p><div class="example"><a name="minim-bdc"></a><p class="title"><b>Example�5.3.�Minimal Setup for Being a BDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2568182"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2568194"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://slave-ldap.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2568206"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id2568218"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2568229"></a><em class="parameter"><code>ldap suffix = dc=abmas,dc=biz</code></em></td></tr><tr><td><a class="indexterm" name="id2568241"></a><em class="parameter"><code>ldap user suffix = ou=Users</code></em></td></tr><tr><td><a class="indexterm" name="id2568253"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2568265"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td><a class="indexterm" name="id2568277"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2568289"></a><em class="parameter"><code>ldap admin dn = cn=sambadmin,dc=quenya,dc=org</code></em></td></tr><tr><td><a class="indexterm" name="id2568301"></a><em class="parameter"><code>idmap backend = ldap:ldap://master-ldap.quenya.org</code></em></td></tr><tr><td><a class="indexterm" name="id2568314"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id2568325"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr></table></div></div><br class="example-break"><p>
 Fully documented working example network configurations using OpenLDAP and Samba
 as available in the <a class="ulink" href="http://www.samba.org/samba/docs/Samba3-ByExample" target="_top">book</a> &#8220;<span class="quote">Samba-3
 by Example</span>&#8221; that may be obtained from local and on-line book stores.
 </p><p>
-<a class="indexterm" name="id2568358"></a>
-<a class="indexterm" name="id2568365"></a>
-<a class="indexterm" name="id2568371"></a>
-<a class="indexterm" name="id2568378"></a>
+<a class="indexterm" name="id2568356"></a>
+<a class="indexterm" name="id2568363"></a>
+<a class="indexterm" name="id2568370"></a>
+<a class="indexterm" name="id2568377"></a>
 This configuration causes the BDC to register only the name MIDEARTH&lt;1C&gt; with the WINS server. This is
 not a problem, as the name MIDEARTH&lt;1C&gt; is a NetBIOS group name that is meant to be registered by more
 than one machine. The parameter <a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = no</a> forces the BDC not to
 register MIDEARTH&lt;1B&gt;, which is a unique NetBIOS name that is reserved for the PDC.
 </p><p>
-<a class="indexterm" name="id2568410"></a>
+<a class="indexterm" name="id2568409"></a>
 <a class="indexterm" name="id2568416"></a>
-<a class="indexterm" name="id2568423"></a>
-<a class="indexterm" name="id2568430"></a>
-<a class="indexterm" name="id2568437"></a>
-<a class="indexterm" name="id2568444"></a>
+<a class="indexterm" name="id2568422"></a>
+<a class="indexterm" name="id2568429"></a>
+<a class="indexterm" name="id2568436"></a>
+<a class="indexterm" name="id2568443"></a>
 <a class="indexterm" name="id2568450"></a>
-<a class="indexterm" name="id2568457"></a>
-<a class="indexterm" name="id2568464"></a>
+<a class="indexterm" name="id2568456"></a>
+<a class="indexterm" name="id2568463"></a>
 The <em class="parameter"><code>idmap backend</code></em> will redirect the <code class="literal">winbindd</code> utility to use the LDAP
 database to store all mappings for Windows SIDs to  UIDs and GIDs for UNIX accounts in a repository that is
 shared. The BDC will however depend on local resolution of UIDs and GIDs via NSS and the
 <code class="literal">nss_ldap</code> utility.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2568497"></a>
+<a class="indexterm" name="id2568496"></a>
 <a class="indexterm" name="id2568506"></a>
-<a class="indexterm" name="id2568513"></a>
-<a class="indexterm" name="id2568520"></a>
+<a class="indexterm" name="id2568512"></a>
+<a class="indexterm" name="id2568519"></a>
 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 to NT domain user and group
 SIDs. One of the new facilities provides for explicitly ensuring that UNIX/Linux UID and GID values
@@ -481,27 +481,27 @@ will be consistent on the PDC, all BDCs, and all domain member servers. The para
 is called <em class="parameter"><code>idmap backend</code></em>. Please refer to the man page for <code class="filename">smb.conf</code> for more information
 regarding its behavior.
 </p></div><p>
-<a class="indexterm" name="id2568558"></a>
-<a class="indexterm" name="id2568564"></a>
-<a class="indexterm" name="id2568571"></a>
+<a class="indexterm" name="id2568557"></a>
+<a class="indexterm" name="id2568563"></a>
+<a class="indexterm" name="id2568570"></a>
 The use of the <a class="link" href="smb.conf.5.html#IDMAPBACKEND" target="_top">idmap backend = ldap:ldap://master.quenya.org</a>
 option on a BDC only makes sense where ldapsam is used on a PDC. The purpose of an LDAP-based idmap backend is
 also to allow a domain member (without its own passdb backend) to use winbindd to resolve Windows network users
 and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on domain
 member servers.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2568602"></a>Common Errors</h2></div></div></div><p>
-<a class="indexterm" name="id2568610"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2568600"></a>Common Errors</h2></div></div></div><p>
+<a class="indexterm" name="id2568608"></a>
 Domain control was a new area for Samba, but there are now many examples that we may refer to.
 Updated information will be published as they become available and may be found in later Samba releases or
 from the Samba Web <a class="ulink" href="http://samba.org" target="_top">site</a>; refer in particular to the
 <code class="filename">WHATSNEW.txt</code> in the Samba release tarball. The book, &#8220;<span class="quote">Samba-3 by Example</span>&#8221;
 documents well tested and proven configuration examples. You can obtain a copy of this
 <a class="ulink" href="http://www.samba.org/samba/docs/Samba3-ByExample.pdf" target="_top">book</a> for the Samba web site.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568646"></a>Machine Accounts Keep Expiring</h3></div></div></div><p>
-<a class="indexterm" name="id2568654"></a>
-<a class="indexterm" name="id2568661"></a>
-<a class="indexterm" name="id2568668"></a>
-<a class="indexterm" name="id2568674"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568644"></a>Machine Accounts Keep Expiring</h3></div></div></div><p>
+<a class="indexterm" name="id2568652"></a>
+<a class="indexterm" name="id2568659"></a>
+<a class="indexterm" name="id2568666"></a>
+<a class="indexterm" name="id2568672"></a>
 This problem will occur when the passdb (SAM) files are copied  from a central
 server but the local BDC is acting as a PDC. This results in the application of
 Local Machine Trust Account password updates to the local SAM. Such updates 
@@ -513,43 +513,43 @@ to proceed and the account expiry error will be reported.
 </p><p>
 The solution is to use a more robust passdb backend, such as the ldapsam backend, setting up
 a 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="id2568701"></a>Can Samba Be a Backup Domain Controller to an NT4 PDC?</h3></div></div></div><p>
-<a class="indexterm" name="id2568709"></a>
-<a class="indexterm" name="id2568718"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568699"></a>Can Samba Be a Backup Domain Controller to an NT4 PDC?</h3></div></div></div><p>
+<a class="indexterm" name="id2568707"></a>
+<a class="indexterm" name="id2568716"></a>
 No. The native NT4 SAM replication protocols have not yet been fully implemented.
 </p><p>
-<a class="indexterm" name="id2568729"></a>
-<a class="indexterm" name="id2568736"></a>
-<a class="indexterm" name="id2568742"></a>
+<a class="indexterm" name="id2568728"></a>
+<a class="indexterm" name="id2568734"></a>
+<a class="indexterm" name="id2568741"></a>
 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="id2568756"></a>How Do I Replicate the smbpasswd File?</h3></div></div></div><p>
-<a class="indexterm" name="id2568764"></a>
-<a class="indexterm" name="id2568773"></a>
-<a class="indexterm" name="id2568780"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568754"></a>How Do I Replicate the smbpasswd File?</h3></div></div></div><p>
+<a class="indexterm" name="id2568762"></a>
+<a class="indexterm" name="id2568771"></a>
+<a class="indexterm" name="id2568778"></a>
 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>
-<a class="indexterm" name="id2568794"></a>
-<a class="indexterm" name="id2568801"></a>
-<a class="indexterm" name="id2568807"></a>
+<a class="indexterm" name="id2568792"></a>
+<a class="indexterm" name="id2568799"></a>
+<a class="indexterm" name="id2568806"></a>
 As the smbpasswd file contains plaintext 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.
 <code class="literal">ssh</code> itself can be set up to accept <span class="emphasis"><em>only</em></span>
 <code class="literal">rsync</code> transfer without requiring the user to type a password.
 </p><p>
-<a class="indexterm" name="id2568838"></a>
-<a class="indexterm" name="id2568845"></a>
+<a class="indexterm" name="id2568836"></a>
+<a class="indexterm" name="id2568843"></a>
 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 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="id2568861"></a>Can I Do This All with LDAP?</h3></div></div></div><p>
-<a class="indexterm" name="id2568869"></a>
-<a class="indexterm" name="id2568876"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2568859"></a>Can I Do This All with LDAP?</h3></div></div></div><p>
+<a class="indexterm" name="id2568867"></a>
+<a class="indexterm" name="id2568874"></a>
 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
diff --git a/docs/htmldocs/Samba3-HOWTO/samba-pdc.html b/docs/htmldocs/Samba3-HOWTO/samba-pdc.html
index 5b60eeaceb..a3c8c1f414 100644
--- a/docs/htmldocs/Samba3-HOWTO/samba-pdc.html
+++ b/docs/htmldocs/Samba3-HOWTO/samba-pdc.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�Domain Control</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="ServerType.html" title="Chapter�3.�Server Types and Security Modes"><link rel="next" href="samba-bdc.html" title="Chapter�5.�Backup Domain Control"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter�4.�Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="orgname">Samba Team</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561237">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562461">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562480">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562984">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564237">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564290">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564309">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565181">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565287">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565352">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565428">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565548">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565575">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565594">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�Domain Control</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="ServerType.html" title="Chapter�3.�Server Types and Security Modes"><link rel="next" href="samba-bdc.html" title="Chapter�5.�Backup Domain Control"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter�4.�Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="orgname">Samba Team</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span>�<div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561235">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562458">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562478">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562982">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564236">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564289">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564308">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565179">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565286">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565350">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565427">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565546">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565573">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565592">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></div><p>
 There are many who approach MS Windows networking with incredible misconceptions.
 That's okay, because it gives the rest of us plenty of opportunity to be of assistance.
 Those who really want help are well advised to become familiar with information
 that is already available.
 </p><p>
-<a class="indexterm" name="id2561100"></a>
+<a class="indexterm" name="id2561097"></a>
 You are 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 
@@ -32,14 +32,14 @@ organization.
 Where is the right place to make mistakes? Only out of harms way. If you are going to
 make mistakes, then please do it 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="id2561237"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2561245"></a>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561235"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2561243"></a>
 <span class="emphasis"><em>What is the key benefit of Microsoft Domain Security?</em></span>
 </p><p>
-<a class="indexterm" name="id2561260"></a>
-<a class="indexterm" name="id2561269"></a>
-<a class="indexterm" name="id2561276"></a>
-<a class="indexterm" name="id2561283"></a>
+<a class="indexterm" name="id2561257"></a>
+<a class="indexterm" name="id2561267"></a>
+<a class="indexterm" name="id2561273"></a>
+<a class="indexterm" name="id2561280"></a>
 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 contains their user account (or in a domain that has an appropriate trust
@@ -47,24 +47,24 @@ relationship with the domain they are visiting) and they will be able to log ont
 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>
-<a class="indexterm" name="id2561311"></a>
-<a class="indexterm" name="id2561318"></a>
-<a class="indexterm" name="id2561325"></a>
-<a class="indexterm" name="id2561334"></a>
-<a class="indexterm" name="id2561343"></a>
+<a class="indexterm" name="id2561308"></a>
+<a class="indexterm" name="id2561315"></a>
+<a class="indexterm" name="id2561322"></a>
+<a class="indexterm" name="id2561331"></a>
+<a class="indexterm" name="id2561340"></a>
 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 recognize only local security identifiers.
 </p><p>
-<a class="indexterm" name="id2561362"></a>
+<a class="indexterm" name="id2561359"></a>
 A SID represents a security context. For example, every Windows machine has local accounts within the security
 context of the local machine which has a unique SID. Every domain (NT4, ADS, Samba) contains accounts that
 exist within the domain security context which is defined by the domain SID.
 </p><p>
-<a class="indexterm" name="id2561376"></a>
-<a class="indexterm" name="id2561383"></a>
+<a class="indexterm" name="id2561374"></a>
+<a class="indexterm" name="id2561380"></a>
 A domain member server will have a SID that differs from the domain SID.  The domain member server can be
 configured to regard all domain users as local users. It can also be configured to recognize domain users and
 groups as non-local. SIDs are persistent. A typical domain of user SID looks like this:
@@ -82,9 +82,9 @@ S-1-5-21-726309263-4128913605-1168186429-500
 </pre><p>
 The result is that every account in the Windows networking world has a globally unique security identifier.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2561430"></a>
-<a class="indexterm" name="id2561439"></a>
-<a class="indexterm" name="id2561446"></a>
+<a class="indexterm" name="id2561427"></a>
+<a class="indexterm" name="id2561437"></a>
+<a class="indexterm" name="id2561444"></a>
 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
@@ -92,44 +92,44 @@ account). Refer to <a class="link" href="domain-member.html" title="Chapter�6.�D
 </p></div><p>
 The following functionalities are new to the Samba-3 release:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2561480"></a>
+	<a class="indexterm" name="id2561477"></a>
 	Samba-3 supports the use of a choice of backends that may be used in which user, group and machine
 	accounts may be stored. Multiple passwd backends can be used in combination, either as additive backend
 	data sets, or as fail-over data sets.
 	</p><p>
-	<a class="indexterm" name="id2561496"></a>
-	<a class="indexterm" name="id2561503"></a>
-	<a class="indexterm" name="id2561510"></a>
-	<a class="indexterm" name="id2561517"></a>
-	<a class="indexterm" name="id2561524"></a>
+	<a class="indexterm" name="id2561494"></a>
+	<a class="indexterm" name="id2561501"></a>
+	<a class="indexterm" name="id2561507"></a>
+	<a class="indexterm" name="id2561514"></a>
+	<a class="indexterm" name="id2561521"></a>
 	An LDAP passdb backend confers the benefit that the account backend can be distributed and replicated,
 	which is of great value because it confers scalability and provides a high degree of reliability. 
 	</p></li><li><p>
-	<a class="indexterm" name="id2561538"></a>
-	<a class="indexterm" name="id2561550"></a>
-	<a class="indexterm" name="id2561559"></a>
+	<a class="indexterm" name="id2561536"></a>
+	<a class="indexterm" name="id2561547"></a>
+	<a class="indexterm" name="id2561557"></a>
 	Windows NT4 domain trusts. Samba-3 supports workstation and server (machine) trust accounts. It also
 	supports Windows NT4 style interdomain trust accounts, which further assists in network scalability
 	and interoperability.
 	</p></li><li><p>
-	<a class="indexterm" name="id2561574"></a>
-	<a class="indexterm" name="id2561581"></a>
-	<a class="indexterm" name="id2561588"></a>
-	<a class="indexterm" name="id2561595"></a>
-	<a class="indexterm" name="id2561604"></a>
-	<a class="indexterm" name="id2561614"></a>
+	<a class="indexterm" name="id2561572"></a>
+	<a class="indexterm" name="id2561579"></a>
+	<a class="indexterm" name="id2561585"></a>
+	<a class="indexterm" name="id2561592"></a>
+	<a class="indexterm" name="id2561602"></a>
+	<a class="indexterm" name="id2561611"></a>
 	Operation without NetBIOS over TCP/IP, rather using the raw SMB over TCP/IP. Note, this is feasible
 	only when operating as a Microsoft active directory domain member server. When acting as a Samba domain
 	controller the use of NetBIOS is necessary to provide network browsing support.
 	</p></li><li><p>
-	<a class="indexterm" name="id2561632"></a>
-	<a class="indexterm" name="id2561639"></a>
-	<a class="indexterm" name="id2561646"></a>
+	<a class="indexterm" name="id2561629"></a>
+	<a class="indexterm" name="id2561636"></a>
+	<a class="indexterm" name="id2561643"></a>
 	Samba-3 provides NetBIOS name services (WINS), NetBIOS over TCP/IP (TCP port 139) session services, SMB over
 	TCP/IP (TCP port 445) session services, and Microsoft compatible ONC DCE RPC services (TCP port 135)
 	services.
 	</p></li><li><p>
-	<a class="indexterm" name="id2561661"></a>
+	<a class="indexterm" name="id2561658"></a>
 	Management of users and groups via the User Manager for Domains. This can be done on any MS Windows client
 	using the <code class="filename">Nexus.exe</code> toolkit for Windows 9x/Me, or using the SRVTOOLS.EXE package for MS
 	Windows NT4/200x/XP platforms. These packages are available from Microsoft's Web site.
@@ -139,55 +139,55 @@ The following functionalities are new to the Samba-3 release:
 	</p></li></ul></div><p>
 The following functionalities are not provided by Samba-3:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2561698"></a>
-	<a class="indexterm" name="id2561704"></a>
+	<a class="indexterm" name="id2561695"></a>
+	<a class="indexterm" name="id2561702"></a>
 	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 Windows NT PDC. Samba-3 can not
 	participate in replication of account data to Windows PDCs and BDCs.
 	</p></li><li><p>
-	<a class="indexterm" name="id2561720"></a>
-	<a class="indexterm" name="id2561727"></a>
+	<a class="indexterm" name="id2561718"></a>
+	<a class="indexterm" name="id2561725"></a>
 	Acting as a Windows 2000 active directory 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.
 	Active directory domain control is one of the features that is being developed in Samba-4, the next
 	generation Samba release. At this time there are no plans to enable active directory domain control
 	support during the Samba-3 series life-cycle.
 	</p></li><li><p>
-	<a class="indexterm" name="id2561746"></a>
-	<a class="indexterm" name="id2561753"></a>
-	<a class="indexterm" name="id2561760"></a>
+	<a class="indexterm" name="id2561744"></a>
+	<a class="indexterm" name="id2561750"></a>
+	<a class="indexterm" name="id2561757"></a>
 	The Windows 200x/XP Microsoft Management Console (MMC) cannot be used to manage a Samba-3 server. For this you
 	can use only the MS Windows NT4 Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are
 	part of the SVRTOOLS.EXE package mentioned later.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2561778"></a>
-<a class="indexterm" name="id2561785"></a>
+<a class="indexterm" name="id2561776"></a>
+<a class="indexterm" name="id2561783"></a>
 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/Windows
 200x-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>
-<a class="indexterm" name="id2561802"></a>
+<a class="indexterm" name="id2561800"></a>
 Samba-3 implements 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 class="link" href="groupmapping.html" title="Chapter�12.�Group Mapping: MS Windows and UNIX">Group Mapping: MS
 Windows and UNIX</a>.
 </p><p>
-<a class="indexterm" name="id2561826"></a>
-<a class="indexterm" name="id2561833"></a>
-<a class="indexterm" name="id2561842"></a>
+<a class="indexterm" name="id2561823"></a>
+<a class="indexterm" name="id2561830"></a>
+<a class="indexterm" name="id2561839"></a>
 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 to <a class="link" href="domain-member.html#machine-trust-accounts" title="MS Windows Workstation/Server Machine Trust Accounts">MS
 Windows Workstation/Server Machine Trust Accounts</a>. With Samba-3 there can be multiple backends for
 this. A complete discussion of account database backends can be found in <a class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">Account
 Information Databases</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561872"></a>Single Sign-On and Domain Security</h2></div></div></div><p>
-<a class="indexterm" name="id2561880"></a>
-<a class="indexterm" name="id2561889"></a>
-<a class="indexterm" name="id2561896"></a>
-<a class="indexterm" name="id2561903"></a>
-<a class="indexterm" name="id2561910"></a>
-<a class="indexterm" name="id2561916"></a>
-<a class="indexterm" name="id2561923"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2561870"></a>Single Sign-On and Domain Security</h2></div></div></div><p>
+<a class="indexterm" name="id2561878"></a>
+<a class="indexterm" name="id2561886"></a>
+<a class="indexterm" name="id2561893"></a>
+<a class="indexterm" name="id2561900"></a>
+<a class="indexterm" name="id2561907"></a>
+<a class="indexterm" name="id2561914"></a>
+<a class="indexterm" name="id2561921"></a>
 When network administrators  are asked to describe the benefits of Windows NT4 and active directory networking
 the most often mentioned feature is that of single sign-on (SSO). Many companies have implemented SSO
 solutions. The mode of implementation of a single sign-on solution is an important factor in the practice of
@@ -197,16 +197,16 @@ uncommon that users may need to remember more than ten login IDs and passwords.
 when the password for each system must be changed at regular intervals, and particularly so where password
 uniqueness and history limits are applied.
 </p><p>
-<a class="indexterm" name="id2561947"></a>
+<a class="indexterm" name="id2561944"></a>
 There is a broadly held perception that SSO is the answer to the problem of users having to deal with too many
 information system access credentials (username/password pairs). Many elaborate schemes have been devised to
 make it possible to deliver a user-friendly SSO solution. The trouble is that if this implementation is not
 done correctly, the site may end up paying dearly by way of complexity and management overheads. Simply put,
 many SSO solutions are an administrative nightmare.
 </p><p>
-<a class="indexterm" name="id2561965"></a>
-<a class="indexterm" name="id2561972"></a>
-<a class="indexterm" name="id2561979"></a>
+<a class="indexterm" name="id2561962"></a>
+<a class="indexterm" name="id2561969"></a>
+<a class="indexterm" name="id2561976"></a>
 SSO implementations utilize centralization of all user account information. Depending on environmental
 complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to
 change the solution architecture so as to accommodate a new identity management and user authentication system.
@@ -215,11 +215,11 @@ behalf of the user. The software that gets layered over the old system may simpl
 authentication system. This means that the addition of SSO increases over-all information systems complexity.
 Ideally, the implementation of SSO should reduce complexity and reduce administative overheads.
 </p><p>
-<a class="indexterm" name="id2562001"></a>
-<a class="indexterm" name="id2562008"></a>
-<a class="indexterm" name="id2562017"></a>
-<a class="indexterm" name="id2562027"></a>
-<a class="indexterm" name="id2562034"></a>
+<a class="indexterm" name="id2561998"></a>
+<a class="indexterm" name="id2562005"></a>
+<a class="indexterm" name="id2562015"></a>
+<a class="indexterm" name="id2562024"></a>
+<a class="indexterm" name="id2562031"></a>
 The initial goal of many network administrators is often to create and use a centralized identity management
 system. It is often assumed that such a centralized system will use a single authentication infrastructure
 that can be used by all information systems. The Microsoft Windows NT4 security domain architecture and the
@@ -232,14 +232,14 @@ system it uses because its implementation will be excessively invasive from a re
 because application software has built-in dependencies on particular elements of the way user authentication
 and access control were designed and built.
 </p><p>
-<a class="indexterm" name="id2562063"></a>
-<a class="indexterm" name="id2562070"></a>
-<a class="indexterm" name="id2562076"></a>
-<a class="indexterm" name="id2562084"></a>
-<a class="indexterm" name="id2562091"></a>
-<a class="indexterm" name="id2562098"></a>
-<a class="indexterm" name="id2562104"></a>
-<a class="indexterm" name="id2562111"></a>
+<a class="indexterm" name="id2562060"></a>
+<a class="indexterm" name="id2562067"></a>
+<a class="indexterm" name="id2562074"></a>
+<a class="indexterm" name="id2562081"></a>
+<a class="indexterm" name="id2562088"></a>
+<a class="indexterm" name="id2562095"></a>
+<a class="indexterm" name="id2562102"></a>
+<a class="indexterm" name="id2562109"></a>
 Over the past decade an industry has been developed around the various methods that have been built to get
 around the key limitations of legacy information technology systems. One approach that is often used involves
 the use of a meta-directory. The meta-directory stores user credentials for all disparate information systems
@@ -248,22 +248,22 @@ rigidly enforced work-flow protocol for managing user rights and privileges with
 are provisioned by the new infrastructure makes possible user access to all systems using a single set of user
 credentials.
 </p><p>
-<a class="indexterm" name="id2562133"></a>
-<a class="indexterm" name="id2562143"></a>
-<a class="indexterm" name="id2562152"></a>
-<a class="indexterm" name="id2562162"></a>
+<a class="indexterm" name="id2562130"></a>
+<a class="indexterm" name="id2562140"></a>
+<a class="indexterm" name="id2562150"></a>
+<a class="indexterm" name="id2562159"></a>
 The Organization for the Advancement of Structured Information Standards (OASIS) has developed the Security
 Assertion Markup Language (SAML), a structured method for communication of authentication information. The
 over-all umbrella name for the technologies and methods that deploy SAML is called Federated Identity
 Management (FIM). FIM depends on each system in the complex maze of disparate information systems to
 authenticate their respective users and vouch for secure access to the services each provides.
 </p><p>
-<a class="indexterm" name="id2562181"></a>
-<a class="indexterm" name="id2562190"></a>
-<a class="indexterm" name="id2562197"></a>
-<a class="indexterm" name="id2562204"></a>
-<a class="indexterm" name="id2562211"></a>
-<a class="indexterm" name="id2562217"></a>
+<a class="indexterm" name="id2562178"></a>
+<a class="indexterm" name="id2562188"></a>
+<a class="indexterm" name="id2562195"></a>
+<a class="indexterm" name="id2562202"></a>
+<a class="indexterm" name="id2562208"></a>
+<a class="indexterm" name="id2562214"></a>
 SAML documents can be wrapped in a Simple Object Access Protocol (SOAP) message for the computer-to-computer
 communications needed for Web services. Or they may be passed between Web servers of federated organizations
 that share live services. The Liberty Alliance, an industry group formed to promote federated-identity
@@ -273,11 +273,11 @@ converge when the SAML 2.0 standard is introduced. A few Web access-management p
 but implementation of the technology mostly requires customization to integrate applications and develop user
 interfaces. In a nutshell, that is why FIM is a big and growing industry.
 </p><p>
-<a class="indexterm" name="id2562253"></a>
-<a class="indexterm" name="id2562260"></a>
-<a class="indexterm" name="id2562266"></a>
-<a class="indexterm" name="id2562273"></a>
-<a class="indexterm" name="id2562280"></a>
+<a class="indexterm" name="id2562250"></a>
+<a class="indexterm" name="id2562257"></a>
+<a class="indexterm" name="id2562264"></a>
+<a class="indexterm" name="id2562271"></a>
+<a class="indexterm" name="id2562277"></a>
 Ignoring the bigger picture, which is beyond the scope of this book, the migration of all user and group
 management to a centralized system is a step in the right direction. It is essential for interoperability
 reasons to locate the identity management system data in a directory such as Microsoft Active Directory
@@ -286,20 +286,20 @@ access (such as LDAP) and that can be coupled with a flexible array of authentic
 kerberos) that use the protocols that are defined by the various general security service application
 programming interface (GSSAPI) services.
 </p><p>
-<a class="indexterm" name="id2562305"></a>
-<a class="indexterm" name="id2562311"></a>
-<a class="indexterm" name="id2562318"></a>
+<a class="indexterm" name="id2562302"></a>
+<a class="indexterm" name="id2562309"></a>
+<a class="indexterm" name="id2562315"></a>
 A growing number of companies provide authentication agents for disparate legacy platforms to permit the use
 of LDAP systems. Thus the use of OpenLDAP, the dominant open source software implementation of the light
 weight directory access protocol standard. This fact, means that by providing support in Samba for the use of
 LDAP and Microsoft ADS make Samba a highly scalable and forward reaching organizational networking technology.
 </p><p>
-<a class="indexterm" name="id2562336"></a>
-<a class="indexterm" name="id2562342"></a>
-<a class="indexterm" name="id2562349"></a>
-<a class="indexterm" name="id2562356"></a>
-<a class="indexterm" name="id2562363"></a>
-<a class="indexterm" name="id2562370"></a>
+<a class="indexterm" name="id2562333"></a>
+<a class="indexterm" name="id2562340"></a>
+<a class="indexterm" name="id2562346"></a>
+<a class="indexterm" name="id2562353"></a>
+<a class="indexterm" name="id2562360"></a>
+<a class="indexterm" name="id2562367"></a>
 Microsoft ADS provides purely proprietary services that, with limitation, can be extended to provide a
 centralized authentication infrastructure. Samba plus LDAP provides a similar opportunity for extension of a
 centralized authentication architecture, but it is the fact that the Samba Team are pro-active in introducing
@@ -307,29 +307,29 @@ the extension of authentication services, using LDAP or otherwise, to applicatio
 source proxy server) through tools such as the <code class="literal">ntlm_auth</code> utility, that does much to create
 sustainable choice and competition in the FIM market place.
 </p><p>
-<a class="indexterm" name="id2562395"></a>
-<a class="indexterm" name="id2562402"></a>
-<a class="indexterm" name="id2562409"></a>
+<a class="indexterm" name="id2562392"></a>
+<a class="indexterm" name="id2562399"></a>
+<a class="indexterm" name="id2562406"></a>
 Primary domain control, if it is to be scalable to meet the needs of large sites, must therefore be capable of
 using LDAP. The rapid adoption of OpenLDAP, and Samba configurations that use it, is ample proof that the era
 of the directory has started. Samba-3 does not demand the use of LDAP, but the demand for a mechanism by which
 user and group identity information can be distributed makes it an an unavoidable option.
 </p><p>
-<a class="indexterm" name="id2562433"></a>
-<a class="indexterm" name="id2562440"></a>
-<a class="indexterm" name="id2562446"></a>
+<a class="indexterm" name="id2562430"></a>
+<a class="indexterm" name="id2562437"></a>
+<a class="indexterm" name="id2562444"></a>
 At this time, the use of Samba based BDCs, necessitates the use of LDAP. The most commonly used LDAP
 implementation used by Samba sites is OpenLDAP. It is possible to use any standards compliant LDAP server.
 Those known to work includes those manufactured by: IBM, CA, Novell (e-Directory), and others.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562461"></a>Basics of Domain Control</h2></div></div></div><p>
-<a class="indexterm" name="id2562469"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562458"></a>Basics of Domain Control</h2></div></div></div><p>
+<a class="indexterm" name="id2562466"></a>
 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="id2562480"></a>Domain Controller Types</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>NT4 style Primary Domain Controller</p></li><li><p>NT4 style Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p>
-<a class="indexterm" name="id2562506"></a>
-<a class="indexterm" name="id2562513"></a>
-<a class="indexterm" name="id2562520"></a>
-<a class="indexterm" name="id2562529"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562478"></a>Domain Controller Types</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>NT4 style Primary Domain Controller</p></li><li><p>NT4 style Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p>
+<a class="indexterm" name="id2562504"></a>
+<a class="indexterm" name="id2562510"></a>
+<a class="indexterm" name="id2562517"></a>
+<a class="indexterm" name="id2562526"></a>
 The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in MS Windows NT4. In
 Windows 200x domain control architecture, this role is held by domain controllers.  Folklore dictates that
 because of its role in the MS Windows network, the domain controller should be the most powerful and most
@@ -337,37 +337,37 @@ capable machine in the network.  As strange as it may seem to say this here, goo
 dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone
 (domain member) servers than in the domain controllers.
 </p><p>
-<a class="indexterm" name="id2562557"></a>
-<a class="indexterm" name="id2562563"></a>
-<a class="indexterm" name="id2562570"></a>
-<a class="indexterm" name="id2562577"></a>
-<a class="indexterm" name="id2562584"></a>
+<a class="indexterm" name="id2562554"></a>
+<a class="indexterm" name="id2562561"></a>
+<a class="indexterm" name="id2562567"></a>
+<a class="indexterm" name="id2562574"></a>
+<a class="indexterm" name="id2562581"></a>
 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 Security Account Manager (SAM). It plays a key
 part in NT4-type domain user authentication and in synchronization of the domain authentication
 database with BDCs. 
 </p><p>
-<a class="indexterm" name="id2562602"></a>
-<a class="indexterm" name="id2562613"></a>
-<a class="indexterm" name="id2562620"></a>
-<a class="indexterm" name="id2562629"></a>
+<a class="indexterm" name="id2562599"></a>
+<a class="indexterm" name="id2562610"></a>
+<a class="indexterm" name="id2562617"></a>
+<a class="indexterm" name="id2562626"></a>
 With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential
 hierarchy of domain controllers, each with its own area of delegated control. The master domain
 controller has the ability to override any downstream controller, but a downline controller has
 control only over its downline. With Samba-3, this functionality can be implemented using an
 LDAP-based user and machine account backend.
 </p><p>
-<a class="indexterm" name="id2562647"></a>
-<a class="indexterm" name="id2562654"></a>
+<a class="indexterm" name="id2562644"></a>
+<a class="indexterm" name="id2562651"></a>
 New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM
-database (one of the registry files)<sup>[<a name="id2562663" href="#ftn.id2562663" class="footnote">1</a>]</sup>
-</p><p>
-<a class="indexterm" name="id2562678"></a>
-<a class="indexterm" name="id2562684"></a>
-<a class="indexterm" name="id2562691"></a>
-<a class="indexterm" name="id2562698"></a>
-<a class="indexterm" name="id2562704"></a>
-<a class="indexterm" name="id2562711"></a>
+database (one of the registry files)<sup>[<a name="id2562660" href="#ftn.id2562660" class="footnote">1</a>]</sup>
+</p><p>
+<a class="indexterm" name="id2562676"></a>
+<a class="indexterm" name="id2562683"></a>
+<a class="indexterm" name="id2562689"></a>
+<a class="indexterm" name="id2562696"></a>
+<a class="indexterm" name="id2562703"></a>
+<a class="indexterm" name="id2562710"></a>
 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 most likely service network logon requests. The PDC will answer network logon
@@ -379,13 +379,13 @@ the UDP broadcast protocol. This means that the netlogon server that the windows
 by a number of variables, thus there is no simple determinant of whether a PDC or a BDC will serve a
 particular logon authentication request.
 </p><p>
-<a class="indexterm" name="id2562742"></a>
-<a class="indexterm" name="id2562748"></a>
+<a class="indexterm" name="id2562740"></a>
+<a class="indexterm" name="id2562747"></a>
 A Windows NT4 BDC can be promoted to a PDC. If the PDC is online 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 other appropriate changes also need to be made.
 </p><p>
-<a class="indexterm" name="id2562764"></a>
+<a class="indexterm" name="id2562762"></a>
 With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be.
 It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provide to convert a
 Windows NT4 domain controller to a domain member server or a standalone server is to reinstall it. The install
@@ -393,28 +393,28 @@ 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>Standalone Server</em></span>  one that plays no part in SAM synchronization,
 		has its own authentication database, and plays no role in domain security.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2562833"></a>
+<a class="indexterm" name="id2562831"></a>
 Algin Technology LLC provide a commercial tool that makes it possible to promote a Windows NT4 standalone
 server to a PDC or a BDC, and also permits this process to be reversed. Refer to the <a class="ulink" href="http://utools.com/UPromote.asp" target="_top">Algin</a> web site for further information.
 </p></div><p>
-<a class="indexterm" name="id2562852"></a>
-<a class="indexterm" name="id2562864"></a>
+<a class="indexterm" name="id2562851"></a>
+<a class="indexterm" name="id2562862"></a>
 Samba-3 servers can readily be converted to and from domain controller roles through simple changes to the
 <code class="filename">smb.conf</code> file. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active
 Directory domain.
 </p><p>
-<a class="indexterm" name="id2562884"></a>
+<a class="indexterm" name="id2562882"></a>
 For the sake of providing a complete picture, MS Windows 2000 domain control configuration is done after the server has been
 installed. Please refer to Microsoft documentation for the procedures that should be followed to convert a
 domain member server to or from a domain control, and to install or remove active directory service support.
 </p><p>
-<a class="indexterm" name="id2562902"></a>
-<a class="indexterm" name="id2562911"></a>
+<a class="indexterm" name="id2562901"></a>
+<a class="indexterm" name="id2562910"></a>
 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 also supports the
 MS Windows 200x domain control protocols.
 </p><p>
-<a class="indexterm" name="id2562927"></a>
+<a class="indexterm" name="id2562926"></a>
 At this time any appearance that Samba-3 is capable of acting as a <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
@@ -422,19 +422,19 @@ configuration and management requirements. Samba can act as a NT4-style domain c
 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 Active Directory logon scripts.</p></li><li><p>Can't use Active Directory management tools to manage users and machines.</p></li><li><p>Registry changes tattoo the main registry, while with Active Directory they do not leave
 		permanent changes in effect.</p></li><li><p>Without Active Directory you cannot perform the function of exporting specific
-		applications to specific users or groups.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562984"></a>Preparing for Domain Control</h3></div></div></div><p>
-<a class="indexterm" name="id2562992"></a>
-<a class="indexterm" name="id2562999"></a>
-<a class="indexterm" name="id2563006"></a>
-<a class="indexterm" name="id2563013"></a>
+		applications to specific users or groups.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562982"></a>Preparing for Domain Control</h3></div></div></div><p>
+<a class="indexterm" name="id2562991"></a>
+<a class="indexterm" name="id2562997"></a>
+<a class="indexterm" name="id2563004"></a>
+<a class="indexterm" name="id2563011"></a>
 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>standalone</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>
-<a class="indexterm" name="id2563038"></a>
-<a class="indexterm" name="id2563045"></a>
-<a class="indexterm" name="id2563054"></a>
+<a class="indexterm" name="id2563036"></a>
+<a class="indexterm" name="id2563043"></a>
+<a class="indexterm" name="id2563052"></a>
 It should be noted that workgroup membership involves no special configuration other than the machine being
 configured so the network configuration has a commonly used name for its 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
@@ -442,16 +442,16 @@ Accounts, and any concept of membership as such is limited to the fact that all
 neighborhood to be logically grouped together. Again, just to be clear: <span class="emphasis"><em>workgroup mode does not
 involve security machine accounts</em></span>.
 </p><p>
-<a class="indexterm" name="id2563077"></a>
-<a class="indexterm" name="id2563084"></a>
-<a class="indexterm" name="id2563093"></a>
+<a class="indexterm" name="id2563075"></a>
+<a class="indexterm" name="id2563082"></a>
+<a class="indexterm" name="id2563092"></a>
 Domain member machines have a machine trust account in the domain accounts database. A special procedure
 must be followed on each machine to effect domain membership. This procedure, which can be done
 only by the local machine Administrator account, creates the domain machine account (if it does
 not exist), and then initializes that account. When the client first logs onto the
 domain, a machine trust account password change will be automatically triggered.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2563112"></a>
+<a class="indexterm" name="id2563111"></a>
 When Samba is configured as a domain controller, secure network operation demands that
 all MS Windows NT4/200x/XP Professional clients should be configured as domain members.
 If a machine is not made a member of the domain, then it will operate like a workgroup
@@ -460,14 +460,14 @@ information regarding domain membership.
 </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="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>).</p></li><li><p>Consistent configuration of name resolution.<sup>[<a name="id2563168" href="#ftn.id2563168" class="footnote">2</a>]</sup></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 NT4/2000 Professional and Windows XP Professional client machines to become domain members.</p></li></ul></div><p>
+</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="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>).</p></li><li><p>Consistent configuration of name resolution.<sup>[<a name="id2563166" href="#ftn.id2563166" class="footnote">2</a>]</sup></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 NT4/2000 Professional and Windows XP Professional 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="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>).</p></li><li><p>Network logon configuration (since Windows 9x/Me/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 &#8220;<span class="quote">Client for MS Windows Networks</span>&#8221; 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>
-<a class="indexterm" name="id2563290"></a>
-<a class="indexterm" name="id2563296"></a>
+<a class="indexterm" name="id2563288"></a>
+<a class="indexterm" name="id2563294"></a>
 Roaming profiles and system/network policies are advanced network administration topics
 that are covered in <a class="link" href="ProfileMgmt.html" title="Chapter�27.�Desktop Profile Management">Desktop Profile Management</a> and
 <a class="link" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies">System and Account Policies</a> of this document. However, these are not
@@ -475,102 +475,102 @@ necessarily specific to a Samba PDC as much as they are related to Windows NT ne
 </p></div><p>
 A domain controller is an SMB/CIFS server that:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2563332"></a>
-	<a class="indexterm" name="id2563341"></a>
-	<a class="indexterm" name="id2563348"></a>
-	<a class="indexterm" name="id2563355"></a>
-	<a class="indexterm" name="id2563362"></a>
+	<a class="indexterm" name="id2563330"></a>
+	<a class="indexterm" name="id2563339"></a>
+	<a class="indexterm" name="id2563346"></a>
+	<a class="indexterm" name="id2563353"></a>
+	<a class="indexterm" name="id2563360"></a>
 	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>
-	<a class="indexterm" name="id2563377"></a>
-	<a class="indexterm" name="id2563384"></a>
+	<a class="indexterm" name="id2563376"></a>
+	<a class="indexterm" name="id2563382"></a>
 	Provides the NETLOGON service. (This is actually a collection of services that runs over
 	multiple 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>
-<a class="indexterm" name="id2563404"></a>
-<a class="indexterm" name="id2563416"></a>
-<a class="indexterm" name="id2563428"></a>
-<a class="indexterm" name="id2563435"></a>
-<a class="indexterm" name="id2563441"></a>
+<a class="indexterm" name="id2563403"></a>
+<a class="indexterm" name="id2563414"></a>
+<a class="indexterm" name="id2563426"></a>
+<a class="indexterm" name="id2563433"></a>
+<a class="indexterm" name="id2563440"></a>
 It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON
 service that Samba calls the <a class="link" href="smb.conf.5.html#DOMAINLOGONS" target="_top">domain logons</a> functionality (after the name of the
 parameter in the <code class="filename">smb.conf</code> file). Additionally, one server in a Samba-3 domain must advertise itself as the
-domain master browser.<sup>[<a name="id2563473" href="#ftn.id2563473" class="footnote">3</a>]</sup> This causes the PDC to claim a domain-specific NetBIOS name that identifies
+domain master browser.<sup>[<a name="id2563471" href="#ftn.id2563471" class="footnote">3</a>]</sup> This causes the PDC to claim a domain-specific NetBIOS name that identifies
 it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on
 broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network.
 Browser clients then contact their LMB, 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="id2563495"></a>Domain Control: Example Configuration</h2></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2563493"></a>Domain Control: Example Configuration</h2></div></div></div><p>
 The first step in creating a working Samba PDC is to understand the parameters necessary
 in <code class="filename">smb.conf</code>. An example <code class="filename">smb.conf</code> for acting as a PDC can be found in <a class="link" href="samba-pdc.html#pdc-example" title="Example�4.1.�smb.conf for being a PDC">the
 smb.conf file for an example PDC</a>. 
-</p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example�4.1.�smb.conf for being a PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2563550"></a></td></tr><tr><td><a class="indexterm" name="id2563557"></a></td></tr><tr><td><a class="indexterm" name="id2563563"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2563575"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id2563587"></a><em class="parameter"><code>preferred master = auto</code></em></td></tr><tr><td><a class="indexterm" name="id2563599"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563610"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563622"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2563634"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563646"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2563657"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2563669"></a><em class="parameter"><code>logon home = \\homeserver\%U\winprofile</code></em></td></tr><tr><td><a class="indexterm" name="id2563681"></a><em class="parameter"><code>logon script = logon.cmd</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2563702"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2563714"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563725"></a></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2563741"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2563753"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id2563764"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2563776"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr></table></div></div><br class="example-break"><p>
+</p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example�4.1.�smb.conf for being a PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2563548"></a></td></tr><tr><td><a class="indexterm" name="id2563555"></a></td></tr><tr><td><a class="indexterm" name="id2563562"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2563574"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id2563585"></a><em class="parameter"><code>preferred master = auto</code></em></td></tr><tr><td><a class="indexterm" name="id2563597"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563609"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563621"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2563632"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563644"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id2563656"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id2563667"></a><em class="parameter"><code>logon home = \\homeserver\%U\winprofile</code></em></td></tr><tr><td><a class="indexterm" name="id2563679"></a><em class="parameter"><code>logon script = logon.cmd</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2563700"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2563712"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2563724"></a></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id2563739"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id2563751"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id2563763"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2563774"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr></table></div></div><br class="example-break"><p>
 The basic options shown in <a class="link" href="samba-pdc.html#pdc-example" title="Example�4.1.�smb.conf for being a PDC">this example</a> are explained as follows:
 </p><div class="variablelist"><dl><dt><span class="term">passdb backend </span></dt><dd><p>
-		<a class="indexterm" name="id2563810"></a>
-		<a class="indexterm" name="id2563819"></a>
-		<a class="indexterm" name="id2563826"></a>
-		<a class="indexterm" name="id2563833"></a>
-		<a class="indexterm" name="id2563840"></a>
-		<a class="indexterm" name="id2563847"></a>
+		<a class="indexterm" name="id2563809"></a>
+		<a class="indexterm" name="id2563818"></a>
+		<a class="indexterm" name="id2563825"></a>
+		<a class="indexterm" name="id2563831"></a>
+		<a class="indexterm" name="id2563838"></a>
+		<a class="indexterm" name="id2563845"></a>
 		This contains all the user and group account information. Acceptable values for a PDC
 		are: <span class="emphasis"><em>smbpasswd, tdbsam, and ldapsam</em></span>. The &#8220;<span class="quote">guest</span>&#8221; entry provides
 		default accounts and is included by default; there is no need to add it explicitly.
 		</p><p>
-		<a class="indexterm" name="id2563868"></a>
-		<a class="indexterm" name="id2563875"></a>
-		<a class="indexterm" name="id2563882"></a>
-		<a class="indexterm" name="id2563888"></a>
+		<a class="indexterm" name="id2563866"></a>
+		<a class="indexterm" name="id2563873"></a>
+		<a class="indexterm" name="id2563880"></a>
+		<a class="indexterm" name="id2563887"></a>
 		Where use of BDCs is intended, the only logical choice is
 		to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files
 		cannot effectively be distributed and therefore should not be used.
 		</p></dd><dt><span class="term">Domain Control Parameters </span></dt><dd><p>
-		<a class="indexterm" name="id2563909"></a>
-		<a class="indexterm" name="id2563916"></a>
-		<a class="indexterm" name="id2563923"></a>
-		<a class="indexterm" name="id2563930"></a>
+		<a class="indexterm" name="id2563908"></a>
+		<a class="indexterm" name="id2563914"></a>
+		<a class="indexterm" name="id2563921"></a>
+		<a class="indexterm" name="id2563928"></a>
 		The parameters <span class="emphasis"><em>os level, preferred master, domain master, security, 
 		encrypt passwords</em></span>, and <span class="emphasis"><em>domain logons</em></span> play a central role in assuring domain
 		control and network logon support.
 		</p><p>
-		<a class="indexterm" name="id2563953"></a>
-		<a class="indexterm" name="id2563959"></a>
+		<a class="indexterm" name="id2563951"></a>
+		<a class="indexterm" name="id2563958"></a>
 		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 DMB, 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 class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">Account Information Databases</a>.
 		</p></dd><dt><span class="term">Environment Parameters </span></dt><dd><p>
-		<a class="indexterm" name="id2563996"></a>
-		<a class="indexterm" name="id2564003"></a>
-		<a class="indexterm" name="id2564010"></a>
-		<a class="indexterm" name="id2564017"></a>
+		<a class="indexterm" name="id2563995"></a>
+		<a class="indexterm" name="id2564002"></a>
+		<a class="indexterm" name="id2564008"></a>
+		<a class="indexterm" name="id2564015"></a>
 		The parameters <span class="emphasis"><em>logon path, logon home, logon drive</em></span>, and <span class="emphasis"><em>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>
-		<a class="indexterm" name="id2564046"></a>
-		<a class="indexterm" name="id2564053"></a>
-		<a class="indexterm" name="id2564060"></a>
-		<a class="indexterm" name="id2564067"></a>
-		<a class="indexterm" name="id2564074"></a>
-		<a class="indexterm" name="id2564081"></a>
+		<a class="indexterm" name="id2564044"></a>
+		<a class="indexterm" name="id2564051"></a>
+		<a class="indexterm" name="id2564058"></a>
+		<a class="indexterm" name="id2564065"></a>
+		<a class="indexterm" name="id2564072"></a>
+		<a class="indexterm" name="id2564079"></a>
 		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>
-		<a class="indexterm" name="id2564104"></a>
-		<a class="indexterm" name="id2564111"></a>
-		<a class="indexterm" name="id2564117"></a>
-		<a class="indexterm" name="id2564124"></a>
-		<a class="indexterm" name="id2564131"></a>
+		<a class="indexterm" name="id2564102"></a>
+		<a class="indexterm" name="id2564109"></a>
+		<a class="indexterm" name="id2564116"></a>
+		<a class="indexterm" name="id2564123"></a>
+		<a class="indexterm" name="id2564129"></a>
 		This share is used to store user desktop profiles. Each 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 &#8220;<span class="quote">fake_permissions</span>&#8221; that may be installed on this share. This will
@@ -580,12 +580,12 @@ The basic options shown in <a class="link" href="samba-pdc.html#pdc-example" tit
 The above parameters make for a full set of functionality that may define the server's mode
 of operation. The following <code class="filename">smb.conf</code> parameters are the essentials alone:
 </p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2564171"></a><em class="parameter"><code>netbios name = BELERIAND</code></em></td></tr><tr><td><a class="indexterm" name="id2564183"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2564195"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564207"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564218"></a><em class="parameter"><code>security = User</code></em></td></tr></table><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2564170"></a><em class="parameter"><code>netbios name = BELERIAND</code></em></td></tr><tr><td><a class="indexterm" name="id2564182"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2564193"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564205"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564217"></a><em class="parameter"><code>security = User</code></em></td></tr></table><p>
 </p><p>
 The additional parameters shown in the longer listing in this section just make for
 a more complete explanation.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564237"></a>Samba ADS Domain Control</h2></div></div></div><p>
-<a class="indexterm" name="id2564245"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564236"></a>Samba ADS Domain Control</h2></div></div></div><p>
+<a class="indexterm" name="id2564244"></a>
 Samba-3 is not, and cannot act as, an Active Directory server. It cannot truly function as an Active Directory
 PDC. The protocols for some of the functionality of 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
@@ -594,24 +594,24 @@ features or may change their behavior. This is mentioned for the benefit of thos
 capabilities in Samba-3 and who have asked when this functionality will be completed. The answer is maybe
 someday or maybe never!
 </p><p>
-<a class="indexterm" name="id2564267"></a>
-<a class="indexterm" name="id2564274"></a>
+<a class="indexterm" name="id2564265"></a>
+<a class="indexterm" name="id2564272"></a>
 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 controllers do not have. In short, Samba-3 is not NT4 and it
 is not Windows Server 200x: 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="id2564290"></a>Domain and Network Logon Configuration</h2></div></div></div><p>
-<a class="indexterm" name="id2564298"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2564289"></a>Domain and Network Logon Configuration</h2></div></div></div><p>
+<a class="indexterm" name="id2564297"></a>
 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="id2564309"></a>Domain Network Logon Service</h3></div></div></div><p>
-<a class="indexterm" name="id2564318"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564308"></a>Domain Network Logon Service</h3></div></div></div><p>
+<a class="indexterm" name="id2564316"></a>
 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="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = Yes</a>
 (the PDC); on all BDCs set the parameter <a class="link" href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master = No</a>.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564357"></a>Example Configuration</h4></div></div></div><div class="example"><a name="PDC-config"></a><p class="title"><b>Example�4.2.�smb.conf for being a PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2564386"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564398"></a><em class="parameter"><code>domain master = (Yes on PDC, No on BDCs)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2564418"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2564430"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2564442"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564454"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564467"></a>The Special Case of MS Windows XP Home Edition</h4></div></div></div><p>
-<a class="indexterm" name="id2564476"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564355"></a>Example Configuration</h4></div></div></div><div class="example"><a name="PDC-config"></a><p class="title"><b>Example�4.2.�smb.conf for being a PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2564385"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564396"></a><em class="parameter"><code>domain master = (Yes on PDC, No on BDCs)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2564417"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id2564429"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2564440"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2564452"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564466"></a>The Special Case of MS Windows XP Home Edition</h4></div></div></div><p>
+<a class="indexterm" name="id2564474"></a>
 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 cannot be done.
 The only option is to purchase the upgrade from MS Windows XP Home Edition to
@@ -625,12 +625,12 @@ Now that this has been said, please do not ask the mailing list or email any of
 Samba Team members with your questions asking how to make this work. It can't be done.
 If it can be done, then to do so would violate your software license agreement with
 Microsoft, and we recommend that you do not do that.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564506"></a>The Special Case of Windows 9x/Me</h4></div></div></div><p>
-<a class="indexterm" name="id2564514"></a>
-<a class="indexterm" name="id2564521"></a>
-<a class="indexterm" name="id2564528"></a>
-<a class="indexterm" name="id2564535"></a>
-<a class="indexterm" name="id2564542"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2564504"></a>The Special Case of Windows 9x/Me</h4></div></div></div><p>
+<a class="indexterm" name="id2564513"></a>
+<a class="indexterm" name="id2564519"></a>
+<a class="indexterm" name="id2564526"></a>
+<a class="indexterm" name="id2564533"></a>
+<a class="indexterm" name="id2564540"></a>
 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
@@ -638,22 +638,22 @@ 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 as MS Windows NT/200x.
 </p><p>
-<a class="indexterm" name="id2564558"></a>
+<a class="indexterm" name="id2564556"></a>
 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>
-<a class="indexterm" name="id2564574"></a>
-<a class="indexterm" name="id2564581"></a>
-<a class="indexterm" name="id2564588"></a>
+<a class="indexterm" name="id2564573"></a>
+<a class="indexterm" name="id2564580"></a>
+<a class="indexterm" name="id2564586"></a>
 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>
-<a class="indexterm" name="id2564602"></a>
+<a class="indexterm" name="id2564601"></a>
 When an SMB client in a domain wishes to log on, 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;
@@ -669,8 +669,8 @@ MS Windows XP Home edition is not able to join a domain and does not permit the
 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>
-	<a class="indexterm" name="id2564649"></a>
-	<a class="indexterm" name="id2564656"></a>
+	<a class="indexterm" name="id2564647"></a>
+	<a class="indexterm" name="id2564654"></a>
 	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&lt;1C&gt; at the
 	NetBIOS layer. The client chooses the first response it receives, which
@@ -679,13 +679,13 @@ performs a logon:
 	type that is registered by domain controllers (SMB/CIFS servers that provide
 	the netlogon service).
 	</p></li><li><p>
-	<a class="indexterm" name="id2564698"></a>
-	<a class="indexterm" name="id2564704"></a>
-	<a class="indexterm" name="id2564711"></a>
+	<a class="indexterm" name="id2564696"></a>
+	<a class="indexterm" name="id2564703"></a>
+	<a class="indexterm" name="id2564710"></a>
 	The client connects to that server, logs on (does an SMBsessetupX) and
 	then connects to the IPC$ share (using an SMBtconX).
 	</p></li><li><p>
-	<a class="indexterm" name="id2564727"></a>
+	<a class="indexterm" name="id2564725"></a>
 	The client does a NetWkstaUserLogon request, which retrieves the name
 	of the user's logon script. 
 	</p></li><li><p>
@@ -693,60 +693,60 @@ performs a logon:
 	If it is found and can be read, it is retrieved and executed by the client.
 	After this, the client disconnects from the NetLogon share.
 	</p></li><li><p>
-	<a class="indexterm" name="id2564752"></a>
-	<a class="indexterm" name="id2564759"></a>
+	<a class="indexterm" name="id2564750"></a>
+	<a class="indexterm" name="id2564757"></a>
 	The client 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 Windows 9x clients must reside in the user
 	home directory.
 	</p></li><li><p>
-	<a class="indexterm" name="id2564778"></a>
+	<a class="indexterm" name="id2564776"></a>
 	The client 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 share name and path. For example, <code class="filename">\\server\fred\.winprofile</code>.
 	If the profiles are found, they are implemented.
 	</p></li><li><p>
-	<a class="indexterm" name="id2564801"></a>
+	<a class="indexterm" name="id2564799"></a>
 	The client then disconnects from the user's home share and reconnects to
 	the NetLogon share and looks for <code class="filename">CONFIG.POL</code>, 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/Me logon server configuration is:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2564830"></a>
-	<a class="indexterm" name="id2564839"></a>
+	<a class="indexterm" name="id2564829"></a>
+	<a class="indexterm" name="id2564838"></a>
 	Password encryption is not required for a Windows 9x/Me logon server. But note
 	that beginning with MS Windows 98 the default setting is that plaintext
 	password support is disabled. It can be re-enabled with the registry
 	changes that are documented in <a class="link" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies">System and Account Policies</a>.
 	</p></li><li><p>
-	<a class="indexterm" name="id2564862"></a>
+	<a class="indexterm" name="id2564861"></a>
 	Windows 9x/Me clients do not require and do not use Machine Trust Accounts.
 	</p></li></ul></div><p>
-<a class="indexterm" name="id2564875"></a>
+<a class="indexterm" name="id2564873"></a>
 A Samba PDC will act as a Windows 9x/Me 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>
-<a class="indexterm" name="id2564889"></a>
+<a class="indexterm" name="id2564887"></a>
 Use of plaintext 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="id2564901"></a>Security Mode and Master Browsers</h3></div></div></div><p>
-<a class="indexterm" name="id2564909"></a>
-<a class="indexterm" name="id2564916"></a>
-<a class="indexterm" name="id2564923"></a>
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564899"></a>Security Mode and Master Browsers</h3></div></div></div><p>
+<a class="indexterm" name="id2564908"></a>
+<a class="indexterm" name="id2564914"></a>
+<a class="indexterm" name="id2564921"></a>
 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 it is okay to configure Samba as a domain controller that operates with security mode other than
 user-mode. The only security mode that will not work due to technical reasons is share-mode security. Domain
 and server mode security are really just a variation on SMB user-level security.
 </p><p>
-<a class="indexterm" name="id2564947"></a>
-<a class="indexterm" name="id2564954"></a>
-<a class="indexterm" name="id2564961"></a>
-<a class="indexterm" name="id2564967"></a>
-<a class="indexterm" name="id2564974"></a>
-<a class="indexterm" name="id2564981"></a>
-<a class="indexterm" name="id2564988"></a>
+<a class="indexterm" name="id2564945"></a>
+<a class="indexterm" name="id2564952"></a>
+<a class="indexterm" name="id2564959"></a>
+<a class="indexterm" name="id2564966"></a>
+<a class="indexterm" name="id2564972"></a>
+<a class="indexterm" name="id2564979"></a>
+<a class="indexterm" name="id2564986"></a>
 Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup
 when operating as a domain controller.  In a pure Microsoft Windows NT domain, the PDC wins the election to be
 the DMB, and then registers the DOMAIN&lt;1B&gt; NetBIOS name. This is not the name used by Windows clients
@@ -757,11 +757,11 @@ DMB, if it loses that election it will report a continuous and rapid sequence of
 Windows event logger complaining that it has lost the election to become a DMB.  For this reason, in networks
 where a Samba server is the PDC it is wise to configure the Samba domain controller as the DMB.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2565042"></a>
-<a class="indexterm" name="id2565048"></a>
-<a class="indexterm" name="id2565055"></a>
-<a class="indexterm" name="id2565062"></a>
-<a class="indexterm" name="id2565069"></a>
+<a class="indexterm" name="id2565040"></a>
+<a class="indexterm" name="id2565047"></a>
+<a class="indexterm" name="id2565054"></a>
+<a class="indexterm" name="id2565060"></a>
+<a class="indexterm" name="id2565068"></a>
 SMB/CIFS servers that register the DOMAIN&lt;1C&gt; name do so because they provide the network logon
 service. Server that register the DOMAIN&lt;1B&gt; name are DMBs  meaning that they are responsible
 for browse list synchronization across all machines that have registered the DOMAIN&lt;1D&gt; name. The later
@@ -782,15 +782,15 @@ Configuring a Samba box as a domain controller for a domain that already by defi
 PDC is asking for trouble. Therefore, you should always configure the Samba domain controller
 to be the DMB for its domain and set <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>.
 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="id2565181"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565186"></a>&#8220;<span class="quote">$</span>&#8221; Cannot Be Included in Machine Name</h3></div></div></div><p>
-<a class="indexterm" name="id2565197"></a>
-<a class="indexterm" name="id2565203"></a>
-<a class="indexterm" name="id2565210"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2565179"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565185"></a>&#8220;<span class="quote">$</span>&#8221; Cannot Be Included in Machine Name</h3></div></div></div><p>
+<a class="indexterm" name="id2565195"></a>
+<a class="indexterm" name="id2565202"></a>
+<a class="indexterm" name="id2565208"></a>
 A machine account, typically stored in <code class="filename">/etc/passwd</code>, takes the form of the machine
 name with a &#8220;<span class="quote">$</span>&#8221; appended. Some BSD systems will not create a user with a &#8220;<span class="quote">$</span>&#8221; in the name.
 Recent versions of FreeBSD have removed this limitation, but older releases are still in common use.
 </p><p>
-<a class="indexterm" name="id2565236"></a>
+<a class="indexterm" name="id2565234"></a>
 The problem is only in the program used to make the entry. Once made, it works perfectly.  Create a user
 without the &#8220;<span class="quote">$</span>&#8221;. Then use <code class="literal">vipw</code> to edit the entry, adding the &#8220;<span class="quote">$</span>&#8221;.
 Or create the whole entry with vipw if you like; make sure you use a unique user login ID.
@@ -798,8 +798,8 @@ Or create the whole entry with vipw if you like; make sure you use a unique user
 The UNIX tool <code class="literal">vipw</code> is a common tool for directly editing the <code class="filename">/etc/passwd</code> file.
 The use of vipw will ensure that shadow files (where used) will remain current with the passwd file. This is
 important for security reasons.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565287"></a>Joining Domain Fails Because of Existing Machine Account</h3></div></div></div><p>
-<a class="indexterm" name="id2565296"></a>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565286"></a>Joining Domain Fails Because of Existing Machine Account</h3></div></div></div><p>
+<a class="indexterm" name="id2565294"></a>
 &#8220;<span class="quote">I get told, `You already have a connection to the Domain....' or `Cannot join domain, the
 credentials supplied conflict with an existing set...' when creating a Machine Trust Account.</span>&#8221;
 </p><p>
@@ -814,12 +814,12 @@ This will break all network connections.
 Further, if the machine is already a &#8220;<span class="quote">member of a workgroup</span>&#8221; 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="id2565352"></a>The System Cannot Log You On (C000019B)</h3></div></div></div><p>&#8220;<span class="quote">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565350"></a>The System Cannot Log You On (C000019B)</h3></div></div></div><p>&#8220;<span class="quote">
 I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message,
 <span class="errorname">`The system cannot log you on (C000019B). Please try again or consult your system
 administrator</span> when attempting to logon.'</span>&#8221;
 </p><p>
-<a class="indexterm" name="id2565373"></a>
+<a class="indexterm" name="id2565371"></a>
 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
@@ -836,7 +836,7 @@ Workstation Machine Trust Accounts work only with the domain (or network) SID. I
 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 rejoin
 it to the domain.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565428"></a>The Machine Trust Account Is Not Accessible</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565427"></a>The Machine Trust Account Is Not Accessible</h3></div></div></div><p>
 &#8220;<span class="quote">When I try to join the domain I get the message, <span class="errorname">"The machine account 
 for this computer either does not exist or is not accessible</span>." What's wrong?</span>&#8221;
 </p><p>
@@ -858,16 +858,16 @@ by alternative settings in the NSS <code class="filename">/etc/nsswitch.conf</co
 </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="id2565548"></a>Account Disabled</h3></div></div></div><p>&#8220;<span class="quote">When I attempt to log in to a Samba domain from a NT4/W200x workstation,
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565546"></a>Account Disabled</h3></div></div></div><p>&#8220;<span class="quote">When I attempt to log in to a Samba domain from a NT4/W200x workstation,
 I get a message about my account being disabled.</span>&#8221;</p><p>
 Enable the user accounts with <strong class="userinput"><code>smbpasswd -e <em class="replaceable"><code>username</code></em>
 </code></strong>. 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="id2565575"></a>Domain Controller Unavailable</h3></div></div></div><p>&#8220;<span class="quote">Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</span>&#8221;</p><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565573"></a>Domain Controller Unavailable</h3></div></div></div><p>&#8220;<span class="quote">Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</span>&#8221;</p><p>
 A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes,
 then try again.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565594"></a>Cannot Log onto Domain Member Workstation After Joining Domain</h3></div></div></div><p>
-<a class="indexterm" name="id2565602"></a>
-<a class="indexterm" name="id2565609"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565592"></a>Cannot Log onto Domain Member Workstation After Joining Domain</h3></div></div></div><p>
+<a class="indexterm" name="id2565601"></a>
+<a class="indexterm" name="id2565608"></a>
 After successfully joining the domain, user logons fail with one of two messages: one to the
 effect that the domain controller cannot be found; the other claims that the account does not
 exist in the domain or that the password is incorrect. This may be due to incompatible
@@ -884,7 +884,7 @@ Control Panel. The Policy settings are found in the Local Policies/Security Opti
 <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.id2562663" href="#id2562663" class="para">1</a>] </sup>See also <a class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">Account Information
-Databases</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2563168" href="#id2563168" class="para">2</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a>, and 
-		<a class="link" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba">Integrating MS Windows Networks with Samba</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2563473" href="#id2563473" class="para">3</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network
+</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2562660" href="#id2562660" class="para">1</a>] </sup>See also <a class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">Account Information
+Databases</a>.</p>.</div><div class="footnote"><p><sup>[<a name="ftn.id2563166" href="#id2563166" class="para">2</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network Browsing</a>, and 
+		<a class="link" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba">Integrating MS Windows Networks with Samba</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2563471" href="#id2563471" class="para">3</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter�10.�Network Browsing">Network
 Browsing</a>.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ServerType.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="samba-bdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�3.�Server Types and Security Modes�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�5.�Backup Domain Control</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/securing-samba.html b/docs/htmldocs/Samba3-HOWTO/securing-samba.html
index 0c421a6a0c..24a846e802 100644
--- a/docs/htmldocs/Samba3-HOWTO/securing-samba.html
+++ b/docs/htmldocs/Samba3-HOWTO/securing-samba.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�18.�Securing Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="locking.html" title="Chapter�17.�File and Record Locking"><link rel="next" href="InterdomainTrusts.html" title="Chapter�19.�Interdomain Trust Relationships"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�18.�Securing Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="locking.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="InterdomainTrusts.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter�18.�Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 26, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="securing-samba.html#id2618040">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618151">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618297">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618313">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618467">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618527">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618877">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619021">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619076">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619119">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619142">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619170">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618040"></a>Introduction</h2></div></div></div><p>
-<a class="indexterm" name="id2618048"></a>
-<a class="indexterm" name="id2618055"></a>
-<a class="indexterm" name="id2618062"></a>
-<a class="indexterm" name="id2618069"></a>
-<a class="indexterm" name="id2618076"></a>
-<a class="indexterm" name="id2618082"></a>
-<a class="indexterm" name="id2618089"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�18.�Securing Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="locking.html" title="Chapter�17.�File and Record Locking"><link rel="next" href="InterdomainTrusts.html" title="Chapter�19.�Interdomain Trust Relationships"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�18.�Securing Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="locking.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="InterdomainTrusts.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter�18.�Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 26, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="securing-samba.html#id2618082">Introduction</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618181">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2618327">Technical Discussion of Protective Measures and Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2618343">Using Host-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618497">User-Based Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618557">Using Interface Protection</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#firewallports">Using a Firewall</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2618907">Using IPC$ Share-Based Denials </a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619056">NTLMv2 Security</a></span></dt></dl></dd><dt><span class="sect1"><a href="securing-samba.html#id2619110">Upgrading Samba</a></span></dt><dt><span class="sect1"><a href="securing-samba.html#id2619154">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="securing-samba.html#id2619170">Smbclient Works on Localhost, but the Network Is Dead</a></span></dt><dt><span class="sect2"><a href="securing-samba.html#id2619198">Why Can Users Access Other Users' Home Directories?</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618082"></a>Introduction</h2></div></div></div><p>
+<a class="indexterm" name="id2618090"></a>
+<a class="indexterm" name="id2618097"></a>
+<a class="indexterm" name="id2618104"></a>
+<a class="indexterm" name="id2618111"></a>
+<a class="indexterm" name="id2618118"></a>
+<a class="indexterm" name="id2618124"></a>
+<a class="indexterm" name="id2618131"></a>
 The information contained in this chapter applies in general to all Samba installations. Security is
 everyone's concern in the information technology world. A surprising number of Samba servers are being
 installed on machines that have direct internet access, thus security is made more critical than it would have been had the
@@ -22,11 +22,11 @@ on it!</span>&#8221;
 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="id2618151"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2618159"></a>
-<a class="indexterm" name="id2618166"></a>
-<a class="indexterm" name="id2618173"></a>
-<a class="indexterm" name="id2618180"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618181"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2618189"></a>
+<a class="indexterm" name="id2618196"></a>
+<a class="indexterm" name="id2618203"></a>
+<a class="indexterm" name="id2618210"></a>
 There are three levels at which security principles must be observed in order to render a site
 at least moderately secure. They are the perimeter firewall, the configuration of the host
 server that is running Samba, and Samba itself.
@@ -34,154 +34,154 @@ server that is running Samba, and Samba itself.
 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>
-<a class="indexterm" name="id2618200"></a>
-<a class="indexterm" name="id2618207"></a>
-<a class="indexterm" name="id2618214"></a>
+<a class="indexterm" name="id2618230"></a>
+<a class="indexterm" name="id2618237"></a>
+<a class="indexterm" name="id2618244"></a>
 Samba can be secured from connections that originate from outside the local network. This can be done using
 <span class="emphasis"><em>host-based protection</em></span>, using Samba's implementation of a technology known as
 &#8220;<span class="quote">tcpwrappers,</span>&#8221; or it may be done be using <span class="emphasis"><em>interface-based exclusion</em></span> so
 <span class="application">smbd</span> will bind only to specifically permitted interfaces. It is also possible to set specific share- or
 resource-based exclusions, for example, on the <em class="parameter"><code>[IPC$]</code></em> autoshare. The <em class="parameter"><code>[IPC$]</code></em> share is used for browsing purposes as well as to establish TCP/IP connections.
 </p><p>
-<a class="indexterm" name="id2618261"></a>
-<a class="indexterm" name="id2618271"></a>
-<a class="indexterm" name="id2618277"></a>
+<a class="indexterm" name="id2618291"></a>
+<a class="indexterm" name="id2618301"></a>
+<a class="indexterm" name="id2618307"></a>
 Another method by which Samba may be secured is by setting Access Control Entries (ACEs) in an Access 
 Control List (ACL) on the shares themselves. This is discussed in
 <a class="link" href="AccessControls.html" title="Chapter�16.�File, Directory, and Share Access Controls">File, Directory, and Share Access Controls</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618297"></a>Technical Discussion of Protective Measures and Issues</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618327"></a>Technical Discussion of Protective Measures and Issues</h2></div></div></div><p>
 The key challenge of security is 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, 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="id2618313"></a>Using Host-Based Protection</h3></div></div></div><p>
-<a class="indexterm" name="id2618321"></a>
-<a class="indexterm" name="id2618328"></a>
-<a class="indexterm" name="id2618334"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618343"></a>Using Host-Based Protection</h3></div></div></div><p>
+<a class="indexterm" name="id2618351"></a>
+<a class="indexterm" name="id2618358"></a>
+<a class="indexterm" name="id2618364"></a>
 	In many installations of Samba, the greatest threat comes from outside
 	your immediate network. By default, Samba accepts 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>
-<a class="indexterm" name="id2618350"></a>
-<a class="indexterm" name="id2618356"></a>
+<a class="indexterm" name="id2618380"></a>
+<a class="indexterm" name="id2618386"></a>
 	One of the simplest fixes in this case is to use the <a class="link" href="smb.conf.5.html#HOSTSALLOW" target="_top">hosts allow</a> and
 	<a class="link" href="smb.conf.5.html#HOSTSDENY" target="_top">hosts deny</a> options in the Samba <code class="filename">smb.conf</code> configuration file to
 	allow access to your server only from a specific range of hosts. An example might be:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618403"></a><em class="parameter"><code>hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24</code></em></td></tr><tr><td><a class="indexterm" name="id2618415"></a><em class="parameter"><code>hosts deny = 0.0.0.0/0</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618433"></a><em class="parameter"><code>hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24</code></em></td></tr><tr><td><a class="indexterm" name="id2618445"></a><em class="parameter"><code>hosts deny = 0.0.0.0/0</code></em></td></tr></table><p>
 	</p><p>
-<a class="indexterm" name="id2618430"></a>
-<a class="indexterm" name="id2618437"></a>
-<a class="indexterm" name="id2618444"></a>
+<a class="indexterm" name="id2618460"></a>
+<a class="indexterm" name="id2618467"></a>
+<a class="indexterm" name="id2618474"></a>
 	The above will allow SMB connections only from <code class="constant">localhost</code> (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 <code class="literal">not listening on called name</code> error.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618467"></a>User-Based Protection</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618497"></a>User-Based Protection</h3></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 <code class="filename">smb.conf</code> <em class="parameter"><code>[global]</code></em> section put:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618495"></a><em class="parameter"><code>valid users = @smbusers, jacko</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618525"></a><em class="parameter"><code>valid users = @smbusers, jacko</code></em></td></tr></table><p>
 	</p><p>
-<a class="indexterm" name="id2618510"></a>
+<a class="indexterm" name="id2618540"></a>
 	This restricts all server access either to 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="id2618527"></a>Using Interface Protection</h3></div></div></div><p>
-<a class="indexterm" name="id2618535"></a>
-<a class="indexterm" name="id2618542"></a>
-<a class="indexterm" name="id2618549"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618557"></a>Using Interface Protection</h3></div></div></div><p>
+<a class="indexterm" name="id2618565"></a>
+<a class="indexterm" name="id2618572"></a>
+<a class="indexterm" name="id2618579"></a>
 	By default, Samba accepts connections on any network interface that
 	it finds on your system. That means if you have an 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 behavior using options like this:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618570"></a><em class="parameter"><code>interfaces = eth* lo</code></em></td></tr><tr><td><a class="indexterm" name="id2618581"></a><em class="parameter"><code>bind interfaces only = yes</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2618600"></a><em class="parameter"><code>interfaces = eth* lo</code></em></td></tr><tr><td><a class="indexterm" name="id2618611"></a><em class="parameter"><code>bind interfaces only = yes</code></em></td></tr></table><p>
 	</p><p>
-<a class="indexterm" name="id2618596"></a>
-<a class="indexterm" name="id2618603"></a>
-<a class="indexterm" name="id2618610"></a>
-<a class="indexterm" name="id2618617"></a>
+<a class="indexterm" name="id2618626"></a>
+<a class="indexterm" name="id2618633"></a>
+<a class="indexterm" name="id2618640"></a>
+<a class="indexterm" name="id2618647"></a>
 	This tells Samba to listen for connections only on interfaces with a name starting with
 	<code class="constant">eth</code> such as <code class="constant">eth0</code> or <code class="constant">eth1</code>, plus on the loopback interface called
 	<code class="constant">lo</code>. 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>
-<a class="indexterm" name="id2618646"></a>
-<a class="indexterm" name="id2618653"></a>
-<a class="indexterm" name="id2618660"></a>
-<a class="indexterm" name="id2618666"></a>
+<a class="indexterm" name="id2618676"></a>
+<a class="indexterm" name="id2618683"></a>
+<a class="indexterm" name="id2618690"></a>
+<a class="indexterm" name="id2618696"></a>
 	If you use the above and someone tries to make an SMB connection to your host over a PPP interface called
 	<code class="constant">ppp0</code>, then [s]he will get a TCP connection refused reply. In that case, no Samba code
 	is run at all, because the operating system has been told not to pass connections from that interface to any
 	Samba process. However, the refusal helps a would-be cracker by confirming that the IP address provides
 	valid active services.
 	</p><p>
-<a class="indexterm" name="id2618687"></a>
-<a class="indexterm" name="id2618694"></a>
-<a class="indexterm" name="id2618701"></a>
-<a class="indexterm" name="id2618708"></a>
-<a class="indexterm" name="id2618715"></a>
+<a class="indexterm" name="id2618717"></a>
+<a class="indexterm" name="id2618724"></a>
+<a class="indexterm" name="id2618731"></a>
+<a class="indexterm" name="id2618738"></a>
+<a class="indexterm" name="id2618745"></a>
 	A better response would be to ignore the connection (from, for example, ppp0) altogether. The
 	advantage of ignoring the connection attempt, as compared with refusing it, is that it foils those who
 	probe an interface with the sole intention of finding valid IP addresses for later use in exploitation
 	or denial of service attacks. This method of dealing with potential malicious activity demands the
 	use of appropriate firewall mechanisms.
 	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="firewallports"></a>Using a Firewall</h3></div></div></div><p>
-<a class="indexterm" name="id2618744"></a>
-<a class="indexterm" name="id2618751"></a>
-<a class="indexterm" name="id2618757"></a>
+<a class="indexterm" name="id2618774"></a>
+<a class="indexterm" name="id2618781"></a>
+<a class="indexterm" name="id2618787"></a>
 	Many people use a firewall to deny access to services they do not want exposed outside their network. This can
 	be a good idea, although I recommend using it in conjunction with the above methods so you are protected even
 	if your firewall is not active for some reason.
 	</p><p>
 	If you are setting up a firewall, you need to know what TCP and UDP ports to allow and block. Samba uses
 	the following:
-<a class="indexterm" name="id2618774"></a>
-<a class="indexterm" name="id2618781"></a>
-<a class="indexterm" name="id2618788"></a>
-<a class="indexterm" name="id2618795"></a>
-<a class="indexterm" name="id2618802"></a>
+<a class="indexterm" name="id2618804"></a>
+<a class="indexterm" name="id2618811"></a>
+<a class="indexterm" name="id2618818"></a>
+<a class="indexterm" name="id2618825"></a>
+<a class="indexterm" name="id2618832"></a>
 	</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Port 135/TCP - used by smbd</td></tr><tr><td>Port 137/UDP - used by nmbd</td></tr><tr><td>Port 138/UDP - used by nmbd</td></tr><tr><td>Port 139/TCP - used by smbd</td></tr><tr><td>Port 445/TCP - used by smbd</td></tr></table><p>
-<a class="indexterm" name="id2618836"></a>
+<a class="indexterm" name="id2618866"></a>
 	The last one is important because many older firewall setups may not be aware of it, given that this port
 	was only added to the protocol in recent years.
 	</p><p>
-<a class="indexterm" name="id2618849"></a>
-<a class="indexterm" name="id2618856"></a>
-<a class="indexterm" name="id2618863"></a>
+<a class="indexterm" name="id2618879"></a>
+<a class="indexterm" name="id2618886"></a>
+<a class="indexterm" name="id2618893"></a>
 	When configuring a firewall, the high order ports (1024-65535) are often used for outgoing connections and
 	therefore should be permitted through the firewall. It is prudent to block incoming packets on the high order
 	ports except for established connections.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618877"></a>Using IPC$ Share-Based Denials </h3></div></div></div><p>
-<a class="indexterm" name="id2618885"></a>
-<a class="indexterm" name="id2618892"></a>
-<a class="indexterm" name="id2618899"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2618907"></a>Using IPC$ Share-Based Denials </h3></div></div></div><p>
+<a class="indexterm" name="id2618915"></a>
+<a class="indexterm" name="id2618922"></a>
+<a class="indexterm" name="id2618929"></a>
 	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 this you could use:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[IPC$]</code></em></td></tr><tr><td><a class="indexterm" name="id2618929"></a><em class="parameter"><code>hosts allow = 192.168.115.0/24 127.0.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2618941"></a><em class="parameter"><code>hosts deny = 0.0.0.0/0</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[IPC$]</code></em></td></tr><tr><td><a class="indexterm" name="id2618963"></a><em class="parameter"><code>hosts allow = 192.168.115.0/24 127.0.0.1</code></em></td></tr><tr><td><a class="indexterm" name="id2618975"></a><em class="parameter"><code>hosts deny = 0.0.0.0/0</code></em></td></tr></table><p>
 	</p><p>
-<a class="indexterm" name="id2618956"></a>
-<a class="indexterm" name="id2618962"></a>
-<a class="indexterm" name="id2618970"></a>
+<a class="indexterm" name="id2618990"></a>
+<a class="indexterm" name="id2618997"></a>
+<a class="indexterm" name="id2619004"></a>
 	This instructs Samba that IPC$ connections are not allowed from anywhere except the two listed network
 	addresses (localhost and the 192.168.115 subnet). Connections to other shares are still allowed. Because the
 	IPC$ share is the only share that is always accessible anonymously, this provides some level of protection
 	against attackers who do not know a valid username/password for your host.
 	</p><p>
-<a class="indexterm" name="id2618987"></a>
-<a class="indexterm" name="id2618994"></a>
-<a class="indexterm" name="id2619000"></a>
+<a class="indexterm" name="id2619021"></a>
+<a class="indexterm" name="id2619028"></a>
+<a class="indexterm" name="id2619035"></a>
 	If you use this method, then clients will be given an <code class="literal">`access denied'</code> reply when they try
 	to access the IPC$ share. Those clients will not be able to browse shares and may also be unable to access
 	some other resources.  This is not recommended unless for some reason you cannot use one of the other methods
 	just discussed.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619021"></a>NTLMv2 Security</h3></div></div></div><p>
-<a class="indexterm" name="id2619029"></a>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619056"></a>NTLMv2 Security</h3></div></div></div><p>
+<a class="indexterm" name="id2619063"></a>
 	To configure NTLMv2 authentication, the following registry keys are worth knowing about:
 	</p><p>
 		</p><pre class="screen">
@@ -201,20 +201,20 @@ before someone will find yet another vulnerability.
 	The value 0x00080000 means permit only NTLMv2 session security. If either NtlmMinClientSec or
 	NtlmMinServerSec is set to 0x00080000, the connection will fail if NTLMv2
 	session security is negotiated.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619076"></a>Upgrading Samba</h2></div></div></div><p>
-<a class="indexterm" name="id2619084"></a>
-<a class="indexterm" name="id2619090"></a>
-<a class="indexterm" name="id2619097"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619110"></a>Upgrading Samba</h2></div></div></div><p>
+<a class="indexterm" name="id2619118"></a>
+<a class="indexterm" name="id2619125"></a>
+<a class="indexterm" name="id2619132"></a>
 Please check regularly on <a class="ulink" 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 promptly 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="id2619119"></a>Common Errors</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619154"></a>Common Errors</h2></div></div></div><p>
 If all Samba and host platform configurations were really as intuitive as one might like them to be, this
 chapter would not be necessary. Security issues are often vexing for a support person to resolve, not because
 of the complexity of the problem, but because 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="id2619142"></a>Smbclient Works on Localhost, but the Network Is Dead</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619170"></a>Smbclient Works on Localhost, but the Network Is Dead</h3></div></div></div><p>
 	This is a common problem. Linux vendors tend to install a default firewall.
 	With the default firewall in place, only traffic on the loopback adapter (IP address 127.0.0.1)
 	is allowed through the firewall.
@@ -222,10 +222,10 @@ problem request are totally convinced that the problem is with Samba.
 	The solution is either to remove the firewall (stop it) or modify the firewall script to
 	allow SMB networking traffic through. See <a class="link" href="securing-samba.html#firewallports" title="Using a Firewall">the Using a 
 	Firewall</a> section.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619170"></a>Why Can Users Access Other Users' Home Directories?</h3></div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619198"></a>Why Can Users Access Other Users' Home Directories?</h3></div></div></div><p>
 	&#8220;<span class="quote">
-<a class="indexterm" name="id2619181"></a>
-<a class="indexterm" name="id2619188"></a>
+<a class="indexterm" name="id2619209"></a>
+<a class="indexterm" name="id2619216"></a>
 	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 to
 	configure Samba so that users may map only their own home directory.
@@ -233,20 +233,20 @@ problem request are totally convinced that the problem is with Samba.
 	</p><p>&#8220;<span class="quote">
 	User xyzzy can map his home directory. Once mapped, user xyzzy can also map anyone else's home directory.
 	</span>&#8221;</p><p>
-<a class="indexterm" name="id2619210"></a>
-<a class="indexterm" name="id2619217"></a>
+<a class="indexterm" name="id2619238"></a>
+<a class="indexterm" name="id2619245"></a>
 	This is not a security flaw, it is by design. Samba allows users to have exactly the same access to the UNIX
 	file system as when they were logged on to the UNIX box, except that it only allows such views onto the file
 	system as are allowed by the defined shares.
 	</p><p>
-<a class="indexterm" name="id2619232"></a>
-<a class="indexterm" name="id2619239"></a>
+<a class="indexterm" name="id2619260"></a>
+<a class="indexterm" name="id2619267"></a>
 	If your UNIX home directories are set up so that one user can happily <code class="literal">cd</code>
 	into another user's directory and execute <code class="literal">ls</code>, the UNIX security solution is to change file
 	permissions on the user's home directories so that the <code class="literal">cd</code> and <code class="literal">ls</code> are denied.
 	</p><p>
-<a class="indexterm" name="id2619276"></a>
-<a class="indexterm" name="id2619283"></a>
+<a class="indexterm" name="id2619304"></a>
+<a class="indexterm" name="id2619311"></a>
 	Samba tries very hard not to second guess the UNIX administrator's security policies and
 	trusts the UNIX admin to set the policies and permissions he or she desires.
 	</p><p>
@@ -255,9 +255,9 @@ problem request are totally convinced that the problem is with Samba.
 	</p><p>
 	The <a class="link" href="smb.conf.5.html#ONLYUSER" target="_top">only user</a> works in conjunction with the <a class="link" href="smb.conf.5.html#USERS" target="_top">users = list</a>,
 	so to get the behavior you require, add the line:
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619349"></a><em class="parameter"><code>users = %S</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619377"></a><em class="parameter"><code>users = %S</code></em></td></tr></table><p>
 	This is equivalent to adding
-	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619367"></a><em class="parameter"><code>valid users = %S</code></em></td></tr></table><p>
+	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2619395"></a><em class="parameter"><code>valid users = %S</code></em></td></tr></table><p>
 	to the definition of the <em class="parameter"><code>[homes]</code></em> share, as recommended in
 	the <code class="filename">smb.conf</code> man page.
 	</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="locking.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="InterdomainTrusts.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�17.�File and Record Locking�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�19.�Interdomain Trust Relationships</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/speed.html b/docs/htmldocs/Samba3-HOWTO/speed.html
index 2d69b23fa2..6e1a39ce9b 100644
--- a/docs/htmldocs/Samba3-HOWTO/speed.html
+++ b/docs/htmldocs/Samba3-HOWTO/speed.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�45.�Samba Performance Tuning</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Other-Clients.html" title="Chapter�44.�Samba and Other CIFS Clients"><link rel="next" href="ch-ldap-tls.html" title="Chapter�46.�LDAP and Transport Layer Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�45.�Samba Performance Tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch-ldap-tls.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter�45.�Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="orgname">Dundee Limb Fitting Centre</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="speed.html#id2690558">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690596">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690693">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690737">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690785">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690809">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690876">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690928">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690952">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690973">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691160">Samba Performance is Very Slow</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690558"></a>Comparisons</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�45.�Samba Performance Tuning</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Reference Section"><link rel="prev" href="Other-Clients.html" title="Chapter�44.�Samba and Other CIFS Clients"><link rel="next" href="ch-ldap-tls.html" title="Chapter�46.�LDAP and Transport Layer Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�45.�Samba Performance Tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Reference Section</th><td width="20%" align="right">�<a accesskey="n" href="ch-ldap-tls.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter�45.�Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="orgname">Dundee Limb Fitting Centre</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="speed.html#id2690694">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690732">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690829">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690873">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690921">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id2690945">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691012">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691064">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691088">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691109">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691200">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id2691296">Samba Performance is Very Slow</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690694"></a>Comparisons</h2></div></div></div><p>
 The Samba server uses TCP to talk to the client, so if you are
 trying to see if it performs well, you should really compare it to
 programs that use the same protocol. The most readily available
@@ -20,7 +20,7 @@ suspect the biggest factor is not Samba versus some other system, but the
 hardware and drivers used on the various systems. Given similar
 hardware, Samba should certainly be competitive in speed with other
 systems.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690596"></a>Socket Options</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690732"></a>Socket Options</h2></div></div></div><p>
 There are a number of socket options that can greatly affect the
 performance of a TCP-based server like Samba.
 </p><p>
@@ -44,7 +44,7 @@ There have been reports that setting <em class="parameter"><code>socket options
 can seriously degrade Samba performance on the loopback adaptor (IP Address 127.0.0.1). It is strongly
 recommended that before specifying any settings for <em class="parameter"><code>socket options</code></em>, the effect
 first be quantitatively measured on the server being configured.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690693"></a>Read Size</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690829"></a>Read Size</h2></div></div></div><p>
 The option <a class="link" href="smb.conf.5.html#READSIZE" target="_top">read size</a> affects the overlap of disk
 reads/writes with network reads/writes. If the amount of data being
 transferred in several of the SMB commands (currently SMBwrite, SMBwriteX, and
@@ -61,7 +61,7 @@ The default value is 16384, but little experimentation has been
 done as yet to determine the optimal value, and it is likely that the best
 value will vary greatly between systems anyway. A value over 65536 is
 pointless and will cause you to allocate memory unnecessarily.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690737"></a>Max Xmit</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690873"></a>Max Xmit</h2></div></div></div><p>
 	At startup the client and server negotiate a <em class="parameter"><code>maximum transmit</code></em> size,
 which limits the size of nearly all SMB commands. You can set the
 maximum size that Samba will negotiate using the <a class="link" href="smb.conf.5.html#MAXXMIT" target="_top">max xmit</a> option
@@ -74,12 +74,12 @@ It defaults to 65536 bytes (the maximum), but it is possible that some
 clients may perform better with a smaller transmit unit. Trying values
 of less than 2048 is likely to cause severe problems.
 In most cases the default is the best option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690785"></a>Log Level</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690921"></a>Log Level</h2></div></div></div><p>
 If you set the log level (also known as <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debug level</a>) higher than 2,
 then you may suffer a large drop in performance. This is because the
 server flushes the log file after each operation, which can be quite
 expensive. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690809"></a>Read Raw</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690945"></a>Read Raw</h2></div></div></div><p>
 The <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw</a> operation is designed to be an optimized, low-latency
 file read operation. A server may choose to not support it,
 however, and Samba makes support for <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw</a> optional, with it
@@ -90,26 +90,26 @@ get lower performance using it than they get using the conventional
 read operations, so you might like to try <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw = no</a> and see what happens on your
 network. It might lower, raise, or not affect your performance. Only
 testing can really tell.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690876"></a>Write Raw</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691012"></a>Write Raw</h2></div></div></div><p>
 The <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> operation is designed to be an optimized, low-latency
 file write operation. A server may choose to not support it, however, and Samba makes support for
 <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> optional, with it being enabled by default.
 </p><p>
 Some machines may find <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> slower than normal write, in which
 case you may wish to change this option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690928"></a>Slow Logins</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691064"></a>Slow Logins</h2></div></div></div><p>
 Slow logins are almost always due to the password checking time. Using
 the lowest practical <a class="link" href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> will improve things. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690952"></a>Client Tuning</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691088"></a>Client Tuning</h2></div></div></div><p>
 Often a speed problem can be traced to the client. The client (for
 example Windows for Workgroups) can often be tuned for better TCP
 performance. Check the sections on the various clients in 
 <a class="link" href="Other-Clients.html" title="Chapter�44.�Samba and Other CIFS Clients">Samba and Other CIFS Clients</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690973"></a>Samba Performance Problem Due to Changing Linux Kernel</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691109"></a>Samba Performance Problem Due to Changing Linux Kernel</h2></div></div></div><p>
 A user wrote the following to the mailing list:
 </p><div class="blockquote"><blockquote class="blockquote"><p>
-<a class="indexterm" name="id2690988"></a>
-<a class="indexterm" name="id2690994"></a>
+<a class="indexterm" name="id2691124"></a>
+<a class="indexterm" name="id2691130"></a>
 I am running Gentoo on my server and Samba 2.2.8a. Recently I changed kernel versions from
 <code class="filename">linux-2.4.19-gentoo-r10</code> to <code class="filename">linux-2.4.20-wolk4.0s</code>. Now I have a
 performance issue with Samba.  Many of you will probably say,  &#8220;<span class="quote">Move to vanilla sources!</span>&#8221; Well, I
@@ -120,16 +120,16 @@ server and Windows, and it is terribly slow.
 </p></blockquote></div><p>
 The answer he was given is:
 </p><div class="blockquote"><blockquote class="blockquote"><p>
-<a class="indexterm" name="id2691036"></a>
-<a class="indexterm" name="id2691043"></a>
-<a class="indexterm" name="id2691050"></a>
+<a class="indexterm" name="id2691172"></a>
+<a class="indexterm" name="id2691179"></a>
+<a class="indexterm" name="id2691186"></a>
 Grab the mii-tool and check the duplex settings on the NIC.  My guess is that it is a link layer issue, not an
 application layer problem. Also run ifconfig and verify that the framing error, collisions, and so on, look
 normal for ethernet.
-</p></blockquote></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691064"></a>Corrupt tdb Files</h2></div></div></div><p>
-<a class="indexterm" name="id2691072"></a>
-<a class="indexterm" name="id2691079"></a>
-<a class="indexterm" name="id2691086"></a>
+</p></blockquote></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691200"></a>Corrupt tdb Files</h2></div></div></div><p>
+<a class="indexterm" name="id2691208"></a>
+<a class="indexterm" name="id2691215"></a>
+<a class="indexterm" name="id2691222"></a>
 Our Samba PDC server has been hosting three TB of data to our 500+ users [Windows NT/XP]  for the last three
 years using Samba without a problem.  Today all shares went very slow. Also, the main smbd kept spawning new
 processes, so we had 1600+ running SMDB's (normally we average 250).  It crashed the SUN E3500 cluster twice.
@@ -138,28 +138,28 @@ After a lot of searching, I decided to <code class="literal">rm /var/locks/*.tdb
 <span class="emphasis"><em>Question:</em></span> Is there any method of keeping the *.tdb files in top condition, or
 how can I detect early corruption?
 </p><p>
-<a class="indexterm" name="id2691117"></a>
-<a class="indexterm" name="id2691124"></a>
+<a class="indexterm" name="id2691253"></a>
+<a class="indexterm" name="id2691260"></a>
 <span class="emphasis"><em>Answer:</em></span> Yes, run <code class="literal">tdbbackup</code> each time after stopping nmbd and before starting nmbd.
 </p><p>
 <span class="emphasis"><em>Question:</em></span> What I also would like to mention is that the service latency seems
 a lot lower than before the locks cleanup. Any ideas on keeping it top notch?
 </p><p>
 <span class="emphasis"><em>Answer:</em></span> Yes. Same answer as for previous question!
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691160"></a>Samba Performance is Very Slow</h2></div></div></div><p>
-<a class="indexterm" name="id2691168"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691296"></a>Samba Performance is Very Slow</h2></div></div></div><p>
+<a class="indexterm" name="id2691304"></a>
 A site reported experiencing very baffling symptoms with MYOB Premier opening and
 accessing its data files. Some  operations on the file would take between 40 and
 45 seconds.
 </p><p>
-<a class="indexterm" name="id2691181"></a>
-<a class="indexterm" name="id2691188"></a>
+<a class="indexterm" name="id2691317"></a>
+<a class="indexterm" name="id2691324"></a>
 It turned out that the printer monitor program running on the Windows
 clients was causing the problems. From the logs, we saw activity coming
 through with pauses of about 1 second.
 </p><p>
-<a class="indexterm" name="id2691201"></a>
-<a class="indexterm" name="id2691208"></a>
+<a class="indexterm" name="id2691337"></a>
+<a class="indexterm" name="id2691344"></a>
 Stopping the monitor software resulted in the networks access at normal
 (quick) speed. Restarting the program caused the speed to slow down
 again. The printer was a Canon LBP-810 and the relevant task was
diff --git a/docs/htmldocs/Samba3-HOWTO/tdb.html b/docs/htmldocs/Samba3-HOWTO/tdb.html
index 683ed0d45c..813d59115a 100644
--- a/docs/htmldocs/Samba3-HOWTO/tdb.html
+++ b/docs/htmldocs/Samba3-HOWTO/tdb.html
@@ -1,15 +1,15 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�41.�Managing TDB Files</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="bugreport.html" title="Chapter�40.�Reporting Bugs"><link rel="next" href="Appendix.html" title="Part�VI.�Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�41.�Managing TDB Files</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreport.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="Appendix.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="tdb"></a>Chapter�41.�Managing TDB Files</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 28, 2008</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="tdb.html#id2686735">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687197">Managing TDB Files</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686735"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2686743"></a>
-<a class="indexterm" name="id2686750"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�41.�Managing TDB Files</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="bugreport.html" title="Chapter�40.�Reporting Bugs"><link rel="next" href="Appendix.html" title="Part�VI.�Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�41.�Managing TDB Files</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreport.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="Appendix.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="tdb"></a>Chapter�41.�Managing TDB Files</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">May 28, 2008</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="tdb.html#id2686891">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687352">Managing TDB Files</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2686891"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2686899"></a>
+<a class="indexterm" name="id2686905"></a>
 	Samba uses a lightweight database called Trivial Database (tdb) in which it stores persistent and transient data.
 	Some tdb files can be disposed of before restarting Samba, but others are used to store information that is vital
 	to Samba configuration and behavior. The following information is provided to help administrators who are seeking
 	to better manage their Samba installations.
 	</p><p>
-<a class="indexterm" name="id2686766"></a>
-<a class="indexterm" name="id2686773"></a>
-<a class="indexterm" name="id2686780"></a>
-<a class="indexterm" name="id2686787"></a>
+<a class="indexterm" name="id2686922"></a>
+<a class="indexterm" name="id2686928"></a>
+<a class="indexterm" name="id2686935"></a>
+<a class="indexterm" name="id2686942"></a>
 	Those who package Samba for commercial distribution with operating systems and appliances would do well to take
 	note that tdb files can get corrupted, and for this reason ought to be backed up regularly.  An appropriate time
 	is at system shutdown (backup) and startup (restore from backup).
@@ -37,7 +37,7 @@
 				This stores secure channel access token information used with SMB signing.
 				</p></td></tr><tr><td align="center">passdb.tdb</td><td align="center">Y</td><td align="center"><p>
 				This stores the Samba SAM account information when using a tdbsam password backend.
-				</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687197"></a>Managing TDB Files</h2></div></div></div><p>
+				</p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687352"></a>Managing TDB Files</h2></div></div></div><p>
 	The <code class="literal">tdbbackup</code> utility is a tool that may be used to backup samba tdb files.
 	This tool may also be used to verify the integrity of the tdb files prior to Samba startup or
 	during normal operation. If it finds file damage it will search for a prior backup the backup
diff --git a/docs/htmldocs/Samba3-HOWTO/troubleshooting.html b/docs/htmldocs/Samba3-HOWTO/troubleshooting.html
index efdd847ff4..4d3a37d16a 100644
--- a/docs/htmldocs/Samba3-HOWTO/troubleshooting.html
+++ b/docs/htmldocs/Samba3-HOWTO/troubleshooting.html
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�V.�Troubleshooting</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool"><link rel="next" href="diagnosis.html" title="Chapter�38.�The Samba Checklist"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�V.�Troubleshooting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SWAT.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="diagnosis.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Part�V.�Troubleshooting</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="diagnosis.html">38. The Samba Checklist</a></span></dt><dd><dl><dt><span class="sect1"><a href="diagnosis.html#id2682610">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682648">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682941">The Tests</a></span></dt></dl></dd><dt><span class="chapter"><a href="problems.html">39. Analyzing and Solving Samba Problems</a></span></dt><dd><dl><dt><span class="sect1"><a href="problems.html#id2684689">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684741">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2684997">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685047">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685190">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685523">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685560">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685735">How to Get Off the Mailing Lists</a></span></dt></dl></dd><dt><span class="chapter"><a href="bugreport.html">40. Reporting Bugs</a></span></dt><dd><dl><dt><span class="sect1"><a href="bugreport.html#id2685866">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2685956">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686191">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686393">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686526">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686652">Patches</a></span></dt></dl></dd><dt><span class="chapter"><a href="tdb.html">41. Managing TDB Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="tdb.html#id2686735">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687197">Managing TDB Files</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SWAT.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="diagnosis.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�37.�SWAT: The Samba Web Administration Tool�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�38.�The Samba Checklist</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�V.�Troubleshooting</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool"><link rel="next" href="diagnosis.html" title="Chapter�38.�The Samba Checklist"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�V.�Troubleshooting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SWAT.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="diagnosis.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Part�V.�Troubleshooting</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="diagnosis.html">38. The Samba Checklist</a></span></dt><dd><dl><dt><span class="sect1"><a href="diagnosis.html#id2682772">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682811">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2683103">The Tests</a></span></dt></dl></dd><dt><span class="chapter"><a href="problems.html">39. Analyzing and Solving Samba Problems</a></span></dt><dd><dl><dt><span class="sect1"><a href="problems.html#id2684851">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684903">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685159">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685209">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685353">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685678">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685716">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685890">How to Get Off the Mailing Lists</a></span></dt></dl></dd><dt><span class="chapter"><a href="bugreport.html">40. Reporting Bugs</a></span></dt><dd><dl><dt><span class="sect1"><a href="bugreport.html#id2686022">Introduction</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686111">General Information</a></span></dt><dt><span class="sect1"><a href="bugreport.html#dbglvl">Debug Levels</a></span></dt><dd><dl><dt><span class="sect2"><a href="bugreport.html#id2686347">Debugging-Specific Operations</a></span></dt></dl></dd><dt><span class="sect1"><a href="bugreport.html#id2686549">Internal Errors</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686682">Attaching to a Running Process</a></span></dt><dt><span class="sect1"><a href="bugreport.html#id2686807">Patches</a></span></dt></dl></dd><dt><span class="chapter"><a href="tdb.html">41. Managing TDB Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="tdb.html#id2686891">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="tdb.html#id2687352">Managing TDB Files</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SWAT.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="diagnosis.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�37.�SWAT: The Samba Web Administration Tool�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�38.�The Samba Checklist</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/type.html b/docs/htmldocs/Samba3-HOWTO/type.html
index bb159ebaab..b02807c773 100644
--- a/docs/htmldocs/Samba3-HOWTO/type.html
+++ b/docs/htmldocs/Samba3-HOWTO/type.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Server Configuration Basics</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="prev" href="FastStart.html" title="Chapter�2.�Fast Start: Cure for Impatience"><link rel="next" href="ServerType.html" title="Chapter�3.�Server Types and Security Modes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Server Configuration Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FastStart.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ServerType.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Part�II.�Server Configuration Basics</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2558674"></a>First Steps in Server Configuration</h1></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part�II.�Server Configuration Basics</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="prev" href="FastStart.html" title="Chapter�2.�Fast Start: Cure for Impatience"><link rel="next" href="ServerType.html" title="Chapter�3.�Server Types and Security Modes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part�II.�Server Configuration Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FastStart.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="ServerType.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Part�II.�Server Configuration Basics</h1></div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2558669"></a>First Steps in Server Configuration</h1></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><span class="chapter"><a href="ServerType.html">3. Server Types and Security Modes</a></span></dt><dd><dl><dt><span class="sect1"><a href="ServerType.html#id2558810">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558970">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559114">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559276">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559439">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559628">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560123">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560266">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560541">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560728">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560758">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560791">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560828">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560854">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560912">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-pdc.html">4. Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561237">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561872">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562461">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562480">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562984">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563495">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564237">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564290">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564309">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564901">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565181">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565186">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565287">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565352">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565428">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565548">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565575">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565594">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-bdc.html">5. Backup Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565778">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566184">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566253">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566941">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567306">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567364">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567455">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567637">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568138">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568602">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568646">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568701">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568756">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568861">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="domain-member.html">6. Domain Membership</a></span></dt><dd><dl><dt><span class="sect1"><a href="domain-member.html#id2569109">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569796">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570619">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571111">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571847">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572129">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572320">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573414">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573692">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="StandAloneServer.html">7. Standalone Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574171">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574265">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574457">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575441">Common Errors</a></span></dt></dl></dd><dt><span class="chapter"><a href="ClientConfig.html">8. MS Windows Network Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575508">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575568">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575612">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577384">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577910">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578353">Common Errors</a></span></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FastStart.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="ServerType.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Fast Start: Cure for Impatience�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�3.�Server Types and Security Modes</td></tr></table></div></body></html>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ServerType.html">3. Server Types and Security Modes</a></span></dt><dd><dl><dt><span class="sect1"><a href="ServerType.html#id2558805">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2558964">Server Types</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2559109">Samba Security Modes</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2559271">User Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559434">Share-Level Security</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2559626">Domain Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560121">ADS Security Mode (User-Level Security)</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560264">Server Security (User Level Security)</a></span></dt></dl></dd><dt><span class="sect1"><a href="ServerType.html#id2560539">Password Checking</a></span></dt><dt><span class="sect1"><a href="ServerType.html#id2560726">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ServerType.html#id2560756">What Makes Samba a Server?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560788">What Makes Samba a Domain Controller?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560825">What Makes Samba a Domain Member?</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560852">Constantly Losing Connections to Password Server</a></span></dt><dt><span class="sect2"><a href="ServerType.html#id2560910">Stand-alone Server is converted to Domain Controller  Now User accounts don't work</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-pdc.html">4. Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-pdc.html#id2561235">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2561870">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2562458">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2562478">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2562982">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2563493">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564236">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id2564289">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2564308">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2564899">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id2565179">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id2565185">$ Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565286">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565350">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565427">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565546">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565573">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id2565592">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="samba-bdc.html">5. Backup Domain Control</a></span></dt><dd><dl><dt><span class="sect1"><a href="samba-bdc.html#id2565776">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-bdc.html#id2566182">Essential Background Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2566252">MS Windows NT4-style Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2566940">LDAP Configuration Notes</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567305">Active Directory Domain Control</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567363">What Qualifies a Domain Controller on the Network?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2567454">How Does a Workstation find its Domain Controller?</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2567635">Backup Domain Controller Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568136">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-bdc.html#id2568600">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-bdc.html#id2568644">Machine Accounts Keep Expiring</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568699">Can Samba Be a Backup Domain Controller to an NT4 PDC?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568754">How Do I Replicate the smbpasswd File?</a></span></dt><dt><span class="sect2"><a href="samba-bdc.html#id2568859">Can I Do This All with LDAP?</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="domain-member.html">6. Domain Membership</a></span></dt><dd><dl><dt><span class="sect1"><a href="domain-member.html#id2569108">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570618">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572100">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573385">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573664">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="StandAloneServer.html">7. Standalone Servers</a></span></dt><dd><dl><dt><span class="sect1"><a href="StandAloneServer.html#id2574148">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574242">Background</a></span></dt><dt><span class="sect1"><a href="StandAloneServer.html#id2574443">Example Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></span></dt><dt><span class="sect2"><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></span></dt></dl></dd><dt><span class="sect1"><a href="StandAloneServer.html#id2575426">Common Errors</a></span></dt></dl></dd><dt><span class="chapter"><a href="ClientConfig.html">8. MS Windows Network Configuration Guide</a></span></dt><dd><dl><dt><span class="sect1"><a href="ClientConfig.html#id2575494">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2575554">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2575598">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577370">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2577896">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2578339">Common Errors</a></span></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FastStart.html">Prev</a>�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="ServerType.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Fast Start: Cure for Impatience�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�3.�Server Types and Security Modes</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba3-HOWTO/unicode.html b/docs/htmldocs/Samba3-HOWTO/unicode.html
index 3c43bafb9c..ba424458f5 100644
--- a/docs/htmldocs/Samba3-HOWTO/unicode.html
+++ b/docs/htmldocs/Samba3-HOWTO/unicode.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�30.�Unicode/Charsets</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter�31.�Backup Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�30.�Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="Backup.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter�30.�Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><span class="contrib">Japanese character support</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unicode.html#id2669736">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669787">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669921">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670056">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670088">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670218">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670859">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670982">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671128">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671134">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669736"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2669744"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�30.�Unicode/Charsets</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="integrate-ms-networks.html" title="Chapter�29.�Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter�31.�Backup Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�30.�Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="Backup.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter�30.�Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><span class="contrib">Japanese character support</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unicode.html#id2669864">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669916">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670049">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670185">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670216">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670356">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670996">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2671120">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671266">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671272">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669864"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2669872"></a>
 Every industry eventually matures. One of the great areas of maturation is in
 the focus that has been given over the past decade to make it possible for anyone
 anywhere to use a computer. It has not always been that way. In fact, not so long
@@ -11,19 +11,19 @@ language support for all computer users, the efforts of the
 <a class="ulink" href="http://www.openi18n.org/" target="_top">Openi18n organization</a>
 is deserving of special mention.
 </p><p>
-<a class="indexterm" name="id2669772"></a>
+<a class="indexterm" name="id2669900"></a>
 Samba-2.x supported a single locale through a mechanism called 
 <span class="emphasis"><em>codepages</em></span>. Samba-3 is destined to become a truly transglobal
 file- and printer-sharing platform.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669787"></a>What Are Charsets and Unicode?</h2></div></div></div><p>
-<a class="indexterm" name="id2669795"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669916"></a>What Are Charsets and Unicode?</h2></div></div></div><p>
+<a class="indexterm" name="id2669924"></a>
 Computers communicate in numbers. In texts, each number is 
 translated to a corresponding letter. The meaning that will be assigned 
 to a certain number depends on the <span class="emphasis"><em>character set (charset)
 </em></span> that is used. 
 </p><p>
-<a class="indexterm" name="id2669813"></a>
-<a class="indexterm" name="id2669819"></a>
+<a class="indexterm" name="id2669941"></a>
+<a class="indexterm" name="id2669948"></a>
 A charset can be seen as a table that is used to translate numbers to 
 letters. Not all computers use the same charset (there are charsets 
 with German umlauts, Japanese characters, and so on). The American Standard Code
@@ -31,36 +31,36 @@ for Information Interchange (ASCII) encoding system has been the normative chara
 encoding scheme used by computers to date. This employs a charset that contains 
 256 characters. Using this mode of encoding, each character takes exactly one byte.
 </p><p>
-<a class="indexterm" name="id2669837"></a>
-<a class="indexterm" name="id2669844"></a>
+<a class="indexterm" name="id2669966"></a>
+<a class="indexterm" name="id2669973"></a>
 There are also charsets that support extended characters, but those need at least
 twice as much storage space as does ASCII encoding. Such charsets can contain
 <code class="literal">256 * 256 = 65536</code> characters, which is more than all possible
 characters one could think of. They are called multibyte charsets because they use
 more then one byte to store one character. 
 </p><p>
-<a class="indexterm" name="id2669866"></a>
+<a class="indexterm" name="id2669994"></a>
 One standardized multibyte charset encoding scheme is known as
 <a class="ulink" href="http://www.unicode.org/" target="_top">unicode</a>.  A big advantage of using a
 multibyte charset is that you only need one. There is no need to make sure two
 computers use the same charset when they are communicating.
 </p><p>
-<a class="indexterm" name="id2669886"></a>
-<a class="indexterm" name="id2669893"></a>
-<a class="indexterm" name="id2669900"></a>
+<a class="indexterm" name="id2670015"></a>
+<a class="indexterm" name="id2670022"></a>
+<a class="indexterm" name="id2670028"></a>
 Old Windows clients use single-byte charsets, named 
 <em class="parameter"><code>codepages</code></em>, by Microsoft. However, there is no support for 
 negotiating the charset to be used in the SMB/CIFS protocol. Thus, you 
 have to make sure you are using the same charset when talking to an older client.
 Newer clients (Windows NT, 200x, XP) talk Unicode over the wire.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669921"></a>Samba and Charsets</h2></div></div></div><p>
-<a class="indexterm" name="id2669929"></a>
-<a class="indexterm" name="id2669936"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670049"></a>Samba and Charsets</h2></div></div></div><p>
+<a class="indexterm" name="id2670057"></a>
+<a class="indexterm" name="id2670064"></a>
 As of Samba-3, Samba can (and will) talk Unicode over the wire. Internally, 
 Samba knows of three kinds of character sets: 
 </p><div class="variablelist"><dl><dt><span class="term"><a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a></span></dt><dd><p>
-<a class="indexterm" name="id2669968"></a>
-<a class="indexterm" name="id2669974"></a>
+<a class="indexterm" name="id2670096"></a>
+<a class="indexterm" name="id2670102"></a>
 		This is the charset used internally by your operating system. 
 		The default is <code class="constant">UTF-8</code>, which is fine for most 
 		systems and covers all characters in all languages. The default
@@ -73,26 +73,26 @@ Samba knows of three kinds of character sets:
 		The default depends on the charsets you have installed on your system.
 		Run <code class="literal">testparm -v | grep "dos charset"</code> to see 
 		what the default is on your system. 
-		</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670056"></a>Conversion from Old Names</h2></div></div></div><p>
-<a class="indexterm" name="id2670064"></a>
+		</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670185"></a>Conversion from Old Names</h2></div></div></div><p>
+<a class="indexterm" name="id2670193"></a>
 Because previous Samba versions did not do any charset conversion, 
 characters in filenames are usually not correct in the UNIX charset but only 
 for the local charset used by the DOS/Windows clients.
 </p><p>Bjoern Jacke has written a utility named <a class="ulink" href="http://j3e.de/linux/convmv/" target="_top">convmv</a>
 that can convert whole directory structures to different charsets with one single command. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670088"></a>Japanese Charsets</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670216"></a>Japanese Charsets</h2></div></div></div><p>
 Setting up Japanese charsets is quite difficult. This is mainly because:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2670104"></a>
+<a class="indexterm" name="id2670232"></a>
 		The Windows character set is extended from the original legacy Japanese
 		standard (JIS X 0208) and is not standardized. This means that the strictly
 		standardized implementation cannot support the full Windows character set.
 	</p></li><li><p>
-<a class="indexterm" name="id2670119"></a>
-<a class="indexterm" name="id2670125"></a>
-<a class="indexterm" name="id2670132"></a>
-<a class="indexterm" name="id2670139"></a>
-<a class="indexterm" name="id2670146"></a>
+<a class="indexterm" name="id2670247"></a>
+<a class="indexterm" name="id2670254"></a>
+<a class="indexterm" name="id2670260"></a>
+<a class="indexterm" name="id2670267"></a>
+<a class="indexterm" name="id2670274"></a>
 		Mainly for historical reasons, there are several encoding methods in
 		Japanese, which are not fully compatible with each other. There are
 		two major encoding methods. One is the Shift_JIS series used in Windows
@@ -112,24 +112,24 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 		names may be different on different systems.  This means that the value of 
 		the charset parameters depends on the implementation of iconv() you are using.
 		</p><p>
-<a class="indexterm" name="id2670186"></a>
-<a class="indexterm" name="id2670192"></a>
-<a class="indexterm" name="id2670199"></a>
-<a class="indexterm" name="id2670206"></a>
+<a class="indexterm" name="id2670324"></a>
+<a class="indexterm" name="id2670330"></a>
+<a class="indexterm" name="id2670337"></a>
+<a class="indexterm" name="id2670344"></a>
 		Though 2-byte fixed UCS-2 encoding is used in Windows internally,
 		Shift_JIS series encoding is usually used in Japanese environments
 		as ASCII encoding is in English environments.
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670218"></a>Basic Parameter Setting</h3></div></div></div><p>
-<a class="indexterm" name="id2670225"></a>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670356"></a>Basic Parameter Setting</h3></div></div></div><p>
+<a class="indexterm" name="id2670363"></a>
 	The <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a> and 
 	<a class="link" href="smb.conf.5.html#DISPLAYCHARSET" target="_top">display charset</a>
 	should be set to the locale compatible with the character set 
 	and encoding method used on Windows. This is usually CP932
 	but sometimes has a different name.
 	</p><p>
-<a class="indexterm" name="id2670262"></a>
-<a class="indexterm" name="id2670268"></a>
-<a class="indexterm" name="id2670275"></a>
+<a class="indexterm" name="id2670400"></a>
+<a class="indexterm" name="id2670406"></a>
+<a class="indexterm" name="id2670413"></a>
 	The <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> can be either Shift_JIS series,
 	EUC-JP series, or UTF-8. UTF-8 is always available, but the availability of other locales
 	and the name itself depends on the system.
@@ -166,8 +166,8 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			only. It is good practice to verify that the Japanized free software can work
 			with Shift_JIS.
 			</p></dd><dt><span class="term">EUC-JP series</span></dt><dd><p>
-<a class="indexterm" name="id2670409"></a>
-<a class="indexterm" name="id2670416"></a>
+<a class="indexterm" name="id2670547"></a>
+<a class="indexterm" name="id2670554"></a>
 			EUC-JP series means a locale that is equivalent to the industry
 			standard called EUC-JP, widely used in Japanese UNIX (although EUC
 			contains specifications for languages other than Japanese, such as
@@ -176,16 +176,16 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			Windows on Samba, the filename on UNIX becomes 0xb6a6, 0xcdad,
 			&#8220;<span class="quote">.txt</span>&#8221; (an 8-byte BINARY string). 
 			</p><p>
-<a class="indexterm" name="id2670441"></a>
-<a class="indexterm" name="id2670448"></a>
-<a class="indexterm" name="id2670454"></a>
-<a class="indexterm" name="id2670461"></a>
-<a class="indexterm" name="id2670468"></a>
-<a class="indexterm" name="id2670475"></a>
-<a class="indexterm" name="id2670482"></a>
-<a class="indexterm" name="id2670488"></a>
-<a class="indexterm" name="id2670495"></a>
-<a class="indexterm" name="id2670502"></a>
+<a class="indexterm" name="id2670579"></a>
+<a class="indexterm" name="id2670585"></a>
+<a class="indexterm" name="id2670592"></a>
+<a class="indexterm" name="id2670599"></a>
+<a class="indexterm" name="id2670606"></a>
+<a class="indexterm" name="id2670613"></a>
+<a class="indexterm" name="id2670619"></a>
+<a class="indexterm" name="id2670626"></a>
+<a class="indexterm" name="id2670633"></a>
+<a class="indexterm" name="id2670640"></a>
 			Since EUC-JP is usually used on open source UNIX, Linux, and FreeBSD, and on commercial-based UNIX, Solaris,
 			IRIX, and Tru64 UNIX as Japanese locale (however, it is also possible on Solaris to use Shift_JIS and UTF-8,
 			and on Tru64 UNIX it is possible to use Shift_JIS). To use EUC-JP series, most Japanese filenames created from
@@ -198,7 +198,7 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			commands that cannot handle non-ASCII filenames may be aborted
 			during parsing filenames.
 			</p><p>
-<a class="indexterm" name="id2670535"></a>
+<a class="indexterm" name="id2670673"></a>
 			Moreover, if you built Samba using differently installed libiconv,
 			the eucJP-ms locale included in libiconv and EUC-JP series locale
 			included in the operating system may not be compatible. In this case, you may need to
@@ -223,9 +223,9 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			must be handled carefully, so you had better not touch filenames
 			written from Windows on UNIX.
 			</p><p>
-<a class="indexterm" name="id2670608"></a>
-<a class="indexterm" name="id2670615"></a>
-<a class="indexterm" name="id2670622"></a>
+<a class="indexterm" name="id2670746"></a>
+<a class="indexterm" name="id2670753"></a>
+<a class="indexterm" name="id2670760"></a>
 			In addition, although it is not directly concerned with Samba, since
 			there is a delicate difference between the iconv() function, which is
 			generally used on UNIX, and the functions used on other platforms,
@@ -233,14 +233,14 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			Shift_JIS and Unicode UTF-8 must be done with care and recognition
 			of the limitations involved in the process.
 			</p><p>
-<a class="indexterm" name="id2670639"></a>
+<a class="indexterm" name="id2670777"></a>
 			Although Mac OS X uses UTF-8 as its encoding method for filenames,
 			it uses an extended UTF-8 specification that Samba cannot handle, so
 			UTF-8 locale is not available for Mac OS X.
 			</p></dd><dt><span class="term">Shift_JIS series + vfs_cap (CAP encoding)</span></dt><dd><p>
-<a class="indexterm" name="id2670660"></a>
-<a class="indexterm" name="id2670666"></a>
-<a class="indexterm" name="id2670673"></a>
+<a class="indexterm" name="id2670798"></a>
+<a class="indexterm" name="id2670804"></a>
+<a class="indexterm" name="id2670811"></a>
 			CAP encoding means a specification used in CAP and NetAtalk, file
 			server software for Macintosh. In the case of CAP encoding, for
 			example, if a Japanese filename consists of 0x8ba4 and 0x974c, and
@@ -269,14 +269,14 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			</p><p>
 			To use CAP encoding on Samba-3, you should use the unix charset parameter and VFS 
 			as in <a class="link" href="unicode.html#vfscap-intl" title="Example�30.1.�VFS CAP">the VFS CAP smb.conf file</a>.
-			</p><div class="example"><a name="vfscap-intl"></a><p class="title"><b>Example�30.1.�VFS CAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># the locale name "CP932" may be different</td></tr><tr><td><a class="indexterm" name="id2670773"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2670784"></a><em class="parameter"><code>unix charset = CP932</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[cap-share]</code></em></td></tr><tr><td><a class="indexterm" name="id2670805"></a><em class="parameter"><code>vfs option = cap</code></em></td></tr></table></div></div><br class="example-break"><p>
-<a class="indexterm" name="id2670820"></a>
-<a class="indexterm" name="id2670827"></a>
-<a class="indexterm" name="id2670833"></a>
-<a class="indexterm" name="id2670840"></a>
+			</p><div class="example"><a name="vfscap-intl"></a><p class="title"><b>Example�30.1.�VFS CAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># the locale name "CP932" may be different</td></tr><tr><td><a class="indexterm" name="id2670910"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2670922"></a><em class="parameter"><code>unix charset = CP932</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[cap-share]</code></em></td></tr><tr><td><a class="indexterm" name="id2670943"></a><em class="parameter"><code>vfs option = cap</code></em></td></tr></table></div></div><br class="example-break"><p>
+<a class="indexterm" name="id2670958"></a>
+<a class="indexterm" name="id2670964"></a>
+<a class="indexterm" name="id2670971"></a>
+<a class="indexterm" name="id2670978"></a>
 			You should set CP932 if using GNU libiconv for unix charset. With this setting,
 			filenames in the &#8220;<span class="quote">cap-share</span>&#8221; share are written with CAP encoding.
-			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670859"></a>Individual Implementations</h3></div></div></div><p>
+			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670996"></a>Individual Implementations</h3></div></div></div><p>
 Here is some additional information regarding individual implementations:
 </p><div class="variablelist"><dl><dt><span class="term">GNU libiconv</span></dt><dd><p>
 			To handle Japanese correctly, you should apply the patch
@@ -299,15 +299,15 @@ display charset = CP932
 			to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later.
 			</p><p>
 			Using the above glibc, these setting are available:
-			</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2670935"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2670947"></a><em class="parameter"><code>unix charset = CP932 / eucJP-ms / UTF-8</code></em></td></tr><tr><td><a class="indexterm" name="id2670959"></a><em class="parameter"><code>display charset = CP932</code></em></td></tr></table><p>
+			</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2671073"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2671085"></a><em class="parameter"><code>unix charset = CP932 / eucJP-ms / UTF-8</code></em></td></tr><tr><td><a class="indexterm" name="id2671097"></a><em class="parameter"><code>display charset = CP932</code></em></td></tr></table><p>
 			</p><p>
 			Other Japanese locales (for example, Shift_JIS and EUC-JP) should not
 			be used because of the lack of the compatibility with Windows.
-			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670982"></a>Migration from Samba-2.2 Series</h3></div></div></div><p> 
+			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671120"></a>Migration from Samba-2.2 Series</h3></div></div></div><p> 
 Prior to Samba-2.2 series, the &#8220;<span class="quote">coding system</span>&#8221; parameter was used. The default codepage in Samba
 2.x was code page 850. In the Samba-3 series this has been replaced with the <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> parameter.  <a class="link" href="unicode.html#japancharsets" title="Table�30.1.�Japanese Character Sets in Samba-2.2 and Samba-3">Japanese Character Sets in Samba-2.2 and Samba-3</a>
 shows the mapping table when migrating from the Samba-2.2 series to Samba-3.
-</p><div class="table"><a name="japancharsets"></a><p class="title"><b>Table�30.1.�Japanese Character Sets in Samba-2.2 and Samba-3</b></p><div class="table-contents"><table summary="Japanese Character Sets in Samba-2.2 and Samba-3" border="1"><colgroup><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Samba-2.2 Coding System</th><th align="center">Samba-3 unix charset</th></tr></thead><tbody><tr><td align="center">SJIS</td><td align="center">Shift_JIS series</td></tr><tr><td align="center">EUC</td><td align="center">EUC-JP series</td></tr><tr><td align="center">EUC3<sup>[<a name="id2671078" href="#ftn.id2671078" class="footnote">a</a>]</sup></td><td align="center">EUC-JP series</td></tr><tr><td align="center">CAP</td><td align="center">Shift_JIS series + VFS</td></tr><tr><td align="center">HEX</td><td align="center">currently none</td></tr><tr><td align="center">UTF8</td><td align="center">UTF-8</td></tr><tr><td align="center">UTF8-Mac<sup>[<a name="id2671108" href="#ftn.id2671108" class="footnote">b</a>]</sup></td><td align="center">currently none</td></tr><tr><td align="center">others</td><td align="center">none</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2671078" href="#id2671078" class="para">a</a>] </sup>Only exists in Japanese Samba version</p></div><div class="footnote"><p><sup>[<a name="ftn.id2671108" href="#id2671108" class="para">b</a>] </sup>Only exists in Japanese Samba version</p></div></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671128"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671134"></a>CP850.so Can't Be Found</h3></div></div></div><p>&#8220;<span class="quote">Samba is complaining about a missing <code class="filename">CP850.so</code> file.</span>&#8221;</p><p>
+</p><div class="table"><a name="japancharsets"></a><p class="title"><b>Table�30.1.�Japanese Character Sets in Samba-2.2 and Samba-3</b></p><div class="table-contents"><table summary="Japanese Character Sets in Samba-2.2 and Samba-3" border="1"><colgroup><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Samba-2.2 Coding System</th><th align="center">Samba-3 unix charset</th></tr></thead><tbody><tr><td align="center">SJIS</td><td align="center">Shift_JIS series</td></tr><tr><td align="center">EUC</td><td align="center">EUC-JP series</td></tr><tr><td align="center">EUC3<sup>[<a name="id2671215" href="#ftn.id2671215" class="footnote">a</a>]</sup></td><td align="center">EUC-JP series</td></tr><tr><td align="center">CAP</td><td align="center">Shift_JIS series + VFS</td></tr><tr><td align="center">HEX</td><td align="center">currently none</td></tr><tr><td align="center">UTF8</td><td align="center">UTF-8</td></tr><tr><td align="center">UTF8-Mac<sup>[<a name="id2671246" href="#ftn.id2671246" class="footnote">b</a>]</sup></td><td align="center">currently none</td></tr><tr><td align="center">others</td><td align="center">none</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2671215" href="#id2671215" class="para">a</a>] </sup>Only exists in Japanese Samba version</p></div><div class="footnote"><p><sup>[<a name="ftn.id2671246" href="#id2671246" class="para">b</a>] </sup>Only exists in Japanese Samba version</p></div></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671266"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671272"></a>CP850.so Can't Be Found</h3></div></div></div><p>&#8220;<span class="quote">Samba is complaining about a missing <code class="filename">CP850.so</code> file.</span>&#8221;</p><p>
 		CP850 is the default <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a>.
 		The <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a> is used to convert data to the codepage used by your DOS clients.
 		If you do not have any DOS clients, you can safely ignore this message. </p><p>
diff --git a/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html b/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html
index b63e4c4829..4580a0fc08 100644
--- a/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html
+++ b/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�35.�Updating and Upgrading Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="next" href="NT4Migration.html" title="Chapter�36.�Migration from NT4 PDC to Samba-3 PDC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�35.�Updating and Upgrading Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="migration.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="NT4Migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter�35.�Updating and Upgrading Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">August 16, 2007</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676070">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676098">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676148">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676299">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676308">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676318">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677518">New Functionality</a></span></dt></dl></dd></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�35.�Updating and Upgrading Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="next" href="NT4Migration.html" title="Chapter�36.�Migration from NT4 PDC to Samba-3 PDC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�35.�Updating and Upgrading Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="migration.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="NT4Migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter�35.�Updating and Upgrading Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">August 16, 2007</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676214">Key Update Requirements</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676251">Upgrading from Samba-3.0.x to Samba-3.2.0</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676300">Quick Migration Guide</a></span></dt></dl></dd><dt><span class="sect1"><a href="upgrading-to-3.0.html#id2676451">New Features in Samba-3.x Series</a></span></dt><dd><dl><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676460">New Features in Samba-3.2.x Series</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2676470">New Features in Samba-3.0.x</a></span></dt><dt><span class="sect2"><a href="upgrading-to-3.0.html#id2677671">New Functionality</a></span></dt></dl></dd></dl></div><p>
 This chapter provides a detailed record of changes made during the 3.x series releases. At this time this
 series consists of the 3.0.x series that is under the GNU GPL version 2 license, and the Samba 3.2.x series
 that is being released under the terms of the GNU GPL version 3 license.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2676070"></a>Key Update Requirements</h2></div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2676214"></a>Key Update Requirements</h2></div></div></div><p>
 Samba is a fluid product in which there may be significant changes between releases. Some of these changes are
 brought about as a result of changes in the protocols that are used by Microsoft Windows network clients as a
 result of security or functionality updates through official Microsoft patches and updates. Samba must track
@@ -13,113 +13,113 @@ all changes that apply to a new release will apply to follow-on releases also. F
 3.0.23 affect all releases up to an including 3.0.25 and later.  Samba 3.2.x was originaly cut from Samba
 3.0.25 before 3.2.0-specific changes were applied. Unless a 3.0.x series feature is specifically revoked, the
 behavior of the 3.2.x series can be expected to follow the earlier pattern.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676098"></a>Upgrading from Samba-3.0.x to Samba-3.2.0</h3></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676251"></a>Upgrading from Samba-3.0.x to Samba-3.2.0</h3></div></div></div><p>
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="oldupdatenotes"></a>Upgrading from Samba-2.x to Samba-3.0.25</h3></div></div></div><p>
-<a class="indexterm" name="id2676121"></a>
-<a class="indexterm" name="id2676128"></a>
-<a class="indexterm" name="id2676135"></a>
+<a class="indexterm" name="id2676274"></a>
+<a class="indexterm" name="id2676280"></a>
+<a class="indexterm" name="id2676287"></a>
 This chapter deals exclusively with the differences between Samba-3.0.25 and Samba-2.2.8a.
 It points out where configuration parameters have changed, and provides a simple guide for
 the move from 2.2.x to 3.0.25.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676148"></a>Quick Migration Guide</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676300"></a>Quick Migration Guide</h3></div></div></div><p>
 Samba-3.0.25 default behavior should be approximately the same as Samba-2.2.x.
 The default behavior when the new parameter <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>
 is not defined in the <code class="filename">smb.conf</code> file provides the same default behavior as Samba-2.2.x
 with <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = Yes</a> and
 will use the <code class="filename">smbpasswd</code> database.
 </p><p>
-<a class="indexterm" name="id2676198"></a>
-<a class="indexterm" name="id2676205"></a>
+<a class="indexterm" name="id2676351"></a>
+<a class="indexterm" name="id2676358"></a>
 So why say that <span class="emphasis"><em>behavior should be approximately the same as Samba-2.2.x</em></span>? Because
 Samba-3.0.25 can negotiate new protocols, such as support for native Unicode, that may result in
 differing protocol code paths being taken. The new behavior under such circumstances is not
 exactly the same as the old one. The good news is that the domain and machine SIDs will be
 preserved across the upgrade.
 </p><p>
-<a class="indexterm" name="id2676226"></a>
-<a class="indexterm" name="id2676233"></a>
-<a class="indexterm" name="id2676239"></a>
-<a class="indexterm" name="id2676246"></a>
+<a class="indexterm" name="id2676378"></a>
+<a class="indexterm" name="id2676385"></a>
+<a class="indexterm" name="id2676392"></a>
+<a class="indexterm" name="id2676399"></a>
 If the Samba-2.2.x system is using an LDAP backend, and there is no time to update the LDAP
 database, then make sure that <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend = ldapsam_compat</a>
 is specified in the <code class="filename">smb.conf</code> file. For the rest, behavior should remain more or less the same.
 At a later date, when there is time to implement a new Samba-3-compatible LDAP backend, it is possible
 to migrate the old LDAP database to the new one through use of the <code class="literal">pdbedit</code>.
 See <a class="link" href="passdb.html#pdbeditthing" title="The pdbedit Tool">The <span class="emphasis"><em>pdbedit</em></span> Command</a>.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2676299"></a>New Features in Samba-3.x Series</h2></div></div></div><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676308"></a>New Features in Samba-3.2.x Series</h3></div></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676318"></a>New Features in Samba-3.0.x</h3></div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2676451"></a>New Features in Samba-3.x Series</h2></div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676460"></a>New Features in Samba-3.2.x Series</h3></div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2676470"></a>New Features in Samba-3.0.x</h3></div></div></div><p>
 The major new features are:
 </p><div class="orderedlist"><ol type="1"><li><p>
-<a class="indexterm" name="id2676340"></a>
-<a class="indexterm" name="id2676347"></a>
+<a class="indexterm" name="id2676492"></a>
+<a class="indexterm" name="id2676498"></a>
 	Active Directory support. This release is able to join an ADS realm
 	as a member server and authenticate users using LDAP/Kerberos.
 	</p></li><li><p>
-<a class="indexterm" name="id2676360"></a>
-<a class="indexterm" name="id2676367"></a>
+<a class="indexterm" name="id2676512"></a>
+<a class="indexterm" name="id2676519"></a>
 	Unicode support. Samba will now negotiate Unicode on the wire, and
 	internally there is a much better infrastructure for multibyte
 	and Unicode character sets.
 	</p></li><li><p>
-<a class="indexterm" name="id2676381"></a>
+<a class="indexterm" name="id2676533"></a>
 	New authentication system. The internal authentication system has
 	been almost completely rewritten. Most of the changes are internal,
 	but the new authoring system is also very configurable.
 	</p></li><li><p>
-<a class="indexterm" name="id2676395"></a>
+<a class="indexterm" name="id2676547"></a>
 	New filename mangling system. The filename mangling system has been
 	completely rewritten. An internal database now stores mangling maps
 	persistently.
 	</p></li><li><p>
-<a class="indexterm" name="id2676409"></a>
+<a class="indexterm" name="id2676561"></a>
 	New &#8220;<span class="quote">net</span>&#8221; command. A new &#8220;<span class="quote">net</span>&#8221; command has been added. It is
 	somewhat similar to the &#8220;<span class="quote">net</span>&#8221; command in Windows. Eventually, we
 	plan to replace a bunch of other utilities (such as smbpasswd)
 	with subcommands in &#8220;<span class="quote">net</span>&#8221;.
 	</p></li><li><p>
-<a class="indexterm" name="id2676437"></a>
+<a class="indexterm" name="id2676589"></a>
 	Samba now negotiates NT-style status32 codes on the wire. This
 	considerably improves error handling.
 	</p></li><li><p>
-<a class="indexterm" name="id2676450"></a>
+<a class="indexterm" name="id2676602"></a>
 	Better Windows 200x/XP printing support, including publishing
 	printer attributes in Active Directory.
 	</p></li><li><p>
-<a class="indexterm" name="id2676463"></a>
-<a class="indexterm" name="id2676470"></a>
-<a class="indexterm" name="id2676477"></a>
+<a class="indexterm" name="id2676615"></a>
+<a class="indexterm" name="id2676622"></a>
+<a class="indexterm" name="id2676629"></a>
 	New loadable RPC modules for passdb backends and character sets.
 	</p></li><li><p>
-<a class="indexterm" name="id2676490"></a>
+<a class="indexterm" name="id2676642"></a>
 	New default dual-daemon winbindd support for better performance.
 	</p></li><li><p>
-<a class="indexterm" name="id2676502"></a>
-<a class="indexterm" name="id2676509"></a>
-<a class="indexterm" name="id2676516"></a>
+<a class="indexterm" name="id2676654"></a>
+<a class="indexterm" name="id2676661"></a>
+<a class="indexterm" name="id2676668"></a>
 	Support for migrating from a Windows NT 4.0 domain to a Samba
 	domain and maintaining user, group, and domain SIDs.
 	</p></li><li><p>
-<a class="indexterm" name="id2676529"></a>
-<a class="indexterm" name="id2676535"></a>
+<a class="indexterm" name="id2676681"></a>
+<a class="indexterm" name="id2676688"></a>
 	Support for establishing trust relationships with Windows NT 4.0
 	domain controllers.
 	</p></li><li><p>
-<a class="indexterm" name="id2676548"></a>
-<a class="indexterm" name="id2676555"></a>
-<a class="indexterm" name="id2676562"></a>
+<a class="indexterm" name="id2676701"></a>
+<a class="indexterm" name="id2676708"></a>
+<a class="indexterm" name="id2676715"></a>
 	Initial support for a distributed Winbind architecture using
 	an LDAP directory for storing SID to UID/GID mappings.
 	</p></li><li><p>
 	Major updates to the Samba documentation tree.
 	</p></li><li><p>
-<a class="indexterm" name="id2676580"></a>
-<a class="indexterm" name="id2676587"></a>
+<a class="indexterm" name="id2676733"></a>
+<a class="indexterm" name="id2676740"></a>
 	Full support for client and server SMB signing to ensure
 	compatibility with default Windows 2003 security settings.
 	</p></li></ol></div><p>
 Plus lots of other improvements!
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676602"></a>Configuration Parameter Changes</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676755"></a>Configuration Parameter Changes</h4></div></div></div><p>
 This section contains a brief listing of changes to <code class="filename">smb.conf</code> options since the Samba-2.2.x series up to and
 including Samba-3.0.25.
 </p><p>
@@ -130,83 +130,83 @@ Whenever a Samba update or upgrade is performed it is highly recommended to read
 <span class="emphasis"><em>WHATSNEW.txt</em></span> that is part of the Samba distribution tarball. This file may also
 be obtain on-line from the Samba <a class="ulink" href="http://www.samba.org/samba/" target="_top">web site</a>, in
 the right column, under Current Stable Release, by clicking on <span class="emphasis"><em>Release Notes</em></span>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676647"></a>Removed Parameters</h4></div></div></div><a class="indexterm" name="id2676653"></a><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676800"></a>Removed Parameters</h4></div></div></div><a class="indexterm" name="id2676805"></a><p>
 In alphabetical order, these are the parameters eliminated from Samba-2.2.x through 3.0.25.
-</p><div class="itemizedlist"><ul type="disc"><li><p>admin log</p></li><li><p>alternate permissions</p></li><li><p>character set</p></li><li><p>client codepage</p></li><li><p>code page directory</p></li><li><p>coding system</p></li><li><p>domain admin group</p></li><li><p>domain guest group</p></li><li><p>enable rid algorithm</p></li><li><p>enable svcctl</p></li><li><p>force unknown acl user</p></li><li><p>hosts equiv</p></li><li><p>ldap filter</p></li><li><p>min password length</p></li><li><p>nt smb support</p></li><li><p>post script</p></li><li><p>printer admin</p></li><li><p>printer driver</p></li><li><p>printer driver file</p></li><li><p>printer driver location</p></li><li><p>read size</p></li><li><p>source environment</p></li><li><p>status </p></li><li><p>strip dot </p></li><li><p>total print jobs</p></li><li><p>unicode</p></li><li><p>use rhosts</p></li><li><p>valid chars</p></li><li><p>vfs options</p></li><li><p>winbind enable local accounts</p></li><li><p>winbind max idle children</p></li><li><p>wins partners</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676818"></a>New Parameters</h4></div></div></div><p>The following new parameters have been released up to and including Samba 3.0.25 (grouped by function:)</p><p>Remote Management</p><a class="indexterm" name="id2676832"></a><div class="itemizedlist"><ul type="disc"><li><p>abort shutdown script</p></li><li><p>shutdown script</p></li></ul></div><p>User and Group Account Management</p><div class="itemizedlist"><ul type="disc"><li><p>add group script</p></li><li><p>add machine script</p></li><li><p>add user to group script</p></li><li><p>algorithmic rid base</p></li><li><p>delete group script</p></li><li><p>delete user from group script</p></li><li><p>passdb backend</p></li><li><p>rename user script</p></li><li><p>set primary group script</p></li><li><p>username map script</p></li></ul></div><p>Authentication</p><div class="itemizedlist"><ul type="disc"><li><p>auth methods</p></li><li><p>ldap password sync</p></li><li><p>passdb expand explicit</p></li><li><p>realm</p></li></ul></div><p>Protocol Options</p><div class="itemizedlist"><ul type="disc"><li><p>add port command</p></li><li><p>afs token lifetime</p></li><li><p>client lanman auth</p></li><li><p>client NTLMv2 auth</p></li><li><p>client schannel</p></li><li><p>client signing</p></li><li><p>client use spnego</p></li><li><p>defer sharing violations</p></li><li><p>disable netbios</p></li><li><p>dmapi support</p></li><li><p>enable privileges</p></li><li><p>use kerberos keytab</p></li><li><p>log nt token command</p></li><li><p>ntlm auth</p></li><li><p>paranoid server security </p></li><li><p>sendfile</p></li><li><p>server schannel</p></li><li><p>server signing</p></li><li><p>smb ports</p></li><li><p>svcctl list</p></li><li><p>use spnego</p></li></ul></div><p>File Service</p><div class="itemizedlist"><ul type="disc"><li><p>allocation roundup size</p></li><li><p>acl check permissions</p></li><li><p>acl group control</p></li><li><p>acl map full control</p></li><li><p>aio read size</p></li><li><p>aio write size</p></li><li><p>dfree cache time</p></li><li><p>dfree command</p></li><li><p>ea support</p></li><li><p>enable asu support</p></li><li><p>fam change notify</p></li><li><p>force unknown acl user</p></li><li><p>get quota command</p></li><li><p>hide special files</p></li><li><p>hide unwriteable files</p></li><li><p>inherit owner</p></li><li><p>hostname lookups</p></li><li><p>kernel change notify</p></li><li><p>mangle prefix</p></li><li><p>map acl inherit</p></li><li><p>map read only</p></li><li><p>max stat cache size</p></li><li><p>msdfs proxy</p></li><li><p>open files database hash size</p></li><li><p>set quota command</p></li><li><p>store dos attributes</p></li><li><p>use sendfile</p></li><li><p>usershare allow guests</p></li><li><p>usershare max shares</p></li><li><p>usershare owner only</p></li><li><p>usershare path</p></li><li><p>usershare prefix allow list</p></li><li><p>usershare prefix deny list</p></li><li><p>usershare template share</p></li><li><p>vfs objects</p></li></ul></div><p>Printing</p><div class="itemizedlist"><ul type="disc"><li><p>cups options</p></li><li><p>cups server</p></li><li><p>force printername</p></li><li><p>iprint server</p></li><li><p>max reported print jobs</p></li><li><p>printcap cache time</p></li></ul></div><p>Unicode and Character Sets</p><div class="itemizedlist"><ul type="disc"><li><p>display charset</p></li><li><p>dos charset</p></li><li><p>UNIX charset</p></li></ul></div><p>SID to UID/GID Mappings</p><div class="itemizedlist"><ul type="disc"><li><p>idmap backend</p></li><li><p>idmap gid</p></li><li><p>idmap uid</p></li><li><p>username map script</p></li><li><p>winbind nss info</p></li><li><p>winbind offline logon</p></li><li><p>winbind refresh tickets</p></li><li><p>winbind trusted domains only</p></li><li><p>template primary group</p></li></ul></div><p>LDAP</p><div class="itemizedlist"><ul type="disc"><li><p>ldap delete dn</p></li><li><p>ldap group suffix</p></li><li><p>ldap idmap suffix</p></li><li><p>ldap machine suffix</p></li><li><p>ldap passwd sync</p></li><li><p>ldap replication sleep</p></li><li><p>ldap timeout</p></li><li><p>ldap user suffix</p></li></ul></div><p>General Configuration</p><div class="itemizedlist"><ul type="disc"><li><p>eventlog list</p></li><li><p>preload modules</p></li><li><p>reset on zero vc</p></li><li><p>privatedir</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677383"></a>Modified Parameters (Changes in Behavior)</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>acl group control (new default is No, deprecated parameter)</p></li><li><p>change notify timeout (scope changed)</p></li><li><p>dos filemode (disabled by default)</p></li><li><p>dos filetimes (enabled by default)</p></li><li><p>enable asu support (disabled by default)</p></li><li><p>enable privileges (enabled by default)</p></li><li><p>encrypt passwords (enabled by default) </p></li><li><p>host msdfs (enabled by default)</p></li><li><p>mangling method (set to hash2 by default) </p></li><li><p>map to guest</p></li><li><p>only user (deprecated)</p></li><li><p>passwd chat</p></li><li><p>passwd program</p></li><li><p>password server</p></li><li><p>restrict anonymous (integer value)</p></li><li><p>security (new ads value)</p></li><li><p>strict locking (auto by default)</p></li><li><p>winbind cache time (increased to 5 minutes)</p></li><li><p>winbind enum groups (disabled by default)</p></li><li><p>winbind enum users (disabled by default)</p></li><li><p>winbind nested groups (enabled by default)</p></li><li><p>winbind uid (deprecated in favor of idmap uid)</p></li><li><p>winbind gid (deprecated in favor of idmap gid)</p></li><li><p>winbindd nss info</p></li><li><p>write cache (deprecated)</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2677518"></a>New Functionality</h3></div></div></div><p>
-<a class="indexterm" name="id2677526"></a>
+</p><div class="itemizedlist"><ul type="disc"><li><p>admin log</p></li><li><p>alternate permissions</p></li><li><p>character set</p></li><li><p>client codepage</p></li><li><p>code page directory</p></li><li><p>coding system</p></li><li><p>domain admin group</p></li><li><p>domain guest group</p></li><li><p>enable rid algorithm</p></li><li><p>enable svcctl</p></li><li><p>force unknown acl user</p></li><li><p>hosts equiv</p></li><li><p>ldap filter</p></li><li><p>min password length</p></li><li><p>nt smb support</p></li><li><p>post script</p></li><li><p>printer admin</p></li><li><p>printer driver</p></li><li><p>printer driver file</p></li><li><p>printer driver location</p></li><li><p>read size</p></li><li><p>source environment</p></li><li><p>status </p></li><li><p>strip dot </p></li><li><p>total print jobs</p></li><li><p>unicode</p></li><li><p>use rhosts</p></li><li><p>valid chars</p></li><li><p>vfs options</p></li><li><p>winbind enable local accounts</p></li><li><p>winbind max idle children</p></li><li><p>wins partners</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2676970"></a>New Parameters</h4></div></div></div><p>The following new parameters have been released up to and including Samba 3.0.25 (grouped by function:)</p><p>Remote Management</p><a class="indexterm" name="id2676985"></a><div class="itemizedlist"><ul type="disc"><li><p>abort shutdown script</p></li><li><p>shutdown script</p></li></ul></div><p>User and Group Account Management</p><div class="itemizedlist"><ul type="disc"><li><p>add group script</p></li><li><p>add machine script</p></li><li><p>add user to group script</p></li><li><p>algorithmic rid base</p></li><li><p>delete group script</p></li><li><p>delete user from group script</p></li><li><p>passdb backend</p></li><li><p>rename user script</p></li><li><p>set primary group script</p></li><li><p>username map script</p></li></ul></div><p>Authentication</p><div class="itemizedlist"><ul type="disc"><li><p>auth methods</p></li><li><p>ldap password sync</p></li><li><p>passdb expand explicit</p></li><li><p>realm</p></li></ul></div><p>Protocol Options</p><div class="itemizedlist"><ul type="disc"><li><p>add port command</p></li><li><p>afs token lifetime</p></li><li><p>client lanman auth</p></li><li><p>client NTLMv2 auth</p></li><li><p>client schannel</p></li><li><p>client signing</p></li><li><p>client use spnego</p></li><li><p>defer sharing violations</p></li><li><p>disable netbios</p></li><li><p>dmapi support</p></li><li><p>enable privileges</p></li><li><p>use kerberos keytab</p></li><li><p>log nt token command</p></li><li><p>ntlm auth</p></li><li><p>paranoid server security </p></li><li><p>sendfile</p></li><li><p>server schannel</p></li><li><p>server signing</p></li><li><p>smb ports</p></li><li><p>svcctl list</p></li><li><p>use spnego</p></li></ul></div><p>File Service</p><div class="itemizedlist"><ul type="disc"><li><p>allocation roundup size</p></li><li><p>acl check permissions</p></li><li><p>acl group control</p></li><li><p>acl map full control</p></li><li><p>aio read size</p></li><li><p>aio write size</p></li><li><p>dfree cache time</p></li><li><p>dfree command</p></li><li><p>ea support</p></li><li><p>enable asu support</p></li><li><p>fam change notify</p></li><li><p>force unknown acl user</p></li><li><p>get quota command</p></li><li><p>hide special files</p></li><li><p>hide unwriteable files</p></li><li><p>inherit owner</p></li><li><p>hostname lookups</p></li><li><p>kernel change notify</p></li><li><p>mangle prefix</p></li><li><p>map acl inherit</p></li><li><p>map read only</p></li><li><p>max stat cache size</p></li><li><p>msdfs proxy</p></li><li><p>open files database hash size</p></li><li><p>set quota command</p></li><li><p>store dos attributes</p></li><li><p>use sendfile</p></li><li><p>usershare allow guests</p></li><li><p>usershare max shares</p></li><li><p>usershare owner only</p></li><li><p>usershare path</p></li><li><p>usershare prefix allow list</p></li><li><p>usershare prefix deny list</p></li><li><p>usershare template share</p></li><li><p>vfs objects</p></li></ul></div><p>Printing</p><div class="itemizedlist"><ul type="disc"><li><p>cups options</p></li><li><p>cups server</p></li><li><p>force printername</p></li><li><p>iprint server</p></li><li><p>max reported print jobs</p></li><li><p>printcap cache time</p></li></ul></div><p>Unicode and Character Sets</p><div class="itemizedlist"><ul type="disc"><li><p>display charset</p></li><li><p>dos charset</p></li><li><p>UNIX charset</p></li></ul></div><p>SID to UID/GID Mappings</p><div class="itemizedlist"><ul type="disc"><li><p>idmap backend</p></li><li><p>idmap gid</p></li><li><p>idmap uid</p></li><li><p>username map script</p></li><li><p>winbind nss info</p></li><li><p>winbind offline logon</p></li><li><p>winbind refresh tickets</p></li><li><p>winbind trusted domains only</p></li><li><p>template primary group</p></li></ul></div><p>LDAP</p><div class="itemizedlist"><ul type="disc"><li><p>ldap delete dn</p></li><li><p>ldap group suffix</p></li><li><p>ldap idmap suffix</p></li><li><p>ldap machine suffix</p></li><li><p>ldap passwd sync</p></li><li><p>ldap replication sleep</p></li><li><p>ldap timeout</p></li><li><p>ldap user suffix</p></li></ul></div><p>General Configuration</p><div class="itemizedlist"><ul type="disc"><li><p>eventlog list</p></li><li><p>preload modules</p></li><li><p>reset on zero vc</p></li><li><p>privatedir</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677536"></a>Modified Parameters (Changes in Behavior)</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>acl group control (new default is No, deprecated parameter)</p></li><li><p>change notify timeout (scope changed)</p></li><li><p>dos filemode (disabled by default)</p></li><li><p>dos filetimes (enabled by default)</p></li><li><p>enable asu support (disabled by default)</p></li><li><p>enable privileges (enabled by default)</p></li><li><p>encrypt passwords (enabled by default) </p></li><li><p>host msdfs (enabled by default)</p></li><li><p>mangling method (set to hash2 by default) </p></li><li><p>map to guest</p></li><li><p>only user (deprecated)</p></li><li><p>passwd chat</p></li><li><p>passwd program</p></li><li><p>password server</p></li><li><p>restrict anonymous (integer value)</p></li><li><p>security (new ads value)</p></li><li><p>strict locking (auto by default)</p></li><li><p>winbind cache time (increased to 5 minutes)</p></li><li><p>winbind enum groups (disabled by default)</p></li><li><p>winbind enum users (disabled by default)</p></li><li><p>winbind nested groups (enabled by default)</p></li><li><p>winbind uid (deprecated in favor of idmap uid)</p></li><li><p>winbind gid (deprecated in favor of idmap gid)</p></li><li><p>winbindd nss info</p></li><li><p>write cache (deprecated)</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2677671"></a>New Functionality</h3></div></div></div><p>
+<a class="indexterm" name="id2677679"></a>
 	The major changes in behavior since that Samba-2.2.x series are documented in this section.
 	Please refer to the <code class="filename">WHATSNEW.txt</code> file that ships with every release of
 	Samba to obtain detailed information regarding the changes that have been made during the
 	life of the current Samba release.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677545"></a>TDB Data Files</h4></div></div></div><a class="indexterm" name="id2677551"></a><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677698"></a>TDB Data Files</h4></div></div></div><a class="indexterm" name="id2677703"></a><p>
 	Refer to <a class="link" href="install.html" title="Chapter�1.�How to Install and Test SAMBA">Installation, Chapter 1</a>, <a class="link" href="install.html#tdbdocs" title="TDB Database File Information">Chapter 1</a>
 	for information pertaining to the Samba-3 data files, their location and the information that must be
 	preserved across server migrations, updates and upgrades.
 	</p><p>
-<a class="indexterm" name="id2677581"></a>
+<a class="indexterm" name="id2677734"></a>
 	Please remember to back up your existing ${lock directory}/*tdb before upgrading to Samba-3. If necessary,
 	Samba will upgrade databases as they are opened. Downgrading from Samba-3 to 2.2, or reversion to an earlier
 	version of Samba-3 from a later release, is an unsupported path.
 	</p><p>
-<a class="indexterm" name="id2677596"></a>
+<a class="indexterm" name="id2677749"></a>
 	The old Samba-2.2.x tdb files are described in <a class="link" href="upgrading-to-3.0.html#oldtdbfiledesc" title="Table�35.1.�Samba-2.2.x TDB File Descriptions">the next table</a>.
 	</p><div class="table"><a name="oldtdbfiledesc"></a><p class="title"><b>Table�35.1.�Samba-2.2.x TDB File Descriptions</b></p><div class="table-contents"><table summary="Samba-2.2.x TDB File Descriptions" border="1"><colgroup><col align="left"><col align="justify"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="justify">Description</th><th align="center">Backup?</th></tr></thead><tbody><tr><td align="left">account_policy</td><td align="justify">User policy settings</td><td align="left">yes</td></tr><tr><td align="left">brlock</td><td align="justify">Byte-range file locking information.</td><td align="left">no</td></tr><tr><td align="left">connections</td><td align="justify"><p>Client connection information</p></td><td align="left">no</td></tr><tr><td align="left">locking</td><td align="justify">Temporary file locking data.</td><td align="left">no</td></tr><tr><td align="left">messages</td><td align="justify"><p>Temporary storage of messages being processed by smbd.</p></td><td align="left">no</td></tr><tr><td align="left">ntdrivers</td><td align="justify"><p>Stores per-printer driver information.</p></td><td align="left">yes</td></tr><tr><td align="left">ntforms</td><td align="justify"><p>Stores per-printer forms information.</p></td><td align="left">yes</td></tr><tr><td align="left">ntprinters</td><td align="justify"><p>Stores the per-printer devmode configuration settings.</p></td><td align="left">yes</td></tr><tr><td align="left">printing/*.tdb</td><td align="justify"><p>Cached output from lpq command created on a per-print-service basis.</p></td><td align="left">no</td></tr><tr><td align="left">registry</td><td align="justify"><p>Read-only Samba registry skeleton that provides support for
-				exporting various database tables via the winreg RPCs.</p></td><td align="left">no</td></tr><tr><td align="left">sessionid</td><td align="justify"><p>Temporary cache for miscellaneous session information.</p></td><td align="left">no</td></tr><tr><td align="left">share_info</td><td align="justify">Share ACL settings.</td><td align="left">yes</td></tr><tr><td align="left">unexpected</td><td align="justify"><p>Packets received for which no process was listening.</p></td><td align="left">no</td></tr><tr><td align="left">winbindd_cache</td><td align="justify"><p>Cache of identity information received from an NT4 or an ADS domain.</p></td><td align="left">yes</td></tr><tr><td align="left">winbindd_idmap</td><td align="justify"><p>New ID map table from SIDS to UNIX UIDs/GIDs.</p></td><td align="left">yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677897"></a>Changes in Behavior</h4></div></div></div><p>
+				exporting various database tables via the winreg RPCs.</p></td><td align="left">no</td></tr><tr><td align="left">sessionid</td><td align="justify"><p>Temporary cache for miscellaneous session information.</p></td><td align="left">no</td></tr><tr><td align="left">share_info</td><td align="justify">Share ACL settings.</td><td align="left">yes</td></tr><tr><td align="left">unexpected</td><td align="justify"><p>Packets received for which no process was listening.</p></td><td align="left">no</td></tr><tr><td align="left">winbindd_cache</td><td align="justify"><p>Cache of identity information received from an NT4 or an ADS domain.</p></td><td align="left">yes</td></tr><tr><td align="left">winbindd_idmap</td><td align="justify"><p>New ID map table from SIDS to UNIX UIDs/GIDs.</p></td><td align="left">yes</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2678050"></a>Changes in Behavior</h4></div></div></div><p>
 	The following issues are known changes in behavior between Samba-2.2 and
 	Samba-3 that may affect certain installations of Samba.
 	</p><div class="orderedlist"><ol type="1"><li><p>
-<a class="indexterm" name="id2677918"></a>
-<a class="indexterm" name="id2677925"></a>
-<a class="indexterm" name="id2677932"></a>
+<a class="indexterm" name="id2678071"></a>
+<a class="indexterm" name="id2678078"></a>
+<a class="indexterm" name="id2678085"></a>
 		When operating as a member of a Windows domain, Samba-2.2 would map any users authenticated by the remote DC
 		to the &#8220;<span class="quote">guest account</span>&#8221; if a UID could not be obtained via the getpwnam() call. Samba-3 rejects
 		the connection with the error message &#8220;<span class="quote">NT_STATUS_LOGON_FAILURE.</span>&#8221; There is no current workaround
 		to re-establish the Samba-2.2 behavior.
 		</p></li><li><p>
-<a class="indexterm" name="id2677956"></a>
-<a class="indexterm" name="id2677963"></a>
+<a class="indexterm" name="id2678109"></a>
+<a class="indexterm" name="id2678116"></a>
 		When adding machines to a Samba-2.2 controlled domain, the
 		&#8220;<span class="quote">add user script</span>&#8221; was used to create the UNIX identity of the
 		machine trust account. Samba-3 introduces a new &#8220;<span class="quote">add machine
 		script</span>&#8221; that must be specified for this purpose. Samba-3 will
 		not fall back to using the &#8220;<span class="quote">add user script</span>&#8221; in the absence of
 		an &#8220;<span class="quote">add machine script</span>&#8221;.
-		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2677993"></a>Passdb Backends and Authentication</h4></div></div></div><p>
+		</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2678146"></a>Passdb Backends and Authentication</h4></div></div></div><p>
 	There have been a few new changes that Samba administrators should be
 	aware of when moving to Samba-3.
 	</p><div class="orderedlist"><ol type="1"><li><p>
-<a class="indexterm" name="id2678014"></a>
+<a class="indexterm" name="id2678167"></a>
 		Encrypted passwords have been enabled by default in order to
 		interoperate better with out-of-the-box Windows client
 		installations. This does mean that either (a) a Samba account
 		must be created for each user, or (b) &#8220;<span class="quote">encrypt passwords = no</span>&#8221;
 		must be explicitly defined in <code class="filename">smb.conf</code>.
 		</p></li><li><p>
-<a class="indexterm" name="id2678040"></a>
-<a class="indexterm" name="id2678046"></a>
-<a class="indexterm" name="id2678053"></a>
+<a class="indexterm" name="id2678192"></a>
+<a class="indexterm" name="id2678199"></a>
+<a class="indexterm" name="id2678206"></a>
 		Inclusion of new <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = ads</a> option for integration
 		with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols.
 		</p></li></ol></div><p>
-<a class="indexterm" name="id2678079"></a>
+<a class="indexterm" name="id2678232"></a>
 	Samba-3 also includes the possibility of setting up chains of authentication methods (<a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods</a>) and account storage backends (<a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>).  Please refer to
 	the <code class="filename">smb.conf</code> man page and <a class="link" href="passdb.html" title="Chapter�11.�Account Information Databases">Account Information Databases</a>, for
 	details. While both parameters assume sane default values, it is likely that you will need to understand what
 	the values actually mean in order to ensure Samba operates correctly.
 	</p><p>
-<a class="indexterm" name="id2678130"></a>
-<a class="indexterm" name="id2678137"></a>
-<a class="indexterm" name="id2678144"></a>
+<a class="indexterm" name="id2678283"></a>
+<a class="indexterm" name="id2678289"></a>
+<a class="indexterm" name="id2678296"></a>
 	Certain functions of the <code class="literal">smbpasswd</code> tool have been split between the
 	new <code class="literal">smbpasswd</code> utility, the <code class="literal">net</code> tool, and the new <code class="literal">pdbedit</code>
 	utility. See the respective man pages for details.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2678178"></a>LDAP</h4></div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2678330"></a>LDAP</h4></div></div></div><p>
 	This section outlines the new features effecting Samba/LDAP integration.
-	</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678188"></a>New Schema</h5></div></div></div><p>
-<a class="indexterm" name="id2678196"></a>
-<a class="indexterm" name="id2678202"></a>
-<a class="indexterm" name="id2678209"></a>
-<a class="indexterm" name="id2678216"></a>
+	</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678340"></a>New Schema</h5></div></div></div><p>
+<a class="indexterm" name="id2678348"></a>
+<a class="indexterm" name="id2678355"></a>
+<a class="indexterm" name="id2678362"></a>
+<a class="indexterm" name="id2678369"></a>
 		A new object class (sambaSamAccount) has been introduced to replace
 		the old sambaAccount. This change aids in the renaming of attributes
 		to prevent clashes with attributes from other vendors. There is a
@@ -214,29 +214,29 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro
 		file to the new schema.
 		</p><p>
 		Example:
-<a class="indexterm" name="id2678232"></a>
+<a class="indexterm" name="id2678385"></a>
 		</p><pre class="screen">
 		<code class="prompt">$ </code>ldapsearch .... -LLL -b "ou=people,dc=..." &gt; old.ldif
 		<code class="prompt">$ </code>convertSambaAccount --sid &lt;DOM SID&gt; --input old.ldif --output new.ldif
 		</pre><p>
-<a class="indexterm" name="id2678264"></a>
+<a class="indexterm" name="id2678417"></a>
 		The &lt;DOM SID&gt; can be obtained by running
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>net getlocalsid &lt;DOMAINNAME&gt;</code></strong>
 </pre><p>
-<a class="indexterm" name="id2678291"></a>
+<a class="indexterm" name="id2678444"></a>
 		on the Samba PDC as root.
 		</p><p>
 		Under Samba-2.x the domain SID can be obtained by executing:
-<a class="indexterm" name="id2678303"></a>
+<a class="indexterm" name="id2678455"></a>
 </p><pre class="screen">
 <code class="prompt">$ </code><strong class="userinput"><code>smbpasswd -S &lt;DOMAINNAME&gt;</code></strong>
 </pre><p>
 		</p><p>
-<a class="indexterm" name="id2678329"></a>
-<a class="indexterm" name="id2678336"></a>
-<a class="indexterm" name="id2678343"></a>
-<a class="indexterm" name="id2678350"></a>
+<a class="indexterm" name="id2678481"></a>
+<a class="indexterm" name="id2678488"></a>
+<a class="indexterm" name="id2678495"></a>
+<a class="indexterm" name="id2678502"></a>
 		The old <code class="literal">sambaAccount</code> schema may still be used by specifying the
 		<em class="parameter"><code>ldapsam_compat</code></em> passdb backend. However, the sambaAccount and
 		associated attributes have been moved to the historical section of
@@ -246,53 +246,53 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro
 		</p><p>
 		Other new object classes and their uses include:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2678397"></a>
-<a class="indexterm" name="id2678404"></a>
-<a class="indexterm" name="id2678410"></a>
-<a class="indexterm" name="id2678417"></a>
-<a class="indexterm" name="id2678424"></a>
-<a class="indexterm" name="id2678431"></a>
+<a class="indexterm" name="id2678549"></a>
+<a class="indexterm" name="id2678556"></a>
+<a class="indexterm" name="id2678563"></a>
+<a class="indexterm" name="id2678570"></a>
+<a class="indexterm" name="id2678576"></a>
+<a class="indexterm" name="id2678583"></a>
 			<code class="literal">sambaDomain</code>  domain information used to allocate RIDs
 			for users and groups as necessary. The attributes are added
 			in &#8220;<span class="quote">ldap suffix</span>&#8221; directory entry automatically if
 			an idmap UID/GID range has been set and the &#8220;<span class="quote">ldapsam</span>&#8221;
 			passdb backend has been selected.
 			</p></li><li><p>
-<a class="indexterm" name="id2678461"></a>
-<a class="indexterm" name="id2678468"></a>
-<a class="indexterm" name="id2678475"></a>
+<a class="indexterm" name="id2678614"></a>
+<a class="indexterm" name="id2678621"></a>
+<a class="indexterm" name="id2678628"></a>
 			sambaGroupMapping  an object representing the
 			relationship between a posixGroup and a Windows
 			group/SID. These entries are stored in the &#8220;<span class="quote">ldap
 			group suffix</span>&#8221; and managed by the &#8220;<span class="quote">net groupmap</span>&#8221; command.
 			</p></li><li><p>
-<a class="indexterm" name="id2678500"></a>
-<a class="indexterm" name="id2678507"></a>
-<a class="indexterm" name="id2678514"></a>
-<a class="indexterm" name="id2678520"></a>
+<a class="indexterm" name="id2678652"></a>
+<a class="indexterm" name="id2678659"></a>
+<a class="indexterm" name="id2678666"></a>
+<a class="indexterm" name="id2678673"></a>
 			<code class="literal">sambaUNIXIdPool</code>  created in the &#8220;<span class="quote">ldap idmap suffix</span>&#8221; entry
 			automatically and contains the next available &#8220;<span class="quote">idmap UID</span>&#8221; and
 			&#8220;<span class="quote">idmap GID</span>&#8221;.
 			</p></li><li><p>
-<a class="indexterm" name="id2678552"></a>
-<a class="indexterm" name="id2678559"></a>
+<a class="indexterm" name="id2678705"></a>
+<a class="indexterm" name="id2678712"></a>
 			<code class="literal">sambaIdmapEntry</code>  object storing a mapping between a
 			SID and a UNIX UID/GID. These objects are created by the
 			idmap_ldap module as needed.
-			</p></li></ul></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678581"></a>New Suffix for Searching</h5></div></div></div><p>
-<a class="indexterm" name="id2678588"></a>
-<a class="indexterm" name="id2678595"></a>
-<a class="indexterm" name="id2678602"></a>
-<a class="indexterm" name="id2678609"></a>
-<a class="indexterm" name="id2678616"></a>
-<a class="indexterm" name="id2678623"></a>
-<a class="indexterm" name="id2678630"></a>
+			</p></li></ul></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678733"></a>New Suffix for Searching</h5></div></div></div><p>
+<a class="indexterm" name="id2678741"></a>
+<a class="indexterm" name="id2678748"></a>
+<a class="indexterm" name="id2678755"></a>
+<a class="indexterm" name="id2678761"></a>
+<a class="indexterm" name="id2678768"></a>
+<a class="indexterm" name="id2678775"></a>
+<a class="indexterm" name="id2678782"></a>
 		The following new <code class="filename">smb.conf</code> parameters have been added to aid in directing
 		certain LDAP queries when <em class="parameter"><code>passdb backend = ldapsam://...</code></em> has been
 		specified.
 		</p><div class="itemizedlist"><ul type="disc"><li><p>ldap suffix          used to search for user and computer accounts.</p></li><li><p>ldap user suffix     used to store user accounts.</p></li><li><p>ldap machine suffix  used to store machine trust accounts.</p></li><li><p>ldap group suffix    location of posixGroup/sambaGroupMapping entries.</p></li><li><p>ldap idmap suffix    location of sambaIdmapEntry objects.</p></li></ul></div><p>
-<a class="indexterm" name="id2678698"></a>
-<a class="indexterm" name="id2678705"></a>
+<a class="indexterm" name="id2678851"></a>
+<a class="indexterm" name="id2678857"></a>
 		If an <em class="parameter"><code>ldap suffix</code></em> is defined, it will be appended to all of the
 		remaining subsuffix parameters. In this case, the order of the suffix
 		listings in <code class="filename">smb.conf</code> is important. Always place the <em class="parameter"><code>ldap suffix</code></em> first
@@ -300,13 +300,13 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro
 		</p><p>
 		Due to a limitation in Samba's <code class="filename">smb.conf</code> parsing, you should not surround
 		the domain names with quotation marks.
-		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678746"></a>IdMap LDAP Support</h5></div></div></div><p>
-<a class="indexterm" name="id2678754"></a>
+		</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2678899"></a>IdMap LDAP Support</h5></div></div></div><p>
+<a class="indexterm" name="id2678907"></a>
 		Samba-3 supports an LDAP backend for the idmap subsystem. The
 		following options inform Samba that the idmap table should be
 		stored on the directory server <span class="emphasis"><em>onterose</em></span> in the ou=Idmap,dc=quenya,dc=org partition.
-		</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td>...</td></tr><tr><td><a class="indexterm" name="id2678787"></a><em class="parameter"><code>idmap backend = ldap:ldap://onterose/</code></em></td></tr><tr><td><a class="indexterm" name="id2678799"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2678811"></a><em class="parameter"><code>idmap uid = 40000-50000</code></em></td></tr><tr><td><a class="indexterm" name="id2678823"></a><em class="parameter"><code>idmap gid = 40000-50000</code></em></td></tr></table><p>
-<a class="indexterm" name="id2678836"></a>
+		</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td>...</td></tr><tr><td><a class="indexterm" name="id2678939"></a><em class="parameter"><code>idmap backend = ldap:ldap://onterose/</code></em></td></tr><tr><td><a class="indexterm" name="id2678952"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id2678964"></a><em class="parameter"><code>idmap uid = 40000-50000</code></em></td></tr><tr><td><a class="indexterm" name="id2678975"></a><em class="parameter"><code>idmap gid = 40000-50000</code></em></td></tr></table><p>
+<a class="indexterm" name="id2678989"></a>
 		This configuration allows Winbind installations on multiple servers to
 		share a UID/GID number space, thus avoiding the interoperability problems
 		with NFS that were present in Samba-2.2.
diff --git a/docs/htmldocs/Samba3-HOWTO/winbind.html b/docs/htmldocs/Samba3-HOWTO/winbind.html
index 6fd857f9a7..c239606a5e 100644
--- a/docs/htmldocs/Samba3-HOWTO/winbind.html
+++ b/docs/htmldocs/Samba3-HOWTO/winbind.html
@@ -1,23 +1,23 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�24.�Winbind: Use of Domain Accounts</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="VFS.html" title="Chapter�23.�Stackable VFS modules"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter�25.�Advanced Network Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�24.�Winbind: Use of Domain Accounts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter�24.�Winbind: Use of Domain Accounts</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="orgname">Samba Team</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="orgname">SNAP</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 15, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="winbind.html#id2652992">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653341">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653431">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653584">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653629">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653755">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653805">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653892">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653940">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654172">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654327">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654403">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654460">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654466">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654580">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654732">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657151">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657199">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657241">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657278">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2652992"></a>Features and Benefits</h2></div></div></div><p>
-<a class="indexterm" name="id2653000"></a>
-<a class="indexterm" name="id2653007"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�24.�Winbind: Use of Domain Accounts</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="VFS.html" title="Chapter�23.�Stackable VFS modules"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter�25.�Advanced Network Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�24.�Winbind: Use of Domain Accounts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter�24.�Winbind: Use of Domain Accounts</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="orgname">Samba Team</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span>�<div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="orgname">SNAP</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">June 15, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="winbind.html#id2653125">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653468">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653558">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653711">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653756">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653882">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654026">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654073">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654305">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654460">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654536">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654593">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654599">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654713">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654865">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657284">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657333">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657374">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657411">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653125"></a>Features and Benefits</h2></div></div></div><p>
+<a class="indexterm" name="id2653133"></a>
+<a class="indexterm" name="id2653139"></a>
 	Integration of UNIX and Microsoft Windows NT through a unified logon has
 	been considered a &#8220;<span class="quote">holy grail</span>&#8221; in heterogeneous computing environments for
 	a long time.
 	</p><p>
-<a class="indexterm" name="id2653024"></a>
-<a class="indexterm" name="id2653031"></a>
-<a class="indexterm" name="id2653038"></a>
-<a class="indexterm" name="id2653044"></a>
+<a class="indexterm" name="id2653156"></a>
+<a class="indexterm" name="id2653163"></a>
+<a class="indexterm" name="id2653170"></a>
+<a class="indexterm" name="id2653177"></a>
 	There is one other facility without which UNIX and Microsoft Windows network
 	interoperability would suffer greatly. It is imperative that there be a
 	mechanism for sharing files across UNIX systems and to be able to assign
 	domain user and group ownerships with integrity.
 	</p><p>
-<a class="indexterm" name="id2653059"></a>
-<a class="indexterm" name="id2653069"></a>
-<a class="indexterm" name="id2653076"></a>
-<a class="indexterm" name="id2653082"></a>
+<a class="indexterm" name="id2653192"></a>
+<a class="indexterm" name="id2653201"></a>
+<a class="indexterm" name="id2653208"></a>
+<a class="indexterm" name="id2653214"></a>
 	<span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs that
 	solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
 	RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to
@@ -27,23 +27,23 @@
 	</p><p>
 	Winbind provides three separate functions:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="indexterm" name="id2653110"></a>
-<a class="indexterm" name="id2653117"></a>
+<a class="indexterm" name="id2653242"></a>
+<a class="indexterm" name="id2653249"></a>
 		Authentication of user credentials (via PAM). This makes it possible to
 		log onto a UNIX/Linux system using user and group accounts from a Windows
 		NT4 (including a Samba domain) or an Active Directory domain.
 		</p></li><li><p>
-<a class="indexterm" name="id2653131"></a>
-<a class="indexterm" name="id2653138"></a>
+<a class="indexterm" name="id2653264"></a>
+<a class="indexterm" name="id2653271"></a>
 		Identity resolution (via NSS). This is the default when winbind is not used.
 		</p></li><li><p>
-<a class="indexterm" name="id2653151"></a>
-<a class="indexterm" name="id2653157"></a>
-<a class="indexterm" name="id2653164"></a>
-<a class="indexterm" name="id2653170"></a>
-<a class="indexterm" name="id2653177"></a>
-<a class="indexterm" name="id2653184"></a>
-<a class="indexterm" name="id2653191"></a>
+<a class="indexterm" name="id2653283"></a>
+<a class="indexterm" name="id2653289"></a>
+<a class="indexterm" name="id2653296"></a>
+<a class="indexterm" name="id2653302"></a>
+<a class="indexterm" name="id2653309"></a>
+<a class="indexterm" name="id2653316"></a>
+<a class="indexterm" name="id2653323"></a>
 		Winbind maintains a database called winbind_idmap.tdb in which it stores
 		mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
 		for users and groups that do not have a local UID/GID. It stores the UID/GID
@@ -52,23 +52,23 @@
 		then instead of using a local mapping, Winbind will obtain this information
 		from the LDAP database.
 		</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-	<a class="indexterm" name="id2653226"></a>
-	<a class="indexterm" name="id2653232"></a>
-<a class="indexterm" name="id2653242"></a>
-<a class="indexterm" name="id2653248"></a>
-<a class="indexterm" name="id2653255"></a>
-<a class="indexterm" name="id2653262"></a>
+	<a class="indexterm" name="id2653353"></a>
+	<a class="indexterm" name="id2653359"></a>
+<a class="indexterm" name="id2653369"></a>
+<a class="indexterm" name="id2653376"></a>
+<a class="indexterm" name="id2653382"></a>
+<a class="indexterm" name="id2653389"></a>
 	If <code class="literal">winbindd</code> is not running, smbd (which calls <code class="literal">winbindd</code>) will fall back to
 	using purely local information from <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> and no dynamic
 	mapping will be used. On an operating system that has been enabled with the NSS,
 	the resolution of user and group information will be accomplished via NSS.
-	</p></div><div class="figure"><a name="winbind_idmap"></a><p class="title"><b>Figure�24.1.�Winbind Idmap</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap_winbind_no_loop.png" width="243" alt="Winbind Idmap"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653341"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have
+	</p></div><div class="figure"><a name="winbind_idmap"></a><p class="title"><b>Figure�24.1.�Winbind Idmap</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap_winbind_no_loop.png" width="243" alt="Winbind Idmap"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653468"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have
 	different models for representing user and group information and
 	use different technologies for implementing them. This fact has
 	made it difficult to integrate the two systems in a satisfactory
 	manner.</p><p>
-<a class="indexterm" name="id2653357"></a>
-<a class="indexterm" name="id2653364"></a>
+<a class="indexterm" name="id2653484"></a>
+<a class="indexterm" name="id2653491"></a>
 	One common solution in use today has been to create
 	identically named user accounts on both the UNIX and Windows systems
 	and use the Samba suite of programs to provide file and print services
@@ -81,29 +81,29 @@
 		</p></li><li><p>Authenticating Windows NT users.
 		</p></li><li><p>Password changing for Windows NT users.
 		</p></li></ul></div><p>
-<a class="indexterm" name="id2653408"></a>
-<a class="indexterm" name="id2653415"></a>
+<a class="indexterm" name="id2653535"></a>
+<a class="indexterm" name="id2653542"></a>
 	Ideally, a prospective solution to the unified logon problem
 	would satisfy all the above components without duplication of
 	information on the UNIX machines and without creating additional
 	tasks for the system administrator when maintaining users and
 	groups on either system. The Winbind system provides a simple
 	and elegant solution to all three components of the unified logon
-	problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653431"></a>What Winbind Provides</h2></div></div></div><p>
-<a class="indexterm" name="id2653439"></a>
-<a class="indexterm" name="id2653446"></a>
-<a class="indexterm" name="id2653452"></a>
-<a class="indexterm" name="id2653459"></a>
+	problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653558"></a>What Winbind Provides</h2></div></div></div><p>
+<a class="indexterm" name="id2653566"></a>
+<a class="indexterm" name="id2653573"></a>
+<a class="indexterm" name="id2653580"></a>
+<a class="indexterm" name="id2653586"></a>
 	Winbind unifies UNIX and Windows NT account management by
 	allowing a UNIX box to become a full member of an NT domain. Once
 	this is done, the UNIX box will see NT users and groups as if
 	they were &#8220;<span class="quote">native</span>&#8221; UNIX users and groups, allowing the NT domain
 	to be used in much the same manner that NIS+ is used within
 	UNIX-only environments.</p><p>
-<a class="indexterm" name="id2653479"></a>
-<a class="indexterm" name="id2653486"></a>
-<a class="indexterm" name="id2653492"></a>
-<a class="indexterm" name="id2653499"></a>
+<a class="indexterm" name="id2653606"></a>
+<a class="indexterm" name="id2653613"></a>
+<a class="indexterm" name="id2653620"></a>
+<a class="indexterm" name="id2653626"></a>
 	The end result is that whenever a
 	program on the UNIX machine asks the operating system to look up
 	a user or group name, the query will be resolved by asking the
@@ -112,26 +112,26 @@
 	(via the NSS name resolution modules in the C library), this
 	redirection to the NT domain controller is completely
 	transparent.</p><p>
-<a class="indexterm" name="id2653516"></a>
-<a class="indexterm" name="id2653523"></a>
+<a class="indexterm" name="id2653643"></a>
+<a class="indexterm" name="id2653650"></a>
 	Users on the UNIX machine can then use NT user and group
 	names as they would &#8220;<span class="quote">native</span>&#8221; UNIX names. They can chown files
 	so they are owned by NT domain users or even login to the
 	UNIX machine and run a UNIX X-Window session as a domain user.</p><p>
-<a class="indexterm" name="id2653541"></a>
+<a class="indexterm" name="id2653668"></a>
 	The only obvious indication that Winbind is being used is
 	that user and group names take the form <code class="constant">DOMAIN\user</code> and
 	<code class="constant">DOMAIN\group</code>. This is necessary because it allows Winbind to determine
 	that redirection to a domain controller is wanted for a particular
 	lookup and which trusted domain is being referenced.</p><p>
-<a class="indexterm" name="id2653563"></a>
-<a class="indexterm" name="id2653570"></a>
+<a class="indexterm" name="id2653690"></a>
+<a class="indexterm" name="id2653697"></a>
 	Additionally, Winbind provides an authentication service that hooks into the PAM system
 	to provide authentication via an NT domain to any PAM-enabled
 	applications. This capability solves the problem of synchronizing
 	passwords between systems, since all passwords are stored in a single
-	location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653584"></a>Target Uses</h3></div></div></div><p>
-<a class="indexterm" name="id2653592"></a>
+	location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653711"></a>Target Uses</h3></div></div></div><p>
+<a class="indexterm" name="id2653719"></a>
 		Winbind is targeted at organizations that have an
 		existing NT-based domain infrastructure into which they wish
 		to put UNIX workstations or servers. Winbind will allow these
@@ -139,40 +139,40 @@
 		maintain a separate account infrastructure. This greatly
 		simplifies the administrative overhead of deploying UNIX
 		workstations into an NT-based organization.</p><p>
-<a class="indexterm" name="id2653609"></a>
-<a class="indexterm" name="id2653615"></a>
+<a class="indexterm" name="id2653736"></a>
+<a class="indexterm" name="id2653742"></a>
 		Another interesting way in which we expect Winbind to
 		be used is as a central part of UNIX-based appliances. Appliances
 		that provide file and print services to Microsoft-based networks
 		will be able to use Winbind to provide seamless integration of
-		the appliance into the domain.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653629"></a>Handling of Foreign SIDs</h3></div></div></div><p>
-<a class="indexterm" name="id2653637"></a>
+		the appliance into the domain.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653756"></a>Handling of Foreign SIDs</h3></div></div></div><p>
+<a class="indexterm" name="id2653764"></a>
 	The term <span class="emphasis"><em>foreign SID</em></span> is often met with the reaction that it
 	is not relevant to a particular environment. The following documents an interchange
 	that took place on the Samba mailing list. It is a good example of the confusion
 	often expressed regarding the use of winbind.
 	</p><p>
-<a class="indexterm" name="id2653655"></a>
+<a class="indexterm" name="id2653782"></a>
 	Fact: Winbind is needed to handle users who use workstations that are NOT part
 	of the local domain.
 	</p><p>
-<a class="indexterm" name="id2653667"></a>
+<a class="indexterm" name="id2653794"></a>
 	Response: &#8220;<span class="quote">Why? I've used Samba with workstations that are not part of my domains
 	lots of times without using winbind. I thought winbind was for using Samba as a member server
 	in a domain controlled by another Samba/Windows PDC.</span>&#8221;
 	</p><p>
-<a class="indexterm" name="id2653684"></a>
-<a class="indexterm" name="id2653691"></a>
-<a class="indexterm" name="id2653698"></a>
+<a class="indexterm" name="id2653812"></a>
+<a class="indexterm" name="id2653818"></a>
+<a class="indexterm" name="id2653825"></a>
 	If the Samba server will be accessed from a domain other than the local Samba domain, or
 	if there will be access from machines that are not local domain members, winbind will
 	permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity
 	of the foreign user separate from users that are members of the Samba domain.
 	</p><p>
-<a class="indexterm" name="id2653714"></a>
-<a class="indexterm" name="id2653720"></a>
-<a class="indexterm" name="id2653727"></a>
-<a class="indexterm" name="id2653734"></a>
+<a class="indexterm" name="id2653841"></a>
+<a class="indexterm" name="id2653847"></a>
+<a class="indexterm" name="id2653854"></a>
+<a class="indexterm" name="id2653861"></a>
 	This means that winbind is eminently useful in cases where a single
 	Samba PDC on a local network is combined with both domain member and domain non-member workstations.
 	If winbind is not used, the user george on a Windows workstation that is not a domain
@@ -181,49 +181,49 @@
 	is that the local user george will be treated as the account DOMAIN\george and the
 	foreign (non-member of the domain) account will be treated as MACHINE\george because
 	each has a different SID.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653755"></a>How Winbind Works</h2></div></div></div><p>
-<a class="indexterm" name="id2653763"></a>
-<a class="indexterm" name="id2653770"></a>
-<a class="indexterm" name="id2653777"></a>
-<a class="indexterm" name="id2653783"></a>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653882"></a>How Winbind Works</h2></div></div></div><p>
+<a class="indexterm" name="id2653890"></a>
+<a class="indexterm" name="id2653897"></a>
+<a class="indexterm" name="id2653904"></a>
+<a class="indexterm" name="id2653910"></a>
 	The Winbind system is designed around a client/server
 	architecture. A long-running <code class="literal">winbindd</code> daemon
 	listens on a UNIX domain socket waiting for requests
 	to arrive. These requests are generated by the NSS and PAM
 	clients and are processed sequentially.</p><p>The technologies used to implement Winbind are described
-	in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653805"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>
-<a class="indexterm" name="id2653814"></a>
-<a class="indexterm" name="id2653823"></a>
-<a class="indexterm" name="id2653830"></a>
-<a class="indexterm" name="id2653837"></a>
-<a class="indexterm" name="id2653844"></a>
+	in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653932"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>
+<a class="indexterm" name="id2653941"></a>
+<a class="indexterm" name="id2653950"></a>
+<a class="indexterm" name="id2653957"></a>
+<a class="indexterm" name="id2653964"></a>
+<a class="indexterm" name="id2653971"></a>
 		Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of
 		the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations
 		between Windows NT machines, including remote management, user authentication, and print spooling. Although
 		initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in
 		Samba, it has also yielded a body of code that can be used for other purposes.
 		</p><p>
-<a class="indexterm" name="id2653863"></a>
-<a class="indexterm" name="id2653869"></a>
-<a class="indexterm" name="id2653876"></a>
+<a class="indexterm" name="id2653990"></a>
+<a class="indexterm" name="id2653996"></a>
+<a class="indexterm" name="id2654004"></a>
 		Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about
 		individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user
 		passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account
 		information onto UNIX user and group names.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653892"></a>Microsoft Active Directory Services</h3></div></div></div><p>
-<a class="indexterm" name="id2653900"></a>
-<a class="indexterm" name="id2653907"></a>
-<a class="indexterm" name="id2653914"></a>
-<a class="indexterm" name="id2653921"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654026"></a>Microsoft Active Directory Services</h3></div></div></div><p>
+<a class="indexterm" name="id2654034"></a>
+<a class="indexterm" name="id2654040"></a>
+<a class="indexterm" name="id2654047"></a>
+<a class="indexterm" name="id2654054"></a>
 		Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its &#8220;<span class="quote">native
 		mode</span>&#8221; protocols rather than the NT4 RPC services.  Using LDAP and Kerberos, a domain member running
 		Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing
 		provide a much more efficient and effective Winbind implementation.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653940"></a>Name Service Switch</h3></div></div></div><p>
-<a class="indexterm" name="id2653948"></a>
-<a class="indexterm" name="id2653954"></a>
-<a class="indexterm" name="id2653961"></a>
-<a class="indexterm" name="id2653968"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654073"></a>Name Service Switch</h3></div></div></div><p>
+<a class="indexterm" name="id2654081"></a>
+<a class="indexterm" name="id2654088"></a>
+<a class="indexterm" name="id2654095"></a>
+<a class="indexterm" name="id2654101"></a>
 		The NSS is a feature that is present in many UNIX operating systems. It allows system
 		information such as hostnames, mail aliases, and user information
 		to be resolved from different sources. For example, a standalone
@@ -232,20 +232,20 @@
 		may first attempt to resolve system information from local files,
 		and then consult an NIS database for user information or a DNS server
 		for hostname information.</p><p>
-<a class="indexterm" name="id2653986"></a>
-<a class="indexterm" name="id2653993"></a>
-<a class="indexterm" name="id2654000"></a>
-<a class="indexterm" name="id2654007"></a>
-<a class="indexterm" name="id2654014"></a>
+<a class="indexterm" name="id2654120"></a>
+<a class="indexterm" name="id2654126"></a>
+<a class="indexterm" name="id2654133"></a>
+<a class="indexterm" name="id2654140"></a>
+<a class="indexterm" name="id2654147"></a>
 		The NSS application programming interface allows Winbind to present itself as a source of system
 		information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained
 		from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX
 		library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and
 		groups in an NT domain plus any trusted domain as though they were local users and groups.
 		</p><p>
-<a class="indexterm" name="id2654033"></a>
-<a class="indexterm" name="id2654039"></a>
-<a class="indexterm" name="id2654046"></a>
+<a class="indexterm" name="id2654166"></a>
+<a class="indexterm" name="id2654172"></a>
+<a class="indexterm" name="id2654179"></a>
 		The primary control file for NSS is <code class="filename">/etc/nsswitch.conf</code>.  When a UNIX application
 		makes a request to do a lookup, the C library looks in <code class="filename">/etc/nsswitch.conf</code> for a line that
 		matches the service type being requested; for example, the &#8220;<span class="quote">passwd</span>&#8221; service type is used when
@@ -254,46 +254,46 @@
 </p><pre class="screen">
 passwd: files example
 </pre><p>
-<a class="indexterm" name="id2654082"></a>
-<a class="indexterm" name="id2654089"></a>
-<a class="indexterm" name="id2654096"></a>
+<a class="indexterm" name="id2654215"></a>
+<a class="indexterm" name="id2654222"></a>
+<a class="indexterm" name="id2654229"></a>
 		then the C library will first load a module called <code class="filename">/lib/libnss_files.so</code> followed
 		by the module <code class="filename">/lib/libnss_example.so</code>. The C library will dynamically load each of these
 		modules in turn and call resolver functions within the modules to try to resolve the request. Once the request
 		is resolved, the C library returns the result to the application.
 		</p><p>
-<a class="indexterm" name="id2654123"></a>
-<a class="indexterm" name="id2654130"></a>
-<a class="indexterm" name="id2654137"></a>
+<a class="indexterm" name="id2654257"></a>
+<a class="indexterm" name="id2654263"></a>
+<a class="indexterm" name="id2654270"></a>
 		This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs
 		to be done is to put <code class="filename">libnss_winbind.so</code> in <code class="filename">/lib/</code> then add
 		&#8220;<span class="quote">winbind</span>&#8221; into <code class="filename">/etc/nsswitch.conf</code> at the appropriate place. The C library
 		will then call Winbind to resolve user and group names.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654172"></a>Pluggable Authentication Modules</h3></div></div></div><p>
-<a class="indexterm" name="id2654180"></a>
-<a class="indexterm" name="id2654187"></a>
-<a class="indexterm" name="id2654194"></a>
-<a class="indexterm" name="id2654201"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654305"></a>Pluggable Authentication Modules</h3></div></div></div><p>
+<a class="indexterm" name="id2654313"></a>
+<a class="indexterm" name="id2654320"></a>
+<a class="indexterm" name="id2654327"></a>
+<a class="indexterm" name="id2654334"></a>
 		PAMs provide a system for abstracting authentication and authorization technologies. With a PAM
 		module, it is possible to specify different authentication methods for different system applications without
 		having to recompile these applications. PAM is also useful for implementing a particular policy for
 		authorization. For example, a system administrator may only allow console logins from users stored in the
 		local password file but only allow users resolved from an NIS database to log in over the network.
 		</p><p>
-<a class="indexterm" name="id2654220"></a>
-<a class="indexterm" name="id2654226"></a>
-<a class="indexterm" name="id2654233"></a>
-<a class="indexterm" name="id2654240"></a>
-<a class="indexterm" name="id2654247"></a>
+<a class="indexterm" name="id2654353"></a>
+<a class="indexterm" name="id2654359"></a>
+<a class="indexterm" name="id2654366"></a>
+<a class="indexterm" name="id2654373"></a>
+<a class="indexterm" name="id2654380"></a>
 		Winbind uses the authentication management and password management PAM interface to integrate Windows
 		NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated
 		against a suitable PDC.  These users can also change their passwords and have this change take effect directly
 		on the PDC.
 		</p><p>
-<a class="indexterm" name="id2654262"></a>
-<a class="indexterm" name="id2654269"></a>
-<a class="indexterm" name="id2654276"></a>
-<a class="indexterm" name="id2654283"></a>
+<a class="indexterm" name="id2654396"></a>
+<a class="indexterm" name="id2654402"></a>
+<a class="indexterm" name="id2654409"></a>
+<a class="indexterm" name="id2654416"></a>
 		PAM is configured by providing control files in the directory <code class="filename">/etc/pam.d/</code> for
 		each of the services that require authentication. When an authentication request is made by an application,
 		the PAM code in the C library looks up this control file to determine what modules to load to do the
@@ -301,10 +301,10 @@ passwd: files example
 		very easy: simply copy the <code class="filename">pam_winbind.so</code> module to <code class="filename">/lib/security/</code>,
 		and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM
 		documentation in <a class="link" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication">PAM-Based Distributed Authentication</a>, for more information.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654327"></a>User and Group ID Allocation</h3></div></div></div><p>
-<a class="indexterm" name="id2654335"></a>
-<a class="indexterm" name="id2654341"></a>
-<a class="indexterm" name="id2654348"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654460"></a>User and Group ID Allocation</h3></div></div></div><p>
+<a class="indexterm" name="id2654468"></a>
+<a class="indexterm" name="id2654475"></a>
+<a class="indexterm" name="id2654482"></a>
 		When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier
 		(RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and
 		the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa.
@@ -313,18 +313,18 @@ passwd: files example
 		allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind
 		will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.
 		</p><p>
-<a class="indexterm" name="id2654371"></a>
-<a class="indexterm" name="id2654378"></a>
-<a class="indexterm" name="id2654384"></a>
-<a class="indexterm" name="id2654391"></a>
+<a class="indexterm" name="id2654504"></a>
+<a class="indexterm" name="id2654511"></a>
+<a class="indexterm" name="id2654518"></a>
+<a class="indexterm" name="id2654524"></a>
 		The results of this mapping are stored persistently in an ID mapping database held in a tdb database.
 		This ensures that RIDs are mapped to UNIX IDs in a consistent way.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654403"></a>Result Caching</h3></div></div></div><p>
-<a class="indexterm" name="id2654411"></a>
-<a class="indexterm" name="id2654417"></a>
-<a class="indexterm" name="id2654424"></a>
-<a class="indexterm" name="id2654431"></a>
-<a class="indexterm" name="id2654437"></a>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654536"></a>Result Caching</h3></div></div></div><p>
+<a class="indexterm" name="id2654544"></a>
+<a class="indexterm" name="id2654550"></a>
+<a class="indexterm" name="id2654557"></a>
+<a class="indexterm" name="id2654564"></a>
+<a class="indexterm" name="id2654571"></a>
 		An active directory system can generate a lot of user and group name lookups. To reduce the network
 		cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain
 		controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number
@@ -332,66 +332,66 @@ passwd: files example
 		information is modified. If a cached entry has expired, the sequence number is requested from the PDC and
 		compared against the sequence number of the cached entry.  If the sequence numbers do not match, then the
 		cached information is discarded and up-to-date information is requested directly from the PDC.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2654460"></a>Installation and Configuration</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654466"></a>Introduction</h3></div></div></div><p>
-<a class="indexterm" name="id2654474"></a>
-<a class="indexterm" name="id2654480"></a>
-<a class="indexterm" name="id2654487"></a>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2654593"></a>Installation and Configuration</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654599"></a>Introduction</h3></div></div></div><p>
+<a class="indexterm" name="id2654607"></a>
+<a class="indexterm" name="id2654614"></a>
+<a class="indexterm" name="id2654620"></a>
 This section describes the procedures used to get Winbind up and running. Winbind is capable of providing
 access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular
 services, such as telnet and ftp, as well for Samba services.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 	<span class="emphasis"><em>Why should I do this?</em></span>
 	</p><p>
-<a class="indexterm" name="id2654513"></a>
-<a class="indexterm" name="id2654520"></a>
-<a class="indexterm" name="id2654527"></a>
-<a class="indexterm" name="id2654534"></a>
+<a class="indexterm" name="id2654646"></a>
+<a class="indexterm" name="id2654653"></a>
+<a class="indexterm" name="id2654660"></a>
+<a class="indexterm" name="id2654667"></a>
 This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC
 for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on
 the Samba server.
 	</p></li><li><p>
 	<span class="emphasis"><em>Who should be reading this document?</em></span>
 	</p><p>
-<a class="indexterm" name="id2654558"></a>
-<a class="indexterm" name="id2654565"></a>
+<a class="indexterm" name="id2654692"></a>
+<a class="indexterm" name="id2654698"></a>
 This document is designed for system administrators. If you are implementing Samba on a file server and wish
 to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document
 is for you.
-	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654580"></a>Requirements</h3></div></div></div><p>
-<a class="indexterm" name="id2654588"></a>
-<a class="indexterm" name="id2654594"></a>
-<a class="indexterm" name="id2654601"></a>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654713"></a>Requirements</h3></div></div></div><p>
+<a class="indexterm" name="id2654721"></a>
+<a class="indexterm" name="id2654728"></a>
+<a class="indexterm" name="id2654735"></a>
 If you have a Samba configuration file that you are currently using, <span class="emphasis"><em>BACK IT UP!</em></span>
 If your system already uses PAM, <span class="emphasis"><em>back up the <code class="filename">/etc/pam.d</code> directory
 contents!</em></span> If you haven't already made a boot disk, <span class="emphasis"><em>MAKE ONE NOW!</em></span>
 </p><p>
-<a class="indexterm" name="id2654631"></a>
-<a class="indexterm" name="id2654638"></a>
-<a class="indexterm" name="id2654645"></a>
+<a class="indexterm" name="id2654764"></a>
+<a class="indexterm" name="id2654771"></a>
+<a class="indexterm" name="id2654778"></a>
 Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
 why you want to be able to boot back into your machine in single-user mode and restore your
 <code class="filename">/etc/pam.d</code> to the original state it was in if you get frustrated with the
 way things are going.
 </p><p>
-<a class="indexterm" name="id2654666"></a>
-<a class="indexterm" name="id2654672"></a>
+<a class="indexterm" name="id2654799"></a>
+<a class="indexterm" name="id2654806"></a>
 The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <a class="ulink" href="http://samba.org/" target="_top">main Samba Web page</a>, or better yet, your closest Samba mirror site for
 instructions on downloading the source code.
 </p><p>
-<a class="indexterm" name="id2654692"></a>
-<a class="indexterm" name="id2654699"></a>
-<a class="indexterm" name="id2654706"></a>
-<a class="indexterm" name="id2654712"></a>
+<a class="indexterm" name="id2654825"></a>
+<a class="indexterm" name="id2654832"></a>
+<a class="indexterm" name="id2654839"></a>
+<a class="indexterm" name="id2654846"></a>
 To allow domain users the ability to access Samba shares and files, as well as potentially other services
 provided by your Samba machine, PAM must be set up properly on your
 machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
 on your system. Please refer to the PAM Web site <a class="ulink" href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">http://www.kernel.org/pub/linux/libs/pam/</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654732"></a>Testing Things Out</h3></div></div></div><p>
-<a class="indexterm" name="id2654740"></a>
-<a class="indexterm" name="id2654747"></a>
-<a class="indexterm" name="id2654754"></a>
-<a class="indexterm" name="id2654760"></a>
-<a class="indexterm" name="id2654767"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654865"></a>Testing Things Out</h3></div></div></div><p>
+<a class="indexterm" name="id2654873"></a>
+<a class="indexterm" name="id2654880"></a>
+<a class="indexterm" name="id2654887"></a>
+<a class="indexterm" name="id2654894"></a>
+<a class="indexterm" name="id2654900"></a>
 Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
 Kill off all <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> processes that may be running. To use PAM,
 make sure that you have the standard PAM package that supplies the <code class="filename">/etc/pam.d</code>
@@ -399,11 +399,11 @@ directory structure, including the PAM modules that are used by PAM-aware servic
 and the <code class="filename">/usr/doc</code> and <code class="filename">/usr/man</code> entries for PAM. Winbind is built
 better in Samba if the pam-devel package is also installed. This package includes the header files
 needed to compile PAM-aware applications.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2654819"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>
-<a class="indexterm" name="id2654834"></a>
-<a class="indexterm" name="id2654840"></a>
-<a class="indexterm" name="id2654847"></a>
-<a class="indexterm" name="id2654854"></a>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2654952"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>
+<a class="indexterm" name="id2654967"></a>
+<a class="indexterm" name="id2654973"></a>
+<a class="indexterm" name="id2654980"></a>
+<a class="indexterm" name="id2654987"></a>
 PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
 the <code class="filename">pam-devel</code> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3
 may auto-install the Winbind files into their correct locations on your system, so before you get too far down
@@ -413,7 +413,7 @@ necessary. You may only need to configure
 </p><p>
 The libraries needed to run the <span class="application">winbindd</span> daemon through nsswitch need to be copied to their proper locations:
 </p><p>
-<a class="indexterm" name="id2654893"></a>
+<a class="indexterm" name="id2655027"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/libnss_winbind.so /lib</code></strong>
 </pre><p>
@@ -422,14 +422,14 @@ I also found it necessary to make the following symbolic link:
 </p><p>
 <code class="prompt">root# </code> <strong class="userinput"><code>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</code></strong>
 </p><p>And, in the case of Sun Solaris:
-<a class="indexterm" name="id2654941"></a>
+<a class="indexterm" name="id2655074"></a>
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</code></strong>
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</code></strong>
 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2654990"></a>
+<a class="indexterm" name="id2655124"></a>
 As root, edit <code class="filename">/etc/nsswitch.conf</code> to allow user and group entries to be visible from the
 <span class="application">winbindd</span> daemon. My <code class="filename">/etc/nsswitch.conf</code> file looked like this after editing:
 </p><pre class="programlisting">
@@ -437,11 +437,11 @@ passwd:     files winbind
 shadow:     files
 group:      files winbind
 </pre><p>
-<a class="indexterm" name="id2655026"></a>
-<a class="indexterm" name="id2655033"></a>
-<a class="indexterm" name="id2655040"></a>
-<a class="indexterm" name="id2655047"></a>
-<a class="indexterm" name="id2655054"></a>
+<a class="indexterm" name="id2655160"></a>
+<a class="indexterm" name="id2655166"></a>
+<a class="indexterm" name="id2655173"></a>
+<a class="indexterm" name="id2655180"></a>
+<a class="indexterm" name="id2655187"></a>
 The libraries needed by the <code class="literal">winbindd</code> daemon will be automatically
 entered into the <code class="literal">ldconfig</code> cache the next time
 your system reboots, but it is faster (and you do not need to reboot) if you do it manually:
@@ -453,11 +453,11 @@ search path that is used by the dynamic link loader. The use of the <code class=
 filters the output of the <code class="literal">ldconfig</code> command so that we may see proof that
 this library is indeed recognized by the dynamic link loader.
 </p><p>
-<a class="indexterm" name="id2655117"></a>
-<a class="indexterm" name="id2655124"></a>
-<a class="indexterm" name="id2655131"></a>
-<a class="indexterm" name="id2655138"></a>
-<a class="indexterm" name="id2655145"></a>
+<a class="indexterm" name="id2655251"></a>
+<a class="indexterm" name="id2655258"></a>
+<a class="indexterm" name="id2655264"></a>
+<a class="indexterm" name="id2655271"></a>
+<a class="indexterm" name="id2655278"></a>
 The Sun Solaris dynamic link loader management tool is called <code class="literal">crle</code>. The
 use of this tool is necessary to instruct the dynamic link loader to search directories that
 contain library files that were not supplied as part of the original operating system platform.
@@ -480,13 +480,13 @@ Command line:
 </pre><p>
 From this it is apparent that the <code class="filename">/usr/local/lib</code> directory is included
 in the search dynamic link libraries in order to satisfy object module dependencies.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655217"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>
-<a class="indexterm" name="id2655229"></a>
-<a class="indexterm" name="id2655236"></a>
-<a class="indexterm" name="id2655242"></a>
-<a class="indexterm" name="id2655249"></a>
-<a class="indexterm" name="id2655256"></a>
-<a class="indexterm" name="id2655264"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655350"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>
+<a class="indexterm" name="id2655362"></a>
+<a class="indexterm" name="id2655369"></a>
+<a class="indexterm" name="id2655376"></a>
+<a class="indexterm" name="id2655383"></a>
+<a class="indexterm" name="id2655390"></a>
+<a class="indexterm" name="id2655397"></a>
 The Winbind AIX identification module gets built as <code class="filename">libnss_winbind.so</code> in the
 nsswitch directory of the Samba source. This file can be copied to <code class="filename">/usr/lib/security</code>,
 and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
@@ -504,50 +504,50 @@ describes the <a class="ulink" href="http://publibn.boulder.ibm.com/doc_link/en_
 Loadable Authentication Module Programming Interface</a> for AIX. Further information on administering the modules
 can be found in the <a class="ulink" href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm" target="_top">System
 Management Guide: Operating System and Devices.</a>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655330"></a>Configure smb.conf</h4></div></div></div><p>
-<a class="indexterm" name="id2655338"></a>
-<a class="indexterm" name="id2655345"></a>
-<a class="indexterm" name="id2655352"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655464"></a>Configure smb.conf</h4></div></div></div><p>
+<a class="indexterm" name="id2655472"></a>
+<a class="indexterm" name="id2655478"></a>
+<a class="indexterm" name="id2655485"></a>
 Several parameters are needed in the <code class="filename">smb.conf</code> file to control the behavior of <span class="application">winbindd</span>. These
 are described in more detail in the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> man page. My <code class="filename">smb.conf</code> file, as shown in <a class="link" href="winbind.html#winbindcfg" title="Example�24.1.�smb.conf for Winbind Setup">the smb.conf for Winbind Setup</a>, was modified to include the necessary entries in the [global] section.
-</p><div class="example"><a name="winbindcfg"></a><p class="title"><b>Example�24.1.�smb.conf for Winbind Setup</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td>#  separate domain and username with '\', like DOMAIN\username</td></tr><tr><td><a class="indexterm" name="id2655425"></a><em class="parameter"><code>winbind separator = \</code></em></td></tr><tr><td>#  use uids from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2655441"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td>#  use gids from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2655457"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td>#  allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2655473"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2655485"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td>#  give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><a class="indexterm" name="id2655501"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2655514"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655528"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>
-<a class="indexterm" name="id2655536"></a>
-<a class="indexterm" name="id2655543"></a>
-<a class="indexterm" name="id2655549"></a>
+</p><div class="example"><a name="winbindcfg"></a><p class="title"><b>Example�24.1.�smb.conf for Winbind Setup</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td>#  separate domain and username with '\', like DOMAIN\username</td></tr><tr><td><a class="indexterm" name="id2655559"></a><em class="parameter"><code>winbind separator = \</code></em></td></tr><tr><td>#  use uids from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2655575"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td>#  use gids from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2655591"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td>#  allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2655606"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2655618"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td>#  give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><a class="indexterm" name="id2655635"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2655647"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655661"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>
+<a class="indexterm" name="id2655669"></a>
+<a class="indexterm" name="id2655676"></a>
+<a class="indexterm" name="id2655683"></a>
 All machines that will participate in domain security should be members of
 the domain. This applies also to the PDC and all BDCs.
 </p><p>
-<a class="indexterm" name="id2655561"></a>
-<a class="indexterm" name="id2655568"></a>
-<a class="indexterm" name="id2655575"></a>
-<a class="indexterm" name="id2655586"></a>
-<a class="indexterm" name="id2655593"></a>
-<a class="indexterm" name="id2655599"></a>
-<a class="indexterm" name="id2655606"></a>
-<a class="indexterm" name="id2655613"></a>
-<a class="indexterm" name="id2655620"></a>
+<a class="indexterm" name="id2655695"></a>
+<a class="indexterm" name="id2655702"></a>
+<a class="indexterm" name="id2655708"></a>
+<a class="indexterm" name="id2655719"></a>
+<a class="indexterm" name="id2655726"></a>
+<a class="indexterm" name="id2655733"></a>
+<a class="indexterm" name="id2655740"></a>
+<a class="indexterm" name="id2655746"></a>
+<a class="indexterm" name="id2655753"></a>
 The process of joining a domain requires the use of the <code class="literal">net rpc join</code>
 command. This process communicates with the domain controller it will register with
 (usually the PDC) via MS DCE RPC. This means, of course, that the <code class="literal">smbd</code>
 process must be running on the target domain controller. It is therefore necessary to temporarily
 start Samba on a PDC so that it can join its own domain.
 </p><p>
-<a class="indexterm" name="id2655648"></a>
-<a class="indexterm" name="id2655654"></a>
-<a class="indexterm" name="id2655661"></a>
+<a class="indexterm" name="id2655781"></a>
+<a class="indexterm" name="id2655788"></a>
+<a class="indexterm" name="id2655795"></a>
 Enter the following command to make the Samba server join the domain, where <em class="replaceable"><code>PDC</code></em> is
 the name of your PDC and <em class="replaceable"><code>Administrator</code></em> is a domain user who has administrative
 privileges in the domain.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2655683"></a>
-<a class="indexterm" name="id2655690"></a>
-<a class="indexterm" name="id2655696"></a>
-<a class="indexterm" name="id2655703"></a>
+<a class="indexterm" name="id2655816"></a>
+<a class="indexterm" name="id2655823"></a>
+<a class="indexterm" name="id2655830"></a>
+<a class="indexterm" name="id2655836"></a>
 Before attempting to join a machine to the domain, verify that Samba is running
 on the target domain controller (usually PDC) and that it is capable of being reached via ports
 137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).
 </p></div><p>
-<a class="indexterm" name="id2655717"></a>
+<a class="indexterm" name="id2655851"></a>
 The use of the <code class="literal">net rpc join</code> facility is shown here:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</code></strong>
@@ -555,10 +555,10 @@ The use of the <code class="literal">net rpc join</code> facility is shown here:
 The proper response to the command should be &#8220;<span class="quote">Joined the domain
 <em class="replaceable"><code>DOMAIN</code></em></span>&#8221; where <em class="replaceable"><code>DOMAIN</code></em>
 is your domain name.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655765"></a>Starting and Testing the <code class="literal">winbindd</code> Daemon</h4></div></div></div><p>
-<a class="indexterm" name="id2655779"></a>
-<a class="indexterm" name="id2655786"></a>
-<a class="indexterm" name="id2655793"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655899"></a>Starting and Testing the <code class="literal">winbindd</code> Daemon</h4></div></div></div><p>
+<a class="indexterm" name="id2655913"></a>
+<a class="indexterm" name="id2655920"></a>
+<a class="indexterm" name="id2655926"></a>
 Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when
 the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up
 Winbind services, enter the following command as root:
@@ -567,27 +567,27 @@ Winbind services, enter the following command as root:
 </pre><p>
 Use the appropriate path to the location of the <code class="literal">winbindd</code> executable file.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2655832"></a>
-<a class="indexterm" name="id2655839"></a>
+<a class="indexterm" name="id2655966"></a>
+<a class="indexterm" name="id2655972"></a>
 The command to start up Winbind services assumes that Samba has been installed in the
 <code class="filename">/usr/local/samba</code> directory tree. You may need to search for the location of Samba files
 if this is not the location of <code class="literal">winbindd</code> on your system.
 </p></div><p>
-<a class="indexterm" name="id2655865"></a>
-<a class="indexterm" name="id2655872"></a>
+<a class="indexterm" name="id2655998"></a>
+<a class="indexterm" name="id2656005"></a>
 I'm always paranoid and like to make sure the daemon is really running.
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>ps -ae | grep winbindd</code></strong>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2655899"></a>
+<a class="indexterm" name="id2656033"></a>
 This command should produce output like the following if the daemon is running.
 </p><pre class="screen">
 3025 ?        00:00:00 winbindd
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2655917"></a>
-<a class="indexterm" name="id2655924"></a>
+<a class="indexterm" name="id2656050"></a>
+<a class="indexterm" name="id2656057"></a>
 Now, for the real test, try to get some information about the users on your PDC:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -u</code></strong>
@@ -605,8 +605,8 @@ CEO\TsInternetUser
 Obviously, I have named my domain &#8220;<span class="quote">CEO</span>&#8221; and my <a class="link" href="smb.conf.5.html#WINBINDSEPARATOR" target="_top">winbind separator</a> is
 &#8220;<span class="quote">\</span>&#8221;.
 </p><p>
-<a class="indexterm" name="id2655982"></a>
-<a class="indexterm" name="id2655988"></a>
+<a class="indexterm" name="id2656115"></a>
+<a class="indexterm" name="id2656122"></a>
 You can do the same sort of thing to get group information from the PDC:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -g</code></strong>
@@ -620,13 +620,13 @@ CEO\Schema Admins
 CEO\Enterprise Admins
 CEO\Group Policy Creator Owners
 </pre><p>
-<a class="indexterm" name="id2656018"></a>
-<a class="indexterm" name="id2656025"></a>
-<a class="indexterm" name="id2656032"></a>
-<a class="indexterm" name="id2656038"></a>
-<a class="indexterm" name="id2656045"></a>
-<a class="indexterm" name="id2656051"></a>
-<a class="indexterm" name="id2656058"></a>
+<a class="indexterm" name="id2656152"></a>
+<a class="indexterm" name="id2656158"></a>
+<a class="indexterm" name="id2656165"></a>
+<a class="indexterm" name="id2656172"></a>
+<a class="indexterm" name="id2656178"></a>
+<a class="indexterm" name="id2656185"></a>
+<a class="indexterm" name="id2656191"></a>
 The function <code class="literal">getent</code> can now be used to get unified lists of both local and PDC users and
 groups. Try the following command:
 </p><pre class="screen">
@@ -640,16 +640,16 @@ The same thing can be done for groups with the command:
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>getent group</code></strong>
 </pre><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656120"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656126"></a>Linux</h5></div></div></div><p>
-<a class="indexterm" name="id2656134"></a>
-<a class="indexterm" name="id2656141"></a>
-<a class="indexterm" name="id2656148"></a>
-<a class="indexterm" name="id2656155"></a>
-<a class="indexterm" name="id2656162"></a>
-<a class="indexterm" name="id2656169"></a>
-<a class="indexterm" name="id2656176"></a>
-<a class="indexterm" name="id2656181"></a>
-<a class="indexterm" name="id2656187"></a>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656253"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656259"></a>Linux</h5></div></div></div><p>
+<a class="indexterm" name="id2656267"></a>
+<a class="indexterm" name="id2656274"></a>
+<a class="indexterm" name="id2656281"></a>
+<a class="indexterm" name="id2656287"></a>
+<a class="indexterm" name="id2656294"></a>
+<a class="indexterm" name="id2656301"></a>
+<a class="indexterm" name="id2656308"></a>
+<a class="indexterm" name="id2656314"></a>
+<a class="indexterm" name="id2656319"></a>
 The <span class="application">winbindd</span> daemon needs to start up after the <span class="application">smbd</span> and <span class="application">nmbd</span> daemons are running.  To accomplish this
 task, you need to modify the startup scripts of your system.  They are located at
 <code class="filename">/etc/init.d/smb</code> in Red Hat Linux and in <code class="filename">/etc/init.d/samba</code> in Debian
@@ -710,16 +710,16 @@ stop() {
         echo ""
         return $RETVAL
 }
-</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656332"></a>Solaris</h5></div></div></div><p>
+</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656465"></a>Solaris</h5></div></div></div><p>
 Winbind does not work on Solaris 9; see <a class="link" href="Portability.html#winbind-solaris9" title="Winbind on Solaris 9">Winbind on Solaris 9 section</a>
 for details.
 </p><p>
-<a class="indexterm" name="id2656353"></a>
-<a class="indexterm" name="id2656360"></a>
-<a class="indexterm" name="id2656367"></a>
-<a class="indexterm" name="id2656374"></a>
-<a class="indexterm" name="id2656380"></a>
-<a class="indexterm" name="id2656387"></a>
+<a class="indexterm" name="id2656486"></a>
+<a class="indexterm" name="id2656493"></a>
+<a class="indexterm" name="id2656500"></a>
+<a class="indexterm" name="id2656507"></a>
+<a class="indexterm" name="id2656514"></a>
+<a class="indexterm" name="id2656521"></a>
 On Solaris, you need to modify the <code class="filename">/etc/init.d/samba.server</code> startup script. It
 usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
 <code class="filename">/usr/local/samba/bin</code>, the file could contains something like this:
@@ -780,28 +780,28 @@ in the script above with:
 </p><pre class="programlisting">
 /usr/local/samba/sbin/winbindd -D
 </pre><p>
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656476"></a>Restarting</h5></div></div></div><p>
-<a class="indexterm" name="id2656484"></a>
-<a class="indexterm" name="id2656491"></a>
+</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656610"></a>Restarting</h5></div></div></div><p>
+<a class="indexterm" name="id2656617"></a>
+<a class="indexterm" name="id2656624"></a>
 If you restart the <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> daemons at this point, you
 should be able to connect to the Samba server as a domain member just as
 if you were a local user.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656521"></a>Configure Winbind and PAM</h4></div></div></div><p>
-<a class="indexterm" name="id2656529"></a>
-<a class="indexterm" name="id2656536"></a>
-<a class="indexterm" name="id2656543"></a>
-<a class="indexterm" name="id2656549"></a>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656654"></a>Configure Winbind and PAM</h4></div></div></div><p>
+<a class="indexterm" name="id2656662"></a>
+<a class="indexterm" name="id2656669"></a>
+<a class="indexterm" name="id2656676"></a>
+<a class="indexterm" name="id2656683"></a>
 If you have made it this far, you know that <code class="literal">winbindd</code> and Samba are working together. If you
 want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files
 need to be altered in this step. (Did you remember to make backups of your original
 <code class="filename">/etc/pam.d</code> files? If not, do it now.)
 </p><p>
-<a class="indexterm" name="id2656576"></a>
-<a class="indexterm" name="id2656583"></a>
-<a class="indexterm" name="id2656590"></a>
-<a class="indexterm" name="id2656597"></a>
-<a class="indexterm" name="id2656604"></a>
-<a class="indexterm" name="id2656610"></a>
+<a class="indexterm" name="id2656710"></a>
+<a class="indexterm" name="id2656716"></a>
+<a class="indexterm" name="id2656723"></a>
+<a class="indexterm" name="id2656730"></a>
+<a class="indexterm" name="id2656737"></a>
+<a class="indexterm" name="id2656744"></a>
 You will need a PAM module to use winbindd with these other services. This module will be compiled in the
 <code class="filename">../source/nsswitch</code> directory by invoking the command:
 </p><pre class="screen">
@@ -814,22 +814,22 @@ copied to the location of your other PAM security modules. On my Red Hat system,
 </p><pre class="screen">
 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</code></strong>
 </pre><p>
-</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656687"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>
-<a class="indexterm" name="id2656695"></a>
+</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656821"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>
+<a class="indexterm" name="id2656829"></a>
 The <code class="filename">/etc/pam.d/samba</code> file does not need to be changed. I just left this file as it was:
 </p><pre class="programlisting">
 auth    required  /lib/security/pam_stack.so service=system-auth
 account required  /lib/security/pam_stack.so service=system-auth
 </pre><p>
-<a class="indexterm" name="id2656720"></a>
-<a class="indexterm" name="id2656727"></a>
-<a class="indexterm" name="id2656734"></a>
-<a class="indexterm" name="id2656740"></a>
-<a class="indexterm" name="id2656747"></a>
-<a class="indexterm" name="id2656754"></a>
-<a class="indexterm" name="id2656761"></a>
-<a class="indexterm" name="id2656768"></a>
-<a class="indexterm" name="id2656775"></a>
+<a class="indexterm" name="id2656853"></a>
+<a class="indexterm" name="id2656860"></a>
+<a class="indexterm" name="id2656867"></a>
+<a class="indexterm" name="id2656874"></a>
+<a class="indexterm" name="id2656881"></a>
+<a class="indexterm" name="id2656888"></a>
+<a class="indexterm" name="id2656894"></a>
+<a class="indexterm" name="id2656901"></a>
+<a class="indexterm" name="id2656908"></a>
 The other services that I modified to allow the use of Winbind as an authentication service were the normal
 login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these
 services, you may first need to change the entries in <code class="filename">/etc/xinetd.d</code> (or
@@ -843,20 +843,20 @@ to
 </p><pre class="programlisting">
 	enable = yes
 </pre><p>
-<a class="indexterm" name="id2656827"></a>
-<a class="indexterm" name="id2656834"></a>
-<a class="indexterm" name="id2656841"></a>
+<a class="indexterm" name="id2656961"></a>
+<a class="indexterm" name="id2656968"></a>
+<a class="indexterm" name="id2656975"></a>
 For ftp services to work properly, you will also need to either have individual directories for the domain
 users already present on the server or change the home directory template to a general directory for all
 domain users. These can be easily set using the <code class="filename">smb.conf</code> global entry <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2656877"></a>
+<a class="indexterm" name="id2657011"></a>
 The directory in <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> is not created automatically! Use pam_mkhomedir or
 pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
 </p></div><p>
-<a class="indexterm" name="id2656902"></a>
-<a class="indexterm" name="id2656908"></a>
-<a class="indexterm" name="id2656915"></a>
+<a class="indexterm" name="id2657035"></a>
+<a class="indexterm" name="id2657042"></a>
+<a class="indexterm" name="id2657048"></a>
 The <code class="filename">/etc/pam.d/ftp</code> file can be changed to allow Winbind ftp access in a manner similar to
 the samba file. My <code class="filename">/etc/pam.d/ftp</code> file was changed to look like this:
 </p><pre class="programlisting">
@@ -869,7 +869,7 @@ account    sufficient   /lib/security/pam_winbind.so
 account    required     /lib/security/pam_stack.so service=system-auth
 session    required     /lib/security/pam_stack.so service=system-auth
 </pre><p>
-<a class="indexterm" name="id2656951"></a>
+<a class="indexterm" name="id2657085"></a>
 The <code class="filename">/etc/pam.d/login</code> file can be changed in nearly the same way. It now looks like this:
 </p><pre class="programlisting">
 auth       required     /lib/security/pam_securetty.so
@@ -883,17 +883,17 @@ password   required     /lib/security/pam_stack.so service=system-auth
 session    required     /lib/security/pam_stack.so service=system-auth
 session    optional     /lib/security/pam_console.so
 </pre><p>
-<a class="indexterm" name="id2656982"></a>
-<a class="indexterm" name="id2656989"></a>
-<a class="indexterm" name="id2656996"></a>
+<a class="indexterm" name="id2657115"></a>
+<a class="indexterm" name="id2657122"></a>
+<a class="indexterm" name="id2657129"></a>
 In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p> lines
 as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p> above it to disallow
 root logins over the network. I also added a </p><pre class="programlisting">sufficient /lib/security/pam_unix.so
 use_first_pass</pre><p> line after the <code class="literal">winbind.so</code> line to get rid of annoying
 double prompts for passwords.
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2657034"></a>Solaris-Specific Configuration</h5></div></div></div><p>
-<a class="indexterm" name="id2657042"></a>
-<a class="indexterm" name="id2657049"></a>
+</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2657167"></a>Solaris-Specific Configuration</h5></div></div></div><p>
+<a class="indexterm" name="id2657175"></a>
+<a class="indexterm" name="id2657182"></a>
 The <code class="filename">/etc/pam.conf</code> needs to be changed. I changed this file so my Domain
 users can log on both locally as well as with telnet. The following are the changes
 that I made. You can customize the <code class="filename">pam.conf</code> file as per your requirements, but
@@ -960,22 +960,22 @@ dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
 #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
 </pre><p>
-<a class="indexterm" name="id2657120"></a>
+<a class="indexterm" name="id2657253"></a>
 I also added a <em class="parameter"><code>try_first_pass</code></em> line after the <code class="filename">winbind.so</code>
 line to get rid of annoying double prompts for passwords.
 </p><p>
 Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657151"></a>Conclusion</h2></div></div></div><p>
-<a class="indexterm" name="id2657158"></a>
-<a class="indexterm" name="id2657165"></a>
-<a class="indexterm" name="id2657172"></a>
-<a class="indexterm" name="id2657178"></a>
-<a class="indexterm" name="id2657185"></a>
+</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657284"></a>Conclusion</h2></div></div></div><p>
+<a class="indexterm" name="id2657292"></a>
+<a class="indexterm" name="id2657299"></a>
+<a class="indexterm" name="id2657305"></a>
+<a class="indexterm" name="id2657312"></a>
+<a class="indexterm" name="id2657318"></a>
 The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to
 provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great
 reduction in the administrative cost of running a mixed UNIX and NT network.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657199"></a>Common Errors</h2></div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657333"></a>Common Errors</h2></div></div></div><p>
 	Winbind has a number of limitations in its current released version that we hope to overcome in future releases:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 		Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although
@@ -989,14 +989,14 @@ reduction in the administrative cost of running a mixed UNIX and NT network.
 		</p></li><li><p>
 		Currently the Winbind PAM module does not take into account possible workstation and logon time
 		restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce.
-		</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657241"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
+		</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657374"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 	Do not under any circumstances run <code class="literal">nscd</code> on any system
 	on which <code class="literal">winbindd</code> is running.
 	</p></div><p>
 	If <code class="literal">nscd</code> is running on the UNIX/Linux system, then
 	even though NSSWITCH is correctly configured, it will not be possible to resolve
 	domain users and groups for file and directory controls.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657278"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>&#8220;<span class="quote">
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657411"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>&#8220;<span class="quote">
 	My <code class="filename">smb.conf</code> file is correctly configured. I have specified <a class="link" href="smb.conf.5.html#IDMAPUID" target="_top">idmap uid = 12000</a>,
 	and <a class="link" href="smb.conf.5.html#IDMAPGID" target="_top">idmap gid = 3000-3500</a> and <code class="literal">winbind</code> is running.
 	When I do the following, it all works fine.
diff --git a/docs/htmldocs/manpages/cifs.upcall.8.html b/docs/htmldocs/manpages/cifs.upcall.8.html
index ace9aaea15..a75e66291c 100644
--- a/docs/htmldocs/manpages/cifs.upcall.8.html
+++ b/docs/htmldocs/manpages/cifs.upcall.8.html
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>cifs.upcall</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="cifs.upcall.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>cifs.upcall &#8212; Userspace upcall helper for Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">cifs.upcall</code> [--trust-dns|-t] [--version|-v] {keyid}</p></div></div><div class="refsect1" lang="en"><a name="id2522928"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>cifs.upcall is a userspace helper program for the linux CIFS client
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>cifs.upcall</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="cifs.upcall.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>cifs.upcall &#8212; Userspace upcall helper for Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">cifs.upcall</code> [--trust-dns|-t] [--version|-v] {keyid}</p></div></div><div class="refsect1" lang="en"><a name="id2522940"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>cifs.upcall is a userspace helper program for the linux CIFS client
 filesystem. There are a number of activities that the kernel cannot easily
 do itself. This program is a callout program that does these things for the
 kernel and then returns the result.</p><p>cifs.upcall is generally intended to be run when the kernel calls
 request-key(8) for a particular key type. While it
 can be run directly from the command-line, it's not generally intended
-to be run that way.</p></div><div class="refsect1" lang="en"><a name="id2483334"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c</span></dt><dd><p>This option is deprecated and is currently ignored.
+to be run that way.</p></div><div class="refsect1" lang="en"><a name="id2483345"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c</span></dt><dd><p>This option is deprecated and is currently ignored.
 		</p></dd><dt><span class="term">--trust-dns|-t</span></dt><dd><p>With krb5 upcalls, the name used as the host portion of the service principal defaults to the hostname portion of the UNC. This option allows the upcall program to reverse resolve the network address of the server in order to get the hostname.</p><p>This is less secure than not trusting DNS. When using this option, it's possible that an attacker could get control of DNS and trick the client into mounting a different server altogether. It's preferable to instead add server principals to the KDC for every possible hostname, but this option exists for cases where that isn't possible. The default is to not trust reverse hostname lookups in this fashion.
 		</p></dd><dt><span class="term">--version|-v</span></dt><dd><p>Print version number and exit.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483520"></a><h2>CONFIGURATION FOR KEYCTL</h2><p>cifs.upcall is designed to be called from the kernel via the
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483529"></a><h2>CONFIGURATION FOR KEYCTL</h2><p>cifs.upcall is designed to be called from the kernel via the
 	request-key callout program. This requires that request-key be told
 	where and how to call this program. The current cifs.upcall program
 	handles two different key types:
@@ -20,10 +20,10 @@ create      cifs.spnego    * * /usr/local/sbin/cifs.upcall %k
 create      dns_resolver   * * /usr/local/sbin/cifs.upcall %k
 </pre><p>
 See <a class="citerefentry" href="request-key.conf5..html"><span class="citerefentry"><span class="refentrytitle">request-key.conf(5)</span></span></a> for more info on each field.
-</p></div><div class="refsect1" lang="en"><a name="id2483591"></a><h2>SEE ALSO</h2><p>
+</p></div><div class="refsect1" lang="en"><a name="id2483600"></a><h2>SEE ALSO</h2><p>
 	<a class="citerefentry" href="request-key.conf.5.html"><span class="citerefentry"><span class="refentrytitle">request-key.conf</span>(5)</span></a>,
 	<a class="citerefentry" href="mount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">mount.cifs</span>(8)</span></a>
-	</p></div><div class="refsect1" lang="en"><a name="id2483616"></a><h2>AUTHOR</h2><p>Igor Mammedov wrote the cifs.upcall program.</p><p>Jeff Layton authored this manpage.</p><p>The maintainer of the Linux CIFS VFS is Steve French.</p><p>The <a class="ulink" href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux
+	</p></div><div class="refsect1" lang="en"><a name="id2483626"></a><h2>AUTHOR</h2><p>Igor Mammedov wrote the cifs.upcall program.</p><p>Jeff Layton authored this manpage.</p><p>The maintainer of the Linux CIFS VFS is Steve French.</p><p>The <a class="ulink" href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux
 		CIFS Mailing list</a> is the preferred place to ask
 		questions regarding these programs.
 	</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/eventlogadm.8.html b/docs/htmldocs/manpages/eventlogadm.8.html
index 560dedcac7..70f29c3966 100644
--- a/docs/htmldocs/manpages/eventlogadm.8.html
+++ b/docs/htmldocs/manpages/eventlogadm.8.html
@@ -10,10 +10,10 @@
 		<code class="literal">dump</code>
 		<em class="replaceable"><code>EVENTLOG</code></em>
 		<em class="replaceable"><code>RECORD_NUMBER</code></em>
-		 </p></div></div><div class="refsect1" lang="en"><a name="id2483543"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">eventlogadm</code> is a filter that accepts
+		 </p></div></div><div class="refsect1" lang="en"><a name="id2483552"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">eventlogadm</code> is a filter that accepts
 	formatted event log records on standard input and writes them
 	to the Samba event log store. Windows client can then manipulate
-	these record using the usual administration tools.</p></div><div class="refsect1" lang="en"><a name="id2483573"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">-d</code></span></dt><dd><p>
+	these record using the usual administration tools.</p></div><div class="refsect1" lang="en"><a name="id2483582"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">-d</code></span></dt><dd><p>
 		The <code class="literal">-d</code> option causes <code class="literal">eventlogadm</code> to emit debugging
 		information.
 		</p></dd><dt><span class="term">
@@ -35,7 +35,7 @@
 		event log store named by EVENTLOG.
 		</p></dd><dt><span class="term">
 		<code class="option">-o</code>
-		<code class="literal">write</code>
+		<code class="literal">dump</code>
 		<em class="replaceable"><code>EVENTLOG</code></em>
 		<em class="replaceable"><code>RECORD_NUMBER</code></em>
 		</span></dt><dd><p>
@@ -44,7 +44,7 @@
 		output on screen.
 		</p></dd><dt><span class="term"><code class="option">-h</code></span></dt><dd><p>
 		Print usage information.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483724"></a><h2>EVENTLOG RECORD FORMAT</h2><p>For the write operation, <code class="literal">eventlogadm</code>
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483733"></a><h2>EVENTLOG RECORD FORMAT</h2><p>For the write operation, <code class="literal">eventlogadm</code>
 	expects to be able to read structured records from standard
 	input. These records are a sequence of lines, with the record key
 	and data separated by a colon character. Records are separated
@@ -93,7 +93,7 @@
 		eventlog. There may be more than one string in a record.
 		</p></li><li><p>
 		<code class="literal">DAT</code> - This field should be left unset.
-		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481590"></a><h2>EXAMPLES</h2><p>An example of the record format accepted by <code class="literal">eventlogadm</code>:</p><pre class="programlisting">
+		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481600"></a><h2>EXAMPLES</h2><p>An example of the record format accepted by <code class="literal">eventlogadm</code>:</p><pre class="programlisting">
 	LEN: 0
 	RS1: 1699505740
 	RCN: 0
@@ -116,7 +116,7 @@
 	tail -f /var/log/messages | \\
 		my_program_to_parse_into_eventlog_records | \\
 	      	eventlogadm SystemLogEvents
-	</pre></div><div class="refsect1" lang="en"><a name="id2481639"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481650"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
+	</pre></div><div class="refsect1" lang="en"><a name="id2481650"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481661"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
 	created by Andrew Tridgell.  Samba is now developed by the
 	Samba Team as an Open Source project similar to the way the
 	Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/findsmb.1.html b/docs/htmldocs/manpages/findsmb.1.html
index 1b299495ed..94fad87f8f 100644
--- a/docs/htmldocs/manpages/findsmb.1.html
+++ b/docs/htmldocs/manpages/findsmb.1.html
@@ -1,12 +1,12 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>findsmb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="findsmb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>findsmb &#8212; list info about machines that respond to SMB 
-	name queries on a subnet</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">findsmb</code> [subnet broadcast address]</p></div></div><div class="refsect1" lang="en"><a name="id2522919"></a><h2>DESCRIPTION</h2><p>This perl script is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>
+	name queries on a subnet</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">findsmb</code> [subnet broadcast address]</p></div></div><div class="refsect1" lang="en"><a name="id2522923"></a><h2>DESCRIPTION</h2><p>This perl script is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>
 	suite.</p><p><code class="literal">findsmb</code> is a perl script that
 	prints out several pieces of information about machines 
 	on a subnet that respond to SMB  name query requests.
 	It uses <a class="citerefentry" href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a>
 	and <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>
 	to obtain this information.
-	</p></div><div class="refsect1" lang="en"><a name="id2483328"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>Controls whether <code class="literal">findsmb</code> takes
+	</p></div><div class="refsect1" lang="en"><a name="id2483331"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>Controls whether <code class="literal">findsmb</code> takes
 		bugs in Windows95 into account when trying to find a Netbios name
 		registered of the remote machine. This option is disabled by default
 		because it is specific to Windows 95 and Windows 95 machines only. 
@@ -16,7 +16,7 @@
 		<a class="citerefentry" href="findsmb.1.html"><span class="citerefentry"><span class="refentrytitle">findsmb</span>(1)</span></a>
 		is run. This value is passed to 
 		<a class="citerefentry" href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a>
-		as part of the <code class="constant">-B</code> option.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483527"></a><h2>EXAMPLES</h2><p>The output of <code class="literal">findsmb</code> lists the following 
+		as part of the <code class="constant">-B</code> option.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483530"></a><h2>EXAMPLES</h2><p>The output of <code class="literal">findsmb</code> lists the following 
 	information for all machines that respond to the initial 
 	<code class="literal">nmblookup</code> for any name: IP address, NetBIOS name, 
 	Workgroup name, operating system, and SMB server version.</p><p>There will be a '+' in front of the workgroup name for 
@@ -48,10 +48,10 @@ IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION
 192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
 192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
 192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
-</pre></div><div class="refsect1" lang="en"><a name="id2483629"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483640"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>,
+</pre></div><div class="refsect1" lang="en"><a name="id2483632"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483643"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>,
 	<a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, and <a class="citerefentry" href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a>
-	</p></div><div class="refsect1" lang="en"><a name="id2483674"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	</p></div><div class="refsect1" lang="en"><a name="id2483677"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/idmap_ad.8.html b/docs/htmldocs/manpages/idmap_ad.8.html
index c2228b0e57..d1f831d002 100644
--- a/docs/htmldocs/manpages/idmap_ad.8.html
+++ b/docs/htmldocs/manpages/idmap_ad.8.html
@@ -4,7 +4,7 @@
 	API, and is READONLY. Mappings must be provided in advance
 	by the administrator by adding the posixAccount/posixGroup
 	classes and relative attribute/value pairs to the user and
-	group objects in the AD.</p></div><div class="refsect1" lang="en"><a name="id2522913"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
+	group objects in the AD.</p></div><div class="refsect1" lang="en"><a name="id2522918"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
 			Defines the available matching UID and GID range for which the
 			backend is authoritative. Note that the range acts as a filter.
 			If specified any UID or GID stored in AD that fall outside the
@@ -16,7 +16,7 @@
 			Active Directory regarding user and group information.
 			This can be either the RFC2307 schema support included
 			in Windows 2003 R2 or the Service for Unix (SFU) schema.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483324"></a><h2>EXAMPLES</h2><p>
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483327"></a><h2>EXAMPLES</h2><p>
 	The following example shows how to retrieve idmappings from our principal and
 	and trusted AD domains. If trusted domains are present id conflicts must be
 	resolved beforehand, there is no
@@ -32,7 +32,7 @@
 
 	idmap config CORP : backend  = ad
 	idmap config CORP : range = 1000-999999
-	</pre></div><div class="refsect1" lang="en"><a name="id2483349"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483351"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_adex.8.html b/docs/htmldocs/manpages/idmap_adex.8.html
index 5700ea1987..0d56a8c9d2 100644
--- a/docs/htmldocs/manpages/idmap_adex.8.html
+++ b/docs/htmldocs/manpages/idmap_adex.8.html
@@ -25,7 +25,7 @@
 	  Username aliases are implement by setting the uid attribute
 	  on the user object.  While group name aliases are implemented
 	  by reading the displayname attribute from the group object.
-	</p></div><div class="refsect1" lang="en"><a name="id2522940"></a><h2>EXAMPLES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>EXAMPLES</h2><p>
 	  The following example shows how to retrieve idmappings and NSS data
 	  from our principal and trusted AD domains.
 	</p><pre class="programlisting">
@@ -36,7 +36,7 @@
 
 	winbind nss info = adex
 	winbind normalize names = yes
-	</pre></div><div class="refsect1" lang="en"><a name="id2483330"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483341"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_hash.8.html b/docs/htmldocs/manpages/idmap_hash.8.html
index d224965770..4aa8f71525 100644
--- a/docs/htmldocs/manpages/idmap_hash.8.html
+++ b/docs/htmldocs/manpages/idmap_hash.8.html
@@ -4,13 +4,13 @@
 	  to support a local name mapping files if enabled via the
 	  "winbind normalize names" and "winbind nss info"
 	  parameters in smb.conf.
-	</p></div><div class="refsect1" lang="en"><a name="id2522906"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">name_map</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522917"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">name_map</span></dt><dd><p>
 		    Specifies the absolute path to the name mapping
 		    file used by the nss_info API.  Entries in the file
 		    are of the form "<em class="replaceable"><code>unix name</code></em>
 		    = <em class="replaceable"><code>qualified domain name</code></em>".
 		    Mapping of both user and group names is supported.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2522937"></a><h2>EXAMPLES</h2><p>The following example utilizes the idmap_hash plugin for
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>EXAMPLES</h2><p>The following example utilizes the idmap_hash plugin for
 	  the idmap and nss_info information.
 	</p><pre class="programlisting">
 	[global]
@@ -21,7 +21,7 @@
 	winbind nss info = hash
 	winbind normalize names = yes
 	idmap_hash:name_map = /etc/samba/name_map.cfg
-	</pre></div><div class="refsect1" lang="en"><a name="id2483327"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483339"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_ldap.8.html b/docs/htmldocs/manpages/idmap_ldap.8.html
index 232b949a3b..f5e6e59cb2 100644
--- a/docs/htmldocs/manpages/idmap_ldap.8.html
+++ b/docs/htmldocs/manpages/idmap_ldap.8.html
@@ -19,7 +19,7 @@
 	any explicitly configured domain with idmap backend ldap
 	should have the same range as the default range, since it needs
 	to use the global uid / gid allocator. See the example below.
-	</p></div><div class="refsect1" lang="en"><a name="id2522932"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">ldap_base_dn = DN</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522944"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">ldap_base_dn = DN</span></dt><dd><p>
 			Defines the directory base suffix to use when searching for
 			SID/uid/gid mapping entries.  If not defined, idmap_ldap will default
 			to using the "ldap idmap suffix" option from smb.conf.
@@ -36,7 +36,7 @@
 			If the parameter is absent, Winbind fails over to use the
 			"idmap uid" and "idmap gid" options
 			from smb.conf.
-                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483370"></a><h2>IDMAP ALLOC OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">ldap_base_dn = DN</span></dt><dd><p>
+                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483381"></a><h2>IDMAP ALLOC OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">ldap_base_dn = DN</span></dt><dd><p>
 			Defines the directory base suffix under which new SID/uid/gid mapping
 			entries should be stored.  If not defined, idmap_ldap will default
 			to using the "ldap idmap suffix" option from smb.conf.
@@ -47,7 +47,7 @@
 			Specifies the LDAP server to which modify/add/delete requests should
 			be sent.  If not defined, idmap_ldap will assume that ldap://localhost/
 			should be used.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483550"></a><h2>EXAMPLES</h2><p>
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483559"></a><h2>EXAMPLES</h2><p>
 	The follow sets of a LDAP configuration which uses two LDAP
 	directories, one for storing the ID mappings and one for retrieving
 	new IDs.
@@ -65,7 +65,7 @@
 	in plain text in the configuration file we store it into a security
 	store. The "net idmap " command is used to store a secret
 	for the DN specified in a specific idmap domain.
-	</p></div><div class="refsect1" lang="en"><a name="id2483586"></a><h2>AUTHOR</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483596"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_nss.8.html b/docs/htmldocs/manpages/idmap_nss.8.html
index 11b187d7b9..9c7cd0f6f4 100644
--- a/docs/htmldocs/manpages/idmap_nss.8.html
+++ b/docs/htmldocs/manpages/idmap_nss.8.html
@@ -4,7 +4,7 @@
 	for a Unix user named jsmith is reported as the one assigned to
 	DOMAIN\jsmith which is necessary for reporting ACLs on files and printers
 	stored on a Samba member server.
-	</p></div><div class="refsect1" lang="en"><a name="id2522913"></a><h2>EXAMPLES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522918"></a><h2>EXAMPLES</h2><p>
 	This example shows how to use idmap_nss to check the local accounts for its
 	own domain while using allocation to create new mappings for trusted domains
 	</p><pre class="programlisting">
@@ -15,7 +15,7 @@
 
 	idmap config SAMBA : backend  = nss
 	idmap config SAMBA : range = 1000-999999
-	</pre></div><div class="refsect1" lang="en"><a name="id2522934"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2522939"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_rid.8.html b/docs/htmldocs/manpages/idmap_rid.8.html
index ffb7ef656b..7a31560135 100644
--- a/docs/htmldocs/manpages/idmap_rid.8.html
+++ b/docs/htmldocs/manpages/idmap_rid.8.html
@@ -1,6 +1,6 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>idmap_rid</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="idmap_rid.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>idmap_rid &#8212; Samba's idmap_rid Backend for Winbind</p></div><div class="refsynopsisdiv"><h2>DESCRIPTION</h2><p>The idmap_rid backend provides a way to use an algorithmic
 	mapping scheme to map UIDs/GIDs and SIDs. No database is required
-	in this case as the mapping is deterministic.</p></div><div class="refsect1" lang="en"><a name="id2522909"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
+	in this case as the mapping is deterministic.</p></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
 			Defines the available matching uid and gid range for which the
 			backend is authoritative. Note that the range acts as a filter.
 			If algorithmically determined UID or GID fall outside the
@@ -28,7 +28,7 @@
 		</p><pre class="programlisting">
 			RID = ID + BASE_RID - LOW_RANGE_ID.
 		</pre><p>
-	</p></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>EXAMPLES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483357"></a><h2>EXAMPLES</h2><p>
 		This example shows how to configure two domains with idmap_rid,
 		the principal domain and a trusted domain, leaving the default
 		id mapping scheme at tdb. The example also demonstrates the use
@@ -48,7 +48,7 @@
 	idmap config TRUSTED : backend  = rid
 	idmap config TRUSTED : range    = 50000 - 99999
 	idmap config TRUSTED : base_rid = 1000
-	</pre></div><div class="refsect1" lang="en"><a name="id2483384"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483383"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_tdb.8.html b/docs/htmldocs/manpages/idmap_tdb.8.html
index 580dbce75a..0d1dfbcfb8 100644
--- a/docs/htmldocs/manpages/idmap_tdb.8.html
+++ b/docs/htmldocs/manpages/idmap_tdb.8.html
@@ -19,13 +19,13 @@
 	any explicitly configured domain with idmap backend tdb
 	should have the same range as the default range, since it needs
 	to use the global uid / gid allocator. See the example below.
-	</p></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522944"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
 			Defines the available matching uid and gid range for which the
 			backend is authoritative.
 			If the parameter is absent, Winbind fails over to use
 			the "idmap uid" and "idmap gid" options
 			from smb.conf.
-                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483330"></a><h2>EXAMPLES</h2><p>
+                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483335"></a><h2>EXAMPLES</h2><p>
 	This example shows how tdb is used as a the default idmap backend.
 	It configures the idmap range through the global options for all
 	domains encountered. This same range is used for uid/gid allocation.
@@ -53,7 +53,7 @@
 
 	idmap config DOM1 : backend = tdb
 	idmap config DOM1 : range = 1000000-2000000
-	</pre></div><div class="refsect1" lang="en"><a name="id2483372"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483376"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/idmap_tdb2.8.html b/docs/htmldocs/manpages/idmap_tdb2.8.html
index fcf060585f..9198b56e3d 100644
--- a/docs/htmldocs/manpages/idmap_tdb2.8.html
+++ b/docs/htmldocs/manpages/idmap_tdb2.8.html
@@ -20,13 +20,13 @@
 	any explicitly configured domain with idmap backend tdb2
 	should have the same range as the default range, since it needs
 	to use the global uid / gid allocator. See the example below.
-	</p></div><div class="refsect1" lang="en"><a name="id2522933"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522945"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
 			Defines the available matching uid and gid range for which the
 			backend is authoritative.
 			If the parameter is absent, Winbind fails over to use
 			the "idmap uid" and "idmap gid" options
 			from smb.conf.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483328"></a><h2>IDMAP SCRIPT</h2><p>
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483340"></a><h2>IDMAP SCRIPT</h2><p>
 	The tdb2 idmap backend supports a script for performing id mappings
 	through the smb.conf option <em class="parameter"><code>idmap : script</code></em>.
 	The script should accept the following command line options.
@@ -47,7 +47,7 @@
 	that can be passed in for SID to Unix ID mapping, since otherwise
 	SIDs unmapped by the script might get mapped to IDs that had
 	previously been mapped by the script.
-	</p></div><div class="refsect1" lang="en"><a name="id2483371"></a><h2>EXAMPLES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483382"></a><h2>EXAMPLES</h2><p>
 	This example shows how tdb2 is used as a the default idmap backend.
 	It configures the idmap range through the global options for all
 	domains encountered. This same range is used for uid/gid allocation.
@@ -56,7 +56,7 @@
 	idmap backend = tdb2
 	idmap uid = 1000000-2000000
 	idmap gid = 1000000-2000000
-	</pre></div><div class="refsect1" lang="en"><a name="id2483519"></a><h2>AUTHOR</h2><p>
+	</pre></div><div class="refsect1" lang="en"><a name="id2483528"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
diff --git a/docs/htmldocs/manpages/index.html b/docs/htmldocs/manpages/index.html
index 75a3976a2e..130a807a16 100644
--- a/docs/htmldocs/manpages/index.html
+++ b/docs/htmldocs/manpages/index.html
@@ -30,7 +30,6 @@
 	names
 </p></dd><dt><span class="term"><a class="ulink" href="ntlm_auth.1.html" target="_top">ntlm_auth(1)</a></span></dt><dd><p>tool to allow external access to Winbind's NTLM authentication function
 </p></dd><dt><span class="term"><a class="ulink" href="pam_winbind.8.html" target="_top">pam_winbind(8)</a></span></dt><dd><p>PAM module for Winbind
-</p></dd><dt><span class="term"><a class="ulink" href="pam_winbind.conf.5.html" target="_top">pam_winbind.conf(5)</a></span></dt><dd><p>Configuration file of PAM module for Winbind
 </p></dd><dt><span class="term"><a class="ulink" href="pdbedit.8.html" target="_top">pdbedit(8)</a></span></dt><dd><p>manage the SAM database (Database of Samba Users)
 </p></dd><dt><span class="term"><a class="ulink" href="profiles.1.html" target="_top">profiles(1)</a></span></dt><dd><p>A utility to report and change SIDs in registry files
 	
@@ -84,8 +83,6 @@
 </p></dd><dt><span class="term"><a class="ulink" href="vfs_readahead.8.html" target="_top">vfs_readahead(8)</a></span></dt><dd><p>pre-load the kernel buffer cache
 </p></dd><dt><span class="term"><a class="ulink" href="vfs_readonly.8.html" target="_top">vfs_readonly(8)</a></span></dt><dd><p>make a Samba share read only for a specified time period
 </p></dd><dt><span class="term"><a class="ulink" href="vfs_recycle.8.html" target="_top">vfs_recycle(8)</a></span></dt><dd><p>Samba VFS recycle bin
-</p></dd><dt><span class="term"><a class="ulink" href="vfs_scannedonly.8.html" target="_top">vfs_scannedonly(8)</a></span></dt><dd><p>Ensures that only files that have been scanned for viruses are
-	visible and accessible to the end user.
 </p></dd><dt><span class="term"><a class="ulink" href="vfs_shadow_copy2.8.html" target="_top">vfs_shadow_copy2(8)</a></span></dt><dd><p>Expose snapshots to Windows clients as shadow copies.
 </p></dd><dt><span class="term"><a class="ulink" href="vfs_shadow_copy.8.html" target="_top">vfs_shadow_copy(8)</a></span></dt><dd><p>Make a Samba share read only for a specified time period
 </p></dd><dt><span class="term"><a class="ulink" href="smb_traffic_analyzer.8.html" target="_top">smb_traffic_analyzer(8)</a></span></dt><dd><p>log Samba VFS read and write operations through a socket
diff --git a/docs/htmldocs/manpages/ldb.3.html b/docs/htmldocs/manpages/ldb.3.html
index ac19ade122..8c2d96645e 100644
--- a/docs/htmldocs/manpages/ldb.3.html
+++ b/docs/htmldocs/manpages/ldb.3.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldb.3"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldb<p><b>The Samba Project</b></p> &#8212; A light-weight database library</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><pre class="synopsis">#include &lt;ldb.h&gt;</pre></div><div class="refsect1" lang="en"><a name="id2522906"></a><h2>description</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldb.3"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldb<p><b>The Samba Project</b></p> &#8212; A light-weight database library</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><pre class="synopsis">#include &lt;ldb.h&gt;</pre></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>description</h2><p>
 ldb is a light weight embedded database library and API. With a
 programming interface that is very similar to LDAP, ldb can store its
 data either in a tdb(3) database or in a real LDAP database.
@@ -34,7 +34,7 @@ If you are new to ldb, then I suggest starting with the manual pages
 for ldbsearch(1) and ldbedit(1), and experimenting with a local
 database. Then I suggest you look at the ldb_connect(3) and
 ldb_search(3) manual pages.
-	</p></div><div class="refsect1" lang="en"><a name="id2483332"></a><h2>TOOLS</h2><div class="itemizedlist"><ul type="disc"><li><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483339"></a><h2>TOOLS</h2><div class="itemizedlist"><ul type="disc"><li><p>
 			<span class="application">ldbsearch(1)</span>
 			  - command line ldb search utility
 		</p></li><li><p>
@@ -49,7 +49,7 @@ ldb_search(3) manual pages.
 		</p></li><li><p>
 			<span class="application">ldbmodify(1)</span>
 			 - modify records in a ldb database using LDIF formatted input
-		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483518"></a><h2>FUNCTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>
+		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483525"></a><h2>FUNCTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>
 			<code class="function">ldb_connect(3)</code>
 			 - connect to a ldb backend
 		</p></li><li><p>
@@ -124,7 +124,7 @@ ldb_search(3) manual pages.
 		</p></li><li><p>
 			<code class="function">ldb_set_debug_stderr(3)</code>
 			 - set a debug handler for stderr output
-		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481467"></a><h2>Author</h2><p>
+		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481474"></a><h2>Author</h2><p>
 		ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
diff --git a/docs/htmldocs/manpages/ldbadd.1.html b/docs/htmldocs/manpages/ldbadd.1.html
index f596c365ca..f682dc4457 100644
--- a/docs/htmldocs/manpages/ldbadd.1.html
+++ b/docs/htmldocs/manpages/ldbadd.1.html
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbadd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbadd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbadd &#8212; Command-line utility for adding records to an LDB</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbadd</code> [-h] [-H LDB-URL] [ldif-file1] [ldif-file2] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2522946"></a><h2>DESCRIPTION</h2><p>ldbadd adds records to an ldb(7) database. It reads 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbadd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbadd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbadd &#8212; Command-line utility for adding records to an LDB</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbadd</code> [-h] [-H LDB-URL] [ldif-file1] [ldif-file2] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>DESCRIPTION</h2><p>ldbadd adds records to an ldb(7) database. It reads 
 		the ldif(5) files specified on the command line and adds 
 		the records from these files to the LDB database, which is specified 
 		by the -H option or the LDB_URL environment variable.
 	</p><p>If - is specified as a ldb file, the ldif input is read from 
-		standard input.</p></div><div class="refsect1" lang="en"><a name="id2483331"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
+		standard input.</p></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
 		Show list of available options.</p></dd><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
 				LDB URL to connect to. See ldb(7) for details.
-			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483365"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
-					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483387"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483522"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbdel, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483532"></a><h2>AUTHOR</h2><p> ldb was written by 
+			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483371"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483392"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483527"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbdel, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483537"></a><h2>AUTHOR</h2><p> ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
 If you wish to report a problem or make a suggestion then please see
diff --git a/docs/htmldocs/manpages/ldbdel.1.html b/docs/htmldocs/manpages/ldbdel.1.html
index 1ca1528919..d38fa74fe4 100644
--- a/docs/htmldocs/manpages/ldbdel.1.html
+++ b/docs/htmldocs/manpages/ldbdel.1.html
@@ -1,12 +1,12 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbdel</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbdel.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbdel &#8212; Command-line program for deleting LDB records</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbdel</code> [-h] [-H LDB-URL] [dn] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>DESCRIPTION</h2><p>ldbdel deletes records from an ldb(7) database. 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbdel</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbdel.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbdel &#8212; Command-line program for deleting LDB records</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbdel</code> [-h] [-H LDB-URL] [dn] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2522944"></a><h2>DESCRIPTION</h2><p>ldbdel deletes records from an ldb(7) database. 
 		It deletes the records identified by the dn's specified 
 		on the command-line. </p><p>ldbdel uses either the database that is specified with 
 		the -H option or the database specified by the LDB_URL environment
-		variable.</p></div><div class="refsect1" lang="en"><a name="id2483324"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
+		variable.</p></div><div class="refsect1" lang="en"><a name="id2483328"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
 		Show list of available options.</p></dd><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
 				LDB URL to connect to. See ldb(7) for details.
-			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
-					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483379"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483514"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbadd, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483524"></a><h2>AUTHOR</h2><p> ldb was written by 
+			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483362"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483383"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483394"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbadd, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483529"></a><h2>AUTHOR</h2><p> ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
 If you wish to report a problem or make a suggestion then please see
diff --git a/docs/htmldocs/manpages/ldbedit.1.html b/docs/htmldocs/manpages/ldbedit.1.html
index 20da8eeccc..9d2de5acc6 100644
--- a/docs/htmldocs/manpages/ldbedit.1.html
+++ b/docs/htmldocs/manpages/ldbedit.1.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbedit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbedit.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbedit &#8212; Edit LDB databases using your preferred editor</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbedit</code> [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...]</p></div></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>DESCRIPTION</h2><p>ldbedit is a utility that allows you to edit LDB entries (in 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbedit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbedit.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbedit &#8212; Edit LDB databases using your preferred editor</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbedit</code> [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...]</p></div></div><div class="refsect1" lang="en"><a name="id2483351"></a><h2>DESCRIPTION</h2><p>ldbedit is a utility that allows you to edit LDB entries (in 
 	    tdb files, sqlite files or LDAP servers) using your preferred editor.
 	    ldbedit generates an LDIF file based on your query, allows you to edit
 	    the LDIF, and then merges that LDIF back into the LDB backend.
-	</p></div><div class="refsect1" lang="en"><a name="id2483363"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-?, </span><span class="term">--help</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483366"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-?, </span><span class="term">--help</span></dt><dd><p>
 			Show list of available options, and a phrase describing what that option
 			does.
 		    </p></dd><dt><span class="term">--usage</span></dt><dd><p>
@@ -34,14 +34,14 @@
 			operations that are being performed. Without
 			this option, ldbedit will only provide a
 			summary change line.
-		    </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483647"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to. This can be
+		    </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483649"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to. This can be
 		    overridden by using the -H command-line option.)
 		    </p></dd><dt><span class="term">VISUAL and EDITOR</span></dt><dd><p>
 			Environment variables used to determine what 
 			editor to use. VISUAL takes precedence over
 			EDITOR, and both are overridden by the
 			-e command-line option.
-		    </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483688"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483699"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)</p></div><div class="refsect1" lang="en"><a name="id2483710"></a><h2>AUTHOR</h2><p>
+		    </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483690"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483701"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)</p></div><div class="refsect1" lang="en"><a name="id2483712"></a><h2>AUTHOR</h2><p>
 	    ldb was written by 
 	    <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
diff --git a/docs/htmldocs/manpages/ldbmodify.1.html b/docs/htmldocs/manpages/ldbmodify.1.html
index 8cc2b04822..9cbd67b5e1 100644
--- a/docs/htmldocs/manpages/ldbmodify.1.html
+++ b/docs/htmldocs/manpages/ldbmodify.1.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbmodify</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbmodify.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbmodify &#8212; Modify records in a LDB database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbmodify</code> [-H LDB-URL] [ldif-file]</p></div></div><div class="refsect1" lang="en"><a name="id2522926"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbmodify</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbmodify.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbmodify &#8212; Modify records in a LDB database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbmodify</code> [-H LDB-URL] [ldif-file]</p></div></div><div class="refsect1" lang="en"><a name="id2522929"></a><h2>DESCRIPTION</h2><p>
 		ldbmodify changes, adds and deletes records in a LDB database. 
 		The changes that should be made to the LDB database are read from 
 		the specified LDIF-file. If - is specified as the filename, input is read from stdin.
-	</p><p>For now, see ldapmodify(1) for details on the LDIF file format.</p></div><div class="refsect1" lang="en"><a name="id2522945"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
+	</p><p>For now, see ldapmodify(1) for details on the LDIF file format.</p></div><div class="refsect1" lang="en"><a name="id2522948"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
 				LDB URL to connect to. See ldb(7) for details.
-			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483332"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
-					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483354"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483365"></a><h2>SEE ALSO</h2><p>ldb(7), ldbedit</p></div><div class="refsect1" lang="en"><a name="id2483375"></a><h2>AUTHOR</h2><p> ldb was written by 
+			</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483336"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483369"></a><h2>SEE ALSO</h2><p>ldb(7), ldbedit</p></div><div class="refsect1" lang="en"><a name="id2483379"></a><h2>AUTHOR</h2><p> ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
 If you wish to report a problem or make a suggestion then please see
diff --git a/docs/htmldocs/manpages/ldbrename.1.html b/docs/htmldocs/manpages/ldbrename.1.html
index e6fcea1992..cbb1b6226c 100644
--- a/docs/htmldocs/manpages/ldbrename.1.html
+++ b/docs/htmldocs/manpages/ldbrename.1.html
@@ -1,13 +1,13 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbrename</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbrename.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbrename &#8212; Edit LDB databases using your favorite editor</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbrename</code> [-h] [-o options] {olddn} {newdb}</p></div></div><div class="refsect1" lang="en"><a name="id2522943"></a><h2>DESCRIPTION</h2><p>ldbrename is a utility that allows you to rename trees in 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbrename</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbrename.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbrename &#8212; Edit LDB databases using your favorite editor</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbrename</code> [-h] [-o options] {olddn} {newdb}</p></div></div><div class="refsect1" lang="en"><a name="id2522946"></a><h2>DESCRIPTION</h2><p>ldbrename is a utility that allows you to rename trees in 
 		an LDB database based by DN. This utility takes 
 		two arguments: the original 
 		DN name of the top element and the DN to change it to.
-	</p></div><div class="refsect1" lang="en"><a name="id2483322"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483328"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
 		Show list of available options.</p></dd><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
 				LDB URL to connect to. See ldb(7) for details.
 			</p></dd><dt><span class="term">-o options</span></dt><dd><p>Extra ldb options, such as 
-			modules.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483368"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
-					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483389"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483524"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbdel, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483534"></a><h2>AUTHOR</h2><p> ldb was written by 
+			modules.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483372"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483393"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483526"></a><h2>SEE ALSO</h2><p>ldb(7), ldbmodify, ldbdel, ldif(5)</p></div><div class="refsect1" lang="en"><a name="id2483535"></a><h2>AUTHOR</h2><p> ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
 If you wish to report a problem or make a suggestion then please see
diff --git a/docs/htmldocs/manpages/ldbsearch.1.html b/docs/htmldocs/manpages/ldbsearch.1.html
index e611c9200a..ca8489a54c 100644
--- a/docs/htmldocs/manpages/ldbsearch.1.html
+++ b/docs/htmldocs/manpages/ldbsearch.1.html
@@ -1,12 +1,12 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbsearch</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbsearch.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbsearch &#8212; Search for records in a LDB database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbsearch</code> [-h] [-s base|one|sub] [-b basedn] [-i] [-H LDB-URL] [expression] [attributes]</p></div></div><div class="refsect1" lang="en"><a name="id2483333"></a><h2>DESCRIPTION</h2><p>ldbsearch searches a LDB database for records matching the 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ldbsearch</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ldbsearch.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ldbsearch &#8212; Search for records in a LDB database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ldbsearch</code> [-h] [-s base|one|sub] [-b basedn] [-i] [-H LDB-URL] [expression] [attributes]</p></div></div><div class="refsect1" lang="en"><a name="id2483338"></a><h2>DESCRIPTION</h2><p>ldbsearch searches a LDB database for records matching the 
 		specified expression (see the ldapsearch(1) manpage for 
 		a description of the expression format). For each 
 		record, the specified attributes are printed.
-	</p></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483352"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
 		Show list of available options.</p></dd><dt><span class="term">-H &lt;ldb-url&gt;</span></dt><dd><p>
 				LDB URL to connect to. See ldb(7) for details.
-			</p></dd><dt><span class="term">-s one|sub|base</span></dt><dd><p>Search scope to use. One-level, subtree or base.</p></dd><dt><span class="term">-i</span></dt><dd><p>Read search expressions from stdin. </p></dd><dt><span class="term">-b basedn</span></dt><dd><p>Specify Base DN to use.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483540"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
-					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483561"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483572"></a><h2>SEE ALSO</h2><p>ldb(7), ldbedit(1)</p></div><div class="refsect1" lang="en"><a name="id2483582"></a><h2>AUTHOR</h2><p> ldb was written by 
+			</p></dd><dt><span class="term">-s one|sub|base</span></dt><dd><p>Search scope to use. One-level, subtree or base.</p></dd><dt><span class="term">-i</span></dt><dd><p>Read search expressions from stdin. </p></dd><dt><span class="term">-b basedn</span></dt><dd><p>Specify Base DN to use.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483543"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl><dt><span class="term">LDB_URL</span></dt><dd><p>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483564"></a><h2>VERSION</h2><p>This man page is correct for version 4.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483575"></a><h2>SEE ALSO</h2><p>ldb(7), ldbedit(1)</p></div><div class="refsect1" lang="en"><a name="id2483585"></a><h2>AUTHOR</h2><p> ldb was written by 
 		 <a class="ulink" href="http://samba.org/~tridge/" target="_top">Andrew Tridgell</a>.
 	</p><p>
 If you wish to report a problem or make a suggestion then please see
diff --git a/docs/htmldocs/manpages/libsmbclient.7.html b/docs/htmldocs/manpages/libsmbclient.7.html
index ef0b3e662d..e2fed89e5c 100644
--- a/docs/htmldocs/manpages/libsmbclient.7.html
+++ b/docs/htmldocs/manpages/libsmbclient.7.html
@@ -2,7 +2,7 @@
 	Browser URL:
 	<code class="literal">smb://[[[domain:]user[:password@]]server[/share[/path[/file]]]] [?options]
 	</code>
-	</p></p></div></div><div class="refsect1" lang="en"><a name="id2522909"></a><h2>DESCRIPTION</h2><p>
+	</p></p></div></div><div class="refsect1" lang="en"><a name="id2522921"></a><h2>DESCRIPTION</h2><p>
 	This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.
 	</p><p>
 	<code class="literal">libsmbclient</code> is a library toolset that permits applications to manipulate CIFS/SMB network
@@ -14,7 +14,7 @@
 	<code class="literal">libsmbclient</code> can not be used directly from the command line, instead it provides an
 	extension of the capabilities of tools such as file managers and browsers.  This man page describes the
 	configuration options for this tool so that the user may obtain greatest utility of use.
-	</p></div><div class="refsect1" lang="en"><a name="id2483328"></a><h2>OPTIONS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483338"></a><h2>OPTIONS</h2><p>
 	What the URLs mean:
 	</p><div class="variablelist"><dl><dt><span class="term">smb://</span></dt><dd><p>
 			Shows all workgroups or domains that are visible in the network. The behavior matches
@@ -46,11 +46,11 @@
 	<code class="literal">libsmbclient</code> will check the users shell environment for the <code class="literal">USER</code>
 	parameter and will use its value when if the <code class="literal">user</code> parameter was not included
 	in the URL.
-	</p></div><div class="refsect1" lang="en"><a name="id2483594"></a><h2>PROGRAMMERS GUIDE</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483603"></a><h2>PROGRAMMERS GUIDE</h2><p>
 	Watch this space for future updates.
-	</p></div><div class="refsect1" lang="en"><a name="id2483605"></a><h2>VERSION</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483613"></a><h2>VERSION</h2><p>
 	This man page is correct for version 3 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483616"></a><h2>AUTHOR</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483624"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities were created by Andrew Tridgell.
 	Samba is now developed by the Samba Team as an Open Source project similar to the way
 	the Linux kernel is developed.
diff --git a/docs/htmldocs/manpages/lmhosts.5.html b/docs/htmldocs/manpages/lmhosts.5.html
index 1aea6849a7..9d4dd64522 100644
--- a/docs/htmldocs/manpages/lmhosts.5.html
+++ b/docs/htmldocs/manpages/lmhosts.5.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>lmhosts</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="lmhosts.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>lmhosts &#8212; The Samba NetBIOS hosts file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">lmhosts</code> is the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> NetBIOS name to IP address mapping file.</p></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This file is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="filename">lmhosts</code> is the <span class="emphasis"><em>Samba
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>lmhosts</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="lmhosts.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>lmhosts &#8212; The Samba NetBIOS hosts file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">lmhosts</code> is the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> NetBIOS name to IP address mapping file.</p></div><div class="refsect1" lang="en"><a name="id2522921"></a><h2>DESCRIPTION</h2><p>This file is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="filename">lmhosts</code> is the <span class="emphasis"><em>Samba
 	</em></span> NetBIOS name to IP address mapping file.  It 
 	is very similar to the <code class="filename">/etc/hosts</code> file 
 	format, except that the hostname component must correspond 
-	to the NetBIOS naming format.</p></div><div class="refsect1" lang="en"><a name="id2483320"></a><h2>FILE FORMAT</h2><p>It is an ASCII file containing one line for NetBIOS name. 
+	to the NetBIOS naming format.</p></div><div class="refsect1" lang="en"><a name="id2483325"></a><h2>FILE FORMAT</h2><p>It is an ASCII file containing one line for NetBIOS name. 
 	The two fields on each line are separated from each other by 
 	white space. Any entry beginning with '#' is ignored. Each line 
 	in the lmhosts file contains the following information:</p><div class="itemizedlist"><ul type="disc"><li><p>IP Address - in dotted decimal format.</p></li><li><p>NetBIOS Name - This name format is a 
@@ -25,10 +25,10 @@
 	the NetBIOS name requested.</p><p>The second mapping will be returned only when the "0x20" name 
 	type for a name "NTSERVER" is queried. Any other name type will not 
 	be resolved.</p><p>The default location of the <code class="filename">lmhosts</code> file 
-	is in the same directory as the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.</p></div><div class="refsect1" lang="en"><a name="id2483523"></a><h2>FILES</h2><p>lmhosts is loaded from the configuration directory. This is 
+	is in the same directory as the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.</p></div><div class="refsect1" lang="en"><a name="id2483526"></a><h2>FILES</h2><p>lmhosts is loaded from the configuration directory. This is 
 		usually <code class="filename">/etc/samba</code> or <code class="filename">/usr/local/samba/lib</code>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483545"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483556"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, and <a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>
-	</p></div><div class="refsect1" lang="en"><a name="id2483591"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	</p></div><div class="refsect1" lang="en"><a name="id2483549"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483560"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, and <a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>
+	</p></div><div class="refsect1" lang="en"><a name="id2483594"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/log2pcap.1.html b/docs/htmldocs/manpages/log2pcap.1.html
index 0bdae05715..f019208784 100644
--- a/docs/htmldocs/manpages/log2pcap.1.html
+++ b/docs/htmldocs/manpages/log2pcap.1.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>log2pcap</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="log2pcap.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>log2pcap &#8212; Extract network traces from Samba log files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">log2pcap</code> [-h] [-q] [logfile] [pcap_file]</p></div></div><div class="refsect1" lang="en"><a name="id2522942"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">log2pcap</code> reads in a 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>log2pcap</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="log2pcap.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>log2pcap &#8212; Extract network traces from Samba log files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">log2pcap</code> [-h] [-q] [logfile] [pcap_file]</p></div></div><div class="refsect1" lang="en"><a name="id2522946"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">log2pcap</code> reads in a 
 	samba log file and generates a pcap file (readable 
 	by most sniffers, such as ethereal or tcpdump) based on the packet 
 	dumps in the log file.</p><p>The log file must have a <em class="parameter"><code>log level</code></em> 
 	of at least <code class="constant">5</code> to get the SMB header/parameters 
 	right, <code class="constant">10</code> to get the first 512 data bytes of the 
 	packet and <code class="constant">50</code> to get the whole packet.
-	</p></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>If this parameter is 
+	</p></div><div class="refsect1" lang="en"><a name="id2483363"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>If this parameter is 
 		specified the output file will be a 
 		hex dump, in a format that is readable 
 		by the <span class="application">text2pcap</span> utility.</p></dd><dt><span class="term">-q</span></dt><dd><p>Be quiet. No warning messages about missing 
@@ -17,13 +17,13 @@
 		If this argument is not specified, output data will be written 
 		to stdout.
 		</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483561"></a><h2>EXAMPLES</h2><p>Extract all network traffic from all samba log files:</p><pre class="programlisting">
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483564"></a><h2>EXAMPLES</h2><p>Extract all network traffic from all samba log files:</p><pre class="programlisting">
 			<code class="prompt">$</code> log2pcap &lt; /var/log/* &gt; trace.pcap
 	</pre><p>Convert to pcap using text2pcap:</p><pre class="programlisting">
 	<code class="prompt">$</code> log2pcap -h samba.log | text2pcap -T 139,139 - trace.pcap
-	</pre></div><div class="refsect1" lang="en"><a name="id2483602"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483613"></a><h2>BUGS</h2><p>Only SMB data is extracted from the samba logs, no LDAP, 
+	</pre></div><div class="refsect1" lang="en"><a name="id2483605"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483616"></a><h2>BUGS</h2><p>Only SMB data is extracted from the samba logs, no LDAP, 
 	NetBIOS lookup or other data.</p><p>The generated TCP and IP headers don't contain a valid 
-	checksum.</p></div><div class="refsect1" lang="en"><a name="id2483629"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="text2pcap.1.html"><span class="citerefentry"><span class="refentrytitle">text2pcap</span>(1)</span></a>, <a class="citerefentry" href="ethereal.1.html"><span class="citerefentry"><span class="refentrytitle">ethereal</span>(1)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483652"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	checksum.</p></div><div class="refsect1" lang="en"><a name="id2483632"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="text2pcap.1.html"><span class="citerefentry"><span class="refentrytitle">text2pcap</span>(1)</span></a>, <a class="citerefentry" href="ethereal.1.html"><span class="citerefentry"><span class="refentrytitle">ethereal</span>(1)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483655"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>This manpage was written by Jelmer Vernooij.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/mount.cifs.8.html b/docs/htmldocs/manpages/mount.cifs.8.html
index 068b862447..b80db6c383 100644
--- a/docs/htmldocs/manpages/mount.cifs.8.html
+++ b/docs/htmldocs/manpages/mount.cifs.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>mount.cifs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="mount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>mount.cifs &#8212; mount using the Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">mount.cifs</code> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><a name="id2522927"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>mount.cifs mounts a Linux CIFS filesystem. It
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>mount.cifs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="mount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>mount.cifs &#8212; mount using the Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">mount.cifs</code> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><a name="id2522940"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>mount.cifs mounts a Linux CIFS filesystem. It
 is usually invoked indirectly by
 the <a class="citerefentry" href="mount.8.html"><span class="citerefentry"><span class="refentrytitle">mount</span>(8)</span></a> command when using the 
 "-t cifs" option. This command only works in Linux, and the kernel must
@@ -11,6 +11,9 @@ by the popular Open Source server Samba.
 	specified as <span class="emphasis"><em>service</em></span> (using //server/share syntax,
 	where "server" is the server name or IP address and "share" is the name
 	of the share) to the local directory <span class="emphasis"><em>mount-point</em></span>.
+	It is possible to set the mode for mount.cifs to setuid root to allow
+	non-root users to mount shares to directories for which they
+	have write permission.
 	</p><p>
 		Options to <span class="emphasis"><em>mount.cifs</em></span> are specified as a comma-separated
 list of key=value pairs. It is possible to send options other
@@ -25,7 +28,7 @@ kernel log.
 	</p><p>
 
 		<span class="emphasis"><em>modinfo cifs</em></span> command displays the version of cifs module.
-	</p></div><div class="refsect1" lang="en"><a name="id2483383"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">user=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>specifies the username to connect as. If
+	</p></div><div class="refsect1" lang="en"><a name="id2483524"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">user=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>specifies the username to connect as. If
 				this is not given, then the environment variable <span class="emphasis"><em>USER</em></span> is used. This option can also take the
 form "user%password" or "workgroup/user" or
 "workgroup/user%password" to allow the password and workgroup
@@ -54,23 +57,42 @@ below) or entered at the password prompt will be read correctly.
 This is preferred over having passwords in plaintext in a
 shared file, such as <code class="filename">/etc/fstab</code>. Be sure to protect any
 credentials file properly.
-		</p></dd><dt><span class="term">uid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the uid that will own all files or directories on the
-mounted filesystem when the server does not provide ownership
-information. It may be specified as either a username or a numeric uid.
-When not specified, the default is uid 0.  The mount.cifs helper must be
-at version 1.10 or higher to support specifying the uid in non-numeric
-form. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more
-information.  </p></dd><dt><span class="term">forceuid</span></dt><dd><p>instructs the client to ignore any uid provided by
-the server for files and directories and to always assign the owner to
-be the value of the uid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.</p></dd><dt><span class="term">gid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the gid that will own all files or
-directories on the mounted filesystem when the server does not provide
-ownership information.  It may be specified as either a groupname or a
-numeric gid.  When not specified, the default is gid 0. The mount.cifs
-helper must be at version 1.10 or higher to support specifying the gid
-in non-numeric form. See the section on FILE AND DIRECTORY OWNERSHIP AND
-PERMISSIONS below for more information.</p></dd><dt><span class="term">forcegid</span></dt><dd><p>instructs the client to ignore any gid provided by
-the server for files and directories and to always assign the owner to
-be the value of the gid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.</p></dd><dt><span class="term">port=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the port number on the server to attempt to contact to negotiate
+		</p></dd><dt><span class="term">uid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the uid that will own all files on
+	the mounted filesystem.
+	It may be specified as either a username or a numeric uid.
+	For mounts to servers which do support the CIFS Unix extensions, 
+        such as a properly configured Samba server, the server provides
+                the uid, gid and mode so this parameter should not be
+                specified unless the server and client uid and gid
+                numbering differ.  If the server and client are in the
+                same domain (e.g. running winbind or nss_ldap) and
+                the server supports the Unix Extensions then the uid
+                and gid can be retrieved from the server (and uid
+                and gid would not have to be specified on the mount.
+                For servers which do not support the CIFS Unix
+                extensions, the default uid (and gid) returned on lookup 
+                of existing files will be the uid (gid) of the person
+                who executed the mount (root, except when mount.cifs
+                is configured setuid for user mounts) unless the "uid="
+                (gid) mount option is specified.  For the uid (gid) of newly
+                created files and directories, ie files created since
+                the last mount of the server share, the expected uid
+                (gid) is cached as long as the inode remains in
+                memory on the client.   Also note that permission
+                checks (authorization checks) on accesses to a file occur
+                at the server, but there are cases in which an administrator
+                may want to restrict at the client as well.  For those
+                servers which do not report a uid/gid owner
+                (such as Windows), permissions can also be checked at the
+                client, and a crude form of client side permission checking
+                can be enabled by specifying file_mode and dir_mode on
+                the client.  Note that the mount.cifs helper must be
+                at version 1.10 or higher to support specifying the uid
+                (or gid) in non-numeric form.
+	</p></dd><dt><span class="term">gid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the gid that will own all files on
+the mounted filesystem.  It may be specified as either a groupname or a numeric 
+gid. For other considerations see the description of uid above. 
+		</p></dd><dt><span class="term">port=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the port number on the server to attempt to contact to negotiate
 CIFS support.  If the CIFS server is not listening on this port or
 if it is not specified, the default ports will be tried i.e. 
 port 445 is tried and if no response then port 139 is tried.
@@ -122,9 +144,7 @@ port 445 is tried and if no response then port 139 is tried.
                 access by the user doing the mount.
                 Note that this does not affect the normal ACL check on the
                 target machine done by the server software (of the server
-                ACL against the user name provided at mount time).</p></dd><dt><span class="term">dynperm</span></dt><dd><p>Instructs the server to maintain ownership and
-permissions in memory that can't be stored on the server. This information can disappear at any time (whenever the inode is flushed from the cache), so while this may help make some applications work, it's behavior is somewhat unreliable. See the section below on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS for more information.
-		</p></dd><dt><span class="term">directio</span></dt><dd><p>Do not do inode data caching on files opened on this mount.
+                ACL against the user name provided at mount time).</p></dd><dt><span class="term">directio</span></dt><dd><p>Do not do inode data caching on files opened on this mount.
                 This precludes mmaping files on this mount. In some cases
                 with fast networks and little or no caching benefits on the
                 client (e.g. when the application is doing large sequential
@@ -143,9 +163,7 @@ permissions in memory that can't be stored on the server. This information can d
                 (which also forbids creating and opening files
                 whose names contain any of these seven characters).
                 This has no effect if the server does not support
-                Unicode on the wire. Please note that the files created
-		with mapchars mount option may not be accessible
-		if the share is mounted without that option.</p></dd><dt><span class="term">nomapchars</span></dt><dd><p>Do not translate any of these seven characters (default)</p></dd><dt><span class="term">intr</span></dt><dd><p>currently unimplemented</p></dd><dt><span class="term">nointr</span></dt><dd><p>(default) currently unimplemented </p></dd><dt><span class="term">hard</span></dt><dd><p>The  program  accessing  a file on the cifs mounted file system will hang when the
+                Unicode on the wire.</p></dd><dt><span class="term">nomapchars</span></dt><dd><p>Do not translate any of these seven characters (default)</p></dd><dt><span class="term">intr</span></dt><dd><p>currently unimplemented</p></dd><dt><span class="term">nointr</span></dt><dd><p>(default) currently unimplemented </p></dd><dt><span class="term">hard</span></dt><dd><p>The  program  accessing  a file on the cifs mounted file system will hang when the
               server crashes.</p></dd><dt><span class="term">soft</span></dt><dd><p>(default) The  program  accessing  a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application.</p></dd><dt><span class="term">noacl</span></dt><dd><p>Do not allow POSIX ACL operations even if server would support them.</p><p>
 		The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers
 		version 3.0.10 and later.  Setting POSIX ACLs requires enabling both XATTR and
@@ -188,22 +206,8 @@ permissions in memory that can't be stored on the server. This information can d
 		later servers typically do support this (although not necessarily
 		on every local server filesystem). Parameter has no effect if
                 the server lacks support for returning inode numbers or equivalent.
-		</p></dd><dt><span class="term">noserverino</span></dt><dd><p>
-			Client generates inode numbers (rather than
-		using the actual one from the server) by default.
-		</p><p>
-			See section <span class="emphasis"><em>INODE NUMBERS</em></span> for
-		more information.
-		</p></dd><dt><span class="term">nounix</span></dt><dd><p>
-			Disable the CIFS Unix Extensions for this mount. This
-		can be useful in order to turn off multiple settings at once.
-		This includes POSIX acls, POSIX locks, POSIX paths, symlink
-		support and retrieving uids/gids/mode from the server. This
-		can also be useful to work around a bug in a server that
-		supports Unix Extensions.
-		</p><p>
-		See section <span class="emphasis"><em>INODE NUMBERS</em></span> for
-		more information.
+		</p></dd><dt><span class="term">noserverino</span></dt><dd><p>client generates inode numbers (rather than using the actual one
+                from the server) by default.
 		</p></dd><dt><span class="term">nouser_xattr</span></dt><dd><p>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </p></dd><dt><span class="term">rsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network read size (usually 16K). The client currently
                 can not use rsize larger than CIFSMaxBufSize. CIFSMaxBufSize
                 defaults to 16K and may be changed (from 8K to the maximum
@@ -219,56 +223,11 @@ permissions in memory that can't be stored on the server. This information can d
 
 		</p></dd><dt><span class="term">wsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network write size (default 57344)
                 maximum wsize currently allowed by CIFS is 57344 (fourteen
-                4096 byte pages)</p></dd><dt><span class="term">--verbose</span></dt><dd><p>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</p><p>mount -t cifs //server/share /mnt --verbose -o user=username</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532669"></a><h2>SERVICE FORMATTING AND DELIMITERS</h2><p>
+                4096 byte pages)</p></dd><dt><span class="term">--verbose</span></dt><dd><p>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</p><p>mount -t cifs //server/share /mnt --verbose -o user=username</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481455"></a><h2>SERVICE FORMATTING AND DELIMITERS</h2><p>
 		It's generally preferred to use forward slashes (/) as a delimiter in service names. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\) unconditionally. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can't be automatically converted in the same way.
 	</p><p>
 		mount.cifs will attempt to convert backslashes to forward slashes where it's able to do so, but it cannot do so in any path component following the sharename.
-	</p></div><div class="refsect1" lang="en"><a name="id2532692"></a><h2>INODE NUMBERS</h2><p>
-		When Unix Extensions are enabled, we use the actual inode
-	number provided by the server in response to the POSIX calls as an
-	inode number.
-	</p><p>
-		When Unix Extensions are disabled and "serverino" mount option
-	is enabled there is no way to get the server inode number. The
-	client typically maps the server-assigned "UniqueID" onto an inode
-	number.
-	</p><p>
-		Note that the UniqueID is a different value from the server
-	inode number. The UniqueID value is unique over the scope of the entire
-	server and is often greater than 2 power 32. This value often makes
-	programs that are not compiled with LFS (Large File Support), to
-	trigger a glibc EOVERFLOW error as this won't fit in the target
-	structure field. It is strongly recommended to compile your programs
-	with LFS support (i.e. with -D_FILE_OFFSET_BITS=64) to prevent this
-	problem. You can also use "noserverino" mount option to generate inode
-	numbers smaller than 2 power 32 on the client. But you may not be able
-	to detect hardlinks properly.
-	</p></div><div class="refsect1" lang="en"><a name="id2532725"></a><h2>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</h2><p> The core CIFS protocol does not provide unix ownership
-information or mode for files and directories. Because of this, files
-and directories will generally appear to be owned by whatever values the
-uid= or gid= options are set, and will have permissions set to the
-default file_mode and dir_mode for the mount. Attempting to change these
-values via chmod/chown will return success but have no effect.</p><p>When the client and server negotiate unix extensions,
-files and directories will be assigned the uid, gid, and mode provided
-by the server. Because CIFS mounts are generally single-user, and the
-same credentials are used no matter what user accesses the mount, newly
-created files and directories will generally be given ownership
-corresponding to whatever credentials were used to mount the
-share.</p><p>If the uid's and gid's being used do not match on the
-client and server, the forceuid and forcegid options may be helpful.
-Note however, that there is no corresponding option to override the
-mode. Permissions assigned to a file when forceuid or forcegid are in
-effect may not reflect the the real permissions.</p><p>When unix extensions are not negotiated, it's also
-possible to emulate them locally on the server using the "dynperm" mount
-option. When this mount option is in effect, newly created files and
-directories will receive what appear to be proper permissions. These
-permissions are not stored on the server however and can disappear at
-any time in the future (subject to the whims of the kernel flushing out
-the inode cache). In general, this mount option is discouraged.
-	</p><p>It's also possible to override permission checking on the client
-altogether via the noperm option. Server-side permission checks cannot be
-overriden. The permission checks done by the server will always correspond to
-the credentials used to mount the share, and not necessarily to the user who is accessing the share.</p></div><div class="refsect1" lang="en"><a name="id2532781"></a><h2>ENVIRONMENT VARIABLES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2481902"></a><h2>ENVIRONMENT VARIABLES</h2><p>
 		The variable <span class="emphasis"><em>USER</em></span> may contain the username of the
 person to be used to authenticate to the server.
 The variable can be used to set both username and
@@ -280,12 +239,7 @@ person using the client.
 		The variable <span class="emphasis"><em>PASSWD_FILE</em></span> may contain the pathname
 of a file to read the password from. A single line of input is
 read and used as the password.
-	</p></div><div class="refsect1" lang="en"><a name="id2532813"></a><h2>NOTES</h2><p>This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled. When installed as a setuid program, the program follows the conventions set forth by the mount program for user mounts.</p><p>
-	Some samba client tools like smbclient(8) honour client-side
-	configuration parameters present in smb.conf. Unlike those
-	client tools, <span class="emphasis"><em>mount.cifs</em></span> ignores smb.conf
-	completely.
-	</p></div><div class="refsect1" lang="en"><a name="id2532836"></a><h2>CONFIGURATION</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2481937"></a><h2>NOTES</h2><p>This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.</p></div><div class="refsect1" lang="en"><a name="id2481949"></a><h2>CONFIGURATION</h2><p>
 The primary mechanism for making configuration changes and for reading 
 debug information for the cifs vfs is via the Linux /proc filesystem.
 In the directory <code class="filename">/proc/fs/cifs</code> are various 
@@ -296,7 +250,7 @@ loaded.  These can be seen by running the modinfo utility against the file
 cifs.ko which will list the options that may be passed to cifs during module
 installation (device driver load).
 For more information see the kernel file <code class="filename">fs/cifs/README</code>.
-</p></div><div class="refsect1" lang="en"><a name="id2532866"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported.
+</p></div><div class="refsect1" lang="en"><a name="id2481982"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported.
 	</p><p>The credentials file does not handle usernames or passwords with
 		leading space.</p><p>
 Note that the typical response to a bug report is a suggestion
@@ -304,11 +258,11 @@ to try the latest version first. So please try doing that first,
 and always include which versions you use of relevant software
 when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and
 server type you are trying to contact.
-</p></div><div class="refsect1" lang="en"><a name="id2532891"></a><h2>VERSION</h2><p>This man page is correct for version 1.52 of 
-	the cifs vfs filesystem (roughly Linux kernel 2.6.24).</p></div><div class="refsect1" lang="en"><a name="id2532902"></a><h2>SEE ALSO</h2><p>
+</p></div><div class="refsect1" lang="en"><a name="id2482007"></a><h2>VERSION</h2><p>This man page is correct for version 1.52 of 
+	the cifs vfs filesystem (roughly Linux kernel 2.6.24).</p></div><div class="refsect1" lang="en"><a name="id2482018"></a><h2>SEE ALSO</h2><p>
 	Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
 	source tree may contain additional options and information.
-</p><p><a class="citerefentry" href="umount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">umount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2532923"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It 
+</p><p><a class="citerefentry" href="umount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">umount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2532776"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It 
 		was converted to Docbook/XML by Jelmer Vernooij.</p><p>The maintainer of the Linux cifs vfs and the userspace
 		tool <span class="emphasis"><em>mount.cifs</em></span> is <a class="ulink" href="mailto:sfrench@samba.org" target="_top">Steve French</a>.
 		The <a class="ulink" href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux CIFS Mailing list</a> 
diff --git a/docs/htmldocs/manpages/net.8.html b/docs/htmldocs/manpages/net.8.html
index 57915ac90f..c73c62d708 100644
--- a/docs/htmldocs/manpages/net.8.html
+++ b/docs/htmldocs/manpages/net.8.html
@@ -1,13 +1,13 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>net</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="net.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>net &#8212; Tool for administration of Samba and remote
 	CIFS servers.
-	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">net</code> {&lt;ads|rap|rpc&gt;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-d debuglevel] [-V] [--request-timeout seconds]</p></div></div><div class="refsect1" lang="en"><a name="id2483514"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The Samba net utility is meant to work just like the net utility 
+	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">net</code> {&lt;ads|rap|rpc&gt;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-d debuglevel] [-V] [--request-timeout seconds]</p></div></div><div class="refsect1" lang="en"><a name="id2483395"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The Samba net utility is meant to work just like the net utility 
 	available for windows and DOS. The first argument should be used 
 	to specify the protocol to use when executing a certain command. 
 	ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) 
 	clients and RPC can be used for NT4 and Windows 2000. If this 
 	argument is omitted, net will try to determine it automatically. 
 	Not all commands are available on all protocols.
-	</p></div><div class="refsect1" lang="en"><a name="id2483543"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
+	</p></div><div class="refsect1" lang="en"><a name="id2483548"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd><dt><span class="term">-w target-workgroup</span></dt><dd><p>
 		Sets target workgroup or domain. You have to specify 
 		either this option or the IP address or the name of a server.
@@ -57,18 +57,18 @@ investigating a problem. Levels above 3 are designed for
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
 override the <a class="link" href="smb.conf.5.html#" target="_top"></a> parameter
-in the <code class="filename">smb.conf</code> file.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481559"></a><h2>COMMANDS</h2><div class="refsect2" lang="en"><a name="id2481565"></a><h3>CHANGESECRETPW</h3><p>This command allows the Samba machine account password to be set from an external application
+in the <code class="filename">smb.conf</code> file.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481568"></a><h2>COMMANDS</h2><div class="refsect2" lang="en"><a name="id2481573"></a><h3>CHANGESECRETPW</h3><p>This command allows the Samba machine account password to be set from an external application
 to a machine account password that has already been stored in Active Directory. DO NOT USE this command
 unless you know exactly what you are doing. The use of this command requires that the force flag (-f)
 be used also. There will be NO command prompt. Whatever information is piped into stdin, either by
 typing at the command line or otherwise, will be stored as the literal machine password. Do NOT use
 this without care and attention as it will overwrite a legitimate machine password without warning.
 YOU HAVE BEEN WARNED.
-</p></div><div class="refsect2" lang="en"><a name="id2481586"></a><h3>TIME</h3><p>The <code class="literal">NET TIME</code> command allows you to view the time on a remote server
-	or synchronise the time on the local server with the time on the remote server.</p><div class="refsect3" lang="en"><a name="id2481603"></a><h4>TIME</h4><p>Without any options, the <code class="literal">NET TIME</code> command 
+</p></div><div class="refsect2" lang="en"><a name="id2481594"></a><h3>TIME</h3><p>The <code class="literal">NET TIME</code> command allows you to view the time on a remote server
+	or synchronise the time on the local server with the time on the remote server.</p><div class="refsect3" lang="en"><a name="id2481611"></a><h4>TIME</h4><p>Without any options, the <code class="literal">NET TIME</code> command 
 displays the time on the remote server.
-</p></div><div class="refsect3" lang="en"><a name="id2481619"></a><h4>TIME SYSTEM</h4><p>Displays the time on the remote server in a format ready for <code class="literal">/bin/date</code>.</p></div><div class="refsect3" lang="en"><a name="id2481636"></a><h4>TIME SET</h4><p>Tries to set the date and time of the local server to that on 
-the remote server using <code class="literal">/bin/date</code>. </p></div><div class="refsect3" lang="en"><a name="id2481654"></a><h4>TIME ZONE</h4><p>Displays the timezone in hours from GMT on the remote computer.</p></div></div><div class="refsect2" lang="en"><a name="id2481666"></a><h3>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [createupn=UPN] [createcomputer=OU] [options]</h3><p>
+</p></div><div class="refsect3" lang="en"><a name="id2481628"></a><h4>TIME SYSTEM</h4><p>Displays the time on the remote server in a format ready for <code class="literal">/bin/date</code>.</p></div><div class="refsect3" lang="en"><a name="id2481644"></a><h4>TIME SET</h4><p>Tries to set the date and time of the local server to that on 
+the remote server using <code class="literal">/bin/date</code>. </p></div><div class="refsect3" lang="en"><a name="id2481662"></a><h4>TIME ZONE</h4><p>Displays the timezone in hours from GMT on the remote computer.</p></div></div><div class="refsect2" lang="en"><a name="id2481674"></a><h3>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [createupn=UPN] [createcomputer=OU] [options]</h3><p>
 Join a domain.  If the account already exists on the server, and 
 [TYPE] is MEMBER, the machine will attempt to join automatically. 
 (Assuming that the machine has been created in server manager)
@@ -85,89 +85,81 @@ OU string reads from top to bottom without RDNs, and is delimited by
 a '/'.  Please note that '\' is used for escape by both the shell
 and ldap, so it may need to be doubled or quadrupled to pass through, 
 and it is not used as a delimiter.
-</p></div><div class="refsect2" lang="en"><a name="id2481700"></a><h3>[RPC] OLDJOIN [options]</h3><p>Join a domain. Use the OLDJOIN option to join the domain 
+</p></div><div class="refsect2" lang="en"><a name="id2481709"></a><h3>[RPC] OLDJOIN [options]</h3><p>Join a domain. Use the OLDJOIN option to join the domain 
 using the old style of domain joining - you need to create a trust 
-account in server manager first.</p></div><div class="refsect2" lang="en"><a name="id2481713"></a><h3>[RPC|ADS] USER</h3><div class="refsect3" lang="en"><a name="id2481718"></a><h4>[RPC|ADS] USER</h4><p>List all users</p></div><div class="refsect3" lang="en"><a name="id2481729"></a><h4>[RPC|ADS] USER DELETE <em class="replaceable"><code>target</code></em></h4><p>Delete specified user</p></div><div class="refsect3" lang="en"><a name="id2481741"></a><h4>[RPC|ADS] USER INFO <em class="replaceable"><code>target</code></em></h4><p>List the domain groups of the specified user.</p></div><div class="refsect3" lang="en"><a name="id2481754"></a><h4>[RPC|ADS] USER RENAME <em class="replaceable"><code>oldname</code></em> <em class="replaceable"><code>newname</code></em></h4><p>Rename specified user.</p></div><div class="refsect3" lang="en"><a name="id2481769"></a><h4>[RPC|ADS] USER ADD <em class="replaceable"><code>name</code></em> [password] [-F user flags] [-C comment]</h4><p>Add specified user.</p></div></div><div class="refsect2" lang="en"><a name="id2481784"></a><h3>[RPC|ADS] GROUP</h3><div class="refsect3" lang="en"><a name="id2481790"></a><h4>[RPC|ADS] GROUP [misc options] [targets]</h4><p>List user groups.</p></div><div class="refsect3" lang="en"><a name="id2481801"></a><h4>[RPC|ADS] GROUP DELETE <em class="replaceable"><code>name</code></em> [misc. options]</h4><p>Delete specified group.</p></div><div class="refsect3" lang="en"><a name="id2481814"></a><h4>[RPC|ADS] GROUP ADD <em class="replaceable"><code>name</code></em> [-C comment]</h4><p>Create specified group.</p></div></div><div class="refsect2" lang="en"><a name="id2481829"></a><h3>[RAP|RPC] SHARE</h3><div class="refsect3" lang="en"><a name="id2481834"></a><h4>[RAP|RPC] SHARE [misc. options] [targets]</h4><p>Enumerates all exported resources (network shares) on target server.</p></div><div class="refsect3" lang="en"><a name="id2481846"></a><h4>[RAP|RPC] SHARE ADD <em class="replaceable"><code>name=serverpath</code></em> [-C comment] [-M maxusers] [targets]</h4><p>Adds a share from a server (makes the export active). Maxusers 
+account in server manager first.</p></div><div class="refsect2" lang="en"><a name="id2481721"></a><h3>[RPC|ADS] USER</h3><div class="refsect3" lang="en"><a name="id2481727"></a><h4>[RPC|ADS] USER</h4><p>List all users</p></div><div class="refsect3" lang="en"><a name="id2481737"></a><h4>[RPC|ADS] USER DELETE <em class="replaceable"><code>target</code></em></h4><p>Delete specified user</p></div><div class="refsect3" lang="en"><a name="id2481749"></a><h4>[RPC|ADS] USER INFO <em class="replaceable"><code>target</code></em></h4><p>List the domain groups of the specified user.</p></div><div class="refsect3" lang="en"><a name="id2481762"></a><h4>[RPC|ADS] USER RENAME <em class="replaceable"><code>oldname</code></em> <em class="replaceable"><code>newname</code></em></h4><p>Rename specified user.</p></div><div class="refsect3" lang="en"><a name="id2481778"></a><h4>[RPC|ADS] USER ADD <em class="replaceable"><code>name</code></em> [password] [-F user flags] [-C comment]</h4><p>Add specified user.</p></div></div><div class="refsect2" lang="en"><a name="id2481793"></a><h3>[RPC|ADS] GROUP</h3><div class="refsect3" lang="en"><a name="id2481798"></a><h4>[RPC|ADS] GROUP [misc options] [targets]</h4><p>List user groups.</p></div><div class="refsect3" lang="en"><a name="id2481809"></a><h4>[RPC|ADS] GROUP DELETE <em class="replaceable"><code>name</code></em> [misc. options]</h4><p>Delete specified group.</p></div><div class="refsect3" lang="en"><a name="id2481823"></a><h4>[RPC|ADS] GROUP ADD <em class="replaceable"><code>name</code></em> [-C comment]</h4><p>Create specified group.</p></div></div><div class="refsect2" lang="en"><a name="id2481837"></a><h3>[RAP|RPC] SHARE</h3><div class="refsect3" lang="en"><a name="id2481843"></a><h4>[RAP|RPC] SHARE [misc. options] [targets]</h4><p>Enumerates all exported resources (network shares) on target server.</p></div><div class="refsect3" lang="en"><a name="id2481855"></a><h4>[RAP|RPC] SHARE ADD <em class="replaceable"><code>name=serverpath</code></em> [-C comment] [-M maxusers] [targets]</h4><p>Adds a share from a server (makes the export active). Maxusers 
 specifies the number of users that can be connected to the 
-share simultaneously.</p></div><div class="refsect3" lang="en"><a name="id2481863"></a><h4>SHARE DELETE <em class="replaceable"><code>sharename</code></em></h4><p>Delete specified share.</p></div></div><div class="refsect2" lang="en"><a name="id2481876"></a><h3>[RPC|RAP] FILE</h3><div class="refsect3" lang="en"><a name="id2481882"></a><h4>[RPC|RAP] FILE</h4><p>List all open files on remote server.</p></div><div class="refsect3" lang="en"><a name="id2481893"></a><h4>[RPC|RAP] FILE CLOSE <em class="replaceable"><code>fileid</code></em></h4><p>Close file with specified <em class="replaceable"><code>fileid</code></em> on 
-remote server.</p></div><div class="refsect3" lang="en"><a name="id2481909"></a><h4>[RPC|RAP] FILE INFO <em class="replaceable"><code>fileid</code></em></h4><p>
+share simultaneously.</p></div><div class="refsect3" lang="en"><a name="id2481871"></a><h4>SHARE DELETE <em class="replaceable"><code>sharename</code></em></h4><p>Delete specified share.</p></div></div><div class="refsect2" lang="en"><a name="id2481885"></a><h3>[RPC|RAP] FILE</h3><div class="refsect3" lang="en"><a name="id2481890"></a><h4>[RPC|RAP] FILE</h4><p>List all open files on remote server.</p></div><div class="refsect3" lang="en"><a name="id2481901"></a><h4>[RPC|RAP] FILE CLOSE <em class="replaceable"><code>fileid</code></em></h4><p>Close file with specified <em class="replaceable"><code>fileid</code></em> on 
+remote server.</p></div><div class="refsect3" lang="en"><a name="id2481917"></a><h4>[RPC|RAP] FILE INFO <em class="replaceable"><code>fileid</code></em></h4><p>
 Print information on specified <em class="replaceable"><code>fileid</code></em>. 
 Currently listed are: file-id, username, locks, path, permissions.
-</p></div><div class="refsect3" lang="en"><a name="id2481925"></a><h4>[RAP|RPC] FILE USER <em class="replaceable"><code>user</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2481934"></a><h4>[RAP|RPC] FILE USER <em class="replaceable"><code>user</code></em></h4><p>
 List files opened by specified <em class="replaceable"><code>user</code></em>.
 Please note that <code class="literal">net rap file user</code> does not work
 against Samba servers. 
-</p></div></div><div class="refsect2" lang="en"><a name="id2481949"></a><h3>SESSION</h3><div class="refsect3" lang="en"><a name="id2481955"></a><h4>RAP SESSION</h4><p>Without any other options, SESSION enumerates all active SMB/CIFS 
-sessions on the target server.</p></div><div class="refsect3" lang="en"><a name="id2481966"></a><h4>RAP SESSION DELETE|CLOSE <em class="replaceable"><code>CLIENT_NAME</code></em></h4><p>Close the specified sessions.</p></div><div class="refsect3" lang="en"><a name="id2481978"></a><h4>RAP SESSION INFO <em class="replaceable"><code>CLIENT_NAME</code></em></h4><p>Give a list with all the open files in specified session.</p></div></div><div class="refsect2" lang="en"><a name="id2481993"></a><h3>RAP SERVER <em class="replaceable"><code>DOMAIN</code></em></h3><p>List all servers in specified domain or workgroup. Defaults
-to local domain.</p></div><div class="refsect2" lang="en"><a name="id2482006"></a><h3>RAP DOMAIN</h3><p>Lists all domains and workgroups visible on the 
-current network.</p></div><div class="refsect2" lang="en"><a name="id2482018"></a><h3>RAP PRINTQ</h3><div class="refsect3" lang="en"><a name="id2482023"></a><h4>RAP PRINTQ INFO <em class="replaceable"><code>QUEUE_NAME</code></em></h4><p>Lists the specified print queue and print jobs on the server.
+</p></div></div><div class="refsect2" lang="en"><a name="id2481957"></a><h3>SESSION</h3><div class="refsect3" lang="en"><a name="id2481963"></a><h4>RAP SESSION</h4><p>Without any other options, SESSION enumerates all active SMB/CIFS 
+sessions on the target server.</p></div><div class="refsect3" lang="en"><a name="id2481975"></a><h4>RAP SESSION DELETE|CLOSE <em class="replaceable"><code>CLIENT_NAME</code></em></h4><p>Close the specified sessions.</p></div><div class="refsect3" lang="en"><a name="id2481987"></a><h4>RAP SESSION INFO <em class="replaceable"><code>CLIENT_NAME</code></em></h4><p>Give a list with all the open files in specified session.</p></div></div><div class="refsect2" lang="en"><a name="id2482001"></a><h3>RAP SERVER <em class="replaceable"><code>DOMAIN</code></em></h3><p>List all servers in specified domain or workgroup. Defaults
+to local domain.</p></div><div class="refsect2" lang="en"><a name="id2482015"></a><h3>RAP DOMAIN</h3><p>Lists all domains and workgroups visible on the 
+current network.</p></div><div class="refsect2" lang="en"><a name="id2482026"></a><h3>RAP PRINTQ</h3><div class="refsect3" lang="en"><a name="id2482032"></a><h4>RAP PRINTQ INFO <em class="replaceable"><code>QUEUE_NAME</code></em></h4><p>Lists the specified print queue and print jobs on the server.
 If the <em class="replaceable"><code>QUEUE_NAME</code></em> is omitted, all 
-queues are listed.</p></div><div class="refsect3" lang="en"><a name="id2532506"></a><h4>RAP PRINTQ DELETE <em class="replaceable"><code>JOBID</code></em></h4><p>Delete job with specified id.</p></div></div><div class="refsect2" lang="en"><a name="id2532518"></a><h3>RAP VALIDATE <em class="replaceable"><code>user</code></em> [<em class="replaceable"><code>password</code></em>]</h3><p>
+queues are listed.</p></div><div class="refsect3" lang="en"><a name="id2532513"></a><h4>RAP PRINTQ DELETE <em class="replaceable"><code>JOBID</code></em></h4><p>Delete job with specified id.</p></div></div><div class="refsect2" lang="en"><a name="id2532526"></a><h3>RAP VALIDATE <em class="replaceable"><code>user</code></em> [<em class="replaceable"><code>password</code></em>]</h3><p>
 Validate whether the specified user can log in to the 
 remote server. If the password is not specified on the commandline, it 
 will be prompted. 
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><a name="id2532541"></a><h3>RAP GROUPMEMBER</h3><div class="refsect3" lang="en"><a name="id2532547"></a><h4>RAP GROUPMEMBER LIST <em class="replaceable"><code>GROUP</code></em></h4><p>List all members of the specified group.</p></div><div class="refsect3" lang="en"><a name="id2532559"></a><h4>RAP GROUPMEMBER DELETE <em class="replaceable"><code>GROUP</code></em> <em class="replaceable"><code>USER</code></em></h4><p>Delete member from group.</p></div><div class="refsect3" lang="en"><a name="id2532574"></a><h4>RAP GROUPMEMBER ADD <em class="replaceable"><code>GROUP</code></em> <em class="replaceable"><code>USER</code></em></h4><p>Add member to group.</p></div></div><div class="refsect2" lang="en"><a name="id2532590"></a><h3>RAP ADMIN <em class="replaceable"><code>command</code></em></h3><p>Execute the specified <em class="replaceable"><code>command</code></em> on 
+</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><a name="id2532549"></a><h3>RAP GROUPMEMBER</h3><div class="refsect3" lang="en"><a name="id2532554"></a><h4>RAP GROUPMEMBER LIST <em class="replaceable"><code>GROUP</code></em></h4><p>List all members of the specified group.</p></div><div class="refsect3" lang="en"><a name="id2532567"></a><h4>RAP GROUPMEMBER DELETE <em class="replaceable"><code>GROUP</code></em> <em class="replaceable"><code>USER</code></em></h4><p>Delete member from group.</p></div><div class="refsect3" lang="en"><a name="id2532582"></a><h4>RAP GROUPMEMBER ADD <em class="replaceable"><code>GROUP</code></em> <em class="replaceable"><code>USER</code></em></h4><p>Add member to group.</p></div></div><div class="refsect2" lang="en"><a name="id2532598"></a><h3>RAP ADMIN <em class="replaceable"><code>command</code></em></h3><p>Execute the specified <em class="replaceable"><code>command</code></em> on 
 the remote server. Only works with OS/2 servers.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><a name="id2532610"></a><h3>RAP SERVICE</h3><div class="refsect3" lang="en"><a name="id2532616"></a><h4>RAP SERVICE START <em class="replaceable"><code>NAME</code></em> [arguments...]</h4><p>Start the specified service on the remote server. Not implemented yet.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><a name="id2532634"></a><h4>RAP SERVICE STOP</h4><p>Stop the specified service on the remote server.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><a name="id2532650"></a><h3>RAP PASSWORD <em class="replaceable"><code>USER</code></em> <em class="replaceable"><code>OLDPASS</code></em> <em class="replaceable"><code>NEWPASS</code></em></h3><p>
+</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><a name="id2532618"></a><h3>RAP SERVICE</h3><div class="refsect3" lang="en"><a name="id2532623"></a><h4>RAP SERVICE START <em class="replaceable"><code>NAME</code></em> [arguments...]</h4><p>Start the specified service on the remote server. Not implemented yet.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><a name="id2532642"></a><h4>RAP SERVICE STOP</h4><p>Stop the specified service on the remote server.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><a name="id2532658"></a><h3>RAP PASSWORD <em class="replaceable"><code>USER</code></em> <em class="replaceable"><code>OLDPASS</code></em> <em class="replaceable"><code>NEWPASS</code></em></h3><p>
 Change password of <em class="replaceable"><code>USER</code></em> from <em class="replaceable"><code>OLDPASS</code></em> to <em class="replaceable"><code>NEWPASS</code></em>.
-</p></div><div class="refsect2" lang="en"><a name="id2532678"></a><h3>LOOKUP</h3><div class="refsect3" lang="en"><a name="id2532683"></a><h4>LOOKUP HOST <em class="replaceable"><code>HOSTNAME</code></em> [<em class="replaceable"><code>TYPE</code></em>]</h4><p>
+</p></div><div class="refsect2" lang="en"><a name="id2532685"></a><h3>LOOKUP</h3><div class="refsect3" lang="en"><a name="id2532691"></a><h4>LOOKUP HOST <em class="replaceable"><code>HOSTNAME</code></em> [<em class="replaceable"><code>TYPE</code></em>]</h4><p>
 Lookup the IP address of the given host with the specified type (netbios suffix). 
 The type defaults to 0x20 (workstation).
-</p></div><div class="refsect3" lang="en"><a name="id2532701"></a><h4>LOOKUP LDAP [<em class="replaceable"><code>DOMAIN</code></em>]</h4><p>Give IP address of LDAP server of specified <em class="replaceable"><code>DOMAIN</code></em>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><a name="id2532718"></a><h4>LOOKUP KDC [<em class="replaceable"><code>REALM</code></em>]</h4><p>Give IP address of KDC for the specified <em class="replaceable"><code>REALM</code></em>.
-Defaults to local realm.</p></div><div class="refsect3" lang="en"><a name="id2532735"></a><h4>LOOKUP DC [<em class="replaceable"><code>DOMAIN</code></em>]</h4><p>Give IP's of Domain Controllers for specified <em class="replaceable"><code>
-DOMAIN</code></em>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><a name="id2532752"></a><h4>LOOKUP MASTER <em class="replaceable"><code>DOMAIN</code></em></h4><p>Give IP of master browser for specified <em class="replaceable"><code>DOMAIN</code></em>
-or workgroup. Defaults to local domain.</p></div></div><div class="refsect2" lang="en"><a name="id2532770"></a><h3>CACHE</h3><p>Samba uses a general caching interface called 'gencache'. It 
+</p></div><div class="refsect3" lang="en"><a name="id2532709"></a><h4>LOOKUP LDAP [<em class="replaceable"><code>DOMAIN</code></em>]</h4><p>Give IP address of LDAP server of specified <em class="replaceable"><code>DOMAIN</code></em>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><a name="id2532726"></a><h4>LOOKUP KDC [<em class="replaceable"><code>REALM</code></em>]</h4><p>Give IP address of KDC for the specified <em class="replaceable"><code>REALM</code></em>.
+Defaults to local realm.</p></div><div class="refsect3" lang="en"><a name="id2532743"></a><h4>LOOKUP DC [<em class="replaceable"><code>DOMAIN</code></em>]</h4><p>Give IP's of Domain Controllers for specified <em class="replaceable"><code>
+DOMAIN</code></em>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><a name="id2532760"></a><h4>LOOKUP MASTER <em class="replaceable"><code>DOMAIN</code></em></h4><p>Give IP of master browser for specified <em class="replaceable"><code>DOMAIN</code></em>
+or workgroup. Defaults to local domain.</p></div></div><div class="refsect2" lang="en"><a name="id2532777"></a><h3>CACHE</h3><p>Samba uses a general caching interface called 'gencache'. It 
 can be controlled using 'NET CACHE'.</p><p>All the timeout parameters support the suffixes:
 
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>s - Seconds</td></tr><tr><td>m - Minutes</td></tr><tr><td>h - Hours</td></tr><tr><td>d - Days</td></tr><tr><td>w - Weeks</td></tr></table><p>
 
-</p><div class="refsect3" lang="en"><a name="id2532805"></a><h4>CACHE ADD <em class="replaceable"><code>key</code></em> <em class="replaceable"><code>data</code></em> <em class="replaceable"><code>time-out</code></em></h4><p>Add specified key+data to the cache with the given timeout.</p></div><div class="refsect3" lang="en"><a name="id2532824"></a><h4>CACHE DEL <em class="replaceable"><code>key</code></em></h4><p>Delete key from the cache.</p></div><div class="refsect3" lang="en"><a name="id2532836"></a><h4>CACHE SET <em class="replaceable"><code>key</code></em> <em class="replaceable"><code>data</code></em> <em class="replaceable"><code>time-out</code></em></h4><p>Update data of existing cache entry.</p></div><div class="refsect3" lang="en"><a name="id2532855"></a><h4>CACHE SEARCH <em class="replaceable"><code>PATTERN</code></em></h4><p>Search for the specified pattern in the cache data.</p></div><div class="refsect3" lang="en"><a name="id2532868"></a><h4>CACHE LIST</h4><p>
+</p><div class="refsect3" lang="en"><a name="id2532813"></a><h4>CACHE ADD <em class="replaceable"><code>key</code></em> <em class="replaceable"><code>data</code></em> <em class="replaceable"><code>time-out</code></em></h4><p>Add specified key+data to the cache with the given timeout.</p></div><div class="refsect3" lang="en"><a name="id2532832"></a><h4>CACHE DEL <em class="replaceable"><code>key</code></em></h4><p>Delete key from the cache.</p></div><div class="refsect3" lang="en"><a name="id2532844"></a><h4>CACHE SET <em class="replaceable"><code>key</code></em> <em class="replaceable"><code>data</code></em> <em class="replaceable"><code>time-out</code></em></h4><p>Update data of existing cache entry.</p></div><div class="refsect3" lang="en"><a name="id2532863"></a><h4>CACHE SEARCH <em class="replaceable"><code>PATTERN</code></em></h4><p>Search for the specified pattern in the cache data.</p></div><div class="refsect3" lang="en"><a name="id2532875"></a><h4>CACHE LIST</h4><p>
 List all current items in the cache.
-</p></div><div class="refsect3" lang="en"><a name="id2532878"></a><h4>CACHE FLUSH</h4><p>Remove all the current items from the cache.</p></div></div><div class="refsect2" lang="en"><a name="id2532890"></a><h3>GETLOCALSID [DOMAIN]</h3><p>Prints the SID of the specified domain, or if the parameter is
-omitted, the SID of the local server.</p></div><div class="refsect2" lang="en"><a name="id2532901"></a><h3>SETLOCALSID S-1-5-21-x-y-z</h3><p>Sets SID for the local server to the specified SID.</p></div><div class="refsect2" lang="en"><a name="id2532912"></a><h3>GETDOMAINSID</h3><p>Prints the local machine SID and the SID of the current 
-domain.</p></div><div class="refsect2" lang="en"><a name="id2532922"></a><h3>SETDOMAINSID</h3><p>Sets the SID of the current domain.</p></div><div class="refsect2" lang="en"><a name="id2532932"></a><h3>GROUPMAP</h3><p>Manage the mappings between Windows group SIDs and UNIX groups.
+</p></div><div class="refsect3" lang="en"><a name="id2532886"></a><h4>CACHE FLUSH</h4><p>Remove all the current items from the cache.</p></div></div><div class="refsect2" lang="en"><a name="id2532897"></a><h3>GETLOCALSID [DOMAIN]</h3><p>Prints the SID of the specified domain, or if the parameter is
+omitted, the SID of the local server.</p></div><div class="refsect2" lang="en"><a name="id2532909"></a><h3>SETLOCALSID S-1-5-21-x-y-z</h3><p>Sets SID for the local server to the specified SID.</p></div><div class="refsect2" lang="en"><a name="id2532919"></a><h3>GETDOMAINSID</h3><p>Prints the local machine SID and the SID of the current 
+domain.</p></div><div class="refsect2" lang="en"><a name="id2532930"></a><h3>SETDOMAINSID</h3><p>Sets the SID of the current domain.</p></div><div class="refsect2" lang="en"><a name="id2532940"></a><h3>GROUPMAP</h3><p>Manage the mappings between Windows group SIDs and UNIX groups.
 Common options include:</p><div class="itemizedlist"><ul type="disc"><li><p>unixgroup - Name of the UNIX group</p></li><li><p>ntgroup - Name of the Windows NT group (must be
   resolvable to a SID</p></li><li><p>rid - Unsigned 32-bit integer</p></li><li><p>sid - Full SID in the form of "S-1-..."</p></li><li><p>type - Type of the group; either 'domain', 'local',
-  or 'builtin'</p></li><li><p>comment - Freeform text description of the group</p></li></ul></div><div class="refsect3" lang="en"><a name="id2532975"></a><h4>GROUPMAP ADD</h4><p>
+  or 'builtin'</p></li><li><p>comment - Freeform text description of the group</p></li></ul></div><div class="refsect3" lang="en"><a name="id2532983"></a><h4>GROUPMAP ADD</h4><p>
 Add a new group mapping entry:
 </p><pre class="programlisting">
 net groupmap add {rid=int|sid=string} unixgroup=string \
 	[type={domain|local}] [ntgroup=string] [comment=string]
 </pre><p>
-</p></div><div class="refsect3" lang="en"><a name="id2532992"></a><h4>GROUPMAP DELETE</h4><p>Delete a group mapping entry. If more than one group name matches, the first entry found is deleted.</p><p>net groupmap delete {ntgroup=string|sid=SID}</p></div><div class="refsect3" lang="en"><a name="id2533008"></a><h4>GROUPMAP MODIFY</h4><p>Update en existing group entry.</p><p>
+</p></div><div class="refsect3" lang="en"><a name="id2533000"></a><h4>GROUPMAP DELETE</h4><p>Delete a group mapping entry. If more than one group name matches, the first entry found is deleted.</p><p>net groupmap delete {ntgroup=string|sid=SID}</p></div><div class="refsect3" lang="en"><a name="id2533015"></a><h4>GROUPMAP MODIFY</h4><p>Update en existing group entry.</p><p>
 </p><pre class="programlisting">
 net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] \
        [comment=string] [type={domain|local}]
 </pre><p>
-</p></div><div class="refsect3" lang="en"><a name="id2533028"></a><h4>GROUPMAP LIST</h4><p>List existing group mapping entries.</p><p>net groupmap list [verbose] [ntgroup=string] [sid=SID]</p></div></div><div class="refsect2" lang="en"><a name="id2533043"></a><h3>MAXRID</h3><p>Prints out the highest RID currently in use on the local
+</p></div><div class="refsect3" lang="en"><a name="id2533035"></a><h4>GROUPMAP LIST</h4><p>List existing group mapping entries.</p><p>net groupmap list [verbose] [ntgroup=string] [sid=SID]</p></div></div><div class="refsect2" lang="en"><a name="id2533051"></a><h3>MAXRID</h3><p>Prints out the highest RID currently in use on the local
 server (by the active 'passdb backend').
-</p></div><div class="refsect2" lang="en"><a name="id2533055"></a><h3>RPC INFO</h3><p>Print information about the domain of the remote server,
+</p></div><div class="refsect2" lang="en"><a name="id2533062"></a><h3>RPC INFO</h3><p>Print information about the domain of the remote server,
 such as domain name, domain sid and number of users and groups.
-</p></div><div class="refsect2" lang="en"><a name="id2533066"></a><h3>[RPC|ADS] TESTJOIN</h3><p>Check whether participation in a domain is still valid.</p></div><div class="refsect2" lang="en"><a name="id2533077"></a><h3>[RPC|ADS] CHANGETRUSTPW</h3><p>Force change of domain trust password.</p></div><div class="refsect2" lang="en"><a name="id2533088"></a><h3>RPC TRUSTDOM</h3><div class="refsect3" lang="en"><a name="id2533093"></a><h4>RPC TRUSTDOM ADD <em class="replaceable"><code>DOMAIN</code></em></h4><p>Add a interdomain trust account for <em class="replaceable"><code>DOMAIN</code></em>. 
+</p></div><div class="refsect2" lang="en"><a name="id2533074"></a><h3>[RPC|ADS] TESTJOIN</h3><p>Check whether participation in a domain is still valid.</p></div><div class="refsect2" lang="en"><a name="id2533085"></a><h3>[RPC|ADS] CHANGETRUSTPW</h3><p>Force change of domain trust password.</p></div><div class="refsect2" lang="en"><a name="id2533095"></a><h3>RPC TRUSTDOM</h3><div class="refsect3" lang="en"><a name="id2533101"></a><h4>RPC TRUSTDOM ADD <em class="replaceable"><code>DOMAIN</code></em></h4><p>Add a interdomain trust account for <em class="replaceable"><code>DOMAIN</code></em>. 
 This is in fact a Samba account named <em class="replaceable"><code>DOMAIN$</code></em> 
 with the account flag <code class="constant">'I'</code> (interdomain trust account). 
-This is required for incoming trusts to work. It makes Samba be a
-trusted domain of the foreign (trusting) domain.
-Users of the Samba domain will be made available in the foreign domain.
 If the command is used against localhost it has the same effect as 
 <code class="literal">smbpasswd -a -i DOMAIN</code>. Please note that both commands
 expect a appropriate UNIX account. 
-</p></div><div class="refsect3" lang="en"><a name="id2533127"></a><h4>RPC TRUSTDOM DEL <em class="replaceable"><code>DOMAIN</code></em></h4><p>Remove interdomain trust account for 
+</p></div><div class="refsect3" lang="en"><a name="id2533132"></a><h4>RPC TRUSTDOM DEL <em class="replaceable"><code>DOMAIN</code></em></h4><p>Remove interdomain trust account for 
 <em class="replaceable"><code>DOMAIN</code></em>. If it is used against localhost 
 it has the same effect as <code class="literal">smbpasswd -x DOMAIN$</code>. 
-</p></div><div class="refsect3" lang="en"><a name="id2533149"></a><h4>RPC TRUSTDOM ESTABLISH <em class="replaceable"><code>DOMAIN</code></em></h4><p>
-Establish a trust relationship to a trusted domain. 
+</p></div><div class="refsect3" lang="en"><a name="id2533154"></a><h4>RPC TRUSTDOM ESTABLISH <em class="replaceable"><code>DOMAIN</code></em></h4><p>
+Establish a trust relationship to a trusting domain. 
 Interdomain account must already be created on the remote PDC.
-This is required for outgoing trusts to work. It makes Samba be a
-trusting domain of a foreign (trusted) domain.
-Users of the foreign domain will be made available in our domain.
-You'll need winbind and a working idmap config to make them
-appear in your system.
-</p></div><div class="refsect3" lang="en"><a name="id2533168"></a><h4>RPC TRUSTDOM REVOKE <em class="replaceable"><code>DOMAIN</code></em></h4><p>Abandon relationship to trusted domain</p></div><div class="refsect3" lang="en"><a name="id2533180"></a><h4>RPC TRUSTDOM LIST</h4><p>List all interdomain trust relationships.</p></div><div class="refsect3" lang="en"><a name="id2533190"></a><h4>RPC RIGHTS</h4><p>This subcommand is used to view and manage Samba's rights assignments (also 
+</p></div><div class="refsect3" lang="en"><a name="id2533168"></a><h4>RPC TRUSTDOM REVOKE <em class="replaceable"><code>DOMAIN</code></em></h4><p>Abandon relationship to trusted domain</p></div><div class="refsect3" lang="en"><a name="id2533180"></a><h4>RPC TRUSTDOM LIST</h4><p>List all current interdomain trust relationships.</p></div><div class="refsect3" lang="en"><a name="id2533191"></a><h4>RPC RIGHTS</h4><p>This subcommand is used to view and manage Samba's rights assignments (also 
 referred to as privileges).  There are three options currently available: 
 <em class="parameter"><code>list</code></em>, <em class="parameter"><code>grant</code></em>, and 
 <em class="parameter"><code>revoke</code></em>.  More details on Samba's privilege model and its use
-can be found in the Samba-HOWTO-Collection.</p></div></div><div class="refsect2" lang="en"><a name="id2533221"></a><h3>RPC ABORTSHUTDOWN</h3><p>Abort the shutdown of a remote server.</p></div><div class="refsect2" lang="en"><a name="id2533232"></a><h3>RPC SHUTDOWN [-t timeout] [-r] [-f] [-C message]</h3><p>Shut down the remote server.</p><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>
+can be found in the Samba-HOWTO-Collection.</p></div></div><div class="refsect2" lang="en"><a name="id2533222"></a><h3>RPC ABORTSHUTDOWN</h3><p>Abort the shutdown of a remote server.</p></div><div class="refsect2" lang="en"><a name="id2533232"></a><h3>RPC SHUTDOWN [-t timeout] [-r] [-f] [-C message]</h3><p>Shut down the remote server.</p><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>
 Reboot after shutdown.
 </p></dd><dt><span class="term">-f</span></dt><dd><p>
 Force shutting down all applications.
@@ -180,18 +172,18 @@ to run this against the PDC, from a Samba machine joined as a BDC. </p></div><di
 local server.  You need to run this against the PDC, from a Samba machine joined as a BDC. 
 </p></div><div class="refsect2" lang="en"><a name="id2533317"></a><h3>RPC VAMPIRE KEYTAB</h3><p>Dump remote SAM database to local Kerberos keytab file.
 </p></div><div class="refsect2" lang="en"><a name="id2533328"></a><h3>RPC VAMPIRE LDIF</h3><p>Dump remote SAM database to local LDIF file or standard output.
-</p></div><div class="refsect2" lang="en"><a name="id2533338"></a><h3>RPC GETSID</h3><p>Fetch domain SID and store it in the local <code class="filename">secrets.tdb</code>. </p></div><div class="refsect2" lang="en"><a name="id2533354"></a><h3>ADS LEAVE</h3><p>Make the remote host leave the domain it is part of. </p></div><div class="refsect2" lang="en"><a name="id2533365"></a><h3>ADS STATUS</h3><p>Print out status of machine account of the local machine in ADS.
+</p></div><div class="refsect2" lang="en"><a name="id2533339"></a><h3>RPC GETSID</h3><p>Fetch domain SID and store it in the local <code class="filename">secrets.tdb</code>. </p></div><div class="refsect2" lang="en"><a name="id2533354"></a><h3>ADS LEAVE</h3><p>Make the remote host leave the domain it is part of. </p></div><div class="refsect2" lang="en"><a name="id2533365"></a><h3>ADS STATUS</h3><p>Print out status of machine account of the local machine in ADS.
 Prints out quite some debug info. Aimed at developers, regular 
-users should use <code class="literal">NET ADS TESTJOIN</code>.</p></div><div class="refsect2" lang="en"><a name="id2533382"></a><h3>ADS PRINTER</h3><div class="refsect3" lang="en"><a name="id2533387"></a><h4>ADS PRINTER INFO [<em class="replaceable"><code>PRINTER</code></em>] [<em class="replaceable"><code>SERVER</code></em>]</h4><p>
+users should use <code class="literal">NET ADS TESTJOIN</code>.</p></div><div class="refsect2" lang="en"><a name="id2533382"></a><h3>ADS PRINTER</h3><div class="refsect3" lang="en"><a name="id2533388"></a><h4>ADS PRINTER INFO [<em class="replaceable"><code>PRINTER</code></em>] [<em class="replaceable"><code>SERVER</code></em>]</h4><p>
 Lookup info for <em class="replaceable"><code>PRINTER</code></em> on <em class="replaceable"><code>SERVER</code></em>. The printer name defaults to "*", the 
-server name defaults to the local host.</p></div><div class="refsect3" lang="en"><a name="id2533411"></a><h4>ADS PRINTER PUBLISH <em class="replaceable"><code>PRINTER</code></em></h4><p>Publish specified printer using ADS.</p></div><div class="refsect3" lang="en"><a name="id2533424"></a><h4>ADS PRINTER REMOVE <em class="replaceable"><code>PRINTER</code></em></h4><p>Remove specified printer from ADS directory.</p></div></div><div class="refsect2" lang="en"><a name="id2533437"></a><h3>ADS SEARCH <em class="replaceable"><code>EXPRESSION</code></em> <em class="replaceable"><code>ATTRIBUTES...</code></em></h3><p>Perform a raw LDAP search on a ADS server and dump the results. The 
+server name defaults to the local host.</p></div><div class="refsect3" lang="en"><a name="id2533412"></a><h4>ADS PRINTER PUBLISH <em class="replaceable"><code>PRINTER</code></em></h4><p>Publish specified printer using ADS.</p></div><div class="refsect3" lang="en"><a name="id2533424"></a><h4>ADS PRINTER REMOVE <em class="replaceable"><code>PRINTER</code></em></h4><p>Remove specified printer from ADS directory.</p></div></div><div class="refsect2" lang="en"><a name="id2533438"></a><h3>ADS SEARCH <em class="replaceable"><code>EXPRESSION</code></em> <em class="replaceable"><code>ATTRIBUTES...</code></em></h3><p>Perform a raw LDAP search on a ADS server and dump the results. The 
 expression is a standard LDAP search expression, and the 
 attributes are a list of LDAP fields to show in the results.</p><p>Example: <strong class="userinput"><code>net ads search '(objectCategory=group)' sAMAccountName</code></strong>
 </p></div><div class="refsect2" lang="en"><a name="id2533465"></a><h3>ADS DN <em class="replaceable"><code>DN</code></em> <em class="replaceable"><code>(attributes)</code></em></h3><p>
 Perform a raw LDAP search on a ADS server and dump the results. The 
 DN standard LDAP DN, and the attributes are a list of LDAP fields 
 to show in the result. 
-</p><p>Example: <strong class="userinput"><code>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</code></strong></p></div><div class="refsect2" lang="en"><a name="id2533491"></a><h3>ADS WORKGROUP</h3><p>Print out workgroup name for specified kerberos realm.</p></div><div class="refsect2" lang="en"><a name="id2533502"></a><h3>SAM CREATEBUILTINGROUP &lt;NAME&gt;</h3><p>
+</p><p>Example: <strong class="userinput"><code>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</code></strong></p></div><div class="refsect2" lang="en"><a name="id2533492"></a><h3>ADS WORKGROUP</h3><p>Print out workgroup name for specified kerberos realm.</p></div><div class="refsect2" lang="en"><a name="id2533502"></a><h3>SAM CREATEBUILTINGROUP &lt;NAME&gt;</h3><p>
 (Re)Create a BUILTIN group.
 Only a wellknown set of BUILTIN groups can be created with this command.
 This is the list of currently recognized group names: Administrators,
@@ -209,15 +201,15 @@ configured. The group gid will be allocated out of the winbindd range.
 </p></div><div class="refsect2" lang="en"><a name="id2533535"></a><h3>SAM DELETELOCALGROUP &lt;NAME&gt;</h3><p>
 Delete an existing LOCAL group (also known as Alias).
 
-</p></div><div class="refsect2" lang="en"><a name="id2533546"></a><h3>SAM MAPUNIXGROUP &lt;NAME&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533547"></a><h3>SAM MAPUNIXGROUP &lt;NAME&gt;</h3><p>
 Map an existing Unix group and make it a Domain Group, the domain group
 will have the same name.
-</p></div><div class="refsect2" lang="en"><a name="id2533558"></a><h3>SAM UNMAPUNIXGROUP &lt;NAME&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533559"></a><h3>SAM UNMAPUNIXGROUP &lt;NAME&gt;</h3><p>
 Remove an existing group mapping entry.
 </p></div><div class="refsect2" lang="en"><a name="id2533570"></a><h3>SAM ADDMEM &lt;GROUP&gt; &lt;MEMBER&gt;</h3><p>
 Add a member to a Local group. The group can be specified only by name,
 the member can be specified by name or SID.
-</p></div><div class="refsect2" lang="en"><a name="id2533582"></a><h3>SAM DELMEM  &lt;GROUP&gt; &lt;MEMBER&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533583"></a><h3>SAM DELMEM  &lt;GROUP&gt; &lt;MEMBER&gt;</h3><p>
 Remove a member from a Local group. The group and the member must be
 specified by name.
 </p></div><div class="refsect2" lang="en"><a name="id2533595"></a><h3>SAM LISTMEM &lt;GROUP&gt;</h3><p>
@@ -229,7 +221,7 @@ the rid and description is also provided for each account.
 List all available privileges.
 </p></div><div class="refsect2" lang="en"><a name="id2533630"></a><h3>SAM RIGHTS GRANT &lt;NAME&gt; &lt;PRIVILEGE&gt;</h3><p>
 Grant one or more privileges to a user.
-</p></div><div class="refsect2" lang="en"><a name="id2533641"></a><h3>SAM RIGHTS REVOKE &lt;NAME&gt; &lt;PRIVILEGE&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533642"></a><h3>SAM RIGHTS REVOKE &lt;NAME&gt; &lt;PRIVILEGE&gt;</h3><p>
 Revoke one or more privileges from a user.
 </p></div><div class="refsect2" lang="en"><a name="id2533653"></a><h3>SAM SHOW &lt;NAME&gt;</h3><p>
 Show the full DOMAIN\\NAME the SID and the type for the corresponding
@@ -240,9 +232,9 @@ Set the home directory for a user account.
 Set the profile path for a user account.
 </p></div><div class="refsect2" lang="en"><a name="id2533686"></a><h3>SAM SET COMMENT &lt;NAME&gt; &lt;COMMENT&gt;</h3><p>
 Set the comment for a user or group account.
-</p></div><div class="refsect2" lang="en"><a name="id2533697"></a><h3>SAM SET FULLNAME &lt;NAME&gt; &lt;FULL NAME&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533698"></a><h3>SAM SET FULLNAME &lt;NAME&gt; &lt;FULL NAME&gt;</h3><p>
 Set the full name for a user account.
-</p></div><div class="refsect2" lang="en"><a name="id2533708"></a><h3>SAM SET LOGONSCRIPT &lt;NAME&gt; &lt;SCRIPT&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533709"></a><h3>SAM SET LOGONSCRIPT &lt;NAME&gt; &lt;SCRIPT&gt;</h3><p>
 Set the logon script for a user account.
 </p></div><div class="refsect2" lang="en"><a name="id2533720"></a><h3>SAM SET HOMEDRIVE &lt;NAME&gt; &lt;DRIVE&gt;</h3><p>
 Set the home drive for a user account.
@@ -252,7 +244,7 @@ Set the workstations a user account is allowed to log in from.
 Set the "disabled" flag for a user account.
 </p></div><div class="refsect2" lang="en"><a name="id2533754"></a><h3>SAM SET PWNOTREQ &lt;NAME&gt;</h3><p>
 Set the "password not required" flag for a user account.
-</p></div><div class="refsect2" lang="en"><a name="id2533765"></a><h3>SAM SET AUTOLOCK &lt;NAME&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533766"></a><h3>SAM SET AUTOLOCK &lt;NAME&gt;</h3><p>
 Set the "autolock" flag for a user account.
 </p></div><div class="refsect2" lang="en"><a name="id2533777"></a><h3>SAM SET PWNOEXP &lt;NAME&gt;</h3><p>
 Set the "password do not expire" flag for a user account.
@@ -260,16 +252,16 @@ Set the "password do not expire" flag for a user account.
 Set or unset the "password must change" flag for a user account.
 </p></div><div class="refsect2" lang="en"><a name="id2533800"></a><h3>SAM POLICY LIST</h3><p>
 List the available account policies.
-</p></div><div class="refsect2" lang="en"><a name="id2533810"></a><h3>SAM POLICY SHOW &lt;account policy&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533811"></a><h3>SAM POLICY SHOW &lt;account policy&gt;</h3><p>
 Show the account policy value.
-</p></div><div class="refsect2" lang="en"><a name="id2533821"></a><h3>SAM POLICY SET &lt;account policy&gt; &lt;value&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533822"></a><h3>SAM POLICY SET &lt;account policy&gt; &lt;value&gt;</h3><p>
 Set a value for the account policy.
 Valid values can be: "forever", "never", "off", or a number.
 </p></div><div class="refsect2" lang="en"><a name="id2533834"></a><h3>SAM PROVISION</h3><p>
 Only available if ldapsam:editposix is set and winbindd is running.
 Properly populates the ldap tree with the basic accounts (Administrator)
 and groups (Domain Users, Domain Admins, Domain Guests) on the ldap tree.
-</p></div><div class="refsect2" lang="en"><a name="id2533847"></a><h3>IDMAP DUMP &lt;local tdb file name&gt;</h3><p>
+</p></div><div class="refsect2" lang="en"><a name="id2533848"></a><h3>IDMAP DUMP &lt;local tdb file name&gt;</h3><p>
 Dumps the mappings contained in the local tdb file specified.
 This command is useful to dump only the mappings produced by the idmap_tdb backend.
 </p></div><div class="refsect2" lang="en"><a name="id2533861"></a><h3>IDMAP RESTORE [input file]</h3><p>
@@ -307,7 +299,7 @@ can create user defined shares on demand using the commands below.
 
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] - to add or change a user defined share.</td></tr><tr><td>net usershare delete sharename - to delete a user defined share.</td></tr><tr><td>net usershare info [-l|--long] [wildcard sharename] - to print info about a user defined share.</td></tr><tr><td>net usershare list [-l|--long] [wildcard sharename] - to list user defined shares.</td></tr></table><p>
 
-</p><div class="refsect3" lang="en"><a name="id2533944"></a><h4>USERSHARE ADD <em class="replaceable"><code>sharename</code></em> <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>[comment]</code></em> <em class="replaceable"><code>[acl]</code></em> <em class="replaceable"><code>[guest_ok=[y|n]]</code></em></h4><p>
+</p><div class="refsect3" lang="en"><a name="id2533959"></a><h4>USERSHARE ADD <em class="replaceable"><code>sharename</code></em> <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>[comment]</code></em> <em class="replaceable"><code>[acl]</code></em> <em class="replaceable"><code>[guest_ok=[y|n]]</code></em></h4><p>
 Add or replace a new user defined share, with name "sharename".
 </p><p>
 "path" specifies the absolute pathname on the system to be exported.
@@ -344,11 +336,11 @@ sharename as the one you wish to modify and specify the new options
 you wish. The Samba smbd daemon notices user defined share modifications
 at connect time so will see the change immediately, there is no need
 to restart smbd on adding, deleting or changing a user defined share.
-</div><div class="refsect3" lang="en"><a name="id2534016"></a><h4>USERSHARE DELETE <em class="replaceable"><code>sharename</code></em></h4><p>
+</div><div class="refsect3" lang="en"><a name="id2534031"></a><h4>USERSHARE DELETE <em class="replaceable"><code>sharename</code></em></h4><p>
 Deletes the user defined share by name. The Samba smbd daemon
 immediately notices this change, although it will not disconnect
 any users currently connected to the deleted share.
-</p></div><div class="refsect3" lang="en"><a name="id2534031"></a><h4>USERSHARE INFO <em class="replaceable"><code>[-l|--long]</code></em> <em class="replaceable"><code>[wildcard sharename]</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534046"></a><h4>USERSHARE INFO <em class="replaceable"><code>[-l|--long]</code></em> <em class="replaceable"><code>[wildcard sharename]</code></em></h4><p>
 Get info on user defined shares owned by the current user matching the given pattern, or all users.
 </p><p>
 net usershare info on its own dumps out info on the user defined shares that were
@@ -367,7 +359,7 @@ guest_ok=n
 
 And is a list of the current settings of the user defined share that can be
 modified by the "net usershare add" command.
-</p></div><div class="refsect3" lang="en"><a name="id2534065"></a><h4>USERSHARE LIST <em class="replaceable"><code>[-l|--long]</code></em> <em class="replaceable"><code>wildcard sharename</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534086"></a><h4>USERSHARE LIST <em class="replaceable"><code>[-l|--long]</code></em> <em class="replaceable"><code>wildcard sharename</code></em></h4><p>
 List all the user defined shares owned by the current user matching the given pattern, or all users.
 </p><p>
 net usershare list on its own list out the names of the user defined shares that were
@@ -375,7 +367,7 @@ created by the current user, or restricts the list to share names that match the
 wildcard pattern ('*' matches one or more characters, '?' matches only one character).
 If the '-l' or '--long' option is also given, it includes the names of user defined
 shares created by other users.
-</p></div></div><div class="refsect2" lang="en"><a name="id2534092"></a><h3>CONF</h3><p>Starting with version 3.2.0, a Samba server can be configured by data
+</p></div></div><div class="refsect2" lang="en"><a name="id2534113"></a><h3>CONF</h3><p>Starting with version 3.2.0, a Samba server can be configured by data
 stored in registry. This configuration data can be edited with the new "net
 conf" commands.
 </p><p>
@@ -393,10 +385,10 @@ See the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry
 format.</td></tr><tr><td>net conf import - Import configuration from file in smb.conf
 format.</td></tr><tr><td>net conf listshares - List the registry shares.</td></tr><tr><td>net conf drop - Delete the complete configuration from
 registry.</td></tr><tr><td>net conf showshare - Show the definition of a registry share.</td></tr><tr><td>net conf addshare - Create a new registry share.</td></tr><tr><td>net conf delshare - Delete a registry share.</td></tr><tr><td>net conf setparm - Store a parameter.</td></tr><tr><td>net conf getparm - Retrieve the value of a parameter.</td></tr><tr><td>net conf delparm - Delete a parameter.</td></tr><tr><td>net conf getincludes - Show the includes of a share definition.</td></tr><tr><td>net conf setincludes - Set includes for a share.</td></tr><tr><td>net conf delincludes - Delete includes from a share definition.</td></tr></table><p>
-</p><div class="refsect3" lang="en"><a name="id2534213"></a><h4>CONF LIST</h4><p>
+</p><div class="refsect3" lang="en"><a name="id2534234"></a><h4>CONF LIST</h4><p>
 Print the configuration data stored in the registry in a smb.conf-like format to
 standard output.
-</p></div><div class="refsect3" lang="en"><a name="id2534224"></a><h4>CONF IMPORT <em class="replaceable"><code>[--test|-T]</code></em> <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>[section]</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534245"></a><h4>CONF IMPORT <em class="replaceable"><code>[--test|-T]</code></em> <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>[section]</code></em></h4><p>
 This command imports configuration from a file in smb.conf format.
 If a section encountered in the input file is present in registry,
 its contents is replaced. Sections of registry configuration that have
@@ -406,30 +398,30 @@ Optionally, a section may be specified to restrict the effect of the
 import command to that specific section. A test mode is enabled by specifying
 the parameter "-T" on the commandline. In test mode, no changes are made to the
 registry, and the resulting configuration is printed to standard output instead.
-</p></div><div class="refsect3" lang="en"><a name="id2534254"></a><h4>CONF LISTSHARES</h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534286"></a><h4>CONF LISTSHARES</h4><p>
 List the names of the shares defined in registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534264"></a><h4>CONF DROP</h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534296"></a><h4>CONF DROP</h4><p>
 Delete the complete configuration data from registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534275"></a><h4>CONF SHOWSHARE <em class="replaceable"><code>sharename</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534307"></a><h4>CONF SHOWSHARE <em class="replaceable"><code>sharename</code></em></h4><p>
 Show the definition of the share or section specified. It is valid to specify
 "global" as sharename to retrieve the global configuration options from
 registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534289"></a><h4>CONF ADDSHARE <em class="replaceable"><code>sharename</code></em> <em class="replaceable"><code>path</code></em> [<em class="replaceable"><code>writeable={y|N}</code></em> [<em class="replaceable"><code>guest_ok={y|N}</code></em> [<em class="replaceable"><code>comment</code></em>]]] </h4><p>Create a new share definition in registry.
+</p></div><div class="refsect3" lang="en"><a name="id2534321"></a><h4>CONF ADDSHARE <em class="replaceable"><code>sharename</code></em> <em class="replaceable"><code>path</code></em> [<em class="replaceable"><code>writeable={y|N}</code></em> [<em class="replaceable"><code>guest_ok={y|N}</code></em> [<em class="replaceable"><code>comment</code></em>]]] </h4><p>Create a new share definition in registry.
 The sharename and path have to be given. The share name may
 <span class="emphasis"><em>not</em></span> be "global". Optionally, values for the very
 common options "writeable", "guest ok" and a "comment" may be specified.
 The same result may be obtained by a sequence of "net conf setparm"
 commands.
-</p></div><div class="refsect3" lang="en"><a name="id2534323"></a><h4>CONF DELSHARE <em class="replaceable"><code>sharename</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534356"></a><h4>CONF DELSHARE <em class="replaceable"><code>sharename</code></em></h4><p>
 Delete a share definition from registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534336"></a><h4>CONF SETPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em> <em class="replaceable"><code>value</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534368"></a><h4>CONF SETPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em> <em class="replaceable"><code>value</code></em></h4><p>
 Store a parameter in registry. The section may be global or a sharename.
 The section is created if it does not exist yet.
-</p></div><div class="refsect3" lang="en"><a name="id2534356"></a><h4>CONF GETPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534388"></a><h4>CONF GETPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em></h4><p>
 Show a parameter stored in registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534372"></a><h4>CONF DELPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534404"></a><h4>CONF DELPARM <em class="replaceable"><code>section</code></em> <em class="replaceable"><code>parameter</code></em></h4><p>
 Delete a parameter stored in registry.
-</p></div><div class="refsect3" lang="en"><a name="id2534388"></a><h4>CONF GETINCLUDES <em class="replaceable"><code>section</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534420"></a><h4>CONF GETINCLUDES <em class="replaceable"><code>section</code></em></h4><p>
 Get the list of includes for the provided section (global or share).
 </p><p>
 Note that due to the nature of the registry database and the nature of include directives,
@@ -445,13 +437,13 @@ per share, and this list is evaluated after all the parameters of the share.
 Further note that currently, only files can be included from registry
 configuration. In the future, there will be the ability to include configuration
 data from other registry keys.
-</p></div><div class="refsect3" lang="en"><a name="id2534423"></a><h4>CONF SETINCLUDES <em class="replaceable"><code>section</code></em> [<em class="replaceable"><code>filename</code></em>]+</h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534455"></a><h4>CONF SETINCLUDES <em class="replaceable"><code>section</code></em> [<em class="replaceable"><code>filename</code></em>]+</h4><p>
 Set the list of includes for the provided section (global or share) to the given
 list of one or more filenames. The filenames may contain the usual smb.conf
 macros like %I.
-</p></div><div class="refsect3" lang="en"><a name="id2534442"></a><h4>CONF DELINCLUDES <em class="replaceable"><code>section</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534474"></a><h4>CONF DELINCLUDES <em class="replaceable"><code>section</code></em></h4><p>
 Delete the list of includes from the provided section (global or share).
-</p></div></div><div class="refsect2" lang="en"><a name="id2534456"></a><h3>EVENTLOG</h3><p>Starting with version 3.4.0 net can read, dump, import and export native
+</p></div></div><div class="refsect2" lang="en"><a name="id2534488"></a><h3>EVENTLOG</h3><p>Starting with version 3.4.0 net can read, dump, import and export native
 win32 eventlog files (usually *.evt). evt files are used by the native Windows eventviewer tools.
 </p><p>
 The import and export of evt files can only succeed when <em class="parameter"><code>eventlog list</code></em> is used in
@@ -461,25 +453,25 @@ See the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>net eventlog dump - Dump a eventlog *.evt file on the screen.</td></tr><tr><td>net eventlog import - Import a eventlog *.evt into the samba internal
 tdb based representation of eventlogs.</td></tr><tr><td>net eventlog export - Export the samba internal tdb based representation
 of eventlogs into an eventlog *.evt file.</td></tr></table><p>
-</p><div class="refsect3" lang="en"><a name="id2534511"></a><h4>EVENTLOG DUMP <em class="replaceable"><code>filename</code></em></h4><p>
+</p><div class="refsect3" lang="en"><a name="id2534543"></a><h4>EVENTLOG DUMP <em class="replaceable"><code>filename</code></em></h4><p>
 Prints a eventlog *.evt file to standard output.
-</p></div><div class="refsect3" lang="en"><a name="id2534523"></a><h4>EVENTLOG IMPORT <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>eventlog</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534555"></a><h4>EVENTLOG IMPORT <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>eventlog</code></em></h4><p>
 Imports a eventlog *.evt file defined by <em class="replaceable"><code>filename</code></em> into the
 samba internal tdb representation of eventlog defined by <em class="replaceable"><code>eventlog</code></em>.
 <em class="replaceable"><code>eventlog</code></em> needs to part of the <em class="parameter"><code>eventlog list</code></em>
 defined in smb.conf.
 See the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> manpage for details.
-</p></div><div class="refsect3" lang="en"><a name="id2534563"></a><h4>EVENTLOG EXPORT <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>eventlog</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534595"></a><h4>EVENTLOG EXPORT <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>eventlog</code></em></h4><p>
 Exports the samba internal tdb representation of eventlog defined by <em class="replaceable"><code>eventlog</code></em>
 to a eventlog *.evt file defined by <em class="replaceable"><code>filename</code></em>.
 <em class="replaceable"><code>eventlog</code></em> needs to part of the <em class="parameter"><code>eventlog list</code></em>
 defined in smb.conf.
 See the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> manpage for details.
-</p></div></div><div class="refsect2" lang="en"><a name="id2534604"></a><h3>DOM</h3><p>Starting with version 3.2.0 Samba has support for remote join and unjoin APIs, both client and server-side. Windows supports remote join capabilities since Windows 2000.
+</p></div></div><div class="refsect2" lang="en"><a name="id2534636"></a><h3>DOM</h3><p>Starting with version 3.2.0 Samba has support for remote join and unjoin APIs, both client and server-side. Windows supports remote join capabilities since Windows 2000.
 </p><p>In order for Samba to be joined or unjoined remotely an account must be used that is either member of the Domain Admins group, a member of the local Administrators group or a user that is granted the SeMachineAccountPrivilege privilege.
 </p><p>The client side support for remote join is implemented in the net dom commands which are:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>net dom join - Join a remote computer into a domain.</td></tr><tr><td>net dom unjoin - Unjoin a remote computer from a domain.</td></tr><tr><td>net dom renamecomputer - Renames a remote computer joined to a domain.</td></tr></table><p>
-</p><div class="refsect3" lang="en"><a name="id2534646"></a><h4>DOM JOIN	<em class="replaceable"><code>domain=DOMAIN</code></em> <em class="replaceable"><code>ou=OU</code></em> <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
+</p><div class="refsect3" lang="en"><a name="id2534678"></a><h4>DOM JOIN	<em class="replaceable"><code>domain=DOMAIN</code></em> <em class="replaceable"><code>ou=OU</code></em> <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
 Joins a computer into a domain. This command supports the following additional parameters:
 </p><div class="itemizedlist"><ul type="disc"><li><p><em class="replaceable"><code>DOMAIN</code></em> can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains. As in Windows, it is also possible to control which Domain Controller to use. This can be achieved by appending the DC name using the \ separator character. Example: MYDOM\MYDC. The <em class="replaceable"><code>DOMAIN</code></em> parameter cannot be NULL.</p></li><li><p><em class="replaceable"><code>OU</code></em> can be set to a RFC 1779 LDAP DN, like <span class="emphasis"><em>ou=mymachines,cn=Users,dc=example,dc=com</em></span> in order to create the machine account in a non-default LDAP containter. This optional parameter is only supported when joining Active Directory Domains.</p></li><li><p><em class="replaceable"><code>ACCOUNT</code></em> defines a domain account that will be used to join the machine to the domain. This domain account needs to have sufficient privileges to join machines.</p></li><li><p><em class="replaceable"><code>PASSWORD</code></em> defines the password for the domain account defined with <em class="replaceable"><code>ACCOUNT</code></em>.</p></li><li><p><em class="replaceable"><code>REBOOT</code></em> is an optional parameter that can be set to reboot the remote machine after successful join to the domain.</p></li></ul></div><p>
 Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to join. These additional parameters include: -S computer and -U user.
@@ -488,7 +480,7 @@ Note that you also need to use standard net parameters to connect and authentica
 	net dom join -S xp -U XP\\administrator%secret domain=MYDOM account=MYDOM\\administrator password=topsecret reboot.
 </p><p>
 This example would connect to a computer named XP as the local administrator using password secret, and join the computer into a domain called MYDOM using the MYDOM domain administrator account and password topsecret. After successful join, the computer would reboot.
-</p></div><div class="refsect3" lang="en"><a name="id2534752"></a><h4>DOM UNJOIN <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534784"></a><h4>DOM UNJOIN <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
 Unjoins a computer from a domain. This command supports the following additional parameters:
 </p><div class="itemizedlist"><ul type="disc"><li><p><em class="replaceable"><code>ACCOUNT</code></em> defines a domain account that will be used to unjoin the machine from the domain. This domain account needs to have sufficient privileges to unjoin machines.</p></li><li><p><em class="replaceable"><code>PASSWORD</code></em> defines the password for the domain account defined with <em class="replaceable"><code>ACCOUNT</code></em>.</p></li><li><p><em class="replaceable"><code>REBOOT</code></em> is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain.</p></li></ul></div><p>
 Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to unjoin. These additional parameters include: -S computer and -U user.
@@ -497,7 +489,7 @@ Note that you also need to use standard net parameters to connect and authentica
 	net dom unjoin -S xp -U XP\\administrator%secret account=MYDOM\\administrator password=topsecret reboot.
 </p><p>
 This example would connect to a computer named XP as the local administrator using password secret, and unjoin the computer from the domain using the MYDOM domain administrator account and password topsecret. After successful unjoin, the computer would reboot.
-</p></div><div class="refsect3" lang="en"><a name="id2534823"></a><h4>DOM RENAMECOMPUTER <em class="replaceable"><code>newname=NEWNAME</code></em> <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
+</p></div><div class="refsect3" lang="en"><a name="id2534855"></a><h4>DOM RENAMECOMPUTER <em class="replaceable"><code>newname=NEWNAME</code></em> <em class="replaceable"><code>account=ACCOUNT</code></em> <em class="replaceable"><code>password=PASSWORD</code></em> <em class="replaceable"><code>reboot</code></em></h4><p>
 Renames a computer that is joined to a domain. This command supports the following additional parameters:
 </p><div class="itemizedlist"><ul type="disc"><li><p><em class="replaceable"><code>NEWNAME</code></em> defines the new name of the machine in the domain.</p></li><li><p><em class="replaceable"><code>ACCOUNT</code></em> defines a domain account that will be used to rename the machine in the domain. This domain account needs to have sufficient privileges to rename machines.</p></li><li><p><em class="replaceable"><code>PASSWORD</code></em> defines the password for the domain account defined with <em class="replaceable"><code>ACCOUNT</code></em>.</p></li><li><p><em class="replaceable"><code>REBOOT</code></em> is an optional parameter that can be set to reboot the remote machine after successful rename in the domain.</p></li></ul></div><p>
 Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to rename in the domain. These additional parameters include: -S computer and -U user.
@@ -506,8 +498,8 @@ Note that you also need to use standard net parameters to connect and authentica
 	net dom renamecomputer -S xp -U XP\\administrator%secret newname=XPNEW account=MYDOM\\administrator password=topsecret reboot.
 </p><p>
 This example would connect to a computer named XP as the local administrator using password secret, and rename the joined computer to XPNEW using the MYDOM domain administrator account and password topsecret. After successful rename, the computer would reboot.
-</p></div></div><div class="refsect2" lang="en"><a name="id2534906"></a><h3>HELP [COMMAND]</h3><p>Gives usage information for the specified command.</p></div></div><div class="refsect1" lang="en"><a name="id2534918"></a><h2>VERSION</h2><p>This man page is complete for version 3 of the Samba 
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2534928"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+</p></div></div><div class="refsect2" lang="en"><a name="id2534938"></a><h3>HELP [COMMAND]</h3><p>Gives usage information for the specified command.</p></div></div><div class="refsect1" lang="en"><a name="id2534950"></a><h2>VERSION</h2><p>This man page is complete for version 3 of the Samba 
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2534961"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The net manpage was written by Jelmer Vernooij.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/nmbd.8.html b/docs/htmldocs/manpages/nmbd.8.html
index 7f28d1ac82..772acddaf5 100644
--- a/docs/htmldocs/manpages/nmbd.8.html
+++ b/docs/htmldocs/manpages/nmbd.8.html
@@ -1,5 +1,5 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmbd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmbd &#8212; NetBIOS name server to provide NetBIOS 
-	over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">nmbd</code> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483379"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">nmbd</code> is a server that understands 
+	over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">nmbd</code> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483383"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">nmbd</code> is a server that understands 
 	and can reply to NetBIOS over IP name service requests, like 
 	those produced by SMB/CIFS clients such as Windows 95/98/ME, 
 	Windows NT, Windows 2000, Windows XP and LanManager clients. It also
@@ -22,7 +22,7 @@
 	replying to queries from clients for these names.</p><p>In addition, <code class="literal">nmbd</code> can act as a WINS 
 	proxy, relaying broadcast queries from clients that do 
 	not understand how to talk the WINS protocol to a WINS 
-	server.</p></div><div class="refsect1" lang="en"><a name="id2483718"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes 
+	server.</p></div><div class="refsect1" lang="en"><a name="id2483721"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes 
 		<code class="literal">nmbd</code> to operate as a daemon. That is, 
 		it detaches itself and runs in the background, fielding 
 		requests on the appropriate port. By default, <code class="literal">nmbd</code> 
@@ -88,7 +88,7 @@ log.smbd, etc...). The log file is never removed by the client.
 		This option changes the default UDP port number (normally 137)
 		that <code class="literal">nmbd</code> responds to name queries on. Don't
 		use this option unless you are an expert, in which case you
-		won't need help!</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481741"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the
+		won't need help!</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481745"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the
 		<code class="literal">inetd</code> meta-daemon, this file
 		must contain suitable startup information for the
 		meta-daemon. 
@@ -115,7 +115,7 @@ log.smbd, etc...). The log file is never removed by the client.
 		will store the browsing database in the file <code class="filename">browse.dat
 		</code> in the <code class="filename">var/locks</code> directory
 		configured under wherever Samba was configured to install itself.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481946"></a><h2>SIGNALS</h2><p>To shut down an <code class="literal">nmbd</code> process it is recommended
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481952"></a><h2>SIGNALS</h2><p>To shut down an <code class="literal">nmbd</code> process it is recommended
 	that SIGKILL (-9) <span class="emphasis"><em>NOT</em></span> be used, except as a last
 	resort, as this may leave the name database in an inconsistent state.
 	The correct way to terminate <code class="literal">nmbd</code> is to send it
@@ -129,13 +129,13 @@ log.smbd, etc...). The log file is never removed by the client.
 	using <a class="citerefentry" href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a> (SIGUSR[1|2] signals
 	are no longer used since Samba 2.2). This is to allow
 	transient problems to be diagnosed, whilst still running 
-	at a normally low log level.</p></div><div class="refsect1" lang="en"><a name="id2532496"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532507"></a><h2>SEE ALSO</h2><p>
+	at a normally low log level.</p></div><div class="refsect1" lang="en"><a name="id2482037"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532512"></a><h2>SEE ALSO</h2><p>
 	<a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the Internet 
 	RFC's <code class="filename">rfc1001.txt</code>, <code class="filename">rfc1002.txt</code>. 
 	In addition the CIFS (formerly SMB) specification is available 
 	as a link from the Web page <a class="ulink" href="http://samba.org/cifs/" target="_top"> 
-	http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532581"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532586"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/nmblookup.1.html b/docs/htmldocs/manpages/nmblookup.1.html
index 1b809d53b0..104ce95057 100644
--- a/docs/htmldocs/manpages/nmblookup.1.html
+++ b/docs/htmldocs/manpages/nmblookup.1.html
@@ -1,9 +1,9 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmblookup</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmblookup"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmblookup &#8212; NetBIOS over TCP/IP client used to lookup NetBIOS 
-	names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">nmblookup</code> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</p></div></div><div class="refsect1" lang="en"><a name="id2483388"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">nmblookup</code> is used to query NetBIOS names 
+	names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">nmblookup</code> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</p></div></div><div class="refsect1" lang="en"><a name="id2483393"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">nmblookup</code> is used to query NetBIOS names 
 	and map them to IP addresses in a network using NetBIOS over TCP/IP 
 	queries. The options allow the name queries to be directed at a 
 	particular IP broadcast area or to a particular machine. All queries 
-	are done over UDP.</p></div><div class="refsect1" lang="en"><a name="id2483542"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-M</span></dt><dd><p>Searches for a master browser by looking 
+	are done over UDP.</p></div><div class="refsect1" lang="en"><a name="id2483545"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-M</span></dt><dd><p>Searches for a master browser by looking 
 		up the  NetBIOS name <em class="replaceable"><code>name</code></em> with a 
 		type of <code class="constant">0x1d</code>. If <em class="replaceable"><code>
 		name</code></em> is "-" then it does a lookup on the special name 
@@ -88,12 +88,12 @@ log.smbd, etc...). The log file is never removed by the client.
 		If a NetBIOS name then the different name types may be specified 
 		by appending '#&lt;type&gt;' to the name. This name may also be
 		'*', which will return all registered names within a broadcast 
-		area.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481756"></a><h2>EXAMPLES</h2><p><code class="literal">nmblookup</code> can be used to query 
+		area.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481763"></a><h2>EXAMPLES</h2><p><code class="literal">nmblookup</code> can be used to query 
 		a WINS server (in the same way <code class="literal">nslookup</code> is 
 		used to query DNS servers). To query a WINS server, <code class="literal">nmblookup</code> 
 		must be called like this:</p><p><code class="literal">nmblookup -U server -R 'name'</code></p><p>For example, running :</p><p><code class="literal">nmblookup -U samba.org -R 'IRIX#1B'</code></p><p>would query the WINS server samba.org for the domain 
-		master browser (1B name type) for the IRIX workgroup.</p></div><div class="refsect1" lang="en"><a name="id2481806"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481817"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, and <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481850"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+		master browser (1B name type) for the IRIX workgroup.</p></div><div class="refsect1" lang="en"><a name="id2481812"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481823"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, and <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481856"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/ntlm_auth.1.html b/docs/htmldocs/manpages/ntlm_auth.1.html
index 231884df1b..0d59843a2c 100644
--- a/docs/htmldocs/manpages/ntlm_auth.1.html
+++ b/docs/htmldocs/manpages/ntlm_auth.1.html
@@ -1,18 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ntlm_auth</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ntlm-auth.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ntlm_auth &#8212; tool to allow external access to Winbind's NTLM authentication function</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ntlm_auth</code> [-d debuglevel] [-l logdir] [-s &lt;smb config file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2522936"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">ntlm_auth</code> is a helper utility that authenticates 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ntlm_auth</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ntlm-auth.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ntlm_auth &#8212; tool to allow external access to Winbind's NTLM authentication function</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">ntlm_auth</code> [-d debuglevel] [-l logdir] [-s &lt;smb config file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2522939"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">ntlm_auth</code> is a helper utility that authenticates 
 	users using NT/LM authentication. It returns 0 if the users is authenticated
 	successfully and 1 if access was denied. ntlm_auth uses winbind to access 
 	the user and authentication data for a domain.  This utility 
 	is only intended to be used by other programs (currently
 	<a class="ulink" href="http://www.squid-cache.org/" target="_top">Squid</a>
 	and <a class="ulink" href="http://download.samba.org/ftp/unpacked/lorikeet/trunk/mod_ntlm_winbind/" target="_top">mod_ntlm_winbind</a>)
-	</p></div><div class="refsect1" lang="en"><a name="id2483346"></a><h2>OPERATIONAL REQUIREMENTS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483350"></a><h2>OPERATIONAL REQUIREMENTS</h2><p>
     The <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon must be operational
     for many of these commands to function.</p><p>Some of these commands also require access to the directory 
     <code class="filename">winbindd_privileged</code> in
     <code class="filename">$LOCKDIR</code>.  This should be done either by running
     this command as root or providing group access
     to the <code class="filename">winbindd_privileged</code> directory.  For
-    security reasons, this directory should not be world-accessable. </p></div><div class="refsect1" lang="en"><a name="id2483515"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">--helper-protocol=PROTO</span></dt><dd><p>
+    security reasons, this directory should not be world-accessable. </p></div><div class="refsect1" lang="en"><a name="id2483395"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">--helper-protocol=PROTO</span></dt><dd><p>
 	Operate as a stdio-based helper.  Valid helper protocols are:
         </p><div class="variablelist"><dl><dt><span class="term">squid-2.4-basic</span></dt><dd><p>
                 Server-side helper for use with Squid 2.4's basic (plaintext)
@@ -65,32 +65,32 @@
 		a newline.  They may also need to decode strings from
 		the helper, which likewise may have been base64 encoded.</div><dl><dt><span class="term">Username</span></dt><dd><p>The username, expected to be in
                 Samba's <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a>.
-                </p><div class="example"><a name="id2483765"></a><p class="title"><b>Example�1.�</b></p><div class="example-contents">Username: bob</div></div><p><br class="example-break"></p><div class="example"><a name="id2483770"></a><p class="title"><b>Example�2.�</b></p><div class="example-contents">Username:: Ym9i</div></div><p><br class="example-break"></p></dd><dt><span class="term">Username</span></dt><dd><p>The user's domain, expected to be in
+                </p><div class="example"><a name="id2483767"></a><p class="title"><b>Example�1.�</b></p><div class="example-contents">Username: bob</div></div><p><br class="example-break"></p><div class="example"><a name="id2483772"></a><p class="title"><b>Example�2.�</b></p><div class="example-contents">Username:: Ym9i</div></div><p><br class="example-break"></p></dd><dt><span class="term">Username</span></dt><dd><p>The user's domain, expected to be in
                 Samba's <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a>.
-                </p><div class="example"><a name="id2481569"></a><p class="title"><b>Example�3.�</b></p><div class="example-contents">Domain: WORKGROUP</div></div><p><br class="example-break"></p><div class="example"><a name="id2481574"></a><p class="title"><b>Example�4.�</b></p><div class="example-contents">Domain:: V09SS0dST1VQ</div></div><p><br class="example-break"></p></dd><dt><span class="term">Full-Username</span></dt><dd><p>The fully qualified username, expected to be in
+                </p><div class="example"><a name="id2481575"></a><p class="title"><b>Example�3.�</b></p><div class="example-contents">Domain: WORKGROUP</div></div><p><br class="example-break"></p><div class="example"><a name="id2481579"></a><p class="title"><b>Example�4.�</b></p><div class="example-contents">Domain:: V09SS0dST1VQ</div></div><p><br class="example-break"></p></dd><dt><span class="term">Full-Username</span></dt><dd><p>The fully qualified username, expected to be in
                 Samba's <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> and qualified with the
                 <a class="link" href="smb.conf.5.html#WINBINDSEPARATOR" target="_top">winbind separator</a>.
-                </p><div class="example"><a name="id2481611"></a><p class="title"><b>Example�5.�</b></p><div class="example-contents">Full-Username: WORKGROUP\bob</div></div><p><br class="example-break"></p><div class="example"><a name="id2481615"></a><p class="title"><b>Example�6.�</b></p><div class="example-contents">Full-Username:: V09SS0dST1VQYm9i</div></div><p><br class="example-break"></p></dd><dt><span class="term">LANMAN-Challenge</span></dt><dd><p>The 8 byte <code class="literal">LANMAN Challenge</code> value,
+                </p><div class="example"><a name="id2481615"></a><p class="title"><b>Example�5.�</b></p><div class="example-contents">Full-Username: WORKGROUP\bob</div></div><p><br class="example-break"></p><div class="example"><a name="id2481619"></a><p class="title"><b>Example�6.�</b></p><div class="example-contents">Full-Username:: V09SS0dST1VQYm9i</div></div><p><br class="example-break"></p></dd><dt><span class="term">LANMAN-Challenge</span></dt><dd><p>The 8 byte <code class="literal">LANMAN Challenge</code> value,
                 generated randomly by the server, or (in cases such as
                 MSCHAPv2) generated in some way by both the server and
                 the client.
-                </p><div class="example"><a name="id2481640"></a><p class="title"><b>Example�7.�</b></p><div class="example-contents">LANMAN-Challege: 0102030405060708</div></div><p><br class="example-break"></p></dd><dt><span class="term">LANMAN-Response</span></dt><dd><p>The 24 byte <code class="literal">LANMAN Response</code> value,
+                </p><div class="example"><a name="id2481644"></a><p class="title"><b>Example�7.�</b></p><div class="example-contents">LANMAN-Challege: 0102030405060708</div></div><p><br class="example-break"></p></dd><dt><span class="term">LANMAN-Response</span></dt><dd><p>The 24 byte <code class="literal">LANMAN Response</code> value,
                 calculated from the user's password and the supplied
                 <code class="literal">LANMAN Challenge</code>.  Typically, this
                 is provided over the network by a client wishing to authenticate.
-                </p><div class="example"><a name="id2481671"></a><p class="title"><b>Example�8.�</b></p><div class="example-contents">LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</div></div><p><br class="example-break"></p></dd><dt><span class="term">NT-Response</span></dt><dd><p>The &gt;= 24 byte <code class="literal">NT Response</code>
+                </p><div class="example"><a name="id2481675"></a><p class="title"><b>Example�8.�</b></p><div class="example-contents">LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</div></div><p><br class="example-break"></p></dd><dt><span class="term">NT-Response</span></dt><dd><p>The &gt;= 24 byte <code class="literal">NT Response</code>
                 calculated from the user's password and the supplied
                 <code class="literal">LANMAN Challenge</code>.  Typically, this is 
                 provided over the network by a client wishing to authenticate.
-                 </p><div class="example"><a name="id2481704"></a><p class="title"><b>Example�9.�</b></p><div class="example-contents">NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</div></div><p><br class="example-break"></p></dd><dt><span class="term">Password</span></dt><dd><p>The user's password.  This would be
+                 </p><div class="example"><a name="id2481708"></a><p class="title"><b>Example�9.�</b></p><div class="example-contents">NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</div></div><p><br class="example-break"></p></dd><dt><span class="term">Password</span></dt><dd><p>The user's password.  This would be
                 provided by a network client, if the helper is being
                 used in a legacy situation that exposes plaintext
                 passwords in this way.
-                 </p><div class="example"><a name="id2481724"></a><p class="title"><b>Example�10.�</b></p><div class="example-contents">Password: samba2</div></div><p><br class="example-break"></p><div class="example"><a name="id2481729"></a><p class="title"><b>Example�11.�</b></p><div class="example-contents">Password:: c2FtYmEy</div></div><p><br class="example-break"></p></dd><dt><span class="term">Request-User-Session-Key</span></dt><dd><p>Apon sucessful authenticaiton, return
+                 </p><div class="example"><a name="id2481729"></a><p class="title"><b>Example�10.�</b></p><div class="example-contents">Password: samba2</div></div><p><br class="example-break"></p><div class="example"><a name="id2481733"></a><p class="title"><b>Example�11.�</b></p><div class="example-contents">Password:: c2FtYmEy</div></div><p><br class="example-break"></p></dd><dt><span class="term">Request-User-Session-Key</span></dt><dd><p>Apon sucessful authenticaiton, return
                 the user session key associated with the login.
-                 </p><div class="example"><a name="id2481746"></a><p class="title"><b>Example�12.�</b></p><div class="example-contents">Request-User-Session-Key: Yes</div></div><p><br class="example-break"></p></dd><dt><span class="term">Request-LanMan-Session-Key</span></dt><dd><p>Apon sucessful authenticaiton, return
+                 </p><div class="example"><a name="id2481751"></a><p class="title"><b>Example�12.�</b></p><div class="example-contents">Request-User-Session-Key: Yes</div></div><p><br class="example-break"></p></dd><dt><span class="term">Request-LanMan-Session-Key</span></dt><dd><p>Apon sucessful authenticaiton, return
                 the LANMAN session key associated with the login.
-                 </p><div class="example"><a name="id2481763"></a><p class="title"><b>Example�13.�</b></p><div class="example-contents">Request-LanMan-Session-Key: Yes</div></div><p><br class="example-break"></p></dd></dl></div></dd></dl></div></dd><dt><span class="term">--username=USERNAME</span></dt><dd><p>
+                 </p><div class="example"><a name="id2481768"></a><p class="title"><b>Example�13.�</b></p><div class="example-contents">Request-LanMan-Session-Key: Yes</div></div><p><br class="example-break"></p></dd></dl></div></dd></dl></div></dd><dt><span class="term">--username=USERNAME</span></dt><dd><p>
 	Specify username of user to authenticate
 	</p></dd><dt><span class="term">--domain=DOMAIN</span></dt><dd><p>
 	Specify domain of user to authenticate
@@ -128,7 +128,7 @@ compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</spa
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532516"></a><h2>EXAMPLE SETUP</h2><p>To setup ntlm_auth for use by squid 2.5, with both basic and
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532521"></a><h2>EXAMPLE SETUP</h2><p>To setup ntlm_auth for use by squid 2.5, with both basic and
 	NTLMSSP authentication, the following
 	should be placed in the <code class="filename">squid.conf</code> file.
 </p><pre class="programlisting">
@@ -144,13 +144,13 @@ auth_param basic credentialsttl 2 hours
 </p><pre class="programlisting">
 auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp --require-membership-of='WORKGROUP\Domain Users'
 auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of='WORKGROUP\Domain Users'
-</pre></div><div class="refsect1" lang="en"><a name="id2532573"></a><h2>TROUBLESHOOTING</h2><p>If you're experiencing problems with authenticating Internet Explorer running
+</pre></div><div class="refsect1" lang="en"><a name="id2532578"></a><h2>TROUBLESHOOTING</h2><p>If you're experiencing problems with authenticating Internet Explorer running
 	under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication
 	helper (--helper-protocol=squid-2.5-ntlmssp), then please read 
 	<a class="ulink" href="http://support.microsoft.com/support/kb/articles/Q239/8/69.ASP" target="_top">
 	the Microsoft Knowledge Base article #239869 and follow instructions described there</a>.
-	</p></div><div class="refsect1" lang="en"><a name="id2532594"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2532605"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	</p></div><div class="refsect1" lang="en"><a name="id2532599"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2532610"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The ntlm_auth manpage was written by Jelmer Vernooij and
diff --git a/docs/htmldocs/manpages/pam_winbind.8.html b/docs/htmldocs/manpages/pam_winbind.8.html
index fa708fdc75..159ce09333 100644
--- a/docs/htmldocs/manpages/pam_winbind.8.html
+++ b/docs/htmldocs/manpages/pam_winbind.8.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pam_winbind</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pam_winbind.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pam_winbind &#8212; PAM module for Winbind</p></div><div class="refsect1" lang="en"><a name="id2522890"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pam_winbind</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pam_winbind.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pam_winbind &#8212; PAM module for Winbind</p></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>
 	pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon.
-	</p></div><div class="refsect1" lang="en"><a name="id2522913"></a><h2>SYNOPSIS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522925"></a><h2>SYNOPSIS</h2><p>
 		Edit the PAM system config /etc/pam.d/service and modify it as the following example shows:
 		</p><pre class="programlisting">
 			    ...
@@ -19,16 +19,14 @@
 
 		Make sure that pam_winbind is one of the first modules in the session part. It may retrieve
 		kerberos tickets which are needed by other modules.
-	</p></div><div class="refsect1" lang="en"><a name="id2522942"></a><h2>OPTIONS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522954"></a><h2>OPTIONS</h2><p>
 	
 		pam_winbind supports several options which can either be set in
 		the PAM configuration files or in the pam_winbind configuration
 		file situated at
 		<code class="filename">/etc/security/pam_winbind.conf</code>. Options
 		from the PAM configuration file take precedence to those from
-		the configuration file. See
-		<a class="citerefentry" href="pam_winbind.conf.5.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind.conf</span>(5)</span></a>
-		for further details.
+		the configuration file.
 
 		</p><div class="variablelist"><dl><dt><span class="term">debug</span></dt><dd><p>Gives debugging output to syslog.</p></dd><dt><span class="term">debug_state</span></dt><dd><p>Gives detailed PAM state debugging output to syslog.</p></dd><dt><span class="term">require_membership_of=[SID or NAME]</span></dt><dd><p>
 		If this option is set, pam_winbind will only succeed if the user is a member of the given SID or NAME. A SID
@@ -84,7 +82,7 @@
 		going to expire. Defaults to 14 days.
 		</p></dd></dl></div><p>
 
-	</p></div><div class="refsect1" lang="en"><a name="id2483685"></a><h2>PAM DATA EXPORTS</h2><p>This section describes the data exported in the PAM stack which could be used in other PAM modules.</p><dt><span class="term">PAM_WINBIND_HOMEDIR</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483686"></a><h2>PAM DATA EXPORTS</h2><p>This section describes the data exported in the PAM stack which could be used in other PAM modules.</p><dt><span class="term">PAM_WINBIND_HOMEDIR</span></dt><dd><p>
 				This is the Windows Home Directory set in the profile tab in the user settings
 				on the Active Directory Server. This could be a local path or a directory on a
 				share mapped to a drive.
@@ -95,9 +93,9 @@
 				This exports the Active Directory server we are authenticating against. This can be
 				used as a variable later.
 			</p></dd><dt><span class="term">PAM_WINBIND_PROFILEPATH</span></dt><dd><p>
-				This is the profile path set in the profile tab in the user settings. Normally
+				This is the profile path set in the profile tab in the user settings. Noramlly
 				the home directory is synced with this directory on a share.
-			</p></dd></div><div class="refsect1" lang="en"><a name="id2483760"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="pam_winbind.conf.5.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind.conf</span>(5)</span></a>, <a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2481469"></a><h2>VERSION</h2><p>This man page is correct for version 3 of Samba.</p></div><div class="refsect1" lang="en"><a name="id2481479"></a><h2>AUTHOR</h2><p>
+			</p></dd></div><div class="refsect1" lang="en"><a name="id2483761"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483796"></a><h2>VERSION</h2><p>This man page is correct for version 3 of Samba.</p></div><div class="refsect1" lang="en"><a name="id2481475"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by
 	the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
 	</p><p>This manpage was written by Jelmer Vernooij and Guenther Deschner.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/pam_winbind.conf.5.html b/docs/htmldocs/manpages/pam_winbind.conf.5.html
deleted file mode 100644
index f3ac426c3c..0000000000
--- a/docs/htmldocs/manpages/pam_winbind.conf.5.html
+++ /dev/null
@@ -1,71 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pam_winbind.conf</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pam_winbind.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pam_winbind.conf &#8212; Configuration file of PAM module for Winbind</p></div><div class="refsect1" lang="en"><a name="id2522891"></a><h2>DESCRIPTION</h2><p>This configuration file is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>
-	pam_winbind.conf is the configuration file for the pam_winbind PAM
-	module. See
-	<a class="citerefentry" href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a>
-	for further details.
-	</p></div><div class="refsect1" lang="en"><a name="id2522921"></a><h2>SYNOPSIS</h2><p>
-		The pam_winbind.conf configuration file is a classic ini-style
-		configuration file. There is only one section (global) where
-		various options are defined.
-	</p></div><div class="refsect1" lang="en"><a name="id2522934"></a><h2>OPTIONS</h2><p>
-
-		pam_winbind supports several options which can either be set in
-		the PAM configuration files or in the pam_winbind configuration
-		file situated at
-		<code class="filename">/etc/security/pam_winbind.conf</code>. Options
-		from the PAM configuration file take precedence to those from
-		the pam_winbind.conf configuration file.
-
-		</p><div class="variablelist"><dl><dt><span class="term">debug = yes|no</span></dt><dd><p>Gives debugging output to syslog. Defaults to "no".</p></dd><dt><span class="term">debug_state = yes|no</span></dt><dd><p>Gives detailed PAM state debugging output to syslog. Defaults to "no".</p></dd><dt><span class="term">require_membership_of = [SID or NAME]</span></dt><dd><p>
-		If this option is set, pam_winbind will only succeed if the user is a member of the given SID or NAME. A SID
-		can be either a group-SID, an alias-SID or even an user-SID. It is also possible to give a NAME instead of the
-		SID. That name must have the form: <em class="parameter"><code>MYDOMAIN\\mygroup</code></em> or
-		<em class="parameter"><code>MYDOMAIN\\myuser</code></em>.  pam_winbind will, in that case, lookup the SID internally. Note that
-		NAME may not contain any spaces. It is thus recommended to only use SIDs. You can verify the list of SIDs a
-		user is a member of with <code class="literal">wbinfo --user-sids=SID</code>. This setting is empty by default.
-		</p></dd><dt><span class="term">try_first_pass = yes|no</span></dt><dd><p>
-		By default, pam_winbind tries to get the authentication token from a previous module. If no token is available
-		it asks the user for the old password. With this option, pam_winbind aborts with an error if no authentication
-		token from a previous module is available. If a primary password is not valid, PAM will prompt for a password.
-		Default to "no".
-		</p></dd><dt><span class="term">krb5_auth = yes|no</span></dt><dd><p>
-
-		pam_winbind can authenticate using Kerberos when winbindd is
-		talking to an Active Directory domain controller. Kerberos
-		authentication must be enabled with this parameter. When
-		Kerberos authentication can not succeed (e.g. due to clock
-		skew), winbindd will fallback to samlogon authentication over
-		MSRPC. When this parameter is used in conjunction with
-		<em class="parameter"><code>winbind refresh tickets</code></em>, winbind will
-		keep your Ticket Granting Ticket (TGT) uptodate by refreshing
-		it whenever necessary. Defaults to "no".
-
-		</p></dd><dt><span class="term">krb5_ccache_type = [type]</span></dt><dd><p>
-
-		When pam_winbind is configured to try kerberos authentication
-		by enabling the <em class="parameter"><code>krb5_auth</code></em> option, it can
-		store the retrieved Ticket Granting Ticket (TGT) in a
-		credential cache. The type of credential cache can be set with
-		this option. Currently the only supported value is:
-		<em class="parameter"><code>FILE</code></em>. In that case a credential cache in
-		the form of /tmp/krb5cc_UID will be created, where UID is
-		replaced with the numeric user id.  Leave empty to just do
-		kerberos authentication without having a ticket cache after the
-		logon has succeeded. This setting is empty by default.
-
-		</p></dd><dt><span class="term">cached_login = yes|no</span></dt><dd><p>
-		Winbind allows to logon using cached credentials when <em class="parameter"><code>winbind offline logon</code></em> is enabled. To use this feature from the PAM module this option must be set. Defaults to "no".
-		</p></dd><dt><span class="term">silent = yes|no</span></dt><dd><p>
-		Do not emit any messages. Defaults to "no".
-		</p></dd><dt><span class="term">mkhomedir = yes|no</span></dt><dd><p>
-		Create homedirectory for a user on-the-fly, option is valid in
-		PAM session block. Defaults to "no".
-		</p></dd><dt><span class="term">warn_pwd_expire = days</span></dt><dd><p>
-		Defines number of days before pam_winbind starts to warn about passwords that are
-		going to expire. Defaults to 14 days.
-		</p></dd></dl></div><p>
-
-	</p></div><div class="refsect1" lang="en"><a name="id2483648"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a>, <a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483692"></a><h2>VERSION</h2><p>This man page is correct for version 3 of Samba.</p></div><div class="refsect1" lang="en"><a name="id2483703"></a><h2>AUTHOR</h2><p>
-	The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by
-	the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
-	</p><p>This manpage was written by Jelmer Vernooij and Guenther Deschner.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/pdbedit.8.html b/docs/htmldocs/manpages/pdbedit.8.html
index e504b7bc5b..37eb2d0475 100644
--- a/docs/htmldocs/manpages/pdbedit.8.html
+++ b/docs/htmldocs/manpages/pdbedit.8.html
@@ -1,16 +1,16 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pdbedit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pdbedit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pdbedit &#8212; manage the SAM database (Database of Samba Users)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">pdbedit</code> [-a] [-b passdb-backend] [-c account-control] [-C value] [-d debuglevel] [-D drive] [-e passdb-backend] [-f fullname] [--force-initialized-passwords] [-g] [-h homedir] [-i passdb-backend] [-I domain] [-K] [-L ] [-m] [-M SID|RID] [-N description] [-P account-policy] [-p profile] [--policies-reset] [-r] [-s configfile] [-S script] [-t] [--time-format] [-u username] [-U SID|RID] [-v] [-V] [-w] [-x] [-y] [-z] [-Z]</p></div></div><div class="refsect1" lang="en"><a name="id2483670"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The pdbedit program is used to manage the users accounts
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pdbedit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pdbedit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pdbedit &#8212; manage the SAM database (Database of Samba Users)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">pdbedit</code> [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-K] [-a] [-t, --password-from-stdin] [-m] [-r] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value] [-c account-control] [-y]</p></div></div><div class="refsect1" lang="en"><a name="id2483597"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The pdbedit program is used to manage the users accounts
 	stored in the sam database and can only be run by root.</p><p>The pdbedit tool uses the passdb modular interface and is
 	independent from the kind of users database used (currently there
 	are smbpasswd, ldap, nis+ and tdb based and more can be added
 	without changing the tool).</p><p>There are five main ways to use pdbedit: adding a user account,
 	removing a user account, modifing a user account, listing user
-	accounts, importing users accounts.</p></div><div class="refsect1" lang="en"><a name="id2483707"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-L|--list</span></dt><dd><p>This option lists all the user accounts
+	accounts, importing users accounts.</p></div><div class="refsect1" lang="en"><a name="id2483633"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-L</span></dt><dd><p>This option lists all the user accounts
 		present in the users database.
 		This option prints a list of user/uid pairs separated by
 		the ':' character.</p><p>Example: <code class="literal">pdbedit -L</code></p><pre class="programlisting">
 sorce:500:Simo Sorce
 samba:45:Test User
-</pre></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>This option enables the verbose listing format.
+</pre></dd><dt><span class="term">-v</span></dt><dd><p>This option enables the verbose listing format.
 		It causes pdbedit to list the users in the database, printing
 		out the account fields in a descriptive format.</p><p>Example: <code class="literal">pdbedit -L -v</code></p><pre class="programlisting">
 ---------------
@@ -31,7 +31,7 @@ Home Directory: \\BERSERKER\samba
 HomeDir Drive:  
 Logon Script:   
 Profile Path:   \\BERSERKER\profile
-</pre></dd><dt><span class="term">-w|--smbpasswd-style</span></dt><dd><p>This option sets the "smbpasswd" listing format.
+</pre></dd><dt><span class="term">-w</span></dt><dd><p>This option sets the "smbpasswd" listing format.
 		It will make pdbedit list the users in the database, printing
 		out the account fields in a format compatible with the
 		<code class="filename">smbpasswd</code> file format. (see the
@@ -42,38 +42,38 @@ sorce:500:508818B733CE64BEAAD3B435B51404EE:
 samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:
           BC281CE3F53B6A5146629CD4751D3490:
           [UX         ]:LCT-3BFA1E8D:
-</pre></dd><dt><span class="term">-u|--user username</span></dt><dd><p>This option specifies the username to be
+</pre></dd><dt><span class="term">-u username</span></dt><dd><p>This option specifies the username to be
 		used for the operation requested (listing, adding, removing).
 		It is <span class="emphasis"><em>required</em></span> in add, remove and modify
 		operations and <span class="emphasis"><em>optional</em></span> in list
-		operations.</p></dd><dt><span class="term">-f|--fullname fullname</span></dt><dd><p>This option can be used while adding or
+		operations.</p></dd><dt><span class="term">-f fullname</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's full
-		name. </p><p>Example: <code class="literal">-f "Simo Sorce"</code></p></dd><dt><span class="term">-h|--homedir homedir</span></dt><dd><p>This option can be used while adding or
+		name. </p><p>Example: <code class="literal">-f "Simo Sorce"</code></p></dd><dt><span class="term">-h homedir</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's home
 		directory network path.</p><p>Example: <code class="literal">-h "\\\\BERSERKER\\sorce"</code>
-		</p></dd><dt><span class="term">-D|--drive drive</span></dt><dd><p>This option can be used while adding or
+		</p></dd><dt><span class="term">-D drive</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the windows drive
 		letter to be used to map the home directory.</p><p>Example: <code class="literal">-D "H:"</code>
-		</p></dd><dt><span class="term">-S|--script script</span></dt><dd><p>This option can be used while adding or
+		</p></dd><dt><span class="term">-S script</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's logon
 		script path.</p><p>Example: <code class="literal">-S "\\\\BERSERKER\\netlogon\\sorce.bat"</code>
-		</p></dd><dt><span class="term">-p|--profile profile</span></dt><dd><p>This option can be used while adding or
+		</p></dd><dt><span class="term">-p profile</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's profile
 		directory.</p><p>Example: <code class="literal">-p "\\\\BERSERKER\\netlogon"</code>
-		</p></dd><dt><span class="term">-M|'--machine SID' SID|rid</span></dt><dd><p>
-		This option can be used while adding or modifying a machine account. It
-		will specify the machines' new primary group SID (Security Identifier) or
-		rid. </p><p>Example: <code class="literal">-M S-1-5-21-2447931902-1787058256-3961074038-1201</code></p></dd><dt><span class="term">-U|'--user SID' SID|rid</span></dt><dd><p>
+		</p></dd><dt><span class="term">-G SID|rid</span></dt><dd><p>
+		This option can be used while adding or modifying a user account. It 
+		will specify the users' new primary group SID (Security Identifier) or 
+		rid. </p><p>Example: <code class="literal">-G S-1-5-21-2447931902-1787058256-3961074038-1201</code></p></dd><dt><span class="term">-U SID|rid</span></dt><dd><p>
 		This option can be used while adding or modifying a user account. It 
 		will specify the users' new SID (Security Identifier) or 
-		rid. </p><p>Example: <code class="literal">-U S-1-5-21-2447931902-1787058256-3961074038-5004</code></p><p>Example: <code class="literal">'--user SID' S-1-5-21-2447931902-1787058256-3961074038-5004</code></p><p>Example: <code class="literal">-U 5004</code></p><p>Example: <code class="literal">'--user SID' 5004</code></p></dd><dt><span class="term">-c|--account-control account-control</span></dt><dd><p>This option can be used while adding or modifying a user
+		rid. </p><p>Example: <code class="literal">-U S-1-5-21-2447931902-1787058256-3961074038-5004</code></p></dd><dt><span class="term">-c account-control</span></dt><dd><p>This option can be used while adding or modifying a user
 				account. It will specify the users' account control property. Possible flags are listed below.
 	</p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>N: No password required</p></li><li><p>D: Account disabled</p></li><li><p>H: Home directory required</p></li><li><p>T: Temporary duplicate of other account</p></li><li><p>U: Regular user account</p></li><li><p>M: MNS logon user account</p></li><li><p>W: Workstation Trust Account</p></li><li><p>S: Server Trust Account</p></li><li><p>L: Automatic Locking</p></li><li><p>X: Password does not expire</p></li><li><p>I: Domain Trust Account</p></li></ul></div><p>
 	</p><p>Example: <code class="literal">-c "[X          ]"</code></p></dd><dt><span class="term">-K|--kickoff-time</span></dt><dd><p>This option is used to modify the kickoff
 		time for a certain user. Use "never" as argument to set the
 		kickoff time to unlimited.
-		</p><p>Example: <code class="literal">pdbedit -K never user</code></p></dd><dt><span class="term">-a|--create</span></dt><dd><p>This option is used to add a user into the
+		</p><p>Example: <code class="literal">pdbedit -K never user</code></p></dd><dt><span class="term">-a</span></dt><dd><p>This option is used to add a user into the
 		database. This command needs a user name specified with
 		the -u switch. When adding a new user, pdbedit will also
 		ask for the password to be used.</p><p>Example: <code class="literal">pdbedit -a -u sorce</code>
@@ -86,59 +86,43 @@ retype new password
 				user database. 
 			</p><p>If you wish to add a user and synchronise the password
 				that immediately, use <code class="literal">smbpasswd</code>'s <code class="option">-a</code> option.
-			</p></div></dd><dt><span class="term">-t|--password-from-stdin</span></dt><dd><p>This option causes pdbedit to read the password
+			</p></div></dd><dt><span class="term">-t, --password-from-stdin</span></dt><dd><p>This option causes pdbedit to read the password
 		from standard input, rather than from /dev/tty (like the
 		<code class="literal">passwd(1)</code> program does).  The password has
-		to be submitted twice and terminated by a newline each.</p></dd><dt><span class="term">-r|--modify</span></dt><dd><p>This option is used to modify an existing user 
+		to be submitted twice and terminated by a newline each.</p></dd><dt><span class="term">-r</span></dt><dd><p>This option is used to modify an existing user 
 		in the database. This command needs a user name specified with the -u 
 		switch. Other options can be specified to modify the properties of 
 		the specified user. This flag is kept for backwards compatibility, but 
 		it is no longer necessary to specify it.
-		</p></dd><dt><span class="term">-m|--machine</span></dt><dd><p>This option may only be used in conjunction 
+		</p></dd><dt><span class="term">-m</span></dt><dd><p>This option may only be used in conjunction 
 		with the <em class="parameter"><code>-a</code></em> option. It will make
 		pdbedit to add a machine trust account instead of a user
 		account (-u username will provide the machine name).</p><p>Example: <code class="literal">pdbedit -a -m -u w2k-wks</code>
-		</p></dd><dt><span class="term">-x|--delete</span></dt><dd><p>This option causes pdbedit to delete an account
+		</p></dd><dt><span class="term">-x</span></dt><dd><p>This option causes pdbedit to delete an account
 		from the database. It needs a username specified with the
-		-u switch.</p><p>Example: <code class="literal">pdbedit -x -u bob</code></p></dd><dt><span class="term">-i|--import passdb-backend</span></dt><dd><p>Use a different passdb backend to retrieve users
+		-u switch.</p><p>Example: <code class="literal">pdbedit -x -u bob</code></p></dd><dt><span class="term">-i passdb-backend</span></dt><dd><p>Use a different passdb backend to retrieve users
                 than the one specified in smb.conf. Can be used to import data into
                 your local user database.</p><p>This option will ease migration from one passdb backend to
 		another.</p><p>Example: <code class="literal">pdbedit -i smbpasswd:/etc/smbpasswd.old
-                </code></p></dd><dt><span class="term">-e|--export passdb-backend</span></dt><dd><p>Exports all currently available users to the
+                </code></p></dd><dt><span class="term">-e passdb-backend</span></dt><dd><p>Exports all currently available users to the
 		specified password database backend.</p><p>This option will ease migration from one passdb backend to
-		another and will ease backing up.</p><p>Example: <code class="literal">pdbedit -e smbpasswd:/root/samba-users.backup</code></p></dd><dt><span class="term">-g|--group</span></dt><dd><p>If you specify <em class="parameter"><code>-g</code></em>,
+		another and will ease backing up.</p><p>Example: <code class="literal">pdbedit -e smbpasswd:/root/samba-users.backup</code></p></dd><dt><span class="term">-g</span></dt><dd><p>If you specify <em class="parameter"><code>-g</code></em>,
 		then <em class="parameter"><code>-i in-backend -e out-backend</code></em>
 		applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
-		another and will ease backing up.</p></dd><dt><span class="term">-b|--backend passdb-backend</span></dt><dd><p>Use a different default passdb backend. </p><p>Example: <code class="literal">pdbedit -b xml:/root/pdb-backup.xml -l</code></p></dd><dt><span class="term">-P|--account-policy account-policy</span></dt><dd><p>Display an account policy</p><p>Valid policies are: minimum password age, reset count minutes, disconnect time,
+		another and will ease backing up.</p></dd><dt><span class="term">-b passdb-backend</span></dt><dd><p>Use a different default passdb backend. </p><p>Example: <code class="literal">pdbedit -b xml:/root/pdb-backup.xml -l</code></p></dd><dt><span class="term">-P account-policy</span></dt><dd><p>Display an account policy</p><p>Valid policies are: minimum password age, reset count minutes, disconnect time,
 		user must logon to change password, password history, lockout duration, min password length,
 		maximum password age and bad lockout attempt.</p><p>Example: <code class="literal">pdbedit -P "bad lockout attempt"</code></p><pre class="programlisting">
 account policy value for bad lockout attempt is 0
-</pre></dd><dt><span class="term">-C|--value account-policy-value</span></dt><dd><p>Sets an account policy to a specified value. 
+</pre></dd><dt><span class="term">-C account-policy-value</span></dt><dd><p>Sets an account policy to a specified value. 
 		This option may only be used in conjunction
 		with the <em class="parameter"><code>-P</code></em> option.
 		</p><p>Example: <code class="literal">pdbedit -P "bad lockout attempt" -C 3</code></p><pre class="programlisting">
 account policy value for bad lockout attempt was 0
 account policy value for bad lockout attempt is now 3
-</pre></dd><dt><span class="term">-y|--policies</span></dt><dd><p>If you specify <em class="parameter"><code>-y</code></em>,
+</pre></dd><dt><span class="term">-y</span></dt><dd><p>If you specify <em class="parameter"><code>-y</code></em>,
 		then <em class="parameter"><code>-i in-backend -e out-backend</code></em>
 		applies to the account policies instead of the user database.</p><p>This option will allow to migrate account policies from their default
-		tdb-store into a passdb backend, e.g. an LDAP directory server.</p><p>Example: <code class="literal">pdbedit -y -i tdbsam: -e ldapsam:ldap://my.ldap.host</code></p></dd><dt><span class="term">--force-initialized-passwords</span></dt><dd><p>This option forces all users to change their
-				password upon next login.
-		</p></dd><dt><span class="term">-N|--account-desc description</span></dt><dd><p>This option can be used while adding or
-		modifing a user account. It will specify the user's description
-		field.</p><p>Example: <code class="literal">-N "test description"</code>
-		</p></dd><dt><span class="term">-Z|--logon-hours-reset</span></dt><dd><p>This option can be used while adding or
-		modifing a user account. It will reset the user's allowed logon
-		hours. A user may login at any time afterwards.</p><p>Example: <code class="literal">-Z</code>
-		</p></dd><dt><span class="term">-z|--bad-password-count-reset</span></dt><dd><p>This option can be used while adding or
-		modifing a user account. It will reset the stored bad login
-		counter from a specified user.</p><p>Example: <code class="literal">-z</code>
-		</p></dd><dt><span class="term">--policies-reset</span></dt><dd><p>This option can be used to reset the general
-				password policies stored for a domain to their
-				default values.</p><p>Example: <code class="literal">--policies-reset</code>
-		</p></dd><dt><span class="term">-I|--domain</span></dt><dd><p>This option can be used while adding or
-		modifing a user account. It will specify the user's domain field.</p><p>Example: <code class="literal">-I "MYDOMAIN"</code>
-		</p></dd><dt><span class="term">--time-format</span></dt><dd><p>This option is currently not being used.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
+		tdb-store into a passdb backend, e.g. an LDAP directory server.</p><p>Example: <code class="literal">pdbedit -y -i tdbsam: -e ldapsam:ldap://my.ldap.host</code></p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
 from 0 to 10. The default value if this parameter is 
 not specified is 0.</p><p>The higher this value, the more detail will be 
@@ -163,8 +147,8 @@ The default configuration file name is determined at
 compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532991"></a><h2>NOTES</h2><p>This command may be used only by root.</p></div><div class="refsect1" lang="en"><a name="id2533001"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2533012"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a></p></div><div class="refsect1" lang="en"><a name="id2533034"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532758"></a><h2>NOTES</h2><p>This command may be used only by root.</p></div><div class="refsect1" lang="en"><a name="id2532768"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532778"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a></p></div><div class="refsect1" lang="en"><a name="id2532801"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The pdbedit manpage was written by Simo Sorce and Jelmer Vernooij.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/profiles.1.html b/docs/htmldocs/manpages/profiles.1.html
index 99cfac4e37..7deb9257c5 100644
--- a/docs/htmldocs/manpages/profiles.1.html
+++ b/docs/htmldocs/manpages/profiles.1.html
@@ -1,12 +1,12 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>profiles</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="profiles.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>profiles &#8212; A utility to report and change SIDs in registry files
-	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">profiles</code> [-v] [-c SID] [-n SID] {file}</p></div></div><div class="refsect1" lang="en"><a name="id2522943"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">profiles</code> is a utility that 
+	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">profiles</code> [-v] [-c SID] [-n SID] {file}</p></div></div><div class="refsect1" lang="en"><a name="id2522946"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">profiles</code> is a utility that 
 	reports and changes SIDs in windows registry files. It currently only 
 	supports NT.
-	</p></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">file</span></dt><dd><p>Registry file to view or edit.  </p></dd><dt><span class="term">-v,--verbose</span></dt><dd><p>Increases verbosity of messages. 
+	</p></div><div class="refsect1" lang="en"><a name="id2483340"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">file</span></dt><dd><p>Registry file to view or edit.  </p></dd><dt><span class="term">-v,--verbose</span></dt><dd><p>Increases verbosity of messages. 
 		</p></dd><dt><span class="term">-c SID1 -n SID2</span></dt><dd><p>Change all occurences of SID1 in <code class="filename">file</code> by SID2.
 		</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483521"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2483532"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483525"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2483536"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The profiles man page was written by Jelmer Vernooij. </p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/rpcclient.1.html b/docs/htmldocs/manpages/rpcclient.1.html
index 692c9369c3..27ec206ddb 100644
--- a/docs/htmldocs/manpages/rpcclient.1.html
+++ b/docs/htmldocs/manpages/rpcclient.1.html
@@ -1,12 +1,12 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>rpcclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="rpcclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>rpcclient &#8212; tool for executing client side 
-	MS-RPC functions</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">rpcclient</code> [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logdir] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-I destinationIP] {server}</p></div></div><div class="refsect1" lang="en"><a name="id2483364"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">rpcclient</code> is a utility initially developed
+	MS-RPC functions</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">rpcclient</code> [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logdir] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</p></div></div><div class="refsect1" lang="en"><a name="id2483375"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">rpcclient</code> is a utility initially developed
 	to test MS-RPC functionality in Samba itself.  It has undergone 
 	several stages of development and stability.  Many system administrators
 	have now written scripts around it to manage Windows NT clients from 
-	their UNIX workstation. </p></div><div class="refsect1" lang="en"><a name="id2483521"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">server</span></dt><dd><p>NetBIOS name of Server to which to connect. 
+	their UNIX workstation. </p></div><div class="refsect1" lang="en"><a name="id2483528"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">server</span></dt><dd><p>NetBIOS name of Server to which to connect. 
 		The server can be  any SMB/CIFS server.  The name is 
 		resolved using the <a class="link" href="smb.conf.5.html#NAMERESOLVEORDER" target="_top">name resolve order</a> line from <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></dd><dt><span class="term">-c|--command='command string'</span></dt><dd><p>execute semicolon separated commands (listed 
-		below)) </p></dd><dt><span class="term">-I|--dest-ip IP-address</span></dt><dd><p><em class="replaceable"><code>IP address</code></em> is the address of the server to connect to. 
+		below)) </p></dd><dt><span class="term">-I IP-address</span></dt><dd><p><em class="replaceable"><code>IP address</code></em> is the address of the server to connect to. 
 		It should be specified in standard "a.b.c.d" notation. </p><p>Normally the client would attempt to locate a named 
 		SMB/CIFS server by looking it up via the NetBIOS name resolution 
 		mechanism described above in the <em class="parameter"><code>name resolve order</code></em> 
@@ -15,10 +15,7 @@
 		address and the NetBIOS name component of the resource being 
 		connected to will be ignored. </p><p>There is no default for this parameter. If not supplied, 
 		it will be determined automatically by the client as described 
-		above. </p></dd><dt><span class="term">-p|--port port</span></dt><dd><p>This number is the TCP port number that will be used
-		when making connections to the server. The standard (well-known)
-		TCP port number for an SMB/CIFS server is 139, which is the
-		default. </p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
+		above. </p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
 from 0 to 10. The default value if this parameter is 
 not specified is 0.</p><p>The higher this value, the more detail will be 
 logged to the log files about the activities of the 
@@ -51,6 +48,8 @@ option is also defined the password on the command line will
 be silently ingnored and no password will be used.</p></dd><dt><span class="term">-k|--kerberos</span></dt><dd><p>
 Try to authenticate with kerberos. Only useful in
 an Active Directory environment.
+</p></dd><dt><span class="term">-C|--use-ccache</span></dt><dd><p>
+Try to use the credentials cached by winbind.
 </p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows
 you to specify a file from which to read the username and
 password used in the connection.  The format of the file is
@@ -92,11 +91,11 @@ SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O|--socket-
 socket. See the socket options parameter in
 the <code class="filename">smb.conf</code> manual page for the list of valid
 options. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481733"></a><h2>COMMANDS</h2><div class="refsect2" lang="en"><a name="id2481739"></a><h3>LSARPC</h3><div class="variablelist"><dl><dt><span class="term">lsaquery</span></dt><dd><p>Query info policy</p></dd><dt><span class="term">lookupsids</span></dt><dd><p>Resolve a list 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481745"></a><h2>COMMANDS</h2><div class="refsect2" lang="en"><a name="id2481751"></a><h3>LSARPC</h3><div class="variablelist"><dl><dt><span class="term">lsaquery</span></dt><dd><p>Query info policy</p></dd><dt><span class="term">lookupsids</span></dt><dd><p>Resolve a list 
 		of SIDs to usernames.
 		</p></dd><dt><span class="term">lookupnames</span></dt><dd><p>Resolve a list 
 		of usernames to SIDs.
-		</p></dd><dt><span class="term">enumtrusts</span></dt><dd><p>Enumerate trusted domains</p></dd><dt><span class="term">enumprivs</span></dt><dd><p>Enumerate privileges</p></dd><dt><span class="term">getdispname</span></dt><dd><p>Get the privilege name</p></dd><dt><span class="term">lsaenumsid</span></dt><dd><p>Enumerate the LSA SIDS</p></dd><dt><span class="term">lsaenumprivsaccount</span></dt><dd><p>Enumerate the privileges of an SID</p></dd><dt><span class="term">lsaenumacctrights</span></dt><dd><p>Enumerate the rights of an SID</p></dd><dt><span class="term">lsaenumacctwithright</span></dt><dd><p>Enumerate accounts with a right</p></dd><dt><span class="term">lsaaddacctrights</span></dt><dd><p>Add rights to an account</p></dd><dt><span class="term">lsaremoveacctrights</span></dt><dd><p>Remove rights from an account</p></dd><dt><span class="term">lsalookupprivvalue</span></dt><dd><p>Get a privilege value given its name</p></dd><dt><span class="term">lsaquerysecobj</span></dt><dd><p>Query LSA security object</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481863"></a><h3>LSARPC-DS</h3><div class="variablelist"><dl><dt><span class="term">dsroledominfo</span></dt><dd><p>Get Primary Domain Information</p></dd></dl></div><p> </p><p><span class="emphasis"><em>DFS</em></span></p><div class="variablelist"><dl><dt><span class="term">dfsexist</span></dt><dd><p>Query DFS support</p></dd><dt><span class="term">dfsadd</span></dt><dd><p>Add a DFS share</p></dd><dt><span class="term">dfsremove</span></dt><dd><p>Remove a DFS share</p></dd><dt><span class="term">dfsgetinfo</span></dt><dd><p>Query DFS share info</p></dd><dt><span class="term">dfsenum</span></dt><dd><p>Enumerate dfs shares</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481932"></a><h3>REG</h3><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd><p>Remote Shutdown</p></dd><dt><span class="term">abortshutdown</span></dt><dd><p>Abort Shutdown</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481958"></a><h3>SRVSVC</h3><div class="variablelist"><dl><dt><span class="term">srvinfo</span></dt><dd><p>Server query info</p></dd><dt><span class="term">netshareenum</span></dt><dd><p>Enumerate shares</p></dd><dt><span class="term">netfileenum</span></dt><dd><p>Enumerate open files</p></dd><dt><span class="term">netremotetod</span></dt><dd><p>Fetch remote time of day</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2482000"></a><h3>SAMR</h3><div class="variablelist"><dl><dt><span class="term">queryuser</span></dt><dd><p>Query user info</p></dd><dt><span class="term">querygroup</span></dt><dd><p>Query group info</p></dd><dt><span class="term">queryusergroups</span></dt><dd><p>Query user groups</p></dd><dt><span class="term">querygroupmem</span></dt><dd><p>Query group membership</p></dd><dt><span class="term">queryaliasmem</span></dt><dd><p>Query alias membership</p></dd><dt><span class="term">querydispinfo</span></dt><dd><p>Query display info</p></dd><dt><span class="term">querydominfo</span></dt><dd><p>Query domain info</p></dd><dt><span class="term">enumdomusers</span></dt><dd><p>Enumerate domain users</p></dd><dt><span class="term">enumdomgroups</span></dt><dd><p>Enumerate domain groups</p></dd><dt><span class="term">enumalsgroups</span></dt><dd><p>Enumerate alias groups</p></dd><dt><span class="term">createdomuser</span></dt><dd><p>Create domain user</p></dd><dt><span class="term">samlookupnames</span></dt><dd><p>Look up names</p></dd><dt><span class="term">samlookuprids</span></dt><dd><p>Look up names</p></dd><dt><span class="term">deletedomuser</span></dt><dd><p>Delete domain user</p></dd><dt><span class="term">samquerysecobj</span></dt><dd><p>Query SAMR security object</p></dd><dt><span class="term">getdompwinfo</span></dt><dd><p>Retrieve domain password info</p></dd><dt><span class="term">lookupdomain</span></dt><dd><p>Look up domain</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2532606"></a><h3>SPOOLSS</h3><div class="variablelist"><dl><dt><span class="term">adddriver &lt;arch&gt; &lt;config&gt; [&lt;version&gt;]</span></dt><dd><p>
+		</p></dd><dt><span class="term">enumtrusts</span></dt><dd><p>Enumerate trusted domains</p></dd><dt><span class="term">enumprivs</span></dt><dd><p>Enumerate privileges</p></dd><dt><span class="term">getdispname</span></dt><dd><p>Get the privilege name</p></dd><dt><span class="term">lsaenumsid</span></dt><dd><p>Enumerate the LSA SIDS</p></dd><dt><span class="term">lsaenumprivsaccount</span></dt><dd><p>Enumerate the privileges of an SID</p></dd><dt><span class="term">lsaenumacctrights</span></dt><dd><p>Enumerate the rights of an SID</p></dd><dt><span class="term">lsaenumacctwithright</span></dt><dd><p>Enumerate accounts with a right</p></dd><dt><span class="term">lsaaddacctrights</span></dt><dd><p>Add rights to an account</p></dd><dt><span class="term">lsaremoveacctrights</span></dt><dd><p>Remove rights from an account</p></dd><dt><span class="term">lsalookupprivvalue</span></dt><dd><p>Get a privilege value given its name</p></dd><dt><span class="term">lsaquerysecobj</span></dt><dd><p>Query LSA security object</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481876"></a><h3>LSARPC-DS</h3><div class="variablelist"><dl><dt><span class="term">dsroledominfo</span></dt><dd><p>Get Primary Domain Information</p></dd></dl></div><p> </p><p><span class="emphasis"><em>DFS</em></span></p><div class="variablelist"><dl><dt><span class="term">dfsexist</span></dt><dd><p>Query DFS support</p></dd><dt><span class="term">dfsadd</span></dt><dd><p>Add a DFS share</p></dd><dt><span class="term">dfsremove</span></dt><dd><p>Remove a DFS share</p></dd><dt><span class="term">dfsgetinfo</span></dt><dd><p>Query DFS share info</p></dd><dt><span class="term">dfsenum</span></dt><dd><p>Enumerate dfs shares</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481945"></a><h3>REG</h3><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd><p>Remote Shutdown</p></dd><dt><span class="term">abortshutdown</span></dt><dd><p>Abort Shutdown</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2481972"></a><h3>SRVSVC</h3><div class="variablelist"><dl><dt><span class="term">srvinfo</span></dt><dd><p>Server query info</p></dd><dt><span class="term">netshareenum</span></dt><dd><p>Enumerate shares</p></dd><dt><span class="term">netfileenum</span></dt><dd><p>Enumerate open files</p></dd><dt><span class="term">netremotetod</span></dt><dd><p>Fetch remote time of day</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2482014"></a><h3>SAMR</h3><div class="variablelist"><dl><dt><span class="term">queryuser</span></dt><dd><p>Query user info</p></dd><dt><span class="term">querygroup</span></dt><dd><p>Query group info</p></dd><dt><span class="term">queryusergroups</span></dt><dd><p>Query user groups</p></dd><dt><span class="term">querygroupmem</span></dt><dd><p>Query group membership</p></dd><dt><span class="term">queryaliasmem</span></dt><dd><p>Query alias membership</p></dd><dt><span class="term">querydispinfo</span></dt><dd><p>Query display info</p></dd><dt><span class="term">querydominfo</span></dt><dd><p>Query domain info</p></dd><dt><span class="term">enumdomusers</span></dt><dd><p>Enumerate domain users</p></dd><dt><span class="term">enumdomgroups</span></dt><dd><p>Enumerate domain groups</p></dd><dt><span class="term">enumalsgroups</span></dt><dd><p>Enumerate alias groups</p></dd><dt><span class="term">createdomuser</span></dt><dd><p>Create domain user</p></dd><dt><span class="term">samlookupnames</span></dt><dd><p>Look up names</p></dd><dt><span class="term">samlookuprids</span></dt><dd><p>Look up names</p></dd><dt><span class="term">deletedomuser</span></dt><dd><p>Delete domain user</p></dd><dt><span class="term">samquerysecobj</span></dt><dd><p>Query SAMR security object</p></dd><dt><span class="term">getdompwinfo</span></dt><dd><p>Retrieve domain password info</p></dd><dt><span class="term">lookupdomain</span></dt><dd><p>Look up domain</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2532617"></a><h3>SPOOLSS</h3><div class="variablelist"><dl><dt><span class="term">adddriver &lt;arch&gt; &lt;config&gt; [&lt;version&gt;]</span></dt><dd><p>
 		Execute an AddPrinterDriver() RPC to install the printer driver 
 		information on the server.  Note that the driver files should 
 		already exist in the directory returned by  
@@ -181,11 +180,11 @@ Comma Separated list of Files
 		already be correctly installed on the print server.  </p><p>See also the <code class="literal">enumprinters</code> and 
 		<code class="literal">enumdrivers</code> commands for obtaining a list of
 		of installed printers and drivers.</p></dd><dt><span class="term">addform</span></dt><dd><p>Add form</p></dd><dt><span class="term">setform</span></dt><dd><p>Set form</p></dd><dt><span class="term">getform</span></dt><dd><p>Get form</p></dd><dt><span class="term">deleteform</span></dt><dd><p>Delete form</p></dd><dt><span class="term">enumforms</span></dt><dd><p>Enumerate form</p></dd><dt><span class="term">setprinter</span></dt><dd><p>Set printer comment</p></dd><dt><span class="term">setprinterdata</span></dt><dd><p>Set REG_SZ printer data</p></dd><dt><span class="term">setprintername &lt;printername&gt;
-		&lt;newprintername&gt;</span></dt><dd><p>Set printer name</p></dd><dt><span class="term">rffpcnex</span></dt><dd><p>Rffpcnex test</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2533001"></a><h3>NETLOGON</h3><div class="variablelist"><dl><dt><span class="term">logonctrl2</span></dt><dd><p>Logon Control 2</p></dd><dt><span class="term">logonctrl</span></dt><dd><p>Logon Control</p></dd><dt><span class="term">samsync</span></dt><dd><p>Sam Synchronisation</p></dd><dt><span class="term">samdeltas</span></dt><dd><p>Query Sam Deltas</p></dd><dt><span class="term">samlogon</span></dt><dd><p>Sam Logon</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2533059"></a><h3>GENERAL COMMANDS</h3><div class="variablelist"><dl><dt><span class="term">debuglevel</span></dt><dd><p>Set the current
+		&lt;newprintername&gt;</span></dt><dd><p>Set printer name</p></dd><dt><span class="term">rffpcnex</span></dt><dd><p>Rffpcnex test</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2533012"></a><h3>NETLOGON</h3><div class="variablelist"><dl><dt><span class="term">logonctrl2</span></dt><dd><p>Logon Control 2</p></dd><dt><span class="term">logonctrl</span></dt><dd><p>Logon Control</p></dd><dt><span class="term">samsync</span></dt><dd><p>Sam Synchronisation</p></dd><dt><span class="term">samdeltas</span></dt><dd><p>Query Sam Deltas</p></dd><dt><span class="term">samlogon</span></dt><dd><p>Sam Logon</p></dd></dl></div></div><div class="refsect2" lang="en"><a name="id2533069"></a><h3>GENERAL COMMANDS</h3><div class="variablelist"><dl><dt><span class="term">debuglevel</span></dt><dd><p>Set the current
 		debug level used to log information.</p></dd><dt><span class="term">help (?)</span></dt><dd><p>Print a listing of all 
 		known commands or extended help  on a particular command. 
 		</p></dd><dt><span class="term">quit (exit)</span></dt><dd><p>Exit <code class="literal">rpcclient
-		</code>.</p></dd></dl></div></div></div><div class="refsect1" lang="en"><a name="id2533100"></a><h2>BUGS</h2><p><code class="literal">rpcclient</code> is designed as a developer testing tool 
+		</code>.</p></dd></dl></div></div></div><div class="refsect1" lang="en"><a name="id2533110"></a><h2>BUGS</h2><p><code class="literal">rpcclient</code> is designed as a developer testing tool 
 	and may not be robust in certain areas (such as command line parsing).  
 	It has been known to  generate a core dump upon failures when invalid 
 	parameters where passed to the interpreter. </p><p>From Luke Leighton's original rpcclient man page:</p><p><span class="emphasis"><em>WARNING!</em></span> The MSRPC over SMB code has 
@@ -198,8 +197,8 @@ Comma Separated list of Files
 	versions of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a class="citerefentry" href="rpcclient.1.html"><span class="citerefentry"><span class="refentrytitle">rpcclient</span>(1)</span></a> that are incompatible for some commands or  services. Additionally, 
 	the developers are sending reports to Microsoft,  and problems found 
 	or reported to Microsoft are fixed in Service Packs,  which may 
-	result in incompatibilities.</p></div><div class="refsect1" lang="en"><a name="id2533157"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2533168"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	result in incompatibilities.</p></div><div class="refsect1" lang="en"><a name="id2533168"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2533179"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original rpcclient man page was written by Matthew 
diff --git a/docs/htmldocs/manpages/samba.7.html b/docs/htmldocs/manpages/samba.7.html
index a13bcdb826..641173f4b4 100644
--- a/docs/htmldocs/manpages/samba.7.html
+++ b/docs/htmldocs/manpages/samba.7.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="samba.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>samba &#8212; A Windows SMB/CIFS fileserver for UNIX</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">samba</code></p></div></div><div class="refsect1" lang="en"><a name="id2522905"></a><h2>DESCRIPTION</h2><p>The Samba software suite is a collection of programs 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="samba.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>samba &#8212; A Windows SMB/CIFS fileserver for UNIX</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">samba</code></p></div></div><div class="refsect1" lang="en"><a name="id2522912"></a><h2>DESCRIPTION</h2><p>The Samba software suite is a collection of programs 
 	that implements the Server Message Block (commonly abbreviated 
 	as SMB) protocol for UNIX systems. This protocol is sometimes 
 	also referred to as the Common Internet File System (CIFS). For a
@@ -63,7 +63,7 @@
 <a class="citerefentry" href="smbmnt.8.html"><span class="citerefentry"><span class="refentrytitle">smbmnt</span>(8)</span></a></span></dt><dd><p><code class="literal">smbmount</code>,<code class="literal">smbumount</code> and <code class="literal">smbmnt</code> are commands that can be used to 
 		mount CIFS/SMB shares on Linux.
 		</p></dd><dt><span class="term"><a class="citerefentry" href="smbcquotas.1.html"><span class="citerefentry"><span class="refentrytitle">smbcquotas</span>(1)</span></a></span></dt><dd><p><code class="literal">smbcquotas</code> is a tool that 
-		can set remote QUOTA's on server with NTFS 5. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481790"></a><h2>COMPONENTS</h2><p>The Samba suite is made up of several components. Each 
+		can set remote QUOTA's on server with NTFS 5. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481796"></a><h2>COMPONENTS</h2><p>The Samba suite is made up of several components. Each 
 	component is described in a separate manual page. It is strongly 
 	recommended that you read the documentation that comes with Samba 
 	and the manual pages of those components that you use. If the 
@@ -72,7 +72,7 @@
 	for information on how to file a bug report or submit a patch.</p><p>If you require help, visit the Samba webpage at
 	<a class="ulink" href="http://samba.org/" target="_top">http://www.samba.org/</a> and
 	explore the many option available to you.
-	</p></div><div class="refsect1" lang="en"><a name="id2481823"></a><h2>AVAILABILITY</h2><p>The Samba software suite is licensed under the 
+	</p></div><div class="refsect1" lang="en"><a name="id2481829"></a><h2>AVAILABILITY</h2><p>The Samba software suite is licensed under the 
 	GNU Public License(GPL). A copy of that license should 
 	have come with the package in the file COPYING. You are 
 	encouraged to distribute copies of the Samba suite, but 
@@ -86,14 +86,14 @@
 	the README file that comes with Samba.</p><p>If you have access to a WWW viewer (such as Mozilla
 	or Konqueror) then you will also find lots of useful information, 
 	including back issues of the Samba mailing list, at
-	<a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.</p></div><div class="refsect1" lang="en"><a name="id2481867"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the 
-	Samba suite. </p></div><div class="refsect1" lang="en"><a name="id2481878"></a><h2>CONTRIBUTIONS</h2><p>If you wish to contribute to the Samba project, 
+	<a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.</p></div><div class="refsect1" lang="en"><a name="id2481874"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the 
+	Samba suite. </p></div><div class="refsect1" lang="en"><a name="id2481885"></a><h2>CONTRIBUTIONS</h2><p>If you wish to contribute to the Samba project, 
 	then I suggest you join the Samba mailing list at 
 	<a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.
 	</p><p>If you have patches to submit, visit
 	<a class="ulink" href="http://devel.samba.org/" target="_top">http://devel.samba.org/</a>
 	for information on how to do it properly. We prefer patches 
-	in <code class="literal">diff -u</code> format.</p></div><div class="refsect1" lang="en"><a name="id2481912"></a><h2>CONTRIBUTORS</h2><p>Contributors to the project are now too numerous 
+	in <code class="literal">diff -u</code> format.</p></div><div class="refsect1" lang="en"><a name="id2481918"></a><h2>CONTRIBUTORS</h2><p>Contributors to the project are now too numerous 
 	to mention here but all deserve the thanks of all Samba 
 	users. To see a full list, look at the
 	<code class="filename">change-log</code> in the source package 
@@ -101,7 +101,7 @@
 	http://cvs.samba.org/</a>
 	for the contributors to Samba post-CVS. CVS is the Open Source 
 	source code control system used by the Samba Team to develop 
-	Samba. The project would have been unmanageable without it.</p></div><div class="refsect1" lang="en"><a name="id2481940"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	Samba. The project would have been unmanageable without it.</p></div><div class="refsect1" lang="en"><a name="id2481946"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/sharesec.1.html b/docs/htmldocs/manpages/sharesec.1.html
index 0c389b7da6..9f180e19d1 100644
--- a/docs/htmldocs/manpages/sharesec.1.html
+++ b/docs/htmldocs/manpages/sharesec.1.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>sharesec</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="sharesec.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>sharesec &#8212; Set or get share ACLs</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">sharesec</code> {sharename} [-r, --remove=ACL] [-m, --modify=ACL] [-a, --add=ACL] [-R, --replace=ACLs] [-D, --delete] [-v, --view] [-M, --machine-sid] [-F, --force] [-d, --debuglevel=DEBUGLEVEL] [-s, --configfile=CONFIGFILE] [-l, --log-basename=LOGFILEBASE] [-V, --version] [-?, --help] [--usage]</p></div></div><div class="refsect1" lang="en"><a name="id2483516"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">sharesec</code> program manipulates share permissions
-	on SMB file shares.</p></div><div class="refsect1" lang="en"><a name="id2483544"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">sharesec</code> program.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>sharesec</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="sharesec.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>sharesec &#8212; Set or get share ACLs</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">sharesec</code> {sharename} [-r, --remove=ACL] [-m, --modify=ACL] [-a, --add=ACL] [-R, --replace=ACLs] [-D, --delete] [-v, --view] [-M, --machine-sid] [-F, --force] [-d, --debuglevel=DEBUGLEVEL] [-s, --configfile=CONFIGFILE] [-l, --log-basename=LOGFILEBASE] [-V, --version] [-?, --help] [--usage]</p></div></div><div class="refsect1" lang="en"><a name="id2483396"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">sharesec</code> program manipulates share permissions
+	on SMB file shares.</p></div><div class="refsect1" lang="en"><a name="id2483546"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">sharesec</code> program.
 	The format of ACLs is described in the section ACL FORMAT </p><div class="variablelist"><dl><dt><span class="term">-a|--add=ACL</span></dt><dd><p>Add the ACEs specified to the ACL list.
 		</p></dd><dt><span class="term">-D|--delete</span></dt><dd><p>Delete the entire security descriptor.
 		</p></dd><dt><span class="term">-F|--force</span></dt><dd><p>Force storing the ACL.
@@ -33,7 +33,7 @@ The default configuration file name is determined at
 compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483760"></a><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483764"></a><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by
 	either commas or newlines.  An ACL entry is one of the following: </p><pre class="programlisting">
 	REVISION:&lt;revision number&gt;
 	OWNER:&lt;sid or name&gt;
@@ -57,13 +57,13 @@ log.smbd, etc...). The log file is never removed by the client.
 	file permissions of the same name.</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>R</em></span> - Allow read access </p></li><li><p><span class="emphasis"><em>W</em></span> - Allow write access</p></li><li><p><span class="emphasis"><em>X</em></span> - Execute permission on the object</p></li><li><p><span class="emphasis"><em>D</em></span> - Delete the object</p></li><li><p><span class="emphasis"><em>P</em></span> - Change permissions</p></li><li><p><span class="emphasis"><em>O</em></span> - Take ownership</p></li></ul></div><p>The following combined permissions can be specified:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>READ</em></span> -  Equivalent to 'RX'
 		permissions</p></li><li><p><span class="emphasis"><em>CHANGE</em></span> - Equivalent to 'RXWD' permissions
 		</p></li><li><p><span class="emphasis"><em>FULL</em></span> - Equivalent to 'RWXDPO'
-		permissions</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481664"></a><h2>EXIT STATUS</h2><p>The <code class="literal">sharesec</code> program sets the exit status
+		permissions</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481668"></a><h2>EXIT STATUS</h2><p>The <code class="literal">sharesec</code> program sets the exit status
 	depending on the success or otherwise of the operations performed.
 	The exit status may be one of the following values. </p><p>If the operation succeeded, sharesec returns and exit
 	status of 0.  If <code class="literal">sharesec</code> couldn't connect to the specified server,
 	or there was an error getting or setting the ACLs, an exit status
 	of 1 is returned.  If there was an error parsing any command line
-	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481696"></a><h2>EXAMPLES</h2><p>Add full access for SID
+	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481700"></a><h2>EXAMPLES</h2><p>Add full access for SID
 	<em class="parameter"><code>S-1-5-21-1866488690-1365729215-3963860297-17724</code></em> on
 	<em class="parameter"><code>share</code></em>:
 	</p><pre class="programlisting">
@@ -76,7 +76,7 @@ log.smbd, etc...). The log file is never removed by the client.
 	GROUP:(NULL SID)
 	ACL:S-1-1-0:ALLOWED/0/0x101f01ff
 	ACL:S-1-5-21-1866488690-1365729215-3963860297-17724:ALLOWED/0/FULL
-	</pre></div><div class="refsect1" lang="en"><a name="id2481745"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481756"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</pre></div><div class="refsect1" lang="en"><a name="id2481749"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481760"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/smb.conf.5.html b/docs/htmldocs/manpages/smb.conf.5.html
index 0c16482afb..a2db005732 100644
--- a/docs/htmldocs/manpages/smb.conf.5.html
+++ b/docs/htmldocs/manpages/smb.conf.5.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smb.conf</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smb.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smb.conf &#8212; The configuration file for the Samba suite</p></div><div class="refsect1" lang="en"><a name="id2522900"></a><h2>SYNOPSIS</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smb.conf</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smb.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smb.conf &#8212; The configuration file for the Samba suite</p></div><div class="refsect1" lang="en"><a name="id2522905"></a><h2>SYNOPSIS</h2><p>
 	The <code class="filename">smb.conf</code> file is a configuration  file for the Samba suite. <code class="filename">smb.conf</code> contains  runtime configuration information for the Samba programs. The
 	 <code class="filename">smb.conf</code> file is designed to be configured and administered by the
 	 <a class="citerefentry" href="swat.8.html"><span class="citerefentry"><span class="refentrytitle">swat</span>(8)</span></a> program. The
@@ -26,7 +26,7 @@
 	The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean,
 	which may be given as yes/no, 1/0 or true/false. Case is not significant in boolean values, but is preserved
 	in string values. Some items such as create masks are numeric.
-	</p></div><div class="refsect1" lang="en"><a name="id2483384"></a><h2>SECTION DESCRIPTIONS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483389"></a><h2>SECTION DESCRIPTIONS</h2><p>
 	Each section in the configuration file (except for the [global] section) describes a shared resource (known as
 	a &#8220;<span class="quote">share</span>&#8221;). The section name is the name of the shared resource and the parameters within the
 	section define the shares attributes.
@@ -69,7 +69,7 @@
 	<a class="link" href="smb.conf.5.html#PRINTABLE" target="_top">printable = yes</a>
 	<a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok = yes</a>
 </pre><p>
-	</p></div><div class="refsect1" lang="en"><a name="id2481464"></a><h2>SPECIAL SECTIONS</h2><div class="refsect2" lang="en"><a name="id2481470"></a><h3>The [global] section</h3><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2481471"></a><h2>SPECIAL SECTIONS</h2><div class="refsect2" lang="en"><a name="id2481477"></a><h3>The [global] section</h3><p>
 		Parameters in this section apply to the server as a whole, or are defaults for sections that do not
 		specifically define certain items. See the notes under PARAMETERS for more information.
 		</p></div><div class="refsect2" lang="en"><a name="HOMESECT"></a><h3>The [homes] section</h3><p>
@@ -160,7 +160,7 @@ alias|alias|alias|alias...
 		On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use
 		<code class="literal">printcap name = lpstat</code> to automatically obtain a list of printers. See the
 		<code class="literal">printcap name</code> option for more details.
-		</p></div></div></div><div class="refsect1" lang="en"><a name="id2481784"></a><h2>USERSHARES</h2><p>Starting with Samba version 3.0.23 the capability for non-root users to add, modify, and delete
+		</p></div></div></div><div class="refsect1" lang="en"><a name="id2481791"></a><h2>USERSHARES</h2><p>Starting with Samba version 3.0.23 the capability for non-root users to add, modify, and delete
 	their own share definitions has been added. This capability is called <span class="emphasis"><em>usershares</em></span> and
 	is controlled by a set of parameters in the [global] section of the smb.conf.
 	The relevant parameters are :
@@ -184,7 +184,7 @@ chmod 1770 /usr/local/samba/lib/usershares
 
 	to the global
 	section of your <code class="filename">smb.conf</code>. Members of the group foo may then manipulate the user defined shares
-	using the following commands.</p><div class="variablelist"><dl><dt><span class="term">net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]</span></dt><dd><p>To create or modify (overwrite) a user defined share.</p></dd><dt><span class="term">net usershare delete sharename</span></dt><dd><p>To delete a user defined share.</p></dd><dt><span class="term">net usershare list wildcard-sharename</span></dt><dd><p>To list user defined shares.</p></dd><dt><span class="term">net usershare info wildcard-sharename</span></dt><dd><p>To print information about user defined shares.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2482011"></a><h2>PARAMETERS</h2><p>Parameters define the specific attributes of sections.</p><p>
+	using the following commands.</p><div class="variablelist"><dl><dt><span class="term">net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]</span></dt><dd><p>To create or modify (overwrite) a user defined share.</p></dd><dt><span class="term">net usershare delete sharename</span></dt><dd><p>To delete a user defined share.</p></dd><dt><span class="term">net usershare list wildcard-sharename</span></dt><dd><p>To list user defined shares.</p></dd><dt><span class="term">net usershare info wildcard-sharename</span></dt><dd><p>To print information about user defined shares.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2482018"></a><h2>PARAMETERS</h2><p>Parameters define the specific attributes of sections.</p><p>
 	Some parameters are specific to the [global] section (e.g., <span class="emphasis"><em>security</em></span>).  Some parameters
 	are usable in all sections (e.g., <span class="emphasis"><em>create mask</em></span>). All others are permissible only in normal
 	sections. For the purposes of the following descriptions the [homes] and [printers] sections will be
@@ -196,7 +196,7 @@ chmod 1770 /usr/local/samba/lib/usershares
 	Parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can
 	find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred
 	synonym.
-	</p></div><div class="refsect1" lang="en"><a name="id2532525"></a><h2>VARIABLE SUBSTITUTIONS</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2532531"></a><h2>VARIABLE SUBSTITUTIONS</h2><p>
 	Many of the strings that are settable in the config file can take substitutions. For example the option
 	&#8220;<span class="quote">path = /tmp/%u</span>&#8221; is interpreted as &#8220;<span class="quote">path = /tmp/john</span>&#8221; if the user connected with the
 	username john.
@@ -305,7 +305,7 @@ chmod 1770 /usr/local/samba/lib/usershares
 		</p></li><li><p>
 		If the service is a guest service, a connection is made as the username given in the <code class="literal">guest account
 		=</code> for the service, irrespective of the supplied password.
-		</p></li></ol></div></div><div class="refsect1" lang="en"><a name="id2533226"></a><h2>REGISTRY-BASED CONFIGURATION</h2><p>
+		</p></li></ol></div></div><div class="refsect1" lang="en"><a name="id2533232"></a><h2>REGISTRY-BASED CONFIGURATION</h2><p>
 		Starting with Samba version 3.2.0, the capability to
 		store Samba configuration in the registry is available.
 		The configuration is stored in the registry key
@@ -360,19 +360,19 @@ chmod 1770 /usr/local/samba/lib/usershares
 		registry based configuration locally, i.e. directly
 		accessing the database file, circumventing the
 		server.
-	</p></div><div class="refsect1" lang="en"><a name="id2533401"></a><h2>EXPLANATION OF EACH PARAMETER</h2><div class="section" lang="en"><div class="titlepage"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533412"></a>
+	</p></div><div class="refsect1" lang="en"><a name="id2533407"></a><h2>EXPLANATION OF EACH PARAMETER</h2><div class="section" lang="en"><div class="titlepage"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533418"></a>
 
 abort shutdown script (G)
-</h3></div></div></div><a class="indexterm" name="id2533413"></a><a name="ABORTSHUTDOWNSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This a full path name to a script called by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> that
+</h3></div></div></div><a class="indexterm" name="id2533419"></a><a name="ABORTSHUTDOWNSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This a full path name to a script called by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> that
 	should stop a shutdown procedure issued by the <a class="link" href="smb.conf.5.html#SHUTDOWNSCRIPT" target="_top">shutdown script</a>.</p><p>If the connected user posseses the <code class="constant">SeRemoteShutdownPrivilege</code>,
 	right, this command will be run as root.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>abort shutdown script</code></em> = <code class="literal">""</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>abort shutdown script</code></em> = <code class="literal">/sbin/shutdown -c</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533492"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533498"></a>
 
 access based share enum (S)
-</h3></div></div></div><a class="indexterm" name="id2533493"></a><a name="ACCESSBASEDSHAREENUM"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for a
+</h3></div></div></div><a class="indexterm" name="id2533499"></a><a name="ACCESSBASEDSHAREENUM"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for a
     service, then the share hosted by the service will only be visible
     to users who have read or write access to the share during share
     enumeration (for example net view \\sambaserver).  This has
@@ -381,10 +381,10 @@ access based share enum (S)
     descriptors on files contained on the share are not used in
     computing enumeration access rights.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>access based share enum</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533540"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533546"></a>
 
 acl check permissions (S)
-</h3></div></div></div><a class="indexterm" name="id2533541"></a><a name="ACLCHECKPERMISSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls what <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>does on receiving a protocol request of "open for delete"
+</h3></div></div></div><a class="indexterm" name="id2533547"></a><a name="ACLCHECKPERMISSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls what <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>does on receiving a protocol request of "open for delete"
     from a Windows client. If a Windows client doesn't have permissions to delete a file then they
     expect this to be denied at open time. POSIX systems normally only detect restrictions on delete by
     actually attempting to delete the file or directory. As Windows clients can (and do) "back out" a
@@ -404,10 +404,10 @@ acl check permissions (S)
     with slightly different semantics was introduced in 3.0.20. That older version is not documented here.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>acl check permissions</code></em> = <code class="literal">True</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533636"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533642"></a>
 
 acl compatibility (G)
-</h3></div></div></div><a class="indexterm" name="id2533637"></a><a name="ACLCOMPATIBILITY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies what OS ACL semantics should 
+</h3></div></div></div><a class="indexterm" name="id2533643"></a><a name="ACLCOMPATIBILITY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies what OS ACL semantics should 
 	be compatible with. Possible values are <span class="emphasis"><em>winnt</em></span> for Windows NT 4, 
 	<span class="emphasis"><em>win2k</em></span> for Windows 2000 and above and <span class="emphasis"><em>auto</em></span>.
 	If you specify <span class="emphasis"><em>auto</em></span>, the value for this parameter 
@@ -416,10 +416,10 @@ acl compatibility (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>acl compatibility</code></em> = <code class="literal">win2k</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533707"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533713"></a>
 
 acl group control (S)
-</h3></div></div></div><a class="indexterm" name="id2533708"></a><a name="ACLGROUPCONTROL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2533714"></a><a name="ACLGROUPCONTROL"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	In a POSIX filesystem, only the owner of a file or directory and the superuser can modify the permissions
 	and ACLs on a file. If this parameter is set, then Samba overrides this restriction, and also allows the
  	 <span class="emphasis"><em>primary group owner</em></span> of a file or directory to modify the permissions and ACLs
@@ -446,10 +446,10 @@ acl group control (S)
 	<em class="parameter"><code>dos filemode</code></em> option.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>acl group control</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533803"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533809"></a>
 
 acl map full control (S)
-</h3></div></div></div><a class="indexterm" name="id2533804"></a><a name="ACLMAPFULLCONTROL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2533810"></a><a name="ACLMAPFULLCONTROL"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>maps a POSIX ACE entry of "rwx" (read/write/execute), the maximum
 	allowed POSIX permission set, into a Windows ACL of "FULL CONTROL". If this parameter is set to true any POSIX
 	ACE entry of "rwx" will be returned in a Windows ACL as "FULL CONTROL", is this parameter is set to false any
@@ -457,10 +457,10 @@ acl map full control (S)
 	execute.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>acl map full control</code></em> = <code class="literal">True</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533854"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533860"></a>
 
 add group script (G)
-</h3></div></div></div><a class="indexterm" name="id2533855"></a><a name="ADDGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2533861"></a><a name="ADDGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the full pathname to a script that will be run <span class="emphasis"><em>AS ROOT</em></span> by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when a new group is requested. It
 	will expand any <em class="parameter"><code>%g</code></em> to the group name passed. This script is only useful
 	for installations using the Windows NT domain administration tools. The script is free to create a group with
@@ -470,10 +470,10 @@ add group script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add group script</code></em> = <code class="literal">/usr/sbin/groupadd %g</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533929"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2533935"></a>
 
 add machine script (G)
-</h3></div></div></div><a class="indexterm" name="id2533930"></a><a name="ADDMACHINESCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2533936"></a><a name="ADDMACHINESCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the full pathname to a script that will  be run by
 	 <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when a machine is
 	added to Samba's domain and a Unix account matching the machine's name appended with a "$" does not
@@ -484,10 +484,10 @@ add machine script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add machine script</code></em> = <code class="literal">/usr/sbin/adduser -n -g machines -c Machine -d /var/lib/nobody -s /bin/false %u</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534008"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534014"></a>
 
 add port command (G)
-</h3></div></div></div><a class="indexterm" name="id2534009"></a><a name="ADDPORTCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>Samba 3.0.23 introduced support for adding printer ports
+</h3></div></div></div><a class="indexterm" name="id2534015"></a><a name="ADDPORTCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>Samba 3.0.23 introduced support for adding printer ports
 	remotely using the Windows "Add Standard TCP/IP Port Wizard".
 	This option defines an external program to be executed when
 	smbd receives a request to add a new Port to the system.
@@ -496,10 +496,10 @@ add port command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add port command</code></em> = <code class="literal">/etc/samba/scripts/addport.sh</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534091"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534096"></a>
 
 addprinter command (G)
-</h3></div></div></div><a class="indexterm" name="id2534092"></a><a name="ADDPRINTERCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printing
+</h3></div></div></div><a class="indexterm" name="id2534097"></a><a name="ADDPRINTERCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printing
     support for Windows NT/2000 clients in Samba 2.2, The MS Add
     Printer Wizard (APW) icon is now also available in the 
     "Printers..." folder displayed a share listing.  The APW
@@ -530,10 +530,10 @@ addprinter command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>addprinter command</code></em> = <code class="literal">/usr/bin/addprinter</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534279"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534284"></a>
 
 add share command (G)
-</h3></div></div></div><a class="indexterm" name="id2534280"></a><a name="ADDSHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2534286"></a><a name="ADDSHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
 	Manager.  The <em class="parameter"><code>add share command</code></em> is used to define an external program
 	or script which will add a new service definition to
@@ -565,10 +565,10 @@ add share command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add share command</code></em> = <code class="literal">/usr/local/bin/addshare</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534465"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534471"></a>
 
 add user script (G)
-</h3></div></div></div><a class="indexterm" name="id2534466"></a><a name="ADDUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2534472"></a><a name="ADDUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the full pathname to a script that will be run <span class="emphasis"><em>AS ROOT</em></span> by 
 	<a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> 
 	under special circumstances described below.
@@ -603,10 +603,10 @@ add user script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add user script</code></em> = <code class="literal">/usr/local/samba/bin/add_user %u</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534676"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534682"></a>
 
 add user to group script (G)
-</h3></div></div></div><a class="indexterm" name="id2534677"></a><a name="ADDUSERTOGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2534683"></a><a name="ADDUSERTOGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Full path to the script that will be called when a user is added to a group using the Windows NT domain administration 
 	tools. It will be run by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>
 	<span class="emphasis"><em>AS ROOT</em></span>. Any <em class="parameter"><code>%g</code></em> will be replaced with the group name and 
@@ -618,20 +618,20 @@ add user to group script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>add user to group script</code></em> = <code class="literal">/usr/sbin/adduser %u %g</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534763"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534769"></a>
 
 administrative share (S)
-</h3></div></div></div><a class="indexterm" name="id2534764"></a><a name="ADMINISTRATIVESHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is set to <code class="constant">yes</code> for
+</h3></div></div></div><a class="indexterm" name="id2534770"></a><a name="ADMINISTRATIVESHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is set to <code class="constant">yes</code> for
       a share, then the share will be an administrative share. The Administrative
       Shares are the default network shares created by all Windows NT-based
       operating systems. These are shares like C$, D$ or ADMIN$. The type of these
       shares is STYPE_DISKTREE_HIDDEN.</p><p>See the section below on <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> for more 
       information about this option.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>administrative share</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534821"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534827"></a>
 
 admin users (S)
-</h3></div></div></div><a class="indexterm" name="id2534822"></a><a name="ADMINUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of users who will be granted 
+</h3></div></div></div><a class="indexterm" name="id2534828"></a><a name="ADMINUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of users who will be granted 
     administrative privileges on the share. This means that they 
     will do all file operations as the super-user (root).</p><p>You should use this option very carefully, as any user in 
     this list will be able to do anything they like on the share, 
@@ -640,20 +640,20 @@ admin users (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>admin users</code></em> = <code class="literal">jason</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534894"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534900"></a>
 
 afs share (S)
-</h3></div></div></div><a class="indexterm" name="id2534895"></a><a name="AFSSHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether special AFS features are enabled
+</h3></div></div></div><a class="indexterm" name="id2534901"></a><a name="AFSSHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether special AFS features are enabled
 	for this share. If enabled, it assumes that the directory exported via
 	the <em class="parameter"><code>path</code></em> parameter is a local AFS import. The
 	special AFS features include the attempt to hand-craft an AFS token
 	if you enabled --with-fake-kaserver in configure.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>afs share</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534941"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534947"></a>
 
 afs username map (G)
-</h3></div></div></div><a class="indexterm" name="id2534942"></a><a name="AFSUSERNAMEMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>If you are using the fake kaserver AFS feature, you might
+</h3></div></div></div><a class="indexterm" name="id2534948"></a><a name="AFSUSERNAMEMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>If you are using the fake kaserver AFS feature, you might
 	want to hand-craft the usernames you are creating tokens for.
 	For example this is necessary if you have users from several domain
 	in your AFS Protection Database. One possible scheme to code users
@@ -663,10 +663,10 @@ afs username map (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>afs username map</code></em> = <code class="literal">%u@afs.samba.org</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535003"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535009"></a>
 
 aio read size (S)
-</h3></div></div></div><a class="indexterm" name="id2535004"></a><a name="AIOREADSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support and this
+</h3></div></div></div><a class="indexterm" name="id2535010"></a><a name="AIOREADSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support and this
     integer parameter is set to non-zero value,
     Samba will read from file asynchronously when size of request is bigger
     than this value. Note that it happens only for non-chained and non-chaining
@@ -677,10 +677,10 @@ aio read size (S)
 #  Use asynchronous I/O for reads bigger than 16KB
     request size</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535090"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535096"></a>
 
 aio write behind (S)
-</h3></div></div></div><a class="indexterm" name="id2535092"></a><a name="AIOWRITEBEHIND"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support,
+</h3></div></div></div><a class="indexterm" name="id2535098"></a><a name="AIOWRITEBEHIND"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support,
 	Samba will not wait until write requests are finished before returning
 	the result to the client for files listed in this parameter.
 	Instead, Samba will immediately return that the write
@@ -695,10 +695,10 @@ aio write behind (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>aio write behind</code></em> = <code class="literal">/*.tmp/</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535169"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535175"></a>
 
 aio write size (S)
-</h3></div></div></div><a class="indexterm" name="id2535170"></a><a name="AIOWRITESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support and this
+</h3></div></div></div><a class="indexterm" name="id2535176"></a><a name="AIOWRITESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba has been built with asynchronous I/O support and this
     integer parameter is set to non-zero value,
     Samba will write to file asynchronously when size of request is bigger
     than this value. Note that it happens only for non-chained and non-chaining
@@ -709,10 +709,10 @@ aio write size (S)
 #  Use asynchronous I/O for writes bigger than 16KB
     request size</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535255"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535261"></a>
 
 algorithmic rid base (G)
-</h3></div></div></div><a class="indexterm" name="id2535256"></a><a name="ALGORITHMICRIDBASE"></a><div class="variablelist"><dl><dt></dt><dd><p>This determines how Samba will use its
+</h3></div></div></div><a class="indexterm" name="id2535262"></a><a name="ALGORITHMICRIDBASE"></a><div class="variablelist"><dl><dt></dt><dd><p>This determines how Samba will use its
     algorithmic mapping from uids/gid to the RIDs needed to construct
     NT Security Identifiers.
     </p><p>Setting this option to a larger value could be useful to sites
@@ -727,10 +727,10 @@ algorithmic rid base (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>algorithmic rid base</code></em> = <code class="literal">100000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535325"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535331"></a>
 
 allocation roundup size (S)
-</h3></div></div></div><a class="indexterm" name="id2535326"></a><a name="ALLOCATIONROUNDUPSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows an administrator to tune the 
+</h3></div></div></div><a class="indexterm" name="id2535332"></a><a name="ALLOCATIONROUNDUPSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows an administrator to tune the 
     allocation size reported to Windows clients.  The default 
     size of 1Mb generally results in improved Windows client
     performance.   However, rounding the allocation size may cause
@@ -742,10 +742,10 @@ allocation roundup size (S)
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>allocation roundup size</code></em> = <code class="literal">0
 # (to disable roundups)</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535389"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535395"></a>
 
 allow trusted domains (G)
-</h3></div></div></div><a class="indexterm" name="id2535390"></a><a name="ALLOWTRUSTEDDOMAINS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2535396"></a><a name="ALLOWTRUSTEDDOMAINS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This option only takes effect when the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> option is set to 
     <code class="constant">server</code>, <code class="constant">domain</code> or <code class="constant">ads</code>.  
     If it is set to no, then attempts to connect to a resource from 
@@ -760,10 +760,10 @@ allow trusted domains (G)
     Samba server even if they do not have an account in DOMA.  This 
     can make implementing a security boundary difficult.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>allow trusted domains</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535462"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535468"></a>
 
 announce as (G)
-</h3></div></div></div><a class="indexterm" name="id2535463"></a><a name="ANNOUNCEAS"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies what type of server <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will announce itself as, to a network neighborhood browse 
+</h3></div></div></div><a class="indexterm" name="id2535469"></a><a name="ANNOUNCEAS"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies what type of server <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will announce itself as, to a network neighborhood browse 
     list. By default this is set to Windows NT. The valid options 
     are : "NT Server" (which can also be written as "NT"), 
     "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, 
@@ -775,20 +775,20 @@ announce as (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>announce as</code></em> = <code class="literal">Win95</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535531"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535537"></a>
 
 announce version (G)
-</h3></div></div></div><a class="indexterm" name="id2535532"></a><a name="ANNOUNCEVERSION"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies the major and minor version numbers 
+</h3></div></div></div><a class="indexterm" name="id2535538"></a><a name="ANNOUNCEVERSION"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies the major and minor version numbers 
     that nmbd will use when announcing itself as a server. The default 
     is 4.9.  Do not change this parameter unless you have a specific 
 	need to set a Samba server to be a downlevel server.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>announce version</code></em> = <code class="literal">4.9</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>announce version</code></em> = <code class="literal">2.0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535588"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535594"></a>
 
 auth methods (G)
-</h3></div></div></div><a class="indexterm" name="id2535589"></a><a name="AUTHMETHODS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2535595"></a><a name="AUTHMETHODS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This option allows the administrator to chose what authentication methods <code class="literal">smbd</code> 
     will use when authenticating a user. This option defaults to sensible values based on <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a>.  
     This should be considered a developer option and used only in rare circumstances.  In the majority (if not all) 
@@ -809,18 +809,18 @@ auth methods (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>auth methods</code></em> = <code class="literal">guest sam winbind</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535694"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535700"></a>
 
 available (S)
-</h3></div></div></div><a class="indexterm" name="id2535695"></a><a name="AVAILABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter lets you "turn off" a service. If 
+</h3></div></div></div><a class="indexterm" name="id2535701"></a><a name="AVAILABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter lets you "turn off" a service. If 
 	<em class="parameter"><code>available = no</code></em>, then <span class="emphasis"><em>ALL</em></span> 
 	attempts to connect to the service will fail. Such failures are 
 	logged.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>available</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535741"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2535747"></a>
 
 bind interfaces only (G)
-</h3></div></div></div><a class="indexterm" name="id2535742"></a><a name="BINDINTERFACESONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This global parameter allows the Samba admin 
+</h3></div></div></div><a class="indexterm" name="id2535748"></a><a name="BINDINTERFACESONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This global parameter allows the Samba admin 
         to limit what interfaces on a machine will serve SMB requests. It 
         affects file service <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and name service <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> in a slightly different ways.</p><p>
 	For name service it causes <code class="literal">nmbd</code> to bind to ports 137 and 138 on the
@@ -861,10 +861,10 @@ bind interfaces only (G)
 	from starting/stopping/restarting <code class="literal">smbd</code> and <code class="literal">nmbd</code>.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>bind interfaces only</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536069"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536075"></a>
 
 blocking locks (S)
-</h3></div></div></div><a class="indexterm" name="id2536070"></a><a name="BLOCKINGLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls the behavior 
+</h3></div></div></div><a class="indexterm" name="id2536076"></a><a name="BLOCKINGLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls the behavior 
 	of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when given a request by a client 
 	to obtain a byte range lock on a region of an open file, and the 
 	request has a time limit associated with it.</p><p>If this parameter is set and the lock range requested 
@@ -875,10 +875,10 @@ blocking locks (S)
 	will fail the lock request immediately if the lock range 
 	cannot be obtained.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>blocking locks</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536133"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536139"></a>
 
 block size (S)
-</h3></div></div></div><a class="indexterm" name="id2536134"></a><a name="BLOCKSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls the behavior of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when reporting disk free 
+</h3></div></div></div><a class="indexterm" name="id2536140"></a><a name="BLOCKSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls the behavior of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when reporting disk free 
     sizes. By default, this reports a disk block size of 1024 bytes.
     </p><p>Changing this parameter may have some effect on the
     efficiency of client writes, this is not yet confirmed. This
@@ -892,27 +892,27 @@ block size (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>block size</code></em> = <code class="literal">4096</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536211"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536217"></a>
 
 <a name="BROWSABLE"></a>browsable
-</h3></div></div></div><a class="indexterm" name="id2536212"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#BROWSEABLE">browseable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536238"></a>
+</h3></div></div></div><a class="indexterm" name="id2536218"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#BROWSEABLE">browseable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536244"></a>
 
 browseable (S)
-</h3></div></div></div><a class="indexterm" name="id2536239"></a><a name="BROWSEABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether this share is seen in 
+</h3></div></div></div><a class="indexterm" name="id2536245"></a><a name="BROWSEABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether this share is seen in 
 	the list of available shares in a net view and in the browse list.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>browseable</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536276"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536282"></a>
 
 browse list (G)
-</h3></div></div></div><a class="indexterm" name="id2536278"></a><a name="BROWSELIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will serve a browse list to 
+</h3></div></div></div><a class="indexterm" name="id2536284"></a><a name="BROWSELIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will serve a browse list to 
 	a client doing a <code class="literal">NetServerEnum</code> call. Normally 
 	set to <code class="constant">yes</code>. You should never need to change 
 	this.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>browse list</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536331"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536337"></a>
 
 cache directory (G)
-</h3></div></div></div><a class="indexterm" name="id2536332"></a><a name="CACHEDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>Usually, most of the TDB files are stored in the <em class="parameter"><code>lock directory</code></em>. Since Samba 3.4.0, it is
+</h3></div></div></div><a class="indexterm" name="id2536338"></a><a name="CACHEDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>Usually, most of the TDB files are stored in the <em class="parameter"><code>lock directory</code></em>. Since Samba 3.4.0, it is
 	possible to differentiate between TDB files with persistent data and
 	TDB files with non-persistent data using the
 	<em class="parameter"><code>state directory</code></em> and the
@@ -923,25 +923,25 @@ cache directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>cache directory</code></em> = <code class="literal">/var/run/samba/locks/cache</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536408"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536414"></a>
 
 <a name="CASESIGNAMES"></a>casesignames
-</h3></div></div></div><a class="indexterm" name="id2536409"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#CASESENSITIVE">case sensitive</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536434"></a>
+</h3></div></div></div><a class="indexterm" name="id2536415"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#CASESENSITIVE">case sensitive</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536440"></a>
 
 case sensitive (S)
-</h3></div></div></div><a class="indexterm" name="id2536436"></a><a name="CASESENSITIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>See the discussion in the section <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>case sensitive</code></em> = <code class="literal">no</code>
+</h3></div></div></div><a class="indexterm" name="id2536442"></a><a name="CASESENSITIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>See the discussion in the section <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>case sensitive</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536481"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536487"></a>
 
 change notify (S)
-</h3></div></div></div><a class="indexterm" name="id2536482"></a><a name="CHANGENOTIFY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should reply
+</h3></div></div></div><a class="indexterm" name="id2536488"></a><a name="CHANGENOTIFY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should reply
 	to a client's file change notify requests.
 	</p><p>You should never need to change this parameter</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>change notify</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536524"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536530"></a>
 
 change share command (G)
-</h3></div></div></div><a class="indexterm" name="id2536525"></a><a name="CHANGESHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2536531"></a><a name="CHANGESHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
 Manager.  The <em class="parameter"><code>change share command</code></em> is used to define an external
 program or script which will modify an existing service definition in <code class="filename">smb.conf</code>.
@@ -976,10 +976,10 @@ program or script which will modify an existing service definition in <code clas
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>change share command</code></em> = <code class="literal">/usr/local/bin/changeshare</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536703"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536709"></a>
 
 check password script (G)
-</h3></div></div></div><a class="indexterm" name="id2536704"></a><a name="CHECKPASSWORDSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>The name of a program that can be used to check password
+</h3></div></div></div><a class="indexterm" name="id2536710"></a><a name="CHECKPASSWORDSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>The name of a program that can be used to check password
     complexity. The password is sent to the program's standard input.</p><p>The program must return 0 on a good password, or any other value
     if the password is bad.
     In case the password is considered weak (the program does not return 0) the
@@ -988,10 +988,10 @@ check password script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>check password script</code></em> = <code class="literal">/usr/local/sbin/crackcheck</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536776"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536782"></a>
 
 client lanman auth (G)
-</h3></div></div></div><a class="indexterm" name="id2536777"></a><a name="CLIENTLANMANAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbclient.8.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(8)</span></a> and other samba client
+</h3></div></div></div><a class="indexterm" name="id2536783"></a><a name="CLIENTLANMANAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbclient.8.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(8)</span></a> and other samba client
     tools will attempt to authenticate itself to servers using the
     weaker LANMAN password hash. If disabled, only server which support NT 
     password hashes (e.g. Windows NT/2000, Samba, etc... but not 
@@ -1002,10 +1002,10 @@ client lanman auth (G)
     auth</code> parameter is enabled, then only NTLMv2 logins will be
     attempted.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client lanman auth</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536852"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536858"></a>
 
 client ldap sasl wrapping (G)
-</h3></div></div></div><a class="indexterm" name="id2536853"></a><a name="CLIENTLDAPSASLWRAPPING"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2536859"></a><a name="CLIENTLDAPSASLWRAPPING"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The <a class="link" href="smb.conf.5.html#CLIENTLDAPSASLWRAPPING" target="_top">client ldap sasl wrapping</a> defines whether
 	ldap traffic will be signed or signed and encrypted (sealed). 
 	Possible values are <span class="emphasis"><em>plain</em></span>, <span class="emphasis"><em>sign</em></span> 
@@ -1033,10 +1033,10 @@ client ldap sasl wrapping (G)
 	<span class="emphasis"><em>seal</em></span>.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client ldap sasl wrapping</code></em> = <code class="literal">plain</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536968"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2536974"></a>
 
 client ntlmv2 auth (G)
-</h3></div></div></div><a class="indexterm" name="id2536969"></a><a name="CLIENTNTLMV2AUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbclient.8.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(8)</span></a> will attempt to
+</h3></div></div></div><a class="indexterm" name="id2536975"></a><a name="CLIENTNTLMV2AUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbclient.8.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(8)</span></a> will attempt to
     authenticate itself to servers using the NTLMv2 encrypted password
     response.</p><p>If enabled, only an NTLMv2 and LMv2 response (both much more
     secure than earlier versions) will be sent.  Many servers
@@ -1048,16 +1048,16 @@ client ntlmv2 auth (G)
     those following 'best practice' security polices) only allow NTLMv2
 	responses, and not the weaker LM or NTLM.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client ntlmv2 auth</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537055"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537061"></a>
 
 client plaintext auth (G)
-</h3></div></div></div><a class="indexterm" name="id2537056"></a><a name="CLIENTPLAINTEXTAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies whether a client should send a plaintext 
+</h3></div></div></div><a class="indexterm" name="id2537062"></a><a name="CLIENTPLAINTEXTAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies whether a client should send a plaintext 
 		password if the server does not support encrypted passwords.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client plaintext auth</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537094"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537100"></a>
 
 client schannel (G)
-</h3></div></div></div><a class="indexterm" name="id2537095"></a><a name="CLIENTSCHANNEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2537101"></a><a name="CLIENTSCHANNEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This controls whether the client offers or even demands the use of the netlogon schannel.
     <a class="link" href="smb.conf.5.html#CLIENTSCHANNEL" target="_top">client schannel = no</a> does not offer the schannel, 
     <a class="link" href="smb.conf.5.html#CLIENTSCHANNEL" target="_top">client schannel = auto</a> offers the schannel but does not
@@ -1067,10 +1067,10 @@ client schannel (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>client schannel</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537178"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537184"></a>
 
 client signing (G)
-</h3></div></div></div><a class="indexterm" name="id2537179"></a><a name="CLIENTSIGNING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether the client is allowed or required to use SMB signing. Possible values 
+</h3></div></div></div><a class="indexterm" name="id2537185"></a><a name="CLIENTSIGNING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether the client is allowed or required to use SMB signing. Possible values 
     are <span class="emphasis"><em>auto</em></span>, <span class="emphasis"><em>mandatory</em></span> 
     and <span class="emphasis"><em>disabled</em></span>. 
     </p><p>When set to auto, SMB signing is offered, but not enforced. 
@@ -1078,19 +1078,19 @@ client signing (G)
 	to disabled, SMB signing is not offered either.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client signing</code></em> = <code class="literal">auto</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537233"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537239"></a>
 
 client use spnego (G)
-</h3></div></div></div><a class="indexterm" name="id2537234"></a><a name="CLIENTUSESPNEGO"></a><div class="variablelist"><dl><dt></dt><dd><p> This variable controls whether Samba clients will try 
+</h3></div></div></div><a class="indexterm" name="id2537240"></a><a name="CLIENTUSESPNEGO"></a><div class="variablelist"><dl><dt></dt><dd><p> This variable controls whether Samba clients will try 
     to use Simple and Protected NEGOciation (as specified by rfc2478) with 
     supporting servers (including WindowsXP, Windows2000 and Samba
     3.0) to agree upon an authentication
     mechanism.  This enables Kerberos authentication in particular.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>client use spnego</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537275"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537281"></a>
 
 cluster addresses (G)
-</h3></div></div></div><a class="indexterm" name="id2537276"></a><a name="CLUSTERADDRESSES"></a><div class="variablelist"><dl><dt></dt><dd><p>With this parameter you can add additional addresses
+</h3></div></div></div><a class="indexterm" name="id2537282"></a><a name="CLUSTERADDRESSES"></a><div class="variablelist"><dl><dt></dt><dd><p>With this parameter you can add additional addresses
 	nmbd will register with a WINS server. These addresses are not
 	necessarily present on all nodes simultaneously, but they will
 	be registered with the WINS server so that clients can contact
@@ -1099,20 +1099,20 @@ cluster addresses (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>cluster addresses</code></em> = <code class="literal">10.0.0.1 10.0.0.2 10.0.0.3</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537331"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537337"></a>
 
 clustering (G)
-</h3></div></div></div><a class="indexterm" name="id2537332"></a><a name="CLUSTERING"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should contact
+</h3></div></div></div><a class="indexterm" name="id2537338"></a><a name="CLUSTERING"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should contact
 	ctdb for accessing its tdb files and use ctdb as a backend
 	for its messaging backend.
 	</p><p>Set this parameter to <code class="literal">yes</code> only if
 	you have a cluster setup with ctdb running.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>clustering</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537380"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537386"></a>
 
 comment (S)
-</h3></div></div></div><a class="indexterm" name="id2537381"></a><a name="COMMENT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a text field that is seen next to a share 
+</h3></div></div></div><a class="indexterm" name="id2537387"></a><a name="COMMENT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a text field that is seen next to a share 
 	when a client does a queries the server, either via the network 
 	neighborhood or via <code class="literal">net view</code> to list what shares 
 	are available.</p><p>If you want to set the string that is displayed next to the 
@@ -1121,10 +1121,10 @@ comment (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>comment</code></em> = <code class="literal">Fred's Files</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537454"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537460"></a>
 
 config backend (G)
-</h3></div></div></div><a class="indexterm" name="id2537455"></a><a name="CONFIGBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2537461"></a><a name="CONFIGBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 		This controls the backend for storing the configuration.
 		Possible values are <span class="emphasis"><em>file</em></span> (the default)
 		and <span class="emphasis"><em>registry</em></span>.
@@ -1142,10 +1142,10 @@ config backend (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>config backend</code></em> = <code class="literal">registry</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537543"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537549"></a>
 
 config file (G)
-</h3></div></div></div><a class="indexterm" name="id2537544"></a><a name="CONFIGFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>This allows you to override the config file 
+</h3></div></div></div><a class="indexterm" name="id2537550"></a><a name="CONFIGFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>This allows you to override the config file 
 	to use, instead of the default (usually <code class="filename">smb.conf</code>). 
 	There is a chicken and egg problem here as this option is set 
 	in the config file!</p><p>For this reason, if the name of the config file has changed 
@@ -1155,10 +1155,10 @@ config file (G)
 	(allowing you to special case the config files of just a few 
 	clients).</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>config file</code></em> = <code class="literal">/usr/local/samba/lib/smb.conf.%m</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537608"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537614"></a>
 
 copy (S)
-</h3></div></div></div><a class="indexterm" name="id2537610"></a><a name="COPY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows you to "clone" service 
+</h3></div></div></div><a class="indexterm" name="id2537616"></a><a name="COPY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows you to "clone" service 
 	entries. The specified service is simply duplicated under the 
 	current service's name. Any parameters specified in the current 
 	section will override those in the section being copied.</p><p>This feature lets you set up a 'template' service and 
@@ -1168,29 +1168,13 @@ copy (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>copy</code></em> = <code class="literal">otherservice</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537671"></a>
-
-create krb5 conf (G)
-</h3></div></div></div><a class="indexterm" name="id2537672"></a><a name="CREATEKRB5CONF"></a><div class="variablelist"><dl><dt></dt><dd><p>
-	Setting this paramter to <code class="literal">no</code> prevents
-	winbind from creating custom krb5.conf files. Winbind normally does
-	this because the krb5 libraries are not AD-site-aware and thus would
-	pick any domain controller out of potentially very many. Winbind
-	is site-aware and makes the krb5 libraries use a local DC by
-	creating its own krb5.conf files.
-	</p><p>
-	Preventing winbind from doing this might become necessary if you
-	have to add special options into your system-krb5.conf that winbind
-	does not see.
-	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>create krb5 conf</code></em> = <code class="literal">yes</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537724"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537677"></a>
 
 <a name="CREATEMODE"></a>create mode
-</h3></div></div></div><a class="indexterm" name="id2537725"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#CREATEMASK">create mask</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537751"></a>
+</h3></div></div></div><a class="indexterm" name="id2537678"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#CREATEMASK">create mask</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537704"></a>
 
 create mask (S)
-</h3></div></div></div><a class="indexterm" name="id2537752"></a><a name="CREATEMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2537705"></a><a name="CREATEMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to
 	UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may
 	be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit <span class="emphasis"><em>not</em></span> set here will
@@ -1211,10 +1195,10 @@ create mask (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>create mask</code></em> = <code class="literal">0775</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2481437"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537825"></a>
 
 csc policy (S)
-</h3></div></div></div><a class="indexterm" name="id2481438"></a><a name="CSCPOLICY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2537826"></a><a name="CSCPOLICY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This stands for <span class="emphasis"><em>client-side caching policy</em></span>, and specifies how clients capable of offline
 	caching will cache the files in the share. The valid values are: manual, documents, programs, disable.
 	</p><p>
@@ -1226,10 +1210,10 @@ csc policy (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>csc policy</code></em> = <code class="literal">programs</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538100"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537900"></a>
 
 ctdbd socket (G)
-</h3></div></div></div><a class="indexterm" name="id2538102"></a><a name="CTDBDSOCKET"></a><div class="variablelist"><dl><dt></dt><dd><p>If you set <code class="literal">clustering=yes</code>,
+</h3></div></div></div><a class="indexterm" name="id2537902"></a><a name="CTDBDSOCKET"></a><div class="variablelist"><dl><dt></dt><dd><p>If you set <code class="literal">clustering=yes</code>,
 	you need to tell Samba where ctdbd listens on its unix domain
 	socket. The default path as of ctdb 1.0 is /tmp/ctdb.socket which
 	you have to explicitly set for Samba in smb.conf.
@@ -1237,39 +1221,10 @@ ctdbd socket (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ctdbd socket</code></em> = <code class="literal">/tmp/ctdb.socket</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538160"></a>
-
-ctdb timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2538161"></a><a name="CTDBTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a timeout in seconds for the
-	  connection between Samba and ctdb. It is only valid if you
-	  have compiled Samba with clustering and if you have
-	  set <em class="parameter"><code>clustering=yes</code></em>.
-	</p><p>When something in the cluster blocks, it can happen that
-	  we wait indefinitely long for ctdb, just adding to the
-	  blocking condition. In a well-running cluster this should
-	  never happen, but there are too many components in a cluster
-	  that might have hickups. Choosing the right balance for this
-	  value is very tricky, because on a busy cluster long service
-	  times to transfer something across the cluster might be
-	  valid. Setting it too short will degrade the service your
-	  cluster presents, setting it too long might make the cluster
-	  itself not recover from something severely broken for too
-	  long.
-	</p><p>
-	  Be aware that if you set this parameter, this needs to be in
-	  the file smb.conf, it is not really helpful to put this into
-	  a registry configuration (typical on a cluster), because to
-	  access the registry contact to ctdb is requred.
-	</p><p>Setting <em class="parameter"><code>ctdb timeout</code></em> to n makes
-	  any process waiting longer than n seconds for a reply by the
-	  cluster panic. Setting it to 0 (the default) makes Samba
-	  block forever, which is the highly recommended default.
-	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ctdb timeout</code></em> = <code class="literal">0</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538238"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2537960"></a>
 
 cups connection timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2538240"></a><a name="CUPSCONNECTIONTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2537961"></a><a name="CUPSCONNECTIONTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter is only applicable if <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> is set to <code class="constant">cups</code>.
     </p><p>
    If set, this option specifies the number of seconds that smbd will wait
@@ -1279,26 +1234,10 @@ cups connection timeout (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>cups connection timeout</code></em> = <code class="literal">60</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538310"></a>
-
-cups encrypt (G)
-</h3></div></div></div><a class="indexterm" name="id2538311"></a><a name="CUPSENCRYPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
-	This parameter is only applicable if <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a>
-	is set to <code class="constant">cups</code> and if you use CUPS newer than
-	1.0.x.It is used to define whether or not Samba should use encryption
-	when talking to the CUPS server. Possible values are
-	<span class="emphasis"><em>auto</em></span>, <span class="emphasis"><em>yes</em></span> and
-	<span class="emphasis"><em>no</em></span>
-	</p><p>
-	When set to auto we will try to do a TLS handshake on each CUPS
-	connection setup. If that fails, we will fall back to unencrypted
-	operation.
-	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>cups encrypt</code></em> = <code class="literal">"no"</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538377"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538032"></a>
 
 cups options (S)
-</h3></div></div></div><a class="indexterm" name="id2538378"></a><a name="CUPSOPTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538033"></a><a name="CUPSOPTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter is only applicable if <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> is 
     set to <code class="constant">cups</code>.  Its value is a free form string of options
     passed directly to the cups library.  
@@ -1320,10 +1259,10 @@ cups options (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>cups options</code></em> = <code class="literal">"raw media=a4"</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538475"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2481393"></a>
 
 cups server (G)
-</h3></div></div></div><a class="indexterm" name="id2538476"></a><a name="CUPSSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2481394"></a><a name="CUPSSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter is only applicable if <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> is set to <code class="constant">cups</code>.
     </p><p>
    If set, this option overrides the ServerName option in the CUPS <code class="filename">client.conf</code>. This is 
@@ -1337,10 +1276,10 @@ cups server (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>cups server</code></em> = <code class="literal">mycupsserver:1631</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538573"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538376"></a>
 
 deadtime (G)
-</h3></div></div></div><a class="indexterm" name="id2538574"></a><a name="DEADTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a decimal integer) 
+</h3></div></div></div><a class="indexterm" name="id2538377"></a><a name="DEADTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a decimal integer) 
     represents the number of minutes of inactivity before a connection 
     is considered dead, and it is disconnected. The deadtime only takes 
     effect if the number of open files is zero.</p><p>This is useful to stop a server's resources being 
@@ -1352,10 +1291,10 @@ deadtime (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>deadtime</code></em> = <code class="literal">15</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538650"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538453"></a>
 
 debug class (G)
-</h3></div></div></div><a class="indexterm" name="id2538651"></a><a name="DEBUGCLASS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538454"></a><a name="DEBUGCLASS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     With this boolean parameter enabled, the debug class (DBGC_CLASS) 
     will be displayed in the debug header.
     </p><p>
@@ -1363,20 +1302,20 @@ debug class (G)
     section about <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a>.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug class</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538702"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538504"></a>
 
 debug hires timestamp (G)
-</h3></div></div></div><a class="indexterm" name="id2538703"></a><a name="DEBUGHIRESTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538506"></a><a name="DEBUGHIRESTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
     Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this 
     boolean parameter adds microsecond resolution to the timestamp  message header when turned on.
     </p><p>
     Note that the parameter <a class="link" href="smb.conf.5.html#DEBUGTIMESTAMP" target="_top">debug timestamp</a> must be on for this to have an effect.
-    </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug hires timestamp</code></em> = <code class="literal">yes</code>
+    </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug hires timestamp</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538756"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538559"></a>
 
 debug pid (G)
-</h3></div></div></div><a class="indexterm" name="id2538757"></a><a name="DEBUGPID"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538560"></a><a name="DEBUGPID"></a><div class="variablelist"><dl><dt></dt><dd><p>
     When using only one log file for more then one forked <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>-process there may be hard to follow which process outputs which 
     message. This boolean parameter is adds the process-id to the timestamp message headers in the
     logfile when turned on.
@@ -1384,10 +1323,10 @@ debug pid (G)
     Note that the parameter <a class="link" href="smb.conf.5.html#DEBUGTIMESTAMP" target="_top">debug timestamp</a> must be on for this to have an effect.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug pid</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538818"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538621"></a>
 
 debug prefix timestamp (G)
-</h3></div></div></div><a class="indexterm" name="id2538819"></a><a name="DEBUGPREFIXTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538622"></a><a name="DEBUGPREFIXTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
     With this option enabled, the timestamp message header is prefixed to the debug message without the
     filename and function information that is included with the <a class="link" href="smb.conf.5.html#DEBUGTIMESTAMP" target="_top">debug timestamp</a> 
     parameter. This gives timestamps to the messages without adding an additional line.
@@ -1395,32 +1334,32 @@ debug prefix timestamp (G)
     Note that this parameter overrides the <a class="link" href="smb.conf.5.html#DEBUGTIMESTAMP" target="_top">debug timestamp</a> parameter.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug prefix timestamp</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538882"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538684"></a>
 
 <a name="TIMESTAMPLOGS"></a>timestamp logs
-</h3></div></div></div><a class="indexterm" name="id2538883"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DEBUGTIMESTAMP">debug timestamp</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538909"></a>
+</h3></div></div></div><a class="indexterm" name="id2538686"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DEBUGTIMESTAMP">debug timestamp</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538711"></a>
 
 debug timestamp (G)
-</h3></div></div></div><a class="indexterm" name="id2538910"></a><a name="DEBUGTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538712"></a><a name="DEBUGTIMESTAMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
     Samba debug log messages are timestamped by default. If you are running at a high 
     <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debug level</a> these timestamps can be distracting. This 
     boolean parameter allows timestamping to be turned off.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug timestamp</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538957"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538760"></a>
 
 debug uid (G)
-</h3></div></div></div><a class="indexterm" name="id2538958"></a><a name="DEBUGUID"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538761"></a><a name="DEBUGUID"></a><div class="variablelist"><dl><dt></dt><dd><p>
     Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the 
     current euid, egid, uid and gid to the timestamp message headers in the log file if turned on.
     </p><p>
     Note that the parameter <a class="link" href="smb.conf.5.html#DEBUGTIMESTAMP" target="_top">debug timestamp</a> must be on for this to have an effect.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>debug uid</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539011"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538814"></a>
 
 dedicated keytab file (G)
-</h3></div></div></div><a class="indexterm" name="id2539012"></a><a name="DEDICATEDKEYTABFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538815"></a><a name="DEDICATEDKEYTABFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	  Specifies the path to the kerberos keytab file when
 	  <a class="link" href="smb.conf.5.html#KERBEROSMETHOD" target="_top">kerberos method</a> is set to "dedicated
 	  keytab".
@@ -1428,16 +1367,16 @@ dedicated keytab file (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>dedicated keytab file</code></em> = <code class="literal">/usr/local/etc/krb5.keytab</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539073"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538876"></a>
 
 default case (S)
-</h3></div></div></div><a class="indexterm" name="id2539074"></a><a name="DEFAULTCASE"></a><div class="variablelist"><dl><dt></dt><dd><p>See the section on <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a>.
+</h3></div></div></div><a class="indexterm" name="id2538877"></a><a name="DEFAULTCASE"></a><div class="variablelist"><dl><dt></dt><dd><p>See the section on <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a>.
 	Also note the <a class="link" href="smb.conf.5.html#SHORTPRESERVECASE" target="_top">short preserve case</a> parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>default case</code></em> = <code class="literal">lower</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539127"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538930"></a>
 
 default devmode (S)
-</h3></div></div></div><a class="indexterm" name="id2539128"></a><a name="DEFAULTDEVMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only applicable to <a class="link" href="smb.conf.5.html#PRINTABLE" target="_top">printable</a> services.
+</h3></div></div></div><a class="indexterm" name="id2538931"></a><a name="DEFAULTDEVMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only applicable to <a class="link" href="smb.conf.5.html#PRINTABLE" target="_top">printable</a> services.
     When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
     server has a Device Mode which defines things such as paper size and
     orientation and duplex settings.  The device mode can only correctly be
@@ -1460,13 +1399,13 @@ default devmode (S)
     see the <a class="ulink" href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a>.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>default devmode</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539215"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539018"></a>
 
 <a name="DEFAULT"></a>default
-</h3></div></div></div><a class="indexterm" name="id2539216"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DEFAULTSERVICE">default service</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539242"></a>
+</h3></div></div></div><a class="indexterm" name="id2539019"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DEFAULTSERVICE">default service</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539045"></a>
 
 default service (G)
-</h3></div></div></div><a class="indexterm" name="id2539243"></a><a name="DEFAULTSERVICE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the name of a service
+</h3></div></div></div><a class="indexterm" name="id2539046"></a><a name="DEFAULTSERVICE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the name of a service
 	which will be connected to if the service actually requested cannot
 	be found. Note that the square brackets are <span class="emphasis"><em>NOT</em></span>
 	given in the parameter value (see example below).</p><p>There is no default value for this parameter. If this 
@@ -1480,10 +1419,10 @@ default service (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>default service</code></em> = <code class="literal">pub</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539344"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539146"></a>
 
 defer sharing violations (G)
-</h3></div></div></div><a class="indexterm" name="id2539345"></a><a name="DEFERSHARINGVIOLATIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2539148"></a><a name="DEFERSHARINGVIOLATIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Windows allows specifying how a file will be shared with 
 	other processes when it is opened. Sharing violations occur when 
 	a file is opened by a different process using options that violate 
@@ -1496,19 +1435,19 @@ defer sharing violations (G)
 	designed to enable Samba to more correctly emulate Windows.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>defer sharing violations</code></em> = <code class="literal">True</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539399"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539201"></a>
 
 delete group script (G)
-</h3></div></div></div><a class="indexterm" name="id2539400"></a><a name="DELETEGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the full pathname to a script that will 
+</h3></div></div></div><a class="indexterm" name="id2539202"></a><a name="DELETEGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the full pathname to a script that will 
 	be run <span class="emphasis"><em>AS ROOT</em></span> <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when a group is requested to be deleted. 
 	It will expand any <em class="parameter"><code>%g</code></em> to the group name passed.  
 	This script is only useful for installations using the Windows NT domain administration tools.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>delete group script</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539455"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539258"></a>
 
 deleteprinter command (G)
-</h3></div></div></div><a class="indexterm" name="id2539456"></a><a name="DELETEPRINTERCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printer
+</h3></div></div></div><a class="indexterm" name="id2539259"></a><a name="DELETEPRINTERCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printer
     support for Windows NT/2000 clients in Samba 2.2, it is now 
     possible to delete a printer at run time by issuing the
     DeletePrinter() RPC call.</p><p>For a Samba host this means that the printer must be 
@@ -1526,18 +1465,18 @@ deleteprinter command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>deleteprinter command</code></em> = <code class="literal">/usr/bin/removeprinter</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539582"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539385"></a>
 
 delete readonly (S)
-</h3></div></div></div><a class="indexterm" name="id2539583"></a><a name="DELETEREADONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows readonly files to be deleted.  
+</h3></div></div></div><a class="indexterm" name="id2539386"></a><a name="DELETEREADONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows readonly files to be deleted.  
 	This is not normal DOS semantics, but is allowed by UNIX.</p><p>This option may be useful for running applications such 
 	as rcs, where UNIX file ownership prevents changing file 
 	permissions, and DOS semantics prevent deletion of a read only file.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>delete readonly</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539627"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539430"></a>
 
 delete share command (G)
-</h3></div></div></div><a class="indexterm" name="id2539628"></a><a name="DELETESHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2539431"></a><a name="DELETESHARECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
 	Manager.  The <em class="parameter"><code>delete share command</code></em> is used to define an external
 	program or script which will remove an existing service definition from
@@ -1563,10 +1502,10 @@ delete share command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>delete share command</code></em> = <code class="literal">/usr/local/bin/delshare</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539779"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539582"></a>
 
 delete user from group script (G)
-</h3></div></div></div><a class="indexterm" name="id2539780"></a><a name="DELETEUSERFROMGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>Full path to the script that will be called when 
+</h3></div></div></div><a class="indexterm" name="id2539583"></a><a name="DELETEUSERFROMGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>Full path to the script that will be called when 
 	a user is removed from a group using the Windows NT domain administration 
 	tools. It will be run by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> <span class="emphasis"><em>AS ROOT</em></span>. 
 	Any <em class="parameter"><code>%g</code></em> will be replaced with the group name and 
@@ -1575,10 +1514,10 @@ delete user from group script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>delete user from group script</code></em> = <code class="literal">/usr/sbin/deluser %u %g</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539859"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539662"></a>
 
 delete user script (G)
-</h3></div></div></div><a class="indexterm" name="id2539860"></a><a name="DELETEUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the full pathname to a script that will 
+</h3></div></div></div><a class="indexterm" name="id2539663"></a><a name="DELETEUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the full pathname to a script that will 
 	be run by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when managing users 
 	with remote RPC (NT) tools.
 	</p><p>This script is called when a remote client removes a user
@@ -1587,10 +1526,10 @@ delete user script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>delete user script</code></em> = <code class="literal">/usr/local/samba/bin/del_user %u</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539935"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539738"></a>
 
 delete veto files (S)
-</h3></div></div></div><a class="indexterm" name="id2539936"></a><a name="DELETEVETOFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used when Samba is attempting to 
+</h3></div></div></div><a class="indexterm" name="id2539739"></a><a name="DELETEVETOFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used when Samba is attempting to 
 	delete a directory that contains one or more vetoed directories 
 	(see the <a class="link" href="smb.conf.5.html#VETOFILES" target="_top">veto files</a>
 	option).  If this option is set to <code class="constant">no</code> (the default) then if a vetoed 
@@ -1604,10 +1543,10 @@ delete veto files (S)
 	directories to be  transparently deleted when the parent directory 
 	is deleted (so long as the user has permissions to do so).</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>delete veto files</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540021"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539824"></a>
 
 dfree cache time (S)
-</h3></div></div></div><a class="indexterm" name="id2540022"></a><a name="DFREECACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2539825"></a><a name="DFREECACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The <em class="parameter"><code>dfree cache time</code></em> should only be used on systems where a problem
 	occurs with the internal disk space calculations. This has been known to happen with Ultrix, but may occur
 	with other operating systems. The symptom that was seen was an error of "Abort Retry Ignore" at the
@@ -1620,10 +1559,10 @@ dfree cache time (S)
 	By default this parameter is zero, meaning no caching will be done.
 	</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>dfree cache time</code></em> = <code class="literal">dfree cache time = 60</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540093"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2539896"></a>
 
 dfree command (S)
-</h3></div></div></div><a class="indexterm" name="id2540094"></a><a name="DFREECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2539897"></a><a name="DFREECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The <em class="parameter"><code>dfree command</code></em> setting should only be used on systems where a
 	problem occurs with the internal disk space calculations. This has been known to happen with Ultrix, but may
 	occur with other operating systems. The symptom that was seen was an error of "Abort Retry Ignore"
@@ -1661,13 +1600,13 @@ df $1 | tail -1 | awk '{print $(NF-4),$(NF-2)}'
 	By default internal routines for determining the disk capacity and remaining space will be used.
 	</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>dfree command</code></em> = <code class="literal">/usr/local/samba/bin/dfree</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540215"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540018"></a>
 
 <a name="DIRECTORYMODE"></a>directory mode
-</h3></div></div></div><a class="indexterm" name="id2540216"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DIRECTORYMASK">directory mask</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540242"></a>
+</h3></div></div></div><a class="indexterm" name="id2540019"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#DIRECTORYMASK">directory mask</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540045"></a>
 
 directory mask (S)
-</h3></div></div></div><a class="indexterm" name="id2540243"></a><a name="DIRECTORYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is the octal modes which are 
+</h3></div></div></div><a class="indexterm" name="id2540046"></a><a name="DIRECTORYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is the octal modes which are 
     used when converting DOS modes to UNIX modes when creating UNIX 
     directories.</p><p>When a directory is created, the necessary permissions are 
     calculated according to the mapping from DOS modes to UNIX permissions, 
@@ -1685,18 +1624,18 @@ directory mask (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>directory mask</code></em> = <code class="literal">0775</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540347"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540150"></a>
 
 directory name cache size (S)
-</h3></div></div></div><a class="indexterm" name="id2540348"></a><a name="DIRECTORYNAMECACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2540151"></a><a name="DIRECTORYNAMECACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the the size of the directory name cache.
 	It will be needed to turn this off for *BSD systems.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>directory name cache size</code></em> = <code class="literal">100</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540387"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540190"></a>
 
 directory security mask (S)
-</h3></div></div></div><a class="indexterm" name="id2540388"></a><a name="DIRECTORYSECURITYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls what UNIX permission bits
+</h3></div></div></div><a class="indexterm" name="id2540191"></a><a name="DIRECTORYSECURITYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls what UNIX permission bits
     will be set when a Windows NT client is manipulating the UNIX
     permission on a directory using the native NT security dialog
     box.</p><p>
@@ -1716,19 +1655,19 @@ directory security mask (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>directory security mask</code></em> = <code class="literal">0700</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540487"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540290"></a>
 
 disable netbios (G)
-</h3></div></div></div><a class="indexterm" name="id2540488"></a><a name="DISABLENETBIOS"></a><div class="variablelist"><dl><dt></dt><dd><p>Enabling this parameter will disable netbios support
+</h3></div></div></div><a class="indexterm" name="id2540291"></a><a name="DISABLENETBIOS"></a><div class="variablelist"><dl><dt></dt><dd><p>Enabling this parameter will disable netbios support
     in Samba. Netbios is the only available form of browsing in 
     all windows versions except for 2000 and XP. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Clients that only support netbios won't be able to 
     see your samba server when netbios support is disabled.
 	</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>disable netbios</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540533"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540336"></a>
 
 disable spoolss (G)
-</h3></div></div></div><a class="indexterm" name="id2540534"></a><a name="DISABLESPOOLSS"></a><div class="variablelist"><dl><dt></dt><dd><p>Enabling this parameter will disable Samba's support
+</h3></div></div></div><a class="indexterm" name="id2540337"></a><a name="DISABLESPOOLSS"></a><div class="variablelist"><dl><dt></dt><dd><p>Enabling this parameter will disable Samba's support
     for the SPOOLSS set of MS-RPC's and will yield identical behavior
     as Samba 2.0.x.  Windows NT/2000 clients will downgrade to using
     Lanman style printing commands. Windows 9x/ME will be unaffected by
@@ -1740,10 +1679,10 @@ disable spoolss (G)
     <span class="emphasis"><em>Be very careful about enabling this parameter.</em></span>
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>disable spoolss</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540584"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540387"></a>
 
 display charset (G)
-</h3></div></div></div><a class="indexterm" name="id2540585"></a><a name="DISPLAYCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2540388"></a><a name="DISPLAYCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Specifies the charset that samba will use to print messages to stdout and stderr.
 	The default value is "LOCALE", which means automatically set, depending on the
 	current locale. The value should generally be the same as the value of the parameter
@@ -1752,10 +1691,10 @@ display charset (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>display charset</code></em> = <code class="literal">UTF8</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540651"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540454"></a>
 
 dmapi support (S)
-</h3></div></div></div><a class="indexterm" name="id2540652"></a><a name="DMAPISUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should use DMAPI to
+</h3></div></div></div><a class="indexterm" name="id2540455"></a><a name="DMAPISUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should use DMAPI to
 	determine whether a file is offline or not. This would typically
 	be used in conjunction with a hierarchical storage system that
 	automatically migrates files to tape.
@@ -1770,10 +1709,10 @@ dmapi support (S)
 	</p><p>
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dmapi support</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540710"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540512"></a>
 
 dns proxy (G)
-</h3></div></div></div><a class="indexterm" name="id2540711"></a><a name="DNSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies that <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> when acting as a WINS server and 
+</h3></div></div></div><a class="indexterm" name="id2540514"></a><a name="DNSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies that <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> when acting as a WINS server and 
 	finding that a NetBIOS name has not been registered, should treat the 
 	NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server 
 	for that name on behalf of the name-querying client.</p><p>Note that the maximum length for a NetBIOS name is 15 
@@ -1782,10 +1721,10 @@ dns proxy (G)
 	DNS name lookup requests, as doing a name lookup is a blocking 
 	action.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dns proxy</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540773"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540576"></a>
 
 domain logons (G)
-</h3></div></div></div><a class="indexterm" name="id2540774"></a><a name="DOMAINLOGONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2540577"></a><a name="DOMAINLOGONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If set to <code class="constant">yes</code>, the Samba server will
 	provide the netlogon service for Windows 9X network logons for the
 	<a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> it is in.
@@ -1795,10 +1734,10 @@ domain logons (G)
 	Samba HOWTO Collection.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>domain logons</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540827"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540629"></a>
 
 domain master (G)
-</h3></div></div></div><a class="indexterm" name="id2540828"></a><a name="DOMAINMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2540630"></a><a name="DOMAINMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Tell <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> to enable
 	WAN-wide browse list collation. Setting this option causes <code class="literal">nmbd</code> to claim a
 	special domain specific NetBIOS name that identifies it as a domain master browser for its given
@@ -1824,10 +1763,10 @@ domain master (G)
 	Samba will function as a BDC. In general, this parameter should be set to 'No' only on a BDC.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>domain master</code></em> = <code class="literal">auto</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541018"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540820"></a>
 
 dont descend (S)
-</h3></div></div></div><a class="indexterm" name="id2541019"></a><a name="DONTDESCEND"></a><div class="variablelist"><dl><dt></dt><dd><p>There are certain directories on some systems 
+</h3></div></div></div><a class="indexterm" name="id2540822"></a><a name="DONTDESCEND"></a><div class="variablelist"><dl><dt></dt><dd><p>There are certain directories on some systems 
 	(e.g., the <code class="filename">/proc</code> tree under Linux) that are either not 
 	of interest to clients or are infinitely deep (recursive). This 
 	parameter allows you to specify a comma-delimited list of directories 
@@ -1838,18 +1777,18 @@ dont descend (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>dont descend</code></em> = <code class="literal">/proc,/dev</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541096"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540899"></a>
 
 dos charset (G)
-</h3></div></div></div><a class="indexterm" name="id2541097"></a><a name="DOSCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>DOS SMB clients assume the server has 
+</h3></div></div></div><a class="indexterm" name="id2540900"></a><a name="DOSCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>DOS SMB clients assume the server has 
 	the same charset as they do. This option specifies which 
 	charset Samba should talk to DOS clients.
 	</p><p>The default depends on which charsets you have installed. 
 	Samba tries to use charset 850 but falls back to ASCII in 
-	case it is not available. Run <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a> to check the default on your system.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541137"></a>
+	case it is not available. Run <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a> to check the default on your system.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540940"></a>
 
 dos filemode (S)
-</h3></div></div></div><a class="indexterm" name="id2541138"></a><a name="DOSFILEMODE"></a><div class="variablelist"><dl><dt></dt><dd><p> The default behavior in Samba is to provide
+</h3></div></div></div><a class="indexterm" name="id2540941"></a><a name="DOSFILEMODE"></a><div class="variablelist"><dl><dt></dt><dd><p> The default behavior in Samba is to provide
 	UNIX-like behavior where only the owner of a file/directory is
 	able to change the permissions on it.  However, this behavior
 	is often confusing to  DOS/Windows users.  Enabling this parameter
@@ -1858,18 +1797,12 @@ dos filemode (S)
 	(including ACL) on it. Note that a user belonging to the group
 	owning the file will not be allowed to change permissions if
 	the group is only granted read access. Ownership of the
-	file/directory may also be changed.
-
-	Note that using the VFS modules acl_xattr or acl_tdb which store native
-	Windows as meta-data will automatically turn this option on for any
-	share for which they are loaded, as they require this option to emulate
-	Windows ACLs correctly.
-	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dos filemode</code></em> = <code class="literal">no</code>
+	file/directory may also be changed.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dos filemode</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541202"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2540986"></a>
 
 dos filetime resolution (S)
-</h3></div></div></div><a class="indexterm" name="id2541203"></a><a name="DOSFILETIMERESOLUTION"></a><div class="variablelist"><dl><dt></dt><dd><p>Under the DOS and Windows FAT filesystem, the finest 
+</h3></div></div></div><a class="indexterm" name="id2540988"></a><a name="DOSFILETIMERESOLUTION"></a><div class="variablelist"><dl><dt></dt><dd><p>Under the DOS and Windows FAT filesystem, the finest 
 	granularity on time resolution is two seconds. Setting this parameter 
 	for a share causes Samba to round the reported time down to the 
 	nearest two second boundary when a query call that requires one second 
@@ -1884,36 +1817,37 @@ dos filetime resolution (S)
 	this option causes the two timestamps to match, and Visual C++ is
 	happy.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dos filetime resolution</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541265"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541050"></a>
 
 dos filetimes (S)
-</h3></div></div></div><a class="indexterm" name="id2541266"></a><a name="DOSFILETIMES"></a><div class="variablelist"><dl><dt></dt><dd><p>Under DOS and Windows, if a user can write to a 
+</h3></div></div></div><a class="indexterm" name="id2541051"></a><a name="DOSFILETIMES"></a><div class="variablelist"><dl><dt></dt><dd><p>Under DOS and Windows, if a user can write to a 
 	file they can change the timestamp on it. Under POSIX semantics, 
 	only the owner of the file or root may change the timestamp. By 
-	default, Samba emulates the DOS semantics and allows to change the 
+	default, Samba runs with POSIX semantics and refuses to change the 
 	timestamp on a file if the user <code class="literal">smbd</code> is acting 
-	on behalf has write permissions.
-	Due to changes in Microsoft Office 2000 and beyond,
+	on behalf of is not the file owner. Setting this option to <code class="constant">
+	yes</code> allows DOS semantics and <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will change the file 
+	timestamp as DOS requires. Due to changes in Microsoft Office 2000 and beyond,
 	the default for this parameter has been changed from "no" to "yes" in Samba 3.0.14
 	and above. Microsoft Excel will display dialog box warnings about the file being
 	changed by another user if this parameter is not set to "yes" and files are being
 	shared between users.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>dos filetimes</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541319"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541116"></a>
 
 ea support (S)
-</h3></div></div></div><a class="indexterm" name="id2541320"></a><a name="EASUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will allow clients to attempt to store OS/2 style Extended
+</h3></div></div></div><a class="indexterm" name="id2541117"></a><a name="EASUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will allow clients to attempt to store OS/2 style Extended
     attributes on a share. In order to enable this parameter the underlying filesystem exported by
     the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the
     correct kernel patches). On Linux the filesystem must have been mounted with the mount
         option user_xattr in order for extended attributes to work, also
 		extended attributes must be compiled into the Linux kernel.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ea support</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541372"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541177"></a>
 
 enable asu support (G)
-</h3></div></div></div><a class="indexterm" name="id2541373"></a><a name="ENABLEASUSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>Hosts running the "Advanced Server for Unix (ASU)" product 
+</h3></div></div></div><a class="indexterm" name="id2541178"></a><a name="ENABLEASUSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>Hosts running the "Advanced Server for Unix (ASU)" product 
     require some special accomodations such as creating a builtin [ADMIN$] 
     share that only supports IPC connections.  The has been the default
     behavior in smbd for many years.  However, certain Microsoft applications
@@ -1921,20 +1855,20 @@ enable asu support (G)
     an [ADMIN$} file share.  Disabling this parameter allows for creating 
     an [ADMIN$] file share in smb.conf.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enable asu support</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541417"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541222"></a>
 
 enable core files (G)
-</h3></div></div></div><a class="indexterm" name="id2541418"></a><a name="ENABLECOREFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether core dumps should be written
+</h3></div></div></div><a class="indexterm" name="id2541223"></a><a name="ENABLECOREFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether core dumps should be written
 	on internal exits. Normally set to <code class="constant">yes</code>.
 	You should never need to change this.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enable core files</code></em> = <code class="literal">yes</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>enable core files</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541475"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541280"></a>
 
 enable privileges (G)
-</h3></div></div></div><a class="indexterm" name="id2541476"></a><a name="ENABLEPRIVILEGES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2541281"></a><a name="ENABLEPRIVILEGES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either
 	 <code class="literal">net rpc rights</code> or one of the Windows user and group manager tools.  This parameter is
 	enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to
@@ -1947,15 +1881,15 @@ enable privileges (G)
 	Please read the extended description provided in the Samba HOWTO documentation.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enable privileges</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541536"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541340"></a>
 
 enable spoolss (G)
-</h3></div></div></div><a class="indexterm" name="id2541537"></a><a name="ENABLESPOOLSS"></a><div class="variablelist"><dl><dt></dt><dd><p>Inverted synonym for <a class="link" href="smb.conf.5.html#DISABLESPOOLSS" target="_top">disable spoolss</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enable spoolss</code></em> = <code class="literal">yes</code>
+</h3></div></div></div><a class="indexterm" name="id2541342"></a><a name="ENABLESPOOLSS"></a><div class="variablelist"><dl><dt></dt><dd><p>Inverted synonym for <a class="link" href="smb.conf.5.html#DISABLESPOOLSS" target="_top">disable spoolss</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enable spoolss</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541582"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541387"></a>
 
 encrypt passwords (G)
-</h3></div></div></div><a class="indexterm" name="id2541583"></a><a name="ENCRYPTPASSWORDS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean controls whether encrypted passwords 
+</h3></div></div></div><a class="indexterm" name="id2541388"></a><a name="ENCRYPTPASSWORDS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean controls whether encrypted passwords 
     will be negotiated with the client. Note that Windows NT 4.0 SP3 and 
     above and also Windows 98 will by default expect encrypted passwords 
     unless a registry entry is changed. To use encrypted passwords in 
@@ -1978,10 +1912,10 @@ encrypt passwords (G)
     causes <code class="literal">smbd</code> to authenticate against another 
 	server.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>encrypt passwords</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541685"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541490"></a>
 
 enhanced browsing (G)
-</h3></div></div></div><a class="indexterm" name="id2541686"></a><a name="ENHANCEDBROWSING"></a><div class="variablelist"><dl><dt></dt><dd><p>This option enables a couple of enhancements to 
+</h3></div></div></div><a class="indexterm" name="id2541491"></a><a name="ENHANCEDBROWSING"></a><div class="variablelist"><dl><dt></dt><dd><p>This option enables a couple of enhancements to 
 	cross-subnet browse propagation that have been added in Samba 
 	but which are not standard in Microsoft implementations.  
 	</p><p>The first enhancement to browse propagation consists of a regular
@@ -1994,10 +1928,10 @@ enhanced browsing (G)
 	to stay around forever which can be annoying.</p><p>In general you should leave this option enabled as it makes
 	cross-subnet browse propagation much more reliable.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>enhanced browsing</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541747"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541552"></a>
 
 enumports command (G)
-</h3></div></div></div><a class="indexterm" name="id2541748"></a><a name="ENUMPORTSCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The concept of a "port" is fairly foreign
+</h3></div></div></div><a class="indexterm" name="id2541553"></a><a name="ENUMPORTSCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The concept of a "port" is fairly foreign
     to UNIX hosts.  Under Windows NT/2000 print servers, a port
     is associated with a port monitor and generally takes the form of
     a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
@@ -2014,10 +1948,10 @@ enumports command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>enumports command</code></em> = <code class="literal">/usr/bin/listports</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541827"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541632"></a>
 
 eventlog list (G)
-</h3></div></div></div><a class="indexterm" name="id2541828"></a><a name="EVENTLOGLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This option defines a list of log names that Samba will 
+</h3></div></div></div><a class="indexterm" name="id2541633"></a><a name="EVENTLOGLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This option defines a list of log names that Samba will 
     report to the Microsoft EventViewer utility.  The listed 
     eventlogs will be associated with tdb file on disk in the 
     <code class="filename">$(lockdir)/eventlog</code>.
@@ -2030,10 +1964,10 @@ eventlog list (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>eventlog list</code></em> = <code class="literal">Security Application Syslog Apache</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541907"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541705"></a>
 
 fake directory create times (S)
-</h3></div></div></div><a class="indexterm" name="id2541908"></a><a name="FAKEDIRECTORYCREATETIMES"></a><div class="variablelist"><dl><dt></dt><dd><p>NTFS and Windows VFAT file systems keep a create 
+</h3></div></div></div><a class="indexterm" name="id2541706"></a><a name="FAKEDIRECTORYCREATETIMES"></a><div class="variablelist"><dl><dt></dt><dd><p>NTFS and Windows VFAT file systems keep a create 
 	time for all files and directories. This is not the same as the 
 	ctime - status change time - that Unix keeps, so Samba by default 
 	reports the earliest of the various times Unix does keep. Setting 
@@ -2055,10 +1989,10 @@ fake directory create times (S)
 	ensures directories always predate their contents and an NMAKE build 
 	will proceed as expected.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>fake directory create times</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541979"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541773"></a>
 
 fake oplocks (S)
-</h3></div></div></div><a class="indexterm" name="id2541980"></a><a name="FAKEOPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>Oplocks are the way that SMB clients get permission 
+</h3></div></div></div><a class="indexterm" name="id2541774"></a><a name="FAKEOPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>Oplocks are the way that SMB clients get permission 
 	from a server to locally cache file operations. If a server grants 
 	an oplock (opportunistic lock) then the client is free to assume 
 	that it is the only one accessing the file and it will aggressively 
@@ -2074,10 +2008,10 @@ fake oplocks (S)
 	files read-write at the same time you can get data corruption. Use 
 	this option carefully!</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>fake oplocks</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542071"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541864"></a>
 
 follow symlinks (S)
-</h3></div></div></div><a class="indexterm" name="id2542072"></a><a name="FOLLOWSYMLINKS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2541865"></a><a name="FOLLOWSYMLINKS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter allows the Samba administrator to stop <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>	from following symbolic links in a particular share. Setting this 
 	parameter to <code class="constant">no</code> prevents any file or directory that is a symbolic link from being 
 	followed (the user will get an 	error).  This option is very useful to stop users from adding a symbolic 
@@ -2087,10 +2021,10 @@ follow symlinks (S)
 	This option is enabled (i.e. <code class="literal">smbd</code> will follow symbolic links) by default.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>follow symlinks</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542146"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2541939"></a>
 
 force create mode (S)
-</h3></div></div></div><a class="indexterm" name="id2542147"></a><a name="FORCECREATEMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a set of UNIX mode bit
+</h3></div></div></div><a class="indexterm" name="id2541940"></a><a name="FORCECREATEMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a set of UNIX mode bit
     permissions that will <span class="emphasis"><em>always</em></span> be set on a
     file created by Samba. This is done by bitwise 'OR'ing these bits onto
     the mode bits of a file that is being created. The default for this parameter is (in octal)
@@ -2102,10 +2036,10 @@ force create mode (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force create mode</code></em> = <code class="literal">0755</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542227"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542020"></a>
 
 force directory mode (S)
-</h3></div></div></div><a class="indexterm" name="id2542228"></a><a name="FORCEDIRECTORYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a set of UNIX mode bit 
+</h3></div></div></div><a class="indexterm" name="id2542021"></a><a name="FORCEDIRECTORYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a set of UNIX mode bit 
     permissions that will <span class="emphasis"><em>always</em></span> be set on a directory 
     created by Samba. This is done by bitwise 'OR'ing these bits onto the 
     mode bits of a directory that is being created. The default for this 
@@ -2118,10 +2052,10 @@ force directory mode (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force directory mode</code></em> = <code class="literal">0755</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542308"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542101"></a>
 
 force directory security mode (S)
-</h3></div></div></div><a class="indexterm" name="id2542309"></a><a name="FORCEDIRECTORYSECURITYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2542102"></a><a name="FORCEDIRECTORYSECURITYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating
 	the UNIX permission on a directory using the native NT security dialog box.
 	</p><p>
@@ -2142,13 +2076,13 @@ force directory security mode (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force directory security mode</code></em> = <code class="literal">700</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542412"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542205"></a>
 
 <a name="GROUP"></a>group
-</h3></div></div></div><a class="indexterm" name="id2542413"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#FORCEGROUP">force group</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542445"></a>
+</h3></div></div></div><a class="indexterm" name="id2542206"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#FORCEGROUP">force group</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542238"></a>
 
 force group (S)
-</h3></div></div></div><a class="indexterm" name="id2542446"></a><a name="FORCEGROUP"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies a UNIX group name that will be 
+</h3></div></div></div><a class="indexterm" name="id2542239"></a><a name="FORCEGROUP"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies a UNIX group name that will be 
     assigned as the default primary group for all users connecting 
     to this service. This is useful for sharing files by ensuring 
     that all access to files on service will use the named group for 
@@ -2172,10 +2106,10 @@ force group (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force group</code></em> = <code class="literal">agroup</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542560"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538149"></a>
 
 force printername (S)
-</h3></div></div></div><a class="indexterm" name="id2542561"></a><a name="FORCEPRINTERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>When printing from Windows NT (or later), 
+</h3></div></div></div><a class="indexterm" name="id2538150"></a><a name="FORCEPRINTERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>When printing from Windows NT (or later), 
     each printer in <code class="filename">smb.conf</code> has two 
     associated names which can be used by the client.  The first
     is the sharename (or shortname) defined in smb.conf.  This
@@ -2198,10 +2132,10 @@ force printername (S)
     not be able to delete printer connections from their local Printers 
     folder.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>force printername</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542652"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538240"></a>
 
 force security mode (S)
-</h3></div></div></div><a class="indexterm" name="id2542653"></a><a name="FORCESECURITYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538241"></a><a name="FORCESECURITYMODE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating 
     the UNIX permission on a file using the native NT security dialog box.
 	</p><p>
@@ -2221,10 +2155,10 @@ force security mode (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force security mode</code></em> = <code class="literal">700</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542753"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538342"></a>
 
 force unknown acl user (S)
-</h3></div></div></div><a class="indexterm" name="id2542754"></a><a name="FORCEUNKNOWNACLUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2538343"></a><a name="FORCEUNKNOWNACLUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>
     If this parameter is set, a Windows NT ACL that contains an unknown SID (security descriptor, or 
     representation of a user or group id) as the owner or group owner of the file will be silently
     mapped into the current UNIX uid or gid of the currently connected user.
@@ -2238,10 +2172,10 @@ force unknown acl user (S)
     Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>force unknown acl user</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542816"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542882"></a>
 
 force user (S)
-</h3></div></div></div><a class="indexterm" name="id2542817"></a><a name="FORCEUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies a UNIX user name that will be 
+</h3></div></div></div><a class="indexterm" name="id2542883"></a><a name="FORCEUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>This 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. You should also use it carefully 
     as using it incorrectly can cause security problems.</p><p>This user name only gets used once a connection is established. 
@@ -2255,10 +2189,10 @@ force user (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>force user</code></em> = <code class="literal">auser</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542892"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542958"></a>
 
 fstype (S)
-</h3></div></div></div><a class="indexterm" name="id2542893"></a><a name="FSTYPE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2542959"></a><a name="FSTYPE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter allows the administrator to configure the string that specifies the type of filesystem a share 
 	is using that is reported by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> 
 	when a client queries the filesystem type for a share. The default type is <code class="constant">NTFS</code> for compatibility 
@@ -2268,10 +2202,10 @@ fstype (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>fstype</code></em> = <code class="literal">Samba</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2542974"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543040"></a>
 
 get quota command (G)
-</h3></div></div></div><a class="indexterm" name="id2542975"></a><a name="GETQUOTACOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The <code class="literal">get quota command</code> should only be used 
+</h3></div></div></div><a class="indexterm" name="id2543041"></a><a name="GETQUOTACOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The <code class="literal">get quota command</code> should only be used 
 	whenever there is no operating system API available from the OS that 
 	samba can use.</p><p>This option is only available you have compiled Samba with the
 	<code class="literal">--with-sys-quotas</code> option or on Linux with
@@ -2284,18 +2218,18 @@ get quota command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>get quota command</code></em> = <code class="literal">/usr/local/sbin/query_quota</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543160"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543227"></a>
 
 getwd cache (G)
-</h3></div></div></div><a class="indexterm" name="id2543162"></a><a name="GETWDCACHE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a tuning option. When this is enabled a 
+</h3></div></div></div><a class="indexterm" name="id2543228"></a><a name="GETWDCACHE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a tuning option. When this is enabled a 
     caching algorithm will be used to reduce the time taken for getwd() 
     calls. This can have a significant impact on performance, especially 
     when the <a class="link" href="smb.conf.5.html#WIDESMBCONFOPTIONS" target="_top">wide smbconfoptions</a> parameter is set to <code class="constant">no</code>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>getwd cache</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543221"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543287"></a>
 
 guest account (G)
-</h3></div></div></div><a class="indexterm" name="id2543222"></a><a name="GUESTACCOUNT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a username which will be used for access 
+</h3></div></div></div><a class="indexterm" name="id2543288"></a><a name="GUESTACCOUNT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a username which will be used for access 
     to services which are specified as <a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok</a> (see below). Whatever privileges this 
     user has will be available to any client connecting to the guest service. 
     This user must exist in the password file, but does not require
@@ -2313,40 +2247,40 @@ guest account (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>guest account</code></em> = <code class="literal">ftp</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543329"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543395"></a>
 
 <a name="PUBLIC"></a>public
-</h3></div></div></div><a class="indexterm" name="id2543330"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#GUESTOK">guest ok</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543360"></a>
+</h3></div></div></div><a class="indexterm" name="id2543396"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#GUESTOK">guest ok</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543426"></a>
 
 guest ok (S)
-</h3></div></div></div><a class="indexterm" name="id2543361"></a><a name="GUESTOK"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for 
+</h3></div></div></div><a class="indexterm" name="id2543427"></a><a name="GUESTOK"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for 
     a service, then no password is required to connect to the service. 
     Privileges will be those of the <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a>.</p><p>This paramater nullifies the benifits of setting
     <a class="link" href="smb.conf.5.html#RESTRICTANONYMOUS" target="_top">restrict anonymous = 2</a>
 	</p><p>See the section below on <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> for more information about this option.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>guest ok</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543448"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543514"></a>
 
 <a name="ONLYGUEST"></a>only guest
-</h3></div></div></div><a class="indexterm" name="id2543449"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#GUESTONLY">guest only</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543481"></a>
+</h3></div></div></div><a class="indexterm" name="id2543515"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#GUESTONLY">guest only</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543547"></a>
 
 guest only (S)
-</h3></div></div></div><a class="indexterm" name="id2543482"></a><a name="GUESTONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for 
+</h3></div></div></div><a class="indexterm" name="id2543548"></a><a name="GUESTONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code> for 
     a service, then only guest connections to the service are permitted. 
     This parameter will have no effect if <a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok</a> is not set for the service.</p><p>See the section below on <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> for more information about this option.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>guest only</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543553"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543620"></a>
 
 hide dot files (S)
-</h3></div></div></div><a class="indexterm" name="id2543554"></a><a name="HIDEDOTFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean parameter that controls whether 
+</h3></div></div></div><a class="indexterm" name="id2543621"></a><a name="HIDEDOTFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean parameter that controls whether 
 	files starting with a dot appear as hidden files.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>hide dot files</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543596"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543662"></a>
 
 hide files (S)
-</h3></div></div></div><a class="indexterm" name="id2543597"></a><a name="HIDEFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of files or directories that are not 
+</h3></div></div></div><a class="indexterm" name="id2543663"></a><a name="HIDEFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of files or directories that are not 
 	visible but are accessible.  The DOS 'hidden' attribute is applied 
 	to any files or directories that match.</p><p>Each entry in the list must be separated by a '/', 
 	which allows spaces to be included in the entry.  '*'
@@ -2368,32 +2302,32 @@ hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>hide files</code></em> = <code class="literal">
 # no file are hidden</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543685"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543751"></a>
 
 hide special files (S)
-</h3></div></div></div><a class="indexterm" name="id2543686"></a><a name="HIDESPECIALFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2543752"></a><a name="HIDESPECIALFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter prevents clients from seeing special files such as sockets, devices and
 	fifo's in directory listings.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>hide special files</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543728"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543794"></a>
 
 hide unreadable (S)
-</h3></div></div></div><a class="indexterm" name="id2543729"></a><a name="HIDEUNREADABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter prevents clients from seeing the
+</h3></div></div></div><a class="indexterm" name="id2543795"></a><a name="HIDEUNREADABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter prevents clients from seeing the
 		existance of files that cannot be read. Defaults to off.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>hide unreadable</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543770"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543837"></a>
 
 hide unwriteable files (S)
-</h3></div></div></div><a class="indexterm" name="id2543771"></a><a name="HIDEUNWRITEABLEFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2543838"></a><a name="HIDEUNWRITEABLEFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter prevents clients from seeing the existance of files that cannot be written to. 
     Defaults to off. Note that unwriteable directories are shown as usual.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>hide unwriteable files</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543815"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543881"></a>
 
 homedir map (G)
-</h3></div></div></div><a class="indexterm" name="id2543816"></a><a name="HOMEDIRMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2543882"></a><a name="HOMEDIRMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If <a class="link" href="smb.conf.5.html#NISHOMEDIR" target="_top">nis homedir</a> is <code class="constant">yes</code>, and <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> is also acting 	as a Win95/98 <em class="parameter"><code>logon server</code></em> 
 	then this parameter specifies the NIS (or YP) map from which the server for the user's 	home directory should be extracted.  
 	At present, only the Sun auto.home map format is understood. The form of the map is:
@@ -2408,10 +2342,10 @@ homedir map (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>homedir map</code></em> = <code class="literal">amd.homedir</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543928"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543994"></a>
 
 host msdfs (G)
-</h3></div></div></div><a class="indexterm" name="id2543929"></a><a name="HOSTMSDFS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2543995"></a><a name="HOSTMSDFS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If set to <code class="constant">yes</code>, Samba will act as a Dfs server, and allow Dfs-aware clients to browse
 	Dfs trees hosted on the server.
 	</p><p>
@@ -2419,10 +2353,10 @@ host msdfs (G)
 	setting  up a Dfs tree on Samba, refer to the MSFDS chapter in the book Samba3-HOWTO.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>host msdfs</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543992"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544058"></a>
 
 hostname lookups (G)
-</h3></div></div></div><a class="indexterm" name="id2543993"></a><a name="HOSTNAMELOOKUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies whether samba should use (expensive)
+</h3></div></div></div><a class="indexterm" name="id2544059"></a><a name="HOSTNAMELOOKUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies whether samba should use (expensive)
     hostname lookups or use the ip addresses instead. An example place
     where hostname lookups are currently used is when checking 
     the <code class="literal">hosts deny</code> and <code class="literal">hosts allow</code>.
@@ -2430,13 +2364,13 @@ hostname lookups (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>hostname lookups</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544066"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544132"></a>
 
 <a name="ALLOWHOSTS"></a>allow hosts
-</h3></div></div></div><a class="indexterm" name="id2544067"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#HOSTSALLOW">hosts allow</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544098"></a>
+</h3></div></div></div><a class="indexterm" name="id2544133"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#HOSTSALLOW">hosts allow</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544164"></a>
 
 hosts allow (S)
-</h3></div></div></div><a class="indexterm" name="id2544099"></a><a name="HOSTSALLOW"></a><div class="variablelist"><dl><dt></dt><dd><p>A synonym for this parameter is <a class="link" href="smb.conf.5.html#ALLOWHOSTS" target="_top">allow hosts</a>.</p><p>This parameter is a comma, space, or tab delimited 
+</h3></div></div></div><a class="indexterm" name="id2544165"></a><a name="HOSTSALLOW"></a><div class="variablelist"><dl><dt></dt><dd><p>A synonym for this parameter is <a class="link" href="smb.conf.5.html#ALLOWHOSTS" target="_top">allow hosts</a>.</p><p>This parameter is a comma, space, or tab delimited 
     set of hosts which are permitted to access a service.</p><p>If specified in the [global] section then it will
     apply to all services, regardless of whether the individual 
     service has a different setting.</p><p>You can specify the hosts by name or IP number. For 
@@ -2456,13 +2390,13 @@ hosts allow (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>hosts allow</code></em> = <code class="literal">150.203.5. myhost.mynet.edu.au</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544300"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544366"></a>
 
 <a name="DENYHOSTS"></a>deny hosts
-</h3></div></div></div><a class="indexterm" name="id2544301"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#HOSTSDENY">hosts deny</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544331"></a>
+</h3></div></div></div><a class="indexterm" name="id2544367"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#HOSTSDENY">hosts deny</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544398"></a>
 
 hosts deny (S)
-</h3></div></div></div><a class="indexterm" name="id2544332"></a><a name="HOSTSDENY"></a><div class="variablelist"><dl><dt></dt><dd><p>The opposite of <em class="parameter"><code>hosts allow</code></em> 
+</h3></div></div></div><a class="indexterm" name="id2544399"></a><a name="HOSTSDENY"></a><div class="variablelist"><dl><dt></dt><dd><p>The opposite of <em class="parameter"><code>hosts allow</code></em> 
     - hosts listed here are <span class="emphasis"><em>NOT</em></span> permitted access to 
     services unless the specific services have their own lists to override 
     this one. Where the lists conflict, the <em class="parameter"><code>allow</code></em> 
@@ -2476,10 +2410,10 @@ hosts deny (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>hosts deny</code></em> = <code class="literal">150.203.4. badhost.mynet.edu.au</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544433"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544500"></a>
 
 idmap alloc backend (G)
-</h3></div></div></div><a class="indexterm" name="id2544434"></a><a name="IDMAPALLOCBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2544501"></a><a name="IDMAPALLOCBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The idmap alloc backend provides a plugin interface for Winbind to use
 	when allocating Unix uids/gids for Windows SIDs. This option refers
 	to the name of the idmap module which will provide the id allocation
@@ -2496,18 +2430,18 @@ idmap alloc backend (G)
 	Also refer to the <a class="link" href="smb.conf.5.html#IDMAPALLOCCONFIG" target="_top">idmap alloc config</a> option.
 	</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>idmap alloc backend</code></em> = <code class="literal">tdb</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544539"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544605"></a>
 
 idmap alloc config (G)
-</h3></div></div></div><a class="indexterm" name="id2544540"></a><a name="IDMAPALLOCCONFIG"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2544606"></a><a name="IDMAPALLOCCONFIG"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The idmap alloc config prefix provides a means of managing settings
 	for the backend defined by the <a class="link" href="smb.conf.5.html#IDMAPALLOCBACKEND" target="_top">idmap alloc backend</a> 
 	parameter.  Refer to the man page for each idmap plugin regarding
 	specific configuration details.
-	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544583"></a>
+	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544649"></a>
 
 idmap backend (G)
-</h3></div></div></div><a class="indexterm" name="id2544584"></a><a name="IDMAPBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2544650"></a><a name="IDMAPBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The idmap backend provides a plugin interface for Winbind to use
 	varying backends to store SID/uid/gid mapping tables.
 	</p><p>
@@ -2528,17 +2462,17 @@ idmap backend (G)
 	and ad (<a class="citerefentry" href="idmap_ad.8.html"><span class="citerefentry"><span class="refentrytitle">idmap_ad</span>(8)</span></a>).
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>idmap backend</code></em> = <code class="literal">tdb</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544755"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544821"></a>
 
 idmap cache time (G)
-</h3></div></div></div><a class="indexterm" name="id2544756"></a><a name="IDMAPCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of seconds that Winbind's
+</h3></div></div></div><a class="indexterm" name="id2544822"></a><a name="IDMAPCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of seconds that Winbind's
 	idmap interface will cache positive SID/uid/gid query results.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>idmap cache time</code></em> = <code class="literal">604800 (one week)</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544799"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544865"></a>
 
 idmap config (G)
-</h3></div></div></div><a class="indexterm" name="id2544800"></a><a name="IDMAPCONFIG"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2544866"></a><a name="IDMAPCONFIG"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The idmap config prefix provides a means of managing each trusted
         domain separately. The idmap config prefix should be followed by the
         name of the domain, a colon, and a setting specific to the chosen
@@ -2570,13 +2504,13 @@ idmap config (G)
 
 	idmap config CORP : backend  = ad
 	idmap config CORP : range = 1000-999999
-	</pre><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544932"></a>
+	</pre><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544998"></a>
 
 <a name="WINBINDGID"></a>winbind gid
-</h3></div></div></div><a class="indexterm" name="id2544933"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#IDMAPGID">idmap gid</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544964"></a>
+</h3></div></div></div><a class="indexterm" name="id2544999"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#IDMAPGID">idmap gid</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545030"></a>
 
 idmap gid (G)
-</h3></div></div></div><a class="indexterm" name="id2544965"></a><a name="IDMAPGID"></a><div class="variablelist"><dl><dt></dt><dd><p>The idmap gid parameter specifies the range of group ids 
+</h3></div></div></div><a class="indexterm" name="id2545031"></a><a name="IDMAPGID"></a><div class="variablelist"><dl><dt></dt><dd><p>The idmap gid parameter specifies the range of group ids 
 	that are allocated for the purpose of mapping UNX groups to NT group 
 	SIDs. This range of group ids should have no 
 	existing local or NIS groups within it as strange conflicts can 
@@ -2586,20 +2520,20 @@ idmap gid (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>idmap gid</code></em> = <code class="literal">10000-20000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545050"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545116"></a>
 
 idmap negative cache time (G)
-</h3></div></div></div><a class="indexterm" name="id2545051"></a><a name="IDMAPNEGATIVECACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of seconds that Winbind's
+</h3></div></div></div><a class="indexterm" name="id2545117"></a><a name="IDMAPNEGATIVECACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of seconds that Winbind's
 	idmap interface will cache negative SID/uid/gid query results.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>idmap negative cache time</code></em> = <code class="literal">120</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545094"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545161"></a>
 
 <a name="WINBINDUID"></a>winbind uid
-</h3></div></div></div><a class="indexterm" name="id2545095"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#IDMAPUID">idmap uid</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545125"></a>
+</h3></div></div></div><a class="indexterm" name="id2545162"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#IDMAPUID">idmap uid</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545192"></a>
 
 idmap uid (G)
-</h3></div></div></div><a class="indexterm" name="id2545126"></a><a name="IDMAPUID"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545193"></a><a name="IDMAPUID"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The idmap uid parameter specifies the range of user ids that are 
 	allocated for use in mapping UNIX users to NT user SIDs. This 
 	range of ids should have no existing local
@@ -2609,10 +2543,10 @@ idmap uid (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>idmap uid</code></em> = <code class="literal">10000-20000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545212"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545278"></a>
 
 include (G)
-</h3></div></div></div><a class="indexterm" name="id2545213"></a><a name="INCLUDE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545279"></a><a name="INCLUDE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This allows you to include one config file inside another.  The file is included literally, as though typed 
 	in place.
 	</p><p>
@@ -2630,26 +2564,21 @@ include (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>include</code></em> = <code class="literal">/usr/local/samba/lib/admin_smb.conf</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545312"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545379"></a>
 
 inherit acls (S)
-</h3></div></div></div><a class="indexterm" name="id2545314"></a><a name="INHERITACLS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter can be used to ensure that if default acls
+</h3></div></div></div><a class="indexterm" name="id2545380"></a><a name="INHERITACLS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter can be used to ensure that if default acls
     exist on parent directories, they are always honored when creating a
     new file or subdirectory in these parent directories. The default 
     behavior is to use the unix mode specified when creating the directory. 
     Enabling this option sets the unix mode to 0777, thus guaranteeing that 
     default directory acls are propagated.
-
-    Note that using the VFS modules acl_xattr or acl_tdb which store native
-    Windows as meta-data will automatically turn this option on for any
-    share for which they are loaded, as they require this option to emulate
-    Windows ACLs correctly.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>inherit acls</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545363"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545426"></a>
 
 inherit owner (S)
-</h3></div></div></div><a class="indexterm" name="id2545364"></a><a name="INHERITOWNER"></a><div class="variablelist"><dl><dt></dt><dd><p>The ownership of new files and directories 
+</h3></div></div></div><a class="indexterm" name="id2545427"></a><a name="INHERITOWNER"></a><div class="variablelist"><dl><dt></dt><dd><p>The ownership of new files and directories 
 	is normally governed by effective uid of the connected user.
 	This option allows the Samba administrator to specify that
 	the ownership for new files and directories should be controlled
@@ -2658,10 +2587,10 @@ inherit owner (S)
 	delete them and to ensure that newly create files in a user's
 	roaming profile directory are actually owner by the user.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>inherit owner</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545416"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545479"></a>
 
 inherit permissions (S)
-</h3></div></div></div><a class="indexterm" name="id2545417"></a><a name="INHERITPERMISSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545480"></a><a name="INHERITPERMISSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The permissions on new files and directories are normally governed by <a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a>,
 	<a class="link" href="smb.conf.5.html#DIRECTORYMASK" target="_top">directory mask</a>, <a class="link" href="smb.conf.5.html#FORCECREATEMODE" target="_top">force create mode</a> and <a class="link" href="smb.conf.5.html#FORCEDIRECTORYMODE" target="_top">force directory mode</a> but the boolean inherit permissions parameter overrides this.
 	</p><p>New directories inherit the mode of the parent directory,
@@ -2673,10 +2602,10 @@ inherit permissions (S)
     many users, perhaps several thousand, to allow a single [homes] 
     share to be used flexibly by each user.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>inherit permissions</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545566"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545628"></a>
 
 init logon delayed hosts (G)
-</h3></div></div></div><a class="indexterm" name="id2545567"></a><a name="INITLOGONDELAYEDHOSTS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545629"></a><a name="INITLOGONDELAYEDHOSTS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter takes a list of host names, addresses or networks for
 	which the initial samlogon reply should be delayed (so other DCs get
 	preferred by XP workstations if there are any).
@@ -2687,19 +2616,19 @@ init logon delayed hosts (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>init logon delayed hosts</code></em> = <code class="literal">150.203.5. myhost.mynet.de</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545644"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545706"></a>
 
 init logon delay (G)
-</h3></div></div></div><a class="indexterm" name="id2545645"></a><a name="INITLOGONDELAY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545707"></a><a name="INITLOGONDELAY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies a delay in milliseconds for the hosts configured
 	for delayed initial samlogon with
 	<a class="link" href="smb.conf.5.html#INITLOGONDELAYEDHOSTS" target="_top">init logon delayed hosts</a>.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>init logon delay</code></em> = <code class="literal">100</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545698"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545760"></a>
 
 interfaces (G)
-</h3></div></div></div><a class="indexterm" name="id2545699"></a><a name="INTERFACES"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to override the default 
+</h3></div></div></div><a class="indexterm" name="id2545761"></a><a name="INTERFACES"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to override the default 
 	network interfaces list that Samba will use for browsing, name 
 	registration and other NetBIOS over TCP/IP (NBT) traffic. By default Samba will query
 	the kernel for the list of all active interfaces and use any 
@@ -2723,10 +2652,10 @@ interfaces (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>interfaces</code></em> = <code class="literal">eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545815"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545877"></a>
 
 invalid users (S)
-</h3></div></div></div><a class="indexterm" name="id2545816"></a><a name="INVALIDUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of users that should not be allowed 
+</h3></div></div></div><a class="indexterm" name="id2545878"></a><a name="INVALIDUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of users that should not be allowed 
     to login to this service. This is really a <span class="emphasis"><em>paranoid</em></span> 
     check to absolutely ensure an improper setting does not breach 
     your security.</p><p>A name starting with a '@' is interpreted as an NIS 
@@ -2746,10 +2675,10 @@ invalid users (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>invalid users</code></em> = <code class="literal">root fred admin @wheel</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545930"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545992"></a>
 
 iprint server (G)
-</h3></div></div></div><a class="indexterm" name="id2545931"></a><a name="IPRINTSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2545993"></a><a name="IPRINTSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter is only applicable if <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing</a> is set to <code class="constant">iprint</code>.
     </p><p>
    If set, this option overrides the ServerName option in the CUPS <code class="filename">client.conf</code>. This is 
@@ -2758,10 +2687,10 @@ iprint server (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>iprint server</code></em> = <code class="literal">MYCUPSSERVER</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546016"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546078"></a>
 
 keepalive (G)
-</h3></div></div></div><a class="indexterm" name="id2546017"></a><a name="KEEPALIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (an integer) represents 
+</h3></div></div></div><a class="indexterm" name="id2546079"></a><a name="KEEPALIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (an integer) represents 
     the number of seconds between <em class="parameter"><code>keepalive</code></em> 
     packets. If this parameter is zero, no keepalive packets will be 
     sent. Keepalive packets, if sent, allow the server to tell whether 
@@ -2771,10 +2700,10 @@ Basically you should only use this option if you strike difficulties.</p><p>Defa
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>keepalive</code></em> = <code class="literal">600</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546104"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546165"></a>
 
 kerberos method (G)
-</h3></div></div></div><a class="indexterm" name="id2546105"></a><a name="KERBEROSMETHOD"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2546166"></a><a name="KERBEROSMETHOD"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Controls how kerberos tickets are verified.
 	</p><p>Valid options are:</p><div class="itemizedlist"><ul type="disc"><li><p>secrets only - use only the secrets.tdb for
 	  ticket verification (default)</p></li><li><p>system keytab - use only the system keytab
@@ -2791,20 +2720,20 @@ kerberos method (G)
 	  specify the location of the keytab file.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>kerberos method</code></em> = <code class="literal">secrets only</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546200"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546262"></a>
 
 kernel change notify (S)
-</h3></div></div></div><a class="indexterm" name="id2546201"></a><a name="KERNELCHANGENOTIFY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should ask the 
+</h3></div></div></div><a class="indexterm" name="id2546263"></a><a name="KERNELCHANGENOTIFY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether Samba should ask the 
 	kernel for change notifications in directories so that
 	SMB clients can refresh whenever the data on the server changes.
 	</p><p>This parameter is only used when your kernel supports 
 	change notification to user programs using the inotify interface.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>kernel change notify</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546250"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546312"></a>
 
 kernel oplocks (G)
-</h3></div></div></div><a class="indexterm" name="id2546251"></a><a name="KERNELOPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>For UNIXes that support kernel based <a class="link" href="smb.conf.5.html#OPLOCKS" target="_top">oplocks</a>
+</h3></div></div></div><a class="indexterm" name="id2546313"></a><a name="KERNELOPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>For UNIXes that support kernel based <a class="link" href="smb.conf.5.html#OPLOCKS" target="_top">oplocks</a>
 	(currently only IRIX and the Linux 2.4 kernel), this parameter 
 	allows the use of them to be turned on or off.</p><p>Kernel oplocks support allows Samba <em class="parameter"><code>oplocks
 	</code></em> to be broken whenever a local UNIX process or NFS operation 
@@ -2814,10 +2743,10 @@ kernel oplocks (G)
 	to a no-op on systems that no not have the necessary kernel support.
 	You should never need to touch this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>kernel oplocks</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546338"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546400"></a>
 
 lanman auth (G)
-</h3></div></div></div><a class="indexterm" name="id2546339"></a><a name="LANMANAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to
+</h3></div></div></div><a class="indexterm" name="id2546401"></a><a name="LANMANAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to
     authenticate users or permit password changes
     using the LANMAN password hash. If disabled, only clients which support NT 
     password hashes (e.g. Windows NT/2000 clients, smbclient, but not 
@@ -2825,12 +2754,7 @@ lanman auth (G)
     connect to the Samba host.</p><p>The LANMAN encrypted response is easily broken, due to its
     case-insensitive nature, and the choice of algorithm.  Servers
     without Windows 95/98/ME or MS DOS clients are advised to disable
-    this option.  </p><p>When this parameter is set to <code class="literal">no</code> this
-    will also result in sambaLMPassword in Samba's passdb being
-    blanked after the next password change. As a result of that
-    lanman clients won't be able to authenticate, even if lanman
-    auth is reenabled later on.
-    </p><p>Unlike the <code class="literal">encrypt
+    this option.  </p><p>Unlike the <code class="literal">encrypt
     passwords</code> option, this parameter cannot alter client
     behaviour, and the LANMAN response will still be sent over the
     network.  See the <code class="literal">client lanman
@@ -2839,10 +2763,10 @@ lanman auth (G)
     permited.  Not all clients support NTLMv2, and most will require
     special configuration to use it.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>lanman auth</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546444"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546493"></a>
 
 large readwrite (G)
-</h3></div></div></div><a class="indexterm" name="id2546445"></a><a name="LARGEREADWRITE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not
+</h3></div></div></div><a class="indexterm" name="id2546494"></a><a name="LARGEREADWRITE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not
     <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> supports the new 64k
     streaming read and write variant SMB requests introduced with
     Windows 2000. Note that due to Windows 2000 client redirector bugs
@@ -2851,10 +2775,10 @@ large readwrite (G)
     performance by 10% with Windows 2000 clients. Defaults to on. Not as
 	tested as some other Samba code paths.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>large readwrite</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546507"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546549"></a>
 
 ldap admin dn (G)
-</h3></div></div></div><a class="indexterm" name="id2546508"></a><a name="LDAPADMINDN"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2546550"></a><a name="LDAPADMINDN"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> defines the Distinguished  Name (DN) name used by Samba to contact
 	the ldap server when retreiving  user account information. The <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> is used
 	in conjunction with the admin dn password stored in the <code class="filename">private/secrets.tdb</code>
@@ -2862,10 +2786,10 @@ ldap admin dn (G)
 	man page for more information on how  to accomplish this.
 	</p><p>
 	The <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> requires a fully specified DN. The <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap  suffix</a> is not appended to the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a>.
-	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546617"></a>
+	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546658"></a>
 
 ldap connection timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2546618"></a><a name="LDAPCONNECTIONTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2546659"></a><a name="LDAPCONNECTIONTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter tells the LDAP library calls which timeout in seconds
 	they should honor during initial connection establishments to LDAP servers.
 	It is very useful in failover scenarios in particular. If one or more LDAP
@@ -2877,10 +2801,10 @@ ldap connection timeout (G)
 	and not establishing an initial connection.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap connection timeout</code></em> = <code class="literal">2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546682"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546723"></a>
 
 ldap debug level (G)
-</h3></div></div></div><a class="indexterm" name="id2546683"></a><a name="LDAPDEBUGLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2546724"></a><a name="LDAPDEBUGLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
 		This parameter controls the debug level of the LDAP library
 		calls. In the case of OpenLDAP, it is the same
 		bit-field as understood by the server and documented in the
@@ -2897,10 +2821,10 @@ ldap debug level (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap debug level</code></em> = <code class="literal">1</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546770"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546811"></a>
 
 ldap debug threshold (G)
-</h3></div></div></div><a class="indexterm" name="id2546771"></a><a name="LDAPDEBUGTHRESHOLD"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2546812"></a><a name="LDAPDEBUGTHRESHOLD"></a><div class="variablelist"><dl><dt></dt><dd><p>
 		This parameter controls the Samba debug level at which
 		the ldap library debug output is
 		printed in the Samba logs. See the description of
@@ -2909,56 +2833,28 @@ ldap debug threshold (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap debug threshold</code></em> = <code class="literal">5</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546837"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546879"></a>
 
 ldap delete dn (G)
-</h3></div></div></div><a class="indexterm" name="id2546838"></a><a name="LDAPDELETEDN"></a><div class="variablelist"><dl><dt></dt><dd><p> This parameter specifies whether a delete
+</h3></div></div></div><a class="indexterm" name="id2546880"></a><a name="LDAPDELETEDN"></a><div class="variablelist"><dl><dt></dt><dd><p> This parameter specifies whether a delete
 	operation in the ldapsam deletes the complete entry or only the attributes
 	specific to Samba.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap delete dn</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546881"></a>
-
-ldap deref (G)
-</h3></div></div></div><a class="indexterm" name="id2546882"></a><a name="LDAPDEREF"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls whether Samba should tell the LDAP library
-	to use a certain alias dereferencing method. The default is
-	<span class="emphasis"><em>auto</em></span>, which means that the default setting of the
-	ldap client library will be kept. Other possible values are
-	<span class="emphasis"><em>never</em></span>, <span class="emphasis"><em>finding</em></span>,
-	<span class="emphasis"><em>searching</em></span> and <span class="emphasis"><em>always</em></span>. Grab
-	your LDAP manual for more information.
-	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap deref</code></em> = <code class="literal">auto</code>
-</em></span>
-</p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap deref</code></em> = <code class="literal">searching</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546962"></a>
-
-ldap follow referral (G)
-</h3></div></div></div><a class="indexterm" name="id2546963"></a><a name="LDAPFOLLOWREFERRAL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls whether to follow LDAP referrals or not when
-	searching for entries in the LDAP database. Possible values are
-	<span class="emphasis"><em>on</em></span> to enable following referrals,
-	<span class="emphasis"><em>off</em></span> to disable this, and
-	<span class="emphasis"><em>auto</em></span>, to use the libldap default settings.
-	libldap's choice of following referrals or not is set in
-	/etc/openldap/ldap.conf with the REFERRALS parameter as documented in
-	ldap.conf(5).</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap follow referral</code></em> = <code class="literal">auto</code>
-</em></span>
-</p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap follow referral</code></em> = <code class="literal">off</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547037"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546923"></a>
 
 ldap group suffix (G)
-</h3></div></div></div><a class="indexterm" name="id2547038"></a><a name="LDAPGROUPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the suffix that is 
+</h3></div></div></div><a class="indexterm" name="id2546924"></a><a name="LDAPGROUPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the suffix that is 
 	used for groups when these are added to the LDAP directory.
 	If this parameter is unset, the value of <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> will be used instead.  The suffix string is pre-pended to the
         <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> string so use a partial DN.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap group suffix</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap group suffix</code></em> = <code class="literal">ou=Groups</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547121"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547007"></a>
 
 ldap idmap suffix (G)
-</h3></div></div></div><a class="indexterm" name="id2547122"></a><a name="LDAPIDMAPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547008"></a><a name="LDAPIDMAPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameters specifies the suffix that is used when storing idmap mappings. If this parameter 
 	is unset, the value of <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> will be used instead.  The suffix 
 	string is pre-pended to the <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> string so use a partial DN.
@@ -2966,10 +2862,10 @@ ldap idmap suffix (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap idmap suffix</code></em> = <code class="literal">ou=Idmap</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547203"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547089"></a>
 
 ldap machine suffix (G)
-</h3></div></div></div><a class="indexterm" name="id2547204"></a><a name="LDAPMACHINESUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547090"></a><a name="LDAPMACHINESUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	It specifies where machines should be added to the ldap tree.  If this parameter is unset, the value of
 	<a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> will be used instead.  The suffix string is pre-pended to the
 	<a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> string so use a partial DN.
@@ -2977,10 +2873,10 @@ ldap machine suffix (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap machine suffix</code></em> = <code class="literal">ou=Computers</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547286"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547172"></a>
 
 ldap page size (G)
-</h3></div></div></div><a class="indexterm" name="id2547287"></a><a name="LDAPPAGESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547173"></a><a name="LDAPPAGESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the number of entries per page.
 	</p><p>If the LDAP server supports paged results, clients can
 	request	subsets of search results (pages) instead of the entire list.
@@ -2989,10 +2885,10 @@ ldap page size (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap page size</code></em> = <code class="literal">512</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547352"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547238"></a>
 
 ldap passwd sync (G)
-</h3></div></div></div><a class="indexterm" name="id2547353"></a><a name="LDAPPASSWDSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547239"></a><a name="LDAPPASSWDSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This option is used to define whether or not Samba should sync the LDAP password with the NT
 	and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password
 	change via SAMBA.  
@@ -3003,10 +2899,10 @@ ldap passwd sync (G)
 			LM passwords and update the pwdLastSet time.</p></li><li><p><em class="parameter"><code>Only</code></em> = Only update 
 			the LDAP password and let the LDAP server do the rest.</p></li></ul></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap passwd sync</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547453"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547339"></a>
 
 ldap replication sleep (G)
-</h3></div></div></div><a class="indexterm" name="id2547454"></a><a name="LDAPREPLICATIONSLEEP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547340"></a><a name="LDAPREPLICATIONSLEEP"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	When Samba is asked to write to a read-only LDAP replica, we are redirected to talk to the read-write master server.
 	This server then replicates our changes back to the 'local' server, however the replication might take some seconds, 
 	especially over slow links.  Certain client activities, particularly domain joins, can become confused by the 'success' 
@@ -3019,10 +2915,10 @@ ldap replication sleep (G)
 	The value is specified in milliseconds, the maximum value is 5000 (5 seconds).
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap replication sleep</code></em> = <code class="literal">1000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547517"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547403"></a>
 
 ldapsam:editposix (G)
-</h3></div></div></div><a class="indexterm" name="id2547518"></a><a name="LDAPSAM:EDITPOSIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547404"></a><a name="LDAPSAM:EDITPOSIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Editposix is an option that leverages ldapsam:trusted to make it simpler to manage a domain controller
 	eliminating the need to set up custom scripts to add and manage the posix users and groups. This option
 	will instead directly manipulate the ldap tree to create, remove and modify user and group entries.
@@ -3100,10 +2996,10 @@ ldapsam:editposix (G)
 	</pre><p>
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldapsam:editposix</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547654"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547529"></a>
 
 ldapsam:trusted (G)
-</h3></div></div></div><a class="indexterm" name="id2547655"></a><a name="LDAPSAM:TRUSTED"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2547530"></a><a name="LDAPSAM:TRUSTED"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	By default, Samba as a Domain Controller with an LDAP backend needs to use the Unix-style NSS subsystem to
 	access user and group information. Due to the way Unix stores user information in /etc/passwd and /etc/group
 	this inevitably leads to inefficiencies. One important question a user needs to know is the list of groups he
@@ -3121,10 +3017,10 @@ ldapsam:trusted (G)
 	is easily achieved.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldapsam:trusted</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547743"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547618"></a>
 
 ldap ssl ads (G)
-</h3></div></div></div><a class="indexterm" name="id2547744"></a><a name="LDAPSSLADS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used to define whether or not Samba should
+</h3></div></div></div><a class="indexterm" name="id2547619"></a><a name="LDAPSSLADS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used to define whether or not Samba should
 	use SSL when connecting to the ldap server using
 	<span class="emphasis"><em>ads</em></span> methods.
 	Rpc methods are not affected by this parameter. Please note, that
@@ -3134,10 +3030,10 @@ ldap ssl ads (G)
 	for more information on <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a>.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap ssl ads</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547828"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547703"></a>
 
 ldap ssl (G)
-</h3></div></div></div><a class="indexterm" name="id2547829"></a><a name="LDAPSSL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used to define whether or not Samba should
+</h3></div></div></div><a class="indexterm" name="id2547704"></a><a name="LDAPSSL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used to define whether or not Samba should
 	use SSL when connecting to the ldap server
 	This is <span class="emphasis"><em>NOT</em></span> related to
 	Samba's previous SSL support which was enabled by specifying the
@@ -3162,10 +3058,10 @@ ldap ssl (G)
 	for more information on	<a class="link" href="smb.conf.5.html#LDAPSSLADS" target="_top">ldap ssl ads</a>.
         </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap ssl</code></em> = <code class="literal">start tls</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548021"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2547896"></a>
 
 ldap suffix (G)
-</h3></div></div></div><a class="indexterm" name="id2548022"></a><a name="LDAPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the base for all ldap suffixes and for storing the sambaDomain object.</p><p>
+</h3></div></div></div><a class="indexterm" name="id2547897"></a><a name="LDAPSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the base for all ldap suffixes and for storing the sambaDomain object.</p><p>
 	The ldap suffix will be appended to the values specified for the <a class="link" href="smb.conf.5.html#LDAPUSERSUFFIX" target="_top">ldap user suffix</a>,
 	 <a class="link" href="smb.conf.5.html#LDAPGROUPSUFFIX" target="_top">ldap group suffix</a>, <a class="link" href="smb.conf.5.html#LDAPMACHINESUFFIX" target="_top">ldap machine suffix</a>, and the
 	 <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX" target="_top">ldap idmap suffix</a>. Each of these should be given only a DN relative to the
@@ -3174,17 +3070,17 @@ ldap suffix (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap suffix</code></em> = <code class="literal">dc=samba,dc=org</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548144"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548019"></a>
 
 ldap timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2548145"></a><a name="LDAPTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2548020"></a><a name="LDAPTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter defines the number of seconds that Samba should use as timeout for LDAP operations.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ldap timeout</code></em> = <code class="literal">15</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548186"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548061"></a>
 
 ldap user suffix (G)
-</h3></div></div></div><a class="indexterm" name="id2548187"></a><a name="LDAPUSERSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2548062"></a><a name="LDAPUSERSUFFIX"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies where users are added to the tree. If this parameter is unset, 
 	the value of <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> will be used instead.  The suffix 
 	string is pre-pended to the  <a class="link" href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a> string so use a partial DN.
@@ -3192,10 +3088,10 @@ ldap user suffix (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>ldap user suffix</code></em> = <code class="literal">ou=people</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548268"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548143"></a>
 
 level2 oplocks (S)
-</h3></div></div></div><a class="indexterm" name="id2548269"></a><a name="LEVEL2OPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether Samba supports
+</h3></div></div></div><a class="indexterm" name="id2548144"></a><a name="LEVEL2OPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether Samba supports
 	level2 (read-only) oplocks on a share.</p><p>Level2, or read-only oplocks allow Windows NT clients 
 	that have an oplock on a file to downgrade from a read-write oplock 
 	to a read-only oplock once a second client opens the file (instead 
@@ -3215,10 +3111,10 @@ level2 oplocks (S)
 	parameter must be set to <code class="constant">yes</code> on this share in order for 
 	this parameter to have any effect.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>level2 oplocks</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548375"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548250"></a>
 
 lm announce (G)
-</h3></div></div></div><a class="indexterm" name="id2548376"></a><a name="LMANNOUNCE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will produce Lanman announce 
+</h3></div></div></div><a class="indexterm" name="id2548251"></a><a name="LMANNOUNCE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will produce Lanman announce 
 	broadcasts that are needed by OS/2 clients in order for them to see 
 	the Samba server in their browse list. This parameter can have three 
 	values, <code class="constant">yes</code>, <code class="constant">no</code>, or
@@ -3234,10 +3130,10 @@ lm announce (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lm announce</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548497"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548372"></a>
 
 lm interval (G)
-</h3></div></div></div><a class="indexterm" name="id2548498"></a><a name="LMINTERVAL"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba is set to produce Lanman announce 
+</h3></div></div></div><a class="indexterm" name="id2548373"></a><a name="LMINTERVAL"></a><div class="variablelist"><dl><dt></dt><dd><p>If Samba is set to produce Lanman announce 
 	broadcasts needed by OS/2 clients (see the 
 		<a class="link" href="smb.conf.5.html#LMANNOUNCE" target="_top">lm announce</a> parameter) then this 
 	parameter defines the frequency in seconds with which they will be 
@@ -3247,18 +3143,18 @@ lm interval (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lm interval</code></em> = <code class="literal">120</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548581"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548456"></a>
 
 load printers (G)
-</h3></div></div></div><a class="indexterm" name="id2548582"></a><a name="LOADPRINTERS"></a><div class="variablelist"><dl><dt></dt><dd><p>A boolean variable that controls whether all 
+</h3></div></div></div><a class="indexterm" name="id2548457"></a><a name="LOADPRINTERS"></a><div class="variablelist"><dl><dt></dt><dd><p>A boolean variable that controls whether all 
     printers in the printcap will be loaded for browsing by default. 
     See the <a class="link" href="smb.conf.5.html#PRINTERS" target="_top">printers</a> section for 
     more details.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>load printers</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548638"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548512"></a>
 
 local master (G)
-</h3></div></div></div><a class="indexterm" name="id2548639"></a><a name="LOCALMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to try and become a local master browser 
+</h3></div></div></div><a class="indexterm" name="id2548514"></a><a name="LOCALMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to try and become a local master browser 
 	on a subnet. If set to <code class="constant">no</code> then <code class="literal">
 	nmbd</code> will not attempt to become a local master browser 
 	on a subnet and will also lose in all browsing elections. By
@@ -3268,13 +3164,13 @@ local master (G)
 	will <span class="emphasis"><em>participate</em></span> in elections for local master browser.</p><p>Setting this value to <code class="constant">no</code> will cause <code class="literal">nmbd</code> <span class="emphasis"><em>never</em></span> to become a local 
 master browser.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>local master</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548737"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548612"></a>
 
 <a name="LOCKDIR"></a>lock dir
-</h3></div></div></div><a class="indexterm" name="id2548738"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#LOCKDIRECTORY">lock directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548769"></a>
+</h3></div></div></div><a class="indexterm" name="id2548613"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#LOCKDIRECTORY">lock directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548644"></a>
 
 lock directory (G)
-</h3></div></div></div><a class="indexterm" name="id2548770"></a><a name="LOCKDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the directory where lock 
+</h3></div></div></div><a class="indexterm" name="id2548645"></a><a name="LOCKDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the directory where lock 
 	files will be placed.  The lock files are used to implement the 
 	<a class="link" href="smb.conf.5.html#MAXCONNECTIONS" target="_top">max connections</a> option.
 	</p><p>
@@ -3284,10 +3180,10 @@ lock directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lock directory</code></em> = <code class="literal">/var/run/samba/locks</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548847"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548723"></a>
 
 locking (S)
-</h3></div></div></div><a class="indexterm" name="id2548848"></a><a name="LOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether or not locking will be 
+</h3></div></div></div><a class="indexterm" name="id2548724"></a><a name="LOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether or not locking will be 
 	performed by the server in response to lock requests from the 
 	client.</p><p>If <code class="literal">locking = no</code>, all lock and unlock 
 	requests will appear to succeed and all lock queries will report 
@@ -3297,18 +3193,18 @@ locking (S)
 	CDROM drives), although setting this parameter of <code class="constant">no</code> 
 	is not really recommended even in this case.</p><p>Be careful about disabling locking either globally or in a 
 	specific service, as lack of locking may result in data corruption. 
-	You should never need to set this parameter.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548923"></a>
+	You should never need to set this parameter.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548798"></a>
 
 lock spin count (G)
-</h3></div></div></div><a class="indexterm" name="id2548924"></a><a name="LOCKSPINCOUNT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter has been made inoperative in Samba 3.0.24.
+</h3></div></div></div><a class="indexterm" name="id2548800"></a><a name="LOCKSPINCOUNT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter has been made inoperative in Samba 3.0.24.
 	The functionality it contolled is now controlled by the parameter
 	<a class="link" href="smb.conf.5.html#LOCKSPINTIME" target="_top">lock spin time</a>.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>lock spin count</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548979"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548854"></a>
 
 lock spin time (G)
-</h3></div></div></div><a class="indexterm" name="id2548980"></a><a name="LOCKSPINTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>The time in microseconds that smbd should 
+</h3></div></div></div><a class="indexterm" name="id2548855"></a><a name="LOCKSPINTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>The time in microseconds that smbd should 
 	keep waiting to see if a failed lock request can
 	be granted. This parameter has changed in default
 	value from Samba 3.0.23 from 10 to 200. The associated
@@ -3316,22 +3212,22 @@ lock spin time (G)
 	no longer used in Samba 3.0.24. You should not need
 	to change the value of this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>lock spin time</code></em> = <code class="literal">200</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549037"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548912"></a>
 
 log file (G)
-</h3></div></div></div><a class="indexterm" name="id2549038"></a><a name="LOGFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2548913"></a><a name="LOGFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This option allows you to override the name of the Samba log file (also known as the debug file).
     </p><p>
     This option takes the standard substitutions, allowing you to have separate log files for each user or machine.
     </p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>log file</code></em> = <code class="literal">/usr/local/samba/var/log.%m</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549090"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548965"></a>
 
 <a name="DEBUGLEVEL"></a>debuglevel
-</h3></div></div></div><a class="indexterm" name="id2549091"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#LOGLEVEL">log level</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549121"></a>
+</h3></div></div></div><a class="indexterm" name="id2548966"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#LOGLEVEL">log level</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548996"></a>
 
 log level (G)
-</h3></div></div></div><a class="indexterm" name="id2549122"></a><a name="LOGLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2548997"></a><a name="LOGLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
     The value of the parameter (a astring) allows the debug level (logging level) to be specified in the 
     <code class="filename">smb.conf</code> file. 
     </p><p>This parameter has been extended since the 2.2.x 
@@ -3342,10 +3238,10 @@ log level (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>log level</code></em> = <code class="literal">3 passdb:5 auth:10 winbind:2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549354"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549229"></a>
 
 logon drive (G)
-</h3></div></div></div><a class="indexterm" name="id2549356"></a><a name="LOGONDRIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2549230"></a><a name="LOGONDRIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the local path to which the home directory will be
 	connected (see <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>) and is only used by NT
 	Workstations.
@@ -3355,10 +3251,10 @@ logon drive (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>logon drive</code></em> = <code class="literal">h:</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549430"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549304"></a>
 
 logon home (G)
-</h3></div></div></div><a class="indexterm" name="id2549431"></a><a name="LOGONHOME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2549305"></a><a name="LOGONHOME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC.  
 	It allows you to do
 	</p><p>
@@ -3389,10 +3285,10 @@ logon home (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>logon home</code></em> = <code class="literal">\\remote_smb_server\%U</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549594"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549469"></a>
 
 logon path (G)
-</h3></div></div></div><a class="indexterm" name="id2549595"></a><a name="LOGONPATH"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2549470"></a><a name="LOGONPATH"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the directory where roaming profiles (Desktop, NTuser.dat, etc) are 
 	stored.  Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming
 	profiles.  To find out how to handle roaming profiles for Win 9X system, see the
@@ -3436,10 +3332,10 @@ logon path = \\PROFILESERVER\PROFILE\%U
 </pre><p>
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>logon path</code></em> = <code class="literal">\\%N\%U\profile</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549763"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549638"></a>
 
 logon script (G)
-</h3></div></div></div><a class="indexterm" name="id2549764"></a><a name="LOGONSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2549639"></a><a name="LOGONSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the batch file (<code class="filename">.bat</code>) or NT command file
 	(<code class="filename">.cmd</code>) to be downloaded and run on a machine when a user successfully logs in.  The file
 	must contain the DOS style CR/LF line endings. Using a DOS-style editor to create the file is recommended.
@@ -3470,10 +3366,10 @@ logon script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>logon script</code></em> = <code class="literal">scripts\%U.bat</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549932"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549807"></a>
 
 lppause command (S)
-</h3></div></div></div><a class="indexterm" name="id2549934"></a><a name="LPPAUSECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2549808"></a><a name="LPPAUSECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to stop printing or spooling 
     a specific print job.</p><p>This command should be a program or script which takes 
     a printer name and job number to pause the print job. One way 
@@ -3497,10 +3393,10 @@ lppause command (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lppause command</code></em> = <code class="literal">/usr/bin/lpalt %p-%j -p0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550080"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2549955"></a>
 
 lpq cache time (G)
-</h3></div></div></div><a class="indexterm" name="id2550082"></a><a name="LPQCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls how long lpq info will be cached 
+</h3></div></div></div><a class="indexterm" name="id2549956"></a><a name="LPQCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls how long lpq info will be cached 
 	for to prevent the <code class="literal">lpq</code> command being called too 
 	often. A separate cache is kept for each variation of the <code class="literal">
 	lpq</code> command used by the system, so if you use different 
@@ -3513,10 +3409,10 @@ lpq cache time (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lpq cache time</code></em> = <code class="literal">10</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550199"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550074"></a>
 
 lpq command (S)
-</h3></div></div></div><a class="indexterm" name="id2550200"></a><a name="LPQCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2550075"></a><a name="LPQCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to obtain <code class="literal">lpq
     </code>-style printer status information.</p><p>This command should be a program or script which 
     takes a printer name as its only parameter and outputs printer 
@@ -3538,10 +3434,10 @@ lpq command (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lpq command</code></em> = <code class="literal">/usr/bin/lpq -P%p</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550326"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550200"></a>
 
 lpresume command (S)
-</h3></div></div></div><a class="indexterm" name="id2550327"></a><a name="LPRESUMECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2550201"></a><a name="LPRESUMECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to restart or continue 
     printing or spooling a specific print job.</p><p>This command should be a program or script which takes 
     a printer name and job number to resume the print job. See 
@@ -3554,10 +3450,10 @@ lpresume command (S)
     parameter is <code class="constant">SYSV</code>, in which case the default is:</p><p><code class="literal">lp -i %p-%j -H resume</code></p><p>or if the value of the <em class="parameter"><code>printing</code></em> parameter 
     is <code class="constant">SOFTQ</code>, then the default is:</p><p><code class="literal">qstat -s -j%j -r</code></p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>lpresume command</code></em> = <code class="literal">/usr/bin/lpalt %p-%j -p2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550479"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550353"></a>
 
 lprm command (S)
-</h3></div></div></div><a class="indexterm" name="id2550480"></a><a name="LPRMCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2550354"></a><a name="LPRMCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to delete a print job.</p><p>This command should be a program or script which takes 
     a printer name and job number, and deletes the print job.</p><p>If a <em class="parameter"><code>%p</code></em> is given then the printer name 
     is put in its place. A <em class="parameter"><code>%j</code></em> is replaced with 
@@ -3574,10 +3470,10 @@ lprm command = /usr/bin/cancel %p-%j
 </pre><p>
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>lprm command</code></em> = <code class="literal"> determined by printing parameter</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550566"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550441"></a>
 
 machine password timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2550567"></a><a name="MACHINEPASSWORDTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2550442"></a><a name="MACHINEPASSWORDTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If a Samba server is a member of a Windows NT Domain (see the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a> parameter) then periodically a running smbd process will try and change
 	the MACHINE ACCOUNT PASSWORD stored in the TDB called <code class="filename">private/secrets.tdb
 	</code>.  This parameter specifies how often this password will be changed, in seconds. The default is one
@@ -3587,10 +3483,10 @@ machine password timeout (G)
 	and the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a> parameter.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>machine password timeout</code></em> = <code class="literal">604800</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550654"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550528"></a>
 
 magic output (S)
-</h3></div></div></div><a class="indexterm" name="id2550655"></a><a name="MAGICOUTPUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2550530"></a><a name="MAGICOUTPUT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the name of a file which will contain output created by a magic script (see the 
 	<a class="link" href="smb.conf.5.html#MAGICSCRIPT" target="_top">magic script</a> parameter below).
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>If two clients use the same <em class="parameter"><code>magic script
@@ -3599,10 +3495,10 @@ magic output (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>magic output</code></em> = <code class="literal">myfile.txt</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550738"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550612"></a>
 
 magic script (S)
-</h3></div></div></div><a class="indexterm" name="id2550739"></a><a name="MAGICSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the name of a file which, 
+</h3></div></div></div><a class="indexterm" name="id2550614"></a><a name="MAGICSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the name of a file which, 
 	if opened, will be executed by the server when the file is closed. 
 	This allows a UNIX script to be sent to the Samba host and 
 	executed on behalf of the connected user.</p><p>Scripts executed in this way will be deleted upon 
@@ -3618,10 +3514,10 @@ magic script (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>magic script</code></em> = <code class="literal">user.csh</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550844"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550718"></a>
 
 mangled names (S)
-</h3></div></div></div><a class="indexterm" name="id2550845"></a><a name="MANGLEDNAMES"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether non-DOS names under UNIX 
+</h3></div></div></div><a class="indexterm" name="id2550719"></a><a name="MANGLEDNAMES"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether non-DOS names under UNIX 
 	should be mapped to DOS-compatible names ("mangled") and made visible, 
 	or whether non-DOS names should simply be ignored.</p><p>See the section on <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a> for 
 	details on how to control the mangling process.</p><p>If mangling is used then the mangling method is as follows:</p><div class="itemizedlist"><ul type="disc"><li><p>The first (up to) five alphanumeric characters 
@@ -3646,10 +3542,10 @@ mangled names (S)
 	from Windows/DOS and will retain the same basename. Mangled names 
 	do not change between sessions.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>mangled names</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550981"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550855"></a>
 
 mangle prefix (G)
-</h3></div></div></div><a class="indexterm" name="id2550982"></a><a name="MANGLEPREFIX"></a><div class="variablelist"><dl><dt></dt><dd><p> controls the number of prefix
+</h3></div></div></div><a class="indexterm" name="id2550856"></a><a name="MANGLEPREFIX"></a><div class="variablelist"><dl><dt></dt><dd><p> controls the number of prefix
 	characters from the original name used when generating
 	the mangled names. A larger value will give a weaker
 	hash and therefore more name collisions. The minimum
@@ -3659,20 +3555,20 @@ mangle prefix (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>mangle prefix</code></em> = <code class="literal">4</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551047"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550922"></a>
 
 mangling char (S)
-</h3></div></div></div><a class="indexterm" name="id2551048"></a><a name="MANGLINGCHAR"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what character is used as 
+</h3></div></div></div><a class="indexterm" name="id2550923"></a><a name="MANGLINGCHAR"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what character is used as 
 	the <span class="emphasis"><em>magic</em></span> character in <a class="link" href="smb.conf.5.html#NAMEMANGLING" target="_top">name mangling</a>. The 
 	default is a '~' but this may interfere with some software. Use this option to set 
 	it to whatever you prefer. This is effective only when mangling method is hash.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>mangling char</code></em> = <code class="literal">~</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>mangling char</code></em> = <code class="literal">^</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551125"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2550999"></a>
 
 mangling method (G)
-</h3></div></div></div><a class="indexterm" name="id2551126"></a><a name="MANGLINGMETHOD"></a><div class="variablelist"><dl><dt></dt><dd><p> controls the algorithm used for the generating
+</h3></div></div></div><a class="indexterm" name="id2551000"></a><a name="MANGLINGMETHOD"></a><div class="variablelist"><dl><dt></dt><dd><p> controls the algorithm used for the generating
 	the mangled names. Can take two different values, "hash" and
 	"hash2". "hash" is the algorithm that was used
 	used in Samba for many years and was the default in Samba 2.2.x "hash2" is
@@ -3683,10 +3579,10 @@ mangling method (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>mangling method</code></em> = <code class="literal">hash</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551192"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551066"></a>
 
 map acl inherit (S)
-</h3></div></div></div><a class="indexterm" name="id2551193"></a><a name="MAPACLINHERIT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to map the 'inherit' and 'protected'
+</h3></div></div></div><a class="indexterm" name="id2551067"></a><a name="MAPACLINHERIT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to map the 'inherit' and 'protected'
     access control entry flags stored in Windows ACLs into an extended attribute
     called user.SAMBA_PAI. This parameter only takes effect if Samba is being run
     on a platform that supports extended attributes (Linux and IRIX so far) and
@@ -3694,10 +3590,10 @@ map acl inherit (S)
     POSIX ACL mapping code.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>map acl inherit</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551249"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551123"></a>
 
 map archive (S)
-</h3></div></div></div><a class="indexterm" name="id2551250"></a><a name="MAPARCHIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2551124"></a><a name="MAPARCHIVE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls whether the DOS archive attribute 
 	should be mapped to the UNIX owner execute bit.  The DOS archive bit 
 	is set when a file has been modified since its last backup.  One 
@@ -3710,19 +3606,19 @@ map archive (S)
 	<a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> for details.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>map archive</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551324"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551199"></a>
 
 map hidden (S)
-</h3></div></div></div><a class="indexterm" name="id2551326"></a><a name="MAPHIDDEN"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2551200"></a><a name="MAPHIDDEN"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.
 	</p><p>
 	Note that this requires the <a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> to be set such that the world execute 
 	bit is not masked out (i.e. it must include 001). See the parameter <a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> 
 	for details.
-	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551382"></a>
+	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551256"></a>
 
-map readonly (S)
-</h3></div></div></div><a class="indexterm" name="id2551383"></a><a name="MAPREADONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+map read only (S)
+</h3></div></div></div><a class="indexterm" name="id2551257"></a><a name="MAPREADONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls how the DOS read only attribute should be mapped from a UNIX filesystem.
 	</p><p>
 	This parameter can take three different values, which tell <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> how to display the read only attribute on files, where either
@@ -3745,12 +3641,12 @@ map readonly (S)
 		</p></li><li><p>
 		<code class="constant">No</code> - The read only DOS attribute is unaffected by permissions, and can only be set by
 		the <a class="link" href="smb.conf.5.html#STOREDOSATTRIBUTES" target="_top">store dos attributes</a> method. This may be useful for exporting mounted CDs.
-		</p></li></ul></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>map readonly</code></em> = <code class="literal">yes</code>
+		</p></li></ul></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>map read only</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551538"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551413"></a>
 
 map system (S)
-</h3></div></div></div><a class="indexterm" name="id2551540"></a><a name="MAPSYSTEM"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2551414"></a><a name="MAPSYSTEM"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls whether DOS style system files should be mapped to the UNIX group execute bit.
 	</p><p>
 	Note that this requires the <a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a>	to be set such that the group 
@@ -3758,10 +3654,10 @@ map system (S)
 	<a class="link" href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> for details.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>map system</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551608"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551482"></a>
 
 map to guest (G)
-</h3></div></div></div><a class="indexterm" name="id2551609"></a><a name="MAPTOGUEST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only useful in <a class="link" href="smb.conf.5.html#SECURITY" target="_top">SECURITY = 
+</h3></div></div></div><a class="indexterm" name="id2551483"></a><a name="MAPTOGUEST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only useful in <a class="link" href="smb.conf.5.html#SECURITY" target="_top">SECURITY = 
     security</a> modes other than <em class="parameter"><code>security = share</code></em> 
     and <em class="parameter"><code>security = server</code></em>
     - i.e. <code class="constant">user</code>, and <code class="constant">domain</code>.</p><p>This parameter can take four different values, which tell
@@ -3803,10 +3699,10 @@ map to guest (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>map to guest</code></em> = <code class="literal">Bad User</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551848"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551722"></a>
 
 map untrusted to domain (G)
-</h3></div></div></div><a class="indexterm" name="id2551849"></a><a name="MAPUNTRUSTEDTODOMAIN"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2551723"></a><a name="MAPUNTRUSTEDTODOMAIN"></a><div class="variablelist"><dl><dt></dt><dd><p>
     If a client connects to smbd using an untrusted domain name, such as
     BOGUS\user, smbd replaces the BOGUS domain with it's SAM name before
     attempting to authenticate that user.  In the case where smbd is acting as
@@ -3824,10 +3720,10 @@ map untrusted to domain (G)
     effect.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>map untrusted to domain</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551915"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551789"></a>
 
 max connections (S)
-</h3></div></div></div><a class="indexterm" name="id2551916"></a><a name="MAXCONNECTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows the number of simultaneous connections to a service to be limited.
+</h3></div></div></div><a class="indexterm" name="id2551790"></a><a name="MAXCONNECTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows the number of simultaneous connections to a service to be limited.
     If <em class="parameter"><code>max connections</code></em> is greater than 0 then connections
     will be refused if this number of connections to the service are already open. A value 
     of zero mean an unlimited number of connections may be made.</p><p>Record lock files are used to implement this feature. The lock files will be stored in 
@@ -3835,10 +3731,10 @@ max connections (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max connections</code></em> = <code class="literal">10</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552001"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551875"></a>
 
 max disk size (G)
-</h3></div></div></div><a class="indexterm" name="id2552002"></a><a name="MAXDISKSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to put an upper limit 
+</h3></div></div></div><a class="indexterm" name="id2551876"></a><a name="MAXDISKSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to put an upper limit 
     on the apparent size of disks. If you set this option to 100 
     then all shares will appear to be not larger than 100 MB in 
     size.</p><p>Note that this option does not limit the amount of 
@@ -3852,10 +3748,10 @@ max disk size (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max disk size</code></em> = <code class="literal">1000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552093"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2551967"></a>
 
 max log size (G)
-</h3></div></div></div><a class="indexterm" name="id2552094"></a><a name="MAXLOGSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2551968"></a><a name="MAXLOGSIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This option (an integer in kilobytes) specifies the max size the log file should grow to. 
     Samba periodically checks the size and if it is exceeded it will rename the file, adding 
 	a <code class="filename">.old</code> extension.
@@ -3864,61 +3760,56 @@ max log size (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max log size</code></em> = <code class="literal">1000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552164"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552038"></a>
 
 max mux (G)
-</h3></div></div></div><a class="indexterm" name="id2552165"></a><a name="MAXMUX"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum number of 
+</h3></div></div></div><a class="indexterm" name="id2552039"></a><a name="MAXMUX"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum number of 
     outstanding simultaneous SMB operations that Samba tells the client 
 	it will allow. You should never need to set this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max mux</code></em> = <code class="literal">50</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552207"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552081"></a>
 
 max open files (G)
-</h3></div></div></div><a class="indexterm" name="id2552208"></a><a name="MAXOPENFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of
-    open files that one <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> file
-    serving process may have open for a client at any one time. The
-    This parameter can be set very high (16404) as Samba uses
-    only one bit per unopened file. Setting this parameter lower than
-    16404 will cause Samba to complain and set this value back to
-    the minimum of 16404, as Windows 7 depends on this number of
-    open file handles being available.</p><p>The limit of the number of open files is usually set
-    by the UNIX per-process file descriptor limit rather than
-    this parameter so you should never need to touch this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max open files</code></em> = <code class="literal">16404</code>
-</em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552270"></a>
+</h3></div></div></div><a class="indexterm" name="id2552082"></a><a name="MAXOPENFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of 
+    open files that one <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> file 
+    serving process may have open for a client at any one time. The 
+    default for this parameter is set very high (10,000) as Samba uses 
+    only one bit per unopened file.</p><p>The limit of the number of open files is usually set 
+    by the UNIX per-process file descriptor limit rather than 
+    this parameter so you should never need to touch this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max open files</code></em> = <code class="literal">10000</code>
+</em></span>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552141"></a>
 
 max print jobs (S)
-</h3></div></div></div><a class="indexterm" name="id2552271"></a><a name="MAXPRINTJOBS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of 
+</h3></div></div></div><a class="indexterm" name="id2552142"></a><a name="MAXPRINTJOBS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of 
     jobs allowable in a Samba printer queue at any given moment.
     If this number is exceeded, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will remote "Out of Space" to the client.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max print jobs</code></em> = <code class="literal">1000</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max print jobs</code></em> = <code class="literal">5000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552340"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552212"></a>
 
 <a name="PROTOCOL"></a>protocol
-</h3></div></div></div><a class="indexterm" name="id2552341"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#MAXPROTOCOL">max protocol</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552373"></a>
+</h3></div></div></div><a class="indexterm" name="id2552213"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#MAXPROTOCOL">max protocol</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552244"></a>
 
 max protocol (G)
-</h3></div></div></div><a class="indexterm" name="id2552374"></a><a name="MAXPROTOCOL"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a string) is the highest 
+</h3></div></div></div><a class="indexterm" name="id2552246"></a><a name="MAXPROTOCOL"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a string) is the highest 
     protocol level that will be supported by the server.</p><p>Possible values are :</p><div class="itemizedlist"><ul type="disc"><li><p><code class="constant">CORE</code>: Earliest version. No 
 	    concept of user names.</p></li><li><p><code class="constant">COREPLUS</code>: Slight improvements on 
 	    CORE for efficiency.</p></li><li><p><code class="constant">LANMAN1</code>: First <span class="emphasis"><em>
 	    modern</em></span> version of the protocol. Long filename
 	    support.</p></li><li><p><code class="constant">LANMAN2</code>: Updates to Lanman1 protocol.</p></li><li><p><code class="constant">NT1</code>: Current up to date version of the protocol. 
-	    Used by Windows NT. Known as CIFS.</p></li><li><p><code class="constant">SMB2</code>: Re-implementation of the SMB protocol.
-	    Used by Windows Vista and newer. The Samba implementation of SMB2 is
-	    currently marked experimental!</p></li></ul></div><p>Normally this option should not be set as the automatic 
+	    Used by Windows NT. Known as CIFS.</p></li></ul></div><p>Normally this option should not be set as the automatic 
     negotiation phase in the SMB protocol takes care of choosing 
 	the appropriate protocol.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max protocol</code></em> = <code class="literal">NT1</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max protocol</code></em> = <code class="literal">LANMAN1</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552510"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552370"></a>
 
 max reported print jobs (S)
-</h3></div></div></div><a class="indexterm" name="id2552511"></a><a name="MAXREPORTEDPRINTJOBS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2552371"></a><a name="MAXREPORTEDPRINTJOBS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter limits the maximum number of jobs displayed in a port monitor for 
     Samba printer queue at any given moment. If this number is exceeded, the excess 
     jobs will not be shown. A value of zero means there is no limit on the number of 
@@ -3927,10 +3818,10 @@ max reported print jobs (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max reported print jobs</code></em> = <code class="literal">1000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552574"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552434"></a>
 
 max smbd processes (G)
-</h3></div></div></div><a class="indexterm" name="id2552575"></a><a name="MAXSMBDPROCESSES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> processes concurrently running on a system and is intended
+</h3></div></div></div><a class="indexterm" name="id2552435"></a><a name="MAXSMBDPROCESSES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the maximum number of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> processes concurrently running on a system and is intended
     as a stopgap to prevent degrading service to clients in the event that the server has insufficient
     resources to handle more than this number of connections.  Remember that under normal operating
     conditions, each user will have an <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> associated with him or her to handle connections to all
@@ -3938,10 +3829,10 @@ max smbd processes (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max smbd processes</code></em> = <code class="literal">1000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552655"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552515"></a>
 
 max stat cache size (G)
-</h3></div></div></div><a class="indexterm" name="id2552656"></a><a name="MAXSTATCACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the size in memory of any 
+</h3></div></div></div><a class="indexterm" name="id2552516"></a><a name="MAXSTATCACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter limits the size in memory of any 
 	  <em class="parameter"><code>stat cache</code></em> being used
 	  to speed up case insensitive name mappings. It represents
 	  the number of kilobyte (1024) units the stat cache can use.
@@ -3952,27 +3843,27 @@ max stat cache size (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max stat cache size</code></em> = <code class="literal">100</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552725"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552584"></a>
 
 max ttl (G)
-</h3></div></div></div><a class="indexterm" name="id2552726"></a><a name="MAXTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> what the default 'time to live' 
+</h3></div></div></div><a class="indexterm" name="id2552585"></a><a name="MAXTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> what the default 'time to live' 
     of NetBIOS names should be (in seconds) when <code class="literal">nmbd</code> is 
     requesting a name using either a broadcast packet or from a WINS server. You should 
 	never need to change this parameter. The default is 3 days.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max ttl</code></em> = <code class="literal">259200</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552784"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552643"></a>
 
 max wins ttl (G)
-</h3></div></div></div><a class="indexterm" name="id2552785"></a><a name="MAXWINSTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when acting as a WINS server
+</h3></div></div></div><a class="indexterm" name="id2552644"></a><a name="MAXWINSTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when acting as a WINS server
 	(<a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a>) what the maximum
     'time to live' of NetBIOS names that <code class="literal">nmbd</code> 
     will grant will be (in seconds). You should never need to change this
 	parameter.  The default is 6 days (518400 seconds).</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>max wins ttl</code></em> = <code class="literal">518400</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552855"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552714"></a>
 
 max xmit (G)
-</h3></div></div></div><a class="indexterm" name="id2552856"></a><a name="MAXXMIT"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum packet size 
+</h3></div></div></div><a class="indexterm" name="id2552716"></a><a name="MAXXMIT"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum packet size 
     that will be negotiated by Samba. The default is 16644, which 
     matches the behavior of Windows 2000.  A value below 2048 is likely to cause problems.
     You should never need to change this parameter from its default value.
@@ -3980,10 +3871,10 @@ max xmit (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>max xmit</code></em> = <code class="literal">8192</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552917"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552777"></a>
 
 message command (G)
-</h3></div></div></div><a class="indexterm" name="id2552918"></a><a name="MESSAGECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies what command to run when the 
+</h3></div></div></div><a class="indexterm" name="id2552778"></a><a name="MESSAGECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies what command to run when the 
 	server receives a WinPopup style message.</p><p>This would normally be a command that would 
 	deliver the message somehow. How this is to be done is 
 	up to your imagination.</p><p>An example is:
@@ -4022,20 +3913,20 @@ message command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>message command</code></em> = <code class="literal">csh -c 'xedit %s; rm %s' &amp;</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553128"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552987"></a>
 
 min print space (S)
-</h3></div></div></div><a class="indexterm" name="id2553129"></a><a name="MINPRINTSPACE"></a><div class="variablelist"><dl><dt></dt><dd><p>This sets the minimum amount of free disk 
+</h3></div></div></div><a class="indexterm" name="id2552988"></a><a name="MINPRINTSPACE"></a><div class="variablelist"><dl><dt></dt><dd><p>This sets the minimum amount of free disk 
     space that must be available before a user will be able to spool 
     a print job. It is specified in kilobytes. The default is 0, which 
     means a user can always spool a print job.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>min print space</code></em> = <code class="literal">0</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>min print space</code></em> = <code class="literal">2000</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553190"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553050"></a>
 
 min protocol (G)
-</h3></div></div></div><a class="indexterm" name="id2553191"></a><a name="MINPROTOCOL"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a string) is the 
+</h3></div></div></div><a class="indexterm" name="id2553051"></a><a name="MINPROTOCOL"></a><div class="variablelist"><dl><dt></dt><dd><p>The value of the parameter (a string) is the 
     lowest SMB protocol dialect than Samba will support.  Please refer
     to the <a class="link" href="smb.conf.5.html#MAXPROTOCOL" target="_top">max protocol</a>
     parameter for a list of valid protocol names and a brief description
@@ -4047,10 +3938,10 @@ min protocol (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>min protocol</code></em> = <code class="literal">NT1</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553289"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553149"></a>
 
 min receivefile size (G)
-</h3></div></div></div><a class="indexterm" name="id2553290"></a><a name="MINRECEIVEFILESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option changes the behavior of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when processing SMBwriteX calls. Any incoming
+</h3></div></div></div><a class="indexterm" name="id2553150"></a><a name="MINRECEIVEFILESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option changes the behavior of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when processing SMBwriteX calls. Any incoming
 SMBwriteX call on a non-signed SMB/CIFS connection greater than this value will not be processed in the normal way but will
 be passed to any underlying kernel recvfile or splice system call (if there is no such
 call Samba will emulate in user space). This allows zero-copy writes directly from network
@@ -4059,19 +3950,19 @@ but user testing is recommended. If set to zero Samba processes SMBwriteX calls
 normal way. To enable POSIX large write support (SMB/CIFS writes up to 16Mb) this option must be
 nonzero. The maximum value is 128k. Values greater than 128k will be silently set to 128k.</p><p>Note this option will have NO EFFECT if set on a SMB signed connection.</p><p>The default is zero, which diables this option.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>min receivefile size</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553358"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553218"></a>
 
 min wins ttl (G)
-</h3></div></div></div><a class="indexterm" name="id2553359"></a><a name="MINWINSTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>
+</h3></div></div></div><a class="indexterm" name="id2553219"></a><a name="MINWINSTTL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option tells <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>
     when acting as a WINS server (<a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support = yes</a>) what the minimum 'time to live' 
     of NetBIOS names that <code class="literal">nmbd</code> will grant will be (in 
     seconds). You should never need to change this parameter.  The default 
     is 6 hours (21600 seconds).</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>min wins ttl</code></em> = <code class="literal">21600</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553429"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553288"></a>
 
 msdfs proxy (S)
-</h3></div></div></div><a class="indexterm" name="id2553430"></a><a name="MSDFSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter indicates that the share is a
+</h3></div></div></div><a class="indexterm" name="id2553290"></a><a name="MSDFSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter indicates that the share is a
 	stand-in for another CIFS share whose location is specified by
 	the value of the parameter. When clients attempt to connect to
 	this share, they are redirected to the proxied share using
@@ -4079,10 +3970,10 @@ msdfs proxy (S)
 	<a class="link" href="smb.conf.5.html#MSDFSROOT" target="_top">msdfs root</a> and <a class="link" href="smb.conf.5.html#HOSTMSDFS" target="_top">host msdfs</a>
 	options to find out how to set up a Dfs root share.</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>msdfs proxy</code></em> = <code class="literal">\otherserver\someshare</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553507"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553366"></a>
 
 msdfs root (S)
-</h3></div></div></div><a class="indexterm" name="id2553508"></a><a name="MSDFSROOT"></a><div class="variablelist"><dl><dt></dt><dd><p>If set to <code class="constant">yes</code>, Samba treats the
+</h3></div></div></div><a class="indexterm" name="id2553368"></a><a name="MSDFSROOT"></a><div class="variablelist"><dl><dt></dt><dd><p>If set to <code class="constant">yes</code>, Samba treats the
 	share as a Dfs root and allows clients to browse the
 	distributed file system tree rooted at the share directory.
 	Dfs links are specified in the share directory by symbolic
@@ -4090,20 +3981,20 @@ msdfs root (S)
 	and so on.  For more information on setting up a Dfs tree on
 	Samba, refer to the MSDFS chapter in the Samba3-HOWTO book.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>msdfs root</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553562"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553422"></a>
 
 name cache timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2553563"></a><a name="NAMECACHETIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the number of seconds it takes before 
+</h3></div></div></div><a class="indexterm" name="id2553423"></a><a name="NAMECACHETIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the number of seconds it takes before 
     entries in samba's hostname resolve cache time out. If 
     the timeout is set to 0. the caching is disabled.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>name cache timeout</code></em> = <code class="literal">660</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>name cache timeout</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553623"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553483"></a>
 
 name resolve order (G)
-</h3></div></div></div><a class="indexterm" name="id2553624"></a><a name="NAMERESOLVEORDER"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used by the programs in the Samba 
+</h3></div></div></div><a class="indexterm" name="id2553484"></a><a name="NAMERESOLVEORDER"></a><div class="variablelist"><dl><dt></dt><dd><p>This option is used by the programs in the Samba 
     suite to determine what naming services to use and in what order 
     to resolve host names to IP addresses. Its main purpose to is to
     control how netbios name resolution is performed.  The option takes a space 
@@ -4134,10 +4025,10 @@ name resolve order (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>name resolve order</code></em> = <code class="literal">lmhosts bcast host</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553831"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553685"></a>
 
 netbios aliases (G)
-</h3></div></div></div><a class="indexterm" name="id2553832"></a><a name="NETBIOSALIASES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of NetBIOS names that nmbd will 
+</h3></div></div></div><a class="indexterm" name="id2553686"></a><a name="NETBIOSALIASES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of NetBIOS names that nmbd will 
         advertise as additional names by which the Samba server is known. This allows one machine 
 	to appear in browse lists under multiple names. If a machine is acting as a browse server 
         or logon server none of these names will be advertised as either browse server or logon 
@@ -4147,10 +4038,10 @@ netbios aliases (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>netbios aliases</code></em> = <code class="literal">TEST TEST1 TEST2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553897"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553751"></a>
 
 netbios name (G)
-</h3></div></div></div><a class="indexterm" name="id2553898"></a><a name="NETBIOSNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2553752"></a><a name="NETBIOSNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 		This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component
 		of the host's DNS name. If a machine is a browse server or logon server this name (or the first component of
 		the hosts DNS name) will be the name that these services are advertised under.
@@ -4163,17 +4054,17 @@ netbios name (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>netbios name</code></em> = <code class="literal">MYNAME</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553978"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553833"></a>
 
 netbios scope (G)
-</h3></div></div></div><a class="indexterm" name="id2553979"></a><a name="NETBIOSSCOPE"></a><div class="variablelist"><dl><dt></dt><dd><p>This sets the NetBIOS scope that Samba will 
+</h3></div></div></div><a class="indexterm" name="id2553834"></a><a name="NETBIOSSCOPE"></a><div class="variablelist"><dl><dt></dt><dd><p>This sets the NetBIOS scope that Samba will 
 	operate under. This should not be set unless every machine 
 	on your LAN also sets this value.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>netbios scope</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554021"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553875"></a>
 
 nis homedir (G)
-</h3></div></div></div><a class="indexterm" name="id2554022"></a><a name="NISHOMEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>Get the home share server from a NIS map. For 
+</h3></div></div></div><a class="indexterm" name="id2553876"></a><a name="NISHOMEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>Get the home share server from a NIS map. For 
 	UNIX systems that use an automounter, the user's home directory 
 	will often be mounted on a workstation on demand from a remote 
 	server. </p><p>When the Samba logon server is not the actual home directory 
@@ -4192,20 +4083,20 @@ nis homedir (G)
 	NIS system and the Samba server with this option must also 
 	be a logon server.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>nis homedir</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554101"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553961"></a>
 
 nt acl support (S)
-</h3></div></div></div><a class="indexterm" name="id2554102"></a><a name="NTACLSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to map 
+</h3></div></div></div><a class="indexterm" name="id2553962"></a><a name="NTACLSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to map 
     UNIX permissions into Windows NT access control lists.  The UNIX
     permissions considered are the the traditional UNIX owner and
     group permissions, as well as POSIX ACLs set on any files or
     directories.  This parameter was formally a global parameter in
     releases prior to 2.2.2.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>nt acl support</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554156"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554016"></a>
 
 ntlm auth (G)
-</h3></div></div></div><a class="indexterm" name="id2554157"></a><a name="NTLMAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to
+</h3></div></div></div><a class="indexterm" name="id2554017"></a><a name="NTLMAUTH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines whether or not <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will attempt to
     authenticate users using the NTLM encrypted password response.
     If disabled, either the lanman password hash or an NTLMv2 response
     will need to be sent by the client.</p><p>If this option, and <code class="literal">lanman
@@ -4213,33 +4104,33 @@ ntlm auth (G)
     permited.  Not all clients support NTLMv2, and most will require
 	special configuration to use it.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>ntlm auth</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554220"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554080"></a>
 
 nt pipe support (G)
-</h3></div></div></div><a class="indexterm" name="id2554221"></a><a name="NTPIPESUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether 
+</h3></div></div></div><a class="indexterm" name="id2554081"></a><a name="NTPIPESUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether 
     <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will allow Windows NT 
     clients to connect to the NT SMB specific <code class="constant">IPC$</code> 
     pipes. This is a developer debugging option and can be left
 	alone.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>nt pipe support</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554276"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554136"></a>
 
 nt status support (G)
-</h3></div></div></div><a class="indexterm" name="id2554277"></a><a name="NTSTATUSSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will negotiate NT specific status
+</h3></div></div></div><a class="indexterm" name="id2554137"></a><a name="NTSTATUSSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will negotiate NT specific status
     support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone.
     If this option is set to <code class="constant">no</code> then Samba offers
     exactly the same DOS error codes that versions prior to Samba 2.2.3
     reported.</p><p>You should not need to ever disable this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>nt status support</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554337"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554197"></a>
 
 null passwords (G)
-</h3></div></div></div><a class="indexterm" name="id2554338"></a><a name="NULLPASSWORDS"></a><div class="variablelist"><dl><dt></dt><dd><p>Allow or disallow client access to accounts that have null passwords. </p><p>See also <a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>null passwords</code></em> = <code class="literal">no</code>
+</h3></div></div></div><a class="indexterm" name="id2554198"></a><a name="NULLPASSWORDS"></a><div class="variablelist"><dl><dt></dt><dd><p>Allow or disallow client access to accounts that have null passwords. </p><p>See also <a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>null passwords</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554391"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554251"></a>
 
 obey pam restrictions (G)
-</h3></div></div></div><a class="indexterm" name="id2554392"></a><a name="OBEYPAMRESTRICTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>When Samba 3.0 is configured to enable PAM support
+</h3></div></div></div><a class="indexterm" name="id2554252"></a><a name="OBEYPAMRESTRICTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>When Samba 3.0 is configured to enable PAM support
     (i.e. --with-pam), this parameter will control whether or not Samba
     should obey PAM's account and session management directives.  The 
     default behavior is to use PAM for clear text authentication only
@@ -4249,10 +4140,10 @@ obey pam restrictions (G)
     authentication mechanism needed in the presence of SMB password encryption.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>obey pam restrictions</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554455"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554315"></a>
 
 only user (S)
-</h3></div></div></div><a class="indexterm" name="id2554456"></a><a name="ONLYUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean option that controls whether 
+</h3></div></div></div><a class="indexterm" name="id2554316"></a><a name="ONLYUSER"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean option that controls whether 
     connections with usernames not in the <em class="parameter"><code>user</code></em> 
     list will be allowed. By default this option is disabled so that a 
     client can supply a username to be used by the server.  Enabling
@@ -4265,10 +4156,10 @@ only user (S)
     will be just the service name, which for home directories is the 
     name of the user.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>only user</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554544"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554404"></a>
 
 oplock break wait time (G)
-</h3></div></div></div><a class="indexterm" name="id2554545"></a><a name="OPLOCKBREAKWAITTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2554405"></a><a name="OPLOCKBREAKWAITTIME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too 
 	quickly when that client issues an SMB that can cause an oplock break request, then the network client can 
 	fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount 
@@ -4277,10 +4168,10 @@ oplock break wait time (G)
 	DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
 	</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>oplock break wait time</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554599"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554459"></a>
 
 oplock contention limit (S)
-</h3></div></div></div><a class="indexterm" name="id2554600"></a><a name="OPLOCKCONTENTIONLIMIT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2554460"></a><a name="OPLOCKCONTENTIONLIMIT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is a <span class="emphasis"><em>very</em></span> advanced <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> tuning option to improve the efficiency of the 
 	granting of oplocks under multiple client contention for the same file.
 	</p><p>
@@ -4292,10 +4183,10 @@ oplock contention limit (S)
 	DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
 	</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>oplock contention limit</code></em> = <code class="literal">2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554681"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554542"></a>
 
 oplocks (S)
-</h3></div></div></div><a class="indexterm" name="id2554682"></a><a name="OPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2554543"></a><a name="OPLOCKS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean option tells <code class="literal">smbd</code> whether to 
 	issue oplocks (opportunistic locks) to file open requests on this 
 	share. The oplock code can dramatically (approx. 30% or more) improve 
@@ -4312,10 +4203,10 @@ oplocks (S)
 	<a class="link" href="smb.conf.5.html#KERNELOPLOCKS" target="_top">kernel oplocks</a> parameter for details.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>oplocks</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554774"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554627"></a>
 
 os2 driver map (G)
-</h3></div></div></div><a class="indexterm" name="id2554775"></a><a name="OS2DRIVERMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>The parameter is used to define the absolute
+</h3></div></div></div><a class="indexterm" name="id2554628"></a><a name="OS2DRIVERMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>The parameter is used to define the absolute
     path to a file containing a mapping of Windows NT printer driver
     names to OS/2 printer driver names.  The format is:</p><p>&lt;nt driver name&gt; = &lt;os2 driver name&gt;.&lt;device name&gt;</p><p>For example, a valid entry using the HP LaserJet 5
     printer driver would appear as <code class="literal">HP LaserJet 5L = LASERJET.HP 
@@ -4325,10 +4216,10 @@ os2 driver map (G)
     details on OS/2 clients, please refer to chapter on other clients in the Samba3-HOWTO book.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>os2 driver map</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554841"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554694"></a>
 
 os level (G)
-</h3></div></div></div><a class="indexterm" name="id2554842"></a><a name="OSLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2554695"></a><a name="OSLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This integer value controls what level Samba advertises itself as for browse elections. The value of this
 	parameter determines whether <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> has a chance of becoming a local master browser for the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> in the local broadcast area.
 </p><p><span class="emphasis"><em>
@@ -4344,10 +4235,10 @@ os level (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>os level</code></em> = <code class="literal">65</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554940"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554794"></a>
 
 pam password change (G)
-</h3></div></div></div><a class="indexterm" name="id2554941"></a><a name="PAMPASSWORDCHANGE"></a><div class="variablelist"><dl><dt></dt><dd><p>With the addition of better PAM support in Samba 2.2, 
+</h3></div></div></div><a class="indexterm" name="id2554795"></a><a name="PAMPASSWORDCHANGE"></a><div class="variablelist"><dl><dt></dt><dd><p>With the addition of better PAM support in Samba 2.2, 
     this parameter, it is possible to use PAM's password change control 
     flag for Samba.  If enabled, then PAM will be used for password
     changes when requested by an SMB client instead of the program listed in 
@@ -4355,20 +4246,20 @@ pam password change (G)
     It should be possible to enable this without changing your 
     <a class="link" href="smb.conf.5.html#PASSWDCHAT" target="_top">passwd chat</a> parameter for most setups.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>pam password change</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555013"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554867"></a>
 
 panic action (G)
-</h3></div></div></div><a class="indexterm" name="id2555014"></a><a name="PANICACTION"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a Samba developer option that allows a 
+</h3></div></div></div><a class="indexterm" name="id2554868"></a><a name="PANICACTION"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a Samba developer option that allows a 
 	system command to be called when either <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> or <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>	crashes. This is usually used to 
 	draw attention to the fact that a problem occurred.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>panic action</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>panic action</code></em> = <code class="literal">"/bin/sleep 90000"</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555089"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554942"></a>
 
 paranoid server security (G)
-</h3></div></div></div><a class="indexterm" name="id2555090"></a><a name="PARANOIDSERVERSECURITY"></a><div class="variablelist"><dl><dt></dt><dd><p>Some version of NT 4.x allow non-guest 
+</h3></div></div></div><a class="indexterm" name="id2554944"></a><a name="PARANOIDSERVERSECURITY"></a><div class="variablelist"><dl><dt></dt><dd><p>Some version of NT 4.x allow non-guest 
     users with a bad passowrd. When this option is enabled, samba will not 
     use a broken NT 4.x server as password server, but instead complain
     to the logs and exit.  
@@ -4376,10 +4267,10 @@ paranoid server security (G)
     this check, which involves deliberatly attempting a
     bad logon to the remote server.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>paranoid server security</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555140"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554994"></a>
 
 passdb backend (G)
-</h3></div></div></div><a class="indexterm" name="id2555141"></a><a name="PASSDBBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows the administrator to chose which backend
+</h3></div></div></div><a class="indexterm" name="id2554995"></a><a name="PASSDBBACKEND"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows the administrator to chose which backend
     will be used for storing user and possibly group information.  This allows 
     you to swap between different storage mechanisms without recompile. </p><p>The parameter value is divided into two parts, the backend's name, and a 'location'
     string that has meaning only to that particular backed.  These are separated
@@ -4414,19 +4305,19 @@ or multi server LDAP URL with Netscape based LDAP library:
 passdb backend = ldapsam:"ldap://ldap-1.example.com ldap-2.example.com"
 </pre><p>Default: <span class="emphasis"><em><em class="parameter"><code>passdb backend</code></em> = <code class="literal">tdbsam</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555299"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555152"></a>
 
 passdb expand explicit (G)
-</h3></div></div></div><a class="indexterm" name="id2555300"></a><a name="PASSDBEXPANDEXPLICIT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2555154"></a><a name="PASSDBEXPANDEXPLICIT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter controls whether Samba substitutes %-macros in the passdb fields if they are explicitly set. We
 	used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable
 	%G_osver% in which %G would have been substituted by the user's primary group.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>passdb expand explicit</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555346"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555199"></a>
 
 passwd chat debug (G)
-</h3></div></div></div><a class="indexterm" name="id2555347"></a><a name="PASSWDCHATDEBUG"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean specifies if the passwd chat script 
+</h3></div></div></div><a class="indexterm" name="id2555200"></a><a name="PASSWDCHATDEBUG"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean specifies if the passwd chat script 
     parameter is run in <span class="emphasis"><em>debug</em></span> mode. In this mode the 
     strings passed to and received from the passwd chat are printed 
     in the <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> log with a 
@@ -4439,18 +4330,18 @@ passwd chat debug (G)
     <a class="link" href="smb.conf.5.html#PAMPASSWORDCHANGE" target="_top">pam password change</a>
 	parameter is set. This parameter is off by default.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>passwd chat debug</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555449"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555303"></a>
 
 passwd chat timeout (G)
-</h3></div></div></div><a class="indexterm" name="id2555450"></a><a name="PASSWDCHATTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>This integer specifies the number of seconds smbd will wait for an initial
+</h3></div></div></div><a class="indexterm" name="id2555304"></a><a name="PASSWDCHATTIMEOUT"></a><div class="variablelist"><dl><dt></dt><dd><p>This integer specifies the number of seconds smbd will wait for an initial
     answer from a passwd chat script being run. Once the initial answer is received
     the subsequent answers must be received in one tenth of this time. The default it
     two seconds.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>passwd chat timeout</code></em> = <code class="literal">2</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555494"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555348"></a>
 
 passwd chat (G)
-</h3></div></div></div><a class="indexterm" name="id2555495"></a><a name="PASSWDCHAT"></a><div class="variablelist"><dl><dt></dt><dd><p>This string controls the <span class="emphasis"><em>"chat"</em></span> 
+</h3></div></div></div><a class="indexterm" name="id2555349"></a><a name="PASSWDCHAT"></a><div class="variablelist"><dl><dt></dt><dd><p>This string controls the <span class="emphasis"><em>"chat"</em></span> 
     conversation that takes places between <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and the local password changing
     program to change the user's password. The string describes a 
     sequence of response-receive pairs that <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> uses to determine what to send to the 
@@ -4481,10 +4372,10 @@ passwd chat (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>passwd chat</code></em> = <code class="literal">"*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555700"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555553"></a>
 
 passwd program (G)
-</h3></div></div></div><a class="indexterm" name="id2555701"></a><a name="PASSWDPROGRAM"></a><div class="variablelist"><dl><dt></dt><dd><p>The name of a program that can be used to set 
+</h3></div></div></div><a class="indexterm" name="id2555554"></a><a name="PASSWDPROGRAM"></a><div class="variablelist"><dl><dt></dt><dd><p>The name of a program that can be used to set 
     UNIX user passwords.  Any occurrences of <em class="parameter"><code>%u</code></em> 
     will be replaced with the user name. The user name is checked for 
     existence before calling the password changing program.</p><p>Also note that many passwd programs insist in <span class="emphasis"><em>reasonable
@@ -4505,10 +4396,10 @@ passwd program (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>passwd program</code></em> = <code class="literal">/bin/passwd %u</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555835"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555688"></a>
 
 password level (G)
-</h3></div></div></div><a class="indexterm" name="id2555836"></a><a name="PASSWORDLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>Some client/server combinations have difficulty 
+</h3></div></div></div><a class="indexterm" name="id2555690"></a><a name="PASSWORDLEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>Some client/server combinations have difficulty 
     with mixed-case passwords.  One offending client is Windows for 
     Workgroups, which for some reason forces passwords to upper 
     case when using the LANMAN1 protocol, but leaves them alone when 
@@ -4530,10 +4421,10 @@ password level (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>password level</code></em> = <code class="literal">4</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555972"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555825"></a>
 
 password server (G)
-</h3></div></div></div><a class="indexterm" name="id2555973"></a><a name="PASSWORDSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>By specifying the name of another SMB server 
+</h3></div></div></div><a class="indexterm" name="id2555826"></a><a name="PASSWORDSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>By specifying the name of another SMB server 
     or Active Directory domain controller with this option, 
     and using <code class="literal">security = [ads|domain|server]</code> 
     it is possible to get Samba
@@ -4593,13 +4484,13 @@ password server (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>password server</code></em> = <code class="literal">windc.mydomain.com:389 192.168.1.101 *</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556270"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556124"></a>
 
 <a name="DIRECTORY"></a>directory
-</h3></div></div></div><a class="indexterm" name="id2556271"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PATH">path</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556301"></a>
+</h3></div></div></div><a class="indexterm" name="id2556125"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PATH">path</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556155"></a>
 
 path (S)
-</h3></div></div></div><a class="indexterm" name="id2556302"></a><a name="PATH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a directory to which 
+</h3></div></div></div><a class="indexterm" name="id2556156"></a><a name="PATH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a directory to which 
 	the user of the service is to be given access. In the case of 
 	printable services, this is where print data will spool prior to 
 	being submitted to the host for printing.</p><p>For a printable service offering guest access, the service 
@@ -4616,25 +4507,25 @@ path (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>path</code></em> = <code class="literal">/home/fred</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556405"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556259"></a>
 
 perfcount module (G)
-</h3></div></div></div><a class="indexterm" name="id2556406"></a><a name="PERFCOUNTMODULE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the perfcount backend to be used when monitoring SMB
+</h3></div></div></div><a class="indexterm" name="id2556260"></a><a name="PERFCOUNTMODULE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the perfcount backend to be used when monitoring SMB
 	operations.  Only one perfcount module may be used, and it must implement all of the
 	apis contained in the smb_perfcount_handler structure defined in smb.h.
-	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556439"></a>
+	</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556293"></a>
 
 pid directory (G)
-</h3></div></div></div><a class="indexterm" name="id2556440"></a><a name="PIDDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2556294"></a><a name="PIDDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This option specifies the directory where pid files will be placed.  
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>pid directory</code></em> = <code class="literal">${prefix}/var/locks</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>pid directory</code></em> = <code class="literal">pid directory = /var/run/</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556499"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556352"></a>
 
 posix locking (S)
-</h3></div></div></div><a class="indexterm" name="id2556500"></a><a name="POSIXLOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2556353"></a><a name="POSIXLOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	The <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>
 	daemon maintains an database of file locks obtained by SMB clients. The default behavior is 
 	to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are 
@@ -4642,10 +4533,10 @@ posix locking (S)
 	method (e.g. NFS or local file access). You should never need to disable this parameter.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>posix locking</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556554"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556408"></a>
 
 postexec (S)
-</h3></div></div></div><a class="indexterm" name="id2556555"></a><a name="POSTEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies a command to be run 
+</h3></div></div></div><a class="indexterm" name="id2556409"></a><a name="POSTEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies a command to be run 
 	whenever the service is disconnected. It takes the usual 
 	substitutions. The command may be run as the root on some 
 	systems.</p><p>An interesting example may be to unmount server 
@@ -4653,21 +4544,21 @@ postexec (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>postexec</code></em> = <code class="literal">echo \"%u disconnected from %S from %m (%I)\" &gt;&gt; /tmp/log</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556627"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556481"></a>
 
 preexec close (S)
-</h3></div></div></div><a class="indexterm" name="id2556628"></a><a name="PREEXECCLOSE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2556482"></a><a name="PREEXECCLOSE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean option controls whether a non-zero return code from <a class="link" href="smb.conf.5.html#PREEXEC" target="_top">preexec</a> 
 	should close the service being connected to.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>preexec close</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556682"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556536"></a>
 
 <a name="EXEC"></a>exec
-</h3></div></div></div><a class="indexterm" name="id2556683"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PREEXEC">preexec</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556714"></a>
+</h3></div></div></div><a class="indexterm" name="id2556537"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PREEXEC">preexec</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556567"></a>
 
 preexec (S)
-</h3></div></div></div><a class="indexterm" name="id2556715"></a><a name="PREEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies a command to be run whenever 
+</h3></div></div></div><a class="indexterm" name="id2556568"></a><a name="PREEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies a command to be run whenever 
 	the service is connected to. It takes the usual substitutions.</p><p>An interesting example is to send the users a welcome 
 	message every time they log in. Maybe a message of the day? Here 
 	is an example:</p><p>
@@ -4679,13 +4570,13 @@ preexec (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>preexec</code></em> = <code class="literal">echo \"%u connected to %S from %m (%I)\" &gt;&gt; /tmp/log</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556822"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556676"></a>
 
 <a name="PREFEREDMASTER"></a>prefered master
-</h3></div></div></div><a class="indexterm" name="id2556823"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PREFERREDMASTER">preferred master</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556855"></a>
+</h3></div></div></div><a class="indexterm" name="id2556677"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PREFERREDMASTER">preferred master</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556709"></a>
 
 preferred master (G)
-</h3></div></div></div><a class="indexterm" name="id2556856"></a><a name="PREFERREDMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2556710"></a><a name="PREFERREDMASTER"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter controls if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> is a preferred master browser  for its workgroup.
 	</p><p>
 	If this is set to <code class="constant">yes</code>, on startup, <code class="literal">nmbd</code> will force
@@ -4699,22 +4590,22 @@ preferred master (G)
 	capabilities.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>preferred master</code></em> = <code class="literal">auto</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556948"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556802"></a>
 
 preload modules (G)
-</h3></div></div></div><a class="indexterm" name="id2556949"></a><a name="PRELOADMODULES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of paths to modules that should
+</h3></div></div></div><a class="indexterm" name="id2556803"></a><a name="PRELOADMODULES"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of paths to modules that should
 	be loaded into smbd before a client connects. This improves
 	the speed of smbd when reacting to new connections somewhat. </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>preload modules</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>preload modules</code></em> = <code class="literal">/usr/lib/samba/passdb/mysql.so</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557009"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556863"></a>
 
 <a name="AUTOSERVICES"></a>auto services
-</h3></div></div></div><a class="indexterm" name="id2557010"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRELOAD">preload</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557042"></a>
+</h3></div></div></div><a class="indexterm" name="id2556864"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRELOAD">preload</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556896"></a>
 
 preload (G)
-</h3></div></div></div><a class="indexterm" name="id2557043"></a><a name="PRELOAD"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of services that you want to be 
+</h3></div></div></div><a class="indexterm" name="id2556897"></a><a name="PRELOAD"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a list of services that you want to be 
 	automatically added to the browse lists. This is most useful 
 	for homes and printers services that would otherwise not be 
 	visible.</p><p>
@@ -4725,33 +4616,33 @@ preload (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>preload</code></em> = <code class="literal">fred lp colorlp</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557120"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556974"></a>
 
 preserve case (S)
-</h3></div></div></div><a class="indexterm" name="id2557121"></a><a name="PRESERVECASE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2556975"></a><a name="PRESERVECASE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls if new filenames are created with the case that the client passes, or if 
 	they are forced to be the <a class="link" href="smb.conf.5.html#DEFAULTCASE" target="_top">default case</a>.
 	</p><p>
 	See the section on <a class="link" href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a> for a fuller discussion.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>preserve case</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557187"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557040"></a>
 
 <a name="PRINTOK"></a>print ok
-</h3></div></div></div><a class="indexterm" name="id2557188"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTABLE">printable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557218"></a>
+</h3></div></div></div><a class="indexterm" name="id2557041"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTABLE">printable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557071"></a>
 
 printable (S)
-</h3></div></div></div><a class="indexterm" name="id2557219"></a><a name="PRINTABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code>, then 
+</h3></div></div></div><a class="indexterm" name="id2557072"></a><a name="PRINTABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code>, then 
     clients may open, write to and submit spool files on the directory 
     specified for the service. </p><p>Note that a printable service will ALWAYS allow writing 
     to the service path (user privileges permitting) via the spooling 
     of print data. The <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only</a> parameter controls only non-printing access to 
     the resource.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>printable</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557281"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557135"></a>
 
 printcap cache time (G)
-</h3></div></div></div><a class="indexterm" name="id2557282"></a><a name="PRINTCAPCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the number of seconds before the printing
+</h3></div></div></div><a class="indexterm" name="id2557136"></a><a name="PRINTCAPCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the number of seconds before the printing
     subsystem is again asked for the known printers.  If the value
     is greater than 60 the initial waiting time is set to 60 seconds
     to allow an earlier first rescan of the printing subsystem.
@@ -4761,13 +4652,13 @@ printcap cache time (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>printcap cache time</code></em> = <code class="literal">600</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557350"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557203"></a>
 
 <a name="PRINTCAP"></a>printcap
-</h3></div></div></div><a class="indexterm" name="id2557351"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTCAPNAME">printcap name</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557383"></a>
+</h3></div></div></div><a class="indexterm" name="id2557204"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTCAPNAME">printcap name</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557236"></a>
 
 printcap name (G)
-</h3></div></div></div><a class="indexterm" name="id2557384"></a><a name="PRINTCAPNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2557237"></a><a name="PRINTCAPNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter may be used to override the compiled-in default printcap name used by the server (usually
 	<code class="filename"> /etc/printcap</code>). See the discussion of the <a class="link" href="#PRINTERSSECT" title="The [printers] section">[printers]</a> section above for reasons why you might want to do this.
 	</p><p>
@@ -4802,10 +4693,10 @@ print5|My Printer 5
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>printcap name</code></em> = <code class="literal">/etc/myprintcap</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557567"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557421"></a>
 
 print command (S)
-</h3></div></div></div><a class="indexterm" name="id2557568"></a><a name="PRINTCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>After a print job has finished spooling to 
+</h3></div></div></div><a class="indexterm" name="id2557422"></a><a name="PRINTCOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>After a print job has finished spooling to 
     a service, this command will be used via a <code class="literal">system()</code> 
     call to process the spool file. Typically the command specified will 
     submit the spool file to the host's printing subsystem, but there 
@@ -4847,10 +4738,10 @@ print command (S)
     and if SAMBA is compiled against libcups, any manually 
 	set print command will be ignored.</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>print command</code></em> = <code class="literal">/usr/local/samba/bin/myprintscript %p %s</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557837"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557691"></a>
 
 printer admin (S)
-</h3></div></div></div><a class="indexterm" name="id2557838"></a><a name="PRINTERADMIN"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2557692"></a><a name="PRINTERADMIN"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This lists users who can do anything to printers
 	via the remote administration interfaces offered
 	by MS-RPC (usually using a NT workstation).
@@ -4866,13 +4757,13 @@ printer admin (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>printer admin</code></em> = <code class="literal">admin, @staff</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557906"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557760"></a>
 
 <a name="PRINTER"></a>printer
-</h3></div></div></div><a class="indexterm" name="id2557907"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTERNAME">printer name</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557938"></a>
+</h3></div></div></div><a class="indexterm" name="id2557761"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#PRINTERNAME">printer name</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557791"></a>
 
 printer name (S)
-</h3></div></div></div><a class="indexterm" name="id2557939"></a><a name="PRINTERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2557792"></a><a name="PRINTERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter specifies the name of the printer to which print jobs spooled through a printable service
 	will be sent.
 	</p><p>
@@ -4885,10 +4776,10 @@ printer name (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>printer name</code></em> = <code class="literal">laserwriter</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558025"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2557879"></a>
 
 printing (S)
-</h3></div></div></div><a class="indexterm" name="id2558026"></a><a name="PRINTING"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameters controls how printer status  information is
+</h3></div></div></div><a class="indexterm" name="id2557880"></a><a name="PRINTING"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameters controls how printer status  information is
     interpreted on your system. It also affects the  default values for
     the <em class="parameter"><code>print command</code></em>,  <em class="parameter"><code>lpq command</code></em>, <em class="parameter"><code>lppause command </code></em>, <em class="parameter"><code>lpresume command</code></em>, and  <em class="parameter"><code>lprm command</code></em> if specified in the 
     [global] section.</p><p>Currently nine printing styles are supported. They are
@@ -4905,27 +4796,27 @@ printing (S)
     [printers]</a> section.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>printing</code></em> = <code class="literal">Depends on the operating system, see
 <code class="literal">testparm -v.</code></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558179"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558032"></a>
 
 printjob username (S)
-</h3></div></div></div><a class="indexterm" name="id2558180"></a><a name="PRINTJOBUSERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies which user information will be 
+</h3></div></div></div><a class="indexterm" name="id2558033"></a><a name="PRINTJOBUSERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies which user information will be 
     passed to the printing system. Usually, the username is sent,
     but in some cases, e.g. the domain prefix is useful, too.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>printjob username</code></em> = <code class="literal">%U</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>printjob username</code></em> = <code class="literal">%D\%U</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558240"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558094"></a>
 
 private dir (G)
-</h3></div></div></div><a class="indexterm" name="id2558241"></a><a name="PRIVATEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameters defines the directory
+</h3></div></div></div><a class="indexterm" name="id2558095"></a><a name="PRIVATEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameters defines the directory
     smbd will use for storing such files as <code class="filename">smbpasswd</code>
     and <code class="filename">secrets.tdb</code>.
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>private dir</code></em> = <code class="literal">${prefix}/private</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558294"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558148"></a>
 
 profile acls (S)
-</h3></div></div></div><a class="indexterm" name="id2558295"></a><a name="PROFILEACLS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2558149"></a><a name="PROFILEACLS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter was added to fix the problems that people have been
 	having with storing user profiles on Samba shares from Windows 2000 or
 	Windows XP clients. New versions of Windows 2000 or Windows XP service
@@ -4953,10 +4844,10 @@ profile acls (S)
 	tree to the owning user.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>profile acls</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558378"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558221"></a>
 
 queuepause command (S)
-</h3></div></div></div><a class="indexterm" name="id2558379"></a><a name="QUEUEPAUSECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2558222"></a><a name="QUEUEPAUSECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to pause the printer queue.</p><p>This command should be a program or script which takes 
     a printer name as its only parameter and stops the printer queue, 
     such that no longer jobs are submitted to the printer.</p><p>This command is not supported by Windows for Workgroups, 
@@ -4967,10 +4858,10 @@ queuepause command (S)
     path in the command as the PATH may not be available to the 
 	server.</p><p><span class="emphasis"><em>No default</em></span></p><p>Example: <span class="emphasis"><em><em class="parameter"><code>queuepause command</code></em> = <code class="literal">disable %p</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558455"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558297"></a>
 
 queueresume command (S)
-</h3></div></div></div><a class="indexterm" name="id2558456"></a><a name="QUEUERESUMECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
+</h3></div></div></div><a class="indexterm" name="id2558298"></a><a name="QUEUERESUMECOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the command to be 
     executed on the server host in order to resume the printer queue. It 
     is the command to undo the behavior that is caused by the 
     previous parameter (<a class="link" href="smb.conf.5.html#QUEUEPAUSECOMMAND" target="_top">queuepause command</a>).</p><p>This command should be a program or script which takes 
@@ -4985,10 +4876,10 @@ queueresume command (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>queueresume command</code></em> = <code class="literal">enable %p</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558558"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558400"></a>
 
 read list (S)
-</h3></div></div></div><a class="indexterm" name="id2558559"></a><a name="READLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2558401"></a><a name="READLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is a list of users that are given read-only access to a service. If the connecting user is in this list
 	then they will not be given write access, no matter what the <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only</a> option is set
 	to. The list can include group names using the syntax described in the <a class="link" href="smb.conf.5.html#INVALIDUSERS" target="_top">invalid users</a>
@@ -4998,19 +4889,19 @@ read list (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>read list</code></em> = <code class="literal">mary, @students</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558657"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558500"></a>
 
 read only (S)
-</h3></div></div></div><a class="indexterm" name="id2558658"></a><a name="READONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>An inverted synonym is <a class="link" href="smb.conf.5.html#WRITEABLE" target="_top">writeable</a>.</p><p>If this parameter is <code class="constant">yes</code>, then users 
+</h3></div></div></div><a class="indexterm" name="id2558501"></a><a name="READONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>An inverted synonym is <a class="link" href="smb.conf.5.html#WRITEABLE" target="_top">writeable</a>.</p><p>If this parameter is <code class="constant">yes</code>, then users 
     of a service may not create or modify files in the service's 
     directory.</p><p>Note that a printable service (<code class="literal">printable = yes</code>)
     will <span class="emphasis"><em>ALWAYS</em></span> allow writing to the directory 
     (user privileges permitting), but only via spooling operations.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>read only</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558734"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558577"></a>
 
 read raw (G)
-</h3></div></div></div><a class="indexterm" name="id2558735"></a><a name="READRAW"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not the server 
+</h3></div></div></div><a class="indexterm" name="id2558578"></a><a name="READRAW"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not the server 
     will support the raw read SMB requests when transferring data 
     to clients.</p><p>If enabled, raw reads allow reads of 65535 bytes in 
     one packet. This typically provides a major performance benefit.
@@ -5019,20 +4910,20 @@ read raw (G)
 	sizes, and for these clients you may need to disable raw reads.</p><p>In general this parameter should be viewed as a system tuning 
 	tool and left severely alone.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>read raw</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558794"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558637"></a>
 
 realm (G)
-</h3></div></div></div><a class="indexterm" name="id2558796"></a><a name="REALM"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the kerberos realm to use. The realm is 
+</h3></div></div></div><a class="indexterm" name="id2558638"></a><a name="REALM"></a><div class="variablelist"><dl><dt></dt><dd><p>This option specifies the kerberos realm to use. The realm is 
 	used as the ADS equivalent of the NT4 <code class="literal">domain</code>. It
 	is usually set to the DNS name of the kerberos server.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>realm</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>realm</code></em> = <code class="literal">mysambabox.mycompany.com</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558859"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558702"></a>
 
 registry shares (G)
-</h3></div></div></div><a class="indexterm" name="id2558860"></a><a name="REGISTRYSHARES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2558703"></a><a name="REGISTRYSHARES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This turns on or off support for share definitions read from
 	registry. Shares defined in <span class="emphasis"><em>smb.conf</em></span> take
 	precedence over shares with the same name defined in
@@ -5047,10 +4938,10 @@ registry shares (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>registry shares</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558946"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558788"></a>
 
 remote announce (G)
-</h3></div></div></div><a class="indexterm" name="id2558947"></a><a name="REMOTEANNOUNCE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2558789"></a><a name="REMOTEANNOUNCE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This option allows you to setup <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to periodically announce itself 
 	to arbitrary IP addresses with an arbitrary workgroup name.
 	</p><p>
@@ -5074,10 +4965,10 @@ remote announce (G)
 	See the chapter on Network Browsing in the Samba-HOWTO book.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>remote announce</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559051"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2558894"></a>
 
 remote browse sync (G)
-</h3></div></div></div><a class="indexterm" name="id2559052"></a><a name="REMOTEBROWSESYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2558895"></a><a name="REMOTEBROWSESYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This option allows you to setup <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to periodically request 
 	synchronization of browse lists with the master browser of a Samba 
 	server that is on a remote segment. This option will allow you to 
@@ -5109,10 +5000,10 @@ remote browse sync (G)
 	each network has its own WINS server.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>remote browse sync</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559164"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559011"></a>
 
 rename user script (G)
-</h3></div></div></div><a class="indexterm" name="id2559165"></a><a name="RENAMEUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2559012"></a><a name="RENAMEUSERSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the full pathname to a script that will be run as root by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> under special circumstances described below.
 	</p><p>
 	When a user with admin authority or SeAddUserPrivilege rights renames a user (e.g.: from the NT4 User Manager
@@ -5130,10 +5021,10 @@ rename user script (G)
 	needs to change for other applications using the same directory.
 	</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>rename user script</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559254"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559102"></a>
 
 reset on zero vc (G)
-</h3></div></div></div><a class="indexterm" name="id2559255"></a><a name="RESETONZEROVC"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2559103"></a><a name="RESETONZEROVC"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean option controls whether an incoming session setup
 	should kill other connections coming from the same IP. This matches
         the default Windows 2003 behaviour.
@@ -5152,10 +5043,10 @@ reset on zero vc (G)
 
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>reset on zero vc</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559307"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559166"></a>
 
 restrict anonymous (G)
-</h3></div></div></div><a class="indexterm" name="id2559308"></a><a name="RESTRICTANONYMOUS"></a><div class="variablelist"><dl><dt></dt><dd><p>The setting of this parameter determines whether user and
+</h3></div></div></div><a class="indexterm" name="id2559167"></a><a name="RESTRICTANONYMOUS"></a><div class="variablelist"><dl><dt></dt><dd><p>The setting of this parameter determines whether user and
     group list information is returned for an anonymous connection.
     and mirrors the effects of the
 </p><pre class="programlisting">
@@ -5178,16 +5069,16 @@ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
     by setting <a class="link" href="smb.conf.5.html#GUESTOK" target="_top">guest ok = yes</a> on any share.
 	</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>restrict anonymous</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559391"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559250"></a>
 
 <a name="ROOT"></a>root
-</h3></div></div></div><a class="indexterm" name="id2559392"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#ROOTDIRECTORY">root directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559424"></a>
+</h3></div></div></div><a class="indexterm" name="id2559251"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#ROOTDIRECTORY">root directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559283"></a>
 
 <a name="ROOTDIR"></a>root dir
-</h3></div></div></div><a class="indexterm" name="id2559425"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#ROOTDIRECTORY">root directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559456"></a>
+</h3></div></div></div><a class="indexterm" name="id2559284"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#ROOTDIRECTORY">root directory</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559314"></a>
 
 root directory (G)
-</h3></div></div></div><a class="indexterm" name="id2559457"></a><a name="ROOTDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>The server will <code class="literal">chroot()</code> (i.e. 
+</h3></div></div></div><a class="indexterm" name="id2559316"></a><a name="ROOTDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>The server will <code class="literal">chroot()</code> (i.e. 
     Change its root directory) to this directory on startup. This is 
     not strictly necessary for secure operation. Even without it the 
     server will deny access to files not in one of the service entries. 
@@ -5210,34 +5101,34 @@ root directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>root directory</code></em> = <code class="literal">/homes/smb</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559580"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559438"></a>
 
 root postexec (S)
-</h3></div></div></div><a class="indexterm" name="id2559581"></a><a name="ROOTPOSTEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2559440"></a><a name="ROOTPOSTEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the same as the <em class="parameter"><code>postexec</code></em>
 	parameter except that the command is run as root. This is useful for 
 	unmounting filesystems (such as CDROMs) after a connection is closed.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>root postexec</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559628"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559487"></a>
 
 root preexec close (S)
-</h3></div></div></div><a class="indexterm" name="id2559629"></a><a name="ROOTPREEXECCLOSE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the same as the <em class="parameter"><code>preexec close
+</h3></div></div></div><a class="indexterm" name="id2559488"></a><a name="ROOTPREEXECCLOSE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is the same as the <em class="parameter"><code>preexec close
 	</code></em> parameter except that the command is run as root.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>root preexec close</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559677"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559536"></a>
 
 root preexec (S)
-</h3></div></div></div><a class="indexterm" name="id2559678"></a><a name="ROOTPREEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2559537"></a><a name="ROOTPREEXEC"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is the same as the <em class="parameter"><code>preexec</code></em>
 	parameter except that the command is run as root. This is useful for 
 	mounting filesystems (such as CDROMs) when a connection is opened.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>root preexec</code></em> = <code class="literal"></code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559725"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559584"></a>
 
 security mask (S)
-</h3></div></div></div><a class="indexterm" name="id2559726"></a><a name="SECURITYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2559585"></a><a name="SECURITYMASK"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the
 	UNIX permission on a file using the native NT security dialog box.
 	</p><p>
@@ -5256,10 +5147,10 @@ security mask (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>security mask</code></em> = <code class="literal">0770</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559831"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559690"></a>
 
 security (G)
-</h3></div></div></div><a class="indexterm" name="id2559832"></a><a name="SECURITY"></a><div class="variablelist"><dl><dt></dt><dd><p>This option affects how clients respond to 
+</h3></div></div></div><a class="indexterm" name="id2559691"></a><a name="SECURITY"></a><div class="variablelist"><dl><dt></dt><dd><p>This option affects how clients respond to 
     Samba and is one of the most important settings in the <code class="filename">
     smb.conf</code> file.</p><p>The option sets the "security mode bit" in replies to 
     protocol negotiations with <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> to turn share level security on or off. Clients decide 
@@ -5383,10 +5274,10 @@ security (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>security</code></em> = <code class="literal">DOMAIN</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560716"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560569"></a>
 
 server schannel (G)
-</h3></div></div></div><a class="indexterm" name="id2560717"></a><a name="SERVERSCHANNEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2560570"></a><a name="SERVERSCHANNEL"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This controls whether the server offers or even demands the use of the netlogon schannel.
 	<a class="link" href="smb.conf.5.html#SERVERSCHANNEL" target="_top">server schannel = no</a> does not offer the schannel, <a class="link" href="smb.conf.5.html#SERVERSCHANNEL" target="_top">server schannel = auto</a> offers the schannel but does not enforce it, and <a class="link" href="smb.conf.5.html#SERVERSCHANNEL" target="_top">server schannel = yes</a> denies access if the client is not able to speak netlogon schannel.
 	This is only the case for Windows NT4 before SP4.
@@ -5397,20 +5288,20 @@ server schannel (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>server schannel</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560832"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560685"></a>
 
 server signing (G)
-</h3></div></div></div><a class="indexterm" name="id2560833"></a><a name="SERVERSIGNING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether the client is allowed or required to use SMB signing. Possible values 
+</h3></div></div></div><a class="indexterm" name="id2560686"></a><a name="SERVERSIGNING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls whether the client is allowed or required to use SMB signing. Possible values 
     are <span class="emphasis"><em>auto</em></span>, <span class="emphasis"><em>mandatory</em></span> 
     and <span class="emphasis"><em>disabled</em></span>. 
     </p><p>When set to auto, SMB signing is offered, but not enforced. 
     When set to mandatory, SMB signing is required and if set 
 	to disabled, SMB signing is not offered either.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>server signing</code></em> = <code class="literal">Disabled</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560893"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560746"></a>
 
 server string (G)
-</h3></div></div></div><a class="indexterm" name="id2560894"></a><a name="SERVERSTRING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what string will show up in the printer comment box in print 
+</h3></div></div></div><a class="indexterm" name="id2560747"></a><a name="SERVERSTRING"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what string will show up in the printer comment box in print 
         manager and next to the IPC connection in <code class="literal">net view</code>. It 
         can be any string that you wish to show to your users.</p><p>It also sets what will appear in browse lists next 
 	to the machine name.</p><p>A <em class="parameter"><code>%v</code></em> will be replaced with the Samba 
@@ -5419,10 +5310,10 @@ server string (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>server string</code></em> = <code class="literal">University of GNUs Samba Server</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560984"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560837"></a>
 
 set directory (S)
-</h3></div></div></div><a class="indexterm" name="id2560985"></a><a name="SETDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2560838"></a><a name="SETDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If <code class="literal">set directory = no</code>, then 	users of the 
 	service may not use the setdir command to change directory.
 	</p><p>
@@ -5431,10 +5322,10 @@ set directory (S)
 	for details.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>set directory</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561044"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560897"></a>
 
 set primary group script (G)
-</h3></div></div></div><a class="indexterm" name="id2561045"></a><a name="SETPRIMARYGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>Thanks to the Posix subsystem in NT a Windows User has a
+</h3></div></div></div><a class="indexterm" name="id2560898"></a><a name="SETPRIMARYGROUPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>Thanks to the Posix subsystem in NT a Windows User has a
 	primary group in addition to the auxiliary groups.  This script
 	sets the primary group in the unix userdatase when an
 	administrator sets the primary group from the windows user
@@ -5446,10 +5337,10 @@ set primary group script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>set primary group script</code></em> = <code class="literal">/usr/sbin/usermod -g '%g' '%u'</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561126"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2560979"></a>
 
 set quota command (G)
-</h3></div></div></div><a class="indexterm" name="id2561127"></a><a name="SETQUOTACOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The <code class="literal">set quota command</code> should only be used 
+</h3></div></div></div><a class="indexterm" name="id2560980"></a><a name="SETQUOTACOMMAND"></a><div class="variablelist"><dl><dt></dt><dd><p>The <code class="literal">set quota command</code> should only be used 
 	whenever there is no operating system API available from the OS that 
 	samba can use.</p><p>This option is only available if Samba was configured with the argument <code class="literal">--with-sys-quotas</code> or 
 	on linux when <code class="literal">./configure --with-quotas</code> was used and a working quota api 
@@ -5459,10 +5350,10 @@ set quota command (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>set quota command</code></em> = <code class="literal">/usr/local/sbin/set_quota</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561290"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561142"></a>
 
 share:fake_fscaps (G)
-</h3></div></div></div><a class="indexterm" name="id2561291"></a><a name="SHARE:FAKE_FSCAPS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2561144"></a><a name="SHARE:FAKE_FSCAPS"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is needed to support some special application that makes
 	QFSINFO calls to check whether we set the SPARSE_FILES bit
 	(0x40). If this bit is not set that particular application
@@ -5472,10 +5363,10 @@ share:fake_fscaps (G)
 	decimal values to specify the bitmask you need to fake.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>share:fake_fscaps</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561349"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561202"></a>
 
 share modes (S)
-</h3></div></div></div><a class="indexterm" name="id2561350"></a><a name="SHAREMODES"></a><div class="variablelist"><dl><dt></dt><dd><p>This enables or disables the honoring of
+</h3></div></div></div><a class="indexterm" name="id2561203"></a><a name="SHAREMODES"></a><div class="variablelist"><dl><dt></dt><dd><p>This enables or disables the honoring of
 	the <em class="parameter"><code>share modes</code></em> during a file open. These
 	modes are used by clients to gain exclusive read or write access
 	to a file.</p><p>This is a deprecated option from old versions of
@@ -5487,20 +5378,20 @@ share modes (S)
 	by default.</p><p>You should <span class="emphasis"><em>NEVER</em></span> turn this parameter
 	off as many Windows applications will break if you do so.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>share modes</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561426"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561279"></a>
 
 short preserve case (S)
-</h3></div></div></div><a class="indexterm" name="id2561427"></a><a name="SHORTPRESERVECASE"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2561280"></a><a name="SHORTPRESERVECASE"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter controls if new files which conform to 8.3 syntax, that is all in upper case and of
 	suitable length, are created upper case, or if they are forced to be the <a class="link" href="smb.conf.5.html#DEFAULTCASE" target="_top">default case</a>.
 	This  option can be use with <a class="link" href="smb.conf.5.html#PRESERVECASE" target="_top">preserve case = yes</a> to permit long filenames
 	to retain their case, while short names are lowered.
 	</p><p>See the section on <a class="link" href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>short preserve case</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561505"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561358"></a>
 
 show add printer wizard (G)
-</h3></div></div></div><a class="indexterm" name="id2561506"></a><a name="SHOWADDPRINTERWIZARD"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printing support
+</h3></div></div></div><a class="indexterm" name="id2561359"></a><a name="SHOWADDPRINTERWIZARD"></a><div class="variablelist"><dl><dt></dt><dd><p>With the introduction of MS-RPC based printing support
     for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will 
     appear on Samba hosts in the share listing.  Normally this folder will 
     contain an icon for the MS Add Printer Wizard (APW).  However, it is 
@@ -5518,10 +5409,10 @@ show add printer wizard (G)
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This does not prevent the same user from having 
 		administrative privilege on an individual printer.</p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>show add printer wizard</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561588"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561441"></a>
 
 shutdown script (G)
-</h3></div></div></div><a class="indexterm" name="id2561589"></a><a name="SHUTDOWNSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This a full path name to a script called by 
+</h3></div></div></div><a class="indexterm" name="id2561442"></a><a name="SHUTDOWNSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This a full path name to a script called by 
 	 <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> that should 
 	start a shutdown procedure.</p><p>If the connected user posseses the <code class="constant">SeRemoteShutdownPrivilege</code>,
 	right, this command will be run as root.</p><p>The %z %t %r %f variables are expanded as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><em class="parameter"><code>%z</code></em> will be substituted with the
@@ -5534,23 +5425,22 @@ shutdown script (G)
 			even if applications do not respond for NT.</p></li></ul></div><p>Shutdown script example:
 </p><pre class="programlisting">
 #!/bin/bash
-
-time=$2
-let time="${time} / 60"
-let time="${time} + 1"
+		
+$time=0
+let "time/60"
+let "time++"
 
 /sbin/shutdown $3 $4 +$time $1 &amp;
-
 </pre><p>
         Shutdown does not return so we need to launch it in background.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>shutdown script</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>shutdown script</code></em> = <code class="literal">/usr/local/samba/sbin/shutdown %m %t %r %f</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561742"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561595"></a>
 
 smb encrypt (S)
-</h3></div></div></div><a class="indexterm" name="id2561743"></a><a name="SMBENCRYPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a new feature introduced with Samba 3.2 and above. It is an
+</h3></div></div></div><a class="indexterm" name="id2561596"></a><a name="SMBENCRYPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a new feature introduced with Samba 3.2 and above. It is an
     extension to the SMB/CIFS protocol negotiated as part of the UNIX extensions.
     SMB encryption uses the GSSAPI (SSPI on Windows) ability to encrypt
     and sign every request/response in a SMB protocol stream. When
@@ -5578,10 +5468,10 @@ smb encrypt (S)
     When set to mandatory, SMB encryption is required and if set 
     to disabled, SMB encryption can not be negotiated.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>smb encrypt</code></em> = <code class="literal">auto</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561855"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561701"></a>
 
 smb passwd file (G)
-</h3></div></div></div><a class="indexterm" name="id2561856"></a><a name="SMBPASSWDFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option sets the path to the encrypted smbpasswd file. By
+</h3></div></div></div><a class="indexterm" name="id2561702"></a><a name="SMBPASSWDFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>This option sets the path to the encrypted smbpasswd file. By
     default the path to the smbpasswd file  is compiled into Samba.</p><p>
     An example of use is:
 </p><pre class="programlisting">
@@ -5589,15 +5479,15 @@ smb passwd file = /etc/samba/smbpasswd
 </pre><p>
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>smb passwd file</code></em> = <code class="literal">${prefix}/private/smbpasswd</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561908"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561754"></a>
 
 smb ports (G)
-</h3></div></div></div><a class="indexterm" name="id2561909"></a><a name="SMBPORTS"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies which ports the server should listen on for SMB traffic.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>smb ports</code></em> = <code class="literal">445 139</code>
+</h3></div></div></div><a class="indexterm" name="id2561755"></a><a name="SMBPORTS"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies which ports the server should listen on for SMB traffic.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>smb ports</code></em> = <code class="literal">445 139</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561950"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561796"></a>
 
 socket address (G)
-</h3></div></div></div><a class="indexterm" name="id2561951"></a><a name="SOCKETADDRESS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to control what
+</h3></div></div></div><a class="indexterm" name="id2561797"></a><a name="SOCKETADDRESS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to control what
 	address Samba will listen for connections on. This is used to
 	support multiple virtual interfaces on the one server, each
 	with a different configuration.</p><p>Setting this option should never be necessary on usual Samba
@@ -5606,10 +5496,10 @@ socket address (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>socket address</code></em> = <code class="literal">192.168.2.20</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562020"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2561866"></a>
 
 socket options (G)
-</h3></div></div></div><a class="indexterm" name="id2562021"></a><a name="SOCKETOPTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to set socket options 
+</h3></div></div></div><a class="indexterm" name="id2561867"></a><a name="SOCKETOPTIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option allows you to set socket options 
     to be used when talking with the client.</p><p>Socket options are controls on the networking layer 
     of the operating systems which allow the connection to be 
     tuned.</p><p>This option will typically be used to tune your Samba  server
@@ -5637,17 +5527,17 @@ socket options (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>socket options</code></em> = <code class="literal">IPTOS_LOWDELAY</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562231"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562077"></a>
 
 stat cache (G)
-</h3></div></div></div><a class="indexterm" name="id2562232"></a><a name="STATCACHE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will use a cache in order to 
+</h3></div></div></div><a class="indexterm" name="id2562078"></a><a name="STATCACHE"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will use a cache in order to 
 	speed up case insensitive name mappings. You should never need 
 	to change this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>stat cache</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562282"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562128"></a>
 
 state directory (G)
-</h3></div></div></div><a class="indexterm" name="id2562283"></a><a name="STATEDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>Usually, most of the TDB files are stored in the
+</h3></div></div></div><a class="indexterm" name="id2562129"></a><a name="STATEDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>Usually, most of the TDB files are stored in the
 	<em class="parameter"><code>lock directory</code></em>. Since
 	Samba 3.4.0, it is possible to differentiate between TDB files
 	with persistent data and TDB files with non-persistent data using
@@ -5659,10 +5549,10 @@ state directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>state directory</code></em> = <code class="literal">/var/run/samba/locks/state</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562368"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562214"></a>
 
 store dos attributes (S)
-</h3></div></div></div><a class="indexterm" name="id2562369"></a><a name="STOREDOSATTRIBUTES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2562215"></a><a name="STOREDOSATTRIBUTES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	If this parameter is set Samba attempts to first read DOS attributes (SYSTEM, HIDDEN, ARCHIVE or
 	READ-ONLY) from a filesystem extended attribute, before mapping DOS attributes to UNIX permission bits (such
 	as occurs with <a class="link" href="smb.conf.5.html#MAPHIDDEN" target="_top">map hidden</a> and <a class="link" href="smb.conf.5.html#MAPREADONLY" target="_top">map readonly</a>).  When set, DOS
@@ -5672,19 +5562,12 @@ store dos attributes (S)
 	attribute named "user.DOSATTRIB". This extended attribute is explicitly hidden from smbd clients requesting an
 	EA list. On Linux the filesystem must have been mounted with the mount option user_xattr in order for
 	extended attributes to work, also extended attributes must be compiled into the Linux kernel.
-
-	In Samba 3.5.0 and above the "user.DOSATTRIB" extended attribute has been extended to store
-	the create time for a file as well as the DOS attributes. This is done in a backwards compatible
-	way so files created by Samba 3.5.0 and above can still have the DOS attribute read from this
-	extended attribute by earlier versions of Samba, but they will not be able to read the create
-	time stored there. Storing the create time separately from the normal filesystem meta-data
-	allows Samba to faithfully reproduce NTFS semantics on top of a POSIX filesystem.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>store dos attributes</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562498"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562335"></a>
 
 strict allocate (S)
-</h3></div></div></div><a class="indexterm" name="id2562499"></a><a name="STRICTALLOCATE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean that controls the handling of 
+</h3></div></div></div><a class="indexterm" name="id2562336"></a><a name="STRICTALLOCATE"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean that controls the handling of 
     disk space allocation in the server. When this is set to <code class="constant">yes</code> 
     the server will change from UNIX behaviour of not committing real
     disk storage blocks when a file is extended to the Windows behaviour
@@ -5696,10 +5579,10 @@ strict allocate (S)
     out of quota messages on systems that are restricting the disk quota
     of users.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>strict allocate</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562568"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562405"></a>
 
 strict locking (S)
-</h3></div></div></div><a class="indexterm" name="id2562570"></a><a name="STRICTLOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2562406"></a><a name="STRICTLOCKING"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is an enumerated type that controls the handling of file locking in the server. When this is set to <code class="constant">yes</code>,
 	the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on 
 	some systems.
@@ -5715,10 +5598,10 @@ strict locking (S)
 	 <code class="literal">strict locking = no</code> is acceptable.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>strict locking</code></em> = <code class="literal">Auto</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562648"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562485"></a>
 
 strict sync (S)
-</h3></div></div></div><a class="indexterm" name="id2562649"></a><a name="STRICTSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>Many Windows applications (including the Windows 98 explorer
+</h3></div></div></div><a class="indexterm" name="id2562486"></a><a name="STRICTSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>Many Windows applications (including the Windows 98 explorer
     shell) seem to confuse flushing buffer contents to disk with doing
     a sync to disk. Under UNIX, a sync call forces the process to be
     suspended until the kernel has ensured that all outstanding data in
@@ -5732,10 +5615,10 @@ strict sync (S)
     addition, this fixes many performance problems that people have
     reported with the new Windows98 explorer shell file copies.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>strict sync</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562713"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562550"></a>
 
 svcctl list (G)
-</h3></div></div></div><a class="indexterm" name="id2562714"></a><a name="SVCCTLLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This option defines a list of init scripts that smbd
+</h3></div></div></div><a class="indexterm" name="id2562551"></a><a name="SVCCTLLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This option defines a list of init scripts that smbd
     will use for starting and stopping Unix services via the Win32 
     ServiceControl API.  This allows Windows administrators to 
     utilize the MS Management Console plug-ins to manage a 
@@ -5748,10 +5631,10 @@ svcctl list (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>svcctl list</code></em> = <code class="literal">cups postfix portmap httpd</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562799"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562635"></a>
 
 sync always (S)
-</h3></div></div></div><a class="indexterm" name="id2562800"></a><a name="SYNCALWAYS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean parameter that controls 
+</h3></div></div></div><a class="indexterm" name="id2562636"></a><a name="SYNCALWAYS"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean parameter that controls 
     whether writes will always be written to stable storage before 
     the write call returns. If this is <code class="constant">no</code> then the server will be 
     guided by the client's request in each write call (clients can 
@@ -5762,19 +5645,19 @@ sync always (S)
     <code class="constant">yes</code> in order for this parameter to have 
     any effect.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>sync always</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562871"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562707"></a>
 
 syslog only (G)
-</h3></div></div></div><a class="indexterm" name="id2562872"></a><a name="SYSLOGONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2562708"></a><a name="SYSLOGONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
     If this parameter is set then Samba debug messages are logged into the system 
     syslog only, and not to the debug log files. There still will be some
 	logging to log.[sn]mbd even if <span class="emphasis"><em>syslog only</em></span> is enabled.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>syslog only</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562918"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562754"></a>
 
 syslog (G)
-</h3></div></div></div><a class="indexterm" name="id2562919"></a><a name="SYSLOG"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2562756"></a><a name="SYSLOG"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This parameter maps how Samba debug messages are logged onto the system syslog logging levels. 
     Samba debug level zero maps onto syslog <code class="constant">LOG_ERR</code>, debug level one maps onto 
     <code class="constant">LOG_WARNING</code>, debug level two maps onto <code class="constant">LOG_NOTICE</code>,
@@ -5785,10 +5668,10 @@ syslog (G)
     logging to log.[sn]mbd even if <span class="emphasis"><em>syslog only</em></span> is enabled.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>syslog</code></em> = <code class="literal">1</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562989"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562825"></a>
 
 template homedir (G)
-</h3></div></div></div><a class="indexterm" name="id2562990"></a><a name="TEMPLATEHOMEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>When filling out the user information for a Windows NT 
+</h3></div></div></div><a class="indexterm" name="id2562826"></a><a name="TEMPLATEHOMEDIR"></a><div class="variablelist"><dl><dt></dt><dd><p>When filling out the user information for a Windows NT 
 	user, the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon  uses this
 	parameter to fill in the home directory for that user. If the
 	string <em class="parameter"><code>%D</code></em> is present it
@@ -5796,31 +5679,31 @@ template homedir (G)
 	string <em class="parameter"><code>%U</code></em> is present it
 	is substituted with the user's Windows  NT user name.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>template homedir</code></em> = <code class="literal">/home/%D/%U</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563054"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562891"></a>
 
 template shell (G)
-</h3></div></div></div><a class="indexterm" name="id2563055"></a><a name="TEMPLATESHELL"></a><div class="variablelist"><dl><dt></dt><dd><p>When filling out the user information for a Windows NT 
+</h3></div></div></div><a class="indexterm" name="id2562892"></a><a name="TEMPLATESHELL"></a><div class="variablelist"><dl><dt></dt><dd><p>When filling out the user information for a Windows NT 
 	user, the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon uses this
-	parameter to fill in the login shell for that user.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563094"></a>
+	parameter to fill in the login shell for that user.</p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562930"></a>
 
 time offset (G)
-</h3></div></div></div><a class="indexterm" name="id2563095"></a><a name="TIMEOFFSET"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a setting in minutes to add 
+</h3></div></div></div><a class="indexterm" name="id2562931"></a><a name="TIMEOFFSET"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a setting in minutes to add 
 	to the normal GMT to local time conversion. This is useful if 
 	you are serving a lot of PCs that have incorrect daylight 
 	saving time handling.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>time offset</code></em> = <code class="literal">0</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>time offset</code></em> = <code class="literal">60</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563154"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562990"></a>
 
 time server (G)
-</h3></div></div></div><a class="indexterm" name="id2563155"></a><a name="TIMESERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> advertises itself as a time server to Windows 
+</h3></div></div></div><a class="indexterm" name="id2562991"></a><a name="TIMESERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter determines if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> advertises itself as a time server to Windows 
 clients.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>time server</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563204"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563040"></a>
 
 unix charset (G)
-</h3></div></div></div><a class="indexterm" name="id2563205"></a><a name="UNIXCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the charset the unix machine 
+</h3></div></div></div><a class="indexterm" name="id2563041"></a><a name="UNIXCHARSET"></a><div class="variablelist"><dl><dt></dt><dd><p>Specifies the charset the unix machine 
 		Samba runs on uses. Samba needs to know this in order to be able to 
 		convert text to the charsets other SMB clients use.
 	</p><p>This is also the charset Samba will use when specifying arguments 
@@ -5829,10 +5712,10 @@ unix charset (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>unix charset</code></em> = <code class="literal">ASCII</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563270"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563106"></a>
 
 unix extensions (G)
-</h3></div></div></div><a class="indexterm" name="id2563271"></a><a name="UNIXEXTENSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether Samba
+</h3></div></div></div><a class="indexterm" name="id2563107"></a><a name="UNIXEXTENSIONS"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether Samba
     implements the CIFS UNIX extensions, as defined by HP.
     These extensions enable Samba to better serve UNIX CIFS clients
     by supporting features such as symbolic links, hard links, etc...
@@ -5842,10 +5725,10 @@ unix extensions (G)
     parameter will automatically be disabled.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>unix extensions</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563335"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563171"></a>
 
 unix password sync (G)
-</h3></div></div></div><a class="indexterm" name="id2563336"></a><a name="UNIXPASSWORDSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether Samba 
+</h3></div></div></div><a class="indexterm" name="id2563172"></a><a name="UNIXPASSWORDSYNC"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean parameter controls whether Samba 
     attempts to synchronize the UNIX password with the SMB password 
     when the encrypted SMB password in the smbpasswd file is changed. 
     If this is set to <code class="constant">yes</code> the program specified in the <em class="parameter"><code>passwd
@@ -5854,10 +5737,10 @@ unix password sync (G)
     old UNIX password (as the SMB password change code has no 
 	access to the old password cleartext, only the new).</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>unix password sync</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563396"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563232"></a>
 
 update encrypted (G)
-</h3></div></div></div><a class="indexterm" name="id2563397"></a><a name="UPDATEENCRYPTED"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2563233"></a><a name="UPDATEENCRYPTED"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed)
 	password in the smbpasswd file to be updated automatically as they log on. This option allows a site to
 	migrate from plaintext password authentication (users authenticate with plaintext password over the
@@ -5875,10 +5758,10 @@ update encrypted (G)
 	passwords.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>update encrypted</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563527"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563350"></a>
 
 use client driver (S)
-</h3></div></div></div><a class="indexterm" name="id2563528"></a><a name="USECLIENTDRIVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter applies only to Windows NT/2000
+</h3></div></div></div><a class="indexterm" name="id2563351"></a><a name="USECLIENTDRIVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter applies only to Windows NT/2000
     clients.  It has no effect on Windows 95/98/ME clients.  When 
     serving a printer to Windows NT/2000 clients without first installing
     a valid printer driver on the Samba host, the client will be required
@@ -5903,10 +5786,10 @@ use client driver (S)
     on a print share which has valid print driver installed on the Samba 
 	server.</em></span></p><p>Default: <span class="emphasis"><em><em class="parameter"><code>use client driver</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563608"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563431"></a>
 
 use mmap (G)
-</h3></div></div></div><a class="indexterm" name="id2563609"></a><a name="USEMMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>This global parameter determines if the tdb internals of Samba can
+</h3></div></div></div><a class="indexterm" name="id2563432"></a><a name="USEMMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>This global parameter determines if the tdb internals of Samba can
     depend on mmap working correctly on the running system. Samba requires a coherent
     mmap/read-write system memory cache. Currently only HPUX does not have such a
     coherent cache, and so this parameter is set to <code class="constant">no</code> by
@@ -5915,10 +5798,10 @@ use mmap (G)
     the tdb internal code.
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>use mmap</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563660"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563483"></a>
 
 username level (G)
-</h3></div></div></div><a class="indexterm" name="id2563661"></a><a name="USERNAMELEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option helps Samba to try and 'guess' at 
+</h3></div></div></div><a class="indexterm" name="id2563484"></a><a name="USERNAMELEVEL"></a><div class="variablelist"><dl><dt></dt><dd><p>This option helps Samba to try and 'guess' at 
     the real UNIX username, as many DOS clients send an all-uppercase 
     username. By default Samba tries all lowercase, followed by the 
     username with the first letter capitalized, and fails if the 
@@ -5933,10 +5816,10 @@ username level (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>username level</code></em> = <code class="literal">5</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563742"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563565"></a>
 
 username map script (G)
-</h3></div></div></div><a class="indexterm" name="id2563743"></a><a name="USERNAMEMAPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This script is a mutually exclusive alternative to the 
+</h3></div></div></div><a class="indexterm" name="id2563566"></a><a name="USERNAMEMAPSCRIPT"></a><div class="variablelist"><dl><dt></dt><dd><p>This script is a mutually exclusive alternative to the 
 	<a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map</a> parameter.  This parameter 
 	specifies and external program or script that must accept a single 
 	command line option (the username transmitted in the authentication
@@ -5947,10 +5830,10 @@ username map script (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>username map script</code></em> = <code class="literal">/etc/samba/scripts/mapusers.sh</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563818"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563642"></a>
 
 username map (G)
-</h3></div></div></div><a class="indexterm" name="id2563820"></a><a name="USERNAMEMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2563643"></a><a name="USERNAMEMAP"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This option allows you to specify a file containing a mapping of usernames from the clients to the server.
 	This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows
 	machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they
@@ -6034,16 +5917,16 @@ username map = /usr/local/samba/lib/users.map
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>username map</code></em> = <code class="literal">
 # no username map</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564098"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563921"></a>
 
 <a name="USER"></a>user
-</h3></div></div></div><a class="indexterm" name="id2564099"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#USERNAME">username</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564130"></a>
+</h3></div></div></div><a class="indexterm" name="id2563922"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#USERNAME">username</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563953"></a>
 
 <a name="USERS"></a>users
-</h3></div></div></div><a class="indexterm" name="id2564131"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#USERNAME">username</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564162"></a>
+</h3></div></div></div><a class="indexterm" name="id2563954"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#USERNAME">username</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563985"></a>
 
 username (S)
-</h3></div></div></div><a class="indexterm" name="id2564163"></a><a name="USERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>Multiple users may be specified in a comma-delimited 
+</h3></div></div></div><a class="indexterm" name="id2563986"></a><a name="USERNAME"></a><div class="variablelist"><dl><dt></dt><dd><p>Multiple users may be specified in a comma-delimited 
     list, in which case the supplied password will be tested against 
     each username in turn (left to right).</p><p>The <em class="parameter"><code>username</code></em> line is needed only when 
     the PC is unable to supply its own username. This is the case 
@@ -6081,28 +5964,28 @@ username (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>username</code></em> = <code class="literal">fred, mary, jack, jane, @users, @pcgroup</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564332"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564155"></a>
 
 usershare allow guests (G)
-</h3></div></div></div><a class="indexterm" name="id2564333"></a><a name="USERSHAREALLOWGUESTS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether user defined shares are allowed
+</h3></div></div></div><a class="indexterm" name="id2564156"></a><a name="USERSHAREALLOWGUESTS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether user defined shares are allowed
 	to be accessed by non-authenticated users or not. It is the equivalent
 	of allowing people who can create a share the option of setting
 	<em class="parameter"><code>guest ok = yes</code></em> in a share
 	definition. Due to its security sensitive nature, the default
 	is set to off.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>usershare allow guests</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564385"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564208"></a>
 
 usershare max shares (G)
-</h3></div></div></div><a class="indexterm" name="id2564386"></a><a name="USERSHAREMAXSHARES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of user defined shares
+</h3></div></div></div><a class="indexterm" name="id2564209"></a><a name="USERSHAREMAXSHARES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of user defined shares
 	that are allowed to be created by users belonging to the group owning the
 	usershare directory. If set to zero (the default) user defined shares are ignored.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>usershare max shares</code></em> = <code class="literal">0</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564430"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564253"></a>
 
 usershare owner only (G)
-</h3></div></div></div><a class="indexterm" name="id2564431"></a><a name="USERSHAREOWNERONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether the pathname exported by
+</h3></div></div></div><a class="indexterm" name="id2564254"></a><a name="USERSHAREOWNERONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether the pathname exported by
 	a user defined shares must be owned by the user creating the
 	user defined share or not. If set to True (the default) then
 	smbd checks that the directory path being shared is owned by
@@ -6112,10 +5995,10 @@ usershare owner only (G)
 	regardless of who owns it.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>usershare owner only</code></em> = <code class="literal">True</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564480"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564303"></a>
 
 usershare path (G)
-</h3></div></div></div><a class="indexterm" name="id2564481"></a><a name="USERSHAREPATH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the absolute path of the directory on the
+</h3></div></div></div><a class="indexterm" name="id2564304"></a><a name="USERSHAREPATH"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the absolute path of the directory on the
 	filesystem used to store the user defined share definition files.
 	This directory must be owned by root, and have no access for
 	other, and be writable only by the group owner. In addition the
@@ -6136,10 +6019,10 @@ usershare path (G)
 	In this case, only members of the group "power_users" can create user defined shares.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>usershare path</code></em> = <code class="literal">NULL</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564551"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564374"></a>
 
 usershare prefix allow list (G)
-</h3></div></div></div><a class="indexterm" name="id2564552"></a><a name="USERSHAREPREFIXALLOWLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a list of absolute pathnames
+</h3></div></div></div><a class="indexterm" name="id2564375"></a><a name="USERSHAREPREFIXALLOWLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a list of absolute pathnames
 	the root of which are allowed to be exported by user defined share definitions.
 	If the pathname to be exported doesn't start with one of the strings in this
 	list, the user defined share will not be allowed. This allows the Samba
@@ -6154,10 +6037,10 @@ usershare prefix allow list (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>usershare prefix allow list</code></em> = <code class="literal">/home /data /space</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564630"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564447"></a>
 
 usershare prefix deny list (G)
-</h3></div></div></div><a class="indexterm" name="id2564631"></a><a name="USERSHAREPREFIXDENYLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a list of absolute pathnames
+</h3></div></div></div><a class="indexterm" name="id2564448"></a><a name="USERSHAREPREFIXDENYLIST"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies a list of absolute pathnames
 	the root of which are NOT allowed to be exported by user defined share definitions.
 	If the pathname exported starts with one of the strings in this
 	list the user defined share will not be allowed. Any pathname not
@@ -6173,10 +6056,10 @@ usershare prefix deny list (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>usershare prefix deny list</code></em> = <code class="literal">/etc /dev /private</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564704"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564521"></a>
 
 usershare template share (G)
-</h3></div></div></div><a class="indexterm" name="id2564706"></a><a name="USERSHARETEMPLATESHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>User defined shares only have limited possible parameters
+</h3></div></div></div><a class="indexterm" name="id2564522"></a><a name="USERSHARETEMPLATESHARE"></a><div class="variablelist"><dl><dt></dt><dd><p>User defined shares only have limited possible parameters
 	such as path, guest ok, etc. This parameter allows usershares to
 	"cloned" from an existing share. If "usershare template share"
 	is set to the name of an existing share, then all usershares
@@ -6191,10 +6074,10 @@ usershare template share (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>usershare template share</code></em> = <code class="literal">template_share</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564778"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564594"></a>
 
 use sendfile (S)
-</h3></div></div></div><a class="indexterm" name="id2564779"></a><a name="USESENDFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code>, and the <code class="constant">sendfile()</code> 
+</h3></div></div></div><a class="indexterm" name="id2564595"></a><a name="USESENDFILE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this parameter is <code class="constant">yes</code>, and the <code class="constant">sendfile()</code> 
     system call is supported by the underlying operating system, then some SMB read calls 
     (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that
     are exclusively oplocked. This may make more efficient use of the system CPU's
@@ -6203,10 +6086,10 @@ use sendfile (S)
     Windows 9x (using sendfile from Linux will cause these clients to fail).
     </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>use sendfile</code></em> = <code class="literal">false</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564835"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564652"></a>
 
 use spnego (G)
-</h3></div></div></div><a class="indexterm" name="id2564836"></a><a name="USESPNEGO"></a><div class="variablelist"><dl><dt></dt><dd><p>This variable controls controls whether samba will try 
+</h3></div></div></div><a class="indexterm" name="id2564653"></a><a name="USESPNEGO"></a><div class="variablelist"><dl><dt></dt><dd><p>This variable controls controls whether samba will try 
     to use Simple and Protected NEGOciation (as specified by rfc2478) with 
     WindowsXP and Windows2000 clients to agree upon an authentication mechanism. 
 </p><p>
@@ -6214,10 +6097,10 @@ use spnego (G)
     implementation, there is no reason this should ever be
 	disabled.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>use spnego</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564885"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564701"></a>
 
 utmp directory (G)
-</h3></div></div></div><a class="indexterm" name="id2564886"></a><a name="UTMPDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only available if Samba has 
+</h3></div></div></div><a class="indexterm" name="id2564702"></a><a name="UTMPDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is only available if Samba has 
 	been configured and compiled with the option <code class="literal">
 	--with-utmp</code>. It specifies a directory pathname that is
 	used to store the utmp or utmpx files (depending on the UNIX system) that
@@ -6229,10 +6112,10 @@ utmp directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>utmp directory</code></em> = <code class="literal">/var/run/utmp</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564963"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564779"></a>
 
 utmp (G)
-</h3></div></div></div><a class="indexterm" name="id2564964"></a><a name="UTMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2564780"></a><a name="UTMP"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This boolean parameter is only available if Samba has been configured and compiled  
 	with the option <code class="literal">--with-utmp</code>. If set to 
 	 <code class="constant">yes</code> then Samba will attempt to add utmp or utmpx records 
@@ -6244,10 +6127,10 @@ utmp (G)
 	to find this number.  This may impede performance on large installations. 
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>utmp</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565025"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564842"></a>
 
 valid users (S)
-</h3></div></div></div><a class="indexterm" name="id2565026"></a><a name="VALIDUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2564843"></a><a name="VALIDUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This is a list of users that should be allowed to login to this service. Names starting with 
     '@', '+' and  '&amp;' are interpreted using the same rules as described in the 
     <em class="parameter"><code>invalid users</code></em> parameter.
@@ -6263,10 +6146,10 @@ valid users (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>valid users</code></em> = <code class="literal">greg, @pcusers</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565117"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564933"></a>
 
 -valid (S)
-</h3></div></div></div><a class="indexterm" name="id2565118"></a><a name="-VALID"></a><div class="variablelist"><dl><dt></dt><dd><p> This parameter indicates whether a share is 
+</h3></div></div></div><a class="indexterm" name="id2564934"></a><a name="-VALID"></a><div class="variablelist"><dl><dt></dt><dd><p> This parameter indicates whether a share is 
 	valid and thus can be used. When this parameter is set to false, 
 	the share will be in no way visible nor accessible.
 	</p><p>
@@ -6275,10 +6158,10 @@ valid users (S)
 	Samba uses this option internally to mark shares as deleted.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>-valid</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565166"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564983"></a>
 
 veto files (S)
-</h3></div></div></div><a class="indexterm" name="id2565167"></a><a name="VETOFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2564984"></a><a name="VETOFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This is a list of files and directories that are neither visible nor accessible.  Each entry in 
 	the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' 
 	can be used to specify multiple files or directories as in DOS wildcards.
@@ -6309,10 +6192,10 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
 </pre><p>
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>veto files</code></em> = <code class="literal">No files or directories are vetoed.</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565285"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565102"></a>
 
 veto oplock files (S)
-</h3></div></div></div><a class="indexterm" name="id2565286"></a><a name="VETOOPLOCKFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2565103"></a><a name="VETOOPLOCKFILES"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter is only valid when the <a class="link" href="smb.conf.5.html#OPLOCKS" target="_top">oplocks</a>
 	parameter is turned on for a share. It allows the Samba administrator
 	to selectively turn off the granting of oplocks on selected files that
@@ -6333,31 +6216,31 @@ veto oplock files = /.*SEM/
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>veto oplock files</code></em> = <code class="literal">
 # No files are vetoed for oplock grants</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565378"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565195"></a>
 
 <a name="VFSOBJECT"></a>vfs object
-</h3></div></div></div><a class="indexterm" name="id2565379"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#VFSOBJECTS">vfs objects</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565410"></a>
+</h3></div></div></div><a class="indexterm" name="id2565196"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#VFSOBJECTS">vfs objects</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565227"></a>
 
 vfs objects (S)
-</h3></div></div></div><a class="indexterm" name="id2565411"></a><a name="VFSOBJECTS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the backend names which 
+</h3></div></div></div><a class="indexterm" name="id2565228"></a><a name="VFSOBJECTS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the backend names which 
 	are used for Samba VFS I/O operations.  By default, normal 
 	disk I/O operations are used but these can be overloaded 
 	with one or more VFS objects. </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>vfs objects</code></em> = <code class="literal"></code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>vfs objects</code></em> = <code class="literal">extd_audit recycle</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565470"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565287"></a>
 
 volume (S)
-</h3></div></div></div><a class="indexterm" name="id2565471"></a><a name="VOLUME"></a><div class="variablelist"><dl><dt></dt><dd><p>This allows you to override the volume label 
+</h3></div></div></div><a class="indexterm" name="id2565288"></a><a name="VOLUME"></a><div class="variablelist"><dl><dt></dt><dd><p>This allows you to override the volume label 
 	returned for a share. Useful for CDROMs with installation programs 
 	that insist on a particular volume label.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>volume</code></em> = <code class="literal">
 # the name of the share</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565514"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565330"></a>
 
 wide links (S)
-</h3></div></div></div><a class="indexterm" name="id2565515"></a><a name="WIDELINKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not links 
+</h3></div></div></div><a class="indexterm" name="id2565332"></a><a name="WIDELINKS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not links 
 	in the UNIX file system may be followed by the server. Links 
 	that point to areas within the directory tree exported by the 
 	server are always allowed; this parameter controls access only 
@@ -6370,10 +6253,10 @@ wide links (S)
 	<a class="link" href="smb.conf.5.html#UNIXEXTENSIONS" target="_top">unix extensions</a> option is on.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>wide links</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565582"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565399"></a>
 
 winbind cache time (G)
-</h3></div></div></div><a class="indexterm" name="id2565583"></a><a name="WINBINDCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of 
+</h3></div></div></div><a class="indexterm" name="id2565400"></a><a name="WINBINDCACHETIME"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of 
 	seconds the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon will cache 
 	user and group information before querying a Windows NT server 
 	again.</p><p>
@@ -6381,10 +6264,10 @@ winbind cache time (G)
 	evaluated in real time unless the <a class="link" href="smb.conf.5.html#WINBINDOFFLINELOGON" target="_top">winbind   offline logon</a> option has been enabled.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind cache time</code></em> = <code class="literal">300</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565653"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565470"></a>
 
 winbind enum groups (G)
-</h3></div></div></div><a class="indexterm" name="id2565654"></a><a name="WINBINDENUMGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>On large installations using <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> it may be necessary to suppress 
+</h3></div></div></div><a class="indexterm" name="id2565471"></a><a name="WINBINDENUMGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>On large installations using <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> it may be necessary to suppress 
 	the enumeration of groups through the <code class="literal">setgrent()</code>,
 	<code class="literal">getgrent()</code> and
 	<code class="literal">endgrent()</code> group of system calls.  If
@@ -6392,10 +6275,10 @@ winbind enum groups (G)
 	<code class="constant">no</code>, calls to the <code class="literal">getgrent()</code> system
 	call will not return any data. </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Turning off group enumeration may cause some programs to behave oddly.  </p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind enum groups</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565744"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565560"></a>
 
 winbind enum users (G)
-</h3></div></div></div><a class="indexterm" name="id2565745"></a><a name="WINBINDENUMUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>On large installations using <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> it may be
+</h3></div></div></div><a class="indexterm" name="id2565561"></a><a name="WINBINDENUMUSERS"></a><div class="variablelist"><dl><dt></dt><dd><p>On large installations using <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> it may be
 	necessary to suppress the enumeration of users through the <code class="literal">setpwent()</code>,
 	 <code class="literal">getpwent()</code> and
 	 <code class="literal">endpwent()</code> group of system calls.  If
@@ -6407,10 +6290,10 @@ winbind enum users (G)
 	full user list when searching for matching
 	usernames. </p></div><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind enum users</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565837"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565654"></a>
 
 winbind expand groups (G)
-</h3></div></div></div><a class="indexterm" name="id2565838"></a><a name="WINBINDEXPANDGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum depth that winbindd
+</h3></div></div></div><a class="indexterm" name="id2565655"></a><a name="WINBINDEXPANDGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>This option controls the maximum depth that winbindd
               will traverse when flattening nested group memberships
 	      of Windows domain groups.  This is different from the
 	      <a class="link" href="smb.conf.5.html#WINBINDNESTEDGROUPS" target="_top">winbind nested groups</a> option
@@ -6422,10 +6305,10 @@ winbind expand groups (G)
 	 must perform the group unrolling and will be unable to answer
 	 incoming NSS or authentication requests during this time.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind expand groups</code></em> = <code class="literal">1</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565906"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565722"></a>
 
 winbind nested groups (G)
-</h3></div></div></div><a class="indexterm" name="id2565907"></a><a name="WINBINDNESTEDGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>If set to yes, this parameter activates the support for nested
+</h3></div></div></div><a class="indexterm" name="id2565723"></a><a name="WINBINDNESTEDGROUPS"></a><div class="variablelist"><dl><dt></dt><dd><p>If set to yes, this parameter activates the support for nested
                  groups. Nested groups are also called local groups or
                  aliases. They work like their counterparts in Windows: Nested
                  groups are defined locally on any machine (they are shared
@@ -6433,10 +6316,10 @@ winbind nested groups (G)
                  global groups from any trusted SAM. To be able to use nested
                  groups, you need to run nss_winbind.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind nested groups</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565956"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565773"></a>
 
 winbind normalize names (G)
-</h3></div></div></div><a class="indexterm" name="id2565957"></a><a name="WINBINDNORMALIZENAMES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether winbindd will replace
+</h3></div></div></div><a class="indexterm" name="id2565774"></a><a name="WINBINDNORMALIZENAMES"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether winbindd will replace
 	  whitespace in user and group names with an underscore (_) character.
 	  For example, whether the name "Space Kadet" should be
 	  replaced with the string "space_kadet".
@@ -6456,10 +6339,10 @@ winbind normalize names (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind normalize names</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566034"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565850"></a>
 
 winbind nss info (G)
-</h3></div></div></div><a class="indexterm" name="id2566035"></a><a name="WINBINDNSSINFO"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control how Winbind retrieves Name
+</h3></div></div></div><a class="indexterm" name="id2565852"></a><a name="WINBINDNSSINFO"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control how Winbind retrieves Name
 	Service Information to construct a user's home directory and login shell. 
 	Currently the following settings are available: 
 
@@ -6481,10 +6364,10 @@ winbind nss info (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind nss info</code></em> = <code class="literal">template sfu</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566154"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565970"></a>
 
 winbind offline logon (G)
-</h3></div></div></div><a class="indexterm" name="id2566155"></a><a name="WINBINDOFFLINELOGON"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control whether Winbind should
+</h3></div></div></div><a class="indexterm" name="id2565971"></a><a name="WINBINDOFFLINELOGON"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control whether Winbind should
 	allow to login with the <em class="parameter"><code>pam_winbind</code></em> 
 	module using Cached Credentials. If enabled, winbindd will store user credentials
 	from successful logins encrypted in a local cache.
@@ -6492,37 +6375,37 @@ winbind offline logon (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind offline logon</code></em> = <code class="literal">true</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566223"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566039"></a>
 
 winbind reconnect delay (G)
-</h3></div></div></div><a class="indexterm" name="id2566224"></a><a name="WINBINDRECONNECTDELAY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of
+</h3></div></div></div><a class="indexterm" name="id2566040"></a><a name="WINBINDRECONNECTDELAY"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies the number of
 	seconds the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon will wait between
 	attempts to contact a Domain controller for a domain that is
 	determined to be down or not contactable.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind reconnect delay</code></em> = <code class="literal">30</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566276"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566092"></a>
 
 winbind refresh tickets (G)
-</h3></div></div></div><a class="indexterm" name="id2566277"></a><a name="WINBINDREFRESHTICKETS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control whether Winbind should refresh Kerberos Tickets
+</h3></div></div></div><a class="indexterm" name="id2566093"></a><a name="WINBINDREFRESHTICKETS"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is designed to control whether Winbind should refresh Kerberos Tickets
 	retrieved using the <em class="parameter"><code>pam_winbind</code></em> module.
 
 </p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind refresh tickets</code></em> = <code class="literal">false</code>
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind refresh tickets</code></em> = <code class="literal">true</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566343"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566159"></a>
 
 winbind rpc only (G)
-</h3></div></div></div><a class="indexterm" name="id2566344"></a><a name="WINBINDRPCONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2566160"></a><a name="WINBINDRPCONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	Setting this parameter to <code class="literal">yes</code> forces 
 	winbindd to use RPC instead of LDAP to retrieve information from Domain
         Controllers.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind rpc only</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566392"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566208"></a>
 
 winbind separator (G)
-</h3></div></div></div><a class="indexterm" name="id2566393"></a><a name="WINBINDSEPARATOR"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows an admin to define the character 
+</h3></div></div></div><a class="indexterm" name="id2566209"></a><a name="WINBINDSEPARATOR"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter allows an admin to define the character 
 	used when listing a username of the form of <em class="replaceable"><code>DOMAIN
 	</code></em>\<em class="replaceable"><code>user</code></em>.  This parameter 
 	is only applicable when using the <code class="filename">pam_winbind.so</code>
@@ -6533,10 +6416,10 @@ winbind separator (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind separator</code></em> = <code class="literal">+</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566479"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566296"></a>
 
 winbind trusted domains only (G)
-</h3></div></div></div><a class="indexterm" name="id2566480"></a><a name="WINBINDTRUSTEDDOMAINSONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2566297"></a><a name="WINBINDTRUSTEDDOMAINSONLY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter is designed to allow Samba servers that are members 
 	of a Samba controlled domain to use UNIX accounts distributed via NIS, 
 	rsync, or LDAP as the uid's for winbindd users in the hosts primary domain.
@@ -6547,10 +6430,10 @@ winbind trusted domains only (G)
 	Refer to the <a class="citerefentry" href="idmap_nss.8.html"><span class="citerefentry"><span class="refentrytitle">idmap_nss</span>(8)</span></a> man page for more information.
 	</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>winbind trusted domains only</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566546"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566363"></a>
 
 winbind use default domain (G)
-</h3></div></div></div><a class="indexterm" name="id2566547"></a><a name="WINBINDUSEDEFAULTDOMAIN"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether the
+</h3></div></div></div><a class="indexterm" name="id2566364"></a><a name="WINBINDUSEDEFAULTDOMAIN"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter specifies whether the
 	 <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon should operate on users  
 	without domain component in their username. Users without a domain
 	component are treated as is part of the winbindd server's own
@@ -6560,10 +6443,10 @@ winbind use default domain (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>winbind use default domain</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566619"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566435"></a>
 
 wins hook (G)
-</h3></div></div></div><a class="indexterm" name="id2566620"></a><a name="WINSHOOK"></a><div class="variablelist"><dl><dt></dt><dd><p>When Samba is running as a WINS server this 
+</h3></div></div></div><a class="indexterm" name="id2566436"></a><a name="WINSHOOK"></a><div class="variablelist"><dl><dt></dt><dd><p>When Samba is running as a WINS server this 
 	allows you to call an external program for all changes to the 
 	WINS database. The primary use for this option is to allow the 
 	dynamic update of external name resolution databases such as 
@@ -6584,17 +6467,17 @@ wins hook (G)
 			addresses currently registered for that name. If this list is 
 			empty then the name should be deleted.</p></li></ul></div><p>An example script that calls the BIND dynamic DNS update 
 	program <code class="literal">nsupdate</code> is provided in the examples 
-	directory of the Samba source code. </p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566725"></a>
+	directory of the Samba source code. </p><p><span class="emphasis"><em>No default</em></span></p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566542"></a>
 
 wins proxy (G)
-</h3></div></div></div><a class="indexterm" name="id2566726"></a><a name="WINSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean that controls if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will respond to broadcast name 
+</h3></div></div></div><a class="indexterm" name="id2566543"></a><a name="WINSPROXY"></a><div class="variablelist"><dl><dt></dt><dd><p>This is a boolean that controls if <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will respond to broadcast name 
 	queries on behalf of  other hosts. You may need to set this 
 	to <code class="constant">yes</code> for some older clients.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>wins proxy</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566780"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566597"></a>
 
 wins server (G)
-</h3></div></div></div><a class="indexterm" name="id2566781"></a><a name="WINSSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies the IP address (or DNS name: IP 
+</h3></div></div></div><a class="indexterm" name="id2566598"></a><a name="WINSSERVER"></a><div class="variablelist"><dl><dt></dt><dd><p>This specifies the IP address (or DNS name: IP 
 	address for preference) of the WINS server that <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> should register with. If you have a WINS server on 
 	your network then you should set this to the WINS server's IP.</p><p>You should point this at your WINS server if you have a
 	multi-subnetted network.</p><p>If you want to work in multiple namespaces, you can 
@@ -6613,19 +6496,19 @@ wins server (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>wins server</code></em> = <code class="literal">192.9.200.1 192.168.2.61</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566891"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566707"></a>
 
 wins support (G)
-</h3></div></div></div><a class="indexterm" name="id2566892"></a><a name="WINSSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean controls if the <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> process in Samba will act as a WINS server. You should 
+</h3></div></div></div><a class="indexterm" name="id2566708"></a><a name="WINSSUPPORT"></a><div class="variablelist"><dl><dt></dt><dd><p>This boolean controls if the <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> process in Samba will act as a WINS server. You should 
 	not set this to <code class="constant">yes</code> unless you have a multi-subnetted network and 
 	you wish a particular <code class="literal">nmbd</code> to be your WINS server. 
 	Note that you should <span class="emphasis"><em>NEVER</em></span> set this to <code class="constant">yes</code>
 	on more than one machine in your network.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>wins support</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566960"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566776"></a>
 
 workgroup (G)
-</h3></div></div></div><a class="indexterm" name="id2566962"></a><a name="WORKGROUP"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what workgroup your server will 
+</h3></div></div></div><a class="indexterm" name="id2566778"></a><a name="WORKGROUP"></a><div class="variablelist"><dl><dt></dt><dd><p>This controls what workgroup your server will 
 	appear to be in when queried by clients. Note that this parameter 
 	also controls the Domain name used with 
 	the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>
@@ -6633,18 +6516,18 @@ workgroup (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>workgroup</code></em> = <code class="literal">MYGROUP</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567033"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566848"></a>
 
 <a name="WRITABLE"></a>writable
-</h3></div></div></div><a class="indexterm" name="id2567034"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#WRITEABLE">writeable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567064"></a>
+</h3></div></div></div><a class="indexterm" name="id2566849"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter is a synonym for <a class="link" href="#WRITEABLE">writeable</a>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566880"></a>
 
 writeable (S)
-</h3></div></div></div><a class="indexterm" name="id2567065"></a><a name="WRITEABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>Inverted synonym for <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>writeable</code></em> = <code class="literal">no</code>
+</h3></div></div></div><a class="indexterm" name="id2566881"></a><a name="WRITEABLE"></a><div class="variablelist"><dl><dt></dt><dd><p>Inverted synonym for <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only</a>.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>writeable</code></em> = <code class="literal">no</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567115"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566931"></a>
 
 write cache size (S)
-</h3></div></div></div><a class="indexterm" name="id2567116"></a><a name="WRITECACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this integer parameter is set to non-zero value,
+</h3></div></div></div><a class="indexterm" name="id2566932"></a><a name="WRITECACHESIZE"></a><div class="variablelist"><dl><dt></dt><dd><p>If this integer parameter is set to non-zero value,
     Samba will create an in-memory cache for each oplocked file 
     (it does <span class="emphasis"><em>not</em></span> do this for 
     non-oplocked files). All writes that the client does not request 
@@ -6662,10 +6545,10 @@ write cache size (S)
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>write cache size</code></em> = <code class="literal">262144
 #  for a 256k cache size per file</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567199"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567015"></a>
 
 write list (S)
-</h3></div></div></div><a class="indexterm" name="id2567200"></a><a name="WRITELIST"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2567016"></a><a name="WRITELIST"></a><div class="variablelist"><dl><dt></dt><dd><p>
     This is a list of users that are given read-write access to a service. If the 
     connecting user is in this list then they will be given write access, no matter 
     what the <a class="link" href="smb.conf.5.html#READONLY" target="_top">read only</a> option is set to. The list can 
@@ -6680,17 +6563,17 @@ write list (S)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>write list</code></em> = <code class="literal">admin, root, @staff</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567292"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567108"></a>
 
 write raw (G)
-</h3></div></div></div><a class="indexterm" name="id2567293"></a><a name="WRITERAW"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not the server 
+</h3></div></div></div><a class="indexterm" name="id2567109"></a><a name="WRITERAW"></a><div class="variablelist"><dl><dt></dt><dd><p>This parameter controls whether or not the server 
     will support raw write SMB's when transferring data from clients. 
     You should never need to change this parameter.</p><p>Default: <span class="emphasis"><em><em class="parameter"><code>write raw</code></em> = <code class="literal">yes</code>
 </em></span>
-</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567336"></a>
+</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567152"></a>
 
 wtmp directory (G)
-</h3></div></div></div><a class="indexterm" name="id2567337"></a><a name="WTMPDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
+</h3></div></div></div><a class="indexterm" name="id2567153"></a><a name="WTMPDIRECTORY"></a><div class="variablelist"><dl><dt></dt><dd><p>
 	This parameter is only available if Samba has been configured and compiled with the option <code class="literal">
 	--with-utmp</code>. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on 
 	the UNIX system) that record user connections to a Samba server. The difference with the utmp directory is the fact 
@@ -6702,7 +6585,7 @@ wtmp directory (G)
 </em></span>
 </p><p>Example: <span class="emphasis"><em><em class="parameter"><code>wtmp directory</code></em> = <code class="literal">/var/log/wtmp</code>
 </em></span>
-</p></dd></dl></div></div></div></div><div class="refsect1" lang="en"><a name="id2567420"></a><h2>WARNINGS</h2><p>
+</p></dd></dl></div></div></div></div><div class="refsect1" lang="en"><a name="id2567236"></a><h2>WARNINGS</h2><p>
 	Although the configuration file permits service names to contain spaces, your client software may not.
 	Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility.
 	</p><p>
@@ -6715,8 +6598,8 @@ wtmp directory (G)
 	for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme
 	care when designing these sections. In particular, ensure that the permissions on spool directories are
 	correct.
-	</p></div><div class="refsect1" lang="en"><a name="id2567470"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2567481"></a><h2>SEE ALSO</h2><p>
-	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>, <a class="citerefentry" href="swat.8.html"><span class="citerefentry"><span class="refentrytitle">swat</span>(8)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2567560"></a><h2>AUTHOR</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2567286"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2567297"></a><h2>SEE ALSO</h2><p>
+	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>, <a class="citerefentry" href="swat.8.html"><span class="citerefentry"><span class="refentrytitle">swat</span>(8)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2567376"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
 	</p><p>
diff --git a/docs/htmldocs/manpages/smbcacls.1.html b/docs/htmldocs/manpages/smbcacls.1.html
index 75b38772db..54fe6c0eb3 100644
--- a/docs/htmldocs/manpages/smbcacls.1.html
+++ b/docs/htmldocs/manpages/smbcacls.1.html
@@ -1,25 +1,30 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcacls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcacls.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcacls &#8212; Set or get ACLs on an NT file or directory names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcacls</code> {//server/share} {filename} [-D acls] [-M acls] [-a acls] [-S acls] [-C name] [-G name] [--numeric] [-t] [-U username] [-h] [-d]</p></div></div><div class="refsect1" lang="en"><a name="id2483378"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">smbcacls</code> program manipulates NT Access Control
-	Lists (ACLs) on SMB file shares. </p></div><div class="refsect1" lang="en"><a name="id2483530"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">smbcacls</code> program.  
-	The format of ACLs is described in the section ACL FORMAT </p><div class="variablelist"><dl><dt><span class="term">-a|--add acls</span></dt><dd><p>Add the ACLs specified to the ACL list.  Existing 
-		access control entries are unchanged. </p></dd><dt><span class="term">-M|--modify acls</span></dt><dd><p>Modify the mask value (permissions) for the ACLs 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcacls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcacls.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcacls &#8212; Set or get ACLs on an NT file or directory names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcacls</code> {//server/share} {filename} [-D acls] [-M acls] [-a acls] [-S acls] [-C name] [-G name] [--numeric] [-t] [-U username] [-h] [-d]</p></div></div><div class="refsect1" lang="en"><a name="id2483382"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">smbcacls</code> program manipulates NT Access Control
+	Lists (ACLs) on SMB file shares. </p></div><div class="refsect1" lang="en"><a name="id2483531"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">smbcacls</code> program.  
+	The format of ACLs is described in the section ACL FORMAT </p><div class="variablelist"><dl><dt><span class="term">-a acls</span></dt><dd><p>Add the ACLs specified to the ACL list.  Existing 
+		access control entries are unchanged. </p></dd><dt><span class="term">-M acls</span></dt><dd><p>Modify the mask value (permissions) for the ACLs 
 		specified on the command line.  An error will be printed for each 
 		ACL specified that was not already present in the ACL list
-		</p></dd><dt><span class="term">-D|--delete acls</span></dt><dd><p>Delete any ACLs specified on the command line.  
+		</p></dd><dt><span class="term">-D acls</span></dt><dd><p>Delete any ACLs specified on the command line.  
 		An error will be printed for each ACL specified that was not 
-		already present in the ACL list. </p></dd><dt><span class="term">-S|--set acls</span></dt><dd><p>This command sets the ACLs on the file with 
+		already present in the ACL list. </p></dd><dt><span class="term">-S acls</span></dt><dd><p>This command sets the ACLs on the file with 
 		only the ones specified on the command line.  All other ACLs are 
 		erased. Note that the ACL specified must contain at least a revision,
-		type, owner and group for the call to succeed. </p></dd><dt><span class="term">-C|--chown name</span></dt><dd><p>The owner of a file or directory can be changed 
+		type, owner and group for the call to succeed. </p></dd><dt><span class="term">-U username</span></dt><dd><p>Specifies a username used to connect to the 
+		specified service.  The username may be of the form "username" in 
+		which case the user is prompted to enter in a password and the 
+		workgroup specified in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file is 
+		used, or "username%password"  or "DOMAIN\username%password" and the 
+		password and workgroup names are used as provided. </p></dd><dt><span class="term">-C name</span></dt><dd><p>The owner of a file or directory can be changed 
 		to the name given using the <em class="parameter"><code>-C</code></em> option.  
 		The name can be a sid in the form S-1-x-y-z or a name resolved 
 		against the server specified in the first argument. </p><p>This command is a shortcut for -M OWNER:name. 
-		</p></dd><dt><span class="term">-G|--chgrp name</span></dt><dd><p>The group owner of a file or directory can 
+		</p></dd><dt><span class="term">-G name</span></dt><dd><p>The group owner of a file or directory can 
 		be changed to the name given using the <em class="parameter"><code>-G</code></em> 
 		option.  The name can be a sid in the form S-1-x-y-z or a name 
 		resolved against the server specified n the first argument.
 		</p><p>This command is a shortcut for -M GROUP:name.</p></dd><dt><span class="term">--numeric</span></dt><dd><p>This option displays all ACL information in numeric 
 		format.  The default is to convert SIDs to names and ACE types 
-		and masks to a readable string format.  </p></dd><dt><span class="term">-t|--test-args</span></dt><dd><p>
+		and masks to a readable string format.  </p></dd><dt><span class="term">-t</span></dt><dd><p>
 		Don't actually do anything, only validate the correctness of 
 		the arguments.
 		</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
@@ -47,38 +52,7 @@ The default configuration file name is determined at
 compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
-</p></dd><dt><span class="term">-N|--no-pass</span></dt><dd><p>If specified, this parameter suppresses the normal
-password prompt from the client to the user. This is useful when
-accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or
-this parameter is specified, the client will request a
-password.</p><p>If a password is specified on the command line and this
-option is also defined the password on the command line will
-be silently ingnored and no password will be used.</p></dd><dt><span class="term">-k|--kerberos</span></dt><dd><p>
-Try to authenticate with kerberos. Only useful in
-an Active Directory environment.
-</p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows
-you to specify a file from which to read the username and
-password used in the connection.  The format of the file is
-</p><pre class="programlisting">
-username = &lt;value&gt;
-password = &lt;value&gt;
-domain   = &lt;value&gt;
-</pre><p>Make certain that the permissions on the file restrict 
-access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The
-client will first check the <code class="envar">USER</code> environment variable, then the
-<code class="envar">LOGNAME</code> variable and if either exists, the
-string is uppercased. If these environmental variables are not
-found, the username <code class="constant">GUEST</code> is used. </p><p>A third option is to use a credentials file which
-contains the plaintext of the username and password.  This
-option is mainly provided for scripts where the admin does not
-wish to pass the credentials on the command line or via environment
-variables. If this method is used, make certain that the permissions
-on the file restrict access from unwanted users.  See the
-<em class="parameter"><code>-A</code></em> for more details. </p><p>Be cautious about including passwords in scripts. Also, on
-many systems the command line of a running process may be seen
-via the <code class="literal">ps</code> command.  To be safe always allow
-<code class="literal">rpcclient</code> to prompt for a password and type
-it in directly. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481697"></a><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481600"></a><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by 
 	either commas or newlines.  An ACL entry is one of the following: </p><pre class="programlisting"> 
 REVISION:&lt;revision number&gt;
 OWNER:&lt;sid or name&gt;
@@ -103,13 +77,13 @@ ACL:&lt;sid or name&gt;:&lt;type&gt;/&lt;flags&gt;/&lt;mask&gt;
 	file permissions of the same name. </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>R</em></span> - Allow read access </p></li><li><p><span class="emphasis"><em>W</em></span> - Allow write access</p></li><li><p><span class="emphasis"><em>X</em></span> - Execute permission on the object</p></li><li><p><span class="emphasis"><em>D</em></span> - Delete the object</p></li><li><p><span class="emphasis"><em>P</em></span> - Change permissions</p></li><li><p><span class="emphasis"><em>O</em></span> - Take ownership</p></li></ul></div><p>The following combined permissions can be specified:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>READ</em></span> -  Equivalent to 'RX'
 		permissions</p></li><li><p><span class="emphasis"><em>CHANGE</em></span> - Equivalent to 'RXWD' permissions
 		</p></li><li><p><span class="emphasis"><em>FULL</em></span> - Equivalent to 'RWXDPO' 
-		permissions</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481861"></a><h2>EXIT STATUS</h2><p>The <code class="literal">smbcacls</code> program sets the exit status 
+		permissions</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481764"></a><h2>EXIT STATUS</h2><p>The <code class="literal">smbcacls</code> program sets the exit status 
 	depending on the success or otherwise of the operations performed.  
 	The exit status may be one of the following values. </p><p>If the operation succeeded, smbcacls returns and exit 
 	status of 0.  If <code class="literal">smbcacls</code> couldn't connect to the specified server, 
 	or there was an error getting or setting the ACLs, an exit status 
 	of 1 is returned.  If there was an error parsing any command line 
-	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481894"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481904"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481797"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481808"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p><code class="literal">smbcacls</code> was written by Andrew Tridgell 
diff --git a/docs/htmldocs/manpages/smbclient.1.html b/docs/htmldocs/manpages/smbclient.1.html
index 8ff419c7ad..d278db2534 100644
--- a/docs/htmldocs/manpages/smbclient.1.html
+++ b/docs/htmldocs/manpages/smbclient.1.html
@@ -1,11 +1,11 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient &#8212; ftp-like client to access SMB/CIFS resources
-	on servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b &lt;buffer size&gt;] [-d debuglevel] [-e] [-L &lt;netbios name&gt;] [-U username] [-I destinationIP] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-k] [-P] [-c &lt;command&gt;]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan] [-k]</p></div></div><div class="refsect1" lang="en"><a name="id2483752"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can 
+	on servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b &lt;buffer size&gt;] [-d debuglevel] [-e] [-L &lt;netbios name&gt;] [-U username] [-I destinationIP] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-k] [-P] [-c &lt;command&gt;]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan] [-k]</p></div></div><div class="refsect1" lang="en"><a name="id2483754"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can 
 	'talk' to an SMB/CIFS server. It offers an interface
 	similar to that of the ftp program (see <a class="citerefentry" href="ftp.1.html"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a>).  
 	Operations include things like getting files from the server 
 	to the local machine, putting files from the local machine to 
 	the server, retrieving directory information from the server 
-	and so on. </p></div><div class="refsect1" lang="en"><a name="id2483792"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service 
+	and so on. </p></div><div class="refsect1" lang="en"><a name="id2483794"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service 
 		you want to use on the server. A service name takes the form
 		<code class="filename">//server/service</code> where <em class="parameter"><code>server
 		</code></em> is the NetBIOS name of the SMB/CIFS server 
@@ -36,7 +36,7 @@
 		Workgroups) insist on an uppercase password. Lowercase 
 		or mixed case passwords may be rejected by these servers. 		
 		</p><p>Be cautious about including passwords in scripts.
-		</p></dd><dt><span class="term">-R|--name-resolve &lt;name resolve order&gt;</span></dt><dd><p>This option is used by the programs in the Samba 
+		</p></dd><dt><span class="term">-R &lt;name resolve order&gt;</span></dt><dd><p>This option is used by the programs in the Samba 
 		suite to determine what naming services and in what order to resolve 
 		host names to IP addresses. The option takes a space-separated 
 		string of different name resolution options.</p><p>The options are :"lmhosts", "host", "wins" and "bcast". They 
@@ -64,7 +64,7 @@
 		(name resolve order) will be used. </p><p>The default order is lmhosts, host, wins, bcast and without 
 		this parameter or any entry in the <em class="parameter"><code>name resolve order
 		</code></em> parameter of the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file the name resolution
-		methods will be attempted in this order. </p></dd><dt><span class="term">-M|--message NetBIOS name</span></dt><dd><p>This options allows you to send messages, using 
+		methods will be attempted in this order. </p></dd><dt><span class="term">-M NetBIOS name</span></dt><dd><p>This options allows you to send messages, using 
 		the "WinPopup" protocol, to another computer. Once a connection is 
 		established you then type your message, pressing ^D (control-D) to 
 		end. </p><p>If the receiving computer is running WinPopup the user will 
@@ -82,17 +82,16 @@
 		control the FROM and TO parts of the message. </p><p>See the <em class="parameter"><code>message command</code></em> parameter in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> for a description of how to handle incoming 
 		WinPopup messages in Samba. </p><p><span class="emphasis"><em>Note</em></span>: Copy WinPopup into the startup group 
 		on your WfWg PCs if you want them to always be able to receive 
-		messages. </p></dd><dt><span class="term">-p|--port port</span></dt><dd><p>This number is the TCP port number that will be used 
+		messages. </p></dd><dt><span class="term">-p port</span></dt><dd><p>This number is the TCP port number that will be used 
 		when making connections to the server. The standard (well-known)
 		TCP port number for an SMB/CIFS server is 139, which is the 
-		default. </p></dd><dt><span class="term">-g|--grepable</span></dt><dd><p>This parameter provides combined with
+		default. </p></dd><dt><span class="term">-g</span></dt><dd><p>This parameter provides combined with
 		<em class="parameter"><code>-L</code></em> easy parseable output	that allows processing
 		with utilities such as grep and cut.
-		</p></dd><dt><span class="term">-m|--max-protocol protocol</span></dt><dd><p>This parameter sets the maximum protocol version announced by the client.
 		</p></dd><dt><span class="term">-P</span></dt><dd><p>
 		Make queries to the external server using the machine account of the local server.
 		</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-I|--ip-address IP-address</span></dt><dd><p><em class="replaceable"><code>IP address</code></em> is the address of the server to connect to.
+</p></dd><dt><span class="term">-I IP-address</span></dt><dd><p><em class="replaceable"><code>IP address</code></em> is the address of the server to connect to.
 		It should be specified in standard "a.b.c.d" notation. </p><p>Normally the client would attempt to locate a named 
 		SMB/CIFS server by looking it up via the NetBIOS name resolution 
 		mechanism described above in the <em class="parameter"><code>name resolve order</code></em> 
@@ -101,15 +100,24 @@
 		address and the NetBIOS name component of the resource being 
 		connected to will be ignored. </p><p>There is no default for this parameter. If not supplied, 
 		it will be determined automatically by the client as described 
-		above. </p></dd><dt><span class="term">-E|--stderr</span></dt><dd><p>This parameter causes the client to write messages 
+		above. </p></dd><dt><span class="term">-E</span></dt><dd><p>This parameter causes the client to write messages 
 		to the standard error stream (stderr) rather than to the standard 
 		output stream. </p><p>By default, the client writes messages to standard output 
-		- typically the user's tty. </p></dd><dt><span class="term">-L|--list</span></dt><dd><p>This option allows you to look at what services 
+		- typically the user's tty. </p></dd><dt><span class="term">-L</span></dt><dd><p>This option allows you to look at what services 
 		are available on a server. You use it as <code class="literal">smbclient -L 
 		host</code> and a list should appear.  The <em class="parameter"><code>-I
 		</code></em> option may be useful if your NetBIOS names don't 
 		match your TCP/IP DNS host names or if you are trying to reach a 
-		host on another network. </p></dd><dt><span class="term">-b|--send-buffer buffersize</span></dt><dd><p>This option changes the transmit/send buffer 
+		host on another network. </p></dd><dt><span class="term">-t terminal code</span></dt><dd><p>This option tells <code class="literal">smbclient</code> how to interpret 
+		filenames coming from the remote server. Usually Asian language 
+		multibyte UNIX implementations use different character sets than 
+		SMB/CIFS servers (<span class="emphasis"><em>EUC</em></span> instead of <span class="emphasis"><em>
+		SJIS</em></span> for example). Setting this parameter will let 
+		<code class="literal">smbclient</code> convert between the UNIX filenames and 
+		the SMB filenames correctly. This option has not been seriously tested 
+		and may have some problems. </p><p>The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
+		CWjunet, CWhex, CWcap. This is not a complete list, check the Samba 
+		source code for the complete list. </p></dd><dt><span class="term">-b buffersize</span></dt><dd><p>This option changes the transmit/send buffer 
 		size when getting or putting a file from/to the server. The default 
 		is 65520 bytes. Setting this value smaller (to 1200 bytes) has been 
 		observed to speed up file transfers to and from a Win9x server. 
@@ -153,6 +161,8 @@ option is also defined the password on the command line will
 be silently ingnored and no password will be used.</p></dd><dt><span class="term">-k|--kerberos</span></dt><dd><p>
 Try to authenticate with kerberos. Only useful in
 an Active Directory environment.
+</p></dd><dt><span class="term">-C|--use-ccache</span></dt><dd><p>
+Try to use the credentials cached by winbind.
 </p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows
 you to specify a file from which to read the username and
 password used in the connection.  The format of the file is
@@ -193,7 +203,7 @@ NetBIOS name, it causes the client to log on using the servers local
 SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O|--socket-options socket options</span></dt><dd><p>TCP socket options to set on the client
 socket. See the socket options parameter in
 the <code class="filename">smb.conf</code> manual page for the list of valid
-options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>smbclient may be used to create <code class="literal">tar(1)
+options. </p></dd><dt><span class="term">-T tar options</span></dt><dd><p>smbclient may be used to create <code class="literal">tar(1)
 		</code> compatible backups of all the files on an SMB/CIFS
 		share. The secondary tar flags that can be given to this option 
 		are : </p><div class="itemizedlist"><ul type="disc"><li><p><em class="parameter"><code>c</code></em> - Create a tar file on UNIX. 
@@ -258,11 +268,11 @@ options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>
 		users\edocs </code></p><p>Create a tar file of the files listed in the file <code class="filename">tarlist</code>.</p><p><code class="literal">smbclient //mypc/myshare "" -N -TcF
 		backup.tar tarlist</code></p><p>Create a tar file of all the files and directories in 
 		the share. </p><p><code class="literal">smbclient //mypc/myshare "" -N -Tc backup.tar *
-		</code></p></dd><dt><span class="term">-D|--directory initial directory</span></dt><dd><p>Change to initial directory before starting. Probably 
-		only of any use with the tar -T option. </p></dd><dt><span class="term">-c|--comand command string</span></dt><dd><p>command string is a semicolon-separated list of 
+		</code></p></dd><dt><span class="term">-D initial directory</span></dt><dd><p>Change to initial directory before starting. Probably 
+		only of any use with the tar -T option. </p></dd><dt><span class="term">-c command string</span></dt><dd><p>command string is a semicolon-separated list of 
 		commands to be executed instead of prompting from stdin. <em class="parameter"><code>
 		-N</code></em> is implied by <em class="parameter"><code>-c</code></em>.</p><p>This is particularly useful in scripts and for printing stdin 
-		to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2533270"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with 
+		to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2533317"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with 
 	a prompt : </p><p><code class="prompt">smb:\&gt; </code></p><p>The backslash ("\\") indicates the current working directory 
 	on the server, and will change if the current working directory 
 	is changed. </p><p>The prompt indicates that the client is ready and waiting to 
@@ -414,10 +424,7 @@ options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>
 		name the remote copy <code class="filename">remote file name</code>. Note that all transfers
 		in <code class="literal">smbclient</code> are binary. See also the lowercase command.
 		</p></dd><dt><span class="term">queue</span></dt><dd><p>Displays the print queue, showing the job id,
-		name, size and current status. </p></dd><dt><span class="term">quit</span></dt><dd><p>See the exit command. </p></dd><dt><span class="term">readlink symlinkname</span></dt><dd><p>This command depends on the server supporting the CIFS
-		UNIX extensions and will fail if the server does not. Print
-		the value of the symlink "symlinkname".
-		</p></dd><dt><span class="term">rd &lt;directory name&gt;</span></dt><dd><p>See the rmdir command. </p></dd><dt><span class="term">recurse</span></dt><dd><p>Toggle directory recursion for the commands mget
+		name, size and current status. </p></dd><dt><span class="term">quit</span></dt><dd><p>See the exit command. </p></dd><dt><span class="term">rd &lt;directory name&gt;</span></dt><dd><p>See the rmdir command. </p></dd><dt><span class="term">recurse</span></dt><dd><p>Toggle directory recursion for the commands mget
 		and mput. </p><p>When toggled ON, these commands will process all directories
 		in the source directory (i.e., the directory they are copying
 		from ) and will recurse into any that match the mask specified
@@ -463,14 +470,14 @@ options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>
 		</p></dd><dt><span class="term">vuid &lt;number&gt;</span></dt><dd><p>Changes the currently used vuid in the protocol to
 		the given arbitrary number. Without an argument prints out the current
 		vuid being used. Used for internal Samba testing purposes.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2534521"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames,
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2534408"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames,
 	passwords, share names (AKA service names) and machine names.
 	If you fail to connect try giving all parameters in uppercase.
 	</p><p>It is often necessary to use the -n option when connecting
 	to some types of servers. For example OS/2 LanManager insists
 	on a valid NetBIOS name being used, so you need to supply a valid
 	name that would be known to the server.</p><p>smbclient supports long file names where the server 
-	supports the LANMAN2 protocol or above. </p></div><div class="refsect1" lang="en"><a name="id2534546"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the 
+	supports the LANMAN2 protocol or above. </p></div><div class="refsect1" lang="en"><a name="id2534433"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the 
 	username of the person  using the client. This information is 
 	used only if the protocol  level is high enough to support 
 	session-level passwords.</p><p>The variable <code class="envar">PASSWD</code> may contain 
@@ -480,7 +487,7 @@ options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>
 	the path, executed with system(), which the client should connect 
         to instead of connecting to a server.  This functionality is primarily
         intended as a development aid, and works best when using a LMHOSTS 
-        file</p></div><div class="refsect1" lang="en"><a name="id2534582"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for 
+        file</p></div><div class="refsect1" lang="en"><a name="id2534469"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for 
 	individual system administrators. The following are thus
 	suggestions only. </p><p>It is recommended that the smbclient software be installed
 	in the <code class="filename">/usr/local/samba/bin/</code> or <code class="filename">
@@ -491,11 +498,11 @@ options. </p></dd><dt><span class="term">-T|--tar tar options</span></dt><dd><p>
 	and writeable only by the user. </p><p>To test the client, you will need to know the name of a 
 	running SMB/CIFS server. It is possible to run <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> as an ordinary user - running that server as a daemon 
 	on a user-accessible port (typically any port number over 1024)
-	would provide a suitable test server. </p></div><div class="refsect1" lang="en"><a name="id2534634"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a 
+	would provide a suitable test server. </p></div><div class="refsect1" lang="en"><a name="id2534522"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a 
 	specified log file. The log file name is specified at compile time, 
 	but may be overridden on the command line. </p><p>The number and nature of diagnostics available depends 
 	on the debug level used by the client. If you have problems, 
-	set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" lang="en"><a name="id2534653"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2534664"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" lang="en"><a name="id2534540"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2534551"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbcontrol.1.html b/docs/htmldocs/manpages/smbcontrol.1.html
index 5be4111e6e..6317baeb91 100644
--- a/docs/htmldocs/manpages/smbcontrol.1.html
+++ b/docs/htmldocs/manpages/smbcontrol.1.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcontrol</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcontrol.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcontrol &#8212; send messages to smbd, nmbd or winbindd processes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcontrol</code> [-i] [-s]</p></div><div class="cmdsynopsis"><p><code class="literal">smbcontrol</code> [destination] [message-type] [parameter]</p></div></div><div class="refsect1" lang="en"><a name="id2483324"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbcontrol</code> is a very small program, which 
-	sends messages to a <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, a <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, or a <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon running on the system.</p></div><div class="refsect1" lang="en"><a name="id2483375"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcontrol</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcontrol.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcontrol &#8212; send messages to smbd, nmbd or winbindd processes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcontrol</code> [-i] [-s]</p></div><div class="cmdsynopsis"><p><code class="literal">smbcontrol</code> [destination] [message-type] [parameter]</p></div></div><div class="refsect1" lang="en"><a name="id2483336"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbcontrol</code> is a very small program, which 
+	sends messages to a <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, a <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, or a <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon running on the system.</p></div><div class="refsect1" lang="en"><a name="id2483387"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd><dt><span class="term">-s|--configfile &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the 
 configuration details required by the server.  The 
 information in this file includes server-specific
@@ -22,17 +22,14 @@ compile time.</p></dd><dt><span class="term">-i</span></dt><dd><p>Run interactiv
 		<code class="filename">winbindd.pid</code> file.</p><p>If a single process ID is given, the message is sent 
 		to only that process.</p></dd><dt><span class="term">message-type</span></dt><dd><p>Type of message to send. See 
 		the section <code class="constant">MESSAGE-TYPES</code> for details.
-		</p></dd><dt><span class="term">parameters</span></dt><dd><p>any parameters required for the message-type</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483681"></a><h2>MESSAGE-TYPES</h2><p>Available message types are:</p><div class="variablelist"><dl><dt><span class="term">close-share</span></dt><dd><p>Order smbd to close the client 
+		</p></dd><dt><span class="term">parameters</span></dt><dd><p>any parameters required for the message-type</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483690"></a><h2>MESSAGE-TYPES</h2><p>Available message types are:</p><div class="variablelist"><dl><dt><span class="term">close-share</span></dt><dd><p>Order smbd to close the client 
 	connections to the named share. Note that this doesn't affect client 
 	connections to any other shares. This message-type takes an argument of the
 	share name for which client connections will be closed, or the
 	"*" character which will close all currently open shares.
 	This may be useful if you made changes to the access controls on the share.
 	This message can only be sent to <code class="constant">smbd</code>.</p></dd><dt><span class="term">debug</span></dt><dd><p>Set debug level to the value specified by the 
-	parameter. This can be sent to any of the destinations. If this
-	message is sent to either the smbd or winbindd daemons, the parent
-	process will rebroadcast the message to all child processes changing
-	the debug level in each one.</p></dd><dt><span class="term">force-election</span></dt><dd><p>This message causes the <code class="literal">nmbd</code> daemon to 
+	parameter. This can be sent to any of the destinations.</p></dd><dt><span class="term">force-election</span></dt><dd><p>This message causes the <code class="literal">nmbd</code> daemon to 
 	force a new browse master election. </p></dd><dt><span class="term">ping</span></dt><dd><p>
 	Send specified number of "ping" messages and 
 	wait for the same number of  reply "pong" messages. This can be sent to 
@@ -68,8 +65,8 @@ compile time.</p></dd><dt><span class="term">-i</span></dt><dd><p>Run interactiv
 	to update their local version of the driver. Can only be 
 	sent to smbd.</p></dd><dt><span class="term">reload-config</span></dt><dd><p>Force daemon to reload smb.conf configuration file. Can be sent
 	to <code class="constant">smbd</code>, <code class="constant">nmbd</code>, or <code class="constant">winbindd</code>.
-	</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481695"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481706"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> and <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481731"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481702"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481713"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> and <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481738"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbcquotas.1.html b/docs/htmldocs/manpages/smbcquotas.1.html
index 793e79ddbf..2a2666adce 100644
--- a/docs/htmldocs/manpages/smbcquotas.1.html
+++ b/docs/htmldocs/manpages/smbcquotas.1.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcquotas</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcquotas.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcquotas &#8212; Set or get QUOTAs of NTFS 5 shares</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcquotas</code> {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logdir] [-V] [-U username] [-N] [-k] [-A]</p></div></div><div class="refsect1" lang="en"><a name="id2483523"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">smbcquotas</code> program manipulates NT Quotas on SMB file shares. </p></div><div class="refsect1" lang="en"><a name="id2483552"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">smbcquotas</code> program. </p><div class="variablelist"><dl><dt><span class="term">-u user</span></dt><dd><p> Specifies the user of whom the quotas are get or set.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcquotas</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcquotas.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcquotas &#8212; Set or get QUOTAs of NTFS 5 shares</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbcquotas</code> {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logdir] [-V] [-U username] [-N] [-k] [-A]</p></div></div><div class="refsect1" lang="en"><a name="id2483534"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">smbcquotas</code> program manipulates NT Quotas on SMB file shares. </p></div><div class="refsect1" lang="en"><a name="id2483562"></a><h2>OPTIONS</h2><p>The following options are available to the <code class="literal">smbcquotas</code> program. </p><div class="variablelist"><dl><dt><span class="term">-u user</span></dt><dd><p> Specifies the user of whom the quotas are get or set.
 		By default the current user's username will be used.</p></dd><dt><span class="term">-L</span></dt><dd><p>Lists all quota records of the share.</p></dd><dt><span class="term">-F</span></dt><dd><p>Show the share quota status and default limits.</p></dd><dt><span class="term">-S QUOTA_SET_COMMAND</span></dt><dd><p>This command sets/modifies quotas for a user or on the share,
 		depending on the QUOTA_SET_COMMAND parameter which is described later.</p></dd><dt><span class="term">-n</span></dt><dd><p>This option displays all QUOTA information in numeric 
 		format.  The default is to convert SIDs to names and QUOTA limits 
@@ -40,6 +40,8 @@ option is also defined the password on the command line will
 be silently ingnored and no password will be used.</p></dd><dt><span class="term">-k|--kerberos</span></dt><dd><p>
 Try to authenticate with kerberos. Only useful in
 an Active Directory environment.
+</p></dd><dt><span class="term">-C|--use-ccache</span></dt><dd><p>
+Try to use the credentials cached by winbind.
 </p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows
 you to specify a file from which to read the username and
 password used in the connection.  The format of the file is
@@ -62,7 +64,7 @@ on the file restrict access from unwanted users.  See the
 many systems the command line of a running process may be seen
 via the <code class="literal">ps</code> command.  To be safe always allow
 <code class="literal">rpcclient</code> to prompt for a password and type
-it in directly. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481668"></a><h2>QUOTA_SET_COMAND</h2><p>The format of an the QUOTA_SET_COMMAND is an operation
+it in directly. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481692"></a><h2>QUOTA_SET_COMAND</h2><p>The format of an the QUOTA_SET_COMMAND is an operation
 	name followed by a set of parameters specific to that operation.
 	</p><p>To set user quotas for the user specified by -u or for the
 	current username: </p><p><strong class="userinput"><code>
@@ -74,13 +76,13 @@ it in directly. </p></dd></dl></div></div><div class="refsect1" lang="en"><a nam
 	To change the share quota settings:
 	</p><p><strong class="userinput"><code>
 	FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
-	</code></strong></p><p>All limits are specified as a number of bytes.</p></div><div class="refsect1" lang="en"><a name="id2481721"></a><h2>EXIT STATUS</h2><p>The <code class="literal">smbcquotas</code> program sets the exit status
+	</code></strong></p><p>All limits are specified as a number of bytes.</p></div><div class="refsect1" lang="en"><a name="id2481744"></a><h2>EXIT STATUS</h2><p>The <code class="literal">smbcquotas</code> program sets the exit status
 	depending on the success or otherwise of the operations performed.
 	The exit status may be one of the following values. </p><p>If the operation succeeded, smbcquotas returns an exit
 	status of 0.  If <code class="literal">smbcquotas</code> couldn't connect to the specified server,
 	or when there was an error getting or setting the quota(s), an exit status
 	of 1 is returned.  If there was an error parsing any command line
-	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481754"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481764"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><a name="id2481777"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481788"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p><code class="literal">smbcquotas</code> was written by Stefan Metzmacher.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/smbd.8.html b/docs/htmldocs/manpages/smbd.8.html
index 0c80d75da0..56cd060c09 100644
--- a/docs/htmldocs/manpages/smbd.8.html
+++ b/docs/htmldocs/manpages/smbd.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbd &#8212; server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbd</code> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d &lt;debug level&gt;] [-l &lt;log directory&gt;] [-p &lt;port number(s)&gt;] [-P &lt;profiling level&gt;] [-O &lt;socket option&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483378"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbd</code> is the server daemon that 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbd &#8212; server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbd</code> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d &lt;debug level&gt;] [-l &lt;log directory&gt;] [-p &lt;port number(s)&gt;] [-P &lt;profiling level&gt;] [-O &lt;socket option&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483383"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbd</code> is the server daemon that 
 	provides filesharing and printing services to Windows clients. 
 	The server provides filespace and printer services to
 	clients using the SMB (or CIFS) protocol. This is compatible 
@@ -21,7 +21,7 @@
 	can force a reload by sending a SIGHUP to the server.  Reloading 
 	the configuration file will not affect connections to any service 
 	that is already established.  Either the user will have to 
-	disconnect from the service, or <code class="literal">smbd</code> killed and restarted.</p></div><div class="refsect1" lang="en"><a name="id2483589"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes 
+	disconnect from the service, or <code class="literal">smbd</code> killed and restarted.</p></div><div class="refsect1" lang="en"><a name="id2483594"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes 
 		the server to operate as a daemon. That is, it detaches 
 		itself and runs in the background, fielding requests 
 		on the appropriate port. Operating the server as a
@@ -82,7 +82,7 @@ log.smbd, etc...). The log file is never removed by the client.
 		number specifying the level of profiling data to be collected.
 		0 turns off profiling, 1 turns on counter profiling only,
 		2 turns on complete profiling, and 3 resets all profiling data.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481674"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the 
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481680"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the 
 		<code class="literal">inetd</code> meta-daemon, this file 
 		must contain suitable startup information for the 
 		meta-daemon. 
@@ -96,17 +96,17 @@ log.smbd, etc...). The log file is never removed by the client.
 		</p></dd><dt><span class="term"><code class="filename">/usr/local/samba/lib/smb.conf</code></span></dt><dd><p>This is the default location of the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server configuration file. Other common places that systems 
 		install this file are <code class="filename">/usr/samba/lib/smb.conf</code> 
 		and <code class="filename">/etc/samba/smb.conf</code>.</p><p>This file describes all the services the server 
-		is to make available to clients. See <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481800"></a><h2>LIMITATIONS</h2><p>On some systems <code class="literal">smbd</code> cannot change uid back 
+		is to make available to clients. See <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481806"></a><h2>LIMITATIONS</h2><p>On some systems <code class="literal">smbd</code> cannot change uid back 
 	to root after a setuid() call.  Such systems are called 
 	trapdoor uid systems. If you have such a system, 
 	you will be unable to connect from a client (such as a PC) as 
 	two different users at once. Attempts to connect the
 	second user will result in access denied or 
-	similar.</p></div><div class="refsect1" lang="en"><a name="id2481821"></a><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><code class="envar">PRINTER</code></span></dt><dd><p>If no printer name is specified to 
+	similar.</p></div><div class="refsect1" lang="en"><a name="id2481827"></a><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><code class="envar">PRINTER</code></span></dt><dd><p>If no printer name is specified to 
 		printable services, most systems will use the value of 
 		this variable (or <code class="constant">lp</code> if this variable is 
 		not defined) as the name of the printer to use. This 
-		is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481850"></a><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext 
+		is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481856"></a><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext 
 	password), for account checking (is this account disabled?) and for
 	session management.  The degree too which samba supports PAM is restricted
 	by the limitations of the SMB protocol and the <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a> <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> paramater.  When this is set, the following restrictions apply:
@@ -119,8 +119,8 @@ log.smbd, etc...). The log file is never removed by the client.
 	is granted.  Note however, that this is bypassed in share level secuirty.  
 	Note also that some older pam configuration files may need a line 
 	added for session support. 
-	</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481909"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481920"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged 
+	</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481915"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481926"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged 
 	in a specified log file. The log file name is specified 
 	at compile time, but may be overridden on the command line.</p><p>The number and nature of diagnostics available depends 
 	on the debug level used by the server. If you have problems, set 
@@ -129,10 +129,10 @@ log.smbd, etc...). The log file is never removed by the client.
 	available in the source code to warrant describing each and every 
 	diagnostic. At this stage your best bet is still to grep the 
 	source code and inspect the conditions that gave rise to the 
-	diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><a name="id2481948"></a><h2>TDB FILES</h2><p>Samba stores it's data in several TDB (Trivial Database) files, usually located in <code class="filename">/var/lib/samba</code>.</p><p>
+	diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><a name="id2481954"></a><h2>TDB FILES</h2><p>Samba stores it's data in several TDB (Trivial Database) files, usually located in <code class="filename">/var/lib/samba</code>.</p><p>
 	(*) information persistent across restarts (but not
 	necessarily important to backup).
-	</p><div class="variablelist"><dl><dt><span class="term">account_policy.tdb*</span></dt><dd><p>NT account policy settings such as pw expiration, etc...</p></dd><dt><span class="term">brlock.tdb</span></dt><dd><p>byte range locks</p></dd><dt><span class="term">browse.dat</span></dt><dd><p>browse lists</p></dd><dt><span class="term">connections.tdb</span></dt><dd><p>share connections (used to enforce max connections, etc...)</p></dd><dt><span class="term">gencache.tdb</span></dt><dd><p>generic caching db</p></dd><dt><span class="term">group_mapping.tdb*</span></dt><dd><p>group mapping information</p></dd><dt><span class="term">locking.tdb</span></dt><dd><p>share modes &amp; oplocks</p></dd><dt><span class="term">login_cache.tdb*</span></dt><dd><p>bad pw attempts</p></dd><dt><span class="term">messages.tdb</span></dt><dd><p>Samba messaging system</p></dd><dt><span class="term">netsamlogon_cache.tdb*</span></dt><dd><p>cache of user net_info_3 struct	from net_samlogon() request (as a domain member)</p></dd><dt><span class="term">ntdrivers.tdb*</span></dt><dd><p>installed printer drivers</p></dd><dt><span class="term">ntforms.tdb*</span></dt><dd><p>installed printer forms</p></dd><dt><span class="term">ntprinters.tdb*</span></dt><dd><p>installed printer information</p></dd><dt><span class="term">printing/</span></dt><dd><p>directory containing tdb per print queue of cached lpq output</p></dd><dt><span class="term">registry.tdb</span></dt><dd><p>Windows registry skeleton (connect via regedit.exe)</p></dd><dt><span class="term">sessionid.tdb</span></dt><dd><p>session information (e.g. support for 'utmp = yes')</p></dd><dt><span class="term">share_info.tdb*</span></dt><dd><p>share acls</p></dd><dt><span class="term">winbindd_cache.tdb</span></dt><dd><p>winbindd's cache of user lists, etc...</p></dd><dt><span class="term">winbindd_idmap.tdb*</span></dt><dd><p>winbindd's local idmap db</p></dd><dt><span class="term">wins.dat*</span></dt><dd><p>wins database when 'wins support = yes'</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532643"></a><h2>SIGNALS</h2><p>Sending the <code class="literal">smbd</code> a SIGHUP will cause it to 
+	</p><div class="variablelist"><dl><dt><span class="term">account_policy.tdb*</span></dt><dd><p>NT account policy settings such as pw expiration, etc...</p></dd><dt><span class="term">brlock.tdb</span></dt><dd><p>byte range locks</p></dd><dt><span class="term">browse.dat</span></dt><dd><p>browse lists</p></dd><dt><span class="term">connections.tdb</span></dt><dd><p>share connections (used to enforce max connections, etc...)</p></dd><dt><span class="term">gencache.tdb</span></dt><dd><p>generic caching db</p></dd><dt><span class="term">group_mapping.tdb*</span></dt><dd><p>group mapping information</p></dd><dt><span class="term">locking.tdb</span></dt><dd><p>share modes &amp; oplocks</p></dd><dt><span class="term">login_cache.tdb*</span></dt><dd><p>bad pw attempts</p></dd><dt><span class="term">messages.tdb</span></dt><dd><p>Samba messaging system</p></dd><dt><span class="term">netsamlogon_cache.tdb*</span></dt><dd><p>cache of user net_info_3 struct	from net_samlogon() request (as a domain member)</p></dd><dt><span class="term">ntdrivers.tdb*</span></dt><dd><p>installed printer drivers</p></dd><dt><span class="term">ntforms.tdb*</span></dt><dd><p>installed printer forms</p></dd><dt><span class="term">ntprinters.tdb*</span></dt><dd><p>installed printer information</p></dd><dt><span class="term">printing/</span></dt><dd><p>directory containing tdb per print queue of cached lpq output</p></dd><dt><span class="term">registry.tdb</span></dt><dd><p>Windows registry skeleton (connect via regedit.exe)</p></dd><dt><span class="term">sessionid.tdb</span></dt><dd><p>session information (e.g. support for 'utmp = yes')</p></dd><dt><span class="term">share_info.tdb*</span></dt><dd><p>share acls</p></dd><dt><span class="term">winbindd_cache.tdb</span></dt><dd><p>winbindd's cache of user lists, etc...</p></dd><dt><span class="term">winbindd_idmap.tdb*</span></dt><dd><p>winbindd's local idmap db</p></dd><dt><span class="term">wins.dat*</span></dt><dd><p>wins database when 'wins support = yes'</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532649"></a><h2>SIGNALS</h2><p>Sending the <code class="literal">smbd</code> a SIGHUP will cause it to 
 	reload its <code class="filename">smb.conf</code> configuration 
 	file within a short period of time.</p><p>To shut down a user's <code class="literal">smbd</code> process it is recommended 
 	that <code class="literal">SIGKILL (-9)</code> <span class="emphasis"><em>NOT</em></span> 
@@ -147,11 +147,11 @@ log.smbd, etc...). The log file is never removed by the client.
 	<code class="literal">smbd</code> is in a state of waiting for an incoming SMB before 
 	issuing them. It is possible to make the signal handlers safe 
 	by un-blocking the signals before the select call and re-blocking 
-	them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><a name="id2532730"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the 
+	them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><a name="id2532737"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the 
 	Internet RFC's	<code class="filename">rfc1001.txt</code>, <code class="filename">rfc1002.txt</code>. 
 	In addition the CIFS (formerly SMB) specification is available 
 	as a link from the Web page <a class="ulink" href="http://samba.org/cifs/" target="_top"> 
-	http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532810"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532817"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbget.1.html b/docs/htmldocs/manpages/smbget.1.html
index 0d2badbd9e..24754a56a4 100644
--- a/docs/htmldocs/manpages/smbget.1.html
+++ b/docs/htmldocs/manpages/smbget.1.html
@@ -1,14 +1,14 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbget</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbget.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbget &#8212; wget-like utility for download files over SMB</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbget</code> [-a, --guest] [-r, --resume] [-R, --recursive] [-u, --username=STRING] [-p, --password=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-P, --keep-permissions] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-O, --stdout] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2483559"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line. 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbget</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbget.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbget &#8212; wget-like utility for download files over SMB</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbget</code> [-a, --guest] [-r, --resume] [-R, --recursive] [-u, --username=STRING] [-p, --password=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-P, --keep-permissions] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]</p></div></div><div class="refsect1" lang="en"><a name="id2483556"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line. 
 	</p><p>
 		The files should be in the smb-URL standard, e.g. use smb://host/share/file
 		for the UNC path <span class="emphasis"><em>\\\\HOST\\SHARE\\file</em></span>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483592"></a><h2>OPTIONS</h2><dt><span class="term">-a, --guest</span></dt><dd><p>Work as user guest</p></dd><dt><span class="term">-r, --resume</span></dt><dd><p>Automatically resume aborted files</p></dd><dt><span class="term">-R, --recursive</span></dt><dd><p>Recursively download files</p></dd><dt><span class="term">-u, --username=STRING</span></dt><dd><p>Username to use</p></dd><dt><span class="term">-p, --password=STRING</span></dt><dd><p>Password to use</p></dd><dt><span class="term">-w, --workgroup=STRING</span></dt><dd><p>Workgroup to use (optional)</p></dd><dt><span class="term">-n, --nonprompt</span></dt><dd><p>Don't ask anything (non-interactive)</p></dd><dt><span class="term">-d, --debuglevel=INT</span></dt><dd><p>Debuglevel to use</p></dd><dt><span class="term">-D, --dots</span></dt><dd><p>Show dots as progress indication</p></dd><dt><span class="term">-P, --keep-permissions</span></dt><dd><p>Set same permissions on local file as are set on remote file.</p></dd><dt><span class="term">-o, --outputfile</span></dt><dd><p>Write the file that is being downloaded to the specified file. Can not be used together with -R.</p></dd><dt><span class="term">-O, --stdout</span></dt><dd><p>Write the file that is being downloaded to standard output.</p></dd><dt><span class="term">-f, --rcfile</span></dt><dd><p>Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.</p></dd><dt><span class="term">-q, --quiet</span></dt><dd><p>Be quiet</p></dd><dt><span class="term">-v, --verbose</span></dt><dd><p>Be verbose</p></dd><dt><span class="term">-b, --blocksize</span></dt><dd><p>Number of bytes to download in a block. Defaults to 64000.</p></dd><dt><span class="term">-?, --help</span></dt><dd><p>Show help message</p></dd><dt><span class="term">--usage</span></dt><dd><p>Display brief usage message</p></dd></div><div class="refsect1" lang="en"><a name="id2481475"></a><h2>SMB URLS</h2><p> SMB URL's should be specified in the following format:</p><pre class="programlisting">
+	</p></div><div class="refsect1" lang="en"><a name="id2483588"></a><h2>OPTIONS</h2><dt><span class="term">-a, --guest</span></dt><dd><p>Work as user guest</p></dd><dt><span class="term">-r, --resume</span></dt><dd><p>Automatically resume aborted files</p></dd><dt><span class="term">-R, --recursive</span></dt><dd><p>Recursively download files</p></dd><dt><span class="term">-u, --username=STRING</span></dt><dd><p>Username to use</p></dd><dt><span class="term">-p, --password=STRING</span></dt><dd><p>Password to use</p></dd><dt><span class="term">-w, --workgroup=STRING</span></dt><dd><p>Workgroup to use (optional)</p></dd><dt><span class="term">-n, --nonprompt</span></dt><dd><p>Don't ask anything (non-interactive)</p></dd><dt><span class="term">-d, --debuglevel=INT</span></dt><dd><p>Debuglevel to use</p></dd><dt><span class="term">-D, --dots</span></dt><dd><p>Show dots as progress indication</p></dd><dt><span class="term">-P, --keep-permissions</span></dt><dd><p>Set same permissions on local file as are set on remote file.</p></dd><dt><span class="term">-o, --outputfile</span></dt><dd><p>Write the file that is being download to the specified file. Can not be used together with -R.</p></dd><dt><span class="term">-f, --rcfile</span></dt><dd><p>Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.</p></dd><dt><span class="term">-q, --quiet</span></dt><dd><p>Be quiet</p></dd><dt><span class="term">-v, --verbose</span></dt><dd><p>Be verbose</p></dd><dt><span class="term">-b, --blocksize</span></dt><dd><p>Number of bytes to download in a block. Defaults to 64000.</p></dd><dt><span class="term">-?, --help</span></dt><dd><p>Show help message</p></dd><dt><span class="term">--usage</span></dt><dd><p>Display brief usage message</p></dd></div><div class="refsect1" lang="en"><a name="id2483791"></a><h2>SMB URLS</h2><p> SMB URL's should be specified in the following format:</p><pre class="programlisting">
 smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
 </pre><pre class="programlisting">
 smb:// means all the workgroups
 </pre><pre class="programlisting">
 smb://name/ means, if <em class="replaceable"><code>name</code></em> is a workgroup, all the servers in this workgroup, or if <em class="replaceable"><code>name</code></em> is a server, all the shares on this server.
-</pre></div><div class="refsect1" lang="en"><a name="id2481516"></a><h2>EXAMPLES</h2><pre class="programlisting">
+</pre></div><div class="refsect1" lang="en"><a name="id2481502"></a><h2>EXAMPLES</h2><pre class="programlisting">
 # Recursively download 'src' directory
 smbget -R smb://rhonwyn/jelmer/src
 # Download FreeBSD ISO and enable resuming
@@ -17,10 +17,10 @@ smbget -r smb://rhonwyn/isos/FreeBSD5.1.iso
 smbget -Rr smb://rhonwyn/isos
 # Backup my data on rhonwyn
 smbget -Rr smb://rhonwyn/
-</pre></div><div class="refsect1" lang="en"><a name="id2481534"></a><h2>BUGS</h2><p>Permission denied is returned in some cases where the cause of the error is unknown 
+</pre></div><div class="refsect1" lang="en"><a name="id2481519"></a><h2>BUGS</h2><p>Permission denied is returned in some cases where the cause of the error is unknown 
 (such as an illegally formatted smb:// url or trying to get a directory without -R 
-turned on).</p></div><div class="refsect1" lang="en"><a name="id2481547"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481558"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+turned on).</p></div><div class="refsect1" lang="en"><a name="id2481532"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481543"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The smbget manpage was written by Jelmer Vernooij.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/smbgetrc.5.html b/docs/htmldocs/manpages/smbgetrc.5.html
index fd5a0d9525..aa9cb5f819 100644
--- a/docs/htmldocs/manpages/smbgetrc.5.html
+++ b/docs/htmldocs/manpages/smbgetrc.5.html
@@ -1,17 +1,17 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbgetrc</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbgetrc.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbgetrc &#8212; configuration file for smbget</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">smbgetrc</code></p></div><div class="refsect1" lang="en"><a name="id2522906"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbgetrc</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbgetrc.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbgetrc &#8212; configuration file for smbget</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">smbgetrc</code></p></div><div class="refsect1" lang="en"><a name="id2522911"></a><h2>DESCRIPTION</h2><p>
 		This manual page documents the format and options of the <span class="emphasis"><em>smbgetrc</em></span> 
 		file. This is the configuration file used by the <a class="citerefentry" href="smbget.1.html"><span class="citerefentry"><span class="refentrytitle">smbget</span>(1)</span></a> 
 		utility. The file contains of key-value pairs, one pair on each line. The key 
 			and value should be separated by a space.
 	</p><p>By default, smbget reads its configuration from <span class="emphasis"><em>$HOME/.smbgetrc</em></span>, though 
-		other locations can be specified using the command-line options.</p></div><div class="refsect1" lang="en"><a name="id2522940"></a><h2>OPTIONS</h2><p>
+		other locations can be specified using the command-line options.</p></div><div class="refsect1" lang="en"><a name="id2522944"></a><h2>OPTIONS</h2><p>
 	The following keys can be set:
 </p><div class="variablelist"><dl><dt><span class="term">resume on|off</span></dt><dd><p>
 			Whether aborted downloads should be automatically resumed.
 			</p></dd><dt><span class="term">recursive on|off</span></dt><dd><p>Whether directories should be downloaded recursively</p></dd><dt><span class="term">username <em class="replaceable"><code>name</code></em></span></dt><dd><p>Username to use when logging in to the remote server. Use an empty string for anonymous access.
-			</p></dd><dt><span class="term">password <em class="replaceable"><code>pass</code></em></span></dt><dd><p>Password to use when logging in.</p></dd><dt><span class="term">workgroup <em class="replaceable"><code>wg</code></em></span></dt><dd><p>Workgroup to use when logging in</p></dd><dt><span class="term">nonprompt on|off</span></dt><dd><p>Turns off asking for username and password. Useful for scripts.</p></dd><dt><span class="term">debuglevel <em class="replaceable"><code>int</code></em></span></dt><dd><p>(Samba) debuglevel to run at. Useful for tracking down protocol level problems.</p></dd><dt><span class="term">dots on|off</span></dt><dd><p>Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.</p></dd><dt><span class="term">blocksize <em class="replaceable"><code>int</code></em></span></dt><dd><p>Number of bytes to put in a block. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483553"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483564"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbget.1.html"><span class="citerefentry"><span class="refentrytitle">smbget</span>(1)</span></a> and <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483589"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+			</p></dd><dt><span class="term">password <em class="replaceable"><code>pass</code></em></span></dt><dd><p>Password to use when logging in.</p></dd><dt><span class="term">workgroup <em class="replaceable"><code>wg</code></em></span></dt><dd><p>Workgroup to use when logging in</p></dd><dt><span class="term">nonprompt on|off</span></dt><dd><p>Turns off asking for username and password. Useful for scripts.</p></dd><dt><span class="term">debuglevel <em class="replaceable"><code>int</code></em></span></dt><dd><p>(Samba) debuglevel to run at. Useful for tracking down protocol level problems.</p></dd><dt><span class="term">dots on|off</span></dt><dd><p>Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.</p></dd><dt><span class="term">blocksize <em class="replaceable"><code>int</code></em></span></dt><dd><p>Number of bytes to put in a block. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483556"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483567"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbget.1.html"><span class="citerefentry"><span class="refentrytitle">smbget</span>(1)</span></a> and <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>.
+	</p></div><div class="refsect1" lang="en"><a name="id2483592"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>This manual page was written by Jelmer Vernooij</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/smbpasswd.5.html b/docs/htmldocs/manpages/smbpasswd.5.html
index 1c9c982406..ee52054e9a 100644
--- a/docs/htmldocs/manpages/smbpasswd.5.html
+++ b/docs/htmldocs/manpages/smbpasswd.5.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; The Samba encrypted password file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">smbpasswd</code></p></div><div class="refsect1" lang="en"><a name="id2522906"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbpasswd is the Samba encrypted password file. It contains 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; The Samba encrypted password file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">smbpasswd</code></p></div><div class="refsect1" lang="en"><a name="id2522911"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbpasswd is the Samba encrypted password file. It contains 
 	the username, Unix user id and the SMB hashed passwords of the 
 	user, as well as account flag information and the time the 
 	password was last changed. This file format has been evolving with 
-	Samba and has had several different formats in the past. </p></div><div class="refsect1" lang="en"><a name="id2522932"></a><h2>FILE FORMAT</h2><p>The format of the smbpasswd file used by Samba 2.2 
+	Samba and has had several different formats in the past. </p></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>FILE FORMAT</h2><p>The format of the smbpasswd file used by Samba 2.2 
 	is very similar to the familiar Unix <code class="filename">passwd(5)</code> 
 	file. It is an ASCII file containing one line for each user. Each field 
 	ithin each line is separated from the next by a colon. Any entry 
@@ -76,10 +76,10 @@
 		last modified. It consists of the characters 'LCT-' (standing for 
 		"Last Change Time") followed by a numeric encoding of the UNIX time 
 		in seconds since the epoch (1970) that the last change was made. 
-		</p></dd></dl></div><p>All other colon separated fields are ignored at this time.</p></div><div class="refsect1" lang="en"><a name="id2483685"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483696"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>, <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>, and
+		</p></dd></dl></div><p>All other colon separated fields are ignored at this time.</p></div><div class="refsect1" lang="en"><a name="id2483686"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483698"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>, <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>, and
 	the Internet RFC1321 for details on the MD4 algorithm.
-	</p></div><div class="refsect1" lang="en"><a name="id2483722"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	</p></div><div class="refsect1" lang="en"><a name="id2483724"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbpasswd.8.html b/docs/htmldocs/manpages/smbpasswd.8.html
index fc954827a1..30836e3df8 100644
--- a/docs/htmldocs/manpages/smbpasswd.8.html
+++ b/docs/htmldocs/manpages/smbpasswd.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; change a user's SMB password</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbpasswd</code> [-a] [-c &lt;config file&gt;] [-x] [-d] [-e] [-D debuglevel] [-n] [-r &lt;remote machine&gt;] [-R &lt;name resolve order&gt;] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-W] [-i] [-L] [username]</p></div></div><div class="refsect1" lang="en"><a name="id2483541"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The smbpasswd program has several different 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; change a user's SMB password</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbpasswd</code> [-a] [-c &lt;config file&gt;] [-x] [-d] [-e] [-D debuglevel] [-n] [-r &lt;remote machine&gt;] [-R &lt;name resolve order&gt;] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-W] [-i] [-L] [username]</p></div></div><div class="refsect1" lang="en"><a name="id2483542"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The smbpasswd program has several different 
 	functions, depending on whether it is run by the <span class="emphasis"><em>root</em></span> user 
 	or not. When run as a normal user it allows the user to change 
 	the password used for their SMB sessions on any machines that store 
@@ -151,7 +151,7 @@
 		<span class="emphasis"><em>root only</em></span> options to operate on. Only root 
 		can specify this parameter as only root has the permission needed 
 		to modify attributes directly in the local smbpasswd file. 
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532551"></a><h2>NOTES</h2><p>Since <code class="literal">smbpasswd</code> works in client-server 
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532553"></a><h2>NOTES</h2><p>Since <code class="literal">smbpasswd</code> works in client-server 
 	mode communicating  with a local smbd for a non-root user then 
 	the smbd daemon must be running for this to work. A common problem 
 	is to add a restriction to the hosts that may access the <code class="literal">
@@ -159,7 +159,7 @@
 	hosts</code></em> or <em class="parameter"><code>deny hosts</code></em> entry in 
 	the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file and neglecting to 
 	allow "localhost" access to the smbd. </p><p>In addition, the smbpasswd command is only useful if Samba
-	has been set up to use encrypted passwords. </p></div><div class="refsect1" lang="en"><a name="id2532600"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532610"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2532634"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	has been set up to use encrypted passwords. </p></div><div class="refsect1" lang="en"><a name="id2532602"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532613"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a class="citerefentry" href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2532636"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbspool.8.html b/docs/htmldocs/manpages/smbspool.8.html
index 02c801bd83..9650b2cd4d 100644
--- a/docs/htmldocs/manpages/smbspool.8.html
+++ b/docs/htmldocs/manpages/smbspool.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbspool</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbspool.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbspool &#8212; send a print file to an SMB printer</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbspool</code> {job} {user} {title} {copies} {options} [filename]</p></div></div><div class="refsect1" lang="en"><a name="id2483321"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbspool is a very small print spooling program that 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbspool</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbspool.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbspool &#8212; send a print file to an SMB printer</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbspool</code> {job} {user} {title} {copies} {options} [filename]</p></div></div><div class="refsect1" lang="en"><a name="id2483326"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>smbspool is a very small print spooling program that 
 	sends a print file to an SMB printer. The command-line arguments 
 	are position-dependent for compatibility with the Common UNIX 
 	Printing System, but you can use smbspool with any printing system 
@@ -10,7 +10,7 @@
 	or argv[1] if that is not the case.</p><p>Programs using the <code class="literal">exec(2)</code> functions can 
 	pass the URI in argv[0], while shell scripts must set the 
 	<code class="envar">DEVICE_URI</code> environment variable prior to
-	running smbspool.</p></div><div class="refsect1" lang="en"><a name="id2483536"></a><h2>OPTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>The job argument (argv[1]) contains the 
+	running smbspool.</p></div><div class="refsect1" lang="en"><a name="id2483539"></a><h2>OPTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>The job argument (argv[1]) contains the 
 		job ID number and is presently not used by smbspool.
 		</p></li><li><p>The user argument (argv[2]) contains the 
 		print user's name and is presently not used by smbspool.
@@ -23,7 +23,7 @@
 		the print options in a single string and is currently 
 		not used by smbspool.</p></li><li><p>The filename argument (argv[6]) contains the 
 		name of the file to print. If this argument is not specified 
-		then the print file is read from the standard input.</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483587"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483598"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2483622"></a><h2>AUTHOR</h2><p><code class="literal">smbspool</code> was written by Michael Sweet 
+		then the print file is read from the standard input.</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483590"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483601"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2483626"></a><h2>AUTHOR</h2><p><code class="literal">smbspool</code> was written by Michael Sweet 
 	at Easy Software Products.</p><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
diff --git a/docs/htmldocs/manpages/smbstatus.1.html b/docs/htmldocs/manpages/smbstatus.1.html
index d703b0819b..50cd06b650 100644
--- a/docs/htmldocs/manpages/smbstatus.1.html
+++ b/docs/htmldocs/manpages/smbstatus.1.html
@@ -1,5 +1,5 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbstatus</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbstatus.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbstatus &#8212; report on current Samba connections</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbstatus</code> [-P] [-b] [-d &lt;debug level&gt;] [-v] [-L] [-B] [-p] [-S] [-s &lt;configuration file&gt;] [-u &lt;username&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483356"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbstatus</code> is a very simple program to 
-	list the current Samba connections.</p></div><div class="refsect1" lang="en"><a name="id2483384"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-P|--profile</span></dt><dd><p>If samba has been compiled with the 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbstatus</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbstatus.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbstatus &#8212; report on current Samba connections</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbstatus</code> [-P] [-b] [-d &lt;debug level&gt;] [-v] [-L] [-B] [-p] [-S] [-s &lt;configuration file&gt;] [-u &lt;username&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483359"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbstatus</code> is a very simple program to 
+	list the current Samba connections.</p></div><div class="refsect1" lang="en"><a name="id2483386"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-P|--profile</span></dt><dd><p>If samba has been compiled with the 
 		profiling option, print only the contents of the profiling 
 		shared memory area.</p></dd><dt><span class="term">-b|--brief</span></dt><dd><p>gives brief output.</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
 from 0 to 10. The default value if this parameter is 
@@ -28,8 +28,8 @@ log.smbd, etc...). The log file is never removed by the client.
 </p></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>gives verbose output.</p></dd><dt><span class="term">-L|--locks</span></dt><dd><p>causes smbstatus to only list locks.</p></dd><dt><span class="term">-B|--byterange</span></dt><dd><p>causes smbstatus to include byte range locks.
 		</p></dd><dt><span class="term">-p|--processes</span></dt><dd><p>print a list of <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> processes and exit. 
 		Useful for scripting.</p></dd><dt><span class="term">-S|--shares</span></dt><dd><p>causes smbstatus to only list shares.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-u|--user=&lt;username&gt;</span></dt><dd><p>selects information relevant to <em class="parameter"><code>username</code></em> only.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481516"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481527"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481552"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+</p></dd><dt><span class="term">-u|--user=&lt;username&gt;</span></dt><dd><p>selects information relevant to <em class="parameter"><code>username</code></em> only.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481522"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481533"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481558"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/smbtar.1.html b/docs/htmldocs/manpages/smbtar.1.html
index f96d01e131..22e9de2032 100644
--- a/docs/htmldocs/manpages/smbtar.1.html
+++ b/docs/htmldocs/manpages/smbtar.1.html
@@ -1,6 +1,6 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtar</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtar.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbtar &#8212; shell script for backing up SMB/CIFS shares 
-	directly to UNIX tape drives</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbtar</code> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</p></div></div><div class="refsect1" lang="en"><a name="id2483515"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbtar</code> is a very small shell script on top 
-	of <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> which dumps SMB shares directly to tape.</p></div><div class="refsect1" lang="en"><a name="id2483549"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s server</span></dt><dd><p>The SMB/CIFS server that the share resides 
+	directly to UNIX tape drives</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbtar</code> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</p></div></div><div class="refsect1" lang="en"><a name="id2483521"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbtar</code> is a very small shell script on top 
+	of <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> which dumps SMB shares directly to tape.</p></div><div class="refsect1" lang="en"><a name="id2483555"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s server</span></dt><dd><p>The SMB/CIFS server that the share resides 
 		upon.</p></dd><dt><span class="term">-x service</span></dt><dd><p>The share name on the server to connect to. 
 		The default is "backup".</p></dd><dt><span class="term">-X</span></dt><dd><p>Exclude mode. Exclude filenames... from tar 
 		create or restore. </p></dd><dt><span class="term">-d directory</span></dt><dd><p>Change to initial <em class="parameter"><code>directory
@@ -17,14 +17,14 @@
 		up if they have the archive bit set. The archive bit is reset 
 		after each file is read. </p></dd><dt><span class="term">-r</span></dt><dd><p>Restore. Files are restored to the share 
 		from the tar file. </p></dd><dt><span class="term">-l log level</span></dt><dd><p>Log (debug) level. Corresponds to the 
-		<em class="parameter"><code>-d</code></em> flag of <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483768"></a><h2>ENVIRONMENT VARIABLES</h2><p>The <em class="parameter"><code>$TAPE</code></em> variable specifies the 
+		<em class="parameter"><code>-d</code></em> flag of <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483774"></a><h2>ENVIRONMENT VARIABLES</h2><p>The <em class="parameter"><code>$TAPE</code></em> variable specifies the 
 	default tape device to write to. May be overridden
-	with the -t option. </p></div><div class="refsect1" lang="en"><a name="id2483785"></a><h2>BUGS</h2><p>The <code class="literal">smbtar</code> script has different 
-	options from ordinary tar and from smbclient's tar command. </p></div><div class="refsect1" lang="en"><a name="id2481471"></a><h2>CAVEATS</h2><p>Sites that are more careful about security may not like 
+	with the -t option. </p></div><div class="refsect1" lang="en"><a name="id2483791"></a><h2>BUGS</h2><p>The <code class="literal">smbtar</code> script has different 
+	options from ordinary tar and from smbclient's tar command. </p></div><div class="refsect1" lang="en"><a name="id2481478"></a><h2>CAVEATS</h2><p>Sites that are more careful about security may not like 
 	the way the script handles PC passwords. Backup and restore work 
 	on entire shares; should work on file lists. smbtar works best
-	with GNU tar and may not work well with other versions. </p></div><div class="refsect1" lang="en"><a name="id2481486"></a><h2>DIAGNOSTICS</h2><p>See the <span class="emphasis"><em>DIAGNOSTICS</em></span> section for the <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> command.</p></div><div class="refsect1" lang="en"><a name="id2481509"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481520"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481554"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	with GNU tar and may not work well with other versions. </p></div><div class="refsect1" lang="en"><a name="id2481492"></a><h2>DIAGNOSTICS</h2><p>See the <span class="emphasis"><em>DIAGNOSTICS</em></span> section for the <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> command.</p></div><div class="refsect1" lang="en"><a name="id2481516"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481527"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></div><div class="refsect1" lang="en"><a name="id2481561"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p><a class="ulink" href="mailto:poultenr@logica.co.uk" target="_top">Ricky Poulten</a>  
diff --git a/docs/htmldocs/manpages/smbtree.1.html b/docs/htmldocs/manpages/smbtree.1.html
index 57d969bea6..c48f7a36e8 100644
--- a/docs/htmldocs/manpages/smbtree.1.html
+++ b/docs/htmldocs/manpages/smbtree.1.html
@@ -1,14 +1,14 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtree</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtree.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbtree &#8212; A text based smb network browser
-	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbtree</code> [-b] [-D] [-S]</p></div></div><div class="refsect1" lang="en"><a name="id2522934"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbtree</code> is a smb browser program 
+	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbtree</code> [-b] [-D] [-S]</p></div></div><div class="refsect1" lang="en"><a name="id2522937"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbtree</code> is a smb browser program 
 	in text mode. It is similar to the "Network Neighborhood" found 
 	on Windows computers. It prints a tree with all 
 	the known domains, the servers in those domains and 
 	the shares on the servers.
-	</p></div><div class="refsect1" lang="en"><a name="id2483330"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-b|--broadcast</span></dt><dd><p>Query network nodes by sending requests 
+	</p></div><div class="refsect1" lang="en"><a name="id2483333"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-b</span></dt><dd><p>Query network nodes by sending requests 
 		as broadcasts instead of querying the local master browser.
-		</p></dd><dt><span class="term">-D|--domains</span></dt><dd><p>Only print a list of all 
+		</p></dd><dt><span class="term">-D</span></dt><dd><p>Only print a list of all 
 		the domains known on broadcast or by the 
-		master browser</p></dd><dt><span class="term">-S|--servers</span></dt><dd><p>Only print a list of 
+		master browser</p></dd><dt><span class="term">-S</span></dt><dd><p>Only print a list of 
 		all the domains and servers responding on broadcast or 
 		known by the master browser. 
 		</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
@@ -44,6 +44,8 @@ option is also defined the password on the command line will
 be silently ingnored and no password will be used.</p></dd><dt><span class="term">-k|--kerberos</span></dt><dd><p>
 Try to authenticate with kerberos. Only useful in
 an Active Directory environment.
+</p></dd><dt><span class="term">-C|--use-ccache</span></dt><dd><p>
+Try to use the credentials cached by winbind.
 </p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows
 you to specify a file from which to read the username and
 password used in the connection.  The format of the file is
@@ -67,8 +69,8 @@ many systems the command line of a running process may be seen
 via the <code class="literal">ps</code> command.  To be safe always allow
 <code class="literal">rpcclient</code> to prompt for a password and type
 it in directly. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481517"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2481528"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481532"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba 
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2481543"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The smbtree man page was written by Jelmer Vernooij. </p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/swat.8.html b/docs/htmldocs/manpages/swat.8.html
index 4b89632511..019ff5a62c 100644
--- a/docs/htmldocs/manpages/swat.8.html
+++ b/docs/htmldocs/manpages/swat.8.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>swat</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="swat.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>swat &#8212; Samba Web Administration Tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">swat</code> [-s &lt;smb config file&gt;] [-a] [-P]</p></div></div><div class="refsect1" lang="en"><a name="id2522930"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">swat</code> allows a Samba administrator to 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>swat</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="swat.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>swat &#8212; Samba Web Administration Tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">swat</code> [-s &lt;smb config file&gt;] [-a] [-P]</p></div></div><div class="refsect1" lang="en"><a name="id2522936"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">swat</code> allows a Samba administrator to 
 	configure the complex <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file via a Web browser. In addition, 
 	a <code class="literal">swat</code> configuration page has help links 
 	to all the configurable options in the <code class="filename">smb.conf</code> file allowing an 
-	administrator to easily look up the effects of any change. </p><p><code class="literal">swat</code> is run from <code class="literal">inetd</code> </p></div><div class="refsect1" lang="en"><a name="id2483360"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s smb configuration file</span></dt><dd><p>The default configuration file path is 
+	administrator to easily look up the effects of any change. </p><p><code class="literal">swat</code> is run from <code class="literal">inetd</code> </p></div><div class="refsect1" lang="en"><a name="id2483366"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s smb configuration file</span></dt><dd><p>The default configuration file path is 
 		determined at compile time.  The file specified contains 
 		the configuration details required by the <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> server. This is the file 
 		that <code class="literal">swat</code> will modify. 
@@ -41,14 +41,14 @@ compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</spa
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481469"></a><h2>INSTALLATION</h2><p>Swat is included as binary package with most distributions. The 
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481475"></a><h2>INSTALLATION</h2><p>Swat is included as binary package with most distributions. The 
 	package manager in this case takes care of the installation and 
 	configuration. This section is only for those who have compiled 
 	swat from scratch.
 	</p><p>After you compile SWAT you need to run <code class="literal">make install
 	</code> to install the <code class="literal">swat</code> binary
 	and the various help files and images. A default install would put 
-	these in: </p><div class="itemizedlist"><ul type="disc"><li><p>/usr/local/samba/sbin/swat</p></li><li><p>/usr/local/samba/swat/images/*</p></li><li><p>/usr/local/samba/swat/help/*</p></li></ul></div><div class="refsect2" lang="en"><a name="id2481516"></a><h3>Inetd Installation</h3><p>You need to edit your <code class="filename">/etc/inetd.conf
+	these in: </p><div class="itemizedlist"><ul type="disc"><li><p>/usr/local/samba/sbin/swat</p></li><li><p>/usr/local/samba/swat/images/*</p></li><li><p>/usr/local/samba/swat/help/*</p></li></ul></div><div class="refsect2" lang="en"><a name="id2481522"></a><h3>Inetd Installation</h3><p>You need to edit your <code class="filename">/etc/inetd.conf
 		</code> and <code class="filename">/etc/services</code>
 		to enable SWAT to be launched via <code class="literal">inetd</code>.</p><p>In <code class="filename">/etc/services</code> you need to 
 		add a line like this: </p><p><code class="literal">swat            901/tcp</code></p><p>Note for NIS/YP and LDAP users - you may need to rebuild the 
@@ -62,21 +62,21 @@ log.smbd, etc...). The log file is never removed by the client.
 		/usr/local/samba/sbin/swat swat</code></p><p>Once you have edited <code class="filename">/etc/services</code> 
 		and <code class="filename">/etc/inetd.conf</code> you need to send a 
 		HUP signal to inetd. To do this use <code class="literal">kill -1 PID
-		</code> where PID is the process ID of the inetd daemon. </p></div></div><div class="refsect1" lang="en"><a name="id2481628"></a><h2>LAUNCHING</h2><p>To launch SWAT just run your favorite web browser and 
+		</code> where PID is the process ID of the inetd daemon. </p></div></div><div class="refsect1" lang="en"><a name="id2481634"></a><h2>LAUNCHING</h2><p>To launch SWAT just run your favorite web browser and 
 	point it at "http://localhost:901/".</p><p>Note that you can attach to SWAT from any IP connected 
 	machine but connecting from a remote machine leaves your 
 	connection open to password sniffing as passwords will be sent 
-	in the clear over the wire. </p></div><div class="refsect1" lang="en"><a name="id2481646"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>This file must contain suitable startup 
+	in the clear over the wire. </p></div><div class="refsect1" lang="en"><a name="id2481652"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>This file must contain suitable startup 
 		information for the meta-daemon.</p></dd><dt><span class="term"><code class="filename">/etc/services</code></span></dt><dd><p>This file must contain a mapping of service name 
 		(e.g., swat) to service port (e.g., 901) and protocol type 
 		(e.g., tcp).  </p></dd><dt><span class="term"><code class="filename">/usr/local/samba/lib/smb.conf</code></span></dt><dd><p>This is the default location of the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server configuration file that swat edits. Other 
 		common places that systems install this file are <code class="filename">
 		/usr/samba/lib/smb.conf</code> and <code class="filename">/etc/smb.conf
 		</code>.  This file describes all the services the server 
-		is to make available to clients. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481727"></a><h2>WARNINGS</h2><p><code class="literal">swat</code> will rewrite your <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. It will rearrange the entries and delete all 
+		is to make available to clients. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481733"></a><h2>WARNINGS</h2><p><code class="literal">swat</code> will rewrite your <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. It will rearrange the entries and delete all 
 	comments, <em class="parameter"><code>include=</code></em> and <em class="parameter"><code>copy=
 	</code></em> options. If you have a carefully crafted <code class="filename">
-	smb.conf</code> then back it up or don't use swat! </p></div><div class="refsect1" lang="en"><a name="id2481771"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481782"></a><h2>SEE ALSO</h2><p><code class="literal">inetd(5)</code>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2481813"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	smb.conf</code> then back it up or don't use swat! </p></div><div class="refsect1" lang="en"><a name="id2481777"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481788"></a><h2>SEE ALSO</h2><p><code class="literal">inetd(5)</code>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2481818"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/tdbbackup.8.html b/docs/htmldocs/manpages/tdbbackup.8.html
index 1dbe017d98..70c00674f1 100644
--- a/docs/htmldocs/manpages/tdbbackup.8.html
+++ b/docs/htmldocs/manpages/tdbbackup.8.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>tdbbackup</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="tdbbackup.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>tdbbackup &#8212; tool for backing up and for validating the integrity of samba .tdb files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">tdbbackup</code> [-s suffix] [-v] [-h]</p></div></div><div class="refsect1" lang="en"><a name="id2522934"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">tdbbackup</code> is a tool that may be used to backup samba .tdb
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>tdbbackup</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="tdbbackup.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>tdbbackup &#8212; tool for backing up and for validating the integrity of samba .tdb files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">tdbbackup</code> [-s suffix] [-v] [-h]</p></div></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">tdbbackup</code> is a tool that may be used to backup samba .tdb
 	files. This tool may also be used to verify the integrity of the .tdb files prior
 	to samba startup or during normal operation. If it finds file damage and it finds 
 	a prior backup the backup file will be restored. 
-	</p></div><div class="refsect1" lang="en"><a name="id2483331"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483335"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h</span></dt><dd><p>
 		Get help information.
 		</p></dd><dt><span class="term">-s suffix</span></dt><dd><p>
 		The <code class="literal">-s</code> option allows the adminisistrator to specify a file
@@ -11,7 +11,7 @@
 		</p></dd><dt><span class="term">-v</span></dt><dd><p>
 		The <code class="literal">-v</code> will check the database for damages (currupt data)
 		which if detected causes the backup to be restored.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483515"></a><h2>COMMANDS</h2><p><span class="emphasis"><em>GENERAL INFORMATION</em></span></p><p>
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483395"></a><h2>COMMANDS</h2><p><span class="emphasis"><em>GENERAL INFORMATION</em></span></p><p>
 	The <code class="literal">tdbbackup</code> utility can safely be run at any time. It was designed so
 	that it can be used at any time to validate the integrity of tdb files, even during Samba
 	operation. Typical usage for the command will be:
@@ -29,7 +29,7 @@
 		</p></li><li><p>
 		<code class="literal">*.tdb</code> located in the /usr/local/samba/var directory or on some
 		systems in the /var/cache or /var/lib/samba directories.
-		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483594"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483605"></a><h2>AUTHOR</h2><p>
+		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2483597"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483608"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities were created by Andrew Tridgell.
 	Samba is now developed by the Samba Team as an Open Source project similar to the way
 	the Linux kernel is developed.
diff --git a/docs/htmldocs/manpages/tdbdump.8.html b/docs/htmldocs/manpages/tdbdump.8.html
index f9671f8b39..871926b019 100644
--- a/docs/htmldocs/manpages/tdbdump.8.html
+++ b/docs/htmldocs/manpages/tdbdump.8.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>tdbdump</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="tdbdump.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>tdbdump &#8212; tool for printing the contents of a TDB file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">tdbdump</code> {filename}</p></div></div><div class="refsect1" lang="en"><a name="id2522918"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">tdbdump</code> is a very simple utility that 'dumps' the 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>tdbdump</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="tdbdump.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>tdbdump &#8212; tool for printing the contents of a TDB file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">tdbdump</code> {filename}</p></div></div><div class="refsect1" lang="en"><a name="id2522922"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">tdbdump</code> is a very simple utility that 'dumps' the 
 		contents of a TDB (Trivial DataBase) file to standard output in a 
 		human-readable format.
 	</p><p>This tool can be used when debugging problems with TDB files. It is 
 		intended for those who are somewhat familiar with Samba internals.
-	</p></div><div class="refsect1" lang="en"><a name="id2483320"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483331"></a><h2>AUTHOR</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483322"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2483333"></a><h2>AUTHOR</h2><p>
 	The original Samba software and related utilities were created by Andrew Tridgell.
 	Samba is now developed by the Samba Team as an Open Source project similar to the way
 	the Linux kernel is developed.
diff --git a/docs/htmldocs/manpages/tdbtool.8.html b/docs/htmldocs/manpages/tdbtool.8.html
index 0199cabb43..9acc770dfa 100644
--- a/docs/htmldocs/manpages/tdbtool.8.html
+++ b/docs/htmldocs/manpages/tdbtool.8.html
@@ -2,11 +2,11 @@
 		<em class="replaceable"><code>TDBFILE</code></em>
 		  [
 		<em class="replaceable"><code>COMMANDS</code></em>
-		...]</p></div></div><div class="refsect1" lang="en"><a name="id2522943"></a><h2>DESCRIPTION</h2><p>This tool is part of the
+		...]</p></div></div><div class="refsect1" lang="en"><a name="id2522946"></a><h2>DESCRIPTION</h2><p>This tool is part of the
 	<a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">tdbtool</code> a tool for displaying and
 	altering the contents of Samba TDB (Trivial DataBase) files. Each
 	of the commands listed below can be entered interactively or
-	provided on the command line.</p></div><div class="refsect1" lang="en"><a name="id2483338"></a><h2>COMMANDS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">create</code>
+	provided on the command line.</p></div><div class="refsect1" lang="en"><a name="id2483342"></a><h2>COMMANDS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">create</code>
 		<em class="replaceable"><code>TDBFILE</code></em></span></dt><dd><p>Create a new database named
 		<em class="replaceable"><code>TDBFILE</code></em>.
 		</p></dd><dt><span class="term"><code class="option">open</code>
@@ -59,10 +59,10 @@
 		</p></dd><dt><span class="term">
 		<code class="option">quit</code>
 		</span></dt><dd><p>Exit <code class="literal">tdbtool</code>.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481464"></a><h2>CAVEATS</h2><p>The contents of the Samba TDB files are private
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481470"></a><h2>CAVEATS</h2><p>The contents of the Samba TDB files are private
 	to the implementation and should not be altered with
 	<code class="literal">tdbtool</code>.
-	</p></div><div class="refsect1" lang="en"><a name="id2481482"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481493"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
+	</p></div><div class="refsect1" lang="en"><a name="id2481487"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481498"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
 	created by Andrew Tridgell.  Samba is now developed by the
 	Samba Team as an Open Source project similar to the way the
 	Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/testparm.1.html b/docs/htmldocs/manpages/testparm.1.html
index 0adbcd572a..3de1fc02f8 100644
--- a/docs/htmldocs/manpages/testparm.1.html
+++ b/docs/htmldocs/manpages/testparm.1.html
@@ -1,5 +1,5 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testparm</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testparm.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>testparm &#8212; check an smb.conf configuration file for 
-	internal correctness</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">testparm</code> [-s] [-h] [-v] [-L &lt;servername&gt;] [-t &lt;encoding&gt;] {config filename} [hostname hostIP]</p></div></div><div class="refsect1" lang="en"><a name="id2483333"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">testparm</code> is a very simple test program 
+	internal correctness</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">testparm</code> [-s] [-h] [-v] [-L &lt;servername&gt;] [-t &lt;encoding&gt;] {config filename} [hostname hostIP]</p></div></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">testparm</code> is a very simple test program 
 	to check an <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> configuration file for 
 	internal correctness. If this program reports no problems, you 
 	can use the configuration file with confidence that <code class="literal">smbd
@@ -11,7 +11,7 @@
 	has access to each service. </p><p>If <code class="literal">testparm</code> finds an error in the <code class="filename">
 	smb.conf</code> file it returns an exit code of 1 to the calling 
 	program, else it returns an exit code of 0. This allows shell scripts 
-	to test the output from <code class="literal">testparm</code>.</p></div><div class="refsect1" lang="en"><a name="id2483543"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s</span></dt><dd><p>Without this option, <code class="literal">testparm</code> 
+	to test the output from <code class="literal">testparm</code>.</p></div><div class="refsect1" lang="en"><a name="id2483544"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s</span></dt><dd><p>Without this option, <code class="literal">testparm</code> 
 		will prompt for a carriage return after printing the service 
 		names and before dumping the service definitions.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd><dt><span class="term">-V|--version</span></dt><dd><p>Prints the program version number.
@@ -41,14 +41,14 @@
 		this parameter is supplied, the hostIP parameter must also
 		be supplied.</p></dd><dt><span class="term">hostIP</span></dt><dd><p>This is the IP address of the host specified 
 		in the previous parameter.  This address must be supplied 
-		if the hostname parameter is supplied. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483753"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></span></dt><dd><p>This is usually the name of the configuration 
+		if the hostname parameter is supplied. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483754"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></span></dt><dd><p>This is usually the name of the configuration 
 		file used by <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>. 
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483788"></a><h2>DIAGNOSTICS</h2><p>The program will issue a message saying whether the 
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483789"></a><h2>DIAGNOSTICS</h2><p>The program will issue a message saying whether the 
 	configuration file loaded OK or not. This message may be preceded by 
 	errors and warnings if the file did not load. If the file was 
 	loaded OK, the program then dumps all known service details 
-	to stdout. </p></div><div class="refsect1" lang="en"><a name="id2481469"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481480"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2481505"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
+	to stdout. </p></div><div class="refsect1" lang="en"><a name="id2481477"></a><h2>VERSION</h2><p>This man page is correct for version 3 of 
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481486"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2481512"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
diff --git a/docs/htmldocs/manpages/umount.cifs.8.html b/docs/htmldocs/manpages/umount.cifs.8.html
index 49c793fd17..21250881cb 100644
--- a/docs/htmldocs/manpages/umount.cifs.8.html
+++ b/docs/htmldocs/manpages/umount.cifs.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>umount.cifs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="umount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>umount.cifs &#8212; for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">umount.cifs</code> {mount-point} [-nVvhfle]</p></div></div><div class="refsect1" lang="en"><a name="id2522920"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>umount.cifs unmounts a Linux CIFS filesystem. It can be invoked
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>umount.cifs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="umount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>umount.cifs &#8212; for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">umount.cifs</code> {mount-point} [-nVvhfle]</p></div></div><div class="refsect1" lang="en"><a name="id2522933"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>umount.cifs unmounts a Linux CIFS filesystem. It can be invoked
 indirectly by the
 <a class="citerefentry" href="umount.8.html"><span class="citerefentry"><span class="refentrytitle">umount</span>(8)</span></a> command 
 when umount.cifs is in /sbin directory, unless you specify the "-i" option to umount.  Specifying -i to umount avoids execution of umount helpers such as umount.cifs. The umount.cifs command only works in Linux, and the kernel must
@@ -11,38 +11,24 @@ by the popular Open Source server Samba.
 It is possible to set the mode for umount.cifs to 
 setuid root (or equivalently update the /etc/permissions file) to allow non-root users to umount shares to directories for which they have write permission.  The umount.cifs utility is typically
 not needed if unmounts need only be performed by root users, or if user mounts and unmounts
-can rely on specifying explicit entries in /etc/fstab See</p><p><a class="citerefentry" href="fstab.5.html"><span class="citerefentry"><span class="refentrytitle">fstab</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483353"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-V</span></dt><dd><p>Print version and exit.</p></dd><dt><span class="term">-h</span></dt><dd><p>Print help message and exit.</p></dd><dt><span class="term">-r</span></dt><dd><p>In case unmounting fails, try to remount
-				read-only.</p></dd><dt><span class="term">-d</span></dt><dd><p>In case the unmounted device was a loop device,
-				 also free this loop device.</p></dd><dt><span class="term">-f</span></dt><dd><p>Force unmount (in case of an unreachable
-				server).</p></dd><dt><span class="term">-l</span></dt><dd><p>Lazy unmount. Detach the filesystem from
-				the filesysetm hierarchy now, and
-				cleanup all references to the filesystem
-				as soon as it is not busy anymore.</p></dd><dt><span class="term">-e</span></dt><dd><p>Mark the mount point as expired.  If a mount
-				point is not currently in use, then an initial
-				call to unmount with this flag fails with the
-              			error EAGAIN, but marks the mount point as
-				expired.  The mount point remains expired as
-				long as it isn't accessed by any process.
-				A second unmount call specifying -e unmounts
-				an expired mount point.  This flag cannot be
-				specified with either -f or -l</p></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>Verbose Mode. Print additional debugging information</p></dd><dt><span class="term">-n|--no-mtab</span></dt><dd><p>Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483613"></a><h2>NOTES</h2><p>This command is normally intended to be installed setuid (since root users can already run unmount).  An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab</p></div><div class="refsect1" lang="en"><a name="id2483628"></a><h2>CONFIGURATION</h2><p>
+can rely on specifying explicit entries in /etc/fstab See</p><p><a class="citerefentry" href="fstab.5.html"><span class="citerefentry"><span class="refentrytitle">fstab</span>(5)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483366"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">--verbose</span></dt><dd><p>print additional debugging information</p></dd><dt><span class="term">--no-mtab</span></dt><dd><p>Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483525"></a><h2>NOTES</h2><p>This command is normally intended to be installed setuid (since root users can already run unmount).  An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab</p></div><div class="refsect1" lang="en"><a name="id2483540"></a><h2>CONFIGURATION</h2><p>
 The primary mechanism for making configuration changes and for reading 
 debug information for the cifs vfs is via the Linux /proc filesystem.
 In the directory <code class="filename">/proc/fs/cifs</code> are various 
 configuration files and pseudo files which can display debug information.  
 For more information see the kernel file <code class="filename">fs/cifs/README</code>.
-</p></div><div class="refsect1" lang="en"><a name="id2483655"></a><h2>BUGS</h2><p>At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time).
+</p></div><div class="refsect1" lang="en"><a name="id2483567"></a><h2>BUGS</h2><p>At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time).
 	</p><p>If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although umount.cifs will actually only unmount the last one), rather than only removing the last matching entry in /etc/mtab.  The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts.</p><p>
 Note that the typical response to a bug report is a suggestion
 to try the latest version first. So please try doing that first,
 and always include which versions you use of relevant software
 when reporting bugs (minimum: umount.cifs (try umount.cifs -V), kernel (see /proc/version) and
 server type you are trying to contact.
-</p></div><div class="refsect1" lang="en"><a name="id2483689"></a><h2>VERSION</h2><p>This man page is correct for version 1.34 of 
-	the cifs vfs filesystem (roughly Linux kernel 2.6.12).</p></div><div class="refsect1" lang="en"><a name="id2483701"></a><h2>SEE ALSO</h2><p>
+</p></div><div class="refsect1" lang="en"><a name="id2483601"></a><h2>VERSION</h2><p>This man page is correct for version 1.34 of 
+	the cifs vfs filesystem (roughly Linux kernel 2.6.12).</p></div><div class="refsect1" lang="en"><a name="id2483613"></a><h2>SEE ALSO</h2><p>
 	Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
 	source tree may contain additional options and information.
-</p><p><a class="citerefentry" href="mount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">mount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483722"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French</p><p>The maintainer of the Linux cifs vfs and the userspace
+</p><p><a class="citerefentry" href="mount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">mount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2483634"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French</p><p>The maintainer of the Linux cifs vfs and the userspace
 		tool <span class="emphasis"><em>umount.cifs</em></span> is <a class="ulink" href="mailto:sfrench@samba.org" target="_top">Steve French</a>.
 		The <a class="ulink" href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux CIFS Mailing list</a> 
 		is the preferred place to ask questions regarding these programs. 
diff --git a/docs/htmldocs/manpages/vfs_acl_tdb.8.html b/docs/htmldocs/manpages/vfs_acl_tdb.8.html
index 8861d19ada..c58f54291a 100644
--- a/docs/htmldocs/manpages/vfs_acl_tdb.8.html
+++ b/docs/htmldocs/manpages/vfs_acl_tdb.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_acl_tdb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_acl_tdb.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_acl_tdb &#8212; Save NTFS-ACLs in a tdb file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = acl_tdb</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_acl_tdb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_acl_tdb.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_acl_tdb &#8212; Save NTFS-ACLs in a tdb file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = acl_tdb</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_acl_tdb</code> VFS module stores
 	NTFS Access Control Lists (ACLs) in a tdb file.
 	This enables the full mapping of Windows ACLs on Samba
@@ -8,9 +8,9 @@
 	<code class="filename">$LOCKDIR/file_ntacls.tdb</code>.
 	</p><p>Please note that this module is
 	<span class="emphasis"><em>experimental</em></span>!
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483321"></a><h2>OPTIONS</h2><p>
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483333"></a><h2>OPTIONS</h2><p>
 	There are no options for <code class="literal">vfs_acl_tdb</code>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483349"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_acl_xattr.8.html b/docs/htmldocs/manpages/vfs_acl_xattr.8.html
index 036acdf20b..b128e1e334 100644
--- a/docs/htmldocs/manpages/vfs_acl_xattr.8.html
+++ b/docs/htmldocs/manpages/vfs_acl_xattr.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_acl_xattr</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_acl_xattr.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_acl_xattr &#8212; Save NTFS-ACLs in Extended Attributes (EAs)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = acl_xattr</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_acl_xattr</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_acl_xattr.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_acl_xattr &#8212; Save NTFS-ACLs in Extended Attributes (EAs)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = acl_xattr</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_acl_xattr</code> VFS module stores
 	NTFS Access Control Lists (ACLs) in Extended Attributes (EAs).
 	This enables the full mapping of Windows ACLs on Samba
@@ -12,9 +12,9 @@
 	</code>).
 	</p><p>Please note that this module is
 	<span class="emphasis"><em>experimental</em></span>!
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483350"></a><h2>OPTIONS</h2><p>
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483362"></a><h2>OPTIONS</h2><p>
 	There are no options for <code class="literal">vfs_acl_xattr</code>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483366"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483378"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_audit.8.html b/docs/htmldocs/manpages/vfs_audit.8.html
index 124b37c78d..d38732e2bd 100644
--- a/docs/htmldocs/manpages/vfs_audit.8.html
+++ b/docs/htmldocs/manpages/vfs_audit.8.html
@@ -1,19 +1,19 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_audit &#8212; record selected Samba VFS operations in the system log</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522911"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_audit &#8212; record selected Samba VFS operations in the system log</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_audit</code> VFS module records selected
 	client operations to the system log using
-	<a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a>.</p><p>The following Samba VFS operations are recorded:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>connect</td></tr><tr><td>disconnect</td></tr><tr><td>opendir</td></tr><tr><td>mkdir</td></tr><tr><td>rmdir</td></tr><tr><td>open</td></tr><tr><td>close</td></tr><tr><td>rename</td></tr><tr><td>unlink</td></tr><tr><td>chmod</td></tr><tr><td>fchmod</td></tr><tr><td>chmod_acl</td></tr><tr><td>fchmod_acl</td></tr></table><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483371"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">audit:facility = FACILITY</span></dt><dd><p>Log messages to the named
+	<a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a>.</p><p>The following Samba VFS operations are recorded:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>connect</td></tr><tr><td>disconnect</td></tr><tr><td>opendir</td></tr><tr><td>mkdir</td></tr><tr><td>rmdir</td></tr><tr><td>open</td></tr><tr><td>close</td></tr><tr><td>rename</td></tr><tr><td>unlink</td></tr><tr><td>chmod</td></tr><tr><td>fchmod</td></tr><tr><td>chmod_acl</td></tr><tr><td>fchmod_acl</td></tr></table><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483374"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">audit:facility = FACILITY</span></dt><dd><p>Log messages to the named
 		<a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a> facility.
 
 		</p></dd><dt><span class="term">audit:priority = PRIORITY</span></dt><dd><p>Log messages with the named
 		<a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a> priority.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483546"></a><h2>EXAMPLES</h2><p>Log operations on all shares using the LOCAL1 facility
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483547"></a><h2>EXAMPLES</h2><p>Log operations on all shares using the LOCAL1 facility
 	and NOTICE priority:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = audit</a>
 	<a class="link" href="smb.conf.5.html#AUDIT:FACILITY" target="_top">audit:facility = LOCAL1</a>
 	<a class="link" href="smb.conf.5.html#AUDIT:PRIORITY" target="_top">audit:priority = NOTICE</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483702"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483712"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483704"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483715"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_cacheprime.8.html b/docs/htmldocs/manpages/vfs_cacheprime.8.html
index 4c1980539b..d619af90ed 100644
--- a/docs/htmldocs/manpages/vfs_cacheprime.8.html
+++ b/docs/htmldocs/manpages/vfs_cacheprime.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_cacheprime</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_cacheprime.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_cacheprime &#8212; prime the kernel file data cache</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = cacheprime</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_cacheprime</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_cacheprime.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_cacheprime &#8212; prime the kernel file data cache</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = cacheprime</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_cacheprime</code> VFS module reads chunks
 	of file data near the range requested by clients in order to
 	make sure the data is present in the kernel file data cache at
@@ -7,20 +7,20 @@
 	cacheprime:rsize option. All disk read operations are aligned
 	on boundaries that are a multiple of this size. Each range of
 	the file data is primed at most once during the time the client
-	has the file open. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483322"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">cacheprime:rsize = BYTES</span></dt><dd><p>The number of bytes with which to prime
-		the kernel data cache.</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483381"></a><h2>EXAMPLES</h2><p>For a hypothetical disk array, it is necessary to ensure
+	has the file open. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483334"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">cacheprime:rsize = BYTES</span></dt><dd><p>The number of bytes with which to prime
+		the kernel data cache.</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483392"></a><h2>EXAMPLES</h2><p>For a hypothetical disk array, it is necessary to ensure
 	that all read operations are of size 1 megabyte (1048576 bytes),
 	and aligned on 1 megabyte boundaries:
 	</p><pre class="programlisting">
 	<em class="parameter"><code>[hypothetical]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = cacheprime</a>
 	<a class="link" href="smb.conf.5.html#CACHEPRIME:RSIZE" target="_top">cacheprime:rsize = 1M</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483653"></a><h2>CAVEATS</h2><p><code class="literal">cacheprime</code> is not a a substitute for
+</pre></div><div class="refsect1" lang="en"><a name="id2483662"></a><h2>CAVEATS</h2><p><code class="literal">cacheprime</code> is not a a substitute for
 	a general-purpose readahead mechanism. It is intended for use
 	only in very specific environments where disk operations must
 	be aligned and sized to known values (as much as that is possible).
-	</p></div><div class="refsect1" lang="en"><a name="id2483671"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483682"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483679"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483690"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_cap.8.html b/docs/htmldocs/manpages/vfs_cap.8.html
index 29d0d9df06..c35653e10a 100644
--- a/docs/htmldocs/manpages/vfs_cap.8.html
+++ b/docs/htmldocs/manpages/vfs_cap.8.html
@@ -1,17 +1,17 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_cap</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_cap.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_cap &#8212; CAP encode filenames</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = cap</code></p></div></div><div class="refsect1" lang="en"><a name="id2522910"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_cap</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_cap.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_cap &#8212; CAP encode filenames</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = cap</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>CAP (Columbia Appletalk Protocol) encoding is a
 	technique for representing non-ASCII filenames in ASCII. The
 	<code class="literal">vfs_cap</code> VFS module translates filenames to and
 	from CAP format, allowing users to name files in their native
 	encoding.  </p><p>CAP encoding is most commonly
-	used in Japanese language environments. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>EXAMPLES</h2><p>On a system using GNU libiconv, use CAP encoding to support
+	used in Japanese language environments. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>EXAMPLES</h2><p>On a system using GNU libiconv, use CAP encoding to support
 	users in the Shift_JIS locale:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset = CP932</a>
 	<a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset = CP932</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = cap</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483366"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483377"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483371"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483381"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_catia.8.html b/docs/htmldocs/manpages/vfs_catia.8.html
index 2ea43c7564..6d7ce35645 100644
--- a/docs/htmldocs/manpages/vfs_catia.8.html
+++ b/docs/htmldocs/manpages/vfs_catia.8.html
@@ -1,14 +1,14 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_catia</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_catia.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_catia &#8212; translate illegal characters in Catia filenames</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = catia</code></p></div></div><div class="refsect1" lang="en"><a name="id2522911"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_catia</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_catia.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_catia &#8212; translate illegal characters in Catia filenames</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = catia</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The Catia CAD package commonly creates filenames that
 	use characters that are illegal in CIFS filenames. The
 	<code class="literal">vfs_catia</code> VFS module implements a fixed character
 	mapping so that these files can be shared with CIFS clients.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522945"></a><h2>EXAMPLES</h2><p>Map Catia filenames on the [CAD] share:</p><pre class="programlisting">
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522948"></a><h2>EXAMPLES</h2><p>Map Catia filenames on the [CAD] share:</p><pre class="programlisting">
         <em class="parameter"><code>[CAD]</code></em>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /data/cad</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = catia</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483352"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483363"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483357"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483368"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_commit.8.html b/docs/htmldocs/manpages/vfs_commit.8.html
index e042dbb6fe..06473d78b6 100644
--- a/docs/htmldocs/manpages/vfs_commit.8.html
+++ b/docs/htmldocs/manpages/vfs_commit.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_commit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_commit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_commit &#8212; flush dirty data at specified intervals</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = commit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_commit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_commit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_commit &#8212; flush dirty data at specified intervals</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = commit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_commit</code> VFS module keeps track of
 	the amount of data written to a file and synchronizes it to
 	disk when a specified amount accumulates.
@@ -7,18 +7,18 @@
 	impact of unexpected power loss can be minimized by a small
 	commit:dthresh value. Secondly, write performance can be
 	improved on some systems by flushing file data early and at
-	regular intervals.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483317"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">commit:dthresh = BYTES</span></dt><dd><p>Synchronize file data each time the specified
+	regular intervals.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483330"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">commit:dthresh = BYTES</span></dt><dd><p>Synchronize file data each time the specified
 		number of bytes has been written.
-		</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483376"></a><h2>EXAMPLES</h2><p>Synchronize the file data on the [precious] share after
+		</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483389"></a><h2>EXAMPLES</h2><p>Synchronize the file data on the [precious] share after
 	every 512 kilobytes (524288 bytes) of data is written:</p><pre class="programlisting">
         <em class="parameter"><code>[precious]</code></em>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /data/precious</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = commit</a>
 	<a class="link" href="smb.conf.5.html#COMMIT:DTHRESH" target="_top">commit:dthresh = 512K</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483660"></a><h2>CAVEATS</h2><p>On some systems, the data synchronization performed by
+</pre></div><div class="refsect1" lang="en"><a name="id2483668"></a><h2>CAVEATS</h2><p>On some systems, the data synchronization performed by
 	<code class="literal">commit</code> may reduce performance.
-	</p></div><div class="refsect1" lang="en"><a name="id2483676"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483687"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483684"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483695"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_default_quota.8.html b/docs/htmldocs/manpages/vfs_default_quota.8.html
index 8d726a02d6..eb075e80eb 100644
--- a/docs/htmldocs/manpages/vfs_default_quota.8.html
+++ b/docs/htmldocs/manpages/vfs_default_quota.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_default_quota</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_default_quota.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_default_quota &#8212; store default quota records for Windows clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = default_quota</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_default_quota</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_default_quota.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_default_quota &#8212; store default quota records for Windows clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = default_quota</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>
 	suite.</p><p>Many common quota implementations only store
 	quotas for users and groups, but do not store a default quota. The
@@ -9,7 +9,7 @@
 	refuses to update them. <code class="literal">vfs_default_quota</code> maps
 	the default quota to the quota record of a user. By default the
 	root user is taken because quota limits for root are typically
-	not enforced.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483320"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">default_quota:uid = UID</span></dt><dd><p>UID specifies the user ID of the quota record where the
+	not enforced.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483336"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">default_quota:uid = UID</span></dt><dd><p>UID specifies the user ID of the quota record where the
 		default user quota values are stored.
 		</p></dd><dt><span class="term">default_quota:gid = GID</span></dt><dd><p>GID specifies the group ID of the quota record where the
 		default group quota values are stored.
@@ -21,15 +21,15 @@
 		quota record is storing the default group quota will
 		be reported as having a quota of NO_LIMIT. Otherwise,
 		the stored values will be reported.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483521"></a><h2>EXAMPLES</h2><p>Store the default quota record in the quota record for
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483527"></a><h2>EXAMPLES</h2><p>Store the default quota record in the quota record for
 	the user with ID 65535 and report that user as having no quota
 	limits:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = default_quota</a>
 	<a class="link" href="smb.conf.5.html#DEFAULT_QUOTA:UID" target="_top">default_quota:uid = 65535</a>
 	<a class="link" href="smb.conf.5.html#DEFAULT_QUOTA:UIDNOLIMIT" target="_top">default_quota:uid nolimit = yes</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483676"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483687"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483681"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483691"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_dirsort.8.html b/docs/htmldocs/manpages/vfs_dirsort.8.html
index 3b00af8184..3d336d17ac 100644
--- a/docs/htmldocs/manpages/vfs_dirsort.8.html
+++ b/docs/htmldocs/manpages/vfs_dirsort.8.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_dirsort</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_dirsort.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_dirsort &#8212; Sort directory contents</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = dirsort</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_dirsort</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_dirsort.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_dirsort &#8212; Sort directory contents</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = dirsort</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_dirsort</code> module sorts directory
 	entries alphabetically before sending them to the client.</p><p>Please be aware that adding this module might have negative
-	performance implications for large directories.</p></div><div class="refsect1" lang="en"><a name="id2522936"></a><h2>EXAMPLES</h2><p>Sort directories for all shares:</p><pre class="programlisting">
+	performance implications for large directories.</p></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>EXAMPLES</h2><p>Sort directories for all shares:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = dirsort</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483347"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483359"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_extd_audit.8.html b/docs/htmldocs/manpages/vfs_extd_audit.8.html
index 35c5ce76c5..fcd4124cae 100644
--- a/docs/htmldocs/manpages/vfs_extd_audit.8.html
+++ b/docs/htmldocs/manpages/vfs_extd_audit.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_extd_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_extd_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_extd_audit &#8212; record selected Samba VFS operations</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = extd_audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_extd_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_extd_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_extd_audit &#8212; record selected Samba VFS operations</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = extd_audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">extd_audit</code> VFS module records selected
 	client operations to both the
 	<a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> log and
@@ -7,8 +7,8 @@
 	<a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> log,
 	<code class="literal">vfs_extd_audit</code> is identical to
 	<a class="citerefentry" href="vfs_audit.8.html"><span class="citerefentry"><span class="refentrytitle">vfs_audit</span>(8)</span></a>.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483345"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483356"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483357"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483368"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_fake_perms.8.html b/docs/htmldocs/manpages/vfs_fake_perms.8.html
index 22fa9c05f3..712cc7171c 100644
--- a/docs/htmldocs/manpages/vfs_fake_perms.8.html
+++ b/docs/htmldocs/manpages/vfs_fake_perms.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_fake_perms</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_fake_perms.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_fake_perms &#8212; enable read only Roaming Profiles</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = fake_perms</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_fake_perms</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_fake_perms.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_fake_perms &#8212; enable read only Roaming Profiles</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = fake_perms</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_fake_perms</code> VFS module was created
 	to allow Roaming Profile files and directories to be set (on
 	the Samba server under UNIX) as read only. This module will,
@@ -6,12 +6,12 @@
 	the Profile files and directories are writeable. This satisfies
 	the client even though the files will never be overwritten as
 	the client logs out or shuts down.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522939"></a><h2>EXAMPLES</h2><pre class="programlisting">
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>EXAMPLES</h2><pre class="programlisting">
         <em class="parameter"><code>[Profiles]</code></em>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /profiles</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = fake_perms</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483358"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483369"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_fileid.8.html b/docs/htmldocs/manpages/vfs_fileid.8.html
index 61ba830e09..5752daa024 100644
--- a/docs/htmldocs/manpages/vfs_fileid.8.html
+++ b/docs/htmldocs/manpages/vfs_fileid.8.html
@@ -1,5 +1,5 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_fileid</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_fileid.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_fileid &#8212; Generates file_id structs with unique device id values for
-	cluster setups</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = fileid</code></p></div></div><div class="refsect1" lang="en"><a name="id2522904"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+	cluster setups</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = fileid</code></p></div></div><div class="refsect1" lang="en"><a name="id2522916"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>
 	suite.</p><p>Samba uses file_id structs to uniquely identify files
 	for locking purpose. By default the file_id contains the device
@@ -9,7 +9,7 @@
 	<code class="literal">SMB_VFS_FILE_ID_CREATE()</code> operation and
 	generates the device number based on the configured algorithm
 	(see the "fileid:algorithm" option).
-	</p></div><div class="refsect1" lang="en"><a name="id2483313"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">fileid:algorithm = ALGORITHM</span></dt><dd><p>Available algorithms are <code class="literal">fsname</code>
+	</p></div><div class="refsect1" lang="en"><a name="id2483326"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">fileid:algorithm = ALGORITHM</span></dt><dd><p>Available algorithms are <code class="literal">fsname</code>
 		and <code class="literal">fsid</code>. The default value is
 		<code class="literal">fsname</code>.
 		</p><p>The <code class="literal">fsname</code> algorithm generates
@@ -20,13 +20,13 @@
 		</p></dd><dt><span class="term">fileid:mapping = ALGORITHM</span></dt><dd><p>This option is the legacy version of the
 		<code class="literal">fileid:algorithm</code> option, which was used in earlier
 		versions of fileid mapping feature in custom Samba 3.0 versions.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483535"></a><h2>EXAMPLES</h2><p>Usage of the <code class="literal">fileid</code> module with the
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483543"></a><h2>EXAMPLES</h2><p>Usage of the <code class="literal">fileid</code> module with the
 	<code class="literal">fsid</code> algorithm:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = fileid</a>
 	<a class="link" href="smb.conf.5.html#FILEID:ALGORITHM" target="_top">fileid:algorithm = fsid</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483692"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483703"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483700"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483711"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_full_audit.8.html b/docs/htmldocs/manpages/vfs_full_audit.8.html
index abc02dcf3d..d2806a8417 100644
--- a/docs/htmldocs/manpages/vfs_full_audit.8.html
+++ b/docs/htmldocs/manpages/vfs_full_audit.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_full_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_full_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_full_audit &#8212; record Samba VFS operations in the system log</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = full_audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_full_audit</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_full_audit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_full_audit &#8212; record Samba VFS operations in the system log</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = full_audit</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_full_audit</code> VFS module records selected
 	client operations to the system log using
 	<a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a>.</p><p><code class="literal">vfs_full_audit</code> is able to record the
@@ -10,7 +10,7 @@
 	format consisting of fields separated by '|' characters. The
 	format is: </p><pre class="programlisting">
 		smbd_audit: PREFIX|OPERATION|RESULT|FILE
-	</pre><p>The record fields are:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">PREFIX</code> - the result of the full_audit:prefix string after variable substitutions</p></li><li><p><code class="literal">OPERATION</code> - the name of the VFS operation</p></li><li><p><code class="literal">RESULT</code> - whether the operation succeeded or failed</p></li><li><p><code class="literal">FILE</code> - the name of the file or directory the operation was performed on</p></li></ul></div><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2481520"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">vfs_full_audit:prefix = STRING</span></dt><dd><p>Prepend audit messages with STRING. STRING is
+	</pre><p>The record fields are:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">PREFIX</code> - the result of the full_audit:prefix string after variable substitutions</p></li><li><p><code class="literal">OPERATION</code> - the name of the VFS operation</p></li><li><p><code class="literal">RESULT</code> - whether the operation succeeded or failed</p></li><li><p><code class="literal">FILE</code> - the name of the file or directory the operation was performed on</p></li></ul></div><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2481531"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">vfs_full_audit:prefix = STRING</span></dt><dd><p>Prepend audit messages with STRING. STRING is
 		processed for standard substitution variables listed in
 		<a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>. The default
 		prefix is "%u|%I". </p></dd><dt><span class="term">vfs_full_audit:success = LIST</span></dt><dd><p>LIST is a list of VFS operations that should be
@@ -24,7 +24,7 @@
 
                 </p></dd><dt><span class="term">full_audit:priority = PRIORITY</span></dt><dd><p>Log messages with the named
                 <a class="citerefentry" href="syslog.3.html"><span class="citerefentry"><span class="refentrytitle">syslog</span>(3)</span></a> priority.
-                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481627"></a><h2>EXAMPLES</h2><p>Log file and directory open operations on the [records]
+                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481637"></a><h2>EXAMPLES</h2><p>Log file and directory open operations on the [records]
 	share using the LOCAL7 facility and ALERT priority, including
 	the username and IP address:</p><pre class="programlisting">
         <em class="parameter"><code>[records]</code></em>
@@ -35,8 +35,8 @@
 	<a class="link" href="smb.conf.5.html#FULL_AUDIT:FAILURE" target="_top">full_audit:failure = all</a>
 	<a class="link" href="smb.conf.5.html#FULL_AUDIT:FACILITY" target="_top">full_audit:facility = LOCAL7</a>
 	<a class="link" href="smb.conf.5.html#FULL_AUDIT:PRIORITY" target="_top">full_audit:priority = ALERT</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2481831"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481842"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2481840"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2481851"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_gpfs.8.html b/docs/htmldocs/manpages/vfs_gpfs.8.html
index fb6c0697ad..cbc958dd3c 100644
--- a/docs/htmldocs/manpages/vfs_gpfs.8.html
+++ b/docs/htmldocs/manpages/vfs_gpfs.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_gpfs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_gpfs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_gpfs &#8212; gpfs specific samba extensions like acls and prealloc</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = gpfs</code></p></div></div><div class="refsect1" lang="en"><a name="id2522911"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_gpfs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_gpfs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_gpfs &#8212; gpfs specific samba extensions like acls and prealloc</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = gpfs</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">gpfs</code> VFS module is the home
 	for all gpfs extensions that Samba requires for proper integration
 	with GPFS. It uses the GPL library interfaces provided by GPFS.
@@ -8,7 +8,7 @@
 	and hence allows permission stealing via chown. Samba might allow at a later
 	point in time, to restrict the chown via this module as such restrictions
 	are the responsibility of the underlying filesystem than of Samba.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483344"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">nfs4:mode = [ simple | special ]</span></dt><dd><p>
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">nfs4:mode = [ simple | special ]</span></dt><dd><p>
 		Enable/Disable substitution of special IDs on GPFS. This parameter
 		should not affect the windows users in anyway. It only ensures that Samba
 		sets the special IDs - OWNER@ and GROUP@ ( mappings to simple uids )
@@ -19,17 +19,17 @@
 		</p><p>Following is the behaviour of Samba for different values :</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">dontcare (default)</code> - copy the ACEs as they come</p></li><li><p><code class="literal">reject</code> - stop operation and exit with error on ACL set op</p></li><li><p><code class="literal">ignore</code> - don't include the second matching ACE</p></li><li><p><code class="literal">merge</code> - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE</p></li></ul></div></dd><dt><span class="term">nfs4:chown = [yes|no]</span></dt><dd><p>This parameter allows enabling or disabling the chown supported
 		by the underlying filesystem. This parameter should be enabled with
 		care as it might leave your system insecure.</p><p>Some filesystems allow chown as a) giving b) stealing. It is the latter
-		that is considered a risk.</p><p>Following is the behaviour of Samba for different values : </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">yes</code> - Enable chown if as supported by the under filesystem</p></li><li><p><code class="literal">no (default)</code> - Disable chown</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483633"></a><h2>EXAMPLES</h2><p>A GPFS mount can be exported via Samba as follows :</p><pre class="programlisting">
+		that is considered a risk.</p><p>Following is the behaviour of Samba for different values : </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">yes</code> - Enable chown if as supported by the under filesystem</p></li><li><p><code class="literal">no (default)</code> - Disable chown</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483635"></a><h2>EXAMPLES</h2><p>A GPFS mount can be exported via Samba as follows :</p><pre class="programlisting">
         <em class="parameter"><code>[samba_gpfs_share]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = gpfs</a>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /test/gpfs_mount</a>
 	<a class="link" href="smb.conf.5.html#NFS4:MODE" target="_top">nfs4: mode = special</a>
 	<a class="link" href="smb.conf.5.html#NFS4:ACEDUP" target="_top">nfs4: acedup = merge</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2481466"></a><h2>CAVEATS</h2><p>The gpfs gpl libraries are required by <code class="literal">gpfs</code> VFS
+</pre></div><div class="refsect1" lang="en"><a name="id2481471"></a><h2>CAVEATS</h2><p>The gpfs gpl libraries are required by <code class="literal">gpfs</code> VFS
 	module during both compilation and runtime.
 	Also this VFS module is tested to work on SLES 9/10 and RHEL 4.4
-	</p></div><div class="refsect1" lang="en"><a name="id2481483"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481494"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2481488"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2481499"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p>The GPFS VFS module was created with contributions from
diff --git a/docs/htmldocs/manpages/vfs_netatalk.8.html b/docs/htmldocs/manpages/vfs_netatalk.8.html
index 381c7bec41..16b8fb0f4c 100644
--- a/docs/htmldocs/manpages/vfs_netatalk.8.html
+++ b/docs/htmldocs/manpages/vfs_netatalk.8.html
@@ -1,15 +1,15 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_netatalk</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_netatalk.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_netatalk &#8212; hide .AppleDouble files from CIFS clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = netatalk</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_netatalk</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_netatalk.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_netatalk &#8212; hide .AppleDouble files from CIFS clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = netatalk</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_netatalk</code> VFS module dynamically
 	hides .AppleDouble files, preventing spurious errors on some
 	CIFS clients. .AppleDouble files may be created by historic
-	implementations of AFP (Apple Filing Protocol) on servers. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522937"></a><h2>EXAMPLES</h2><p>Hide .AppleDouble files on the [data] share:</p><pre class="programlisting">
+	implementations of AFP (Apple Filing Protocol) on servers. </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>EXAMPLES</h2><p>Hide .AppleDouble files on the [data] share:</p><pre class="programlisting">
         <em class="parameter"><code>[data]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = netatalk</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483338"></a><h2>CAVEATS</h2><p>This module is largely historic and unlikely to be of use
+</pre></div><div class="refsect1" lang="en"><a name="id2483350"></a><h2>CAVEATS</h2><p>This module is largely historic and unlikely to be of use
 	in modern networks since current Apple systems are able to mount CIFS
 	shares natively.
-	</p></div><div class="refsect1" lang="en"><a name="id2483351"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483361"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483362"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483373"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_notify_fam.8.html b/docs/htmldocs/manpages/vfs_notify_fam.8.html
index 10cd2e729e..f6447ed2bf 100644
--- a/docs/htmldocs/manpages/vfs_notify_fam.8.html
+++ b/docs/htmldocs/manpages/vfs_notify_fam.8.html
@@ -1,12 +1,12 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_notify_fam</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_notify_fam.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_notify_fam &#8212; FAM support for file change notifications</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = notify_fam</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_notify_fam</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_notify_fam.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_notify_fam &#8212; FAM support for file change notifications</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = notify_fam</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_notify_fam</code> module makes use of
 	the system FAM (File Alteration Monitor) daemon to implement
 	file change notifications for Windows clients. FAM is generally
-	present only on IRIX and some BSD systems.</p><p>This module is not stackable.</p></div><div class="refsect1" lang="en"><a name="id2522936"></a><h2>EXAMPLES</h2><p>Support FAM notifications globally:</p><pre class="programlisting">
+	present only on IRIX and some BSD systems.</p><p>This module is not stackable.</p></div><div class="refsect1" lang="en"><a name="id2522948"></a><h2>EXAMPLES</h2><p>Support FAM notifications globally:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = notify_fam</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483348"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483349"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483360"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_prealloc.8.html b/docs/htmldocs/manpages/vfs_prealloc.8.html
index 15bcea6b4a..dd5de32544 100644
--- a/docs/htmldocs/manpages/vfs_prealloc.8.html
+++ b/docs/htmldocs/manpages/vfs_prealloc.8.html
@@ -1,22 +1,22 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_prealloc</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_prealloc.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_prealloc &#8212; preallocate matching files to a predetermined size</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = prealloc</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_prealloc</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_prealloc.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_prealloc &#8212; preallocate matching files to a predetermined size</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = prealloc</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_prealloc</code> VFS module preallocates
 	files to a specified size each time a new file is created. This
 	is useful in environments where files are of a predetermined
 	size will be written to a disk subsystem where extending file
-	allocations is expensive.  </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">prealloc:EXT = BYTES</span></dt><dd><p>Preallocate all files with the extension EXT to
+	allocations is expensive.  </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522950"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">prealloc:EXT = BYTES</span></dt><dd><p>Preallocate all files with the extension EXT to
 		the size specified by BYTES.
-		</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483367"></a><h2>EXAMPLES</h2><p>A process writes TIFF files to a Samba share, and the
+		</p><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483378"></a><h2>EXAMPLES</h2><p>A process writes TIFF files to a Samba share, and the
 	is known these files will almost always be around 4 megabytes
 	(4194304 bytes): </p><pre class="programlisting">
         <em class="parameter"><code>[frames]</code></em>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /data/frames</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = prealloc</a>
 	<a class="link" href="smb.conf.5.html#PREALLOC:TIFF" target="_top">prealloc:tiff = 4M</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483651"></a><h2>CAVEATS</h2><p><code class="literal">vfs_prealloc</code> is not supported on all
+</pre></div><div class="refsect1" lang="en"><a name="id2483658"></a><h2>CAVEATS</h2><p><code class="literal">vfs_prealloc</code> is not supported on all
 	platforms and filesystems. Currently only XFS filesystems on
 	Linux and IRIX are supported.
-	</p></div><div class="refsect1" lang="en"><a name="id2483667"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483678"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</p></div><div class="refsect1" lang="en"><a name="id2483674"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483686"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_preopen.8.html b/docs/htmldocs/manpages/vfs_preopen.8.html
index 62451d3a44..16b4e48563 100644
--- a/docs/htmldocs/manpages/vfs_preopen.8.html
+++ b/docs/htmldocs/manpages/vfs_preopen.8.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_preopen</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_preopen.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_preopen &#8212; Hide read latencies for applications reading numbered files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = preopen</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_preopen</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_preopen.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_preopen &#8212; Hide read latencies for applications reading numbered files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = preopen</code></p></div></div><div class="refsect1" lang="en"><a name="id2522916"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>This module assists applications that want to read numbered
 	files in sequence with very strict latency requirements. One area
 	where this happens in video streaming applications that want to read
 	one file per frame.</p><p>When you use this module, a number of helper processes is
 	started that speculatively open files and read a number of bytes to
 	prime the file system cache, so that later on when the real
-	application's request comes along, no disk access is necessary.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522939"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">preopen:names = /pattern/</span></dt><dd><p>
+	application's request comes along, no disk access is necessary.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">preopen:names = /pattern/</span></dt><dd><p>
 		preopen:names specifies the file name pattern which should
 		trigger the preopen helpers to do their work. We assume that
 		the files are numbered incrementally. So if your file names
@@ -19,8 +19,8 @@
 		</p></dd><dt><span class="term">preopen:queuelen = NUM-FILES</span></dt><dd><p>
 		Number of files that should be speculatively opened. Defaults
 		to the 10 subsequent files.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483384"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483523"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483396"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483532"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p>The PREOPEN VFS module was created with contributions from
diff --git a/docs/htmldocs/manpages/vfs_readahead.8.html b/docs/htmldocs/manpages/vfs_readahead.8.html
index 38d358604a..1f54fc1f16 100644
--- a/docs/htmldocs/manpages/vfs_readahead.8.html
+++ b/docs/htmldocs/manpages/vfs_readahead.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_readahead</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_readahead.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_readahead &#8212; pre-load the kernel buffer cache</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = readahead</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_readahead</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_readahead.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_readahead &#8212; pre-load the kernel buffer cache</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = readahead</code></p></div></div><div class="refsect1" lang="en"><a name="id2522914"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>This <code class="literal">vfs_readahead</code> VFS module detects
 	read requests at multiples of a given offset (hex 0x80000 by
 	default) and then tells the kernel via either the readahead
@@ -12,14 +12,14 @@
 	readahead:length option. By default this is set to the
 	same value as the readahead:offset option and if not
 	set explicitly will use the current value of
-	readahead:offset.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483334"></a><h2>OPTIONS</h2><div class="variablelist"><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div><dl><dt><span class="term">readahead:offset = BYTES</span></dt><dd><p>The offset multiple that causes readahead to be
+	readahead:offset.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483343"></a><h2>OPTIONS</h2><div class="variablelist"><p>The following suffixes may be applied to BYTES:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">K</code> - BYTES is a number of kilobytes</p></li><li><p><code class="literal">M</code> - BYTES is a number of megabytes</p></li><li><p><code class="literal">G</code> - BYTES is a number of gigabytes</p></li></ul></div><dl><dt><span class="term">readahead:offset = BYTES</span></dt><dd><p>The offset multiple that causes readahead to be
 		requested of the kernel buffer cache.</p></dd><dt><span class="term">readahead:length = BYTES</span></dt><dd><p>The number of bytes requested to be
 		read into the kernel buffer cache on each
-		readahead call.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483532"></a><h2>EXAMPLES</h2><pre class="programlisting">
+		readahead call.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483542"></a><h2>EXAMPLES</h2><pre class="programlisting">
 	<em class="parameter"><code>[hypothetical]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = readahead</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483662"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483673"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483672"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483683"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_readonly.8.html b/docs/htmldocs/manpages/vfs_readonly.8.html
index 2569d1f559..0ac6274d55 100644
--- a/docs/htmldocs/manpages/vfs_readonly.8.html
+++ b/docs/htmldocs/manpages/vfs_readonly.8.html
@@ -1,15 +1,15 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_readonly</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_readonly.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_readonly &#8212; make a Samba share read only for a specified time period</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = readonly</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_readonly</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_readonly.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_readonly &#8212; make a Samba share read only for a specified time period</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = readonly</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_readonly</code> VFS module marks a share
 	as read only for all clients connecting within the configured
 	time period. Clients connecting during this time will be denied
 	write access to all files in the share, irrespective of ther
-	actual access privileges.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">readonly:period = BEGIN, END</span></dt><dd><p>Only mark the share as read only if the client
+	actual access privileges.</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522950"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">readonly:period = BEGIN, END</span></dt><dd><p>Only mark the share as read only if the client
 		connection was made between the times marked by the
 		BEGIN and END date specifiers.
 		The syntax of these date specifiers is the
 		same as that accepted by the -d option of GNU
 		<a class="citerefentry" href="date.1.html"><span class="citerefentry"><span class="refentrytitle">date</span>(1)</span></a>.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483344"></a><h2>EXAMPLES</h2><p>Mark all shares read only:</p><pre class="programlisting">
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483356"></a><h2>EXAMPLES</h2><p>Mark all shares read only:</p><pre class="programlisting">
         <em class="parameter"><code>[global]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = readonly</a>
 </pre><p>Mark the [backup] share as read only during business hours:</p><pre class="programlisting">
@@ -17,8 +17,8 @@
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /readonly</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = readonly</a>
 	<a class="link" href="smb.conf.5.html#READONLY:PERIOD" target="_top">readonly:period = readonly:period = "today 9:00","today 17:00"</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483651"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483662"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483659"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483669"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_recycle.8.html b/docs/htmldocs/manpages/vfs_recycle.8.html
index 5654ca65f2..06906c2a1b 100644
--- a/docs/htmldocs/manpages/vfs_recycle.8.html
+++ b/docs/htmldocs/manpages/vfs_recycle.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_recycle</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_recycle.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_recycle &#8212; Samba VFS recycle bin</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = recycle</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_recycle</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_recycle.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_recycle &#8212; Samba VFS recycle bin</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = recycle</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_recycle</code> intercepts file deletion
 	requests and moves the affected files to a temporary repository
 	rather than deleting them immediately. This gives the same effect
@@ -10,7 +10,7 @@
 	of the created directory depends on recycle:repository. Users
 	can recover files from the recycle bin. If the recycle:keeptree
 	option has been specified, deleted files will be found in a path
-	identical with that from which the file was deleted.  </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483318"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">recycle:repository = PATH</span></dt><dd><p>Path of the directory where deleted files should be moved.
+	identical with that from which the file was deleted.  </p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522952"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">recycle:repository = PATH</span></dt><dd><p>Path of the directory where deleted files should be moved.
 		</p><p>If this option is not set, the default path .recycle
 		is used. </p></dd><dt><span class="term">recycle:directory_mode = MODE</span></dt><dd><p>Set MODE to the octal mode the recycle repository
 		should be created with.  The recycle repository will be
@@ -47,7 +47,7 @@
 		</p></dd><dt><span class="term">recycle:noversions = LIST</span></dt><dd><p>Specifies a list of paths (wildcards such as *
 		and ? are supported) for which no versioning should
 		be used. Only useful when recycle:versions is enabled.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483653"></a><h2>EXAMPLES</h2><p>Move files "deleted" on <em class="parameter"><code>share</code></em> to
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483663"></a><h2>EXAMPLES</h2><p>Move files "deleted" on <em class="parameter"><code>share</code></em> to
 	<em class="parameter"><code>/data/share/.recycle</code></em> instead of deleting them:
 	</p><pre class="programlisting">
         <em class="parameter"><code>[share]</code></em>
@@ -56,8 +56,8 @@
 	<a class="link" href="smb.conf.5.html#RECYCLE:REPOSITORY" target="_top">recycle:repository = .recycle</a>
 	<a class="link" href="smb.conf.5.html#RECYCLE:KEEPTREE" target="_top">recycle:keeptree = yes</a>
 	<a class="link" href="smb.conf.5.html#RECYCLE:VERSIONS" target="_top">recycle:versions = yes</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2481504"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481515"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2481515"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2481526"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_scannedonly.8.html b/docs/htmldocs/manpages/vfs_scannedonly.8.html
deleted file mode 100644
index eadfbe9359..0000000000
--- a/docs/htmldocs/manpages/vfs_scannedonly.8.html
+++ /dev/null
@@ -1,90 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_scannedonly</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_scannedonly.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_scannedonly &#8212; Ensures that only files that have been scanned for viruses are
-	visible and accessible to the end user.</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = scannedonly</code></p></div></div><div class="refsect1" lang="en"><a name="id2522904"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
-	<a class="citerefentry" href="samba.8.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(8)</span></a> suite.</p><p>The <code class="literal">vfs_scannedonly</code> VFS module ensures that
-	only files that have been scanned for viruses are visible and accessible
-	to the end user. If non-scanned files are found an anti-virus scanning
-	daemon is notified. The anti-virus scanning daemon is not part of the
-	Samba suite.
-	</p><p>Scannedonly comes in two parts: a samba vfs module and (one or
-	more) daemons. The daemon scans files. If a certain file is clean,
-	a second file is created with prefix <code class="filename">.scanned:</code>.
-	The Samba module simply looks if such a <code class="filename">.scanned:</code>
-	file exists, and is newer than the pertinent file. If this is the case,
-	the file is shown to the user. If this is not the case, the file is not
-	returned in a directory listing (configurable), and cannot be opened
-	(configurable). The Samba vfs module will notify the daemon to scan
-	this file.
-	</p><p>So what happens for the user in the default configuration. The
-	first time a directory is listed, it shows files as 'file is being
-	scanned for viruses, but after the first time all files are shown.
-	There is a utility scannedonly_prescan that can help you to prescan
-	all directories. When new files are written the daemon is notified
-	immediately after the file is complete.
-	</p><p>If a virus is found by the daemon, a file with a warning message
-	is created in the directory of the user, a warning is sent to the logs,
-	and the file is renamed to have prefix <code class="filename">.virus:</code>.
-	Files with the <code class="filename">.virus:</code> prefix are never shown to
-	the user and all access is denied.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483361"></a><h2>CONFIGURATION</h2><p><code class="literal">vfs_scannedonly</code> relies on a anti-virus scanning
-	daemon that listens on the scannedonly socket (unix domain socket or UDP
-	socket).
-	</p></div><div class="refsect1" lang="en"><a name="id2483378"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">scannedonly:domain_socket = True </span></dt><dd><p>Whether to use a unix domain socket or not (false reverts
-		to use udp)
-		</p></dd><dt><span class="term">scannedonly:socketname = /var/lib/scannedonly/scan</span></dt><dd><p>The location of the unix domain socket to connect to</p></dd><dt><span class="term">scannedonly:portnum = 2020</span></dt><dd><p>The udp port number to connect to
-		</p></dd><dt><span class="term">scannedonly:scanhost = localhost</span></dt><dd><p>
-		When using UDP the host that runs the scanning daemon (this host
-		needs access to the files!)
-		</p></dd><dt><span class="term">scannedonly:show_special_files = True</span></dt><dd><p>
-		Whether sockets, devices and fifo's (all not scanned for
-		viruses) should be visible to the user
-		</p></dd><dt><span class="term">scannedonly:rm_hidden_files_on_rmdir = True</span></dt><dd><p>
-		Whether files that are not visible (<code class="filename">.scanned:</code>
-		files, <code class="filename">.failed:</code> files and <code class="filename">.virus:
-		</code> files) should be deleted if the user tries to remove
-		the directory. If false, the user will get the "directory is not
-		empty" error.
-		</p></dd><dt><span class="term">scannedonly:hide_nonscanned_files = True</span></dt><dd><p>
-		If false, all non-scanned files are visible in directory listings.
-		If such files are found in a directory listing the scanning daemon
-		is notified that scanning is required. Access to non-scanned files
-		is still denied (see scannedonly:allow_nonscanned_files).
-		</p></dd><dt><span class="term">scannedonly:scanning_message = is being scanned for
-	viruses</span></dt><dd><p>
-		If non-scanned files are hidden
-		(if scannedonly:hide_nonscanned_files = True), a fake 0 byte file
-		is shown. The filename is the original filename with the message
-		as suffix.
-		</p></dd><dt><span class="term">scannedonly:recheck_time_open = 50</span></dt><dd><p>
-		If a non-scanned file is opened, the vfs module will wait
-		recheck_tries_open times for recheck_time_open milliseconds for
-		the scanning daemon to create a <code class="filename">.scanned:</code>
-		file. For small files that are scanned by the daemon within the
-		time (tries * time) the behavior will be just like on-access
-		scanning.
-		</p></dd><dt><span class="term">scannedonly:recheck_tries_open = 100</span></dt><dd><p>
-		See recheck_time_open.
-		</p></dd><dt><span class="term">scannedonly:recheck_time_readdir = 50</span></dt><dd><p>
-		If a non-scanned file is in a directory listing the vfs module
-		notifies the daemon (once for all files that need scanning in
-		that directory), and waits recheck_tries_readdir times for
-		recheck_time_readdir milliseconds. Only used when
-		hide_nonscanned_files is false.
-		</p></dd><dt><span class="term">scannedonly:recheck_tries_readdir = 20</span></dt><dd><p>
-		See recheck_time_readdir.
-		</p></dd><dt><span class="term">scannedonly:allow_nonscanned_files = False</span></dt><dd><p>
-		Allow access to non-scanned files. The daemon is notified,
-		however, and special files such as <code class="filename">.scanned:</code>
-		files. <code class="filename">.virus:</code> files and
-		<code class="filename">.failed:</code> files are not listed.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483751"></a><h2>EXAMPLES</h2><p>Enable anti-virus scanning:</p><pre class="programlisting">
-        <em class="parameter"><code>[homes]</code></em>
-	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = scannedonly</a>
-	<a class="link" href="smb.conf.5.html#SCANNEDONLY:HIDE_NONSCANNED_FILES" target="_top">scannedonly:hide_nonscanned_files = False</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483793"></a><h2>CAVEATS</h2><p>This is not true on-access scanning. However, it is very fast
-	for files that have been scanned already.
-	</p></div><div class="refsect1" lang="en"><a name="id2481570"></a><h2>VERSION</h2><p>This man page is correct for version 3.5.0 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481581"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
-	were created by Andrew Tridgell. Scannedonly was
-	developed for Samba by Olivier Sessink. Samba is now developed
-	by the Samba Team as an Open Source project similar
-	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_shadow_copy.8.html b/docs/htmldocs/manpages/vfs_shadow_copy.8.html
index 0caf5bb455..8f58918b07 100644
--- a/docs/htmldocs/manpages/vfs_shadow_copy.8.html
+++ b/docs/htmldocs/manpages/vfs_shadow_copy.8.html
@@ -1,9 +1,9 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_shadow_copy</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_shadow_copy.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_shadow_copy &#8212; Make a Samba share read only for a specified time period</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = shadow_copy</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_shadow_copy</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_shadow_copy.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_shadow_copy &#8212; Make a Samba share read only for a specified time period</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = shadow_copy</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_shadow_copy</code> VFS module functionality
 	that is similar to Microsoft Shadow Copy services. When setup properly,
 	this module allows Microsoft Shadow Copy clients to browse
 	"shadow copies" on Samba shares.
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522936"></a><h2>CONFIGURATION</h2><p><code class="literal">vfs_shadow_copy</code> relies on a filesystem
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>CONFIGURATION</h2><p><code class="literal">vfs_shadow_copy</code> relies on a filesystem
 	snapshot implementation. Many common filesystems have native
 	support for this.
 	</p><p>Filesystem snapshots must be mounted on
@@ -16,17 +16,17 @@
 	<a class="citerefentry" href="date.1.html"><span class="citerefentry"><span class="refentrytitle">date</span>(1)</span></a> command:
 	</p><pre class="programlisting">
 	TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
-	</pre></div><div class="refsect1" lang="en"><a name="id2483552"></a><h2>EXAMPLES</h2><p>Add shadow copy support to user home directories:</p><pre class="programlisting">
+	</pre></div><div class="refsect1" lang="en"><a name="id2483556"></a><h2>EXAMPLES</h2><p>Add shadow copy support to user home directories:</p><pre class="programlisting">
         <em class="parameter"><code>[homes]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = shadow_copy</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483686"></a><h2>CAVEATS</h2><p>This is not a backup, archival, or version control solution.
+</pre></div><div class="refsect1" lang="en"><a name="id2483690"></a><h2>CAVEATS</h2><p>This is not a backup, archival, or version control solution.
 	</p><p>With Samba or Windows servers,
 	<code class="literal">vfs_shadow_copy</code> is designed to be an end-user
 	tool only. It does not replace or enhance your backup and
 	archival solutions and should in no way be considered as
 	such. Additionally, if you need version control, implement a
-	version control system.</p></div><div class="refsect1" lang="en"><a name="id2483710"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483721"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	version control system.</p></div><div class="refsect1" lang="en"><a name="id2483714"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2483726"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_shadow_copy2.8.html b/docs/htmldocs/manpages/vfs_shadow_copy2.8.html
index f441196091..3447f906a0 100644
--- a/docs/htmldocs/manpages/vfs_shadow_copy2.8.html
+++ b/docs/htmldocs/manpages/vfs_shadow_copy2.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_shadow_copy2</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_shadow_copy2.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_shadow_copy2 &#8212; Expose snapshots to Windows clients as shadow copies.</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = shadow_copy2</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_shadow_copy2</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_shadow_copy2.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_shadow_copy2 &#8212; Expose snapshots to Windows clients as shadow copies.</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = shadow_copy2</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_shadow_copy2</code> VFS module functionality
 	that is similar to Microsoft Shadow Copy services. When setup properly,
 	this module allows Microsoft Shadow Copy clients to browse
@@ -8,7 +8,7 @@
 	snapshots. This can be very important when you have thousands of
 	shares, or use [homes].</p></li><li><p>The inode number of the files is altered so it is different
 	from the original. This allows the 'restore' button to work
-	without a sharing violation.</p></li></ol></div><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483335"></a><h2>CONFIGURATION</h2><p><code class="literal">vfs_shadow_copy2</code> relies on a filesystem
+	without a sharing violation.</p></li></ol></div><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483351"></a><h2>CONFIGURATION</h2><p><code class="literal">vfs_shadow_copy2</code> relies on a filesystem
 	snapshot implementation. Many common filesystems have native
 	support for this.
 	</p><p>Filesystem snapshots must be mounted on
@@ -21,7 +21,7 @@
 	produced with the following <a class="citerefentry" href="date.1.html"><span class="citerefentry"><span class="refentrytitle">date</span>(1)</span></a> command:
 	</p><pre class="programlisting">
 	TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
-	</pre></div><div class="refsect1" lang="en"><a name="id2483579"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">shadow:snapdir = SNAPDIR
+	</pre></div><div class="refsect1" lang="en"><a name="id2483583"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">shadow:snapdir = SNAPDIR
                 </span></dt><dd><p>Path to the directory where snapshots are kept.
                 </p></dd><dt><span class="term">shadow:basedir = BASEDIR
 		</span></dt><dd><p>Path to the base directory that snapshots are from.
@@ -34,19 +34,19 @@
 		files (such as happens with GPFS snapshots). If you don't set
 		this option then the 'restore' button in the shadow copy UI
 		will fail with a sharing violation.
-                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483646"></a><h2>EXAMPLES</h2><p>Add shadow copy support to user home directories:</p><pre class="programlisting">
+                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483651"></a><h2>EXAMPLES</h2><p>Add shadow copy support to user home directories:</p><pre class="programlisting">
         <em class="parameter"><code>[homes]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = shadow_copy2</a>
 	<a class="link" href="smb.conf.5.html#SHADOW:SNAPDIR" target="_top">shadow:snapdir = /data/snaphots</a>
 	<a class="link" href="smb.conf.5.html#SHADOW:BASEDIR" target="_top">shadow:basedir = /data/home</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2481463"></a><h2>CAVEATS</h2><p>This is not a backup, archival, or version control solution.
+</pre></div><div class="refsect1" lang="en"><a name="id2481475"></a><h2>CAVEATS</h2><p>This is not a backup, archival, or version control solution.
 	</p><p>With Samba or Windows servers,
 	<code class="literal">vfs_shadow_copy2</code> is designed to be an end-user
 	tool only. It does not replace or enhance your backup and
 	archival solutions and should in no way be considered as
 	such. Additionally, if you need version control, implement a
-	version control system.</p></div><div class="refsect1" lang="en"><a name="id2481487"></a><h2>VERSION</h2><p>This man page is correct for version 3.2.7 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481498"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	version control system.</p></div><div class="refsect1" lang="en"><a name="id2481498"></a><h2>VERSION</h2><p>This man page is correct for version 3.2.7 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2481509"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html b/docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html
index 4150f959a3..17cc96616d 100644
--- a/docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html
+++ b/docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html
@@ -1,5 +1,5 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smb_traffic_analyzer</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_smb_traffic_analyzer.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_smb_traffic_analyzer &#8212; log Samba VFS read and write operations through a socket
-	to a helper application</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = smb_traffic_analyzer</code></p></div></div><div class="refsect1" lang="en"><a name="id2522906"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+	to a helper application</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = smb_traffic_analyzer</code></p></div></div><div class="refsect1" lang="en"><a name="id2522909"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_smb_traffic_analyzer</code> VFS module logs
 	client write and read operations on a Samba server and sends this data
 	over a socket to a helper program, which feeds a SQL database. More
@@ -15,7 +15,7 @@
 
 	</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">BYTES</code> - the length in bytes of the VFS operation</p></li><li><p><code class="literal">USER</code> - the user who initiated the operation</p></li><li><p><code class="literal">DOMAIN</code> - the domain of the user</p></li><li><p><code class="literal">READ/WRITE</code> - either "W" for a write operation or "R" for read</p></li><li><p><code class="literal">SHARE</code> - the name of the share on which the VFS operation occured</p></li><li><p><code class="literal">FILENAME</code> - the name of the file that was used by the VFS operation</p></li><li><p><code class="literal">TIMESTAMP</code> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured</p></li></ul></div><p>
 
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483552"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">smb_traffic_analyzer:mode = STRING</span></dt><dd><p>If STRING matches to "unix_domain_socket", the module will
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2483551"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">smb_traffic_analyzer:mode = STRING</span></dt><dd><p>If STRING matches to "unix_domain_socket", the module will
 		use a unix domain socket located at /var/tmp/stadsocket, if
 		STRING contains an different string or is not defined, the module will
 		use an internet domain socket for data transfer.</p></dd><dt><span class="term">smb_traffic_analyzer:host = STRING</span></dt><dd><p>The module will send the data to the system named with
@@ -28,7 +28,7 @@
 		smb_traffic_analyzer:anonymize_prefix, without generating
 		an additional hash number. This means that any transfer data
 		will be mapped to a single user, leading to a total 
-		anonymization of user related data.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483644"></a><h2>EXAMPLES</h2><p>The module running on share "example_share", using a unix domain socket</p><pre class="programlisting">
+		anonymization of user related data.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483642"></a><h2>EXAMPLES</h2><p>The module running on share "example_share", using a unix domain socket</p><pre class="programlisting">
 	<em class="parameter"><code>[example_share]</code></em>
 	<a class="link" href="smb.conf.5.html#PATH" target="_top">path = /data/example</a>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = smb_traffic_analyzer</a>
@@ -49,8 +49,8 @@
 	<a class="link" href="smb.conf.5.html#SMB_TRAFFIC_ANALYZER:HOST" target="_top">smb_traffic_analyzer:host = examplehost</a>
 	<a class="link" href="smb.conf.5.html#SMB_TRAFFIC_ANALYZER:PORT" target="_top">smb_traffic_analyzer:port = 3491</a>
 	<a class="link" href="smb.conf.5.html#SMB_TRAFFIC_ANALYZER:ANONYMIZE_PREFIX" target="_top">smb_traffic_analyzer:anonymize_prefix = User</a>
-	</pre></div><div class="refsect1" lang="en"><a name="id2481591"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2481602"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	</pre></div><div class="refsect1" lang="en"><a name="id2481601"></a><h2>VERSION</h2><p>This man page is correct for version 3.3 of the Samba suite.
+	</p></div><div class="refsect1" lang="en"><a name="id2481612"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p>The original version of the VFS module and the
diff --git a/docs/htmldocs/manpages/vfs_streams_depot.8.html b/docs/htmldocs/manpages/vfs_streams_depot.8.html
index 50de14536c..7301b34fad 100644
--- a/docs/htmldocs/manpages/vfs_streams_depot.8.html
+++ b/docs/htmldocs/manpages/vfs_streams_depot.8.html
@@ -1,15 +1,15 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_streams_depot</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_streams_depot.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_streams_depot &#8212; EXPERIMENTAL module to store alternate data streams in a
 	central directory.
-	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = streams_depot</code></p></div></div><div class="refsect1" lang="en"><a name="id2522904"></a><h2>DESCRIPTION</h2><p>This <span class="emphasis"><em>EXPERIMENTAL</em></span> VFS module is part of the
+	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = streams_depot</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This <span class="emphasis"><em>EXPERIMENTAL</em></span> VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_streams_depot</code> enables storing of NTFS
 	alternate data streams in the file system. As a normal posix file
 	system does not support the concept of multiple data streams per file,
 	the streams_depot module stores the data in files in a separate
-	directory.</p></div><div class="refsect1" lang="en"><a name="id2522938"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">streams_depot:directory = PATH</span></dt><dd><p>Path of the directory where the alternate data streams
-		should be stored. Defaults to the sharepath/.streams.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483334"></a><h2>EXAMPLES</h2><pre class="programlisting">
+	directory.</p></div><div class="refsect1" lang="en"><a name="id2522951"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">streams_depot:directory = PATH</span></dt><dd><p>Path of the directory where the alternate data streams
+		should be stored. Defaults to the sharepath/.streams.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483349"></a><h2>EXAMPLES</h2><pre class="programlisting">
         <em class="parameter"><code>[share]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = streams_depot</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483361"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483376"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_streams_xattr.8.html b/docs/htmldocs/manpages/vfs_streams_xattr.8.html
index 84b7e7dace..08de1a91f0 100644
--- a/docs/htmldocs/manpages/vfs_streams_xattr.8.html
+++ b/docs/htmldocs/manpages/vfs_streams_xattr.8.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_streams_xattr</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_streams_xattr.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_streams_xattr &#8212; Store alternate data streams in posix xattrs</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = streams_xattr</code></p></div></div><div class="refsect1" lang="en"><a name="id2522902"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_streams_xattr</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_streams_xattr.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_streams_xattr &#8212; Store alternate data streams in posix xattrs</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = streams_xattr</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_streams_xattr</code> enables storing of NTFS
 	alternate data streams in the file system. As a normal posix file
 	system does not support the concept of multiple data streams per file,
@@ -8,10 +8,10 @@
 	support xattrs.</p><p>Please note that most file systems have severe limitations on
 	the size of xattrs. So this module might work for applications like IE
 	that stores small zone information in streams but will fail for
-	applications that store serious amounts of data in ADSs.</p></div><div class="refsect1" lang="en"><a name="id2483321"></a><h2>EXAMPLES</h2><pre class="programlisting">
+	applications that store serious amounts of data in ADSs.</p></div><div class="refsect1" lang="en"><a name="id2483335"></a><h2>EXAMPLES</h2><pre class="programlisting">
         <em class="parameter"><code>[share]</code></em>
 	<a class="link" href="smb.conf.5.html#VFSOBJECTS" target="_top">vfs objects = streams_xattr</a>
-</pre></div><div class="refsect1" lang="en"><a name="id2483346"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+</pre></div><div class="refsect1" lang="en"><a name="id2483361"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfs_xattr_tdb.8.html b/docs/htmldocs/manpages/vfs_xattr_tdb.8.html
index e7ebb908c1..d76bd56549 100644
--- a/docs/htmldocs/manpages/vfs_xattr_tdb.8.html
+++ b/docs/htmldocs/manpages/vfs_xattr_tdb.8.html
@@ -1,12 +1,12 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_xattr_tdb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_xattr_tdb.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_xattr_tdb &#8212; Save Extended Attributes (EAs) in a tdb file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = xattr_tdb</code></p></div></div><div class="refsect1" lang="en"><a name="id2522903"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfs_xattr_tdb</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfs_xattr_tdb.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfs_xattr_tdb &#8212; Save Extended Attributes (EAs) in a tdb file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfs objects = xattr_tdb</code></p></div></div><div class="refsect1" lang="en"><a name="id2522915"></a><h2>DESCRIPTION</h2><p>This VFS module is part of the
 	<a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">vfs_xattr_tdb</code> VFS module stores
 	Extended Attributes (EAs) in a tdb file. 
 	This enables the usage of Extended Attributes on OS and 
 	filesystems which do not support Extended Attributes 
 	by themselves.	
-	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522937"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">xattr_tdb:file = PATH</span></dt><dd><p>Name of the tdb file the EAs are stored in.
+	</p><p>This module is stackable.</p></div><div class="refsect1" lang="en"><a name="id2522949"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">xattr_tdb:file = PATH</span></dt><dd><p>Name of the tdb file the EAs are stored in.
 		If this option is not set, the default filename 
-		<code class="filename">xattr.tdb</code> is used.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483338"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+		<code class="filename">xattr.tdb</code> is used.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483350"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/vfstest.1.html b/docs/htmldocs/manpages/vfstest.1.html
index 442a04e754..3db40ddcec 100644
--- a/docs/htmldocs/manpages/vfstest.1.html
+++ b/docs/htmldocs/manpages/vfstest.1.html
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfstest</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfstest.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfstest &#8212; tool for testing samba VFS modules </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfstest</code> [-d debuglevel] [-c command] [-l logdir] [-h]</p></div></div><div class="refsect1" lang="en"><a name="id2522942"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">vfstest</code> is a small command line
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfstest</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfstest.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfstest &#8212; tool for testing samba VFS modules </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">vfstest</code> [-d debuglevel] [-c command] [-l logdir] [-h]</p></div></div><div class="refsect1" lang="en"><a name="id2522945"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">vfstest</code> is a small command line
 	utility that has the ability to test dso samba VFS modules. It gives the
 	user the ability to call the various VFS functions manually and
 	supports cascaded VFS modules.
-	</p></div><div class="refsect1" lang="en"><a name="id2483337"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c|--command=command</span></dt><dd><p>Execute the specified (colon-separated) commands.
+	</p></div><div class="refsect1" lang="en"><a name="id2483340"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c|--command=command</span></dt><dd><p>Execute the specified (colon-separated) commands.
 		See below for the commands that are available.
 		</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
@@ -32,10 +32,10 @@ The default configuration file name is determined at
 compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
 log.smbd, etc...). The log file is never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483719"></a><h2>COMMANDS</h2><p><span class="emphasis"><em>VFS COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">load &lt;module.so&gt;</code> - Load specified VFS module </p></li><li><p><code class="literal">populate &lt;char&gt; &lt;size&gt;</code> - Populate a data buffer with the specified data
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483721"></a><h2>COMMANDS</h2><p><span class="emphasis"><em>VFS COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">load &lt;module.so&gt;</code> - Load specified VFS module </p></li><li><p><code class="literal">populate &lt;char&gt; &lt;size&gt;</code> - Populate a data buffer with the specified data
 		</p></li><li><p><code class="literal">showdata [&lt;offset&gt; &lt;len&gt;]</code> - Show data currently in data buffer
-		</p></li><li><p><code class="literal">connect</code> - VFS connect()</p></li><li><p><code class="literal">disconnect</code> - VFS disconnect()</p></li><li><p><code class="literal">disk_free</code> - VFS disk_free()</p></li><li><p><code class="literal">opendir</code> - VFS opendir()</p></li><li><p><code class="literal">readdir</code> - VFS readdir()</p></li><li><p><code class="literal">mkdir</code> - VFS mkdir()</p></li><li><p><code class="literal">rmdir</code> - VFS rmdir()</p></li><li><p><code class="literal">closedir</code> - VFS closedir()</p></li><li><p><code class="literal">open</code> - VFS open()</p></li><li><p><code class="literal">close</code> - VFS close()</p></li><li><p><code class="literal">read</code> - VFS read()</p></li><li><p><code class="literal">write</code> - VFS write()</p></li><li><p><code class="literal">lseek</code> - VFS lseek()</p></li><li><p><code class="literal">rename</code> - VFS rename()</p></li><li><p><code class="literal">fsync</code> - VFS fsync()</p></li><li><p><code class="literal">stat</code> - VFS stat()</p></li><li><p><code class="literal">fstat</code> - VFS fstat()</p></li><li><p><code class="literal">lstat</code> - VFS lstat()</p></li><li><p><code class="literal">unlink</code> - VFS unlink()</p></li><li><p><code class="literal">chmod</code> - VFS chmod()</p></li><li><p><code class="literal">fchmod</code> - VFS fchmod()</p></li><li><p><code class="literal">chown</code> - VFS chown()</p></li><li><p><code class="literal">fchown</code> - VFS fchown()</p></li><li><p><code class="literal">chdir</code> - VFS chdir()</p></li><li><p><code class="literal">getwd</code> - VFS getwd()</p></li><li><p><code class="literal">utime</code> - VFS utime()</p></li><li><p><code class="literal">ftruncate</code> - VFS ftruncate()</p></li><li><p><code class="literal">lock</code> - VFS lock()</p></li><li><p><code class="literal">symlink</code> - VFS symlink()</p></li><li><p><code class="literal">readlink</code> - VFS readlink()</p></li><li><p><code class="literal">link</code> - VFS link()</p></li><li><p><code class="literal">mknod</code> - VFS mknod()</p></li><li><p><code class="literal">realpath</code> - VFS realpath()</p></li></ul></div><p><span class="emphasis"><em>GENERAL COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">conf &lt;smb.conf&gt;</code> - Load a different configuration file</p></li><li><p><code class="literal">help [&lt;command&gt;]</code> - Get list of commands or info about specified command</p></li><li><p><code class="literal">debuglevel &lt;level&gt;</code> - Set debug level</p></li><li><p><code class="literal">freemem</code> - Free memory currently in use</p></li><li><p><code class="literal">exit</code> - Exit vfstest</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481797"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba
-	suite.</p></div><div class="refsect1" lang="en"><a name="id2481808"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+		</p></li><li><p><code class="literal">connect</code> - VFS connect()</p></li><li><p><code class="literal">disconnect</code> - VFS disconnect()</p></li><li><p><code class="literal">disk_free</code> - VFS disk_free()</p></li><li><p><code class="literal">opendir</code> - VFS opendir()</p></li><li><p><code class="literal">readdir</code> - VFS readdir()</p></li><li><p><code class="literal">mkdir</code> - VFS mkdir()</p></li><li><p><code class="literal">rmdir</code> - VFS rmdir()</p></li><li><p><code class="literal">closedir</code> - VFS closedir()</p></li><li><p><code class="literal">open</code> - VFS open()</p></li><li><p><code class="literal">close</code> - VFS close()</p></li><li><p><code class="literal">read</code> - VFS read()</p></li><li><p><code class="literal">write</code> - VFS write()</p></li><li><p><code class="literal">lseek</code> - VFS lseek()</p></li><li><p><code class="literal">rename</code> - VFS rename()</p></li><li><p><code class="literal">fsync</code> - VFS fsync()</p></li><li><p><code class="literal">stat</code> - VFS stat()</p></li><li><p><code class="literal">fstat</code> - VFS fstat()</p></li><li><p><code class="literal">lstat</code> - VFS lstat()</p></li><li><p><code class="literal">unlink</code> - VFS unlink()</p></li><li><p><code class="literal">chmod</code> - VFS chmod()</p></li><li><p><code class="literal">fchmod</code> - VFS fchmod()</p></li><li><p><code class="literal">chown</code> - VFS chown()</p></li><li><p><code class="literal">fchown</code> - VFS fchown()</p></li><li><p><code class="literal">chdir</code> - VFS chdir()</p></li><li><p><code class="literal">getwd</code> - VFS getwd()</p></li><li><p><code class="literal">utime</code> - VFS utime()</p></li><li><p><code class="literal">ftruncate</code> - VFS ftruncate()</p></li><li><p><code class="literal">lock</code> - VFS lock()</p></li><li><p><code class="literal">symlink</code> - VFS symlink()</p></li><li><p><code class="literal">readlink</code> - VFS readlink()</p></li><li><p><code class="literal">link</code> - VFS link()</p></li><li><p><code class="literal">mknod</code> - VFS mknod()</p></li><li><p><code class="literal">realpath</code> - VFS realpath()</p></li></ul></div><p><span class="emphasis"><em>GENERAL COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">conf &lt;smb.conf&gt;</code> - Load a different configuration file</p></li><li><p><code class="literal">help [&lt;command&gt;]</code> - Get list of commands or info about specified command</p></li><li><p><code class="literal">debuglevel &lt;level&gt;</code> - Set debug level</p></li><li><p><code class="literal">freemem</code> - Free memory currently in use</p></li><li><p><code class="literal">exit</code> - Exit vfstest</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481803"></a><h2>VERSION</h2><p>This man page is correct for version 3 of the Samba
+	suite.</p></div><div class="refsect1" lang="en"><a name="id2481814"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p>The vfstest man page was written by Jelmer Vernooij.</p></div></div></body></html>
diff --git a/docs/htmldocs/manpages/wbinfo.1.html b/docs/htmldocs/manpages/wbinfo.1.html
index c8ef185ddf..e07b7aee90 100644
--- a/docs/htmldocs/manpages/wbinfo.1.html
+++ b/docs/htmldocs/manpages/wbinfo.1.html
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>wbinfo</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="wbinfo.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>wbinfo &#8212; Query information from winbind daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">wbinfo</code> [-a user%password] [--all-domains] [--allocate-gid] [--allocate-uid] [-c] [-D domain] [--domain domain] [-g] [--getdcname domain] [--get-auth-user] [-G gid] [-h] [-i user] [-I ip] [-K user%password] [-m] [-n name] [-N netbios-name] [--own-domain] [-p] [-r user] [--remove-uid-mapping uid,sid] [--remove-gid-mapping gid,sid] [-s sid] [--separator] [--sequence] [--set-auth-user user%password] [--set-uid-mapping uid,sid] [--set-gid-mapping gid,sid] [-S sid] [-t] [-u] [--uid-info uid] [--user-domgroups sid] [--user-sids sid] [-U uid] [-V] [-Y sid] [--verbose]</p></div></div><div class="refsect1" lang="en"><a name="id2483698"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">wbinfo</code> program queries and returns information
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>wbinfo</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="wbinfo.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>wbinfo &#8212; Query information from winbind daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">wbinfo</code> [-a user%password] [--all-domains] [--allocate-gid] [--allocate-uid] [-D domain] [--domain domain] [-g] [--getdcname domain] [--get-auth-user] [-G gid] [-h] [-i user] [-I ip] [-K user%password] [-m] [-n name] [-N netbios-name] [--own-domain] [-p] [-r user] [--remove-uid-mapping uid,sid] [--remove-gid-mapping gid,sid] [-s sid] [--separator] [--sequence] [--set-auth-user user%password] [--set-uid-mapping uid,sid] [--set-gid-mapping gid,sid] [-S sid] [-t] [-u] [--uid-info uid] [--user-domgroups sid] [--user-sids sid] [-U uid] [-V] [-Y sid] [--verbose]</p></div></div><div class="refsect1" lang="en"><a name="id2483696"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>The <code class="literal">wbinfo</code> program queries and returns information
 	created and used by the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon. </p><p>The <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon must be configured
 	and running for the <code class="literal">wbinfo</code> program to be able
-	to return information.</p></div><div class="refsect1" lang="en"><a name="id2483754"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-a|--authenticate <em class="replaceable"><code>username%password</code></em></span></dt><dd><p>Attempt to authenticate a user via <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>.
+	to return information.</p></div><div class="refsect1" lang="en"><a name="id2483752"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-a|--authenticate <em class="replaceable"><code>username%password</code></em></span></dt><dd><p>Attempt to authenticate a user via <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>.
                 This checks both authentication methods and reports its results.
 		</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Do not be tempted to use this
 		functionality for authentication in third-party
@@ -9,9 +9,6 @@
 		</p></dd><dt><span class="term">--allocate-uid</span></dt><dd><p>Get a new UID out of idmap
 		</p></dd><dt><span class="term">--all-domains</span></dt><dd><p>List all domains (trusted and
 		own domain).
-		</p></dd><dt><span class="term">-c|--change-secret</span></dt><dd><p>Change the trust account password. May be used
-		in conjunction with <code class="option">domain</code> in order to change
-		interdomain trust account passwords.
 		</p></dd><dt><span class="term">--domain <em class="replaceable"><code>name</code></em></span></dt><dd><p>This parameter sets the domain on which any specified
 		operations will performed.  If special domain name '.' is used to represent
 		the current domain to which <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> belongs.  Currently only the
@@ -69,9 +66,7 @@
 		</p></dd><dt><span class="term">-S|--sid-to-uid <em class="replaceable"><code>sid</code></em></span></dt><dd><p>Convert a SID to a UNIX user id.  If the SID
 		does not correspond to a UNIX user mapped by <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> then the operation will fail. </p></dd><dt><span class="term">-t|--check-secret</span></dt><dd><p>Verify that the workstation trust account
 		created when the Samba server is added to the Windows NT
-		domain is working. May be used in conjunction with
-		<code class="option">domain</code> in order to verify interdomain
-		trust accounts.</p></dd><dt><span class="term">-u|--domain-users</span></dt><dd><p>This option will list all users available
+		domain is working. </p></dd><dt><span class="term">-u|--domain-users</span></dt><dd><p>This option will list all users available
 		in the Windows NT domain for which the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon is operating in. Users in all trusted domains
 		will also be listed.  Note that this operation does not assign
 		user ids to any users that have not already been seen by <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a>
@@ -90,10 +85,10 @@
 		mapping in the IDmap backend.</p></dd><dt><span class="term">--set-gid-mapping gid,sid</span></dt><dd><p>Create a new or modify an existing gid to sid
 		mapping in the IDmap backend.</p></dd><dt><span class="term">-V|--version</span></dt><dd><p>Prints the program version number.
 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532652"></a><h2>EXIT STATUS</h2><p>The wbinfo program returns 0 if the operation
+</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532629"></a><h2>EXIT STATUS</h2><p>The wbinfo program returns 0 if the operation
 	succeeded, or 1 if the operation failed.  If the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon is not working <code class="literal">wbinfo</code> will always return
-	failure. </p></div><div class="refsect1" lang="en"><a name="id2532678"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
-	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532688"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> and <a class="citerefentry" href="ntlm_auth.1.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(1)</span></a></p></div><div class="refsect1" lang="en"><a name="id2532711"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+	failure. </p></div><div class="refsect1" lang="en"><a name="id2532654"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
+	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532665"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> and <a class="citerefentry" href="ntlm_auth.1.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(1)</span></a></p></div><div class="refsect1" lang="en"><a name="id2532688"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p><code class="literal">wbinfo</code> and <code class="literal">winbindd</code>
diff --git a/docs/htmldocs/manpages/winbind_krb5_locator.7.html b/docs/htmldocs/manpages/winbind_krb5_locator.7.html
index 2a8080f872..a1833202c2 100644
--- a/docs/htmldocs/manpages/winbind_krb5_locator.7.html
+++ b/docs/htmldocs/manpages/winbind_krb5_locator.7.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbind_krb5_locator</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbind_krb5_locator.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbind_krb5_locator &#8212; A plugin for MIT and Heimdal Kerberos for detecting KDCs using Windows semantics.</p></div><div class="refsect1" lang="en"><a name="id2522893"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbind_krb5_locator</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbind_krb5_locator.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbind_krb5_locator &#8212; A plugin for MIT and Heimdal Kerberos for detecting KDCs using Windows semantics.</p></div><div class="refsect1" lang="en"><a name="id2522895"></a><h2>DESCRIPTION</h2><p>
 	This plugin is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.
 	</p><p>
 		<code class="literal">winbind_krb5_locator</code> is a plugin that permits MIT and
@@ -8,7 +8,7 @@
 		of closest dc.
 		The plugin uses the public locator API provided by most modern Kerberos
 		implementations.
-	</p></div><div class="refsect1" lang="en"><a name="id2522925"></a><h2>PREREQUISITES</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2522928"></a><h2>PREREQUISITES</h2><p>
 		MIT Kerberos (at least version 1.5) or Heimdal Kerberos (at least version
 		1.0) is required.
 	</p><p>
@@ -32,9 +32,9 @@
 		Users should be able to kinit into their kerberized Windows
 		environment without any modification or servers
 		being put manually into <code class="filename">/etc/krb5.conf</code>.
-	</p></div><div class="refsect1" lang="en"><a name="id2483356"></a><h2>VERSION</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483376"></a><h2>VERSION</h2><p>
 	This man page is correct for version 3 of the Samba suite.
-	</p></div><div class="refsect1" lang="en"><a name="id2483368"></a><h2>AUTHOR</h2><p>
+	</p></div><div class="refsect1" lang="en"><a name="id2483387"></a><h2>AUTHOR</h2><p>
 		The original Samba software and related utilities were created by Andrew
 		Tridgell. Samba is now developed by the Samba Team as an Open Source
 		project similar to the way the Linux kernel is developed.
diff --git a/docs/htmldocs/manpages/winbindd.8.html b/docs/htmldocs/manpages/winbindd.8.html
index 64c7f5409d..3ac65897cc 100644
--- a/docs/htmldocs/manpages/winbindd.8.html
+++ b/docs/htmldocs/manpages/winbindd.8.html
@@ -1,5 +1,5 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbindd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbindd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbindd &#8212; Name Service Switch daemon for resolving names
-	from NT servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">winbindd</code> [-D] [-F] [-S] [-i] [-Y] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</p></div></div><div class="refsect1" lang="en"><a name="id2483339"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">winbindd</code> is a daemon that provides
+	from NT servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">winbindd</code> [-D] [-F] [-S] [-i] [-Y] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</p></div></div><div class="refsect1" lang="en"><a name="id2483342"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">winbindd</code> is a daemon that provides
 	a number of services to the Name Service Switch capability found
 	in most modern C libraries, to arbitrary applications via PAM
 	and <code class="literal">ntlm_auth</code> and to Samba itself.</p><p>Even if winbind is not used for nsswitch, it still provides a
@@ -60,7 +60,7 @@ hosts:          files dns wins
 	resolve hostnames from <code class="filename">/etc/hosts</code> and then from the
 	WINS server.</p><pre class="programlisting">
 hosts:		files wins
-</pre></div><div class="refsect1" lang="en"><a name="id2481543"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
+</pre></div><div class="refsect1" lang="en"><a name="id2481549"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
 		the main <code class="literal">winbindd</code> process to not daemonize,
 		i.e. double-fork and disassociate with the terminal.
 		Child processes are still created as normal to service
@@ -113,7 +113,7 @@ log.smbd, etc...). The log file is never removed by the client.
 		as a single process (the mode of operation in Samba 2.2).  Winbindd's
 		default behavior is to launch a child process that is responsible for
 		updating expired cache entries.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481802"></a><h2>NAME AND ID RESOLUTION</h2><p>Users and groups on a Windows NT server are assigned
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481808"></a><h2>NAME AND ID RESOLUTION</h2><p>Users and groups on a Windows NT server are assigned
 	a security id (SID) which is globally unique when the
 	user or group is created.  To convert the Windows NT user or group
 	into a unix user or group, a mapping between SIDs and unix user
@@ -127,7 +127,7 @@ log.smbd, etc...). The log file is never removed by the client.
 	where the user and group mappings are stored by winbindd.  If this
 	store is deleted or corrupted, there is no way for winbindd to
 	determine which user and group ids correspond to Windows NT user
-	and group rids. </p></div><div class="refsect1" lang="en"><a name="id2481840"></a><h2>CONFIGURATION</h2><p>Configuration of the <code class="literal">winbindd</code> daemon
+	and group rids. </p></div><div class="refsect1" lang="en"><a name="id2481846"></a><h2>CONFIGURATION</h2><p>Configuration of the <code class="literal">winbindd</code> daemon
 	is done through configuration parameters in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.  All parameters should be specified in the
 	[global] section of smb.conf. </p><div class="itemizedlist"><ul type="disc"><li><p>
 		<a class="link" href="smb.conf.5.html#WINBINDSEPARATOR" target="_top">winbind separator</a></p></li><li><p>
@@ -144,7 +144,7 @@ log.smbd, etc...). The log file is never removed by the client.
 		Setting this parameter forces winbindd to use RPC
 		instead of LDAP to retrieve information from Domain
 		Controllers.
-		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2532496"></a><h2>EXAMPLE SETUP</h2><p>
+		</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2532502"></a><h2>EXAMPLE SETUP</h2><p>
 	To setup winbindd for user and group lookups plus
 	authentication from a domain controller use something like the
 	following setup. This was tested on an early Red Hat Linux box.
@@ -195,7 +195,7 @@ auth  required    /lib/security/pam_unix.so \
 	and that you can login to your unix box as a domain user, using
 	the DOMAIN+user syntax for the username. You may wish to use the
 	commands <code class="literal">getent passwd</code> and <code class="literal">getent group
-	</code> to confirm the correct operation of winbindd.</p></div><div class="refsect1" lang="en"><a name="id2532687"></a><h2>NOTES</h2><p>The following notes are useful when configuring and
+	</code> to confirm the correct operation of winbindd.</p></div><div class="refsect1" lang="en"><a name="id2532693"></a><h2>NOTES</h2><p>The following notes are useful when configuring and
 	running <code class="literal">winbindd</code>: </p><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> must be running on the local machine
 	for <code class="literal">winbindd</code> to work. </p><p>PAM is really easy to misconfigure.  Make sure you know what
 	you are doing when modifying PAM configuration files.  It is possible
@@ -203,7 +203,7 @@ auth  required    /lib/security/pam_unix.so \
 	then in general the user and groups ids allocated by winbindd will not
 	be the same.  The user and group ids will only be valid for the local
 	machine, unless a shared <a class="link" href="smb.conf.5.html#IDMAPBACKEND" target="_top">idmap backend</a> is configured.</p><p>If the the Windows NT SID to UNIX user and group id mapping
-	file is damaged or destroyed then the mappings will be lost. </p></div><div class="refsect1" lang="en"><a name="id2532752"></a><h2>SIGNALS</h2><p>The following signals can be used to manipulate the
+	file is damaged or destroyed then the mappings will be lost. </p></div><div class="refsect1" lang="en"><a name="id2532758"></a><h2>SIGNALS</h2><p>The following signals can be used to manipulate the
 	<code class="literal">winbindd</code> daemon. </p><div class="variablelist"><dl><dt><span class="term">SIGHUP</span></dt><dd><p>Reload the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file and
 		apply any parameter changes to the running
 		version of winbindd.  This signal also clears any cached
@@ -211,7 +211,7 @@ auth  required    /lib/security/pam_unix.so \
 		by winbindd is also reloaded.  </p></dd><dt><span class="term">SIGUSR2</span></dt><dd><p>The SIGUSR2 signal will cause <code class="literal">
 		winbindd</code> to write status information to the winbind
 		log file.</p><p>Log files are stored in the filename specified by the
-		log file parameter.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532815"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/nsswitch.conf(5)</code></span></dt><dd><p>Name service switch configuration file.</p></dd><dt><span class="term">/tmp/.winbindd/pipe</span></dt><dd><p>The UNIX pipe over which clients communicate with
+		log file parameter.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532821"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/nsswitch.conf(5)</code></span></dt><dd><p>Name service switch configuration file.</p></dd><dt><span class="term">/tmp/.winbindd/pipe</span></dt><dd><p>The UNIX pipe over which clients communicate with
 		the <code class="literal">winbindd</code> program.  For security reasons, the
 		winbind client will only attempt to connect to the winbindd daemon
 		if both the <code class="filename">/tmp/.winbindd</code> directory
@@ -232,8 +232,8 @@ auth  required    /lib/security/pam_unix.so \
 		compiled using the <em class="parameter"><code>--with-lockdir</code></em> option.
 		This directory is by default <code class="filename">/usr/local/samba/var/locks
 		</code>. </p></dd><dt><span class="term">$LOCKDIR/winbindd_cache.tdb</span></dt><dd><p>Storage for cached user and group information.
-		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532961"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
-        the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532971"></a><h2>SEE ALSO</h2><p><code class="filename">nsswitch.conf(5)</code>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="ntlm_auth.8.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2533027"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
+		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2532966"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
+        the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532977"></a><h2>SEE ALSO</h2><p><code class="filename">nsswitch.conf(5)</code>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="ntlm_auth.8.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id2533033"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar
 	to the way the Linux kernel is developed.</p><p><code class="literal">wbinfo</code> and <code class="literal">winbindd</code> were
diff --git a/docs/htmldocs/using_samba/appa.html b/docs/htmldocs/using_samba/appa.html
new file mode 100644
index 0000000000..9f3dc4b56f
--- /dev/null
+++ b/docs/htmldocs/using_samba/appa.html
@@ -0,0 +1,362 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76" 
+hspace="10" align="left" />
+<h1 class="head0">Appendix A. Example Configuration Files</h1>
+
+
+<p>Earlier in this book, we provided information on how to set
+parameters inside the Samba configuration file, but rarely have we
+shown an example of a complete file that can actually be used to run
+a server. In this appendix, we provide examples of complete
+configuration files for running Samba in the various modes
+we've discussed. Using one of these examples, you
+can run Samba as a workgroup authentication server, workgroup server,
+primary domain controller, or domain member server.</p>
+
+<p>We have kept the examples simple so that they have the most universal
+application. They can be used as starting templates, which you can
+easily modify to fit your own needs, to get a Samba server up and
+running with minimal delay. The comments inside the files indicate
+what needs to be changed, and how, to work on a particular system on
+your network.</p>
+
+
+
+<div class="sect1"><a name="samba2-APP-A-SECT-1"/>
+
+<h2 class="head1">Samba in a Workgroup</h2>
+
+<p>If your network is configured as a workgroup, adding a Samba server
+is pretty simple. Samba even lets you add features, such as
+user-level security and WINS, that would normally require an
+expensive Windows NT/2000 Server.</p>
+
+
+<div class="sect2"><a name="samba2-APP-A-SECT-1.1"/>
+
+<h3 class="head2">Authentication and WINS Server</h3>
+
+<p>In a workgroup environment, Samba can be set up with share-level
+security and without offering WINS name service. This works and is
+simple, but we generally recommend that user-level security be
+enabled to allow Windows 95/98/Me systems to make use of it. Also, it
+only takes a single parameter to enable Samba as a WINS server,
+resulting in far better network efficiency.
+<a name="INDEX-1"/><a name="INDEX-2"/><a name="INDEX-3"/>Here is the configuration file
+that does it:</p>
+
+<blockquote><pre class="code">[global]
+    # replace &quot;toltec&quot; with your system's hostname
+
+    netbios name = toltec
+
+    # replace &quot;METRAN&quot; with the name of your workgroup
+
+    workgroup = METRAN
+
+    security = user
+    encrypt passwords = yes
+
+    # Run a WINS server
+
+    wins support = yes
+
+    # The following three lines ensure that the Samba
+    # server will maintain the role of master browser.
+    # Make sure no other Samba server has its OS level
+    # set higher than it is here.
+
+    local master = yes
+    preferred master = yes
+    os level = 65
+
+# Make home directories on the server available to users.
+
+[homes]
+    comment = %u's Home Directory
+    browsable = no
+    read only = no
+    map archive = yes
+
+# This is a shared directory, accessible by all
+# users. Use your own share name and path.
+
+[d]
+    path = /d
+    create mask = 0700
+    read only = no</pre></blockquote>
+
+<p>Generally, you will use a configuration file similar to this one when
+<a name="INDEX-4"/><a name="INDEX-5"/>adding your first Samba server to the
+workgroup.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-A-SECT-1.2"/>
+
+<h3 class="head2">Workgroup Server</h3>
+
+<p><a name="INDEX-6"/><a name="INDEX-7"/>Things are a
+little different if another system&mdash;either a Samba server or
+Windows NT/2000 server&mdash;is already handling WINS and/or
+authentication. In this case, Samba is configured to use that server
+for WINS. Here is a configuration file that does this:</p>
+
+<blockquote><pre class="code">[global]
+    # replace &quot;mixtec&quot; with your system's hostname
+
+    netbios name = mixtec
+
+    # replace &quot;METRAN&quot; with your workgroup name
+
+    workgroup = METRAN
+
+    security = user
+    encrypt passwords = yes
+
+    # Replace &quot;172.16.1.1&quot; with the IP address
+    # of your WINS server. If there is none,
+    # omit this line.
+
+    wins server = 172.16.1.1
+
+    # The OS level is set to 17 to allow
+    # this system to win over all Windows
+    # versions, but not the Samba server 
+    # that uses the configuration file
+    # in the previous section.
+
+    os level = 17
+
+[homes]
+    comment = %u's Home Directory
+    browsable = no
+    read only = no
+
+# This is a shared directory, accessible by all
+# users. Use your own share name and path.
+
+[d]
+    path = /d
+    create mask = 0700
+    read only = no</pre></blockquote>
+
+<p>Once you have a server in your workgroup handling authentication and
+WINS, this is the configuration file to use when adding additional
+Samba servers to the workgroup.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-APP-A-SECT-2"/>
+
+<h2 class="head1">Samba in a Windows NT Domain</h2>
+
+<p>When operating in a Windows NT domain, Samba can act either as a
+primary domain controller or as a domain member server.</p>
+
+
+<div class="sect2"><a name="samba2-APP-A-SECT-2.1"/>
+
+<h3 class="head2">Primary Domain Controller</h3>
+
+<p><a name="INDEX-8"/><a name="INDEX-9"/>Setting up Samba as a primary domain
+controller is more complicated than the other configurations.
+However, the extra difficulty is offset by having a more secure
+network and additional features such as logon scripts and roaming
+profiles. In the following configuration file, we also include
+support for a Microsoft Dfs share:</p>
+
+<blockquote><pre class="code">[global]
+    # Replace &quot;toltec&quot; with the hostname of your system.
+
+    netbios name = toltec
+
+    # Replace &quot;METRAN&quot; with the name of your Windows NT domain.
+
+    workgroup = METRAN
+
+    # Run a WINS server
+
+    wins support = yes
+    
+    # Always act as the local master browser
+    # and domain master browser.  Do not allow
+    # any other system to take over these roles!
+
+    domain master = yes
+    local master = yes
+    preferred master = yes
+    os level = 255
+
+    # Perform domain authentication.
+
+    security = user
+    encrypt passwords = yes
+    domain logons = yes
+    
+    # The location of user profiles for Windows NT/2000/XP.
+
+    logon path = \\%L\profiles\%u\%m
+
+    # Users' Windows home directories and storage of Win95/98/Me roaming profiles.
+
+    logon drive = G:
+    logon home = \\toltec\%u\.win_profile\%m
+
+    # The following line is optional because
+    # Samba always offers NetBIOS time service.
+    # This causes it to also be advertised:
+
+    time server = yes
+
+    # The logon script used for all users,
+    # Relative to [netlogon] share directory.
+
+    logon script = logon.bat
+
+    # The group identifying administrative users.
+    # If you have domain users in the Domain Admins
+    # group, use them here instead of &quot;jay&quot;.
+
+    domain admin group = root jay
+
+    # For adding machine accounts automatically.
+    # This example works on Linux. For other host
+    # operating systems, you might need a different
+    # command.
+
+    add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
+
+    # Provide Microsoft Dfs support.
+
+    host msdfs = yes
+
+# The netlogon share is required for
+# functioning as the primary domain controller.
+# Make sure the directory used for the path exists.
+
+[netlogon]
+    path = /usr/local/samba/lib/netlogon
+    writable = no
+    browsable = no
+
+# The profiles share is for storing
+# Windows NT/2000/XP roaming profiles.
+# Use your own path, and make sure
+# the directory exists.
+
+[profiles]
+    path = /home/samba-ntprof
+    writable = yes
+    create mask = 0600
+    directory mask = 0700
+    browsable = no
+
+[homes]
+    comment = Home Directory
+    browsable = no
+    read only = no
+    map archive = yes
+
+# The Dfs share.
+# Use your own path, making
+# sure the directory exists.
+
+[dfs]
+    comment = Dfs share
+    path = /usr/local/samba/dfs
+    msdfs root = yes
+
+# A shared directory, accessible by all domain users.
+# Use your own share name and path.
+
+[d]
+    comment = %u's Home Directory
+    path = /d
+    create mask = 0700
+    read only = no</pre></blockquote>
+
+<p>See <a href="ch04.html">Chapter 4</a> for more information on configuring
+Samba as a primary domain controller, and see <a href="ch08.html">Chapter 8</a> for more information about setting up a
+Microsoft Dfs share. <a name="INDEX-10"/><a name="INDEX-11"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-A-SECT-2.2"/>
+
+<h3 class="head2">Domain Member Server</h3>
+
+<p><a name="INDEX-12"/><a name="INDEX-13"/>In a domain that
+already has either a Samba PDC or Windows NT/2000 Server PDC,
+additional Samba servers can be added as domain member servers using
+the following configuration file:</p>
+
+<blockquote><pre class="code">[global]
+    # Replace &quot;mixtec&quot; with the system's hostname.
+
+    netbios name = mixtec
+
+    # Replace &quot;METRAN&quot; with the name of your domain.
+
+    workgroup = METRAN
+
+    # Replace &quot;172.16.1.1&quot; with the
+    # IP address of your WINS server.
+
+    wins server = 172.16.1.1
+
+    os level = 33
+    
+    security = domain
+    encrypt passwords = yes
+    password server = *
+
+# Home directories.
+
+[homes]
+    comment = %u's Home Directory
+    browsable = no
+    read only = no
+    map archive = yes
+
+# This is an example printers
+# share, which works for Linux.
+
+[printers]
+    printable = yes
+    printing = BSD
+    print command = /usr/bin/lpr -P%p %s
+    path = /var/tmp
+    min print space = 2000
+
+# A shared directory, accessible by all domain users.
+# Use your own share name and path.
+
+[d]
+    path = /d
+    create mask = 0755
+    read only = no</pre></blockquote>
+
+<p>See <a href="ch10.html">Chapter 10</a> for more information on sharing
+printers with Samba.</p>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/appb.html b/docs/htmldocs/using_samba/appb.html
new file mode 100644
index 0000000000..9cb6d957a8
--- /dev/null
+++ b/docs/htmldocs/using_samba/appb.html
@@ -0,0 +1,1840 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix B. Samba Configuration Option Quick Reference</h1>
+
+
+<p>The first section of this appendix lists each option that can be used
+in a Samba configuration file, which is usually named
+<em class="filename">smb.conf</em>. Most configuration files contain a
+global section of options that apply to all services (shares) and a
+separate section for various individual shares. If an option applies
+only to the global section, <tt class="literal">[global]</tt> appears to
+the right of its name in the following reference section.</p>
+
+<p>Except where noted, when specifying elements of a list, the elements
+can be separated by spaces, tabs, commas, semicolons, escaped
+newlines, or escaped carriage returns.</p>
+
+<p>Following this reference section is a glossary of value types, and a
+list of variables Samba recognizes.</p>
+
+
+
+<div class="sect1"><a name="samba2-APP-B-SECT-1"/>
+
+<h2 class="head1">Configuration File Options</h2>
+
+</div>
+
+
+<a name="INDEX-1"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>abort shutdown script = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that stops the shutdown procedure started by
+<tt class="literal">shutdown script</tt>. The command will be run with the
+UID of the connected user. New in Samba 3.0.</p></div>
+<a name="INDEX-2"/><a name="INDEX-3"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>add printer command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that creates a new
+<a name="INDEX-3"/>printer on the system hosting the Samba
+server. This command runs as <tt class="literal">root</tt> when the Windows
+NT/2000/XP Add Printer Wizard is run. The command will be passed a
+printer name, share name, port name, driver name, Windows NT/2000/XP
+driver location, and Windows 95/98/Me driver location, in that order.
+It will need to add the printer to the system and a share definition
+for the printer to <em class="filename">smb.conf.</em> See also
+<tt class="literal">add printer wizard</tt>, <tt class="literal">printing</tt>,
+and <tt class="literal">show add printer wizard</tt>.</p></div>
+<a name="INDEX-4"/><a name="INDEX-5"/><a name="INDEX-6"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>add machine script = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that adds a computer to the Samba
+server's <a name="INDEX-5"/><a name="INDEX-6"/>domain. New in Samba 3.0.</p></div>
+<a name="INDEX-7"/><a name="INDEX-8"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>add share command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that creates a new
+<a name="INDEX-8"/>share on the Samba server. This command
+runs as <tt class="literal">root</tt> when a share is created using the
+Windows NT/2000/XP Server Manager. The client user must be logged on
+as the <tt class="literal">root</tt> user. The command will be passed the
+name of the Samba configuration file, the name of the share to be
+created, the full pathname of a directory on the Samba server (which
+must already exist), and a string to use as a comment for the share,
+in that order. The command must add a share definition for the share
+to <em class="filename">smb.conf.</em> See also <tt class="literal">add printer
+command</tt>, for adding a print share.</p></div>
+<a name="INDEX-9"/><a name="INDEX-10"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>add user script = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that creates a new
+<a name="INDEX-10"/>user on the system hosting the Samba
+server. This command runs as <tt class="literal">root</tt> when access to a
+Samba share is attempted by a Windows user who does not have an
+account on the hosting system, but does have an account maintained by
+a primary domain controller on a different system. The command should
+accept the name of the user as a single argument that matches the
+behavior of typical <em class="emphasis">adduser</em> commands. Samba
+honors the <tt class="literal">%u</tt> value (username) as the argument to
+the command. Requires <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">server</tt> or
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">domain</tt>. See also <tt class="literal">delete user</tt>
+<tt class="literal">script</tt>.</p></div>
+<a name="INDEX-11"/><a name="INDEX-12"/><a name="INDEX-13"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>admin users = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p><a name="INDEX-12"/>Specifies users who will be granted
+<a name="INDEX-13"/><tt class="literal">root</tt>
+permissions on the share by Samba.</p></div>
+<a name="INDEX-14"/><a name="INDEX-15"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ads server = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: DNS hostname or IP address</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Specifies the <a name="INDEX-15"/>Active Directory server, used by
+Samba 3.0 for authenticating clients. Requires
+<tt class="literal">security</tt> <tt class="literal">= ads</tt>. New in Samba
+3.0.</p></div>
+<a name="INDEX-16"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>algorithmic rid base = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive integer</p><p><b class="emphasis-bold">Default</b>: 1000</p><p>Specifies the base value that Samba uses when calculating Windows
+domain security identifier equivalents to Unix UIDs. See also
+<tt class="literal">non unix account range</tt>. New in Samba 3.0.</p></div>
+<a name="INDEX-17"/><a name="INDEX-18"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>allow hosts = host list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies systems that can connect to the share or
+<a name="INDEX-18"/>shares. If NULL, any
+system can access the share unless there is a <tt class="literal">hosts
+deny</tt> option. Synonym for <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt>.</p></div>
+<a name="INDEX-19"/><a name="INDEX-20"/><a name="INDEX-21"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>allow trusted domains = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows access to users who lack accounts on the Samba server but have
+accounts in another, trusted <a name="INDEX-20"/><a name="INDEX-21"/>domain.
+Requires <tt class="literal">security</tt> <tt class="literal">= server</tt> or
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">domain</tt>.</p></div>
+<a name="INDEX-22"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>announce as = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NT, Win95, Wf W</p><p><b class="emphasis-bold">Default</b>: NT</p><p>Has Samba announce itself as something other than an NT server.
+Discouraged because it interferes with serving browse lists.</p></div>
+<a name="INDEX-23"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>announce version = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: two numbers separated by a dot character</p><p><b class="emphasis-bold">Default</b>: 4.5</p><p>Instructs Samba to announce itself as a different version SMB server.
+Discouraged.</p></div>
+<a name="INDEX-24"/><a name="INDEX-25"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>auth methods = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: guest, sam, ntdomain</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Specifies what methods Samba tries in turn to
+<a name="INDEX-25"/>authenticate users. New in Samba
+3.0.</p></div>
+<a name="INDEX-26"/><a name="INDEX-27"/><a name="INDEX-28"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>auto services = service list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: service list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of <a name="INDEX-27"/><a name="INDEX-28"/>shares that always appear in
+browse lists. Also called <tt class="literal">preload</tt>.</p></div>
+<a name="INDEX-29"/><a name="INDEX-30"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>available = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to NO, denies access to a share. The
+<a name="INDEX-30"/>share appears in the browse list, but
+attempts to access it will fail.</p></div>
+<a name="INDEX-31"/><a name="INDEX-32"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>bind interfaces only = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, shares and browsing are provided only on interfaces in
+an <a name="INDEX-32"/>interfaces list (see
+<tt class="literal">interfaces</tt>). If you set this option to YES, be
+sure to add 127.0.0.1 to the interfaces list to allow
+<em class="emphasis">smbpasswd</em> to connect to the local system to
+change passwords. This is a convenience option; it does not improve
+security.</p></div>
+<a name="INDEX-33"/><a name="INDEX-34"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>block size = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer</p><p><b class="emphasis-bold">Default</b>: 1024</p><p>Sets the size of disk blocks as reported by <em class="emphasis">smbd</em>
+to the client. <a name="INDEX-34"/>Obsolete
+starting with Samba 3.0.</p></div>
+<a name="INDEX-35"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>blocking locks = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, honors byte range lock requests with time limits. Samba will
+queue the requests and retry them until the time period expires.</p></div>
+<a name="INDEX-36"/><a name="INDEX-37"/><a name="INDEX-38"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>browsable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p><a name="INDEX-37"/><a name="INDEX-38"/>Allows a share to be announced
+in browse lists. Also called <tt class="literal">browseable</tt>.</p></div>
+<a name="INDEX-39"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>browse list = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, serves the browse list to other systems on the network. Avoid
+changing.</p></div>
+<a name="INDEX-40"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>browseable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Synonym for <tt class="literal">browsable</tt>.</p></div>
+<a name="INDEX-41"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>case sensitive = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, uses the exact case the client supplied when trying to
+resolve a filename. If NO, matches either upper- or lowercase name.
+Avoid changing. Also called <tt class="literal">casesignames</tt>.</p></div>
+<a name="INDEX-42"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>casesignames = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Synonym for <tt class="literal">case</tt> <tt class="literal">sensitive</tt>.</p></div>
+<a name="INDEX-43"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>change notify timeout = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive number</p><p><b class="emphasis-bold">Default</b>: 60</p><p>Sets the number of seconds between checks when a client asks for
+notification of changes in a directory. Avoid lowering.</p></div>
+<a name="INDEX-44"/><a name="INDEX-45"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>change share command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that modifies a
+<a name="INDEX-45"/>share
+definition on the Samba server. This command runs as
+<tt class="literal">root</tt> when a share is created using the Windows
+NT/2000/XP Server Manager. The client user must be logged on as the
+<tt class="literal">root</tt> user. The command is passed the name of the
+Samba configuration file, the name of the share to be modified, the
+full pathname of a directory on the Samba server (which must already
+exist), and a string to use as a comment for the share, in that
+order. The command modifies the share definition for the share in
+<em class="filename">smb.conf.</em> See also <tt class="literal">add share
+command</tt> and <tt class="literal">delete share command</tt>.</p></div>
+<a name="INDEX-46"/><a name="INDEX-47"/><a name="INDEX-48"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>character set = name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: ISO8859-1, ISO8859-2, ISO8859-5, KOI8-R</p><p><b class="emphasis-bold">Default</b>: NULL</p><p><a name="INDEX-47"/>If set, translates from DOS code
+pages to the Western European (ISO8859-1), Eastern European
+(ISO8859-2), Russian Cyrillic (ISO8859-5), or Alternate Russian
+(KOI8-R) character set. The <tt class="literal">client</tt>
+<tt class="literal">code</tt> <tt class="literal">page</tt> option must be set to
+850. <a name="INDEX-48"/>Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-49"/><a name="INDEX-50"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>client code page = name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: see <a href="ch11.html#samba2-CHP-11-TABLE-4">Table 11-4</a> in <a href="ch11.html">Chapter 11</a></p><p><b class="emphasis-bold">Default</b>: 850 (MS-DOS Latin 1)</p><p>Sets the DOS code page explicitly, overriding any previous
+<tt class="literal">valid</tt> <tt class="literal">chars</tt> settings. Examples
+of values are 850 for Western European, 437 for the U.S. standard,
+and 932 for Japanese Shift-JIS. <a name="INDEX-50"/>Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-51"/><a name="INDEX-52"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>code page directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full directory name</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/samba/lib/codepages</em></p><p>Specifies the directory that stores code pages.
+<a name="INDEX-52"/>Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-53"/><a name="INDEX-54"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>coding system = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: euc, cap, hex, hexN, sjis, j8bb, j8bj, jis8, j8bh,
+j8@b, j8@j,j8@h, j7bb, j7bj, jis7, j7bh, j7@b, j7@j, j7@h, jubb,
+jubj, junet, jubh, ju@b, ju@j, ju@h</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the coding system used, notably for Kanji. This is employed for
+filenames and should correspond to the code page in use. The
+<tt class="literal">client</tt> <tt class="literal">code</tt>
+<tt class="literal">page</tt> option must be set to 932 ( Japanese
+Shift-JIS). <a name="INDEX-54"/>Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-55"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>comment = string</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: string</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the comment corresponding to a share. The comment appears in
+places such as a <em class="emphasis">net view</em> listing or through the
+Network Neighborhood. See also the <tt class="literal">server</tt>
+<tt class="literal">string</tt> configuration option.</p></div>
+<a name="INDEX-56"/><a name="INDEX-57"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>config file = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: \filename</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Selects a new Samba <a name="INDEX-57"/>configuration file to read instead of the
+current one. Used to relocate the configuration file or used with
+<tt class="literal">%</tt> variables to select custom configuration files
+for some users or systems.</p></div>
+<a name="INDEX-58"/><a name="INDEX-59"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>copy = section name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: existing section's name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Copies the configuration of an already defined share into the
+<a name="INDEX-59"/>share in which this option
+appears. Used with <tt class="literal">%</tt> variables to select custom
+configurations for systems, architectures, and users. Each option
+specified or copied takes precedence over earlier specifications of
+the option.</p></div>
+<a name="INDEX-60"/><a name="INDEX-61"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>create mask = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0744</p><p>Sets the maximum allowable <a name="INDEX-61"/>permissions for new files (e.g.,
+0755). See also <tt class="literal">directory</tt> <tt class="literal">mask</tt>.
+To require certain permissions to be set, see
+<tt class="literal">force</tt> <tt class="literal">create</tt>
+<tt class="literal">mask</tt> and <tt class="literal">force</tt>
+<tt class="literal">directory</tt> <tt class="literal">mask</tt>. Also called
+<tt class="literal">create</tt> <tt class="literal">mode</tt>.</p></div>
+<a name="INDEX-62"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>create mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0744</p><p>Synonym for <tt class="literal">create</tt> <tt class="literal">mask</tt>.</p></div>
+<a name="INDEX-63"/><a name="INDEX-64"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>csc policy = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: manual, documents, programs, or disable</p><p><b class="emphasis-bold">Default</b>: manual</p><p>Sets the client-side <a name="INDEX-64"/>caching policy, telling them how to
+cache files offline if they are capable of doing so.</p></div>
+<a name="INDEX-65"/><a name="INDEX-66"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>deadtime = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Specifies the time in minutes before an unused
+<a name="INDEX-66"/>connection will be
+terminated. Zero means never. Used to keep clients from tying up
+server resources for long periods of time. If used, clients must
+autoreconnect after the specified period of inactivity. See also
+<tt class="literal">keepalive</tt>.</p></div>
+<a name="INDEX-67"/><a name="INDEX-68"/><a name="INDEX-69"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>debug hires timestamp = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Changes the <a name="INDEX-68"/><a name="INDEX-69"/>timestamps in log entries from seconds
+to microseconds. Useful for measuring performance.</p></div>
+<a name="INDEX-70"/><a name="INDEX-71"/><a name="INDEX-72"/><a name="INDEX-73"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>debug pid = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Adds the process ID of the Samba server to <a name="INDEX-71"/><a name="INDEX-72"/><a name="INDEX-73"/>log lines, making it easier to
+debug a particular server. Requires debug <tt class="literal">timestamp =
+yes</tt> to work.</p></div>
+<a name="INDEX-74"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>debug timestamp = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Timestamps all log messages. Can be turned off when
+it's not useful (e.g., in debugging ). Also called
+<tt class="literal">timestamp</tt> <tt class="literal">logs</tt>.</p></div>
+<a name="INDEX-75"/><a name="INDEX-76"/><a name="INDEX-77"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>debug uid = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p><a name="INDEX-76"/><a name="INDEX-77"/>Adds the real and effective
+user ID and group ID of the user being served to the logs, making it
+easier to debug one particular user.</p></div>
+<a name="INDEX-78"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>debuglevel = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Sets the logging level used. Values of 3 or more slow Samba
+noticeably. Also called <tt class="literal">log</tt>
+<tt class="literal">level</tt>. Recommended value is 1.</p></div>
+<a name="INDEX-79"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>default = service name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: share name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies the name of a service (share) to provide if someone
+requests a service he doesn't have permission to use
+or that doesn't exist. The path is set from the name
+the client specified, with any underscore ( _ ) characters changed to
+slash ( / ) characters, allowing access to any directory on the Samba
+server. Use is discouraged. See also <tt class="literal">load
+printers</tt>. Also called <tt class="literal">default service</tt>.</p></div>
+<a name="INDEX-80"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>default case = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: LOWER, UPPER</p><p><b class="emphasis-bold">Default</b>: LOWER</p><p>Sets the case in which to store new filenames. LOWER indicates
+lowercase, and UPPER indicates uppercase.</p></div>
+<a name="INDEX-81"/><a name="INDEX-82"/><a name="INDEX-83"/><a name="INDEX-84"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>default devmode = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Used with printer shares being accessed by Windows NT/2000/XP clients
+to set a default device mode for the
+<a name="INDEX-82"/><a name="INDEX-83"/><a name="INDEX-84"/>printer. Can be
+problematic. Use with care.</p></div>
+<a name="INDEX-85"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>default service = share name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: share name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">default</tt>.</p></div>
+<a name="INDEX-86"/><a name="INDEX-87"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>delete printer command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that removes a
+<a name="INDEX-87"/>printer from the system hosting the
+Samba server and deletes its service definition from
+<em class="filename">smb.conf</em>. The command is passed a printer name
+as its only argument. See also <tt class="literal">add printer
+command</tt>, <tt class="literal">printing</tt>, and <tt class="literal">show add
+printer wizard</tt>.</p></div>
+<a name="INDEX-88"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>delete readonly = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NO, YES</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, allows delete requests to remove read-only files. This
+is not allowed in MS-DOS/Windows, but it is normal in Unix, which has
+separate directory permissions. Used with programs such as RCS.</p></div>
+<a name="INDEX-89"/><a name="INDEX-90"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>delete share command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command that deletes a
+<a name="INDEX-90"/>share
+from the Samba server. The command runs when a user logged in as the
+<tt class="literal">root</tt> user on a Windows NT/2000/XP system deletes a
+share using Server Manager. The command is passed the name of the
+Samba configuration file and the name of the share to be deleted. The
+command must remove the definition of the share from the
+configuration file. See also <tt class="literal">add share command</tt> and
+<tt class="literal">change share command</tt>.</p></div>
+<a name="INDEX-91"/><a name="INDEX-92"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>delete user script = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to script</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the command to run as <tt class="literal">root</tt> when a user
+connects who no longer has an account on the
+domain's PDC. Honors <tt class="literal">%u</tt>. Can be
+used to delete the
+<a name="INDEX-92"/>user account automatically from
+the Samba server's host. Requires
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">domain</tt> or <tt class="literal">security = user</tt>. Use
+with caution. See also <tt class="literal">add user script</tt>.</p></div>
+<a name="INDEX-93"/><a name="INDEX-94"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>delete veto files = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NO, YES</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, allows delete requests for a
+<a name="INDEX-94"/>directory containing
+files or subdirectories the user can't see due to
+the <tt class="literal">veto</tt> <tt class="literal">files</tt> option. If set
+to NO, the directory is not deleted and still contains invisible
+files.</p></div>
+<a name="INDEX-95"/><a name="INDEX-96"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>deny hosts = host list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of systems from which to refuse
+<a name="INDEX-96"/>connections.
+Also called <tt class="literal">hosts</tt> <tt class="literal">deny</tt>.</p></div>
+<a name="INDEX-97"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dfree command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Specifies a command to run on the server to return free disk space.
+Not needed unless the Samba host system's
+<em class="emphasis">dfree</em> command does not work properly.</p></div>
+<a name="INDEX-98"/><a name="INDEX-99"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>directory = directory</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: Unix directory name</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the path to the
+<a name="INDEX-99"/>directory provided by a file share or
+used by a printer share. If the option is omitted in the
+<tt class="literal">[homes]</tt> share, it is set automatically to the
+user's home directory; otherwise, it defaults
+to<em class="filename"> /tmp</em>. For a printer share, the directory is
+used to spool printer files. Honors the <tt class="literal">%u</tt> (user)
+and <tt class="literal">%m</tt> (machine) variables. Synonym for
+<tt class="literal">path</tt>.</p></div>
+<a name="INDEX-100"/><a name="INDEX-101"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>directory mask = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0755</p><p>Sets the maximum allowable permissions for newly created
+<a name="INDEX-101"/>directories. To require
+that certain permissions be set, see the <tt class="literal">force</tt>
+<tt class="literal">create</tt> <tt class="literal">mask</tt> and
+<tt class="literal">force</tt> <tt class="literal">directory</tt>
+<tt class="literal">mask</tt> options. Also called
+<tt class="literal">directory</tt> <tt class="literal">mode</tt>.</p></div>
+<a name="INDEX-102"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>directory mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0755</p><p>Synonym for <tt class="literal">directory</tt> <tt class="literal">mask</tt>.</p></div>
+<a name="INDEX-103"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>directory security mask = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>:  same as <tt class="literal">directory</tt> <tt class="literal">mode</tt></p><p>Controls which permission bits can be changed if a user edits the
+Unix permissions of directories on the Samba server from a Windows
+system. Any bit that is set in the mask can be changed by the user;
+any bit that is clear remains the same on the directory even if the
+user tries to change it. Requires <tt class="literal">nt</tt>
+<tt class="literal">acl</tt> <tt class="literal">support</tt>
+<tt class="literal">=</tt> <tt class="literal">YES</tt>.</p></div>
+<a name="INDEX-104"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>disable spools = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, Windows NT/2000/XP systems will downgrade to
+Lanman-style printing. Prevents printer driver uploading and
+downloading from working. Use with care. See also <tt class="literal">use client
+driver</tt>.</p></div>
+<a name="INDEX-105"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dns proxy = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES and if <tt class="literal">wins</tt>
+<tt class="literal">server</tt> <tt class="literal">=</tt>
+<tt class="literal">YES</tt>, looks up hostnames in DNS when they are not
+found using WINS.</p></div>
+<a name="INDEX-106"/><a name="INDEX-107"/><a name="INDEX-108"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>domain admin group = user list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: usernames and/or group names</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies users who are in the <a name="INDEX-107"/>Domain Admins group and have
+<a name="INDEX-108"/>domain
+administrator authority when Samba is the PDC. See also
+<tt class="literal">domain guest group</tt> and <tt class="literal">domain
+logons</tt>. Useful in Samba 2.2 only. Obsolete in Samba 3.0.</p></div>
+<a name="INDEX-109"/><a name="INDEX-110"/><a name="INDEX-111"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>domain guest group = user/group list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of usernames and/or group names</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies users who are in the <a name="INDEX-110"/>Domain Guest group when Samba is the PDC.
+See also <tt class="literal">domain admin group</tt> and <tt class="literal">domain
+logons</tt>. Useful in Samba 2.2 only. <a name="INDEX-111"/>Obsolete in Samba 3.0.</p></div>
+<a name="INDEX-112"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>domain logons = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Causes Samba to serve domain logons. This is one of the basic
+functions required when Samba is acting as the PDC.</p></div>
+<a name="INDEX-113"/><a name="INDEX-114"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>domain master = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: automatic</p><p>Makes Samba a <a name="INDEX-114"/>domain master browser for its domain. When
+domain logons are enabled, <tt class="literal">domain master</tt> defaults
+to YES. Otherwise, it defaults to NO.</p></div>
+<a name="INDEX-115"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dont descend = list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of directories</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Prohibits a change directory or search in the directories specified.
+This is a browsing-convenience option; it doesn't
+provide any extra security.</p></div>
+<a name="INDEX-116"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dos filemode = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Allows anyone with write permissions to change permissions on a file,
+as allowed by MS-DOS.</p></div>
+<a name="INDEX-117"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dos filetime resolution = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Sets file times on Unix to match MS-DOS standards (rounding to the
+next even second). Recommended if using Visual C++ or a PC
+<em class="emphasis">make</em> program to avoid remaking the programs
+unnecessarily. Use with the <tt class="literal">dos</tt>
+<tt class="literal">filetimes</tt> option.</p></div>
+<a name="INDEX-118"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>dos filetimes = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Allows nonowners to change file times if they can write to the files,
+matching the behavior of MS-DOS and Windows. See also
+<tt class="literal">dos</tt> <tt class="literal">filetime</tt>
+<tt class="literal">resolution</tt>.</p></div>
+<a name="INDEX-119"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>encrypt passwords = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO in Samba 2.2, YES in Samba 3.0</p><p>If enabled, Samba will use password encryption. Requires an
+<em class="filename">smbpasswd</em> file on the Samba server.</p></div>
+<a name="INDEX-120"/><a name="INDEX-121"/><a name="INDEX-122"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>enhanced browsing = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Automatically synchronizes <a name="INDEX-121"/><a name="INDEX-122"/>browse lists with all domain master
+browsers known to the WINS server. Makes cross-subnet browsing more
+reliable, but also can cause empty workgroups to persist forever in
+browse lists.</p></div>
+<a name="INDEX-123"/><a name="INDEX-124"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>enumports command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Allows for a command to provide clients with customized
+MS-DOS/Windows <a name="INDEX-124"/>port names (e.g., PRN:) corresponding
+to printers. Samba's default behavior is to return
+<tt class="literal">Samba Printer Port</tt>. The command must return a
+series of lines, with one port name per line.</p></div>
+<a name="INDEX-125"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>exec = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a command to run as the user before connecting to the share.
+Synonym for <tt class="literal">preexec</tt>. See also the
+<tt class="literal">postexec</tt>, <tt class="literal">root</tt>
+<tt class="literal">preexec</tt>, and <tt class="literal">root postexec</tt>
+options.</p></div>
+<a name="INDEX-126"/><a name="INDEX-127"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>fake directory create times = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>A bug fix for users of Microsoft
+<em class="emphasis">nmake</em><a name="INDEX-127"/>. If YES, Samba sets directory create
+times such that <em class="emphasis">nmake</em> won't
+remake all files every time.</p></div>
+<a name="INDEX-128"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>fake oplocks = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set, returns YES whenever a client asks if it can lock a file and
+cache it locally but does not enforce the lock on the server. Results
+in performance improvement for read-only shares. <em class="emphasis">Never use
+with read/write shares!</em> See also
+<tt class="literal">oplocks</tt> and <tt class="literal">veto</tt>
+<tt class="literal">oplock</tt> <tt class="literal">files</tt>.</p></div>
+<a name="INDEX-129"/><a name="INDEX-130"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>follow symlinks = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES, Samba follows <a name="INDEX-130"/>symlinks in a file share(s). See the
+<tt class="literal">wide</tt> <tt class="literal">links</tt> option if you want
+to restrict symlinks to just the current share.</p></div>
+<a name="INDEX-131"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force create mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Takes effect when a user on a Windows client creates a file that
+resides on the Samba server. This option ensures that bits set in
+this mask will always be set on the new file. Used with the
+<tt class="literal">create mask</tt> configuration option.</p></div>
+<a name="INDEX-132"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force directory mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Takes effect when a user on a Windows client creates a directory on
+the Samba server. This option ensures that bits set in the mask will
+be set on every newly created directory. Used with <tt class="literal">directory
+mask</tt>.</p></div>
+<a name="INDEX-133"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force directory security mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>:  same as <tt class="literal">force</tt>
+<tt class="literal">directory</tt> <tt class="literal">mode</tt></p><p>Takes effect when a user on a Windows client edits the Unix
+permissions of a directory on the Samba server. This option ensures
+that bits set in this mask will be set on the directory. Requires
+<tt class="literal">nt</tt> <tt class="literal">acl</tt>
+<tt class="literal">support</tt> <tt class="literal">=</tt>
+<tt class="literal">YES</tt>.</p></div>
+<a name="INDEX-134"/><a name="INDEX-135"/><a name="INDEX-136"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force group = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: a Unix group name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the effective group name assigned to all users accessing a
+share. Used to override a
+<a name="INDEX-135"/><a name="INDEX-136"/>user's
+normal group memberships.</p></div>
+<a name="INDEX-137"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force security mode = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>: same as <tt class="literal">force</tt> <tt class="literal">create</tt>
+<tt class="literal">mode</tt></p><p>Takes effect when a user on a Windows client edits the Unix
+permissions of a file on the Samba server. This option ensures that
+bits set in the mask will always be set on the file. Requires
+<tt class="literal">nt</tt> <tt class="literal">acl</tt>
+<tt class="literal">support</tt> <tt class="literal">=</tt>
+<tt class="literal">YES</tt>. See also <tt class="literal">force directory security
+mode</tt> for directories.</p></div>
+<a name="INDEX-138"/><a name="INDEX-139"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force unknown acl user = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>When set, unknown users or groups in Windows NT ACLs will be mapped
+to the user or group of the connected user. <a name="INDEX-139"/>Obsolete starting with Samba
+3.0.</p></div>
+<a name="INDEX-140"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>force user = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: a single username</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the effective username assigned to all users accessing a share.
+Discouraged.</p></div>
+<a name="INDEX-141"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>fstype = string</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NTFS, FAT, Samba</p><p><b class="emphasis-bold">Default</b>: NTFS</p><p>Sets the filesystem type reported to the client. Avoid changing.</p></div>
+<a name="INDEX-142"/><a name="INDEX-143"/><a name="INDEX-144"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>getwd cache = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Caches the current <a name="INDEX-143"/><a name="INDEX-144"/>directory for performance.
+Recommended with the <tt class="literal">wide</tt> <tt class="literal">links</tt>
+option.</p></div>
+<a name="INDEX-145"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>group = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: a Unix group name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">force</tt> <tt class="literal">group</tt>.</p></div>
+<a name="INDEX-146"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>guest account = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: a single username</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the name of the unprivileged Unix account to use for tasks such
+as printing and for accessing shares marked with
+<tt class="literal">guest</tt> <tt class="literal">ok</tt>. The default is
+specified at compile time and is usually set to
+<tt class="literal">nobody</tt>.</p></div>
+<a name="INDEX-147"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>guest ok = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, doesn't need passwords for this
+share. Used with <tt class="literal">security = share</tt>. Synonym for
+<tt class="literal">public</tt>.</p></div>
+<a name="INDEX-148"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>guest only = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Forces users of a share to log on as the guest account. Requires
+<tt class="literal">guest</tt> <tt class="literal">ok</tt> or
+<tt class="literal">public</tt> to be YES. Also called
+<tt class="literal">only</tt> <tt class="literal">guest</tt>.</p></div>
+<a name="INDEX-149"/><a name="INDEX-150"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hide dot files = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Treats files with names beginning with a dot as if they had the
+MS-DOS <a name="INDEX-150"/>hidden
+attribute set. The files are either not displayed on a Windows client
+or appear grayed-out, depending on the settings on the client.</p></div>
+<a name="INDEX-151"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hide files = slash-separated list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: patterns, separated by <tt class="literal">/</tt>
+characters</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of file or directory names on which to set the
+MS-DOS hidden attribute. Names can contain <tt class="literal">?</tt> or
+<tt class="literal">*</tt> pattern characters and <tt class="literal">%</tt>
+variables. See also <tt class="literal">hide</tt> <tt class="literal">dot</tt>
+<tt class="literal">files</tt> and <tt class="literal">veto</tt>
+<tt class="literal">files</tt>.</p></div>
+<a name="INDEX-152"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hide local users = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, hides Unix-specific dummy accounts
+(<tt class="literal">root</tt>, <tt class="literal">wheel</tt>,
+<tt class="literal">floppy</tt>, etc.) from clients.</p></div>
+<a name="INDEX-153"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hide unreadable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, hides all unreadable files.</p></div>
+<a name="INDEX-154"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>homedir map = name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NIS map name</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Used with <tt class="literal">nis</tt> <tt class="literal">homedir</tt> to locate
+a user's Unix home directory from Sun NIS (not
+NIS+).</p></div>
+<a name="INDEX-155"/><a name="INDEX-156"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>host msdfs = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p><a name="INDEX-156"/>If set to YES and Samba was
+configured with the <tt class="literal">--with-msdfs</tt> option, provides
+Microsoft Distributed filesystem (Dfs) service, allowing Dfs-capable
+clients to browse Dfs trees on the Samba server. See also
+<tt class="literal">msdfs root</tt>.</p></div>
+<a name="INDEX-157"/><a name="INDEX-158"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hosts allow = host list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of systems that can access the
+<a name="INDEX-158"/>share. If NULL, any system can access
+the share unless there is a <tt class="literal">hosts</tt>
+<tt class="literal">deny</tt> option. Synonym for <tt class="literal">allow</tt>
+<tt class="literal">hosts</tt>.</p></div>
+<a name="INDEX-159"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hosts deny = host list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of systems that cannot connect to the share. Synonym
+for <tt class="literal">deny</tt> <tt class="literal">hosts</tt>.</p></div>
+<a name="INDEX-160"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>hosts equiv = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies the path to a file of trusted systems from which
+passwordless logons are allowed. Strongly discouraged because Windows
+NT/2000/XP users can always override the username&mdash;the only
+security in this scheme.</p></div>
+<a name="INDEX-161"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>include = filename</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Includes the named file in <em class="filename">smb.conf</em> at the line
+where it appears. This option accepts most variables, but not
+<tt class="literal">%u</tt> (user), <tt class="literal">%P</tt> (current
+share's <tt class="literal">root</tt> directory), or
+<tt class="literal">%S</tt> (current share's name) because
+they are not set at the time the file is read.</p></div>
+<a name="INDEX-162"/><a name="INDEX-163"/><a name="INDEX-164"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>inherit acls = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set, files and subdirectories are created with the same
+<a name="INDEX-163"/>ACLs
+as their parent directories. Directories are given Unix permissions
+of 0777 (full permissions) ensuring that the ACL on the directory
+will govern the actual permissions given to clients. Requires
+<a name="INDEX-164"/>POSIX ACL
+support to be provided on the Samba host system.</p></div>
+<a name="INDEX-165"/><a name="INDEX-166"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>inherit permissions = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set, files and subdirectories are created with the same
+<a name="INDEX-166"/>permissions as their parent
+directories. This allows Unix directory permissions to be propagated
+automatically to new files and subdirectories, especially in the
+<tt class="literal">[homes]</tt> share. This option overrides
+<tt class="literal">create</tt> <tt class="literal">mask</tt>,
+<tt class="literal">directory</tt> <tt class="literal">mask</tt>,
+<tt class="literal">force</tt> <tt class="literal">create</tt>
+<tt class="literal">mode</tt>, and <tt class="literal">force</tt>
+<tt class="literal">directory</tt> <tt class="literal">mode</tt>, but not
+<tt class="literal">map</tt> <tt class="literal">archive</tt>,
+<tt class="literal">map</tt> <tt class="literal">hidden</tt>, or
+<tt class="literal">map</tt> <tt class="literal">system</tt>. Samba never sets
+the <tt class="literal">setuid</tt> bit when creating a file or directory.</p></div>
+<a name="INDEX-167"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>interfaces = interface list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: interface list</p><p><b class="emphasis-bold">Default</b>: NULL (all interfaces except 127.0.0.1)</p><p>Sets the interfaces to which Samba will respond. The default is the
+system's primary interface only. Recommended on
+multihomed systems or to override erroneous addresses and netmasks.
+Allows interface names such as <tt class="literal">eth0</tt>, DNS names,
+address/netmask pairs, and broadcast/netmask pairs. See also
+<tt class="literal">bind interfaces only</tt>.</p></div>
+<a name="INDEX-168"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>invalid users = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of users not permitted access to the share.</p></div>
+<a name="INDEX-169"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>keepalive = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 300</p><p>Sets the number of seconds between checks for a crashed client. The
+value of 0 causes no checks to be performed. Setting
+<tt class="literal">keepalive = 3600</tt> will turn on checks every hour. A
+value of 600 (every 10 minutes) is recommended if you want more
+frequent checks. See also <tt class="literal">socket</tt>
+<tt class="literal">options</tt> for another approach.</p></div>
+<a name="INDEX-170"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>kernel oplocks = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Breaks the oplock when a local Unix process or NFS operation accesses
+an oplocked file, thus preventing corruption. This works only on
+operating systems that support kernel-based oplocks, such as Linux
+2.4 and Irix. Avoid changing. See also <tt class="literal">oplocks</tt> and
+<tt class="literal">level2</tt> <tt class="literal">oplocks</tt>.</p></div>
+<a name="INDEX-171"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lanman auth = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES, allows clients to use the (weak) LANMAN password hash
+used by Windows 95/98/Me. If set to NO, allows only the better NT1
+hash used by Windows NT/2000/XP.</p></div>
+<a name="INDEX-172"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>large readwrite = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO in Samba 2.2, YES in Samba 3.0</p><p>If set to YES, allows Windows 2000/XP to read and write 64KB at a
+time to improve performance. Requires Samba to be hosted by a 64-bit
+OS, such as Linux 2.4, Irix, or Solaris. Somewhat experimental.</p></div>
+<a name="INDEX-173"/><a name="INDEX-174"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap admin dn = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: Distinguished Name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the Distinguished Name used by Samba when contacting the LDAP
+server. Requires Samba to be configured with the
+<tt class="literal">--with-ldapsam</tt> configuration option. Experimental
+option added in Samba 2.2.3 and <a name="INDEX-174"/>obsolete in Samba 3.0.</p></div>
+<a name="INDEX-175"/><a name="INDEX-176"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap filter = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: LDAP search filter</p><p><b class="emphasis-bold">Default</b>: <tt class="literal">(&amp;(uid=%u)(objectclass=sambaAccount))</tt></p><p>Sets the LDAP search filter. Requires that Samba be configured with
+the <tt class="literal">--with-ldapsam</tt> configuration option.
+Experimental option added in Samba 2.2.3 and
+<a name="INDEX-176"/>obsolete in Samba 3.0.</p></div>
+<a name="INDEX-177"/><a name="INDEX-178"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap port = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive integer</p><p><b class="emphasis-bold">Default</b>: In Samba 2.2, 636 if <tt class="literal">ldap ssl = on</tt>;
+otherwise 389</p><p>Sets the TCP port number for contacting the LDAP server. Requires
+that Samba be configured with the <tt class="literal">--with-ldapsam</tt>
+configuration option. Experimental option added in Samba 2.2.3 and
+<a name="INDEX-178"/>obsolete
+starting with Samba 3.0. See also <tt class="literal">ldap ssl</tt>.</p></div>
+<a name="INDEX-179"/><a name="INDEX-180"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap server = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: fully qualified domain name</p><p><b class="emphasis-bold">Default</b>: localhost</p><p>Sets the domain name of the LDAP server. Requires that Samba be
+configured with the <tt class="literal">--with-ldapsam</tt> configuration
+option. Experimental option added in Samba 2.2.3 and
+<a name="INDEX-180"/>obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-181"/><a name="INDEX-182"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap ssl = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: ON, OFF, START TLS</p><p><b class="emphasis-bold">Default</b>: ON</p><p>Sets whether Samba uses SSL to contact the LDAP server. ON and OFF
+turn SSL encryption on or off. The START TLS setting causes Samba to
+use LDAPv3 StartTLS extended operation. Requires that Samba be
+configured with the <tt class="literal">--with-ldapsam</tt> configuration
+option. Experimental option added in Samba 2.2.3 and
+<a name="INDEX-182"/>obsolete
+in Samba 3.0.</p></div>
+<a name="INDEX-183"/><a name="INDEX-184"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ldap suffix = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: Distinguished Name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the base Distinguished Name to use for LDAP searches. Requires
+that Samba be configured with the <tt class="literal">--with-ldapsam</tt>
+configuration option. Experimental option added in Samba 2.2.3 and
+<a name="INDEX-184"/>obsolete in Samba 3.0.</p></div>
+<a name="INDEX-185"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>level2 oplocks = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows files to be cached read-only on the client when multiple
+clients have opened the file. This allows executables to be cached
+locally, improving performance.</p></div>
+<a name="INDEX-186"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lm announce = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: AUTO, YES, NO</p><p><b class="emphasis-bold">Default</b>: AUTO</p><p>Produces OS/2 SMB broadcasts at an interval specified by the
+<tt class="literal">lm</tt> <tt class="literal">interval</tt> option. YES/NO
+turns them on/off unconditionally. AUTO causes the Samba server to
+wait for a LAN manager announcement from another client before
+sending one out. Required for OS/2 client browsing.</p></div>
+<a name="INDEX-187"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lm interval = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 60</p><p>Sets the time period, in seconds, between OS/2 SMB broadcast
+announcements.</p></div>
+<a name="INDEX-188"/><a name="INDEX-189"/><a name="INDEX-190"/><a name="INDEX-191"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>load printers = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Loads all printer names from the system's
+<em class="emphasis">printcap</em><a name="INDEX-189"/> file into the
+<a name="INDEX-190"/><a name="INDEX-191"/>browse
+list. Uses configuration options from the
+<tt class="literal">[printers]</tt> section.</p></div>
+<a name="INDEX-192"/><a name="INDEX-193"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>local master = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows Samba to participate in <a name="INDEX-193"/>elections for the local master
+browser. See also <tt class="literal">domain</tt> <tt class="literal">master</tt>
+and <tt class="literal">os</tt> <tt class="literal">level</tt>.</p></div>
+<a name="INDEX-194"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lock dir = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: <em class="emphasis">/usr/local/samba/var/locks</em></p><p>Synonym for <tt class="literal">lock</tt> <tt class="literal">directory</tt>.</p></div>
+<a name="INDEX-195"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lock directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: <em class="emphasis">/usr/local/samba/var/locks</em></p><p>Sets a directory in which to keep lock files. The directory must be
+writable by Samba and readable by everyone. Also called
+<tt class="literal">lock</tt> <tt class="literal">dir</tt>.</p></div>
+<a name="INDEX-196"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lock spin count = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive integer</p><p><b class="emphasis-bold">Default</b>: 2</p><p>Sets the number of attempts to attain a byte range lock. See also
+<tt class="literal">lock spin time</tt>.</p></div>
+<a name="INDEX-197"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lock spin time = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of microseconds</p><p><b class="emphasis-bold">Default</b>: 10</p><p>Sets the number of microseconds between attempts to attain a lock.
+See also <tt class="literal">lock</tt> <tt class="literal">spin</tt>
+<tt class="literal">count</tt>.</p></div>
+<a name="INDEX-198"/><a name="INDEX-199"/><a name="INDEX-200"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>locking = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Performs <a name="INDEX-199"/><a name="INDEX-200"/>file locking. If set to NO, Samba
+accepts lock requests but won't actually lock
+resources. Turn off for read-only filesystems.</p></div>
+<a name="INDEX-201"/><a name="INDEX-202"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>log file = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the name and location of the <a name="INDEX-202"/>log file. Allows all <tt class="literal">%</tt>
+variables.</p></div>
+<a name="INDEX-203"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>log level = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Sets the logging level used. Values of 3 or more slow the system
+noticeably. Recommended value is 1. Synonym for
+<tt class="literal">debug</tt> <tt class="literal">level</tt>.</p></div>
+<a name="INDEX-204"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>logon drive = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: MS-DOS drive name</p><p><b class="emphasis-bold">Default</b>: Z:</p><p>Sets the drive to be used as a home directory for domain logons by
+Windows NT/2000/XP clients. See also <tt class="literal">logon</tt>
+<tt class="literal">home</tt>.</p></div>
+<a name="INDEX-205"/><a name="INDEX-206"/><a name="INDEX-207"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>logon home = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: UNC of shared directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">\\ %N \ %U</em></p><p>Sets the home <a name="INDEX-206"/><a name="INDEX-207"/>directory of a Windows 95/98/Me or
+NT/2000/XP user. Allows <tt class="literal">NET</tt> <tt class="literal">USE</tt>
+<tt class="literal">H:/HOME</tt> from the command prompt if Samba is acting
+as a logon server. Append <tt class="literal">\profile</tt> or other
+directory to the value of this parameter if storing Windows 95/98/Me
+profiles in a subdirectory of the user's home
+directory. See <tt class="literal">logon path</tt> for Windows NT/2000/XP
+roaming profiles.</p></div>
+<a name="INDEX-208"/><a name="INDEX-209"/><a name="INDEX-210"/><a name="INDEX-211"/><a name="INDEX-212"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>logon path = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: UNC of shared directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">\\ %N \  %U \ profile</em></p><p>Sets the path to the directory where Windows NT/2000/XP
+<a name="INDEX-209"/><a name="INDEX-210"/><a name="INDEX-211"/><a name="INDEX-212"/>roaming profiles are stored. See
+also <tt class="literal">logon home</tt> for Windows 95/98/Me roaming
+profiles.</p></div>
+<a name="INDEX-213"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>logon script = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: UNC of shared file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the pathname (relative to the <tt class="literal">[netlogon]</tt>
+share) of an MS-DOS/NT command to run on the client at logon time.
+Allows all <tt class="literal">%</tt> variables.</p></div>
+<a name="INDEX-214"/><a name="INDEX-215"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lppause command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command to pause a <a name="INDEX-215"/>print job.
+Honors the <tt class="literal">%p</tt> (printer name) and
+<tt class="literal">%j</tt> (job number) variables.</p></div>
+<a name="INDEX-216"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lpq cache time = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 10</p><p>Sets how long to keep print queue status cached, in seconds.</p></div>
+<a name="INDEX-217"/><a name="INDEX-218"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lpq command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command used to get <a name="INDEX-218"/>printer status. Usually
+initialized to a default value by the <tt class="literal">printing</tt>
+option. Honors the <tt class="literal">%p</tt> (printer name) variable.</p></div>
+<a name="INDEX-219"/><a name="INDEX-220"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lpresume command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command to resume a paused <a name="INDEX-220"/>print job.
+Honors the <tt class="literal">%p</tt> (printer name) and
+<tt class="literal">%j</tt> ( job number) variables.</p></div>
+<a name="INDEX-221"/><a name="INDEX-222"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>lprm command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command to delete a <a name="INDEX-222"/>print job.
+Usually initialized to a default value by the
+<tt class="literal">printing</tt> option. Honors the <tt class="literal">%p</tt>
+(printer name) and <tt class="literal">%j</tt> (job number) variables.</p></div>
+<a name="INDEX-223"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>machine password timeout = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 604800 (1 week)</p><p>Sets the period between (NT domain) computer account password changes.</p></div>
+<a name="INDEX-224"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>magic output = filename</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="replaceable">command</em><em class="emphasis">.out</em></p><p>Sets the output file for the <tt class="literal">magic</tt>
+<tt class="literal">scripts</tt> option. Default is the command name,
+followed by the <em class="emphasis">.out</em> extension.</p></div>
+<a name="INDEX-225"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>magic script = filename</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a filename for execution via a shell whenever the file is closed
+from the client, allowing clients to run commands on the server. The
+scripts will be deleted on completion, if permissions allow. Use is
+discouraged.</p></div>
+<a name="INDEX-226"/><a name="INDEX-227"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangle case = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p><a name="INDEX-227"/>Mangles a
+name if it is in mixed case.</p></div>
+<a name="INDEX-228"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangled map = map list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of to/from pairs</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets up a table of names to remap (e.g., <em class="emphasis">.html</em>
+to <em class="emphasis">.htm</em>).</p></div>
+<a name="INDEX-229"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangled names = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Sets Samba to abbreviate to the MS-DOS 8.3 style names that are too
+long or have unsupported characters.</p></div>
+<a name="INDEX-230"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangled stack = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 50</p><p>Sets the size of the cache of recently mangled filenames.</p></div>
+<a name="INDEX-231"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangling char = character</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: character</p><p><b class="emphasis-bold">Default</b>: ~</p><p>Sets the unique mangling character used in all mangled names.</p></div>
+<a name="INDEX-232"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>mangling method = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: hash, hash2</p><p><b class="emphasis-bold">Default</b>: hash</p><p>Sets the algorithm used to mangle filenames. The
+<tt class="literal">hash2</tt> method is a newer method introduced in Samba
+2.2.x, and it creates different filenames than the
+<tt class="literal">hash</tt> method.</p></div>
+<a name="INDEX-233"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>map archive = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, Samba sets the executable-by-user (0100) bit on Unix files if
+the MS-DOS archive attribute is set. If used, the
+<tt class="literal">create</tt> <tt class="literal">mask</tt> must contain the
+0100 bit.</p></div>
+<a name="INDEX-234"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>map hidden = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, Samba sets the executable-by-other (0001) bit on Unix files
+if the MS-DOS hidden attribute is set. If used, the <tt class="literal">create
+mask</tt> option must contain the 0001 bit.</p></div>
+<a name="INDEX-235"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>map system = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, Samba sets the executable-by-group (0010) bit on Unix files
+if the MS-DOS system attribute is set. If used, the
+<tt class="literal">create</tt> <tt class="literal">mask</tt> must contain the
+0010 bit.</p></div>
+<a name="INDEX-236"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>map to guest = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: Never, Bad User, Bad Password</p><p><b class="emphasis-bold">Default</b>:  Never</p><p>If set to Bad User, allows users without accounts on the Samba system
+to log in and be assigned the guest account. This option can be used
+as part of making public shares for anyone to use. If set to Bad
+Password, users who mistype their passwords will be logged in to the
+guest account instead of their own. Because no warning is given, the
+Bad Password value can be extremely confusing: we recommend against
+it. The default setting of Never prevents users without accounts from
+logging in.</p></div>
+<a name="INDEX-237"/><a name="INDEX-238"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max connections = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0 (infinity)</p><p>Sets the maximum number of
+<a name="INDEX-238"/>share connections allowed from each
+client system.</p></div>
+<a name="INDEX-239"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max disk size = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: size in MB</p><p><b class="emphasis-bold">Default</b>: 0 (no limit)</p><p>Sets the maximum disk size/free-space size (in megabytes) to return
+to the client. Some clients or applications can't
+understand large maximum disk sizes.</p></div>
+<a name="INDEX-240"/><a name="INDEX-241"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max log size = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: size in KB</p><p><b class="emphasis-bold">Default</b>: 5000</p><p>Sets the size (in kilobytes) at which Samba will start a new
+<a name="INDEX-241"/>log file. The current log file will be
+renamed with a <em class="emphasis">.old</em> extension, replacing any
+existing file with that name.</p></div>
+<a name="INDEX-242"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max mux = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 50</p><p>Sets the number of simultaneous SMB operations that Samba clients can
+make. Avoid changing.</p></div>
+<a name="INDEX-243"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max open files = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 10000</p><p>Limits the number of files a Samba process will try to keep open at
+one time. Samba allows you to set this to less than the maximum
+imposed by the Unix host operating system. Avoid changing.</p></div>
+<a name="INDEX-244"/><a name="INDEX-245"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max print jobs = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive integer</p><p><b class="emphasis-bold">Default</b>: 1000</p><p>Limits the number of jobs that can be in the queue for this
+<a name="INDEX-245"/>printer share at any one time. The printer
+will report <tt class="literal">out of space</tt> if the limit is exceeded.
+See also <tt class="literal">total print jobs</tt>.</p></div>
+<a name="INDEX-246"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max protocol = name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: CORE, COREPLUS, LANMAN1, LANMAN2, NT1</p><p><b class="emphasis-bold">Default</b>: NT1</p><p>If set, limits the negotiation to the protocol specified, or older.
+See <tt class="literal">min protocol</tt>. Avoid using.</p></div>
+<a name="INDEX-247"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max smbd processes = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer</p><p><b class="emphasis-bold">Default</b>: 0 (no limit)</p><p>Limits the number of users who can connect to the server. Used to
+prevent degraded service under an overload, at the cost of refusing
+services entirely.</p></div>
+<a name="INDEX-248"/><a name="INDEX-249"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max ttl = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 259200 (3 days)</p><p>Sets the <a name="INDEX-249"/>time to live (TTL) of NetBIOS names in the
+<em class="emphasis">nmbd</em> WINS cache. Avoid changing.</p></div>
+<a name="INDEX-250"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max wins ttl = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 518400 (6 days)</p><p>Limits the TTL, in seconds, of a NetBIOS name in the
+<em class="emphasis">nmbd</em> WINS cache. Avoid changing. See also
+<tt class="literal">min wins ttl</tt>.</p></div>
+<a name="INDEX-251"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>max xmit = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: size in bytes</p><p><b class="emphasis-bold">Default</b>: 65535</p><p>Sets the maximum packet size negotiated by Samba. This is a tuning
+parameter for slow links and bugs in older clients. Values less than
+2048 are discouraged.</p></div>
+<a name="INDEX-252"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>message command = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the command to run on the server when a WinPopup message arrives
+from a client. If it does not complete quickly, the command must end
+in <tt class="literal">&amp;</tt> to allow immediate return. Honors all
+<tt class="literal">%</tt> variables except <tt class="literal">%u</tt> (user)
+and supports the extra variables <tt class="literal">%s</tt> (filename the
+message is in), <tt class="literal">%t</tt> (destination system), and
+<tt class="literal">%f</tt> (from).</p></div>
+<a name="INDEX-253"/><a name="INDEX-254"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>min passwd length = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer</p><p><b class="emphasis-bold">Default</b>: 5</p><p><a name="INDEX-254"/>Synonym for <tt class="literal">min</tt>
+<tt class="literal">password</tt> <tt class="literal">length</tt>.</p></div>
+<a name="INDEX-255"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>min password length = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer</p><p><b class="emphasis-bold">Default</b>: 5</p><p>Sets the shortest Unix password allowed by Samba when updating a
+user's password on its system. Also called
+<tt class="literal">min</tt> <tt class="literal">passwd</tt>
+<tt class="literal">length</tt>.</p></div>
+<a name="INDEX-256"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>min print space = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: space in kilobytes</p><p><b class="emphasis-bold">Default</b>: 0 (unlimited)</p><p>Sets the minimum spool space required before accepting a print
+request.</p></div>
+<a name="INDEX-257"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>min protocol = name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: CORE, COREPLUS, LANMAN1, LANMAN2, NT1</p><p><b class="emphasis-bold">Default</b>: CORE</p><p>If set, prevents use of old (less secure) protocols. Using NT1
+disables MS-DOS clients. See also <tt class="literal">lanman auth</tt>.</p></div>
+<a name="INDEX-258"/><a name="INDEX-259"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>min wins ttl = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 21600 (6 hours)</p><p>Sets the minimum <a name="INDEX-259"/>TTL, in seconds, of a NetBIOS name in the
+<em class="emphasis">nmbd</em> WINS cache. Avoid changing.</p></div>
+<a name="INDEX-260"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>msdfs root = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Makes the share a Dfs <tt class="literal">root</tt>. Requires the
+<tt class="literal">--with-msdfs</tt> configure option. Any symbolic links
+of the form <tt class="literal">msdfs:server\share</tt> will be seen as Dfs
+links. See also <tt class="literal">host msdfs</tt>.</p></div>
+<a name="INDEX-261"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>name resolve order = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: lmhosts, wins, host, bcast</p><p><b class="emphasis-bold">Default</b>: lmhosts, host, wins, bcast</p><p>Sets the order of lookup when trying to get IP addresses from names.
+The host parameter carries out a regular name lookup using the
+server's normal sources:
+<em class="emphasis">/etc/hosts</em>, DNS, NIS, or a combination of these.</p></div>
+<a name="INDEX-262"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>netbios aliases = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of NetBIOS names</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Adds additional NetBIOS names by which the Samba server will
+advertise itself.</p></div>
+<a name="INDEX-263"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>netbios name = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: local hostname</p><p><b class="emphasis-bold">Default</b>: DNS name of system</p><p>Sets the NetBIOS name by which a Samba server is known, or the
+primary name if NetBIOS aliases exist. See also <tt class="literal">netbios
+aliases</tt>.</p></div>
+<a name="INDEX-264"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>netbios scope = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: string</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the NetBIOS scope string, an early predecessor of workgroups.
+Samba will not communicate with a system with a different scope. This
+option is not recommended.</p></div>
+<a name="INDEX-265"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nis homedir = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, the <tt class="literal">homedir</tt> <tt class="literal">map</tt> is used
+to look up the server hosting the user's home
+directory and return it to the client. The client will contact that
+system to connect to the share. This avoids mounting from a system
+that doesn't actually have the directory, which
+would cause the data to be transmitted twice. The system with the
+home directories must be an SMB server.</p></div>
+<a name="INDEX-266"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>non unix account range = numeric range</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: range of positive integers</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Specifies a range of Unix UIDs for Samba to use for user accounts and
+computer accounts that are maintained outside of
+<em class="filename">/etc/passwd</em>. The UIDs in this range must not
+overlap those of regular Unix users in
+<em class="filename">/etc/passwd</em>. See also <tt class="literal">algorithmic rid
+base</tt>. New in Samba 3.0.</p></div>
+<a name="INDEX-267"/><a name="INDEX-268"/><a name="INDEX-269"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nt acl support = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Causes the Samba server to map Unix
+<a name="INDEX-268"/><a name="INDEX-269"/>permissions to Windows NT
+ACLs.</p></div>
+<a name="INDEX-270"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nt pipe support = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows turning off of NT-specific pipe calls. This is a
+developer/benchmarking option and might be removed in the future.
+Avoid changing.</p></div>
+<a name="INDEX-271"/><a name="INDEX-272"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nt smb support = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, allows the use of NT-specific SMBs. This is a
+developer/benchmarking option that is <a name="INDEX-272"/>obsolete in Samba 3.0. Avoid changing.</p></div>
+<a name="INDEX-273"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nt status support = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, allows the use of NT-specific status messages. This is a
+developer/benchmarking option and might be removed in the future.
+Avoid changing.</p></div>
+<a name="INDEX-274"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>null passwords = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, allows access to accounts that have null passwords. Strongly
+discouraged.</p></div>
+<a name="INDEX-275"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>obey pam restrictions = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set, Samba will adhere to the PAM's account and
+session restrictions. Requires <tt class="literal">--with-pam</tt>
+configuration option.</p></div>
+<a name="INDEX-276"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>only guest = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Forces users of a share to log on as the guest account. Synonym for
+<tt class="literal">guest</tt> <tt class="literal">only</tt>. Requires
+<tt class="literal">guest</tt> <tt class="literal">ok</tt> or
+<tt class="literal">public</tt> to be YES.</p></div>
+<a name="INDEX-277"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>only user = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Requires that users of the share be in the list specified by the
+<tt class="literal">user</tt> option.</p></div>
+<a name="INDEX-278"/><a name="INDEX-279"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>oplock break wait time = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p><a name="INDEX-279"/>This is an advanced tuning parameter and
+is recommended only for experts who know how Samba handles oplocks.
+This option might need to be set if a Windows system fails to release
+an oplock in response to a break request from the Samba server. Due
+to bugs on some Windows systems, they might fail to respond if Samba
+responds too quickly; the default on this option can be lengthened in
+such cases.</p></div>
+<a name="INDEX-280"/><a name="INDEX-281"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>oplock contention limit = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of milliseconds</p><p><b class="emphasis-bold">Default</b>:  2</p><p><a name="INDEX-281"/>This is an advanced tuning
+parameter and is recommended only for experts who know how Samba
+handles oplocks. It causes Samba to refuse to grant an oplock if the
+number of clients contending for a file exceeds the specified value.</p></div>
+<a name="INDEX-282"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>oplocks = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If YES, supports local caching of oplocked files on the client. This
+option is recommended because it improves performance by about 30%.
+See also <tt class="literal">fake</tt> <tt class="literal">oplocks</tt> and
+<tt class="literal">veto</tt> <tt class="literal">oplock</tt>
+<tt class="literal">files</tt>.</p></div>
+<a name="INDEX-283"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>os level = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer</p><p><b class="emphasis-bold">Default</b>: 20</p><p>Sets the candidacy of the server when electing a browse master. Used
+with the <tt class="literal">domain</tt> <tt class="literal">master</tt> or
+<tt class="literal">local</tt> <tt class="literal">master</tt> options. You can
+set a higher value than a competing operating system if you want
+Samba to win. Windows for Workgroups and Windows 95/98/Me use 1.
+Windows NT/2000/XP, when not acting as a PDC, use 16 and, when acting
+as a PDC, use 32. Warning: this can override non-Samba browse masters
+unexpectedly.</p></div>
+<a name="INDEX-284"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>os2 driver map = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a file containing mappings of Windows NT printer driver
+names to OS/2 printer driver names.</p></div>
+<a name="INDEX-285"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>pam password change = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, and if Samba is configured with
+<tt class="literal">--with-pam</tt>, PAM is allowed to handle password
+changes from clients, instead of using the program defined by the
+<tt class="literal">passwd</tt> <tt class="literal">program</tt> parameter.</p></div>
+<a name="INDEX-286"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>panic action = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the command to run when Samba panics. Honors all
+<tt class="literal">%</tt> variables. For Samba developers and testers,
+<tt class="literal">/usr/bin/X11/xterm</tt> <tt class="literal">-display</tt>
+<tt class="literal">:0</tt> <tt class="literal">-e</tt> <tt class="literal">gdb</tt>
+<tt class="literal">/samba/bin/smbd</tt> <tt class="literal">%d</tt> is a
+possible value.</p></div>
+<a name="INDEX-287"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>passdb backend = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: smbpasswd, smbpasswd_nua, tdbsam, tdbsam_nua, plugin</p><p><b class="emphasis-bold">Default</b>: smbpasswd</p><p>Specifies methods Samba uses to store and retrieve passwords when
+using a method other than the Unix system's
+<em class="filename">/etc/passwd</em>. See also <tt class="literal">non unix account
+range</tt>. New in Samba 3.0.</p></div>
+<a name="INDEX-288"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>passwd chat = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: sequence of strings</p><p><b class="emphasis-bold">Default</b>: compiled-in value</p><p>Sets the chat strings used to change passwords on the server.
+Supports the variables <tt class="literal">%o</tt> (old password) and
+<tt class="literal">%n</tt> (new password) and allows the escapes
+<tt class="literal">\r</tt>, <tt class="literal">\n</tt>, <tt class="literal">\t</tt>,
+and <tt class="literal">\s</tt> (space) in the sequence. See also
+<tt class="literal">unix password sync</tt>, <tt class="literal">passwd
+program</tt>, <tt class="literal">passwd chat debug</tt>, and
+<tt class="literal">pam</tt> <tt class="literal">password change</tt>.</p></div>
+<a name="INDEX-289"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>passwd chat debug = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Logs an entire password chat, including passwords passed, with a log
+level of 100. For debugging only. See also <tt class="literal">passwd
+chat</tt>, <tt class="literal">pam password change</tt>, and
+<tt class="literal">passwd program</tt>.</p></div>
+<a name="INDEX-290"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>passwd program = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/bin/passwd</em></p><p>Sets the command used to change a user's password.
+Will be run as <tt class="literal">root</tt>. Supports
+<tt class="literal">%u</tt> (user). See also <tt class="literal">unix password
+sync</tt>.</p></div>
+<a name="INDEX-291"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>password level = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Specifies the number of uppercase-letter permutations used to match
+passwords. A workaround for clients that change passwords to a single
+case before sending them to the Samba server. Causes repeated login
+attempts with mixed-case passwords, which can trigger account
+lockouts. Required for Windows 95/98/Me, plain-text passwords, and
+mixed-case passwords. Try to avoid using.</p></div>
+<a name="INDEX-292"/><a name="INDEX-293"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>password server = list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of NetBIOS names</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of SMB servers that validate
+<a name="INDEX-293"/>passwords. Used with a Windows
+NT/2000 password server (PDC or BDC) and the
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">server</tt> or <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">domain</tt> configuration options.
+Caution: a Windows NT/2000 password server must allow logins from the
+Samba server. If set to <tt class="literal">*</tt>, Samba will look up the
+PDC by resolving the NetBIOS name WORKGROUP&lt;1C&gt;.</p></div>
+<a name="INDEX-294"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>path = directory</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the path to the directory provided by a file share or used by a
+printer share. If the option is omitted, it is set automatically in
+the <tt class="literal">[homes]</tt> share to the user's
+home directory; otherwise, defaults to<em class="filename"> /tmp</em>.
+Honors the <tt class="literal">%u</tt> (user) and <tt class="literal">%m</tt>
+(machine) variables.</p></div>
+<a name="INDEX-295"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>pid directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/samba/var/locks</em></p><p>Sets the path to the directory where PID files are located.</p></div>
+<a name="INDEX-296"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>posix locking = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES, Samba will map file locks owned by SMB clients to
+POSIX locks. Avoid changing.</p></div>
+<a name="INDEX-297"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>postexec = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a command to run as the user after disconnecting from the share.
+See also the <tt class="literal">preexec</tt>, <tt class="literal">root</tt>
+<tt class="literal">preexec</tt>, and <tt class="literal">root</tt>
+<tt class="literal">postexec</tt> options.</p></div>
+<a name="INDEX-298"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>postscript = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Forces a printer to recognize a file as PostScript by inserting
+<tt class="literal">%!</tt> as the first line. Works only if the printer is
+actually PostScript-compatible.</p></div>
+<a name="INDEX-299"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>preexec = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a command to run as the user before connecting to the share.
+Synonym for <tt class="literal">exec</tt>. See also the
+<tt class="literal">postexec</tt>, <tt class="literal">root</tt>
+<tt class="literal">preexec</tt>, and <tt class="literal">root</tt>
+<tt class="literal">postexec</tt> options.</p></div>
+<a name="INDEX-300"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>preexec close = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>:  NO</p><p>If set, allows the <tt class="literal">preexec</tt> command to decide if
+the share can be accessed by the user. If the command returns a
+nonzero return code, the user is denied permission to connect.</p></div>
+<a name="INDEX-301"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>preferred master = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: auto</p><p>If YES, Samba is the preferred master browser. Causes Samba to call a
+browsing election when it comes online. See also <tt class="literal">os
+level</tt>.</p></div>
+<a name="INDEX-302"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>prefered master = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: auto</p><p>Synonym for <tt class="literal">preferred master</tt>.</p></div>
+<a name="INDEX-303"/><a name="INDEX-304"/><a name="INDEX-305"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>preload = service list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of shares</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of shares that always appears in
+<a name="INDEX-304"/><a name="INDEX-305"/>browse lists. Synonym for
+<tt class="literal">auto</tt> <tt class="literal">services</tt>. See also
+<tt class="literal">load printers</tt>.</p></div>
+<a name="INDEX-306"/><a name="INDEX-307"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>preserve case = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p><a name="INDEX-307"/>Leaves filenames in the case
+sent by the client. If NO, it forces filenames to the case specified
+by the <tt class="literal">default</tt> <tt class="literal">case</tt> option. See
+also <tt class="literal">short</tt> <tt class="literal">preserve</tt>
+<tt class="literal">case</tt>.</p></div>
+<a name="INDEX-308"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Sets a share to be a print share. Required for all printers. Synonym
+for <tt class="literal">print</tt> <tt class="literal">ok</tt>.</p></div>
+<a name="INDEX-309"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printcap name = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="emphasis">/etc/printcap</em></p><p>Sets the path to the printer capabilities file used by the
+<tt class="literal">[printers]</tt> share. The default value changes to
+<em class="filename">/etc/qconfig</em> under AIX and
+<em class="filename">lpstat</em> on System V. Also called
+<tt class="literal">printcap</tt>.</p></div>
+<a name="INDEX-310"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>print command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command used to send a spooled file to the printer. Usually
+initialized to a default value corresponding to the
+<tt class="literal">printing</tt> option. This option honors the
+<tt class="literal">%p</tt> (printer name), <tt class="literal">%s</tt> (spool
+file), and <tt class="literal">%f</tt> (spool file as a relative path)
+variables. The command must delete the spool file.</p></div>
+<a name="INDEX-311"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer = name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: printer name</p><p><b class="emphasis-bold">Default</b>: lp</p><p>Sets the name of the Unix printer used by the share. Also called
+<tt class="literal">printer</tt> <tt class="literal">name</tt>.</p></div>
+<a name="INDEX-312"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer admin = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>:  NULL</p><p>Specifies users who can administer a printer using the remote printer
+administration interface on a Windows system. The
+<tt class="literal">root</tt> user always has these privileges.</p></div>
+<a name="INDEX-313"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer driver = name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: exact printer driver string used by Windows</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the string to pass to Windows when asked which driver to use to
+prepare files for a printer share. Note that the value is
+case-sensitive. Part of pre-2.2 printing system. Deprecated.</p></div>
+<a name="INDEX-314"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer driver file = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="emphasis">/usr/local/samba/printers/printers.def</em></p><p>Sets the location of a <em class="emphasis">msprint.def</em> file. Usable
+by Windows 95/98/Me. Part of pre-2.2 printing system. Deprecated.</p></div>
+<a name="INDEX-315"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer driver location = directory</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: UNC of shared directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">\\ server\ PRINTER$</em></p><p>Sets the location of the driver for a particular printer. The value
+is the pathname of the share that stores the printer driver files.
+Part of pre-2.2 printing system. Deprecated.</p></div>
+<a name="INDEX-316"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printer name = name</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">printer</tt>.</p></div>
+<a name="INDEX-317"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>printing = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: bsd, sysv, hpux, aix, qnx, plp, softq, lprng, cups</p><p><b class="emphasis-bold">Default</b>: bsd</p><p>Sets the printing style to a value other than that in which
+you've compiled. This sets initial values of at
+least <tt class="literal">print</tt> <tt class="literal">command</tt> ,
+<tt class="literal">lpq</tt> <tt class="literal">command</tt> , and
+<tt class="literal">lprm</tt> <tt class="literal">command</tt>.</p></div>
+<a name="INDEX-318"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>print ok = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Synonym for <tt class="literal">printable</tt>.</p></div>
+<a name="INDEX-319"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>private directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/samba/private</em></p><p>Specifies the directory used for storing security-sensitive files
+such as <em class="filename">smbpasswd</em> and
+<em class="filename">secrets.tdb</em>. New in Samba 3.0.</p></div>
+<a name="INDEX-320"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>protocol = name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: NT1, LANMAN2, LANMAN1, COREPLUS, CORE</p><p><b class="emphasis-bold">Default</b>: NT1</p><p>Synonym for <tt class="literal">max protocol</tt>.</p></div>
+<a name="INDEX-321"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>public = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If YES, passwords are not needed for this share. Also called
+<tt class="literal">guest</tt> <tt class="literal">ok</tt>.</p></div>
+<a name="INDEX-322"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>queuepause command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to script</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command used to pause a print queue. Usually initialized to
+a default value by the <tt class="literal">printing</tt> option.</p></div>
+<a name="INDEX-323"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>queueresume command = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to script</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Sets the command used to resume a print queue. Usually initialized to
+a default value by the <tt class="literal">printing</tt> option.</p></div>
+<a name="INDEX-324"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>read bmpx = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, supports the &quot;Read Block
+Multiplex&quot; message. Avoid changing.</p></div>
+<a name="INDEX-325"/><a name="INDEX-326"/><a name="INDEX-327"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>read list = list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of user and/or group names</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of <a name="INDEX-326"/><a name="INDEX-327"/>users given read-only access
+to a writable share.</p></div>
+<a name="INDEX-328"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>read only = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Sets a share to read-only. Antonym of <tt class="literal">writable</tt>,
+<tt class="literal">writeable</tt>, and <tt class="literal">write ok</tt>.</p></div>
+<a name="INDEX-329"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>read raw = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows clients to read data using a 64K packet size. Recommended.</p></div>
+<a name="INDEX-330"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>read size = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: positive integer</p><p><b class="emphasis-bold">Default</b>: 16384</p><p>Allows disk reads and writes to overlap network reads and writes. A
+tuning parameter. Do not set larger than the default.</p></div>
+<a name="INDEX-331"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>realm = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: Kerberos realm name</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Specifies the realm name for Kerberos 5 authentication. Requires the
+<tt class="literal">--with-krb5</tt> configure option. New in Samba 3.0.</p></div>
+<a name="INDEX-332"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>remote announce = remote list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of remote addresses</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Adds workgroups to the list on which the Samba server will announce
+itself. Specified as an IP address and optional workgroup (for
+instance, 192.168.220.215/SIMPLE) with multiple entries separated by
+spaces. Addresses can be the specific address of the browse master on
+a subnet or on directed broadcasts (i.e., ###.###.###.255). The
+server will appear on those workgroups' browse
+lists. Does not require WINS.</p></div>
+<a name="INDEX-333"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>remote browse sync = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: IP addresses</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Perform browse list synchronization with other Samba local master
+browsers. Addresses can be specific addresses or directed broadcasts
+(i.e., ###.###.###.255). The latter causes Samba to locate the local
+master browser on that subnet.</p></div>
+<a name="INDEX-334"/><a name="INDEX-335"/><a name="INDEX-336"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>restrict anonymous = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p><a name="INDEX-335"/><a name="INDEX-336"/>Denies access to users who do not
+supply a username. This is disabled by default because when the Samba
+server acts as the domain's PDC, the option can keep
+a client from revalidating its computer account when someone new logs
+in. Use of the option is recommended only when all clients are
+Windows NT/2000/XP systems.</p></div>
+<a name="INDEX-337"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">root</tt> <tt class="literal">directory</tt>.</p></div>
+<a name="INDEX-338"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root dir = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">root</tt> <tt class="literal">directory</tt>.</p></div>
+<a name="INDEX-339"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: /</p><p>Specifies a directory to <em class="emphasis">chroot( )</em> before
+starting daemons. Prevents any access outside that directory tree.
+See also the <tt class="literal">wide</tt> <tt class="literal">links</tt>
+configuration option. Also called <tt class="literal">root</tt> and
+<tt class="literal">root</tt> <tt class="literal">dir</tt>.</p></div>
+<a name="INDEX-340"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root postexec = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a command to run as <tt class="literal">root</tt> after disconnecting
+from the share. See also the <tt class="literal">preexec</tt>,
+<tt class="literal">postexec</tt>, and <tt class="literal">root</tt>
+<tt class="literal">preexec</tt> configuration options. Runs after the
+user's <tt class="literal">postexec</tt> command. Use with
+caution.</p></div>
+<a name="INDEX-341"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root preexec = command</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a command to run as <tt class="literal">root</tt> before connecting to
+the share. See also the <tt class="literal">preexec</tt>,
+<tt class="literal">postexec</tt>, and <tt class="literal">root</tt>
+<tt class="literal">postexec</tt> configuration options. Runs before the
+user's <tt class="literal">preexec</tt> command. Use with
+caution.</p></div>
+<a name="INDEX-342"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>root preexec close = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>:  NO</p><p>If set, allows the <tt class="literal">root</tt> <tt class="literal">preexec</tt>
+command to decide if the share can be accessed by the user. If the
+command returns a nonzero return code, the user will be denied
+permission to connect.</p></div>
+<a name="INDEX-343"/><a name="INDEX-344"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>security = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: share, user, server, domain</p><p><b class="emphasis-bold">Default</b>: user</p><p>Sets the client
+<a name="INDEX-344"/>authentication method. If
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">share</tt>, services are password-protected, available
+to everyone who knows the password. If <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">user</tt>, users have accounts and
+passwords, and are required to authenticate with the server before
+accessing services. If <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">server</tt>, users have accounts
+and passwords as with <tt class="literal">security = user</tt>, and a
+separate system authenticates them for Samba. If
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">domain</tt>, Windows NT domain authentication is
+implemented using a Windows NT/2000 or other Samba server to validate
+accounts. See also the <tt class="literal">password server</tt> and
+<tt class="literal">encrypted</tt> <tt class="literal">passwords</tt>
+configuration options.</p></div>
+<a name="INDEX-345"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>security mask = value</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: octal value from 0 to 0777</p><p><b class="emphasis-bold">Default</b>:  0777</p><p>Controls which permission bits can be changed if a user on a Windows
+NT/2000/XP system edits the Unix permissions of files on the Samba
+server using the Windows system's ACL editing dialog
+box. Any bit that is set in the mask can be changed by the user; any
+bit that is clear remains the same on the file even if the user tries
+to change it. Requires <tt class="literal">nt</tt> <tt class="literal">acl</tt>
+<tt class="literal">support</tt> <tt class="literal">=</tt>
+<tt class="literal">YES</tt>. Note that some rarely used bits map to the
+DOS system, hidden, and archive bits in the file attributes in a
+nonintuitive way.</p></div>
+<a name="INDEX-346"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>server string = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: string</p><p><b class="emphasis-bold">Default</b>: Samba <tt class="literal">%v</tt></p><p>Sets the name that corresponds to the Samba server in browse lists.
+Honors the <tt class="literal">%v</tt> (Samba version number) and
+<tt class="literal">%h</tt> (hostname) variables.</p></div>
+<a name="INDEX-347"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>set directory = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Allows the DEC Pathworks client to use the <em class="emphasis">set
+dir</em> command.</p></div>
+<a name="INDEX-348"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>share modes = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Directs Samba to support Windows-style whole-file (deny mode) locks.
+Do not change.</p></div>
+<a name="INDEX-349"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>short preserve case = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES, leaves mangled 8.3-style filenames in the case sent by
+the client. If NO, forces the case to that specified by the
+<tt class="literal">default</tt> <tt class="literal">case</tt> option. See also
+<tt class="literal">preserve</tt> <tt class="literal">case</tt>.</p></div>
+<a name="INDEX-350"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>show add printer wizard = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set, tells clients that the Add Printer Wizard can be used to add
+a Samba printer from Windows NT/2000/XP clients. See also
+<tt class="literal">add printer command</tt>, <tt class="literal">delete
+printer</tt> <tt class="literal">comamnd</tt>, and <tt class="literal">printer
+admin</tt>.</p></div>
+<a name="INDEX-351"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>shutdown script = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: command</p><p><b class="emphasis-bold">Default</b>: NONE</p><p>Specifies a command that initiates a system shutdown. The command is
+run with the UID of the connected user. The <tt class="literal">%m</tt>
+(message), <tt class="literal">%t</tt> (delay time), <tt class="literal">%r</tt>
+(reboot), and <tt class="literal">%f</tt> (force) options are supported.
+See also <tt class="literal">abort shutdown script</tt>. New in Samba 3.0.</p></div>
+<a name="INDEX-352"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smb passwd file = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/samba/private/smbpasswd</em></p><p>Overrides the compiled-in path to the encrypted password file. See
+also <tt class="literal">encrypted</tt> <tt class="literal">passwords</tt> and
+<tt class="literal">private dir</tt>.</p></div>
+<a name="INDEX-353"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>socket address = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: IP address</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the address on which to listen for connections. Default is to
+listen to all addresses.</p></div>
+<a name="INDEX-354"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>socket options = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: socket option list</p><p><b class="emphasis-bold">Default</b>: TCP_NODELAY</p><p>Sets OS-specific socket options. SO_KEEPALIVE makes TCP check clients
+every four hours to see if they are still accessible. TCP_NODELAY
+sends even tiny packets to keep delay low. Both are recommended
+wherever the operating system supports them.</p></div>
+<a name="INDEX-355"/><a name="INDEX-356"/><a name="INDEX-357"/><a name="INDEX-358"/><a name="INDEX-359"/><a name="INDEX-360"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>source environment = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Causes Samba to read a list of <a name="INDEX-356"/>environment variables from a file upon
+startup. This can be useful when setting up Samba in a
+<a name="INDEX-357"/><a name="INDEX-358"/><a name="INDEX-359"/><a name="INDEX-360"/>clustered environment. The
+filename can begin with a &quot;|&quot;
+(pipe) character, in which case it causes Samba to run the file as a
+command to obtain the variables.</p><p>The file must be owned by <tt class="literal">root</tt> and must not be
+world-writable. If the filename begins with a
+&quot;|&quot; character, it must point to a
+command that is neither world-writable nor resides in a
+world-writable directory.</p><p>The data should be in the form of lines such as
+SAMBA_NETBIOS_NAME=<em class="replaceable">myhostname</em>. This value
+will then be available in the <em class="filename">smb.conf</em> files as
+%$SAMBA_NETBIOS_NAME.</p></div>
+<a name="INDEX-361"/><a name="INDEX-362"/><a name="INDEX-363"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>:  NO</p><p><a name="INDEX-362"/><a name="INDEX-363"/>Makes
+Samba use SSL for data exchange with some or all hosts. Requires
+<tt class="literal">--with-ssl</tt> configure option.Obsolete starting with
+Samba 3.0.</p></div>
+<a name="INDEX-364"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl CA certDir = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/ssl/certs</em></p><p>Specifies a directory containing a file for each Certification
+Authority (CA) that the Samba server trusts so that Samba can verify
+client certificates. Part of SSL support. Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.</p></div>
+<a name="INDEX-365"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl CA certFile = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/ssl/certs/trustedCAs.pem</em></p><p>Specifies a file that contains information for each CA that the Samba
+server trusts so that Samba can verify client certificates. Part of
+SSL support. Requires <tt class="literal">--with-ssl</tt> configure option.
+Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-366"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl ciphers = list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of ciphers</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies which ciphers should be offered during SSL negotiation. Not
+recommended. Requires <tt class="literal">--with-ssl</tt> configure option.
+Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-367"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl client cert = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/ssl/certs/smbclient.pem</em></p><p>Specifies a file containing the server's SSL
+certificate, for use by <em class="emphasis">smbclient</em> if
+certificates are required in this environment. Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.</p></div>
+<a name="INDEX-368"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl client key = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/usr/local/ssl/private/smbclient.pem</em></p><p>Specifies a file containing the server's private SSL
+key, for use by <em class="emphasis">smbclient</em>. Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.</p></div>
+<a name="INDEX-369"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl compatibility = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Determines whether SSLeay should be configured for bug compatibility
+with other SSL implementations. Not recommended. Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.</p></div>
+<a name="INDEX-370"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl hosts = host list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Requires that SSL be used with the hosts listed. By default, if the
+<tt class="literal">ssl</tt> option is set, the server requires SSL with
+all hosts. Requires <tt class="literal">--with-ssl</tt> configure option.
+Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-371"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl hosts resign = host list</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of hosts or networks</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Suppresses the use of SSL with the hosts listed. By default, if the
+<tt class="literal">ssl</tt> option is set, the server requires SSL with
+all hosts. Requires <tt class="literal">--with-ssl</tt> configure option.
+Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-372"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl require clientcert = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Requires clients to use certificates when SSL is in use. This option
+is recommended if SSL is used. Requires <tt class="literal">--with-ssl</tt>
+configure option. Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-373"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl require servercert = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>When SSL is in use, <em class="emphasis">smbclient</em> requires servers
+to use certificates. This option is recommended if SSL is used.
+Requires <tt class="literal">--with-ssl</tt> configure option. Obsolete
+starting with Samba 3.0.</p></div>
+<a name="INDEX-374"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl server cert = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a file containing the server's SSL
+certificate. Requires <tt class="literal">--with-ssl</tt> configure option.
+Obsolete starting with Samba 3.0.</p></div>
+<a name="INDEX-375"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl server key = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a file containing the server's private SSL
+key. If no file is specified and SSL is in use, the server looks up
+its key in its server certificate. Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.</p></div>
+<a name="INDEX-376"/><a name="INDEX-377"/><a name="INDEX-378"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>ssl version = string</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: &quot;ssl2&quot;,
+&quot;ssl3&quot;,
+&quot;ssl2or3&quot;,
+&quot;tls1&quot;</p><p><b class="emphasis-bold">Default</b>: &quot;ssl2or3&quot;</p><p>Defines which versions of the SSL protocol the server can use:
+Version 2 only (&quot;ssl2&quot;), Version 3
+only (&quot;ssl3&quot;), Version 2 or 3
+dynamically negotiated (&quot;ssl2or3&quot;),
+or Transport Layer Security
+(&quot;tls1&quot;). Requires
+<tt class="literal">--with-ssl</tt> configure option. Obsolete starting
+with Samba 3.0.<a name="INDEX-377"/><a name="INDEX-378"/></p></div>
+<a name="INDEX-379"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>stat cache = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Makes the Samba server cache client names for faster resolution.
+Should not be changed.</p></div>
+<a name="INDEX-380"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>stat cache size = number </i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 50</p><p>Determines the number of client names cached for faster resolution.
+Should not be changed.</p></div>
+<a name="INDEX-381"/><a name="INDEX-382"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>status = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to YES, logs connections to a file (or shared memory)
+accessible to <em class="filename">smbstatus</em>.
+<a name="INDEX-382"/>Obsolete
+starting with Samba 3.0.</p></div>
+<a name="INDEX-383"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>strict allocate = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, allocates all disk blocks when creating or extending
+the size of files, instead of using the normal sparse file allocation
+used on Unix. This slows the server, but results in behavior that
+matches that of Windows and helps Samba correctly report
+&quot;out of quota&quot; messages.</p></div>
+<a name="INDEX-384"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>strict locking = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, checks locks on every access, not just on demand and
+at open time. Not recommended.</p></div>
+<a name="INDEX-385"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>strict sync = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, Samba synchronizes to disk whenever the client sets
+the sync bit in a packet. If set to NO, Samba flushes data to disk
+whenever buffers fill. Defaults to NO because Windows 98 Explorer
+sets the bit (incorrectly) in all packets.</p></div>
+<a name="INDEX-386"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>strip dot = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Removes trailing dots from filenames. Dysfunctional in Samba 2.2; use
+<tt class="literal">mangled</tt> <tt class="literal">map</tt> instead.</p></div>
+<a name="INDEX-387"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>sync always = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, Samba forces the data to disk through <em class="emphasis">fsync</em>
+(3) after every write. Avoid except to debug crashing
+servers.</p></div>
+<a name="INDEX-388"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>syslog = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 1</p><p>Sets the level of Samba log messages to send to
+<em class="filename">syslog</em>. Higher is more verbose. The
+<em class="filename">syslog.conf</em> file must have suitable logging
+enabled.</p></div>
+<a name="INDEX-389"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>syslog only = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, logs only to <em class="emphasis">syslog</em> instead of
+the standard Samba log files.</p></div>
+<a name="INDEX-390"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>template homedir = path</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to directory</p><p><b class="emphasis-bold">Default</b>: /home/<tt class="literal">%D</tt>/<tt class="literal">%U</tt></p><p>Sets the home directory for Unix login sessions for users
+authenticated through winbind. <tt class="literal">%D</tt> will be replaced
+with user's domain name; <tt class="literal">%U</tt> by
+the username.</p></div>
+<a name="INDEX-391"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>template shell = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to shell</p><p><b class="emphasis-bold">Default</b>: <em class="filename">/bin/false</em></p><p>Sets the shell for Unix login sessions for users authenticated
+through winbind. The default value prevents all Windows domain user
+logins.</p></div>
+<a name="INDEX-392"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>time offset = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of minutes</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Sets the number of minutes to add to the system time-zone
+calculation. Provided to fix a client daylight-savings bug. Not
+recommended.</p></div>
+<a name="INDEX-393"/><a name="INDEX-394"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>time server = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, <em class="emphasis">nmbd</em><a name="INDEX-394"/>
+advertises itself as a provider of SMB time service to clients. This
+option only affects whether the time service is advertised. It does
+not enable or disable time service.</p></div>
+<a name="INDEX-395"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>timestamp logs = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Synonym for <tt class="literal">debug</tt> <tt class="literal">timestamp</tt>.</p></div>
+<a name="INDEX-396"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>total print jobs = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0 (no limit)</p><p>Limits total number of current print jobs on server. See also
+<tt class="literal">max print jobs</tt>.</p></div>
+<a name="INDEX-397"/><a name="INDEX-398"/><a name="INDEX-399"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>unix extensions = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, supports
+<a name="INDEX-398"/>CIFS Unix extensions, providing
+better filesystem support for Unix clients. <a name="INDEX-399"/>Obsolete in Samba 3.0, which always
+offers support.</p></div>
+<a name="INDEX-400"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>unix password sync = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, attempts to change the user's Unix
+password whenever the user changes her SMB password. Used to ease
+synchronization of Unix and Microsoft password databases. See also
+<tt class="literal">password program</tt> and <tt class="literal">passwd</tt>
+<tt class="literal">chat</tt>.</p></div>
+<a name="INDEX-401"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>update encrypted = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Updates the encrypted password file when a user logs on with an
+unencrypted password. Provided to ease conversion from unencrypted to
+encrypted passwords.</p></div>
+<a name="INDEX-402"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>use client driver = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>Used for avoiding <tt class="literal">Access Denied; Unable to connect</tt>
+messages when connecting to a Samba printer from Windows NT/2000/XP
+clients. Necessary only when the client has a local printer driver
+for the Samba printer.</p></div>
+<a name="INDEX-403"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>use mmap = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: varies</p><p>Tells Samba whether the <em class="emphasis">mmap( )</em> system call
+works correctly on the Samba host. Default is automatically set
+correctly. Do not change.</p></div>
+<a name="INDEX-404"/><a name="INDEX-405"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>use rhosts = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, users' <em class="filename">~/.rhosts</em>
+files will be used to identify systems from which users can connect
+without providing a password. Discouraged. <a name="INDEX-405"/>Obsolete
+in Samba 3.0.</p></div>
+<a name="INDEX-406"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>use sendfile = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If yes, Samba will perform some data transfers for exclusively
+oplocked files using the <em class="emphasis">sendfile( )</em> system
+call, which results in significant performance improvements. This is
+available if Samba has been configured with the
+<tt class="literal">--with-sendfile-support</tt> option. This is an
+experimental option and is new in Samba 2.2.5.</p></div>
+<a name="INDEX-407"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>user = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">username</tt>.</p></div>
+<a name="INDEX-408"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>username = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets a list of users that are tried when logging on with share-level
+security in effect. Also called <tt class="literal">user</tt> or
+<tt class="literal">users</tt>. Discouraged. Use <tt class="literal">NET</tt>
+<tt class="literal">USE</tt>
+<tt class="literal">\\</tt><em class="replaceable">server</em><tt class="literal">\</tt><em class="replaceable">share
+</em><tt class="literal">%</tt><em class="replaceable">user</em>
+from the client instead.</p></div>
+<a name="INDEX-409"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>username level = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number</p><p><b class="emphasis-bold">Default</b>: 0</p><p>Specifies the number of uppercase-letter permutations allowed to
+match Unix usernames. A workaround for Windows'
+single-case usernames. Use is discouraged.</p></div>
+<a name="INDEX-410"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>username map = filename</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of file</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Names a file of Unix-to-Windows name pairs; used to map different
+spellings of account names and Windows usernames longer than eight
+characters.</p></div>
+<a name="INDEX-411"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>users = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Synonym for <tt class="literal">username</tt>.</p></div>
+<a name="INDEX-412"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>utmp = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>This is available if Samba has been configured with the
+<tt class="literal">--with-utmp</tt> option. If set, Samba adds
+<em class="emphasis">utmp</em>/<em class="emphasis">utmpx</em> records whenever
+a connection is made to a Samba server. Sites can use this option to
+record each connection to a Samba share as a system login.</p></div>
+<a name="INDEX-413"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>utmp directory = directory</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: name of directory</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>This is available if Samba has been configured with the
+<tt class="literal">--with-utmp</tt> option. If this option and
+<tt class="literal">utmp</tt> are set, Samba will look in the specified
+directory rather than the default system directory for
+<em class="filename">utmp</em>/<em class="filename">utmpx</em> files.</p></div>
+<a name="INDEX-414"/><a name="INDEX-415"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>valid chars = list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: list of numeric values</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Adds national characters to a character set map. See also
+<tt class="literal">client</tt> <tt class="literal">code</tt>
+<tt class="literal">page</tt>. <a name="INDEX-415"/>Obsolete in Samba 3.0.</p></div>
+<a name="INDEX-416"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>valid users = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL (allows everyone)</p><p>Specifies a list of users that can connect to a share. See also
+<tt class="literal">invalid users</tt>.</p></div>
+<a name="INDEX-417"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>veto files = slash-separated list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: slash-separated list of filenames</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of files that the client will not see when listing a
+directory's contents. See also
+<tt class="literal">delete</tt> <tt class="literal">veto</tt>
+<tt class="literal">files</tt> and <tt class="literal">hide files</tt>.</p></div>
+<a name="INDEX-418"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>veto oplock files = slash-separated list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: slash-separated list of filenames</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of files not to oplock (and cache on clients). See
+also <tt class="literal">oplocks</tt> and <tt class="literal">fake</tt>
+<tt class="literal">oplocks</tt>.</p></div>
+<a name="INDEX-419"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>vfs object = filename</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to shared library</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies the shared library to use for Samba's
+Virtual File System (VFS). Requires the <tt class="literal">--with-vfs</tt>
+configure option.</p></div>
+<a name="INDEX-420"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>vfs options = string</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: space-separated list of options</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies parameters to the VFS. Requires the
+<tt class="literal">--with-vfs</tt> configure option. See <tt class="literal">vfs
+object</tt>.</p></div>
+<a name="INDEX-421"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>volume = string</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: share name</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the volume label of a disk share. Especially useful with shared
+CD-ROMs.</p></div>
+<a name="INDEX-422"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wide links = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set, Samba follows symlinks out of the disk share. See also the
+<tt class="literal">root</tt> <tt class="literal">dir</tt> and
+<tt class="literal">follow</tt> <tt class="literal">symlinks</tt> options.</p></div>
+<a name="INDEX-423"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind cache time = number</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: number of seconds</p><p><b class="emphasis-bold">Default</b>: 15</p><p>Sets the amount of time that the <em class="emphasis">winbindd</em> daemon
+caches user and group information.</p></div>
+<a name="INDEX-424"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind enum users = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES/NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to NO, enumeration of users is suppressed by winbind.
+Discouraged.</p></div>
+<a name="INDEX-425"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind enum groups = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES/NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>If set to NO, enumeration of groups is suppressed by winbind.
+Discouraged.</p></div>
+<a name="INDEX-426"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind gid = numeric range</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer-integer</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies the group ID range winbind uses for Windows NT domain users
+connecting to Samba.</p></div>
+<a name="INDEX-427"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind separator = character</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: ASCII character</p><p><b class="emphasis-bold">Default</b>: \</p><p>Specifies the character winbind uses to separate a domain name and
+username.</p></div>
+<a name="INDEX-428"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbind uid = numeric range</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: integer-integer</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies the user ID range winbind will use for Windows NT domain
+users connecting to Samba.</p></div>
+<a name="INDEX-429"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wins hook = command</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: full path to script</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a command to run whenever the WINS server updates its
+database. Allows WINS to be synchronized with DNS or other services.
+The command is passed one of the arguments <tt class="literal">add</tt>,
+<tt class="literal">delete</tt>, or <tt class="literal">refresh</tt>, followed by
+the NetBIOS name, the name type (two hexadecimal digits), the TTL in
+seconds, and the IP addresses corresponding to the NetBIOS name.
+Requires <tt class="literal">wins</tt> <tt class="literal">service</tt>
+<tt class="literal">=</tt> <tt class="literal">YES</tt>.</p></div>
+<a name="INDEX-430"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wins proxy = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, <em class="emphasis">nmbd</em> proxies resolution requests
+to WINS servers on behalf of old clients, which use broadcasts. The
+WINS server is typically on another subnet.</p></div>
+<a name="INDEX-431"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wins server = value</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: hostname or IP address</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Sets the DNS name or IP address of the WINS server.</p></div>
+<a name="INDEX-432"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wins support = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: NO</p><p>If set to YES, activates the WINS service. The
+<tt class="literal">wins</tt> <tt class="literal">server</tt> option must not be
+set if <tt class="literal">wins</tt> <tt class="literal">support</tt>
+<tt class="literal">=</tt> <tt class="literal">YES</tt>.</p></div>
+<a name="INDEX-433"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>workgroup = name</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: workgroup name</p><p><b class="emphasis-bold">Default</b>: compiled-in</p><p>Sets the workgroup or domain to which the Samba server belongs.
+Overrides the compiled-in default of WORKGROUP. Choosing a name other
+than WORKGROUP is highly recommended.</p></div>
+<a name="INDEX-434"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>writable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Antonym for <tt class="literal">read</tt> <tt class="literal">only</tt>;
+<tt class="literal">writeable</tt> and <tt class="literal">write</tt>
+<tt class="literal">ok</tt> are synonyms.</p></div>
+<a name="INDEX-435"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>writeable = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Antonym for <tt class="literal">read</tt> <tt class="literal">only</tt>;
+<tt class="literal">writable</tt> and <tt class="literal">write</tt>
+<tt class="literal">ok</tt> are synonyms.</p></div>
+<a name="INDEX-436"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>write cache size = number</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: decimal number of bytes</p><p><b class="emphasis-bold">Default</b>: 0 (disabled)</p><p>Allocates a write buffer of the specified size in which Samba
+accumulates data before a write to disk. This option can be used to
+ensure that each write has the optimal size for a given filesystem.
+It is typically used with RAID drives, which have a preferred write
+size, and with systems that have large memory and slow disks.</p></div>
+<a name="INDEX-437"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>write list = user list</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: user list</p><p><b class="emphasis-bold">Default</b>: NULL</p><p>Specifies a list of users that are given read/write access to a
+read-only share. See also <tt class="literal">read</tt>
+<tt class="literal">list</tt>.</p></div>
+<a name="INDEX-438"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>write ok = boolean</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Synonym for <tt class="literal">writable</tt>.</p></div>
+<a name="INDEX-439"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>write raw = boolean</i></b></font></td><td align="right"><i>[global]
+</i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p><b class="emphasis-bold">Allowable values</b>: YES, NO</p><p><b class="emphasis-bold">Default</b>: YES</p><p>Allows fast-streaming writes over TCP using 64KB buffers. Recommended.</p></div>
+
+
+
+<div class="sect1"><a name="samba2-APP-B-SECT-2"/>
+
+<h2 class="head1">Glossary of Configuration Value Types</h2>
+
+<dl>
+<dt><b><a name="INDEX-440"/><em class="emphasis">boolean</em></b></dt>
+<dd>
+<p>One of two values, either YES or NO.</p>
+</dd>
+
+
+
+<dt><b>character</b></dt>
+<dd>
+<p>A single ASCII character.</p>
+</dd>
+
+
+
+<dt><b>command</b></dt>
+<dd>
+<p>A Unix script or compiled program, with an absolute path specified
+for the executable and parameters.</p>
+</dd>
+
+
+
+<dt><b>directory</b></dt>
+<dd>
+<p>An absolute path specification to a directory. For example:</p>
+
+<blockquote><pre class="code">/usr/local/samba/lib</pre></blockquote>
+</dd>
+
+</dl>
+
+<dl>
+<dt><b>filename</b></dt>
+<dd>
+<p>An absolute path specification to a file. For example:</p>
+
+<blockquote><pre class="code">/etc/printcap</pre></blockquote>
+</dd>
+
+
+<dt><b>host list</b></dt>
+<dd>
+<p>A list of hosts. Allows IP addresses, address masks, domain names,
+ALL, and EXCEPT.</p>
+</dd>
+
+
+
+<dt><b>interface list</b></dt>
+<dd>
+<p>A list of interfaces, in either address/netmask or address/n-bits
+format. For example:</p>
+
+
+<blockquote><pre class="code">192.168.2.10/255.255.255.0, 192.168.2.10/24</pre></blockquote>
+</dd>
+
+
+<dt><b>map list</b></dt>
+<dd>
+<p>A list of filename remapping strings such as
+<tt class="literal">(*.html</tt> <tt class="literal">*.htm)</tt>.</p>
+</dd>
+
+
+
+<dt><b>name</b></dt>
+<dd>
+<p>A single name of a type of object, as specified in the
+option's description.</p>
+</dd>
+
+
+
+<dt><b>number</b></dt>
+<dd>
+<p>A positive integer.</p>
+</dd>
+
+
+
+<dt><b>numeric range</b></dt>
+<dd>
+<p>Two numbers separated by a dash, specifying a minimum and a maximum
+value. For example:</p>
+
+
+<blockquote><pre class="code">100-250</pre></blockquote>
+</dd>
+
+
+<dt><b>remote list</b></dt>
+<dd>
+<p>A list of subnet-broadcast-address/workgroup pairs. For example:</p>
+
+<blockquote><pre class="code">192.168.2.255/SERVERS 192.168.4.255/STAFF</pre></blockquote>
+</dd>
+
+
+<dt><b>service (share) list</b></dt>
+<dd>
+<p>A list of service (share) names, without the enclosing parentheses.</p>
+</dd>
+
+
+
+<dt><b>slash-separated list</b></dt>
+<dd>
+<p>A list of filenames, separated by
+&quot;/&quot; characters to allow embedded
+spaces. For example:</p>
+
+
+<blockquote><pre class="code">/.*/My Documents/*.doc/</pre></blockquote>
+</dd>
+
+
+<dt><b>string</b></dt>
+<dd>
+<p>One line of arbitrary text.</p>
+</dd>
+
+
+
+<dt><b>user list</b></dt>
+<dd>
+<p>A list of usernames and/or group names.
+<tt class="literal">@</tt><em class="replaceable">group_name</em> includes
+whomever is in the NIS netgroup
+<em class="replaceable">group_name</em>, if one exists, or otherwise
+whomever is in the Unix group <em class="replaceable">group_name</em>.
+In addition,
+<tt class="literal">+</tt><em class="replaceable">group_name</em> is a Unix
+group, <tt class="literal">&amp;</tt><em class="replaceable">group_name</em>
+is an NIS netgroup, and <tt class="literal">&amp;+</tt> and
+<tt class="literal">+&amp;</tt> cause an ordered search of both Unix and
+NIS groups.</p>
+</dd>
+
+
+
+<dt><b>value</b></dt>
+<dd>
+<p>A value of some miscellaneous type, as specified in the
+option's description.<a name="INDEX-441"/></p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-APP-B-SECT-3"/>
+
+<h2 class="head1">Configuration File Variables</h2>
+
+<p><a href="appb.html#samba2-APP-B-TABLE-1">Table B-1</a> lists the Samba configuration file
+variables.</p>
+
+<a name="samba2-APP-B-TABLE-1"/><h4 class="head4">Table B-1. Configuration file variables</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Name</p>
+</th>
+<th>
+<p>Meaning</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">%a</tt></p>
+</td>
+<td>
+<p>Client's architecture (Samba, WfWg, WinNT, Win95, or
+UNKNOWN)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%d</tt></p>
+</td>
+<td>
+<p>Current server process's process ID</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%D</tt></p>
+</td>
+<td>
+<p>User's Windows NT Domain</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%f</tt></p>
+</td>
+<td>
+<p>Printer spool file as a relative path (printing only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%f</tt></p>
+</td>
+<td>
+<p>User from which a message was sent (messages only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%G</tt></p>
+</td>
+<td>
+<p>Primary group name of <tt class="literal">%U</tt> (requested username)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%g</tt></p>
+</td>
+<td>
+<p>Primary group name of <tt class="literal">%u</tt> (actual username)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%H</tt></p>
+</td>
+<td>
+<p>Home directory of <tt class="literal">%u</tt> (actual username)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%h</tt></p>
+</td>
+<td>
+<p>Samba server's (Internet) hostname</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%I</tt></p>
+</td>
+<td>
+<p>Client's IP address</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%j</tt></p>
+</td>
+<td>
+<p>Print job number (printing only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%L</tt></p>
+</td>
+<td>
+<p>Samba server's NetBIOS name (virtual servers have
+multiple names)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%M</tt></p>
+</td>
+<td>
+<p>Client's (Internet) hostname</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%m</tt></p>
+</td>
+<td>
+<p>Client's NetBIOS name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%N</tt></p>
+</td>
+<td>
+<p>Name of the NIS home directory server (without NIS, same as
+<tt class="literal">%L</tt>)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%n</tt></p>
+</td>
+<td>
+<p>New password (password change only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%o</tt></p>
+</td>
+<td>
+<p>Old password (password change only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%P</tt></p>
+</td>
+<td>
+<p>Current share's root directory (actual)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%p</tt></p>
+</td>
+<td>
+<p>Current share's root directory (in an NIS homedir
+map)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%p</tt></p>
+</td>
+<td>
+<p>Print filename (printing only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%R</tt></p>
+</td>
+<td>
+<p>Protocol level in use (CORE, COREPLUS, LANMAN1, LANMAN2, or NT1)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%S</tt></p>
+</td>
+<td>
+<p>Current share's name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%s</tt></p>
+</td>
+<td>
+<p>Name of the file in which the message resides (messages only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%s</tt></p>
+</td>
+<td>
+<p>Printer spool filename (printing only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%T</tt></p>
+</td>
+<td>
+<p>Current date and time</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%t</tt></p>
+</td>
+<td>
+<p>Destination system (messages only)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%U</tt></p>
+</td>
+<td>
+<p>Requested username for current share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%u</tt></p>
+</td>
+<td>
+<p>Current share's username</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%v</tt></p>
+</td>
+<td>
+<p>Samba version</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>%$<em class="replaceable">name</em></p>
+</td>
+<td>
+<p>Value of environment variable <em class="replaceable">name</em></p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+
+</body></html>
diff --git a/docs/htmldocs/using_samba/appc.html b/docs/htmldocs/using_samba/appc.html
new file mode 100644
index 0000000000..22ec5a5115
--- /dev/null
+++ b/docs/htmldocs/using_samba/appc.html
@@ -0,0 +1,4534 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix C. Summary of Samba Daemons and Commands</h1>
+
+
+<p>This appendix is a reference listing of command-line options and
+other information to help you use the programs that come with the
+Samba distribution.</p>
+
+
+
+<div class="sect1"><a name="samba2-APP-C-SECT-1"/>
+
+<h2 class="head1">Samba Daemons</h2>
+
+<p>The following sections provide information about the command-line
+parameters for <em class="emphasis">smbd</em>, <em class="emphasis">nmbd</em>,
+and <em class="emphasis">winbindd</em>.</p>
+
+</div>
+
+
+<a name="INDEX-1"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbd</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbd</em> program provides
+Samba's file and printer services, using one TCP/IP
+stream and one daemon per client. It is controlled from
+<em class="filename">/usr/local/samba/lib/smb.conf</em>, the default
+configuration file, which can be overridden by command-line options.</p><p>The configuration file is automatically reevaluated every minute. If
+it has changed, most new options are immediately effective. You can
+force Samba to reload the configuration file immediately by sending a
+SIGHUP signal to <em class="emphasis">smbd</em>. Reloading the
+configuration file does not affect any clients that are already
+connected. To escape this condition, a client would need to
+disconnect and reconnect, or the server itself would have to be
+restarted, forcing all clients to reconnect.</p>
+<div class="sect1"><a name="appc-5-fm2xml"/>
+
+<h4 class="refsect1">Other Signals</h4>
+<p>To shut down an <em class="emphasis">smbd</em> process, send it the
+termination signal SIGTERM (15), which allows it to die gracefully,
+instead of a SIGKILL (9). With Samba versions prior to 2.2, the
+debugging level could be raised or lowered using SIGUSR1 or SIGUSR2.
+This is no longer supported. Use <em class="emphasis">smbcontrol</em>
+instead.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-6-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbd <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-7-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt></b></dt>
+<dd>
+<p>Causes each new connection to the Samba server to append all logging
+messages to the log file. This option is the opposite of
+<tt class="literal">-o</tt> and is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt></b></dt>
+<dd>
+<p>Runs the <em class="emphasis">smbd</em> program as a daemon. This is the
+recommended way to use <em class="emphasis">smbd</em>. It is also the
+default action when <em class="emphasis">smbd</em> is run from an
+interactive command line. In addition, <em class="emphasis">smbd</em> can
+be run from <em class="emphasis">inetd</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Specifying the value on the command line overrides the
+value specified in the <em class="filename">smb.conf</em> file. Debug
+level 0 logs only the most important messages; level 1 is normal;
+levels 3 and above are primarily for debugging and slow
+<em class="emphasis">smbd</em> considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt> </b></dt>
+<dd>
+<p>Prints usage information for the <em class="emphasis">smbd</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt></b></dt>
+<dd>
+<p>Runs <em class="emphasis">smbd</em> interactively, rather than as a
+daemon. This option is used to override the default daemon mode when
+<em class="emphasis">smbd</em> is run from the command line.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt> <em class="replaceable">log_ directory</em></b></dt>
+<dd>
+<p>Sends the log messages to somewhere other than the location compiled
+into the executable or specified in the <em class="filename">smb.conf</em>
+file. The default is often
+<em class="filename">/usr/local/samba/var/</em>,
+<em class="filename">/usr/samba/var/</em>, or
+<em class="filename">/var/log/</em>. The log file is placed in the
+specified directory and named <em class="filename">log.smbd</em>. If the
+directory does not exist, Samba's compiled-in
+default will be used.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-O</tt> <em class="replaceable">socket_options</em></b></dt>
+<dd>
+<p>Sets the TCP/IP socket options, using the same parameters as the
+<tt class="literal">socket options</tt> configuration option. Often used
+for performance tuning and testing.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-o</tt></b></dt>
+<dd>
+<p>Causes log files to be overwritten when opened (the opposite of
+<tt class="literal">-a</tt>). Using this option saves you from hunting for
+the right log entries if you are performing a series of tests and
+inspecting the log file each time.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">port_number</em></b></dt>
+<dd>
+<p>Sets the TCP/IP port number from which the server will accept
+requests. All Microsoft clients send to the default port of 139,
+except for Windows 2000/XP, which can use port 445 for SMB
+networking, without the NetBIOS protocol layer.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-P</tt></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbd</em> to run in
+&quot;passive&quot; mode, in which it just
+listens, and does not transmit any network traffic. This is useful
+only for debugging by developers.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">configuration_ file</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file. Although the
+file defaults to <em class="filename">/usr/local/samba/lib/smb.conf</em>,
+you can override it on the command line. Typically used for
+debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-v</tt></b></dt>
+<dd>
+<p>Prints the current version of Samba.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-2"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nmbd</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">nmbd</em> program is Samba's
+NetBIOS name service and browsing daemon. It replies to NetBIOS over
+TCP/IP (also called NetBT or NBT) name-service requests broadcast
+from SMB clients, and optionally to Microsoft's
+Windows Internet Name Service (WINS) requests. Both are versions of
+the name-to-address lookup required by SMB clients. The broadcast
+version uses UDP broadcast on the local subnet only, while WINS uses
+TCP, which can be routed. If running as a WINS server,
+<em class="emphasis">nmbd</em> keeps a current name and address database
+in the file <em class="filename">/usr/local/samba/var/locks/wins.dat</em>.</p><p>An active <em class="emphasis">nmbd</em> daemon also responds to browsing
+protocol requests used by the Windows Network Neighborhood. This
+protocol provides a dynamic directory of servers, as well as the
+disks and printers that the servers are providing. As with WINS, this
+was initially done by making UDP broadcasts on the local subnet. With
+the addition of the local master browser to the network architecture,
+it is done by making TCP connections to a server. If
+<em class="emphasis">nmbd</em> is acting as a local master browser, it
+stores the browsing database in the file
+<em class="filename">/usr/local/samba/var/locks/browse.dat</em>.</p><p>Some clients (especially older ones) cannot use the WINS protocol. To
+support these clients, <em class="emphasis">nmbd</em> can act as a WINS
+proxy, accepting broadcast requests from the non-WINS clients,
+contacting a WINS server on their behalf, and returning the WINS
+server's response to them.</p>
+<div class="sect1"><a name="appc-9-fm2xml"/>
+
+<h4 class="refsect1">Signals</h4>
+<p>Like <em class="emphasis">smbd</em>, the <em class="emphasis">nmbd</em> program
+responds to several Unix signals. Sending <em class="emphasis">nmbd</em> a
+SIGHUP signal causes it to dump the names it knows about to the
+<em class="filename">/usr/local/samba/var/locks/namelist.debug</em> file.
+To shut down an <em class="emphasis">nmbd</em> process and allow it to die
+gracefully, send it a SIGTERM (15) signal, rather than a SIGKILL (9).
+With Samba versions prior to 2.2, the debugging level could be raised
+or lowered using SIGUSR1 or SIGUSR2. This is no longer supported. Use
+<em class="emphasis">smbcontrol</em> instead.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-10-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">nmbd <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-11-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt></b></dt>
+<dd>
+<p>Causes each new connection to the Samba server to append all logging
+messages to the log file. This option is the opposite of
+<tt class="literal">-o</tt> and is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Specifying the value on the command line overrides the
+value specified in the <em class="filename">smb.conf</em> file. Debug
+level 0 logs only the most important messages; level 1 is normal;
+levels 3 and above are primarily for debugging and slow
+<em class="emphasis">nmbd</em> considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt></b></dt>
+<dd>
+<p>Instructs the <em class="emphasis">nmbd</em> program to run as a daemon.
+This is the recommended way to use <em class="emphasis">nmbd</em> and is
+the default when <em class="emphasis">nmbd</em> is run from an interactive
+shell. In addition, <em class="emphasis">nmbd</em> can be run from
+<em class="emphasis">inetd</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt> </b></dt>
+<dd>
+<p>Prints usage information for the <em class="emphasis">nmbd</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-H</tt> <em class="replaceable">lmhosts_  file</em></b></dt>
+<dd>
+<p>Specifies the location of the <em class="emphasis">lmhosts</em> file for
+name resolution. This file is used only to resolve names for the
+local server, and not to answer queries from remote systems. The
+compiled-in default is commonly
+<em class="filename">/usr/local/samba/lib/lmhosts</em>,
+<em class="filename">/usr/samba/lib/lmhosts</em>, or
+<em class="filename">/etc/lmhosts</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt></b></dt>
+<dd>
+<p>Runs <em class="emphasis">nmbd</em> interactively, rather than as a
+daemon. This option is used to override the default daemon mode when
+<em class="emphasis">nmbd</em> is run from the command line.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt> <em class="replaceable">log_ file</em></b></dt>
+<dd>
+<p>Sends the log messages to somewhere other than the location compiled
+into the executable or specified in the <em class="filename">smb.conf</em>
+file. The default is often
+<em class="filename">/usr/local/samba/var/log.nmbd</em>,
+<em class="emphasis">/usr/samba/var/log.nmbd</em>, or <em class="emphasis">/var/log
+/log.nmbd</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt> <em class="replaceable">NetBIOS_name</em></b></dt>
+<dd>
+<p>Allows you to override the NetBIOS name by which the daemon
+advertises itself. Specifying this option on the command line
+overrides the <tt class="literal">netbios name</tt> option in the Samba
+configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-O</tt> <em class="replaceable">socket_options</em></b></dt>
+<dd>
+<p>Sets the TCP/IP socket options, using the same parameters as the
+<tt class="literal">socket options</tt> configuration option. Often used
+for performance tuning and testing.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-o</tt></b></dt>
+<dd>
+<p>Causes log files to be overwritten when opened (the opposite of
+<tt class="literal">-a</tt>). This option saves you from hunting for the
+right log entries if you are performing a series of tests and
+inspecting the log file each time.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">port_number</em></b></dt>
+<dd>
+<p>Sets the UDP port number from which the server accepts requests.
+Currently, all Microsoft clients use only the default port, 137.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">configuration_ file</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file. Although the
+file defaults to <em class="filename">/usr/local/samba/lib/smb.conf</em>,
+you can override it here on the command line. Typically used for
+debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-v</tt></b></dt>
+<dd>
+<p>Prints the current version of Samba.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-3"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>winbindd</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">winbindd</em> daemon is part of the winbind
+service and is used to allow Unix systems to obtain user and group
+information from a Windows NT/2000 server. Winbind maps Windows
+relative IDs (RIDs) to Unix UIDs and GIDs and allows accounts stored
+on the Windows server to be used for Unix authentication. Its purpose
+is to ease integration of Microsoft and Unix networks when a
+preexisting Windows domain controller is set up to handle user and
+computer accounts.</p><p>The daemon is accessed by users via the name service switch and PAM.
+The name service switch calls a library
+(<em class="filename">/lib/libnss_winbind.so</em>), which calls the
+daemon, which in turn calls the Windows NT/2000 server using
+Microsoft RPC. The PAM module for winbind can call the daemon
+similarly, allowing users whose accounts are stored on the Windows
+server to log in to the Unix system and run an interactive shell,
+FTP, or any other program that authenticates users through PAM.</p><p>The winbind subsystem is currently available only for the Linux
+operating system and a few other systems that use shared libraries,
+nsswitch and PAM.</p>
+<div class="sect1"><a name="appc-13-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">winbindd <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-14-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debuglevel</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Specifying the value on the command line overrides the
+value specified in the <em class="filename">smb.conf</em> file. Debug
+level 0 logs only the most important messages; level 1 is normal;
+levels 3 and above are primarily for debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt></b></dt>
+<dd>
+<p>Runs <em class="emphasis">winbindd</em> interactively. This option is used
+to override the default, which is for winbindd to detach and run as a
+daemon.</p>
+</dd>
+
+</dl>
+
+</div>
+</div>
+
+
+
+
+
+<div class="sect1"><a name="samba2-APP-C-SECT-2"/>
+
+<h2 class="head1">Samba Distribution Programs</h2>
+
+<p>This section lists the command-line options and subcommands provided
+by each nondaemon program in the Samba distribution.</p>
+
+</div>
+
+
+
+<a name="INDEX-4"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>findsmb</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This Perl script reports information about systems on the subnet that
+respond to SMB name-query requests. The report includes the IP
+address, NetBIOS name, workgroup/domain, and operating system of each
+system.</p>
+<div class="sect1"><a name="appc-17-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">findsmb <em class="replaceable">[subnet_broadcast_address]</em></pre></blockquote>
+<p>If a different subnet's broadcast address is
+provided, it will find SMB servers on that subnet. If no subnet
+broadcast address is supplied, <em class="emphasis">findsmb</em> will look
+on the local subnet.</p>
+
+<p>The output from <em class="emphasis">findsmb</em> looks like this:</p>
+<blockquote><pre class="code">$ <tt class="userinput"><b>findsmb</b></tt>
+                                *=DMB
+                                +=LMB
+IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
+---------------------------------------------------------------------
+172.16.1.1      TOLTEC         *[METRAN] [Unix] [Samba 2.2.6]
+172.16.1.3      MIXTEC         +[METRAN] [Unix] [Samba 2.2.6]
+172.16.1.4      ZAPOTEC         [METRAN] [Windows 5.0] [Windows 2000 LAN Manager]
+172.16.1.5      HUASTEC         [       METRAN        ]
+172.16.1.6      MAYA            [       METRAN        ]
+172.16.1.7      OLMEC           [METRAN] [Windows 5.1] [Windows 2000 LAN Manager]
+172.16.1.10     UTE             [       METRAN        ]
+172.16.1.13     DINE            [METRAN] [Windows NT 4.0] [NT LAN Manager 4.0]</pre></blockquote>
+<p>The system with an asterisk (<tt class="literal">*</tt>) in front of its
+workgroup name is the domain master browser for the workgroup/domain,
+and the system with a plus sign (+) preceding its workgroup name is
+the local master browser.</p>
+
+<p>The <em class="emphasis">findsmb</em> command was introduced during the
+development of Samba 2.2 and is installed by default in Samba
+Versions 2.2.5 and later.</p>
+
+</div>
+</div>
+
+<a name="INDEX-5"/><a name="INDEX-6"/><a name="INDEX-7"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>make_smbcodepage</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program is part of the
+<a name="INDEX-6"/>internationalization features of
+Samba 2.2 and is obsolete in Samba 3.0, which supports
+<a name="INDEX-7"/>Unicode
+automatically. The <em class="emphasis">make_smbcodepage</em> program
+compiles a binary codepage file from a text-format codepage
+definition. It can also perform the reverse operation, decompiling a
+binary codepage file into a text version. Examples of text-format
+codepage files can be found in the Samba distribution in the
+<em class="filename">source/codepages</em> directory. After Samba has been
+installed, examples of binary codepages can be found in the directory
+<em class="filename">/usr/local/samba/lib/codepages</em>.</p>
+<div class="sect1"><a name="appc-19-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">make_smbcodepage <em class="replaceable">c|d codepage_number input_file output_file</em></pre></blockquote>
+<p>For the first argument, use <tt class="literal">c</tt> to compile a
+codepage and <tt class="literal">d</tt> to decompile a codepage file. The
+<em class="replaceable">codepage_number</em> argument is the number of
+the codepage being processed (e.g., 850). The
+<em class="replaceable">input_file</em> and
+<em class="replaceable">output_file</em> are the text- and
+binary-format codepages, with the types dependent on the operation
+(compiling or decompiling) that is being performed.</p>
+
+</div>
+</div>
+
+<a name="INDEX-8"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>make_unicodemap</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program is part of the internationalization features of Samba
+2.2 and is obsolete in Samba 3.0, which supports Unicode
+automatically. The <em class="emphasis">make_unicodemap</em> command
+compiles binary Unicode maps from text files, so Samba can display
+non-ASCII characters in file and directory names via the Unicode
+international alphabets. Examples of input mapping files can be found
+in the directory <em class="filename">source/codepages</em> in the Samba
+source distribution.</p>
+<div class="sect1"><a name="appc-21-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">make_unicodemap <em class="replaceable">codepage_number inputfile outputfile</em></pre></blockquote>
+<p>The input file is an ASCII map; the output file is a binary file
+loadable by Samba. The codepage is the number of the DOS codepage
+(e.g., 850) for the map.</p>
+
+</div>
+</div>
+
+<a name="INDEX-9"/><a name="INDEX-10"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>net</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">net</em> command, new to Samba 3.0, is a program
+with a syntax similar to the MS-DOS/Windows command of the same name.
+It is used for performing various administrative functions related to
+Windows networking, which can be executed either locally or on a
+remote system.</p>
+<div class="sect1"><a name="appc-23-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">net <em class="replaceable">[method] function [misc_options] [target_options]</em></pre></blockquote>
+<p>The <em class="replaceable">function</em> argument is made up of one or
+more space-separated words. In Windows terminology, it is sometimes
+referred to as a function with options. Here we list every function
+in its complete form, including multiple words.</p>
+
+<p>By default, the action is performed on the local system. The
+<em class="replaceable">target_options</em> argument can be used to
+specify a remote system (either by hostname or IP address), a domain,
+or a workgroup.</p>
+
+<p>Depending on the function, the <em class="replaceable">method</em>
+argument can be optional, required, or disallowed. It specifies one
+of three methods for performing the operation specified by the rest
+of the command. It can be <tt class="literal">ads</tt> (Active Directory),
+<tt class="literal">rpc</tt> (Microsoft's DCE/RPC), or
+<tt class="literal">rap</tt> (Microsoft's original SMB
+remote procedure call). To determine which methods (if any) can be
+used with a function, the <tt class="literal">net help ads</tt>,
+<tt class="literal">net help rap</tt>, and <tt class="literal">net help rpc</tt>
+commands can be used to list the functions for each method.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-24-fm2xml"/>
+
+<h4 class="refsect1">Miscellaneous options</h4>
+
+<dl>
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">level</em></b></dt>
+<dt><b><tt class="literal">--debug=l</tt><em class="replaceable">evel</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt></b></dt>
+<dt><b><tt class="literal">--long</tt></b></dt>
+<dd>
+<p><tt class="literal">S</tt>pecifies the long listing mode. This is provided
+for functions that print informational listings.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt> <em class="replaceable">name</em></b></dt>
+<dt><b><tt class="literal">--myname</tt><em class="emphasis">=</em><em class="replaceable">name</em></b></dt>
+<dd>
+<p>Specifies the NetBIOS name for the client.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">port</em></b></dt>
+<dt><b><tt class="literal">--port</tt><em class="emphasis">=</em><em class="replaceable">port</em></b></dt>
+<dd>
+<p>Specifies the port number to use.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">filename</em></b></dt>
+<dt><b><tt class="literal">--conf</tt><em class="emphasis">=</em><em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the name of the Samba configuration file, overriding the
+compiled-in default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">username[</em><tt class="literal">%</tt><em class="replaceable">password]</em></b></dt>
+<dt><b><tt class="literal">--user</tt><em class="emphasis">=</em><em class="replaceable">username[</em><tt class="literal">%</tt><em class="replaceable">password]</em></b></dt>
+<dd>
+<p>Specifies the username and, optionally, the password to use for
+functions that require authentication.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-W</tt> <em class="replaceable">name</em></b></dt>
+<dt><b><tt class="literal">--myworkgroup</tt>=<em class="replaceable">name</em></b></dt>
+<dd>
+<p>Specifies the name of the client's workgroup,
+overriding the definition of the <tt class="literal">workgroup</tt>
+parameter in the Samba configuration file.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-25-fm2xml"/>
+
+<h4 class="refsect1">Target options</h4>
+
+<dl>
+<dt><b><tt class="literal">-S</tt> <em class="replaceable">hostname</em></b></dt>
+<dd>
+<p>Specifies the remote system using a hostname or NetBIOS name.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-I</tt> <em class="replaceable">ip_address</em></b></dt>
+<dd>
+<p>Specifies the remote system using its IP address.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-w</tt> <em class="replaceable">workgroup</em></b></dt>
+<dd>
+<p>Specifies the name of the target domain or workgroup.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-26-fm2xml"/>
+
+<h4 class="refsect1">Functions</h4>
+
+<dl>
+<dt><b><tt class="literal">abortshutdown</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">rpc</tt> <tt class="literal">abortshutdown</tt>
+function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads</tt> <tt class="literal">info</tt></b></dt>
+<dd>
+<p>Prints information about the Active Directory server. The method
+(<tt class="literal">ads</tt>) must be specified to differentiate this
+function from the <tt class="literal">rpc info</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads</tt> <tt class="literal">join</tt> <em class="replaceable">OU</em></b></dt>
+<dd>
+<p>Joins the local system to the Active Directory realm (organizational
+unit) specified by OU. The method (<tt class="literal">ads</tt>) must be
+specified to differentiate this function from the <tt class="literal">rpc
+join</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads</tt> <tt class="literal">leave</tt></b></dt>
+<dd>
+<p>Removes the local system from the Active Directory realm.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads password</tt> <em class="replaceable">username</em><tt class="literal">@</tt><em class="replaceable">REALM</em> <tt class="literal">-U</tt><em class="replaceable">admin_username</em><tt class="literal">@</tt><em class="replaceable">REALM</em><tt class="literal">%admin_</tt><em class="replaceable">password</em></b></dt>
+<dd>
+<p>Changes the Active Directory password for the user specified by
+<em class="replaceable">username</em><tt class="literal">@</tt><em class="replaceable">REALM</em>.
+The administrative account authentication information is specified
+with the <tt class="literal">-U</tt> option. The Active Directory realm
+must be supplied in all uppercase.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads printer info</tt> <em class="replaceable">[printer] [server]</em></b></dt>
+<dd>
+<p>Prints information on the specified printer on the specified server.
+The <em class="replaceable">printer</em> argument defaults to an
+asterisk (<tt class="literal">*</tt>), meaning all printers, and the
+<em class="replaceable">server</em> argument defaults to
+<tt class="literal">localhost</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads printer publish</tt> <em class="replaceable">printer_name</em></b></dt>
+<dd>
+<p>Publishes the specified printer in Active Directory.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads printer remove</tt> <em class="replaceable">printer_name</em></b></dt>
+<dd>
+<p>Removes the specified printer from Active Directory.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads search</tt> <em class="replaceable">expr attrib</em></b></dt>
+<dd>
+<p>Performs a raw Active Directory search, using the standard LDAP
+search expression and attributes specified by the
+<em class="replaceable">expr</em> and <em class="replaceable">attrib</em>
+arguments, respectively.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ads status</tt></b></dt>
+<dd>
+<p>Prints details about the Active Directory computer account of the
+system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">change localhost pass</tt></b></dt>
+<dd>
+<p>Changes the Active Directory password for the local
+system's computer trust account.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">domain</tt></b></dt>
+<dd>
+<p>Lists the domains or workgroups on the network.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">file</tt></b></dt>
+<dd>
+<p>Lists open files on the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">file close</tt> <em class="replaceable">file_id</em></b></dt>
+<dd>
+<p>Closes the specified file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">file info</tt> <em class="replaceable">file_id</em></b></dt>
+<dd>
+<p>Prints information about the specified file, which must be open.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">file user</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Lists all files opened on the server by the user specified by
+<em class="replaceable">username</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">group add</tt> <em class="replaceable">group_name</em></b></dt>
+<dd>
+<p>Adds the specified group. This function accepts the miscellaneous
+option <tt class="literal">-C</tt> <em class="replaceable">comment</em>
+(which can also be specified as <tt class="literal">-
+-comment=</tt><em class="replaceable">string</em>) to set the
+descriptive comment for the group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">group delete</tt> <em class="replaceable">group_name</em></b></dt>
+<dd>
+<p>Deletes the specified group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">groupmember add</tt> <em class="replaceable">group_name username</em></b></dt>
+<dd>
+<p>Adds the user specified by <em class="replaceable">username</em> to the
+group specified by <em class="replaceable">group_name</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">groupmember delete</tt> <em class="replaceable">group_name username</em></b></dt>
+<dd>
+<p>Deletes the user specified by <em class="replaceable">username</em>
+from the group specified by <em class="replaceable">group_name</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">groupmember list</tt> <em class="replaceable">group_name</em></b></dt>
+<dd>
+<p>Lists the users who are members of the specified group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">help</tt></b></dt>
+<dd>
+<p>Prints a help message for the <em class="emphasis">net</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">help</tt> <em class="replaceable">method</em></b></dt>
+<dd>
+<p>Prints a help message for <em class="replaceable">method</em>, which
+can be <tt class="literal">ads</tt>, <tt class="literal">rap</tt>, or
+<tt class="literal">rpc</tt>. This lists the functions that can use the
+method, along with a brief description.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">help</tt> <em class="replaceable">function</em></b></dt>
+<dd>
+<p>Prints a help message for the specified function, which can be more
+than one word.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">info</tt></b></dt>
+<dd>
+<p>Must be preceded by a method. See the <tt class="literal">ads</tt>
+<tt class="literal">info</tt> and <tt class="literal">rpc</tt>
+<tt class="literal">info</tt> functions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">join</tt></b></dt>
+<dd>
+<p>Joins the computer to a Windows NT domain or Active Directory realm.
+If the method argument is not specified, a check is made to determine
+if Active Directory is in use, and if so, <tt class="literal">ads join</tt>
+is performed. Otherwise, <tt class="literal">rpc join</tt> is run. See also
+the <tt class="literal">ads join</tt> and <tt class="literal">rpc join</tt>
+functions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">leave</tt></b></dt>
+<dd>
+<p>Must be preceded by a method. See the <tt class="literal">ads</tt>
+<tt class="literal">leave</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookup dc</tt> <em class="replaceable">[domain]</em></b></dt>
+<dd>
+<p>Prints the IP address of the specified domain's
+domain controllers. The domain defaults to the value of the
+<tt class="literal">workgroup</tt> parameter in the Samba configuration
+file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookup host</tt> <em class="replaceable">hostname [type]</em></b></dt>
+<dd>
+<p>Prints the IP address of the specified host.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookup kdc</tt> <em class="replaceable">[realm]</em></b></dt>
+<dd>
+<p>Prints the IP address of the specified realm's
+Kerberos domain controller. If <em class="replaceable">realm</em> is
+not specified, it defaults to the value of the
+<tt class="literal">realm</tt> parameter in the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookup ldap</tt> <em class="replaceable">[domain]</em></b></dt>
+<dd>
+<p>Prints the IP address of the specified domain's LDAP
+server. If <em class="replaceable">domain</em> is not specified, it
+defaults to the value of the <tt class="literal">workgroup</tt> parameter
+in the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookup master</tt> <em class="replaceable">[domain]</em></b></dt>
+<dd>
+<p>Prints the IP address of the master browser of the specified domain
+or workgroup. If <em class="replaceable">domain</em> is not specified,
+it defaults to the value of the <tt class="literal">workgroup</tt>
+parameter in the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">password</tt> <em class="replaceable">username old_password new_password</em></b></dt>
+<dd>
+<p>Changes the password for the user specified by the
+<em class="replaceable">username</em> argument. The
+user's old and new passwords are provided in plain
+text as part of the command. Be careful regarding security issues.
+See also the <tt class="literal">ads password</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printer info</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">ads printer info</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printer publish</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">ads printer publish</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printer remove</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">ads printer remove</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printq</tt></b></dt>
+<dd>
+<p>Prints information (including the job IDs) about printer queues on
+the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printq delete</tt> <em class="replaceable">queue_name</em></b></dt>
+<dd>
+<p>Deletes the specified printer queue. The
+<tt class="literal">-j</tt>
+<em class="replaceable">job_id</em> (which can also be
+specified as
+<tt class="literal">--jobid</tt><em class="emphasis">=</em><em class="replaceable">job_id</em>
+) option may be used to specify the job ID of the queue.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc abortshutdown</tt></b></dt>
+<dd>
+<p>Aborts the shutdown of a remote server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc info</tt></b></dt>
+<dd>
+<p>Prints information about the server's domain. The
+method (<tt class="literal">rpc</tt>) must be specified to differentiate
+this function from the <tt class="literal">ads</tt> <tt class="literal">info</tt>
+function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc join</tt> </b></dt>
+<dd>
+<p>Joins a computer to a Windows NT domain. If the <tt class="literal">-U</tt>
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>
+option is included, the specified username and password will be used
+as the administrative account required for authenticating with the
+PDC. If the <tt class="literal">-U</tt> option is not included, this
+function can be used only to join the computer to the domain after
+the computer account has been created using the Server Manager. The
+method (<tt class="literal">rpc</tt>) must be specified to differentiate
+this function from the <tt class="literal">ads</tt> <tt class="literal">join</tt>
+function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc shutdown</tt></b></dt>
+<dd>
+<p>Shuts down a server. This function accepts the <tt class="literal">-r</tt>,
+<tt class="literal">-f</tt>, <tt class="literal">-t</tt>, and
+<tt class="literal">-c</tt> miscellaneous options. The
+<tt class="literal">-r</tt> option (which can also be specified as
+<tt class="literal">--reboot</tt>) requests that the system reboot after
+shutting down. The <tt class="literal">-f</tt> option (which can also be
+specified as <tt class="literal">--force</tt>) forces a shutdown. The
+<tt class="literal">-t</tt> <em class="replaceable">timeout</em> option
+(which can also be specified as <tt class="literal">-
+-timeout=</tt><em class="replaceable">number</em>) specifies the
+number of seconds to wait before shutting down, and the
+<tt class="literal">-c</tt> <em class="replaceable">comment</em> option
+(which can also be specified as <tt class="literal">-
+-comment=</tt><em class="replaceable">string</em>) can be used to
+specify a message to the client user. On Windows, the comment appears
+in the Message area in the System Shutdown dialog box.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc trustdom add</tt> <em class="replaceable">domain_name</em></b></dt>
+<dd>
+<p>Adds an account for the trust relationship with the specified Windows
+NT domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc trustdom establish</tt> <em class="replaceable">domain_name</em></b></dt>
+<dd>
+<p>Establishes a trust relationship with the specified Windows NT domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rpc trustdom revoke</tt> <em class="replaceable">domain_name</em></b></dt>
+<dd>
+<p>Revokes the trust relationship with the specified Windows NT domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">search</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">ads search</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">server</tt></b></dt>
+<dd>
+<p>Lists servers in the domain or workgroup, which defaults to the value
+of the <tt class="literal">workgroup</tt> parameter in the Samba
+configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">session</tt></b></dt>
+<dd>
+<p>Lists clients with open sessions to the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">session delete NetBIOS_</tt><em class="replaceable">name</em></b></dt>
+<dd>
+<p>Closes the session to the server from the specified client. A synonym
+is <tt class="literal">session</tt> <tt class="literal">close</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">session close</tt></b></dt>
+<dd>
+<p>A synonym for <tt class="literal">session delete</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">share</tt></b></dt>
+<dd>
+<p>Lists the shares offered by the server. When a Windows 95/98/Me
+server is the target system, it might be necessary to specify the
+method as <tt class="literal">rap</tt> for this to work properly.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">share add</tt> <em class="replaceable">share_name</em><tt class="literal">=</tt><em class="replaceable">server_path</em></b></dt>
+<dd>
+<p>Adds a share on the target server. The name of the share and the
+folder to be shared are specified by the
+<em class="replaceable">share_name</em><tt class="literal">=</tt><em class="replaceable">server_path</em>
+argument, with <em class="replaceable">server_path</em> the Windows
+directory name, with spaces and other special characters (if any)
+quoted and with the backslashes escaped (e.g.,
+&quot;<tt class="literal">data=C:\\Documents</tt> <tt class="literal">and</tt>
+<tt class="literal">Settings\\jay\\Desktop\\data</tt>&quot;). The
+<tt class="literal">-C</tt> <em class="replaceable">comment</em> option
+(which can also be specified as <tt class="literal">-
+-comment=</tt><em class="replaceable">string</em>) can be used to
+define a description for the share. The <tt class="literal">-M</tt>
+<em class="replaceable">number</em> option (which can also be specified
+as <tt class="literal">--maxusers=</tt><em class="replaceable">number</em>)
+can be used to set the maximum number of users that can connect to
+the share. The method (<tt class="literal">rap</tt> or
+<tt class="literal">rpc</tt>) might need to be specified for this function
+to work. The regular folder icon cannot change into a
+&quot;shared folder&quot; icon in Windows
+Explorer until the display is refreshed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">share delete</tt> <em class="replaceable">share_name</em></b></dt>
+<dd>
+<p>Deletes a share from the target server. The
+<em class="replaceable">share_name</em> argument is simply the name of
+the share on the target server, not a UNC. The method
+(<tt class="literal">rap</tt> or <tt class="literal">rpc</tt>) might need to be
+specified for this function to work. The &quot;shared
+folder&quot; icon in Windows Explorer cannot change back
+to the regular folder icon until the display is refreshed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">shutdown</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">rpc shutdown</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">status</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">ads status</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">time</tt></b></dt>
+<dd>
+<p>Displays the system time&mdash;in Unix <em class="emphasis">date</em>
+command format&mdash;on the target system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">time set</tt></b></dt>
+<dd>
+<p>Sets the local system's hardware clock using the
+time obtained from the operating system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">time system</tt></b></dt>
+<dd>
+<p>Sets the time on the local system using the time obtained from the
+remote system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">time zone</tt></b></dt>
+<dd>
+<p>Prints the time zone (in hours from GMT) in use on the system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">trustdom add</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">rpc trustdom add</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">trustdom establish</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">rpc trustdom establish</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">trustdom revoke</tt></b></dt>
+<dd>
+<p>See the <tt class="literal">rpc trustdom revoke</tt> function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">user</tt></b></dt>
+<dd>
+<p>Lists user accounts. The method can be specified as
+<tt class="literal">ads</tt>, <tt class="literal">rap</tt>, or
+<tt class="literal">rpc</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">user add</tt> <em class="replaceable">username [password]</em></b></dt>
+<dd>
+<p>Adds a user account for the user specified by
+<em class="replaceable">username</em>. The <tt class="literal">-c</tt>
+<em class="replaceable">comment</em> option (which can also be
+specified as <tt class="literal">-
+-comment=</tt><em class="replaceable">string</em>) can be used to
+set a comment for the account. The <tt class="literal">-F</tt>
+<em class="replaceable">user_flags</em> option can be used to set flags
+(specified in numeric format) for the account. The method can be
+specified as <tt class="literal">ads</tt>, <tt class="literal">rap</tt>, or
+<tt class="literal">rpc</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">user delete</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Deletes the specified user's account. The method can
+be specified as <tt class="literal">ads</tt>, <tt class="literal">rap</tt>, or
+<tt class="literal">rpc</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">user info</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Lists the domain groups to which the specified user belongs. The
+method can be specified as <tt class="literal">ads</tt>,
+<tt class="literal">rap</tt>, or <tt class="literal">rpc</tt>. <a name="INDEX-10"/></p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-11"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>nmblookup</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">nmblookup</em> program is a client program that
+allows command-line access to NetBIOS name service for resolving
+NetBIOS computer names into IP addresses. The program works by
+broadcasting its queries on the local subnet until a machine with the
+specified name responds. You can think of it as a Windows analog of
+<em class="emphasis">nslookup</em> or <em class="emphasis">dig</em>. This is
+useful for looking up regular computer names, as well as
+special-purpose names, such as _ _MSBROWSE_ _ . If you wish to query
+for a particular type of NetBIOS name, add the NetBIOS type to the
+end of the name, using the format
+<em class="replaceable">netbios_name</em><tt class="literal">#&lt;</tt><em class="replaceable">dd</em><tt class="literal">&gt;</tt>.</p>
+<div class="sect1"><a name="appc-28-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">nmblookup <em class="replaceable">[options] netbios_name</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-29-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-A</tt></b></dt>
+<dd>
+<p>Interprets <em class="replaceable">netbios_name</em> as an IP address
+and does a node status query on it.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-B</tt> <em class="replaceable">broadcast_address</em></b></dt>
+<dd>
+<p>Sends the query to the given broadcast address. The default is to
+send the query to the broadcast address of the primary network
+interface.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Debug level 0 logs only the most important messages.
+Level 1 is normal; levels 3 and above are primarily used by
+developers for debugging the <em class="emphasis">nmblookup</em> program
+itself and slow the program considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-f</tt></b></dt>
+<dd>
+<p>Prints the flags in the packet headers.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints command-line usage information for the program.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt> <em class="replaceable">scope</em></b></dt>
+<dd>
+<p>Sets a NetBIOS scope identifier. NetBIOS scope is a rarely used
+precursor to workgroups.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-M</tt></b></dt>
+<dd>
+<p>Searches for a local master browser by looking up
+<em class="replaceable">netbios_name</em><tt class="literal">&lt;1d&gt;</tt>.
+If <em class="replaceable">netbios_name</em> is specified as a dash
+(<tt class="literal">-</tt>), a lookup is done on the special name _
+_MSBROWSE_ _ .</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-R</tt></b></dt>
+<dd>
+<p>Sets the &quot;recursion desired&quot; bit in
+the packet. This causes the system that responds to try a WINS lookup
+and return the address and any other information the WINS server has
+saved.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-r</tt></b></dt>
+<dd>
+<p>Uses the <tt class="literal">root</tt> port of 137. This option exists as a
+bug workaround for Windows 95. This option might require the user to
+be superuser.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-S</tt></b></dt>
+<dd>
+<p>Performs a node status query once the name query has returned an IP
+address. This returns all the resource types that the system knows
+about, including their numeric attributes. For example:</p>
+
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>nmblookup -S toltec</b></tt>
+querying toltec on 172.16.1.255
+172.16.1.1 toltec&lt;00&gt;
+Looking up status of 172.16.1.1
+    TOLTEC          &lt;00&gt; -         M &lt;ACTIVE&gt;
+    TOLTEC          &lt;03&gt; -         M &lt;ACTIVE&gt;
+    TOLTEC          &lt;20&gt; -         M &lt;ACTIVE&gt;
+    ..__MSBROWSE__. &lt;01&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt;
+    METRAN          &lt;00&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt;
+    METRAN          &lt;1b&gt; -         M &lt;ACTIVE&gt;
+    METRAN          &lt;1c&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt;
+    METRAN          &lt;1d&gt; -         M &lt;ACTIVE&gt;
+    METRAN          &lt;1e&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt;</pre></blockquote>
+</dd>
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">configuration_ file</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file. Although the
+file defaults to <em class="filename">/usr/local/samba/lib/smb.conf</em>,
+you can override it here on the command line. Normally used for
+debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-T</tt></b></dt>
+<dd>
+<p>Translates IP addresses into resolved names.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">unicast_address</em></b></dt>
+<dd>
+<p>Performs a unicast query to the specified address. Used with
+<tt class="literal">-R</tt> to query WINS servers.</p>
+</dd>
+
+</dl>
+
+
+<p>Note that <em class="emphasis">nmblookup</em> has no option for setting
+the workgroup. You can get around this by putting
+<tt class="literal">workgroup</tt> <tt class="literal">=</tt>
+<em class="replaceable">workgroup_name</em> in a file and passing it to
+<em class="emphasis">nmblookup</em> with the
+<tt class="literal">-s</tt> option.</p>
+
+</div>
+</div>
+
+<a name="INDEX-12"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>pdbedit</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program, new to Samba 3.0, can be used to manage accounts that
+are held in a SAM database. The implementation of the database can be
+any of the types supported by Samba, including the
+<em class="filename">smbpasswd</em> file, LDAP, NIS+ and the
+<em class="filename">tdb</em> database library. The user must be the
+superuser to use this tool.</p>
+<div class="sect1"><a name="appc-31-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">pdbedit <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-32-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt></b></dt>
+<dd>
+<p>Adds the user specified by the <tt class="literal">-u</tt> option to the
+SAM database. The command issues a prompt for the
+user's password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">drive_letter</em></b></dt>
+<dd>
+<p>Sets the Windows drive letter to which to map the
+user's home directory. The drive letter should be
+specified as a letter followed by a colon&mdash;e.g.,
+<tt class="literal">H</tt>:.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Debug level 0 logs only the most important messages.
+Level 1 is normal, and levels 3 and above are primarily for
+debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-e</tt> <em class="replaceable">pwdb_backend</em></b></dt>
+<dd>
+<p>Exports the user account database to another format, written to the
+specified location. Used for migrating from one type of account
+database to another. The <em class="replaceable">pwdb_backend</em>
+argument is specified in the format of a database type, followed by a
+colon, then the location of the database. For example, to export the
+existing account database to an <em class="filename">smbpasswd</em>
+database in the file
+<em class="filename">/usr/local/samba/private/smbpw</em>,
+<em class="replaceable">pwdb_backend</em> would be specified as
+<tt class="literal">smbpasswd:/usr/local/samba/private/smbpw</tt>. The
+allowable database types are <tt class="literal">smbpasswd</tt>,
+<tt class="literal">smbpasswd nua</tt>, <tt class="literal">tdbsam</tt>,
+<tt class="literal">tdbsam nua</tt>, <tt class="literal">ldapsam</tt>,
+<tt class="literal">ldapsam_nua</tt>, and <tt class="literal">plugin</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-f</tt> <em class="replaceable">full_name</em></b></dt>
+<dd>
+<p>Sets the full name of the user specified with the
+<tt class="literal">-u</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt> <em class="replaceable">unc</em></b></dt>
+<dd>
+<p>Sets the home directory path (as a UNC) for the user specified with
+the <tt class="literal">-u</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt> <em class="replaceable">pwdb_backend</em></b></dt>
+<dd>
+<p>Specifies a password database backend from which to retrieve account
+information, overriding the one specified by the <tt class="literal">passdb
+backend</tt> parameter in the Samba configuration file. This,
+along with the <tt class="literal">-e</tt> option, is useful for migrating
+user accounts from one type of account database to another. See the
+<tt class="literal">-e</tt> option regarding how to specify the
+<em class="replaceable">pwdb_backend</em> argument.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt></b></dt>
+<dd>
+<p>Lists the user accounts in the database. See also the
+<tt class="literal">-v</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-m</tt></b></dt>
+<dd>
+<p>Indicates that the account is a computer account rather than a user
+account. Used only with the <tt class="literal">-a</tt> option when
+creating the account. In this case, the <tt class="literal">-u</tt> option
+specifies the computer name rather than a username.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">unc</em></b></dt>
+<dd>
+<p>Sets the directory in which the user's profile is
+kept. The directory is specified as a UNC.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">unc</em></b></dt>
+<dd>
+<p>Specifies the UNC of the user's logon script.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-u</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Specifies the username of the account to add (with the
+<tt class="literal">-a</tt> option), delete (with the <tt class="literal">-x</tt>
+option), or modify.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-v</tt></b></dt>
+<dd>
+<p>Selects verbose mode when listing accounts with the
+<tt class="literal">-l</tt> option. The account fields will be printed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-w</tt></b></dt>
+<dd>
+<p>Selects the <tt class="literal">smbpasswd</tt> listing mode, for use with
+the <tt class="literal">-l</tt> option, which prints information in the
+same format as it would appear in an <em class="filename">smbpasswd</em>
+file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-x</tt></b></dt>
+<dd>
+<p>Deletes the user (specified with the <tt class="literal">-u</tt> option)
+from the account database.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-13"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>rpcclient</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This is a program for issuing administrative commands that are
+implemented using Microsoft RPCs. It provides access to the RPCs that
+Windows administrative GUIs use for system management. The
+<em class="emphasis">rpcclient</em> command is mainly for use by advanced
+users who understand the RPCs. More information on these can be found
+in Microsoft's Platform Software Development Kit
+(SDK), available for download from the Microsoft web site at
+<a href="http://www.microsoft.com">http://www.microsoft.com</a>.</p><p>You can run a single <em class="emphasis">rpcclient</em> command by using
+the <tt class="literal">-c command string</tt> option, or interactively
+with <em class="emphasis">rpcclient</em> prompting for commands.</p>
+<div class="sect1"><a name="appc-34-fm2xml"/>
+
+<h4 class="refsect1">Command Synopsis</h4>
+
+<p>rpcclient <em class="replaceable">server [options]</em></p>
+
+
+</div>
+
+<div class="sect1"><a name="appc-35-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-A</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies a file from which to read the authentication values used in
+the connection. The format of the file is as follows:</p>
+
+<blockquote><pre class="code">username = <em class="replaceable">value</em>
+password = <em class="replaceable">value</em>
+domain   = <em class="replaceable">value</em></pre></blockquote>
+
+<p>This option is used to avoid password prompts or to have the password
+appear in plain text inside scripts. The permissions on the file
+should be very restrictive (0600, for example) to prevent access from
+unwanted users.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-c</tt> <em class="replaceable">command_string</em></b></dt>
+<dd>
+<p>Executes a sequence of semicolon-separated commands. Commands are
+listed in the following section.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debuglevel</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0 to 10. Specifying the value on the command line overrides the
+value specified in the <em class="filename">smb.conf</em> file. Debug
+level 0 logs only the most important messages; level 1 is normal;
+levels 3 and above are primarily for debugging and slow the program
+considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints a summary of options.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt> <em class="replaceable">logbasename</em></b></dt>
+<dd>
+<p>Sets the filename for log/debug files. The extension
+<em class="filename">.client</em> is appended to the filename.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-N</tt></b></dt>
+<dd>
+<p>Does not prompt for a password. This is used when Samba is configured
+for share-mode security and a service with no password is being
+accessed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file, which by
+default is usually
+<em class="filename">/usr/local/samba/lib/smb.conf</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">username[</em><tt class="literal">%</tt><em class="replaceable">password]</em></b></dt>
+<dd>
+<p>Sets the SMB username or username and password to use. Be careful
+when specifying the password with
+<tt class="literal">%</tt><em class="replaceable">password</em>; this is a
+major security risk. If
+<tt class="literal">%</tt><em class="replaceable">password</em> is not
+specified, the user will be prompted for the password, which will not
+be echoed. Normally the user is set from the USER or LOGNAME
+environment variable. The <tt class="literal">-U</tt> option by itself
+means to use the guest account. See also <tt class="literal">-A</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-W</tt> <em class="replaceable">domain</em></b></dt>
+<dd>
+<p>Sets the domain, overriding the <tt class="literal">workgroup</tt>
+parameter in the Samba configuration file. If the domain is the
+server's NetBIOS name, it causes the client to log
+on using the server's local SAM database rather than
+the SAM of the domain.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-14"/><a name="INDEX-15"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>rpcclient commands</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>Aside from a few miscellaneous commands, the
+<em class="emphasis">rpclient</em> commands fall into three groups:
+LSARPC, SAMR, and SPOOLSS. The function names mentioned in some of
+the commands are those documented in the Microsoft Platform SDK.</p>
+<div class="sect1"><a name="appc-37-fm2xml"/>
+
+<h4 class="refsect1">General commands</h4>
+
+<dl>
+<dt><b><tt class="literal">debuglevel</tt> <em class="replaceable">level</em></b></dt>
+<dd>
+<p>Sets the debugging level to <em class="replaceable">level</em>. With no
+argument, the current debugging level is printed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">help</tt></b></dt>
+<dd>
+<p>Prints help on the commands.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">quit</tt></b></dt>
+<dd>
+<p>Exits <em class="emphasis">rpcclient</em>. A synonym is
+<tt class="literal">exit</tt>.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-38-fm2xml"/>
+
+<h4 class="refsect1">Local Security Authority Remote Procedure Calls (LSARPC) commands</h4>
+
+<dl>
+<dt><b><tt class="literal">enumprivs</tt></b></dt>
+<dd>
+<p>Lists the types of privileges known to this domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumtrust</tt></b></dt>
+<dd>
+<p>Lists the domains trusted by this domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">getdispname</tt> <em class="replaceable">priv_name</em></b></dt>
+<dd>
+<p>Prints information on the privilege named
+<em class="replaceable">priv_name</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookupsids</tt> <em class="replaceable">name</em></b></dt>
+<dd>
+<p>Finds a name that corresponds to a security identifier (SID).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lookupnames</tt> <em class="replaceable">sid</em></b></dt>
+<dd>
+<p>Finds the SID for one or more names.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lsaquery</tt></b></dt>
+<dd>
+<p>Queries the LSA object.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lsaenumsid</tt></b></dt>
+<dd>
+<p>Lists SIDs for the local LSA.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lsaquerysecobj</tt></b></dt>
+<dd>
+<p>Prints information on security objects for the LSA.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-39-fm2xml"/>
+
+<h4 class="refsect1">Security Access Manager RPC (SAMR) commands</h4>
+
+<dl>
+<dt><b><tt class="literal">createdomuser</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Adds a new user in the domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">deletedomuser</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Removes a user from the domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumalsgroups</tt> <em class="replaceable">type</em></b></dt>
+<dd>
+<p>Lists alias groups in the domain, along with their group RIDs. The
+<em class="replaceable">type</em> argument can be either
+<tt class="literal">builtin</tt>, to list Windows built-in groups such as
+<tt class="literal">Administrators</tt> and <tt class="literal">Power</tt>
+<tt class="literal">Users</tt>, or <tt class="literal">domain</tt>, to list
+groups in the domain. See also the
+<em class="emphasis">queryuseraliases</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumdomgroups</tt></b></dt>
+<dd>
+<p>Lists the groups in the domain, along with their group RIDs.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">queryaliasmem</tt> <em class="replaceable">user_rid</em></b></dt>
+<dd>
+<p>Prints information regarding alias membership. See also the
+<em class="emphasis">queryuseraliases</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">querydispinfo</tt></b></dt>
+<dd>
+<p>Prints out the account database. The information printed includes the
+RID, username, and full name of each user. The RID is printed in
+hexadecimal notation and can be used in this form for commands that
+take a RID as an argument.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">querydominfo</tt></b></dt>
+<dd>
+<p>Prints information regarding the domain. This includes the name of
+the domain, as well as the number of users, groups, and aliases.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">querygroup</tt> <em class="replaceable">group_rid</em></b></dt>
+<dd>
+<p>Given a group RID, prints the group name, description, number of
+members, and group description.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">queryuser</tt> <em class="replaceable">user_rid</em></b></dt>
+<dd>
+<p>Given a user RID, prints the corresponding username, full name, and
+other information pertaining to the user.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">queryuseraliases</tt> <em class="replaceable">type</em> <em class="replaceable">user_rid</em></b></dt>
+<dd>
+<p>Prints aliases for the user. The <em class="replaceable">type</em>
+argument can be either <tt class="literal">builtin</tt> or
+<tt class="literal">domain</tt>. Aliases are used with the Windows
+messaging service and act like usernames, but they can be attached to
+a computer rather than a user. This allows messages intended for a
+user to be sent to a computer on which the user is either not logged
+on, or logged on under another username.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">queryusergroups</tt> <em class="replaceable">user_rid</em></b></dt>
+<dd>
+<p>Prints information on each group inhabited by the user.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">querygroupmem</tt> <em class="replaceable">group_rid</em></b></dt>
+<dd>
+<p>Prints the RID and attributes for each member of the group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">samlookupnames</tt> <em class="replaceable">type username</em></b></dt>
+<dd>
+<p>Looks up the <em class="replaceable">username</em> in the SAM database
+and prints its associated RID. The <em class="replaceable">type</em>
+argument can be either <tt class="literal">builtin</tt>, to look up
+built-in Windows usernames, or <tt class="literal">domain</tt>, to look up
+names in the domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">samlookuprids</tt> <em class="replaceable">type rid</em></b></dt>
+<dd>
+<p>Looks up <em class="replaceable">rid</em> in the SAM database and
+prints its associated group or username. The
+<em class="replaceable">type</em> argument can be either
+<tt class="literal">builtin</tt>, to look up built-in Windows usernames, or
+<tt class="literal">domain</tt>, to look up names in the domain. The RID
+argument can be given in either 0xDDD hexadecimal notation or
+decimal.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">samquerysecobj</tt></b></dt>
+<dd>
+<p>Prints information on security objects (such as ACLs) in the SAM
+database.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-40-fm2xml"/>
+
+<h4 class="refsect1">Windows NT/2000/XP Printing Services (SPOOLSS) commands</h4>
+
+<dl>
+<dt><b><tt class="literal">adddriver</tt> <em class="replaceable">arch config_file</em> </b></dt>
+<dd>
+<p>Adds a printer driver to the server. The driver files must already
+exist in the directory returned by <em class="emphasis">getdriverdir</em>.
+The <em class="replaceable">arch</em> argument can be one of
+<tt class="literal">Windows 4.0</tt> for Windows 95/98/Me, or
+<tt class="literal">Windows NT x86</tt>, <tt class="literal">Windows NT
+PowerPC</tt>, <tt class="literal">Windows Alpha_AXP</tt>, and
+<tt class="literal">Windows NT R4000</tt>. Others might be introduced in
+the future.</p>
+
+
+<p>The <em class="replaceable">config_file</em> should contain:</p>
+
+<blockquote><pre class="code">Long Printer Name:\
+Driver File Name:\
+Data File Name:\
+Config File Name:\
+Help File Name:\
+NULL:\
+Default Data Type:\</pre></blockquote>
+
+<p>followed by a comma-separated list of files. Any empty fields should
+contain the string <tt class="literal">NULL</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">addprinter</tt> <em class="replaceable">printername sharename drivername port</em> </b></dt>
+<dd>
+<p>Adds a printer on the remote server as
+<em class="replaceable">sharename</em>. The printer driver must already
+be installed on the server with <em class="emphasis">adddriver</em>, and
+the port must be a valid port name returned by
+<em class="emphasis">enumports</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">deldriver</tt> <em class="replaceable">drivername</em></b></dt>
+<dd>
+<p>Deletes a printer driver (for all architectures) from the
+server's list of printer drivers.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumports</tt> <em class="replaceable">[level]</em></b></dt>
+<dd>
+<p>Prints information regarding the printer ports on the server. The
+<em class="replaceable">level</em> argument can be <tt class="literal">1</tt>
+or <tt class="literal">2</tt>. Level 1 is the default and prints out only
+the Port Name. Information level 2 is the Port Name, Monitor Name,
+Description, and Port Type.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumdrivers</tt> <em class="replaceable">[level]</em> </b></dt>
+<dd>
+<p>Lists all the printer drivers on the system. The
+<em class="replaceable">level</em> argument specifies the information
+level. Level 1 is the default and prints the Driver Name(s). Level 2
+prints the Version, Driver Name, Architecture, Driver Path, Data
+File, and Config File. Level 3 prints the contents of Level 2, plus
+the Help File, one or more Dependent Files, Monitor Name, and Default
+Data Type.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">enumprinters</tt> <em class="replaceable">[level]</em></b></dt>
+<dd>
+<p>Lists all installed printers, regardless of whether they are shared.
+The <em class="replaceable">level</em> argument specifies the
+information level. Level 1 is the default, and prints Flags, Name,
+Description, and Comment. Level 2 prints the Server Name, Printer
+Name, Share Name, Port Name, Driver Name, Comment, Location,
+Separator File, Print Processor, Data Type, Parameters, Attributes,
+Priority, Default Priority, Start Time, Until Time, Status, Current
+Jobs, Average PPM (pages per minute), and a Security Descriptor.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">getdriver</tt> <em class="replaceable">[level] printername</em></b></dt>
+<dd>
+<p>Prints the printer driver information for the given printer. The
+<em class="replaceable">level</em> argument specifies the information
+level.</p>
+
+
+<p>Level 1 is the default, and prints the Driver Name. Level 2 prints
+the Version, Driver Name, Architecture, Driver Path, Data File, and
+Config File. Level 3 prints the contents of level 2, plus the Help
+File, one or more Dependent Files, Monitor Name, and Default Data
+Type.</p>
+</dd>
+
+
+<dt><b><tt class="literal">getdriverdir</tt> <em class="replaceable">arch</em></b></dt>
+<dd>
+<p>Retrieves the share name and directory for storing printer driver
+files for a given architecture. Possible values for
+<em class="replaceable">arch</em> are &quot;<tt class="literal">Windows</tt>
+<tt class="literal">4.0</tt>&quot; for Windows 95/98/Me,
+&quot;<tt class="literal">Windows</tt> <tt class="literal">NT</tt>
+<tt class="literal">x86</tt>&quot; for Windows NT on Intel,
+&quot;<tt class="literal">Windows</tt> <tt class="literal">NT</tt>
+<tt class="literal">PowerPC</tt>&quot; for Windows NT on PowerPC,
+&quot;<tt class="literal">Windows</tt> <tt class="literal">Alpha</tt>
+<tt class="literal">AXP</tt>&quot; for Windows NT on Alpha, and
+&quot;<tt class="literal">Windows</tt> <tt class="literal">NT</tt>
+<tt class="literal">R4000</tt>&quot; for Windows NT on MIPS. Include the quote
+marks in the command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">getprinter</tt> <em class="replaceable">printername</em></b></dt>
+<dd>
+<p>Prints the current printer information. The
+<em class="replaceable">level</em> argument specifies the information
+level.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">openprinter</tt> <em class="replaceable">printername</em></b></dt>
+<dd>
+<p>Attempts to open and close a specified printer and reports whether it
+was successful.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">setdriver</tt> <em class="replaceable">printername drivername</em></b></dt>
+<dd>
+<p>Unconditionally updates the printer driver used by an installed
+printer. Both the printer and printer driver must already be
+correctly installed on the print server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">setprinter</tt> <em class="replaceable">printername comment</em></b></dt>
+<dd>
+<p>Assigns a comment string to a printer.<a name="INDEX-15"/></p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-16"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbcacls</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program provides a way of modifying Windows NT ACLs on files and
+directories shared by the Samba server.</p>
+<div class="sect1"><a name="appc-42-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbcacls //<em class="replaceable">server</em>/<em class="replaceable">share filename</em> <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-43-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-A</tt> <em class="replaceable">acls</em></b></dt>
+<dd>
+<p>Adds one or more ACLs to the file or directory. Any ACLs already
+existing for the file or directory are unchanged.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-M</tt> <em class="replaceable">acls</em></b></dt>
+<dd>
+<p>Modifies the <em class="replaceable">mask</em> of the ACLs specified.
+Refer to the following section, &quot;Specifying
+ACLs,&quot; for details.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt> <em class="replaceable">acls</em></b></dt>
+<dd>
+<p>Deletes the specified ACLs.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-S</tt> <em class="replaceable">acls</em></b></dt>
+<dd>
+<p>Sets the specified ACLs, deleting any ACLs previously set on the file
+or directory. The ACLs must contain at least a revision, type, owner,
+and group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Sets the username used to connect to the specified service. The user
+is prompted for a password unless the argument is specified as
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>.
+(Specifying the password on the command line is a security risk.) If
+<tt class="literal">-U</tt>
+<em class="replaceable">domain</em><tt class="literal">\\</tt><em class="replaceable">username</em>
+is specified, the specified domain or workgroup will be used in place
+of the one specified in the <em class="filename">smb.conf</em> file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-C</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Changes the owner of the file or directory. This is a shortcut for
+<tt class="literal">-M</tt>
+<tt class="literal">OWNER</tt>:<em class="replaceable">username</em>. The
+<em class="replaceable">username</em> argument can be given as a
+username or a SID in the form
+<tt class="literal">S-1-</tt><em class="replaceable">N-N-D-D-D-R</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-G</tt> <em class="replaceable">groupname</em></b></dt>
+<dd>
+<p>Changes the group of the file or directory. This is a shortcut for
+<tt class="literal">-M</tt>
+<tt class="literal">GROUP</tt>:<em class="replaceable">groupname</em>. The
+<em class="replaceable">groupname</em> argument can be given as a group
+name or a SID in the form
+<tt class="literal">S-1-</tt><em class="replaceable">N-N-D-D-D-R</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt></b></dt>
+<dd>
+<p>Causes all ACL information to be displayed in numeric format rather
+than in readable strings.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints a help message.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-44-fm2xml"/>
+
+<h4 class="refsect1">Specifying ACLs</h4>
+<p>In the previous options, the same format is always used when
+specifying ACLs. An ACL is made up of one or more Access Control
+Entries (ACEs), separated by either commas or escaped newlines. An
+ACE can be one of the following:</p>
+
+<blockquote class="simplelist">
+
+<p><tt class="literal">REVISION</tt>:<em class="replaceable">revision_number</em></p>
+
+
+
+
+<p><tt class="literal">OWNER</tt>:<em class="replaceable">username_or_SID</em></p>
+
+
+
+
+<p><tt class="literal">GROUP</tt>:<em class="replaceable">group_name_or_SID</em></p>
+
+
+
+
+<p><tt class="literal">ACL</tt>:<em class="replaceable">name_or_SID</em>:<em class="replaceable">type</em>/<em class="replaceable">flags</em>/<em class="replaceable">mask</em></p>
+
+</blockquote>
+
+
+<p>The <em class="replaceable">revision_number</em> should always be 1.
+The <tt class="literal">OWNER</tt> and <tt class="literal">GROUP</tt> entries can
+be used to set the owner and group for the file or directory. The
+names can be the textual ones or SIDs in the form
+<tt class="literal">S-1-</tt><em class="replaceable">N</em><tt class="literal">-</tt><em class="replaceable">N</em><tt class="literal">-</tt><em class="replaceable">D</em><tt class="literal">-</tt><em class="replaceable">D-D-R</em>.</p>
+
+<p>The <tt class="literal">ACL</tt> entry specifies what access rights to
+apply to the file or directory. The
+<em class="replaceable">name_or_SID</em> field specifies to which user
+or group the permissions apply and can be supplied either as a
+textual name or a SID. An ACE can be used to either allow or deny
+access. The <em class="replaceable">type</em> field is set to
+<tt class="literal">1</tt> to specify a permission to be allowed or
+<tt class="literal">0</tt> for specifying a permission to deny. The
+<em class="replaceable">mask</em> field is the name of the permission
+and is one of the following:</p>
+
+<dl>
+<dt><b><tt class="literal">R</tt></b></dt>
+<dd>
+<p>Read access.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">W</tt></b></dt>
+<dd>
+<p>Write access.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">X</tt></b></dt>
+<dd>
+<p>Execute permission.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">D</tt></b></dt>
+<dd>
+<p>Permission to delete.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">P</tt></b></dt>
+<dd>
+<p>Change permissions on the object.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">O</tt></b></dt>
+<dd>
+<p>Take ownership.</p>
+</dd>
+
+</dl>
+
+
+<p>The following combined permissions can also be specified:</p>
+
+<dl>
+<dt><b><tt class="literal">READ</tt></b></dt>
+<dd>
+<p>Equivalent to RX permissions</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">CHANGE</tt></b></dt>
+<dd>
+<p>Equivalent to RWXD permissions</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">FULL</tt></b></dt>
+<dd>
+<p>Equivalent to RWXDPO permissions</p>
+</dd>
+
+</dl>
+
+
+<p>The <em class="replaceable">flags</em> field is for specifying how
+objects in directories are to inherit their default permissions from
+their parent directory. For files, <em class="replaceable">flags</em>
+is normally set to <tt class="literal">0</tt>. For directories,
+<em class="replaceable">flags</em> is usually set to either
+<tt class="literal">9</tt> or <tt class="literal">2</tt>.</p>
+
+</div>
+</div>
+
+<a name="INDEX-17"/><a name="INDEX-18"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbclient</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbclient</em> program is the
+&quot;Swiss army knife&quot; of the Samba
+suite. Initially developed as a testing tool, it has become a command
+shell capable of acting as a general-purpose Unix client, with a
+command set very similar to that of <em class="emphasis">ftp</em>. It
+offers the following set of functions:</p><ul><li>
+<p>Interactive file transfer, similar to <em class="emphasis">ftp</em></p>
+</li>
+<li>
+<p>Interactive printing to shared SMB printers</p>
+</li>
+<li>
+<p>Interactive tar format archiving</p>
+</li>
+<li>
+<p>Sending messages on the SMB network</p>
+</li>
+<li>
+<p>Batch mode tar format archiving</p>
+</li>
+<li>
+<p>&quot;What services do you have?&quot;
+querying</p>
+</li>
+<li>
+<p>Debugging</p>
+</li></ul>
+<div class="sect1"><a name="appc-45-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbclient //<em class="replaceable">server</em>/<em class="replaceable">share</em> <em class="replaceable">[ password] [options]</em></pre></blockquote>
+<p>It is possible to run <em class="emphasis">smbclient</em>
+noninteractively, for use in scripts, by specifying the
+<tt class="literal">-c</tt> option along with a list of commands to
+execute. Otherwise, <em class="emphasis">smbclient</em> runs in
+interactive mode, prompting for commands such as this:</p>
+
+<blockquote><pre class="code">smb:\&gt;</pre></blockquote>
+<p>The backslash in the prompt is replaced by the current directory
+within the share as you change your working directory with
+<em class="emphasis">smbclient</em>'s
+<em class="emphasis">cd</em> command.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-46-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-A</tt> <em class="replaceable">authfile</em></b></dt>
+<dd>
+<p>Specifies a file from which to read the username and password used
+for the connection. The format of the file is as follows:</p>
+
+
+<blockquote><pre class="code">username = <em class="replaceable">value</em>
+password = <em class="replaceable">value</em>
+domain   = <em class="replaceable">value</em></pre></blockquote>
+
+<p>This is to avoid having the password prompted for or have it appear
+in plain text in scripts. The permissions on the file should be very
+restrictive (0600, for example) to prevent access by unwanted users.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-b</tt> <em class="replaceable">buffer_size</em></b></dt>
+<dd>
+<p>Sets the size of the buffer used when transferring files. It defaults
+to 65520 bytes and can be changed as a tuning measure. Generally it
+should be quite large or set to match the size of the buffer on the
+remote system. It can be set smaller to work around Windows bugs:
+some Windows 98 systems work best with a buffer size of 1200.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-B</tt> <em class="replaceable">IP_addr</em></b></dt>
+<dd>
+<p>Sets the broadcast address.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-c</tt> <em class="replaceable">command_string</em> </b></dt>
+<dd>
+<p>Passes a command string to the <em class="emphasis">smbclient</em> command
+interpreter. The argument consists of a semicolon-separated list of
+commands to be executed.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-d</em> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (logging) level, from 0 to 10, with A for all.
+Overrides the value in <em class="filename">smb.conf</em>. Debug level 0
+logs only the most important messages; level 1 is normal; debug
+levels 3 and above are for debugging and slow
+<em class="emphasis">smbclient</em> considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt> <em class="replaceable">init_dir</em></b></dt>
+<dd>
+<p>Upon starting up, causes <em class="emphasis">smbclient</em> to change its
+working directory to <em class="replaceable">init_dir</em> on the
+remote host.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-E</tt></b></dt>
+<dd>
+<p>Sends output from commands to <em class="emphasis">stderr</em> instead of
+<em class="emphasis">stdout</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints the command-line help information (usage) for
+<em class="emphasis">smbclient</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-I</tt> <em class="replaceable">IP_address</em></b></dt>
+<dd>
+<p>Sets the IP address of the server to which the client connects.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt> <em class="replaceable">scope</em></b></dt>
+<dd>
+<p>Sets a NetBIOS scope identifier.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt> <em class="replaceable">log_ file</em></b></dt>
+<dd>
+<p>Sends the log messages to <em class="replaceable">log_file</em> rather
+than to the log file specified in the Samba configuration file or the
+compiled-in default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-L</tt> <em class="replaceable">server</em></b></dt>
+<dd>
+<p>Lists services (shares) offered by the server. This can be used as a
+quick way to test an SMB server to see if it is working. If there is
+a name-service problem, use the <tt class="literal">-I</tt> option to
+specify the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-M</tt> <em class="replaceable">NetBIOS_name</em></b></dt>
+<dd>
+<p>Allows you to send messages using the Windows messaging protocol.
+Once a connection is established, you can type your message, pressing
+Ctrl-D to end. The <tt class="literal">-U</tt> and <tt class="literal">-I</tt>
+options can be used to control the
+&quot;From&quot; and
+&quot;To&quot; parts of the message.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-N</tt></b></dt>
+<dd>
+<p>Suppresses the password prompt. Useful when using share mode security
+and accessing a service that has no password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt> <em class="replaceable">NetBIOS_name</em></b></dt>
+<dd>
+<p>Allows you to override the NetBIOS name by which
+<em class="emphasis">smbclient</em> will advertise itself.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-O</tt> <em class="replaceable">socket_options</em></b></dt>
+<dd>
+<p>Sets the TCP/IP socket options using the same parameters as the
+<tt class="literal">socket options</tt> configuration option. Often used
+for performance tuning and testing.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">port_number</em></b></dt>
+<dd>
+<p>Sets the port number with which <em class="emphasis">smbclient</em> will
+connect.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-R</tt> <em class="replaceable">resolve_order</em></b></dt>
+<dd>
+<p>Sets the resolve order of the name servers. This option is similar to
+the <tt class="literal">resolve</tt> <tt class="literal">order</tt> configuration
+option and can take any of the four parameters
+<tt class="literal">lmhosts</tt>, <tt class="literal">host</tt>,
+<tt class="literal">wins</tt>, and <tt class="literal">bcast</tt>, in any order.
+If more than one is specified, the argument is specified as a
+space-separated list. This option can be used to test name service by
+specifying only the name service to be tested.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file. Used for
+debugging.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-t</tt> <em class="replaceable">terminal_code</em></b></dt>
+<dd>
+<p>Sets the terminal code for Asian languages.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-T</tt> <em class="replaceable">command_string tarfile</em></b></dt>
+<dd>
+<p>Runs the tar archiver, which is <em class="emphasis">gtar</em> compatible.
+The tar file that is written to or read from is specified by
+<em class="replaceable">tarfile</em>. The two main commands are
+<tt class="literal">c</tt> (create) and <tt class="literal">x</tt> (extract),
+which can be followed by any of these:</p>
+
+<dl>
+<dt><b><tt class="literal">a</tt></b></dt>
+<dd>
+<p>Resets the archive attribute on files after they have been saved. See
+also the <tt class="literal">g</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">b</tt> <em class="replaceable">size</em></b></dt>
+<dd>
+<p>Sets the block size for writing the tar file, in 512-byte units.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">g</tt></b></dt>
+<dd>
+<p>Backs up only files that have their archive bit set. See also the
+<tt class="literal">a</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">I</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Includes files and directories. This is the default, so specifying
+this is redundant. To perform pattern matching, see also the
+<tt class="literal">r</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">N</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Backs up only those files newer than <em class="replaceable">file</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">q</tt></b></dt>
+<dd>
+<p>Suppresses diagnostics.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">r</tt></b></dt>
+<dd>
+<p>Performs regular expression matching, which can be used along with
+the <tt class="literal">I</tt> or <tt class="literal">E</tt> option to include or
+exclude files.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">X</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Excludes files and directories.</p>
+</dd>
+
+</dl>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Sets the username and, optionally, the password used for
+authentication when connecting to the share.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-W</tt> <em class="replaceable">workgroup</em></b></dt>
+<dd>
+<p>Specifies the workgroup/domain in which
+<em class="emphasis">smbclient</em> will claim to be a member.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-47-fm2xml"/>
+
+<h4 class="refsect1">smbclient commands</h4>
+
+<dl>
+<dt><b><tt class="literal">help</tt> <em class="replaceable">[smbclient_command]</em></b></dt>
+<dd>
+<p>With no command specified, prints a list of available commands. If a
+command is specified as an argument, a brief help message will be
+printed for it.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">!</tt> <em class="replaceable">[shell_command]</em></b></dt>
+<dd>
+<p>Shell escape. With no command specified, runs a Unix shell. If a
+command is specified, runs the command in a Unix shell.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">altname</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbclient</em> to request from the server and
+then print the old-style, 8.3-format filename for the specified file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">cancel</tt> <em class="replaceable">print_jobid [...]</em></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbclient</em> to request the server to cancel
+one or more print jobs, as specified by the numeric job IDs provided
+as arguments. See also the <em class="emphasis">queue</em> command, which
+prints job IDs.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">chmod</tt> <em class="replaceable">filename octal_mode</em></b></dt>
+<dd>
+<p>Requests that the server change the Unix file permissions on
+<em class="replaceable">filename</em> to
+<em class="replaceable">octal_mode</em>, specified in octal numeric
+format. Works only if the server supports Unix CIFS extensions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">chown</tt> <em class="replaceable">filename UID GID</em></b></dt>
+<dd>
+<p>Requests that the server change the owner and group of the file
+specified by <em class="replaceable">filename</em> to those provided as
+decimal numeric arguments <em class="replaceable">UID</em> and
+<em class="replaceable">GID</em>. Works only if the server supports
+Unix CIFS extensions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">cd</tt> <em class="replaceable">[directory]</em></b></dt>
+<dd>
+<p>With no argument, prints the current working directory on the remote
+system. If a directory name is supplied as an argument, changes the
+working directory on the remote system to that specified.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">del</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Requests that the server delete one or more files, as specified by
+the argument, from the current working directory. The argument can be
+a filename globbing pattern using the * and ? characters.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">dir</tt> [<em class="replaceable">filename]</em></b></dt>
+<dd>
+<p>With no arguments, prints a list of files and directories in the
+working directory on the server. If an argument is provided, only
+files and directories whose names match the argument will be listed.
+The argument can be a filename globbing pattern using the * and ?
+characters.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">exit</tt></b></dt>
+<dd>
+<p>Quits the <em class="emphasis">smbclient</em> program after terminating
+the SMB connection to the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">get</tt> <em class="replaceable">remote_file [local_file]</em></b></dt>
+<dd>
+<p>Copies the file specified by <em class="replaceable">remote_file</em>
+from the server to the local system. If no
+<em class="replaceable">local_file</em> argument is specified,
+<em class="emphasis">smbclient</em> will name the local file the same as
+it is named on the server. If <em class="replaceable">local_file</em>
+is specified, it will be used as the name of the local copy. See also
+the <em class="emphasis">lowercase</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">help</tt> <em class="replaceable">[command]</em></b></dt>
+<dd>
+<p>A synonym for the <em class="emphasis">?</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lcd</tt> <em class="replaceable">[directory]</em></b></dt>
+<dd>
+<p>If no argument is provided, prints the name of
+<em class="emphasis">smbclient</em>'s working directory
+on the local system. If a directory name is provided as an argument,
+changes <em class="emphasis">smbclient</em>'s working
+directory to the directory specified.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">link</tt> <em class="replaceable">link_name filename</em></b></dt>
+<dd>
+<p>Requests that the server create a hard link to
+<em class="replaceable">filename</em> and name it
+<em class="replaceable">link_name</em>. This command works only if the
+server supports Unix CIFS extensions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">lowercase</tt></b></dt>
+<dd>
+<p>Toggles the boolean lowercasing setting. When this setting is on,
+names of files copied from the server with the
+<em class="emphasis">get</em> and <em class="emphasis">mget</em> commands will
+be changed to all lowercase. This is mainly used for accessing
+servers that report filenames in all uppercase only.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ls</tt> <em class="replaceable">[filename]</em></b></dt>
+<dd>
+<p>A synonym for <em class="emphasis">dir</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">mask</tt> <em class="replaceable">[globbing_pattern]</em></b></dt>
+<dd>
+<p>Sets the filename globbing pattern for use with the
+<em class="emphasis">mget</em> and <em class="emphasis">mput</em> commands when
+recursion is turned on. (When recursion is off, the setting has no
+effect.) Both <em class="emphasis">mget</em> and <em class="emphasis">mput</em>
+accept a globbing pattern as arguments; however, those patterns apply
+only to the current directory. This command specifies the pattern
+used for all subdirectories that are recursively traversed. The
+pattern stays in effect until it is changed with another
+<em class="emphasis">mask</em> command. To return the setting to its
+original default, specify a
+<em class="replaceable">globbing_pattern</em> of an asterisk
+(<tt class="literal">*</tt>), which matches all files. See also the
+<em class="emphasis">mget</em>, <em class="emphasis">mput</em>, and
+<em class="emphasis">recurse</em> commands.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">mdir</tt> <em class="replaceable">directory</em></b></dt>
+<dd>
+<p>A synonym for the <em class="emphasis">mkdir</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">mget</tt> <em class="replaceable">pattern</em></b></dt>
+<dd>
+<p>When recursion is turned off, copies files matching the file-globbing
+pattern, as specified by the argument, from the current working
+directory on the server to the local system. When recursion is on,
+the <em class="replaceable">pattern</em> argument is used to match
+directories in the current working directory, and the pattern
+specified by the <em class="emphasis">mask</em> command is used for
+matching files within each directory and all subdirectories. See also
+the <em class="emphasis">lowercase</em>, <em class="emphasis">mask</em>, and
+<em class="emphasis">recurse</em> commands.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">print</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Prints the specified file. This requires that
+<em class="emphasis">smbclient</em> be connected to a print share. See
+also the <em class="emphasis">printmode</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printmode</tt> <em class="replaceable">mode</em></b></dt>
+<dd>
+<p>Sets the mode that is used by the <em class="emphasis">print</em> command.
+The mode can be either <tt class="literal">text</tt>, for printing text
+files such as the ASCII files commonly found on Unix, or
+<tt class="literal">graphics</tt>, for printing binary files.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">prompt</tt></b></dt>
+<dd>
+<p>Toggles the prompting mode. When prompting is on (the default), the
+<em class="emphasis">mget</em> and <em class="emphasis">mput</em> commands will
+interactively prompt the user for permission to transfer each file.
+The user can answer either <tt class="literal">y</tt> (yes) or
+<tt class="literal">n</tt> (no), followed by a newline, to this prompt.
+When prompting is off, all the files will be transferred with no
+prompts issued.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">put</tt> <em class="replaceable">local_file [remote_file]</em></b></dt>
+<dd>
+<p>Copies the file specified by <em class="replaceable">local_file</em>
+from the local to the remote system. If no
+<em class="replaceable">remote_file</em> argument is specified,
+<em class="emphasis">smbclient</em> will name the remote file the same as
+it is named on the local system. If
+<em class="replaceable">remote_file</em> is specified, it will be used
+as the name of the remote copy. See also the
+<em class="emphasis">lowercase</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">queue</tt></b></dt>
+<dd>
+<p>Prints information on the print queue on the server. This requires
+that <em class="emphasis">smbclient</em> is connected to a print share.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">quit</tt></b></dt>
+<dd>
+<p>A synonym for <em class="emphasis">exit</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rd</tt> <em class="replaceable">directory</em></b></dt>
+<dd>
+<p>A synonym for <em class="emphasis">rmdir</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">recurse</tt></b></dt>
+<dd>
+<p>Toggles the recursion mode, which affects the
+<em class="emphasis">mget</em> and <em class="emphasis">mput</em> commands.
+When recursion is off (the default), the <em class="emphasis">mget</em>
+and <em class="emphasis">mput</em> commands will copy only files from the
+current working directory that match the file-globbing pattern
+specified as an argument to the command, and the pattern set by the
+<em class="emphasis">mask</em> command is ignored. When recursion is
+turned on, the <em class="emphasis">mget</em> and
+<em class="emphasis">mput</em> commands recursively traverse any
+directories that match the pattern specified as the argument to the
+command, and the pattern set by the <em class="emphasis">mask</em> command
+is used to match files in those directories.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rm</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>A synonym for <em class="emphasis">del</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rmdir</tt> <em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Requests that the server remove the specified directory.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">setmode</tt> <em class="replaceable">filename attributes</em></b></dt>
+<dd>
+<p>Requests that the server assign the specified MS-DOS file attributes
+on the specified file. The <em class="replaceable">attributes</em>
+argument has the format of a leading plus sign (<tt class="literal">+</tt>)
+or minus sign (<tt class="literal">-</tt>) either to set or to unset the
+attribute(s), respectively, followed by one or more of the characters
+<tt class="literal">r</tt> (read), <tt class="literal">s</tt> (system),
+<tt class="literal">h</tt> (hidden), or <tt class="literal">a</tt> (archive).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">symlink</tt> <em class="replaceable">link_name filename</em></b></dt>
+<dd>
+<p>Requests that the server create a symbolic link named
+<em class="replaceable">link_name</em> to
+<em class="replaceable">filename</em>. This command works only if the
+server supports Unix CIFS extensions. The server will not create a
+link that refers to a file not in the share to which
+<em class="emphasis">smbclient</em> is connected.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">tar</tt> <em class="replaceable">cmd_str</em></b></dt>
+<dd>
+<p>Performs an archiving operation using the tar format. This is the
+interactive form of the <tt class="literal">-T</tt> command-line operation,
+and the <em class="replaceable">cmd_str</em> argument is specified in
+the same manner. See also the <em class="emphasis">tarmode</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">blocksize</tt> <em class="replaceable">size</em></b></dt>
+<dd>
+<p>Sets the block size, in units of 512 bytes, for files written by the
+<em class="emphasis">tar</em> command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">tarmode</tt> <em class="replaceable">mode ...</em></b></dt>
+<dd>
+<p>Specifies how the <em class="emphasis">tar</em> command performs its
+archiving, including how it handles the archive attribute on files.
+Multiple <em class="replaceable">mode</em> arguments can be provided,
+chosen from the following:</p>
+
+<dl>
+<dt><b><tt class="literal">full</tt></b></dt>
+<dd>
+<p>All files will be included, regardless of whether their
+<tt class="literal">archive</tt> attribute is set. This is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">inc</tt></b></dt>
+<dd>
+<p>Only files that have the <tt class="literal">archive</tt> attribute set
+will be included in the backup.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">reset</tt></b></dt>
+<dd>
+<p>The <tt class="literal">archive</tt> attribute will be unset by
+<em class="emphasis">tar</em> after the file is included in the archive.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">noreset</tt></b></dt>
+<dd>
+<p>The <tt class="literal">archive</tt> attribute will be left unchanged. This
+is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">system</tt></b></dt>
+<dd>
+<p>Files with the <tt class="literal">system</tt> attribute set will be
+included in the archive. This is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">nosystem</tt></b></dt>
+<dd>
+<p>Files with the <tt class="literal">system</tt> attribute set will not be
+included in the archive.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">hidden</tt></b></dt>
+<dd>
+<p>Files with the <tt class="literal">hidden</tt> attribute set will be
+included in the archive. This is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">nohidden</tt></b></dt>
+<dd>
+<p>Files with the <tt class="literal">hidden</tt> attribute set will not be
+included in the archive.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">verbose</tt></b></dt>
+<dd>
+<p>As files are included in the archive (when creating the archive) or
+are read from the archive (when extracting it), the name of each file
+will be printed. This is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">noverbose</tt></b></dt>
+<dd>
+<p>This turns verbose mode off, causing <em class="emphasis">tar</em> to
+perform its work quietly.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">quiet</tt></b></dt>
+<dd>
+<p>An antonym for the <tt class="literal">verbose</tt> mode. When quiet is on,
+verbose is off, and vice versa.<a name="INDEX-18"/></p>
+</dd>
+
+</dl>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-19"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbcontrol</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbcontrol</em> command sends control messages to
+running <em class="emphasis">smbd</em> or <em class="emphasis">nmbd</em>
+processes.</p>
+<div class="sect1"><a name="appc-49-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbcontrol -i<em class="replaceable"> [options]</em></pre></blockquote>
+<p>or:</p>
+
+<blockquote><pre class="code">smbcontrol <em class="replaceable">[options] process message-type [parameters]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-50-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-i</tt></b></dt>
+<dd>
+<p>Runs <em class="emphasis">smbcontrol</em> interactively, executing
+commands until a blank line or &quot;q&quot;
+is read. The user must have superuser privileges.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the location of the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">debuglevel</em></b></dt>
+<dd>
+<p>Sets the debugging level for logging. The debug level can be set from
+to 10.</p>
+</dd>
+
+</dl>
+
+
+<p>Whether <em class="emphasis">smbcontrol</em> commands are issued in
+interactive mode or from the command line, the commands are in the
+same format. Each command has up to three parts:</p>
+
+<dl>
+<dt><b><em class="replaceable">process</em></b></dt>
+<dd>
+<p>Specifies the process or group of processes to which to send the
+message. If <em class="replaceable">process</em> is
+<tt class="literal">smbd</tt>, all <em class="emphasis">smbd</em> processes will
+receive the message. If <em class="replaceable">process</em> is
+<tt class="literal">nmbd</tt>, only the main <em class="emphasis">nmbd</em>
+process (identified by Samba's
+<em class="filename">nmbd.pid</em> file) receives the message. If
+<em class="replaceable">process</em> is the numeric PID of a running
+process on the system, that process will receive the message.</p>
+</dd>
+
+
+
+<dt><b><em class="replaceable">message-type</em></b></dt>
+<dd>
+<p>Specifies the type of message that is sent. For more information, see
+<a href="appc.html#appc-51-fm2xml">smbcontrol message
+types</a> that follows.</p>
+</dd>
+
+
+
+<dt><b><em class="replaceable">parameters</em></b></dt>
+<dd>
+<p>Specifies additional parameters required by some messages.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-51-fm2xml"/>
+
+<h4 class="refsect1">smbcontrol message types</h4>
+
+<dl>
+<dt><b><tt class="literal">close-share</tt> <em class="replaceable">share_name</em></b></dt>
+<dd>
+<p>Closes the connection to a share or shares. If
+<em class="replaceable">share_name</em> is specified as an asterisk
+(<tt class="literal">*</tt>), connections to all shares will be closed. To
+close a single connection, <em class="replaceable">share_name</em> is
+given as the name of a share, as specified in the Samba configuration
+file, not including the enclosing brackets. Warning: no message is
+printed if there is an error in specifying
+<em class="replaceable">share_name</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">debug</tt> <em class="replaceable">num</em></b></dt>
+<dd>
+<p>Sets the debugging level. The <em class="replaceable">num</em>
+parameter specifies the level, which can be from 0 to 10.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">debuglevel</tt></b></dt>
+<dd>
+<p>Prints the current debugging level.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">force-election</tt></b></dt>
+<dd>
+<p>Can be used only with <em class="emphasis">nmbd</em>, telling it to force
+a master browser election.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ping</tt> <em class="replaceable">number</em></b></dt>
+<dd>
+<p>Sends <em class="emphasis">number</em> of pings and reports when they
+receive a reply or timeout. Used for connectivity testing.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">profile</tt> <em class="replaceable">mode</em></b></dt>
+<dd>
+<p>Controls profiling statistics collection. If
+<em class="replaceable">mode</em> is <tt class="literal">on</tt>, profile
+statistics will be collected. If <em class="replaceable">mode</em> is
+<tt class="literal">off</tt>, collection of statistics is turned off. If
+<em class="replaceable">mode</em> is specified as
+<tt class="literal">count</tt>, only counting statistics are collected (and
+not timing statistics). If <em class="replaceable">mode</em> is
+<tt class="literal">flush</tt>, the data set is cleared (initialized).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">profilelevel</tt></b></dt>
+<dd>
+<p>Prints the current profiling level.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">printer-notify</tt> <em class="replaceable">printer_name</em></b></dt>
+<dd>
+<p>Sends a printer notify message to Windows NT/2000/XP for the
+specified printer. This message can be sent only to
+<em class="emphasis">smbd</em>. Warning: no message is printed if the
+<em class="replaceable">printer_name</em> parameter is specified
+incorrectly.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-20"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbgroupedit</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This command, new to Samba 3.0, sets up mappings between Unix groups
+and Windows NT/2000/XP groups and also allows a Unix group to become
+a domain group. This command must be run by the superuser.</p>
+<div class="sect1"><a name="appc-53-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbgroupedit <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-54-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt> <em class="replaceable">Unix_group_name</em></b></dt>
+<dd>
+<p>Adds a mapping for the specified Unix group. The
+<tt class="literal">-n</tt> option is used along with this option to
+specify the Windows NT group to which the Unix group is mapped.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-c</tt> <em class="replaceable">SID</em></b></dt>
+<dd>
+<p>Changes a mapping between a Windows NT group and a Unix group. The
+Windows NT group is specified as a SID with this option, and the Unix
+group is specified with the <tt class="literal">-u</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">description</em></b></dt>
+<dd>
+<p>Specifies a comment for the mapping, which will be stored along with
+it.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt></b></dt>
+<dd>
+<p>When used with the <tt class="literal">-v</tt> option, prints a long
+listing. This is the default. The information printed includes the
+name of the Windows NT group, its SID, its corresponding Unix group
+(if a mapping has been defined), the group type, the comment, and the
+privileges of the group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt> <em class="replaceable">Windows_group_name</em></b></dt>
+<dd>
+<p>Specifies the name of the Windows NT group. Used with the
+<tt class="literal">-a</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">privilege</em></b></dt>
+<dd>
+<p>Used along with the <tt class="literal">-a</tt> option to specify a Windows
+NT privilege to be given to the Unix group.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt></b></dt>
+<dd>
+<p>When used with the <tt class="literal">-v</tt> option, prints a short
+listing. The information printed includes just the name of the
+Windows NT group, its SID, and, if a mapping has been defined, its
+corresponding Unix group. This option is useful for determining the
+SID of a group, for use with the <tt class="literal">-c</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-t</tt> <em class="replaceable">TYPE</em></b></dt>
+<dd>
+<p>Assigns a Windows group type to the group.
+<em class="replaceable">TYPE</em> is a single character, and is one of
+<tt class="literal">b</tt> (built-in), <tt class="literal">d</tt> (domain), or
+<tt class="literal">l</tt> (local).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-u</tt> <em class="replaceable">Unix_group_name</em></b></dt>
+<dd>
+<p>Specifies the name of the Unix group to map to the Windows NT group.
+Used with the <tt class="literal">-c</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-v</tt></b></dt>
+<dd>
+<p>Prints a list of groups in the Windows NT domain in which the Samba
+server is operating. See also the <tt class="literal">-l</tt> and
+<tt class="literal">-s</tt> options.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-x</tt> <em class="replaceable">Unix_group_name</em></b></dt>
+<dd>
+<p>Deletes the mapping for the Unix group specified.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-21"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbmnt</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This is a low-level helper program for mounting smbfs filesystems. It
+used by <em class="emphasis">smbmount</em> to do the privileged part of
+the mount operation on behalf of an ordinary user. Generally, users
+should not run this command directly.</p>
+<div class="sect1"><a name="appc-56-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbmnt mnt_point <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-57-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-r</tt></b></dt>
+<dd>
+<p>Mounts the filesystem as read-only.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-u</tt> <em class="replaceable">uid</em> </b></dt>
+<dd>
+<p>Specifies the UID to use for the owner of the files.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-g</tt> <em class="replaceable">gid</em></b></dt>
+<dd>
+<p>Specifies the GID to use for the group of the files.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-f</tt> <em class="replaceable">mask</em></b></dt>
+<dd>
+<p>Specifies the octal file mask.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">mask</em></b></dt>
+<dd>
+<p>Specifies the octal directory mask.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-o</tt> <em class="replaceable">options</em></b></dt>
+<dd>
+<p>Specifies the list of options that are passed to the smbfs module.</p>
+</dd>
+
+</dl>
+
+
+<p>To allow users to mount SMB shares without help from an
+administrator, set the &quot;set user
+ID&quot; permission on the <em class="emphasis">smbmnt</em>
+executable. However, note that this can raise security issues.</p>
+
+</div>
+</div>
+
+<a name="INDEX-22"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbmount</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program mounts an smbfs filesystem on a mount point in the Unix
+filesystem. It is typically called as <em class="emphasis">mount.smb</em>
+from <em class="emphasis">mount</em>, although it can also be run directly
+by users. After mounting the smbfs filesystem,
+<em class="emphasis">smbmount</em> continues to run as a daemon as long as
+the filesystem is mounted. It logs events in the file
+<em class="filename">log.smbmount</em> in the same directory as the other
+Samba log files (which is commonly
+<em class="filename">/usr/local/samba/var</em> by default). The logging
+level is controlled by the <tt class="literal">debug level</tt> parameter
+in the Samba configuration file.</p>
+<div class="sect1"><a name="appc-59-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbmount <em class="replaceable">service mount_point [-o options]</em></pre></blockquote>
+<p>The service argument specifies the SMB share to mount, given as a
+UNC. The <em class="replaceable">mount_point</em> argument specifies a
+directory to use as the mount point. The options to
+<em class="emphasis">smbmount</em> are specified as a comma-separated list
+of
+<em class="replaceable">key</em><tt class="literal">=</tt><em class="replaceable">value</em>
+pairs. The documented options are as follows. Others can be passed if
+the kernel supports them.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-60-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">username=</tt><em class="replaceable">name</em></b></dt>
+<dd>
+<p>Specifies the username to connect as. If this is not provided, the
+environment variable USER will be tried. The name can be specified as
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>,
+<em class="replaceable">user</em><tt class="literal">/</tt><em class="replaceable">workgroup</em>,
+or
+<em class="replaceable">user</em><tt class="literal">/</tt><em class="replaceable">workgroup</em><tt class="literal">%</tt><em class="replaceable">password</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">password=</tt><em class="replaceable">string</em></b></dt>
+<dd>
+<p>Specifies the SMB password. If no password is provided using this
+option, the <em class="emphasis">username</em> option, or the
+<em class="emphasis">credentials</em> option, the environment variable
+PASSWD is used. If that also does not exist,
+<em class="emphasis">smbmount</em> will prompt interactively for a
+password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">credentials=</tt><em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies a file that contains a username and password in the
+following format:</p>
+
+
+<blockquote><pre class="code">username = <em class="replaceable">value</em>
+password = <em class="replaceable">value</em></pre></blockquote>
+</dd>
+
+
+<dt><b><tt class="literal">uid=</tt><em class="replaceable">number</em></b></dt>
+<dd>
+<p>Sets the Unix user ID to be used as the owner of all files in the
+mounted filesystem. It can be specified as a username or numeric UID.
+Defaults to the UID of the user running
+<em class="emphasis">smbmount</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">gid=</tt><em class="replaceable">number</em></b></dt>
+<dd>
+<p>Sets the Unix group ID to be used as the group for all files in the
+mounted filesystem. It can be specified as a group name or a numeric
+GID. Defaults to the GID of the user running
+<em class="emphasis">smbmount</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">port=</tt><em class="replaceable">number</em></b></dt>
+<dd>
+<p>Sets the TCP port number. This is 139, which is required by most
+Windows versions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">fmask=</tt><em class="replaceable">octal_mask</em> </b></dt>
+<dd>
+<p>Sets the Unix permissions of all files in the mounted filesystem.
+Defaults to the user's current umask.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">dmask=</tt><em class="replaceable">octal_mask</em></b></dt>
+<dd>
+<p>Sets the Unix permissions of all directories in the mounted
+filesystem. Defaults to the current umask.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">debug=</tt><em class="replaceable">number</em></b></dt>
+<dd>
+<p>Sets the debugging level.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ip=</tt><em class="replaceable">host</em></b></dt>
+<dd>
+<p>Sets the destination hostname or IP address.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">netbiosname=</tt><em class="replaceable">name</em></b></dt>
+<dd>
+<p>Sets the computer name to connect as. This defaults to the hostname
+of the local system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">workgroup=</tt><em class="replaceable">name</em></b></dt>
+<dd>
+<p>Sets the workgroup or domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">sockopt=</tt><em class="replaceable">opts</em></b></dt>
+<dd>
+<p>Sets TCP socket options.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">scope=</tt><em class="replaceable">num</em></b></dt>
+<dd>
+<p>Sets the NetBIOS scope.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">guest</tt></b></dt>
+<dd>
+<p>Don't expect or prompt for a password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ro</tt></b></dt>
+<dd>
+<p>Mounts the share read-only.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">rw</tt></b></dt>
+<dd>
+<p>Mounts the share read-write.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">iocharset=</tt><em class="replaceable">charset</em></b></dt>
+<dd>
+<p>Sets the charset used by the Linux machine for codepage-to-charset
+translation. See also the <em class="emphasis">codepage</em> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">codepage=</tt><em class="replaceable">page</em></b></dt>
+<dd>
+<p>Sets the DOS code page. See also the <em class="emphasis">iocharset</em>
+option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">ttl=</tt><em class="replaceable">milliseconds</em></b></dt>
+<dd>
+<p>Sets the time to live, in milliseconds, for entries in the directory
+cache. A higher value gives better performance on large directories
+and/or slower connections. The default is 1000ms. Try 10000ms (10
+seconds) as a starting value if directory operations are visibly
+slow.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-23"/><a name="INDEX-24"/><a name="INDEX-25"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbpasswd</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbpasswd</em> program provides the general
+function of managing <a name="INDEX-24"/><a name="INDEX-25"/>encrypted
+passwords. How it works depends on whether it is run by the superuser
+or an ordinary user.</p><p>For the superuser, <em class="emphasis">smbpasswd</em> can be used to
+maintain Samba's <em class="filename">smbpasswd</em>
+file. It can add or delete users, change their passwords, and modify
+other attributes pertaining to the user that are held in the
+<em class="filename">smbpasswd</em> file.</p><p>When run by ordinary users, <em class="emphasis">smbpasswd</em> can be
+used only to change their encrypted passwords. In this mode of
+operation, <em class="emphasis">smbpasswd</em> acts as a client to the
+<em class="emphasis">smbd</em> daemon. The program will fail if
+<em class="emphasis">smbd</em> is not operating, if the <tt class="literal">hosts
+allow</tt> or <tt class="literal">hosts deny</tt> parameters in the
+Samba configuration file do not permit connections from localhost (IP
+address 127.0.0.1), or if the <tt class="literal">encrypted passwords</tt>
+option is set to <tt class="literal">no</tt>. It is also possible for
+<em class="emphasis">smbpasswd</em> to change a user's
+password when it is maintained on a remote system, including a
+Windows NT domain controller.</p>
+<div class="sect1"><a name="appc-62-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+<p>When run by the superuser:</p>
+
+<blockquote><pre class="code">smbpasswd <em class="replaceable">[options] [username] [password]</em></pre></blockquote>
+<p>In this case, the username of the user whose
+<em class="emphasis">smbpasswd</em> entry is to be modified is provided as
+the second argument.</p>
+
+<p>Otherwise:</p>
+
+<blockquote><pre class="code">smbpasswd <em class="replaceable">[options] [password]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-63-fm2xml"/>
+
+<h4 class="refsect1">Superuser-only options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Adds a user to the encrypted password file. The user must already
+exist in the system password file (<em class="filename">/etc/passwd</em>
+). If the user already exists in the <em class="filename">smbpasswd</em>
+file, the <tt class="literal">-a</tt> option changes the existing password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Disables a user in the encrypted password file. The
+user's entry in the file will remain, but will be
+marked with a flag disabling the user from authenticating.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-e</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Enables a disabled user in the encrypted password file. This
+overrides the effect of the <tt class="literal">-d</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-j</tt> <em class="replaceable">domain</em></b></dt>
+<dd>
+<p>Joins the Samba server to a Windows NT domain as a domain member
+server. The <em class="replaceable">domain</em> argument is the NetBIOS
+name of the Windows NT domain that is being joined. See also the
+<tt class="literal">-r</tt> and <tt class="literal">-U</tt> options.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-m</tt></b></dt>
+<dd>
+<p>Indicates that the account is a computer account in a Windows NT
+domain rather than a domain user account.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt></b></dt>
+<dd>
+<p>Sets the user's password to a null password. For the
+user to authenticate, the parameter <tt class="literal">null</tt>
+<tt class="literal">passwords</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> must exist in the <tt class="literal">[global]</tt>
+section of the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-R</tt> <em class="replaceable">resolve_order_list</em></b></dt>
+<dd>
+<p>Sets the resolve order of the name servers. This option is similar to
+the <tt class="literal">resolve</tt> <tt class="literal">order</tt> configuration
+option and can take any of the four parameters
+<tt class="literal">lmhosts</tt>, <tt class="literal">host</tt>,
+<tt class="literal">wins</tt>, and <tt class="literal">bcast</tt>, in any order.
+If more than one is specified, the argument is specified as a
+space-separated list.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-w</tt> <em class="replaceable">password</em></b></dt>
+<dd>
+<p>For use when Samba has been compiled with the
+<tt class="literal">--with-ldapsam</tt> configure option. Specifies the
+password that goes with the value of the <tt class="literal">ldap admin
+dn</tt> Samba configuration file parameter.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-x</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Deletes the user from the <em class="filename">smbpasswd</em> file. This
+is a one-way operation, and all information associated with the entry
+is lost. To disable the account without deleting the
+user's entry in the file, see the
+<tt class="literal">-d</tt> option.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+<div class="sect1"><a name="appc-64-fm2xml"/>
+
+<h4 class="refsect1">Other options</h4>
+
+<dl>
+<dt><b><tt class="literal">-c</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the Samba configuration file, overriding the compiled-in
+default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-D</tt> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (also called logging) level. The level can range from
+to 10. Debug level 0 logs only the most important messages; level 1
+is normal; levels 3 and above are primarily for debugging and slow
+the program considerably.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints command-line usage information.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-L</tt></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbpasswd</em> to run in local mode, in which
+ordinary users are allowed to use the superuser-only options. This
+requires that the <em class="filename">smbpasswd</em> file be made
+readable and writable by the user. This is for testing purposes.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-r</tt> <em class="replaceable">NetBIOS_name</em></b></dt>
+<dd>
+<p>Specifies on which machine the password should change. If changing a
+Windows NT domain password, the remote system specified by
+<em class="replaceable">NetBIOS_name</em> must be the PDC for the
+domain. The user's username on the local system is
+used by default. See also the <tt class="literal">-U</tt> option for use
+when the user's Samba username is different from the
+local username.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-R</tt> <em class="replaceable">resolve_order</em></b></dt>
+<dd>
+<p>Sets the resolve order of the name servers. This option is similar to
+the resolve order configuration option and can take any of the four
+parameters <tt class="literal">lmhosts</tt>, <tt class="literal">host</tt>,
+<tt class="literal">wins</tt>, and <tt class="literal">bcast</tt>, in any order.
+If more than one is specified, the argument is specified as a
+space-separated list.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbpasswd</em> not to prompt for passwords
+from <em class="filename">/dev/tty</em>, but instead to read the old and
+new passwords from the standard input. This is useful when calling
+<em class="emphasis">smbpasswd</em> from a script.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-S</tt></b></dt>
+<dd>
+<p>Queries the domain controller of the domain, as specified by the
+<tt class="literal">workgroup</tt> parameter in the Samba configuration
+file, and retrieves the domain's SID. This will then
+be used as the SID for the local system. A specific PDC can be
+selected by combining this option with the <tt class="literal">-r</tt>
+option, and its domain's SID will be used. This
+option is for migrating domain accounts from a Windows NT primary
+domain controller to a Samba PDC.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">username[</em><tt class="literal">%</tt><em class="replaceable">password]</em></b></dt>
+<dd>
+<p>Changes the password for <em class="replaceable">username</em> on the
+remote system. This is to handle instances in which the remote
+username and local username are different. This option requires that
+<tt class="literal">-r</tt> also be used. Often used with
+<tt class="literal">-j</tt> to provide the username of the administrative
+user on the primary domain controller for adding computer accounts.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-26"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbsh</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbsh</em> program allows SMB shares to be
+accessed from a Unix system. When <em class="emphasis">smbsh</em> is run,
+an extra directory tree called <em class="filename">/smb </em>becomes
+available to dynamically linked shell commands. The first level of
+directories under <em class="filename">/smb</em> represent available
+workgroups, the next level of subdirectories represent the SMB
+servers in each workgroup, and the third level of subdirectories
+represent the disk and printer shares of each server.</p><p>Samba must be compiled with the <tt class="literal">--with-smbwrappers</tt>
+option to enable <em class="emphasis">smbsh</em>.</p>
+<div class="sect1"><a name="appc-66-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><em class="emphasis">-d</em> <em class="replaceable">debug_level</em></b></dt>
+<dd>
+<p>Sets the debug (sometimes called logging) level. The level can range
+from 0, the default, to 10. Debug level 0 logs only the most
+important messages; level 1 is normal; levels 3 and above are
+primarily for debugging and slow <em class="emphasis">smbsh</em>
+considerably.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-l</em> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Sets the name of the logging file. By default, messages are sent to
+<em class="emphasis">stderr</em>.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-L</em> <em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the location of
+<em class="emphasis">smbsh</em>'s shared libraries,
+overriding the compiled-in default.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-P</em> <em class="replaceable">prefix</em></b></dt>
+<dd>
+<p>Sets the name of the <tt class="literal">root</tt> directory to use for the
+SMB filesystem. The default is <em class="filename">/smb</em>.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-R</em> <em class="replaceable">resolve_order</em></b></dt>
+<dd>
+<p>Sets the resolve order of the name servers. This option is similar to
+the <tt class="literal">resolve</tt> <tt class="literal">order</tt> configuration
+option and can take any of the four parameters
+<tt class="literal">lmhosts</tt>, <tt class="literal">host</tt>,
+<tt class="literal">wins</tt>, and <tt class="literal">bcast</tt>, in any order.
+If more than one is specified, the argument is specified as a
+space-separated list.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-U</em> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Provides the username, and optionally the password, for
+authenticating the connection to the SMB server. The password can be
+supplied using the
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>
+format. If either or both the username and password are not provided,
+<em class="emphasis">smbsh</em> will prompt interactively for them.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">-W</em> <em class="replaceable">workgroup</em></b></dt>
+<dd>
+<p>Specifies the NetBIOS workgroup or domain to which the client will
+connect. This overrides the workgroup parameter in the Samba
+configuration file and is sometimes necessary to connect to some
+servers.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-27"/><a name="INDEX-28"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbspool</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbspool</em> program provides a
+<a name="INDEX-28"/>CUPS-compatible
+interface to Samba printing by providing a way to send a print job to
+an SMB printer using the command-line format specified by CUPS
+printers. Although <em class="emphasis">smbspool</em> is designed to work
+best with CUPS printers, it can be used to send print jobs to
+non-CUPS Samba printers as well.</p>
+<div class="sect1"><a name="appc-68-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbspool <em class="replaceable">job user title copies options filename</em></pre></blockquote>
+<p>The arguments for <em class="emphasis">smbspool</em>, as shown here, are
+those used in the CUPS printing system. However, some of the
+arguments are currently ignored because they don't
+correspond to the Samba printing system. These arguments must be
+supplied in the command and can be filled in with
+&quot;dummy&quot; values.</p>
+
+<p>The <em class="replaceable">job</em> argument refers to the job number
+and is currently ignored. The <em class="replaceable">user</em>
+argument is the name of the user who submitted the print job and is
+also ignored. The <em class="replaceable">title</em> argument is the
+name of the print job and must be supplied. It is used as the name of
+the remote print file. The <em class="replaceable">copies</em> argument
+is the number of copies that will be printed. This number is used
+only if the (optional) <em class="filename">filename</em> argument is
+supplied. Otherwise, only one copy is printed. The
+<em class="replaceable">options</em> argument, for specifying printing
+options, is ignored. The <em class="replaceable">filename</em> argument
+is used for specifying the name of the file to be printed. If it is
+not provided, the standard input will be used.</p>
+
+<p>The printer that the job is to be sent to is specified in the
+DEVICE_URI environment variable. The format for the printer name is a
+device Universal Resource Indicator, which can be in any of the
+following formats:</p>
+
+<blockquote class="simplelist">
+
+<p><em class="emphasis">smb://server/printer</em></p>
+
+
+
+
+<p><em class="emphasis">smb://workgroup/server/printer</em></p>
+
+
+
+
+<p><em class="emphasis">smb://username:password@server/printer</em></p>
+
+
+
+
+<p><em class="emphasis">smb://username:password@workgroup/server/printer</em></p>
+
+</blockquote>
+
+
+</div>
+</div>
+
+<a name="INDEX-29"/><a name="INDEX-30"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbstatus</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program lists the current connections on a Samba server.</p>
+<div class="sect1"><a name="appc-70-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-b</tt></b></dt>
+<dd>
+<p>Causes <em class="emphasis">smbstatus</em> to produce brief output. This
+includes the version of Samba and auditing information about the
+users that are connected to the server.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt></b></dt>
+<dd>
+<p>Gives verbose output, which includes a list of services, a list of
+locked files, and memory usage statistics. This is the default.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-L</tt></b></dt>
+<dd>
+<p>Prints only the list of current file locks.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt></b></dt>
+<dd>
+<p>Prints only a list of <em class="emphasis">smbd</em> process IDs.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-P</tt></b></dt>
+<dd>
+<p>Prints only the contents of the profiling memory area. Requires that
+Samba has been compiled with the profiling option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-S</tt></b></dt>
+<dd>
+<p>Prints only a list of shares and their connections.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the Samba configuration file to use when processing this
+command.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-u</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Limits the report to the activity of a single user.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-31"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbtar</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbtar</em> program is a shell-script wrapper
+around <em class="emphasis">smbclient</em> for doing tar-format archiving
+operations. It is functionally very similar to the Unix
+<em class="emphasis">tar</em> program.</p>
+<div class="sect1"><a name="appc-72-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbtar <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-73-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-a</tt></b></dt>
+<dd>
+<p>Resets (clears) the archive attribute on files after they are backed
+up. The default is to leave the archive attribute unchanged.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-b</tt> <em class="replaceable">blocksize</em></b></dt>
+<dd>
+<p>Sets block size, in units of 512 bytes, for reading or writing the
+archive file. Defaults to 20, which results in a block size of 10240
+bytes.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-d</tt> <em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Changes the working directory on the remote system to
+<em class="replaceable">directory</em> before starting the restore or
+backup operation.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-i</tt></b></dt>
+<dd>
+<p>Specifies incremental mode; files are backed up only if they have the
+DOS archive attribute set. The archive attribute is reset (cleared)
+after each file is read.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-l</tt> <em class="replaceable">log_level</em></b></dt>
+<dd>
+<p>Sets the logging level. This corresponds to the <tt class="literal">-d</tt>
+option of <em class="emphasis">smbclient</em> and other Samba programs.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-N</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Backs up only files newer than <em class="filename">filename</em>. For
+incremental backups.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-p</tt> <em class="replaceable">password</em></b></dt>
+<dd>
+<p>Specifies the password to use to access a share. An alternative to
+using the
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>
+format with the <tt class="literal">-u</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-r</tt></b></dt>
+<dd>
+<p>Restores files to the share from the tar file.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">server</em></b></dt>
+<dd>
+<p>Specifies the SMB server. See also the <tt class="literal">-x</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-t</tt> <em class="replaceable">filename</em></b></dt>
+<dd>
+<p>Specifies the file or Unix device to use as the archiving medium. The
+default is <em class="filename">tar.out</em> or the value of the TAPE
+environment variable, if it has been set.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-u</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Specifies the user account to use when connecting to the share. You
+can specify the password as well, in the format
+<em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em>.
+The username defaults to the user's Unix username.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-v</tt></b></dt>
+<dd>
+<p>Operates in verbose mode, printing error messages and additional
+information that can be used in debugging and monitoring. Backup and
+restore operations will list each file as it is processed.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-x</tt> <em class="replaceable">share</em></b></dt>
+<dd>
+<p>States the name of the share on the server to which to connect. The
+default is <tt class="literal">backup</tt>. See also the
+<tt class="literal">-s</tt> option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-X</tt> <em class="replaceable">file_list</em></b></dt>
+<dd>
+<p>Tells <em class="emphasis">smbtar</em> to exclude the specified files from
+the backup or restore operation.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-32"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>smbumount</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">smbumount</em> command exists to allow an
+ordinary (nonsuperuser) user to unmount a smbfs filesystem, which the
+user had previously mounted using <em class="emphasis">smbmount</em>.</p>
+<div class="sect1"><a name="appc-75-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">smbumount <em class="replaceable">mount_point</em></pre></blockquote>
+<p>For ordinary users to issue the command,
+<em class="emphasis">smbumount</em> must be made suid
+<tt class="literal">root</tt>.</p>
+
+</div>
+</div>
+
+<a name="INDEX-33"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>testparm</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>The <em class="emphasis">testparm</em> program checks a Samba
+configuration file for obvious errors.</p>
+<div class="sect1"><a name="appc-77-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">testparm <em class="replaceable">[options] [filename] [hostname IP_addr]</em></pre></blockquote>
+<p>If the configuration file is not provided using the
+<em class="filename">filename</em> argument, then it defaults to
+<em class="filename">/usr/local/samba/lib/smb.conf</em>. If the hostname
+and an IP address of a system are included, an extra check is made to
+ensure that the system is allowed to connect to each service defined
+in the configuration file. This is done by comparing the hostname and
+IP address to the definitions of the <tt class="literal">hosts allow</tt>
+and <tt class="literal">hosts deny</tt> parameters.</p>
+
+</div>
+
+<div class="sect1"><a name="appc-78-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-h</tt></b></dt>
+<dd>
+<p>Prints usage information for the program.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-L</tt> <em class="replaceable">server_name</em></b></dt>
+<dd>
+<p>Sets the <tt class="literal">%L</tt> configuration variable to the
+specified server name.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt></b></dt>
+<dd>
+<p>Disables the default behavior of prompting for the Enter key to be
+pressed before printing the list of configuration options for the
+server.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+<a name="INDEX-34"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>testprns</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This is a very simple program that checks to see if a specified
+printer name exists in the system printer capabilities (printcap)
+file.</p>
+<div class="sect1"><a name="appc-80-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">testprns <em class="replaceable">printername [printcapname]</em></pre></blockquote>
+<p>If <em class="replaceable">printcapname</em> isn't
+specified, Samba attempts to use the one specified in the Samba
+configuration file with the <tt class="literal">printcap name</tt>
+parameter. If none is specified there, Samba will try
+<em class="filename">/etc/printcap</em>.</p>
+
+</div>
+</div>
+
+<a name="INDEX-35"/><div class="refentry"><table width="515" border="0" cellpadding="5"><tr><td align="left"><font size="+1"><b><i>wbinfo</i></b></font></td><td align="right"><i></i></td></tr></table><hr width="515" size="3" noshade="true" align="left" color="black"/><table width="515" border="0" cellpadding="5"><tr><td align="left"/><td align="right"/></tr></table><p>This program retrieves and prints information from the
+<em class="emphasis">winbindd</em> daemon, which must be running for
+<em class="emphasis">wbinfo</em> to function.</p>
+<div class="sect1"><a name="appc-82-fm2xml"/>
+
+<h4 class="refsect1">Command synopsis</h4>
+
+<blockquote><pre class="code">wbinfo <em class="replaceable">[options]</em></pre></blockquote>
+
+
+</div>
+
+<div class="sect1"><a name="appc-83-fm2xml"/>
+
+<h4 class="refsect1">Options</h4>
+
+<dl>
+<dt><b><tt class="literal">-u</tt> </b></dt>
+<dd>
+<p>Prints all usernames that have been mapped from the Windows NT domain
+to Unix users. Users in all trusted domains are also listed.</p>
+</dd>
+
+
+
+<dt><b> <tt class="literal">-</tt><em class="emphasis">g</em> </b></dt>
+<dd>
+<p>Prints all group names that have been mapped from the Windows NT
+domain to Unix groups. Groups in all trusted domains are also
+reported.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-h</tt> <em class="replaceable">NetBIOS_name</em></b></dt>
+<dd>
+<p>Queries the WINS server and prints the IP address of the specified
+system.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-n</tt> <em class="replaceable">name</em> </b></dt>
+<dd>
+<p>Prints the SID corresponding to the name specified. The argument can
+be specified as <em class="replaceable">DOMAIN/name</em> (or by using a
+character other than the slash, as defined by the winbind separator
+character) to specify both the domain and the name. If the domain and
+separator are omitted, the value of the <tt class="literal">workgroup</tt>
+parameter in the Samba configuration file is used as the name of the
+domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-s</tt> <em class="replaceable">SID</em> </b></dt>
+<dd>
+<p>Prints the name mapped to a SID, which is specified in the format
+<tt class="literal">S-1-</tt><em class="replaceable">N-N-D-D-D-R</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-U</tt> <em class="replaceable">UID</em></b></dt>
+<dd>
+<p>Prints the SID mapped to a Unix UID, if one exists in the current
+domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-G</tt> <em class="replaceable">gid</em></b></dt>
+<dd>
+<p>Prints the SID mapped to a Unix group ID, if one exists in the
+current domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-S</tt> <em class="replaceable">SID</em></b></dt>
+<dd>
+<p>Prints the Unix UID that winbind has mapped to the specified SID, if
+one exists.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-Y</tt> <em class="replaceable">SID</em></b></dt>
+<dd>
+<p>Prints the Unix group ID that winbind has mapped to the specified
+SID, if one exists.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-t</tt></b></dt>
+<dd>
+<p>Tests to see that the workstation trust account for the Samba server
+is valid.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-m</tt> </b></dt>
+<dd>
+<p>Prints a list of Windows NT domains trusted by the Windows server.
+This does not include the PDC's domain.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-r</tt> <em class="replaceable">username</em></b></dt>
+<dd>
+<p>Prints the list of Unix group IDs to which the user belongs. This
+works only if the user's account is maintained on a
+domain controller.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-a</tt> <em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em></b></dt>
+<dd>
+<p>Checks to see if a user can authenticate through
+<em class="emphasis">winbindd</em> using the specified username and
+password.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">-A</tt> <em class="replaceable">username</em><tt class="literal">%</tt><em class="replaceable">password</em></b></dt>
+<dd>
+<p>Saves the username and password used by <em class="emphasis">winbindd</em>
+to the domain controller. For use when operating in a Windows 2000
+domain.</p>
+</dd>
+
+</dl>
+
+
+</div>
+</div>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+
+</body></html>
diff --git a/docs/htmldocs/using_samba/appd.html b/docs/htmldocs/using_samba/appd.html
new file mode 100644
index 0000000000..0e2a8822f8
--- /dev/null
+++ b/docs/htmldocs/using_samba/appd.html
@@ -0,0 +1,82 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix D. Downloading Samba with CVS</h1>
+
+
+<p>In <a href="ch02.html">Chapter 2</a> we showed you how to download the
+latest stable version of Samba published by the Samba developers. For
+most purposes (including virtually all production servers) this
+procedure will meet your needs. However, sometimes you might want to
+run a version of Samba that includes the latest bug fixes and
+features, maybe for research and testing purposes, or just to see
+what the Samba developers have been up to lately.</p>
+
+<p>The Samba team keeps the latest updates of the Samba source code in a
+<a name="INDEX-1"/><a name="INDEX-2"/>Concurrent Versions System
+(CVS) repository. CVS is a freely available
+<a name="INDEX-3"/>configuration management tool
+and is distributed under the GNU General Public License. You can
+download the latest copy from <a href="http://www.cvshome.org/">http://www.cvshome.org/</a>. The Samba team
+describes various ways to access its CVS repository at <a href="http://www.samba.org/samba/cvs.html">http://www.samba.org/samba/cvs.html</a>.</p>
+
+<a name="samba2-APP-D-NOTE-162"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Although the CVS code contains the latest features, it also contains
+the latest bugs and sometimes won't even compile
+properly! If you prefer a less &quot;bleeding
+edge&quot; release, try looking in the
+<em class="filename">alpha</em> and <em class="filename">pre</em> directories
+on the Samba FTP server. The <em class="filename">alpha</em> directory
+contains alpha releases, and the <em class="emphasis">pre</em> directory
+contains (usually more stable) prerelease versions. (See <a href="ch02.html">Chapter 2</a> for information on downloading via FTP.) Alpha
+releases might be a little behind the latest CVS code, but are less
+buggy and usually compile properly on the more common Unix versions.</p>
+</blockquote>
+
+<p>One of the nicest things about CVS is its ability to handle remote
+logins. This means that people across the globe on the Internet can
+download and update various source files for any project that uses a
+CVS repository. Such is the case with Samba. Once you have CVS
+installed on your system, you must first log in to the Samba source
+server with the following command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login</b></tt></pre></blockquote>
+
+<p>When you are prompted for a password, enter <tt class="literal">cvs</tt>.
+You are connected to the CVS server at
+<tt class="literal">pserver.samba.org</tt>. Once you are connected, you can
+download the latest source tree with the following command:<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a></p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cvs -z5 -d :pserver:pserver@pserver.samba.org:/cvsroot co samba</b></tt></pre></blockquote>
+
+<p>This downloads the entire Samba distribution (file by file) into a
+directory called <em class="filename">samba</em>, created in your current
+directory. The <em class="filename">samba</em> directory has the same
+structure as the Samba source distribution described in <a href="ch02.html">Chapter 2</a>, except that it has additional directories
+named <em class="filename">CVS</em> throughout the source tree. These
+directories are used by CVS to store information about each file in
+the source tree and how to update them. After the download is
+completed, you can follow the instructions in <a href="ch02.html">Chapter 2</a> to configure, compile, and install your new
+Samba release.</p>
+
+<p>The Samba developers typically update the Samba source code one or
+more times per day. Whenever you want to catch up to the latest
+changes, simply <em class="emphasis">cd</em> to the
+<em class="filename">samba</em> directory and run the following command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cvs update -d -P</b></tt></pre></blockquote>
+
+<p>Each time you do this, you will need to reconfigure, recompile, and
+reinstall to update your installation as we showed you in <a href="ch02.html">Chapter 2</a>.</p>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/>
+<p><a href="#FNPTR-1">[1]</a> The <tt class="literal">-z</tt> option causes the transfer to be made
+in GNU gzip compressed format and requires the
+<em class="filename">gzip</em> program to be installed on your system to
+work. If you do not have <em class="filename">gzip</em>, omit the
+<tt class="literal">-z</tt> option.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+
+</body></html>
diff --git a/docs/htmldocs/using_samba/appe.html b/docs/htmldocs/using_samba/appe.html
new file mode 100644
index 0000000000..d3263eb3cb
--- /dev/null
+++ b/docs/htmldocs/using_samba/appe.html
@@ -0,0 +1,826 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix E. Configure Options</h1>
+
+
+<p><a name="INDEX-1"/>As we
+explained in <a href="ch02.html">Chapter 2</a>, the
+<em class="emphasis">configure</em> program is run before the Samba source
+code is compiled to fit the compilation process to the local
+architecture. At this stage, it is possible to specify options to
+customize Samba's behavior further and include or
+exclude features. This is an example of specifying configure options:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>./configure --with-smbmount --with-configdir=/etc/samba --with-manpages-langs=ja</b></tt></pre></blockquote>
+
+<p>This example configures the Samba installation to support mounting
+SMB filesystems, look for the Samba configuration file in
+<em class="filename">/etc/samba</em> (instead of the default location of
+<em class="filename">/usr/local/samba/lib</em>), and install
+Japanese-language manual pages. We have picked these three configure
+options because they illustrate the usage of the three types of
+options that are included up to Samba 3.0. The
+<tt class="literal">--with-smbmount</tt> option is a Boolean option, which
+can take a value of <tt class="literal">yes</tt> or <tt class="literal">no</tt>.
+All the Boolean options are set to <tt class="literal">no</tt> by default,
+and it is only necessary to provide the option to turn it on. If you
+want to be more explicit, you can specify
+<tt class="literal">--with-smbmount=yes</tt>. To turn an option off
+explicitly, you can also specify
+<tt class="literal">--without-</tt><em class="replaceable">feature</em>
+rather than
+<tt class="literal">--with-</tt><em class="replaceable">feature</em><tt class="literal">=no</tt>.</p>
+
+<p>In the case of the other two options we have shown, an argument must
+be supplied after the equals (<tt class="literal">=</tt>) sign. Some of the
+options are used to specify the directories that Samba uses for
+various purposes. Only one option is in the last group, where
+something other than a directory is specified as an option argument.</p>
+
+<p>The supported configure options vary from release to release. For
+example, between Samba 2.2.x and Samba 3.0, many options were
+dropped, and a few were added. To get a list of the configure options
+for your release, use the following command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>./configure --help</b></tt></pre></blockquote>
+
+<p><a href="appe.html#samba2-APP-E-TABLE-1">Table E-1</a> lists Samba's configure
+options.</p>
+
+<a name="samba2-APP-E-TABLE-1"/><h4 class="head4">Table E-1. Configuration options</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Configuration option</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">--with-acl-support</tt></p>
+</td>
+<td>
+<p>Support Windows NT/2000/XP ACLs</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-afs</tt></p>
+</td>
+<td>
+<p>Support the Andrew Filesystem (AFS)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-automount</tt></p>
+</td>
+<td>
+<p>Support the NFS automounter</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-codepagedir=</tt><em class="replaceable">dir</em></p>
+</td>
+<td>
+<p>Location of codepage files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-configdir=</tt><em class="replaceable">dir</em></p>
+</td>
+<td>
+<p>Location of configuration files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-dce-dfs</tt></p>
+</td>
+<td>
+<p>Support DCE/DFS</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-fhs</tt></p>
+</td>
+<td>
+<p>Use FHS-compliant locations of files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-included-popt</tt></p>
+</td>
+<td>
+<p>Use Samba's <em class="emphasis">popt(  )</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-krb4=base-</tt><em class="replaceable">dir</em></p>
+</td>
+<td>
+<p>Support Kerberos 4</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-krb5=base-</tt><em class="replaceable">dir</em></p>
+</td>
+<td>
+<p>Support Kerberos 5 (Microsoft ADS)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-ldapsam</tt></p>
+</td>
+<td>
+<p>Support LDAP SAM</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-libiconv=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Specify <em class="filename">iconv</em> library</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-libsmbclient</tt></p>
+</td>
+<td>
+<p>Build <em class="filename">smbclient</em> library</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-lockdir=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of lock files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-logfilebase=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of log files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-manpages-langs=</tt><em class="replaceable">language</em></p>
+</td>
+<td>
+<p>Specify language for manual pages</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-msdfs</tt></p>
+</td>
+<td>
+<p>Support Microsoft Dfs</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-nisplus-home</tt></p>
+</td>
+<td>
+<p>Support NIS+ home directories</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-nisplussam</tt></p>
+</td>
+<td>
+<p>Support NIS+ SAM</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-pam</tt></p>
+</td>
+<td>
+<p>Support PAM restrictions</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-pam_smbpass</tt></p>
+</td>
+<td>
+<p>Build <em class="filename">pam_smbpass.so</em> PAM module</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-piddir=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of PID files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-privatedir=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of <em class="filename">smbpasswd</em> file</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-profiling-data</tt></p>
+</td>
+<td>
+<p>Support gathering of profiling information</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-quotas</tt></p>
+</td>
+<td>
+<p>Support disk quotas</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-readline=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Specify readline library</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-sendfile-support</tt></p>
+</td>
+<td>
+<p>Support <em class="emphasis">sendfile</em>(  ) system call</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-smbmount</tt></p>
+</td>
+<td>
+<p>Support <em class="emphasis">smbmount</em> and smbfs</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-smbwrapper</tt></p>
+</td>
+<td>
+<p>Build <em class="filename">smbwrapper</em> library for
+<em class="emphasis">smbsh</em> support</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-spinlocks</tt></p>
+</td>
+<td>
+<p>Use spinlocks instead of fcntl locks</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-ssl</tt></p>
+</td>
+<td>
+<p>Support SSL</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-sslinc=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of SSL include files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-ssllib=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of SSL libraries</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-swatdir=</tt><em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Location of SWAT files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-syslog</tt></p>
+</td>
+<td>
+<p>Support syslog message logging</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-tdbsam</tt></p>
+</td>
+<td>
+<p>Support TDB database files for SAM</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-utmp</tt></p>
+</td>
+<td>
+<p>Support utmp file accounting</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--with-winbind</tt></p>
+</td>
+<td>
+<p>Build winbind</p>
+</td>
+</tr>
+
+</table>
+
+<dl>
+<dt><b><tt class="literal">--with-acl-support</tt><a name="INDEX-2"/><a name="INDEX-3"/></b></dt>
+<dd>
+<p>Includes support for Windows NT/2000/XP access control lists
+(<a name="INDEX-4"/>ACLs). For this to work, you need
+to have POSIX ACL support in the host operating system. See <a href="ch08.html">Chapter 8</a> for details.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-afs</tt><a name="INDEX-5"/><a name="INDEX-6"/></b></dt>
+<dd>
+<p>Includes support for the <a name="INDEX-7"/>Andrew
+Filesystem (AFS), for authenticating users who are accessing files
+through AFS.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-automount</tt><a name="INDEX-8"/><a name="INDEX-9"/></b></dt>
+<dd>
+<p>Includes support for the automounter, a feature often used in
+conjunction with NFS, to mount <a name="INDEX-10"/><a name="INDEX-11"/>NFS shares automatically at the
+first attempt to access them. You might wish to enable this feature
+if any of the directories shared by your Samba server are (or
+include) NFS-mounted directories.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-codepagedir</tt><a name="INDEX-12"/><a name="INDEX-13"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which to put codepage files for
+<a name="INDEX-14"/>internationalization
+support. See the
+&quot;Internationalization&quot; section
+earlier in this chapter for more information on this feature. By
+default, this directory is
+<em class="filename">/usr/local/samba/lib/codepages</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-configdir</tt><a name="INDEX-15"/><a name="INDEX-16"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which Samba keeps its configuration file,
+usually called <em class="filename">smb.conf</em>. By default, this is
+<em class="filename">/usr/local/samba/lib</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-dce-dfs</tt><a name="INDEX-17"/><a name="INDEX-18"/></b></dt>
+<dd>
+<p>Includes support for the <a name="INDEX-19"/>Distributed Computing Environment
+Distributed Filesystem (DCE/DFS). This is a distributed filesystem
+included in some Unix variants and is not the same as
+Microsoft's Distributed Filesystem (Dfs).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-fhs</tt><a name="INDEX-20"/><a name="INDEX-21"/></b></dt>
+<dd>
+<p>Adheres to the <a name="INDEX-22"/>Filesystem Hierarchy Standard when
+locating files. For details, see <a href="http://www.pathname.com/fhs">http://www.pathname.com/fhs</a>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-included-popt</tt><a name="INDEX-23"/><a name="INDEX-24"/></b></dt>
+<dd>
+<p>Includes Samba's own support for parsing
+<a name="INDEX-25"/>command-line options, instead of using
+the local system's <em class="emphasis">popt( )</em>
+C-library function.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-krb4</tt><a name="INDEX-26"/><a name="INDEX-27"/>=<em class="replaceable">base-dir</em></b></dt>
+<dd>
+<p>Includes support for <a name="INDEX-28"/>Kerberos Version 4.0, specifying the base
+directory of the Kerberos distribution. Kerberos is an authentication
+protocol developed at MIT that uses private-key cryptography to
+provide strong security between nodes. This version is not the same
+as Microsoft's adaptation of Kerberos in Active
+Directory, which is the preferred version for use with Samba. This
+option exists only in versions of Samba earlier than 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-krb5</tt><a name="INDEX-29"/><a name="INDEX-30"/>=<em class="replaceable">base-dir</em></b></dt>
+<dd>
+<p>Includes support for Kerberos Version 5.0, specifying the base
+directory of the Kerberos distribution. This version of Kerberos is
+compatible with the Kerberos authentication in
+Microsoft's Active Directory used in Windows 2000
+and Windows XP.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-ldapsam</tt><a name="INDEX-31"/><a name="INDEX-32"/></b></dt>
+<dd>
+<p>Includes support for using
+<a name="INDEX-33"/>LDAP instead of the
+<em class="filename">smbpasswd</em> file for maintaining
+Samba's equivalent to the Windows NT SAM database.
+This option is necessary to use the parameters
+<tt class="literal">ldap</tt> <tt class="literal">admin</tt>
+<tt class="literal">dn</tt>, <tt class="literal">ldap</tt>
+<tt class="literal">filter</tt>, <tt class="literal">ldap</tt>
+<tt class="literal">port</tt>, <tt class="literal">ldap</tt>
+<tt class="literal">server</tt>, <tt class="literal">ldap</tt>
+<tt class="literal">ssl</tt>, and <tt class="literal">ldap</tt>
+<tt class="literal">suffix</tt> in the Samba configuration file. It is
+necessary to specify <tt class="literal">--with-ldapsam</tt> only in Samba
+versions prior to 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-libiconv</tt><a name="INDEX-34"/><a name="INDEX-35"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies a location for <em class="emphasis">iconv( )</em> support. The
+<a name="INDEX-36"/><em class="emphasis">iconv( )</em> function
+exists in the C library to perform conversion between different
+character sets. This option allows Samba's default
+method of determining the location of the <em class="emphasis">iconv()</em> 
+library to be overridden. Ordinarily, the configuration
+process checks for support in the C library on the system and, if not
+found, uses code included in the Samba source tree. Using
+<tt class="literal">--with-libiconv</tt>, it is possible to specify
+explicitly where the support is located. The include files are
+assumed to be in
+<em class="replaceable">directory</em><em class="filename">/include</em>,
+and library files are assumed to be in
+<em class="replaceable">directory</em><em class="filename">/lib</em>. This
+option is new in Samba 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-libsmbclient</tt><a name="INDEX-37"/><a name="INDEX-38"/></b></dt>
+<dd>
+<p>Allows applications outside the
+<a name="INDEX-39"/>Samba
+suite to access Samba's features. When
+<tt class="literal">--with-libsmbclient</tt> is specified, the library is
+built during the compilation process.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-lockdir</tt><a name="INDEX-40"/><a name="INDEX-41"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which Samba keeps
+<a name="INDEX-42"/>lock
+files. By default this directory is
+<em class="filename">/usr/local/samba/var/locks</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-logfilebase</tt><a name="INDEX-43"/><a name="INDEX-44"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which Samba keeps <a name="INDEX-45"/>log files for the
+<em class="emphasis">smbd</em>, <em class="emphasis">nmbd</em>, and
+<em class="emphasis">winbindd</em> daemons. This defaults to
+<em class="filename">/usr/local/samba/var</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-manpages-langs</tt><a name="INDEX-46"/><a name="INDEX-47"/>=<em class="replaceable">language</em></b></dt>
+<dd>
+<p>Starting with Samba 3.0, <a name="INDEX-48"/><a name="INDEX-49"/>Samba's manual pages
+are available in different languages. The default is
+<tt class="literal">en</tt> for English, and the language can be specified
+as <tt class="literal">ja</tt> for Japanese or <tt class="literal">pl</tt> for
+Polish.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-msdfs</tt><a name="INDEX-50"/><a name="INDEX-51"/></b></dt>
+<dd>
+<p>Includes support for Microsoft Distributed Filesystem
+(<a name="INDEX-52"/>Dfs). See <a href="ch08.html">Chapter 8</a> for
+more information on this feature. Specifying this option is necessary
+only in Samba versions prior to 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-nisplus-home</tt><a name="INDEX-53"/><a name="INDEX-54"/></b></dt>
+<dd>
+<p>Includes support for locating the
+<a name="INDEX-55"/>NIS+ server that is
+serving a particular user's home directory and
+telling the client to connect to it. Use
+<tt class="literal">--with-automount</tt> along with this option.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-nisplussam</tt><a name="INDEX-56"/><a name="INDEX-57"/></b></dt>
+<dd>
+<p>Includes support for integrating
+<a name="INDEX-58"/>NIS+ into Samba's
+equivalent of the Windows NT password database.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-pam</tt><a name="INDEX-59"/><a name="INDEX-60"/></b></dt>
+<dd>
+<p>When this configure option is specified and the parameter
+<tt class="literal">obey</tt> <tt class="literal">pam</tt>
+<tt class="literal">restrictions</tt> in the Samba configuration file is
+set to <tt class="literal">yes</tt>, obeys PAM's
+configuration regarding account and session management. When
+encrypted passwords are in use, Samba uses the
+<em class="filename">smbpasswd</em> file for authentication, bypassing the
+PAM subsystem. Therefore, this option works only when
+<tt class="literal">encrypt</tt> <tt class="literal">passwords</tt> is set to
+<tt class="literal">no</tt>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-pam_smbpass</tt><a name="INDEX-61"/><a name="INDEX-62"/></b></dt>
+<dd>
+<p>When this option is specified, the compilation process builds a PAM
+module called <em class="filename">pam_smbpass.so</em> and places it in
+the <em class="filename">source/bin</em> directory. This module allows
+applications outside of the Samba suite to authenticate users with
+Samba's <em class="filename">smbpasswd</em> file. For
+more information, see the <em class="filename">README</em> file in the
+<em class="filename">source/pam_smbpass</em> directory of the Samba
+distribution and the file
+<em class="filename">PAM-Authentication-And-Samba.html</em> in the
+<em class="filename">docs/html</em> directory.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-piddir</tt><a name="INDEX-63"/><a name="INDEX-64"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which Samba keeps files such as
+<a name="INDEX-65"/>browse lists, WINS
+data, and PID files for keeping track of the process IDs of the Samba
+daemons. The default is
+<em class="filename">/usr/local/samba/var/locks</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-privatedir</tt><a name="INDEX-66"/><a name="INDEX-67"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the directory in which Samba keeps the
+<em class="filename">smbpasswd</em>, <em class="filename">secrets.tdb,</em> and
+related files for
+<a name="INDEX-68"/>authentication.
+The default is <em class="filename">/usr/local/samba/private</em>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-profiling-data</tt><a name="INDEX-69"/><a name="INDEX-70"/></b></dt>
+<dd>
+<p>Includes support for analyzing the execution time of
+Samba's internal code. This is normally used only by
+the Samba developers.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-quotas</tt><a name="INDEX-71"/><a name="INDEX-72"/></b></dt>
+<dd>
+<p>Includes <a name="INDEX-73"/>disk-quota support. This is classified
+as an experimental option by the Samba developers.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-readline</tt><a name="INDEX-74"/><a name="INDEX-75"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies a location for
+<a name="INDEX-76"/><em class="emphasis">readline( )</em>
+support. The <em class="emphasis">readline( )</em> function exists in the
+C library to accept a line of input from an interactive user and
+provide support for editing and history. Samba uses these functions
+in <em class="emphasis">smbclient</em> and <em class="emphasis">rpcclient</em>.</p>
+
+<p>This option allows Samba's default method of
+determining the location of the <tt class="function">readline( )</tt>
+library to be overridden. Ordinarily, the configuration process
+checks for support in the C library on the system and, if not found,
+uses code included in the Samba source tree. Using
+<tt class="literal">--with-readline</tt>, it is possible to specify the
+directory explicitly in which the library containing
+<em class="emphasis">readline( )</em> is located.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-sendfile-support</tt><a name="INDEX-77"/><a name="INDEX-78"/></b></dt>
+<dd>
+<p>Checks to see if the Samba host operating system supports the
+<a name="INDEX-79"/><em class="emphasis">sendfile( )</em> system
+call, which speeds up file transfers by copying data directly to and
+from kernel buffers, avoiding the overhead of copying to and from
+buffers in user space. If the operating system has the
+<em class="emphasis">sendfile( )</em> system call, support is included in
+Samba for the <tt class="literal">use</tt> <tt class="literal">sendfile</tt>
+configuration file option. This is an experimental option included in
+Samba 2.2.5 and later versions.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-smbmount</tt><a name="INDEX-80"/><a name="INDEX-81"/></b></dt>
+<dd>
+<p>Must be specified if you want to mount SMB shares in your Unix
+filesystem using the <em class="filename"/><a name="INDEX-82"/>smbfs</em> filesystem and the
+<em class="emphasis">smbmount</em><a name="INDEX-83"/> command, as discussed in <a href="ch05.html">Chapter 5</a>. Currently, this works only with Linux.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-smbwrapper</tt><a name="INDEX-84"/><a name="INDEX-85"/></b></dt>
+<dd>
+<p>To use <a name="INDEX-86"/>smbsh to access SMB shares from Unix (as
+discussed in <a href="ch05.html">Chapter 5</a>), use this option to
+include the
+<em class="filename">smbwrapper</em><a name="INDEX-87"/> library.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-spinlocks</tt><a name="INDEX-88"/><a name="INDEX-89"/></b></dt>
+<dd>
+<p>Uses <a name="INDEX-90"/><a name="INDEX-91"/>spin locks instead of the normal method of
+file locking that uses the <em class="emphasis">fcntl( )</em> C-library
+function. Using this option results in a Samba installation that
+consumes much more CPU time on the host system. Use it only when
+absolutely necessary.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-ssl</tt><a name="INDEX-92"/><a name="INDEX-93"/></b></dt>
+<dd>
+<p>Includes support for running Samba with
+<a name="INDEX-94"/>SSL encryption. This little-used
+feature was dropped for Samba 3.0. It still works with Samba 2.2.x
+and before, but a better method is to use a <a name="INDEX-95"/>virtual private
+network (VPN).</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-sslinc</tt><a name="INDEX-96"/><a name="INDEX-97"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the location of the SSL include files.
+<em class="filename">/usr/local/ssl/include</em> is the default location.
+This option exists in versions prior to Samba 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-ssllib</tt><a name="INDEX-98"/><a name="INDEX-99"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies the location of the SSL libraries. The default location is
+<em class="filename">/usr/local/ssl/lib</em>. This option exists in
+versions prior to Samba 3.0.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-swatdir</tt><a name="INDEX-100"/><a name="INDEX-101"/>=<em class="replaceable">directory</em></b></dt>
+<dd>
+<p>Specifies where to install the files for
+<a name="INDEX-102"/>SWAT.
+<em class="filename">/usr/local/samba/swat</em> is the default location.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-syslog</tt><a name="INDEX-103"/><a name="INDEX-104"/></b></dt>
+<dd>
+<p>Includes support for
+<a name="INDEX-105"/>syslog error
+logging. This option must be specified for the Samba configuration
+file parameters <tt class="literal">syslog</tt> and
+<tt class="literal">syslog</tt> <tt class="literal">only</tt> to work. This
+option is widely supported, but might not work correctly on all Samba
+host systems.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-tdbsam</tt><a name="INDEX-106"/><a name="INDEX-107"/></b></dt>
+<dd>
+<p>Includes support for keeping Samba's equivalent of
+the Windows NT SAM in a <em class="filename">.tdb</em> database file
+rather than in the <em class="filename">smbpasswd</em> file. This is an
+experimental feature.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-utmp</tt><a name="INDEX-108"/><a name="INDEX-109"/></b></dt>
+<dd>
+<p>Includes support for <a name="INDEX-110"/>user accounting in the
+system's
+<em class="filename">utmp</em><a name="INDEX-111"/> file. It is necessary for the
+<tt class="literal">utmp</tt> and <tt class="literal">utmp</tt>
+<tt class="literal">directory</tt> Samba configuration file options to
+work. This option is widely supported, but might not work correctly
+on all Samba host systems.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-winbind</tt><a name="INDEX-112"/><a name="INDEX-113"/></b></dt>
+<dd>
+<p>Includes <a name="INDEX-114"/>winbind support in Samba.
+Instead of defaulting to <tt class="literal">no</tt>, as with other boolean
+options, <tt class="literal">--with-winbind</tt> is
+automatically set to <tt class="literal">yes</tt> on systems that support
+winbind functionality. The only time you would need to specify this
+option is to turn it off, like this:</p>
+
+
+<blockquote><pre class="code"># <tt class="userinput"><b>configure --without-winbind</b></tt></pre></blockquote>
+
+<p>This excludes winbind functionality from Samba even when the local
+operating system can support it. For more information on winbind, see
+<a href="ch09.html">Chapter 9</a>. <a name="INDEX-115"/></p>
+</dd>
+
+</dl>
+
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/appf.html b/docs/htmldocs/using_samba/appf.html
new file mode 100644
index 0000000000..c3eb7d4d81
--- /dev/null
+++ b/docs/htmldocs/using_samba/appf.html
@@ -0,0 +1,780 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix F. Running Samba on Mac OS X Server</h1>
+
+
+
+<p><a name="INDEX-1"/>Mac OS X Server is an Apple
+operating-system product based on Mac OS X, with the addition of
+administrative tools and server software. One area in which it
+differs from Mac OS X is in the configuration of Samba-based
+services. In this appendix, we'll tell you how to
+set up SMB file and printer shares, enable client user access, and
+monitor activity. Our specific focus is on Mac OS X Server 10.2.</p>
+
+
+
+<div class="sect1"><a name="samba2-APP-F-SECT-1"/>
+
+<h2 class="head1">Setup Procedures</h2>
+
+<p>The first thing to note is that the procedure described in <a href="ch02.html">Chapter 2</a> using System Preferences to enable Samba does
+not apply to Mac OS X Server. Unlike Mac OS X, the Sharing pane of
+System Preferences does not include an option to turn on Windows File
+Sharing. Instead, there is a set of applications to configure,
+activate, and monitor services: Workgroup Manager, Server Settings,
+Server Status, and Open Directory Assistant, all located in the
+directory <em class="filename">/Applications/Utilities</em>.</p>
+
+<a name="samba2-APP-F-NOTE-163"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>In addition to being installed with Mac OS X Server, these and other
+administrative applications are included on a separate installation
+CD-ROM sold with the operating system. They can be used to manage Mac
+OS X Server systems remotely from any Mac OS X machine.</p>
+
+<p>For more information, refer to the <em class="citetitle">Mac OS X Server
+Administrator's
+Guide</em><a name="INDEX-2"/>, included as a PDF
+file in the <em class="filename">/Library/Documentation/MacOSXServer</em>
+directory, and also downloadable from Apple
+Computer's web site at <a href="http://www.apple.com/server/">http://www.apple.com/server/</a>.</p>
+</blockquote>
+
+<p>Briefly, the procedure for setting up SMB file and printer shares is
+as follows:</p>
+
+<ol><li>
+<p>Designate share points in Workgroup Manager for file sharing.</p>
+</li><li>
+<p>Set up print queues in Server Settings for printer sharing, and
+activate Printer Service.</p>
+</li><li>
+<p>Configure and activate Windows Services in Server Settings.</p>
+</li><li>
+<p>Activate Password Server and enable SMB authentication in Open
+Directory Assistant.</p>
+</li><li>
+<p>Enable Password Server authentication for user accounts in Workgroup
+Manager.</p>
+</li><li>
+<p>Monitor file and print services with Server Status.</p>
+</li></ol>
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.1"/>
+
+<h3 class="head2">Sharing Files</h3>
+
+<p><a name="INDEX-3"/><a name="INDEX-4"/>The
+first step to enable SMB file sharing is to designate one or more
+<em class="firstterm">share points</em>. Share points are folders that
+form the root of shared volumes for any of the protocols supported by
+Mac OS X Server: Apple Filesharing Protocol (AFP), Network Filesystem
+(NFS), File Transfer Protocol (FTP), and SMB.</p>
+
+<p>To designate a share point, launch Workgroup Manager. You will be
+prompted for the local or remote server's hostname
+or IP address, as well as for a username and password; this process
+is required by all the Mac OS X Server administrative applications.
+Once Workgroup Manager is open, click the Sharing button in the
+toolbar. The list on the left, under the Share Points tab, displays
+currently defined share points. To add a new one, click the All tab,
+and navigate to the folder you want to share.</p>
+
+<p>On the right, under the General tab, check the box labeled Share this
+item and its contents, change the ownership and permissions if
+desired, then click the Save button. Next, under the Protocols tab,
+select Windows File Settings from the pop-up menu, and ensure that
+the box labeled Share this item using SMB is checked. At this point,
+you can also decide whether to allow guest access to the share,
+change the name of the share displayed to SMB clients, or set
+permissions for files and folders created by SMB clients. Click the
+Save button when you're finished making changes. See
+<a href="appf.html#samba2-APP-F-FIG-1">Figure F-1</a>.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-1"/><img src="figs/sam2_af01.gif"/></div><h4 class="head4">Figure F-1. Workgroup Manager: Share Points and Windows File Settings</h4>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.2"/>
+
+<h3 class="head2">Sharing Printers</h3>
+
+<p><a name="INDEX-5"/><a name="INDEX-6"/>Printer shares are set up
+differently. First, launch Server Settings; under the File &amp;
+Print tab, select Print, then Configure Print Service.... Check the
+box labeled Automatically share new queues for Windows printing.
+Next, click the Print icon again and then Show Print Monitor. Make
+sure the printers you want to share are listed. Printers directly
+attached to the server should have queues created automatically, but
+remote printers you wish to reshare must be added by clicking New
+Queue and discovering or specifying the printers. When
+you're finished, click Save, select the Print icon
+one more time, and select Start Print Service. See <a href="appf.html#samba2-APP-F-FIG-2">Figure F-2</a>.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-2"/><img src="figs/sam2_af02.gif"/></div><h4 class="head4">Figure F-2. Server Settings: Print Service</h4>
+
+<a name="samba2-APP-F-NOTE-164"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Server Settings will make local printers available for sharing only
+if they're PostScript compatible. Unfortunately,
+many printers, including consumer-grade USB inkjet printers,
+aren't. If you want to make one of these printers
+available to SMB clients, you can still add the share to
+<em class="filename">/etc/smb.conf</em> yourself with a text editor. See
+&quot;Rolling Your Own&quot; later in this
+chapter for instructions and caveats related to making manual changes
+to <em class="filename">smb.conf</em>.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.3"/>
+
+<h3 class="head2">Configuring and Activating Services</h3>
+
+<p><a name="INDEX-7"/>At this point, neither
+the file shares nor the printer shares are available to SMB clients.
+To activate them, click the Windows icon in Server Settings, and
+click Configure Windows Services.... Under the General tab, you can
+set the server's NetBIOS hostname, the workgroup or
+Windows NT domain in which the server resides, and the description
+that gets displayed in a browse list. You can also specify the code
+page for an alternate character set. Finally, you can enable
+boot-time startup of Samba. See <a href="appf.html#samba2-APP-F-FIG-3">Figure F-3</a>.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-3"/><img src="figs/sam2_af03.gif"/></div><h4 class="head4">Figure F-3. Server Settings: Windows Services</h4>
+
+<p>The Windows Services Access tab offers options to enable guest access
+and limit the number of simultaneous client connections; under the
+Logging tab, you can specify the verbosity of your logging. With
+options under the Neighborhood tab, you can configure your machine as
+a WINS client or server or have it provide browser services locally
+or across subnets.</p>
+
+<a name="samba2-APP-F-SIDEBAR-1"/><blockquote><table border="1" cellpadding="6"><tr><td>
+<h4 class="head4">Password Server</h4>
+
+<p><a name="INDEX-8"/><a name="INDEX-9"/>Password Server is a feature
+introduced with Mac OS X Server 10.2. In prior versions of Mac OS X
+Server, Windows authentication was handled with Authentication
+Manager, which stored a user's Windows password in
+the <tt class="literal">tim_password</tt> property of the
+user's NetInfo record. This can still be done in
+Version 10.2, although it's strongly discouraged
+because the encrypted password is visible to other users with access
+to the NetInfo domain and can potentially be decrypted.</p>
+
+<p>If you need to use Authentication Manager, use the following
+procedure to enable it:</p>
+
+<ol><li>
+<p>On every machine hosting a domain that will bind into the NetInfo
+hierarchy, execute the command <tt class="literal">tim -init -auto</tt>
+<em class="replaceable">tag</em> for each domain, where
+<em class="replaceable">tag</em> is the name of the
+domain's database.</p>
+</li>
+<li>
+<p>When prompted, provide a password to be used as the encryption key
+for the domain. This key is used to decrypt the Windows passwords and
+is stored in an encrypted file readable only by root,
+<em class="filename">/var/db/netinfo/.tag.tim</em>.</p>
+</li>
+<li>
+<p>Set <tt class="literal">AUTHSERVER=-YES-</tt> in
+<em class="filename">/etc/hostconfig</em>.</p>
+</li>
+<li>
+<p>Start Authentication Manager by invoking <em class="emphasis">tim</em>.
+This is also executed during the boot sequence by the AuthServer
+startup item.</p>
+</li>
+<li>
+<p>Reset the password of each user requiring SMB client access. In Mac
+OS X Server 10.2 or later, make sure the user is set up for Basic
+authentication, not Password Server authentication.</p>
+</li></ol></td></tr></table></blockquote>
+
+<p>When you've finished configuring Windows Services,
+click the Save button, then click the Windows icon in Server
+Settings, and select Start Windows Services. This starts the Samba
+daemons, enabling access from SMB clients.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.4"/>
+
+<h3 class="head2">Activating Password Server</h3>
+
+<p><a name="INDEX-10"/><a name="INDEX-11"/>Now that
+you've set up file and printer shares, you need to
+make sure users can properly authenticate to access them. In Mac OS X
+Server, this is accomplished with the <a name="INDEX-12"/>Open Directory
+Password Server, a service based on the <a name="INDEX-13"/>Simple Authentication and Security
+Layer (SASL) standard and usable with many different authentication
+protocols, including the LAN Manager and Windows NT LAN Manager
+(NTLM) protocols. This section describes how to support SMB client
+authentication, but for more information on what Password Server does
+and how it works, see the Mac OS X Server
+Administrator's Guide.</p>
+
+<p>To enable Password Server or merely check its settings, start the
+Open Directory Assistant. Unless you wish to change any of the
+settings, just click the right arrow button in the lower-right corner
+of the window until you get to the first Security step. At this
+point, activate Password Server by selecting the option marked
+Password and authentication information will be provided to other
+systems. The next step displays the main administrative account, and
+the one after that gives you a choice of authentication protocols to
+enable (see <a href="appf.html#samba2-APP-F-FIG-4">Figure F-4</a>). Make sure that SMB-NT is
+checked, and check SMB-Lan Manager if you have Windows 95/98/Me or
+older clients. The final step saves the Password Server configuration
+and prompts you to reboot.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-4"/><img src="figs/sam2_af04.gif"/></div><h4 class="head4">Figure F-4. Password Server authentication protocols</h4>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.5"/>
+
+<h3 class="head2">Enabling Password Server</h3>
+
+<p><a name="INDEX-14"/><a name="INDEX-15"/>To enable the
+use of Password Server for a user account, launch Workgroup Manager,
+and click the Accounts button in the toolbar. Under the Users tab on
+the far left (with the silhouette of a single person), select the
+account, and under the Advanced tab on the right, select Password
+Server for the User Password Type (see <a href="appf.html#samba2-APP-F-FIG-5">Figure F-5</a>).
+You are prompted to enter a new user password to be stored in the
+Password Server database. After saving the account configuration, the
+user can authenticate and access shares from an SMB client.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-5"/><img src="figs/sam2_af05.gif"/></div><h4 class="head4">Figure F-5. Workgroup Manager: Enabling Password Server authentication</h4>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-F-SECT-1.6"/>
+
+<h3 class="head2">Monitoring Services</h3>
+
+<p><a name="INDEX-16"/>Once you've got
+everything working, you'll want to keep an eye on
+things. The Server Status application gives you views into the
+various services provided by Mac OS X Server. For Windows Services,
+you can see the current state of the service, browse the logs
+(located in the directory
+<em class="filename">/Library/Logs/WindowsServices</em>), display and
+terminate individual connections, and view a graph of connections
+over time (see <a href="appf.html#samba2-APP-F-FIG-6">Figure F-6</a>). Similar information is
+provided for Print Service.</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-6"/><img src="figs/sam2_af06.gif"/></div><h4 class="head4">Figure F-6. Server Status: Windows Services</h4>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-APP-F-SECT-2"/>
+
+<h2 class="head1">Configuration Details</h2>
+
+<p><a name="INDEX-17"/>Underneath the GUI, a lot of activity
+takes place to offer Windows Services. In the non-Server version of
+Mac OS X, selecting Windows File Sharing sets the
+<tt class="literal">SMBSERVER</tt> parameter in
+<em class="filename">/etc/hostconfig</em> and triggers the Samba startup
+item. In Mac OS X Server, under normal circumstances the Samba
+startup item and the <tt class="literal">SMBSERVER</tt> parameter are never
+used.</p>
+
+<p>Instead, a process named <em class="emphasis">sambadmind</em> generates
+<em class="filename">/etc/smb.conf</em> from the configuration specified
+in Server Settings and Workgroup Manager and handles starting and
+restarting the Samba daemons as necessary. The
+<em class="emphasis">sambadmind</em> process is in turn monitored by
+<em class="emphasis">watchdog</em>, which keeps an eye on certain
+processes and restarts those which fail. The
+<em class="emphasis">watchdog</em> utility is configured in
+<em class="filename">/etc/watchdog.conf</em>, a file similar to a System V
+<em class="filename">inittab</em>, which specifies how the services under
+<em class="emphasis">watchdog</em>'s purview are to be
+treated. For example, the line for <em class="emphasis">sambadmind</em>
+looks like this:</p>
+
+<blockquote><pre class="code">sambadmin:respawn:/usr/sbin/sambadmind -d     # SMB Admin daemon</pre></blockquote>
+
+<p>Using a <em class="emphasis">watchdog</em>-monitored process such as
+<em class="emphasis">sambadmind</em> to start the Samba daemons, instead
+of a one-time execution of a startup item, results in more reliable
+service. In Mac OS X Server, if a Samba daemon dies unexpectedly, it
+is quickly restarted. (Examples of other services monitored by
+<em class="emphasis">watchdog</em> are Password Server, Print Service, and
+the Server Settings daemon that allows remote management.)</p>
+
+<p>There's another wrinkle in Mac OS X Server: the
+Samba configuration settings are not written directly to
+<em class="filename">/etc/smb.conf</em>, as they are in the non-Server
+version of Mac OS X. Instead, they're stored in the
+server's local Open Directory domain,<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> from which <em class="emphasis">sambadmind</em> retrieves them
+and regenerates <em class="filename">smb.conf</em>. For example, the Samba
+global parameters are stored in
+<em class="filename">/config/SMBServer</em> (see <a href="appf.html#samba2-APP-F-FIG-7">Figure F-7</a>). Share point information is also kept in Open
+Directory, under <em class="filename">/config/SharePoints</em>, while CUPS
+takes responsibility for printer configuration in
+<em class="filename">/etc/cups/printers.conf</em> (also creating stub
+entries used by Samba in <em class="filename">/etc/printcap</em>).</p>
+
+<div class="figure"><a name="samba2-APP-F-FIG-7"/><img src="figs/sam2_af07.gif"/></div><h4 class="head4">Figure F-7. NetInfo Manager: SMBServer properties</h4>
+
+<p><a href="appf.html#samba2-APP-F-TABLE-1">Table F-1</a> summarizes the association of Windows
+Services settings in the Server Settings application, properties
+stored in Open Directory, and parameters in
+<em class="filename">/etc/smb.conf</em>.</p>
+
+<a name="samba2-APP-F-TABLE-1"/><h4 class="head4">Table F-1. Samba configuration settings in Mac OS X Server</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Server Settings graphical element in Windows Services</p>
+</th>
+<th>
+<p>Open Directory property in <em class="filename">/config/SMBServer</em></p>
+</th>
+<th>
+<p>Samba global parameter in<em class="filename">/etc/smb.conf</em></p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>General &rarr; Server Name</p>
+</td>
+<td>
+<p><tt class="literal">netbios_name</tt></p>
+</td>
+<td>
+<p><tt class="literal">netbios name</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>General &rarr; Workgroup</p>
+</td>
+<td>
+<p><tt class="literal">workgroup</tt></p>
+</td>
+<td>
+<p><tt class="literal">workgroup</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>General &rarr; Description</p>
+</td>
+<td>
+<p><tt class="literal">description</tt></p>
+</td>
+<td>
+<p><tt class="literal">server string</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>General &rarr; Code Page</p>
+</td>
+<td>
+<p><tt class="literal">code_page</tt></p>
+</td>
+<td>
+<p><tt class="literal">client code page</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>General &rarr; Start Windows Services on system startup</p>
+</td>
+<td>
+<p><tt class="literal">auto_start</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Access &rarr; Allow Guest Access</p>
+</td>
+<td>
+<p><tt class="literal">guest_access</tt>, <tt class="literal">map_to_guest</tt></p>
+</td>
+<td>
+<p><tt class="literal">map to guest</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">guest_account</tt></p>
+</td>
+<td>
+<p><tt class="literal">guest account</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Access &rarr; Maximum client connections</p>
+</td>
+<td>
+<p><tt class="literal">max_connections</tt></p>
+</td>
+<td>
+<p><tt class="literal">max smbd processes</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Logging &rarr; Detail Level</p>
+</td>
+<td>
+<p><tt class="literal">logging</tt></p>
+</td>
+<td>
+<p><tt class="literal">log level</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Neighborhood &rarr; WINS Registration &rarr;
+Off</p>
+</td>
+<td>
+<p><tt class="literal">WINS_enabled</tt>, <tt class="literal">WINS_register</tt></p>
+</td>
+<td>
+<p><tt class="literal">wins support</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Neighborhood &rarr; WINS Registration &rarr;
+Enable WINS server</p>
+</td>
+<td>
+<p><tt class="literal">WINS_enabled</tt></p>
+</td>
+<td>
+<p><tt class="literal">wins support</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Neighborhood &rarr; WINS Registration &rarr;
+Register with WINS server</p>
+</td>
+<td>
+<p><tt class="literal">WINS_register</tt>, <tt class="literal">WINS_address</tt></p>
+</td>
+<td>
+<p><tt class="literal">wins server</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Neighborhood &rarr; Workgroup/Domain Services
+&rarr; Master Browser</p>
+</td>
+<td>
+<p><tt class="literal">Local_Master</tt></p>
+</td>
+<td>
+<p><tt class="literal">local master</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Neighborhood &rarr; Workgroup/Domain Services
+&rarr; Domain Master Browser</p>
+</td>
+<td>
+<p><tt class="literal">Domain_Master</tt></p>
+</td>
+<td>
+<p><tt class="literal">domain master</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Print &rarr; Start Print Service</p>
+</td>
+<td>
+<p><tt class="literal">printing</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">lprm_command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lprm command</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">lppause_command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lppause command</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">lpresume_command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpresume command</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">printer_admin</tt></p>
+</td>
+<td>
+<p><tt class="literal">printer admin</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">encryption</tt></p>
+</td>
+<td>
+<p><tt class="literal">encrypt passwords</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">coding_system</tt></p>
+</td>
+<td>
+<p><tt class="literal">coding system</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">log_dir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">smb_log</tt></p>
+</td>
+<td>
+<p><tt class="literal">log file</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">nmb_log</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">samba_sbindir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">samba_bindir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">samba_libdir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">samba_lockdir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">samba_vardir</tt></p>
+</td>
+<td>
+<p>N/A</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>N/A</p>
+</td>
+<td>
+<p><tt class="literal">stop_time</tt></p>
+</td>
+<td>
+<p>N/A <a name="INDEX-19"/></p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-APP-F-SECT-3"/>
+
+<h2 class="head1">Rolling Your Own</h2>
+
+<p><a name="INDEX-20"/>When making manual changes to the Samba
+configuration file, take care to block changes initiated from
+graphical applications by invoking this command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chflags uchg /etc/smb.conf</b></tt></pre></blockquote>
+
+<p>From that point on, the GUI will be useful only for starting,
+stopping, and monitoring the service&mdash;not for configuring it.</p>
+
+<p>If you install your own version of Samba, you can still manage it
+from Server Settings by changing some of the Open Directory
+properties in <em class="filename">/config/SMBServer</em>.</p>
+
+<p>To do this, open NetInfo Manager and modify the
+<tt class="literal">samba_sbindir</tt> and <tt class="literal">samba_bindir</tt>
+properties to match the location of your Samba installation.
+Optionally, you can modify <tt class="literal">samba_libdir</tt>,
+<tt class="literal">samba_vardir</tt>, and
+<tt class="literal">samba_lockdir</tt>. Assuming a default Samba
+installation, you can also change these at the command line with the
+following commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>nicl . -create /config/SMBServer samba_sbindir /usr/local/samba/bin</b></tt>
+# <tt class="userinput"><b>nicl . -create /config/SMBServer samba_bindir /usr/local/samba/bin</b></tt>
+# <tt class="userinput"><b>nicl . -create /config/SMBServer samba_libdir /usr/local/samba/lib</b></tt>
+# <tt class="userinput"><b>nicl . -create /config/SMBServer samba_vardir /usr/local/samba/var</b></tt>
+# <tt class="userinput"><b>nicl . -create /config/SMBServer samba_lockdir /usr/local/samba/var/locks</b></tt></pre></blockquote>
+
+<p>You can check your settings with this command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>nicl . -read /config/SMBServer</b></tt></pre></blockquote>
+
+<p>In Server Settings, select Stop Windows Services, then run this
+command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>killall sambadmind</b></tt></pre></blockquote>
+
+<p>The <em class="emphasis">watchdog</em> utility restarts
+<em class="emphasis">sambadmind</em> within seconds. Finally, go back to
+Server Settings, and select Start Windows Services.</p>
+
+<p>If you don't modify Open Directory properties to
+match your active Samba installation (because you wish to manage your
+configuration another way), be sure never to activate Windows
+Services from the Server Settings application, or
+you'll wind up with two sets of Samba daemons
+running concurrently. <a name="INDEX-21"/></p>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/>
+<p><a href="#FNPTR-1">[1]</a> In versions of Mac OS X prior to 10.2, Open Directory domains
+were called NetInfo domains. NetInfo Manager (located in
+<em class="filename">/Applications/Utilities</em>) provides a graphical
+interface to view and modify the contents of Open Directory
+databases. For more information, see the <em class="citetitle">Mac OS X Server
+Administrator's Guide</em>, as well as
+<em class="citetitle">Understanding and Using NetInfo</em>, downloadable
+from the Mac OS X Server resources web page at <a href="http://www.apple.com/server/resources.html">http://www.apple.com/server/resources.html</a>.</p>
+</blockquote>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/appg.html b/docs/htmldocs/using_samba/appg.html
new file mode 100644
index 0000000000..779f68034f
--- /dev/null
+++ b/docs/htmldocs/using_samba/appg.html
@@ -0,0 +1,500 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Appendix G. GNU Free Documentation License</h1>
+
+
+<div class="sect1"><a name="samba2-APP-G-SECT-1"/>
+
+<a name="INDEX-1"/><h2 class="head1">GNU Free Documentation License</h2>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.1"/>
+
+<h3 class="head2">Version 1.2, November 2002</h3>
+
+<p>Copyright &copy; 2000, 2001, 2002 Free Software Foundation, Inc.</p>
+
+<p>59 Temple Place, Suite 330, Boston, MA 02111-1307 USA</p>
+
+<p>Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.2"/>
+
+<h3 class="head2">0. PREAMBLE</h3>
+
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document
+&quot;free&quot; in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a
+way to get credit for their work, while not being considered
+responsible for modifications made by others.</p>
+
+<p>This License is a kind of
+&quot;copyleft&quot;, which means that
+derivative works of the document must themselves be free in the same
+sense. It complements the GNU General Public License, which is a
+copyleft license designed for free software.</p>
+
+<p>We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.3"/>
+
+<h3 class="head2">1. APPLICABILITY AND DEFINITIONS</h3>
+
+<p>This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The
+&quot;Document&quot;, below, refers to any
+such manual or work. Any member of the public is a licensee, and is
+addressed as &quot;you&quot;. You accept the
+license if you copy, modify or distribute the work in a way requiring
+permission under copyright law.</p>
+
+<p>A &quot;Modified Version&quot; of the
+Document means any work containing the Document or a portion of it,
+either copied verbatim, or with modifications and/or translated into
+another language.</p>
+
+<p>A &quot;Secondary Section&quot; is a named
+appendix or a front-matter section of the Document that deals
+exclusively with the relationship of the publishers or authors of the
+Document to the Document's overall subject (or to
+related matters) and contains nothing that could fall directly within
+that overall subject. (Thus, if the Document is in part a textbook of
+mathematics, a Secondary Section may not explain any mathematics.)
+The relationship could be a matter of historical connection with the
+subject or with related matters, or of legal, commercial,
+philosophical, ethical or political position regarding them.</p>
+
+<p>The &quot;Invariant Sections&quot; are
+certain Secondary Sections whose titles are designated, as being
+those of Invariant Sections, in the notice that says that the
+Document is released under this License. If a section does not fit
+the above definition of Secondary then it is not allowed to be
+designated as Invariant. The Document may contain zero Invariant
+Sections. If the Document does not identify any Invariant Sections
+then there are none.</p>
+
+<p>The &quot;Cover Texts&quot; are certain short
+passages of text that are listed, as Front-Cover Texts or Back-Cover
+Texts, in the notice that says that the Document is released under
+this License. A Front-Cover Text may be at most 5 words, and a
+Back-Cover Text may be at most 25 words.</p>
+
+<p>A &quot;Transparent&quot; copy of the
+Document means a machine-readable copy, represented in a format whose
+specification is available to the general public, that is suitable
+for revising the document straightforwardly with generic text editors
+or (for images composed of pixels) generic paint programs or (for
+drawings) some widely available drawing editor, and that is suitable
+for input to text formatters or for automatic translation to a
+variety of formats suitable for input to text formatters. A copy made
+in an otherwise Transparent file format whose markup, or absence of
+markup, has been arranged to thwart or discourage subsequent
+modification by readers is not Transparent. An image format is not
+Transparent if used for any substantial amount of text. A copy that
+is not &quot;Transparent&quot; is called
+&quot;Opaque&quot;.</p>
+
+<p>Examples of suitable formats for Transparent copies include plain
+ASCII without markup, T<sup class="superscript">E</sup>Xinfo input
+format, L<sup class="superscript">A</sup>T<sup class="superscript">E</sup>X
+input format, SGML or XML using a publicly available DTD, and
+standard-conforming simple HTML, PostScript or PDF designed for human
+modification. Examples of transparent image formats include PNG, XCF
+and JPG. Opaque formats include proprietary formats that can be read
+and edited only by proprietary word processors, SGML or XML for which
+the DTD and/or processing tools are not generally available, and the
+machine-generated HTML, PostScript or PDF produced by some word
+processors for output purposes only.</p>
+
+<p>The &quot;Title Page&quot; means, for a
+printed book, the title page itself, plus such following pages as are
+needed to hold, legibly, the material this License requires to appear
+in the title page. For works in formats which do not have any title
+page as such, &quot;Title Page&quot; means
+the text near the most prominent appearance of the
+work's title, preceding the beginning of the body of
+the text.</p>
+
+<p>A section &quot;Entitled XYZ&quot; means a
+named subunit of the Document whose title either is precisely XYZ or
+contains XYZ in parentheses following text that translates XYZ in
+another language. (Here XYZ stands for a specific section name
+mentioned below, such as
+&quot;Acknowledgments&quot;,
+&quot;Dedications&quot;,
+&quot;Endorsements&quot;, or
+&quot;History&quot;.) To
+&quot;Preserve the Title&quot; of such a
+section when you modify the Document means that it remains a section
+&quot;Entitled XYZ&quot; according to this
+definition.</p>
+
+<p>The Document may include Warranty Disclaimers next to the notice
+which states that this License applies to the Document. These
+Warranty Disclaimers are considered to be included by reference in
+this License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.4"/>
+
+<h3 class="head2">2. VERBATIM COPYING</h3>
+
+<p>You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no
+other conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.</p>
+
+<p>You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.5"/>
+
+<h3 class="head2">3. COPYING IN QUANTITY</h3>
+
+<p>If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you
+must enclose the copies in covers that carry, clearly and legibly,
+all these Cover Texts: Front-Cover Texts on the front cover, and
+Back-Cover Texts on the back cover. Both covers must also clearly and
+legibly identify you as the publisher of these copies. The front
+cover must present the full title with all words of the title equally
+prominent and visible. You may add other material on the covers in
+addition. Copying with changes limited to the covers, as long as they
+preserve the title of the Document and satisfy these conditions, can
+be treated as verbatim copying in other respects.</p>
+
+<p>If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.</p>
+
+<p>If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque
+copy a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute
+an Opaque copy (directly or through your agents or retailers) of that
+edition to the public.</p>
+
+<p>It is requested, but not required, that you contact the authors of
+the Document well before redistributing any large number of copies,
+to give them a chance to provide you with an updated version of the
+Document.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.6"/>
+
+<h3 class="head2">4. MODIFICATIONS</h3>
+
+<p>You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:</p>
+
+<ol><li>
+<p>Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions (which
+should, if there were any, be listed in the History section of the
+Document). You may use the same title as a previous version if the
+original publisher of that version gives permission.</p>
+</li><li>
+<p>List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.</p>
+</li><li>
+<p>State on the Title page the name of the publisher of the Modified
+Version, as the publisher.</p>
+</li><li>
+<p>Preserve all the copyright notices of the Document.</p>
+</li><li>
+<p>Add an appropriate copyright notice for your modifications adjacent
+to the other copyright notices.</p>
+</li><li>
+<p>Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.</p>
+</li><li>
+<p>Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's
+license notice.</p>
+</li><li>
+<p>Include an unaltered copy of this License.</p>
+</li><li>
+<p>Preserve the section Entitled
+&quot;History&quot;, Preserve its Title, and
+add to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page. If
+there is no section Entitled
+&quot;History&quot; in the Document, create
+one stating the title, year, authors, and publisher of the Document
+as given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.</p>
+</li><li>
+<p>Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise the
+network locations given in the Document for previous versions it was
+based on. These may be placed in the
+&quot;History&quot; section. You may omit a
+network location for a work that was published at least four years
+before the Document itself, or if the original publisher of the
+version it refers to gives permission.</p>
+</li><li>
+<p>For any section Entitled
+&quot;Acknowledgments&quot; or
+&quot;Dedications&quot;, Preserve the Title
+of the section, and preserve in the section all the substance and
+tone of each of the contributor acknowledgments and/or dedications
+given therein.</p>
+</li><li>
+<p>Preserve all the Invariant Sections of the Document, unaltered in
+their text and in their titles. Section numbers or the equivalent are
+not considered part of the section titles.</p>
+</li><li>
+<p>Delete any section Entitled
+&quot;Endorsements&quot;. Such a section may
+not be included in the Modified Version.</p>
+</li><li>
+<p>Do not retitle any existing section to be Entitled
+&quot;Endorsements&quot; or to conflict in
+title with any Invariant Section.</p>
+</li><li>
+<p>Preserve any Warranty Disclaimers.</p>
+
+<p>If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or
+all of these sections as invariant. To do this, add their titles to
+the list of Invariant Sections in the Modified
+Version's license notice. These titles must be
+distinct from any other section titles.</p>
+
+<p>You may add a section Entitled
+&quot;Endorsements&quot;, provided it
+contains nothing but endorsements of your Modified Version by various
+parties&mdash;for example, statements of peer review or that the text
+has been approved by an organization as the authoritative definition
+of a standard.</p>
+
+<p>You may add a passage of up to five words as a Front-Cover Text, and
+a passage of up to 25 words as a Back-Cover Text, to the end of the
+list of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.</p>
+
+<p>The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.</p>
+</li></ol>
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.7"/>
+
+<h3 class="head2">5. COMBINING DOCUMENTS</h3>
+
+<p>You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.</p>
+
+<p>The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique
+number. Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.</p>
+
+<p>In the combination, you must combine any sections Entitled
+&quot;History&quot; in the various original
+documents, forming one section Entitled
+&quot;History&quot;; likewise combine any
+sections Entitled
+&quot;Acknowledgements&quot;, and any
+sections Entitled &quot;Dedications&quot;.
+You must delete all sections Entitled
+&quot;Endorsements&quot;.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.8"/>
+
+<h3 class="head2">6. COLLECTIONS OF DOCUMENTS</h3>
+
+<p>You may make a collection consisting of the Document and other
+documents released under this License, and replace the individual
+copies of this License in the various documents with a single copy
+that is included in the collection, provided that you follow the
+rules of this License for verbatim copying of each of the documents
+in all other respects.</p>
+
+<p>You may extract a single document from such a collection, and
+distribute it individually under this License, provided you insert a
+copy of this License into the extracted document, and follow this
+License in all other respects regarding verbatim copying of that
+document.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.9"/>
+
+<h3 class="head2">7. AGGREGATION WITH INDEPENDENT WORKS</h3>
+
+<p>A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an
+&quot;aggregate&quot; if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the
+individual works permit. When the Document is included as an
+aggregate, this License does not apply to the other works in the
+aggregate which are not themselves derivative works of the Document.</p>
+
+<p>If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may
+be placed on covers that bracket the Document within the aggregate,
+or the electronic equivalent of covers if the Document is in
+electronic form. Otherwise they must appear on printed covers that
+bracket the whole aggregate.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.10"/>
+
+<h3 class="head2">8. TRANSLATION</h3>
+
+<p>Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also
+include the original English version of this License and the original
+versions of those notices and disclaimers. In case of a disagreement
+between the translation and the original version of this License or a
+notice or disclaimer, the original version will prevail.</p>
+
+<p>If a section in the Document is Entitled
+&quot;Acknowledgements&quot;,
+&quot;Dedications&quot;, or
+&quot;History&quot;, the requirement (section
+4) to Preserve its Title (section 1) will typically require changing
+the actual title.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.11"/>
+
+<h3 class="head2">9. TERMINATION</h3>
+
+<p>You may not copy, modify, sublicense, or distribute the Document
+except as expressly provided for under this License. Any other
+attempt to copy, modify, sublicense or distribute the Document is
+void, and will automatically terminate your rights under this
+License. However, parties who have received copies, or rights, from
+you under this License will not have their licenses terminated so
+long as such parties remain in full compliance.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-APP-G-SECT-1.12"/>
+
+<h3 class="head2">10. FUTURE REVISIONS OF THIS LICENSE</h3>
+
+<p>The Free Software Foundation may publish new, revised versions of the
+GNU Free Documentation License from time to time. Such new versions
+will be similar in spirit to the present version, but may differ in
+detail to address new problems or concerns. See <a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.</p>
+
+<p>Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License &quot;or any later version&quot;
+applies to it, you have the option of following the terms and
+conditions either of that specified version or of any later version
+that has been published (not as a draft) by the Free Software
+Foundation. If the Document does not specify a version number of this
+License, you may choose any version ever published (not as a draft)
+by the Free Software Foundation. <a name="INDEX-2"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/ch00.html b/docs/htmldocs/using_samba/ch00.html
new file mode 100644
index 0000000000..5a2c89feb8
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch00.html
@@ -0,0 +1,368 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Preface</h1>
+
+
+<p>You are reading a book about Samba, a software suite that networks
+Windows, Unix, and other operating systems using
+Windows' native networking protocol. Samba allows
+Unix servers to offer Windows networking services by matching the
+filesystem and networking models of Unix to those of Windows. Samba
+acts as a bridge between the two systems, connecting the
+corresponding parts of their architectures and providing a
+translation wherever necessary.</p>
+
+<p>Bridging the gap between systems as dissimilar as Windows and Unix is
+a complex task, which Samba handles surprisingly well. To be a good
+Samba administrator, your abilities must parallel
+Samba's. For starters, you need to know basic Unix
+system and network administration and have a good understanding of
+Windows filesystems and networking fundamentals. In addition, you
+need to learn how Samba fills in the &quot;gray
+area&quot; between Unix and Windows. Once you know how
+everything fits together, you'll find it easy to
+configure a Samba server to provide your network with reliable and
+high-performance computational resources.</p>
+
+<p>Our job is to make all of that easier for you. We do this by starting
+out with a quick and yet comprehensive tour of Windows networking in
+<a href="ch01.html">Chapter 1</a>, followed by tutorially-oriented
+<a href="ch02.html">Chapter 2</a> and <a href="ch03.html">Chapter 3</a>, which tell you how to set up a minimal Samba server
+and configure Windows clients to work with it. Most likely, you will
+be surprised how quickly you can complete the required tasks.</p>
+
+<p>We believe that a hands-on approach is the most effective, and you
+can use the Samba server you build in <a href="ch02.html">Chapter 2</a> and <a href="ch03.html">Chapter 3</a> as a test
+system for trying out examples that we show and describe throughout
+the book. You can jump around from chapter to chapter if you like,
+but if you continue sequentially from <a href="ch04.html">Chapter 4</a>
+onward, by the time you finish the book you will have a
+well-configured production Samba server ready for use. All you have
+to do is add the appropriate support for your intended purpose as we
+explain how to use each feature.</p>
+
+
+
+<div class="sect1"><a name="samba2-PREFACE-2-SECT-1"/>
+
+<h2 class="head1">Audience for This Book</h2>
+
+<p>This book is primarily intended for Unix administrators who need to
+support Windows clients on their network, as well as anyone who needs
+to access the resources of a Windows network environment from a Unix
+client. While we assume you are familiar with basic Unix system
+administration, we do <em class="emphasis">not</em> assume you are a
+networking expert. We do our best along the way to help out with
+unusual definitions and terms.</p>
+
+<p>Furthermore, we don't assume that you are an expert
+in Microsoft Windows. We carefully explain all the essential concepts
+related to Windows networking, and we go through the Windows side of
+the installation task in considerable detail, providing examples for
+both Windows 95/98/Me and Windows NT/2000/XP, which are significantly
+different. For the Unix side, we give examples that work with common
+Unix operating systems, such as Linux, Solaris, FreeBSD, and Mac OS
+X.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-PREFACE-2-SECT-2"/>
+
+<h2 class="head1">Organization</h2>
+
+<p>Here is a quick description of each chapter:</p>
+
+<p><a href="ch01.html">Chapter 1</a> introduces Samba and its capabilities,
+then describes the most important concepts of NetBIOS and SMB/CIFS
+networking. Finally, we give you a quick overview of the daemons and
+utilities that are included in the Samba distribution.</p>
+
+<p><a href="ch02.html">Chapter 2</a> covers configuring, compiling,
+installing, setting up, and testing the Samba server on a Unix
+platform.</p>
+
+<p><a href="ch03.html">Chapter 3</a> explains how to configure Microsoft
+Windows 95/98/Me and Windows NT/2000/XP clients to participate in an
+SMB network.</p>
+
+<p><a href="ch04.html">Chapter 4</a> explains the ins and outs of Windows NT
+domains and how to configure Samba to work in a network set up as a
+Windows NT domain.</p>
+
+<p><a href="ch05.html">Chapter 5</a> describes methods for accessing SMB
+shares on the network from Unix client systems.</p>
+
+<p><a href="ch06.html">Chapter 6</a>
+gets you up to speed on the structure of the Samba
+configuration file and shows you how to take control of file-sharing
+services.</p>
+
+<p><a href="ch07.html">Chapter 7</a> introduces name resolution, which is
+used to convert NetBIOS computer names into IP addresses, and
+browsing, the method used in SMB networking to find what resources
+are being shared on the network.</p>
+
+<p><a href="ch08.html">Chapter 8</a> continues the discussion of file-sharing options, and
+covers more advanced functions such as permissions, access control
+lists, opportunistic locks, and setting up a Distributed filesystem
+tree.</p>
+
+<p><a href="ch09.html">Chapter 9</a> discusses how
+to set up Samba users, introduces you to Samba security, and shows
+you how to work with encrypted and nonencrypted passwords.</p>
+
+<p><a href="ch10.html">Chapter 10</a>
+discusses printer setup for sharing Unix printers on the
+SMB network, and allowing Unix workstations to access SMB shared
+printers.</p>
+
+<p><a href="ch11.html">Chapter 11</a>
+bundles several miscellaneous topics associated with
+Samba, such as configuring Samba shares for programmers and
+internationalization issues.</p>
+
+<p><a href="ch12.html">Chapter 12</a> details what to do if
+you have problems installing Samba. This comparatively
+large chapter is packed with troubleshooting hints and strategies for
+identifying what is going wrong.</p>
+
+<p><a href="appa.html">Appendix A</a> provides working examples of
+<em class="filename">smb.conf</em> files for use in configuring Samba for
+its more common applications. You can easily modify the examples for
+use in a wide variety of circumstances.</p>
+
+<p><a href="appb.html">Appendix B</a> covers each option that can be used in
+the Samba configuration file.</p>
+
+<p><a href="appc.html">Appendix C</a> is a quick reference that covers each
+server daemon and tool that make up the Samba suite.</p>
+
+<p><a href="appd.html">Appendix D</a> explains how to download the latest
+development version of the Samba source code using CVS.</p>
+
+<p><a href="appe.html">Appendix E</a> documents each option that can be used
+with the <em class="emphasis">configure</em> command before compiling the
+Samba source code.</p>
+
+<p><a href="appf.html">Appendix F</a> includes directions for sharing files
+and printers with the Server edition of Mac OS X.</p>
+
+<p><a href="appg.html">Appendix G</a> is the copyright license under which
+this book is published.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-PREFACE-2-SECT-3"/>
+
+<h2 class="head1">Conventions Used in This Book</h2>
+
+<p>The following font conventions are followed throughout this book:</p>
+
+<dl>
+<dt><b>Italic </b></dt>
+<dd>
+<p>Filenames, file extensions, URLs, executable files, command options,
+and emphasis.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">Constant</tt> <tt class="literal">width</tt> </b></dt>
+<dd>
+<p>Samba configuration options, computer names, user and group names,
+hostnames, domain names, other code that appears in the text, and
+command-line information that should be typed verbatim on the screen.</p>
+</dd>
+
+
+
+<dt><b><tt class="userinput"><b>Constant width bold</b></tt> </b></dt>
+<dd>
+<p>Commands that are entered by the user and new configuration options
+that we wish to bring to the attention of the reader.</p>
+</dd>
+
+
+
+<dt><b><em class="replaceable">Constant width italic</em></b></dt>
+<dd>
+<p>Replaceable content in code and command-line information.</p>
+</dd>
+
+</dl>
+
+<a name="samba2-PREFACE-2-NOTE-82"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>This designates a note, which is an important aside to the nearby
+text.</p>
+</blockquote>
+<a name="samba2-PREFACE-2-NOTE-83"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>This designates a warning related to the nearby text.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-PREFACE-2-SECT-4"/>
+
+<h2 class="head1">How to Contact Us</h2>
+
+<p>We have tested and verified the information in this book to the best
+of our ability, but you might find that features have changed (or
+even that we have made mistakes!). Please let us know about any
+errors you find, as well as your suggestions for future editions, by
+writing to:</p>
+
+<blockquote class="simplelist">
+
+<p>O'Reilly &amp; Associates, Inc.</p>
+
+<p>1005 Gravenstein Highway North</p>
+
+<p>Sebastopol, CA 95472</p>
+
+<p>(800) 998-9938 (in the United States or Canada)</p>
+
+<p>(707) 829-0515 (international/local)</p>
+
+<p>(707) 829-0104 (fax)</p>
+
+</blockquote>
+
+<p>To ask technical questions or comment on the book, send email to:</p>
+
+<blockquote class="simplelist">
+
+<p><em class="email">bookquestions@oreilly.com</em></p>
+
+</blockquote>
+
+<p>We have a web page for this book where we list examples and any plans
+for future editions. You can access this information at:</p>
+
+<blockquote class="simplelist">
+
+<p><a href="http://www.oreilly.com/catalog/samba2">http://www.oreilly.com/catalog/samba2</a></p>
+
+</blockquote>
+
+<p>You can also contact Jay Ts, the lead author of this edition, through
+his web site at:</p>
+
+<blockquote class="simplelist">
+
+<p><a href="http://www.jayts.com">http://www.jayts.com</a></p>
+
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-PREFACE-2-SECT-5"/>
+
+<h2 class="head1">Acknowledgments</h2>
+
+<p>We thank Leon Towns-von Stauber for thoroughly researching the use of
+Samba on Mac OS X and writing material that appears in <a href="ch02.html">Chapter 2</a>, <a href="ch05.html">Chapter 5</a>, and <a href="ch10.html">Chapter 10</a>, as well as the entire <a href="appf.html">Appendix F</a>. We also thank our technical reviewers Sam
+Johnston, Matthew Temple, Marty Leisner, and Don McCall.</p>
+
+
+<div class="sect2"><a name="samba2-PREFACE-2-SECT-5.1"/>
+
+<h3 class="head2">Jay Ts</h3>
+
+<p>This book would have been extremely difficult to write if it
+hadn't been for the copy of VMware Workstation
+graciously provided by VMware, Inc. I want to thank Rik Farrow for
+his clarifying comments on security topics related to Samba and
+Windows, and both him and Rose Moon for their supportive friendship.
+Thanks also go to Mark Watson for his encouragement and advice on the
+topic of authoring technical books. Additionally,
+I'd like to express my appreciation to Andy Oram at
+O'Reilly for being a supportive, friendly, and
+easygoing editor, and for offering me terms that I could say yes
+to&mdash;something that a few other publishers
+didn't even approach. SuSE, Inc. generously provided
+a copy of SuSE Linux 8.1 Professional.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-PREFACE-2-SECT-5.2"/>
+
+<h3 class="head2">Robert Eckstein</h3>
+
+<p>I'd first like to recognize Dave Collier-Brown and
+Peter Kelly for all their help in the creation of this book.
+I'd also like to thank each technical reviewer who
+helped polish this book into shape on such short notice: Matthew
+Temple, Jeremy Allison, and of course Andrew Tridgell. Andrew and
+Jeremy deserve special recognition, not only for creating such a
+wonderful product, but also for providing a tireless amount of
+support in the final phase of this book&mdash;hats off to you, guys!
+A warm hug goes out to my wife Michelle, who once again put up with a
+husband loaded down with too much caffeine and a tight schedule.
+Thanks to Dave Sifry and the people at LinuxCare, San Francisco, for
+hosting me on such short notice for Andrew
+Tridgell's visit. And finally, a huge amount of
+thanks to our editor, Andy Oram, who (very) patiently helped guide
+this book through its many stages until we got it right.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-PREFACE-2-SECT-5.3"/>
+
+<h3 class="head2">David Collier-Brown</h3>
+
+<p>I'd particularly like to thank Joyce, who put up
+with me during the sometimes exciting development of the book. My
+thanks to Andy Oram, who was kind enough to provide the criticism
+that allowed me to contribute; the crew at ACE (Opcom) who humored
+the obvious madman in their midst; and Ian MacMillan, who voluntarily
+translated several of my early drafts from nerd to English. I would
+also like to give special thanks to Perry Donham, Drew Sullivan, and
+Jerry DeRoo for starting and sustaining this mad project. Finally,
+I'd like to thank Bob Eckstein for a final,
+sustained, and professional effort that lifted the whole book up to
+the level that Andy needed.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-PREFACE-2-SECT-5.4"/>
+
+<h3 class="head2">All</h3>
+
+<p>We would especially like to give thanks to Perry Donham and Peter
+Kelly for helping mold the first draft of this book. Although Perry
+was unable to contribute to subsequent drafts, his material was
+essential to getting this book off on the right foot. In addition,
+some of the browsing material came from text originally written by
+Dan Shearer for O'Reilly.</p>
+
+
+</div>
+
+
+</div>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/ch01.html b/docs/htmldocs/using_samba/ch01.html
new file mode 100644
index 0000000000..98a687f08e
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch01.html
@@ -0,0 +1,3193 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 1. Learning the Samba</h1>
+
+
+<p><a name="INDEX-1"/>Samba
+is an extremely useful networking tool for anyone who has both
+Windows and Unix systems on his network. Running on a Unix system, it
+allows Windows to share files and printers on the Unix host, and it
+also allows Unix users to access resources shared by Windows systems.</p>
+
+<p>Although it might seem natural to use a Windows server to serve files
+and printers to a network containing Windows clients, there are good
+reasons for preferring a Samba server for this duty. Samba is
+reliable software that runs on reliable Unix operating systems,
+resulting in fewer problems and a low cost of maintenance. Samba also
+offers better performance under heavy loads, outperforming Windows
+2000 Server by a factor of 2 to 1 on identical PC hardware, according
+to published third-party benchmarks. When common, inexpensive PC
+hardware fails to meet the demands of a huge client load, the Samba
+server can easily be moved to a proprietary &quot;big
+iron&quot; Unix mainframe, which can outperform Windows
+running on a PC many times. If all that weren't
+enough, Samba has a very nice cost advantage: it's
+free. Not only is the software itself freely available, but also no
+client licenses are required, and it runs on high-quality, free
+operating systems such as Linux and FreeBSD.</p>
+
+<p>After reading the previous paragraph, you might come to the
+conclusion that Samba is commonly used by large organizations with
+thousands of users on their networks&mdash;and you'd
+be right! But Samba's user base includes
+organizations all over the planet, of all types and sizes: from
+international corporations, to medium and small businesses, to
+individuals who run Samba on their Linux laptops. In the last case, a
+tool such as VMware is used to run Windows on the same computer, with
+Samba enabling the two operating systems to share files.</p>
+
+<p>The types of users vary even more&mdash;Samba is used by
+corporations, banks and other financial institutions, government and
+military organizations, schools, public libraries, art galleries,
+families, and even authors! This book was developed on a Linux system
+running VMware and Windows 2000, with Adobe FrameMaker running on
+Windows and the document files served by Samba from the Linux
+filesystem.</p>
+
+<p>Does all this whet your technological appetite? If so, we encourage
+you to keep reading, learn about Samba, and follow our examples to
+set up a Samba server of your own. In this and upcoming chapters, we
+will tell you exactly how to get started.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-1"/>
+
+<h2 class="head1">What Is Samba?</h2>
+
+<p><a name="INDEX-2"/>Samba
+is a suite of Unix applications that speak the
+<a name="INDEX-3"/><a name="INDEX-4"/>Server
+Message Block (SMB) protocol. Microsoft Windows operating systems and
+the OS/2 operating system use SMB to perform client-server networking
+for file and printer sharing and associated operations. By supporting
+this protocol, Samba enables computers running Unix to get in on the
+action, communicating with the same networking protocol as Microsoft
+Windows and appearing as another Windows system on the network from
+the perspective of a Windows client. A <a name="INDEX-5"/>Samba
+server offers the following services:</p>
+
+<ul><li>
+<p>Share one or more directory trees</p>
+</li><li>
+<p>Share one or more Distributed filesystem (Dfs) trees</p>
+</li><li>
+<p>Share printers installed on the server among Windows clients on the
+network</p>
+</li><li>
+<p>Assist clients with network browsing</p>
+</li><li>
+<p>Authenticate clients logging onto a Windows domain</p>
+</li><li>
+<p>Provide or assist with Windows Internet Name Service (WINS)
+name-server resolution</p>
+</li></ul>
+<p>The Samba suite also includes client tools that allow users on a Unix
+system to access folders and printers that Windows systems and Samba
+servers offer on the network.</p>
+
+<p>Samba is the brainchild of Andrew <a name="INDEX-6"/>Tridgell, who currently heads the Samba
+development team. Andrew started the project in 1991, while working
+with a Digital Equipment Corporation (DEC) software suite called
+Pathworks, created for connecting DEC VAX computers to computers made
+by other companies. Without knowing the significance of what he was
+doing, Andrew created a file-server program for an odd protocol that
+was part of Pathworks. That protocol later turned out to be SMB. A
+few years later, he expanded upon his custom-made SMB server and
+began distributing it as a product on the Internet under the name
+&quot;SMB Server.&quot; However, Andrew
+couldn't keep that name&mdash;it already belonged to
+another company's product&mdash;so he tried the
+following Unix renaming approach:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>grep -i '^s.*m.*b' /usr/dict/words</b></tt></pre></blockquote>
+
+<p>And the response was:</p>
+
+<blockquote><pre class="code">salmonberry
+samba
+sawtimber
+scramble</pre></blockquote>
+
+<p>Thus, the name &quot;Samba&quot; was born.</p>
+
+<p>Today, the Samba suite revolves around a pair of Unix daemons that
+provide shared resources&mdash;called <em class="firstterm">shares
+</em>or s<em class="firstterm">ervices</em>&mdash;to SMB clients
+on the network. These are:</p>
+
+<dl>
+<dt><b><a name="INDEX-7"/>smbd</b></dt>
+<dd>
+<p>A daemon that handles file and printer sharing and provides
+authentication and authorization for SMB clients.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-8"/>nmbd</b></dt>
+<dd>
+<p>A daemon that supports NetBIOS Name Service and WINS, which is
+Microsoft's implementation of a NetBIOS Name Server
+(NBNS). It also assists with network browsing.</p>
+</dd>
+
+</dl>
+
+<p>Samba is currently maintained and extended by a group of volunteers
+under the active supervision of Andrew Tridgell. Like the Linux
+operating system, Samba is distributed as open source software
+(<a href="http://opensource.org">http://opensource.org</a>) by its
+authors and is distributed under the GNU General Public License
+(GPL). Since its inception, development of Samba has been sponsored
+in part by the Australian National University, where Andrew Tridgell
+earned his Ph.D. Since then, many other organizations have sponsored
+Samba developers, including LinuxCare, VA Linux Systems,
+Hewlett-Packard, and IBM. It is a true testament to Samba that both
+commercial and noncommercial entities are prepared to spend money to
+support an open source effort.</p>
+
+<p>Microsoft has also contributed by offering its definition of the SMB
+protocol to the Internet Engineering Task Force (IETF) in 1996 as the
+<a name="INDEX-9"/><a name="INDEX-10"/>Common
+Internet File System (CIFS). Although we prefer to use the term
+&quot;SMB&quot; in this book, you will also
+often find the protocol being referred to as
+&quot;CIFS.&quot; This is especially true on
+Microsoft's web site.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-2"/>
+
+<h2 class="head1">What Can Samba Do for Me?</h2>
+
+<p><a name="INDEX-11"/>As explained earlier, Samba can help
+Windows and Unix computers coexist in the same network. However,
+there are some specific reasons why you might want to set up a Samba
+server on your network:</p>
+
+<ul><li>
+<p>You don't want to pay for&mdash;or
+can't afford&mdash;a full-fledged Windows server,
+yet you still need the functionality that one provides.</p>
+</li><li>
+<p>The Client Access Licenses (CALs) that Microsoft requires for each
+Windows client to access a Windows server are unaffordable.</p>
+</li><li>
+<p>You want to provide a common area for data or user directories to
+transition from a Windows server to a Unix one, or vice versa.</p>
+</li><li>
+<p>You want to share printers among Windows and Unix workstations.</p>
+</li><li>
+<p>You are supporting a group of computer users who have a mixture of
+Windows and Unix computers.</p>
+</li><li>
+<p>You want to integrate Unix and Windows authentication, maintaining a
+single database of user accounts that works with both systems.</p>
+</li><li>
+<p>You want to network Unix, Windows, Macintosh (OS X), and other
+systems using a single protocol.</p>
+</li></ul>
+<p>Let's take a quick tour of
+<a name="INDEX-12"/>Samba in action. Assume that we have
+the following basic network configuration: a Samba-enabled Unix
+system, to which we will assign the name <tt class="literal">toltec</tt>,
+and a pair of Windows clients, to which we will assign the names
+<tt class="literal">maya</tt> and <tt class="literal">aztec</tt>, all connected
+via a local area network (LAN). Let's also assume
+that <tt class="literal">toltec</tt> also has a local inkjet printer
+connected to it, <tt class="literal">lp</tt>, and a disk share named
+<tt class="literal">spirit</tt>&mdash;both of which it can offer to the
+other two computers. A graphic of this network is shown in <a href="ch01.html#samba2-CHP-1-FIG-1">Figure 1-1</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-1"/><img src="figs/sam2_0101.gif"/></div><h4 class="head4">Figure 1-1. A simple network set up with a Samba server</h4>
+
+<p>In this network, each computer listed shares the same
+<em class="firstterm">workgroup</em>. A workgroup is a group name tag
+that identifies an arbitrary collection of computers and their
+resources on an SMB network. Several workgroups can be on the network
+at any time, but for our basic network example,
+we'll have only one: the METRAN workgroup.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-2.1"/>
+
+<h3 class="head2">Sharing a Disk Service</h3>
+
+<p><a name="INDEX-13"/><a name="INDEX-14"/><a name="INDEX-15"/>If everything is properly
+configured, we should be able to see the Samba server,
+<tt class="literal">toltec</tt>, through the Network Neighborhood of the
+<tt class="literal">maya</tt> Windows desktop. In fact, <a href="ch01.html#samba2-CHP-1-FIG-2">Figure 1-2</a> shows the Network Neighborhood of the
+<tt class="literal">maya</tt> computer, including <tt class="literal">toltec</tt>
+and each computer that resides in the METRAN workgroup. Note the
+Entire Network icon at the top of the list. As we just mentioned,
+more than one workgroup can be on an SMB network at any given time.
+If a user clicks the Entire Network icon, she will see a list of all
+the workgroups that currently exist on the network.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-2"/><img src="figs/sam2_0102.gif"/></div><h4 class="head4">Figure 1-2. The Network Neighborhood directory</h4>
+
+<p>We can take a closer look at the <tt class="literal">toltec</tt> server by
+double-clicking its icon. This contacts <tt class="literal">toltec</tt>
+itself and requests a list of its
+<em class="firstterm">shares</em>&mdash;the file and printer
+resources&mdash;that the computer provides. In this case, a printer
+named <tt class="literal">lp</tt>, a home directory named
+<tt class="literal">jay</tt>, and a disk share named
+<tt class="literal">spirit</tt> are on the server, as shown in <a href="ch01.html#samba2-CHP-1-FIG-3">Figure 1-3</a>. Note that the Windows display shows hostnames
+in mixed case (Toltec). Case is irrelevant in hostnames, so you might
+see toltec, Toltec, and TOLTEC in various displays or command output,
+but they all refer to a single system. Thanks to Samba, Windows 98
+sees the Unix server as a valid SMB server and can access the
+<tt class="literal">spirit</tt> folder as if it were just another system
+folder.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-3"/><img src="figs/sam2_0103.gif"/></div><h4 class="head4">Figure 1-3. Shares available on the Toltec server as viewed from maya</h4>
+
+<p>One popular Windows feature is the ability to map a drive letter
+(such as E:, F:, or Z:) to a shared directory on the network using
+the Map Network Drive option in Windows Explorer.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a>
+Once you do so, your applications can access the folder across the
+network using the drive letter. You can store data on it, install and
+run programs from it, and even password-protect it against unwanted
+visitors. See <a href="ch01.html#samba2-CHP-1-FIG-4">Figure 1-4</a> for an example of mapping
+a <a name="INDEX-16"/><a name="INDEX-17"/>drive letter to a network
+directory.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-4"/><img src="figs/sam2_0104.gif"/></div><h4 class="head4">Figure 1-4. Mapping a network drive to a Windows drive letter</h4>
+
+<p>Take a look at the Path: entry in the dialog box of <a href="ch01.html#samba2-CHP-1-FIG-4">Figure 1-4</a>. An equivalent way to represent a directory on
+a network computer is by using two backslashes, followed by the name
+of the networked computer, another backslash, and the networked
+directory of the computer, as shown here:</p>
+
+<blockquote><pre class="code">\\<em class="replaceable">network-computer</em>\<em class="replaceable">directory</em></pre></blockquote>
+
+<p>This is known as the <em class="firstterm"/><a name="INDEX-18"/>Universal
+Naming Convention (UNC)</em>  in the Windows world. For example, the dialog
+box in <a href="ch01.html#samba2-CHP-1-FIG-4">Figure 1-4</a> represents the network directory
+on the <tt class="literal">toltec</tt> server as:</p>
+
+<blockquote><pre class="code">\\toltec\spirit</pre></blockquote>
+
+<p>If this looks somewhat familiar to you, you're
+probably thinking of <em class="firstterm">uniform resource
+locators</em><a name="INDEX-19"/><a name="INDEX-20"/> (URLs), which are addresses that web
+browsers such as Netscape Navigator and Internet Explorer use to
+resolve systems across the Internet. Be sure not to confuse the two:
+URLs such as <a href="http://www.oreilly.com">http://www.oreilly.com</a> use forward slashes
+instead of backslashes, and they precede the initial slashes with the
+data transfer protocol (i.e., ftp, http) and a colon (:). In reality,
+URLs and UNCs are two completely separate things, although sometimes
+you can specify an SMB share using a URL rather than a UNC. As a URL,
+the <em class="filename">\\toltec\spirit</em> share would be specified as
+<em class="filename">smb://toltec/spirit</em>.</p>
+
+<p>Once the network drive is set up, Windows and its programs behave as
+if the networked directory were a local disk. If you have any
+applications that support multiuser functionality on a network, you
+can install those programs on the network drive.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> <a href="ch01.html#samba2-CHP-1-FIG-5">Figure 1-5</a> shows the
+resulting network drive as it would appear with other storage devices
+in the Windows 98 client. Note the pipeline attachment in the icon
+for the J: drive; this indicates that it is a network drive rather
+than a fixed drive.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-5"/><img src="figs/sam2_0105.gif"/></div><h4 class="head4">Figure 1-5. The Network directory mapped to the client drive letter J</h4>
+
+<p>My Network Places, found in Windows Me, 2000, and XP, works
+differently from Network Neighborhood. It is necessary to click a few
+more icons, but eventually we can get to the view of the
+<tt class="literal">toltec</tt> server as shown in <a href="ch01.html#samba2-CHP-1-FIG-6">Figure 1-6</a>. This is from a Windows 2000 system. Setting
+up the network drive using the Map Network Drive option in Windows
+2000 works similarly to other Windows versions. <a name="INDEX-21"/><a name="INDEX-22"/><a name="INDEX-23"/></p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-6"/><img src="figs/sam2_0106.gif"/></div><h4 class="head4">Figure 1-6. Shares available on Toltec (viewed from dine)</h4>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-2.2"/>
+
+<h3 class="head2">Sharing a Printer</h3>
+
+<p><a name="INDEX-24"/><a name="INDEX-25"/><a name="INDEX-26"/>You probably noticed that the printer
+<tt class="literal">lp</tt> appeared under the available shares for
+<tt class="literal">toltec</tt> in <a href="ch01.html#samba2-CHP-1-FIG-3">Figure 1-3</a>. This
+indicates that the Unix server has a printer that can be shared by
+the various SMB clients in the workgroup. Data sent to the printer
+from any of the clients will be spooled on the Unix server and
+printed in the order in which it is received.</p>
+
+<p><a name="INDEX-27"/><a name="INDEX-28"/>Setting up a Samba-enabled
+printer on the Windows side is even easier than setting up a disk
+share. By double-clicking the printer and identifying the
+manufacturer and model, you can install a driver for this printer on
+the Windows client. Windows can then properly format any information
+sent to the network printer and access it as if it were a local
+printer. On Windows 98, double-clicking the Printers icon in the
+Control Panel opens the Printers window shown in <a href="ch01.html#samba2-CHP-1-FIG-7">Figure 1-7</a>. Again, note the pipeline attachment below the
+printer, which identifies it as being on a network.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-7"/><img src="figs/sam2_0107.gif"/></div><h4 class="head4">Figure 1-7. A network printer available on Toltec</h4>
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-2.2.1"/>
+
+<h3 class="head3">Seeing things from the Unix side</h3>
+
+<p><a name="INDEX-29"/><a name="INDEX-30"/>As mentioned earlier, Samba
+appears in Unix as a set of daemon programs. You can view them with
+the Unix <a name="INDEX-31"/><em class="emphasis">ps</em> command; you can
+read any messages they generate through custom debug files or the
+Unix <em class="emphasis">syslog</em> (depending on how Samba is set up);
+and you can configure them from a single Samba configuration file:
+<em class="emphasis">smb.conf</em>. In addition, if you want to get an idea of
+what the daemons are doing, Samba has a program called
+<em class="emphasis">smbstatus</em><a name="INDEX-32"/> that will lay it all on the line. Here
+is how it works:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbstatus</b></tt>
+Processing section &quot;[homes]&quot;
+Processing section &quot;[printers]&quot;
+Processing section &quot;[spirit]&quot;
+
+Samba version 2.2.6
+Service     uid    gid    pid     machine
+-----------------------------------------
+spirit      jay    jay    7735    maya     (172.16.1.6) Sun Aug 12 12:17:14 2002
+spirit      jay    jay    7779    aztec    (172.16.1.2) Sun Aug 12 12:49:11 2002
+jay         jay    jay    7735    maya     (172.16.1.6) Sun Aug 12 12:56:19 2002
+
+Locked files:
+Pid    DenyMode   R/W        Oplock     Name
+--------------------------------------------------
+7735   DENY_WRITE RDONLY     NONE       /u/RegClean.exe   Sun Aug 12 13:01:22 2002
+
+Share mode memory usage (bytes):
+   1048368(99%) free + 136(0%) used + 72(0%) overhead = 1048576(100%) total</pre></blockquote>
+
+<p>The Samba status from this output provides three sets of data, each
+divided into separate sections. The first section tells which systems
+have connected to the Samba server, identifying each client by its
+machine name (<tt class="literal">maya</tt> and <tt class="literal">aztec</tt>)
+and IP (Internet Protocol) address. The second section reports the
+name and status of the files that are currently in use on a share on
+the server, including the read/write status and any locks on the
+files. Finally, Samba reports the amount of memory it has currently
+allocated to the shares that it administers, including the amount
+actively used by the shares plus additional overhead. (Note that this
+is not the same as the total amount of memory that the
+<em class="emphasis">smbd</em> or <em class="emphasis">nmbd</em> processes are
+using.)</p>
+
+<p>Don't worry if you don't understand
+these statistics; they will become easier to understand as you move
+through the book.</p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-3"/>
+
+<h2 class="head1">Getting Familiar with an SMB Network</h2>
+
+<p><a name="INDEX-33"/>Now that you have had a brief tour of
+Samba, let's take some time to get familiar with
+Samba's adopted environment: an SMB network.
+Networking with SMB is significantly different from working with
+common TCP/IP protocols such as FTP and Telnet because there are
+several new concepts to learn and a lot of information to cover.
+First, we will discuss the basic concepts behind an SMB network,
+followed by some Microsoft implementations of it, and finally we will
+show you where a Samba server can and cannot fit into the picture.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-3.1"/>
+
+<h3 class="head2">Understanding NetBIOS</h3>
+
+<p>To begin, let's step back in time. In 1984, IBM
+authored a simple application programming interface (API) for
+networking its computers, called the <em class="firstterm">Network Basic
+Input/Output System
+</em>(<a name="INDEX-34"/>NetBIOS).
+The NetBIOS API provided a rudimentary design for an application to
+connect and share data with other computers.</p>
+
+<p>It's helpful to think of the NetBIOS API as
+networking extensions to the standard BIOS API calls. The BIOS
+contains low-level code for performing filesystem operations on the
+local computer. NetBIOS originally had to exchange instructions with
+computers across IBM PC or Token Ring networks. It therefore required
+a low-level transport protocol to carry its requests from one
+computer to the next.</p>
+
+<p>In late 1985, IBM released one such protocol, which it merged with
+the NetBIOS API to become the <em class="firstterm">NetBIOS Extended User
+Interface</em> (<em class="emphasis">NetBEUI</em> ).
+<a name="INDEX-35"/>NetBEUI was
+designed for small LANs, and it let each computer claim a name (up to
+15 characters) that wasn't already in use on the
+network. By a &quot;small LAN,&quot; we mean
+fewer than 255 nodes on the network&mdash;which was considered a
+generous number in 1985!</p>
+
+<p>The NetBEUI protocol was very popular with networking applications,
+including those running under Windows for Workgroups. Later,
+implementations of NetBIOS over Novell's IPX
+networking protocols also emerged, which competed with NetBEUI.
+However, the networking protocols of choice for the burgeoning
+Internet community were TCP/IP and UDP/IP, and implementing the
+NetBIOS APIs over those protocols soon became a necessity.</p>
+
+<p>Recall that TCP/IP uses numbers to represent computer addresses
+(192.168.220.100, for instance) while NetBIOS uses only names. This
+was a major issue when trying to mesh the two protocols together. In
+1987, the IETF published standardization documents, titled RFC 1001
+and 1002, that outlined how NetBIOS would work over a TCP/UDP
+network. This set of documents still governs each implementation that
+exists today, including those provided by Microsoft with its Windows
+operating systems, as well as the Samba suite.</p>
+
+<p>Since then, the standard that this document governs has become known
+as <em class="firstterm">NetBIOS over
+TCP/IP</em><a name="INDEX-36"/><a name="INDEX-37"/><a name="INDEX-38"/>, or NBT for short.<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a> </p>
+
+<p>The NBT standard (RFC 1001/1002)
+currently outlines a trio of services on a network:</p>
+
+<ul><li>
+<p>A name service</p>
+</li><li>
+<p>Two communication services:</p>
+<ul><li>
+<p>Datagrams</p>
+</li>
+
+<li>
+<p>Sessions</p>
+</li></ul>
+</li>
+</ul>
+
+<p>The <a name="INDEX-39"/>name
+service solves the name-to-address problem mentioned earlier; it
+allows each computer to declare a specific name on the network that
+can be translated to a machine-readable IP address, much like
+today's Domain Name System (DNS) on the Internet.
+The <a name="INDEX-40"/>datagram and <a name="INDEX-41"/>session services are both
+secondary communication protocols used to transmit data back and
+forth from NetBIOS computers across the network.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-3.2"/>
+
+<h3 class="head2">Getting a Name</h3>
+
+<p><a name="INDEX-42"/><a name="INDEX-43"/>In the NetBIOS world, when each
+computer comes online, it wants to claim a name for itself; this is
+called <em class="firstterm">name registration</em>. However, no two
+computers in the same workgroup should be able to claim the same
+name; this would cause endless confusion for any computer that wanted
+to communicate with either of them. There are two different
+approaches to ensuring that this doesn't happen:</p>
+
+<ul><li>
+<p>Use an <em class="firstterm"/>NBNS</em> to keep track of which hosts have
+registered a NetBIOS name.</p>
+</li><li>
+<p>Allow each computer on the network to defend its name in the event
+that another computer attempts to use it.</p>
+</li></ul>
+<p><a href="ch01.html#samba2-CHP-1-FIG-8">Figure 1-8</a> illustrates a (failed) name
+registration, with and without an NBNS.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-8"/><img src="figs/sam2_0108.gif"/></div><h4 class="head4">Figure 1-8. Broadcast versus NBNS name registration</h4>
+
+<p><a name="INDEX-44"/><a name="INDEX-45"/>As mentioned earlier,
+there must be a way to resolve a NetBIOS name to a specific IP
+address; this is known as <em class="firstterm">name resolution</em>.
+There are two different approaches with NBT here as well:</p>
+
+<ul><li>
+<p>Have each computer report back its IP address when it
+&quot;hears&quot; a broadcast request for its
+NetBIOS name.</p>
+</li><li>
+<p>Use an NBNS to help resolve NetBIOS names to IP addresses.</p>
+</li></ul>
+<p><a href="ch01.html#samba2-CHP-1-FIG-9">Figure 1-9</a> illustrates the two types of name
+resolution.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-9"/><img src="figs/sam2_0109.gif"/></div><h4 class="head4">Figure 1-9. Broadcast versus NBNS name resolution</h4>
+
+<p>As you might expect, having an NBNS on your network can help out
+tremendously. To see exactly why, let's look at the
+broadcast method.</p>
+
+<p>Here, when a client computer boots, it will
+<a name="INDEX-46"/>broadcast a
+message declaring that it wishes to register a specified NetBIOS name
+as its own. If nobody objects to the use of the name, it keeps the
+name. On the other hand, if another computer on the local subnet is
+currently using the requested name, it will send a message back to
+the requesting client that the name is already taken. This is known
+as <em class="firstterm">defending</em><a name="INDEX-47"/><a name="INDEX-48"/> the hostname. This type of system
+comes in handy when one client has unexpectedly dropped off the
+network&mdash;another can take its name unchallenged&mdash;but it
+does incur an inordinate amount of traffic on the network for
+something as simple as name registration.</p>
+
+<p>With an NBNS, the same thing occurs, except the communication is
+confined to the requesting computer and the NBNS. No broadcasting
+occurs when the computer wishes to register the name; the
+registration message is simply sent directly from the client to the
+NBNS, and the NBNS replies regardless of whether the name is already
+taken. This is known as <em class="firstterm">point-to-point
+communication</em><a name="INDEX-49"/>, and it is often beneficial on
+networks with more than one subnet. This is because routers are
+generally configured to block incoming packets that are broadcast to
+all computers in the subnet.</p>
+
+<p>The same principles apply to name resolution. Without an NBNS,
+NetBIOS name resolution would also be done with a broadcast
+mechanism. All request packets would be sent to each computer in the
+network, with the hope that one computer that might be affected will
+respond directly back to the computer that asked. Using an NBNS and
+point-to-point communication for this purpose is far less taxing on
+the network than flooding the network with broadcasts for every
+name-resolution request.</p>
+
+<p>It can be argued that broadcast packets do not cause significant
+problems in modern, high-bandwidth networks of hosts with fast CPUs,
+if only a small number of hosts are on the network, or the demand for
+bandwidth is low. There are certainly cases where this is true;
+however, our advice throughout this book is to avoid relying on
+broadcasts as much as possible. This is a good rule to follow for
+large, busy networks, and if you follow our advice when configuring a
+small network, your network will be able to grow without encountering
+problems later on that might be difficult to diagnose. <a name="INDEX-50"/><a name="INDEX-51"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-3.3"/>
+
+<h3 class="head2">Node Types</h3>
+
+<p><a name="INDEX-52"/><a name="INDEX-53"/>How can you tell what strategy each
+client on your network will use when performing name registration and
+resolution? Each computer on an NBT network earns one of the
+following designations, depending on how it handles name registration
+and resolution: <a name="INDEX-54"/><a name="INDEX-55"/><a name="INDEX-56"/><a name="INDEX-57"/>b-node, p-node, m-node, and h-node. The
+behaviors of each type of node are summarized in <a href="ch01.html#samba2-CHP-1-TABLE-1">Table 1-1</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-1"/><h4 class="head4">Table 1-1. NetBIOS node types</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Role</p>
+</th>
+<th>
+<p>Value</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>b-node</p>
+</td>
+<td>
+<p>Uses broadcast registration and resolution only.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>p-node</p>
+</td>
+<td>
+<p>Uses point-to-point registration and resolution only.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>m-node (mixed)</p>
+</td>
+<td>
+<p>Uses broadcast for registration. If successful, it notifies the NBNS
+of the result. Uses broadcast for resolution; uses the NBNS if
+broadcast is unsuccessful.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>h-node (hybrid)</p>
+</td>
+<td>
+<p>Uses the NBNS for registration and resolution; uses broadcast if the
+NBNS is unresponsive or inoperative.</p>
+</td>
+</tr>
+
+</table>
+
+<p>In the case of Windows clients, you will usually find them listed as
+h-nodes or hybrid nodes. The first three node types appear in RFC
+1001/1002, and h-nodes were invented later by Microsoft, as a more
+fault-tolerant method.</p>
+
+<p>You can find the node type of a Windows 95/98/Me computer by running
+the <em class="emphasis">winipcfg</em><a name="INDEX-58"/><a name="INDEX-59"/> command from the Start
+&rarr; Run dialog (or from an MS-DOS prompt) and clicking
+the More Info&gt;&gt; button. On Windows NT/2000/XP, you can use the
+<tt class="literal">ipconfig</tt><a name="INDEX-60"/><a name="INDEX-61"/><a name="INDEX-62"/><a name="INDEX-63"/>
+<tt class="literal">/all</tt> command in a command-prompt window. In either
+case, search for the line that says <tt class="literal">Node Type</tt>.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-3.4"/>
+
+<h3 class="head2">What's in a Name?</h3>
+
+<p>The names <a name="INDEX-64"/><a name="INDEX-65"/>NetBIOS uses are quite different
+from the DNS hostnames you might be familiar with. First, NetBIOS
+names exist in a flat namespace. In other words, there are no
+hierarchical levels, such as in <tt class="literal">oreilly.com</tt> (two
+levels) or <em class="emphasis">ftp</em><em class="emphasis">.samba.org</em> (three
+levels). NetBIOS names consist of a single unique string such as
+<tt class="literal">navaho</tt> or <tt class="literal">hopi</tt> within each
+workgroup or domain. Second, NetBIOS names are allowed to be only 15
+characters and can consist only of standard alphanumeric characters
+(a-z, A-Z, 0-9) and the following:</p>
+
+<blockquote><pre class="code">! @ # $ % ^ &amp; ( ) - ' { } . ~</pre></blockquote>
+
+<p>Although you are allowed to use a <a name="INDEX-66"/><a name="INDEX-67"/><a name="INDEX-68"/>period (.) in a NetBIOS name, we recommend
+against it because those names are not guaranteed to work in future
+versions of NBT.</p>
+
+<p>It's not a coincidence that all valid DNS names are
+also valid NetBIOS names. In fact, the unqualified DNS name for a
+Samba server is often reused as its NetBIOS name. For example, if you
+had a system with a hostname of <tt class="literal">mixtec.ora.com</tt> ,
+its NetBIOS name would likely be MIXTEC (followed by 9 spaces).</p>
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-3.4.1"/>
+
+<h3 class="head3">Resource names and types</h3>
+
+<p><a name="INDEX-69"/><a name="INDEX-70"/>With NetBIOS, a computer not
+only advertises its presence, but also tells others what types of
+services it offers. For example, <tt class="literal">mixtec</tt> can
+indicate that it's not just a workstation, but that
+it's also a file server and can receive Windows
+Messenger messages. This is done by adding a 16th byte to the end of
+the machine (resource) name, called the <em class="firstterm">resource
+type</em>, and registering the name multiple times, once for
+each service that it offers. See <a href="ch01.html#samba2-CHP-1-FIG-10">Figure 1-10</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-10"/><img src="figs/sam2_0110.gif"/></div><h4 class="head4">Figure 1-10. The structure of NetBIOS names</h4>
+
+<p>The 1-byte resource type indicates a unique service that the named
+computer provides. In this book, you will often see the resource type
+shown in angled brackets (&lt;&gt;) after the NetBIOS name, such as:</p>
+
+<blockquote><pre class="code">MIXTEC&lt;00&gt;</pre></blockquote>
+
+<p>You can see which names are registered for a particular NBT computer
+using the Windows command-line
+<em class="emphasis">nbtstat</em><a name="INDEX-71"/> utility.
+Because these services are unique (i.e., there cannot be more than
+one registered), you will see them listed as type UNIQUE in the
+output. For example, the following partial output describes the
+<tt class="literal">toltec</tt> server:</p>
+
+<blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>nbtstat -a toltec</b></tt>
+
+       NetBIOS Remote Machine Name Table
+   Name               Type         Status
+---------------------------------------------
+TOLTEC          &lt;00&gt;  UNIQUE      Registered
+TOLTEC          &lt;03&gt;  UNIQUE      Registered
+TOLTEC          &lt;20&gt;  UNIQUE      Registered
+...</pre></blockquote>
+
+<p>This says the server has registered the NetBIOS name
+<tt class="literal">toltec</tt> as a machine (computer) name, as a
+recipient of messages from the Windows Messenger service, and as a
+file server. Some possible attributes a name can have are listed in
+<a href="ch01.html#samba2-CHP-1-TABLE-2">Table 1-2</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-2"/><h4 class="head4">Table 1-2. NetBIOS unique resource types</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Named resource</p>
+</th>
+<th>
+<p>Hexadecimal byte value</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Standard Workstation Service</p>
+</td>
+<td>
+<p>00</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Messenger Service</p>
+</td>
+<td>
+<p>03</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>RAS Server Service</p>
+</td>
+<td>
+<p>06</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Domain Master Browser Service (associated with primary domain controller)</p>
+</td>
+<td>
+<p>1B</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Master Browser name</p>
+</td>
+<td>
+<p>1D</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>NetDDE Service</p>
+</td>
+<td>
+<p>1F</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Fileserver (including printer server)</p>
+</td>
+<td>
+<p>20</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>RAS Client Service</p>
+</td>
+<td>
+<p>21</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Network Monitor Agent</p>
+</td>
+<td>
+<p>BE</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Network Monitor Utility</p>
+</td>
+<td>
+<p>BF</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-3.4.2"/>
+
+<h3 class="head3">Group names and types</h3>
+
+<p>SMB also uses the concept of groups, with which computers can
+register themselves. Earlier we mentioned that the computers in our
+example belonged to a
+<em class="firstterm">workgroup</em><a name="INDEX-73"/>,
+which is a partition of computers on the same network. For example, a
+business might very easily have an ACCOUNTING and a SALES workgroup,
+each with different servers and printers. In the Windows world, a
+workgroup and an
+<a name="INDEX-74"/>SMB
+group are the same thing.</p>
+
+<p>Continuing our
+<em class="emphasis">nbtstat</em><a name="INDEX-75"/> example,
+the <tt class="literal">toltec</tt> Samba server is also a member of the
+METRAN workgroup (the GROUP attribute hex 00) and will participate in
+elections for the browse master (GROUP attribute 1E). Here is the
+remainder of the <em class="emphasis">nbtstat</em> output:</p>
+
+<blockquote><pre class="code">       NetBIOS Remote Machine Name Table
+   Name               Type         Status
+---------------------------------------------
+METRAN         &lt;00&gt;   GROUP       Registered
+METRAN         &lt;1E&gt;   GROUP       Registered
+..__MSBROWSE__.&lt;01&gt;   GROUP       Registered</pre></blockquote>
+
+<p>The possible group attributes a computer can have are illustrated in
+<a href="ch01.html#samba2-CHP-1-TABLE-3">Table 1-3</a>. More
+<a name="INDEX-76"/><a name="INDEX-77"/>information
+is available in <em class="emphasis">Windows NT in a Nutshell</em> by Eric
+<a name="INDEX-78"/>Pearce, also
+published by O'Reilly.</p>
+
+<a name="samba2-CHP-1-TABLE-3"/><h4 class="head4">Table 1-3. NetBIOS group resource types</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Named resource</p>
+</th>
+<th>
+<p>Hexadecimal byte value</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Standard Workstation group</p>
+</td>
+<td>
+<p>00</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Logon server</p>
+</td>
+<td>
+<p>1C</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Master Browser name</p>
+</td>
+<td>
+<p>1D</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Normal Group name (used in browser elections)</p>
+</td>
+<td>
+<p>1E</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Internet Group name (administrative)</p>
+</td>
+<td>
+<p>20</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">&lt;01&gt;&lt;02&gt;_ _MSBROWSE_ _&lt;02&gt;</tt></p>
+</td>
+<td>
+<p>01</p>
+</td>
+</tr>
+
+</table>
+
+<p>The final entry, <tt class="literal">_ _ MSBROWSE _ _</tt>
+<a name="INDEX-80"/>, is used to announce a group to other
+master browsers. The nonprinting characters in the name show up as
+dots in an <em class="emphasis">nbtstat</em> printout.
+Don't worry if you don't understand
+all of the resource or group types. Some of them you will not need
+with Samba, and others you will pick up as you move through the rest
+of the chapter. The important thing to remember here is the logistics
+of the naming mechanism.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-3.4.3"/>
+
+<h3 class="head3">Scope ID</h3>
+
+<p>In the dark ages of SMB networking before NetBIOS groups were
+introduced, you could use a very primitive method to isolate groups
+of computers from the rest of the network. Each SMB packet contains a
+field called the <em class="firstterm">scope
+ID</em><a name="INDEX-81"/><a name="INDEX-82"/>, with the idea being that
+systems on the network could be configured to accept only packets
+with a scope ID matching that of their configuration. This feature
+was hardly ever used and unfortunately lingers in modern
+implementations. Some of the utilities included in the Samba
+distribution allow the scope ID to be set. Setting the scope ID in a
+network is likely to cause problems, and we are mentioning scope ID
+only so that you will not be confused by it when you later encounter
+it in various places.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-3.5"/>
+
+<h3 class="head2">Datagrams and Sessions</h3>
+
+<p>At this point, let's digress to discuss the
+responsibility of NBT: to provide connection services between two
+NetBIOS computers.
+<a name="INDEX-83"/>NBT
+offers two services: the <em class="firstterm">session
+service</em><a name="INDEX-84"/> and the
+<em class="firstterm">datagram service</em><a name="INDEX-85"/>.
+Understanding how these two services work is not essential to using
+Samba, but it does give you an idea of how NBT works and how to
+troubleshoot Samba when it doesn't work.</p>
+
+<p>The datagram service has no stable connection between computers.
+Packets of data are simply sent or broadcast from one computer to
+another, without regard to the order in which they arrive at the
+destination, or even if they arrive at all. The use of datagrams
+requires less processing overhead than sessions, although the
+reliability of the connection can suffer. Datagrams, therefore, are
+used for quickly sending nonvital blocks of data to one or more
+computers. The datagram service communicates using the simple
+primitives shown in <a href="ch01.html#samba2-CHP-1-TABLE-4">Table 1-4</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-4"/><h4 class="head4">Table 1-4. Datagram primitives</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Primitive</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Send Datagram</p>
+</td>
+<td>
+<p>Send datagram packet to computer or groups of computers.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Send Broadcast Datagram</p>
+</td>
+<td>
+<p>Broadcast datagram to any computer waiting with a Receive Broadcast
+datagram.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Receive Datagram</p>
+</td>
+<td>
+<p>Receive a datagram from a computer.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Receive Broadcast Datagram</p>
+</td>
+<td>
+<p>Wait for a Broadcast datagram.</p>
+</td>
+</tr>
+
+</table>
+
+<p>The session service is more complex. Sessions are a communication
+method that, in theory, offers the ability to detect problematic or
+inoperable connections between two NetBIOS applications. It helps to
+think of an NBT session as being similar to a telephone call, an
+analogy that obviously influenced the design of the CIFS standard.</p>
+
+<p>Once the connection is made, it remains open throughout the duration
+of the conversation, each side knows who the caller and the called
+computer are, and each can communicate with the simple primitives
+shown in <a href="ch01.html#samba2-CHP-1-TABLE-5">Table 1-5</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-5"/><h4 class="head4">Table 1-5. Session primitives</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Primitive</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Call</p>
+</td>
+<td>
+<p>Initiate a session with a computer listening under a specified name.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Listen</p>
+</td>
+<td>
+<p>Wait for a call from a known caller or any caller.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Hang-up</p>
+</td>
+<td>
+<p>Exit a call.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Send</p>
+</td>
+<td>
+<p>Send data to the other computer.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Receive</p>
+</td>
+<td>
+<p>Receive data from the other computer.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Session Status</p>
+</td>
+<td>
+<p>Get information on requested sessions.</p>
+</td>
+</tr>
+
+</table>
+
+<p>Sessions are the backbone of resource sharing on an NBT network. They
+are typically used for establishing stable connections from client
+computers to disk or printer shares on a server. The client
+&quot;calls&quot; the server and starts
+trading information such as which files it wishes to open, which data
+it wishes to exchange, etc. These calls can last a long
+time&mdash;hours, even days&mdash;and all of this occurs within the
+context of a single connection. If there is an error, the session
+software (TCP) will retransmit until the data is received properly,
+unlike the &quot;punt-and-pray&quot; approach
+of the datagram service (UDP).</p>
+
+<p>In truth, while sessions are supposed to handle problematic
+communications, they sometimes don't. If the
+connection is interrupted, session information that is open between
+the two computers might become invalid. If that happens, the only way
+to regain the session information is for the same two computers to
+call each other again and start over.</p>
+
+<p>If you want more information on each service, we recommend you look
+at RFC 1001. However, there are two important things to remember
+here:</p>
+
+<ul><li>
+<p><a name="INDEX-88"/>Sessions always
+occur between two NetBIOS computers. If a session service is
+interrupted, the client is supposed to store sufficient state
+information for it to reestablish the connection. However, in
+practice, this often does not happen.</p>
+</li><li>
+<p><a name="INDEX-89"/>Datagrams can
+be broadcast to multiple computers, but they are unreliable. In other
+words, there is no way for the source to know that the datagrams it
+sent have indeed arrived at their destinations. <a name="INDEX-90"/></p>
+</li></ul>
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-4"/>
+
+<h2 class="head1">An Introduction to the SMB Protocol</h2>
+
+<p><a name="INDEX-91"/>Now
+we're going to cover some low-level technical
+details and explore the elementals of the SMB protocol. You probably
+don't need to know much about this to implement a
+simple Samba network, and therefore you might want to skip or skim
+over this section and go on to the next one
+(&quot;Windows Workgroups and Domains&quot;)
+on your first reading. However, assuming you are going to be
+responsible for long-term maintenance of a Samba network, it will
+help if you understand how it actually works. You will more easily be
+able to diagnose and correct any odd problems that pop up.</p>
+
+<p>At a high level, the SMB protocol suite is relatively simple. It
+includes commands for all the file and print operations that you
+might perform on a local disk or printer, such as:</p>
+
+<ul><li>
+<p>Opening and closing files</p>
+</li><li>
+<p>Creating and deleting files and directories</p>
+</li><li>
+<p>Reading and writing files</p>
+</li><li>
+<p>Searching for files</p>
+</li><li>
+<p>Queueing and dequeueing files in a print spool</p>
+</li></ul>
+<p>Each operation can be encoded into an SMB message and transmitted to
+and from a server. The original name
+&quot;SMB&quot; comes from the way in which
+the commands are formatted: they are versions of the standard DOS
+system-call data structures, or <em class="firstterm">Server Message
+Blocks</em>, redesigned for transmitting to another computer
+across a network.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.1"/>
+
+<h3 class="head2">SMB Format</h3>
+
+<p>Richard <a name="INDEX-92"/>Sharpe of the Samba team defines SMB as
+a <em class="firstterm">request-response</em> protocol.<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a> In effect,
+this means that a client sends an SMB request to a server and the
+server sends an SMB response back to the client. In only one rare
+circumstance does a server send a message that is not in response to
+a client.</p>
+
+<p>An <a name="INDEX-94"/>SMB message is not as complex as you
+might think. Let's take a closer look at the
+internal structure of such a message. It can be broken down into two
+parts: the <em class="firstterm">header</em>, which is a fixed size, and
+the <em class="firstterm">command string</em>, whose size can vary
+dramatically based on the contents of the message.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-4.1.1"/>
+
+<h3 class="head3">SMB header format</h3>
+
+<p><a href="ch01.html#samba2-CHP-1-TABLE-6">Table 1-6</a> shows the format of an
+<a name="INDEX-95"/>SMB header. The COM field identifies
+the command being performed. SMB commands are not required to use all
+the fields in the SMB header. For example, when a client first
+attempts to connect to a server, it does not yet have a tree
+identifier (TID) value&mdash;one is assigned after it successfully
+connects&mdash;so a null TID is placed in its header field. Other
+fields can be padded with zeros when not used.</p>
+
+<p>The <a name="INDEX-96"/>SMB header fields are listed in <a href="ch01.html#samba2-CHP-1-TABLE-6">Table 1-6</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-6"/><h4 class="head4">Table 1-6. SMB header fields</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Field</p>
+</th>
+<th>
+<p>Size (bytes)</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">0xFF 'SMB</tt>'</p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Protocol identifier</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">COM</tt></p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Command code, from 0x00 to 0xFF</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">RCLS</tt></p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Error class</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">REH</tt></p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Reserved</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ERR</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>Error code</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">REB</tt></p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Reserved</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">RES</tt></p>
+</td>
+<td>
+<p><tt class="literal">14</tt></p>
+</td>
+<td>
+<p>Reserved</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">TID</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>TID; a unique ID for a resource in use by the client</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">PID</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>Caller process ID</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">UID</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>User identifier</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">MID</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>Multiplex identifier; used to route requests inside a process</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-4.1.2"/>
+
+<h3 class="head3">SMB command format</h3>
+
+<p>Immediately after the header is a variable number of bytes that
+constitute an <a name="INDEX-97"/>SMB command or reply. Each command,
+such as Open File (COM field identifier: <tt class="literal">SMBopen</tt>)
+or Get Print Queue (<tt class="literal">SMBsplretq</tt> ), has its own set
+of parameters and data. Like the SMB header fields, not all of the
+command fields need to be filled, depending on the specific command.
+For example, the Get Server Attributes
+(<tt class="literal">SMBdskattr</tt>) command sets the WCT and BCC fields
+to zero. The fields of the command segment are shown in <a href="ch01.html#samba2-CHP-1-TABLE-7">Table 1-7</a>.</p>
+
+<a name="samba2-CHP-1-TABLE-7"/><h4 class="head4">Table 1-7. SMB command contents</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Field</p>
+</th>
+<th>
+<p>Size (bytes)</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">WCT</tt></p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Word count</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">VWV</tt></p>
+</td>
+<td>
+<p>Variable</p>
+</td>
+<td>
+<p>Parameter words (size given by WCT)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">BCC</tt></p>
+</td>
+<td>
+<p><tt class="literal">2</tt></p>
+</td>
+<td>
+<p>Parameter byte count</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">DATA</tt></p>
+</td>
+<td>
+<p>Variable</p>
+</td>
+<td>
+<p>Data (size given by BCC)</p>
+</td>
+</tr>
+
+</table>
+
+<p>Don't worry if you don't understand
+each field; they are not necessary for using Samba at an
+administrator level. However, they do come in handy when debugging
+system messages. We will show you some of the more common SMB
+messages that clients and servers send using a modified version of
+<em class="filename">tcpdump</em> later in this section. (If you prefer an
+<a name="INDEX-98"/><a name="INDEX-99"/>SMB sniffer with a graphical
+interface, try Ethereal, which uses the GTK libraries; see
+<a href="http://www.ethereal.com">http://www.ethereal.com</a> for more
+information on this tool.)</p>
+
+<a name="samba2-CHP-1-NOTE-84"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>For more information on each command in the
+<a name="INDEX-100"/>SMB protocol, see the
+<em class="citetitle">CIFS Technical
+Reference</em><a name="INDEX-101"/> at <a href="http://www.snia.org/tech_activities/CIFS">http://www.snia.org/tech_activities/CIFS</a>.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-4.1.3"/>
+
+<h3 class="head3">SMB variations</h3>
+
+<p>The SMB protocol has been extended with new commands several times
+since its inception. Each new version is backward-compatible with the
+previous versions, so it is possible for a LAN to have clients and
+servers concurrently running different versions of the SMB protocol.</p>
+
+<p><a href="ch01.html#samba2-CHP-1-TABLE-8">Table 1-8</a> outlines the major versions of the
+<a name="INDEX-102"/>SMB
+protocol. Within each &quot;dialect&quot; of
+SMB are many sub-versions that include commands supporting particular
+releases of major operating systems. The ID string in column 2 is
+used by clients and servers to determine in which level of the
+protocol they will speak to each other.</p>
+
+<a name="samba2-CHP-1-TABLE-8"/><h4 class="head4">Table 1-8. SMB protocol dialects</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Protocol name</p>
+</th>
+<th>
+<p>ID string</p>
+</th>
+<th>
+<p>Used by</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Core</p>
+</td>
+<td>
+<p><tt class="literal">PC NETWORK PROGRAM 1.0</tt></p>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-103"/>Core Plus</p>
+</td>
+<td>
+<p><tt class="literal">MICROSOFT NETWORKS 1.03</tt></p>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-104"/>LAN Manager 1.0</p>
+</td>
+<td>
+<p><tt class="literal">LANMAN1.0</tt></p>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+<p>LAN Manager 2.0</p>
+</td>
+<td>
+<p><tt class="literal">LM1.2X002</tt></p>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+<p>LAN Manager 2.1</p>
+</td>
+<td>
+<p><tt class="literal">LANMAN2.1</tt></p>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-105"/>NT LAN
+Manager 1.0</p>
+</td>
+<td>
+<p><tt class="literal">NT LM 0.12</tt></p>
+</td>
+<td>
+<p>Windows NT 4.0</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-106"/>Samba's NT LM 0.12</p>
+</td>
+<td>
+<p><tt class="literal">Samba</tt></p>
+</td>
+<td>
+<p>Samba</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-107"/><a name="INDEX-108"/>Common
+Internet File System</p>
+</td>
+<td>
+<p><tt class="literal">CIFS 1.0</tt></p>
+</td>
+<td>
+<p>Windows 2000/XP</p>
+</td>
+</tr>
+
+</table>
+
+<p>Samba implements the NT LM 0.12 specification for NT LAN Manager 1.0.
+It is backward-compatible with all the other SMB variants. The CIFS
+specification is, in reality, LAN Manager 0.12 with a few specific
+additions.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.2"/>
+
+<h3 class="head2">SMB Clients and Servers</h3>
+
+<p><a name="INDEX-109"/><a name="INDEX-110"/>As
+mentioned earlier, SMB is a client/server protocol. In the purest
+sense, this means that a client sends a request to a server, which
+acts on the request and returns a reply. However, the client/server
+roles can often be reversed, sometimes within the context of a single
+SMB session. For example, consider the two Windows 95/98/Me computers
+in <a href="ch01.html#samba2-CHP-1-FIG-11">Figure 1-11</a>. The computer named
+<tt class="literal">maya</tt> shares a printer to the network, and the
+computer named <tt class="literal">toltec</tt> shares a disk directory.
+<tt class="literal">maya</tt> is in the client role when accessing
+<tt class="literal">toltec</tt>'s network drive and in the
+server role when printing a job for <tt class="literal">toltec</tt>.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-11"/><img src="figs/sam2_0111.gif"/></div><h4 class="head4">Figure 1-11. Two computers that both have resources to share</h4>
+
+<p>This brings out an important point in Samba terminology:</p>
+
+<ul><li>
+<p>A <em class="firstterm">server</em> is a computer with a resource to
+share.</p>
+</li><li>
+<p>A <em class="firstterm">client</em> is a computer that wishes to use that
+resource.</p>
+</li><li>
+<p>A computer can be a client, a server, or both, or it can be neither
+at any given time.</p>
+</li></ul>
+<p>Microsoft Windows products have both the SMB client and server built
+into the operating system, and it is common to find Windows acting as
+a server, client, both, or neither at any given time in a production
+network. Although Samba has been developed primarily to function as a
+server, there are also ways that it and associated software can act
+as an SMB client. As with Windows, it is even possible to set up a
+Unix system to act as an SMB client and not as a server. See <a href="ch05.html">Chapter 5</a> for more details on this topic.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.3"/>
+
+<h3 class="head2">A Simple SMB Connection</h3>
+
+<p><a name="INDEX-111"/>The client and server must complete
+three steps to establish a connection to a resource:</p>
+
+<ol><li>
+<p>Establish a NetBIOS session.</p>
+</li><li>
+<p>Negotiate the protocol variant.</p>
+</li><li>
+<p>Set session parameters, and make a tree connection to a resource.</p>
+</li></ol>
+<p>We will examine each step through the eyes of a useful tool that we
+mentioned earlier: the modified
+<em class="filename">tcpdump</em><a name="INDEX-112"/> that is
+available from the Samba web site.</p>
+
+<a name="samba2-CHP-1-NOTE-85"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>You can download the tcpdump program at <a href="http://www.samba.org">http://www.samba.org</a> in the
+<em class="filename">samba/ftp/tcpdump-smb</em> directory; the latest
+version as of this writing is 3.4-10. Use this program as you would
+use the standard <em class="filename">tcpdump</em> application, but add
+the <tt class="literal">-s 1500</tt> switch to ensure that you get the
+whole packet and not just the first few bytes.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.4"/>
+
+<h3 class="head2">Establishing a NetBIOS Session</h3>
+
+<p><a name="INDEX-113"/>When a user first makes a request
+to access a network disk or send a print job to a remote printer,
+NetBIOS takes care of making a connection at the session layer. The
+result is a bidirectional channel between the client and server. The
+client and server need only two messages to establish this
+connection. This is shown in the following example session request
+and response, as captured by <em class="filename">tcpdump</em> .</p>
+
+<p>First, the client sends a request to open a session, and
+<em class="filename">tcpdump </em><a name="INDEX-114"/>reports:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Request
+Flags=0x81000044
+Destination=TOLTEC      NameType=0x20 (Server)
+Source=MAYA             NameType=0x00 (Workstation)</pre></blockquote>
+
+<p>Then the server responds, granting a session to the client:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Granted
+Flags=0x82000000</pre></blockquote>
+
+<p>At this point, there is an open channel between the client and server.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.5"/>
+
+<h3 class="head2">Negotiating the Protocol Variant</h3>
+
+<p>Next, the client sends a message to the server to negotiate an
+<a name="INDEX-115"/>SMB protocol. As mentioned
+earlier, the client sets its <a name="INDEX-116"/>tree identifier (TID) field to
+zero, because it does not yet know what TID to use. A <em class="emphasis">tree
+identifier</em> is a number that represents a connection to a
+share on a server.</p>
+
+<p>The command in the message is <tt class="literal">SMBnegprot</tt>, a
+request to negotiate a protocol variant that will be used for the
+entire session. Note that the client sends to the server a list of
+all the variants that it can speak, not vice versa:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Packet
+Flags=0x0
+Length=154
+
+SMB PACKET: SMBnegprot (REQUEST)
+SMB Command   =  0x72
+Error class   =  0x0
+Error code    =  0
+Flags1        =  0x0
+Flags2        =  0x0
+Tree ID       =  0
+Proc ID       =  5315
+UID           =  0
+MID           =  257
+Word Count    =  0
+Dialect=PC NETWORK PROGRAM 1.0
+Dialect=MICROSOFT NETWORKS 3.0
+Dialect=DOS LM1.2X002
+Dialect=DOS LANMAN2.1
+Dialect=Windows for Workgroups 3.1a
+Dialect=NT LM 0.12</pre></blockquote>
+
+<p>The server responds to the
+<tt class="literal">SMBnegprot</tt><a name="INDEX-117"/> request with an index (with counting
+starting at 0) into the list of variants that the client offered, or
+with the value 0xFF if none of the protocol variants is acceptable:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Packet
+Flags=0x0
+Length=84
+
+SMB PACKET: SMBnegprot (REPLY)
+SMB Command   =  0x72
+Error class   =  0x0
+Error code    =  0
+Flags1        =  0x80
+Flags2        =  0x1
+Tree ID       =  0
+Proc ID       =  5315
+UID           =  0
+MID           =  257
+Word Count    =  17
+NT1 Protocol
+DialectIndex=5
+[...]</pre></blockquote>
+
+<p>In this example, the server responds with the value 5, which
+indicates that the <tt class="literal">NT</tt> <tt class="literal">LM</tt>
+<tt class="literal">0.12</tt> dialect will be used for the remainder of the
+session.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-4.6"/>
+
+<h3 class="head2">Set Session and Login Parameters</h3>
+
+<p><a name="INDEX-118"/><a name="INDEX-119"/>The next step is to transmit session and
+login parameters for the session, which you do using the
+<a name="INDEX-120"/><tt class="literal">SMBSesssetupX</tt>
+command. The parameters include the following:</p>
+
+<ul><li>
+<p>The account name and password (if there is one)</p>
+</li><li>
+<p>The workgroup name</p>
+</li><li>
+<p>The maximum size of data that can be transferred</p>
+</li><li>
+<p>The number of pending requests that can be in the queue at a time</p>
+</li></ul>
+<p>The resulting output from <em class="filename">tcpdump </em>is:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Packet
+Flags=0x0
+Length=150
+
+SMB PACKET: SMBsesssetupX (REQUEST)
+SMB Command   =  0x73
+Error class   =  0x0
+Error code    =  0
+Flags1        =  0x10
+Flags2        =  0x0
+Tree ID       =  0
+Proc ID       =  5315
+UID           =  1
+MID           =  257
+Word Count    =  13
+Com2=0x75
+Res1=0x0
+Off2=120
+MaxBuffer=2920
+MaxMpx=50
+VcNumber=0
+SessionKey=0x1380
+CaseInsensitivePasswordLength=24
+CaseSensitivePasswordLength=0
+Res=0x0
+Capabilities=0x1
+Pass1&amp;Pass2&amp;Account&amp;Domain&amp;OS&amp;LanMan=  
+  JAY METRAN Windows 4.0 Windows 4.0
+
+SMB PACKET: SMBtconX (REQUEST) (CHAINED)
+smbvwv[]=
+Com2=0xFF
+Off2=0
+Flags=0x2
+PassLen=1
+Passwd&amp;Path&amp;Device=
+smb_bcc=23
+smb_buf[]=\\TOLTEC\SPIRIT</pre></blockquote>
+
+<p>In this example, the <tt class="literal">SMBsesssetupX</tt> Session Setup
+command allows for an additional SMB command to be piggybacked onto
+it (indicated by the letter X at the end of the command name). The
+hexadecimal code of the second command is given in the
+<tt class="literal">Com2</tt> field. In this case the command is
+<tt class="literal">0x75</tt>, which is the <tt class="literal">SMBtconX</tt>
+<tt class="literal">(</tt>Tree Connect and X) command. The
+<tt class="literal">SMBtconX</tt><a name="INDEX-121"/> message looks for the name of the
+resource in the <em class="emphasis">smb_buf</em> buffer. In this example,
+<em class="emphasis">smb_buf</em> contains the string
+<tt class="literal">\\TOLTEC\SPIRIT</tt>, which is the full pathname to a
+shared directory on <tt class="literal">toltec</tt>. Using the
+&quot;and X&quot; commands like this speeds
+up each transaction because the server doesn't have
+to wait on the client to make a second request.</p>
+
+<p>Note that the TID is still zero. Finally, the server returns a TID to
+the client, indicating that the user has been authorized access and
+that the resource is ready to be used:</p>
+
+<blockquote><pre class="code">&gt;&gt;&gt; NBT Packet
+NBT Session Packet
+Flags=0x0
+Length=85
+
+SMB PACKET: SMBsesssetupX (REPLY)
+SMB Command   =  0x73
+Error class   =  0x0
+Error code    =  0
+Flags1        =  0x80
+Flags2        =  0x1
+Tree ID       =  1
+Proc ID       =  5315
+UID           =  100
+MID           =  257
+Word Count    =  3
+Com2=0x75
+Off2=68
+Action=0x1
+[000] Unix Samba 2.2.6
+[010] METRAN
+
+SMB PACKET: SMBtconX (REPLY) (CHAINED)
+smbvwv[]=
+Com2=0xFF
+Off2=0
+smbbuf[]=
+ServiceType=A:</pre></blockquote>
+
+<p>The <em class="emphasis">ServiceType</em> field is set to
+&quot;A&quot; to indicate that this is a file
+service. Available service types are:</p>
+
+<ul><li>
+<p>&quot;A&quot; for a disk or file</p>
+</li><li>
+<p>&quot;LPT1&quot; for a spooled output</p>
+</li><li>
+<p>&quot;COMM&quot; for a direct-connect printer
+or modem</p>
+</li><li>
+<p>&quot;IPC&quot; for a named pipe</p>
+</li></ul>
+<p>Now that a TID has been assigned, the client can use it as a handle
+to perform any operation that it would use on a local disk drive. It
+can open files, read and write to them, delete them, create new
+files, search for filenames, and so on. <a name="INDEX-122"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-5"/>
+
+<h2 class="head1">Windows Workgroups and Domains</h2>
+
+<p>Up to now, we've covered basic SMB technology, which
+is all you would need if you had nothing more advanced than MS-DOS
+clients on your network. We do assume you want to support Windows
+clients, especially the more recent versions, so next
+we'll describe the enhancements Microsoft has added
+to SMB networking&mdash;namely, Windows for Workgroups and Windows
+domains.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-5.1"/>
+
+<h3 class="head2">Windows Workgroups</h3>
+
+<p><a name="INDEX-123"/><a name="INDEX-124"/>Windows
+Workgroups are very similar to the SMB groups already described. You
+need to know just a few additional things.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.1.1"/>
+
+<h3 class="head3">Browsing</h3>
+
+<p><a name="INDEX-125"/>Browsing
+is the process of finding the other computers and shared resources in
+the Windows network. Note that there is no connection with a World
+Wide Web browser, apart from the general idea of
+&quot;discovering what's
+there.&quot; On the other hand, browsing the Windows
+network is like the Web in that what's out there can
+change without warning.</p>
+
+<p>Before browsing existed, users had to know the name of the computer
+they wanted to connect to on the network and then manually enter a
+UNC such as the following into an application or file manager to
+access resources:</p>
+
+<blockquote><pre class="code">\\toltec\spirit\</pre></blockquote>
+
+<p>Browsing is much more convenient, making it possible to examine the
+contents of a network by using the point-and-click GUI interface of
+the Network Neighborhood (or My Network Places<a name="FNPTR-5"/><a href="#FOOTNOTE-5">[5]</a>) on a Windows client.</p>
+
+<p>You will encounter two types of browsing in an SMB network:</p>
+
+<ul><li>
+<p><a name="INDEX-129"/>Browsing a list
+of computers and shared resources</p>
+</li><li>
+<p><a name="INDEX-130"/>Browsing the shared resource
+of a specific computer</p>
+</li></ul>
+<p>Let's look at the first one. On each LAN (or subnet)
+with a Windows workgroup or domain, one computer has the
+responsibility of maintaining a list of the computers that are
+currently accessible through the network. This computer is called the
+<em class="firstterm">local master
+browser</em><a name="INDEX-131"/><a name="INDEX-132"/>, and the list that it maintains is
+called the <em class="firstterm">browse
+list</em><a name="INDEX-133"/>. Computers on a subnet use the browse
+list to cut down on the amount of network traffic generated while
+browsing. Instead of each computer dynamically polling to determine a
+list of the currently available computers, the computer can simply
+query the local master browser to obtain a complete, up-to-date list.</p>
+
+<p>To browse the resources on a computer, a user must connect to the
+specific computer; this information cannot be obtained from the
+browse list. Browsing the list of resources on a computer can be done
+by double-clicking the computer's icon when it is
+presented in the Network Neighborhood. As you saw at the opening of
+the chapter, the computer will respond with a list of shared
+resources that can be accessed after the user is successfully
+authenticated.</p>
+
+<p>Each server on a Windows workgroup is required to announce its
+presence to the local master browser after it has registered a
+NetBIOS name, and (theoretically) announce that it is leaving the
+workgroup when it is shut down. It is the local master
+browser's responsibility to record what the servers
+have announced.</p>
+<a name="samba2-CHP-1-NOTE-86"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>The Windows <a name="INDEX-134"/>Network Neighborhood can behave
+oddly: until you select a particular computer to browse, the Network
+Neighborhood window might contain data that is not up-to-date. That
+means the Network Neighborhood window can be showing computers that
+have crashed or can be missing computers that
+haven't been noticed yet. Put succinctly, once
+you've selected a server and connected to it, you
+can be a lot more confident that the shares and printers really exist
+on the network.</p>
+</blockquote>
+
+<p>Unlike the roles you've seen earlier, almost any
+Windows system (including Windows for Workgroups and Windows 95/98/Me
+or NT/2000/XP) can act as a local master browser. The local master
+browser can have one or more
+<em class="firstterm"/><a name="INDEX-135"/><a name="INDEX-136"/>backup 
+browsers</em> on the local subnet
+that will take over in the event that the local master browser fails
+or becomes inaccessible. To ensure fluid operation, the local backup
+browsers will frequently synchronize their browse list with the local
+master browser.</p>
+
+<p>Here is how to calculate the minimum number of backup browsers that
+will be allocated on a workgroup:</p>
+
+<ul><li>
+<p>If up to 32 Windows NT/2000/XP workstations are on the network, or up
+to 16 Windows 95/98/Me computers are on the network, the local master
+browser allocates one backup browser in addition to the local master
+browser.</p>
+</li><li>
+<p>If the number of Windows NT/2000/XP workstations falls between 33 and
+64, or the number of Windows 95/98/Me workstations falls between 17
+and 32, the local master browser allocates two backup browsers.</p>
+</li><li>
+<p>For each group of 32 NT/2000/XP workstations or 16 Windows 95/98/Me
+computers beyond this, the local master browser allocates another
+backup browser.</p>
+</li></ul>
+<p>There is currently no upper limit on the number of backup browsers
+that can be allocated by the local master browser.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.1.2"/>
+
+<h3 class="head3">Browsing elections</h3>
+
+<p><a name="INDEX-137"/>Browsing
+is a critical aspect of any Windows workgroup. However, not
+everything runs perfectly on any network. For example,
+let's say that a computer running Windows on the
+desk of a small company's CEO is the local master
+browser&mdash;that is, until he switches it off while plugging in his
+massage chair. At this point the Windows NT Workstation in the spare
+parts department might agree to take over the job. However, that
+computer is currently running a large, poorly written program that
+has brought its processor to its knees. The moral: browsing has to be
+very tolerant of servers coming and going. Because nearly every
+Windows system can serve as a browser, there has to be a way of
+deciding at any time who will take on the job. This decision-making
+process is called an <em class="firstterm">election</em>.</p>
+
+<p>An election algorithm is built into nearly all Windows operating
+systems such that they can each agree who is going to be a local
+master browser and who will be local backup browsers. An election can
+be forced at any time. For example, let's assume
+that the CEO has finished his massage and reboots his server. As the
+server comes online, it will announce its presence, and an election
+will take place to see if the PC in the spare parts department should
+still be the master browser.</p>
+
+<p>When an election is performed, each computer broadcasts information
+about itself via datagrams. This information includes the following:</p>
+
+<ul><li>
+<p>The version of the election protocol used</p>
+</li><li>
+<p>The operating system on the computer</p>
+</li><li>
+<p>The amount of time the client has been on the network</p>
+</li><li>
+<p>The hostname of the client</p>
+</li></ul>
+<p>These values determine which operating system has seniority and will
+fulfill the role of the local master browser. (<a href="ch07.html">Chapter 7</a> describes the election process in more
+detail.) The architecture developed to achieve this is not elegant
+and has built-in security problems. While a browsing domain can be
+integrated with domain security, the election algorithm does not take
+into consideration which computers become browsers. Thus it is
+possible for any computer running a browser service to register
+itself as participating in the browsing election and (after winning)
+being able to change the browse list. Nevertheless, browsing is a key
+feature of Windows networking, and backward-compatibility
+requirements will ensure that it is in use for years to come.
+<a name="INDEX-138"/></p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.1.3"/>
+
+<h3 class="head3">Windows 95/98/Me authentication</h3>
+
+<p>Three types of passwords arise when
+<a name="INDEX-139"/><a name="INDEX-140"/>Windows
+95/98/Me is operating in a Windows workgroup:</p>
+
+<ul><li>
+<p>A Windows password</p>
+</li><li>
+<p>A Windows Networking password</p>
+</li><li>
+<p>A password for each shared resource that has been assigned password
+protection</p>
+</li></ul>
+<p>The Windows <a name="INDEX-141"/>password functions in a manner
+that might be a source of confusion for Unix system administrators.
+It is not there to prevent unauthorized users from using the
+computer. (If you don't believe that, try clicking
+the Cancel button on the password dialog box and see what happens!)
+Instead, the Windows password is used to gain access to a file that
+contains the Windows Networking and network resource passwords. There
+is one such file per registered user of the system, and they can be
+found in the <em class="filename">C:\Windows</em> directory with a name
+composed of the user's account name, followed by a
+<em class="filename">.pwl</em><a name="INDEX-142"/><a name="INDEX-143"/><a name="INDEX-144"/> extension. For example, if the
+user's account name is
+&quot;sarah,&quot; the file will be
+<em class="filename">C:\Windows\sarah.pwl</em>. This file is encrypted
+using the Windows password as the encryption key.</p>
+
+<a name="samba2-CHP-1-NOTE-87"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>As a security measure, you might want to check for junk
+<em class="filename">.pwl</em> files on Windows 95/98/Me clients, which
+might have been created by mistakes users made while attempting to
+log on. A <em class="filename">.pwl</em> file is easily cracked and can
+contain valid passwords for Samba accounts and network shares.</p>
+</blockquote>
+
+<p>The first time the network is accessed, Windows attempts to use the
+Windows password as the Windows Networking password. If this is
+successful, the user will not be prompted for two separate passwords,
+and subsequent logins to the Windows system will automatically result
+in logging on to the Windows network as well, making things much
+simpler for the user.</p>
+
+<p>Shared network resources in the workgroup can also have passwords
+assigned to them to limit their accessibility. The first time a user
+attempts to access the resource, she is asked for its password, and a
+checkbox in the password dialog box gives the user the option to add
+the password to her password list. This is the default; if it is
+accepted, Windows will store the password in the
+user's <em class="filename">.pwl</em> file, and all
+further authentication to the resource will be handled automatically
+by Windows.</p>
+
+<p>Samba's approach to workgroup authentication is a
+little different, which is a result of blending the Windows workgroup
+model with that of the Unix host upon which Samba runs. This will be
+discussed further in <a href="ch09.html">Chapter 9</a>. <a name="INDEX-145"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-5.2"/>
+
+<h3 class="head2">Windows NT Domains</h3>
+
+<p><a name="INDEX-146"/>The
+peer-to-peer networking model of
+<a name="INDEX-147"/>workgroups functions fairly well as long as
+the number of computers on the network is small and there is a
+close-knit community of users. However, in larger networks the
+simplicity of workgroups becomes a limiting factor. Workgroups offer
+only the most basic level of security, and because each resource can
+have its own password, it is inconvenient (to say the least) for
+users to remember the password for each resource in a large network.
+Even if that were not a problem, many people find it frustrating to
+have to interrupt their creative workflow to enter a shared password
+into a dialog box every time another network resource is accessed.</p>
+
+<p>To support the needs of larger networks, such as those found in
+departmental computing environments, Microsoft introduced domains
+with Windows NT 3.51. A <em class="firstterm">Windows NT domain</em> is
+essentially a workgroup of SMB computers that has one addition: a
+server acting as a <em class="firstterm">domain
+controller</em><a name="INDEX-148"/> (see <a href="ch01.html#samba2-CHP-1-FIG-12">Figure 1-12</a>).</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-12"/><img src="figs/sam2_0112.gif"/></div><h4 class="head4">Figure 1-12. A simple Windows domain</h4>
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.2.1"/>
+
+<h3 class="head3">Domain controllers</h3>
+
+<p>A domain controller in a Windows NT domain functions much like a
+<a name="INDEX-149"/><a name="INDEX-150"/>Network
+Information Service (NIS) server in a Unix network, maintaining a
+domain-wide database of user and group information, as well as
+performing related services. The responsibilities of a domain
+controller are mainly centered around security, including
+<em class="firstterm">authentication</em><a name="INDEX-151"/>,
+the process of granting or denying a user access to the resources of
+the domain. This is typically done through the use of a username and
+password. The service that maintains the database on the domain
+controllers is called the <a name="INDEX-152"/><a name="INDEX-153"/>Security Account Manager (SAM).</p>
+
+<p>The <a name="INDEX-154"/>Windows NT security model revolves
+around <em class="firstterm">security
+identifiers</em><a name="INDEX-155"/><a name="INDEX-156"/> (SIDs) and <em class="firstterm">access
+control lists</em><a name="INDEX-157"/><a name="INDEX-158"/>
+(ACLs). Security identifiers are used to represent objects in the
+domain, which include (but are not limited to) users, groups,
+computers, and processes. SIDs are commonly written in ASCII form as
+hyphen-separated fields, like this:</p>
+
+<blockquote><pre class="code">S-1-5-21-1638239387-7675610646-9254035128-545</pre></blockquote>
+
+<p>The part of the SID starting with the
+&quot;S&quot; and leading up to the rightmost
+hyphen identifies a domain. The number after the rightmost hyphen is
+called a <a name="INDEX-159"/>relative identifier (RID) and is a unique
+number within the domain that identifies the user, group, computer,
+or other object. The RID is the analog of a <a name="INDEX-160"/>user ID (UID) or
+<a name="INDEX-161"/>group ID
+(GID) on a Unix system or within an NIS domain.</p>
+
+<p>ACLs supply the same function as
+&quot;rwx&quot;
+<a name="INDEX-162"/><a name="INDEX-163"/><a name="INDEX-164"/><a name="INDEX-165"/><a name="INDEX-166"/>file permissions that are common in Unix
+systems. However, ACLs are more versatile. Unix file permissions only
+set permissions for the owner and group to which the file belongs,
+and &quot;other,&quot; meaning everyone else.
+Windows NT/2000/XP ACLs allow permissions to be set individually for
+any number of arbitrary users and/or groups. ACLs are made up of one
+or more <em class="firstterm">access control
+entries</em><a name="INDEX-167"/> (ACEs), each of which contains an SID
+and the access rights associated with it.</p>
+
+<p>ACL support has been added as a standard feature for some Unix
+variants and is available as an add-on for others. Samba supports
+mappings between Windows and Unix ACLs, and this will be covered in
+<a href="ch08.html">Chapter 8</a>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.2.2"/>
+
+<h3 class="head3">Primary and backup domain controllers</h3>
+
+<p>You've already read about master and backup
+browsers. Domain controllers are similar in that a domain has a
+<em class="firstterm">primary domain
+controller</em><a name="INDEX-168"/><a name="INDEX-169"/><a name="INDEX-170"/> (PDC) and can have
+one or more <em class="firstterm">backup domain
+controllers</em><a name="INDEX-171"/> (BDCs) as well. If the PDC fails or
+becomes inaccessible, its duties are automatically taken over by one
+of the BDCs. BDCs frequently synchronize their SAM data with the PDC
+so if the need arises, any one of them can immediately begin
+performing domain-controller services without impacting the clients.
+However, note that BDCs have read-only copies of the SAM database;
+they can update their data only by synchronizing with a PDC. A server
+in a Windows domain can use the SAM of any PDC or BDC to authenticate
+a user who attempts to access its resources and log on to the domain.</p>
+
+<p>All recent versions of Windows can log on to a domain as clients to
+access the resources of the domain servers. The systems that are
+considered members of the domain are a more exclusive class, composed
+of the PDC and BDCs, as well as domain member servers, which are
+systems that have joined a domain as members, and are known to the
+domain controllers by having a computer account in the SAM database.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.2.3"/>
+
+<h3 class="head3">Authentication</h3>
+
+<p><a name="INDEX-172"/>When
+a user logs on to a Windows domain by typing in a username and
+password, a secure challenge and response protocol is invoked between
+the client computer and a domain controller to verify that the
+username and password are valid. Then the domain controller sends a
+SID back to the client, which uses it to create a
+<a name="INDEX-173"/>Security Access Token (SAT) that is valid
+only for that system, to be used for further authentication. This
+access token has information about the user coded into it, including
+the username, the group, and the rights the user has within the
+domain. At this point, the user is logged on to the domain.</p>
+
+<p>Subsequently, when the client attempts to access a shared resource
+within the domain, the client system enters into a secure challenge
+and response exchange with the server of the resource. The server
+then enters into another secure challenge and response conversation
+with a domain controller to check that the client is valid. (What
+actually happens is that the server uses information it gets from the
+client to pretend to be the client and authenticate itself with the
+domain controller. If the domain controller validates the
+credentials, it sends an SID back to the server, which uses the SID
+to create its own SAT for the client to enable access to its local
+resources on the client's behalf.) At this point,
+the client is authenticated for resources on the server and is
+allowed to access them. The server then uses the SID in the access
+token to determine what permissions the client has to use and modify
+the requested resource by comparing them to entries in the ACL of the
+resource.</p>
+
+<p>Although this method of authentication might seem overly complicated,
+it allows clients to authenticate without having plain-text passwords
+travel through the network, and it is much more difficult to crack
+than the relatively weak workgroup security we described earlier.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.2.4"/>
+
+<h3 class="head3">Name service with WINS and DNS</h3>
+
+<p>The <a name="INDEX-174"/><a name="INDEX-175"/>Windows
+Internet Name Service (WINS) is Microsoft's
+implementation of a NetBIOS name server (NBNS). As such, WINS
+inherits much of NetBIOS's characteristics. First,
+WINS is flat; you can have only simple machine names such as
+<tt class="literal">inca</tt>, <tt class="literal">mixtec</tt>, or
+<tt class="literal">navaho</tt>, and workgroups such as PERU, MEXICO, or
+USA. In addition, WINS is dynamic: when a client first comes online,
+it is required to report its hostname, its address, and its workgroup
+to the local WINS server. This WINS server will retain the
+information so long as the client periodically refreshes its WINS
+registration, which indicates that it's still
+connected to the network. Note that WINS servers are not workgroup-
+or domain-specific; they can contain information for multiple domains
+and/or workgroups, which might exist on more than one subnet.</p>
+
+<p>Multiple <a name="INDEX-176"/>WINS
+servers can be set to synchronize with each other. This allows
+entries for computers that come online and go offline in the network
+to propagate from one WINS server to another. While in theory this
+seems efficient, it can quickly become cumbersome if several WINS
+servers are covering a network. Because WINS services can cross
+multiple subnets (you'll either hardcode the address
+of a WINS server in each of your clients or obtain it via DHCP), it
+is often more efficient to have each Windows client, regardless of
+the number of Windows domains, point themselves to the same WINS
+server. That way, only one authoritative WINS server will have the
+correct information, instead of several WINS servers continually
+struggling to synchronize themselves with the most recent changes.</p>
+
+<p>The currently active WINS server is known as the <em class="firstterm">primary
+WINS server</em><a name="INDEX-177"/><a name="INDEX-178"/>. You can also install a secondary WINS
+server, which will take over if the primary WINS server fails or
+becomes inaccessible. Both the primary and any other WINS servers
+will synchronize their address databases on a periodic basis.</p>
+
+<p>In the Windows family of operating systems, only a server edition of
+Windows NT/2000 can act as a WINS server. Samba 2.2 can function as a
+primary WINS server, but cannot <a name="INDEX-179"/><a name="INDEX-180"/>synchronize
+its database with other WINS servers. It therefore cannot act as a
+secondary WINS server or as a primary WINS server for a Windows
+secondary WINS server.</p>
+
+<p>WINS handles name service by default, although Microsoft added DNS
+starting with Windows NT 4 Server. It is compatible with DNS that is
+standard on virtually every Unix system, and a Unix server (such as
+the Samba host) can also be used for DNS.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-1-SECT-5.2.5"/>
+
+<h3 class="head3">Trust relationships</h3>
+
+<p>One additional aspect of Windows NT domains not yet supported in
+Samba 2.2 is that it is possible to set up a <em class="emphasis">trust
+relationship</em><a name="INDEX-181"/><a name="INDEX-182"/><a name="INDEX-183"/> between domains, allowing clients
+within one domain to access the resources within another without the
+user having to go through additional authentication. The protocol
+that is followed is called <em class="emphasis">pass-through authentication</em>,
+<a name="INDEX-184"/><a name="INDEX-185"/>in which the
+user's credentials are passed from the client system
+in the first domain to the server in the second domain, which
+consults a domain controller in the first (trusted) domain to check
+that the user is valid before granting access to the resource.</p>
+
+<p>Note that in many aspects, the behaviors of a Windows workgroup and a
+Windows NT domain overlap. For example, the master and backup
+browsers in a domain are always the PDC and BDC, respectively.
+Let's update our Windows domain diagram to include
+both a local master and local backup browser. The result is shown in
+<a href="ch01.html#samba2-CHP-1-FIG-13">Figure 1-13</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-13"/><a name="INDEX-186"/><img src="figs/sam2_0113.gif"/></div><h4 class="head4">Figure 1-13. A Windows domain with a local master and local backup browser</h4>
+
+<p>The similarity between workgroups and NT domains is not accidental
+because the concept of Windows domains did not evolve until Windows
+NT 3.5 was introduced, and Windows domains were forced to remain
+backward-compatible with the workgroups present in Windows for
+Workgroups.</p>
+
+<p>Samba can function as a primary domain controller for Windows
+95/98/Me and Windows NT/2000/XP clients with the limitation that it
+can act as a PDC only, and not as a BDC.</p>
+
+<p>Samba can also function as a <em class="firstterm">domain member
+server</em><a name="INDEX-187"/><a name="INDEX-188"/>, meaning that it has a computer account
+in the PDC's account database and is therefore
+recognized as being part of the domain. A domain member server does
+not authenticate users logging on to the domain, but still handles
+security functions (such as file permissions) for domain users
+accessing its resources.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-5.3"/>
+
+<h3 class="head2">Active Directory Domains</h3>
+
+<p>Starting with Windows 2000, Microsoft has introduced
+<a name="INDEX-189"/><a name="INDEX-190"/>Active
+Directory, the next step beyond Windows NT domains. We
+won't go into much detail concerning Active
+Directory because it is a huge topic. <a name="INDEX-191"/>Samba 2.2 doesn't
+support Active Directory at all, and support in Samba 3.0 is limited
+to acting as a client. For now, be aware that with Active Directory,
+the authentication model is centered around
+<a name="INDEX-192"/>Lightweight Directory
+Access Protocol (LDAP), and name service is provided by DNS instead
+of WINS. Domains in Active Directory can be organized in a
+hierarchical tree structure, in which each domain controller operates
+as a peer, with no distinction between primary and backup controllers
+as in Windows NT domains.</p>
+
+<p>Windows 2000/XP systems can be set up as simple workgroup or Windows
+NT domain clients (which will function with Samba). The server
+editions of Windows 2000 can be set up to run Active Directory and
+support Windows NT domains for backward compatibility
+(<em class="firstterm">mixed mode</em>). In this case, Samba 2.2 works
+with Windows 2000 servers in the same way it works with Windows NT
+4.0 servers. When set up to operate in <em class="firstterm">native mode,
+</em><a name="INDEX-193"/>Windows 2000 servers support only
+Active Directory. Even so, <a name="INDEX-194"/>Samba 2.2 can operate as a server
+in a domain hosted by a native-mode Windows 2000 server, using the
+<a name="INDEX-195"/>Windows 2000 server's
+<em class="firstterm">PDC emulation mode</em>. However, it is not
+possible for Samba 2.2 or 3.0 to operate as a domain controller in a
+Windows 2000 Active Directory domain.</p>
+
+<p>If you want to know more about Active Directory, we encourage you to
+obtain a copy of the O'Reilly book,
+<em class="emphasis">Windows 2000 Active Directory</em>. <a name="INDEX-196"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-5.4"/>
+
+<h3 class="head2">Can a Windows Workgroup Span Multiple Subnets?</h3>
+
+<p><a name="INDEX-197"/><a name="INDEX-198"/>Yes, but most people who have
+done it have had their share of headaches. Spanning multiple subnets
+was not part of the initial design of Windows NT 3.5 or Windows for
+Workgroups. As a result, a Windows domain that spans two or more
+subnets is, in reality, the
+&quot;gluing&quot; together of two or more
+workgroups that share an identical name. The good news is that you
+can still use a PDC to control authentication across each subnet. The
+bad news is that things are not as simple with browsing.</p>
+
+<p>As mentioned previously, each subnet must have its own local master
+browser. When a Windows domain spans multiple subnets, a system
+administrator will have to assign one of the computers as the
+<em class="firstterm">domain master
+browser</em><a name="INDEX-199"/><a name="INDEX-200"/>. The domain master browser will keep a
+browse list for the entire Windows domain. This browse list is
+created by periodically synchronizing the browse lists of each local
+master browser with the browse list of the domain master browser.
+After the synchronization, the local master browser and the domain
+master browser should contain identical entries. See <a href="ch01.html#samba2-CHP-1-FIG-14">Figure 1-14</a> for an illustration.</p>
+
+<div class="figure"><a name="samba2-CHP-1-FIG-14"/><img src="figs/sam2_0114.gif"/></div><h4 class="head4">Figure 1-14. A workgroup that spans more than one subnet</h4>
+
+<p>Sound good? <a name="INDEX-201"/>Well, it's not quite
+nirvana for the following reasons:</p>
+
+<ul><li>
+<p>If it exists, a PDC always plays the role of the domain master
+browser. By Microsoft design, the two always share the NetBIOS
+resource type <tt class="literal">&lt;1B&gt;</tt> and (unfortunately)
+cannot be separated.</p>
+</li><li>
+<p>Windows 95/98/Me computers cannot become <em class="emphasis">or</em>
+<em class="emphasis">even contact</em> a domain master browser. This means
+that it is necessary to have at least one Windows NT/2000/XP system
+(or Samba server) on each subnet of a multisubnet workgroup.</p>
+</li></ul>
+<p>Each subnet's local master browser continues to
+maintain the browse list for its subnet, for which it becomes
+authoritative. So if a computer wants to see a list of servers within
+its own subnet, the local master browser of that subnet will be
+queried. If a computer wants to see a list of servers outside the
+subnet, it can still go only as far as the local master browser. This
+works because at appointed intervals, the authoritative browse list
+of a subnet's local master browser is synchronized
+with the domain master browser, which is synchronized with the local
+master browser of the other subnets in the domain. This is called
+<em class="firstterm">browse list propagation</em>.</p>
+
+<p>Samba can act as a domain master browser in a Windows NT domain, or
+it can act as a local master browser for a subnet, synchronizing its
+browse list with the domain master browser.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-6"/>
+
+<h2 class="head1">What's New in Samba 2.2?</h2>
+
+<p><a name="INDEX-202"/><a name="INDEX-203"/>In
+Version 2.2, Samba has more advanced support for Windows networking,
+including the ability to perform the more important tasks necessary
+for acting in a Windows NT domain. In addition, Samba 2.2 has some
+support for technologies that Microsoft introduced in Windows 2000,
+although the Samba team has saved Active Directory support for
+Version 3.0.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.1"/>
+
+<h3 class="head2">PDC Support for Windows 2000/XP Clients</h3>
+
+<p>Samba previously could act as a PDC to authenticate Windows 95/98/Me
+and Windows NT 4 systems. This functionality has been extended in
+Release 2.2 to include Windows 2000 and Windows XP. Thus, it is
+possible to have a Samba server supporting domain logons for a
+network of Windows clients, including the most recent releases from
+Microsoft. This can result in a very stable, high-performance, and
+more secure network, and gives you the added benefit of not having to
+purchase per-seat Windows CALs from Microsoft.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.2"/>
+
+<h3 class="head2">Microsoft Dfs Support</h3>
+
+<p><a name="INDEX-204"/>Microsoft Dfs allows shared resources that
+are dispersed among a number of servers in the network to be gathered
+together and appear to users as if they all exist in a single
+directory tree on one server. This method of organization makes life
+much simpler for users. Instead of having to browse around the
+network on a treasure hunt to locate the resource they want to use,
+they can go directly to the Dfs server and grab what they want. Samba
+2.2 offers support for serving Dfs, so a Windows server is no longer
+needed for this purpose.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.3"/>
+
+<h3 class="head2">Windows NT/2000/XP Printing Support</h3>
+
+<p>Windows NT/2000/XP has a different Remote Procedure Call (RPC)-based
+printer interface than Windows 95/98/Me does. In Samba 2.2, the
+Windows NT/2000/XP interface is supported. Along with this, the Samba
+team has been adding support for automatically downloading the
+printer driver from the Samba server while adding a new printer to a
+Windows client.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.4"/>
+
+<h3 class="head2">ACLs</h3>
+
+<p>Samba now supports
+<a name="INDEX-205"/>ACLs on its Unix host for Unix variants
+that support them. The list includes Solaris 2.6, 7, and 8, Irix,
+AIX, Linux (with either the ACL patch for the
+<a name="INDEX-206"/>ext2/ext3 filesystem from <a href="http://acl.bestbits.at">http://acl.bestbits.at</a> or when using the
+<a name="INDEX-207"/>XFS
+filesystem), and FreeBSD (Version 5.0 and later). When using ACL
+support, Samba translates between Unix ACLs and Windows NT/2000/XP
+ACLs, making the Samba host look and act more like a Windows
+NT/2000/XP server from the point of view of Windows clients.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.5"/>
+
+<h3 class="head2">Support for Windows Client Administration Tools</h3>
+
+<p>Windows comes with tools that can be used from a client to manage
+shared resources remotely on a Windows server. Samba 2.2 allows these
+tools to operate on shares on the Samba server as well.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.6"/>
+
+<h3 class="head2">Integration with Winbind</h3>
+
+<p><a name="INDEX-208"/>Winbind is a
+facility that allows users whose account information is stored in a
+Windows domain database to authenticate on a Unix system. The result
+is a unified logon environment, in which a user account can be kept
+on either the Unix system or a Windows NT/2000 domain controller.
+This greatly facilitates account management because administrators no
+longer need to keep the two systems synchronized, and it is possible
+for users whose accounts are held in a Windows domain to authenticate
+when accessing Samba shares.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.7"/>
+
+<h3 class="head2">Unix CIFS Extensions</h3>
+
+<p>The <a name="INDEX-209"/><a name="INDEX-210"/>Unix CIFS extensions were developed
+at Hewlett-Packard and introduced in Samba 2.2.4. They allow Samba
+servers to support Unix filesystem attributes, such as links and
+permissions, when sharing files with other Unix systems. This allows
+Samba to be used as an alternative to network file sharing (NFS) for
+Unix-to-Unix file sharing. An advantage of using Samba is that it
+authenticates individual users, whereas NFS authenticates only
+clients (based on their IP addresses, which is a poor security
+model). This gives Samba an edge in the area of security, along with
+its much greater configurability. See <a href="ch05.html">Chapter 5</a>
+for information on how to operate Unix systems as Samba clients.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-1-SECT-6.8"/>
+
+<h3 class="head2">And More...</h3>
+
+<p>As usual, the code has numerous improvements that do not show up at
+the administrative level in an immediate or obvious way. Samba now
+functions better on systems that employ <a name="INDEX-211"/>PAM
+(Pluggable Authentication Modules), and there is new support for
+profiling. Samba's support for oplocks has been
+strengthened, offering better integration with NFS server-terminated
+leases (currently on Irix and Linux only) and in the local filesystem
+with SMB locks mapped to POSIX locks (which is dependent on each Unix
+variant's implementation of POSIX locks). And of
+course there have been the usual bug fixes.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-7"/>
+
+<h2 class="head1">What's New in Samba 3.0?</h2>
+
+<p>The main distinguishing feature of <a name="INDEX-212"/><a name="INDEX-213"/>Samba 3.0
+is that it includes support for <a name="INDEX-214"/>Kerberos 5 authentication and
+<a name="INDEX-215"/>LDAP, which are
+required to act as clients in an Active Directory domain. Another
+feature that appeared in Samba 3.0 is support for Unicode, which
+greatly simplifies supporting international languages.</p>
+
+<p>In later Version 3 releases, the Samba team plans to develop support
+for
+<a name="INDEX-216"/>WINS
+replication, allowing Samba to act as a secondary WINS server or as a
+primary WINS server with Windows or Samba secondary WINS servers.
+Also planned are support for acting as a Windows NT BDC and support
+for Windows NT domain trust relationships.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-8"/>
+
+<h2 class="head1">What Can Samba Do?</h2>
+
+<p>Now let's wrap up by showing where Samba can help
+out and where it is limited. <a href="ch01.html#samba2-CHP-1-TABLE-9">Table 1-9</a> summarizes
+which roles Samba can and cannot play in a Windows NT or Active
+Directory domain or a Windows workgroup. Many of the Windows domain
+protocols are proprietary and have not been documented by Microsoft
+and therefore must be reverse-engineered by the Samba team before
+Samba can support them. As of Version 3.0, Samba cannot act as a
+backup in most roles and does not yet fully support Active Directory.</p>
+
+<a name="samba2-CHP-1-TABLE-9"/><h4 class="head4">Table 1-9. Samba roles (as of Version 3.0)</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Role</p>
+</th>
+<th>
+<p>Can perform?</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><a name="INDEX-217"/>File server</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Printer server</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Microsoft Dfs server</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Primary domain controller</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Backup domain controller</p>
+</td>
+<td>
+<p>No</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Active Directory domain controller</p>
+</td>
+<td>
+<p>No</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95/98/Me authentication</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT/2000/XP authentication</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Local master browser</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Local backup browser</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Domain master browser</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Primary WINS server</p>
+</td>
+<td>
+<p>Yes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Secondary WINS server</p>
+</td>
+<td>
+<p>No</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-9"/>
+
+<h2 class="head1">An Overview of the Samba Distribution</h2>
+
+<p><a name="INDEX-218"/>As mentioned earlier, Samba actually
+contains several programs that serve different but related purposes.
+These programs are documented more fully in <a href="appc.html">Appendix C</a>. For now, we will introduce each of them
+briefly and describe how they work together.</p>
+
+<p>The majority of the programs that come with Samba center on its two
+daemons. Let's take a refined look at the
+responsibilities of each daemon:</p>
+
+<dl>
+<dt><b><em class="emphasis">nmbd</em></b></dt>
+<dd>
+<p>The <em class="emphasis">nmbd</em><a name="INDEX-219"/> daemon is a simple name server that
+supplies WINS functionality. This daemon listens for name-server
+requests and provides the appropriate IP addresses when called upon.
+It also provides browse lists for the Network Neighborhood and
+participates in browsing elections.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbd</em></b></dt>
+<dd>
+<p>The <em class="emphasis">smbd</em><a name="INDEX-220"/> daemon manages the shared resources
+between the Samba server and its clients. It provides file, print,
+and browse services to <span class="acronym">SMB</span> clients across one or
+more networks and handles all notifications between the Samba server
+and the network clients. In addition, it is responsible for user
+authentication, resource locking, and data sharing through the
+<span class="acronym">SMB</span> protocol.</p>
+</dd>
+
+</dl>
+
+<p>New with Version 2.2, there is an additional daemon:</p>
+
+<dl>
+<dt><b><a name="INDEX-221"/><em class="emphasis">winbindd</em></b></dt>
+<dd>
+<p>This daemon is used along with the name service switch to get
+information on users and groups from a Windows NT server and allows
+Samba to authorize users through a Windows NT/2000 server.</p>
+</dd>
+
+</dl>
+
+<p>The Samba distribution also comes with a small set of Unix
+command-line tools:</p>
+
+<dl>
+<dt><b><em class="emphasis">findsmb</em><a name="INDEX-222"/></b></dt>
+<dd>
+<p>A program that searches the local network for computers that respond
+to SMB protocol and prints information on them.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">make_smbcodepage</em><a name="INDEX-223"/></b></dt>
+<dd>
+<p>A program used when working with Samba's
+internationalization features for telling Samba how to convert
+between upper- and lowercase in different character sets.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">make_unicodemap</em><a name="INDEX-224"/></b></dt>
+<dd>
+<p>Another internationalization program used with Samba for compiling
+Unicode map files that Samba uses to translate DOS codepages or Unix
+character sets into 16-bit unicode.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-225"/><em class="emphasis">net</em></b></dt>
+<dd>
+<p>A new program distributed with Samba 3.0 that can be used to perform
+remote administration of servers.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">nmblookup</em><a name="INDEX-226"/></b></dt>
+<dd>
+<p>A program that provides NBT name lookups to find a
+computer's IP address when given its machine name.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-227"/><em class="emphasis">pdbedit</em></b></dt>
+<dd>
+<p>A new program distributed with Samba 3.0 that is helpful for managing
+user accounts held in SAM databases.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">rpcclient</em><a name="INDEX-228"/></b></dt>
+<dd>
+<p>A program that can be used to run MS-RPC functions on Windows clients.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbcacls</em><a name="INDEX-229"/></b></dt>
+<dd>
+<p>A program that is used to set or show ACLs on Windows NT filesystems.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbclient</em><a name="INDEX-230"/></b></dt>
+<dd>
+<p>An <em class="emphasis">ftp</em>-like Unix client that can be used to connect to
+SMB shares and operate on them. The <em class="emphasis">smbclient</em>
+command is discussed in detail in <a href="ch05.html">Chapter 5</a>.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbcontrol</em><a name="INDEX-231"/></b></dt>
+<dd>
+<p>A simple administrative utility that sends messages to <em class="emphasis">nmbd</em>
+or <em class="emphasis">smbd</em>.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-232"/><em class="emphasis">smbgroupedit</em></b></dt>
+<dd>
+<p>A command that can be used to define mappings between Windows NT
+groups and Unix groups. It is new in Samba 3.0.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbmnt</em><a name="INDEX-233"/></b></dt>
+<dd>
+<p>A helper utility used along with <em class="emphasis">smbmount.</em></p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbmount</em><a name="INDEX-234"/></b></dt>
+<dd>
+<p>A program that mounts an smbfs filesystem, allowing remote SMB shares
+to be mounted in the filesystem of the Samba host.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbpasswd</em><a name="INDEX-235"/></b></dt>
+<dd>
+<p>A program that allows an administrator to change the passwords used
+by Samba.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbsh</em><a name="INDEX-236"/></b></dt>
+<dd>
+<p>A tool that functions like a command shell to allow access to a
+remote SMB filesystem and allow Unix utilities to operate on it. This
+command is covered in <a href="ch05.html">Chapter 5</a>.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbspool</em><a name="INDEX-237"/></b></dt>
+<dd>
+<p>A print-spooling program used to send files to remote printers that
+are shared on the SMB network.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbstatus</em><a name="INDEX-238"/></b></dt>
+<dd>
+<p>A program that reports the current network connections to the shares
+on a Samba server.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbtar</em><a name="INDEX-239"/></b></dt>
+<dd>
+<p>A program similar to the Unix <em class="filename">tar</em> command, for
+backing up data in SMB shares.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">smbumount</em><a name="INDEX-240"/></b></dt>
+<dd>
+<p>A program that works along with <em class="emphasis">smbmount</em> to unmount
+smbfs filesystems.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">testparm</em><a name="INDEX-241"/></b></dt>
+<dd>
+<p>A simple program for checking the Samba configuration file.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">testprns</em><a name="INDEX-242"/></b></dt>
+<dd>
+<p>A program that tests whether printers on the Samba host are
+recognized by the <em class="filename">smbd</em> daemon.</p>
+</dd>
+
+
+
+<dt><b><em class="emphasis">wbinfo</em><a name="INDEX-243"/></b></dt>
+<dd>
+<p>A utility used to query the <em class="filename">winbindd
+</em><a name="INDEX-244"/>daemon.</p>
+</dd>
+
+</dl>
+
+<p>Each major release of Samba goes through an exposure test before
+it's announced. In addition, it is quickly updated
+afterward if problems or unwanted side effects are found. The latest
+stable distribution as of this writing is Samba 2.2.6, and this book
+focuses mainly on the functionality supported in Samba 2.2.6, as
+opposed to older versions of Samba.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-1-SECT-10"/>
+
+<h2 class="head1">How Can I Get Samba?</h2>
+
+<p><a name="INDEX-245"/><a name="INDEX-246"/>Source
+and binary distributions of Samba are available from mirror sites
+across the Internet. The primary web site for Samba is located at
+<a href="http://www.samba.org/">http://www.samba.org/</a>. From there, you
+can select a mirror site that is geographically near you.</p>
+
+<p>Most Linux and many Unix vendors provide binary packages. These can
+be more convenient to install and maintain than the Samba
+team's source or binary packages, due to the
+vendor's efforts to supply a package that matches
+its specific products. <a name="INDEX-247"/></p>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> You
+can also right-click the shared resource in the Network Neighborhood
+and then select the Map Network Drive menu item.</p> <a name="FOOTNOTE-2"/> <p><a href="#FNPTR-2">[2]</a> Be
+warned that many end-user license agreements forbid installing a
+program on a network so that multiple clients can access it. Check
+the legal agreements that accompany the product to be absolutely
+sure.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> You
+might also see the abbreviation NetBT, which is common in Microsoft
+literature.</p> <a name="FOOTNOTE-4"/>
+<p><a href="#FNPTR-4">[4]</a> See
+<a href="http://www.samba.org/cifs/docs/what-is-smb.html">http://www.samba.org/cifs/docs/what-is-smb.html</a>
+for Richard's excellent summary of
+<a name="INDEX-93"/>SMB.</p> <a name="FOOTNOTE-5"/> <p><a href="#FNPTR-5">[5]</a> This
+was originally called <a name="INDEX-126"/><a name="INDEX-127"/><a name="INDEX-128"/>Network Neighborhood in Windows 95/98/NT,
+but Microsoft has changed the name to My Network Places in the more
+recent Windows Me/2000/XP. We will continue to call it Network
+Neighborhood, and if you're using a new version of
+Windows, be aware that My Network Places can act a little differently
+in some ways.</p> </blockquote>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/ch02.html b/docs/htmldocs/using_samba/ch02.html
new file mode 100644
index 0000000000..ecefb2fb7d
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch02.html
@@ -0,0 +1,1849 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 2. Installing Samba on a Unix System</h1>
+
+<p><a name="INDEX-1"/>Now
+that you know what Samba can do for you and your users,
+it's time to get your own network set up.
+Let's start with the installation of Samba. When
+dancing the samba, one learns by taking small steps.
+It's just the same when installing Samba; we need to
+teach it step by step. This chapter will help you start off on the
+right foot.</p>
+
+<p>For illustrative purposes, we will be installing the 2.2.6 version of
+the Samba server on a Linux system running Version 2.4 of the kernel.
+However, the installation steps are essentially the same for all the
+platforms Samba supports.</p>
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-1"/>
+
+<h2 class="head1">Bundled Versions</h2>
+
+<p><a name="INDEX-2"/><a name="INDEX-3"/>Samba is in such
+popular use that many Unix distributions come with it already
+installed. If you choose to use a bundled version of Samba, you can
+breeze through most of this chapter, but you'll be
+stuck with the Samba version and compile-time options your vendor
+selected for you. That version of Samba can't be any
+newer than the operating system release, so you're
+likely to be pretty far behind the latest developments. On the other
+hand, you can be fairly sure that a bundled version has been
+installed properly, and perhaps it will take only a few simple
+modifications to your <em class="emphasis">smb.conf</em> file for you to
+be off and running. Samba is mature enough that you probably
+don't need the latest release to meet your basic
+needs, so you might be perfectly happy running a bundled version.</p>
+
+<p>If you choose this option, be aware that your Samba files, including
+the very important
+<em class="emphasis">smb.conf</em>,<a name="INDEX-4"/> might be in different places
+than they would be if you were to install from a binary or source
+distribution. For example, with the Red Hat, Debian, and Mandrake
+Linux distributions, <em class="emphasis">smb.conf</em> and some other
+Samba-related files are in the <em class="emphasis">/etc/samba</em>
+directory.</p>
+
+<p>If Samba is already installed on your system, you can check to see
+what version you have by using the command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbd -V</b></tt>
+Version 2.2.6</pre></blockquote>
+
+<p>(If this doesn't work, it might be because
+<em class="emphasis">smbd</em> is not in your shell's
+search path. If you have the <em class="emphasis">locate</em> or
+<em class="emphasis">whereis</em> command in your Unix variant, you can
+use it to locate the <em class="emphasis">smbd</em> executable.)</p>
+
+<p>You might also be able to use a system-specific tool to query a
+software-package maintenance utility. On Red Hat Linux, you can use
+the <em class="emphasis">rpm</em><a name="INDEX-5"/> command to query the installed packages
+for Samba:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>rpm -qa | grep samba</b></tt>
+samba-client-2.0.8-1.7.1
+samba-2.0.8-1.7.1
+samba-common-2.0.8-1.7.1</pre></blockquote>
+
+<p>This shows we have Samba 2.0.8, divided into three Red Hat Package
+Manager (RPM) packages, bundled with Red Hat 7.1. If your version of
+Samba is old, you might at the very least want to check with your
+vendor for an update.</p>
+
+<p>Otherwise, if you're sure you are going to install
+from a binary or source distribution, you can remove the RPM packages
+as follows:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>rpm -e samba</b></tt>
+# <tt class="userinput"><b>rpm -e samba-client</b></tt>
+# <tt class="userinput"><b>rpm -e samba-common</b></tt></pre></blockquote>
+
+<p>If you are not using Red Hat Linux, consult your
+system's documentation to find the method that works
+for you.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-1.1"/>
+
+<h3 class="head2">Binary or Source?</h3>
+
+<p><a name="INDEX-6"/>Precompiled
+&quot;binary&quot; packages are also
+available for a large number of Unix platforms. These packages
+contain binaries for each Samba executable, as well as the standard
+Samba documentation. Note that while installing a binary distribution
+can save you a fair amount of time and trouble, you should keep a
+couple of issues in mind when deciding whether to use the binary or
+compile the source yourself:</p>
+
+<ul><li>
+<p>The binary packages can lag behind the latest version of the software
+by one or two (maybe more) minor releases, especially after a series
+of small changes and for less popular platforms. Compare the release
+notes for the source and binary packages to make sure there
+aren't any new features that you need on your
+platform.</p>
+</li><li>
+<p>If you use a precompiled binary that is dynamically linked, you will
+need to ensure that you have the correct libraries required by the
+executables. If your system does not already have the required
+version of a library, you might have to install a new version. The
+<em class="filename">README</em> file or <em class="filename">makefile</em>
+that accompanies the binary distribution should list any special
+requirements.</p>
+
+<p>Many systems with shared libraries come with a nifty tool called
+<em class="emphasis">ldd</em>. This tool will tell you which libraries a
+specific binary requires and which libraries on the system satisfy
+that requirement. For example, checking the <em class="emphasis">smbd</em>
+program on our test machine gave us:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ldd smbd</b></tt>
+        libdl.so.2 =&gt; /lib/libdl.so.2 (0x40026000)
+        libnsl.so.1 =&gt; /lib/libnsl.so.1 (0x4002a000)
+        libpam.so.0 =&gt; /lib/libpam.so.0 (0x40041000)
+        libc.so.6 =&gt; /lib/libc.so.6 (0x40049000)
+        /lib/ld-linux.so.2 =&gt; /lib/ld-linux.so.2 (0x40000000)</pre></blockquote>
+
+<p>If there are any incompatibilities between Samba and specific
+libraries on your machine, the distribution-specific documentation
+should highlight them.</p>
+</li><li>
+<p>If your precompiled binary is statically linked, it is still possible
+to have problems. There have been cases in which the statically
+linked C library calls in Samba programs have been out of sync with
+the operating-system kernel, even though this is
+&quot;not supposed to happen.&quot;</p>
+</li><li>
+<p>Keep in mind that each binary distribution carries preset values
+about the target platform, such as default directories and
+configuration option values. Again, check the documentation and the
+makefile included in the source directory to see which directives and
+variables were used when the binary was compiled. In some cases,
+these will not be appropriate for your situation.</p>
+
+<p>A few configuration items can be reset with command-line options at
+runtime rather than at compile time. For example, if your binary
+tries to place any log, lock, or status files in the
+&quot;wrong&quot; place (for example, in
+<em class="filename">/usr/local</em> ), you can override this without
+recompiling.</p>
+</li></ul>
+<p>One point worth mentioning is that the Samba source requires an
+<a name="INDEX-7"/><a name="INDEX-8"/><a name="INDEX-9"/>ANSI C
+compiler. If you are on a legacy platform with a non-ANSI compiler,
+such as the <em class="emphasis">cc</em> compiler on SunOS Version 4,
+you'll have to install an ANSI-compliant compiler
+such as <em class="emphasis">gcc</em> <a name="INDEX-10"/>before you do anything else.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a>
+If installing a compiler isn't something you want to
+wrestle with, you can start off with a binary package. However, for
+the most flexibility and compatibility on your system, we always
+recommend compiling from the latest stable or production source.</p>
+
+<p>A typical installation will take about an hour to complete, including
+downloading the source files and compiling them, setting up the
+configuration files, and testing the server.</p>
+
+<p>Here is an overview of the steps:</p>
+
+<ol><li>
+<p><a name="INDEX-11"/>Download the source or binary files.</p>
+</li><li>
+<p>Read the installation documentation.</p>
+</li><li>
+<p>Configure a makefile.</p>
+</li><li>
+<p>Compile the server and utility programs.</p>
+</li><li>
+<p>Install the server files.</p>
+</li><li>
+<p>Create a Samba configuration file.</p>
+</li><li>
+<p>Test the configuration file.</p>
+</li><li>
+<p>Start the Samba daemons.</p>
+</li><li>
+<p>Test the Samba daemons. <a name="INDEX-12"/></p>
+</li></ol>
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-2"/>
+
+<h2 class="head1">Downloading the Samba Distribution</h2>
+
+<p><a name="INDEX-13"/>If
+you would like to download the latest version of the Samba software,
+the primary web site is <a href="http://www.samba.org">http://www.samba.org</a>. Once connected to this
+page, you'll see links to several Samba mirror sites
+across the world, both for the standard Samba web pages and for sites
+devoted exclusively to downloading Samba. For the best performance,
+choose a site that is closest to your own geographic location.</p>
+
+<p>The standard Samba web sites have Samba
+<a name="INDEX-14"/>documentation and
+<a name="INDEX-15"/>tutorials,
+<a name="INDEX-16"/>mailing-list
+archives, and the latest Samba <a name="INDEX-17"/>news, as well as source and binary
+distributions of Samba. The download sites (sometimes called
+<em class="emphasis">F T P sites</em>) have only the source and binary
+distributions. Unless you specifically want an older version of the
+Samba server or are going to install a binary distribution, download
+the latest source distribution from the closest mirror site. This
+distribution is always named:</p>
+
+<blockquote><pre class="code">samba-latest.tar.gz</pre></blockquote>
+
+<p>which for the 2.2.6 release is an approximately 5MB file.</p>
+
+<p>The source distribution has been archived with
+<em class="emphasis">tar</em> and then compressed with the GNU
+<em class="emphasis">gzip</em> program. To unpack it, move the file to the
+directory in which you want the Samba source directory to be located,
+then <em class="emphasis">cd</em> to that directory and run the command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>tar xvfz samba-latest.tar.gz</b></tt></pre></blockquote>
+
+<p>Or, if you do not have the GNU <em class="emphasis">tar</em> program
+(which also handles the unzipping):</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>gunzip samba-latest.tar.gz</b></tt>
+$ <tt class="userinput"><b>tar xvf samba-latest.tar</b></tt></pre></blockquote>
+
+<p>In that latter case, you might need to install the GNU
+<em class="emphasis">gunzip</em> program first. While the
+<em class="emphasis">tar</em> command runs, it will print out a list of
+the files it installs.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-2.1"/>
+
+<h3 class="head2">Read the Documentation</h3>
+
+<p><a name="INDEX-18"/>This
+part might seem obvious, but at one time or other you probably
+uncompressed a package, blindly typed:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>configure; make; make install</b></tt></pre></blockquote>
+
+<p>and walked away to get another cup of coffee. Do yourself a favor and
+be a little more careful this time.</p>
+
+<p>In the top-level directory that you just installed, there is a file
+named <em class="filename">WHATSNEW.txt</em>, which contains the latest
+news about the release. If you are upgrading, you can find important
+information about bug fixes or configuration parameters that have
+been added or are no longer supported.</p>
+
+<p>With both source and binary packages you'll find a
+large number of documents in the <em class="filename">docs</em> directory,
+in a variety of formats. One file is especially important:</p>
+
+<blockquote><pre class="code">docs/htmldocs/UNIX_INSTALL.html</pre></blockquote>
+
+<p>This is the Samba Team's official instructions on
+installing Samba on a Unix system, which you might like to use as
+another perspective besides what we are telling you here.</p>
+
+<p>In general, we expect you'll find to be most useful
+the files in the following directories:</p>
+
+<dl>
+<dt><b>docs/faq</b></dt>
+<dd>
+<p>This is the Samba Frequently Asked Questions (FAQ) files.</p>
+</dd>
+
+
+
+<dt><b>docs/htmldocs</b></dt>
+<dd>
+<p>This is the miscellaneous documentation in HTML format.</p>
+</dd>
+
+
+
+<dt><b>docs/textdocs</b></dt>
+<dd>
+<p>Here is more documentation, in simple text format.</p>
+</dd>
+
+
+
+<dt><b>docs/manpages</b></dt>
+<dd>
+<p>You don't need to worry about these yet; during the
+installation, the files will be installed so that you can use the
+<em class="emphasis">man</em> command to read them. But you can take a
+look in the directory to see which manpages are available.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-3"/>
+
+<h2 class="head1">Configuring Samba</h2>
+
+<p><a name="INDEX-19"/><a name="INDEX-20"/>Samba automatically configures itself
+prior to compilation. This reduces the likelihood of a
+machine-specific problem, but you might end up wishing for an option
+after Samba has been installed.</p>
+
+<p>The source distribution of Samba 2.2 and above
+doesn't initially have a
+<a name="INDEX-21"/>makefile. Instead, one is
+generated through a <a name="INDEX-22"/><a name="INDEX-23"/>GNU <em class="filename">configure</em>
+script, which is located in the <em class="filename">samba-2.2.x
+/source/</em> directory. The <em class="firstterm">configure</em>
+script takes care of the machine-specific issues of building Samba.</p>
+
+<a name="samba2-CHP-2-NOTE-88"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+
+
+
+<p>Before running the <em class="filename">configure</em> script, it is
+important that you become the root user on the system. Otherwise, you
+might get a warning such as:</p>
+
+
+<blockquote><pre class="code">configure: warning: running as non-root will disable some tests</pre></blockquote>
+
+
+<p>You don't want any test to be disabled when the
+Samba makefile is being created; it would leave the potential for
+errors down the road when compiling or running Samba on your system.</p>
+</blockquote>
+
+<p>When the <em class="filename">configure </em>script is run, it prints out
+messages telling what it is doing, and error messages might be mixed
+in. To make sure you see those very important error messages, we
+suggest you run <em class="filename">configure </em>with its standard
+output passed through some filter to capture the output and keep it
+from scrolling out of sight. One method is using the
+<em class="filename">more</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>./configure | more</b></tt></pre></blockquote>
+
+<p>We will show you another in a moment.</p>
+
+<p>Although you can run <em class="filename">configure </em>as previously
+with no options, you might want to add support for extra features by
+passing options on the command line. For example:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>./configure --with-winbind</b></tt></pre></blockquote>
+
+<p>will configure the Samba makefile with support for winbind
+authentication. If you would like a complete list of options, type
+the following:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>./configure --help</b></tt></pre></blockquote>
+
+<p>Each option enables or disables various features. You typically
+enable a feature by specifying the
+<tt class="literal">--</tt><a name="INDEX-24"/><a name="INDEX-25"/><a name="INDEX-26"/><a name="INDEX-27"/><tt class="literal">with-</tt><em class="replaceable">feature</em>
+option, which will cause the feature to be compiled and installed.
+Likewise, if you specify a
+<tt class="literal">--without-</tt><em class="replaceable">feature</em>
+option, the feature will be disabled. A full list of configuration
+options is provided in <a href="appe.html">Appendix E</a>, but for now we
+want to point out three of them, which are features we cover later in
+this book:</p>
+
+<dl>
+<dt><b><tt class="literal">--with-msdfs</tt><a name="INDEX-28"/><a name="INDEX-29"/></b></dt>
+<dd>
+<p>Include support for Microsoft Distributed filesystem (Dfs), which
+allows dispersed network resources to be clumped together into one
+easy-to-navigate directory tree. See <a href="ch08.html">Chapter 8</a>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-smbwrapper</tt><a name="INDEX-30"/><a name="INDEX-31"/></b></dt>
+<dd>
+<p>Include SMB wrapper support, which allows programs running on the
+Unix host to access SMB shared folders as if they were Unix
+filesystems. We recommend using this option. See <a href="ch05.html">Chapter 5</a>.</p>
+</dd>
+
+
+
+<dt><b><tt class="literal">--with-smbmount</tt><a name="INDEX-32"/><a name="INDEX-33"/></b></dt>
+<dd>
+<p>Include <em class="emphasis">smbmount</em> support, which allows SMB
+shared folders to be mounted in the Unix filesystem. At the time of
+this writing, support for this feature exists only for Linux. This is
+also covered in <a href="ch05.html">Chapter 5</a>.</p>
+</dd>
+
+</dl>
+
+<p>Each option is disabled by default, and none of the features is
+essential to Samba. However, you may want to include them in your
+configuration (as we will in our example) at least to be able to try
+out the options in later chapters.</p>
+
+<p>In addition, <a href="ch02.html#samba2-CHP-2-TABLE-1">Table 2-1</a> shows some other parameters
+that you can give the <em class="filename">configure</em> script if you
+wish to store parts of the Samba distribution in different places,
+perhaps to make use of multiple disks or partitions. Note that the
+defaults sometimes refer to a prefix specified earlier in the table.</p>
+
+<a name="samba2-CHP-2-TABLE-1"/><h4 class="head4">Table 2-1. Additional configure options</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Meaning</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">--prefix</tt><a name="INDEX-34"/><a name="INDEX-35"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install architecture-independent files at the base directory
+specified.</p>
+</td>
+<td>
+<p><em class="filename">/usr/local/samba</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--eprefix</tt><a name="INDEX-36"/><a name="INDEX-37"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install architecture-dependent files at the base directory specified.</p>
+</td>
+<td>
+<p><em class="filename">/usr/local/samba</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--bindir</tt><a name="INDEX-38"/><a name="INDEX-39"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install user executables in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">eprefix</em><em class="filename">/bin</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--sbindir</tt><a name="INDEX-40"/><a name="INDEX-41"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install administrator executables in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">eprefix</em><em class="filename">/bin</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--libexecdir</tt><a name="INDEX-42"/><a name="INDEX-43"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install program executables in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">eprefix</em><em class="filename">/libexec</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--datadir</tt><a name="INDEX-44"/><a name="INDEX-45"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install read-only architecture-independent data in the directory
+specified.</p>
+</td>
+<td>
+<p><em class="replaceable">prefix</em><em class="filename">/share</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--libdir</tt><a name="INDEX-46"/><a name="INDEX-47"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install program libraries in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">eprefix</em><em class="filename">/lib</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--includedir</tt><a name="INDEX-48"/><a name="INDEX-49"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install package-include files in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">prefix</em><em class="filename">/include</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--infodir</tt><a name="INDEX-50"/><a name="INDEX-51"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install additional information files in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">prefix</em><em class="filename">/info</em></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">--mandir</tt><a name="INDEX-52"/><a name="INDEX-53"/>=<em class="replaceable">directory</em></p>
+</td>
+<td>
+<p>Install manual pages in the directory specified.</p>
+</td>
+<td>
+<p><em class="replaceable">prefix</em><em class="filename">/man</em></p>
+</td>
+</tr>
+
+</table>
+
+<p>Here is a sample execution of the
+<em class="filename">configure</em><a name="INDEX-54"/>
+script, which creates a Samba 2.2.6 makefile for the Linux platform.
+Note that you must run the configure script in the
+<em class="emphasis">source</em> directory and that we are showing you yet
+another way to capture the output of the script:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cd samba-2.2.6/source/</b></tt>
+$ <tt class="userinput"><b>su</b></tt>
+Password:
+# <tt class="userinput"><b>./configure --with-smbwrapper --with-smbmount \</b></tt>
+<tt class="userinput"><b>--with-msdfs --with-syslog --with-utmp 2&gt;&amp;1 | tee config.my.log</b></tt>
+loading cache ./config.cache
+checking for gcc... (cached) gcc
+checking whether the C compiler (gcc -O ) works... yes
+checking whether the C compiler (gcc -O ) is a cross-compiler... no
+checking whether we are using GNU C... (cached) yes
+checking whether gcc accepts -g... (cached) yes
+checking for a BSD-compatible install... (cached) /usr/bin/install -c
+
+<i class="lineannotation">...(content omitted)...</i>
+
+checking configure summary
+configure OK
+creating ./config.status
+creating include/stamp-h
+creating Makefile
+creating include/config.h</pre></blockquote>
+
+<p>In general, any message from <em class="filename">configure</em> that
+doesn't begin with the words
+<tt class="literal">checking</tt><a name="INDEX-55"/> or
+<tt class="literal">creating</tt><a name="INDEX-56"/> is an
+<a name="INDEX-57"/>error; it often helps to redirect the
+output of the configure script to a file so that you can quickly
+search for errors, as we did with the <em class="filename">tee</em>
+command earlier. If there was an error during configuration, more
+detailed information about it can be found in the
+<em class="filename">config.log</em><a name="INDEX-58"/> file, which is written to the local
+directory by the <em class="filename">configure</em> script, as well as in
+the <em class="filename">config.my.log</em> file, which we created by
+piping through the <em class="filename">tee</em> command. These files are
+very similar in both name and content, but be careful to check both
+of them for error messages before continuing!</p>
+
+<p>If the configuration works, you'll see a
+<tt class="literal">checking</tt> <tt class="literal">configure</tt>
+<tt class="literal">summary</tt> message followed by a
+<tt class="literal">configure</tt> <tt class="literal">OK</tt> message and four
+or five file-creation messages. So far, so good. <a name="INDEX-59"/></p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-4"/>
+
+<h2 class="head1">Compiling and Installing Samba</h2>
+
+<p><a name="INDEX-60"/><a name="INDEX-61"/><a name="INDEX-62"/><a name="INDEX-63"/>At this point you should be ready to build
+the Samba executables. Compiling is also easy: in the
+<em class="filename">source</em> directory, type <tt class="literal">make</tt>
+on the command line. The
+<em class="filename">make</em><a name="INDEX-64"/> utility will produce a stream of
+explanatory and success messages, beginning with:</p>
+
+<blockquote><pre class="code">Using FLAGS = -O -Iinclude ...</pre></blockquote>
+
+<p>This build includes compiles for both <em class="emphasis">smbd</em> and
+<em class="emphasis">nmbd</em> and ends in a linking command for
+<em class="filename">bin/nmblookup</em>. For example, here is a sample
+make of Samba Version 2.2.6 on a Linux server:</p>
+
+<blockquote><pre class="code"># make 2&gt;&amp;1 | tee make.log
+Using FLAGS =  -O  -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_LARGEFILE64
+_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE  -DLOGFILEBASE=&quot;/usr/local/samba/va
+r&quot; -DCONFIGFILE=&quot;/usr/local/samba/lib/smb.conf&quot; -DLMHOSTSFILE=&quot;/usr/local/samba/
+lib/lmhosts&quot;   -DSWATDIR=&quot;/usr/local/samba/swat&quot; -DSBINDIR=&quot;/usr/local/samba/bin
+&quot; -DLOCKDIR=&quot;/usr/local/samba/var/locks&quot; -DCODEPAGEDIR=&quot;/usr/local/samba/lib/cod
+epages&quot; -DDRIVERFILE=&quot;/usr/local/samba/lib/printers.def&quot; -DBINDIR=&quot;/usr/local/sa
+mba/bin&quot;  -DHAVE_INCLUDES_H -DPASSWD_PROGRAM=&quot;/bin/passwd&quot; -DSMB_PASSWD_FILE=&quot;/u
+sr/local/samba/private/smbpasswd&quot; -DTDB_PASSWD_FILE=&quot;/usr/local/samba/private/sm
+bpasswd.tdb&quot;
+Using FLAGS32 =  -O  -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_LARGEFILE
+64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE  -DLOGFILEBASE=&quot;/usr/local/samba/
+var&quot; -DCONFIGFILE=&quot;/usr/local/samba/lib/smb.conf&quot; -DLMHOSTSFILE=&quot;/usr/local/samb
+a/lib/lmhosts&quot;   -DSWATDIR=&quot;/usr/local/samba/swat&quot; -DSBINDIR=&quot;/usr/local/samba/b
+in&quot; -DLOCKDIR=&quot;/usr/local/samba/var/locks&quot; -DCODEPAGEDIR=&quot;/usr/local/samba/lib/c
+odepages&quot; -DDRIVERFILE=&quot;/usr/local/samba/lib/printers.def&quot; -DBINDIR=&quot;/usr/local/
+samba/bin&quot;  -DHAVE_INCLUDES_H -DPASSWD_PROGRAM=&quot;/bin/passwd&quot; -DSMB_PASSWD_FILE=&quot;
+/usr/local/samba/private/smbpasswd&quot; -DTDB_PASSWD_FILE=&quot;/usr/local/samba/private/
+smbpasswd.tdb&quot;
+Using LIBS = -ldl -lnsl -lpam
+Compiling smbd/server.c
+Compiling smbd/files.c
+Compiling smbd/chgpasswd.c
+Compiling smbd/connection.c
+Compiling smbd/utmp.c
+Compiling smbd/session.c
+Compiling smbd/dfree.c
+Compiling smbd/dir.c
+
+<i class="lineannotation">...(content omitted)...</i>
+
+Compiling rpc_server/srv_srvsvc.c
+Compiling rpc_server/srv_srvsvc_nt.c
+Compiling rpc_server/srv_util.c
+Compiling rpc_server/srv_wkssvc.c
+Compiling rpc_server/srv_wkssvc_nt.c
+Compiling rpc_server/srv_pipe.c
+Compiling rpc_server/srv_dfs.c
+Compiling rpc_server/srv_dfs_nt.c
+Compiling rpc_server/srv_spoolss.c
+Compiling rpc_server/srv_spoolss_nt.c
+Compiling lib/util_getent.c
+Compiling rpc_parse/parse_lsa.c
+Compiling rpc_parse/parse_net.c
+Compiling rpc_parse/parsen/smbmount
+Compiling client/smbmnt.c
+Linking bin/smbmnt
+Compiling client/smbumount.c
+Linking bin/smbumount
+Compiling utils/nmblookup.c
+Linking bin/nmblookup</pre></blockquote>
+
+<p>If you encounter a problem when compiling, first check the Samba
+documentation to see if it is easily fixable. Another possibility is
+to search or post to the Samba mailing lists, which are given at the
+end of <a href="ch12.html">Chapter 12</a> and on the Samba home page. Most
+compilation issues are system-specific and almost always easy to
+overcome.</p>
+
+<p>Now that the files have been compiled, you can install them into the
+directories you identified with the command:</p>
+
+<blockquote><pre class="code">#<tt class="userinput"><b> make install</b></tt></pre></blockquote>
+
+<p>If you happen to be <a name="INDEX-65"/>upgrading, your old Samba files will be
+saved with the extension
+<em class="emphasis">.old</em>,<a name="INDEX-66"/> and you can go back to that previous
+version with the command
+<tt class="literal">make</tt><a name="INDEX-67"/> <tt class="literal">revert</tt>. After doing a
+<tt class="literal">make</tt><a name="INDEX-68"/> <tt class="literal">install</tt>, you should
+copy the <em class="emphasis">.old</em> files (if they exist) to a new
+location or name. Otherwise, the next time you install Samba, the
+original <em class="emphasis">.old</em> will be overwritten without
+warning and you could lose your earlier version. If you configured
+Samba to use the default locations for files, the new files will be
+installed in the directories listed in <a href="ch02.html#samba2-CHP-2-TABLE-2">Table 2-2</a>.
+Remember that you need to perform the installation from an account
+that has write privileges on these target directories; this is
+typically the root account.</p>
+
+<a name="samba2-CHP-2-TABLE-2"/><h4 class="head4">Table 2-2. Samba installation directories</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Directory</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba</em></p>
+</td>
+<td>
+<p>Main tree</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/bin</em></p>
+</td>
+<td>
+<p>Binaries</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/lib</em></p>
+</td>
+<td>
+<p><em class="emphasis">smb.conf</em>, <em class="emphasis">lmhosts</em>,
+configuration files, etc.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/man</em></p>
+</td>
+<td>
+<p>Samba documentation</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/private</em></p>
+</td>
+<td>
+<p>Samba-encrypted password file</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/swat</em></p>
+</td>
+<td>
+<p>SWAT files</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">/usr/local/samba/var</em></p>
+</td>
+<td>
+<p>Samba log files, lock files, browse list info, shared memory files,
+process ID files</p>
+</td>
+</tr>
+
+</table>
+
+<p>Throughout the remainder of the book, we occasionally refer to the
+location of the main tree as <em class="filename">/usr/local/samba</em>.
+In most configurations, this is the base directory of the installed
+Samba package; however, it can vary from system to system<em class="filename">
+</em>.</p>
+
+<a name="samba2-CHP-2-NOTE-90"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Watch out if you've made <em class="filename">/usr</em> a
+read-only partition. You will want to put the logs, locks, and
+password files somewhere else.</p>
+</blockquote>
+
+<p>Here is the installation that we performed on our machine. You can
+see that we used <em class="filename">/usr/local/samba</em> as the base
+directory for the distribution:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>make install 2&gt;&amp;1 | tee make-install.log</b></tt>
+Using FLAGS =  -O  -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_LARGEFILE64
+_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE  -DLOGFILEBASE=&quot;/usr/local/samba/va
+r&quot; -DCONFIGFILE=&quot;/usr/local/samba/lib/smb.conf&quot;
+
+<i class="lineannotation">...(content omitted)...</i>
+
+The binaries are installed. You can restore the old binaries (if there
+were any) using the command &quot;make revert&quot;. You can uninstall the binaries
+using the command &quot;make uninstallbin&quot; or &quot;make uninstall&quot; to uninstall
+binaries, manpages and shell scripts.
+
+<i class="lineannotation">...(content omitted)...</i>
+
+======================================================================
+The SWAT files have been installed. Remember to read the swat/README
+for information on enabling and using SWAT.
+======================================================================</pre></blockquote>
+
+<p>If the last message is about SWAT, you've
+successfully installed all the files. Congratulations! You now have
+Samba on your system!</p>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-4.1"/>
+
+<h3 class="head2">Upgrading Your Installation</h3>
+
+<p><a name="INDEX-70"/><a name="INDEX-71"/>Eventually a new version of
+Samba will be released, and you will want to upgrade. This is simple;
+just repeat the same steps you used to install your current version.
+Download the source distribution from the Samba web site and install
+it, then run the <tt class="literal">./configure</tt>,
+<tt class="literal">make</tt>, and <tt class="literal">make</tt>
+<tt class="literal">install</tt> commands as before. If
+you've forgotten which options you used with the
+<a name="INDEX-72"/><a name="INDEX-73"/><a name="INDEX-74"/><a name="INDEX-75"/><em class="emphasis">configure</em>
+script, take a look at the
+<em class="filename">source/config.status</em><a name="INDEX-76"/><a name="INDEX-77"/> file in your previous
+version's source distribution. The first few lines
+of this file show the options used the last time
+<em class="emphasis">configure</em> was run.</p>
+
+<p>When you run the <tt class="literal">make
+install</tt><a name="INDEX-78"/> command to install your new
+version, the files of the previous version are replaced with the new
+ones, and then all you have to do is restart the Samba daemons to get
+your new version running. See <a href="ch02.html#samba2-CHP-2-SECT-8">Section 2.8</a> later in this chapter for directions on how to do this.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-4.2"/>
+
+<h3 class="head2">Reconfiguring Samba</h3>
+
+<p><a name="INDEX-79"/>If you
+have already compiled Samba and wish to recompile the same source
+code with different <em class="emphasis">configure</em> options, you
+should run the following three commands in the
+<em class="emphasis">source</em> directory before rerunning the
+<em class="emphasis">configure</em> script:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>autoconf</b></tt>
+# <tt class="userinput"><b>make clean</b></tt>
+# <tt class="userinput"><b>rm config.cache</b></tt></pre></blockquote>
+
+<p>This ensures that you are starting with a clean slate and that your
+previous <em class="emphasis">configure</em> command does not leave any
+data around that can affect your new build. From here, you can rerun
+<tt class="literal">./configure</tt> and then <tt class="literal">make</tt> and
+<tt class="literal">make install</tt>.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-4.3"/>
+
+<h3 class="head2">Setting Search Paths</h3>
+
+<p><a name="INDEX-80"/>You
+will probably want to run commands included in the Samba distribution
+without having to specify their full directory paths. For that to
+work, the directory in which the Samba executables are located,
+<em class="filename">/usr/local/samba/bin</em> by default, must be added
+to your shell's <a name="INDEX-81"/>PATH environment variable. This
+environment variable is usually set in one or more of the
+shell's startup files, which in the case of
+<em class="emphasis">bash</em> are <em class="filename">/etc/profile</em>
+(systemwide) and the <em class="filename">.bash_profile</em> and
+<em class="filename">.bashrc</em> files in each user's
+home directory.</p>
+
+<p>To be able to read the <a name="INDEX-82"/><a name="INDEX-83"/><a name="INDEX-84"/>Samba manual pages using the
+<em class="emphasis">man</em> command, the directory where
+Samba's manual pages reside,
+<em class="filename">/usr/local/samba/man</em> by default, must be in your
+<a name="INDEX-85"/>MANPATH environment variable. On Red
+Hat Linux, this can be accomplished by adding the following two lines
+to <em class="filename">/etc/man.config</em>:</p>
+
+<a name="INDEX-86"/><a name="INDEX-87"/><blockquote><pre class="code">
+MANPATH            /usr/local/samba/man
+MANPATH_MAP        /usr/local/samba/bin     /usr/local/samba/man</pre></blockquote>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-5"/>
+
+<h2 class="head1">Enabling SWAT</h2>
+
+<p>The <a name="INDEX-88"/><a name="INDEX-89"/>Samba
+Web Administration Tool (SWAT) runs as a daemon under
+<em class="emphasis">inetd</em> or <em class="filename">xinetd </em>and
+provides a forms-based editor in your web browser for creating and
+modifying <a name="INDEX-90"/>Samba's
+configuration file. For SWAT to work, entries must be added for it in
+the <em class="filename">/etc/services</em> and
+<em class="filename">/etc/inetd.conf</em> (or
+<em class="filename">/etc/xinetd.d/swat) </em>configuration files. To add
+the entries, follow these two steps:</p>
+
+<ol><li>
+<p>Check your <em class="filename">/etc/services</em> file, and if it does
+not contain the following line, add it to the end of the file:</p>
+
+<blockquote><pre class="code">swat   901/tcp</pre></blockquote>
+</li>
+<li>
+<p>Now for <em class="filename">inetd </em><a name="INDEX-91"/>or <em class="filename">xinetd.
+</em><a name="INDEX-92"/>These are &quot;Internet
+super daemons&quot; that handle starting daemons on
+demand, instead of letting them sit around in memory consuming system
+resources. Most systems use <em class="filename">inetd, </em>but
+<em class="filename">xinetd </em>is also used in some versions of Unix,
+notably the Red Hat Linux (Versions 7 and newer) that we use in our
+examples. You can use the <em class="emphasis">ps</em> command to see
+which of the two your system is running.</p>
+</li></ol>
+<p>For <em class="filename">inetd, </em>add a line to the
+<em class="emphasis">/etc/</em><em class="filename">inetd.conf </em>file.
+(Check your <em class="filename">inetd.conf</em> manual page to see the
+exact format of the<em class="filename"> inetd.conf</em> file if it
+differs from the following example.) Don't forget to
+change the path to the SWAT binary if you installed it in a different
+location from the default <em class="filename">/usr/local/samba</em>:</p>
+
+<blockquote><pre class="code">swat   stream  tcp  nowait  root  /usr/local/samba/bin/swat  swat</pre></blockquote>
+
+<p>Then force <em class="filename">inetd</em> to reread its configuration
+file by sending it a SIGHUP (hangup) signal:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/bin/kill -HUP -a inetd</b></tt></pre></blockquote>
+
+<p>Notice that we are using a version of the <em class="emphasis">kill</em>
+command that supports the <em class="emphasis">-a</em> option, so as to
+allow us to specify the process by name. On FreeBSD and Linux, you
+can use the <em class="emphasis">killall</em> command<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> as follows:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>killall -HUP inetd</b></tt></pre></blockquote>
+
+<p>If you are not running Linux or FreeBSD and your version of
+<em class="emphasis">kill</em> doesn't have the
+<em class="emphasis">-a</em> option, you will need to use the
+<em class="emphasis">ps</em> command to find the process ID and then
+supply that to <em class="emphasis">kill</em>:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ps ax | grep inetd</b></tt>
+  780 ?        S      0:00 inetd
+ 1981 pts/4    S      0:00 grep inetd                                         
+# <tt class="userinput"><b>kill -HUP 780</b></tt></pre></blockquote>
+
+<p>If your system is using <em class="filename">xinet, </em>add a file named
+<em class="emphasis">swat</em> in your <em class="filename">/etc/xinetd.d
+</em>directory, containing the following:</p>
+
+<blockquote><pre class="code"># description: swat is the Samba Web Administration Tool, which
+#       allows an administrator to configure Samba using a web
+#       browser interface, with the URL http://localhost:901
+service swat.
+{
+        socket_type             = stream
+        wait                    = no
+        protocol                = tcp
+        only_from               = localhost
+        user                    = root
+        log_on_failure          += USERID
+        server                  = /usr/local/samba/bin/swat
+        port                    = 901
+        disable                 = no
+}</pre></blockquote>
+
+<p>Then <em class="emphasis">xinetd</em> needs to be sent a signal<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a> to make it reread its configuration files:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/bin/kill -HUP -a xinetd</b></tt></pre></blockquote>
+
+<p>And that's pretty much it for the installation.
+Before you can start up Samba, however, you need to create a
+configuration file for it.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-6"/>
+
+<h2 class="head1">A Basic Samba Configuration File</h2>
+
+<p><a name="INDEX-93"/>The
+key to configuring Samba is its configuration file,
+<em class="filename">smb.conf</em>. This configuration file can be very
+simple or extremely complex, and the rest of this book is devoted to
+helping you get deeply personal with this file. For now, however,
+we'll show you how to set up a single file service,
+which will allow you to fire up the Samba daemons and see that
+everything is running as it should be. In later chapters, you will
+see how to configure Samba for more complicated and interesting
+tasks.</p>
+
+<p>The installation process does not automatically create an
+<em class="filename">smb.conf</em> configuration file, although several
+example files are included in the Samba distribution. To test the
+server software, though, we'll use the following
+file, which you can create in a text editor. It should be named
+<em class="filename">smb.conf</em> and placed in the
+<em class="emphasis">/usr/local/samba/lib</em> directory:<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a></p>
+
+<blockquote><pre class="code">[global]
+    workgroup = METRAN 
+[test] 
+    comment = For testing only, please
+    path = /usr/local/samba/tmp
+    read only = no
+    guest ok = yes</pre></blockquote>
+
+<p>This brief configuration file tells the Samba server to offer the
+<em class="filename">/usr/local/samba/tmp</em> directory on the server as
+an SMB share called <em class="emphasis">test</em>. The server also
+becomes part of the METRAN workgroup, of which each client must also
+be a part. If you have already chosen a name for your own workgroup,
+use the name of your workgroup instead of METRAN in the previous
+example. In case you are connecting your Samba system into an
+existing network and need to know the workgroup name, you can ask
+another system administrator or go to a Windows system in the
+workgroup and follow these instructions:</p>
+
+<ul><li>
+<p>Windows 95/98/Me/NT: open the Control Panel, then double-click the
+Network icon. Click the Identification tab, and look for the
+&quot;Workgroup:&quot; label.</p>
+</li><li>
+<p>Windows 2000: open the Control Panel and double-click the System
+icon. Click the Network Identification tab. The workgroup name will
+appear below the computer name.</p>
+</li><li>
+<p>Windows XP: open the Control Panel in Classic View mode and
+double-click the System icon. Then click the Computer Name tab.</p>
+</li></ul>
+<p>We'll use the <tt class="literal">[test]</tt> share in the
+next chapter to set up the Windows clients. For now, you can complete
+the setup by performing the following commands as root on your Unix
+server:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /usr/local/samba/tmp</b></tt>
+# <tt class="userinput"><b>chmod 777 /usr/local/samba/tmp</b></tt></pre></blockquote>
+
+<p>You might also want to put a file or two in the
+<em class="filename">/usr/local/samba/tmp</em> directory so that after
+your Windows systems are initially configured, you will have
+something to use to check that everything works.</p>
+
+<p>We should point out that in terms of system security, this is the
+worst setup possible. For the moment, however, we only wish to test
+Samba, so we'll leave security out of the picture.
+In addition, we will encounter some encrypted password issues with
+Windows clients later on, so this setup will afford us the least
+amount of headaches.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-6.1"/>
+
+<h3 class="head2">Encrypted Passwords</h3>
+
+<p><a name="INDEX-94"/><a name="INDEX-95"/><a name="INDEX-96"/>If your Windows clients are using Windows
+98 or Windows NT 4 Service Pack 3 or above (including Windows 2000
+and Windows XP) and you are using a version of Samba earlier than
+3.0, you must add the following entry to the
+<tt class="literal">[global]</tt> section of the Samba configuration file:</p>
+
+<blockquote><pre class="code">[global]
+    encrypt passwords = yes</pre></blockquote>
+
+<p>In addition, you must use the
+<em class="filename">smbpasswd</em><a name="INDEX-97"/> program (typically located in the
+directory <em class="filename">/usr/local/samba/bin/ </em>) to enter the
+username/password combinations of the Samba users into
+Samba's encrypted password database. For example, if
+you wanted to allow Unix user <tt class="literal">steve</tt> to access
+shares from a client system, you would use this command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -a steve</b></tt>
+New SMB password:
+Retype new SMB password:
+Added user steve.</pre></blockquote>
+
+<p>When the first user is added, the program will output a message
+saying that the encrypted password database does not exist.
+Don't worry: it will then create the database for
+you. Make sure that the username/password combinations you add to the
+encrypted database match the usernames and passwords you intend to
+use on the Windows client side. You must run
+<em class="emphasis">smbpasswd</em> for each client user.</p>
+
+<p>In Samba 3.0, passwords are encrypted by default, so the
+<tt class="literal">encrypt</tt> <tt class="literal">passwords</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> parameter in the
+configuration file is optional. However, you will still need to run
+the <em class="emphasis">smbpasswd</em> command to add users to the
+encrypted password file.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-6.2"/>
+
+<h3 class="head2">Using SWAT</h3>
+
+<p><a name="INDEX-98"/>Creating
+a configuration file with SWAT is even easier than writing a
+configuration file by hand. To invoke SWAT, use your web browser to
+connect to <em class="emphasis">http://localhost:901</em>, and log on as
+root with the root password, as shown in <a href="ch02.html#samba2-CHP-2-FIG-1">Figure 2-1</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-2-FIG-1"/><a name="INDEX-99"/><img src="figs/sam2_0201.gif"/></div><h4 class="head4">Figure 2-1. SWAT login</h4>
+
+<p>After logging in, click the GLOBALS button at the top of the screen.
+You should see the Global Variables page shown in <a href="ch02.html#samba2-CHP-2-FIG-2">Figure 2-2</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-2-FIG-2"/><img src="figs/sam2_0202.gif"/></div><h4 class="head4">Figure 2-2. SWAT Global Variables page</h4>
+
+<p>In this example, notice that SWAT retrieved the workgroup name from
+the <em class="emphasis">smb.conf</em> file that you created. (If it
+didn't, go back and perform that step correctly.)
+Make sure that the <tt class="literal">security</tt> field is set to
+<tt class="literal">USER</tt>.</p>
+
+<p>If you are running Samba 2.2 and your Windows clients are at least
+Windows 98 or Windows NT 4 SP 3 or later versions, find
+<tt class="literal">encrypt</tt> <tt class="literal">passwords</tt> in the
+Security Options section and select <tt class="literal">yes</tt>.</p>
+
+<p>The only other option you need to change from the menu is one
+determining which system on the LAN resolves NetBIOS addresses; this
+system is called the <em class="emphasis">WINS server</em>. At the very
+bottom of the page, set the <tt class="literal">wins</tt>
+<tt class="literal">support</tt> field to <tt class="literal">Yes</tt>, unless
+you already have a WINS server on your network. If you do, put the
+WINS server's IP address in the
+<tt class="literal">wins</tt> <tt class="literal">server</tt> field instead. Then
+return to the top of the screen, and press the Commit Changes button
+to write the changes out to the <em class="emphasis">smb.conf</em> file.</p>
+
+<p>Next, click the SHARES icon. You should see a page similar to <a href="ch02.html#samba2-CHP-2-FIG-3">Figure 2-3</a>. Select <tt class="literal">test</tt> (to the right
+of the Choose Share button), and click the Choose Share button. You
+will see the Share Parameters screen, as shown in <a href="ch02.html#samba2-CHP-2-FIG-3">Figure 2-3</a>, with the <tt class="literal">comment</tt> and
+<tt class="literal">path</tt> fields filled in from your
+<em class="emphasis">smb.conf</em> file.</p>
+
+<div class="figure"><a name="samba2-CHP-2-FIG-3"/><img src="figs/sam2_0203.gif"/></div><h4 class="head4">Figure 2-3. SWAT Share Parameters screen</h4>
+
+<p>If you specified that you want to use encrypted passwords on the
+GLOBALS page, click the PASSWORD button. Near the top of the screen,
+you will see the Server Password Management section. Enter your Unix
+username and password in the spaces, and click the Add New User
+button. This functions the same as the <em class="emphasis">smbpasswd</em>
+utility and creates an entry in the
+<em class="emphasis">/usr/local/samba/private/smbpasswd</em> file to allow
+you to authenticate from a Windows client.</p>
+
+<p>Now click the VIEW button at the top, and SWAT shows you the
+following <em class="filename">smb.conf</em> file:</p>
+
+<blockquote><pre class="code"># Samba config file created using SWAT
+# from localhost (127.0.0.1)
+# Date: 2002/09/05 04:56:43
+
+# Global parameters
+        workgroup = METRAN
+        encrypt passwords = Yes
+        wins support = Yes
+
+[test]
+        comment = For testing only!
+        path = /usr/local/samba/tmp
+        read only = No</pre></blockquote>
+
+<p>Once this configuration file is completed, you can skip the next step
+because the output of SWAT is guaranteed to be syntactically correct.
+<a name="INDEX-100"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-6.3"/>
+
+<h3 class="head2">Disabling Oplocks</h3>
+
+<p>The <em class="filename">smb.conf</em><a name="INDEX-101"/><a name="INDEX-102"/>
+file you have just created is certainly good enough for the purpose
+of initial setup and testing, and you can use it as a starting point
+from which to develop the configuration of your production Samba
+server. But before you get too far with that, we want to bring one
+thing to your attention.</p>
+
+<p>If you are the type of administrator who is highly concerned about
+data integrity, you might want to make the following modification to
+your <em class="filename">smb.conf</em> file before continuing:</p>
+
+<blockquote><pre class="code">[global]
+    oplocks = no</pre></blockquote>
+
+<p>That is, use a text editor to add the line <tt class="literal">oplocks</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt> to the
+<tt class="literal">[global]</tt> section of your
+<em class="filename">smb.conf</em> file. With this example, as with other
+examples we will present throughout this book, you do not need to
+enter the <tt class="literal">[global]</tt> line again in your
+configuration file. We include it only to indicate in which section
+the parameter belongs.</p>
+
+<p>The <tt class="literal">oplocks</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> parameter disables opportunistic locking by
+clients. This will result in significantly poorer performance, but
+will help ensure that flaky Windows clients and/or unreliable network
+hardware will not lead to corrupted files on the Samba server.</p>
+
+<p>We will cover opportunistic locking (oplocks) in more detail in the
+section &quot;Locks and Oplocks&quot; in
+<a href="ch08.html">Chapter 8</a>, and recommend that you understand the
+ideas presented there before implementing a production Samba server
+that serves database files or other valuable data.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-6.4"/>
+
+<h3 class="head2">Testing the Configuration File</h3>
+
+<p><a name="INDEX-103"/>If you
+didn't use SWAT to create your configuration file,
+you should probably test it to ensure that it is syntactically
+correct. It might seem silly to run a test program against an
+eight-line configuration file, but it's good
+practice for the real ones that we'll be writing
+later on.</p>
+
+<p>The test parser,
+<em class="filename">testparm</em><a name="INDEX-104"/>, examines an
+<em class="filename">smb.conf</em> file for syntax errors and reports any
+it finds along with a list of the services enabled on your machine.
+An example follows; you'll notice that in our haste
+to get the server running we mistyped <tt class="literal">workgroup</tt> as
+<tt class="literal">workgrp</tt> (the output is often lengthy, so we
+recommend capturing it with the <em class="emphasis">tee</em> command):</p>
+
+<blockquote><pre class="code">Load smb config files from smb.conf
+Unknown parameter encountered: &quot;workgrp&quot;
+Ignoring unknown parameter &quot;workgrp&quot;
+Processing section &quot;[test]&quot;
+Loaded services file OK.
+Press Enter to see a dump of your service definitions
+# Global parameters
+[global]
+    workgroup = WORKGROUP
+    netbios name = 
+    netbios aliases = 
+    server string = Samba 2.2.6
+    interfaces = 
+    bind interfaces only = No
+
+<i class="lineannotation">...(content omitted)...</i>
+
+[test]
+    comment = For testing only!
+    path = /usr/local/samba/tmp
+    read only = No</pre></blockquote>
+
+<p>The interesting parts are at the top and bottom. The top of the
+output will flag any syntax errors that you might have made, and the
+bottom lists the services that the server thinks it should offer. A
+word of advice: make sure you and the server have the same
+expectations. <a name="INDEX-105"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-7"/>
+
+<h2 class="head1">Firewall Configuration</h2>
+
+<p><a name="INDEX-106"/>As
+with any services that run on TCP/IP, the SMB networking services
+offered by Samba can be accessed from across the Internet unless your
+organization's firewall is properly configured. The
+following ports are used by Samba for SMB networking and SWAT:</p>
+
+<dl>
+<dt><b>Port 137</b></dt>
+<dd>
+<p>Used for NetBIOS network browsing</p>
+</dd>
+
+
+
+<dt><b>Port 138</b></dt>
+<dd>
+<p>Used for NetBIOS name service</p>
+</dd>
+
+
+
+<dt><b>Port 139</b></dt>
+<dd>
+<p>Used for file and printer sharing and other operations</p>
+</dd>
+
+
+
+<dt><b>Port 445</b></dt>
+<dd>
+<p>Used by Windows 2000/XP when NetBIOS over TCP/IP is disabled</p>
+</dd>
+
+
+
+<dt><b>Port 901</b></dt>
+<dd>
+<p>Used by SWAT</p>
+</dd>
+
+</dl>
+
+<p>At the minimum, your organization's Internet
+firewall should shut down all the ports in the list to traffic in
+both directions. Do not assume that preventing incoming connections
+is sufficient; there are cracks that trick Windows clients into
+sending data out of the local area network and into the Internet by
+SMB protocol, even from a local network that uses private IP
+addresses not forwarded by routers. If you want SMB traffic to travel
+across the Internet to remote sites, the best way is to use a virtual
+private network (VPN). See the O'Reilly book,
+<em class="citetitle">Virtual Private Networks</em>, for more information
+on this subject.</p>
+
+<p>In addition, you might wish to configure a firewall on the Samba host
+system to keep SMB packets from traveling further than necessary
+within your organization's network. For example,
+port 901 can be shut down for remote accesses so that SWAT can be run
+only on the Samba host system. If you are using Samba to serve only a
+fraction of the client systems within your organization, consider
+allowing SMB packets (i.e., packets on ports 137-139 and 445) to go
+to or come from only those clients.</p>
+
+<p>For more information on configuring firewalls, see the
+O'Reilly book <em class="citetitle">Building Internet
+Firewalls</em>.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-8"/>
+
+<h2 class="head1">Starting the Samba Daemons</h2>
+
+<p>Two Samba processes,
+<em class="emphasis">smbd</em><a name="INDEX-107"/> and
+<em class="emphasis">nmbd</em><a name="INDEX-108"/>, need to be running for Samba to work
+correctly. There are three ways to start them:</p>
+
+<ul><li>
+<p>Manually</p>
+</li><li>
+<p>Automatically, during system boot</p>
+</li><li>
+<p>From <em class="emphasis">inetd or xinetd</em></p>
+</li></ul>
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-8.1"/>
+
+<h3 class="head2">Starting the Daemons Manually</h3>
+
+<p><a name="INDEX-109"/><a name="INDEX-110"/>If you're in a
+hurry, you can start the Samba daemons by hand. As root, simply enter
+the following commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/usr/local/samba/bin/smbd -D</b></tt>
+# <tt class="userinput"><b>/usr/local/samba/bin/nmbd -D</b></tt></pre></blockquote>
+
+<p>Samba will now be running on your system and is ready to accept
+connections. However, keep in mind that if either of the daemons exit
+for any reason (including system reboots), they will need to be
+restarted manually.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-8.2"/>
+
+<h3 class="head2">Automatic Startup</h3>
+
+<p><a name="INDEX-111"/><a name="INDEX-112"/>To have the Samba daemons
+started automatically when the system boots, you need to add the
+commands listed in the previous section to your standard Unix startup
+scripts. The exact method varies depending on the flavor of Unix
+you're using.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-2-SECT-8.2.1"/>
+
+<h3 class="head3">BSD Unix</h3>
+
+<p><a name="INDEX-113"/><a name="INDEX-114"/><a name="INDEX-115"/>With a BSD-style Unix, you need to append
+the following code to the <em class="filename">rc.local </em>file, which
+is typically found in the <em class="filename">/etc</em> or
+<em class="filename">/etc/rc.d</em> directories:</p>
+
+<blockquote><pre class="code">if [ -x /usr/local/samba/bin/smbd]; then
+    echo &quot;Starting smbd...&quot;
+    /usr/local/samba/bin/smbd -D
+    echo &quot;Starting nmbd...&quot;
+    /usr/local/samba/bin/nmbd -D
+fi</pre></blockquote>
+
+<p>This code is very simple: it checks to see if the
+<em class="filename">smbd</em> file exists and has execute permissions,
+and if it does, it starts up both of the Samba daemons on system
+boot.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-2-SECT-8.2.2"/>
+
+<h3 class="head3">System V Unix</h3>
+
+<p><a name="INDEX-116"/><a name="INDEX-117"/><a name="INDEX-118"/>With System V, things can get a little
+more complex. Depending on your Unix version, you might be able to
+get away with making a simple change to an
+<em class="filename">rc.local</em> file as with BSD Unix, but System V
+typically uses directories containing links to scripts that control
+daemons on the system. Hence, you need to instruct the system how to
+start and stop the Samba daemons. The first step to implement this is
+to modify the contents of the <em class="filename">/etc/rc.d/init.d</em>
+directory by adding something similar to the following shell script,
+which for this example we will name <em class="filename">smb </em>:</p>
+
+<blockquote><pre class="code">#!/bin/sh
+
+# Check that the Samba configuration file exists
+[ -f /usr/local/samba/lib/smb.conf ] || exit 0
+
+start(  )
+{
+        echo -n &quot;Starting SMB services: &quot;
+        /usr/local/samba/bin/smbd -D
+        ERROR=$?
+        echo
+
+        echo -n &quot;Starting NMB services: &quot;
+        /usr/local/samba/bin/nmbd -D
+        ERROR2=$?
+        if [ $ERROR2 -ne 0 ]
+        then
+                ERROR=1
+        fi
+        echo
+
+        return $ERROR
+}
+
+stop(  )
+{
+        echo -n &quot;Shutting down SMB services: &quot;
+        /bin/kill -TERM -a smbd
+        ERROR=$?
+        echo
+
+        echo -n &quot;Shutting down NMB services: &quot;
+        /bin/kill -TERM -a nmbd
+        ERROR2=$?
+        if [ $ERROR2 -ne 0 ]
+        then
+                ERROR=1
+        fi
+        echo
+
+        return $ERROR
+}
+
+case &quot;$1&quot; in
+  start)
+        start
+        ;;
+  stop)
+        stop
+        ;;
+  *)
+        echo &quot;Usage: $0 {start|stop}&quot;
+        exit 1
+esac
+
+exit $?</pre></blockquote>
+
+<p>With this script, you can start and stop <em class="emphasis">smbd</em>
+and <em class="emphasis">nmbd</em> like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/etc/rc.d/init.d/smb start</b></tt>
+Starting SMB services:
+Starting NMB services:
+# <tt class="userinput"><b>ps ax | grep mbd</b></tt>
+ 1268 ?        S      0:00 /usr/local/samba/bin/smbd -D
+ 1270 ?        S      0:00 /usr/local/samba/bin/nmbd -D
+ 1465 pts/2    S      0:00 grep mbd
+# <tt class="userinput"><b>/etc/rc.d/init.d/smb stop</b></tt>
+Shutting down SMB services:
+Shutting down NMB services:</pre></blockquote>
+
+<p>If you are having trouble writing a startup script for your system,
+check to see if there is a packaged release of Samba (available from
+your Unix vendor or the Samba FTP site). If so, you might be able to
+extract a startup script from it to use as a starting point.
+Typically, this script doesn't change much (if at
+all) from release to release, so using a script from an older Samba
+version should not be a problem. Another possibility is to check the
+<em class="filename">packaging</em> directory in the Samba source
+distribution. In that directory, there are subdirectories for many
+Unix versions in which you can find a startup script for those
+versions. Even if your version isn't included, you
+can probably find a startup script for a similar version to use as a
+starting point.</p>
+
+<p>Finally, we need to add symbolic links to the
+<em class="filename">smb</em> script in the
+<em class="emphasis">/etc/rc.d/rcX.d</em> directories:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc3.d/S35smb</b></tt>
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc5.d/S35smb</b></tt>
+
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc0.d/K35smb</b></tt>
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc1.d/K35smb</b></tt>
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc2.d/K35smb</b></tt>
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc4.d/K35smb</b></tt>
+# <tt class="userinput"><b>ln -s /etc/rc.d/init.d/smb /etc/rc.d/rc6.d/K35smb</b></tt></pre></blockquote>
+
+<p>The first two commands, with link names starting with an
+&quot;S&quot;, cause Samba to be started when
+entering runlevels 3 or 5, which are the runlevels in which network
+file sharing (NFS) is normally enabled. The second group of commands,
+with link names starting with a
+&quot;K&quot;, cause Samba to be shut down
+when entering any of the other runlevels (0, 1, 2, 4, or 6).</p>
+
+<p>The links starting with &quot;S&quot; are
+used to start the daemons, and the links starting with
+&quot;K&quot; are used for killing them. When
+the runlevel is changed, the links starting with
+&quot;K&quot; in the corresponding directory
+(e.g., the <em class="filename">rc3.d</em> directory for runlevel 3) are
+executed, followed by the links starting with
+&quot;S&quot;. If we wanted, we could have
+Samba restarted when switching between runlevels 3 and 5 by adding a
+<em class="filename">K35smb</em> link to each <em class="filename">rc3.d</em>
+and <em class="filename">rc5.d </em>directory.</p>
+
+<p>The number after the K or S in the link names is used to set the
+order in which all the daemons with links in the directory are
+started or killed off. Get a long listing of the
+<em class="emphasis">rc3.d</em> or <em class="emphasis">rc5.d</em> directories
+to see how this is set up on your system. We use 35 to match the
+behavior of Red Hat's Samba RPM package. The
+important thing is to make sure when starting Samba that all services
+it requires are started before it. When shutting down, it is a good
+idea to shut down Samba before services it requires to avoid excess
+error messages in the log files, but the order is not as crucial.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-2-SECT-8.2.3"/>
+
+<h3 class="head3">Darwin and Mac OS X</h3>
+
+<p><a name="INDEX-119"/><a name="INDEX-120"/><a name="INDEX-121"/><a name="INDEX-122"/>An installation of Samba is bundled with the
+Darwin distribution, which is included in Mac OS X.<a name="FNPTR-5"/><a href="#FOOTNOTE-5">[5]</a> </p>
+
+<p>The Samba daemons are started during system
+boot by the script
+<em class="filename">/System/Library/StartupItems/Samba/Samba</em>. To
+trigger the execution of this script, edit the file
+<em class="filename">/etc/hostconfig</em> and change the SMBSERVER
+parameter to look like this:</p>
+
+<blockquote><pre class="code">SMBSERVER=-YES-</pre></blockquote>
+
+<p>On Mac OS X, the graphical user interface (GUI) provides an
+alternative to using the command line. Launch the System Preferences
+application, and select Sharing (see <a href="ch02.html#samba2-CHP-2-FIG-4">Figure 2-4</a>).
+Under the Services tab, turn on Windows File Sharing. This will make
+the aforementioned change to <em class="filename">/etc/hostconfig</em> and
+immediately execute the startup item.</p>
+
+<div class="figure"><a name="samba2-CHP-2-FIG-4"/><img src="figs/sam2_0204.gif"/></div><h4 class="head4">Figure 2-4. Mac OS X sharing preferences</h4>
+
+<p>If you decide to install Samba yourself on Mac OS X,
+it's best not to stomp on the installation provided
+with the OS. Use the procedures detailed earlier in this chapter to
+install the software into <em class="filename">/usr/local/samba</em> or
+some other area unaffected by OS upgrades. (Remember to set up users
+with <em class="emphasis">smbpasswd</em> if you're using
+encrypted passwords, as described earlier in this chapter. This step
+is handled automatically with entries in
+<em class="filename">/var/db/samba/hash</em> if you're
+using the built-in server on Mac OS X.) Once you've
+got that working, you can edit the Samba startup item script to refer
+to your installation, like this:</p>
+
+<blockquote><pre class="code">    #!/bin/sh
+    # Start Samba
+
+    . /etc/rc.common
+
+    if [ &quot;${SMBSERVER:=-NO-}&quot; = &quot;-YES-&quot; ]; then
+        ConsoleMessage &quot;Starting SMB server&quot;
+
+        if [ -f /usr/local/samba/lib/smb.conf ]; then
+            /usr/local/samba/bin/smbd -D
+            /usr/local/samba/bin/nmbd -D
+        fi
+    fi</pre></blockquote>
+
+<p>However, beware of OS updates, which can wipe out your changes. One
+solution is to make the script immutable, like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chflags uchg /System/Library/StartupItems/Samba/Samba</b></tt></pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-2-SECT-8.2.4"/>
+
+<h3 class="head3">Testing automatic startup</h3>
+
+<p><a name="INDEX-123"/><a name="INDEX-124"/>If you can afford a few minutes of
+downtime, reboot your system and again use the
+<em class="emphasis">ps</em> command to check that the
+<em class="emphasis">smbd</em> and <em class="emphasis">nmbd</em> daemons are
+running. And if you are managing a 24/7 server, we highly recommend
+that you find some downtime in which to reboot and perform this
+check. Otherwise, your next unscheduled downtime might surprise you
+with a mysterious absence of SMB networking services when the system
+comes up again! <a name="INDEX-125"/><a name="INDEX-126"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-2-SECT-8.3"/>
+
+<h3 class="head2">Starting from inetd</h3>
+
+<p><a name="INDEX-127"/><a name="INDEX-128"/><a name="INDEX-129"/>The <em class="emphasis">inetd</em>
+<em class="emphasis"><a name="FNPTR-6"/><a href="#FOOTNOTE-6">[6]</a></em> daemon is a Unix
+system's Internet &quot;super
+daemon.&quot; It listens on ports defined in
+<em class="filename">/etc/services</em> and executes the appropriate
+program for each port, which is defined in
+<em class="filename">/etc/inetd.conf</em>. The advantage of this scheme is
+that you can have a large number of daemons ready to answer queries,
+but they don't all have to be running all the time.
+Instead, <em class="emphasis">inetd</em> listens for connection requests
+and starts the appropriate daemon when it is needed. The penalty is a
+small overhead cost of creating a new daemon process, as well as the
+fact that you need to edit two files rather than one to set things
+up. The <em class="emphasis">inetd</em> daemon is handy if you have only
+one or two Samba users or your machine is running too many daemons
+already. It's also easier to perform an upgrade
+without disturbing an existing connection.</p>
+
+<p>If you wish to start from <em class="filename">inetd</em>, first open
+<em class="filename">/etc/services</em> in your text editor. If you
+don't already have them defined, add the following
+two lines:</p>
+
+<blockquote><pre class="code">netbios-ssn     139/tcp
+netbios-ns      137/udp</pre></blockquote>
+
+<p>Next, edit <em class="filename">/etc/inetd.conf</em>. Look for the
+following two lines and add them if they don't
+exist. If you already have <tt class="literal">smbd</tt> and
+<tt class="literal">nmbd</tt> lines in the file, edit them to point at the
+new <em class="emphasis">smbd</em> and <em class="emphasis">nmbd</em>
+you've installed. Your brand of Unix might use a
+slightly different syntax in this file; use the existing entries and
+the <em class="filename">inetd.conf </em> manual
+page as a guide:</p>
+
+<blockquote><pre class="code">netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
+netbios-ns  dgram  udp wait   root /usr/local/samba/bin/nmbd nmbd</pre></blockquote>
+
+<p>Finally, kill any <em class="emphasis">smbd</em> or
+<em class="emphasis">nmbd</em> processes and send the
+<em class="emphasis">inetd</em> process a hangup (HUP) signal to tell it
+to reread its configuration file:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/bin/kill -TERM -a smbd</b></tt>
+# <tt class="userinput"><b>/bin/kill -TERM -a nmbd</b></tt>
+# <tt class="userinput"><b>/bin/kill -HUP -a inetd</b></tt></pre></blockquote>
+
+<p>After that, Samba should be up and running.</p>
+
+<p>As we've pointed out before, Red Hat and perhaps
+other Unix vendors supply <em class="emphasis">xinetd</em> rather than
+<em class="emphasis">inetd</em>. If you need to use
+<em class="emphasis">xinetd</em>, you will need to supply a configuration
+file in the <em class="emphasis">/etc/xinetd.d</em> directory.
+<a name="INDEX-130"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-2-SECT-9"/>
+
+<h2 class="head1">Testing the Samba Daemons</h2>
+
+<p><a name="INDEX-131"/><a name="INDEX-132"/>We're
+nearly done with the Samba server setup. All that's
+left to do is to make sure everything is working as we think it
+should. A convenient way to do this is to use the
+<em class="filename">smbclient</em><a name="INDEX-133"/> program to examine what the server is
+offering to the network. If everything is set up properly, you should
+be able to do the following:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/usr/local/samba/bin/smbclient -U% -L localhost</b></tt>
+added interface ip=172.16.1.1 bcast=172.16.1.255 nmask=255.255.255.0
+Domain=[METRAN] OS=[Unix] Server=[Samba 2.2.6]
+
+        Sharename      Type      Comment
+        ---------      ----      -------
+        test           Disk      For testing only, please
+        IPC$           IPC       IPC Service (Samba 2.2.6)
+        ADMIN$         Disk      IPC Service (Samba 2.2.6)
+        
+        Server               Comment
+        ---------            -------
+        TOLTEC               Samba 2.2.6 on toltec
+
+        Workgroup            Master
+        ---------            -------
+        METRAN               TOLTEC</pre></blockquote>
+
+<p>If there is a problem, don't panic! Try to start the
+daemons manually, and check the system output or the debug files at
+<em class="filename">/usr/local/samba/var/log.smb</em><a name="INDEX-134"/><a name="INDEX-135"/><a name="INDEX-136"/> to see if you can determine what happened.
+If you think it might be a more serious problem, skip to <a href="ch12.html">Chapter 12</a> for help on troubleshooting the Samba daemons.</p>
+
+<p>If it worked, congratulations! You now have successfully set up the
+Samba server with a disk share. It's a simple one,
+but we can use it to set up and test the Windows 95/98/Me and
+NT/2000/XP clients in the next chapter. Then we will start making it
+more interesting by adding services such as home directories,
+printers, and security, and by seeing how to integrate the server
+into a larger Windows domain. <a name="INDEX-137"/></p>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/>
+<p><a href="#FNPTR-1">[1]</a> <em class="emphasis">gcc</em> binaries are available for almost
+every modern machine. See <a href="http://www.gnu.org/">http://www.gnu.org/</a> for a list of sites with
+<em class="emphasis">gcc</em> and other GNU software.</p> <a name="FOOTNOTE-2"/> <p><a href="#FNPTR-2">[2]</a> Do
+not confuse this with the Solaris <em class="emphasis">killall</em>
+command, which performs part of the system shutdown sequence!</p>
+<a name="FOOTNOTE-3"/>
+<p><a href="#FNPTR-3">[3]</a> Depending on the version of <em class="emphasis">xinetd</em> you
+have and how it was compiled, you might need to send a USR1 or some
+other signal rather than the HUP signal. Check the manual page for
+<em class="emphasis">xinetd (8)</em> on your system for details.</p>
+<a name="FOOTNOTE-4"/>
+<p><a href="#FNPTR-4">[4]</a> If you did not compile Samba, but instead downloaded a binary,
+check with the documentation for the package to find out where it
+expects the <em class="filename">smb.conf</em> file to be. Or, try running
+the <em class="emphasis">testparm</em> program and look for the location
+of <em class="filename">smb.conf</em> in the first line of output. If
+Samba came preinstalled with your Unix system, an
+<em class="filename">smb.conf</em> file is probably already somewhere on
+your system.</p> <a name="FOOTNOTE-5"/>
+<p><a href="#FNPTR-5">[5]</a> In this book, we cover Darwin Version 6.0 and OS X Version
+10.2.</p> <a name="FOOTNOTE-6"/> <p><a href="#FNPTR-6">[6]</a> With early releases of Samba 2.2, there were reports
+of intermittent errors when starting from <em class="emphasis">inetd</em>.
+We provide this information so that it will be available for later
+releases when the problem will hopefully have been identified and
+corrected.</p> </blockquote>
+
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/ch03.html b/docs/htmldocs/using_samba/ch03.html
new file mode 100644
index 0000000000..16e86f4f6d
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch03.html
@@ -0,0 +1,2086 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 3. Configuring Windows Clients</h1>
+
+
+<p><a name="INDEX-1"/><a name="INDEX-2"/>Configuring Windows to use
+your new Samba server is really quite simple. SMB is
+Microsoft's native language for resource sharing on
+a local area network, so much of the installation and setup on the
+Windows client side have been taken care of already.</p>
+
+
+<div class="sect1"><a name="samba2-CHP-3-SECT-1"/>
+
+<h2 class="head1">Windows Networking Concepts</h2>
+
+<p><a name="INDEX-3"/><a name="INDEX-4"/>Windows is different from Unix in
+many ways, including how it supports networking. Before we get into
+the hands-on task of clicking our way through the dialog boxes to
+configure each version of Windows, we need to provide you with a
+common foundation of networking technologies and concepts that apply
+to the entire family of Windows operating systems.</p>
+
+<p>For each Windows version, these are the main issues we will be
+dealing with:</p>
+
+<ul><li>
+<p>Making sure required networking components are installed and bound to
+the network adapter</p>
+</li><li>
+<p>Configuring networking with a valid IP address, netmask and gateway,
+and WINS and DNS name servers</p>
+</li><li>
+<p>Assigning workgroup and computer names</p>
+</li><li>
+<p>Setting the username(s) and password(s)</p>
+</li></ul>
+<p>In addition, some minor issues involving communication and
+coordination between Windows and Unix are different among Windows
+versions.</p>
+
+<p>One can go crazy thinking about the ways in which Unix is different
+from Windows, or the ways in which members of the Windows family are
+different from each other in underlying technology, behavior, or
+appearance. For now let's just focus on their
+similarities and see if we can find some common ground.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-1.1"/>
+
+<h3 class="head2">Components</h3>
+
+<p><a name="INDEX-5"/><a name="INDEX-6"/>Unix
+systems historically have been monolithic in nature, requiring
+recompilation or relinking to create a kernel with a customized
+feature set. However, modern versions have the ability to load or
+unload device drivers or various other operating-system features as
+modules while the system is running, without even needing to reboot.</p>
+
+<p>Windows allows for configuration by installing or uninstalling
+<em class="firstterm">components</em>. As far as networking goes,
+components can be one of three things:<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a></p>
+
+<ul><li>
+<p>Protocols</p>
+</li><li>
+<p>Clients</p>
+</li><li>
+<p>Services</p>
+</li></ul>
+<p>Since Samba works using the TCP/IP protocol, of course
+we'll want to have that installed. In some cases, we
+also will want to find protocols to <em class="emphasis">uninstall</em>.
+For example, if Netware protocol (IPX/SPX) is not required on the
+network, it might as well be removed.</p>
+
+<p><a name="INDEX-7"/><a name="INDEX-8"/>NetBEUI protocol should be removed if
+possible. Having NetBEUI running at the same time as NetBIOS over
+TCP/IP causes the system to look for services under two different
+protocols, only one of which is likely to be in use. When Windows is
+configured with one or more unused protocols, 30-second delays will
+result when Windows tries to communicate with the unused protocol.
+Eventually, it times out and tries another one, until it finds one
+that works. This fruitless searching results in terrible performance.</p>
+
+<p>The other two items in the list, client and service components, are
+pretty much what you'd expect. Client components
+perform tasks related to connecting with network servers, and service
+components are for making the local system into a server of resources
+on the network. In <a href="ch01.html">Chapter 1</a> we told you that SMB
+systems can act as both clients and servers, offering resources on
+the network at the same time they request resources. In accordance
+with that, it is possible to install a component for SMB client
+services and, separately, a service component that allows file and
+printer shares on the local system to be accessible from other
+systems on the network.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.1.1"/>
+
+<h3 class="head3">Bindings</h3>
+
+<p><a name="INDEX-9"/><a name="INDEX-10"/><a name="INDEX-11"/>Once
+a networking component is installed, it must be
+<em class="firstterm">bound</em> to a hardware interface, or
+<em class="firstterm">adapter</em>, to be used on the network. At first
+this might seem like an odd complication; however, it is a conceptual
+model that allows the associations between hardware and software to
+be clearly displayed and easily modified through a graphical
+interface.</p>
+
+<p>We will want to make sure that your Windows client has both TCP/IP
+and the client component for SMB networking installed and also that
+it is bound to the network adapter that connects to our Samba
+network, which in most cases will be an Ethernet adapter.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-1.2"/>
+
+<h3 class="head2">IP Address</h3>
+
+<p>Just like any Unix system (or any other system that is using TCP/IP),
+your Windows systems will need an <a name="INDEX-12"/>IP address. If you are using
+<a name="INDEX-13"/>DHCP
+on your network, you can configure Windows to obtain its IP address
+automatically by using a DHCP server. Otherwise, you will need to
+assign a static IP address manually along with a netmask.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a></p>
+
+<p>If you are on a private network where you have the authority to
+assign your own IP addresses, you can select from addresses in one of
+three ranges:<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a></p>
+
+<ul><li>
+<p>10.0.0.1 through 10.255.255.254</p>
+</li><li>
+<p>172.16.0.1 through 172.31.255.254</p>
+</li><li>
+<p>192.168.0.1 through 192.168.255.254</p>
+</li></ul>
+<p>These address ranges are reserved for private networks not directly
+connected to the Internet. For more information on using these
+private network addresses, see RFC 1918.</p>
+
+<p>If you're not maintaining your own separate network,
+see your system administrator for some available addresses on your
+network, as well as for the proper netmask to use.</p>
+
+<p>You should also be prepared to enter the IP address of the default
+gateway for the network. In some networks, the default gateway is the
+system or router that connects the LAN to the Internet. In other
+cases, the default gateway connects a subnet into a larger
+departmental or enterprise network.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-1.3"/>
+
+<h3 class="head2">Name Resolution</h3>
+
+<p><a name="INDEX-14"/><a name="INDEX-15"/>Name resolution is the function of
+translating human-friendly hostnames, such as
+<em class="emphasis">hopi</em>, or fully qualified domain names (FQDNs),
+such as <tt class="literal">mixtec.metran.cx</tt>, into IP addresses, such
+as 172.16.1.11 or 172.16.1.7.</p>
+
+<p>Unix systems can perform name resolution using an
+<em class="filename">/etc/hosts</em><a name="INDEX-16"/><a name="INDEX-17"/> file at the minimum, and more commonly can
+also incorporate services such as
+<a name="INDEX-18"/>DNS (Domain Name System)
+and <a name="INDEX-19"/>NIS (Network Information Service).
+Thus, name resolution is not necessarily performed by one isolated
+part of the operating system or one daemon, but is a system that can
+have a number of dispersed parts (although the
+<a name="INDEX-20"/>name
+service switch, with its
+<em class="filename">/etc/nsswitch.conf</em><a name="INDEX-21"/><a name="INDEX-22"/> configuration file, helps to tie them
+together).</p>
+
+<p>Although the specific implementation is different, name resolution in
+Windows is also performed by querying a number of resources, some of
+which are similar (or even identical) to their Unix counterparts.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.1"/>
+
+<h3 class="head3">Broadcast name resolution</h3>
+
+<p>On the other hand, there is one way in which Windows is not at all
+similar to Unix. If a Windows workstation is set up with no WINS name
+server, it will use the broadcast method of
+<a name="INDEX-23"/><a name="INDEX-24"/>name resolution, as described in <a href="ch01.html">Chapter 1</a>,<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a> probably resulting in a
+very busy network. And even if you provide name servers for your
+Windows system to use, it might still resort to broadcast name
+resolution if it is unsuccessful at querying the name servers. For
+this reason, we recommend that you provide multiple reliable name
+servers for your Windows computers on the network.</p>
+
+<p>If that weren't enough to get you interested in
+setting up WINS and DNS servers, broadcast name resolution is usually
+limited to working on the local subnet because routers are usually
+configured not to forward broadcast packets to other networks.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.2"/>
+
+<h3 class="head3">WINS</h3>
+
+<p>We've already told you about WINS in <a href="ch01.html">Chapter 1</a>, and we don't have much more
+to say about it here. WINS can translate simple NetBIOS computer
+names such as <em class="emphasis">huastec</em> or
+<em class="emphasis">navajo</em> into IP addresses, as required on an SMB
+network. Of course, the interesting thing here is that Samba can act
+as a WINS server if you include the line:</p>
+
+<blockquote><pre class="code">wins support = yes</pre></blockquote>
+
+<p>in your Samba server's
+<em class="filename">smb.conf</em><a name="INDEX-25"/><a name="INDEX-26"/> file.
+This can be a good thing, to be sure, and we highly recommend it. Not
+only will you have a reliable WINS server to reduce the number of
+broadcast packets, but you won't need to run Windows
+NT/2000/XP to get it.</p>
+<a name="samba2-CHP-3-NOTE-91"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>One caveat about using Samba as a <a name="INDEX-27"/><a name="INDEX-28"/>WINS server is that Samba (up to Version
+2.2, at least) cannot synchronize with other WINS servers. So if you
+specify a Samba server as your Windows system's WINS
+server, you must be careful not to specify any additional (i.e.,
+secondary) WINS servers. If you do, you are likely to run into
+problems because the servers will not be able to synchronize their
+databases with each other. In Samba's defense, if
+you are using a Samba WINS server (running on a typically reliable
+Unix host), you will probably have little need for a secondary WINS
+server anyway.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.3"/>
+
+<h3 class="head3">LMHOSTS</h3>
+
+<p>All Windows versions support a backup method of name resolution, in
+the form of a file called
+<em class="filename">LMHOSTS</em><a name="INDEX-29"/> <em class="emphasis"><a name="FNPTR-5"/><a href="#FOOTNOTE-5">[5]</a></em>
+that contains a lookup table of computer names and IP addresses. This
+exists for &quot;historical purposes,&quot;
+and is a rather awkward method of name resolution because it requires
+the administrator (i.e., you!) to keep copies of
+<em class="filename">LMHOSTS</em> up to date on every single Windows
+system on the network. To be fully effective,
+<em class="filename">LMHOSTS</em> would have to be updated every time a
+new system were added to (or removed from) the network. Of course,
+there might be ways to automate that process, but a better option
+would be simply to run a WINS name server that is intentionally
+designed to solve that specific problem.</p>
+
+<p>There are perhaps a couple of reasons why you might want to bother
+with <em class="filename">LMHOSTS</em> files. In rare situations, there
+might be no WINS server on the network. Or maybe a WINS server
+exists, but it's unreliable. In both cases, if the
+Windows system has a valid <em class="filename">LMHOSTS</em> file, it can
+help to avoid your network bogging down from those dreaded broadcast
+name queries.</p>
+
+<p>The format of the <em class="filename">LMHOSTS</em> file is simple and
+similar to the <em class="filename">/etc/hosts</em> file with which you
+might be familiar from running Unix systems. Here are the contents of
+a sample <em class="filename">LMHOSTS</em> file:</p>
+
+<blockquote><pre class="code">172.16.1.1      toltec
+172.16.1.2      aztec
+172.16.1.3      mixtec
+172.16.1.4      zapotec
+172.16.1.5      huastec
+172.16.1.6      maya
+172.16.1.7      olmec
+172.16.1.8      chichimec
+172.16.1.11     hopi
+172.16.1.12     zuni
+172.16.1.13     dine
+172.16.1.14     pima
+172.16.1.15     apache
+172.16.1.21     inca
+172.16.1.22     qero</pre></blockquote>
+
+<p>As you can see, the format is like that of
+<em class="filename">/etc/hosts</em>, except that instead of an FQDN
+(e.g., <tt class="literal">toltec.metran.cx</tt>), only a NetBIOS computer
+name (<tt class="literal">toltec</tt>) is given. One way to create an
+<em class="filename">LMHOSTS</em> file for your Windows systems is to copy
+a <em class="filename">/etc/hosts</em> file and edit out the parts you
+don't need. This will work great if your network
+doesn't have a DNS (or NIS) name server and the Unix
+system is dependent on <em class="filename">/etc/hosts</em> for its own
+name service. But if your Unix system is querying a DNS server (which
+is the most frequent case on anything larger than the very smallest
+networks), you would be better advised to look in the DNS
+server's configuration files for your source of
+computer names and IP addresses.</p>
+
+<p>If you do not have administrative access to your
+network's DNS server, you might be able to use tools
+such as <em class="emphasis">nslookup</em><a name="INDEX-30"/>,
+<em class="emphasis">nmap</em><a name="INDEX-31"/>, and
+<em class="emphasis">dig</em><a name="INDEX-32"/> to query the server and obtain the
+information you need.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.4"/>
+
+<h3 class="head3">DNS</h3>
+
+<p>The <a name="INDEX-33"/><a name="INDEX-34"/>DNS
+is responsible for translating human-readable, Internet-style
+hostnames such as <tt class="literal">pima.metran.cx</tt> or
+<tt class="literal">sales.oreilly.com</tt> into IP addresses.</p>
+
+<p>On your first reading of this section, you might be wondering what a
+section on DNS is doing in a book about NetBIOS and SMB networking.
+Remember, we told you that Windows can use more than WINS (NetBIOS
+Name Service) in its strategy for performing name resolution. Because
+DNS is also able to supply IP addresses for simple hostnames (which
+are usually the same as NetBIOS computer names), it can be helpful to
+configure Windows to know about a DNS server on your network. This is
+slightly more important for newer Windows versions than older ones,
+and more so for Windows NT/2000/XP than for Windows 95/98/Me, because
+nowadays Microsoft is focusing more on TCP/IP as the standard
+protocol and DNS as the primary name service.</p>
+
+<p>To find the address of your DNS server, look at the file
+<em class="emphasis">/etc/resolv.conf</em><a name="INDEX-35"/><a name="INDEX-36"/> on your Samba server or any other Unix
+system on the local network that is using DNS. It looks like the
+following:</p>
+
+<blockquote><pre class="code">#resolv.conf 
+domain metran.cx
+nameserver 127.0.0.1 
+nameserver 172.16.1.53</pre></blockquote>
+
+<p>In this example, the first name server in the list is 127.0.0.1,
+which indicates that the Samba server is also a DNS server for this
+LAN.<a name="FNPTR-6"/><a href="#FOOTNOTE-6">[6]</a> In that case, you would use its network IP
+address (not <a name="INDEX-37"/><a name="INDEX-38"/>127.0.0.1, its localhost address)
+for your DNS server when configuring Windows. Otherwise, use the
+other addresses you find in the lines beginning with
+<tt class="literal">nameserver</tt>. Try to select ones on your own
+network. Any name servers listed in
+<em class="emphasis">/etc/resolv.conf</em> should work, but
+you'll get better performance by using a server
+nearby.</p>
+
+<p>All versions of Windows can be configured to know of multiple domain
+name servers, and you might wish to take advantage of this for
+increased reliability. If the first domain name server does not
+respond, Windows can try others in its list.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.5"/>
+
+<h3 class="head3"><em class="filename">HOSTS</em></h3>
+
+<p>Similar to how the <em class="filename">LMHOSTS</em> file can be added to
+supplement WINS, the
+<em class="filename">HOSTS</em><a name="INDEX-39"/> file on a Windows system can be optionally
+added to supplement DNS name resolution. Most of our comments
+regarding <em class="filename">LMHOSTS</em> also apply here.</p>
+
+<p>This time the format of the file is not just similar to that of
+<em class="filename">/etc/hosts</em> found on Unix&mdash;the format is
+<em class="emphasis">exactly</em> the same. You can simply copy
+<em class="filename">/etc/hosts</em> from your Samba server or other Unix
+system to the proper directory on your Windows system.</p>
+
+<p>On Windows 95/98/Me, the <em class="filename">HOSTS</em> file goes in the
+Windows installation directory, which is usually
+<em class="filename">C:\Windows</em>. Note that a file called
+<em class="filename">hosts.sam</em><a name="INDEX-40"/> is already there, which is a sample
+<em class="filename">HOSTS</em> file provided by Microsoft.</p>
+
+<p>On Windows NT/2000/XP, the <em class="filename">HOSTS</em> file goes in
+the <em class="filename">\system32\drivers\etc</em> directory under the
+Windows installation directory, which is usually
+<em class="filename">C:\WINNT</em>.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-1.4"/>
+
+<h3 class="head2">Passwords</h3>
+
+<p><a name="INDEX-41"/><a name="INDEX-42"/><a name="INDEX-43"/>Unix systems use
+username and password pairs to authenticate users either on a local
+system or in an NIS domain. Windows NT/2000/XP are very similar; a
+user supplies his username and password to log on to the local system
+or to a Windows domain.</p>
+
+<p>When the SMB network is set up as a workgroup, things are different.
+There is no domain to log on to, although shares on the network can
+be password-protected. In this case, one password is associated with
+each password-protected share, rather than with individual users.</p>
+
+<p>Samba's default user-level
+<a name="INDEX-44"/>authentication in a workgroup is
+different from that of Windows. To access shares on the Samba host,
+users are required to supply a valid username and password for an
+account on the Samba host. This will be discussed in more detail in
+<a href="ch09.html">Chapter 9</a>.</p>
+
+<p><a name="INDEX-45"/>An unfortunate
+complication arises with passwords. In the first release of Windows
+95 and in Windows NT 4.0 with Service Pack 2 (SP2) or less, as well
+as in all previous versions of Windows, passwords are allowed to be
+sent over the network in plain text. But in Windows 95 with the
+network redirector update,<a name="FNPTR-7"/><a href="#FOOTNOTE-7">[7]</a></p>
+
+<p>Windows NT 4.0 SP3 or later, and all subsequent releases of Windows,
+a registry setting must be <a name="INDEX-46"/><a name="INDEX-47"/><a name="INDEX-48"/>modified to enable plain-text
+passwords. These more modern versions of Windows prefer to send
+encrypted passwords, and if you are working with one of them (and
+don't want to have to modify the registry), you must
+have the line:</p>
+
+<blockquote><pre class="code">encrypt passwords = yes</pre></blockquote>
+
+<p>in the <tt class="literal">[global]</tt> section of your
+<em class="filename">smb.conf</em><a name="INDEX-49"/><a name="INDEX-50"/> file. In addition, you must run the
+command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -a <em class="replaceable">username</em></b></tt></pre></blockquote>
+
+<p>for each user on the Samba host to add their passwords to
+Samba's collection of encrypted passwords. We showed
+you how to do this in <a href="ch02.html">Chapter 2</a>.</p>
+
+<p>If your first attempt to access a Samba share results in a dialog box
+asking for a password for
+<tt class="literal">IPC$</tt><a name="INDEX-51"/><a name="INDEX-52"/>, as shown in <a href="ch03.html#samba2-CHP-3-FIG-1">Figure 3-1</a>, it is probably because you neglected either
+or both of these two steps, and the Samba server did not recognize
+the encrypted password that the Windows system sent to it. Another
+possible dialog box that might come up is the one shown in <a href="ch03.html#samba2-CHP-3-FIG-2">Figure 3-2</a>, which was presented by a Windows 2000 client.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-1"/><img src="figs/sam2_0301.gif"/></div><h4 class="head4">Figure 3-1. Windows 98 asking for IPC$ password</h4>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-2"/><img src="figs/sam2_0302.gif"/></div><h4 class="head4">Figure 3-2. Windows 2000 logon error dialog</h4>
+
+<p>The rest of this chapter is divided into four sections. The first
+section covers setting up Windows 95/98/Me computers, and the rest of
+the sections cover Windows NT 4.0, Windows 2000, and Windows XP
+individually. Each section roughly parallels the order in which
+we've introduced networking concepts in this
+section. You need to read only the section that applies to the
+Windows version with which you are working, and once you have
+finished reading it, you can continue at the beginning of the next
+chapter where we will start covering more advanced Samba features and
+networking issues.</p>
+
+<a name="samba2-CHP-3-NOTE-92"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Keep in mind that we are continuing our example from <a href="ch02.html">Chapter 2</a>, in which we are setting up a very simple
+prototype network using a workgroup that has very lax security. After
+you have the basics working, we recommend you continue with later
+chapters to learn how to implement both better security and a Samba
+domain. <a name="INDEX-53"/></p>
+</blockquote>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-3-SECT-2"/>
+
+<h2 class="head1">Setting Up Windows 95/98/Me Computers</h2>
+
+<p>The <a name="INDEX-54"/>Windows 95/98/Me operating systems are very
+similar to each other, and as far as this chapter is concerned, it is
+possible to treat them with a common set of directions.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-2.1"/>
+
+<h3 class="head2">Setting Up the Network</h3>
+
+<p>Samba uses TCP/IP to communicate with clients on the network, so you
+will need to make sure there is support for TCP/IP on each Windows
+client. Unlike Unix operating systems, Windows does not necessarily
+have support for TCP/IP installed. However, when Windows is installed
+on a computer with a network card or a network card is added to a
+system already running Windows, TCP/IP support is installed by
+default, along with the Client for Microsoft Networks, which supports
+SMB file and printer sharing.</p>
+
+<p>To make sure both services are installed on your Windows system,
+double-click the Network icon in the Control Panel to open the
+Network dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-3">Figure 3-3</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-3"/><img src="figs/sam2_0303.gif"/></div><h4 class="head4">Figure 3-3. The Windows 95/98/Me Network dialog</h4>
+
+<p>You should see at least the Client for Microsoft Networks component
+installed on the system, and hopefully a networking device
+(preferably an Ethernet card) bound to the TCP/IP protocol. If there
+is only one networking hardware device, you'll see
+the TCP/IP protocol listed below the device to which it is bound, as
+shown in <a href="ch03.html#samba2-CHP-3-FIG-1">Figure 3-1</a>.</p>
+
+<p>You might also see &quot;File and printer sharing for
+Microsoft Networks,&quot; which is used to make the
+system into a server. In addition, you might see NetBEUI or Novell
+Networking. Definitely remove NetBEUI unless you are sure you need
+it, and if you don't have any Novell servers on your
+network, you can remove Novell (IPX/SPX) as well. To remove a
+service, simply click its name and then click the Remove button.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.1"/>
+
+<h3 class="head3">Adding TCP/IP</h3>
+
+<p><a name="INDEX-55"/><a name="INDEX-56"/>If
+you don't see TCP/IP listed, you'll
+need to install the protocol.</p>
+
+<p>You can add the protocol by inserting the Windows distribution CD-ROM
+in your CD-ROM drive and clicking the Add button below the component
+window. Indicate that you wish to add a protocol by selecting
+Protocol and clicking &quot;Add...&quot; on
+the following dialog box, which should look similar to <a href="ch03.html#samba2-CHP-3-FIG-4">Figure 3-4</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-4"/><img src="figs/sam2_0304.gif"/></div><h4 class="head4">Figure 3-4. Selecting a component type</h4>
+
+<p>After that, select manufacturer Microsoft, then protocol TCP/IP, as
+shown in <a href="ch03.html#samba2-CHP-3-FIG-3">Figure 3-3</a>, then click OK. After doing so,
+you will be returned to the network dialog. Click OK to close the
+dialog box, and Windows will install the necessary components from
+the CD-ROM and request that the system be rebooted. Go ahead and
+reboot the system, and you're set.</p>
+
+<p>If Client for Microsoft Networks is not in the list, you can add it
+similarly. The only significant difference is that you are adding a
+client instead of a protocol, so make sure to select
+&quot;Client&quot; rather than
+&quot;Protocol&quot; when asked.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.2"/>
+
+<h3 class="head3">Configuring TCP/IP</h3>
+
+<p><a name="INDEX-57"/><a name="INDEX-58"/>If you have more than one networking
+device (for example, both an Ethernet card and a modem for dial-up
+networking), the protocol to hardware bindings will be indicated by
+arrows, as shown in <a href="ch03.html#samba2-CHP-3-FIG-5">Figure 3-5</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-5"/><img src="figs/sam2_0305.gif"/></div><h4 class="head4">Figure 3-5. Selecting a protocol to install</h4>
+
+<p>Select the TCP/IP protocol linked to the networking device that will
+be accessing the Samba network. If you have only one networking
+device, simply click the TCP/IP item. Now click the Properties button
+to open the TCP/IP Properties dialog. You should see something
+similar to <a href="ch03.html#samba2-CHP-3-FIG-6">Figure 3-6</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-6"/><img src="figs/sam2_0306.gif"/></div><h4 class="head4">Figure 3-6. Selecting the correct TCP/IP protocol</h4>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.3"/>
+
+<h3 class="head3">IP Address tab</h3>
+
+<p><a name="INDEX-59"/><a name="INDEX-60"/>The
+IP Address tab is shown in <a href="ch03.html#samba2-CHP-3-FIG-7">Figure 3-7</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-7"/><img src="figs/sam2_0307.gif"/></div><h4 class="head4">Figure 3-7. The IP Address tab</h4>
+
+<p>If you use DHCP on your network to provide IP addresses automatically
+to Windows systems, select the &quot;Obtain an IP address
+automatically&quot; radio button. Otherwise, click the
+&quot;Specify an IP address&quot; radio
+button and enter the client's address and subnet
+mask in the space provided. You or your network manager should have
+selected an address for the client on the same subnet (LAN) as the
+Samba server.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.4"/>
+
+<h3 class="head3">WINS Configuration tab</h3>
+
+<p><a name="INDEX-61"/><a name="INDEX-62"/>If you've
+enabled WINS on Samba or are choosing to make use of another WINS
+server on your network, you must tell Windows the
+server's address. After selecting the WINS
+Configuration tab, you will see the dialog box shown in <a href="ch03.html#samba2-CHP-3-FIG-8">Figure 3-8</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-8"/><img src="figs/sam2_0308.gif"/></div><h4 class="head4">Figure 3-8. The WINS Configuration tab</h4>
+
+<p>This is for Windows 98/Me; Windows 95 is just a little different,
+having separate spaces for the primary and backup WINS server IP
+addresses.</p>
+
+<p>Select the &quot;Enable WINS Resolution&quot;
+radio button, and enter the WINS server's address in
+the space provided, then click the Add button. Do not enter anything
+in the Scope ID field.</p>
+<a name="samba2-CHP-3-NOTE-93"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>A bug in Windows 95/98 sometimes causes the IP address of the WINS
+server to disappear after the OK button is clicked. This happens only
+when only a primary WINS server has been specified. The workaround is
+to fill in the fields for both primary and secondary WINS servers,
+using the same IP address for each.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.5"/>
+
+<h3 class="head3">DNS Configuration tab</h3>
+
+<p><a name="INDEX-63"/><a name="INDEX-64"/>Unless you are using DHCP, you
+will need to provide the IP address of one or more DNS servers. Click
+the DNS tab, then click the &quot;Enable
+DNS&quot; radio button, and type the IP address of one or
+more DNS servers into the appropriate field, shown in <a href="ch03.html#samba2-CHP-3-FIG-9">Figure 3-9</a>, to add the server's address
+to the top DNS Server Search Order field.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-9"/><img src="figs/sam2_0309.gif"/></div><h4 class="head4">Figure 3-9. The DNS Configuration tab</h4>
+
+<p>Also, provide the hostname (which is the same as the NetBIOS computer
+name) of the Windows 95/98/Me computer and your Internet domain. (You
+will need to enter the computer name again later, along with the
+workgroup. Make sure to enter the same name each time.) You can
+safely ignore the Domain Suffix Search Order field for anything
+related to Samba.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.6"/>
+
+<h3 class="head3">LMHOSTS file</h3>
+
+<p><a name="INDEX-65"/><a name="INDEX-66"/>If
+you want to install an <em class="filename">LMHOSTS</em> file, it must be
+placed in your Windows installation directory (usually
+<em class="filename">C:\Windows</em>). In the same directory, Microsoft
+has provided a sample <em class="filename">LMHOSTS</em> file named
+<em class="filename">lmhosts.sam</em>, which you might want to look at for
+further information on the file's format.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.7"/>
+
+<h3 class="head3">NetBIOS tab</h3>
+
+<p><a name="INDEX-67"/><a name="INDEX-68"/>This tab
+appears in Windows 98/Me, but not in Windows 95. All you need to do
+here is make sure the checkbox is checked, enabling NetBIOS over
+TCP/IP. If TCP/IP is your only protocol installed (as we recommended
+earlier), the selection will be grayed out, with the box checked so
+that you couldn't uncheck it even if you wanted to.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.8"/>
+
+<h3 class="head3">Bindings tab</h3>
+
+<p><a name="INDEX-69"/><a name="INDEX-70"/>The
+final tab to look at is Bindings, as shown in <a href="ch03.html#samba2-CHP-3-FIG-10">Figure 3-10</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-10"/><img src="figs/sam2_0310.gif"/></div><h4 class="head4">Figure 3-10. The Bindings tab</h4>
+
+<p>You should have a check beside Client for Microsoft Networks,
+indicating that it's using TCP/IP. If you have
+&quot;File and printer sharing for Microsoft
+Networks&quot; in the dialog, it should also be checked,
+as shown in <a href="ch03.html#samba2-CHP-3-FIG-10">Figure 3-10</a>.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-2.2"/>
+
+<h3 class="head2">Setting the Computer Name and Workgroup</h3>
+
+<p><a name="INDEX-71"/><a name="INDEX-72"/><a name="INDEX-73"/><a name="INDEX-74"/>Finally, click the OK button in the
+TCP/IP configuration dialog, and you'll be taken
+back to the Network Configuration dialog. Then select the
+Identification tab, which will take you to the dialog box shown in
+<a href="ch03.html#samba2-CHP-3-FIG-11">Figure 3-11</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-11"/><img src="figs/sam2_0311.gif"/></div><h4 class="head4">Figure 3-11. The Identification tab</h4>
+
+<p>This is where you set your system's NetBIOS name
+(which Microsoft likes to call &quot;computer
+name&quot;). Usually, it is best to make this the same as
+your DNS hostname, if you are going to have one for this system. For
+example, if the system's DNS name is
+<tt class="literal">huastec.metran.cx</tt>, give the computer a NetBIOS
+name of <tt class="literal">huastec</tt> on this tab.</p>
+
+<p>You also set your workgroup name here. In our case,
+it's METRAN, but if you used a different one in
+<a href="ch02.html">Chapter 2</a>, when creating the Samba configuration
+file, use that instead. Just don't call it WORKGROUP
+(the default workgroup name) or you'll be in the
+same workgroup as every misconfigured Windows computer on the planet!</p>
+
+<p>You can also enter a comment string for this computer. See if you can
+come up with some way of describing it that will remind you of what
+and where it is when you see the comment in a list displayed on
+another computer. Everyone on the network will be able to see your
+comment, so be careful not to include any information that might be
+useful to crackers.</p>
+
+<p>Finally, click the OK button and follow whatever instructions Windows
+provides. (You might have to insert your Windows distribution CD-ROM
+and/or reboot.)</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-2.3"/>
+
+<h3 class="head2">Username and Password</h3>
+
+<p><a name="INDEX-75"/><a name="INDEX-76"/><a name="INDEX-77"/>You have probably already given
+Windows a username and password by now. However, to authenticate with
+the Samba server, your Windows username and password must match with
+a valid account on the Samba server.</p>
+
+<p>It is simple to add a new user and password to a Windows 95/98/Me
+system. Just reboot or log out, and when you are prompted for a
+username and password, enter your Unix username and password. (If you
+are using encrypted passwords, you must run
+<em class="emphasis">smbpasswd</em> on the Unix host to enter them into
+Samba's password database, if you have not already
+done so.) You can use this method to add as many users as you want,
+so as to allow more than one user to use the Windows system to gain
+access to the Samba shares.</p>
+
+<p>If you mistakenly entered the wrong password or your Unix password
+changes, you can change your password on the Windows system by going
+to the Control Panel and double-clicking the Passwords icon. This
+will bring up the Passwords Properties dialog. Click the Change
+Passwords tab, and you will see the dialog shown in <a href="ch03.html#samba2-CHP-3-FIG-12">Figure 3-12</a>. Now click the &quot;Change
+Windows Password...&quot; button, which will bring up the
+Change Windows Password dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-13">Figure 3-13</a>. As indicated by the text entry fields in the
+dialog, enter your old password, and then the new password, and again
+to confirm it. Click the OK button and then the Close button on the
+Password Properties dialog box. Reboot or log out, and use your new
+password when you log in again.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-12"/><img src="figs/sam2_0312.gif"/></div><h4 class="head4">Figure 3-12. The Password Properties dialog</h4>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-13"/><img src="figs/sam2_0313.gif"/></div><h4 class="head4">Figure 3-13. The Change Windows Password dialog</h4>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.1"/>
+
+<h3 class="head3">Logging in for the first time</h3>
+
+<p>If you don't have a Change Passwords tab in the
+Passwords Properties window, it is because networking is not fully
+set up yet. Assuming you've followed all the
+directions given so far, you just need to reboot; when the system
+comes up, it will ask you to log in with a username and a password.</p>
+
+<p>Now for the big moment. Your Samba server is running, and you have
+set up your Windows 95/98/Me client to communicate with it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.2"/>
+
+<h3 class="head3">Accessing the Samba Server from Windows 95/98</h3>
+
+<p><a name="INDEX-78"/><a name="INDEX-79"/>Double-click the Network Neighborhood
+icon on the desktop. You should see your Samba server listed as a
+member of the workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-14">Figure 3-14</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-14"/><img src="figs/sam2_0314.gif"/></div><h4 class="head4">Figure 3-14. Windows 95/98 Network Neighborhood</h4>
+
+<p>Double-clicking the server name will show the resources that the
+server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-15">Figure 3-15</a> (in this case, the <em class="emphasis">test</em>
+directory).</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-15"/><img src="figs/sam2_0315.gif"/></div><h4 class="head4">Figure 3-15. The test shared folder on the Toltec server</h4>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.3"/>
+
+<h3 class="head3">Accessing the Samba Server from Windows Me</h3>
+
+<p>Double-click the My Network Places icon on the desktop. You should
+see the test shared directory as shown in <a href="ch03.html#samba2-CHP-3-FIG-16">Figure 3-16</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-16"/><img src="figs/sam2_0316.gif"/></div><h4 class="head4">Figure 3-16. My Network Places on Windows Me</h4>
+
+<p>Double-click the Entire Network icon, and you should see an icon for
+your workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-17">Figure 3-17</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-17"/><img src="figs/sam2_0317.gif"/></div><h4 class="head4">Figure 3-17. Entire Network window, showing the Metran workgroup</h4>
+
+<p>Double-clicking the workgroup icon will bring up a window showing
+every computer in the workgroup, which should include your Samba
+server, as shown in <a href="ch03.html#samba2-CHP-3-FIG-18">Figure 3-18</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-18"/><img src="figs/sam2_0318.gif"/></div><h4 class="head4">Figure 3-18. Computers in Metran workgroup</h4>
+
+<p>Double-click the Samba server's icon, and you will
+get a window showing its shared resources (in this case, the test
+directory) as shown in <a href="ch03.html#samba2-CHP-3-FIG-19">Figure 3-19</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-19"/><img src="figs/sam2_0319.gif"/></div><h4 class="head4">Figure 3-19. View of shares on the Toltec server</h4>
+
+<p>If you don't see the server listed, it might be that
+browsing is not working correctly or maybe the server is just taking
+a few minutes to show up in the browse list. In either case, you can
+click the Start button, then select
+&quot;Run...&quot;. This will give you a
+dialog box into which you can type the name of your server and the
+share name <em class="emphasis">test</em> in the Windows UNC format
+<em class="filename">\\</em><em class="replaceable">server</em><em class="filename">\test</em>,
+as we did in <a href="ch01.html">Chapter 1</a>. This should open a window
+on the desktop showing the contents of the folder. If this does not
+work, there is likely a problem with name resolution, and you can try
+using the server's IP address instead of its
+computer name, like this:</p>
+
+<blockquote><pre class="code">\\172.16.1.1\test</pre></blockquote>
+
+<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
+with the network.</p>
+
+<p>If it works, congratulations! Try copying files to and from the
+server using the Windows drag-and-drop functionality. You might be
+pleasantly surprised how seamlessly everything works. <a name="INDEX-80"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-3-SECT-3"/>
+
+<h2 class="head1">Setting Up Windows NT 4.0 Computers</h2>
+
+<p>Configuring <a name="INDEX-81"/>Windows NT
+is a little different than configuring Windows 95/98/Me. To use Samba
+with Windows NT, you will need both the Workstation service and the
+TCP/IP protocol. Both come standard with NT, but
+we'll work through installing and configuring them
+to make sure they are configured correctly.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-3.1"/>
+
+<h3 class="head2">Basic Configuration</h3>
+
+<p><a name="INDEX-82"/>This section presents the steps
+to follow for TCP/IP-related configuration on Windows NT to get it to
+cooperate with Samba. If you need more details on Windows NT network
+administration, refer to Craig <a name="INDEX-83"/>Hunt and Robert Bruce
+<a name="INDEX-84"/>Thompson's
+<em class="citetitle">Windows NT TCP/IP Network Administration
+</em>(O'Reilly), an excellent guide.</p>
+
+<p>You should perform the following steps as the
+<tt class="literal">Administrator</tt> or another user in the
+<tt class="literal">Administrators</tt> group.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.1"/>
+
+<h3 class="head3">Installing the TCP/IP protocol</h3>
+
+<p><a name="INDEX-85"/><a name="INDEX-86"/>From
+the Control Panel, double-click the Network icon, click the Protocols
+tab in the Network dialog box, and look to see if you have the TCP/IP
+protocol installed, as shown in <a href="ch03.html#samba2-CHP-3-FIG-20">Figure 3-20</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-20"/><img src="figs/sam2_0320.gif"/></div><h4 class="head4">Figure 3-20. The Protocols tab</h4>
+
+<p>If the protocol is not installed, you need to add it. Click the Add
+button, which will display the Select Network Protocol dialog box
+shown in <a href="ch03.html#samba2-CHP-3-FIG-21">Figure 3-21</a>. You should immediately see the
+TCP/IP protocol as one of the last protocols listed.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-21"/><img src="figs/sam2_0321.gif"/></div><h4 class="head4">Figure 3-21. Select Network Protocol dialog box</h4>
+
+<p>Select TCP/IP as the protocol and confirm it. If
+possible, install only the TCP/IP protocol. If you see anything other
+than TCP/IP listed in the Protocols tab and it is not a protocol that
+you need, you can remove it. If you try to remove a protocol and get
+an error message saying that the protocol is being used by another
+service, you need to click the Services tab and remove that service
+before you can remove the protocol. For example, to remove the NWLink
+IPX/SPX Compatible Transport protocol, you would need to remove the
+Client Service for Netware first.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.2"/>
+
+<h3 class="head3">Installing the Workstation service</h3>
+
+<p><a name="INDEX-87"/><a name="INDEX-88"/>After installing TCP/IP, click the
+Services tab in the Network dialog, and check that you have a
+Workstation service, as shown at the end of the list in <a href="ch03.html#samba2-CHP-3-FIG-22">Figure 3-22</a>.<a name="FNPTR-8"/><a href="#FOOTNOTE-8">[8]</a></p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-22"/><img src="figs/sam2_0322.gif"/></div><h4 class="head4">Figure 3-22. Network Services tab</h4>
+
+<p>This service is actually the Microsoft Networking Client, which
+allows the computer to access SMB services. The Workstation service
+is mandatory. The service is installed by default on both Windows NT
+Workstation 4.0 and NT Server 4.0. If it's not
+there, you can install it much like TCP/IP. In this case you need to
+click the Add button and then select Workstation Service, as shown in
+<a href="ch03.html#samba2-CHP-3-FIG-23">Figure 3-23</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-23"/><img src="figs/sam2_0323.gif"/></div><h4 class="head4">Figure 3-23. Select Network Service dialog box</h4>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.3"/>
+
+<h3 class="head3">Configuring TCP/IP</h3>
+
+<p><a name="INDEX-89"/><a name="INDEX-90"/>After you've installed
+the Workstation service, return to the Protocols tab and select the
+TCP/IP Protocol entry in the window. Then click the Properties button
+below the window. The Microsoft TCP/IP Protocol dialog will be
+displayed. There are five tabs in the dialog, and you will need to
+work with four of them:</p>
+
+<ul><li>
+<p>IP Address</p>
+</li><li>
+<p>WINS Address</p>
+</li><li>
+<p>DNS</p>
+</li><li>
+<p>Bindings</p>
+</li></ul>
+
+<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.1"/>
+
+<h4 class="head4">IP Address tab</h4>
+
+<p><a name="INDEX-91"/><a name="INDEX-92"/>The IP
+Address tab is shown in <a href="ch03.html#samba2-CHP-3-FIG-24">Figure 3-24</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-24"/><img src="figs/sam2_0324.gif"/></div><h4 class="head4">Figure 3-24. Microsoft TCP/IP Properties dialog for Windows NT</h4>
+
+<p>Select the &quot;Specify an IP address&quot;
+radio button, and enter the computer's IP address
+and netmask in the space provided for the proper adapter (Ethernet
+card). You or your network manager should have selected an address
+for the client on the same subnet (LAN) as the Samba server. For
+example, if the server's address is 172.16.1.1 and
+its network mask is 255.255.255.0, you might use the address
+172.16.1.13 (if it is available) for the NT workstation, along with
+the same netmask. If you use DHCP on your network, select the
+&quot;Obtain an IP Address from a DHCP
+server&quot; button instead.</p>
+
+<p>The gateway field refers to a system typically known as a
+<em class="emphasis">router</em>. If you have routers connecting multiple
+networks, you should enter the IP address of the one on your subnet.
+In our example, the gateway happens to be the same system as the
+Samba server, but they do not by any means have to be the same.</p>
+
+
+</div>
+
+
+
+<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.2"/>
+
+<h4 class="head4">WINS Address tab</h4>
+
+<p><a name="INDEX-93"/><a name="INDEX-94"/>Click the
+WINS Address tab, shown in <a href="ch03.html#samba2-CHP-3-FIG-25">Figure 3-25</a>, and you can
+begin to enter information about name servers. Enter the address of
+your WINS server in the space labeled Primary WINS Server. If your
+Samba server is providing WINS service (in other words, you have the
+line <tt class="literal">wins</tt> <tt class="literal">support</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
+<em class="emphasis">smb.conf</em> file of your Samba server), provide the
+Samba server's IP address here. Otherwise, provide
+the address of another WINS server on your network.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-25"/><img src="figs/sam2_0325.gif"/></div><h4 class="head4">Figure 3-25. The WINS Address tab</h4>
+
+<p>You probably noticed that there is a field here for the network
+adapter. This field must specify the Ethernet adapter on which
+you're running TCP/IP so that WINS will provide name
+service on the correct network. For example, if you have both a LAN
+and a dial-up adapter, make sure you have the LAN's
+network card specified here.</p>
+
+<p>The checkboxes in the lower half of the dialog are for enabling two
+other methods of name resolution that Windows can incorporate into
+its name service. Samba doesn't require either of
+them, but you might want to enable them to increase the reliability
+or functionality of name service for your client. See <a href="ch07.html">Chapter 7</a> for further information on name resolution
+issues.</p>
+
+<p>If you'd like to use a DNS server, select the Enable
+DNS for Windows Resolution checkbox. In addition, you will need to do
+some configuration to allow the Windows system to find the DNS
+server, unless you're using DHCP.</p>
+
+
+</div>
+
+
+
+<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.3"/>
+
+<h4 class="head4">DNS tab</h4>
+
+<p><a name="INDEX-95"/><a name="INDEX-96"/>Click
+the tab for DNS, as shown in <a href="ch03.html#samba2-CHP-3-FIG-26">Figure 3-26</a>. Enter the
+IP addresses for one or more DNS servers in the space provided. Also,
+enter the hostname (which should be the same as the NetBIOS computer
+name). You will enter this again later in another control panel, so
+make sure they match. Finally, enter the DNS domain on which this
+system resides. For example, if your workstation has a domain name
+such as <em class="emphasis">metran.cx</em>, enter it here. You can safely
+ignore the other options.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-26"/><img src="figs/sam2_0326.gif"/></div><h4 class="head4">Figure 3-26. The DNS tab</h4>
+
+
+</div>
+
+
+
+<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.4"/>
+
+<h4 class="head4">The LMHOSTS file</h4>
+
+<p>If you want to install an
+<em class="filename">LMHOSTS</em><a name="INDEX-97"/><a name="INDEX-98"/> file, it
+must be placed in the directory
+<em class="filename">\system32\drivers\etc</em> under your Windows
+installation directory (usually <em class="filename">C:\WINNT</em>). The
+easy way to make sure it gets to the proper location is to use the
+Import LMHOSTS button on the WINS Address tab. (But if you want to do
+it over the network, you will have to do that after file sharing is
+configured!) Remember to click the Enable LMHOSTS Lookup checkbox on
+the WINS Address tab to enable this functionality.</p>
+
+<p>When you are satisfied with your settings for IP Address, WINS
+Address, and DNS, click OK to return to the Network dialog box.</p>
+
+
+</div>
+
+
+
+<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.5"/>
+
+<h4 class="head4">Bindings</h4>
+
+<p><a name="INDEX-99"/><a name="INDEX-100"/>Now click the
+Bindings tab, and check the bindings of network hardware, services,
+and protocols. Set the &quot;Show Bindings
+for&quot; field to &quot;all
+services,&quot; and click all the + buttons in the tree.
+You should see a display similar to <a href="ch03.html#samba2-CHP-3-FIG-27">Figure 3-27</a>,
+which shows that the NetBIOS, Server, and Workstation interface
+services are connected to the WINS client running TCP/IP protocol,
+and that the WINS client is bound to the Ethernet adapter of the
+local area network.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-27"/><img src="figs/sam2_0327.gif"/></div><h4 class="head4">Figure 3-27. The Bindings tab</h4>
+
+<p>You can safely leave the default values for the remainder of the tabs
+in the Network dialog box. Click the OK button to complete the
+configuration. Once the proper files are loaded (if any), you might
+need to reboot for your changes to take effect.</p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-3.2"/>
+
+<h3 class="head2">Computer Name and Workgroup</h3>
+
+<p><a name="INDEX-101"/><a name="INDEX-102"/><a name="INDEX-103"/><a name="INDEX-104"/>The next
+thing you need to do is to give the system a NetBIOS computer name.
+From the Control Panel, double-click the Network icon to open the
+Network dialog box. The first tab in this dialog box should be the
+Identification tab, as illustrated in <a href="ch03.html#samba2-CHP-3-FIG-28">Figure 3-28</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-28"/><img src="figs/sam2_0328.gif"/></div><h4 class="head4">Figure 3-28. The Identification tab</h4>
+
+<p>Here, you need to identify your computer with a name and change the
+default workgroup to the one you specified in the
+<em class="emphasis">smb.conf</em> file of your Samba server. Click the
+Change button below the two text fields. This will open an
+Identification Changes dialog box, where you can set the workgroup
+and the computer name, as shown in <a href="ch03.html#samba2-CHP-3-FIG-29">Figure 3-29</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-29"/><img src="figs/sam2_0329.gif"/></div><h4 class="head4">Figure 3-29. The Identification Changes dialog</h4>
+<a name="samba2-CHP-3-NOTE-94"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>You entered the computer name earlier as a DNS hostname while
+configuring TCP/IP, so be sure that the two names match. The name you
+set here is the NetBIOS name. You're allowed to make
+it different from the TCP/IP hostname, but doing so is usually not a
+good idea. Don't worry that Windows NT forces the
+computer name and the workgroup to be all capital letters;
+it's smart enough to figure out what you mean when
+it connects to the network.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-3.3"/>
+
+<h3 class="head2">Adding a User</h3>
+
+<p><a name="INDEX-105"/><a name="INDEX-106"/>In all
+the previous steps, you were logged into your Windows NT system as
+<tt class="literal">Administrator</tt> or another user in the
+<tt class="literal">Administrators</tt> group. To access resources on the
+Samba server, you will need to have a username and password that the
+Samba server recognizes as valid. Generally, the best way to do this
+is to add a user to your NT system, with the same username and
+password as a user on the Samba host system.</p>
+
+<a name="samba2-CHP-3-NOTE-95"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The directions in this section assume that your network is set up as
+a workgroup. If you have already set up your network as a domain, as
+we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
+follow the instructions here for adding a local user on the Windows
+NT client system. Simply log on to the domain from the client using a
+username and password in Samba's
+<em class="filename">smbpasswd</em> account database, and continue with
+the next section, <a href="ch03.html#samba2-CHP-3-SECT-3.4">Section 3.3.4</a>.</p>
+</blockquote>
+
+<p>To add a new user, open the Start menu, navigate through the Programs
+submenu to Administrative Tools (Common), and select User Manager for
+Domains. Click the User menu and select the first item, Add User...,
+shown in <a href="ch03.html#samba2-CHP-3-FIG-30">Figure 3-30</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-30"/><img src="figs/sam2_0330.gif"/></div><h4 class="head4">Figure 3-30. User Manager for Domains window</h4>
+
+<p>This brings up the New User dialog box shown in <a href="ch03.html#samba2-CHP-3-FIG-31">Figure 3-31</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-31"/><img src="figs/sam2_0331.gif"/></div><h4 class="head4">Figure 3-31. The New User dialog</h4>
+
+<p>Fill it out as shown, using the username and password that were added
+in the previous chapter, and make sure that only the checkbox labeled
+Password Never Expires is checked. (This is not the default!) Click
+the Add button to add the user, and then click the Close button. You
+should now see your new account added to the list in the User Manager
+dialog box.</p>
+
+<p>Now open the Start menu, select Shut Down, and select the
+&quot;Close all programs and log on as a different
+user?&quot; radio button. Click the Yes button, then log
+in as the user you just added.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-3.4"/>
+
+<h3 class="head2">Connecting to the Samba Server</h3>
+
+<p>Now for the big moment. Your <a name="INDEX-107"/><a name="INDEX-108"/>Samba
+server is running, and you have set up your NT client to communicate
+with it. Double-click the Network Neighborhood icon on the desktop,
+and you should see your Samba server listed as a member of the
+workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-32">Figure 3-32</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-32"/><img src="figs/sam2_0332.gif"/></div><h4 class="head4">Figure 3-32. The Windows NT Network Neighborhood</h4>
+
+<p>Double-clicking the server name will show the resources that the
+server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-33">Figure 3-33</a>. In this case, the <em class="filename">test</em>
+directory and the default printer are offered to the Windows NT
+workstation.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-33"/><img src="figs/sam2_0333.gif"/></div><h4 class="head4">Figure 3-33. Shares offered by the Toltec server</h4>
+
+<p>If you don't see the server listed,
+don't panic. Select Run... from the Start menu. A
+dialog box appears that allows you to type the name of your server
+and its share directory in Windows format. For example, you would
+enter
+<em class="filename">\\</em>toltec<em class="filename">\</em><tt class="literal">test</tt>,
+as shown in <a href="ch03.html#samba2-CHP-3-FIG-34">Figure 3-34</a>, and use your
+server's hostname instead of
+&quot;toltec&quot;.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-34"/><img src="figs/sam2_0334.gif"/></div><h4 class="head4">Figure 3-34. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
+
+<p>This will work even if browsing services are not set up right, which
+is a common problem. You can also work around a name-service problem
+by entering the server's IP Address (such as
+172.16.1.1 in our example) instead of the Samba
+server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-35">Figure 3-35</a>. Go back and check your configuration, and if
+things still aren't right, go to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong with the
+network.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-35"/><img src="figs/sam2_0335.gif"/></div><h4 class="head4">Figure 3-35. Opening a shared directory, using the server's IP address in the UNC</h4>
+
+<p>If it works, congratulations! Try copying files to and from the
+server by dragging their icons to and from the folder on the Samba
+share. You might be pleasantly surprised how seamlessly everything
+works. <a name="INDEX-109"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-3-SECT-4"/>
+
+<h2 class="head1">Setting Up Windows 2000 Computers</h2>
+
+<p><a name="INDEX-110"/>Although
+Windows 2000 is based on NT technology and is similar to Windows NT
+in many respects, configuring it for use with Samba is quite
+different.</p>
+
+<p>You should perform the following steps as the
+<tt class="literal">Administrator</tt> or another user in the
+<tt class="literal">Administrators</tt> group.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.1"/>
+
+<h3 class="head2">Networking Components</h3>
+
+<p><a name="INDEX-111"/><a name="INDEX-112"/>Go to the Control Panel and
+double-click the Network and Dial-up Connections icon. You should see
+at least one Local Area Connection icon. If there is more than one,
+identify the one that corresponds to the network adapter that is
+connected to your Samba network. Right-click the Local Area
+Connection icon, and click the Properties button. (Or double-click
+the Local Area Connection icon, and then click the Properties button
+in the dialog box that comes up.) You should now be looking at the
+Local Area Connection Properties dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-36">Figure 3-36</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-36"/><img src="figs/sam2_0336.gif"/></div><h4 class="head4">Figure 3-36. Windows 2000 Local Area Connection Properties dialog</h4>
+
+<p>First of all, you might want to click the Configure button under the
+field for the network adapter, to make sure you see the message
+&quot;This device is working properly&quot;
+in the Device status window. If there is a problem, make sure to
+correct it before continuing. You should also see the message
+&quot;Use this device (enable)&quot; in the
+Device usage field of the dialog box. Make sure to set it this way if
+it is not already. Click OK or Cancel to get back to the Local Area
+Connection Properties dialog box.</p>
+
+<p>You should see at least the following two components:</p>
+
+<ul><li>
+<p>Client for Microsoft Networks</p>
+</li><li>
+<p>Internet Protocol (TCP/IP)</p>
+</li></ul>
+<p>If you do not see either Client for Microsoft Networks or Internet
+Protocol (TCP/IP) in your list, you will need to add them. For
+either, the method is to click the Install... button, click the type
+of component (Client or Protocol), and then click the Add... button.
+Next, click the component you want to add, and click the OK button.
+You should see the component added to the list with the others.</p>
+
+<p>Some components should be removed if you see them in the list:</p>
+
+<ul><li>
+<p>NetBEUI Protocol</p>
+</li><li>
+<p>NWLink NetBIOS</p>
+</li><li>
+<p>NWLink IPX/SPX/NetBIOS Compatible Transport Protocol</p>
+</li><li>
+<p>Client Service for Netware</p>
+</li></ul>
+<p>If you see anything other than TCP/IP listed as a protocol, and it is
+not a protocol that you need, you can remove it. Uninstall NetBEUI,
+unless you are sure you need it, and the other three if you do not
+need to support Netware. If you try to remove a protocol and get an
+error message saying that the protocol is being used by another
+service, you need to remove that service before you can remove the
+protocol. For example, to remove the NWLink IPX/SPX Compatible
+Transport Protocol, you would need to remove the Client Service for
+Netware first.</p>
+
+<p>To remove a component, click the component in the list, click the
+Uninstall button, and then click Yes in the dialog box that pops up.
+In some cases, Windows might need to reboot to put the change into
+effect.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.2"/>
+
+<h3 class="head2">Bindings</h3>
+
+<p><a name="INDEX-113"/><a name="INDEX-114"/>Next to each
+client, service, or protocol listed in the window in the Local Area
+Connections Properties dialog box, you will see a checkbox. Make sure
+the checkbox is checked for both Client for Microsoft Networks and
+Internet Protocol (TCP/IP). The check marks indicate the networking
+components are bound to the network adapter shown at the top of the
+dialog box.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.3"/>
+
+<h3 class="head2">Configuring TCP/IP</h3>
+
+<p><a name="INDEX-115"/><a name="INDEX-116"/>Now click Internet Protocol (TCP/IP),
+and then click Properties to open the Internet Protocol (TCP/IP)
+Properties dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-37">Figure 3-37</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-37"/><img src="figs/sam2_0337.gif"/></div><h4 class="head4">Figure 3-37. Internet Protocol (TCP/IP) Properties dialog</h4>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.1"/>
+
+<h3 class="head3">IP address</h3>
+
+<p><a name="INDEX-117"/><a name="INDEX-118"/>If
+you are using DHCP on your network to assign IP addresses
+dynamically, select the &quot;Obtain IP address
+automatically&quot; radio button. Otherwise, select the
+&quot;Use the following address:&quot; radio
+button, and fill in the computer's IP address and
+netmask in the spaces provided. You or your network manager should
+have selected an address for the client on the same subnet (LAN) as
+the Samba server. For example, if the server's
+address is 172.16.1.1 and its network mask is 255.255.255.0, you
+might use the address 172.16.1.14, if it is available, along with the
+same netmask. You can also fill in the IP address of the default
+gateway.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.2"/>
+
+<h3 class="head3">DNS server</h3>
+
+<p><a name="INDEX-119"/><a name="INDEX-120"/>In
+the lower part of the dialog box, click the &quot;Use the
+following DNS server addresses:&quot; radio button, and
+fill in the IP address of your DNS server.</p>
+
+<p>Now click the Advanced... button to bring up the Advanced TCP/IP
+Settings dialog box, and then click the WINS tab.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.3"/>
+
+<h3 class="head3">WINS server</h3>
+
+<p><a name="INDEX-121"/><a name="INDEX-122"/>Enter the
+address of your WINS server in the space labeled
+&quot;WINS addresses, in order of use:&quot;.
+If your Samba server is providing WINS service (in other words, you
+have the line <tt class="literal">wins</tt> <tt class="literal">service</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
+<em class="emphasis">smb.conf</em> file of your Samba server), provide the
+Samba server's IP address here. Otherwise, provide
+the address of another WINS server on your network.</p>
+
+<p>Near the bottom of the dialog box, select the radio button labeled
+&quot;Enable NetBIOS over TCP/IP&quot;. <a href="ch03.html#samba2-CHP-3-FIG-38">Figure 3-38</a> shows what your Advanced TCP/IP Settings
+dialog box should look like at this point.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-38"/><img src="figs/sam2_0338.gif"/></div><h4 class="head4">Figure 3-38. Advanced TCP/IP Settings dialog, showing WINS tab</h4>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.4"/>
+
+<h3 class="head3">The LMHOSTS file</h3>
+
+<p>If you want to install an
+<em class="filename">LMHOSTS</em><a name="INDEX-123"/><a name="INDEX-124"/> file,
+it must be placed in the <em class="filename">\system32\drivers\etc</em>
+directory under your Windows installation directory (usually
+<em class="filename">C:\WINNT</em> ). The easy way to make sure it gets to
+the proper location is to use the Import LMHOSTS... button on the
+WINS Address tab. (But if you want to do it over the network, you
+will have to do that after file sharing is configured!) Remember to
+click the Enable LMHOSTS Lookup checkbox on the WINS Address tab to
+enable this functionality.</p>
+
+<p>When you are satisfied with your settings for IP Address, WINS
+Address, and DNS, click the OK buttons in each open dialog box to
+complete the configuration. Windows might need to load some files
+from the Windows 2000 distribution CD-ROM, and you might need to
+reboot for your changes to take effect.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.4"/>
+
+<h3 class="head2">Computer and Workgroup Names</h3>
+
+<p><a name="INDEX-125"/><a name="INDEX-126"/><a name="INDEX-127"/><a name="INDEX-128"/>From
+the Control Panel, double-click the System icon to open the System
+Properties dialog box. Click the Network Identification tab, and your
+System Properties dialog box will look similar to <a href="ch03.html#samba2-CHP-3-FIG-39">Figure 3-39</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-39"/><img src="figs/sam2_0339.gif"/></div><h4 class="head4">Figure 3-39. System Properties dialog, showing Network Identification tab</h4>
+
+<p>To give your system computer a name and a workgroup, click the
+Properties button, which will bring up the Identification Changes
+dialog box, as in <a href="ch03.html#samba2-CHP-3-FIG-40">Figure 3-40</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-40"/><img src="figs/sam2_0340.gif"/></div><h4 class="head4">Figure 3-40. Identification Changes dialog</h4>
+
+<p>You need to identify your computer with a name and change the
+workgroup to the one you specified in the
+<em class="emphasis">smb.conf</em> file of your Samba server.
+Don't worry that Windows forces the computer name
+and the workgroup to be all capital letters; it's
+smart enough to figure out what you mean when it connects to the
+network.</p>
+
+<p>Click the More... button to bring up the DNS Suffix and NetBIOS
+Computer Name dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-41">Figure 3-41</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-41"/><img src="figs/sam2_0341.gif"/></div><h4 class="head4">Figure 3-41. DNS Suffix and NetBIOS Computer Name dialog</h4>
+
+<p>Enter the DNS domain name of this computer in the text field labeled
+Primary DNS Suffix for this computer:, and then click OK. You should
+now see the FQDN of this system underneath the label
+&quot;Full computer name:&quot;. Click the OK
+button and then reboot when requested to put your configuration
+changes into effect. Once again, log in using your administrative
+account.</p>
+<a name="samba2-CHP-3-NOTE-96"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>There have been reports of authentication problems with Samba when a
+username on a Windows 2000 system is the same as its computer name.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.5"/>
+
+<h3 class="head2">Adding a Samba-Enabled User</h3>
+
+<p><a name="INDEX-129"/><a name="INDEX-130"/>So far,
+you have been logged into your Windows 2000 system as a user in the
+<tt class="literal">Administrators</tt> group. To access resources on the
+Samba server, you will need a username and password that the Samba
+server recognizes as valid. If your administrative account has such a
+username and password, you can use it, but you might want to access
+your system and the network from a nonadministrative user account
+instead.</p>
+<a name="samba2-CHP-3-NOTE-97"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>The directions in this section assume that your network is set up as
+a workgroup. If you have already set up your network as a domain, as
+we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
+follow the instructions here for adding a local user on the Windows
+2000 client system. Simply log on to the domain from the client using
+a username and password in Samba's
+<em class="filename">smbpasswd</em> account database, and continue with
+the next section, <a href="ch03.html#samba2-CHP-3-SECT-4.6">Section 3.4.6</a>.</p>
+</blockquote>
+
+<p>To add a new user, open the Control Panel, and double-click the Users
+and Passwords icon to open the Users and Passwords dialog box, shown
+in <a href="ch03.html#samba2-CHP-3-FIG-42">Figure 3-42</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-42"/><img src="figs/sam2_0342.gif"/></div><h4 class="head4">Figure 3-42. Users and Passwords dialog</h4>
+
+<p>The first thing to do is make sure the checkbox labeled
+&quot;Users must enter a user name and password to use
+this computer.&quot; is checked. Next, click the Add...
+button to bring up the first dialog box of the User Wizard, shown in
+<a href="ch03.html#samba2-CHP-3-FIG-43">Figure 3-43</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-43"/><img src="figs/sam2_0343.gif"/></div><h4 class="head4">Figure 3-43. Adding a new user</h4>
+
+<p>Fill out the fields, using the username of a valid user account on
+the Samba host, and then click the Next &gt; button to enter and
+confirm the user's password. This password must be
+the same as the user's password on the Samba host.
+If you are using encrypted passwords, make sure this username and
+password are the same as what you used when you ran the
+<em class="emphasis">smbpasswd</em> program. Click the Next &gt; button,
+which brings up the final dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-44">Figure 3-44</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-44"/><img src="figs/sam2_0344.gif"/></div><h4 class="head4">Figure 3-44. Specifying a group for the new user</h4>
+
+<p>Pick a group for the user (the default Standard User should do), and
+click the Finish button. You should now see your new account added to
+the list in the Users and Passwords dialog box. Click the OK button
+to complete the process.</p>
+
+<p>Now return to the Users and Passwords control panel window, click the
+Advanced tab, then click on the Advanced button. Click the Users
+folder in the left side of the Local Users and Groups window that
+appears, and then double-click the account you just added in the
+right side of the window. In the Properties window that opens, click
+the checkbox labeled Password never expires. You are done! Click the
+OK buttons in all the dialog boxes, and close all open windows.</p>
+
+<p>Open the Start menu, select Shut Down, and select Log off
+<em class="emphasis">username</em> from the drop-down menu. Click the OK
+button, then log on with the username and password you just added.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-4.6"/>
+
+<h3 class="head2">Connecting to the Samba Server</h3>
+
+<p>Now for the big moment. Your Samba server is running, and you have
+set up your <a name="INDEX-131"/><a name="INDEX-132"/>Windows 2000 client to communicate with
+it. Double-click the My Network Places icon on the desktop, and then
+double-click the Computers Near Me icon to browse the workgroup. You
+should see your Samba server listed as a member of the workgroup, as
+shown in <a href="ch03.html#samba2-CHP-3-FIG-45">Figure 3-45</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-45"/><img src="figs/sam2_0345.gif"/></div><h4 class="head4">Figure 3-45. The Computers Near Me window, showing computers in the workgroup</h4>
+
+<p>Double-clicking the server name will show the resources that the
+server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-46">Figure 3-46</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-46"/><img src="figs/sam2_0346.gif"/></div><h4 class="head4">Figure 3-46. Shares offered by the Toltec server</h4>
+
+<p>In this case, the <em class="filename">test</em> directory and the default
+printer are offered to the Windows 2000 workstation. If you
+don't see the server listed, don't
+panic. Select Run from the Start menu. A dialog box appears that
+allows you to type the name of your server and its share directory in
+Windows format. For example, you would enter
+<em class="filename">\\toltec\</em><tt class="literal">test</tt>, as shown in
+<a href="ch03.html#samba2-CHP-3-FIG-47">Figure 3-47</a>, and use your server's
+hostname instead of &quot;toltec&quot;.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-47"/><img src="figs/sam2_0347.gif"/></div><h4 class="head4">Figure 3-47. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
+
+<p>This will work even if browsing services are not set up right, which
+is a common problem. You can also work around a name-service problem
+by entering the server's IP address (such as
+172.16.1.1 in our example) instead of the Samba
+server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-48">Figure 3-48</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-48"/><img src="figs/sam2_0348.gif"/></div><h4 class="head4">Figure 3-48. Opening a shared directory, using the server's IP address in the UNC</h4>
+
+<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
+with the network.</p>
+
+<p>If it works, congratulations! Try copying files to and from the
+server. You will be pleasantly surprised how seamlessly everything
+works. Now that you've finished setting up the Samba
+server and its clients, you can proceed to the next chapter.
+<a name="INDEX-133"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-3-SECT-5"/>
+
+<h2 class="head1">Setting Up Windows XP Computers</h2>
+
+<p>Although <a name="INDEX-134"/>Windows XP
+is very similar to Windows 2000, it has a very different user
+interface, and there are a number of subtle differences. For example,
+getting to the Control Panel is different than in any previous
+version of Windows&mdash;one must click the Control Panel item from
+the Start menu (there is no Settings item in the Start menu in XP).
+By default, XP will display the Control Panel in Category View mode.
+If you see this, click the Switch to Classic View item in the
+upper-left corner of the window. All of our directions are for using
+the Control Panel in Classic View mode.</p>
+
+<p>You should perform the following steps as the
+<tt class="literal">Administrator</tt> or another user in the
+Administrators group.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-5.1"/>
+
+<h3 class="head2">Networking Components</h3>
+
+<p><a name="INDEX-135"/><a name="INDEX-136"/>Go to the Control Panel and
+double-click the Network and Dial-up Connections icon. You should see
+at least one Local Area Connection icon. If there is more than one,
+identify the one that corresponds to the network adapter that is
+connected to your Samba network. Right-click the Local Area
+Connection icon and click the Properties button. (Or double-click the
+Local Area Connection icon and then click the Properties button in
+the dialog box that comes up.) You should now be looking at the Local
+Area Connection Properties dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-49">Figure 3-49</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-49"/><img src="figs/sam2_0349.gif"/></div><h4 class="head4">Figure 3-49. The Local Area Connection Properties dialog</h4>
+
+<p>First of all, you might want to click the Configure button under the
+field for the network adapter to make sure you see the message
+&quot;This device is working properly&quot;
+in the Device status window. If there is a problem, make sure to
+correct it before continuing. You should also see the message
+&quot;Use this device (enable)&quot; in the
+Device usage field of the dialog box. Make sure to set it this way if
+it is not already. Click OK or Cancel to close this dialog box, then
+reopen the Local Area Connection Properties dialog box.</p>
+
+<p>You should see at least the following two components:</p>
+
+<ul><li>
+<p>Client for Microsoft Networks</p>
+</li><li>
+<p>Internet Protocol (TCP/IP)</p>
+</li></ul>
+<p>If you do not see either Client for Microsoft Networks or Internet
+Protocol (TCP/IP) in your list, you will need to add them. For
+either, the method is to click the Install... button, click the type
+of component (Client or Protocol), and then click the Add... button.
+Next, click the component you want to add, and click the OK button.
+You should see the component added to the list with the others.</p>
+
+<p>If you see anything other than TCP/IP listed as a protocol, and it is
+not a protocol that you need, you can remove it. If NetBEUI appears
+in the list, uninstall it if you possibly can. Also uninstall any
+Netware-related components if you do not need to support Netware. If
+you try to remove a protocol and get an error message saying that the
+protocol is being used by another service, you need to remove that
+service before you can remove the protocol. For example, to remove
+the NWLink IPX/SPX Compatible Transport Protocol, you would need to
+remove the Client Service for Netware first.</p>
+
+<p>To remove a component, click the component in the list, click the
+Uninstall button, and then click Yes in the dialog box that pops up.
+In some cases, Windows might need to reboot to put the change into
+effect.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-5.1.1"/>
+
+<h3 class="head3">Bindings</h3>
+
+<p><a name="INDEX-137"/><a name="INDEX-138"/>Next to each client, service, or protocol
+listed in the window in the Local Area Connections Properties dialog
+box, you will see a checkbox. Make sure the checkbox is checked for
+both Client for Microsoft Networks and Internet Protocol (TCP/IP).
+The check marks indicate that the networking components are bound to
+the network adapter shown at the top of the dialog box.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-5.2"/>
+
+<h3 class="head2">Configuring TCP/IP</h3>
+
+<p><a name="INDEX-139"/><a name="INDEX-140"/>Now click Internet Protocol
+(TCP/IP) and then click Properties to open the Internet Protocol
+(TCP/IP) Properties dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-50">Figure 3-50</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-50"/><img src="figs/sam2_0350.gif"/></div><h4 class="head4">Figure 3-50. The Internet Protocol (TCP/IP) Properties dialog</h4>
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.1"/>
+
+<h3 class="head3">IP address</h3>
+
+<p><a name="INDEX-141"/><a name="INDEX-142"/>If
+you are using DHCP on your network to assign IP addresses
+dynamically, select the &quot;Obtain IP address
+automatically&quot; radio button. Otherwise, select the
+&quot;Use the following address:&quot; radio
+button, and fill in the computer's IP address and
+netmask in the spaces provided. You or your network manager should
+have selected an address for the client on the same subnet (LAN) as
+the Samba server. For example, if the server's
+address is 172.16.1.1 and its network mask is 255.255.255.0, you
+might use the address 172.16.1.12 (if it is available) along with the
+same netmask. You can also fill in the IP address of the default
+gateway.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.2"/>
+
+<h3 class="head3">DNS server</h3>
+
+<p><a name="INDEX-143"/><a name="INDEX-144"/>In the lower part of the dialog box, click
+the &quot;Use the following DNS server
+addresses:&quot; radio button, and fill in the IP address
+of your DNS server.</p>
+
+<p>Now click the Advanced... button to bring up the Advanced TCP/IP
+Settings dialog box, and then click the WINS tab.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.3"/>
+
+<h3 class="head3">WINS server</h3>
+
+<p><a name="INDEX-145"/><a name="INDEX-146"/>Enter
+the address of your WINS server in the space labeled
+&quot;WINS addresses, in order of use:&quot;.
+If your Samba server is providing WINS service (in other words, you
+have the line <tt class="literal">wins</tt> <tt class="literal">support</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
+<em class="emphasis">smb.conf</em> file of your Samba server), provide the
+Samba server's IP address here. Otherwise, provide
+the address of another WINS server on your network.</p>
+
+<p>Near the bottom of the dialog box, select the radio button labeled
+Enable NetBIOS over TCP/IP. <a href="ch03.html#samba2-CHP-3-FIG-51">Figure 3-51</a> shows what
+your Advanced TCP/IP Settings dialog box should look like at this
+point.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-51"/><img src="figs/sam2_0351.gif"/></div><h4 class="head4">Figure 3-51. The Advanced TCP/IP Settings dialog, showing the WINS tab</h4>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.4"/>
+
+<h3 class="head3">The LMHOSTS file</h3>
+
+<p>If you want to install an
+<em class="filename">LMHOSTS</em><a name="INDEX-147"/><a name="INDEX-148"/> file, it
+must be placed in the <em class="filename">\system32\drivers\etc</em>
+directory under your Windows installation directory (usually
+<em class="filename">C:\WINNT</em> ). The easy way to make sure it gets to
+the proper location is to use the Import LMHOSTS... button on the
+WINS Address tab. (But if you want to do it over the network, you
+will have to do that after file sharing is configured!) Remember to
+click the Enable LMHOSTS Lookup checkbox on the WINS Address tab to
+enable this functionality.</p>
+
+<p>When you are satisfied with your settings for IP Address, WINS
+Address, and DNS, click the OK buttons in each open dialog box (and
+the Close button in the Local Area Connection Properties dialog box)
+to complete the configuration. Windows might need to load some files
+from the Windows XP distribution CD-ROM, and you might need to reboot
+for your changes to take effect.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-5.3"/>
+
+<h3 class="head2">Computer and Workgroup Names</h3>
+
+<p><a name="INDEX-149"/><a name="INDEX-150"/><a name="INDEX-151"/><a name="INDEX-152"/>From the
+Control Panel, double-click the System icon to open the System
+Properties dialog box. Click the Computer Name tab, and your System
+Properties dialog box will look similar to <a href="ch03.html#samba2-CHP-3-FIG-52">Figure 3-52</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-52"/><img src="figs/sam2_0352.gif"/></div><h4 class="head4">Figure 3-52. The System Properties dialog, showing the Computer Name tab</h4>
+
+<p>To give your system computer a name and a workgroup, click the
+Change... button, which will bring up the Computer Name Changes
+dialog box, as in <a href="ch03.html#samba2-CHP-3-FIG-53">Figure 3-53</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-53"/><img src="figs/sam2_0353.gif"/></div><h4 class="head4">Figure 3-53. The Computer Name Changes dialog</h4>
+
+<p>You need to identify your computer with a name and change the
+workgroup to the one you specified in the
+<em class="emphasis">smb.conf</em> file of your Samba server.
+Don't worry that Windows forces the workgroup to be
+all capital letters; it's smart enough to figure out
+what you mean when it connects to the network.</p>
+
+<p>Click the More... button to bring up the DNS Suffix and NetBIOS
+Computer Name dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-54">Figure 3-54</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-54"/><img src="figs/sam2_0354.gif"/></div><h4 class="head4">Figure 3-54. The DNS Suffix and NetBIOS Computer Name dialog</h4>
+
+<p>Enter the DNS domain name of this computer in the text field labeled
+Primary DNS Suffix for this computer:, and then click OK. You should
+now see the FQDN of this system underneath the label Full computer
+name: in the Computer Name Changes dialog box. Click the OK button
+and then reboot when requested to put your configuration changes into
+effect. Once again, log in using your administrative account.</p>
+<a name="samba2-CHP-3-NOTE-98"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>There have been reports of authentication problems with Samba when a
+username on a Windows XP system is the same as its computer name.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-5.4"/>
+
+<h3 class="head2">Adding a Samba-Enabled User</h3>
+
+<p><a name="INDEX-153"/><a name="INDEX-154"/>So far,
+you have been logged into your Windows XP system as a user in the
+Administrators group. To access resources on the Samba server, you
+will need to have a username and password that the Samba server
+recognizes as valid. If your administrative account has such a
+username and password, you can use it, but you might want to access
+your system and the network from a nonadministrative user account
+instead.</p>
+
+<a name="samba2-CHP-3-NOTE-99"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The directions in this section assume that your network is set up as
+a workgroup. If you have already set up your network as a domain, as
+we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
+follow the instructions here for adding a local user on the Windows
+XP client system. Simply log on to the domain from the client using a
+username and password in Samba's
+<em class="filename">smbpasswd</em> account database, and continue with
+the next section, <a href="ch03.html#samba2-CHP-3-SECT-5.5">Section 3.5.5</a>.</p>
+</blockquote>
+
+<p>To add a new user, open the Control Panel, and double-click the Users
+Accounts icon to open the User Accounts window, shown in <a href="ch03.html#samba2-CHP-3-FIG-55">Figure 3-55</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-55"/><img src="figs/sam2_0355.gif"/></div><h4 class="head4">Figure 3-55. The User Accounts window</h4>
+
+<p>Click the Create a new account task, which will bring up the window
+shown in <a href="ch03.html#samba2-CHP-3-FIG-56">Figure 3-56</a>. Enter the username, then click
+the Next &gt; button.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-56"/><img src="figs/sam2_0356.gif"/></div><h4 class="head4">Figure 3-56. Entering the username</h4>
+
+<p>Click the radio button labeled
+&quot;Limited&quot;, as shown in <a href="ch03.html#samba2-CHP-3-FIG-57">Figure 3-57</a>.</p>
+
+<p>Click the Create Account button, and you will see the username you
+added next to a picture at the bottom of the User Accounts window. We
+still need to assign a password to the account. Click the account to
+bring up the &quot;What do you want to change about
+<em class="emphasis">username</em>'s
+account?&quot; window, and then click Create a password.
+Enter the password, and enter it again to confirm it.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-57"/><img src="figs/sam2_0357.gif"/></div><h4 class="head4">Figure 3-57. Setting the account type</h4>
+
+<p>This password must be the same as the user's
+password on the Samba host. If you are using encrypted passwords,
+make sure this username and password are the same as what you used
+when you ran the <em class="emphasis">smbpasswd</em> program. Click the
+Create Password button, and you're done adding the
+account.</p>
+
+<p>Now open the Start menu and click the Log Off button. In the Log Off
+Windows dialog box that pops up, again click the Log Off button. When
+Windows displays the login screen, click the user you just added, and
+type in the password to log in.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-3-SECT-5.5"/>
+
+<h3 class="head2">Connecting to the Samba Server</h3>
+
+<p><a name="INDEX-155"/><a name="INDEX-156"/>Now for
+the big moment. Your Samba server is running, and you have set up
+your Windows XP client to communicate with it. In the Start menu,
+select My Computer<a name="FNPTR-9"/><a href="#FOOTNOTE-9">[9]</a> to open the My Computer window. Click My
+Network Places, in the Other Places box in the left part of the
+window. You should see a folder icon for the
+<em class="filename">test</em> directory, as shown in <a href="ch03.html#samba2-CHP-3-FIG-58">Figure 3-58</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-58"/><img src="figs/sam2_0358.gif"/></div><h4 class="head4">Figure 3-58. The My Network Places window</h4>
+
+<p>Now click View workgroup computers in the Network Tasks box at the
+left of the window. You should see your Samba server listed as a
+member of the workgroup. Double-click its icon, and you will see a
+window that looks like <a href="ch03.html#samba2-CHP-3-FIG-59">Figure 3-59</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-59"/><img src="figs/sam2_0359.gif"/></div><h4 class="head4">Figure 3-59. Shares offered by the Toltec server</h4>
+
+<p>If you don't see the server listed in the workgroup,
+don't panic. Select Run... from the Start menu. A
+dialog box appears that allows you to type the name of your server
+and its share directory in Windows format. For example, you would
+enter <em class="filename">\\toltec\</em><tt class="literal">test</tt>, as shown
+in <a href="ch03.html#samba2-CHP-3-FIG-60">Figure 3-60</a>, and use your
+server's hostname instead of
+&quot;toltec&quot;.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-60"/><img src="figs/sam2_0360.gif"/></div><h4 class="head4">Figure 3-60. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
+
+<p>This will work even if browsing services are not set up right, which
+is a common problem. You can also work around a name-service problem
+by entering the server's IP Address (such as
+172.16.1.1 in our example) instead of the Samba
+server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-61">Figure 3-61</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-3-FIG-61"/><img src="figs/sam2_0361.gif"/></div><h4 class="head4">Figure 3-61. Opening a shared directory, using the server's IP address in the UNC</h4>
+
+<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
+with the network.</p>
+
+<p>If it works, congratulations! Try copying files to and from the
+server by dragging their icons to and from the Samba
+server's <em class="filename">test</em> folder. You might
+be pleasantly surprised how seamlessly everything works. <a name="INDEX-157"/> <a name="INDEX-158"/></p>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> We are
+intentionally omitting device drivers because they are
+hardware-specific, and we assume you are getting installation
+directions from the manufacturer.</p> <a name="FOOTNOTE-2"/>
+<p><a href="#FNPTR-2">[2]</a> Make sure to use the same netmask as all other systems on the
+network. You can find the netmask in use by checking with Unix or
+Windows systems that have already been configured.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> Keep in mind that IP addresses ending
+in .0 are reserved for network addresses and that ones ending in .255
+are for broadcast addresses. These should never be assigned to any
+system on the network.</p> <a name="FOOTNOTE-4"/> <p><a href="#FNPTR-4">[4]</a> To be more explicit about
+this, the system will identify itself to the network as a b-node
+rather than an h-node.</p> <a name="FOOTNOTE-5"/> <p><a href="#FNPTR-5">[5]</a> We put the
+names of the <em class="filename">LMHOSTS</em> and
+<em class="filename">HOSTS</em> files in uppercase for additional
+clarity&mdash;to remind you that we are referring to the files on
+Windows rather than on Unix, and because that's the
+way we see them in other books on Windows. The case of the letters in
+the two names actually does not matter.</p> <a name="FOOTNOTE-6"/> <p><a href="#FNPTR-6">[6]</a> The address 127.0.0.1 is known as the
+<em class="emphasis">localhost</em> address and always refers to itself.
+For example, if you type <tt class="literal">ping</tt>
+<tt class="literal">127.0.0.1</tt> on a Unix server, you should always get
+a response, because you're pinging the host
+itself.</p> <a name="FOOTNOTE-7"/> <p><a href="#FNPTR-7">[7]</a> This update is supplied in
+various update packages issued by Microsoft.</p> <a name="FOOTNOTE-8"/> <p><a href="#FNPTR-8">[8]</a> Notice how in Windows NT,
+some clients are called &quot;services&quot;!
+In these directions, we will conform to Microsoft's
+terminology.</p> <a name="FOOTNOTE-9"/> <p><a href="#FNPTR-9">[9]</a> If there is a My Network Places
+item in the Start menu at this point, you can save yourself a little
+time and just click that. If you don't see it,
+don't worry; it will appear automatically
+later.</p> </blockquote>
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+</body></html>
diff --git a/docs/htmldocs/using_samba/ch04.html b/docs/htmldocs/using_samba/ch04.html
new file mode 100644
index 0000000000..02cc979284
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch04.html
@@ -0,0 +1,2556 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 4. Windows NT Domains</h1>
+
+
+
+<p><a name="INDEX-1"/>In previous
+chapters, we've focused on workgroup networking to
+keep things simple and introduce you to networking with Samba in the
+most painless manner we could find. However, workgroup computing has
+its drawbacks, and for many computing environments, the greater
+security and single logon of the Windows NT domain make it worthwhile
+to spend the extra effort to implement a domain.</p>
+
+<p>In addition to the domain features of
+<a name="INDEX-2"/>that we discussed in <a href="ch01.html">Chapter 1</a>, having a domain makes it possible to use
+<em class="firstterm">logon scripts</em><a name="INDEX-3"/> and <em class="firstterm">roaming profiles
+</em><a name="INDEX-4"/>(also called<em class="firstterm"> roving
+profiles</em><a name="INDEX-5"/>). A logon
+script is a text file of commands that are run during startup, and a
+profile is a collection of information regarding the desktop
+environment, including the contents of the Start menu, icons that
+appear on the desktop, and other characteristics about the GUI
+environment that users are allowed to customize. A roaming profile
+can follow its owner from computer to computer, allowing her to have
+the same familiar interface appear wherever she logs on.</p>
+
+<p>A Windows NT domain offers centralized control over the network.
+<em class="firstterm">Policies</em><a name="INDEX-6"/> can be set up by an administrator to
+define aspects of the users' environment and limit
+the amount of control they have over the network and their computers.
+It is also possible for administrators to perform remote
+administration of the domain controllers from any Windows NT/2000/XP
+workstation.</p>
+
+<p>Samba 2.2 has the ability to act as a primary domain controller,
+supporting domain logons from Windows 95/98/Me/NT/2000/XP computers
+and allowing Windows NT/2000/XP<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> systems to join the domain as domain
+member servers. Samba can also join a domain as a member server,
+allowing the primary domain controller to be a Windows NT/2000 system
+or another Samba server.</p>
+
+<a name="samba2-CHP-4-NOTE-100"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Samba 2.2 does not support <a name="INDEX-7"/><a name="INDEX-8"/><a name="INDEX-9"/>LDAP and <a name="INDEX-10"/>Kerberos authentication of Active
+Directory, so it cannot act as a Windows 2000 Active Directory domain
+controller. However, Samba can be added to an Active Directory domain
+as a member server, with the Windows 2000 domain controllers running
+in either mixed or native mode. The Windows 2000 server (even if it
+is running in native mode) supports the Samba server by acting as a
+<a name="INDEX-11"/><a name="INDEX-12"/>PDC emulator, using the Windows NT
+style of authentication rather than the Kerberos style.</p>
+</blockquote>
+
+<p>If you're adding a Samba server to a network that
+has already been set up, you won't have to decide
+whether to use a workgroup or a domain; you will simply have to be
+compatible with what's already in place. If you do
+have a choice, we suggest you evaluate both workgroup and domain
+computing carefully before rolling out a big installation. You will
+have a lot of work to do if you later need to convert one to the
+other. One last thought on this matter is that Microsoft is
+developing Windows in the direction of increased use of domains and
+is intending that eventually Windows networks be composed solely of
+Active Directory domains. If you implement a Windows NT domain now,
+you'll be in a better position to transition to
+Active Directory later, after Samba has better support for it.</p>
+
+<p>In this chapter, we cover various topics directly related to using
+Samba in a Windows NT domain, including:</p>
+
+<ul><li>
+<p>Configuring and using Samba as the primary domain controller</p>
+</li><li>
+<p>Setting up Windows 95/98/Me systems to log on to the domain</p>
+</li><li>
+<p>Implementing user-level security on Windows 95/98/Me</p>
+</li><li>
+<p>Adding Windows NT/2000/XP systems to the domain</p>
+</li><li>
+<p>Configuring logon scripts, roaming profiles, and system policies</p>
+</li><li>
+<p>Adding a Samba server to a domain as a member server</p>
+</li></ul>
+
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-1"/>
+
+<h2 class="head1">Samba as the Primary Domain Controller</h2>
+
+<p><a name="INDEX-13"/>Samba 2.2
+is able to handle the most desired functions of a primary domain
+controller in a Windows NT domain, handling domain logons and
+authentication for accessing shared resources, as well as supporting
+logon scripts, roaming profiles, and system policies.</p>
+
+<a name="samba2-CHP-4-NOTE-101"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>You will need to use at least Samba 2.2 to ensure that PDC
+functionality for Windows NT/2000/XP clients is present. Prior to
+Samba 2.2, only limited user authentication for NT clients was
+present.</p>
+</blockquote>
+
+<p>In this section, we will show you how to configure Samba as a PDC for
+use with Windows 95/98/Me and Windows NT/2000/XP clients. The two
+groups of Windows versions interact differently within domains, and
+in some cases are supported in slightly different ways. If you know
+you are going to be using only Windows 95/98/Me or Windows
+NT/2000/XP, you can set up Samba to support only that group. However,
+there isn't any harm in supporting both at the same
+time.</p>
+
+<a name="samba2-CHP-4-NOTE-102"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you would like more information on how to set up
+<a name="INDEX-14"/>domains, see the file
+<em class="filename">Samba-PDC-HOWTO.html</em><a name="INDEX-15"/>
+in the <em class="filename">docs/htmldocs</em> directory of the Samba
+source distribution.</p>
+</blockquote>
+
+<p>Samba must be the only domain controller for the domain. Make sure
+that a PDC isn't already active, and that there are
+no backup domain controllers. Samba 2.2 is not able to communicate
+with backup domain controllers, and having domain controllers in your
+domain with unsynchronized data would result in a very dysfunctional
+network.</p>
+
+<a name="samba2-CHP-4-NOTE-103"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Although Samba 2.2 cannot function as, or work with, a Windows NT
+<a name="INDEX-16"/><a name="INDEX-17"/>BDC, it is possible to set up
+another Samba server to act as a backup for a Samba PDC. For further
+information, see the file
+<em class="filename">Samba-BDC-HOWTO.html</em><a name="INDEX-18"/>
+in the <em class="filename">docs/htmldocs</em> directory of the Samba
+source distribution.</p>
+</blockquote>
+
+<p>Configuring Samba to be a PDC is a matter of modifying the
+<em class="filename">smb.conf</em> file, creating some directories, and
+restarting the server.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-1.1"/>
+
+<h3 class="head2">Modifying smb.conf</h3>
+
+<p>First you will need to start with an
+<em class="filename">smb.conf</em><a name="INDEX-19"/><a name="INDEX-20"/> file that correctly configures Samba for
+workgroup computing, such as the one we created in <a href="ch02.html">Chapter 2</a>, and insert the following lines into the
+<tt class="literal">[global]</tt> section:</p>
+
+<blockquote><pre class="code">[global]
+    ; use the name of your Samba server instead of toltec
+    ; and your own workgroup instead of METRAN
+    netbios name = toltec
+    workgroup = METRAN
+    encrypt passwords = yes
+        
+    domain master = yes
+    local master = yes
+    preferred master = yes
+    os level = 65
+
+    security = user
+    domain logons = yes
+    
+    ; logon path tells Samba where to put Windows NT/2000/XP roaming profiles
+    logon path = \\%L\profiles\%u\%m
+    logon script = logon.bat
+
+    logon drive = H:
+    ; logon home is used to specify home directory and
+    ; Windows 95/98/Me roaming profile location
+    logon home = \\%L\%u\.win_profile\%m
+    
+    time server = yes
+
+    ; instead of jay, use the names of all users in the Windows NT/2000/XP
+    ; Administrators group who log on to the domain
+    domain admin group = root jay
+
+    ; the below works on Red Hat Linux - other OSs might need a different command
+    add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u</pre></blockquote>
+
+<p>And after the <tt class="literal">[global]</tt> section, add these three
+new shares:</p>
+
+<blockquote><pre class="code">[netlogon]
+    path = /usr/local/samba/lib/netlogon
+    writable = no
+    browsable = no
+
+[profiles]
+    ; you might wish to use a different directory for your
+    ; Windows NT/2000/XP roaming profiles
+    path = /home/samba-ntprof
+    browsable = no
+    writable = yes
+    create mask = 0600
+    directory mask = 0700
+
+[homes]
+    read only = no
+    browsable = no
+    guest ok = no
+    map archive = yes</pre></blockquote>
+
+<p>Now for the explanation. If you are comparing this example to the
+configuration file presented in <a href="ch02.html">Chapter 2</a>, you
+will notice that the first three parameter settings are similar. We
+start out in the <tt class="literal">[global]</tt> section by setting the
+NetBIOS name of the Samba server. We are using the default, which is
+the DNS hostname, but are being explicit because the NetBIOS name is
+used in UNCs that appear later in <em class="filename">smb.conf</em>. The
+next two lines, setting the workgroup name and choosing to use
+encrypted passwords, are identical to our
+<em class="filename">smb.conf</em> file from <a href="ch02.html">Chapter 2</a>.
+However, things are now a little different: even though it still
+reads &quot;workgroup&quot;, we are actually
+setting the name of the domain. For a workgroup, using encrypted
+passwords is optional; when using a domain, they are required.</p>
+
+<p>The next four lines set up our Samba PDC to handle browsing services.
+The line <tt class="literal">domain</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> causes Samba to be the
+domain master browser, which handles browsing services for the domain
+across multiple subnets if necessary. Although it looks very similar,
+<tt class="literal">local</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> does not cause Samba to
+be the master browser on the subnet, but merely tells it to
+participate in browser elections and allow itself to win. (These two
+lines are yet more default settings that we include to be clear.) The
+next two lines ensure that Samba wins the elections. Setting the
+<tt class="literal">preferred</tt> <tt class="literal">master</tt> parameter
+makes Samba force an election when it starts up. The
+<tt class="literal">os</tt> <tt class="literal">level</tt> parameter is set
+higher than that of any other system, which results in Samba winning
+that election. (At the time of this writing, an <tt class="literal">os</tt>
+level of 65 was sufficient to win over all versions of
+Windows&mdash;but make sure no other Samba server is set higher!) We
+make sure Samba is both the <a name="INDEX-21"/><a name="INDEX-22"/>domain and local master browser
+because Windows NT/2000 PDCs always reserve the domain master browser
+role for themselves and because Windows clients require things to be
+that way to find the primary domain controller. It is possible to
+allow another computer on the network to win the role of local master
+browser, but having the same server act as both domain and local
+masters is simpler and more efficient.</p>
+
+<p>The next two lines in the <tt class="literal">[global]</tt> section set up
+Samba to handle the actual domain logons. We set
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">user</tt> so that Samba will require a username and
+password. This is actually the same as in the workgroup setup we
+covered in <a href="ch01.html">Chapter 1</a> and <a href="ch02.html">Chapter 2</a> because it is the default. The only
+reason we're including it explicitly is to avoid
+confusion: another valid setting is <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">domain</tt>, but that is for
+having another (Windows or Samba) domain controller handle the logons
+and should never be found in the <em class="filename">smb.conf</em> of a
+Samba PDC. The next line, <tt class="literal">domain</tt>
+<tt class="literal">logons</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt>, is what tells Samba we want this server to
+handle domain logons.</p>
+
+<p>Defining a logon path is necessary for supporting
+<a name="INDEX-23"/><a name="INDEX-24"/>roaming profiles for
+Windows NT/2000/XP clients. The UNC
+<tt class="literal">\\%L\profiles\%u</tt> refers to a share held on the
+Samba server where the profiles are kept. The variables
+<tt class="literal">%L</tt> and <tt class="literal">%u</tt> are replaced by Samba
+with the name of the server and the username of the logged on user,
+respectively. The section in <em class="filename">smb.conf</em> defining
+the <tt class="literal">[profiles]</tt> share contains the definition of
+exactly where the profiles are kept on the server.
+We'll get back to this topic a bit later in this
+chapter.</p>
+
+<p>The <tt class="literal">logon</tt> <tt class="literal">script</tt>
+<tt class="literal">=</tt> <tt class="literal">logon.bat</tt> line specifies the
+name of an MS-DOS batch file that will be executed when the client
+logs on to the domain. The path specified here is relative to the
+<tt class="literal">[netlogon]</tt> share that is defined later in the
+<em class="filename">smb.conf</em> file.</p>
+
+<p>The settings of <tt class="literal">logon</tt> <tt class="literal">drive</tt> and
+<tt class="literal">logon</tt> <tt class="literal">home</tt> have a couple of
+purposes. Setting <tt class="literal">logon</tt> <tt class="literal">drive</tt>
+<tt class="literal">=</tt> <tt class="literal">H</tt>: allows the home directory
+of the user to be connected to drive letter H on the client. The
+<tt class="literal">logon</tt> <tt class="literal">home</tt> parameter is set to
+the location of the home directory on the server, and again,
+<tt class="literal">%u</tt> is replaced at runtime by the logged on
+user's username. The home directory is used to store
+roaming profiles for Windows 95/98/Me clients. These parameters tie
+into the <tt class="literal">[homes]</tt> share that we are adding, as we
+will explain a bit later.</p>
+
+<p>Setting <tt class="literal">time</tt> <tt class="literal">server</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> causes Samba to advertise
+itself as a <a name="INDEX-25"/>time service for the network. This is
+optional.</p>
+
+<p>The <tt class="literal">domain</tt> <tt class="literal">admin</tt>
+<tt class="literal">group</tt> parameter exists as a short-term measure in
+Samba 2.2 to give Samba a list of users who have administrative
+privileges in the domain. The list should contain any Samba users who
+log on from Windows NT/2000/XP systems and are members of the
+Administrators or Domain Admins groups, if roaming profiles are to
+work correctly.</p>
+
+<p>The last parameter to add to the <tt class="literal">[global]</tt> section
+is <tt class="literal">add</tt> <tt class="literal">user</tt>
+<tt class="literal">script</tt>, and you will need it only if one or more
+of your clients is a Windows NT/2000/XP system. We will tell you more
+about this in <a href="ch04.html#samba2-CHP-4-SECT-2">Section 4.2</a> later in this chapter.</p>
+
+<p>The rest of the additions to <em class="filename">smb.conf</em> are the
+definitions for three <a name="INDEX-26"/><a name="INDEX-27"/>shares. The
+<tt class="literal">[netlogon]</tt><a name="INDEX-28"/> share is necessary for Samba to
+handle domain logons because Windows clients need to connect to it
+during the logon process and will fail if the share does not exist.
+Other than that, the only function of <tt class="literal">[netlogon]</tt>
+is to be a repository for logon scripts and system-policy files,
+which we shall cover in detail later in this chapter. The path to a
+directory on the Samba server is given, and because the clients only
+read logon scripts and system-policy files from the share, the
+<tt class="literal">writable</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> definition is used to make the share read-only.
+Users do not need to see the share, so we set
+<tt class="literal">browsable</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> to make the share invisible.</p>
+
+<p>The <tt class="literal">[profiles]</tt><a name="INDEX-29"/> share is needed for use with
+Windows NT/2000/XP roaming profiles. The path points to a directory
+on the Samba server where the profiles are kept, and in this case,
+the clients must be able to read and write the profile data. The
+<tt class="literal">create</tt> <tt class="literal">mask</tt> (read and write
+permitted for the owner only) and <tt class="literal">directory</tt>
+<tt class="literal">mask</tt> (read, write, and search permitted for the
+owner only) are set up such that a user's profile
+data can be read and written only by the user and not accessed or
+modified by anyone else.</p>
+
+<p>The <tt class="literal">[homes]</tt><a name="INDEX-30"/> share is necessary for our
+definitions of <tt class="literal">logon</tt> <tt class="literal">drive</tt> and
+<tt class="literal">logon</tt> <tt class="literal">home</tt> to work. Samba uses
+the <tt class="literal">[homes]</tt> share to add the home directory of the
+user (found in <em class="filename">/etc/passwd</em> ) as a share. Instead
+of appearing as &quot;homes&quot;, the share
+will be accessible on the client through a folder having the same
+name as the user's username. We will cover this
+topic in more detail in <a href="ch09.html">Chapter 9</a>.</p>
+
+<p>At this point, you might want to run
+<em class="filename">testparm</em><a name="INDEX-31"/> to check your
+<em class="filename">smb.conf</em> file. <a name="INDEX-32"/><a name="INDEX-33"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-1.2"/>
+
+<h3 class="head2">Creating Directories on the Samba Server</h3>
+
+<p><a name="INDEX-34"/><a name="INDEX-35"/>The
+<tt class="literal">[netlogon]</tt> and <tt class="literal">[profiles]</tt>
+shares defined in our new <em class="filename">smb.conf</em> file
+reference directories on the Samba server, and it is necessary to
+create those directories with the proper permissions:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /usr/local/samba/lib/netlogon</b></tt>
+# <tt class="userinput"><b>chmod 775 /usr/local/samba/lib/netlogon</b></tt>
+# <tt class="userinput"><b>mkdir /home/samba-ntprof</b></tt>
+# <tt class="userinput"><b>chmod 777 /home/samba-ntprof</b></tt></pre></blockquote>
+
+<p>The directory names we use are just examples. You are free to choose
+your own.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-1.3"/>
+
+<h3 class="head2">Restarting the Samba Server</h3>
+
+<p><a name="INDEX-36"/>At this
+point, the only thing left to do is restart the Samba server, and the
+changes will be put into effect:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/etc/rc.d/init.d/smb restart</b></tt></pre></blockquote>
+
+<p>(or use whatever method works on your system, as discussed in <a href="ch02.html">Chapter 2</a>.) The server is now ready to accept domain
+logons. <a name="INDEX-37"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-2"/>
+
+<h2 class="head1">Adding Computer Accounts</h2>
+
+<p>To interact in a domain, a Windows NT/2000/XP system must be a member
+of the domain. <a name="INDEX-38"/>Domain membership is implemented
+using <em class="firstterm">computer
+accounts,</em><a name="INDEX-39"/><a name="INDEX-40"/> which are similar to user
+accounts and allow a domain controller to keep information with which
+to authenticate computers on the network. That is, the domain
+controller must be able to tell if requests that arrive from a
+computer are coming from a computer that it
+&quot;knows&quot; as being part of the
+domain. Each Windows NT/2000/XP system in the domain has a computer
+account in the domain controllers' database, which
+on a Windows NT/2000 hosted domain is the <a name="INDEX-41"/>SAM
+database. Although Samba uses a different method (involving the
+<em class="filename">smbpasswd</em><a name="INDEX-42"/> file), it also treats computer accounts
+similarly to user accounts.</p>
+
+<p>To create a computer account, an administrator configures a Windows
+NT/2000/XP system to be part of the domain. For Samba 2.2, the
+&quot;<a name="INDEX-43"/><a name="INDEX-44"/>domain
+administrator&quot; is the <a name="INDEX-45"/><a name="INDEX-46"/>root account on the Samba
+server, and you will need to run the command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -a root</b></tt></pre></blockquote>
+
+<p>to add the root user to Samba's password database.
+In this case, do not provide <em class="filename">smbpasswd</em> with the
+same password as the actual root account on the server. Create a
+different password to be used solely for creating computer accounts.
+This will reduce the possibility of compromising the root password.</p>
+
+<p>When the computer account is created, two things must happen on the
+Samba server. An entry is added to the <em class="filename">smbpasswd</em>
+file, with a &quot;username&quot; that is the
+NetBIOS name of the computer with a dollar sign
+(<tt class="literal">$</tt>) appended to it. This part is handled by the
+<em class="emphasis">smbpasswd</em> command, and you do not need to
+perform any additional action to implement it.</p>
+
+<p>With Samba 2.2, an entry is also required in the
+<em class="filename">/etc/passwd</em> file<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> to give the computer account a
+user ID (UID) on the Samba server.</p> 
+
+<p>This account will never be used to
+log in to the Unix system, so it should not be given a valid home
+directory or login shell. To make this part work, you must set the
+<tt class="literal">add</tt> <tt class="literal">user</tt>
+<tt class="literal">script</tt> parameter in your Samba configuration file,
+using a command that adds the entry in the proper manner. On our Red
+Hat Linux system, we set <tt class="literal">add</tt>
+<tt class="literal">user</tt> <tt class="literal">script</tt> to:</p>
+
+<blockquote><pre class="code">/usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u</pre></blockquote>
+
+<p>This command adds an entry in <em class="filename">/etc/passwd</em>
+similar to the following:</p>
+
+<blockquote><pre class="code">aztec$:x:505:100::/dev/null:/bin/false</pre></blockquote>
+
+<p>Again, notice that the username ends in a dollar sign. The user
+account shown has a &quot;home
+directory&quot; of <em class="filename">/dev/null</em>, a
+group ID (GID) of 100, and a &quot;login
+shell&quot; of <em class="filename">/bin/false</em>. The
+<em class="emphasis">-M</em> flag in our <em class="emphasis">useradd</em>
+command prevents it from creating the home directory. Samba replaces
+the <tt class="literal">%u</tt> variable in the
+<em class="emphasis">useradd</em> command with the NetBIOS name of the
+computer, including the trailing dollar sign. The basic idea here is
+to create an entry with a valid username and UID. These are the only
+parts that Samba uses. It is important that the UID be unique, not
+also used for other accounts&mdash;especially ones that are
+associated with Samba users.</p>
+
+<p>If you are using some other variety of Unix, you will need to replace
+our <em class="emphasis">useradd</em> command with a command that performs
+the same function on your system. If a command such as
+<em class="emphasis">useradd</em> does not come with your system, you can
+write a shell script yourself that performs the same function. In any
+case, the command should add a password hash that does not correspond
+to any valid password. For example, in the<em class="filename">
+/etc/shadow</em> file of our Linux server, we find the
+following two lines:</p>
+
+<blockquote><pre class="code">jay:%1%zQ7j7ok8$D/IubyRAY5ovM3bTrpUCn1:11566:0:99999:7:::
+zapotec$:!!:11625:0:99999:7:::</pre></blockquote>
+
+<p>The first line is for <tt class="literal">jay</tt>'s user
+account. The second field is the password hash&mdash;the long string
+between the first and second colons. The second line is for the
+computer account of <tt class="literal">zapotec</tt>, a domain member
+server. Its &quot;username&quot; ends with a
+dollar sign (<tt class="literal">$</tt>), and the second field in this case
+has been set to &quot;!!&quot;, which is an
+arbitrary string not produced from any password. Therefore, there is
+no valid password for this account on the Linux host. Just about any
+ASCII string can be used instead of
+&quot;!!&quot;. For example, you could use
+&quot;DISABLED&quot; instead.</p>
+
+<a name="samba2-CHP-4-NOTE-104"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>It is possible to <a name="INDEX-47"/><a name="INDEX-48"/><a name="INDEX-49"/><a name="INDEX-50"/>create the entries for
+<em class="filename">/etc/passwd</em> and <em class="filename">smbpasswd</em>
+manually; however, we suggest this method be used very carefully, and
+only for initial testing, or as a last resort. The reason for this is
+to maintain security. After the computer account has been created on
+the server, the next Windows NT/2000/XP system on the network with a
+matching NetBIOS name to log on to the domain will be associated with
+this account. This allows crackers a window of opportunity to take
+over computer accounts for their own purposes.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-3"/>
+
+<h2 class="head1">Configuring Windows Clients for Domain Logons</h2>
+
+<p><a name="INDEX-51"/>The client-side configuration for Windows
+clients is really simple. All you have to do is switch from workgroup
+to domain networking by enabling domain logons, and in the case of
+Windows NT/2000/XP, also provide the root password you gave
+<em class="filename">smbpasswd</em> for creating computer accounts. This
+results in the Windows NT/2000/XP system becoming a member of the
+domain.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.1"/>
+
+<h3 class="head2">Windows 95/98/Me</h3>
+
+<p><a name="INDEX-52"/><a name="INDEX-53"/>To
+enable domain logons with Windows 95/98/Me, open the Control Panel
+and double-click the Network icon. Then click Client for Microsoft
+Networks, and click the Properties button. At this point, you should
+see a dialog box similar to <a href="ch04.html#samba2-CHP-4-FIG-1">Figure 4-1</a>. Select the
+Logon to Windows Domain checkbox at the top of the dialog box, and
+enter the name of the domain as you have defined it with the
+<tt class="literal">workgroup</tt> parameter in the Samba configuration
+file. Then click OK, and reboot the machine when asked.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-1"/><img src="figs/sam2_0401.gif"/></div><h4 class="head4">Figure 4-1. Configuring a Windows 95/98 client for domain logons</h4>
+<a name="samba2-CHP-4-NOTE-105"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>If <a name="INDEX-54"/>Windows complains that you are already
+logged into the domain, you probably have an active connection to a
+share in the workgroup (such as a mapped network drive). Simply
+disconnect the resource temporarily by right-clicking its icon and
+choosing the Disconnect pop-up menu item.</p>
+</blockquote>
+
+<p>When Windows reboots, you should see the standard logon dialog with
+an addition: a field for a domain. The domain name should already be
+filled in, so simply enter your password and click the OK button. At
+this point, Windows should consult the primary domain controller
+(Samba) to see if the password is correct. (You can check the log
+files if you want to see this in action.) If it worked,
+congratulations! You have properly configured Samba to act as a
+domain controller for Windows 95/98/Me machines, and your client is
+successfully connected.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.2"/>
+
+<h3 class="head2">User-Level Security for Windows 95/98/Me</h3>
+
+<p><a name="INDEX-55"/><a name="INDEX-56"/><a name="INDEX-57"/>Now that you have a primary domain
+controller to authenticate users, you can implement much better
+security for shares that reside on Windows 95/98/Me
+systems.<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a> To enable this functionality, open the
+Control Panel, double-click the Network icon, and click the Access
+Control tab in the dialog box. The window should now look like <a href="ch04.html#samba2-CHP-4-FIG-2">Figure 4-2</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-2"/><img src="figs/sam2_0402.gif"/></div><h4 class="head4">Figure 4-2. Setting user-level access control</h4>
+
+<p>Click the User-level access control radio button, and type in the
+name of your domain in the text area. Click the OK button. If you get
+the dialog box shown in <a href="ch04.html#samba2-CHP-4-FIG-3">Figure 4-3</a>, it means that
+shares are already on the system.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-3"/><img src="figs/sam2_0403.gif"/></div><h4 class="head4">Figure 4-3. Error dialog while changing to user-level access control</h4>
+
+<p>In that case, you might want to cancel the operation and make a
+record of each of the computer's shares, making it
+easier to re-create them, and then redo this part. (To get a list of
+shares, open an MS-DOS prompt window and run the
+<tt class="literal">net</tt> <tt class="literal">view</tt>
+<tt class="literal">\\</tt><em class="replaceable">computer_name</em>
+command.) Otherwise, you will get a message asking you to reboot to
+put the change in configuration into effect.</p>
+
+<p>After rebooting, you can create shares with user-level access
+control. To do this, right-click the folder you wish to share, and
+select Sharing.... This will bring up the Shared Properties dialog
+box, shown in <a href="ch04.html#samba2-CHP-4-FIG-4">Figure 4-4</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-4"/><img src="figs/sam2_0404.gif"/></div><h4 class="head4">Figure 4-4. The Shared Properties dialog</h4>
+
+<p>Click the Shared As: radio button, and give the share a name and
+comment. Then click the Add... button, and you will see the Add Users
+dialog box, shown in <a href="ch04.html#samba2-CHP-4-FIG-5">Figure 4-5</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-5"/><img src="figs/sam2_0405.gif"/></div><h4 class="head4">Figure 4-5. The Add Users dialog</h4>
+
+<p>What has happened is that Windows has contacted the primary domain
+controller (in this case, Samba) and requested a list of domain users
+and groups. You can now select a user or group and add it to one or
+more of the three lists on the righthand side of the window&mdash;for
+Read Only, Full Access, or Custom Control&mdash;by clicking the
+buttons in the middle of the window. When you are done, click the OK
+button. If you added any users or groups to the Custom Control list,
+you will be presented with the Change Access Rights dialog box, shown
+in <a href="ch04.html#samba2-CHP-4-FIG-6">Figure 4-6</a>, in which you can specify the rights
+you wish to allow. Then click the OK button to close the dialog box.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-6"/><img src="figs/sam2_0406.gif"/></div><h4 class="head4">Figure 4-6. The Change Access Rights dialog</h4>
+
+<p>You are now returned to the Shared Properties dialog box, where you
+will see the Name: and Access Rights: columns filled in with the
+permissions that you just created. Click the OK button to finalize
+the process. Remember, you will have to perform these actions on any
+folders that you had previously shared using share-level security.
+<a name="INDEX-58"/><a name="INDEX-59"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.3"/>
+
+<h3 class="head2">Windows NT 4.0</h3>
+
+<p><a name="INDEX-60"/><a name="INDEX-61"/>To
+configure Windows NT for domain logons, log in to the computer as
+Administrator or another user in the Administrators group, open the
+Control Panel, and double-click the Network icon. If it
+isn't already selected, click on the Network
+Identification tab.</p>
+
+<p>Click the Change... button, and you should see the dialog box shown
+in <a href="ch04.html#samba2-CHP-4-FIG-7">Figure 4-7</a>. In this dialog box, you can choose
+to have the Windows NT client become a member of the domain by
+clicking the checkbox marked Domain: in the Member of box. Then type
+in the name of the domain to which you wish the client to log on; it
+should be the same as the one you specified using the
+<tt class="literal">workgroup</tt> parameter in the Samba configuration
+file. Click the checkbox marked Create a Computer Account in the
+Domain, and fill in &quot;root&quot; for the
+text area labeled User Name:. In the Password: text area, fill in the
+root password you gave <em class="emphasis">smbpasswd</em> for creating
+computer accounts.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-7"/><img src="figs/sam2_0407.gif"/></div><h4 class="head4">Figure 4-7. Configuring a Windows NT client for domain logons</h4>
+<a name="samba2-CHP-4-NOTE-106"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>If Windows complains that you are already logged in, you probably
+have an active connection to a share in the workgroup (such as a
+mapped network drive). Disconnect the resource temporarily by
+right-clicking its icon and choosing the Disconnect pop-up menu item.</p>
+</blockquote>
+
+<p>After you press the OK button, Windows should present you with a
+small dialog box welcoming you to the domain. Click the Close button
+in the Network dialog box, and reboot the computer as requested. When
+the system comes up again, the machine will automatically present you
+with a logon screen similar to the one for Windows 95/98/Me clients,
+except that the domain text area has a drop-down menu so that you can
+opt to log on to either the local system or the domain. Make sure
+your domain is selected, and log on to the domain using any
+Samba-enabled user account on the Samba server.</p>
+<a name="samba2-CHP-4-NOTE-107"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Be sure to select the correct domain in the Windows NT logon dialog
+box. Once it is selected, it might take a moment for Windows NT to
+build the list of available domains.</p>
+</blockquote>
+
+<p>After you enter the password, Windows NT should consult the primary
+domain controller (Samba) to see if the password is correct. Again,
+you can check the log files if you want to see this in action. If it
+worked, you have successfully configured Samba to act as a domain
+controller for Windows NT machines. <a name="INDEX-62"/><a name="INDEX-63"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.4"/>
+
+<h3 class="head2">Windows 2000</h3>
+
+<p><a name="INDEX-64"/><a name="INDEX-65"/>To
+configure Windows 2000 for domain logons, log in to the computer as
+Administrator or another user in the Administrators group, open the
+Control Panel, and double-click the System icon to open the System
+Properties dialog box. Click the Network Identification tab, and then
+click the Properties button. You should now see the Identification
+Changes dialog box shown in <a href="ch04.html#samba2-CHP-4-FIG-8">Figure 4-8</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-8"/><img src="figs/sam2_0408.gif"/></div><h4 class="head4">Figure 4-8. The Identification Changes dialog</h4>
+
+<p>Click the radio button labeled
+&quot;Domain:&quot; and fill in the name of
+your domain in the text-entry area. Then click the OK button. This
+will bring up the Domain Username and Password dialog box. Enter
+&quot;root&quot; for the username. For the
+password, use the password that you gave to
+<em class="emphasis">smbpasswd</em> for the root account.</p>
+<a name="samba2-CHP-4-NOTE-108"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>If Windows complains that you are already logged in, you probably
+have an active connection to a share in the workgroup (such as a
+mapped network drive). Disconnect the resource temporarily by
+right-clicking its icon and choosing the Disconnect pop-up menu item.</p>
+</blockquote>
+
+<p>After you press the OK button, Windows should present you with a
+small dialog box welcoming you to the domain. When you click the OK
+button in this dialog box, you will be told that you need to reboot
+the computer. Click the OK button in the System Properties dialog
+box, and reboot the computer as requested. When the system comes up
+again, the machine will automatically present you with a Log On to
+Windows dialog box similar to the one shown in <a href="ch04.html#samba2-CHP-4-FIG-9">Figure 4-9</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-9"/><img src="figs/sam2_0409.gif"/></div><h4 class="head4">Figure 4-9. The Windows 2000 logon window</h4>
+
+<p>If you do not see the Log on to: drop-down menu, click the Options
+&lt;&lt; button and it will appear. Select your domain, rather than
+the local computer, from the menu.</p>
+<a name="samba2-CHP-4-NOTE-109"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Be sure to select the correct domain in the logon dialog box. Once it
+is selected, it might take a moment for Windows to build the list of
+available domains.</p>
+</blockquote>
+
+<p>Enter the username and password of any Samba-enabled user in the User
+name: and Password: fields, and either press the Enter key or click
+the OK button. If it worked, your Windows session will start up with
+no error dialogs. <a name="INDEX-66"/><a name="INDEX-67"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.5"/>
+
+<h3 class="head2">Windows XP Home</h3>
+
+<p><a name="INDEX-68"/>You have our
+condolences if you are trying to use the Home edition of Windows XP
+in a domain environment! Microsoft has omitted support for Windows NT
+domains from Windows XP Home, resulting in a product that is
+ill-suited for use in a domain-based network.</p>
+
+<p>On the client side, Windows XP Home users cannot log on to a Windows
+NT domain. Although it is still possible to access domain resources,
+a username and password must be supplied each time the user connects
+to a resource, rather than the &quot;single
+signon&quot; of a domain logon. Domain features such as
+logon scripts and roaming profiles are not supported.</p>
+
+<p>As a server, Windows XP Home cannot join a Windows NT domain as a
+domain member server. It can serve files and printers, but only using
+share-mode (&quot;workgroup&quot;) security.
+It can't even use user-mode security, as Windows
+95/98/Me can.</p>
+
+<p>Considering these limitations, we do not recommend Windows XP Home
+for any kind of local area network computing.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-3.6"/>
+
+<h3 class="head2">Windows XP Professional</h3>
+
+<p><a name="INDEX-69"/><a name="INDEX-70"/>To configure Windows XP
+Professional for domain logons, log in to the computer as
+Administrator or another user in the Administrators group, open the
+Control Panel in Classic View, and double-click the System icon to
+open the System Properties dialog box. Click the Computer Name tab
+and then click the Change... button. You should now see the Computer
+Name Changes dialog box shown in <a href="ch04.html#samba2-CHP-4-FIG-10">Figure 4-10</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-10"/><img src="figs/sam2_0410.gif"/></div><h4 class="head4">Figure 4-10. The Computer Name Changes dialog</h4>
+
+<p>Click the radio button labeled
+&quot;Domain:&quot;, and fill in the name of
+your domain in the text-entry area. Then click the OK button. This
+will bring up the Domain Username and Password dialog box. Enter
+&quot;root&quot; for the username. For the
+password, use the password that you gave to
+<em class="emphasis">smbpasswd</em> for the root account.</p>
+<a name="samba2-CHP-4-NOTE-110"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>If Windows complains that you are already logged in, you probably
+have an active connection to a share in the workgroup (such as a
+mapped network drive). Disconnect the resource temporarily by
+right-clicking its icon and choosing the Disconnect pop-up menu item.</p>
+</blockquote>
+
+<p>After you press the OK button, Windows should present you with a
+small dialog box welcoming you to the domain. When you click the OK
+button in this dialog box, you will be told that you need to reboot
+the computer to put the changes into effect. Click the OK buttons in
+the dialog boxes to close them, and reboot the computer as requested.
+When the system comes up again, the machine will automatically
+present you with a Log On to Windows dialog box similar to the one
+shown in <a href="ch04.html#samba2-CHP-4-FIG-11">Figure 4-11</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-11"/><img src="figs/sam2_0411.gif"/></div><h4 class="head4">Figure 4-11. The Windows XP logon window</h4>
+
+<p>If you get a dialog box at this point that tells you the domain
+controller cannot be found, the solution is to change a registry
+setting as follows.</p>
+
+<p>Open the Start Menu and click the Run... menu item. In the text area
+in the dialog box that opens, type in
+&quot;regedit&quot; and click the OK button
+to start the Registry Editor. You will be editing the registry, so
+follow the rest of the directions very carefully. Click the
+&quot;<tt class="literal">+</tt>&quot; button next
+to the HKEY_LOCAL_MACHINE folder, and in the contents that open up,
+click the &quot;<tt class="literal">+</tt>&quot;
+button next to the SYSTEM folder. Continue in the same manner to open
+CurrentControlSet, then Services, then Netlogon. (You will have to
+scroll down many times to find Netlogon in the list of services.)
+Then click the Parameters folder, and you will see items appear in
+the right side of the window. Double-click
+&quot;requiresignorseal&quot;, and a dialog
+box will open. In the Value data: text area, change the
+&quot;1&quot; to a
+&quot;0&quot; (zero), and click the OK
+button, which modifies the registry both in memory and on disk. Now
+close the Registry Editor and log off and back on again.</p>
+
+<p>If you do not see the Log on to: drop-down menu, click the Options
+&lt;&lt; button and it will appear. Select your domain from the menu,
+rather than the local computer.</p>
+<a name="samba2-CHP-4-NOTE-111"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Be sure to select the correct domain in the logon dialog box. Once it
+is selected, it might take a moment for Windows to build the list of
+available domains.</p>
+</blockquote>
+
+<p>Enter the username and password of any Samba-enabled user in the User
+name: and Password: fields, and either press the Enter key or click
+the OK button. If it worked, your Windows session will start up with
+no error dialogs. <a name="INDEX-71"/> <a name="INDEX-72"/><a name="INDEX-73"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-4"/>
+
+<h2 class="head1">Logon Scripts</h2>
+
+<p><a name="INDEX-74"/>After a Windows client connects with a
+domain controller (either to authenticate a user, in the case of
+Windows 95/98/Me, or to log on to the domain, in the case of Windows
+NT/2000/XP), the client downloads an MS-DOS batch file to run. The
+domain controller supplies the file assuming one has been made
+available for it. This batch file is the logon script and is useful
+in setting up an initial environment for the user.</p>
+
+<p>In a Unix environment, the ability to run such a script might lead to
+a very complex initialization and deep customization. However, the
+Windows environment is mainly oriented to the GUI, and the
+command-line functions are more limited. Most commonly, the logon
+script is used to run a <em class="emphasis">net</em> command, such as
+<em class="emphasis">net use</em><a name="INDEX-75"/>, to connect a network drive letter,
+like this:</p>
+
+<blockquote><pre class="code">net use T: \\toltec\test</pre></blockquote>
+
+<p>This command will make our <tt class="literal">[test]</tt> share (from
+<a href="ch02.html">Chapter 2</a>) show up as the T: drive in My Computer.
+This will happen automatically, and T: will be available to the user
+at the beginning of her session, instead of requiring her to run the
+<em class="emphasis">net use</em> command or connect the T: drive using
+the Map Network Drive function of Windows Explorer.</p>
+
+<p>Another useful command is:</p>
+
+<blockquote><pre class="code">net use H: /home</pre></blockquote>
+
+<p>which <a name="INDEX-76"/><a name="INDEX-77"/>connects the
+user's home directory to a drive letter (which can
+be H:, as shown here, or some other letter, as defined by
+<tt class="literal">logon</tt> <tt class="literal">drive</tt>). For this to work,
+you must have a <tt class="literal">[homes]</tt> share defined in your
+<em class="filename">smb.conf</em> file.</p>
+
+<p>If you are using <a name="INDEX-78"/><a name="INDEX-79"/>roaming profiles, you should definitely
+have:</p>
+
+<a name="INDEX-80"/><blockquote><pre class="code">net time \\<em class="replaceable">toltec</em> /set /yes</pre></blockquote>
+
+<p>in your logon script. (As usual, replace
+&quot;toltec&quot; with the name of your
+Samba PDC.) This will make sure the clocks of the Windows clients are
+synchronized with the PDC, which is important for roaming profiles to
+work correctly.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-4.1"/>
+
+<h3 class="head2">Creating a Logon Script</h3>
+
+<p><a name="INDEX-81"/>In our
+<em class="filename">smb.conf</em> file, we have the line:</p>
+
+<a name="INDEX-82"/><blockquote><pre class="code">logon script = logon.bat</pre></blockquote>
+
+<p>This defines the location and name of the logon script batch file on
+the Samba server. The path is relative to the
+<tt class="literal">[netlogon]</tt><a name="INDEX-83"/> share, defined later in the
+file like this:</p>
+
+<blockquote><pre class="code">[netlogon]
+    path = /usr/local/samba/lib/netlogon
+    writable = no
+    browsable = no</pre></blockquote>
+
+<p>With this example, the logon script is
+<em class="filename">/user/local/samba/lib/netlogon/logon.bat</em>. We
+include the directives <tt class="literal">writable</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt>, to make sure network
+clients cannot change anything in the <tt class="literal">[netlogon]</tt>
+share, and also <tt class="literal">browsable</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt>, which keeps them from even seeing the share
+when they browse the contents of the server. Nothing in
+<tt class="literal">[netlogon]</tt> should ever be modified by
+nonadministrative users. Also, the permissions on the directory for
+<tt class="literal">[netlogon]</tt> should be set appropriately (no write
+permissions for &quot;other&quot; users), as
+we showed you earlier in this chapter.</p>
+
+<p>Notice also that the extension of our logon script is
+<em class="filename">.bat</em><a name="INDEX-84"/>. Be careful about this&mdash;an extension
+of <em class="filename">.cmd</em><a name="INDEX-85"/> will work for Windows NT/2000/XP clients,
+but will result in errors for Windows 95/98/Me clients, which do not
+recognize <em class="filename">.cmd</em> as an extension for batch files.</p>
+
+<p>Because the logon script will be executed on a Windows system, it
+must be in MS-DOS text-file format, with the end of line composed of
+a carriage return followed by a linefeed. The Unix convention is a
+newline, which is simply a linefeed character, so if you use a Unix
+text editor to create your logon script, you must somehow make it use
+the appropriate characters. With
+<em class="emphasis">vim</em><a name="INDEX-86"/><a name="INDEX-87"/> (a clone of the <em class="emphasis">vi</em>
+editor that is distributed with Red Hat Linux), the method is to
+create a new file and use the command:</p>
+
+<blockquote><pre class="code">:se ff=dos</pre></blockquote>
+
+<p>to set the file format to MS-DOS style before typing in any text.
+With <em class="emphasis">emacs</em><a name="INDEX-88"/>, the same can be done using the command:</p>
+
+<blockquote><pre class="code">^X <em class="replaceable">Enter</em> f dos <em class="replaceable">Enter</em></pre></blockquote>
+
+<p>where <tt class="literal">^X</tt> is a Control-X character and
+<tt class="literal">Enter</tt> is a press of the Enter key. Another method
+is to create a Unix-format file in any text editor and then convert
+it to MS-DOS format using the
+<em class="emphasis">unix2dos</em><a name="INDEX-89"/> program:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>unix2dos unix_file &gt;logon.bat</b></tt></pre></blockquote>
+
+<p>If your system does not have <em class="emphasis">unix2dos</em>,
+don't worry. You can implement it yourself with the
+following two-line Perl script:</p>
+
+<blockquote><pre class="code">#!/usr/bin/perl
+open FILE, $ARGV[0];
+while (&lt;FILE&gt;) { s/$/\r/; print }</pre></blockquote>
+
+<p>Or, you can use Notepad on a Windows system to write your script and
+then drag the logon script over to a folder on the Samba server. In
+any case, you can <a name="INDEX-90"/>check the format of your script using
+the <em class="emphasis">od</em><a name="INDEX-91"/> command, like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>od -c logon.bat</b></tt></pre></blockquote>
+
+<p>You should see output resembling this:</p>
+
+<blockquote><pre class="code">0000000   n  e  t     u  s  e      T   :    \  \  t  o  l
+0000020   t  e  c  \  t  e  s  t  \r  \n
+0000032</pre></blockquote>
+
+<p>The important detail here is that at the end of each line is a
+<tt class="literal">\r</tt> <tt class="literal">\n</tt>, which is a carriage
+return followed by a linefeed.</p>
+
+<p>Our example logon script, containing a single <em class="emphasis">net
+use</em> command, was created and set up in a way that allows
+it to be run successfully on any Windows client, regardless of which
+Windows version is installed on the client and which user is
+authenticating or logging on to the domain. But what if we need to
+have different users, computers, or Windows versions running
+different logon scripts?</p>
+
+<p>One method is to use variables inside the <a name="INDEX-92"/>logon script that cause commands to be
+conditionally executed. For details on how to do this, you can
+consult a reference on batch-file programming for MS-DOS and Windows
+NT command language. One such reference is <em class="citetitle">Windows NT
+System Administration</em>, published by
+O'Reilly.</p>
+
+<p>Windows batch-command language is very limited in functionality.
+Fortunately, Samba also supports a means by which customization can
+be handled. The
+<em class="filename">smb.conf</em><a name="INDEX-93"/><a name="INDEX-94"/> file contains variables that can be
+used to insert (at runtime) the name of the server
+(<tt class="literal">%L</tt><a name="INDEX-95"/>), the username of the person who is
+accessing the server's resources
+(<tt class="literal">%u</tt><a name="INDEX-96"/>), or the computer name of the client
+system (<tt class="literal">%m</tt><a name="INDEX-97"/>). To give an example, if we set up the
+path to the logon script as:</p>
+
+<blockquote><pre class="code">logon script = %u/logon.bat</pre></blockquote>
+
+<p>we would then put a directory for each user in the
+<tt class="literal">[netlogon]</tt> share, with each directory named the
+same as the user's username, and in each directory
+we would put a customized <em class="filename">logon.bat</em> file. Then
+each user would have his own custom logon script. We will give you a
+better example of how to do this kind of thing in the next section,
+<a href="ch04.html#samba2-CHP-4-SECT-5">Section 4.5</a>.</p>
+
+<a name="samba2-CHP-4-NOTE-112"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>For more information on Samba configuration file variables, such as
+the <tt class="literal">%L</tt>, <tt class="literal">%u</tt>, and
+<tt class="literal">%m</tt> variables we just used, see <a href="ch06.html">Chapter 6</a> and <a href="appb.html">Appendix B</a>.</p>
+</blockquote>
+
+<p>When modifying and testing your logon script, don't
+just log off of your Windows session and log back on to make your
+script run. Instead, restart (reboot) your system before logging back
+on. Because Windows often keeps the <tt class="literal">[netlogon]</tt>
+share open across logon sessions, the reboot ensures that Windows and
+Samba have completely released and reconnected the
+<tt class="literal">[netlogon]</tt> share, and the new version of the logon
+script is being run while logging on.</p>
+
+<p>More information regarding <a name="INDEX-98"/>logon scripts can be found in the
+O'Reilly book, <em class="emphasis">Managing Windows NT
+Logons</em>. <a name="INDEX-99"/> <a name="INDEX-100"/><a name="INDEX-101"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-5"/>
+
+<h2 class="head1">Roaming Profiles</h2>
+
+<p><a name="INDEX-102"/>One benefit of the centralized
+authentication of Windows NT domains is that a user
+<a name="INDEX-103"/>can log on from more than just one
+computer. To help users feel more &quot;at
+home&quot; when logged on at a computer other than their
+usual one, Microsoft has added the ability for
+users' personal settings to
+&quot;roam&quot; from one computer to
+another.</p>
+
+<p>All Windows versions can be configured individually for each user of
+the computer. Windows NT/2000/XP supports the ability to handle
+multiple user accounts, and Windows 95/98/Me can be configured for
+use by multiple users, keeping the configuration settings for each
+user separate. Each user can configure the
+computer's settings to her liking, and the system
+saves these settings as the user's
+<em class="firstterm">profile</em>, such that upon logging on to the
+system, the user is presented with her familiar desktop.</p>
+
+<p>Some of the settings, such as folder options or the image used for
+the desktop background, are held in the registry. Others, including
+the documents and folders appearing on the desktop and the contents
+of the Start menu, are stored as folders and files in the filesystem.</p>
+
+<p>When the profile is stored on the local system, it is called a
+<em class="firstterm">local profile</em><a name="INDEX-104"/>. On Windows NT, local profiles are
+stored in <em class="filename">C:\winnt\profiles</em>. On Windows 2000/XP,
+they can be found in <em class="filename">C:\Documents and Settings.
+</em>On Windows 95/98/Me, when configured for a single user
+(the default case), the local profile is scattered in places such as
+the registry and directories such as
+<em class="filename">C:\Windows\Desktop</em> and
+<em class="filename">C:\Windows\Start Menu</em>. When Windows 95/98/Me is
+configured for multiple users, the local profile of the preexisting
+user is moved to a folder in <em class="filename">C:\Windows\Profiles</em>
+that has the same name as the user, and any users that are
+subsequently added to the computer have their local profiles created
+in that directory as well. You can browse through the local profiles
+to see their structure&mdash;each has a <a name="INDEX-105"/><a name="INDEX-106"/><a name="INDEX-107"/><a name="INDEX-108"/><a name="INDEX-109"/>registry file
+(<em class="filename">USER.DAT</em><a name="INDEX-110"/><a name="INDEX-111"/> for Windows 95/98/Me and
+<em class="filename">NTUSER.DAT</em><a name="INDEX-112"/><a name="INDEX-113"/> for Windows NT/2000/XP) and some folders
+that contain shortcuts and documents.</p>
+
+<p>A roaming profile is a user profile that is stored on a server and
+&quot;follows&quot; its owner around the
+network so that when the user logs on to the domain from another
+computer, his profile is downloaded from the server and his familiar
+desktop appears on that computer as well.</p>
+<a name="samba2-CHP-4-NOTE-113"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p><a name="INDEX-114"/>Samba can
+support roaming profiles, and it is a fairly simple matter to
+configure it for them. However, this is one feature that we recommend
+you <em class="emphasis">do not</em> use, at least until you are sure you
+understand roaming profiles well and are very confident that you can
+implement them with no harm incurred. If you want to (or are required
+to) implement roaming profiles for your Windows clients, we suggest
+you first set up a small domain with a Samba server and a few Windows
+clients exclusively for the purposes of research and testing.
+<em class="emphasis">Under no circumstances should you attempt to implement
+roaming profiles in a careless or frivolous manner</em>.</p>
+</blockquote>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.1"/>
+
+<h3 class="head2">How Roaming Profiles work</h3>
+
+<p><a name="INDEX-115"/>We will start out by explaining to you
+how roaming profiles work when set up correctly. You will need a
+clear understanding of them to tell the difference between when they
+are working as they are designed and when they are not. In addition,
+roaming profiles can be a source of confusion for your users in many
+ways, and you should know how to detect when a problem with a client
+is related to roaming profile function or dysfunction.</p>
+
+<a name="samba2-CHP-4-NOTE-114"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p><a name="INDEX-116"/>A definitive source of
+documentation on Windows NT roaming profiles is the Microsoft white
+paper <em class="citetitle">Implementing Policies and Profiles for Windows NT
+4.0</em><a name="INDEX-117"/>, which can be found at
+<a href="http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp">http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp</a>.</p>
+</blockquote>
+
+<p>During the domain logon process, the roaming profile is copied from
+the domain controller and used as a local profile during the
+user's logon session. When the user logs off the
+domain, the local profile is copied back to the domain controller and
+stored as the new roaming profile. When the local profile is changed,
+the server does not receive an update until the user logs off the
+domain or shuts down or reboots the client. The client does not send
+an update to the server during the logon session, and a client does
+not receive an update of a setting changed on another client during a
+logon session. When the user does log off, changes in the
+configuration settings in the local profile are sent to the server,
+and the updates of the roaming profile are available for the next
+logon session.</p>
+
+<p>This simple behavior can lead to unexpected results when users are
+<a name="INDEX-118"/>logged on to the domain
+on more than one client at a time. If a user makes a change to the
+configuration settings on one client and then logs off, the settings
+can result in the roaming profile being modified accordingly. But the
+next client that logs off might cause those changes to be
+overwritten, and if so, the settings from the first client will be
+lost. The behavior of different Windows versions varies with regard
+to this, and we've seen a wide variety of
+behaviors&mdash;not always in alignment with
+Microsoft's documentation or even working the same
+way on separate occasions. Sometimes Windows will refuse to overwrite
+a profile, perhaps giving an &quot;access
+denied&quot; error, and at other times it will seem to
+work while producing odd side effects. A common source of confusion
+is what happens if a file is added to or deleted from the desktop,
+which is by default configured to be part of the profile. A deleted
+file might later reappear, and it is even possible for a file to
+irrecoverably disappear without warning (on Windows 95/98). Or maybe
+a file that is added to the desktop on one client never gets added to
+the roaming profile and fails to propagate to other clients. This
+behavior is somewhat improved on Windows 2000/XP, which attempts to
+merge items into the profile that are added on concurrently logged-on
+clients.</p>
+
+<p>One factor that comes into play is that Windows compares the
+<a name="INDEX-119"/>timestamps of the local and roaming
+profiles and can refuse to overwrite a roaming profile if it is newer
+than the local profile on the client, or vice versa. For this reason,
+it is important to keep the clocks of the Windows clients and the
+Samba PDC synchronized. We have already shown you how to do this,
+using the <em class="emphasis">net time
+\\</em><em class="replaceable">server</em>
+<em class="emphasis">/set</em> <em class="emphasis">/yes</em> command in the
+logon script.</p>
+
+<p><a name="INDEX-120"/>Even when the server and clients are
+correctly configured, a number of things that can happen make things
+seem &quot;broken.&quot; The most common
+occurrence is that some shortcuts on clients other than the one that
+created the roaming profile will not work. These shortcuts can exist
+on the desktop or as items in the Start menu. This behavior is a
+result of applications or files that exist on one computer but not
+others. Windows will display these shortcuts, but if they appear on
+the desktop, they will have a generic icon and will bring up an error
+message if a user double-clicks them.</p>
+
+<a name="samba2-CHP-4-NOTE-115"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Because profiles can and usually do include the contents of the
+desktop and other folders, it is possible for the roaming profile to
+grow to a huge size due to actions of a user, such as creating new
+files on the desktop or copying files there. By default, Internet
+Explorer keeps its disk cache in the <em class="filename">Temporary Internet
+Files</em><a name="INDEX-121"/><a name="INDEX-122"/> folder in the profile and has been
+known to populate this directory with thousands of files. This can
+result in a huge roaming profile that causes network congestion and
+very large delays while users are logging on to the domain. (A fix
+for this can be found in article Q185255 in the Microsoft Knowledge
+Base.)</p>
+</blockquote>
+
+<p>One behavior we've seen a few times is that if, for
+some reason (e.g., a network error or misconfiguration), the roaming
+profile is not available during the logon process, Windows will use
+the local profile on the client instead. When this happens, the user
+might receive an unfamiliar profile, and all the benefits of roaming
+profiles are lost for that logon session.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.2"/>
+
+<h3 class="head2">Configuring Samba for Roaming Profiles</h3>
+
+<p><a name="INDEX-123"/><a name="INDEX-124"/>In an ideal world, different Windows
+versions would share the same roaming profile, allowing users to log
+on to the domain from any Windows client system, ranging from Windows
+95 to Windows XP, and enjoy their familiar settings. It would even be
+possible to be logged on concurrently from multiple clients, and a
+change made to the profile on any of them would quickly propagate to
+all the others. Settings in a roaming profile made on a client that
+didn't apply to another would be handled sanely.</p>
+
+<p>Unfortunately, this scenario does not work in reality, and it is
+important to maintain separate roaming profiles to prevent different
+Windows versions from using or modifying a roaming profile created
+by, and/or in use by, another version.</p>
+
+<p>We do this by using configuration file variables to point to
+different profile directories. If you look at <a href="appb.html#samba2-APP-B-TABLE-1">Table B-1</a> in <a href="appb.html#samba2-APP-B#samba2-APP-B">Appendix B</a>, which shows
+the variables that can be used, you might be tempted to use the
+<a name="INDEX-125"/><tt class="literal">%a</tt> variable, which
+is replaced by the name of the operating system the client is
+running. However, this does not work because all of Windows 95/98/Me
+will be seen as the same operating system, and likewise for Windows
+2000/XP. So, we use <a name="INDEX-126"/><tt class="literal">%m</tt> to get the
+NetBIOS name of the client, and combine that with a symbolic link to
+point to the directory containing the profile for the Windows version
+that particular client is running.</p>
+
+<p>Our additions to <em class="filename">smb.conf</em> that appeared earlier
+in this chapter included the two lines:</p>
+
+<blockquote><pre class="code">logon path = \\%L\profiles\%u\%m
+logon home = \\%L\%u\.win_profile\%m</pre></blockquote>
+
+<p>The first line specifies where the roaming profiles for Windows
+NT/2000/XP clients are kept, and the second line performs the same
+function for Windows 95/98/Me clients. In both cases, the location is
+specified as a UNC, but
+<tt class="literal">logon</tt><a name="INDEX-127"/> <tt class="literal">path</tt> (for Windows
+NT/2000/XP) is specified relative to the
+<tt class="literal">[profiles]</tt> share, while
+<tt class="literal">logon</tt><a name="INDEX-128"/> <tt class="literal">home</tt> (for Windows
+95/98/Me) is specified relative to the user's home
+directory. This is done to comply with Samba's
+emulation of Windows NT/2000 PDC behavior.</p>
+
+<p>The <tt class="literal">logon</tt> <tt class="literal">home</tt> UNC must begin
+by specifying the user's home directory, which in
+our previous example would be <tt class="literal">\\%L\%u</tt>. The
+variable <tt class="literal">%L</tt><a name="INDEX-129"/> expands to the NetBIOS name of the
+server (in this case, toltec), and
+<tt class="literal">%u</tt><a name="INDEX-130"/> expands to the name of the user. This
+must be done to allow the command:</p>
+
+<a name="INDEX-131"/><blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>net use h: /home</b></tt></pre></blockquote>
+
+<p>to function correctly to connect the user's home
+directory to drive letter H: on all Windows clients. (The drive
+letter used for this purpose is defined by <tt class="literal">logon</tt>
+<tt class="literal">drive</tt>.) We add the directory
+<em class="filename">.win_profile</em><a name="INDEX-132"/> to the UNC to put the Windows
+95/98/Me roaming profile in a subdirectory of the
+user's home directory.</p>
+<a name="samba2-CHP-4-NOTE-116"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Note that in both <tt class="literal">logon path</tt> and <tt class="literal">logon
+home</tt>, we absolutely avoid making the profile directory the
+same as the user's home directory, and the directory
+that contains the profile is not used for any other purpose. This is
+because when the roaming profile is updated, all directories and
+files in the roaming-profile directory that are not part of the
+roaming profile are deleted.</p>
+</blockquote>
+
+<p>In the <tt class="literal">logon</tt> <tt class="literal">path</tt> line in
+<em class="filename">smb.conf</em>, we use <tt class="literal">%u</tt> to put
+the profiles directory in a subdirectory in the
+<tt class="literal">[profiles]</tt> share, such that each user gets her own
+directory that holds her roaming profiles.</p>
+
+<p>We define the <tt class="literal">[profiles]</tt> share like this:</p>
+
+<blockquote><pre class="code">[profiles]
+    writable = yes
+    create mask = 0600
+    directory mask = 0700
+    browsable = no
+    path = /home/samba-ntprof</pre></blockquote>
+
+<p>The first four parameters in the previous share definition specify to
+allow roaming profiles to be written with the users'
+permissions, to create files with read and write permissions for the
+owner, and to create directories with read, write, and search
+permissions for the owner and no access allowed for other users. As
+with the <tt class="literal">[netlogon]</tt> share, we set
+<tt class="literal">browsable</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> so that the share will not show up on the
+clients in Windows Explorer.</p>
+
+<p>We've decided to put our Windows NT/2000/XP profiles
+in <em class="filename">/home</em>, the default location of the home
+directories on Linux. This will make it simple to include the roaming
+profiles in backups of the home directories. You can use another
+directory if you like.</p>
+
+<p>Notice that in both <tt class="literal">logon</tt> <tt class="literal">path</tt>
+and <tt class="literal">logon</tt> <tt class="literal">home</tt>, the directory
+we specify ends in <tt class="literal">%m</tt>, which Samba replaces with
+the NetBIOS name of the client. We are using the
+client's computer name to identify indirectly which
+version of Windows it is running.</p>
+
+<p>Initially, the directories you specify to hold the roaming profiles
+will be empty and will become populated as clients log off for the
+first time. (Samba will even create the directories if they do not
+already exist.) At first, the directories will simply contain
+profiles that are identical to the clients' local
+profiles, and we highly recommend that you make a backup at this
+point before things get complicated. A listing of the roaming profile
+directory for user <tt class="literal">iman</tt>, after she has logged off
+from Windows 98 clients <tt class="literal">mixtec</tt> and
+<tt class="literal">pueblo</tt> and Windows Me clients
+<tt class="literal">huastec</tt> and <tt class="literal">navajo</tt>, might look
+something like the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l /home/iman/.win_profile</b></tt>
+total 4
+drwx------    6 iman      iman          4096 Dec  8 18:09 huastec
+drwx------    9 iman      iman          4096 Dec  7 03:47 mixtec
+drwx------   11 iman      iman          4096 Dec  7 03:05 navajo
+drwx------   11 iman      iman          4096 Dec  7 03:05 pueblo</pre></blockquote>
+
+<p>If things were left like this, the clients would not share their
+roaming profiles, so next we change from using separate directories
+to having symbolic links point to common directories:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mv mixtec Win98</b></tt>
+# <tt class="userinput"><b>mv navajo WinMe</b></tt>
+# <tt class="userinput"><b>rm huastec pueblo</b></tt>
+# <tt class="userinput"><b>ln -s Win98 pueblo</b></tt>
+# <tt class="userinput"><b>ln -s WinMe huastec</b></tt>
+# <tt class="userinput"><b>chown iman:iman *</b></tt>
+# <tt class="userinput"><b>ls -l /home/iman/.win_profile</b></tt>
+total 6
+lrwxrwxrwx    1 iman      iman             5 Nov 16 01:40 huastec -&gt; WinMe
+lrwxrwxrwx    1 iman      iman             5 Nov 16 01:40 mixtec -&gt; Win98
+lrwxrwxrwx    1 iman      iman             5 Nov 21 17:24 navajo -&gt; WinMe
+lrwxrwxrwx    1 iman      iman             5 Nov 23 01:16 pueblo -&gt; Win98
+drwx------    9 iman      iman          4096 Dec  7 03:47 Win98
+drwx------   11 iman      iman          4096 Dec  7 03:05 WinMe</pre></blockquote>
+
+<p>Now when <tt class="literal">iman</tt> logs on to the domain from either
+Windows 98 system, the client from which she is logging on will get
+the profile stored in the <em class="filename">Win98</em> directory (that
+started out as her local profile on <tt class="literal">mixtec</tt>). This
+works likewise for the Windows Me clients.</p>
+
+<p>To show a more complete example, here is a listing of a fully
+operational Windows 95/98/Me profiles directory:</p>
+
+<a name="INDEX-133"/><blockquote><pre class="code">$ <tt class="userinput"><b>ls -l /home/jay/.win_profile</b></tt>
+total 12
+lrwxrwxrwx    1 jay      jay             9 Nov 16 22:14 aztec -&gt; /home/jay
+lrwxrwxrwx    1 jay      jay             5 Nov 16 01:40 hopi -&gt; Win95
+lrwxrwxrwx    1 jay      jay             5 Nov 16 01:40 huastec -&gt; WinMe
+lrwxrwxrwx    1 jay      jay             5 Nov 16 01:38 maya -&gt; Win98
+lrwxrwxrwx    1 jay      jay             5 Nov 16 01:40 mixtec -&gt; Win98
+lrwxrwxrwx    1 jay      jay             5 Nov 21 17:24 navajo -&gt; WinMe
+lrwxrwxrwx    1 jay      jay             5 Nov 23 01:16 pueblo -&gt; Win98
+lrwxrwxrwx    1 jay      jay             5 Nov 22 02:06 ute -&gt; Win95
+drwx------    6 jay      jay          4096 Dec  8 18:09 Win95
+drwx------    9 jay      jay          4096 Dec  7 03:47 Win98
+drwx------   11 jay      jay          4096 Dec  7 03:05 WinMe
+lrwxrwxrwx    1 jay      jay             5 Nov 21 22:48 yaqui -&gt; Win98
+lrwxrwxrwx    1 jay      jay             9 Nov 16 22:14 zuni -&gt; /home/jay</pre></blockquote>
+
+<p>Again, the computer name of each client exists in this directory as a
+symbolic link that points to the directory containing the actual
+roaming profile. For example, <tt class="literal">maya</tt>, a client that
+runs Windows 98, has a symbolic link named <em class="filename">maya</em>
+to the <em class="filename">Win98</em> directory. A listing of
+<em class="filename">Win98</em> shows:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l Win98</b></tt>
+total 148
+drwxr-xr-x    3 jay      jay          4096 Nov 23 01:30 Application Data
+drwxr-xr-x    2 jay      jay          4096 Nov 23 01:30 Cookies
+drwxr-xr-x    3 jay      jay          4096 Dec  7 03:47 Desktop
+drwxr-xr-x    3 jay      jay          4096 Nov 23 01:30 History
+drwxr-xr-x    2 jay      jay          4096 Nov 23 01:30 NetHood
+drwxr-xr-x    2 jay      jay          4096 Dec  7 03:47 Recent
+drwxr-xr-x    3 jay      jay          4096 Nov 23 01:30 Start Menu
+-rw-r--r--    1 jay      jay        114720 Dec  7 03:46 USER.DAT</pre></blockquote>
+
+<p>The contents of the <em class="filename">Win95</em> and
+<em class="filename">WinMe</em> directories appear similar and contain
+roaming profiles that work exactly as they should on their respective
+operating systems.</p>
+
+<p>Notice in the previous listing that <em class="filename">aztec</em> and
+<em class="filename">zuni</em> are symbolic links to
+<em class="filename">/home/jay</em>. We've cautioned you
+never to configure a roaming profile directory to be a
+user's home directory, but this is to handle
+something different. The clients <tt class="literal">aztec</tt> and
+<tt class="literal">zuni</tt> are Windows XP systems, which handle
+<tt class="literal">logon</tt> <tt class="literal">home</tt> differently than
+other versions of Windows. We have set <tt class="literal">logon</tt>
+<tt class="literal">home</tt> <tt class="literal">=</tt>
+<tt class="literal">\\%L\%u\</tt>.<tt class="literal">win</tt>
+<tt class="literal">profile</tt>, and all versions of Windows except for
+Windows XP strip off everything after <tt class="literal">\\%L\%u</tt> and
+correctly locate the home directory&mdash;in this case,
+<em class="filename">/home/jay</em>. Windows XP uses the full UNC, so we
+simply add a symbolic link to redirect it to the correct directory to
+get the <em class="emphasis">net use H: /home</em> command to work as it
+should. The roaming profiles for Windows XP systems are not affected
+by this and are kept with the other roaming profiles in the Windows
+NT/2000/XP family, as shown in this listing:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l /home/samba-ntprof/jay</b></tt>
+total 16
+lrwxrwxrwx    1 jay      jay             5 Nov 20 03:45 apache -&gt; Win2K
+lrwxrwxrwx    1 jay      jay             5 Nov 13 12:35 aztec -&gt; WinXP
+lrwxrwxrwx    1 jay      jay             5 Nov 13 12:34 dine -&gt; WinNT
+lrwxrwxrwx    1 jay      jay             5 Nov 24 03:44 inca -&gt; Win2K
+lrwxrwxrwx    1 jay      jay             5 Nov 13 12:34 pima -&gt; Win2K
+drwx------   13 jay      jay          4096 Dec  3 15:24 qero
+drwx------   13 jay      jay          4096 Dec  1 20:31 Win2K
+drwx------   12 jay      jay          4096 Nov 30 17:04 WinNT
+drwx------   13 jay      jay          4096 Nov 20 01:23 WinXP
+lrwxrwxrwx    1 jay      jay             5 Nov 20 06:09 yavapai -&gt; WinXP
+lrwxrwxrwx    1 jay      jay             5 Nov 13 12:34 zapotec -&gt; Win2K
+lrwxrwxrwx    1 jay      jay             5 Nov 13 12:35 zuni -&gt; WinXP</pre></blockquote>
+
+<p>As you can see, we are using a similar method for the Windows
+NT/2000/XP roaming profiles. In the listing,
+<em class="filename">qero</em> is not a symbolic link, but rather a
+directory that holds the roaming profile for <tt class="literal">qero</tt>,
+a Windows 2000 client that has recently been added. We had not
+created a symbolic link called <em class="filename">qero</em> before
+installing Windows 2000, so when jay logged off for the first time,
+Samba created a directory named <em class="filename">qero</em> and copied
+the roaming profile received from the client to the new directory.
+Because this is a separate directory from <em class="filename">Win2K</em>,
+which all other Windows 2000 clients are using to share their roaming
+profiles, the roaming profile for <tt class="literal">qero</tt> works like
+a local profile, except that it is stored on the primary domain
+controller.</p>
+
+<p>This might seem like an odd thing to do, but it has some purpose.
+Sometimes you might wish to isolate a client in this manner,
+especially while the operating system is being installed and
+initially configured. Remember, if that client, with its default
+local profile, is logged off the domain, the local profile will be
+written to the roaming profile directory. If the client were using
+the shared roaming profile directory, the effect could be
+undesirable, to say the least. Using our method, the
+<em class="filename">qero</em> directory can later be renamed to make it
+into an archival backup, or it can just be deleted. Then a new
+symlink named <em class="filename">qero</em> can be created to point to
+the <em class="filename">Win2K</em> directory, and <tt class="literal">qero</tt>
+will share the roaming profile in <em class="filename">Win2K</em> with the
+other Windows 2000 clients.</p>
+
+<p>An alternative method is simply to create the
+<a name="INDEX-134"/>symbolic
+links before the clients are added to the network. After you become
+more comfortable with the way roaming profiles work, you might find
+this method to be simpler and quicker.</p>
+
+<p>Again, we urge you to be careful about letting different versions of
+Windows share the same roaming profile. The method of configuring
+roaming profiles we've shown you here allows you to
+test a configuration for a few clients at a time without affecting
+your whole network of clients. For example, we could install a small
+number of Windows 2000 and Windows XP systems in the domain for
+testing purposes and then create symlinks for them that point to a
+directory called <em class="filename">Win2KXP</em> to find out if sharing
+roaming profiles between our Windows 2000 and Windows XP systems
+meets our expectations. The <em class="filename">Win2KXP</em> directory
+could be created as an empty directory, in which case it would have a
+roaming profile written to it by the first of the clients to log off.
+Or, <em class="filename">Win2KXP</em> could simply be a renamed roaming
+profile directory that was created by one of the clients when it was
+added to the domain. <a name="INDEX-135"/><a name="INDEX-136"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.3"/>
+
+<h3 class="head2">Configuring Windows 95/98/Me for Roaming Profiles</h3>
+
+<p><a name="INDEX-137"/><a name="INDEX-138"/>For roaming profiles to work on
+Windows 95/98/Me clients, all you need to do is change one setting to
+allow each user to have a separate local profile. This has the side
+effect of enabling roaming profiles as well.</p>
+
+<p>Open the Control Panel and double-click the Passwords icon to open
+the Passwords Properties dialog box. Click the User Profiles tab, and
+the dialog box will appear as shown in <a href="ch04.html#samba2-CHP-4-FIG-12">Figure 4-12</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-12"/><img src="figs/sam2_0412.gif"/></div><h4 class="head4">Figure 4-12. The Windows 98 Passwords Properties dialog</h4>
+
+<p>Click the button labeled &quot;Users can customize their
+preferences and desktop settings.&quot; In the User
+profile settings box, you can check the options you prefer. When
+done, click the OK button and reboot as requested. During this first
+reboot, Windows will copy the local profile data to
+<em class="filename">C:\windows\profiles</em> but will not attempt to copy
+the roaming profile from the server. The next time the system is shut
+down, the local profile will be copied to the server, and when
+Windows reboots, it will copy the roaming profile from the server.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.4"/>
+
+<h3 class="head2">Configuring Windows NT/2000/XP for Roaming Profiles</h3>
+
+<p><a name="INDEX-139"/><a name="INDEX-140"/><a name="INDEX-141"/><a name="INDEX-142"/>Roaming profiles are enabled by
+default on Windows NT/2000/XP. In case you would like to check or
+modify your settings, follow these directions.</p>
+
+<p>Make sure you are logged in to the local system as Administrator or
+another user in the Administrators group. Open the Control Panel and
+double-click the System icon. On Windows NT/2000, click the User
+Profiles tab, or on Windows XP, click the Advanced tab and then the
+Settings button in the User Profiles box. You should see the dialog
+box in <a href="ch04.html#samba2-CHP-4-FIG-13">Figure 4-13</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-13"/><img src="figs/sam2_0413.gif"/></div><h4 class="head4">Figure 4-13. The Windows 2000 System Properties, User Profiles tab</h4>
+
+<p>Notice in the figure that there are two entries for the username
+<tt class="literal">jay</tt>. The entry ZAPOTEC\jay refers to the account
+on the local system, and METRAN\jay refers to the domain account.
+Recall that when a user logs on, a drop-down menu in the dialog box
+allows him to log on to a domain or log in to the local system. When
+<tt class="literal">jay</tt> logs in to the local machine, only the local
+profile is used. When logged on to the domain, the configuration
+shown will use the roaming profile. To switch a
+user's profile type for a domain logon account,
+click the account name to select it, then click the Change Type...
+button near the bottom of the dialog box. The Change Profile Type
+dialog box will appear. Click the radio button for either roaming or
+local profile, and then click the OK buttons for each dialog box.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.5"/>
+
+<h3 class="head2">Mandatory Profiles</h3>
+
+<p><a name="INDEX-143"/>With a simple
+modification, a <a name="INDEX-144"/>roaming profile can be made into a
+<a name="INDEX-145"/>mandatory
+profile, which has the quality of being unmodifiable by its owner.
+Mandatory profiles are used in some computing environments to
+simplify administration. The theory is that if users cannot modify
+their profiles, less can go wrong, and it is also possible to use the
+same standardized profile for all users.</p>
+
+<p>In practice, some issues come up. Because the users can still modify
+the configuration settings in their local profile during their logon
+session, confusion can result the next time they log on to the domain
+and discover their changes have been
+&quot;lost.&quot; If the user of a client
+reinstalls an application in a different place, the shortcuts to the
+program on the desktop, in the Start menu, or in a Quick Launch bar
+cannot be permanently deleted. They will reappear every time the user
+logs back on to the domain. Essentially, a mandatory profile is a
+roaming profile that always fails to update to the server upon
+logging off!</p>
+
+<p>Another complication is that different versions of Windows behave
+differently with mandatory profiles. If a user who has a mandatory
+profile creates a new file on her desktop, the file might be missing
+the next time the user logs off and on again or reboots. Some Windows
+versions preserve desktop files in the local profile (even if the
+file does not exist in the mandatory profile), whereas others do not.</p>
+
+<p>To change a <a name="INDEX-146"/><a name="INDEX-147"/>roaming profile to a mandatory
+profile, all you have to do is rename the
+<em class="filename">.dat</em><a name="INDEX-148"/><a name="INDEX-149"/> file in the roaming profile directory
+on the server to have a <em class="filename">.man</em> extension instead.
+For a Windows 95/98/Me roaming profile, you would rename
+<em class="filename">USER.DAT</em> to <em class="filename">USER.MAN</em>, and
+for a Windows NT/2000/XP roaming profile, you would rename
+<em class="filename">NTUSER.DAT</em> to <em class="filename">NTUSER.MAN</em>.
+Also, you might want to make the roaming-profile directory and its
+contents read-only, to make sure that a user can't
+change it by logging into his Unix user account on the Samba host
+system.</p>
+
+<p>If you want to have all your users share a mandatory profile, you can
+change the definitions of <tt class="literal">logon</tt>
+<tt class="literal">path</tt> and <tt class="literal">logon</tt>
+<tt class="literal">home</tt> in your <em class="filename">smb.conf</em> file to
+point to a shared mandatory profile on the server and adjust your
+directory structure and symbolic links accordingly. For example,
+<tt class="literal">logon</tt> <tt class="literal">path</tt> and
+<tt class="literal">logon</tt> <tt class="literal">home</tt> might be defined
+like this:</p>
+
+<blockquote><pre class="code">logon path = \\%L\profiles\%m
+logon home = \\%L\%u\.win_profile\%m</pre></blockquote>
+
+<p>Notice that we've removed the <tt class="literal">%u</tt>
+part of the path for <tt class="literal">logon</tt>
+<tt class="literal">path</tt>, and we would also change the directory
+structure on the server to do away with the separation of the
+profiles by username and have just one profile for each Windows
+NT/2000/XP version.</p>
+
+<p>We cannot use the same treatment for <tt class="literal">logon</tt>
+<tt class="literal">home</tt> because it is also used to specify the home
+directory. In this case, we would change the symbolic links in each
+user's <em class="filename">.win_profile</em> directory
+to point to a common mandatory profile directory containing the
+mandatory profiles for each of Windows 95/98/Me. Again, check the
+ownership and permissions on the files in the directory, and modify
+them if necessary to make sure a user can't modify
+any files by logging into her Unix account on the Samba host system.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-5.6"/>
+
+<h3 class="head2">Logon Script and Roaming-Profile Options</h3>
+
+<p><a href="ch04.html#samba2-CHP-4-TABLE-1">Table 4-1</a> summarizes the options commonly used in
+association with Windows NT domain <a name="INDEX-150"/><a name="INDEX-151"/>logon
+scripts and roaming profiles.</p>
+
+<a name="samba2-CHP-4-TABLE-1"/><h4 class="head4">Table 4-1. Logon-script options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">logon</tt> <tt class="literal">script</tt></p>
+</td>
+<td>
+<p>string (MS-DOS path)</p>
+</td>
+<td>
+<p>Name of logon script batch file</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">logon</tt> <tt class="literal">path</tt></p>
+</td>
+<td>
+<p>string (UNC server and share name)</p>
+</td>
+<td>
+<p>Location of roaming profile</p>
+</td>
+<td>
+<p><tt class="literal">\\%N\%U\profile</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">logon</tt> <tt class="literal">drive</tt></p>
+</td>
+<td>
+<p>string (drive letter)</p>
+</td>
+<td>
+<p>Specifies the logon drive for a home directory</p>
+</td>
+<td>
+<p><tt class="literal">Z</tt>:</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">logon</tt> <tt class="literal">home</tt></p>
+</td>
+<td>
+<p>string (UNC server and share name)</p>
+</td>
+<td>
+<p>Specifies a location for home directories for clients logging on to
+the domain</p>
+</td>
+<td>
+<p><tt class="literal">\\%N\%U</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-5.6.1"/>
+
+<a name="INDEX-152"/><h3 class="head3">logon script</h3>
+
+<p>This option specifies a Windows batch file that will be executed on
+the client after a user has logged on to the domain. Each logon
+script should be stored in the root directory of the
+<tt class="literal">[netlogon]</tt> share or a subdirectory. This option
+frequently uses the <tt class="literal">%U</tt> or <tt class="literal">%m</tt>
+variables (user or NetBIOS name) to point to an individual script.
+For example:</p>
+
+<blockquote><pre class="code">[global]
+    logon script = %U.bat</pre></blockquote>
+
+<p>will execute a script based on the username. If the user who is
+connecting is <tt class="literal">fred</tt> and the path of the
+<tt class="literal">[netlogon]</tt> share maps to the directory
+<em class="filename">/export/samba/netlogon</em>, the script should be
+<em class="filename">/export/samba/netlogon/fred.bat</em>. Because these
+scripts are downloaded to the client and executed on the Windows
+side, they must have MS-DOS-style newline characters rather than Unix
+newlines.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-5.6.2"/>
+
+<a name="INDEX-153"/><h3 class="head3">logon path</h3>
+
+<p>This option specifies the location where roaming profiles are kept.
+When the user logs on, a roaming profile will be downloaded from the
+server to the client and used as the local profile during the logon
+session. When the user logs off, the contents of the local profile
+will be uploaded back to the server until the next time the user
+connects.</p>
+
+<p>It is often more secure to create a separate share exclusively for
+storing user profiles:</p>
+
+<blockquote><pre class="code">[global]
+    logon path = \\hydra\profile\%U</pre></blockquote>
+
+<p>For more information on this option, see <a href="ch04.html#samba2-CHP-4-SECT-5">Section 4.5</a> earlier in this chapter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-5.6.3"/>
+
+<a name="INDEX-154"/><h3 class="head3">logon drive</h3>
+
+<p>This option specifies the drive letter on a Windows NT/2000/XP client
+to which the home directory specified with the
+<tt class="literal">logon</tt> <tt class="literal">home</tt> option will be
+mapped. Note that this option will work with Windows NT/2000/XP
+clients only. For example:</p>
+
+<blockquote><pre class="code">[global]
+    logon drive = I:</pre></blockquote>
+
+<p>You should always use drive letters that will not conflict with fixed
+drives on the client machine. The default is Z:, which is a good
+choice because it is as far away from A:, C:, and D: as possible.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-5.6.4"/>
+
+<a name="INDEX-155"/><h3 class="head3">logon home</h3>
+
+<p>This option specifies the location of a user's home
+directory for use by the MS-DOS <em class="emphasis">net</em> commands.
+For example, to specify a home directory as a share on a Samba
+server, use the following:</p>
+
+<blockquote><pre class="code">[global]
+    logon home = \\hydra\%U</pre></blockquote>
+
+<p>Note that this works nicely with the <tt class="literal">[homes]</tt>
+service, although you can specify any directory you wish. Home
+directories can be mapped with a logon script using the following
+command:</p>
+
+<a name="INDEX-156"/><blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>net use i: /home  </b></tt></pre></blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-6"/>
+
+<h2 class="head1">System Policies</h2>
+
+<p>A <a name="INDEX-157"/>system policy can be used in a Windows
+NT domain as a remote administration tool for implementing a similar
+computing environment on all clients and limiting the abilities of
+users to change configuration settings on their systems or allowing
+them to run only a limited set of programs. One application of system
+policies is to use them along with mandatory profiles to implement a
+collection of computers for public use, such as in a library, school,
+or Internet cafe.</p>
+
+<p>A system policy is a collection of registry settings that is stored
+in a file on the PDC and is automatically downloaded to the clients
+when users log on to the domain. The file containing the settings is
+created on a Windows system using the <a name="INDEX-158"/>System Policy Editor. Because the format
+of the registry is different between Windows 95/98/Me and Windows
+NT/2000/XP, it is necessary to make sure that the file that is
+created is in the proper format. This is a very simple matter because
+when the System Policy Editor runs on Windows 95/98/Me, it will
+create a file in the format for Windows 95/98/Me, and if it is run on
+Windows NT/2000/XP, it will use the format needed by those versions.
+After the policy file is created with the System Policy Editor, it is
+stored on the primary domain controller and is automatically
+downloaded by the clients during the logon process, and the policies
+are applied to the client system.</p>
+
+<p>On Windows NT 4.0 Server, you can run the System Policy Editor by
+logging in to the system as Administrator or another user in the
+Administrators group, opening the Start menu, and selecting Programs,
+then Administrative Tools, then System Policy Editor. On Windows 2000
+Advanced Server, open the Start menu and click Run . . . . In the
+dialog box that comes up, type in
+<tt class="literal">C:\winnt\poledit.exe</tt>, and click the OK button.</p>
+
+<p>If you are using a Windows version other than NT Server or Windows
+2000 Advanced Server, you must install the System Policy Editor, and
+getting a copy of it can be a little tricky. If you are running
+Windows NT 4.0 Workstation or Windows 2000 Professional and have a
+Windows NT 4.0 Server installation CD-ROM, you can run the file
+<em class="filename">\Clients\Svrtools\Winnt\Setup.bat</em> from that CD
+to install the Client-based Network Administration Tools, which
+includes <em class="emphasis">poledit.exe</em>. Then open the Start menu,
+click Run..., type <tt class="literal">C:\winnt\system32\poledit.exe</tt>
+into the text area, and click the OK button.</p>
+
+<p>If you are using Windows 95/98, insert a Windows 95 or Windows 98
+distribution CD-ROM<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a> into your CD-ROM drive,
+then open the Control Panel and double-click the Add/Remove Programs
+button.</p>
+
+<p>Click the Windows Setup tab, and then click the Have Disk...
+button. In the new dialog box that appears, click the Browse...
+button, then select the CD-ROM drive from the Drives drop-down menu.
+Then:</p>
+
+<ul><li>
+<p>If you are using a Windows 95 installation CD-ROM, double-click the
+admin, then apptools, then poledit folder icons.</p>
+</li><li>
+<p>If you are using a Windows 98 installation CD-ROM, double-click the
+tools, then reskit, then netadmin, then poledit folder icons.</p>
+</li></ul>
+<p>You should see &quot;<a name="INDEX-159"/>grouppol.inf&quot; appear in
+the File name: text area on the left of the dialog box. Click the OK
+buttons in two dialog boxes, and you will be presented with a dialog
+box in which you should select both the Group Policies and System
+Policy Editor checkboxes. Then click the Install button. Close the
+remaining dialog box, and you can now run the System Policy Editor by
+opening the Start menu and selecting Programs, then Accessories, then
+System Tools, then System Policy Editor. Or click the Run... item in
+the Start Menu, and enter <tt class="literal">C:\Windows\Poledit</tt>.</p>
+
+<p>When the System Policy Editor starts up, select New Policy from the
+File menu, and you will see a window similar to that in <a href="ch04.html#samba2-CHP-4-FIG-14">Figure 4-14</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-14"/><img src="figs/sam2_0414.gif"/></div><h4 class="head4">Figure 4-14. The System Policy Editor window</h4>
+
+<p>The next step is to make a selection from the File menu to add
+policies for users, groups, and computers. For each item you add, you
+will be asked for the username, or name of the group or computer, and
+a new icon will appear in the window. Double-clicking one of the
+icons will bring up the Properties dialog box, such as the one shown
+in <a href="ch04.html#samba2-CHP-4-FIG-15">Figure 4-15</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-15"/><img src="figs/sam2_0415.gif"/></div><h4 class="head4">Figure 4-15. The Properties dialog of System Policy Editor</h4>
+
+<p>The upper window in the dialog shows the registry settings that can
+be modified as part of the system policy, and the lower window shows
+descriptive information or more settings pertaining to the one
+selected in the upper window. Notice in the figure that there are
+three checkboxes and that they are all in different states:</p>
+
+<dl>
+<dt><b>Checked</b></dt>
+<dd>
+<p>Meaning that the registry setting is enabled in the policy</p>
+</dd>
+
+
+
+<dt><b>White (unchecked)</b></dt>
+<dd>
+<p>Which clears the registry setting</p>
+</dd>
+
+
+
+<dt><b>Gray</b></dt>
+<dd>
+<p>Which causes the registry setting on the client to be unmodified</p>
+</dd>
+
+</dl>
+
+<p>Basically, if all the items are left gray (the default), the system
+policy will have no effect. The registry of the logged-on client will
+not be modified. However, if any of the items are either checked or
+unchecked (white), the registry on the client will be modified to
+enable the setting or clear it.</p>
+<a name="samba2-CHP-4-NOTE-117"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>In this section, we are giving you enough information on using the
+System Policy Editor to get you started&mdash;or, should we say,
+enough rope with which to hang yourself. Remember that a system
+policy, once put into action, will be modifying the registries of all
+clients who log on to the domain. The usual warnings about editing a
+Windows registry apply here with even greater importance. Consider
+how difficult (or even impossible) it will be for you to restore the
+registries on all those clients if anything happens to go wrong.
+<em class="emphasis">As with roaming profiles, casual or careless implementation
+of system policies can easily lead to domain-wide
+disaster</em>.</p>
+
+<p>Creating a good system policy file is a complex topic, which we
+cannot cover in detail here. It would take a whole book, and yes,
+there happens to be an O'Reilly book on the subject,
+<em class="citetitle">Windows System Policy Editor</em>. Another
+definitive source of documentation on Windows NT system policies and
+the System Policy Editor is the Microsoft white paper
+<em class="citetitle">Implementing Policies and Profiles for Windows NT
+4.0</em>, which can be found at <a href="http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp">http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp</a>.</p>
+</blockquote>
+
+<p>Once you have created a policy, click the OK button and use the Save
+As... item from the File menu to save it. Use the filename
+<em class="filename">config.pol</em><a name="INDEX-160"/> for a Windows 95/98 system policy and
+<em class="filename">ntconfig.pol</em><a name="INDEX-161"/> for a policy that will be used on Windows
+NT/2000/XP clients. Finally, copy the <em class="filename">.pol</em> file
+to the directory used for the <tt class="literal">[netlogon]</tt> share on
+the Samba PDC. The <em class="filename">config.pol</em> and
+<em class="filename">ntconfig.pol</em> files must go in this
+directory&mdash;unlike roaming profiles and logon scripts, there is
+no way to specify the location of the system policy files in
+<em class="filename">smb.conf</em>. If you want to have different system
+policies for different users or computers, you must perform that part
+of the configuration within the System Policy Editor.</p>
+
+<a name="samba2-CHP-4-NOTE-118"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you have, or will have, any <a name="INDEX-162"/><a name="INDEX-163"/>Windows Me clients on your network,
+be careful. Microsoft has stated that Windows Me does not support
+system policies. The odd thing about this is that it will download
+the policy from a <em class="filename">config.pol</em> file on the PDC,
+but there is no guarantee that the results will be what was intended.
+Check the effect of your system policy carefully on your Windows Me
+clients to make sure it is working how you want.</p>
+</blockquote>
+
+<p>When a user logs on to the domain, her Windows client will download
+the <em class="filename">.pol</em> file from the server, and the settings
+in it (that is, the items either checked or cleared in the System
+Policy Editor) will override the client's settings.</p>
+
+<p>If things &quot;should work&quot; but
+don't, try shutting down the Windows client and
+restarting, rather than just logging off and on again. Windows
+sometimes will hold the <tt class="literal">[netlogon]</tt> share open
+across logon sessions, and this can prevent the client from getting
+the updated <em class="filename">.pol</em> file from the server.
+<a name="INDEX-164"/>
+<a name="INDEX-165"/></p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-7"/>
+
+<h2 class="head1">Samba as a Domain Member Server</h2>
+
+<p><a name="INDEX-166"/>Up to now,
+we've focused on configuring and using Samba as the
+primary domain controller. If you already have a domain controller on
+your network, either a Windows NT/2000 Server system or a Samba PDC,
+you can add a Samba server to the domain as a domain member server.
+This involves setting up the Samba server to have a computer account
+with the primary domain controller, in a similar way that Windows
+NT/2000/XP clients can have computer accounts on a Samba PDC. When a
+client accesses shares on the Samba domain member server, Samba will
+pass off the authentication to the domain controller rather than
+performing the task on the local system. If the PDC is a Windows
+server, any number of Windows BDCs might exist that can handle the
+authentication instead of the PDC.</p>
+
+<p>The first step is to add the Samba server to the domain by creating a
+computer account for it on the primary domain controller. You can do
+this using the <em class="emphasis">smbpasswd</em> command, as follows:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -j <em class="replaceable">DOMAIN</em> -r <em class="replaceable">PDCNAME</em> -U<em class="replaceable">admin_acct</em>%<em class="replaceable">password</em></b></tt></pre></blockquote>
+
+<p>In this command, <em class="replaceable">DOMAIN</em> is replaced by the
+name of the domain the Samba host is joining,
+<em class="replaceable">PDCNAME</em> is replaced by the computer name
+of the primary domain controller,
+<em class="replaceable">admin_acct</em> is replaced by the username of
+an administrative account on the domain controller (either
+Administrator&mdash;or another user in the Administrators
+group&mdash;on Windows NT/2000, and root on Samba), and
+<em class="replaceable">password</em> is replaced with the password of
+that user. To give a more concrete example, on our domain that has a
+Windows NT 4 Server primary domain controller or a Windows 2000
+Active Directory domain controller named <tt class="literal">SINAGUA</tt>,
+the command would be:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -j METRAN -r SINAGUA -UAdministrator%hup8ter</b></tt></pre></blockquote>
+
+<p>and if the PDC is a Samba system, we would use the command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -j METRAN -r toltec -Uroot%jwun83jb</b></tt></pre></blockquote>
+
+<p>where <tt class="literal">jwun83jb</tt> is the password for the root user
+that is contained in the<em class="filename"> smbpasswd</em> file, as we
+explained earlier in this chapter.</p>
+
+<p>If you did it right, <em class="emphasis">smbpasswd</em> will respond with
+a message saying the domain has been joined. The security
+identifier<a name="FNPTR-5"/><a href="#FOOTNOTE-5">[5]</a> returned to Samba from the PDC is kept in
+the file <em class="filename">/usr/local/samba/private/secrets.tdb</em>.
+The information in
+<em class="filename">secrets.tdb</em><a name="INDEX-167"/> is security-sensitive, so make sure to
+protect <em class="filename">secrets.tdb</em> in the same way you would
+treat Samba's password file.</p>
+
+<p>The next step is to modify the
+<em class="filename">smb.conf</em><a name="INDEX-168"/> file. Assuming you are starting with a
+valid <em class="filename">smb.conf</em> file that correctly configures
+Samba to function in a workgroup, such as the one we used in <a href="ch02.html">Chapter 2</a>, it is simply a matter of adding the following
+three lines to the <tt class="literal">[global]</tt> section:</p>
+
+<blockquote><pre class="code">workgroup = METRAN
+security = domain
+password server = *</pre></blockquote>
+
+<p>The first line establishes the name of the domain (even though it
+says &quot;workgroup&quot;). Instead of
+METRAN, use the name of the domain you are joining. Setting security
+to &quot;domain&quot; causes Samba to hand
+off authentication to a domain controller, and the
+<tt class="literal">password</tt> <tt class="literal">server</tt>
+<tt class="literal">=</tt> <tt class="literal">*</tt> line tells Samba to find
+the domain controller for authentication (which could be the primary
+domain controller or a backup domain controller) by querying the WINS
+server or using broadcast packets if a WINS server is not available.</p>
+
+<p>At this point, it would be prudent to run
+<em class="emphasis">testparm</em> to check that your
+<em class="filename">smb.conf</em> is free of errors. Then restart the
+Samba daemons.</p>
+
+<p>If the PDC is a Windows NT system, you can use Server Manager to
+check that the Samba server has been added successfully. Open the
+Start menu, then select Programs, then Administrative Tools (Common),
+and then Server Manager. Server Manager starts up with a window that
+looks like <a href="ch04.html#samba2-CHP-4-FIG-16">Figure 4-16</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-16"/><img src="figs/sam2_0416.gif"/></div><h4 class="head4">Figure 4-16. The Windows NT Server Manager window</h4>
+
+<p>As you can see, we've added both
+<tt class="literal">toltec</tt> and <tt class="literal">mixtec</tt> to a domain
+for which the Windows NT 4.0 Server system,
+<tt class="literal">sinagua</tt>, is the primary domain controller.</p>
+
+<p>You can check your setup on Windows 2000 Advanced Server by opening
+the Start menu and selecting Programs, then Administrative Tools,
+then Active Directory Users and Computers. The window that opens up
+will look like <a href="ch04.html#samba2-CHP-4-FIG-17">Figure 4-17</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-4-FIG-17"/><img src="figs/sam2_0417.gif"/></div><h4 class="head4">Figure 4-17. The Windows 2000 Active Directory Users and Computers window</h4>
+
+<p>Click Computers in the left side of the window with the Tree tab. You
+should see your Samba system listed in the right pane of the window.
+<a name="INDEX-169"/></p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-4-SECT-8"/>
+
+<h2 class="head1">Windows NT Domain Options</h2>
+
+<p><a href="ch04.html#samba2-CHP-4-TABLE-2">Table 4-2</a> shows the options that are commonly used
+in association with Samba on a Windows NT domain.</p>
+
+<a name="samba2-CHP-4-TABLE-2"/><h4 class="head4">Table 4-2. Windows NT domain options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">domain logons</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>Indicates whether Windows domain logons are to be used</p>
+</td>
+<td>
+<p><tt class="literal">No</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">domain master</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>For telling Samba to take the role of domain master browser</p>
+</td>
+<td>
+<p>Auto</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">add user script</tt></p>
+</td>
+<td>
+<p>string (command)</p>
+</td>
+<td>
+<p>Script to run to add a user or computer account</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">delete user</tt> <tt class="literal">script</tt></p>
+</td>
+<td>
+<p>string (command)</p>
+</td>
+<td>
+<p>Script to run to delete a user or computer account</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">domain admin group</tt></p>
+</td>
+<td>
+<p>string (list of users)</p>
+</td>
+<td>
+<p>Users that are in the Domain Admins group</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">domain guest group</tt></p>
+</td>
+<td>
+<p>string (list of users)</p>
+</td>
+<td>
+<p>Users that are in the Domain Guests group</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">password server</tt></p>
+</td>
+<td>
+<p>string (list of computers)</p>
+</td>
+<td>
+<p>List of domain controllers used for authentication when Samba is
+running as a domain member server</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">machine password timeout</tt></p>
+</td>
+<td>
+<p>numeric (seconds)</p>
+</td>
+<td>
+<p>Sets the renewal interval for NT domain machine passwords</p>
+</td>
+<td>
+<p><tt class="literal">604,800</tt> (1 week )</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+<p>Here are detailed explanations of each <a name="INDEX-170"/>Windows NT domain option listed
+in <a href="ch04.html#samba2-CHP-4-TABLE-2">Table 4-2</a>.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-4-SECT-8.1"/>
+
+<a name="INDEX-171"/><h3 class="head2">domain logons</h3>
+
+<p>This option configures Samba to accept domain logons as a primary
+domain controller. When a client successfully logs on to the domain,
+Samba will return a special token to the client that allows the
+client to access domain shares without consulting the PDC again for
+authentication. Note that the Samba machine must employ user-level
+security (<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">user</tt>) and must be the PDC for this option to
+function. In addition, Windows machines will expect a
+<tt class="literal">[netlogon]</tt> share to exist on the Samba server.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.1"/>
+
+<a name="INDEX-172"/><h3 class="head3">domain master</h3>
+
+<p>In a Windows network, a local master browser handles browsing within
+a subnet. A Windows domain can be made up of a number of subnets,
+each of which has its own local master browser. The primary domain
+controller serves the function of domain master browser, collecting
+the browse lists from the local master browser of each subnet. Each
+local master browser queries the domain master browser and adds the
+information about other subnets to their own browse lists. When Samba
+is configured as a primary domain controller, it automatically sets
+<tt class="literal">domain</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt>, making itself the domain
+master browser.</p>
+
+<p>Because Windows NT PDCs always claim the role of domain master
+browser, Samba should never be allowed to be domain master if there
+is a Windows PDC in the domain.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.2"/>
+
+<a name="INDEX-173"/><h3 class="head3">add user script</h3>
+
+<p>There are two ways in which <tt class="literal">add</tt>
+<tt class="literal">user</tt> <tt class="literal">script</tt> can be used. When
+the Samba server is set up as a primary domain controller, it can be
+assigned to a command that will run on the Samba server to add a
+Windows NT/2000/XP computer account to Samba's
+password database. When the user on the Windows system changes the
+computer's settings to join a domain, he is asked
+for the username and password of a user who has administrative rights
+on the domain controller. Samba authenticates this user and then runs
+the <tt class="literal">add</tt> <tt class="literal">user</tt>
+<tt class="literal">script</tt> with root permissions.</p>
+
+<p>When Samba is configured as a domain member server, the
+<tt class="literal">add</tt> <tt class="literal">user</tt>
+<tt class="literal">script</tt> can be assigned to a command to add a user
+to the system. This allows Windows clients to add users that can
+access shares on the Samba system without requiring an administrator
+to create the account manually on the Samba host.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.3"/>
+
+<a name="INDEX-174"/><h3 class="head3">delete user script</h3>
+
+<p>There are times when users are automatically deleted from the domain,
+and the <tt class="literal">delete</tt> <tt class="literal">user</tt>
+<tt class="literal">script</tt> can be assigned to a command that removes a
+user from the Samba host as a Windows server would do. However, you
+might not want this to happen, because the Unix user might need the
+account for reasons other than use with Samba. Therefore, we
+recommend that you be very careful about using this option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.4"/>
+
+<a name="INDEX-175"/><h3 class="head3">domain admin group</h3>
+
+<p>In a domain of Windows systems, it is possible for a server to get a
+list of the members of the Domain Admins group from a domain
+controller. Samba 2.2 does not have the ability to handle this, and
+the <tt class="literal">domain</tt> <tt class="literal">admin</tt>
+<tt class="literal">group</tt> parameter exists as a manual means of
+informing Samba who is in the group. The list should contain root
+(necessary for adding computer accounts) and any users on Windows
+NT/2000/XP clients in the domain who are in the Domain Admins group.
+These users must be recognized by the primary controller in order for
+them to perform some administrative duties such as adding users to
+the domain.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.5"/>
+
+<a name="INDEX-176"/><h3 class="head3">password server</h3>
+
+<p>In a Windows domain in which the domain controllers are a Windows
+primary domain controller, along with any number of Windows backup
+domain controllers, clients and domain member servers authenticate
+users by querying either the PDC or any of the BDCs. When Samba is
+configured as a domain member server, the <tt class="literal">password</tt>
+<tt class="literal">server</tt> parameter allows some control over how
+Samba finds a domain controller. Earlier versions of Samba could not
+use the same method that Windows systems use, and it was necessary to
+specify a list of systems to try. When you set
+<tt class="literal">password</tt> <tt class="literal">server</tt>
+<tt class="literal">=</tt> <tt class="literal">*</tt>, Samba 2.2 is able to find
+the domain controller in the same manner that Windows does, which
+helps to spread the requests over several backup domain controllers,
+minimizing the possibility of them becoming overloaded with
+authentication requests. We recommend that you use this method.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-4-SECT-8.1.6"/>
+
+<a name="INDEX-177"/><h3 class="head3">machine password timeout</h3>
+
+<p>The <tt class="literal">machine</tt> <tt class="literal">password</tt>
+<tt class="literal">timeout</tt> global option sets a retention period for
+Windows NT domain machine passwords. The default is currently set to
+the same time period that Windows NT 4.0 uses: 604,800 seconds (one
+week). Samba will periodically attempt to change the
+<em class="firstterm">machine account password</em>, which is a password
+used specifically by another server to report changes to it. This
+option specifies the number of seconds that Samba should wait before
+attempting to change that password. The timeout period can be changed
+to a single day by specifying the following:</p>
+
+<blockquote><pre class="code">[global]
+    machine password timeout = 86400</pre></blockquote>
+
+<a name="samba2-CHP-4-NOTE-119"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you would like more information on how Windows NT uses domain
+usernames and groups, we recommend Eric <a name="INDEX-178"/>Pearce's
+<em class="citetitle">Windows NT in a Nutshell</em>, published by
+O'Reilly. <a name="INDEX-179"/></p>
+</blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> When we include
+Windows XP in discussions of Windows NT domains in this book, we are
+referring to Windows XP Professional and not to the Home edition. The
+reason for this is explained in the section on Windows XP later in
+this chapter.</p> <a name="FOOTNOTE-2"/> <p><a href="#FNPTR-2">[2]</a> The entry in
+<em class="filename">/etc/passwd</em> might not be required in future
+Samba versions.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> If you want to follow our example in this
+section, and your network doesn't have any Windows
+systems offering shares, see <a href="ch05.html">Chapter 5</a> for
+directions on how to create one. Make sure you understand how to set
+up shares before continuing with the directions presented
+here!</p> <a name="FOOTNOTE-4"/> <p><a href="#FNPTR-4">[4]</a> The version of the System Policy
+Editor distributed with Windows 98 is an update of the version
+shipped with Windows 95. Use the version from the Windows 98
+distribution if you can.</p> <a name="FOOTNOTE-5"/> <p><a href="#FNPTR-5">[5]</a> This security identifier (SID) is part of
+an access token that allows the PDC to identify and authenticate the
+client.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch05.html b/docs/htmldocs/using_samba/ch05.html
new file mode 100644
index 0000000000..07a65cd08a
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch05.html
@@ -0,0 +1,1779 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 5. Unix Clients</h1>
+
+<p><a name="INDEX-1"/>In <a href="ch03.html">Chapter 3</a> we showed you how to configure Windows systems
+to access shared resources on both Windows and Samba servers. This
+has probably opened up a whole new world of computing for
+you&mdash;one in which you have to run to a Windows system every time
+you want to copy a file between Unix and Windows! In this chapter, we
+will show you the &quot;other
+side&quot;&mdash;how to access SMB shares from your
+favorite Unix system.</p>
+
+<p>You can access SMB resources from Unix in three ways, depending on
+your version of Unix. A program included with the Samba distribution
+called <em class="emphasis">smbclient</em><a name="INDEX-2"/> can be used to connect with a share on
+the network in a manner similar to using <em class="emphasis">ftp</em>
+when transferring files to or from an FTP site.</p>
+
+<p>If your system is running Linux, you can use the
+<a name="INDEX-3"/>smbfs
+filesystem to mount SMB shares right onto your Linux filesystem, just
+as you would mount a disk partition or NFS filesystem. The SMB shares
+can then be accessed and manipulated by all programs running on the
+Linux system: command shells, desktop GUI interfaces, and application
+software.</p>
+
+<p>On some BSD-based systems, including Mac OS X, a pair of utilities
+named <em class="emphasis">smbutil</em> <a name="INDEX-4"/>and <em class="emphasis">mount_smbfs</em>
+<a name="INDEX-5"/>can be used to query SMB servers and
+mount shares.</p>
+
+<p>For other Unix variants,
+<em class="emphasis">smbsh</em><a name="INDEX-6"/> can be run to enable common shell
+commands such as <em class="emphasis">cd</em>, <em class="emphasis">ls</em>,
+<em class="emphasis">mv, wc</em>, and <em class="emphasis">grep</em> to access
+and manipulate files and directories on SMB shares. This effectively
+extends the reach of the Unix shell and utilities beyond the Unix
+filesystem and into the SMB network.</p>
+
+<p>All the Unix clients can access shares offered by either Windows
+systems or Samba servers. We have already shown you how to set up a
+share on a Samba server and could use that as an example to work
+with. But it's much more fun to use the Unix clients
+with shares served by Windows systems. So before we start covering
+the Unix clients in detail, we will take a quick detour and show you
+how to set up file shares on both Windows 95/98/Me and Windows
+NT/2000/XP systems.</p>
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-1"/>
+
+<h2 class="head1">Sharing Files on Windows 95/98/Me</h2>
+
+<p>When <a name="INDEX-7"/><a name="INDEX-8"/>sharing files on Windows 95/98/Me, you
+can authenticate users in two different ways.
+<a name="INDEX-9"/><a name="INDEX-10"/>Share-level security is the default
+and is easy to use. However, it is not as secure and can require
+users to type in passwords when connecting to shares. User-level
+security offers a better security model and can be used if you have
+either a Samba or Windows NT/2000 server on your network performing
+user authentication.</p>
+
+<p>To configure the type of access control for your system, open the
+Control Panel, double-click the Network icon, then click the Access
+Control tab. You should see the dialog box shown in <a href="ch05.html#samba2-CHP-5-FIG-1">Figure 5-1</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-1"/><img src="figs/sam2_0501.gif"/></div><h4 class="head4">Figure 5-1. The Access Control tab of the Windows 98 Network Control Panel window</h4>
+
+<p>Click the &quot;Share-level access
+control&quot; or &quot;User-level access
+control&quot; radio button, depending on which you want
+to use. When using user-level access control, you will also need to
+fill in the name of your workgroup or Windows NT domain. Reboot as
+requested.</p>
+
+<p>To share a folder, right-click the folder's icon and
+select Sharing . . . . This will open the Sharing tab of the
+folder's Properties dialog box. Click the
+&quot;Shared As:&quot; radio button, and fill
+in a name for the share (which defaults to the
+folder's name) and a description, which will be
+visible to client users. If you don't want the share
+to be visible in the Network Neighborhood view of other Windows
+clients, pick a name for the share that ends in a dollar sign
+(<tt class="literal">$</tt>).</p>
+
+<p><a href="ch05.html#samba2-CHP-5-FIG-2">Figure 5-2</a> shows what the Sharing tab of the
+folder's Properties dialog box will look like when
+using share-level security. The security settings are very simple.
+You can select a radio button for read-only access or full
+(read/write) access, or have the user's permissions
+(either read-only or read/write) depend on which password they use.
+In accordance with which you select, you will be asked to assign
+either or both of the read-only and full-access passwords for the
+share.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-2"/><img src="figs/sam2_0502.gif"/></div><h4 class="head4">Figure 5-2. The Sharing tab of the folder's Properties dialog, with share-level security</h4>
+
+<p>If your system is configured with user-level security, the Sharing
+tab of the folder's Properties dialog box will look
+like <a href="ch05.html#samba2-CHP-5-FIG-3">Figure 5-3</a>. As you can see,
+we've created a share named
+&quot;DATA&quot;, and used the Add . . .
+button to create permissions that allow read-only access for all
+domain users and read/write (full access) for <tt class="literal">jay</tt>.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-3"/><img src="figs/sam2_0503.gif"/></div><h4 class="head4">Figure 5-3. The Sharing tab of the folder Properties dialog, with user-level security</h4>
+
+<p>When you are done specifying your settings for the share, click on
+the OK button, and the share will become available to users on
+network clients. Unless you chose a share name ending in a dollar
+sign, you can see it in the Network Neighborhood or My Network Places
+of Windows clients on the network. You can also now use the Unix
+clients described in this chapter to connect to the share.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-2"/>
+
+<h2 class="head1">Sharing Files on Windows NT/2000/XP</h2>
+
+<p>To create a file share on <a name="INDEX-11"/><a name="INDEX-12"/><a name="INDEX-13"/><a name="INDEX-14"/>Windows NT/2000/XP, you first must
+log in to the system as any member of the Administrators, Power
+Users, or Server Operators groups. Right-click the icon of a folder
+you wish to share, and click Sharing . . . in the pop-up menu. The
+Sharing tab of the folder's Properties dialog box
+will appear, as shown in <a href="ch05.html#samba2-CHP-5-FIG-4">Figure 5-4</a>. Click the
+&quot;Share this folder&quot; radio button.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-4"/><img src="figs/sam2_0504.gif"/></div><h4 class="head4">Figure 5-4. The Sharing tab of the folder's Properties dialog on Windows 2000</h4>
+
+<p>Share name: will default to the name of the folder, and you can
+change it if you want. One reason you might want to use a different
+name for the share is to make the share not appear in browse lists
+(as displayed by the Network Neighborhood, for example). This can be
+done by using a share name ending in a dollar sign
+(<tt class="literal">$</tt>). You can also add a description of the share
+in the Comment: text area. The description will appear to users of
+network clients and can help them understand the contents of the
+share.</p>
+
+<p><a name="INDEX-15"/><a name="INDEX-16"/><a name="INDEX-17"/><a name="INDEX-18"/><a name="INDEX-19"/>By clicking the Permissions button,
+you can set permissions for the share on a user-by-user basis. This
+is equivalent to the user-level security of Windows 95/98/Me file
+sharing. On Windows NT/2000/XP, Microsoft recommends that share
+permissions be set to allow full access by everyone, with the
+permissions controlled on a file-by-file basis using filesystem
+access control lists
+(<a name="INDEX-20"/>ACLs). The actual permissions given
+to network clients are a combination of the share permissions and
+file access permissions. To edit the ACL for the folder, click the
+Security tab. For more information on ACLs, see <a href="ch08.html#samba2-CHP-8-SECT-3">Section 8.3</a> in <a href="ch08.html">Chapter 8</a>.</p>
+
+<p>If you want, you can limit the number of users who can concurrently
+connect to the share using the &quot;User
+limit:&quot; radio button. The New Share button allows
+you to create multiple file shares for the same folder, each having
+its own name, comment, user limit, and other parameters.</p>
+
+<p>When you are done, click the OK button, and the folder will be
+accessible from clients on the network.</p>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-3"/>
+
+<h2 class="head1">smbclient</h2>
+
+<p>The Samba Team supplies <em class="emphasis">smbclient</em><a name="INDEX-21"/> as a basic part of the Samba suite. At
+first, it might seem to be a primitive interface to the SMB network,
+but <em class="emphasis">smbclient</em> is actually a versatile tool. It
+can be used for browsing shares on servers, testing configurations,
+debugging, accessing shared printers, backing up shared data, and
+automating administrative tasks in shell scripts. And unlike
+<tt class="literal">smbfs</tt><a name="INDEX-22"/><a name="INDEX-23"/><a name="INDEX-24"/> and <em class="emphasis">smbsh</em>,
+<em class="emphasis">smbclient</em> works on all Unix variants that
+support Samba.</p>
+
+<p>In this chapter we'll focus mostly on running
+<em class="emphasis">smbclient</em> as an interactive shell, using its
+<em class="emphasis">ftp</em>-like commands to access shared directories
+on the network. Using <em class="emphasis">smbclient</em> to access
+printers and perform backups will be covered in <a href="ch10.html">Chapter 10</a>.</p>
+
+<p>A complete reference to <em class="emphasis">smbclient</em> is found in
+<a href="appc.html">Appendix C</a>.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-3.1"/>
+
+<h3 class="head2">Listing Services</h3>
+
+<p><a name="INDEX-25"/>The <em class="emphasis">-L</em> option
+can be used with <em class="emphasis">smbclient</em> to list the resources
+on a single computer. Assuming the Samba server is configured to take
+the role of the master browser, we can obtain a list of the computers
+in the domain or workgroup like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient -L toltec</b></tt>
+added interface ip=172.16.1.1 bcast=172.16.1.255 nmask=255.255.255.0
+Password:
+Domain=[METRAN] OS=[Unix] Server=[Samba 2.2.5]
+
+    Sharename      Type      Comment
+    ---------      ----      -------
+    test           Disk      For testing only, please
+    IPC$           IPC       IPC Service (Samba 2.2.5)
+    ADMIN$         Disk      IPC Service (Samba 2.2.5)
+
+    Server               Comment
+    ---------            -------
+    MAYA                 Windows 98
+    MIXTEC               Samba 2.2.5
+    TOLTEC               Samba 2.2.5
+    ZAPOTEC              
+
+    Workgroup            Master
+    ---------            -------
+    METRAN               TOLTEC</pre></blockquote>
+
+<p>In the column labeled &quot;Server&quot;,
+<tt class="literal">maya</tt>, <tt class="literal">mixtec</tt>, and
+<tt class="literal">zapotec</tt> are shown along with toltec, the Samba
+server. The services on <tt class="literal">toltec</tt> are listed under
+&quot;Sharename&quot;. The IPC$ and ADMIN$
+shares are standard Windows services that are used for network
+communication and administrative purposes, and
+<em class="filename">test</em> is the directory we added as a share in
+<a href="ch02.html">Chapter 2</a>.</p>
+
+<p>Now that we know the names of computers in the domain, we can list
+services on any of those computers. For example, here is how we would
+list the services offered by <tt class="literal">maya</tt>, a Windows 98
+workstation:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient -L maya</b></tt>
+added interface ip=172.16.1.1 bcast=172.16.1.255 nmask=255.255.255.0
+Password:
+
+
+    Sharename      Type      Comment
+    ---------      ----      -------
+    PRINTER$       Disk      
+    HP             Printer   HP 932C on Maya
+    D              Disk      D: on Maya
+    E              Disk      E: on Maya
+
+    ADMIN$         Disk      
+    IPC$           IPC       Remote Inter Process Communication
+
+    Server               Comment
+    ---------            -------
+
+    Workgroup            Master
+    ---------            -------</pre></blockquote>
+
+<p>A shared printer is attached to <tt class="literal">maya</tt>, so we see
+the PRINTER$ administrative service, along with the HP share for the
+printer itself. Also on <tt class="literal">maya</tt> are the D and E
+shares, which allow access across the network to
+<tt class="literal">maya</tt>'s D: and E: drives. It is
+normal for the Server and Workgroup sections to be empty when listing
+services on a Windows client.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-3.2"/>
+
+<h3 class="head2">Authenticating with smbclient</h3>
+
+<p><a name="INDEX-26"/>As with any other SMB client,
+<em class="emphasis">smbclient</em> needs to supply a username and
+password if it is authenticating in a domain environment or if it is
+contacting a Samba server that is set up with user-level security. In
+a workgroup environment, it will at least need a password to use when
+connecting with a password-protected resource.</p>
+
+<p>By default, <em class="emphasis">smbclient</em> uses the username of the
+user who runs it and then prompts for a password. If you are using
+<em class="emphasis">smbclient</em> a lot, you might tire of entering your
+password every time.</p>
+
+<p><em class="emphasis">smbclient</em> supports some alternate methods of
+entering a username and password. The password can be entered on the
+command line, like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient //maya/e jayspassword</b></tt></pre></blockquote>
+
+<p>Or both the username and password can be supplied by using the
+<em class="emphasis">-U</em> option, including the username and password
+separated by a percent (<tt class="literal">%</tt>) character:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient //maya/e -U kelly%kellyspassword</b></tt></pre></blockquote>
+
+<p>This method is useful if you are logged in to the system under an
+account that is not Samba-enabled or you are testing your
+configuration to see how it treats another user. With either method,
+you can avoid having to enter the username and/or password each time
+you run <em class="emphasis">smbclient</em> by creating an alias for the
+command or creating a shell function or shell script. For example,
+with the <em class="emphasis">bash</em> shell, it is possible to define a
+function like this:</p>
+
+<blockquote><pre class="code">smbcl(  )
+{
+    smbclient $* -U jay%jayspassword
+}</pre></blockquote>
+
+<p>Adding the definition to the shell's startup script
+(which would be <em class="filename">~/.bash_profile</em> for
+<em class="emphasis">bash</em>) would result in the definition affecting
+all subsequent shell invocations.</p>
+
+<p>Another method that can be used to supply both the username and
+password is to set the USER and <a name="INDEX-27"/><a name="INDEX-28"/>PASSWD environment variables. Either
+set the USER environment variable using the
+<em class="replaceable">username</em>%<em class="replaceable">password</em>
+format, or set the USER environment variable to the username, and set
+PASSWD to the user's password.</p>
+
+<p>It is also possible to create a credentials file containing the
+username on the first line and the password on the second line, like
+this:</p>
+
+<blockquote><pre class="code">username = jay
+password = jayspassword</pre></blockquote>
+
+<p>Then, <em class="emphasis">smbclient</em> is run using the
+<em class="emphasis">-A</em> option to specify the name of the file:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient //maya/e -A ~/.smbpw</b></tt></pre></blockquote>
+
+<a name="samba2-CHP-5-NOTE-120"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>Of the methods we described in this section, the only one that is
+really secure is the default method of allowing
+<em class="emphasis">smbclient</em><a name="INDEX-29"/> to
+prompt for the password and typing in the password without echoing.</p>
+
+<p>If security is a concern, you definitely should avoid providing your
+password on the command line because it is very easy for
+&quot;shoulder surfers&quot; to obtain, as
+well as anyone who looks through your shell's
+command history.</p>
+
+<p>If you keep your Samba password in a credentials file, shell startup
+file, or shell script, make sure the file's
+permissions prohibit other users from reading or writing it. (Use an
+octal permissions mode of 0600.) Security experts never keep
+passwords in files owned by nonroot users or accessible by anyone
+other than the superuser. As part of their security policy, some
+organizations do not permit passwords to be stored in files, so you
+might want to check first before using this method.</p>
+
+<p>The authentication method that uses the USER and PASSWD environment
+variables isn't any more secure. Environment
+variables are usually set either on the command line or in one or
+more of the shell's startup files, so this method
+suffers from the same weaknesses we've just
+discussed. In addition, any program run by the user has access to the
+shell's environment variables, making a Trojan horse
+attack on the PASSWD variable really easy!</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-3.3"/>
+
+<h3 class="head2">An Interactive smbclient Session</h3>
+
+<p><a name="INDEX-30"/>A common use for
+<em class="emphasis">smbclient</em> is to use it as an
+<em class="emphasis">ftp</em>-like shell to access SMB resources on the
+network. To begin a session, <em class="emphasis">smbclient</em> must be
+provided with the UNC of a resource (which you can find using the
+<em class="emphasis">-L</em> option) on the command line, like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient //maya/e</b></tt>
+added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
+Password: 
+smb: \&gt;</pre></blockquote>
+
+<p>Forward slashes are accepted by <em class="emphasis">smbclient</em> for
+the share's UNC, which makes entering the UNC on the
+command line easier. Backslashes can also be used, but they must be
+quoted or escaped, and it is somewhat more difficult to type
+'<tt class="literal">\\maya\e</tt>' or <tt class="literal">\\\\maya\\e</tt>.
+After connecting to the share, <em class="emphasis">smbclient</em>
+displays the <tt class="literal">smb: \&gt;</tt> prompt, waiting for a
+command to be entered. Commands are similar to those with which you
+might be familiar in <em class="emphasis">ftp</em> and are also somewhat
+similar to Unix shell commands. To get a list of
+<em class="emphasis">smbclient</em><a name="INDEX-31"/> commands, use the
+<em class="emphasis">help</em> command:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>help</b></tt>
+ls             dir            du             lcd            cd             
+pwd            get            mget           put            mput           
+rename         more           mask           del            open           
+rm             mkdir          md             rmdir          rd             
+prompt         recurse        translate      lowercase      print          
+printmode      queue          cancel         quit           q              
+exit           newer          archive        tar            blocksize      
+tarmode        setmode        help           ?              history        
+!</pre></blockquote>
+
+<p>Some commands in the previous list are synonyms for other commands.
+For example, the <em class="emphasis">?</em> command is a synonym for
+<em class="emphasis">help</em>. You can give this command the name of
+another command as an argument to get a concise reminder of what the
+command does and how to use it:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>? ls</b></tt>
+HELP ls:
+        &lt;mask&gt; list the contents of the current directory</pre></blockquote>
+
+<p>The term <tt class="literal">&lt;mask&gt;</tt> refers to a file-matching
+pattern as commonly found in Unix shells and utilities. For example:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>ls *doc</b></tt>
+  ms-ProfPol-wp.doc                   A      131  Tue Dec 18 09:12:34 2002
+  smbclient.doc                       A    33969  Mon Dec 10 20:22:24 2002
+  smbmount.doc                        A     7759  Mon Dec 10 20:20:00 2002
+
+                      48590 blocks of size 524288. 40443 blocks available</pre></blockquote>
+
+<p>lists all files ending in &quot;doc&quot; in
+the current directory on the remote system. In the listing, the
+leftmost column shows the filename. Moving left to right, we see the
+file's MS-DOS attributes, then its size, and the
+time it was last modified.</p>
+
+<p>As with any other Unix utility, <em class="emphasis">smbclient</em> has a
+working directory on the local host. It also has another current
+directory on the remote SMB share. With
+<em class="citetitle">smbclient</em>, the <em class="emphasis">cd</em> command
+is used to move around on the remote system:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>cd trans  </b></tt> 
+smb: \trans\&gt;</pre></blockquote>
+
+<p>Notice how the prompt changes to reflect the new current working
+directory. To change your current directory on the local system, use
+the <em class="emphasis">lcd</em> command:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>lcd /u/snd</b></tt>
+the local directory is now /u/snd</pre></blockquote>
+
+<p>Most of <em class="emphasis">smbclient</em>'s commands
+are for performing operations on remote files and directories. There
+is no command for listing the contents of the local directory.
+However, <em class="emphasis">smbclient</em> allows a shell escape. Any
+command preceded by an exclamation point (<tt class="literal">!</tt>) is
+interpreted as a shell command and is run in a subshell on the local
+system. For example:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>! ls -l</b></tt>
+total 16
+drwxrwxr-x    2 jay      jay          4096 Jan 10 14:46 dr220-fet
+drwxrwxr-x    2 jay      jay          4096 Sep 22 12:16 dr220-tube
+-rw-rw-r--    1 jay      jay           131 Jan 10 02:22 readme.txt
+drwxrwxr-x    7 jay      jay          4096 Jan 10 02:19 xl1</pre></blockquote>
+
+<p>lists the contents of <em class="filename">/u/snd</em>. By using
+<em class="emphasis">smbclient</em>'s commands to operate
+on the remote system&mdash;and shell-escaped commands to operate on
+the local system&mdash;it is possible to manipulate data on both
+systems without having to exit <em class="emphasis">smbclient</em> or open
+another shell window.</p>
+
+<p><a name="INDEX-32"/><a name="INDEX-33"/>File transfer is performed using
+the <em class="emphasis">get</em> and
+<em class="emphasis">put</em><a name="INDEX-34"/><a name="INDEX-35"/> commands. The <em class="emphasis">get</em>
+command transfers a single file from the remote to the local system,
+and the <em class="emphasis">put</em> command copies a file from the local
+to the remote system. For example, the following command copies the
+file <em class="filename">readme.txt</em> to the SMB share:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>put readme.txt</b></tt>
+putting file readme.txt as \trans\readme.txt (127.9 kb/s) (average 10.7 kb/s)</pre></blockquote>
+
+<a name="samba2-CHP-5-NOTE-121"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>Unlike <em class="emphasis">ftp</em>, <em class="emphasis">smbclient</em> does
+not have <em class="emphasis">ascii</em> and <em class="emphasis">binary</em>
+commands to set the type of the file that is being transferred.
+Before transferring a text file from a Unix system to a Windows or
+Macintosh system, you might want to use the GNU
+<em class="emphasis">unix2dos</em><a name="INDEX-36"/> command to reformat newlines in the
+file to work with the carriage return linefeed (CRLF) standard:</p>
+
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>unix2dos text_file &gt;text_file.txt</b></tt></pre></blockquote>
+
+
+<p>and then transfer the CRLF-formatted version. After transferring a
+text file from a Windows or Macintosh system to Unix, you can use the
+GNU <em class="emphasis">dos2unix</em><a name="INDEX-37"/> command to perform the inverse
+operation:</p>
+
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>dos2unix text_file.txt &gt;text_file</b></tt></pre></blockquote>
+</blockquote>
+
+<p>To transfer more than one file with a single command, you can use the
+<em class="emphasis">mget</em><a name="INDEX-38"/><a name="INDEX-39"/> and <em class="emphasis">mput</em> commands,
+which accept a list of filenames in the command line. The list can be
+provided by typing in the filenames on the command line separated by
+spaces, or the group of files can be specified with a pattern as one
+would use in Unix shell commands. The command:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>mget plain/*</b></tt></pre></blockquote>
+
+<p>copies all the files in the directory <em class="filename">plain</em> on
+the SMB share to the current directory on the local system. By
+default, <em class="emphasis">smbclient</em> prompts for each file, asking
+if you want to copy it:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>mget plain/*</b></tt>
+Get file tomm.wav? n
+Get file toml.wav? n
+Get file tomh.wav? n
+Get file snare.wav? n
+Get file rim.wav? n
+Get file handclap.wav? n
+Get file bassdrum.wav? n</pre></blockquote>
+
+<p>If you are sure you want to copy all the files, you can turn off
+prompting with the <em class="emphasis">prompt</em> command, like this:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>prompt</b></tt>
+prompting is now off</pre></blockquote>
+
+<p>By default, if you specify the name of a directory,
+<em class="emphasis">smbclient</em> will not copy the contents of the
+directory. To transfer the entire contents of directories listed in
+the <em class="emphasis">mput</em> or <em class="emphasis">mget</em> command,
+you must first use the <em class="emphasis">recurse</em> command:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>recurse</b></tt>
+directory recursion is now on</pre></blockquote>
+
+<p>After setting things up with the
+<em class="emphasis">prompt</em><a name="INDEX-40"/><a name="INDEX-41"/> and <em class="emphasis">recurse</em>
+commands, we can copy a directory like this:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>mget acc</b></tt>
+getting file tomm.wav of size 55494 as tomm.wav (2580.6 kb/s) (average 2087.3 kb/s)
+getting file toml.wav of size 57220 as toml.wav (2660.9 kb/s) (average 2167.6 kb/s)
+getting file tomh.wav of size 55936 as tomh.wav (2601.2 kb/s) (average 2220.8 kb/s)
+getting file snare.wav of size 22132 as snare.wav (1200.7 kb/s) (average 2123.7 kb/s)
+getting file rim.wav of size 8314 as rim.wav (1623.8 kb/s) (average 2110.8 kb/s)
+getting file handclap.wav of size 14180 as handclap.wav (1978.2 kb/s) (average 2106.2 
+kb/s)
+getting file bassdrum.wav of size 6950 as bassdrum.wav (2262.3 kb/s) (average 2108.5 
+kb/s)</pre></blockquote>
+
+<p><a name="INDEX-42"/>Directory recursion applies to all
+commands, so if an <em class="emphasis">ls</em> command is used while
+directory recursion is on, all files in the directory tree are
+listed. To turn directory recursion off again, simply re-enter the
+command. At the same time, you might also wish to toggle prompting
+back to its initial state:</p>
+
+<blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>recurse</b></tt>
+directory recursion is now off
+smb: \trans\&gt; <tt class="userinput"><b>prompt</b></tt>
+prompting is now on</pre></blockquote>
+
+<p>There are other <em class="emphasis">smbclient</em> commands that you
+might find useful. The <em class="emphasis">mkdir</em> command can be used
+to create a directory; <em class="emphasis">rmdir</em> removes a
+directory; <em class="emphasis">rm</em> deletes a file; and
+<em class="emphasis">rename</em> changes a file's name.
+These behave very similarly to their Unix shell counterparts. <a href="appc.html">Appendix C</a> contains a complete reference to
+<em class="emphasis">smbclient</em> and its command set.</p>
+
+<p>To exit <em class="emphasis">smbclient</em>, use the
+<em class="emphasis">exit</em> or <em class="emphasis">quit</em> command:</p>
+
+<a name="INDEX-43"/><blockquote><pre class="code">smb: \trans\&gt; <tt class="userinput"><b>quit </b></tt></pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-3.4"/>
+
+<h3 class="head2">Programming with smbclient</h3>
+
+<p><a name="INDEX-44"/>The <em class="emphasis">-c</em> option
+<em class="emphasis">of smbclient</em> allows a list of commands to be
+passed on the command line. To copy the file
+<em class="filename">\\maya\e\trans\readme.txt</em> to
+<em class="filename">/u/snd/readme.txt</em>, we might use the command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient //maya/e -c &quot;lcd /u/snd; cd trans; get readme.txt&quot; -A ~/.smbpw</b></tt></pre></blockquote>
+
+<p>Everything that <em class="emphasis">smbclient</em> needs to know to
+perform the operation has been specified in the command. There is no
+interactive session, so a command such as this can be placed inside a
+shell script or a program in some other programming language.</p>
+
+<p>By using <em class="emphasis">smbclient</em> in this manner, it is
+possible to create customized commands using shell functions, scripts
+or aliases. For example, suppose we wanted a command to print a short
+listing of files in a shared directory, showing just the names of the
+files. Using a <em class="emphasis">bash</em> function, we could define a
+command <em class="emphasis">smbls</em> as follows:</p>
+
+<blockquote><pre class="code">smbls(  )
+{
+        share=`echo $1 | cut -d '/' -f '1-4'`
+        dir=`echo $1 | cut -d '/' -f '5-'`
+        smbclient $share -c &quot;cd $dir; ls&quot; -A ~/.smbpw | \
+                        grep &quot;^  &quot; | cut -d ' ' -f 3 - | sort
+}</pre></blockquote>
+
+<p>After defining this function, we can use <em class="emphasis">smbls</em>
+like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbls //maya/e</b></tt>
+CD-images
+lectures
+ms-ProfPol-wp.doc
+profile-map
+readme.txt
+RECYCLED
+smbclient.doc
+smbmount.doc
+smbsh.txt
+trans
+$ <tt class="userinput"><b>smbls //maya/e/lectures</b></tt>
+.
+..
+lecture1.mp3
+lecture2.mp3
+lecture3.mp3
+lecture4.mp3
+lecture5.mp3
+lecture6.mp3
+lecture7.mp3
+lecture8.mp3
+lecture9.mp3</pre></blockquote>
+
+<p>Another use for <em class="emphasis">smbclient</em> in scripts is
+performing administrative tasks. Suppose a group of users on Windows
+clients are sharing a set of files as part of a project on which they
+are working. Instead of expecting them to coordinate making daily
+backups, we could write a script that copies the share to the Samba
+server and run the script nightly as a cron job. The directory on the
+Samba server could be shared as well, allowing any of the users to
+retrieve a backup file on their own, without having to bother an
+administrator.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-3.5"/>
+
+<h3 class="head2">Backups with smbclient</h3>
+
+<p>A major use of <em class="emphasis">smbclient</em><a name="INDEX-45"/><a name="INDEX-46"/> is to create and restore backups of
+SMB file shares. The backup files <em class="emphasis">smbclient</em>
+writes are in tar format, making them easy to work with and portable
+among all Unix versions. Using <em class="emphasis">smbclient</em> on a
+Unix server to run network backups can result in a more centralized
+and easily managed solution for providing data integrity because both
+SMB shares and NFS filesystems can be backed up on the same system.</p>
+
+<p>You can use <em class="emphasis">smbclient</em> to perform backups in two
+ways. When backing up an entire share, the simplest method is to use
+the <em class="emphasis">-Tc</em> option on the command line:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient //maya/e -A samba-domain-pw -Tc &gt;maya-e.tar</b></tt></pre></blockquote>
+
+<p>This will create a tar archive of the <em class="filename">\\maya\e</em>
+share in the file <em class="filename">maya-e.tar</em>. By using the
+<em class="emphasis">-D</em> option, it is possible to back up a directory
+in the share, rather than the whole share:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient //maya/e -A samba-domain-pw -D trans -Tc &gt;maya-e.tar</b></tt></pre></blockquote>
+
+<p>This causes <em class="emphasis">smbclient</em> to change its working
+directory to the <em class="filename">trans</em> directory of the
+<em class="filename">\\maya\e</em> share before starting the backup. It is
+also possible to use
+<em class="emphasis">smbclient</em>'s
+<em class="emphasis">tar</em> command in interactive mode, like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient //maya/e </b></tt>
+added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
+Password:
+smb: \&gt; <tt class="userinput"><b>cd trans</b></tt>
+smb: \trans\&gt; <tt class="userinput"><b>tarmode full hidden system quiet</b></tt>
+smb: \trans\&gt; <tt class="userinput"><b>tar c maya-e-trans.tar</b></tt></pre></blockquote>
+
+<p>With the previous code, only the <em class="emphasis">trans</em>
+subdirectory in the <em class="emphasis">\\maya\e</em> share will be
+backed up, using the settings specified in the
+<em class="emphasis">tarmode</em> command. To have this type of backup run
+automatically from a script, use the <em class="emphasis">-c</em> option:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient //maya/e -A samba-domain-pw -c &quot;cd trans; tarmode full hidden \</b></tt>
+<tt class="userinput"><b>    system quiet; tar &gt;maya-e-trans.tar&quot;</b></tt></pre></blockquote>
+
+<p>Using either the <em class="emphasis">-T</em> command-line option or
+<em class="emphasis">smbclient</em>'s
+<em class="emphasis">tar</em> command, additional options can be supplied.
+It is necessary to specify either the <em class="emphasis">c</em> option
+to create a backup archive or the <em class="emphasis">x</em> option to
+extract (restore) one.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> </p>
+
+<p>The other options can be appended to the option string
+and are explained in the section on <em class="emphasis">smbclient</em> in
+<a href="appc.html">Appendix C</a>. They allow you to create incremental
+backups, specify which files to include or exclude from the backup,
+and specify a few other miscellaneous settings. For example, suppose
+we wish to create an incremental backup of a share and reset the
+archive bit on the files to set things up for the next incremental
+backup. Instead of using the interactive commands:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>tarmode inc reset quiet</b></tt>
+smb: \&gt; <tt class="userinput"><b>tar c backup.tar</b></tt></pre></blockquote>
+
+<p>we could either use the interactive command:</p>
+
+<blockquote><pre class="code">smb: \&gt; <tt class="userinput"><b>tar cgaq backup.tar</b></tt></pre></blockquote>
+
+<p>or specify the <em class="emphasis">-Tcgaq</em> option on the
+<em class="emphasis">smbclient</em> command line.</p>
+
+<p>Your best strategy for using <em class="emphasis">smbclient</em> for
+network backups depends on your local configuration. If you have only
+a few Windows systems sharing a small amount of data, you might
+create a script containing <em class="emphasis">smbclient -Tc</em>
+commands to back up each share to a separate tar file, placing the
+files in a directory that is included with regular backups of the
+Unix system. If you have huge SMB shares on your network, you might
+prefer to write the backup directly to a tape drive. You can do this
+with <em class="emphasis">smbclient</em> just as you would with a Unix
+<em class="emphasis">tar</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient //maya/d -A samba-domain-pw -Tc &gt;/dev/tape</b></tt></pre></blockquote>
+
+<p>After you have become more familiar with
+<em class="emphasis">smbclient</em> and have an automated backup system in
+place, you might find that using Samba has dramatically decreased
+your anxiety regarding the integrity of your
+network's data. The authors of this book are
+experienced Unix system administrators, and we highly recommend
+having a backup strategy that has been carefully planned,
+implemented, and most importantly, <em class="emphasis">tested and known to work
+as it is supposed to</em>.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-4"/>
+
+<h2 class="head1">smbfs</h2>
+
+<p>On Linux, the <a name="INDEX-47"/>smbfs filesystem can be used to mount
+SMB shares onto the Linux filesystem in a manner similar to mounting
+disk partitions on NFS filesystems. The result is so transparent that
+users on the Linux system might never be aware that they are
+accessing files through a Windows or Samba server. Files and
+directories appear as any other files or directories on the local
+Linux system, although there are a few differences in behavior
+relating to ownership and permissions.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a></p>
+
+<p>Although smbfs is based on the Samba code, it is not itself part of
+the Samba distribution. Instead, it is included with Linux as a
+standard part of the Linux filesystem support.</p>
+
+<p>The <em class="emphasis">smbmount</em> and
+<em class="emphasis">smbmnt</em><a name="INDEX-48"/> programs are part of the Samba
+distribution and are needed on the client to mount smbfs filesystems.
+Samba must be compiled with the <tt class="literal">--with-smbmount</tt>
+configure option to make sure these programs are compiled. They refer
+to <em class="filename">smb.conf</em> for information they need regarding
+the local system and network configuration, so you will need a
+working <em class="filename">smb.conf</em><a name="INDEX-49"/><a name="INDEX-50"/>
+file on the system, even if it is not acting as a Samba server.
+ <a name="INDEX-51"/><a name="INDEX-52"/><a name="INDEX-53"/></p>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-4.1"/>
+
+<h3 class="head2">Mounting an smbfs Filesystem</h3>
+
+<p>The <em class="emphasis">smbmount</em><a name="INDEX-54"/> command is used to mount an smbfs
+filesystem into the Linux filesystem. The basic usage is:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbmount </b></tt><em class="replaceable">Share-UNC mount-point</em><tt class="userinput"><b> -o </b></tt><em class="replaceable">options</em></pre></blockquote>
+
+<p>Replace <em class="replaceable">Share-UNC</em> with the UNC for the SMB
+share, and <em class="replaceable">mount-point</em> with the full path
+to the directory in the Linux filesystem to use as the mount point.
+The <em class="replaceable">options</em> argument is used to set the
+exact manner in which the share is mounted. Let's
+look at an example of a <em class="emphasis">smbmount</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbmount //maya/e /smb/e \</b></tt>
+<tt class="userinput"><b>    -o &quot;credentials=/home/jay/.smbpw,uid=jay,gid=jay,fmask=664,dmask=775&quot;</b></tt></pre></blockquote>
+
+<p>Here we are mounting share <em class="filename">\\maya\e</em> from a
+Windows 98 system on the mount point <em class="filename">/smb/e</em> on
+the Linux system.</p>
+
+<a name="samba2-CHP-5-NOTE-122"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>If your Linux kernel doesn't include smbfs support,
+you will get the error message:</p>
+
+<blockquote><pre class="code">ERROR: smbfs filesystem not supported by the kernel</pre></blockquote>
+
+
+<p>In this case, you must configure and compile a new kernel to include
+support for smbfs. When smbfs is installed, and an SMB share is
+mounted, you can run the command:</p>
+
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cat /proc/filesystems</b></tt></pre></blockquote>
+
+<p>and see a line that looks like:</p>
+
+<blockquote><pre class="code">nodev   smbfs</pre></blockquote>
+
+
+<p>in the command's output.</p>
+</blockquote>
+
+<p>The mount point must exist before <em class="emphasis">smbmount</em> is
+run and can be created using the <em class="emphasis">mkdir</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /smb/e</b></tt></pre></blockquote>
+
+<p>The argument to the <em class="emphasis">-o</em> option might look a
+little complex. It is a comma-separated list of
+<em class="replaceable">key</em><tt class="literal">=</tt><em class="replaceable">value</em>
+pairs. The <tt class="literal">credentials</tt> key is set to the name of
+the credentials file, which is used to give
+<em class="emphasis">smbmount</em> a valid username and password with
+which to authenticate while connecting to the share. The format is
+identical to that used by <em class="emphasis">smbclient</em> (as
+explained in the previous section), so you can use the same
+credentials file for both clients. If you want, you can use the
+<em class="replaceable">key</em>=<em class="replaceable">value</em> pair
+<tt class="literal">username</tt>=<em class="replaceable">name</em>%<em class="replaceable">password</em>
+to specify the username and password directly in the
+<em class="emphasis">smbmount</em> command, although this is considerably
+less secure.</p>
+
+<a name="samba2-CHP-5-NOTE-123"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The <em class="emphasis">smbmount</em> command accepts the same
+authentication methods as <em class="emphasis">smbclient</em>. The
+comments in the section on <em class="emphasis">smbclient</em> regarding
+supplying passwords on the command line&mdash;and keeping passwords
+in files and environment variables&mdash;also apply here.</p>
+</blockquote>
+
+<p>The rest of the options tell <em class="emphasis">smbmount</em> how to
+translate between the SMB filesystem and the Unix filesystem, which
+differ in their handling of ownership and permissions. The
+<em class="emphasis">uid</em> and <em class="emphasis">gid</em> options specify
+the owner and group to be assigned to all directories and files in
+the mounted share.</p>
+
+<p>The <em class="emphasis">fmask</em><a name="INDEX-55"/> and
+<em class="emphasis">dmask</em><a name="INDEX-56"/> options specify
+<a name="INDEX-57"/>bitmasks for
+permissions of files and directories, respectively. These bitmasks
+are logically ANDed with whatever permissions are granted by the
+server to create the effective permissions on the client Unix system.
+On the server side, the permissions granted depend on the
+server's operating system. For a Windows 95/98/Me
+server using share-mode security, the MS-DOS read-only attribute can
+be set on individual files and directories and combined with the Full
+Access or Read Only permissions on the share as a whole. In
+user-level security mode, Windows 95/98/Me can have ACL-like
+permissions applied to the entire share, as discussed in <a href="ch04.html">Chapter 4</a>. Windows NT/2000/XP support ACLs on individual
+files and directories, with Full Control, Change, or Read permissions
+that can be applied to the entire share. If the server is a Samba
+server, the permissions are whatever is defined by the Samba share
+and the local Unix system for the individual files and directories.
+In every case, the permissions applied to the share act to further
+limit access, beyond what is specified for the individual files and
+directories.</p>
+
+<a name="samba2-CHP-5-NOTE-124"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>You might think that the <em class="emphasis">fmask</em> and
+<em class="emphasis">dmask</em> permission masks can be used only to
+reduce the effective permissions on files and directories, but this
+is not always the case. For example, suppose that a file is being
+shared by a Windows 95/98/Me server using share-mode security and
+that some number of users have been given the Full Access password
+for the share. If the share is mounted with
+<em class="emphasis">smbmount</em> using an <em class="emphasis">fmask</em> of
+666, read/write permissions are granted on the Unix system not only
+for the owner, but for everyone else on the Unix system as well!</p>
+</blockquote>
+
+<p>After mounting the <em class="filename">\\maya\d</em> share to
+<em class="filename">/smb/e</em>, here is what the contents of
+<em class="filename">/smb/e</em> look like:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>cd /smb/e ; ls -l</b></tt>
+total 47
+drwxrwxr-x    1 jay      jay           512 Jan  8 20:21 CD-images
+drwxrwxr-x    1 jay      jay           512 Jan  6 21:50 lectures
+-rw-rw-r--    1 jay      jay           131 Dec 18 09:12 ms-ProfPol-wp.doc
+-rw-rw-r--    1 jay      jay            59 Dec 18 09:12 profile-map
+-rw-rw-r--    1 jay      jay           131 Jan 15 05:01 readme.txt
+drwxrwxr-x    1 jay      jay           512 Feb  4  2002 RECYCLED
+-rw-rw-r--    1 jay      jay         33969 Dec 10 20:22 smbclient.doc
+-rw-rw-r--    1 jay      jay          7759 Dec 10 20:20 smbmount.doc
+-rw-rw-r--    1 jay      jay          1914 Dec 10 20:17 smbsh.txt
+drwxrwxr-x    1 jay      jay           512 Jan 10 03:54 trans</pre></blockquote>
+
+<p>For the most part, the files and directories contained in the mounted
+smbfs filesystem will work just like any others, except for
+limitations imposed by the nature of SMB networking. For example, not
+even the superuser can perform the operation:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chown root lectures</b></tt>
+chown: changing ownership of 'lectures': Operation not permitted</pre></blockquote>
+
+<p>because SMB shares do not intrinsically support the idea of
+ownership. Some odd behaviors can result from this. For example, the
+command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chmod 777 readme.txt</b></tt></pre></blockquote>
+
+<p>does not produce an error message, although nothing has been changed.
+The file <em class="filename">readme.txt</em> still has permissions set to
+664:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ls -l readme.txt</b></tt>
+-rw-rw-r--    1 jay      jay           131 Jan 15 05:01 readme.txt</pre></blockquote>
+
+<p>Aside from little things such as these, the mounted smbfs filesystem
+can be used in conjunction with virtually any application, and you
+might be pleasantly surprised at how nicely it integrates with your
+Linux-based computing environment. You can even create symbolic links
+in the Unix filesystem, pointing to files and directories inside SMB
+shares. However, unless the server is a Samba server that supports
+Unix CIFS extensions, you will not be able to create a symbolic link
+inside the mounted smbfs filesystem.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-4.2"/>
+
+<h3 class="head2">Mounting smbfs Filesystems Automatically</h3>
+
+<p><a name="INDEX-58"/>As with other types of
+filesystems, an smbfs filesystem can be mounted automatically during
+system bootup by creating an entry for it in
+<em class="filename">/etc/fstab</em>. The format for the entry is as
+follows:</p>
+
+<blockquote><pre class="code"><em class="replaceable">Share-UNC mount-point</em>  smbfs  <em class="replaceable">options</em> 0 0</pre></blockquote>
+
+<p>Replace <em class="replaceable">Share-UNC</em> with the UNC of the
+share (using the forward slash format), and replace
+<em class="replaceable">mount-point</em> with the name of the directory
+in the Linux filesystem on which the share will be mounted. In place
+of <em class="replaceable">options</em>, simply use the string that you
+used with the <em class="emphasis">-o</em> flag in the
+<em class="emphasis">smbmount</em> command.</p>
+
+<p>Once you have found the arguments to use with the
+<em class="emphasis">smbmount</em> command to mount the share the way you
+like it, it is a very simple matter to create the entry for
+<em class="filename">/etc/fstab</em>. The <em class="emphasis">smbmount</em>
+command we used to mount the share <em class="filename">\\maya\e</em> on
+<em class="filename">/smb/e</em> would translate to this
+<em class="filename">/etc/fstab</em> entry:</p>
+
+<blockquote><pre class="code">//maya/e /smb/e  smbfs  
+credentials=/home/jay/.smbpw,uid=jay,gid=jay,fmask=664,dmask=775 0 0
+
+<i class="lineannotation">(Please note that this should all go on one line.)</i></pre></blockquote>
+<a name="samba2-CHP-5-NOTE-125"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>If you make a mistake in modifying
+<em class="filename">/etc/fstab</em><a name="INDEX-59"/><a name="INDEX-60"/>, your system might not
+reboot properly, and you might be forced to boot into single-user
+mode to fix the problem. Before you edit
+<em class="filename">/etc/fstab</em>, be sure to make a backup copy of it,
+and be prepared to recover your system if anything goes wrong.</p>
+</blockquote>
+
+<p>Once the entry has been added, the system will automatically mount
+the share when booting. Or, the system administrator can manually
+mount or unmount the share with commands such as these:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mount /smb/e</b></tt>
+# <tt class="userinput"><b>umount /smb/e</b></tt></pre></blockquote>
+
+<a name="samba2-CHP-5-NOTE-126"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>It is possible to use <em class="emphasis">mount</em> and
+<em class="emphasis">umount</em> by giving them the UNC for the share
+using forward slashes, as in our <em class="filename">/etc/fstab</em>
+entry. However, be careful about this. A share might be listed more
+than once in <em class="filename">/etc/fstab</em> so that it can be
+mounted at more than one place in the Linux filesystem. If you use
+the UNC to specify the share you wish to mount or unmount, you might
+cause it to be mounted or unmounted at another mount point from the
+one you intended.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-4.3"/>
+
+<h3 class="head2">Common smbmount Options</h3>
+
+<p><a href="ch05.html#samba2-CHP-5-TABLE-1">Table 5-1</a> lists
+<em class="replaceable">key</em><tt class="literal">=</tt><em class="replaceable">value</em>
+pairs that can be used with the <em class="emphasis">-o</em> option of
+<em class="emphasis">smbmount</em> or in the options field of the
+<em class="filename">/etc/fstab</em> entry for the smbfs filesystem. See
+the <em class="emphasis">smbmount</em> manual page for a complete list of
+options.</p>
+
+<a name="samba2-CHP-5-TABLE-1"/><h4 class="head4">Table 5-1. smbmount options</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Key</p>
+</th>
+<th>
+<p>Value</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">username</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Provides the username, and optionally the password and workgroup, for
+authentication.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">password</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Provides the share or domain password, if it hasn't
+been supplied by another means.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">credentials</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Name of file containing the username and password.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">uid</tt></p>
+</td>
+<td>
+<p>string or numeric</p>
+</td>
+<td>
+<p>User ID to apply to all files and directories of the mounted share.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">gid</tt></p>
+</td>
+<td>
+<p>string or numeric</p>
+</td>
+<td>
+<p>Group ID to apply to all files and directories of the mounted share.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">fmask</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Permissions to apply to files. Default is based on current umask.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">dmask</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Permissions to apply to directories. Default is based on current
+umask.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">debug</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Debug level.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">workgroup</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Name of workgroup of remote server.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">guest</tt></p>
+</td>
+<td>
+<p>(none)</p>
+</td>
+<td>
+<p>Suppresses password prompt.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ro</tt></p>
+</td>
+<td>
+<p>(none)</p>
+</td>
+<td>
+<p>Mount read-only.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">rw</tt></p>
+</td>
+<td>
+<p>(none)</p>
+</td>
+<td>
+<p>Mount read/write. This is the default.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ttl</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Amount of time to cache the contents of directories. Defaults to 1000
+ms <a name="INDEX-62"/>.</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-5"/>
+
+<h2 class="head1">smbsh</h2>
+
+<p>The <em class="emphasis">smbsh</em><a name="INDEX-63"/> program is part of the Samba suite and
+works on some, but not all, Unix variants.<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a> Effectively, it adds a wrapper around the
+user's command shell, enabling it and common Unix
+utilities to work on files and directories in SMB shares, in addition
+to files and directories in the local Unix filesystem. From the
+user's perspective, the effect is that of a
+simulated mount of the SMB shares onto the Unix filesystem.</p>
+
+<p><em class="emphasis">smbsh</em> works by running the shell and programs
+run from it in an environment in which calls to the standard C
+library are redirected to the
+<em class="emphasis">smbwrapper</em><a name="INDEX-64"/> library, which has support for
+operating on SMB shares. This redirection can work only if the
+program being run is dynamically linked. Fortunately, modern Unix
+versions ship with most common utilities linked dynamically rather
+than statically.</p>
+
+<a name="samba2-CHP-5-NOTE-127"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>To determine whether a program is dynamically or statically linked,
+try using the <em class="emphasis">file</em> command.</p>
+</blockquote>
+
+<p>To use <em class="emphasis">smbsh</em>, your Samba installation must be
+configured using the configure option
+<tt class="literal">--with-smbwrapper</tt>.</p>
+
+<p>If you have a number of Unix systems with the same host operating
+system and architecture and don't want to bother
+with a full Samba installation, you can simply move the following
+files to the other systems:</p>
+
+<blockquote><pre class="code">/usr/local/samba/bin/smbsh
+/usr/local/samba/bin/smbwrapper.so
+/usr/local/samba/lib/smb.conf</pre></blockquote>
+
+<p>Make sure that <em class="filename">/usr/local/samba/bin</em> is in your
+shell's search path. The
+<em class="filename">smb.conf</em><a name="INDEX-65"/><a name="INDEX-66"/> file is
+needed only for <em class="emphasis">smbsh</em> to determine the workgroup
+or domain and does not need to be as elaborate as your Samba
+server's configuration file.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-5.1"/>
+
+<h3 class="head2">An Interactive Session with smbsh</h3>
+
+<p><a name="INDEX-67"/>To start <em class="emphasis">smbsh</em>,
+simply type in the <em class="emphasis">smbsh</em> command at the shell
+prompt. You will be prompted for a username and password with which
+to authenticate on the SMB network:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbsh</b></tt>
+Username: davecb
+Password:
+smbsh$</pre></blockquote>
+
+<p>While working within the <em class="emphasis">smbsh</em> shell, you have a
+virtual <em class="filename">/smb</em> directory. This does not actually
+exist in the Unix filesystem and is supported within
+<em class="emphasis">smbsh</em> only to help organize the SMB shares in a
+structure familiar to Unix users. You can list the contents of the
+<em class="filename">/smb</em> virtual directory and get a list of
+workgroups in the local network, which are also presented as virtual
+directories:</p>
+
+<blockquote><pre class="code">smbsh$ <tt class="userinput"><b>cd /smb ; ls</b></tt>
+ZOOL PLANK BACIL</pre></blockquote>
+
+<p>You can change your working directory to one of the workgroup virtual
+directories, and listing one of them will show the computers in the
+workgroup:</p>
+
+<blockquote><pre class="code">smbsh$ <tt class="userinput"><b>cd ZOOL ; ls</b></tt>
+ANTILLES         DODO             MILO             SEAL
+ARGON            HANGGLIDE        OSTRICH          SPARTA
+BALLET           INFUSION         PLAQUE           THEBES
+CHABLIS          JAZ              PRAETORIAN       TJ
+COBRA            KIKO             RAYOPCI          TRANCE
+COUGUR           MACHINE-HEADPCI  RUMYA            VIPERPCI
+CRUSTY           MATHUMA          SCOT</pre></blockquote>
+
+<p>Likewise, you can change your current directory to, and list the
+contents of, a computer virtual directory, and then you can see a
+listing of shares offered by that computer:</p>
+
+<blockquote><pre class="code">smbsh$ <tt class="userinput"><b>cd scot ; ls</b></tt>
+ADMIN$      davecb      nc          np2s        pl
+ace         dhcp-mrk03  np          nps         xp
+cl          ep          np2         opcom</pre></blockquote>
+
+<p>This is the lowest level of
+<em class="emphasis">smbsh</em>'s virtual directory
+system. Once you <em class="emphasis">cd</em> into a share, you are within
+the SMB share on the remote computer:</p>
+
+<blockquote><pre class="code">smbsh$ <tt class="userinput"><b>cd davecb ; ls</b></tt>
+Mail                                mkanalysis_dirs.idx
+SUNWexplo                           nfs.ps
+Sent                                nsmail
+allsun.html                         projects.txt
+bin                                 sumtimex</pre></blockquote>
+
+<p>Once in a remote share, most of the Unix shell utilities will work,
+and you can operate on files and directories much as you would on any
+Unix system. You can even create symbolic links in the Unix
+filesystem pointing to files and directories in the SMB share.
+However, attempts to create symbolic links in the SMB share will fail
+unless the share is being served by Samba with support for Unix CIFS
+extensions.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-5-SECT-6"/>
+
+<h2 class="head1">smbutil and mount_smbfs</h2>
+
+<p>The <em class="emphasis">smbutil</em> and <em class="emphasis">mount_smbfs</em>
+programs provide SMB client functionality for FreeBSD, Darwin, and
+Mac OS X. Neither of the programs is part of the Samba distribution;
+however, we are including them to give you a little additional
+support in case you have BSD-related Unix systems on your network.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-6.1"/>
+
+<h3 class="head2">smbutil</h3>
+
+<p>The <em class="emphasis">smbutil</em><a name="INDEX-68"/> program provides functionality similar
+to some of the Samba suite's command-line utilities.
+It can be used to list the shares available on an SMB server or
+perform NetBIOS name lookups.</p>
+
+<p>The first argument given to <em class="emphasis">smbutil</em> is one of a
+number of subcommands and is usually followed by arguments specific
+to the subcommand. For example, to list the resources offered by a
+server, use the <em class="emphasis">view</em> subcommand, and enter your
+server password when prompted:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil view //vamana</b></tt>
+Password:
+Share        Type        Comment
+-------------------------------------------------------------
+public        disk
+SS2500        printer     Stylus Scan 2500
+IPC$          pipe        IPC Service (Samba 2.2.5)
+ADMIN$        disk        IPC Service (Samba 2.2.5)
+leonvs        disk        User Home Directories
+
+5 shares listed from 5 available</pre></blockquote>
+
+<p>If you wish to connect to the server with a username that differs
+from that on your client, you can specify it on the command line by
+preceding the name of the server with the username and using an at
+sign (<tt class="literal">@</tt>) as a separator:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil view //leonvs@vamana</b></tt></pre></blockquote>
+
+<p>You can also include the password after the username, using a colon
+(:) as a separator, to avoid being prompted for
+it:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil view //leonvs:leonspassword@vamana</b></tt></pre></blockquote>
+
+<p>Typing your password in the open like this is strongly discouraged.
+It's a little better if you use an encrypted
+password, which you can generate using
+<em class="emphasis">smbutil</em>'s
+<em class="emphasis">crypt</em> subcommand:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil crypt leonspassword</b></tt>
+$$1625a5723293f0710e5faffcfc6</pre></blockquote>
+
+<p>This can then be used in place of a clear-text password. However, the
+encryption is not particularly strong and will foil only the most
+casual inspection. As noted earlier, the only reasonably secure
+method of providing a password is to be prompted for it.</p>
+
+<p>While starting up, <em class="emphasis">smbutil</em> reads the file
+<em class="filename">.nsmbrc</em><a name="INDEX-69"/> in the user's home
+directory. Also, the file
+<em class="filename">/usr/local/etc/nsmb.conf</em><a name="INDEX-70"/><a name="INDEX-71"/> is read, and directives in that file
+override those in users'
+<em class="filename">~/.nsmbrc</em> files. This is to allow administrators
+to apply mandatory settings to all users. Directives can be placed in
+this file using the section and parameter format similar to that of
+the Samba configuration file. A list of common configuration
+parameters is given in <a href="ch05.html#samba2-CHP-5-TABLE-2">Table 5-2</a>.</p>
+
+<p>For example, to keep your password in your
+<em class="filename">~/.nsmbrc</em> file, you can create an entry in the
+file such as the following:</p>
+
+<blockquote><pre class="code">[VAMANA:LEONVS]
+    password=$$1625a5723293f0710e5faffcfc6</pre></blockquote>
+
+<p>The section heading in brackets specifies the SMB
+server's NetBIOS name and the username to which the
+subsequent parameter settings apply. (The hostname and username
+should be supplied in uppercase characters.) Section headings can
+also consist of just a hostname or can contain a share name as a
+third element for specifying parameters applicable to a single share.
+Finally, if a <tt class="literal">[default]</tt> section is present, the
+settings in it apply to all connections.</p>
+
+<p>The following example <em class="filename">.nsmbrc</em> shows some of the
+other parameters you might use:</p>
+
+<blockquote><pre class="code">[default]
+    username=leonvs
+    # NetBIOS name server
+    nbns=192.168.1.3
+
+[VAMANA]
+    # server IP address
+    addr=192.168.1.6
+    workgroup=TEST
+
+[VAMANA:LEONVS]
+    password=$$1625a5723293f0710e5faffcfc6</pre></blockquote>
+
+<p>Another thing you can do with <em class="emphasis">smbutil</em> is
+<a name="INDEX-72"/><a name="INDEX-73"/><a name="INDEX-74"/>translate between IP addresses or DNS
+names and
+<a name="INDEX-75"/>NetBIOS
+names. For example, the <em class="emphasis">status</em> subcommand takes
+an IP address or DNS hostname as an argument and returns the
+corresponding SMB server's NetBIOS name and
+workgroup:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil status 192.168.1.6</b></tt>
+Workgroup: TEST
+Server: VAMANA</pre></blockquote>
+
+<p>The <em class="emphasis">lookup</em> subcommand returns the IP address
+associated with a given NetBIOS hostname. A NetBIOS name server can
+be optionally specified with the <em class="emphasis">-w</em> argument:</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil lookup -w 192.168.1.3 VAMANA</b></tt>
+Got response from 192.168.1.3
+IP address of VAMANA: 192.168.1.6</pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-6.2"/>
+
+<h3 class="head2">mount_smbfs</h3>
+
+<p>The <em class="emphasis">mount_smbfs</em><a name="INDEX-76"/> program performs essentially the same
+function as <em class="emphasis">smbmount</em> on Linux. It mounts an SMB
+share on a directory in the local filesystem. The SMB share can then
+be accessed just like any other directory, subject to some behavioral
+differences noted earlier in <a href="ch05.html#samba2-CHP-5-SECT-4.1">Section 5.4.1</a>.</p>
+
+<p>The command synopsis for <em class="emphasis">mount_smbfs</em> is:</p>
+
+<blockquote><pre class="code">mount_smbfs <em class="replaceable">[options]</em> <em class="replaceable">Share-UNC</em> <em class="replaceable">mount-point</em></pre></blockquote>
+
+<p>where <em class="replaceable">Share-UNC</em> is of the form:</p>
+
+<blockquote><pre class="code">//[<em class="replaceable">workgroup</em>;][<em class="replaceable">username</em>[:<em class="replaceable">password</em>]@]<em class="replaceable">server</em>[/<em class="replaceable">share</em>]</pre></blockquote>
+
+<p>For example:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mount_smbfs '//TEST;leonvs:$$1625a5723293f0710e5faffcfc6@vamana/leonvs' /</b></tt>
+\<tt class="userinput"><b>Volumes/leonvs</b></tt></pre></blockquote>
+
+<p>The ownership and permissions of the mount point determine the
+default ownership and permissions for files and directories in the
+mounted share. These can be modified with command-line arguments,
+like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mount_smbfs -u leonvs -g admin -f 0750 -d 0755 //leonvs@vamana/leonvs </b></tt>
+\<tt class="userinput"><b>/Volumes/leonvs</b></tt></pre></blockquote>
+
+<p>In this example, the files and directories in the mounted share will
+be owned by the user leonvs and the group admin, with files and
+directories having permissions 750 and 755, respectively. (As usual,
+the permissions are specified in the octal format used by the Unix
+<em class="emphasis">chmod</em> command.)</p>
+
+<p>The <em class="emphasis">mount_smbfs</em><a name="INDEX-77"/><a name="INDEX-78"/> command
+also makes use of settings in
+<em class="filename">/usr/local/etc/nsmb.conf</em> and
+<em class="filename">~/.nsmbrc</em>, as described earlier. A list of
+common configuration parameters and command-line options is provided
+in <a href="ch05.html#samba2-CHP-5-TABLE-2">Table 5-2</a>.</p>
+
+<a name="samba2-CHP-5-TABLE-2"/><h4 class="head4">Table 5-2. Common smbutil and mount_smbfs options</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Command-line option</p>
+</th>
+<th>
+<p>Configuration file parameter</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">-I</tt> <em class="replaceable">hostname</em></p>
+</td>
+<td>
+<p><tt class="literal">addr</tt></p>
+</td>
+<td>
+<p>Avoid NetBIOS name resolution and connect to the server using the
+specified DNS hostname or IP address.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-N</p>
+</td>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p>Do not prompt for a password.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-R <em class="replaceable">count</em></p>
+</td>
+<td>
+<p><tt class="literal">retry_count</tt></p>
+</td>
+<td>
+<p>Number of times to retry connection before giving up.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-T <em class="replaceable">seconds</em></p>
+</td>
+<td>
+<p><tt class="literal">timeout</tt></p>
+</td>
+<td>
+<p>Timeout, in seconds, per connection request.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-U <em class="replaceable">username</em></p>
+</td>
+<td>
+<p><tt class="literal">username</tt></p>
+</td>
+<td>
+<p>Username to use for authentication. Defaults to Unix username.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-W <em class="replaceable">workgroup</em></p>
+</td>
+<td>
+<p><tt class="literal">workgroup</tt></p>
+</td>
+<td>
+<p>Name of workgroup of remote server.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-d <em class="replaceable">mode</em></p>
+</td>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p>Permissions to apply to directories in the mounted share. Defaults to
+the same as the file permissions, plus an execute (search) bit
+whenever the read bit is set.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-f <em class="replaceable">mode</em></p>
+</td>
+<td>
+<p><em class="filename">none</em></p>
+</td>
+<td>
+<p>Permissions to apply to files in the mounted share. Defaults to the
+same as the permissions set on the directory used as the mount point.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-g <em class="replaceable">group</em></p>
+</td>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p>Name or numeric GID to apply to all files and directories in the
+mounted share. Defaults to the group of the directory used as the
+mount point.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-n <em class="replaceable">long</em></p>
+</td>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p>Disable support for long filenames. Restrict filenames to 8.3 naming
+standard.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-u <em class="replaceable">username</em></p>
+</td>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p>Username or numeric UID to apply as the owner of all files and
+directories in the mounted share. Defaults to the owner of the
+directory used as the mount point.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>-w <em class="replaceable">hostname</em></p>
+</td>
+<td>
+<p><tt class="literal">nbns</tt></p>
+</td>
+<td>
+<p>Hostname or IP address of the NetBIOS name server.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><em class="emphasis">none</em></p>
+</td>
+<td>
+<p><tt class="literal">password</tt></p>
+</td>
+<td>
+<p>Password to use for authentication.</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-5-SECT-6.3"/>
+
+<h3 class="head2">Mac OS X</h3>
+
+<p><a name="INDEX-79"/>In addition to
+<em class="emphasis">smbutil</em> and <em class="emphasis">mount_smbfs</em>, OS
+X includes a graphical interface to the functionality they provide.
+To use this interface, open the Go menu and select the Connect to
+Server . . . menu item. Instead of using a UNC, specify the share in
+the form of a Uniform Resource Identifier (URI) with a prefix of
+<tt class="literal">smb://</tt> entered in the Address field, as shown in
+<a href="ch05.html#samba2-CHP-5-FIG-5">Figure 5-5</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-5"/><img src="figs/sam2_0505.gif"/></div><h4 class="head4">Figure 5-5. OS X Connect to Server dialog</h4>
+
+<p>You can specify a server, share, workgroup, username, and password
+(optionally encrypted with <em class="emphasis">smbutil crypt</em>) in the
+URI, in the same format as the UNC argument to
+<em class="emphasis">mount_smbfs</em>. If you don't
+specify a share name in the URI, you will be shown a window that lets
+you choose from a list of shares available to mount. See <a href="ch05.html#samba2-CHP-5-FIG-6">Figure 5-6</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-6"/><img src="figs/sam2_0506.gif"/></div><h4 class="head4">Figure 5-6. Selecting a share to mount</h4>
+
+<p>Only guest-accessible shares will show up in the list until
+you've authenticated. After pressing the
+Authenticate button, you'll be prompted for a
+workgroup, username, and password, as shown in <a href="ch05.html#samba2-CHP-5-FIG-7">Figure 5-7</a>. You'll also see this dialog
+if you provide a share name in the URI, but not a username and
+password.<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a></p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-7"/><img src="figs/sam2_0507.gif"/></div><h4 class="head4">Figure 5-7. Client authentication</h4>
+
+<p>As usual for Mac OS X, shares are mounted under
+<em class="filename">/Volumes</em>, but show up in the root of the Finder
+hierarchy.</p>
+
+<p>If you have a WINS server on your network, you can provide the
+server's IP address in the Directory Access
+application, or by using the <tt class="literal">wins</tt>
+<tt class="literal">server</tt> parameter in
+<em class="filename">/etc/smb.conf</em>.</p>
+
+<p>If you don't know the name of a server to which you
+wish to connect, you can look for it in the browse list, using the
+graphical frontend to the <em class="emphasis">nmblookup</em> command
+provided with Samba. Click the downward-pointing arrow in the Connect
+to Server . . . dialog box to show a hierarchical, column-based view
+of available workgroups and servers, similar to that shown in <a href="ch05.html#samba2-CHP-5-FIG-8">Figure 5-8</a>. If your client is also acting as an SMB file
+server, it won't show up in its own browse
+list.<a name="INDEX-80"/></p>
+
+<div class="figure"><a name="samba2-CHP-5-FIG-8"/><a name="INDEX-81"/><img src="figs/sam2_0508.gif"/></div><h4 class="head4">Figure 5-8. Browsing the network</h4>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> An alternative to extracting
+the tar archive directly to the SMB share is to use the Unix
+system's <em class="emphasis">tar</em> command to extract
+it to a directory on the Unix server, then copy the desired file(s)
+to a shared directory. This allows a greater amount of control over
+the restoration process, as when correcting for an accidental file
+deletion or reverting a set of files to a previous condition.</p>
+<a name="FOOTNOTE-2"/> <p><a href="#FNPTR-2">[2]</a> Samba Versions
+2.2.4 and later have support for Unix CIFS extensions developed by
+Hewlett-Packard, which add full support for Unix ownership, group,
+and permissions in smbfs filesystems when shared between two Samba
+systems. You will also need a recent version of smbfs in your Linux
+kernel.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> At the
+time of this writing, <em class="emphasis">smbsh</em> does not work on
+HP/UX or Linux. However, Linux support might return in the
+future.</p> <a name="FOOTNOTE-4"/> <p><a href="#FNPTR-4">[4]</a> If you've previously
+stored your authentication information in a Keychain, you will
+instead be prompted for your Keychain password.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch06.html b/docs/htmldocs/using_samba/ch06.html
new file mode 100644
index 0000000000..a507b7c9d9
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch06.html
@@ -0,0 +1,2727 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 6. The Samba Configuration File</h1>
+
+
+<p><a name="INDEX-1"/>In
+previous chapters, we showed you how to install Samba on a Unix
+server and set up Windows clients to use a simple disk share. This
+chapter will show you how Samba can assume more productive roles on
+your network.</p>
+
+<p>Samba's daemons, <em class="emphasis">smbd</em> and
+<em class="emphasis">nmbd</em>, are controlled through a single ASCII
+file, <em class="filename">smb.conf</em>, that can contain over 300 unique
+options (also called parameters). Some of these options you will use
+and change frequently; others you might never use, depending on how
+much functionality you want Samba to offer its clients.</p>
+
+<p>This chapter introduces the structure of the Samba configuration file
+and shows you how to use options to create and modify disk shares.
+Subsequent chapters will discuss browsing, how to configure users,
+security, printing, and other topics related to implementing Samba on
+your network.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-1"/>
+
+<h2 class="head1">The Samba Configuration File</h2>
+
+<p>The Samba configuration file, called <em class="filename">smb.conf</em> by
+default, uses the same format as Windows
+<em class="filename">.ini</em><a name="INDEX-2"/><a name="INDEX-3"/> files. If you have ever worked with a
+<em class="filename">.ini</em> file, you will find
+<em class="filename">smb.conf</em> easy to create and modify. Even if you
+haven't, you will find the format to be simple and
+easy to learn. Here is an example of a Samba
+<a name="INDEX-4"/>configuration
+file:</p>
+
+<blockquote><pre class="code">[global]
+    workgroup = METRAN
+    encrypt passwords = yes
+    wins support = yes
+    log level = 1 
+    max log size = 1000
+    read only = no
+[homes] 
+    browsable = no
+    map archive = yes
+[printers] 
+    path = /var/tmp
+    printable = yes
+    min print space = 2000
+[test]
+    browsable = yes
+    read only = yes
+    path = /usr/local/samba/tmp</pre></blockquote>
+
+<p>This configuration file is based on the one we created in <a href="ch02.html">Chapter 2</a> and sets up a workgroup in which Samba
+authenticates users using encrypted passwords and the default
+user-level security method. Samba is providing WINS name server
+support. We've configured very basic event logging
+to use a log file not to exceed 1MB in size. The
+<tt class="literal">[homes]</tt> share has been added to allow Samba to
+create a disk share for the home directory of each user who has a
+standard Unix account on the server. In addition, each printer
+registered on the server will be publicly available, as will a single
+read-only share that maps to the
+<em class="filename">/usr/local/samba/tmp</em> directory.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-1.1"/>
+
+<h3 class="head2">Configuration File Structure</h3>
+
+<p><a name="INDEX-5"/>Let's take another
+look at this configuration file, this time from a higher level:</p>
+
+<blockquote><pre class="code">[global] 
+    ...
+[homes] 
+    ...
+[printers] 
+    ...
+[test] 
+    ...</pre></blockquote>
+
+<p><a name="INDEX-6"/><a name="INDEX-7"/>The
+names inside the square brackets delineate unique
+<em class="firstterm">sections</em> of the <em class="filename">smb.conf</em>
+file; each section names the share (or service) to which the section
+refers. For example, the <tt class="literal">[test]</tt> and
+<tt class="literal">[homes]</tt> sections are unique disk shares; they
+contain options that map to specific directories on the Samba server.
+The <tt class="literal">[printers]</tt> share contains options that map to
+various printers on the server. All the sections defined in the
+<em class="filename">smb.conf</em> file, with the exception of the
+<tt class="literal">[global]</tt> section, will be available as a disk or
+printer share to clients connecting to the Samba server.</p>
+
+<p>The remaining lines are individual configuration options for that
+share. These options will continue until a new section is encountered
+or until the end of the file is reached. Each configuration option
+follows a simple format:</p>
+
+<blockquote><pre class="code"><em class="replaceable">option</em> = <em class="replaceable">value</em></pre></blockquote>
+
+<p><a name="INDEX-8"/>Options in
+the <em class="filename">smb.conf</em> file are set by assigning a value
+to them. We should warn you up front that some of the option names in
+Samba are poorly chosen. For example, <tt class="literal">read</tt>
+<tt class="literal">only</tt> is self-explanatory and is typical of many
+recent Samba options. The <tt class="literal">public</tt> option is an
+older option and is vague. It now has a less-confusing synonym
+<tt class="literal">guest</tt> <tt class="literal">ok</tt> (meaning it can be
+accessed by guests). <em class="emphasis">Appendix B</em> contains an
+alphabetical index of all the configuration options and their
+meanings.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-1.1.1"/>
+
+<h3 class="head3">Whitespace, quotes, and commas</h3>
+
+<p>An important item to remember about configuration options is that all
+whitespace within the <em class="replaceable">value</em> is
+significant. For example, consider the following option:</p>
+
+<blockquote><pre class="code">volume = The Big Bad Hard Drive Number 3543</pre></blockquote>
+
+<p>Samba strips away the spaces up to the first <tt class="literal">T</tt> in
+<tt class="literal">The</tt>. These whitespaces are insignificant. The rest
+of the whitespaces are significant and will be recognized and
+preserved by Samba when reading in the file. Space is not significant
+in option names (such as <tt class="literal">read</tt>
+<tt class="literal">only</tt>), but we recommend you follow convention and
+keep spaces between the words of options.</p>
+
+<p>If you feel safer including quotation marks at the beginning and end
+of a configuration option's value, you can do so.
+Samba will ignore these quotation marks when it encounters them.
+Never use quotation marks around an option name; Samba will treat
+this as an error.</p>
+
+<p>Usually, you can use whitespaces or commas to separate a series of
+values in a list. These two options are equivalent:</p>
+
+<blockquote><pre class="code">netbios aliases = sales, accounting, payroll
+netbios aliases = sales accounting payroll</pre></blockquote>
+
+<p>In some cases, you must use one form of separation&mdash;sometimes
+spaces are required, and sometimes commas.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-1.1.2"/>
+
+<h3 class="head3">Capitalization</h3>
+
+<p><a name="INDEX-9"/>Capitalization
+is not important in the Samba configuration file except in locations
+where it would confuse the underlying operating system. For example,
+let's assume that you included the following option
+in a share that pointed to <em class="filename">/export/samba/simple
+</em>:</p>
+
+<blockquote><pre class="code">PATH = /EXPORT/SAMBA/SIMPLE</pre></blockquote>
+
+<p>Samba would have no problem with the <tt class="literal">path</tt>
+configuration option appearing entirely in capital letters. However,
+when it tries to connect to the given directory, it would be
+unsuccessful because the Unix filesystem <em class="emphasis">is</em>
+case-sensitive. Consequently, the path listed would not be found, and
+clients could not connect to the share.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-1.1.3"/>
+
+<h3 class="head3">Line continuation</h3>
+
+<p><a name="INDEX-10"/>You can continue a line in the
+Samba configuration file using the backslash, like this:</p>
+
+<blockquote><pre class="code">comment = The first share that has the primary copies \
+          of the new Teamworks software product.</pre></blockquote>
+
+<p>Because of the backslash, these two lines will be treated as one line
+by Samba. The second line begins at the first nonwhitespace character
+that Samba encounters; in this case, the <tt class="literal">o</tt> in
+<tt class="literal">of</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-1.1.4"/>
+
+<h3 class="head3">Comments</h3>
+
+<p><a name="INDEX-11"/>You can
+insert comments in the <em class="filename">smb.conf</em> configuration
+file by starting a line with either a hash (<tt class="literal">#</tt>) or
+a semicolon ( <tt class="literal">;</tt> ). For this purpose, both
+characters are equivalent. For example, the first three lines in the
+following example would be considered comments:</p>
+
+<blockquote><pre class="code">#  This is the printers section. We have given a minimum print 
+;  space of 2000 to prevent some errors that we've seen when
+;  the spooler runs out of space.
+
+[printers] 
+    public = yes
+    min print space = 2000</pre></blockquote>
+
+<p>Samba will ignore all comment lines in its configuration file; there
+are no limitations to what can be placed on a comment line after the
+initial hash mark or semicolon. Note that the line continuation
+character (<tt class="literal">\</tt>) will <em class="emphasis">not</em> be
+honored on a commented line. Like the rest of the line, it is
+ignored.</p>
+<a name="samba2-CHP-6-NOTE-128"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Samba does not allow mixing of comment lines and parameters. Be
+careful not to put comments on the same line as anything else, such
+as:</p>
+
+
+<blockquote><pre class="code">path = /d # server's data partition</pre></blockquote>
+
+
+<p>Errors such as this, where the parameter value is defined with a
+string, can be tricky to notice. The <em class="emphasis">testparm</em>
+program won't complain, and the only clues
+you'll receive are that
+<em class="emphasis">testparm</em> reports the <tt class="literal">path</tt>
+parameter set to <tt class="literal">/d # server's data partition</tt>, and
+the failures that result when clients attempt to access the share.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-1.1.5"/>
+
+<h3 class="head3">Changes at runtime</h3>
+
+<p><a name="INDEX-12"/>You can modify the
+<em class="filename">smb.conf</em> configuration file and any of its
+options at any time while the Samba daemons are running. By default,
+Samba checks the configuration file every 60 seconds. If it finds any
+changes, they are immediately put into effect.</p>
+
+<a name="samba2-CHP-6-NOTE-129"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Having Samba check the configuration file automatically can be
+convenient, but it also means that if you edit
+<em class="filename">smb.conf</em> directly, you might be immediately
+changing your network's <a name="INDEX-13"/>configuration every time you save the
+file. If you're making anything more than a minor
+change, it may be wiser to copy <em class="filename">smb.conf</em> to a
+temporary file, edit that, run <tt class="literal">testparm</tt>
+<em class="replaceable">filename</em> to check it, and then copy the
+temporary file back to <em class="filename">smb.conf</em>. That way, you
+can be sure to put all your changes into effect at once, and only
+after you are confident that you have created the exact configuration
+you wish to implement.</p>
+</blockquote>
+
+<p>If you don't want to wait for the configuration file
+to be reloaded automatically, you can force a reload either by
+sending a hangup signal to the <em class="emphasis">smbd</em> and
+<em class="emphasis">nmbd</em> processes or simply by restarting the
+daemons. Actually, it can be a good idea to restart the daemons
+because it forces the clients to disconnect and reconnect, ensuring
+that the new configuration is applied to all clients. We showed you
+how to restart the daemons in <a href="ch02.html">Chapter 2</a>, and
+sending them a hangup (HUP) signal is very similar. On Linux, it can
+be done with the command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>killall -HUP smbd nmbd</b></tt></pre></blockquote>
+
+<p>In this case, not all changes will be immediately recognized by
+clients. For example, changes to a share that is currently in use
+will not be registered until the client disconnects and reconnects to
+that share. In addition, server-specific parameters such as the
+workgroup or NetBIOS name of the server will not go into effect
+immediately either. (This behavior was implemented intentionally
+because it keeps active clients from being suddenly disconnected or
+encountering unexpected access problems while a session is open.)
+<a name="INDEX-14"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-1.2"/>
+
+<h3 class="head2">Variables</h3>
+
+<p><a name="INDEX-15"/>Because a
+new copy of the<em class="filename"> </em><em class="emphasis">smbd</em> daemon
+is created for each connecting client, it is possible for each client
+to have its own customized configuration file. Samba allows a
+limited, yet useful, form of variable substitution in the
+configuration file to allow information about the Samba server and
+the client to be included in the configuration at the time the client
+connects. Inside the configuration file, a variable begins with a
+percent sign (<tt class="literal">%</tt>), followed by a single upper- or
+lowercase letter, and can be used only on the right side of a
+configuration option (i.e., after the equal sign). An example is:</p>
+
+<blockquote><pre class="code">[pub]
+    path = /home/ftp/pub/%a</pre></blockquote>
+
+<p>The <tt class="literal">%a</tt><a name="INDEX-16"/> stands for the client
+system's architecture and will be replaced as shown
+in <a href="ch06.html#samba2-CHP-6-TABLE-1">Table 6-1</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-1"/><h4 class="head4">Table 6-1. %a substitution</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Client operating system
+(&quot;architecture&quot;)</p>
+</th>
+<th>
+<p>Replacement string</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Windows for Workgroups</p>
+</td>
+<td>
+<p><tt class="literal">WfWg</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95 and Windows 98</p>
+</td>
+<td>
+<p><tt class="literal">Win95</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT</p>
+</td>
+<td>
+<p><tt class="literal">WinNT</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 2000 and Windows XP</p>
+</td>
+<td>
+<p><tt class="literal">Win2K</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Samba</p>
+</td>
+<td>
+<p><tt class="literal">Samba</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Any OS not listed earlier</p>
+</td>
+<td>
+<p><tt class="literal">UNKNOWN</tt></p>
+</td>
+</tr>
+
+</table>
+
+<p>In this example, Samba will assign a unique path for the
+<tt class="literal">[pub]</tt> share to client systems based on what
+operating system they are running. The paths that each client would
+see as its share differ according to the client's
+architecture:</p>
+
+<blockquote><pre class="code">/home/ftp/pub/WfwG
+/home/ftp/pub/Win95
+/home/ftp/pub/WinNT
+/home/ftp/pub/Win2K
+/home/ftp/pub/Samba
+/home/ftp/pub/UNKNOWN</pre></blockquote>
+
+<p>Using variables in this manner comes in handy if you wish to have
+different users run custom configurations based on their own unique
+characteristics or conditions.
+<a name="INDEX-17"/><a name="INDEX-18"/>Samba
+has 20 variables, as shown in <a href="ch06.html#samba2-CHP-6-TABLE-2">Table 6-2</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-2"/><h4 class="head4">Table 6-2. Samba variables</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Variable</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><b class="emphasis-bold">Client variables</b></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%a</tt><a name="INDEX-19"/></p>
+</td>
+<td>
+<p>Client's architecture (see <a href="ch06.html#samba2-CHP-6-TABLE-1">Table 6-1</a>)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%I</tt><a name="INDEX-20"/></p>
+</td>
+<td>
+<p>Client's IP address (e.g., 172.16.1.2)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%m</tt><a name="INDEX-21"/></p>
+</td>
+<td>
+<p>Client's NetBIOS name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%M</tt><a name="INDEX-22"/></p>
+</td>
+<td>
+<p>Client's DNS name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><b class="emphasis-bold">User variables</b></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%u</tt><a name="INDEX-23"/></p>
+</td>
+<td>
+<p>Current Unix username</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%U</tt><a name="INDEX-24"/></p>
+</td>
+<td>
+<p>Requested client username (not always used by Samba)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%H</tt><a name="INDEX-25"/></p>
+</td>
+<td>
+<p>Home directory of <tt class="literal">%u</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%g</tt><a name="INDEX-26"/></p>
+</td>
+<td>
+<p>Primary group of <tt class="literal">%u</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%G</tt><a name="INDEX-27"/></p>
+</td>
+<td>
+<p>Primary group of <tt class="literal">%U</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><b class="emphasis-bold">Share variables</b></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%S</tt><a name="INDEX-28"/></p>
+</td>
+<td>
+<p>Current share's name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%P</tt><a name="INDEX-29"/></p>
+</td>
+<td>
+<p>Current share's root directory</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%p</tt><a name="INDEX-30"/></p>
+</td>
+<td>
+<p>Automounter's path to the share's
+root directory, if different from <tt class="literal">%P</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><b class="emphasis-bold">Server variables</b></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%d</tt><a name="INDEX-31"/></p>
+</td>
+<td>
+<p>Current server process ID</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%h</tt><a name="INDEX-32"/></p>
+</td>
+<td>
+<p>Samba server's DNS hostname</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%L</tt><a name="INDEX-33"/></p>
+</td>
+<td>
+<p>Samba server's NetBIOS name</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%N</tt><a name="INDEX-34"/></p>
+</td>
+<td>
+<p>Home directory server, from the automount map</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%v</tt><a name="INDEX-35"/></p>
+</td>
+<td>
+<p>Samba version</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><b class="emphasis-bold">Miscellaneous variables</b></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%R</tt><a name="INDEX-36"/></p>
+</td>
+<td>
+<p>The SMB protocol level that was negotiated</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%T</tt><a name="INDEX-37"/></p>
+</td>
+<td>
+<p>The current date and time</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><a name="INDEX-38"/>%$<em class="replaceable">var</em></p>
+</td>
+<td>
+<p>The value of environment variable <tt class="literal">var</tt></p>
+</td>
+</tr>
+
+</table>
+
+<p>Here's another example of using
+<a name="INDEX-39"/><a name="INDEX-40"/><a name="INDEX-41"/>variables: let's say there
+are five clients on your network, but one client,
+<tt class="literal">maya</tt>, requires a slightly different
+<tt class="literal">[homes]</tt> configuration. With Samba,
+it's simple to handle this:</p>
+
+<blockquote><pre class="code">[homes] 
+    ...
+    include = /usr/local/samba/lib/smb.conf.%m
+    ...</pre></blockquote>
+
+<p>The <tt class="literal">include</tt> option here causes a separate
+configuration file for each particular NetBIOS machine
+(<tt class="literal">%m</tt>) to be read in addition to the current file.
+If the hostname of the client system is <tt class="literal">maya</tt>, and
+if a <em class="filename">smb.conf.maya</em> file exists in the
+<em class="filename">/usr/local/samba/lib</em> directory, Samba will
+insert that configuration file into the default one. If any
+configuration options are restated in
+<em class="filename">smb.conf.maya</em>, those values will override any
+options previously encountered in that share. Note that we say
+&quot;previously.&quot; If any options are
+restated in the main configuration file after the
+<tt class="literal">include</tt> option, Samba will honor those restated
+values for the share in which they are defined.</p>
+
+<p>If the file specified by the <tt class="literal">include</tt> parameter
+does not exist, Samba will not generate an error. In fact, it
+won't do anything at all. This allows you to create
+only one extra configuration file for <tt class="literal">maya</tt> when
+using this strategy, instead of one for each client that is on the
+network.</p>
+
+<p>Client-specific configuration files can be used to customize
+particular clients. They also can be used to make debugging Samba
+easier. For example, if we have one client with a problem, we can use
+this approach to give it a private log file with a more verbose
+logging level. This allows us to see what Samba is doing without
+slowing down all the other clients or overflowing the disk with
+useless logs.</p>
+
+<p>You can use the variables in <a href="ch06.html#samba2-CHP-6-TABLE-2">Table 6-2</a> to give
+custom values to a variety of Samba options. We will highlight
+several of these options as we move through the next few chapters.
+<a name="INDEX-42"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-2"/>
+
+<h2 class="head1">Special Sections</h2>
+
+<p>Now that we've gotten our feet wet with variables,
+there are a few special sections of the Samba configuration file that
+we should talk about. Again, don't worry if you do
+not understand every configuration option listed here;
+we'll go over each of them in the upcoming chapters.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-2.1"/>
+
+<h3 class="head2">The [ global] Section</h3>
+
+<p>The <tt class="literal">[global]</tt><a name="INDEX-43"/><a name="INDEX-44"/> section appears in virtually
+every Samba configuration file, even though it is not mandatory.
+There are two purposes for the <tt class="literal">[global]</tt> section.
+Server-wide settings are defined here, and any options that apply to
+shares will be used as a default in all share definitions, unless
+overridden within the share definition.</p>
+
+<p>To illustrate this, let's again look at the example
+at the beginning of the chapter:</p>
+
+<blockquote><pre class="code">[global]
+    workgroup = METRAN
+    encrypt passwords = yes
+    wins support = yes
+    log level = 1 
+    max log size = 1000
+    read only = no
+[homes] 
+    browsable = no
+    map archive = yes
+[printers] 
+    path = /var/tmp
+    printable = yes
+    min print space = 2000
+[test]
+    browsable = yes
+    read only = yes
+    path = /usr/local/samba/tmp</pre></blockquote>
+
+<p>When a client connects to the <tt class="literal">[test]</tt> share, Samba
+first reads the <tt class="literal">[global]</tt> section and sets the
+option <tt class="literal">read</tt> <tt class="literal">only</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt> as the global default for
+each share it encounters throughout the configuration file. This
+includes the <tt class="literal">[homes]</tt> and <tt class="literal">[test]</tt>
+shares. When it reads the definition of the <tt class="literal">[test]</tt>
+share, it then finds the configuration option <tt class="literal">read</tt>
+<tt class="literal">only</tt> <tt class="literal">=</tt> <tt class="literal">yes</tt>
+and overrides the default from the <tt class="literal">[global]</tt>
+section with the value <tt class="literal">yes</tt>.</p>
+
+<p>Any option that appears before the first marked section is assumed to
+be a global option. This means that the <tt class="literal">[global]</tt>
+section heading is not absolutely required; however, we suggest you
+always include it for clarity and to ensure future compatibility.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-2.2"/>
+
+<h3 class="head2">The [ homes] Section</h3>
+
+<p>If a client attempts to connect to a share that
+doesn't appear in the <em class="filename">smb.conf</em>
+file, Samba will search for a
+<tt class="literal">[homes]</tt><a name="INDEX-45"/><a name="INDEX-46"/> share in the
+configuration file. If a <tt class="literal">[homes]</tt> share exists, the
+unresolved share name is assumed to be a Unix username. If that
+username appears in the password database on the Samba server, Samba
+assumes the client is a Unix user trying to connect to her home
+directory on the server.</p>
+
+<p>For example, assume a client system is connecting to the Samba server
+<tt class="literal">toltec</tt> for the first time and tries to connect to
+a share named <tt class="literal">[alice]</tt>. There is no
+<tt class="literal">[alice]</tt> share defined in the
+<em class="filename">smb.conf</em> file, but there is a
+<tt class="literal">[homes]</tt>, so Samba searches the password database
+file and finds an <tt class="literal">alice</tt> user account is present on
+the system. Samba then checks the password provided by the client
+against user <tt class="literal">alice</tt>'s Unix
+password&mdash;either with the password database file if
+it's using nonencrypted passwords or with
+Samba's <em class="filename">smbpasswd</em> file if
+encrypted passwords are in use. If the passwords match, Samba knows
+it has guessed right: the user <tt class="literal">alice</tt> is trying to
+connect to her home directory. Samba will then create a share called
+<tt class="literal">[alice]</tt> for her, with the share's
+path set to <tt class="literal">alice</tt>'s home
+directory.</p>
+
+<p>The process of using the <tt class="literal">[homes]</tt> section to create
+users (and dealing with their passwords) is discussed in more detail
+in <a href="ch09.html">Chapter 9</a>.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-2.3"/>
+
+<h3 class="head2">The [printers] Section</h3>
+
+<p>The third special section is called
+<tt class="literal">[printers]</tt><a name="INDEX-47"/><a name="INDEX-48"/> and is similar to
+<tt class="literal">[homes]</tt>. If a client attempts to connect to a
+share that isn't in the
+<em class="filename">smb.conf</em> file and its name
+can't be found in the password file, Samba will
+check to see if it is a printer share. Samba does this by reading the
+printer capabilities file (usually
+<em class="filename">/etc/printcap</em>) to see if the share name appears
+there.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> If it does, Samba creates a share named after the
+printer.</p>
+
+<p>This means that as with <tt class="literal">[homes]</tt>, you
+don't have to maintain a share for each system
+printer in the <em class="filename">smb.conf</em> file. Instead, Samba
+honors the Unix printer registry if you ask it to, and it provides
+the registered printers to the client systems. However, there is a
+potential difficulty: if you have an account named
+<tt class="literal">fred</tt> and a printer named <tt class="literal">fred</tt>,
+Samba will always find the user account first, even if the client
+really needed to connect to the printer.</p>
+
+<p>The process of setting up the <tt class="literal">[printers]</tt> share is
+discussed in more detail in <a href="ch10.html">Chapter 10</a>.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-3"/>
+
+<h2 class="head1">Configuration Options</h2>
+
+<p><a name="INDEX-49"/>Options in
+the Samba configuration files fall into one of two categories:
+<em class="firstterm">global</em> options or <em class="firstterm">share</em>
+options. Each category dictates where an option can appear in the
+configuration file.</p>
+
+<dl>
+<dt><b>Global options</b></dt>
+<dd>
+<p>Global options must appear in the <tt class="literal">[global]</tt> section
+and nowhere else. These are options that typically apply to the
+behavior of the Samba server itself and not to any of its shares.</p>
+</dd>
+
+
+
+<dt><b>Share options</b></dt>
+<dd>
+<p>Share options can appear in share definitions, the
+<tt class="literal">[global]</tt> section, or both. If they appear in the
+<tt class="literal">[global]</tt> section, they will define a default
+behavior for all shares unless a share overrides the option with a
+value of its own.</p>
+</dd>
+
+</dl>
+
+<p>In addition, configuration options can take three kinds of values.
+They are as follows:</p>
+
+<dl>
+<dt><b>Boolean</b></dt>
+<dd>
+<p>These are simply yes or no values, but can be represented by any of
+the following: <tt class="literal">yes</tt>, <tt class="literal">no</tt>,
+<tt class="literal">true</tt>, <tt class="literal">false</tt>,
+<tt class="literal">1</tt>, or <tt class="literal">0</tt>. The values are
+case-insensitive: <tt class="literal">YES</tt> is the same as
+<tt class="literal">yes</tt>.</p>
+</dd>
+
+
+
+<dt><b>Numeric</b></dt>
+<dd>
+<p>This is a decimal, hexadecimal, or octal number. The standard
+<tt class="literal">0x</tt><em class="emphasis">nn</em> syntax is used for
+hexadecimal and <tt class="literal">0</tt><em class="emphasis">nnn</em> for
+octal.</p>
+</dd>
+
+
+
+<dt><b>String</b></dt>
+<dd>
+<p>This is a string of case-sensitive characters, such as a filename or
+a username.</p>
+</dd>
+
+</dl>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-3.1"/>
+
+<h3 class="head2">Configuration File Options</h3>
+
+<p>You can instruct Samba to include or replace configuration options as
+it is processing them. The options to do this are summarized in <a href="ch06.html#samba2-CHP-6-TABLE-3">Table 6-3</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-3"/><h4 class="head4">Table 6-3. Configuration file options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">config</tt> <tt class="literal">file</tt></p>
+</td>
+<td>
+<p>string (name of file)</p>
+</td>
+<td>
+<p>Sets the location of a configuration file to use instead of the
+current one</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">include</tt></p>
+</td>
+<td>
+<p>string (name of file)</p>
+</td>
+<td>
+<p>Specifies an additional set of configuration options to be included
+in the configuration file</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">copy</tt></p>
+</td>
+<td>
+<p>string (name of share)</p>
+</td>
+<td>
+<p>Allows you to clone the configuration options of another share in the
+current share</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-3.1.1"/>
+
+<h3 class="head3">config file</h3>
+
+<p>The global <tt class="literal">config</tt><a name="INDEX-50"/> <tt class="literal">file</tt>
+option specifies a replacement configuration file that will be loaded
+when the option is encountered. If the target file exists, the
+remainder of the current configuration file, as well as the options
+encountered so far, will be discarded, and Samba will configure
+itself entirely with the options in the new file. Variables can be
+used with the <tt class="literal">config</tt> <tt class="literal">file</tt>
+option, which is useful in the event that you want to use a special
+configuration file based on the NetBIOS machine name or user of the
+client that is connecting.</p>
+
+<p>For example, the following line instructs Samba to use a
+configuration file specified by the NetBIOS name of the client
+connecting, if such a file exists. If it does, options specified in
+the original configuration file are ignored:</p>
+
+<blockquote><pre class="code">[global]
+    config file = /usr/local/samba/lib/smb.conf.%m</pre></blockquote>
+
+<p>If the configuration file specified does not exist, the option is
+ignored, and Samba will continue to configure itself based on the
+current file. This allows a default configuration file to serve most
+clients, while providing for exceptions with customized configuration
+files.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-3.1.2"/>
+
+<h3 class="head3">include</h3>
+
+<p>This <a name="INDEX-51"/>option, discussed in greater detail
+earlier, copies the target file into the current configuration file
+at the point specified, as shown in <a href="ch06.html#samba2-CHP-6-FIG-1">Figure 6-1</a>.
+This option also can be used with variables. You can use this option
+as follows:</p>
+
+<blockquote><pre class="code">[global]
+    include = /usr/local/samba/lib/smb.conf.%m</pre></blockquote>
+
+<p>If the configuration file specified does not exist, the option is
+ignored. Options in the include file override any option specified
+previously, but not options that are specified later. In <a href="ch06.html#samba2-CHP-6-FIG-1">Figure 6-1</a>, all three options will override their
+previous values.</p>
+
+<div class="figure"><a name="samba2-CHP-6-FIG-1"/><img src="figs/sam2_0601.gif"/></div><h4 class="head4">Figure 6-1. The include option in a Samba configuration file</h4>
+
+<p>The <tt class="literal">include</tt> option does not work with the
+variables <tt class="literal">%u</tt> (user), <tt class="literal">%P</tt>
+(current share's root directory), or
+<tt class="literal">%S</tt> (current share's name) because
+they are not set at the time the <tt class="literal">include</tt> parameter
+is processed.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-3.1.3"/>
+
+<h3 class="head3">copy</h3>
+
+<p>The <tt class="literal">copy</tt><a name="INDEX-52"/> configuration option allows you to clone
+the configuration options of the share name that you specify in the
+current share. The target share must appear earlier in the
+configuration file than the share that is performing the copy. For
+example:</p>
+
+<blockquote><pre class="code">[template]
+    writable = yes
+    browsable = yes
+    valid users = andy, dave, jay
+
+[data]
+    path = /usr/local/samba
+    copy = template</pre></blockquote>
+
+<p>Note that any options in the share that invoked the
+<tt class="literal">copy</tt> directive will override those in the cloned
+share; it does not matter whether they appear before or after the
+<tt class="literal">copy</tt> directive. <a name="INDEX-53"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-4"/>
+
+<h2 class="head1">Server Configuration</h2>
+
+<p><a name="INDEX-54"/>We will now start from
+scratch and build a configuration file for our Samba server. First we
+will introduce three basic configuration options that can appear in
+the <tt class="literal">[global]</tt> section of the
+<em class="filename">smb.conf</em> file:</p>
+
+<blockquote><pre class="code">[global]
+    #  Server configuration parameters
+    netbios name = toltec
+    server string = Samba %v on %L
+    workgroup = METRAN
+    encrypt passwords = yes</pre></blockquote>
+
+<p>This configuration file is pretty simple; it advertises the Samba
+server under the NetBIOS name <tt class="literal">toltec</tt>. In addition,
+it places the system in the METRAN workgroup and displays a
+description to clients that includes the Samba version number, as
+well as the NetBIOS name of the Samba server.</p>
+
+<a name="samba2-CHP-6-NOTE-130"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you used the line <tt class="literal">encrypt passwords = yes</tt> in
+your earlier configuration file, you should do so here as well.</p>
+</blockquote>
+
+<p>If you like, you can go ahead and try this configuration file. Create
+a file named <em class="filename">smb.conf</em> under the
+<em class="filename">/usr/local/samba/lib</em> directory with the text
+listed earlier. Then restart the Samba server and use a Windows
+client to verify the results. Be sure that your Windows clients are
+in the METRAN workgroup as well. After double-clicking the Network
+Neighborhood on a Windows client, you should see a window similar to
+<a href="ch06.html#samba2-CHP-6-FIG-2">Figure 6-2</a>. (In this figure,
+<tt class="literal">Mixtec</tt> is another Samba server,
+<tt class="literal">a</tt>nd <tt class="literal">Zapotec</tt> is a Windows
+client.)</p>
+
+<div class="figure"><a name="samba2-CHP-6-FIG-2"/><img src="figs/sam2_0602.gif"/></div><h4 class="head4">Figure 6-2. Network Neighborhood showing Toltec, the Samba server</h4>
+
+<p>You can verify the <tt class="literal">server</tt>
+<tt class="literal">string</tt> by listing the details of the Network
+Neighborhood window (select Details in the View menu). You should see
+a window similar to <a href="ch06.html#samba2-CHP-6-FIG-3">Figure 6-3</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-6-FIG-3"/><img src="figs/sam2_0603.gif"/></div><h4 class="head4">Figure 6-3. Network Neighborhood details listing</h4>
+
+<p>If you were to click the <em class="filename">toltec</em> icon, a window
+should appear that shows the services that it provides. In this case,
+the window would be completely empty because there are no shares on
+the server yet.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-4.1"/>
+
+<h3 class="head2">Server Configuration Options</h3>
+
+<p><a href="ch06.html#samba2-CHP-6-TABLE-4">Table 6-4</a> summarizes the server configuration
+options introduced previously. All three of these options are global
+in scope, so they must appear in the <tt class="literal">[global]</tt>
+section of the configuration file.<a name="INDEX-55"/></p>
+
+<a name="samba2-CHP-6-TABLE-4"/><h4 class="head4">Table 6-4. Server configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">netbios</tt> <tt class="literal">name</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>NetBIOS name of the Samba server</p>
+</td>
+<td>
+<p>Server's unqualified DNS hostname</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">workgroup</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>NetBIOS group to which the server belongs</p>
+</td>
+<td>
+<p>Defined at compile time</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">server</tt> <tt class="literal">string</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Descriptive string for the Samba server</p>
+</td>
+<td>
+<p><tt class="literal">Samba %v</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-4.1.1"/>
+
+<h3 class="head3">netbios name</h3>
+
+<p>The <tt class="literal">netbios</tt><a name="INDEX-56"/> <tt class="literal">name</tt> option
+allows you to set the NetBIOS name of the server. For example:</p>
+
+<blockquote><pre class="code">netbios name = YORKVM1</pre></blockquote>
+
+<p>The default value for this configuration option is the
+server's hostname&mdash;that is, the first part of
+its fully qualified domain name. For example, a system with the DNS
+name <tt class="literal">ruby.ora.com</tt> would be given the NetBIOS name
+<tt class="literal">RUBY</tt> by default. While you can use this option to
+restate the system's NetBIOS name in the
+configuration file (as we did previously), it is more commonly used
+to assign the Samba server a NetBIOS name other than its current DNS
+name. Remember that the name given must follow the rules for valid
+NetBIOS machine names as outlined in <a href="ch01.html">Chapter 1</a>.</p>
+
+<p>Changing the NetBIOS name of the server is not recommended unless you
+have a good reason. One such reason might be if the hostname of the
+system is not unique because the LAN is divided over two or more DNS
+domains. For example, YORKVM1 is a good NetBIOS candidate for
+<tt class="literal">vm1.york.example.com</tt> to differentiate it from
+<tt class="literal">vm1.falkirk.example.com</tt>, which has the same
+hostname but resides in a different DNS domain.</p>
+
+<p>Another use of this option is for relocating SMB services from a dead
+or retired system. For example, if <tt class="literal">SALES</tt> is the
+SMB server for the department and it suddenly dies, you could
+immediately reset <tt class="literal">netbios</tt> <tt class="literal">name</tt>
+<tt class="literal">=</tt> <tt class="literal">SALES</tt> on a backup Samba
+server that's taking over for it. Users
+won't have to change their drive mappings to a
+different server; new connections to <tt class="literal">SALES</tt> will
+simply go to the new server.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-4.1.2"/>
+
+<h3 class="head3">workgroup</h3>
+
+<p>The <tt class="literal">workgroup</tt><a name="INDEX-57"/> parameter sets the
+current workgroup (or domain) in which the Samba server will
+advertise itself. Clients that wish to access shares on the Samba
+server should be in the same NetBIOS group. Remember that workgroups
+are really just NetBIOS group names and must follow the standard
+NetBIOS naming conventions outlined in <a href="ch01.html">Chapter 1</a>.</p>
+
+<p>The default option for this parameter is set at compile time to
+<tt class="literal">WORKGROUP</tt>. Because this is the default workgroup
+name of every unconfigured Windows and Samba system, we recommend
+that you always set your workgroup name in the Samba configuration
+file. When choosing your workgroup name, try to avoid making it the
+same name as a server or user. This will avoid possible problems with
+WINS name resolution.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-4.1.3"/>
+
+<h3 class="head3">server string</h3>
+
+<p>The <tt class="literal">server</tt><a name="INDEX-58"/> <tt class="literal">string</tt>
+parameter defines a comment string that will appear next to the
+server name in both the Network Neighborhood (when shown with the
+Details view) and the comment entry of the Microsoft Windows printer
+manager.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> </p>
+
+<p>You can use variables to provide
+information in the description. For example, our entry earlier was:</p>
+
+<blockquote><pre class="code">[global]
+    server string = Samba %v on (%h)</pre></blockquote>
+
+<p>The default for this option simply presents the current version of
+Samba and is equivalent to:</p>
+
+<a name="INDEX-59"/><blockquote><pre class="code">server string = Samba %v</pre></blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-5"/>
+
+<h2 class="head1">Disk Share Configuration</h2>
+
+<p><a name="INDEX-60"/><a name="INDEX-61"/>We mentioned in the previous section that
+there were no disk shares on the <tt class="literal">toltec</tt> server.
+Let's continue building the configuration file and
+create an empty disk share called <tt class="literal">[data]</tt>. Here are
+the additions that will do it:</p>
+
+<blockquote><pre class="code">[data]
+    path = /export/samba/data
+    comment = Data Drive
+    volume = Sample-Data-Drive
+    writable = yes</pre></blockquote>
+
+<p>The <tt class="literal">[data]</tt> share is typical for a Samba disk
+share. The share maps to the directory <em class="filename">/export/samba/data
+</em>on the Samba server. We've also provided
+a comment that describes the share as a <tt class="literal">Data</tt>
+<tt class="literal">Drive</tt>, as well as a volume name for the share
+itself.</p>
+
+<p>Samba's default is to create a read-only share. As a
+result, the <tt class="literal">writable</tt> option needs to be explicitly
+set for each disk share you wish to make writable.</p>
+
+<p>We will also need to create the
+<em class="filename">/export/samba/data</em> directory on the Samba server
+with the following commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /export/samba/data</b></tt>
+# <tt class="userinput"><b>chmod 777 /export/samba/data</b></tt></pre></blockquote>
+
+<p>Now, if we connect to the <tt class="literal">toltec</tt> server again by
+double-clicking its icon in the Windows Network Neighborhood, we will
+see a single share entitled <tt class="literal">data</tt>, as shown in
+<a href="ch06.html#samba2-CHP-6-FIG-4">Figure 6-4</a>. This share has read/write access, so
+files can be copied to or from it.</p>
+
+<div class="figure"><a name="samba2-CHP-6-FIG-4"/><img src="figs/sam2_0604.gif"/></div><h4 class="head4">Figure 6-4. The initial data share on the Samba server</h4>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-5.1"/>
+
+<h3 class="head2">Disk Share Configuration Options</h3>
+
+<p>The basic Samba configuration options for disk shares previously
+introduced are listed in <a href="ch06.html#samba2-CHP-6-TABLE-5">Table 6-5</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-5"/><h4 class="head4">Table 6-5. Basic share configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">path</tt> <tt class="literal">(directory)</tt></p>
+</td>
+<td>
+<p>string (directory name)</p>
+</td>
+<td>
+<p>Sets the Unix directory that will be provided for a disk share or
+used for spooling by a printer share.</p>
+</td>
+<td>
+<p><tt class="literal">/tmp</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">comment</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Sets the comment that appears with the share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">volume</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Sets the MS-DOS volume name for the share.</p>
+</td>
+<td>
+<p>Share name</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">read only</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows read-only access to a share.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">writable</tt> <tt class="literal">(write ok or writeable)</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">no</tt>, allows read-only access to a share. If
+<tt class="literal">yes</tt>, both reading and writing are allowed.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-5.1.1"/>
+
+<h3 class="head3">path</h3>
+
+<p>This <a name="INDEX-63"/>option, which has the synonym
+<tt class="literal">directory</tt>, indicates the pathname for the root of
+the shared directory or printer. You can choose any directory on the
+Samba server, so long as the owner of the Samba process that is
+connecting has read and write access to that directory. If the path
+is for a printing share, it should point to a temporary directory
+where files can be written on the server before being spooled to the
+target printer ( <em class="filename"> /tmp</em> and
+<em class="filename">/var/spool</em> are popular choices). If this path is
+for a disk share, the contents of the folder representing the share
+name on the client will match the contents of the directory on the
+Samba server.</p>
+
+<p>The directory specified as the value for <tt class="literal">path</tt> can
+be given as a relative path, in which case it will be relative to the
+directory specified by the <tt class="literal">root</tt>
+<tt class="literal">directory</tt> parameter. Because
+<tt class="literal">root</tt> <tt class="literal">directory</tt> defaults to root
+(<em class="filename">/</em> ), it is generally a good idea to use
+absolute paths for the <tt class="literal">path</tt> parameter, unless
+<tt class="literal">root</tt> <tt class="literal">directory</tt> has been set to
+something other than the default.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-5.1.2"/>
+
+<h3 class="head3">comment</h3>
+
+<p>The <tt class="literal">comment</tt><a name="INDEX-64"/> option allows you to enter a
+comment that will be sent to the client when it attempts to browse
+the share. The user can see the comment by using the Details view on
+the share folder or with the <em class="emphasis">net view</em> command at
+an MS-DOS prompt. For example, here is how you might insert a comment
+for a share:</p>
+
+<blockquote><pre class="code">[network]
+    comment = Network Drive
+    path = /export/samba/network</pre></blockquote>
+
+<p>Be sure not to confuse the <tt class="literal">comment</tt> option, which
+documents a Samba server's shares, with the
+<tt class="literal">server</tt> <tt class="literal">string</tt> option, which
+documents the server itself.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-5.1.3"/>
+
+<h3 class="head3">volume</h3>
+
+<p>This <a name="INDEX-65"/>option allows you to specify the volume
+name of the share, which would otherwise default to the name of the
+share given in the <em class="filename">smb.conf</em> file.</p>
+
+<p>Some software installation programs check the volume name of the
+distribution CD-ROM to make sure the correct CD-ROM is in the drive
+before attempting to install from it. If you copy the contents of the
+CD-ROM into a network share and wish to install from there, you can
+use this option to make sure the installation program sees the
+correct volume name:</p>
+
+<blockquote><pre class="code">[network]
+    comment = Network Drive
+    volume = ASVP-102-RTYUIKA
+    path = /home/samba/network</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-5.1.4"/>
+
+<h3 class="head3">read only, writable</h3>
+
+<p>The options <tt class="literal">read</tt><a name="INDEX-66"/> <tt class="literal">only</tt>
+and <tt class="literal">writable</tt><a name="INDEX-67"/> (also called
+<tt class="literal">writeable</tt><a name="INDEX-68"/> or
+<tt class="literal">write</tt><a name="INDEX-69"/> <tt class="literal">ok</tt> ) are really two
+ways of saying the same thing, but they are approached from opposite
+ends. For example, you can set either of the following options in the
+<tt class="literal">[global]</tt> section or in an individual share:</p>
+
+<blockquote><pre class="code">read only = yes
+writable = no</pre></blockquote>
+
+<p>If either option is set as shown, data can be read from a share, but
+cannot be written to it. You might think you would need this option
+only if you were creating a read-only share. However, note that this
+read-only behavior is the <em class="emphasis">default</em> action for
+shares; if you want to be able to write data to a share, you must
+explicitly specify one of the following options in the configuration
+file for each share:</p>
+
+<blockquote><pre class="code">read only = no
+writable = yes</pre></blockquote>
+
+<p>If you specify more than one occurrence of either option, Samba will
+adhere to the last value it encounters for the share. <a name="INDEX-70"/><a name="INDEX-71"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-6"/>
+
+<h2 class="head1">Networking Options with Samba</h2>
+
+<p><a name="INDEX-72"/><a name="INDEX-73"/>If
+you're running <a name="INDEX-74"/><a name="INDEX-75"/>Samba on a multihomed
+system (on multiple subnets), you will need to configure Samba to use
+all the network interfaces. Another use for the options presented in
+this section is to implement better security by allowing or
+disallowing connections on the specified interfaces.</p>
+
+<p>Let's assume that our Samba server can access both
+the subnets 192.168.220.* and 134.213.233.*. Here are our additions
+to the configuration file to add the networking configuration
+options:</p>
+
+<blockquote><pre class="code">[global]
+    #  Networking configuration options
+    hosts allow = 192.168.220. 134.213.233.
+    hosts deny = 192.168.220.102
+    interfaces = 192.168.220.100/255.255.255.0 \
+                    134.213.233.110/255.255.255.0
+    bind interfaces only = yes</pre></blockquote>
+
+<p>Take a look at the <tt class="literal">hosts</tt><a name="INDEX-76"/> <tt class="literal">allow</tt>
+and <tt class="literal">hosts</tt><a name="INDEX-77"/> <tt class="literal">deny</tt> options. If these
+options sound familiar, you're probably thinking of
+the <em class="filename">hosts.allow</em> and
+<em class="filename">hosts.deny</em> files that are found in the
+<em class="filename">/etc</em> directories of many Unix systems. The
+purpose of these options is identical to those files; they provide a
+means of security by allowing or denying the connections of other
+hosts based on their IP addresses. We could use the
+<em class="filename">hosts.allow</em> and <em class="filename">hosts.deny</em>
+files, but we are using this method instead because there might be
+services on the server that we want others to access without also
+giving them access to Samba's disk or printer
+shares.</p>
+
+<p>With the <tt class="literal">hosts</tt> <tt class="literal">allow</tt> option,
+we've specified a 192.168.220 IP address, which is
+equivalent to saying: &quot;All hosts on the 192.168.220
+subnet.&quot; However, we've explicitly
+specified in a <tt class="literal">hosts</tt> <tt class="literal">deny</tt> line
+that 192.168.220.102 is not to be allowed access.</p>
+
+<p>You might be wondering why 192.168.220.102 will be denied even though
+it is still in the subnet matched by the <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt> option. It is important to understand how
+Samba sorts out the rules specified by <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt> and <tt class="literal">hosts</tt> <tt class="literal">deny</tt>
+:</p>
+
+<ol><li>
+<p>If no <tt class="literal">allow</tt> or <tt class="literal">deny</tt> options are
+defined anywhere in <em class="filename">smb.conf</em>, Samba will allow
+connections from any system.</p>
+</li><li>
+<p>If <tt class="literal">hosts</tt> <tt class="literal">allow</tt> or
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> options are defined
+in the <tt class="literal">[global]</tt> section of
+<em class="filename">smb.conf</em>, they will apply to all shares, even if
+either option is defined in one or more of the shares.</p>
+</li><li>
+<p>If only a <tt class="literal">hosts</tt> <tt class="literal">allow</tt> option is
+defined for a share, only the hosts listed will be allowed to use the
+share. All others will be denied.</p>
+</li><li>
+<p>If only a <tt class="literal">hosts</tt> <tt class="literal">deny</tt> option is
+defined for a share, any client which is not on the list will be able
+to use the share.</p>
+</li><li>
+<p>If both a <tt class="literal">hosts</tt> <tt class="literal">allow</tt> and
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> option are defined,
+a host must appear in the allow list and not appear in the deny list
+(in any form) to access the share. Otherwise, the host will not be
+allowed.</p>
+</li></ol><a name="samba2-CHP-6-NOTE-131"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Take care that you don't explicitly allow a host to
+access a share, but then deny access to the entire subnet of which
+the host is part.</p>
+</blockquote>
+
+<p>Let's look at another example of that final item.
+Consider the following options:</p>
+
+<blockquote><pre class="code">hosts allow = 111.222.
+hosts deny = 111.222.333.</pre></blockquote>
+
+<p>In this case, only the hosts that belong to the subnet 111.222.*.*
+will be allowed access to the Samba shares. However, if a client
+belongs to the 111.222.333.* subnet, it will be denied access, even
+though it still matches the qualifications outlined by
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt>. The client must
+appear on the <tt class="literal">hosts</tt> <tt class="literal">allow</tt> list
+and <em class="emphasis">must not</em> appear on the
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> list to gain access
+to a Samba share.</p>
+
+<p>The other two options that we've specified are
+<tt class="literal">interfaces</tt> and <tt class="literal">bind</tt>
+<tt class="literal">interface</tt> <tt class="literal">only</tt>.
+Let's look at the <tt class="literal">interfaces</tt>
+option first. Samba, by default, sends data only from the primary
+network interface, which in our example is the 192.168.220.100
+subnet. If we would like it to send data to more than that one
+interface, we need to specify the complete list with the
+<tt class="literal">interfaces</tt> option. In the previous example,
+we've bound Samba to interface with both subnets
+(192.168.220 and 134.213.233) on which the system is operating by
+specifying the other network interface address: 134.213.233.100. If
+you have more than one interface on your computer, you should always
+set this option, as there is no guarantee that the primary interface
+that Samba chooses will be the right one.</p>
+
+<p>Finally, the <tt class="literal">bind</tt> <tt class="literal">interfaces</tt>
+<tt class="literal">only</tt> option instructs the
+<em class="filename">nmbd</em> process not to accept any broadcast
+messages other than on the subnets specified with the
+<tt class="literal">interfaces</tt> option. This is different from the
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> and
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> options, which
+prevent clients from making connections to services, but not from
+receiving broadcast messages. Using the <tt class="literal">bind</tt>
+<tt class="literal">interfaces</tt> <tt class="literal">only</tt> option is a way
+to shut out all datagrams from foreign subnets. In addition, it
+instructs the <em class="emphasis">smbd</em> process to bind to only the
+interface list given by the <em class="emphasis">interfaces</em> option.
+This restricts the networks that Samba will serve.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-6.1"/>
+
+<h3 class="head2">Networking Options</h3>
+
+<p>The networking options we introduced earlier are summarized in <a href="ch06.html#samba2-CHP-6-TABLE-6">Table 6-6</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-6"/><h4 class="head4">Table 6-6. Networking configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">hosts allow (allow</tt> <tt class="literal">hosts)</tt></p>
+</td>
+<td>
+<p>string (list of hostnames)</p>
+</td>
+<td>
+<p>Client systems that can connect to Samba.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">hosts deny (deny</tt> <tt class="literal">hosts)</tt></p>
+</td>
+<td>
+<p>string (list of hostnames)</p>
+</td>
+<td>
+<p>Client systems that cannot connect to Samba.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">interfaces</tt></p>
+</td>
+<td>
+<p>string (list of IP/netmask combinations)</p>
+</td>
+<td>
+<p>Network interfaces Samba will respond to. Allows correcting defaults.</p>
+</td>
+<td>
+<p>System-dependent</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">bind</tt></p>
+
+<p><tt class="literal">interfaces only</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, Samba will bind only to those
+interfaces specified by the <tt class="literal">interfaces</tt> option.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-6.1.1"/>
+
+<h3 class="head3">hosts allow</h3>
+
+<p>The <tt class="literal">hosts</tt> <tt class="literal">allow</tt> option
+(sometimes written as <tt class="literal">allow</tt>
+<tt class="literal">hosts</tt>) specifies the clients that have permission
+to access shares on the Samba server, written as a comma- or
+space-separated list of hostnames of systems or their IP addresses.
+You can gain quite a bit of security by simply placing your
+LAN's subnet address in this option.</p>
+
+<p>You can specify any of the following formats for this option:</p>
+
+<ul><li>
+<p>Hostnames, such as <tt class="literal">ftp.example.com</tt> .</p>
+</li><li>
+<p>IP addresses, such as <tt class="literal">130.63.9.252</tt>.</p>
+</li><li>
+<p>Domain names, which can be differentiated from individual hostnames
+because they start with a dot. For example,
+<tt class="literal">.ora.com</tt> represents all systems within the
+<em class="emphasis">ora.com</em> domain.</p>
+</li><li>
+<p>Netgroups, which start with an at sign (<tt class="literal">@</tt>), such
+as <tt class="literal">@printerhosts</tt>. Netgroups are usually available
+only on systems running NIS or NIS+. If netgroups are supported on
+your system, there should be a <tt class="literal">netgroups</tt> manual
+page that describes them in more detail.</p>
+</li><li>
+<p>Subnets, which end with a dot. For example,
+<tt class="literal">130.63.9</tt>. means all the systems whose IP addresses
+begin with 130.63.9.</p>
+</li><li>
+<p>The keyword <tt class="literal">ALL</tt>, which allows any client access.</p>
+</li><li>
+<p>The keyword <tt class="literal">EXCEPT</tt> followed by one or more names,
+IP addresses, domain names, netgroups, or subnets. For example, you
+could specify that Samba allow all hosts except those on the
+192.168.110 subnet with <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt> <tt class="literal">=</tt> <tt class="literal">ALL</tt>
+<tt class="literal">EXCEPT</tt> <tt class="literal">192.168.110</tt>. (remember
+to include the trailing dot).</p>
+</li></ul>
+<p>Using the <tt class="literal">ALL</tt> keyword by itself is almost always a
+bad idea because it means that crackers on any network can access
+your Samba server.</p>
+
+<p>The hostname <tt class="literal">localhost</tt>, for the loopback address
+127.0.0.1, is included in the <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt> list by default and does not need to be
+listed explicitly unless you have specified the
+<tt class="literal">bind</tt> <tt class="literal">interfaces</tt>
+<tt class="literal">only</tt> parameter. This address is required for Samba
+to work properly.</p>
+
+<p>Other than that, there is no default value for the
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> configuration
+option. The default course of action in the event that neither the
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> or
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> option is specified
+in <em class="filename">smb.conf</em> is to allow access from all sources.</p>
+
+<a name="samba2-CHP-6-NOTE-132"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you specify <tt class="literal">hosts allow</tt> in the
+<tt class="literal">[global]</tt> section, that definition will override
+any <tt class="literal">hosts allow</tt> lines in the share definitions.
+This is the opposite of the usual behavior, which is for parameters
+set in share definitions to override default values set in the
+<tt class="literal">[global]</tt> section.<a name="INDEX-78"/></p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-6.1.2"/>
+
+<h3 class="head3">hosts deny</h3>
+
+<p>The <tt class="literal">hosts</tt> <tt class="literal">deny</tt> option
+(synonymous with <tt class="literal">deny</tt> <tt class="literal">hosts</tt>)
+specifies client systems that do not have permission to access a
+share, written as a comma- or space-separated list of hostnames or
+their IP addresses. Use the same format for specifying clients as the
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> option earlier. For
+example, to restrict access to the server from everywhere but
+<tt class="literal">example.com</tt>, you could write:</p>
+
+<blockquote><pre class="code">hosts deny = ALL EXCEPT .example.com</pre></blockquote>
+
+<p>There is no default value for the <tt class="literal">hosts</tt>
+<tt class="literal">deny</tt> configuration option, although the default
+course of action in the event that neither option is specified is to
+allow access from all sources. Also, if you specify this option in
+the <tt class="literal">[global]</tt> section of the configuration file, it
+will override any <tt class="literal">hosts</tt> <tt class="literal">deny</tt>
+options defined in shares. If you wish to deny access to specific
+shares, omit both the <tt class="literal">hosts</tt>
+<tt class="literal">allow</tt> and <tt class="literal">hosts</tt>
+<tt class="literal">deny</tt> options from the <tt class="literal">[global]</tt>
+section of the configuration file.</p>
+
+<a name="samba2-CHP-6-NOTE-133"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>Never include the loopback address (<tt class="literal">localhost</tt> at
+IP address 127.0.0.1) in the <tt class="literal">hosts deny</tt> list. The
+<em class="filename">smbpasswd</em> program needs to connect through the
+loopback address to the Samba server as a client to change a
+user's encrypted password. If the loopback address
+is disabled, the locally generated packets requesting the change of
+the encrypted password will be discarded by Samba.</p>
+
+
+<p>In addition, both local browsing propagation and some functions of
+SWAT require access to the Samba server through the loopback address
+and will not work correctly if this address is disabled.
+<a name="INDEX-79"/></p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-6.1.3"/>
+
+<h3 class="head3">interfaces</h3>
+
+<p>The <tt class="literal">interfaces</tt><a name="INDEX-80"/> option specifies the
+networks that you want the Samba server to recognize and respond to.
+This option is handy if you have a computer that resides on more than
+one network subnet. If this option is not set, Samba searches for the
+primary network interface of the server (typically the first Ethernet
+card) upon startup and configures itself to operate on only that
+subnet. If the server is configured for more than one subnet and you
+do not specify this option, Samba will only work on the first subnet
+it encounters. You must use this option to force Samba to serve the
+other subnets on your network.</p>
+
+<p>The value of this option is one or more sets of IP address/netmask
+pairs, as in the following:</p>
+
+<blockquote><pre class="code">interfaces = 192.168.220.100/255.255.255.0 192.168.210.30/255.255.255.0</pre></blockquote>
+
+<p>You can optionally specify a
+<a name="INDEX-81"/><a name="INDEX-82"/>CIDR format bitmask, like this:</p>
+
+<blockquote><pre class="code">interfaces = 192.168.220.100/24 192.168.210.30/24</pre></blockquote>
+
+<p>The number after the slash specifies the number of bits that will be
+set in the netmask. For example, the number 24 means that the first
+24 (of 32) bits will be set in the bitmask, which is the same as
+specifying 255.255.255.0 as the netmask. Likewise, 16 would be
+equivalent to a netmask of 255.255.0.0, and 8 would be the same as a
+netmask of 255.0.0.0.</p>
+<a name="samba2-CHP-6-NOTE-135"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>This option might not work correctly if you are using DHCP.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-6.1.4"/>
+
+<h3 class="head3">bind interfaces only</h3>
+
+<p>The <tt class="literal">bind</tt><a name="INDEX-83"/>
+<tt class="literal">interfaces</tt> <tt class="literal">only</tt> option can be
+used to force the <em class="emphasis">smbd</em> and
+<em class="emphasis">nmbd</em> processes to respond only to those
+addresses specified by the <tt class="literal">interfaces</tt> option. The
+<em class="emphasis">nmbd</em> process normally binds to the all-addresses
+interface (0.0.0.0.) on ports 137 and 138, allowing it to receive
+broadcasts from anywhere. However, you can override this behavior
+with the following:</p>
+
+<blockquote><pre class="code">bind interfaces only = yes</pre></blockquote>
+
+<p>This will cause Samba to ignore any packets (including broadcast
+packets) whose source address does not correspond to any of the
+network interfaces specified by the <tt class="literal">interfaces</tt>
+option. You should avoid using this option if you want to allow
+temporary network connections, such as those created through SLIP or
+PPP. It's very rare that this option is needed, and
+it should be used only by experts.</p>
+
+<a name="samba2-CHP-6-NOTE-136"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you set <tt class="literal">bind interfaces only</tt> to <tt class="literal">yes</tt>
+, add the <a name="INDEX-84"/><a name="INDEX-85"/><a name="INDEX-86"/>local host
+address (127.0.01) to the
+&quot;interfaces&quot; list. Otherwise,
+<em class="emphasis">smbpasswd</em> will be unable to connect to the
+server using its default mode in order to change a password, local
+browse list propagation will fail, and some functions of swat will
+not work properly. <a name="INDEX-87"/><a name="INDEX-88"/></p>
+</blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-7"/>
+
+<h2 class="head1">Virtual Servers</h2>
+
+<p><a name="INDEX-89"/>Virtual
+servers can be used to create the illusion of having multiple servers
+on the network, when in reality there is only one. The technique is
+simple to implement: a system simply registers more than one NetBIOS
+name in association with its IP address. There are tangible benefits
+to doing this.</p>
+
+<p>For example, the accounting department might have an
+<tt class="literal">accounting</tt> server, and clients of it would see
+just the accounting disks and printers. The marketing department
+could have its own server, <tt class="literal">marketing</tt>, with its own
+reports, and so on. However, all the services would be provided by
+one medium-size Unix server (and one relaxed administrator) instead
+of having one small server per department.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-7.1"/>
+
+<h3 class="head2">Virtual Server Configuration Options</h3>
+
+<p><a name="INDEX-90"/><a name="INDEX-91"/>Samba will allow a server to use more
+than one NetBIOS name with the <tt class="literal">netbios</tt>
+<tt class="literal">aliases</tt> option. See <a href="ch06.html#samba2-CHP-6-TABLE-7">Table 6-7</a>.</p>
+
+<a name="samba2-CHP-6-TABLE-7"/><h4 class="head4">Table 6-7. Virtual server configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">netbios</tt> <tt class="literal">aliases</tt></p>
+</td>
+<td>
+<p>string (list of NetBIOS names)</p>
+</td>
+<td>
+<p>Additional NetBIOS names to respond to, for use with multiple
+&quot;virtual&quot; Samba servers</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-7.1.1"/>
+
+<h3 class="head3">netbios aliases</h3>
+
+<p>The <tt class="literal">netbios</tt><a name="INDEX-92"/>
+<tt class="literal">aliases</tt> option can be used to give the Samba
+server more than one NetBIOS name. Each NetBIOS name listed as a
+value will be displayed in the Network Neighborhood of Windows
+clients. When a connection is requested to any of the servers, it
+will connect to the same Samba server.</p>
+
+<p>This might come in handy, for example, if you're
+transferring three departments' data to a single
+Unix server with larger and faster disks and are retiring or
+reallocating the old Windows NT/2000 servers. If the three servers
+are called <tt class="literal">sales</tt>, <tt class="literal">accounting</tt>,
+and <tt class="literal">admin</tt>, you can have Samba represent all three
+servers with the following options:</p>
+
+<blockquote><pre class="code">[global]
+    netbios aliases = sales accounting admin
+    include = /usr/local/samba/lib/smb.conf.%L</pre></blockquote>
+
+<p>See <a href="ch06.html#samba2-CHP-6-FIG-5">Figure 6-5</a> for what the Network Neighborhood
+would display from a client. When a client attempts to connect to
+Samba, it will specify the name of the server to which
+it's trying to connect, which is made available in
+the configuration file through the <tt class="literal">%L</tt> variable. If
+the requested server is <tt class="literal">sales</tt>, Samba will include
+the file <em class="filename">/usr/local/samba/lib/smb.conf.sales</em>.
+This file might contain global and share declarations exclusively for
+the sales team, such as the following:</p>
+
+<blockquote><pre class="code">[global]
+    workgroup = SALES
+    hosts allow = 192.168.10.255
+
+[sales2003]
+    path = /usr/local/samba/sales/sales2003/
+...</pre></blockquote>
+
+<p>This particular example would set the workgroup to SALES as well and
+set the IP address to allow connections only from the SALES subnet
+(192.168.10). In addition, it would offer shares specific to the
+sales department.</p>
+
+<div class="figure"><a name="samba2-CHP-6-FIG-5"/><img src="figs/sam2_0605.gif"/></div><h4 class="head4">Figure 6-5. Using NetBIOS aliases for a Samba server</h4>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-6-SECT-8"/>
+
+<h2 class="head1">Logging Configuration Options</h2>
+
+<p><a name="INDEX-93"/><a name="INDEX-94"/>Occasionally,
+we need to find out what Samba is up to. This is especially true when
+Samba is performing an unexpected action or is not performing at all.
+To find out this information, we need to check
+Samba's log files to see exactly why it did what it
+did.</p>
+
+<p>Samba <a name="INDEX-95"/>log files
+can be as brief or verbose as you like. Here is an example of what a
+Samba log file looks like:</p>
+
+<blockquote><pre class="code">[2002/07/21 13:23:25, 3] smbd/service.c:close_cnum(514)
+  maya (172.16.1.6) closed connection to service IPC$
+[2002/07/21 13:23:25, 3] smbd/connection.c:yield_connection(40)
+  Yielding connection to IPC$
+[2002/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
+  Transaction 923 of length 49
+[2002/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
+  switch message SMBread (pid 467)
+[2002/07/21 13:23:25, 3] lib/doscalls.c:dos_ChDir(336)
+  dos_ChDir to /home/samba
+[2002/07/21 13:23:25, 3] smbd/reply.c:reply_read(2199)
+  read fnum=4207 num=2820 nread=2820
+[2002/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
+  Transaction 924 of length 55
+[2002/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
+  switch message SMBreadbraw (pid 467)
+[2002/07/21 13:23:25, 3] smbd/reply.c:reply_readbraw(2053)
+  readbraw fnum=4207 start=130820 max=1276 min=0 nread=1276
+[2002/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
+  Transaction 925 of length 55
+[2002/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
+  switch message SMBreadbraw (pid 467)</pre></blockquote>
+
+<p>Much of this information is of use only to Samba programmers.
+However, we will go over the meaning of some of these entries in more
+detail in <a href="ch12.html">Chapter 12</a>.</p>
+
+<p>Samba contains six options that allow users to describe how and where
+logging information should be written. Each of these are global
+options and cannot appear inside a share definition. Here is an
+example of some logging options that we are adding to our
+configuration file:</p>
+
+<blockquote><pre class="code">[global]
+    log level = 2
+    log file = /var/log/samba.log.%m
+    max log size = 50
+    debug timestamp = yes</pre></blockquote>
+
+<p>Here, we've added a custom log file that reports
+information up to debug level 2. This is a relatively light debugging
+level. The logging level ranges from 1 to 10, where level 1 provides
+only a small amount of information and level 10 provides a plethora
+of low-level information. Levels 2 or 3 will provide us with useful
+debugging information without wasting disk space on our server. In
+practice, you should avoid using log levels greater than 3 unless you
+are working on the Samba source code.</p>
+
+<p>The logging file is located in the <em class="filename">/var/log</em>
+directory thanks to the <tt class="literal">log</tt>
+<tt class="literal">file</tt> configuration option. However, we can use
+variable substitution to create log files specifically for individual
+users or clients, such as with the <tt class="literal">%m</tt> variable in
+the following line:</p>
+
+<blockquote><pre class="code">log file = /usr/local/logs/samba.log.%m</pre></blockquote>
+
+<p>Isolating the log messages can be invaluable in tracking down a
+network error if you know the problem is coming from a specific
+client system or user.</p>
+
+<p>We've added a precaution to the log files: no one
+log file can exceed 50 KB in size, as specified by the
+<tt class="literal">max</tt> <tt class="literal">log</tt> <tt class="literal">size</tt>
+option. If a log file exceeds this size, the contents are moved to a
+file with the same name but with the suffix <em class="emphasis">.old</em>
+appended. If the <em class="emphasis">.old</em> file already exists, it is
+overwritten and its contents are lost. The original file is cleared,
+waiting to receive new logging information. This prevents the hard
+drive from being overwhelmed with Samba log files during the life of
+the Samba daemons.</p>
+
+<p>We have decided to write the timestamps of the messages in the logs
+with the <tt class="literal">debug</tt> <tt class="literal">timestamp</tt>
+option, which is the default behavior. This will place a timestamp in
+each message written to the logging file. If we were not interested
+in this information, we could specify <tt class="literal">no</tt> for this
+option instead.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-8.1"/>
+
+<h3 class="head2">Using syslog</h3>
+
+<p>If you wish to use the system logger
+(<a name="INDEX-96"/>syslog<em class="filename">
+</em>) in addition to or in place of the standard Samba logging
+file, Samba provides options for this as well. However, to use
+syslog, the first thing you will have to do is make sure that Samba
+was built with the <tt class="literal">configure</tt>
+<tt class="literal">--with-syslog</tt> option. See <a href="ch02.html">Chapter 2</a> for more information on configuring and
+compiling Samba. See <a href="appe.html">Appendix E</a> for more
+information about the <tt class="literal">--with-syslog</tt> option.</p>
+
+<p>Once that is done, you will need to configure your
+<em class="filename">/etc/syslog.conf</em><a name="INDEX-97"/> to accept logging information from Samba.
+If there is not already a <tt class="literal">daemon.*</tt> entry in the
+<em class="filename">/etc/syslog.conf</em> file, add the following:</p>
+
+<blockquote><pre class="code">daemon.*        /var/log/daemon.log</pre></blockquote>
+
+<p>This specifies that any logging information from system daemons will
+be stored in the <em class="filename">/var/log/daemon.log</em> file. This
+is where the Samba information will be stored as well. From there,
+you can set a value for the <tt class="literal">syslog</tt> parameter in
+your Samba configuration file to specify which logging messages are
+to be sent to syslog. Only messages that have debug levels lower than
+the value of the <tt class="literal">syslog</tt> parameter will be sent to
+syslog. For example, setting the following:</p>
+
+<blockquote><pre class="code">syslog = 3</pre></blockquote>
+
+<p>specifies that any logging messages with a level of 2 or below will
+be sent to both syslog and the Samba logging files. (The mappings to
+<em class="filename">syslog</em> priorities are described in the upcoming
+section &quot;syslog.&quot;) To continue the
+example, let's assume that we have set the
+<tt class="literal">log</tt> <tt class="literal">level</tt> option to 4. Logging
+messages with levels of 2 and 1 will be sent to both syslog and the
+Samba logging files, and messages with a level of 3 or 4 will be sent
+to the Samba logging files, but not to syslog. If the
+<tt class="literal">syslog</tt> value exceeds the <tt class="literal">log</tt>
+<tt class="literal">level</tt> value, nothing will be sent to syslog.</p>
+
+<p>If you want to specify that messages be sent only to syslog&mdash;and
+not to the standard Samba logging files&mdash;you can place this
+option in the configuration file:</p>
+
+<blockquote><pre class="code">syslog only = yes</pre></blockquote>
+
+<p>If this is the case, any logging information above the number
+specified in the <tt class="literal">syslog</tt> option will be discarded,
+as with the <tt class="literal">log</tt> <tt class="literal">level</tt> option.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-6-SECT-8.2"/>
+
+<h3 class="head2">Logging Configuration Options</h3>
+
+<p><a href="ch06.html#samba2-CHP-6-TABLE-8">Table 6-8</a> lists each logging configuration option
+that Samba can use.</p>
+
+<a name="samba2-CHP-6-TABLE-8"/><h4 class="head4">Table 6-8. Logging configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">log file</tt></p>
+</td>
+<td>
+<p>string (name of file)</p>
+</td>
+<td>
+<p>Name of the log file that Samba is to use. Works with all variables.</p>
+</td>
+<td>
+<p>Specified in Samba makefile</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">log level</tt></p>
+
+<p><tt class="literal">(debug level)</tt></p>
+</td>
+<td>
+<p>numeric (0-10)</p>
+</td>
+<td>
+<p>Amount of log/debug messages that are sent to the log file. 0 is
+none; 3 is considerable.</p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max log size</tt></p>
+</td>
+<td>
+<p>numeric (size in KB)</p>
+</td>
+<td>
+<p>Maximum size of log file.</p>
+</td>
+<td>
+<p><tt class="literal">5000</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">debug timestamp</tt> <tt class="literal">(timestamp logs)</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">no</tt>, doesn't timestamp logs,
+making them easier to read during heavy debugging.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">syslog</tt></p>
+</td>
+<td>
+<p>numeric (0-10)</p>
+</td>
+<td>
+<p>Level of messages sent to <em class="emphasis">syslog</em>. Those levels
+below <tt class="literal">syslog</tt> <tt class="literal">level</tt> will be sent
+to the system logger.</p>
+</td>
+<td>
+<p><tt class="literal">1</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">syslog only</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, uses <em class="emphasis">syslog</em> entirely
+and sends no output to the Samba log files.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.1"/>
+
+<h3 class="head3">log file</h3>
+
+<p>By default, Samba writes log information to text files in the
+<em class="filename">/usr/local/samba/var</em> directory. The
+<tt class="literal">log</tt><a name="INDEX-98"/> <tt class="literal">file</tt> option can be
+used to set the name of the log file to another location. For
+example, to put the Samba log information in
+<em class="filename">/usr/local/logs/samba.log</em>, you could use the
+following:</p>
+
+<blockquote><pre class="code">[global]
+    log file = /usr/local/logs/samba.log</pre></blockquote>
+
+<p>You can use variable substitution to create log files specifically
+for individual users or clients.</p>
+
+<p>You can override the default log file location using the
+<em class="emphasis">-l</em> command-line switch when either daemon is
+started. However, this does not override the <tt class="literal">log</tt>
+<tt class="literal">file</tt> option. If you do specify this parameter,
+initial logging information will be sent to the file specified after
+<em class="emphasis">-l</em> (or the default specified in the Samba
+makefile) until the daemons have processed the
+<em class="filename">smb.conf</em> file and know to redirect it to a new
+log file.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.2"/>
+
+<h3 class="head3">log level</h3>
+
+<p>The <tt class="literal">log</tt><a name="INDEX-99"/> <tt class="literal">level</tt> option
+sets the amount of data to be logged. Normally this is set to 0 or 1.
+However, if you have a specific problem, you might want to set it at
+3, which provides the most useful debugging information you would
+need to track down a problem. Levels above 3 provide information
+that's primarily for the developers to use for
+chasing internal bugs, and it slows down the server considerably.
+Therefore, we recommend that for normal day-to-day operation, you
+avoid setting this option to anything above 3.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.3"/>
+
+<h3 class="head3">max log size</h3>
+
+<p>The <tt class="literal">max</tt><a name="INDEX-100"/> <tt class="literal">log</tt>
+<tt class="literal">size</tt> option sets the maximum size, in kilobytes,
+of the debugging log file that Samba keeps. When the log file exceeds
+this size, the current log file is renamed to add a
+<em class="filename">.old</em> extension (erasing any previous file with
+that name) and a new debugging log file is started with the original
+name. For example:</p>
+
+<blockquote><pre class="code">[global]
+    log file = /usr/local/logs/samba.log.%m
+    max log size = 1000</pre></blockquote>
+
+<p>Here, if the size of any log file exceeds 1MB, Samba renames the log
+file <em class="emphasis">samba.log</em>.
+<em class="replaceable">machine-name</em><em class="emphasis">.old</em>,
+and a new log file is generated. If there is already a file with the
+<em class="emphasis">.old</em> extension, Samba deletes it. We highly
+recommend setting this option in your configuration files because
+debug logging (even at lower levels) can quietly eat away at your
+available disk space. Using this option protects unwary
+administrators from suddenly discovering that most of the space on a
+disk or partition has been swallowed up by a single Samba log file.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.4"/>
+
+<h3 class="head3">debug timestamp or timestamp logs</h3>
+
+<p>If you happen to be debugging a network problem and you find that the
+timestamp information within the Samba log lines gets in the way, you
+can turn it off by giving either the
+<tt class="literal">timestamp</tt><a name="INDEX-101"/> <tt class="literal">logs</tt> or the
+synonymous <tt class="literal">debug</tt><a name="INDEX-102"/>
+<tt class="literal">timestamp</tt> option a value of <tt class="literal">no</tt>.
+For example, a regular Samba log file presents its output in the
+following form:</p>
+
+<blockquote><pre class="code">12/31/01 12:03:34 toltec (172.16.1.1) connect to server network as user jay</pre></blockquote>
+
+<p>With a <tt class="literal">no</tt> value for this option, the output would
+appear without the timestamp:</p>
+
+<blockquote><pre class="code">toltec (172.16.1.1) connect to server network as user jay</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.5"/>
+
+<h3 class="head3">syslog</h3>
+
+<p>The <tt class="literal">syslog</tt><a name="INDEX-103"/> option causes Samba log
+messages to be sent to the Unix system logger. The type of log
+information to be sent is specified as a numeric value. Like the
+<tt class="literal">log</tt> <tt class="literal">level</tt> option, it can be a
+number from 0 to 10. Logging information with a level less than the
+number specified will be sent to the system logger. Debug logs
+greater than or equal to the <tt class="literal">syslog</tt> level, but
+less than log level, will still be sent to the standard Samba log
+files. For example:</p>
+
+<blockquote><pre class="code">[global]
+    log level = 3
+    syslog = 1</pre></blockquote>
+
+<p>With this, all logging information with a level of 0 would be sent to
+the standard Samba logs and the system logger, while information with
+levels 1, 2, and 3 would be sent only to the standard Samba logs.
+Levels above 3 are not logged at all. All messages sent to the system
+logger are mapped to a priority level that the syslogd daemon
+understands, as shown in <a href="ch06.html#samba2-CHP-6-TABLE-9">Table 6-9</a>. The default
+level is 1.</p>
+
+<a name="samba2-CHP-6-TABLE-9"/><h4 class="head4">Table 6-9. syslog priority conversion</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Log level</p>
+</th>
+<th>
+<p>syslog priority</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>0</p>
+</td>
+<td>
+<p><tt class="literal">LOG_ERR</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>1</p>
+</td>
+<td>
+<p><tt class="literal">LOG_WARNING</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>2</p>
+</td>
+<td>
+<p><tt class="literal">LOG_NOTICE</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>3</p>
+</td>
+<td>
+<p><tt class="literal">LOG_INFO</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p>4 and above</p>
+</td>
+<td>
+<p><tt class="literal">LOG_DEBUG</tt></p>
+</td>
+</tr>
+
+</table>
+
+<p>If you wish to use <em class="emphasis">syslog</em>, you will have to run
+<tt class="literal">configure</tt> <tt class="literal">--with-syslog</tt> when
+compiling Samba, and you will need to configure your
+<em class="filename">/etc/syslog.conf</em> to suit. (See <a href="ch06.html#samba2-CHP-6-SECT-8.1">Section 6.8.1</a>, earlier in this chapter.)</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-6-SECT-8.2.6"/>
+
+<h3 class="head3">syslog only</h3>
+
+<p>The <tt class="literal">syslog</tt><a name="INDEX-104"/> <tt class="literal">only</tt> option
+tells Samba not to use its own logging files at all and to use only
+the system logger. To enable this, specify the following option in
+the global section of the Samba configuration file:</p>
+
+<a name="INDEX-105"/><a name="INDEX-106"/><a name="INDEX-107"/><blockquote><pre class="code">[global]
+    syslog only = yes</pre></blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> Depending on your system, this file might not
+be <em class="emphasis">/etc/printcap</em>. You can use the
+<em class="emphasis">testparm</em> command that comes with Samba to dump
+the parameter definitions and determine the value of the
+<tt class="literal">printcap</tt> <tt class="literal">name</tt> configuration
+option. The value assigned to it is the default value chosen when
+Samba was configured and compiled, which should be correct.</p>
+<a name="FOOTNOTE-2"/> <p><a href="#FNPTR-2">[2]</a> We are referring here to the window that
+opens when a printer icon in the Printers control panel is
+double-clicked.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch07.html b/docs/htmldocs/using_samba/ch07.html
new file mode 100644
index 0000000000..a6dc8d94b0
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch07.html
@@ -0,0 +1,2139 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 7. Name Resolution and Browsing</h1>
+
+
+
+
+<p><a name="INDEX-1"/><em class="firstterm">Name
+resolution</em> is critical to Samba's
+operation because names are used to find the servers that share files
+or printers. <em class="firstterm">Browsing</em> takes the task of
+finding servers to a new level of sophistication by allowing a user
+to delve down into a hierarchy of networks, domains, hosts, and
+services offered by each server.</p>
+
+<p>While name resolution and
+<a name="INDEX-2"/>browsing are not
+difficult to configure, some complexity is introduced by the variety
+of available name-resolution systems. Historically, Unix and other
+TCP/IP users have moved from a flat hosts file to the Domain Name
+System, with the Network Information System being another popular
+choice. Meanwhile, Microsoft has moved from a broadcasting system to
+a simple, LAN-only name server called WINS and ultimately to DNS.</p>
+
+<p>The reason for going over that history is that all previous systems
+of name resolution are still in use today! Finding a host is so
+crucial to networking that sites want robust (if limited)
+name-resolution systems to fall back on in case the main system
+fails. Browsing is also complicated by the frequent need to show
+hosts in other subnets. This chapter shows you how to configure your
+network to handle name resolution and browsing any way you want.</p>
+
+<p>Some of the differences between Unix and Microsoft networking
+implementations are the result of fundamental design goals. Unix
+networking was originally designed largely to implement a relatively
+formal group of systems that were assumed to be small in number,
+well-maintained, and highly available, that have static IP addresses,
+and that wouldn't physically move around from place
+to place. Bringing a new server online was a labor-intensive task,
+but it did not have to be performed frequently. In contrast, Windows
+networking was originally developed as a peer-to-peer collection of
+small personal computers on a single subnet, having no centrally or
+hierarchically organized structure.</p>
+
+<p>SMB networking is dynamic. Computers are allowed to leave the network
+at any time, sometimes without warning, and also to join or rejoin
+the network at any time. Furthermore, any user in a Windows network
+can add a new shared resource to the network or remove a resource
+that he had previously added. The change in the
+network's configuration is handled automatically by
+the rest of the network without requiring a system administrator to
+take any action.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-7-SECT-1"/>
+
+<h2 class="head1">Name Resolution</h2>
+
+<p>TCP/IP networks identify systems by IP addresses and always associate
+these addresses with more human-readable text names. In
+Microsoft's earliest networking implementations (for
+MS-DOS and Windows for Workgroups), the translation of names to
+network addresses was carried out in a manner that was very simple,
+yet very inefficient. When a system on the network needed an IP
+address corresponding to a name, it broadcasted the name to every
+other system on the network and waited for the system that owned the
+name to respond with its IP address.</p>
+
+<p>The main problem with performing <a name="INDEX-3"/>name resolution using broadcast
+packets is poor performance of the network as a whole, including CPU
+time consumed by each host on the network, which has to accept every
+broadcast packet and decide whether to respond to it. Also, broadcast
+packets usually aren't forwarded by routers,
+limiting name resolution to the local subnet.
+Microsoft's solution was to add WINS (Windows
+Internet Name Service) support to Windows NT so that the computers on
+the network can perform a direct query of the WINS server instead of
+using broadcast packets.</p>
+
+<p>Modern Windows clients use a variety of methods for translating
+hostnames into IP addresses. The exact method varies depending on the
+version of Windows the client is running, how the client is
+configured (i.e., whether DNS server and/or WINS server IP addresses
+are provided), and whether the application software is accessing the
+network through Microsoft's Winsock or TCP/IP API.
+In general, Windows uses some combination of the following
+methods:<a name="INDEX-4"/></p>
+
+<ul><li>
+<p>Looking up the name in its cache of recently resolved names</p>
+</li><li>
+<p>Querying DNS servers</p>
+</li><li>
+<p>Using the DNS <em class="filename">Hosts</em> file</p>
+</li><li>
+<p>Querying WINS servers</p>
+</li><li>
+<p>Using the WINS <em class="filename">LMHOSTS</em> file</p>
+</li><li>
+<p>Performing broadcast name resolution</p>
+</li></ul>
+<p>The first method is pretty much self-explanatory. A hostname is
+checked against a cache of hostnames that have been recently resolved
+to IP addresses. This helps to save time and network bandwidth for
+resolving names that are used frequently.</p>
+
+<p>When a Windows system is configured with the IP address of at least
+one <a name="INDEX-5"/>DNS server, it can use DNS to
+resolve fully qualified domain names, such as those for sites on the
+Internet. The DNS servers can be either Windows NT/2000 or Unix
+systems. You can learn more about DNS and DNS server configuration in
+the O'Reilly book <em class="citetitle">DNS and
+BIND</em>.</p>
+
+<p>In this chapter, we focus mainly on name resolution using WINS, which
+is supported by Samba with the <em class="emphasis">nmbd</em> daemon.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.1"/>
+
+<h3 class="head2">WINS Clients and Server Interaction</h3>
+
+<p>There are two types of interaction between a
+<a name="INDEX-6"/>WINS client and a server: the
+client keeps its own NetBIOS name<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> registered with the server and
+queries the server to get the IP address corresponding to the NetBIOS
+name of another system.</p>
+
+<p>When a WINS client joins the network, it registers its NetBIOS name
+with the WINS server, which stores it along with the
+client's IP address in the WINS database. This entry
+is marked <em class="firstterm">active</em>. The client is then expected
+to renew the registration of its name periodically (typically, every
+four days) to inform the server that it is still using the name. This
+period is called the <em class="firstterm">time to live</em>, or TTL.
+When the client leaves the network by being shut down gracefully, it
+informs the server, and the server marks the
+client's entry in its database as
+<em class="firstterm">released</em>.</p>
+
+<p>When a client leaves the network without telling the WINS server to
+release its name, the server waits until after it fails to receive
+the expected registration renewal from the client and then marks the
+entry as released.</p>
+
+<p>In either case, the released name is available for use by other
+clients joining the network. It might persist in the released state
+in the WINS database, and if it is not reregistered, the entry will
+eventually be deleted.</p>
+
+<p>More information on WINS can be found in the Microsoft white paper
+<em class="citetitle">Windows Internet Naming Service (WINS) Architecture and
+Capacity Planning</em><a name="INDEX-7"/>. It can be downloaded from the
+Microsoft web site at <a href="http://www.microsoft.com">http://www.microsoft.com</a>.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.2"/>
+
+<h3 class="head2">The lmhosts File</h3>
+
+<p>In <a href="ch03.html">Chapter 3</a> we showed you how to configure
+Windows systems to use the
+<em class="filename">LMHOSTS</em><a name="INDEX-8"/>
+file as an alternative to the WINS server for name resolution. Samba
+also can use an <em class="filename">LMHOSTS</em> file, which by default
+is <em class="filename">/usr/local/samba/lib/lmhosts</em>.
+Samba's <em class="filename">lmhosts</em> is the same
+format as the Windows version. A simple <em class="filename">lmhosts</em>
+file might look like this:</p>
+
+<blockquote><pre class="code">172.16.1.1    toltec
+172.16.1.6    maya</pre></blockquote>
+
+<p>The names on the right side of the entries are NetBIOS names, so you
+can assign resource types to them and add additional entries for
+computers:</p>
+
+<blockquote><pre class="code">172.16.1.1    toltec#20
+172.16.1.1    metran#1b
+172.16.1.6    maya#20</pre></blockquote>
+
+<p>Here, we've made <tt class="literal">toltec</tt> the
+primary domain controller of the <tt class="literal">METRAN</tt> domain on
+the second line. This line starts with
+<tt class="literal">toltec</tt>'s IP address, followed by
+the name metran and the resource type &lt;1B&gt;. The other lines are
+entries for <tt class="literal">toltec</tt> and <tt class="literal">maya</tt> as
+standard workstations.</p>
+
+<p>If you wish to place an <em class="emphasis">lmhosts</em> file somewhere
+other than the default location, you will need to notify the
+<em class="emphasis">nmbd</em> process upon startup using the
+<em class="emphasis">-H</em> option, followed by the name of your
+<em class="filename">lmhosts</em> file, as follows:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>nmbd -H /etc/samba/lmhosts -D</b></tt></pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.3"/>
+
+<h3 class="head2">Configuring Name Resolution for the Samba Suite</h3>
+
+<p>Various daemons and tools in the Samba suite need to perform
+<a name="INDEX-9"/>name resolution. You can define the
+order in which the programs try each name-resolution method through
+the <tt class="literal">name</tt><a name="INDEX-10"/><a name="INDEX-11"/>
+<tt class="literal">resolve</tt> <tt class="literal">order</tt> parameter, like
+this:</p>
+
+<blockquote><pre class="code">[global]
+    name resolve order = wins lmhosts hosts bcast</pre></blockquote>
+
+<p>The string used to define the parameter can take up to four values:</p>
+
+<dl>
+<dt><b>lmhosts</b></dt>
+<dd>
+<p>Uses the Samba server's local
+<em class="filename">lmhosts</em> file</p>
+</dd>
+
+
+
+<dt><b>hosts</b></dt>
+<dd>
+<p>Uses the standard Unix name-resolution methods, which can be
+<em class="emphasis">/etc/hosts</em>, DNS, NIS, or a combination,
+depending on how the local system is configured</p>
+</dd>
+
+
+
+<dt><b>wins</b></dt>
+<dd>
+<p>Uses the WINS server</p>
+</dd>
+
+
+
+<dt><b>bcast</b></dt>
+<dd>
+<p>Uses the broadcast method</p>
+</dd>
+
+</dl>
+
+<p>The order in which they are specified is the order in which name
+resolution will be attempted. In our example, Samba will attempt to
+use its WINS server first for name resolution, followed by the
+<em class="emphasis">lmhosts</em> file on the local system. Next, the
+<tt class="literal">hosts</tt> value tells it to use Unix name-resolution
+methods. The word <tt class="literal">hosts</tt> can be misleading; it
+covers not only the <em class="filename">/etc/hosts</em> file, but also
+the use of DNS or NIS (as configured on the Unix host). Finally, if
+those three do not work, it will perform a broadcast name resolution.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.4"/>
+
+<h3 class="head2">Setting Up Samba as a WINS Server</h3>
+
+<p>You can set up Samba as a <a name="INDEX-12"/>WINS server by setting the
+<tt class="literal">wins</tt><a name="INDEX-13"/> <tt class="literal">support</tt>
+parameter in the configuration file, like this:</p>
+
+<blockquote><pre class="code">[global]
+    wins support = yes</pre></blockquote>
+
+<p>Believe it or not, that's all you need to do! The
+<tt class="literal">wins</tt> <tt class="literal">support</tt> option turns Samba
+into a WINS server. For most installations, Samba's
+default configuration is sufficient.</p>
+<a name="samba2-CHP-7-NOTE-137"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Remember, Samba cannot communicate with Windows WINS servers. If you
+are using Samba as your WINS server, you must make sure not to allow
+any Windows systems or other Samba servers on your network to be
+configured as WINS servers. If you do, their WINS databases will not
+synchronize, resulting in inconsistent name resolution.</p>
+</blockquote>
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.4.1"/>
+
+<h3 class="head3">Configuring a DNS proxy</h3>
+
+<p>A Samba <a name="INDEX-14"/><a name="INDEX-15"/>WINS server can check with the
+system's DNS server if a requested host cannot be
+found in its WINS database. With a typical Linux system, for example,
+you can find the IP address of the DNS server by searching the
+<em class="filename">/etc/resolv.conf</em><a name="INDEX-16"/><a name="INDEX-17"/> file. In it, you might see an entry such
+as the following:</p>
+
+<blockquote><pre class="code">nameserver 127.0.0.1
+nameserver 172.16.1.192</pre></blockquote>
+
+<p>This tells us that the Linux system is configured to use a DNS server
+located at 172.16.1.192. (The 127.0.0.1 is the
+<tt class="literal">localhost</tt> address and is never a valid DNS server
+address.)</p>
+
+<p>Now it is a simple matter of using the
+<tt class="literal">dns</tt><a name="INDEX-18"/> <tt class="literal">proxy</tt> option to tell
+Samba to use the DNS server:</p>
+
+<blockquote><pre class="code">[global]
+    dns proxy = yes</pre></blockquote>
+
+<a name="samba2-CHP-7-NOTE-138"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Although this allows Windows clients to resolve fully qualified
+Internet domain names through the Samba WINS server, it will work
+only for domain names that fit within the 15-character limitation of
+NetBIOS names. For this reason, we recommend you use <tt class="literal">dns
+proxy</tt> only to act as a supplement to your WINS server,
+rather than as a replacement for a DNS server.</p>
+</blockquote>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.5"/>
+
+<h3 class="head2">Setting Up Samba to Use Another WINS Server</h3>
+
+<p>You can configure Samba to use a <a name="INDEX-19"/>WINS server somewhere else on the
+network by simply providing it with the IP address of the WINS
+server. This is done with the global
+<tt class="literal">wins</tt><a name="INDEX-20"/> <tt class="literal">server</tt>
+configuration option, as shown here:</p>
+
+<blockquote><pre class="code">[global]
+    wins server = 172.16.1.1</pre></blockquote>
+
+<p>With this option enabled, Samba will direct all WINS requests to the
+server located at 172.16.1.1. Note that because the request is
+directed at a single machine, we don't have to worry
+about any of the problems inherent in broadcasting. However, Samba
+will not necessarily use the WINS server before other forms of name
+resolution. The order in which Samba attempts various name-resolution
+techniques is given with the <tt class="literal">name</tt>
+<tt class="literal">resolve</tt> <tt class="literal">order</tt> configuration
+option, which we discussed earlier.</p>
+
+<p>The <tt class="literal">wins</tt> <tt class="literal">support</tt> and the
+<tt class="literal">wins</tt> <tt class="literal">server</tt> parameters are
+mutually exclusive; you cannot simultaneously offer Samba as the WINS
+server and use another system as the server! Typically, one Samba
+server is set up as the WINS server using <tt class="literal">wins</tt>
+<tt class="literal">support</tt>, and all other Samba servers are
+configured with the <tt class="literal">wins</tt> <tt class="literal">server</tt>
+parameter pointing to the Samba WINS server.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.5.1"/>
+
+<h3 class="head3">Configuring a WINS proxy</h3>
+
+<p><a name="INDEX-21"/>If you have a Samba server on a
+subnet that doesn't have a WINS server, and the
+Samba server has been configured with a WINS server on another
+subnet, you can tell the Samba server to forward any name-resolution
+requests with the <tt class="literal">wins</tt><a name="INDEX-22"/>
+<tt class="literal">proxy</tt> option:</p>
+
+<blockquote><pre class="code">[global]
+    wins server = 172.16.200.12
+    wins proxy = yes</pre></blockquote>
+
+<p>Use this only in situations where the WINS server resides on another
+subnet. Otherwise, the broadcast will reach the WINS server
+regardless of any proxying.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-1.6"/>
+
+<h3 class="head2">Name-Resolution Configuration Options</h3>
+
+<p><a name="INDEX-23"/>Samba's <a name="INDEX-24"/>name-resolution options
+are shown in <a href="ch07.html#samba2-CHP-7-TABLE-1">Table 7-1</a>.</p>
+
+<a name="samba2-CHP-7-TABLE-1"/><h4 class="head4">Table 7-1. Name-resolution options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">wins support</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, allows Samba to act as a WINS server</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">wins server</tt></p>
+</td>
+<td>
+<p>string (IP address or DNS name)</p>
+</td>
+<td>
+<p>Identifies a WINS server for Samba to use for name registration and
+resolution</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">wins proxy</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>Allows Samba to act as a proxy to a WINS server on another subnet</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">wins hook</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Command to run when the WINS database changes</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">dns proxy</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, allows a Samba WINS server to
+search DNS if it cannot find a name in WINS</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">name resolve</tt> <tt class="literal">order</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>The order of methods used to resolve NetBIOS names</p>
+</td>
+<td>
+<p><tt class="literal">lmhosts</tt> <tt class="literal">hosts wins bcast</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max ttl</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum TTL in seconds for a requested NetBIOS name</p>
+</td>
+<td>
+<p><tt class="literal">259200</tt> ( 3 days)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max wins ttl</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum TTL in seconds for NetBIOS names given out by Samba as a WINS
+server</p>
+</td>
+<td>
+<p><tt class="literal">518400</tt> (6 days)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">min wins ttl</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Minimum TTL in seconds for NetBIOS names given out by Samba as a WINS
+server</p>
+</td>
+<td>
+<p><tt class="literal">21600</tt> (6 hours)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.1"/>
+
+<a name="INDEX-25"/><h3 class="head3">wins support</h3>
+
+<p>Samba will provide WINS name service to all machines in the network
+if you set the following in the <tt class="literal">[global]</tt> section
+of the <em class="filename">smb.conf</em> file:</p>
+
+<blockquote><pre class="code">[global]
+    wins support = yes</pre></blockquote>
+
+<p>The default value is <tt class="literal">no</tt>, which is typically used
+to allow a Windows NT/2000 server or another Samba server to be the
+WINS server. If you enable this option, remember that a Samba WINS
+server currently cannot exchange data with other WINS servers, so do
+not allow any other WINS servers on the network. When set to
+<tt class="literal">yes</tt>, this option is mutually exclusive with the
+<tt class="literal">wins</tt> <tt class="literal">server</tt> parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.2"/>
+
+<a name="INDEX-26"/><h3 class="head3">wins server</h3>
+
+<p>Samba will use an existing WINS server on the network if you specify
+the <tt class="literal">wins</tt> <tt class="literal">server</tt> global option
+in your configuration file. The value of this option is either the IP
+address or DNS name (not NetBIOS name) of the WINS server. For
+example:</p>
+
+<blockquote><pre class="code">[global]
+    wins server = 172.16.220.110</pre></blockquote>
+
+<p>or:</p>
+
+<blockquote><pre class="code">[global]
+    wins server = wins.metran.cx</pre></blockquote>
+
+<p>For this option to work, the <tt class="literal">wins</tt>
+<tt class="literal">support</tt> option must be set to
+<tt class="literal">no</tt> (the default). Otherwise, Samba will report an
+error. You can specify only one WINS server using this option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.3"/>
+
+<a name="INDEX-27"/><h3 class="head3">wins proxy</h3>
+
+<p>This option allows Samba to act as a proxy to another WINS server,
+and thus relay name registration and resolution requests from itself
+to the real WINS server, often outside the current subnet. The WINS
+server can be indicated through the <tt class="literal">wins</tt>
+<tt class="literal">server</tt> option. The proxy will then return the WINS
+response back to the client. You can enable this option by specifying
+the following in the <tt class="literal">[global]</tt> section:</p>
+
+<blockquote><pre class="code">[global]
+    wins proxy = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.4"/>
+
+<a name="INDEX-28"/><h3 class="head3">wins hook</h3>
+
+<p>This option allows you to run a script or other program whenever the
+WINS database is modified. One application might be to set up another
+Samba server to act as a backup for another Samba WINS server. This
+is done by having the <tt class="literal">wins</tt> <tt class="literal">hook</tt>
+script call <em class="emphasis">rsync</em> to synchronize the WINS
+databases (<em class="filename">/usr/local/samba/var/locks/wins.dat</em>)
+on the two systems whenever an entry is added or deleted. The script
+would be specified in the Samba configuration file like this:</p>
+
+<blockquote><pre class="code">[global]
+    wins hook = /usr/local/bin/sync_wins</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.5"/>
+
+<a name="INDEX-29"/><h3 class="head3">dns proxy</h3>
+
+<p>If you want the DNS to be used if a NetBIOS name
+isn't found in WINS, you can set the following
+option:</p>
+
+<blockquote><pre class="code">[global]
+    dns proxy = yes</pre></blockquote>
+
+<p>This will permit <em class="filename">nmbd</em> to query the
+server's standard DNS. You might wish to deactivate
+this option if you do not have a permanent connection to your DNS
+server. This option should not be used in place of a DNS server on
+your network; it is intended for resolving NetBIOS names rather than
+fully qualified Internet domain names.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.6"/>
+
+<h3 class="head3">name resolve order</h3>
+
+<p>The global <tt class="literal">name</tt><a name="INDEX-30"/>
+<tt class="literal">resolve</tt> <tt class="literal">order</tt> option specifies
+the order of services that Samba will use in performing name
+resolution. The default order is to use the
+<em class="emphasis">lmhosts</em> file, followed by standard Unix
+name-resolution methods (some combination of
+<em class="filename">/etc/hosts</em>, DNS, and NIS), then to query a WINS
+server, and finally to use broadcasting to determine the address of a
+NetBIOS name. You can override this option by specifying something
+like the following:</p>
+
+<blockquote><pre class="code">[global]
+    name resolve order = lmhosts wins hosts bcast</pre></blockquote>
+
+<p>This causes resolution to use the <em class="emphasis">lmhosts</em> file
+first, followed by a query to a WINS server, the
+<em class="filename">/etc/hosts</em> file, and finally broadcasting. You
+need not use all four options. This option is covered in more detail
+in <a href="ch07.html#samba2-CHP-7-SECT-1.4">Section 7.1.4</a>,
+earlier in this chapter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.7"/>
+
+<a name="INDEX-31"/><h3 class="head3">max ttl</h3>
+
+<p>This option is used when Samba is not acting as a WINS server but is
+using another system on the network for its WINS server. It sets the
+maximum T T L for NetBIOS names registered by the Samba server with
+the WINS server. You should never need to alter this value.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.8"/>
+
+<a name="INDEX-32"/><h3 class="head3">max wins ttl</h3>
+
+<p>This option is used when Samba is providing WINS name service, and it
+sets the maximum T T L for NetBIOS names registered with Samba. You
+should never need to change this value from its default.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-1.6.9"/>
+
+<a name="INDEX-33"/><h3 class="head3">min wins ttl</h3>
+
+<p>This option is used when Samba is providing WINS name service, and it
+sets the minimum T T L for NetBIOS names registered with Samba. You
+should never need to alter this value from its default. <a name="INDEX-34"/> <a name="INDEX-35"/> <a name="INDEX-36"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-7-SECT-2"/>
+
+<h2 class="head1">Browsing</h2>
+
+<p><a name="INDEX-37"/>Browsing
+was developed by Microsoft to help users find shared resources on the
+network. In a networked computing environment where users can add or
+remove shares at any time, it is important to have some automatic
+means of keeping track of the shared resources and allowing users to
+&quot;browse&quot; through them to find the
+ones they wish to use.</p>
+
+<p>Before browsing was added to SMB networking, when anyone added a new
+share, the people with whom they wished to share the data or printer
+would have to be informed of the share's UNC, using
+some relatively low-tech method such as speaking to them in person or
+over the phone, or sending email. Already, this was very inconvenient
+in large organizations. To further complicate matters, the users
+working on client computers had to type in the
+share's UNC to connect to it. The only way to get
+around typing in the share's UNC every time it was
+used was to map a network drive to it, and with a large number of
+shares on the network, this could easily get out of hand.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.1"/>
+
+<h3 class="head2">Browsing in a Windows Network</h3>
+
+<p><a name="INDEX-38"/>To keep things simple, we will
+first describe network browsing in a network that contains only
+Windows systems and then show you how to add a Samba server.</p>
+
+<p>The basic way browsing works is that one computer in the network
+takes on the role of the <em class="firstterm">master
+browser</em><a name="INDEX-39"/> (also
+called <em class="firstterm">local master
+browser</em><a name="INDEX-40"/>,<em class="firstterm"> browse
+master</em><a name="INDEX-41"/>, or
+<em class="firstterm">browse server</em><a name="INDEX-42"/>) and
+keeps a list of all the computers on the local subnet that are acting
+as SMB servers. The list of computers is called the <em class="firstterm">browse
+list</em><a name="INDEX-43"/> and includes all Samba servers, Windows
+NT/2000/XP systems, and any Windows 95/98/Me systems that have the
+&quot;File and printer sharing for Microsoft
+Networks&quot; networking component installed. The browse
+list also contains the names of all workgroups and domains. At this
+level, browsing is limited to the local subnet because the browsing
+protocol depends on broadcast packets, which are typically not
+forwarded to other subnets by routers.</p>
+
+<p>A user at any Windows system can view the browse list by opening up
+the Network Neighborhood (or My Network Places), as we showed you in
+<a href="ch01.html">Chapter 1</a>. Or, the <em class="emphasis">net
+view</em><a name="INDEX-44"/> command can be used from a Windows
+command prompt:</p>
+
+<blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>net view</b></tt>
+Server Name            Remark
+
+-------------------------------------------------------------------------------
+\\MAYA                 Windows 98
+\\MIXTEC               Samba 2.2.5
+\\OLMEC                Windows XP Pro on Pentium/ASUS
+\\TOLTEC               Samba 2.2.5
+\\YAQUI                Windows 95 on mixtec/VMware
+\\ZAPOTEC
+The command completed successfully.</pre></blockquote>
+
+<p>Then, <em class="emphasis">net view</em> can be used with a computer name
+as an argument to contact a server directly and list the resources it
+is sharing:</p>
+
+<blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>net view \\maya</b></tt>
+Shared resources at \\maya
+
+Windows 98
+
+Share name   Type         Used as  Comment
+
+-------------------------------------------------------------------------------
+D            Disk
+E            Disk
+HP           Print
+The command completed successfully.</pre></blockquote>
+
+<p>The computers on the network involved in browsing are more than just
+the master browser and its clients. There are also backup browsers,
+which maintain copies of the browse list and respond to client
+requests for it. Backup browsers are therefore able to take over the
+role of master browser seamlessly in case it fails. The master
+browser usually doesn't serve the browse list
+directly to clients. Instead, its job is mainly to keep the master
+copy of the browse list up-to-date, and also periodically update the
+backup browsers. Clients are expected to get their copies of the
+browse list from backup browsers, selecting among them randomly to
+help to distribute the load on the backup browsers more evenly.
+Ideally, the interaction between any client and the master browser is
+limited to the client announcing when it joins or leaves the network
+(if it is a server) and requesting a list of backup browsers.</p>
+
+<p>There can be more than one <a name="INDEX-45"/>backup browser. A workgroup will have a
+backup browser if two or more computers are running Windows 95/98/Me
+or Windows NT Workstation (or another nonserver version of Windows
+NT/2000/XP) on the subnet. For every 32 additional computers, another
+backup browser is added.</p>
+
+<p>In a Windows NT domain, the <a name="INDEX-46"/>primary domain controller is
+always the local master browser, and if it fails, another Windows
+NT/2000 server (if one exists) will take over the role of local
+master browser. Other versions of Windows can function as backup
+browsers, but will never become a master browser if a Windows NT/2000
+server is available.</p>
+
+<p>In addition to acting as the local master browser, the primary domain
+controller also acts as the <em class="firstterm">domain master
+browser</em><a name="INDEX-47"/>, which ties subnets together and allows
+browse lists to be shared between master and backup browsers on
+separate subnets. This is how browsing is extended to function beyond
+the local subnet. Each subnet functions as a separate browsing
+entity, and the domain master browser synchronizes the master
+browsers of each subnet. In a Windows-only network, browsing cannot
+function across subnets unless a Windows NT/2000 PDC exists on the
+network. Samba can act as a domain master browser and can perform
+that task even in a workgroup network, which means that the Windows
+PDC is not required for this task. (It is also possible to use the
+<tt class="literal">remote</tt> <tt class="literal">browse</tt>
+<tt class="literal">sync</tt> parameter to configure a Samba server to
+synchronize its browse list with a Samba server on another subnet. In
+this case, each server must be acting as the local master browser of
+its subnet.)</p>
+
+<p>Unless it is configured never to act as a browser, each computer on
+the subnet is considered a <em class="firstterm">potential browser</em>
+and can be ordered by the browse master to become a backup browser,
+or it can identify itself as a backup browser and accept the role on
+its own.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.2"/>
+
+<h3 class="head2">Browser Elections</h3>
+
+<p><a name="INDEX-48"/>When no master browser is running on
+the subnet, potential browsers choose a new master browser among
+themselves in a process called an <em class="firstterm">election</em>. An
+election is started by a computer in the subnet when it discovers
+that no master browser is currently running. If a master browser is
+shut down gracefully, it will broadcast an election request datagram,
+initiating an election by the remaining computers. If the master
+browser fails, the election can be started by a client computer that
+requests a list of backup browsers from the master browser or by a
+backup browser that requests to have its browse list updated from the
+master browser. In each case, the system fails to receive a reply
+from the master browser and initiates the election.</p>
+
+<p>Browser elections are decided in multiple rounds of self-elimination.
+During each round, potential browsers broadcast election request
+datagrams containing their qualifications to notify other potential
+browsers that an election is happening and that if the recipient is
+more qualified, it should also broadcast a bid. When a potential
+browser receives an election request datagram from a more qualified
+opponent, it drops out, disqualifying itself from becoming the master
+browser. Otherwise, it responds with its own election request
+datagram. After a few rounds, only one potential browser is left in
+the election. After an additional four rounds of sending out an
+election request datagram and receiving no response, it becomes the
+master browser and sends a broadcast datagram announcing itself as
+the local master browser for the subnet. It then assigns runners-up
+in the election as backup browsers, as needed.</p>
+
+<p>A potential browser's qualifications include the
+following:</p>
+
+<ul><li>
+<p>Whether it has recently lost an election</p>
+</li><li>
+<p>The version of the election protocol it is running</p>
+</li><li>
+<p>Its election criteria</p>
+</li><li>
+<p>The amount of time the system has been up</p>
+</li><li>
+<p>The computer's NetBIOS name</p>
+</li></ul>
+<p>If the potential browser has lost an election recently, it
+immediately disqualifies itself. The version of the election protocol
+it is running is checked, but so far, all Windows systems (and Samba)
+use the same election protocol, so the check is not very meaningful.
+The election criteria are usually what determine which computer
+becomes the local master browser. There are two parts to the election
+criteria, shown in Tables <a href="ch07.html#samba2-CHP-7-TABLE-2">Table 7-2</a> and <a href="ch07.html#samba2-CHP-7-TABLE-3">Table 7-3</a>.</p>
+
+<a name="samba2-CHP-7-TABLE-2"/><h4 class="head4">Table 7-2. Operating-system values in an election</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Operating system</p>
+</th>
+<th>
+<p>Value</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Windows NT/2000 Server, running as PDC</p>
+</td>
+<td>
+<p>32</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT/2000/XP, if not the PDC</p>
+</td>
+<td>
+<p>16</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95/98/Me</p>
+</td>
+<td>
+<p>1</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows for Workgroups</p>
+</td>
+<td>
+<p>1</p>
+</td>
+</tr>
+
+</table>
+
+<a name="samba2-CHP-7-TABLE-3"/><h4 class="head4">Table 7-3. Computer-role settings in an election</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Role</p>
+</th>
+<th>
+<p>Value</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Domain master browser</p>
+</td>
+<td>
+<p>128</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>WINS client</p>
+</td>
+<td>
+<p>32</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Preferred master</p>
+</td>
+<td>
+<p>8</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Running master</p>
+</td>
+<td>
+<p>4</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Recent backup browser</p>
+</td>
+<td>
+<p>2</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Backup browser</p>
+</td>
+<td>
+<p>1</p>
+</td>
+</tr>
+
+</table>
+
+<p>The operating-system type is compared first, and the system with the
+highest value wins. The values have been chosen to cause the primary
+domain controller, if there is one, to become the local master
+browser. Otherwise, a Windows NT/2000/XP system will win over a
+Windows for Workgroups or Windows 95/98/Me system.</p>
+
+<p>When an operating-system type comparison results in a tie, the role
+of the computer is compared. A computer can have more than one of the
+values in <a href="ch07.html#samba2-CHP-7-TABLE-3">Table 7-3</a>, in which case the values are
+added.</p>
+
+<p>A domain master browser has a role value of 128 to weight the
+election so heavily in its favor that it will also become the local
+master browser on its own subnet. Although the primary domain
+controller (which is always the domain master browser) will win the
+election based solely on its operating system value, sometimes there
+is no primary domain controller on the network, and the domain master
+browser would not otherwise be distinguished from other potential
+browsers.</p>
+
+<p>Systems that are using a WINS server for name resolution are weighted
+heavily over ones that use broadcast name resolution with a role
+value of 32.</p>
+
+<p>A <em class="firstterm">preferred master</em> is a computer that has been
+selected and configured manually by a system administrator to be
+favored as the choice master browser. When a preferred master starts
+up, it forces a browser election, even if an existing master browser
+is still active. A preferred master has a role value of 8, and the
+existing master browser gets a value of 4.</p>
+
+<p>A backup browser that has recently been a master browser and still
+has an up-to-date browse list is given a role value of 2, and a
+potential browser that has been running as a backup browser gets a
+value of 1.</p>
+
+<p>If comparing the operating-system type and role results in a tie, the
+computer that has been running the longest wins. In the unlikely
+event that the two have been up for the same amount of time, the
+computer that wins is the one with the NetBIOS name that sorts first
+alphabetically.</p>
+
+<p>You can tell if a machine is a local master browser by using the
+Windows <em class="emphasis">nbtstat</em><a name="INDEX-49"/> command. Place the NetBIOS name of the
+machine you wish to check after the <em class="emphasis">-a</em> option:</p>
+
+<blockquote><pre class="code">C:\&gt;<tt class="userinput"><b>nbtstat -a toltec</b></tt>
+
+Local Area Connection:
+Node IpAddress: [172.16.1.4] Scope Id: []
+
+           NetBIOS Remote Machine Name Table
+
+       Name               Type         Status
+    ---------------------------------------------
+    TOLTEC         &lt;00&gt;  UNIQUE      Registered
+    TOLTEC         &lt;03&gt;  UNIQUE      Registered
+    TOLTEC         &lt;20&gt;  UNIQUE      Registered
+    ..__MSBROWSE__.&lt;01&gt;  GROUP       Registered
+    METRAN         &lt;00&gt;  GROUP       Registered
+    METRAN         &lt;1B&gt;  UNIQUE      Registered
+    METRAN         &lt;1C&gt;  GROUP       Registered
+    METRAN         &lt;1D&gt;  UNIQUE      Registered
+    METRAN         &lt;1E&gt;  GROUP       Registered
+
+    MAC Address = 00-00-00-00-00-00</pre></blockquote>
+
+<p>The resource entry that you're looking for is
+<tt class="literal">.._ _MSBROWSE_ _.&lt;01&gt;</tt><a name="INDEX-50"/>. This indicates
+that the server is currently acting as the local master browser for
+the current subnet. If the machine is a Samba server, you can check
+the Samba <em class="filename">nmbd</em> log file for an entry such as:</p>
+
+<blockquote><pre class="code">nmbd/nmbd_become_lmb.c:become_local_master_stage2(406)
+*****
+Samba name server TOLTEC is now a local master browser for
+workgroup METRAN on subnet 172.16.1.0</pre></blockquote>
+
+<p>Or, you can use the
+<em class="emphasis">nmblookup</em><a name="INDEX-51"/> command with the
+<em class="emphasis">-M</em> option and the workgroup or domain name on
+any Samba server to find the IP address of the local master:</p>
+
+<a name="INDEX-52"/><blockquote><pre class="code">$ <tt class="userinput"><b>nmblookup -M metran</b></tt>
+querying metran on 172.16.1.255
+172.16.1.1 metran&lt;1d&gt;</pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.3"/>
+
+<h3 class="head2">Server Announcements</h3>
+
+<p><a name="INDEX-53"/>After
+the master browser election is decided, each server on the network
+announces itself to the network to allow the master and backup
+browsers to build their browse lists. At first, the server
+announcements happen every minute, but the interval is gradually
+stretched out to every 12 minutes. When a server is shut down
+gracefully, it sends an announcement that it is going offline to
+allow the master and backup browsers to remove it from the browse
+list. However, when a server goes offline by crashing or by some
+other failure, the master browser notices its disappearance only
+because it stops receiving server announcements. The master browser
+waits for three of the server's announcement periods
+before deciding that it is offline, which can take up to 36 minutes.
+Because backup browsers have their browse lists updated from the
+master browser once every 15 minutes, it can take up to 51 minutes
+for clients to be informed of a failed server.</p>
+
+<p>For more detailed information on Microsoft's
+browsing protocols, consult the Microsoft documents
+<em class="citetitle">Browsing and Windows 95
+Networking</em><a name="INDEX-54"/> and
+<em class="citetitle">CIFS/E Browser Protocol</em>. You can find these by
+searching for the titles on the Microsoft web site at <a href="http://www.microsoft.com">http://www.microsoft.com</a>.</p>
+
+<p>More information on configuring Samba for browsing can be found in
+<em class="filename">BROWSING.txt</em><a name="INDEX-55"/> and
+<em class="filename">BROWSING-Config.txt</em> in the Samba
+distribution's <em class="filename">docs/textdocs</em>
+directory. <a name="INDEX-56"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.4"/>
+
+<h3 class="head2">Configuring Samba for Browsing</h3>
+
+<p><a name="INDEX-57"/><a name="INDEX-58"/><a name="INDEX-59"/>Samba has full support for browsing
+and can participate as a master browser, a backup browser, a domain
+master browser, a potential browser, or just a server that
+doesn't participate in browsing elections. If you
+want to make sure your Samba server never becomes a master or backup
+browser, simply set:</p>
+
+<a name="INDEX-60"/><blockquote><pre class="code">[global]
+    local master = no</pre></blockquote>
+
+<p>Usually, you will want Samba to be available as a local master or at
+least a backup browser. In the simplest case, you
+don't need to do anything because
+Samba's default is to participate in browsing
+elections with its operating system value set to 20, which will beat
+any Windows system less than a Windows NT/2000 primary domain
+controller (see <a href="ch07.html#samba2-CHP-7-TABLE-2">Table 7-2</a>). The operating-system
+value Samba reports for itself in browser elections can be set using
+the <tt class="literal">os</tt><a name="INDEX-61"/> <tt class="literal">level</tt>
+parameter:</p>
+
+<blockquote><pre class="code">[global]
+    os level = 33</pre></blockquote>
+
+<p>The preceding value will allow Samba to beat even a Windows 2000
+Advanced Server acting as a primary domain controller. As we show in
+the following section, though, forcing Samba to win this way is not
+recommended.</p>
+
+<p>If you want to allow a Windows XP Professional system to be the
+master browser, you would need to set Samba lower:</p>
+
+<blockquote><pre class="code">[global]
+    os level = 8</pre></blockquote>
+
+<p>The maximum value for <tt class="literal">os</tt> <tt class="literal">level</tt>
+is 255 because it is handled as an 8-bit unsigned integer. Supposing
+we wanted to make absolutely sure our Samba server will be the local
+master browser at all times, we might say:</p>
+
+<blockquote><pre class="code">[global]
+    local master = yes
+    os level = 255
+    preferred master = yes</pre></blockquote>
+
+<p>The addition of the
+<tt class="literal">preferred</tt><a name="INDEX-62"/>
+<tt class="literal">master</tt> parameter causes Samba to start a browser
+election as soon as it starts up, and the <tt class="literal">os</tt>
+<tt class="literal">level</tt> of 255 allows it to beat any other system on
+the network. This includes other Samba servers, assuming they are
+configured properly! If another server is using a similar
+configuration file (with <tt class="literal">os</tt>
+<tt class="literal">level</tt> <tt class="literal">=</tt> <tt class="literal">255</tt>
+and <tt class="literal">preferred</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt>), the two will fight each
+other for the master browser role, winning elections based on minor
+criteria, such as uptime or their current role. To avoid this, other
+Samba servers should be set with a lower <tt class="literal">os</tt>
+<tt class="literal">level</tt> and not configured to be the preferred
+master.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.5"/>
+
+<h3 class="head2">Samba as the Domain Master Browser</h3>
+
+<p><a name="INDEX-63"/>Previously we mentioned that for a Windows
+workgroup or domain to extend into multiple subnets, one system would
+have to take the role of the domain master browser. The domain master
+browser propagates browse lists across each subnet in the workgroup.
+This works because each local master browser periodically
+synchronizes its browse list with the domain master browser. During
+this synchronization, the local master browser passes on the name of
+any server that the domain master browser does not have in its browse
+list, and vice versa. Each local master browser eventually holds the
+browse list for the entire domain.</p>
+
+<p>There is no election to determine which machine assumes the role of
+the domain master browser. Instead, the administrator has to set it
+manually. By Microsoft design, however, the domain master browser and
+the PDC both register a resource type of &lt;1B&gt;, so the
+roles&mdash;and the machines&mdash;are inseparable.</p>
+
+<p>If you have a Windows NT server on the network acting as a PDC, we
+recommend that you do not try to use Samba to become the domain
+master browser. The reverse is true as well: if Samba is taking on
+the responsibilities of a PDC, we recommend making it the domain
+master browser as well. Although it is possible to split the roles
+with Samba, this is not a good idea. Using two different machines to
+serve as the PDC and the domain master browser can cause random
+errors to occur in a Windows workgroup.</p>
+
+<p>Samba can assume the role of a domain master browser for all subnets
+in the workgroup with the following options:</p>
+
+<blockquote><pre class="code">[global]
+    domain master = yes
+    preferred master = yes
+    local master = yes
+    os level = 255</pre></blockquote>
+
+<p>The final three parameters ensure that the server is also the local
+master browser, which is vital for it to work properly as the domain
+master browser. You can verify that a Samba machine is in fact the
+<a name="INDEX-64"/>domain master browser by checking the
+<em class="emphasis">nmbd</em><a name="INDEX-65"/><a name="INDEX-66"/> log file:</p>
+
+<blockquote><pre class="code">nmbd/nmbd_become_dmb.c:become_domain_master_stage2(118)
+*****
+Samba name server TOLTEC is now a domain master browser for
+workgroup METRAN on subnet 172.16.1.0</pre></blockquote>
+
+<p>Or you can use the
+<em class="emphasis">nmblookup</em><a name="INDEX-67"/> command that comes with the Samba
+distribution to query for a unique &lt;1B&gt; resource type in the
+workgroup:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>nmblookup METRAN#1B</b></tt>
+Sending queries to 172.16.1.255
+172.16.1.1 METRAN&lt;1b&gt;</pre></blockquote>
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.5.1"/>
+
+<h3 class="head3">Multiple subnets</h3>
+
+<p><a name="INDEX-68"/>You must
+remember three rules when creating a
+<a name="INDEX-69"/>workgroup/domain
+that spans more than one subnet:</p>
+
+<ul><li>
+<p>You must have either a Windows NT/2000 or Samba server acting as a
+local master browser on each subnet in the workgroup/domain.</p>
+</li><li>
+<p>You must have a Windows NT/2000 Server edition or a Samba server
+acting as a domain master browser somewhere in the workgroup/domain.</p>
+</li><li>
+<p>A WINS server should be on the network, with each system on the
+network configured to use it for name resolution.</p>
+</li></ul>
+<p>Samba has some additional features you can use if you
+don't have or want a domain master browser on your
+network and still need to have <a name="INDEX-70"/>cross-subnet browsing. Consider the
+subnets shown in <a href="ch07.html#samba2-CHP-7-FIG-1">Figure 7-1</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-7-FIG-1"/><a name="INDEX-71"/><a name="INDEX-72"/><img src="figs/sam2_0701.gif"/></div><h4 class="head4">Figure 7-1. Multiple subnets with Samba servers</h4>
+
+<p>First, a Samba server that is a local master browser can use the
+<tt class="literal">remote</tt><a name="INDEX-73"/> <tt class="literal">announce</tt>
+configuration option to make sure that computers in different subnets
+are sent broadcast announcements about the server. This has the
+effect of ensuring that the Samba server appears in the browse lists
+of foreign subnets. To achieve this, however, the directed broadcasts
+must reach the local master browser on the other subnet. Be aware
+that many routers do not allow directed broadcasts by default; you
+might have to change this setting on the router for the directed
+broadcasts to get through to its subnet.</p>
+
+<p>With the <tt class="literal">remote</tt> <tt class="literal">announce</tt>
+option, list the subnets and the workgroup that should receive the
+broadcast. For example, to ensure that machines in the 172.16.2 and
+172.16.3 subnets and the METRAN workgroup are sent broadcast
+information from our Samba server, we could specify the following:</p>
+
+<blockquote><pre class="code">[global]
+    remote announce = 172.16.2.255/METRAN \
+        172.16.3.255/METRAN</pre></blockquote>
+
+<p>Instead of supplying a broadcast address of the remote subnet, you
+are allowed to specify the exact address where broadcasts should be
+sent if the local master browser on the foreign subnet is guaranteed
+to always have the same IP address.</p>
+
+<p>A Samba local master browser can synchronize its browse list directly
+with one or more Samba servers, each acting as a local master browser
+on a different subnet. This is another way to implement browsing
+across subnets. For example, let's assume that Samba
+is configured as a local master browser, and Samba local master
+browsers exist at 172.16.2.130 and 172.16.3.120. We can use the
+<tt class="literal">remote</tt> <tt class="literal">browse</tt>
+<tt class="literal">sync</tt> option to sync directly with the Samba
+servers, as follows:</p>
+
+<blockquote><pre class="code">[global]
+    remote browse sync = 172.16.2.130 172.16.3.120</pre></blockquote>
+
+<p>For this to work, the other Samba machines must also be local master
+browsers. You can also use directed broadcasts with this option if
+you do not know specific IP addresses of local master browsers.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.6"/>
+
+<h3 class="head2">Making a Share Invisible</h3>
+
+<p><a name="INDEX-74"/><a name="INDEX-75"/><a name="INDEX-76"/>You can keep a share from being in the
+browse list by using the
+<tt class="literal">browsable</tt><a name="INDEX-77"/> option. This Boolean option
+prevents a share from being seen in the Network Neighborhood or My
+Network Places. For example, to prevent the <tt class="literal">[data]</tt>
+share from being visible, we could write:</p>
+
+<blockquote><pre class="code">[data]
+    path = /export/samba/userdata
+    browsable = no</pre></blockquote>
+
+<p>Although you typically don't want to do this to an
+ordinary disk share, the <tt class="literal">browsable</tt> option is
+useful in the event that you need to create a share with contents
+that you do not want others to see, such as a
+<tt class="literal">[netlogon]</tt><a name="INDEX-78"/> share for storing logon scripts
+for Windows domain control (see <a href="ch04.html">Chapter 4</a> for more
+information on logon scripts).</p>
+
+<p>Another example is the
+<tt class="literal">[homes]</tt><a name="INDEX-79"/> share. This share is often marked
+nonbrowsable so that a share named <tt class="literal">[homes]</tt>
+won't appear when its machine's
+resources are browsed. However, if a user <tt class="literal">alice</tt>
+logs on and looks at the machine's shares, an
+<tt class="literal">[alice]</tt> share will appear under the machine.</p>
+
+<p>What if we wanted to make sure
+<tt class="literal">alice</tt>'s share appeared to
+everyone before she logs on? This could be done with the global
+<tt class="literal">auto</tt><a name="INDEX-80"/> <tt class="literal">services</tt>
+option. This option preloads shares into the browse list to ensure
+that they are always visible:</p>
+
+<blockquote><pre class="code">[global]
+    auto services = alice</pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-7-SECT-2.7"/>
+
+<h3 class="head2">Browsing Options</h3>
+
+<p><a href="ch07.html#samba2-CHP-7-TABLE-4">Table 7-4</a> <a name="INDEX-81"/><a name="INDEX-82"/>shows
+options that define how Samba handles browsing tasks.</p>
+
+<a name="samba2-CHP-7-TABLE-4"/><h4 class="head4">Table 7-4. Browsing configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">announce as</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Operating system that Samba will announce itself as.</p>
+</td>
+<td>
+<p><tt class="literal">N T Server</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">announce</tt> <tt class="literal">version</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Version of the operating system that Samba will announce itself as.</p>
+</td>
+<td>
+<p><tt class="literal">4.5</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">browsable</tt> <tt class="literal">(browseable)</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Allows share to be displayed in list of machine resources.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">browse list</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows Samba to provide a browse list on
+this server.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">auto services</tt> <tt class="literal">(preload)</tt></p>
+</td>
+<td>
+<p>string (share list)</p>
+</td>
+<td>
+<p>List of shares that will always appear in the browse list.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">default</tt> <tt class="literal">service (default)</tt></p>
+</td>
+<td>
+<p>string (share name)</p>
+</td>
+<td>
+<p>Name of a share (service) that will be provided if the client
+requests a share not listed in <em class="emphasis">smb.conf</em>.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">local master</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows Samba to participate in browsing
+elections.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lm announce</tt></p>
+</td>
+<td>
+<p><tt class="literal">yes</tt>, <tt class="literal">no</tt>, or
+<tt class="literal">auto</tt></p>
+</td>
+<td>
+<p>Enables or disables LAN Manager-style host announcements.</p>
+</td>
+<td>
+<p><tt class="literal">auto</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lm interval</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Frequency in seconds that LAN Manager announcements will be made if
+activated.</p>
+</td>
+<td>
+<p><tt class="literal">60</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">preferred</tt> <tt class="literal">master (prefered
+master)</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows Samba to use the preferred master
+browser bit to attempt to become the local master browser.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">domain master</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows Samba to become the domain browser
+master for the workgroup or domain.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">os level</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Operating system level of Samba in an election for local master
+browser.</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">remote browse</tt> <tt class="literal">sync</tt></p>
+</td>
+<td>
+<p>string (list of IP addresses)</p>
+</td>
+<td>
+<p>Samba servers to synchronize browse lists with.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">remote</tt> <tt class="literal">announce</tt></p>
+</td>
+<td>
+<p>string (IP address/workgroup pairs)</p>
+</td>
+<td>
+<p>Subnets and workgroups to send directed broadcast packets to,
+allowing Samba to appear in their browse lists.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.1"/>
+
+<a name="INDEX-83"/><h3 class="head3">announce as</h3>
+
+<p>This global configuration option specifies the type of operating
+system that Samba announces to other machines on the network. The
+default value for this option is <tt class="literal">N T</tt>
+<tt class="literal">Server</tt>, which causes Samba to masquerade as a
+Windows NT Server operating system. Other possible values are
+<tt class="literal">NT</tt>, <tt class="literal">NT</tt>
+<tt class="literal">Workstation</tt>, <tt class="literal">Win95</tt>, and
+<tt class="literal">W f W</tt> for a Windows for Workgroup operating
+system. You can override the default value with the following:</p>
+
+<blockquote><pre class="code">[global]
+    announce as = Win95</pre></blockquote>
+
+<p>We recommend against changing the default value of this configuration
+option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.2"/>
+
+<a name="INDEX-84"/><h3 class="head3">announce version</h3>
+
+<p>This global option is frequently used with the
+<tt class="literal">announce</tt> <tt class="literal">as</tt> configuration
+option; it specifies the version of the operating system that Samba
+announces to other machines on the network. The default value of this
+option is 4.5, which places Samba above Windows NT Version 4.0, but
+below Windows 2000. You can specify a new value with a global entry
+such as the following:</p>
+
+<blockquote><pre class="code">[global]
+    announce version = 4.3</pre></blockquote>
+
+<p>We recommend against changing the default value of this configuration
+option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.3"/>
+
+<h3 class="head3">browsable</h3>
+
+<p>The <tt class="literal">browsable</tt><a name="INDEX-85"/> option (also spelled
+<tt class="literal">browseable</tt>) indicates whether the share referenced
+should appear in the list of available resources for the system on
+which it resides. This option is always set to <tt class="literal">yes</tt>
+by default. If you wish to prevent the share from being seen in a
+client's browser, you can reset this option to
+<tt class="literal">no</tt>.</p>
+
+<p>Note that this does not prevent someone from accessing the share
+using other means, such as specifying a UNC location (e.g.,
+<tt class="literal">\\server\accounting)</tt> in Windows Explorer. It only
+prevents the share from being listed under the
+system's resources when being browsed.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.4"/>
+
+<a name="INDEX-86"/><h3 class="head3">browse list</h3>
+
+<p>You should never need to change this parameter from its default value
+of <tt class="literal">yes</tt>. If your Samba server is acting as a local
+master browser (i.e., it has won the browsing election), you can use
+the global <tt class="literal">browse</tt> <tt class="literal">list</tt> option
+to instruct Samba to provide or withhold its browse list to all
+clients. By default, Samba always provides a browse list. You can
+withhold this information by specifying the following:</p>
+
+<blockquote><pre class="code">[global]
+    browse list = no</pre></blockquote>
+
+<p>If you disable the browse list, clients cannot browse the names of
+other machines, their services, and other domains currently available
+on the network. Note that this won't make any
+particular machine inaccessible; if someone knows a valid machine
+name/address and a share on that machine, he can still connect to it
+explicitly using the Windows <em class="emphasis">net use</em> command or
+by mapping a drive letter to it using Windows Explorer. It simply
+prevents information in the browse list from being retrieved by any
+client that requests it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.5"/>
+
+<h3 class="head3">auto services</h3>
+
+<p>The global <tt class="literal">auto</tt><a name="INDEX-87"/>
+<tt class="literal">services</tt> option, which is also called
+<tt class="literal">preload</tt> <a name="INDEX-88"/>, ensures that the specified
+shares are always visible in the browse list. One common use for this
+option is to advertise specific user or printer shares that are
+created by the <tt class="literal">[homes]</tt> or
+<tt class="literal">[printers]</tt> shares, but are not otherwise
+browsable.</p>
+
+<p>This option works best with disk shares. If you wish to force each of
+your system printers (i.e., those listed in the printer capabilities
+file) to appear in the browse list, we recommend using the
+<tt class="literal">load</tt> <tt class="literal">printers</tt> option instead.</p>
+
+<p>Shares listed with the <tt class="literal">auto</tt>
+<tt class="literal">services</tt> option will not be displayed if the
+<tt class="literal">browse</tt> <tt class="literal">list</tt> option is set to
+<tt class="literal">no</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.6"/>
+
+<h3 class="head3">default service</h3>
+
+<p>The global <tt class="literal">default</tt><a name="INDEX-89"/>
+<tt class="literal">service</tt> option (sometimes called
+<tt class="literal">default</tt>) names a
+&quot;last-ditch&quot; share. The value is
+set to an existing share name without the enclosing brackets. When a
+client requests a nonexistent disk or printer share, Samba will
+attempt to connect the user to the share specified by this option
+instead. The option is specified as follows:</p>
+
+<blockquote><pre class="code">[global]
+    default service = helpshare</pre></blockquote>
+
+<p>When Samba redirects the requested, nonexistent service to the
+service specified by <tt class="literal">default</tt>
+<tt class="literal">service</tt>, the <tt class="literal">%S</tt> option takes on
+the value of the requested service, with any underscores (
+<tt class="literal">_</tt> ) in the requested service replaced by forward slashes
+(<tt class="literal">/</tt>).</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.7"/>
+
+<a name="INDEX-90"/><h3 class="head3">local master</h3>
+
+<p>This global option specifies whether Samba will attempt to become the
+local master browser for the subnet when it starts up. If this option
+is set to <tt class="literal">yes</tt>, Samba will participate in
+elections. However, setting this option by itself does not guarantee
+victory. (Other parameters, such as <tt class="literal">preferred</tt>
+<tt class="literal">master</tt> and <tt class="literal">os</tt>
+<tt class="literal">level</tt>, help Samba win browsing elections.) If this
+option is set to <tt class="literal">no</tt>, Samba will lose all browsing
+elections, regardless of which values are specified by the other
+configuration options. The default value is <tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.8"/>
+
+<h3 class="head3">lm announce</h3>
+
+<p>The global <tt class="literal">lm</tt><a name="INDEX-91"/>
+<tt class="literal">announce</tt> option tells Samba's
+<em class="emphasis">nmbd</em> whether to send <a name="INDEX-92"/>LAN Manager host
+announcements on behalf of the server. These host announcements might
+be required by older clients, such as IBM's OS/2
+operating system. This announcement allows the server to be added to
+the browse lists of the client. If activated, Samba will announce
+itself repetitively at the number of seconds specified by the
+<tt class="literal">lm</tt> <tt class="literal">interval</tt> option.</p>
+
+<p>You can specify the option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    lm announce = yes</pre></blockquote>
+
+<p>This configuration option takes the standard Boolean values,
+<tt class="literal">yes</tt> and <tt class="literal">no</tt>, which enable or
+disable LAN Manager announcements, respectively. In addition, a third
+option, <tt class="literal">auto</tt>, causes <em class="emphasis">nmbd</em> to
+listen passively for LAN Manager announcements, but not to send any
+of its own initially. If LAN Manager announcements are detected for
+another machine on the network, <em class="emphasis">nmbd</em> will start
+sending its own LAN Manager announcements to ensure that it is
+visible. The default value is <tt class="literal">auto</tt>. You probably
+won't need to change this value from its default.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.9"/>
+
+<a name="INDEX-93"/><h3 class="head3">lm interval</h3>
+
+<p>This option, which is used in conjunction with <tt class="literal">lm</tt>
+<tt class="literal">announce</tt>, indicates the number of seconds
+<em class="emphasis">nmbd</em> will wait before repeatedly broadcasting
+LAN Manager-style announcements. LAN Manager announcements must be
+enabled for this option to work. The default value is 60 seconds. If
+you set this value to 0, Samba will not send any LAN Manager host
+announcements, regardless of the value of the <tt class="literal">lm</tt>
+<tt class="literal">announce</tt> option. You can reset the value of this
+option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    lm interval = 90</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.10"/>
+
+<h3 class="head3">preferred master</h3>
+
+<p>The <tt class="literal">preferred</tt><a name="INDEX-94"/>
+<tt class="literal">master</tt> option requests that Samba set the
+preferred master bit when participating in an election. This gives
+the server a higher preferred status in the workgroup than other
+machines at the same operating-system level. If you are configuring
+your Samba machine to become the local master browser, it is wise to
+set the following value:</p>
+
+<blockquote><pre class="code">[global]
+    preferred master = yes</pre></blockquote>
+
+<p>Otherwise, you should leave it set to its default,
+<tt class="literal">no</tt>. If Samba is configured as a preferred master
+browser, it will force an election when it first comes online.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.11"/>
+
+<a name="INDEX-95"/><h3 class="head3">domain master</h3>
+
+<p>If Samba is the primary domain controller for your workgroup or NT
+domain, it should also be made the domain master browser. The domain
+master browser is a special machine that has the NetBIOS resource
+type &lt;1B&gt; and is used to propagate browse lists to and from
+each local master browser in individual subnets across the domain. To
+force Samba to become the <a name="INDEX-96"/>domain master browser, set the following in
+the <tt class="literal">[global]</tt> section of the
+<em class="filename">smb.conf</em>:</p>
+
+<blockquote><pre class="code">[global]
+    domain master = yes</pre></blockquote>
+
+<p>If you have a Windows NT server on the network acting as a primary
+domain controller (PDC), we recommend that you do not use Samba to
+become the domain master browser. The reverse is true as well: if
+Samba is taking on the responsibilities of a PDC, we recommend making
+it the domain master browser. Splitting the PDC and the domain master
+browser will cause unpredictable errors to occur on the network.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.12"/>
+
+<h3 class="head3">os level</h3>
+
+<p>The global <tt class="literal">os</tt><a name="INDEX-97"/> <tt class="literal">level</tt> option
+defines the operating-system value with which Samba will masquerade
+during a browser election. If you wish to have Samba win an election
+and become the master browser, set the <tt class="literal">os</tt>
+<tt class="literal">level</tt> higher than that of any other system on the
+subnet. The values are shown in <a href="ch07.html#samba2-CHP-7-TABLE-2">Table 7-2</a>. The
+default level is 20, which means that Samba will win elections
+against all versions of Windows, except Windows NT/2000 if it is
+operating as the PDC. If you wish Samba to win all elections, you can
+set its operating system value as follows:</p>
+
+<blockquote><pre class="code">[global]
+    os level = 255</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.13"/>
+
+<h3 class="head3">remote browse sync</h3>
+
+<p>The global <tt class="literal">remote</tt><a name="INDEX-98"/>
+<tt class="literal">browse</tt> <tt class="literal">sync</tt> option specifies
+that Samba should synchronize its browse lists with local master
+browsers in other subnets. However, the synchronization can occur
+only with other Samba servers and not with Windows computers. For
+example, if your Samba server were a master browser on the subnet
+172.16.235, and Samba local master browsers existed on other subnets
+located at 172.16.234.92 and 172.16.236.2, you would specify the
+following:</p>
+
+<blockquote><pre class="code">[global]
+    remote browse sync = 172.16.234.92 172.16.236.2</pre></blockquote>
+
+<p>The Samba server would then directly contact the other machines on
+the address list and synchronize browse lists. You can also say:</p>
+
+<blockquote><pre class="code">[global]
+    remote browse sync = 172.16.234.255 172.16.236.255</pre></blockquote>
+
+<p>This forces Samba to broadcast queries to determine the IP addresses
+of the local master browser on each subnet, with which it will then
+synchronize browse lists. This works, however, only if your router
+doesn't block directed broadcast requests ending in
+255.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-7-SECT-2.7.14"/>
+
+<h3 class="head3">remote announce</h3>
+
+<p>Samba servers are capable of providing browse lists to foreign
+subnets with the <tt class="literal">remote</tt><a name="INDEX-99"/>
+<tt class="literal">announce</tt> option. This is typically sent to the
+local master browser of the foreign subnet in question. However, if
+you do not know the address of the local master browser, you can do
+the following:</p>
+
+<blockquote><pre class="code">[global]
+    remote announce = 172.16.234.255/ACCOUNTING \       
+                        172.16.236.255/ACCOUNTING</pre></blockquote>
+
+<p>With this, Samba will broadcast host announcements to all machines on
+subnets 172.16.234 and 172.16.236, which will hopefully reach the
+local master browser of the subnet.</p>
+
+<p>You can also specify exact IP addresses, if they are known, but this
+works only if the systems are guaranteed to maintain the role of
+master browser on their subnets. By appending a workgroup or domain
+name to the IP address, Samba announces that it is in that workgroup
+or domain. If this is left out, the workgroup set by the
+<tt class="literal">workgroup</tt> parameter is used. <a name="INDEX-100"/> <a name="INDEX-101"/><a name="INDEX-102"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> As we explained in
+<a href="ch01.html">Chapter 1</a>, a system can register under more than
+one NetBIOS name. We use the singular here only to keep our
+explanation simple.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch08.html b/docs/htmldocs/using_samba/ch08.html
new file mode 100644
index 0000000000..001a86a4a3
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch08.html
@@ -0,0 +1,3744 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 8. Advanced Disk Shares</h1>
+
+
+<p>This chapter continues our discussion of configuring Samba from <a href="ch06.html">Chapter 6</a>. We will cover some more advanced issues
+regarding the integration of Unix and Windows filesystems, including
+hidden files, Unix links, file permissions, name mangling, case
+sensitivity of filenames, file locking, opportunistic locking
+(oplocks), connection scripts, supporting Microsoft Dfs (Distributed
+filesystem) shares, and using NIS home directories.</p>
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-1"/>
+
+<h2 class="head1">Filesystem Differences</h2>
+
+<p>One of the biggest issues for which Samba has to correct is the
+difference between Unix and Microsoft filesystems. This includes
+items such as handling symbolic links, hidden files, and dot files.
+In addition, file permissions can also be a headache if not properly
+accounted for.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-1.1"/>
+
+<h3 class="head2">Hiding and Vetoing Files</h3>
+
+<p><a name="INDEX-1"/><a name="INDEX-2"/>Sometimes you need to ensure that a user
+cannot see or access a file at all. Other times, you
+don't want to keep users from accessing a
+file&mdash;you just want to hide it when they view the contents of
+the directory. On Windows systems, an attribute of files allows them
+to be hidden from a folder listing. With Unix, the traditional way of
+hiding files in a directory is to use a <a name="INDEX-3"/><a name="INDEX-4"/>dot (.) as the first character in the
+filename. This prevents items such as configuration files from being
+seen when performing an ordinary <em class="emphasis">ls</em> command.
+Keeping a user from accessing a file at all, however, involves
+working with permissions on files and directories.</p>
+
+<p>The first option we should discuss is the Boolean
+<tt class="literal">hide</tt><a name="INDEX-5"/><a name="INDEX-6"/> <tt class="literal">dot</tt>
+<tt class="literal">files</tt>. When it is set to <tt class="literal">yes</tt>,
+Samba reports files beginning with a period (.) as having their
+hidden attribute set. If the user has chosen to show all hidden files
+while browsing (e.g., using the Folder Options menu item under the
+View menu in Windows 98), he will still be able to see the files,
+although his icons will appear
+&quot;ghosted,&quot; or slightly grayed-out.
+If the client is configured not to show hidden files, the files will
+not appear at all.</p>
+
+<p>Instead of simply hiding files beginning with a dot, you can also
+specify a string pattern to Samba for files to hide, using the
+<tt class="literal">hide</tt><a name="INDEX-7"/> <tt class="literal">files</tt>
+option. For example, let's assume you specified the
+following in our example <tt class="literal">[data]</tt> share:</p>
+
+<blockquote><pre class="code">[data]
+    hide files = /*.java/*README*/</pre></blockquote>
+
+<p>Each entry for this option must begin, end, or be separated from
+another with a slash ( / ) character, even if only one pattern is
+listed. This convention allows spaces to appear in filenames. The
+slashes have nothing to do with Unix directories; they are instead
+acting as delimiters for the <tt class="literal">hide</tt>
+<tt class="literal">files</tt> values.</p>
+
+<p>If you want to prevent users from seeing files completely, you can
+instead use the <tt class="literal">veto</tt><a name="INDEX-8"/> <tt class="literal">files</tt>
+option. This option, which takes the same syntax as the
+<tt class="literal">hide</tt> <tt class="literal">files</tt> option, specifies a
+list of files that should never be seen by the user. For example,
+let's change the <tt class="literal">[data]</tt> share to
+the following:</p>
+
+<blockquote><pre class="code">[data]
+    veto files = /*.java/*README*/</pre></blockquote>
+
+<p>The syntax of this option is identical to the <tt class="literal">hide</tt>
+<tt class="literal">files</tt> configuration option: each entry must begin,
+end, or be separated from another with a slash (<tt class="literal">/</tt>)
+character, even if only one pattern is listed. If you do so, files
+that match the pattern, such as <em class="filename">hello.java</em> and
+<em class="filename">README.txt,</em> will simply disappear from the
+directory, and the user cannot access them through SMB.</p>
+
+<p><a name="INDEX-9"/>We need to address
+one other question. What happens if the user tries to delete a
+directory that contains vetoed files? This is where the
+<tt class="literal">delete</tt><a name="INDEX-10"/> <tt class="literal">veto</tt>
+<tt class="literal">files</tt> option comes in. If this Boolean option is
+set to <tt class="literal">yes</tt>, the user can delete both the regular
+files and the vetoed files in the directory, and the directory itself
+is removed. If the option is set to <tt class="literal">no</tt>, the user
+cannot delete the vetoed files, and consequently the directory is not
+deleted either. From the user's perspective, the
+directory appears empty, but cannot be removed.</p>
+
+<p>The <tt class="literal">dont</tt><a name="INDEX-11"/> <tt class="literal">descend</tt>
+directive specifies a list of directories whose contents Samba should
+not make visible. Note that we say <em class="emphasis">contents</em>, not
+the directory itself. Users can enter a directory marked as such, but
+they are prohibited from descending the directory tree any
+farther&mdash;they always see an empty folder. For example,
+let's use this option with a more basic form of the
+share that we defined earlier in the chapter:</p>
+
+<blockquote><pre class="code">[data]
+    dont descend = config defaults</pre></blockquote>
+
+<p>In addition, let's assume that the
+<em class="filename">/home/samba/data</em> directory has the following
+contents:</p>
+
+<blockquote><pre class="code">drwxr-xr-x   6 tom      users     1024 Jun 13 09:24 .
+drwxr-xr-x   8 root     root      1024 Jun 10 17:53 ..
+-rw-r--r--   2 tom      users     1024 Jun  9 11:43 README
+drwxr-xr-x   3 tom      users     1024 Jun 13 09:28 config
+drwxr-xr-x   3 tom      users     1024 Jun 13 09:28 defaults
+drwxr-xr-x   3 tom      users     1024 Jun 13 09:28 market</pre></blockquote>
+
+<p>If the user then connects to the share, she would see the directories
+in the share. However, the contents of the
+<em class="filename">/config</em> and <em class="filename">/defaults</em>
+directories would appear empty to her, even if other folders or files
+existed in them. In addition, users cannot write any data to the
+folder (which prevents them from creating a file or folder with the
+same name as one that is already there but invisible). If a user
+attempts to do so, she will receive an &quot;Access
+Denied&quot; message. The <tt class="literal">dont</tt>
+<tt class="literal">descend</tt> option is an administrative
+option&mdash;not a security option&mdash;and is not a substitute for
+good file permissions. <a name="INDEX-12"/><a name="INDEX-13"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-1.2"/>
+
+<h3 class="head2">Links</h3>
+
+<p><a name="INDEX-14"/>When a client
+tries to open a symbolic link on a Samba server share, Samba attempts
+to follow the link to find the real file and let the client open it,
+as if the user were on a Unix machine. If you don't
+want to allow this, set the <tt class="literal">follow</tt>
+<tt class="literal">symlinks</tt> option like this:</p>
+
+<blockquote><pre class="code">[data]
+    follow symlinks = no</pre></blockquote>
+
+<p>You can test this by setting up and trying to access a symbolic link.
+Create a directory on the Unix server inside the share, acting as the
+user under which you will log in to Samba. Enter the following
+commands:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>echo &quot;This is a test&quot; &gt;hello.txt</b></tt>
+$ <tt class="userinput"><b>ln -s hello.txt hello-link.txt</b></tt></pre></blockquote>
+
+<p>This results in the text file <em class="filename">hello.txt</em> and a
+symbolic link to it called <em class="filename">hello-link.txt</em>.
+Normally, if you double-click either one, you will receive a file
+that has the text &quot;This is a test&quot;
+inside of it. However, with the <tt class="literal">follow</tt>
+<tt class="literal">symlinks</tt><a name="INDEX-15"/> option set to
+<tt class="literal">no</tt>, you will receive an error dialog if you
+double-click <em class="filename">hello-link.txt</em>.</p>
+
+<p>The <tt class="literal">wide</tt><a name="INDEX-16"/> <tt class="literal">links</tt>
+option, if set to <tt class="literal">no</tt>, prevents the client user
+from following symbolic links that point outside the shared directory
+tree. For example, let's assume that we modified the
+<tt class="literal">[data]</tt> share as follows:</p>
+
+<blockquote><pre class="code">[data]
+    follow symlinks = yes
+    wide links = no</pre></blockquote>
+
+<p>As long as the <tt class="literal">follow</tt><a name="INDEX-17"/>
+<tt class="literal">symlinks</tt> option is disabled, Samba will refuse to
+follow any symbolic links outside the current share tree. If we
+create a file outside the share (for example, in
+someone's home directory) and then create a link to
+it in the share as follows:</p>
+
+<blockquote><pre class="code">ln -s ~tom/datafile ./datafile</pre></blockquote>
+
+<p>the client cannot open the file in Tom's home
+directory.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-1.3"/>
+
+<h3 class="head2">Filesystem Options</h3>
+
+<p><a href="ch08.html#samba2-CHP-8-TABLE-1">Table 8-1</a> <a name="INDEX-18"/><a name="INDEX-19"/>shows a breakdown of the options we
+discussed earlier. We recommend the defaults for most, except those
+listed in the following descriptions.</p>
+
+<a name="samba2-CHP-8-TABLE-1"/><h4 class="head4">Table 8-1. Filesystem configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">dont descend</tt></p>
+</td>
+<td>
+<p>string (list of directories)</p>
+</td>
+<td>
+<p>Indicates a list of directories whose contents Samba should make
+invisible to clients.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">follow</tt> <tt class="literal">symlinks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">no</tt>, will not honor symbolic links.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">getwd cache</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, will use a cache for
+<tt class="literal">getwd( )</tt> calls.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">wide links</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, will follow symbolic links outside
+the share.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">hide dot files</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, treats Unix hidden files as hidden
+files in Windows.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">hide files</tt></p>
+</td>
+<td>
+<p>string (list of files)</p>
+</td>
+<td>
+<p>List of file patterns to treat as hidden.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">veto files</tt></p>
+</td>
+<td>
+<p>string (list of files)</p>
+</td>
+<td>
+<p>List of file patterns to never show.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">delete veto</tt> <tt class="literal">files</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, will delete files matched by
+<tt class="literal">veto files</tt> when the directory they reside in is
+deleted.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.1"/>
+
+<h3 class="head3">dont descend</h3>
+
+<p>The <tt class="literal">dont</tt><a name="INDEX-20"/> <tt class="literal">descend</tt>
+option can be used to specify various directories that should appear
+empty to the client. Note that the directory itself will still
+appear. However, Samba will not show any of the contents of the
+directory to the client user. This is not a good option to use as a
+security feature; it is really meant only as a convenience to keep
+users from casually browsing into directories that might have
+sensitive files. See our example earlier in this section.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.2"/>
+
+<a name="INDEX-21"/><h3 class="head3">follow symlinks</h3>
+
+<p>This option controls whether Samba will follow a symbolic link in the
+Unix operating system to the target or if it should return an error
+to the client user. If the option is set to <tt class="literal">yes</tt>,
+the target of the link will be interpreted as the file. If set to
+<tt class="literal">no</tt>, an error will be generated if the symbolic
+link is accessed.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.3"/>
+
+<a name="INDEX-22"/><h3 class="head3">getwd cache</h3>
+
+<p>This global option specifies whether Samba should use a local cache
+for the Unix <em class="emphasis">getwd( )</em> ( get current working
+directory) system call. You can override the default value of
+<tt class="literal">yes</tt> as follows:</p>
+
+<blockquote><pre class="code">[global]
+    getwd cache = no</pre></blockquote>
+
+<p>Setting this option to <tt class="literal">no</tt> can significantly
+increase the time it takes to resolve the working directory,
+especially if the <tt class="literal">wide</tt> <tt class="literal">links</tt>
+option is set to <tt class="literal">no</tt>. You should normally not need
+to alter this option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.4"/>
+
+<a name="INDEX-23"/><h3 class="head3">wide links</h3>
+
+<p>This option specifies whether the client user can follow symbolic
+links that point outside the shared directory tree. This includes any
+files or directories at the other end of the link, as long as the
+permissions are correct for the user. The default value for this
+option is <tt class="literal">yes</tt>. Note that this option will not be
+honored if the <tt class="literal">follow</tt> <tt class="literal">symlinks</tt>
+options is set to <tt class="literal">no</tt>. Setting this option to
+<tt class="literal">no</tt> slows <em class="emphasis">smbd</em> considerably
+because it will have to check each link it encounters.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.5"/>
+
+<h3 class="head3">hide dot files</h3>
+
+<p>The <tt class="literal">hide</tt><a name="INDEX-24"/><a name="INDEX-25"/> <tt class="literal">dot</tt>
+<tt class="literal">files</tt> option hides any files on the server that
+begin with a dot (.) character to mimic the functionality behind
+several shell commands that are present on Unix systems. Like
+<tt class="literal">hide</tt> <tt class="literal">files</tt>, those files that
+begin with a dot have the DOS hidden attribute set, which
+doesn't guarantee that a client cannot view them.
+The default value for this option is <tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.6"/>
+
+<h3 class="head3">hide files</h3>
+
+<p>The <tt class="literal">hide</tt><a name="INDEX-26"/> <tt class="literal">files</tt> option
+provides one or more directory or filename patterns to Samba. Any
+file matching this pattern will be treated as a hidden file from the
+perspective of the client. Note that this simply means that the DOS
+hidden attribute is set, which might or might not mean that the user
+can actually see it while browsing.</p>
+
+<p>Each entry in the list must begin, end, or be separated from another
+entry with a slash (<tt class="literal">/</tt>) character, even if only one
+pattern is listed. This allows spaces to appear in the list.
+Asterisks can be used as a wildcard to represent zero or more
+characters. Questions marks can be used to represent exactly one
+character. For example:</p>
+
+<blockquote><pre class="code">hide files = /.jav*/README.???/</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.7"/>
+
+<a name="INDEX-27"/><h3 class="head3">veto files</h3>
+
+<p>More stringent than the hidden files state is the state provided by
+the <tt class="literal">veto</tt> <tt class="literal">files</tt> configuration
+option. Samba won't even admit these files exist.
+You cannot list or open them from the client. This should not be used
+as a means of implementing security. It is actually a mechanism to
+keep PC programs from deleting special files, such as ones used to
+store the resource fork of a Macintosh file on a Unix filesystem. If
+both Windows and Macs are sharing the same files, this can prevent
+ill-advised power users from removing files the Mac users need.</p>
+
+<p>The syntax of this option is identical to that of the
+<tt class="literal">hide</tt> <tt class="literal">files</tt> configuration
+option: each entry must begin, end, or be separated from another with
+a slash ( / ) character, even if only one pattern is listed.
+Asterisks can be used as a wildcard to represent zero or more
+characters. Question marks can be used to represent exactly one
+character. For example:</p>
+
+<blockquote><pre class="code">veto files = /*config/*default?/</pre></blockquote>
+
+<p>This option is primarily administrative and is not a substitute for
+good file permissions.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-1.3.8"/>
+
+<a name="INDEX-28"/><h3 class="head3">delete veto files</h3>
+
+<p>This option tells Samba to delete vetoed files when a user attempts
+to delete the directory in which they reside. The default value is
+<tt class="literal">no</tt>. This means that if a user tries to delete a
+directory that contains a vetoed file, the file (and the directory)
+will not be deleted. Instead, the directory remains and appears empty
+from the perspective of the user. If set to <tt class="literal">yes</tt>,
+the directory and the vetoed files will be deleted. <a name="INDEX-29"/><a name="INDEX-30"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-2"/>
+
+<h2 class="head1">File Permissions and Attributes on MS-DOS and Unix</h2>
+
+<p><a name="INDEX-31"/><a name="INDEX-32"/><a name="INDEX-33"/>Originally, DOS was not intended to be a
+multiuser, networked operating system. Unix, on the other hand, was
+designed for multiple users from the start. Consequently, Samba must
+not only be aware of, but also provide special solutions for,
+inconsistencies and gaps in coverage between the two filesystems. One
+of the biggest gaps is how Unix and DOS handle permissions on files.</p>
+
+<p>Let's take a look at how Unix assigns permissions.
+All Unix files have read, write, and execute bits for three
+classifications of users: owner, group, and world. These permissions
+can be seen at the extreme lefthand side when an <em class="emphasis">ls
+-al</em> command is issued in a Unix directory. For example:</p>
+
+<blockquote><pre class="code">-rwxr--r--   1 tom     users   2014 Apr 13 14:11 access.conf</pre></blockquote>
+
+<p>Windows, on the other hand, has four principal bits that it uses with
+any file: read-only, system, hidden, and archive. You can view these
+bits by right-clicking the file and choosing the Properties menu
+item. You should see a dialog similar to <a href="ch08.html#samba2-CHP-8-FIG-1">Figure 8-1</a>.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a></p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-1"/><img src="figs/sam2_0801.gif"/></div><h4 class="head4">Figure 8-1. DOS and Windows file properties</h4>
+
+<p>The definition of each bit follows:</p>
+
+<dl>
+<dt><b>Read-only</b></dt>
+<dd>
+<p>The file's contents can be read by a user but cannot
+be written to.</p>
+</dd>
+
+
+
+<dt><b>System</b></dt>
+<dd>
+<p>This file has a specific purpose required by the operating system.</p>
+</dd>
+
+
+
+<dt><b>Hidden</b></dt>
+<dd>
+<p>This file has been marked to be invisible to the user, unless the
+operating system is explicitly set to show it.</p>
+</dd>
+
+
+
+<dt><b>Archive</b></dt>
+<dd>
+<p>This file has been touched since the last DOS backup was performed on
+it.</p>
+</dd>
+
+</dl>
+
+<p>Note that there is no bit to specify that a file is executable. DOS
+and Windows NT filesystems identify executable files by giving them
+the extensions <em class="filename">.exe</em>, <em class="filename">.com</em>,
+<em class="filename">.cmd</em>, or <em class="filename">.bat</em>.</p>
+
+<p>Consequently, there is no use for any of the three Unix executable
+bits that are present on a file in a Samba disk share. DOS files,
+however, have their own attributes that need to be preserved when
+they are stored in a Unix environment: the archive, system, and
+hidden bits. Samba can preserve these bits by reusing the executable
+permission bits of the file on the Unix side&mdash;if it is
+instructed to do so. Mapping these bits, however, has an unfortunate
+side effect: if a Windows user stores a file in a Samba share, and
+you view it on Unix with the <em class="emphasis">ls -al</em> command,
+some of the executable bits won't mean what
+you'd expect them to.</p>
+
+<p>Three Samba options decide whether the bits are mapped:
+<tt class="literal">map</tt><a name="INDEX-34"/> <tt class="literal">archive</tt>,
+<tt class="literal">map</tt><a name="INDEX-35"/> <tt class="literal">system</tt> , and
+<tt class="literal">map</tt><a name="INDEX-36"/> <tt class="literal">hidden</tt>. These options
+map the archive, system, and hidden attributes to the owner, group,
+and world execute bits of the file, respectively. You can add these
+options to the <tt class="literal">[data]</tt> share, setting each of their
+values as follows:</p>
+
+<blockquote><pre class="code">[data]
+    map archive = yes
+    map system = yes
+    map hidden = yes</pre></blockquote>
+
+<p>After that, try creating a file in the share under Unix&mdash;such as
+<em class="emphasis">hello.java</em>&mdash;and change the permissions of
+the file to 755. With these Samba options set, you should be able to
+check the permissions on the Windows side and see that each of the
+three values has been checked in the Properties dialog box. What
+about the read-only attribute? By default, Samba sets this whenever a
+file does not have the Unix owner write permission bit set. In other
+words, you can set this bit by changing the permissions of the file
+to 555.</p>
+
+<p>The default value of the <tt class="literal">map</tt>
+<tt class="literal">archive</tt> option is <tt class="literal">yes</tt>, while
+the other two options have a default value of <tt class="literal">no</tt>.
+This is because many programs do not work properly if the archive bit
+is not stored correctly for DOS and Windows files. The system and
+hidden attributes, however, are not critical for a
+program's operation and are left to the discretion
+of the administrator.</p>
+
+<p><a href="ch08.html#samba2-CHP-8-FIG-2">Figure 8-2</a> summarizes the <a name="INDEX-37"/><a name="INDEX-38"/>Unix permission bits and
+illustrates how Samba maps those bits to DOS attributes. Note that
+the group read/write and world read/write bits do not directly
+translate to a DOS attribute, but they still retain their original
+Unix definitions on the Samba server.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-2"/><img src="figs/sam2_0802.gif"/></div><h4 class="head4">Figure 8-2. How Samba and Unix view the permissions of a file</h4>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-2.1"/>
+
+<h3 class="head2">Creation Masks</h3>
+
+<p><a name="INDEX-39"/>File and directory creation masks are
+similar to <a name="INDEX-40"/>umasks you
+have probably encountered while working with Unix systems. They are
+used to help define the permissions that will be assigned to a file
+or directory at the time it is created. Samba's
+masks work differently in that the bits that can be set are set in
+the creation mask, while in Unix umasks, the bits
+<em class="emphasis">cannot</em> be set are set in the umask. We think you
+will find Samba's method to be much more intuitive.
+Once in a while you might need to convert between a Unix umask and
+the equivalent Samba mask. It is simple: one is just the bitwise
+complement of the other. For example, an octal umask of 0022 has the
+same effect as a Samba mask of 0755.</p>
+
+<p>Unix umasks are set on a user-by-user basis, usually while executing
+the GUI's or command-line shell's
+startup scripts. When users connect to a Samba share from a network
+client, these scripts are not executed, so Samba supplies the ability
+to set the creation masks for files and directories. By default, this
+is done on a share-by-share basis, although you can use the
+<tt class="literal">include</tt> parameter in the Samba configuration file
+(as explained in <a href="ch06.html">Chapter 6</a>) to assign masks on a
+user-by-user basis, thus matching conventional Unix behavior.</p>
+
+<p>To show how Samba's create masks work, suppose we
+have a Windows Me user connecting to his Unix home directory through
+Samba, and Samba is configured with <tt class="literal">create</tt>
+<tt class="literal">mask</tt> <tt class="literal">=</tt> <tt class="literal">777</tt>
+in the <tt class="literal">[homes]</tt> share. With this value,
+<tt class="literal">create</tt> <tt class="literal">mask</tt> will not affect the
+bits that are set on new files. If the user creates a file with
+Wordpad, it will appear in the Unix filesystem like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l file.doc</b></tt>
+-rwxrw-rw-    1 jay      jay             0 Sep 21 11:02 file.doc</pre></blockquote>
+
+<p>Wordpad created the file with read/write permissions (i.e., the
+MS-DOS read-only attribute was not set), so Samba mapped the MS-DOS
+attributes to Unix read/write permissions for user, group, and other.
+The <a name="INDEX-41"/><a name="INDEX-42"/>execute bit is set for the owner
+because by default, the <tt class="literal">map</tt>
+<tt class="literal">archive</tt> parameter is set to
+<tt class="literal">yes</tt>. The other execute bits are not set because
+<tt class="literal">map</tt> <tt class="literal">system</tt> and
+<tt class="literal">map</tt> <tt class="literal">hidden</tt> are set to
+<tt class="literal">no</tt> by default. You can customize this behavior as
+you see fit, and unless you do backups from MS-DOS or Windows
+systems, you might want to specify <tt class="literal">map</tt>
+<tt class="literal">archive</tt> <tt class="literal">=</tt> <tt class="literal">no</tt>
+to avoid Windows files from appearing as executables on the Unix
+system.</p>
+
+<p>Now suppose we set
+<tt class="literal">create</tt><a name="INDEX-43"/> <tt class="literal">mask</tt> to have
+an effect. For example:</p>
+
+<blockquote><pre class="code">[homes]
+    create mask = 664</pre></blockquote>
+
+<p>This is equivalent to a Unix umask of 113. If the user creates the
+Wordpad document as before, it will show up as:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l file.doc</b></tt>
+-rw-rw-r--    1 jay      jay             0 Sep 22 16:38 file.doc</pre></blockquote>
+
+<p>Comparing this to the previous example, notice that not only has the
+write permission for other disappeared as we expected, but so has the
+execute permission for owner. This happened because the value of
+<tt class="literal">create</tt> <tt class="literal">mask</tt> logically ANDs the
+owner's permissions with a 6, which has masked off
+the execute bit. The lesson here is that if you want to enable any of
+<tt class="literal">map</tt> <tt class="literal">archive</tt>,
+<tt class="literal">map</tt> <tt class="literal">system</tt>, or
+<tt class="literal">map</tt> <tt class="literal">hidden</tt>, you must be careful
+not to mask off the corresponding execute bit with your
+<tt class="literal">create</tt> <tt class="literal">mask</tt>.</p>
+
+<p>The <tt class="literal">directory</tt><a name="INDEX-44"/> <tt class="literal">mask</tt>
+option works similarly, masking permissions for newly created
+directories. The following example will allow the permissions of a
+newly created directory to be, at most, 755:</p>
+
+<blockquote><pre class="code">[data]
+    directory mask = 755</pre></blockquote>
+
+<p>Also, you can force various bits with the <tt class="literal">force</tt>
+<tt class="literal">create</tt> <tt class="literal">mode</tt> and
+<tt class="literal">force</tt> <tt class="literal">directory</tt>
+<tt class="literal">mode</tt> options. These options will perform a logical
+OR against the file and directory creation masks, ensuring that those
+bits that are specified will always be set. You would typically set
+these options globally to ensure that group and world read/write
+permissions have been set appropriately for new files or directories
+in each share.</p>
+
+<p>In the same spirit, if you wish to set explicitly the Unix user and
+group attributes of a file created on the Windows side, you can use
+the <tt class="literal">force</tt><a name="INDEX-45"/> <tt class="literal">user</tt> and
+<tt class="literal">force</tt><a name="INDEX-46"/> <tt class="literal">group</tt>
+options. For example:</p>
+
+<blockquote><pre class="code">[data]
+    create mask = 744
+    directory mask = 755
+    force user = joe
+    force group = accounting</pre></blockquote>
+
+<p>These options assign the same Unix username and group to every client
+that connects to the share. However, this occurs
+<em class="emphasis">after</em> the client authenticates; it does not
+allow free access to a share. These options are frequently used for
+their side effects of assigning a specific user and group to each new
+file or directory that is created in a share. Use these options with
+discretion.</p>
+
+<p>Finally, one of the capabilities of Unix that DOS lacks is the
+ability to delete a read-only file from a writable directory. In
+Unix, if a directory is writable, a read-only file in that directory
+can still be removed. This could permit you to delete files in any of
+your directories, even if the file was left by someone else.</p>
+
+<p>DOS filesystems are not designed for multiple users, and so its
+designers decided that read-only means &quot;protected
+against accidental change, including deletion,&quot;
+rather than &quot;protected against some other user on a
+single-user machine.&quot; So the designers of DOS
+prohibited removal of a read-only file. Even today, Windows
+filesystems exhibit the same behavior.</p>
+
+<p>Normally, this is harmless. Windows programs don't
+try to remove read-only files because they know it's
+a bad idea. However, a number of source-code control
+programs&mdash;which were first written for Unix&mdash;run on Windows
+and require the ability to delete read-only files. Samba permits this
+behavior with the <tt class="literal">delete</tt><a name="INDEX-47"/>
+<tt class="literal">readonly</tt> option. To enable this functionality, set
+the option to <tt class="literal">yes</tt>:</p>
+
+<a name="INDEX-48"/><blockquote><pre class="code">[data]
+    delete readonly = yes</pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-2.2"/>
+
+<h3 class="head2">File and Directory Permission Options</h3>
+
+<p><a name="INDEX-49"/><a name="INDEX-50"/><a name="INDEX-51"/>The
+options for file and directory permissions are summarized in <a href="ch08.html#samba2-CHP-8-TABLE-2">Table 8-2</a>; each option is then described in detail.</p>
+
+<a name="samba2-CHP-8-TABLE-2"/><h4 class="head4">Table 8-2. File and directory permission options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">create mask</tt> <tt class="literal">(create mode)</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum permissions for files created by Samba.</p>
+</td>
+<td>
+<p><tt class="literal">0744</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">directory mask</tt> <tt class="literal">(directory mode)</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum permissions for directories created by Samba.</p>
+</td>
+<td>
+<p><tt class="literal">0744</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force create mode</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Forces the specified permissions (bitwise <tt class="literal">or</tt>) for
+directories created by Samba.</p>
+</td>
+<td>
+<p><tt class="literal">0000</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force directory</tt> <tt class="literal">mode</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Forces the specified permissions (bitwise <tt class="literal">or</tt>) for
+directories created by Samba.</p>
+</td>
+<td>
+<p><tt class="literal">0000</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force group</tt> <tt class="literal">(group)</tt></p>
+</td>
+<td>
+<p>string ( group name)</p>
+</td>
+<td>
+<p>Effective group for a user accessing this share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force user</tt></p>
+</td>
+<td>
+<p>string (username)</p>
+</td>
+<td>
+<p>Effective username for a user accessing this share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">delete readonly</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Allows a user to delete a read-only file from a writable directory.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">map archive</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Preserve DOS archive attribute in user execute bit (0100).</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">map system</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Preserve DOS system attribute in group execute bit (0010).</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">map hidden</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Preserve DOS hidden attribute in world execute bit (0001).</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">inherit permissions</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, permissions on new files and directories
+are inherited from parent directory.</p>
+</td>
+<td>
+<p>no</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.1"/>
+
+<a name="INDEX-52"/><h3 class="head3">create mask</h3>
+
+<p>The argument for this option is an octal number indicating which
+permission flags can be set at file creation by a client in a share.
+The default is 0744, which means that the Unix owner can at most
+read, write, and optionally execute her own files, while members of
+the user's group and others can only read or execute
+them. If you need to change it for nonexecutable files, we recommend
+0644, or <tt class="literal">rw-r--r--</tt>. Keep in mind that the execute
+bits can be used by the server to map certain DOS file attributes, as
+described earlier. If you're altering the create
+mask, those bits have to be part of the create mask as well.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.2"/>
+
+<a name="INDEX-53"/><h3 class="head3">directory mask</h3>
+
+<p>The argument for this option is an octal number indicating which
+permission flags can be set at directory creation by a client in a
+share. The default is 0744, which allows everyone on the Unix side
+to, at most, read and traverse the directories, but allows only you
+to modify them. We recommend the mask 0750, removing access by
+&quot;the world.&quot;</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.3"/>
+
+<a name="INDEX-54"/><h3 class="head3">force create mode</h3>
+
+<p>This option sets the permission bits that Samba will set when a file
+permission change is made. It's often used to force
+group permissions, as mentioned previously. It can also be used to
+preset any of the DOS attributes we mentioned: archive (0100), system
+(0010), or hidden (0001).</p>
+
+<a name="samba2-CHP-8-NOTE-139"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p><a name="INDEX-55"/>When saving
+documents, many Windows applications rename their datafiles with a
+<em class="filename">.bak</em> extension and create new ones. When the
+files are in a Samba share, this changes their ownership and
+permissions so that members of the same Unix group
+can't edit them. Setting <tt class="literal">force</tt>
+<tt class="literal">create mode = 0660</tt> will keep the new file editable
+by members of the group.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.4"/>
+
+<a name="INDEX-56"/><h3 class="head3">force directory mode</h3>
+
+<p>This option sets the permission bits that Samba will set when a
+directory permission change is made or a directory is created.
+It's often used to force group permissions, as
+mentioned previously. This option defaults to 0000 and can be used
+just like the <tt class="literal">force</tt> <tt class="literal">create</tt>
+<tt class="literal">mode</tt> to add group or other permissions if needed.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.5"/>
+
+<a name="INDEX-57"/><h3 class="head3">force group</h3>
+
+<p>This option, sometimes called <tt class="literal">group</tt>, assigns a
+static group ID that will be used on all connections to a share after
+the client has successfully authenticated. This assigns a specific
+group to each new file or directory created from an SMB client.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.6"/>
+
+<h3 class="head3">force user</h3>
+
+<p>The <tt class="literal">force</tt><a name="INDEX-58"/> <tt class="literal">user</tt> option
+assigns a static user ID that will be used on all connections to a
+share after the client has successfully authenticated. This assigns a
+specific user to each new file or directory created from an SMB
+client.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.7"/>
+
+<a name="INDEX-59"/><h3 class="head3">delete readonly</h3>
+
+<p>This option allows a user to delete a directory containing a
+read-only file. By default, DOS and Windows will not allow such an
+operation. You probably will want to leave this option turned off
+unless a program (for example, an RCS program) needs this capability;
+many Windows users would be appalled to find that
+they'd accidentally deleted a file that they had set
+as read-only.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.8"/>
+
+<a name="INDEX-60"/><h3 class="head3">map archive</h3>
+
+<p>The DOS archive bit is used to flag a file that has been changed
+since it was last archived (e.g., backed up with the DOS archive
+program). Setting the Samba option <tt class="literal">map</tt>
+<tt class="literal">archive</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> maps the DOS archive flag to the Unix
+execute-by-owner (0100) bit. It's best to leave this
+option on if your Windows users are doing their own backups or are
+using programs that require the archive bit. Unix lacks the notion of
+an archive bit entirely. Backup programs typically keep a file that
+lists what files were backed up on what date, so comparing
+file-modification dates serves the same purpose.</p>
+
+<p>Setting this option to <tt class="literal">yes</tt> causes an occasional
+surprise on Unix when a user notices that a datafile is marked as
+executable, but rarely causes harm. If a user tries to run it, he
+will normally get a string of error messages as the shell tries to
+execute the first few lines as commands. The reverse is also
+possible; an executable Unix program looks like it
+hasn't been backed up recently on Windows. But
+again, this is rare and usually harmless.</p>
+
+<p>For map archive to work properly, the execute bit for owner must not
+be masked off with the <tt class="literal">create</tt>
+<tt class="literal">mask</tt> parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.9"/>
+
+<a name="INDEX-61"/><h3 class="head3">map system</h3>
+
+<p>The DOS system attribute indicates files that are required by the
+operating system and should not be deleted, renamed, or moved without
+special effort. Set this option only if you need to store Windows
+system files on the Unix fileserver. Executable Unix programs will
+appear to be nonremovable, special Windows files when viewed from
+Windows clients. This might prove mildly inconvenient if you want to
+move or remove one. For most sites, however, this is fairly harmless.</p>
+
+<p>For map archive to work properly, the execute bit for group must not
+be masked off with the <tt class="literal">create</tt>
+<tt class="literal">mask</tt> parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.10"/>
+
+<a name="INDEX-62"/><h3 class="head3">map hidden</h3>
+
+<p>DOS uses the hidden attribute to indicate that a file should not
+ordinarily be visible in directory listings. Unix
+doesn't have such a facility; it's
+up to individual programs (notably, the shell) to decide what to
+display and what not to display. Normally, you won't
+have any DOS files that need to be hidden, so the best thing to do is
+to leave this option turned off.</p>
+
+<p>Setting this option to <tt class="literal">yes</tt> causes the server to
+map the hidden flag onto the executable-by-others bit (0001). This
+feature can produce a rather startling effect. Any Unix program that
+is executable by world seems to vanish when you look for it from a
+Windows client. If this option is not set, however, and a Windows
+user attempts to mark a file hidden on a Samba share, it will not
+work&mdash;Samba has no place to store the hidden attribute!</p>
+
+<p>For map archive to work properly, the execute bit for other must not
+be masked off with the <tt class="literal">create</tt>
+<tt class="literal">mask</tt> parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-2.2.11"/>
+
+<h3 class="head3">inherit permissions</h3>
+
+<p>When the <tt class="literal">inherit</tt><a name="INDEX-63"/>
+<tt class="literal">permissions</tt> option is set to
+<tt class="literal">yes</tt>, the <tt class="literal">create</tt>
+<tt class="literal">mask</tt>, <tt class="literal">directory</tt>
+<tt class="literal">mask</tt>, <tt class="literal">force</tt>
+<tt class="literal">create</tt> <tt class="literal">mode</tt>, and
+<tt class="literal">force</tt> <tt class="literal">directory</tt>
+<tt class="literal">mode</tt> are ignored. The normal behavior of setting
+the permissions on newly created files is overridden such that the
+new files and directories take on permissions from their parent
+directory. New directories will have exactly the same permissions as
+the parent, and new files will inherit the read and write bits from
+the parent directory, while the execute bits are determined as usual
+by the values of the <tt class="literal">map</tt>
+<tt class="literal">archive</tt>, <tt class="literal">map</tt>
+<tt class="literal">hidden</tt>, and <tt class="literal">map</tt>
+<tt class="literal">system</tt> parameters.</p>
+
+<p>By default, this option is set to <tt class="literal">no</tt>. <a name="INDEX-64"/><a name="INDEX-65"/><a name="INDEX-66"/> <a name="INDEX-67"/><a name="INDEX-68"/><a name="INDEX-69"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-3"/>
+
+<h2 class="head1">Windows NT/2000/XP ACLs</h2>
+
+<p><a name="INDEX-70"/><a name="INDEX-71"/><a name="INDEX-72"/><a name="INDEX-73"/>Unix and Windows
+have different <a name="INDEX-74"/>security models, and Windows NT/2000/XP
+has a security model that is different from Windows 95/98/Me. One
+area in which this is readily apparent is file protections. On Unix
+systems, the method used has traditionally been the 9-bit
+&quot;user, group, other&quot; system, in
+which read, write, and execute bits can be set separately for the
+owner of the file, the groups to which the owner belongs, and
+everyone else, respectively.</p>
+
+<p><a name="INDEX-75"/>Windows 95/98/Me has a file-protection
+system that is essentially no protection at all. This family of
+operating systems was developed from MS-DOS, which was implemented as
+a non-networked, single-user system. Multiuser security simply was
+never added. One apparent exception to this is user-level security
+for shared files, which we will discuss in <a href="ch09.html">Chapter 9</a>. Here, separate access permissions can be
+assigned to individual network client users or groups. However,
+user-level security on Windows 95/98/Me systems requires a Windows
+NT/2000 or Samba server to perform the actual authentication.</p>
+
+<p>On <a name="INDEX-76"/><a name="INDEX-77"/><a name="INDEX-78"/>Windows NT/2000/XP,
+user-level security is an extension of the native file security
+model, which involves access control lists (ACLs). This system is
+somewhat more extensive than the Unix security model, allowing the
+access rights on individual files to be set separately for any number
+of individual users and/or any number of arbitrary groups of users.
+<a href="ch08.html#samba2-CHP-8-FIG-3">Figure 8-3</a>, <a href="ch08.html#samba2-CHP-8-FIG-4">Figure 8-4</a>,
+and <a href="ch08.html#samba2-CHP-8-FIG-5">Figure 8-5</a> show the dialog boxes on a Windows
+2000 system in which the ACL is set for a file. By right-clicking a
+file's icon and selecting Properties, then selecting
+the Security tab, we get to the dialog box shown in <a href="ch08.html#samba2-CHP-8-FIG-3">Figure 8-3</a>. Here, we can set the basic permissions for a
+file, which are similar to Unix permissions, although not identical.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-3"/><img src="figs/sam2_0803.gif"/></div><h4 class="head4">Figure 8-3. The Security tab of the file Properties dialog</h4>
+
+<p>By clicking the Advanced tab, we can bring up the dialog box shown in
+<a href="ch08.html#samba2-CHP-8-FIG-4">Figure 8-4</a>, which shows the list of
+<a name="INDEX-79"/>access control entries (ACEs) in the ACL.
+In this dialog, ACEs can be added to or deleted from the ACL, or an
+existing ACE can be viewed and modified. Each ACE either allows or
+denies a set of permissions for a specific user or group.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-4"/><img src="figs/sam2_0804.gif"/></div><h4 class="head4">Figure 8-4. The Permissions tab of the Access Control Settings dialog</h4>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-5"/><img src="figs/sam2_0805.gif"/></div><h4 class="head4">Figure 8-5. Permission Entry dialog, showing the settings of an ACE</h4>
+
+<p><a href="ch08.html#samba2-CHP-8-FIG-5">Figure 8-5</a> shows the dialog box for adding an ACE.
+As you can see, there are more options for permissions in an ACL than
+with the permission bits on typical Unix systems. You can learn more
+about these settings in <em class="citetitle">Essential Windows NT System
+Administration</em>, published by O'Reilly.</p>
+
+<p>In a networked environment where a Samba server is serving files to
+Windows NT/2000/XP clients, Samba has to map Unix permissions for
+files and directories to Windows NT/2000/XP access control lists.
+When a Windows NT/2000/XP client accesses a shared file or directory
+on a Samba server, Samba translates the object's
+ownership, group, and permissions into an ACL and returns them to the
+client.</p>
+
+<p><a href="ch08.html#samba2-CHP-8-FIG-6">Figure 8-6</a> shows the Properties dialog box for the
+file <em class="filename">shopping_list.doc</em> that resides on the Samba
+server.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-6"/><img src="figs/sam2_0806.gif"/></div><h4 class="head4">Figure 8-6. The Properties dialog for a file on the Samba server</h4>
+
+<p>From Unix, this file appears as:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l shopping_list.doc</b></tt>
+-rw-------    1 adilia   users          49 Mar 29 11:58 shopping_list.doc</pre></blockquote>
+
+<p>Notice that because the file has read permissions for the owner, the
+Read-only checkbox will show as cleared, even though the user on the
+Windows client (who is not <tt class="literal">adilia</tt> in this example)
+does not have read access permissions. The checkboxes here show only
+DOS attributes. By clicking the Security tab, we can start to examine
+the ACLs, as shown in <a href="ch08.html#samba2-CHP-8-FIG-7">Figure 8-7</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-7"/><img src="figs/sam2_0807.gif"/></div><h4 class="head4">Figure 8-7. The Security tab of the Properties dialog for a file on the Samba server</h4>
+
+<p>The owner of the file (<tt class="literal">adilia</tt>) is shown as one
+entry, while the group (<tt class="literal">users</tt>) and other
+permissions are presented as the groups called
+<tt class="literal">users</tt> and <tt class="literal">Everyone</tt>. Clicking
+one of the items in the upper windows causes the simplified view of
+the permissions in that item to appear in the bottom window. Here,
+the read/write permissions for <tt class="literal">adilia</tt> appear in a
+manner that makes the security model of Unix and Windows seem
+similar. However, clicking the Advanced . . . button brings up the
+additional dialog box shown in <a href="ch08.html#samba2-CHP-8-FIG-8">Figure 8-8</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-8"/><img src="figs/sam2_0808.gif"/></div><h4 class="head4">Figure 8-8. The Access Control Settings dialog for a file on the Samba server</h4>
+
+<p>In this dialog box, we see the actual ACL of the file. The ACEs for
+<tt class="literal">users</tt> and <tt class="literal">Everyone</tt> are listed
+with Take Ownership in the Permission column. This is a trick used by
+Samba for ACLs that have no permissions on the Unix side. On Windows,
+an ACL with nothing set results in no ACL at all, so Samba sets the
+Take Ownership permission to make sure that all the ACLs
+corresponding to the Unix &quot;user, group,
+other&quot; permissions will show up on Windows. The Take
+Ownership permission has no corresponding Unix attribute, so the
+setting on Windows does not affect the actual file on the Unix system
+in any way. Although Windows client users might be misled into
+thinking they can take ownership of the file (that is, change the
+ownership of the file to themselves), an actual attempt to do so will
+fail.</p>
+
+<p>The Permissions column for the <tt class="literal">adilia</tt> ACL is
+listed as Special because Samba reports permissions for the file that
+do not correspond to settings for which Windows has a more
+descriptive name. Clicking the entry and then clicking the View/Edit
+. . . button brings up the dialog box shown in <a href="ch08.html#samba2-CHP-8-FIG-9">Figure 8-9</a>, in which the details of the ACL permissions
+can be viewed and perhaps modified.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-9"/><img src="figs/sam2_0809.gif"/></div><h4 class="head4">Figure 8-9. Permission Entry dialog for a file served by Samba</h4>
+
+<p>We say &quot;perhaps&quot; here because
+checking or unchecking boxes in this dialog box might not result in
+settings that Samba is able to map back into the Unix security model.
+When a user attempts to modify a setting (either permissions or
+ownership) that she does not have authority to change, or does not
+correspond to a valid setting on the Unix system, Samba will respond
+with an error dialog or by quietly ignoring the unmappable settings.</p>
+
+<p>The ACLs for a directory are slightly different. <a href="ch08.html#samba2-CHP-8-FIG-10">Figure 8-10</a> shows the ACL view after clicking the Advanced
+button.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-10"/><img src="figs/sam2_0810.gif"/></div><h4 class="head4">Figure 8-10. The Access Control Settings dialog for a directory on the Samba server</h4>
+
+<p>Here, there are two ACLs each for <tt class="literal">users</tt> and
+<tt class="literal">Everyone</tt>. One ACL specifies the permissions for
+the directory itself, and the other specifies permissions for the
+directory's contents. When changing settings in the
+View/Edit... dialog, there is an extra drop-down menu to apply the
+settings either to just the directory or to some combination of the
+directory and the files and directories it contains. If settings are
+applied to more than just the directory, Samba will match the
+behavior of a Windows server and change the permissions on the
+contents of the directory, as specified in the dialog.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-3.1"/>
+
+<h3 class="head2">Unix ACLs</h3>
+
+<p><a name="INDEX-80"/><a name="INDEX-81"/>In
+most cases, users of Windows clients will find the Unix security
+model to be sufficient. However, in some cases, people might want the
+Samba server to support the full Windows ACL security model. Even if
+they don't need the fine-grained control over file
+and directory permissions, they might find Samba's
+translation between ACLs and Unix permissions to be a source of
+confusion or frustration.</p>
+
+<p>When the underlying Unix host operating system supports
+<a name="INDEX-82"/><a name="INDEX-83"/>POSIX.1e ACLs, Samba provides much better
+support of Windows NT/2000/XP ACLs. Versions of Unix that offer the
+necessary support include the following:</p>
+
+<ul><li>
+<p>Solaris 2.6 and later</p>
+</li><li>
+<p>SGI Irix</p>
+</li><li>
+<p>Linux, with Andreas Gr&uuml;nbacher's kernel
+patch from <a href="http://acl.bestbits.at">http://acl.bestbits.at</a>
+that adds ACL support to the Linux ext2 and ext3 filesystems</p>
+</li><li>
+<p>Linux, with the XFS filesystem</p>
+</li><li>
+<p>AIX</p>
+</li><li>
+<p>FreeBSD 5.0 and later</p>
+</li><li>
+<p>HP/UX 11.0 and later, with the JFS 3.3 filesystem layout Version 4</p>
+</li></ul>
+<p>If you are fortunate enough to have a Unix host operating system with
+ACL support already provided, all you need to do is recompile Samba
+using the <tt class="literal">--with-acl-support</tt> configure option, as
+we described in <a href="ch02.html">Chapter 2</a>. If you are running
+Linux and need to patch your kernel, things are much more
+complicated. We suggest you refer to the documentation that comes
+with the patch for details on using it.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-3.2"/>
+
+<h3 class="head2">Configuration Options for ACLs</h3>
+
+<p><a href="ch08.html#samba2-CHP-8-TABLE-3">Table 8-3</a> <a name="INDEX-84"/><a name="INDEX-85"/>shows the Samba configuration options
+for working with Windows NT/2000/XP access control lists.</p>
+
+<a name="samba2-CHP-8-TABLE-3"/><h4 class="head4">Table 8-3. ACL configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">nt acl support</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows users on Windows NT/2000/XP clients
+to modify ACL settings</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">security mask</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Bitmask that allows or denies permission settings on files</p>
+</td>
+<td>
+<p><tt class="literal">0777</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force security</tt> <tt class="literal">mode</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Bits that are always set when modifying file permissions</p>
+</td>
+<td>
+<p><tt class="literal">0000</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">directory</tt> <tt class="literal">security mask</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Bitmask that allows or denies permission settings on directories</p>
+</td>
+<td>
+<p><tt class="literal">0777</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">force directory</tt> <tt class="literal">security mode</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Bits that are always set when modifying directory permissions</p>
+</td>
+<td>
+<p><tt class="literal">0000</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-3.2.1"/>
+
+<a name="INDEX-86"/><h3 class="head3">nt acl support</h3>
+
+<p>This parameter defaults to <tt class="literal">yes</tt>, which allows users
+on Windows NT/2000/XP clients to modify ACL settings for files on the
+Samba server. When set to <tt class="literal">no</tt>, files show up as
+owned by <tt class="literal">Everyone</tt>, with permissions appearing as
+&quot;Full Control&quot;. However,
+<em class="emphasis">actual</em> ownership and permissions are enforced as
+whatever they are set to on the Samba server, and the user on the
+Windows client cannot view or modify them with the dialog boxes used
+for managing ACLs.</p>
+
+<p>When enabled, support for Windows NT/2000/XP ACLs is limited to
+whatever ownerships and permissions can map into valid users and
+permissions on the Samba server. If the server supports ACLs (either
+&quot;out of the box&quot; or with an
+additional patch to enhance the filesystem), Samba's
+ACL support more closely matches that of a Windows NT/2000/XP server.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-3.2.2"/>
+
+<h3 class="head3">security mask</h3>
+
+<p>Using the <tt class="literal">security</tt><a name="INDEX-87"/>
+<tt class="literal">mask</tt> option, it is possible to define which file
+permissions users can modify from Windows NT/2000/XP clients. This is
+for files only and not directories, which are handled with the
+<tt class="literal">directory</tt><a name="INDEX-88"/>
+<tt class="literal">security</tt> <tt class="literal">mask</tt> option. The
+parameter is assigned a numeric value that is a Unix-style
+permissions mask. For bits in the mask that are set, the client can
+modify the corresponding bits in the files'
+permissions. If the bit is zero, the client cannot modify that
+permission. For example, if <tt class="literal">security</tt>
+<tt class="literal">mask</tt> is set as:</p>
+
+<blockquote><pre class="code">[data]
+    security mask = 0777</pre></blockquote>
+
+<p>the client can modify all the user/group/other permissions for the
+files in the share. This is the default. A value of
+<tt class="literal">0</tt> would deny clients from changing any of the
+permissions, and setting <tt class="literal">security</tt>
+<tt class="literal">mask</tt> as:</p>
+
+<blockquote><pre class="code">[data]
+    security mask = 0666</pre></blockquote>
+
+<p>would allow client users to modify the read and write permissions,
+but not the execute permissions.</p>
+
+<p>Do not count on <tt class="literal">security</tt> <tt class="literal">mask</tt>
+for complete control because if the user can access the files on the
+Samba server through any other means (for example, by logging
+directly into the Unix host), he can modify the permissions using
+that method.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-3.2.3"/>
+
+<h3 class="head3">force security mode</h3>
+
+<p>The <tt class="literal">force</tt><a name="INDEX-89"/>
+<tt class="literal">security</tt> <tt class="literal">mode</tt> option can be
+used to define a set of permissions that are always set whenever the
+user on a Windows NT/2000/XP client modifies a
+file's permissions. (See the
+<tt class="literal">force</tt> <tt class="literal">directory</tt>
+<tt class="literal">security</tt> <tt class="literal">mode</tt> option for
+handling directories.)</p>
+
+<p>Be careful to understand this properly. The mask given as the
+parameter's value is not necessarily equal to the
+resulting permissions on the file. The permissions that the client
+user attempts to modify are logically OR'd with the
+<tt class="literal">force</tt> <tt class="literal">security</tt>
+<tt class="literal">mode</tt> <tt class="literal">mask</tt> option, and any bits
+that are turned on will cause the file's
+corresponding permissions to be set. As an example, suppose
+<tt class="literal">force</tt> <tt class="literal">security</tt>
+<tt class="literal">mode</tt> is set in a share thusly:</p>
+
+<blockquote><pre class="code">[data]
+    force security mode = 0440</pre></blockquote>
+
+<p>(This sets the read bit for owner and group, but not other.) If a
+user on a Windows NT/2000/XP client modifies an ACL on a file in the
+<tt class="literal">[data]</tt> share and attempts to remove all read
+permissions, the read permission for other
+(<tt class="literal">Everyone</tt>) will be removed, but the read
+permission for the owner and group will remain. Note that this
+parameter cannot force a permission bit to be turned off.</p>
+
+<p>As with the <tt class="literal">security</tt> <tt class="literal">mask</tt>
+option, if a user can access the files in the share through any means
+other than Samba, she can easily work around Samba's
+enforcement of this parameter.</p>
+
+<p>The default value of <tt class="literal">force</tt>
+<tt class="literal">security</tt> <tt class="literal">mode</tt> is
+<tt class="literal">0000</tt>, which allows users to remove any permission
+from files.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-3.2.4"/>
+
+<a name="INDEX-90"/><h3 class="head3">directory security mask</h3>
+
+<p>This option works exactly the same as the <tt class="literal">security</tt>
+<tt class="literal">mask</tt> option, except that it operates on
+directories rather than files. As with <tt class="literal">security</tt>
+<tt class="literal">mask</tt>, it has a default value of
+<tt class="literal">0777</tt>, which allows Windows NT/2000/XP client users
+to modify all Unix permissions on directories in the share.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-3.2.5"/>
+
+<a name="INDEX-91"/><h3 class="head3">force directory security mode</h3>
+
+<p>This option works exactly the same as the <tt class="literal">force</tt>
+<tt class="literal">security</tt> <tt class="literal">mode</tt> option, except
+that it operates on directories rather than files. It also has a
+default value of <tt class="literal">0000</tt>, which allows Windows
+NT/2000/XP client users to remove any permissions from directories in
+the share. <a name="INDEX-92"/><a name="INDEX-93"/><a name="INDEX-94"/><a name="INDEX-95"/> <a name="INDEX-96"/><a name="INDEX-97"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-4"/>
+
+<h2 class="head1">Name Mangling and Case</h2>
+
+<p><a name="INDEX-98"/><a name="INDEX-99"/><a name="INDEX-100"/><a name="INDEX-101"/>Back
+in the days of DOS and Windows 3.1, every filename was limited to
+eight uppercase characters, followed by a dot, and three more
+uppercase characters. This was known as the <em class="firstterm">8.3
+format</em> and was a huge nuisance. Windows 95/98/Me, Windows
+NT/2000/XP, and Unix have since relaxed this problem by allowing
+longer, sometimes case-sensitive, filenames. <a href="ch08.html#samba2-CHP-8-TABLE-4">Table 8-4</a> shows the current naming state of several
+popular operating systems.</p>
+
+<a name="samba2-CHP-8-TABLE-4"/><h4 class="head4">Table 8-4. Operating system filename limitations</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Operating system</p>
+</th>
+<th>
+<p>File-naming rules</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>DOS 6.22 or below</p>
+</td>
+<td>
+<p>Eight characters followed by a dot followed by a three-letter
+extension (8.3 format); case-insensitive</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 3.1 for Workgroups</p>
+</td>
+<td>
+<p>Eight characters followed by a dot followed by a three-letter
+extension (8.3 format); case-insensitive</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95/98/Me</p>
+</td>
+<td>
+<p>255 characters; case-insensitive but case-preserving</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT/2000/XP</p>
+</td>
+<td>
+<p>255 characters; case-insensitive but case-preserving</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Unix</p>
+</td>
+<td>
+<p>255 characters; case-sensitive</p>
+</td>
+</tr>
+
+</table>
+
+<p>Samba still has to remain backward-compatible with network clients
+that store files in just the 8.3 format, such as Windows for
+Workgroups. If a user creates a file on a share called
+<em class="emphasis">antidisestablishmentarianism.txt</em>, a Windows for
+Workgroups client cannot tell it apart from another file in the same
+directory called <em class="emphasis">antidisease.txt</em>. Like Windows
+95/98/Me and Windows NT/2000/XP, Samba has to employ a special method
+for translating a long filename to an 8.3 filename in such a way that
+similar filenames will not cause collisions. This is called
+<em class="firstterm">name mangling</em>, and Samba deals with this in a
+manner that is similar, but not identical to, Windows 95 and its
+successors.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-4.1"/>
+
+<h3 class="head2">The Samba Mangling Operation</h3>
+
+<p><a name="INDEX-102"/>Here is how Samba mangles a long
+filename into an 8.3 filename:</p>
+
+<ul><li>
+<p>If the original filename does not begin with a dot, the first five
+characters before the dot (if there is one) are converted to
+uppercase. These characters are used as the first five characters of
+the 8.3 mangled filename.</p>
+</li><li>
+<p>If the original filename begins with a dot, the dot is removed and
+then the previous step is performed on what is left.</p>
+</li><li>
+<p>These characters are immediately followed by a special mangling
+character: by default, a tilde (~), although Samba allows you to
+change this character.</p>
+</li><li>
+<p>The base of the long filename before the last period is hashed into a
+two-character code; parts of the name after the last dot can be used
+if necessary. This two-character code is appended to the filename
+after the mangling character.</p>
+</li><li>
+<p>The first three characters after the last dot (if there is one) of
+the original filename are converted to uppercase and appended onto
+the mangled name as the extension. If the original filename began
+with a dot, three underscores ( <tt class="literal">_ _ _</tt> ) are used
+as the extension instead.</p>
+</li></ul>
+<p>Here are some examples:</p>
+
+<blockquote><pre class="code">virtuosity.dat                       VIRTU~F1.DAT
+.htaccess                            HTACC~U0._ _ _
+hello.java                           HELLO~1F.JAV
+team.config.txt                      TEAMC~04.TXT
+antidisestablishmentarianism.txt     ANTID~E3.TXT
+antidisease.txt                      ANTID~9K.TXT</pre></blockquote>
+
+<p>Using these rules will allow Windows for Workgroups to differentiate
+the two files on behalf of the poor individual who is forced to see
+the network through the eyes of that operating system. Note that the
+same long filename should always hash to the same mangled name with
+Samba; this doesn't always happen with Windows. The
+downside of this approach is that there can still be collisions;
+however, the chances are greatly reduced.</p>
+
+<p>You generally want to use the mangling configuration options with
+only the oldest clients. We recommend doing this without disrupting
+other clients by adding an <tt class="literal">include</tt> directive to
+the <em class="filename">smb.conf</em> file:</p>
+
+<blockquote><pre class="code">[global]
+    include = /usr/local/samba/lib/smb.conf.%a</pre></blockquote>
+
+<p>This resolves to <em class="filename">smb.conf.WfWg</em> when a Windows
+for Workgroups client attaches. Now you can create a file
+<em class="filename">/usr/local/samba/lib/smb.conf.WfWg</em>, which might
+contain these options:</p>
+
+<blockquote><pre class="code">[global]
+    case sensitive = no
+    default case = upper
+    preserve case = no
+    short preserve case = no
+    mangle case = yes
+    mangled names= yes</pre></blockquote>
+
+<p>If you are not using Windows for Workgroups, you probably do not need
+to change any of these options from their defaults.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.1.1"/>
+
+<h3 class="head3">Representing and resolving filenames with Samba</h3>
+
+<p><a name="INDEX-103"/>Another item that we should
+point out is that there is a difference between how an operating
+system <em class="emphasis">represents</em> a file and how it
+<em class="emphasis">resolves</em> it. For example, you have likely run
+across a file on a Windows system called
+<em class="filename">README.TXT</em>. The file can be represented by the
+operating system entirely in uppercase letters. However, if you open
+an MS-DOS command prompt and enter the command:</p>
+
+<blockquote><pre class="code">C:\&gt; <tt class="userinput"><b>notepad readme.txt</b></tt></pre></blockquote>
+
+<p>the all-caps file is loaded into the editing program, even though you
+typed the name in lowercase letters.</p>
+
+<p>This is because the Windows 95/98/Me and Windows NT/2000/XP families
+of operating systems resolve filenames in a case-insensitive manner,
+even though the files are represented in a case-sensitive manner.
+Unix-based operating systems, on the other hand, always resolve files
+in a case-sensitive manner; if you try to edit
+<em class="filename">README.TXT</em> with the command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>vi readme.txt</b></tt></pre></blockquote>
+
+<p>you will likely be editing the empty buffer of a new file.</p>
+
+<p><a name="INDEX-104"/>Here is how Samba handles case: if the
+<tt class="literal">preserve</tt><a name="INDEX-105"/> <tt class="literal">case</tt> is set
+to <tt class="literal">yes</tt>, Samba will always use the case provided by
+the operating system for representing (not resolving) filenames. If
+it is set to <tt class="literal">no</tt>, it will use the case specified by
+the <tt class="literal">default</tt><a name="INDEX-106"/> <tt class="literal">case</tt> option.
+The same is true for
+<tt class="literal">short</tt><a name="INDEX-107"/>
+<tt class="literal">preserve</tt> <tt class="literal">case</tt>. If this option
+is set to <tt class="literal">yes</tt>, Samba will use the default case of
+the operating system for representing 8.3 filenames; otherwise, it
+will use the case specified by the <tt class="literal">default</tt>
+<tt class="literal">case</tt> option. Finally, Samba will always resolve
+filenames in its shares based on the value of the
+<tt class="literal">case</tt> <tt class="literal">sensitive</tt> option.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-4.2"/>
+
+<h3 class="head2">Mangling Options</h3>
+
+<p><a name="INDEX-108"/><a name="INDEX-109"/>Samba
+allows more refined instructions on how it should perform name
+mangling, including those controlling the case sensitivity, the
+character inserted to form a mangled name, and the ability to map
+filenames manually from one format to another. These options are
+shown in <a href="ch08.html#samba2-CHP-8-TABLE-5">Table 8-5</a>.</p>
+
+<a name="samba2-CHP-8-TABLE-5"/><h4 class="head4">Table 8-5. Name-mangling options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">case sensitive</tt></p>
+
+<p><tt class="literal">(casesignames)</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, treats filenames as case-sensitive
+(Windows doesn't).</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">default case</tt></p>
+</td>
+<td>
+<p>string (<tt class="literal">upper</tt> or <tt class="literal">lower</tt>)</p>
+</td>
+<td>
+<p>Case to assume as default (used only when preserve case is
+<tt class="literal">no</tt>).</p>
+</td>
+<td>
+<p>Lower</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">preserve case</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, keep the case the client supplied (i.e.,
+do not convert to <tt class="literal">default</tt>
+<tt class="literal">case</tt>).</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">short preserve case</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, preserve case of 8.3-format names that the
+client provides.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">mangled names</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Mangles long names into 8.3 DOS format.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">mangle case</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Mangle a name if it is mixed case.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">mangling char</tt></p>
+</td>
+<td>
+<p>string (single character)</p>
+</td>
+<td>
+<p>Gives mangling character.</p>
+</td>
+<td>
+<p><tt class="literal">~</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">mangled stack</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Number of mangled names to keep on the local mangling stack.</p>
+</td>
+<td>
+<p><tt class="literal">50</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">mangled map</tt></p>
+</td>
+<td>
+<p>string (list of patterns)</p>
+</td>
+<td>
+<p>Allows mapping of filenames from one format into another.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.1"/>
+
+<a name="INDEX-110"/><h3 class="head3">case sensitive</h3>
+
+<p>This share-level option, which has the obtuse synonym
+<tt class="literal">casesignames</tt>, specifies whether Samba should
+preserve case when resolving filenames in a specific share. The
+default value for this option is <tt class="literal">no</tt>, which is how
+Windows handles file resolution. If clients are using an operating
+system that takes advantage of case-sensitive filenames, you can set
+this configuration option to <tt class="literal">yes</tt> as shown here:</p>
+
+<blockquote><pre class="code">[accounting]
+    case sensitive = yes</pre></blockquote>
+
+<p>Otherwise, we recommend that you leave this option set to its default.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.2"/>
+
+<h3 class="head3">default case</h3>
+
+<p>The <tt class="literal">default</tt><a name="INDEX-111"/> <tt class="literal">case</tt> option
+is used with <tt class="literal">preserve</tt> <tt class="literal">case</tt>.
+This specifies the default case (upper or lower) Samba uses to create
+a file on one of its shares on behalf of a client. The default case
+is <tt class="literal">lower</tt>, which means that newly created files
+will have lowercase names. If you need to, you can override this
+global option by specifying the following:</p>
+
+<blockquote><pre class="code">[global]
+    default case = upper</pre></blockquote>
+
+<p>If you specify this value, the names of newly created files are
+translated into uppercase and cannot be overridden in a program. We
+recommend that you use the default value unless you are dealing with
+a Windows for Workgroups or other 8.3 client, in which case it should
+be <tt class="literal">upper</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.3"/>
+
+<a name="INDEX-112"/><h3 class="head3">preserve case</h3>
+
+<p>This option specifies whether a file created by Samba on behalf of
+the client is created with the case provided by the client operating
+system or the case specified by the earlier
+<tt class="literal">default</tt> <tt class="literal">case</tt> configuration
+option. The default value is <tt class="literal">yes</tt>, which uses the
+case provided by the client operating system. If it is set to
+<tt class="literal">no</tt>, the value of the <tt class="literal">default</tt>
+<tt class="literal">case</tt> option (upper or lower) is used.</p>
+
+<p>Note that this option does not handle 8.3 file requests sent from the
+client&mdash;see the upcoming <tt class="literal">short</tt>
+<tt class="literal">preserve</tt> <tt class="literal">case</tt> option. You might
+want to set this option to <tt class="literal">yes</tt>, for example, if
+applications that create files on the Samba server demand the file be
+all uppercase. If instead you want Samba to mimic the behavior of a
+Windows NT filesystem, you can leave this option set to its default,
+<tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.4"/>
+
+<a name="INDEX-113"/><h3 class="head3">short preserve case</h3>
+
+<p>This option specifies whether an 8.3 filename created by Samba on
+behalf of the client is created with the default case of the client
+operating system or the case specified by the
+<tt class="literal">default</tt> <tt class="literal">case</tt> configuration
+option. The default value is <tt class="literal">yes</tt>, which uses the
+case provided by the client operating system. You can let Samba
+choose the case through the <tt class="literal">default</tt>
+<tt class="literal">case</tt> option by setting it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    short preserve case = no</pre></blockquote>
+
+<p>If you want to force Samba to mimic the behavior of a Windows NT
+filesystem, you can leave this option set to its default,
+<tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.5"/>
+
+<a name="INDEX-114"/><h3 class="head3">mangled names</h3>
+
+<p>This share-level option specifies whether Samba will mangle filenames
+for 8.3 clients. If the option is set to <tt class="literal">no</tt>, Samba
+will not mangle the names, and (depending on the client) they will
+either be invisible or appear truncated to those using 8.3 operating
+systems. The default value is <tt class="literal">yes</tt>. You can
+override it per share as follows:</p>
+
+<blockquote><pre class="code">[data]
+    mangled names = no</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.6"/>
+
+<a name="INDEX-115"/><h3 class="head3">mangle case</h3>
+
+<p>This option tells Samba whether it should mangle filenames that are
+not composed entirely of the case specified using the
+<tt class="literal">default</tt> <tt class="literal">case</tt> configuration
+option. The default for this option is <tt class="literal">no</tt>. If you
+set it to <tt class="literal">yes</tt>, you should be sure that all clients
+can handle the mangled filenames that result. You can override it per
+share as follows:</p>
+
+<blockquote><pre class="code">[data]
+    mangle case = yes</pre></blockquote>
+
+<p>We recommend that you leave this option alone unless you have a
+well-justified need to change it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.7"/>
+
+<a name="INDEX-116"/><h3 class="head3">mangling char</h3>
+
+<p>This share-level option specifies the mangling character used when
+Samba mangles filenames into the 8.3 format. The default character
+used is a tilde (~). You can reset it to whatever character you wish.
+For instance:</p>
+
+<blockquote><pre class="code">[data]
+    mangling char = #</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.8"/>
+
+<a name="INDEX-117"/><h3 class="head3">mangled stack</h3>
+
+<p>Samba maintains a local stack of recently mangled 8.3 filenames; this
+stack can be used to reverse-map mangled filenames back to their
+original state. This is often needed by applications that create and
+save a file, close it, and need to modify it later. The default
+number of long filename/mangled filename pairs stored on this stack
+is 50. However, if you want to cut down on the amount of processor
+time used to mangle filenames, you can increase the size of the stack
+to whatever you wish, at the expense of memory and slightly slower
+file access:</p>
+
+<blockquote><pre class="code">[global]
+    mangled stack = 100</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-4.2.9"/>
+
+<a name="INDEX-118"/><h3 class="head3">mangled map</h3>
+
+<p>If the default behavior of name mangling is not sufficient, you can
+give Samba further instructions on how to behave using the
+<tt class="literal">mangled</tt> <tt class="literal">map</tt> option. This option
+allows you to specify mapping patterns that can be used in place of
+name mangling performed by Samba. For example:</p>
+
+<blockquote><pre class="code">[data]
+    mangled map =(*.database *.db) (*.class *.cls)</pre></blockquote>
+
+<p>Here, Samba is instructed to search each encountered file for
+characters that match the first pattern specified in the parenthesis
+and convert them to the modified second pattern in the parenthesis
+for display on an 8.3 client. This is useful in the event that name
+mangling converts the filename incorrectly or converts it to a format
+that the client cannot understand readily. Patterns are separated by
+whitespaces. <a name="INDEX-119"/><a name="INDEX-120"/> <a name="INDEX-121"/><a name="INDEX-122"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-5"/>
+
+<h2 class="head1">Locks and Oplocks</h2>
+
+<p><a name="INDEX-123"/><a name="INDEX-124"/><a name="INDEX-125"/><a name="INDEX-126"/>Concurrent
+writes to a single file are not desirable in any operating system. To
+prevent this, most operating systems use <em class="firstterm">locks</em>
+to guarantee that only one process can write to a file at a time.
+Operating systems traditionally lock entire files, although newer
+ones allow a range of bytes within a file to be locked. If another
+process attempts to write to a file (or section of one) that is
+already locked, it receives an error from the operating system and
+will have to wait until the lock is released.</p>
+
+<p>Samba supports the standard DOS and NT filesystem (deny-mode) locking
+requests&mdash;which allow only one process to write to an entire
+file on a server at a given time&mdash;as well as byte-range locking.
+In addition, Samba supports a locking mechanism known in the Windows
+NT world as <em class="firstterm">opportunistic locking,
+</em><a name="INDEX-127"/>or<em class="firstterm">
+</em><em class="emphasis">oplock</em> for short.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-5.1"/>
+
+<h3 class="head2">Opportunistic Locking</h3>
+
+<p>Opportunistic locking allows a client to notify the Samba server that
+it will not only be the exclusive writer of a file, but will also
+cache its changes to that file locally to speed up access by reducing
+network activity. This can result in a large performance
+gain&mdash;typically 30%&mdash;while at the same time reserving
+network bandwidth for other purposes.</p>
+
+<p>Because exclusive access can be obtained using regular file locks,
+the value of opportunistic locks is not so much to lock the file as
+it is to cache it. In fact, a better name for opportunistic locking
+might be <em class="firstterm">opportunistic caching</em>.</p>
+
+<p>When Samba knows that a file in one of its shares has been oplocked
+by a client, it marks its version as having an opportunistic lock and
+waits for the client to complete work on the file, at which point it
+expects the client to send its changes back to the Samba server for
+synchronization with the copy on the server.</p>
+
+<p>If a second client requests access to that file before the first
+client has finished working on it, Samba sends an oplock break
+request to the first client. This tells the client to stop caching
+its changes and return the current state of the file to the server so
+that the interrupting client can use it as it sees fit. An
+opportunistic lock, however, is not a replacement for a standard
+deny-mode lock. It is not unheard of for the interrupting process to
+be granted an oplock break only to discover that the original process
+also has a deny-mode lock on a file as well. <a href="ch08.html#samba2-CHP-8-FIG-11">Figure 8-11</a> illustrates this <a name="INDEX-128"/>opportunistic locking process.</p>
+
+<div class="figure"><a name="samba2-CHP-8-FIG-11"/><img src="figs/sam2_0811.gif"/></div><h4 class="head4">Figure 8-11. Opportunistic locking</h4>
+
+<p>In most cases, the extra performance resulting from the use of
+oplocks is highly desirable. However, allowing the client to cache
+data can be a big risk if either the client or network hardware are
+unreliable. Suppose a client opens a file for writing, creating an
+oplock on it. When another client also tries to open the file, an
+oplock break request is sent to the first client. If this request
+goes unfulfilled for any reason and the second client starts writing
+to the file, the file can be easily corrupted as a result of the two
+processes writing to it concurrently. Unfortunately, this scenario is
+very real. Uncoordinated behavior such as this has been observed many
+times among Windows clients in SMB networks (with files served by
+Windows NT/2000 or Samba). Typically, the affected files are database
+files, which multiple clients open concurrently for writing.</p>
+
+<p>A more concrete example of <a name="INDEX-129"/>oplock failure occurs when database
+files are very large. If a client is allowed to oplock this kind of
+file, there can be a huge delay while the client copies the entire
+file from the server to cache it, even though it might need to update
+only one record. The situation goes from bad to worse when another
+client tries to open the oplocked file. The first client might need
+to write the entire file back to the server before the second
+client's file open request can succeed. This results
+in another huge delay (for both clients), which in practice often
+results in a failed open due to a timeout on the second client,
+perhaps along with a message warning of possible database corruption!</p>
+
+<p>If you are having problems of this variety, you can turn off oplocks
+for the affected files by using the
+<tt class="literal">veto</tt><a name="INDEX-130"/> <tt class="literal">oplock</tt>
+<tt class="literal">files</tt> parameter:</p>
+
+<blockquote><pre class="code">[dbdata]
+    veto oplock files = /*.dbm/</pre></blockquote>
+
+<p>Use the value of the parameter (a list of filename-matching patterns
+separated by slash characters) to match all the files in the share
+that might be a source of trouble. The syntax of this parameter is
+similar to that of the <tt class="literal">veto</tt>
+<tt class="literal">files</tt> parameter.</p>
+
+<p>If you want to be really careful and can live with reduced
+performance, you can turn off oplocks altogether, preventing the
+oplock break problem from ever occurring:</p>
+
+<blockquote><pre class="code">[global]
+    oplocks = no</pre></blockquote>
+
+<p>This disables oplocks for all files in all shares served by the Samba
+server. If you wish to disable oplocks in just a specific share, you
+can specify the <tt class="literal">oplocks</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> parameter in just that share:</p>
+
+<blockquote><pre class="code">[database]
+    oplocks = no</pre></blockquote>
+
+<p>This example allows other shares, which might have less sensitive
+data, to attain better performance, while trading performance for
+better data integrity for files in the <tt class="literal">[database]</tt>
+share.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-5.2"/>
+
+<h3 class="head2">Unix and Oplocks</h3>
+
+<p><a name="INDEX-131"/>Most of the time, oplocks help Windows
+client systems cooperate to avoid overwriting each
+other's changes. Unix systems also have file-locking
+mechanisms to allow Unix processes to cooperate with each other. But
+if a file stored on a Samba system is accessed by both a Windows
+network client and a local Unix process&mdash;without an additional
+coordination between the two systems&mdash;the Unix process could
+easily ride roughshod over an oplock.</p>
+
+<p>Some Unix systems have enhanced kernels that understand the Windows
+oplocks maintained by Samba. Currently the support exists only in SGI
+Irix and Linux.</p>
+
+<p>If you leave oplocks enabled and your Unix system does not support
+kernel oplocks, you could end up with corrupted data when somebody
+runs a Unix process that reads or writes a file that Windows users
+also access. This is another case where the
+<tt class="literal">veto</tt><a name="INDEX-132"/> <tt class="literal">oplock</tt>
+<tt class="literal">files</tt> parameter can be used, assuming you can
+anticipate which Samba files are used by both Windows users and Unix
+users. For example, suppose the <tt class="literal">[usrfiles]</tt> share
+contains some ASCII text files with the <em class="filename">.txt</em>
+filename extension and OpenOffice word processor documents with the
+<em class="filename">.doc</em> filename extension, which Unix and Windows
+users both modify. We can use <tt class="literal">veto</tt>
+<tt class="literal">oplock</tt> <tt class="literal">files</tt> like this:</p>
+
+<blockquote><pre class="code">[usrfiles]
+    veto oplock files = /*.txt/*.doc/</pre></blockquote>
+
+<p>This will suppress the use of oplocks on <em class="filename">.txt</em>
+and <em class="filename">.doc</em> files, which will suppress client
+caching, while allowing the Windows and Unix programs to use regular
+file locking to prevent concurrent writes to the same file.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-5.3"/>
+
+<h3 class="head2">Locks and Oplocks Configuration Options</h3>
+
+<p><a name="INDEX-133"/><a name="INDEX-134"/>Samba's options for
+locks and oplocks are given in <a href="ch08.html#samba2-CHP-8-TABLE-6">Table 8-6</a>.</p>
+
+<a name="samba2-CHP-8-TABLE-6"/><h4 class="head4">Table 8-6. Locks and oplocks configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">locking</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, turns on byte-range locks.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">strict</tt> <tt class="literal">locking</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, denies access to an entire file if a
+byte-range lock exists in it.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">posix locking</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, maps oplocks to POSIX locks on the local
+system.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">oplocks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, turns on local caching of files on the
+client for this share.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">kernel</tt> <tt class="literal">oplocks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, indicates that the kernel supports oplocks.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">level2 oplocks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows oplocks to downgrade to read-only.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">fake oplocks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, tells client the lock was obtained, but
+doesn't actually lock it.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">blocking</tt> <tt class="literal">locks</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Allows lock requestor to wait for the lock to be granted.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">veto oplock</tt> <tt class="literal">files</tt></p>
+</td>
+<td>
+<p>string (list of filenames)</p>
+</td>
+<td>
+<p>Does not oplock specified files.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lock</tt> <tt class="literal">directory</tt></p>
+</td>
+<td>
+<p>string (fully qualified pathname)</p>
+</td>
+<td>
+<p>Sets the location where various Samba files, including locks, are
+stored.</p>
+</td>
+<td>
+<p>As specified in Samba makefile</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.1"/>
+
+<h3 class="head3">locking</h3>
+
+<p>The <tt class="literal">locking</tt><a name="INDEX-135"/> option can be used to tell
+Samba to engage or disengage server-side byte-range locks on behalf
+of the client. Samba implements byte-range locks on the server side
+with normal Unix advisory locks and consequently prevents other
+properly behaved Unix processes from overwriting a locked byte range.</p>
+
+<p>This option can be specified per share as follows:</p>
+
+<blockquote><pre class="code">[accounting]
+    locking = yes</pre></blockquote>
+
+<p>If the <tt class="literal">locking</tt> option is set to
+<tt class="literal">yes</tt>, the requestor is delayed until the holder of
+either type of lock releases it (or crashes). If, however, the option
+is set to <tt class="literal">no</tt>, no byte-range locks are kept for the
+files, although requests to lock and unlock files will appear to
+succeed. The option is set to <tt class="literal">yes</tt> by default;
+however, you can turn this option off if you have read-only media.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.2"/>
+
+<a name="INDEX-136"/><h3 class="head3">strict locking</h3>
+
+<p>This option checks every file access for a byte-range lock on the
+range of bytes being accessed. This is typically not needed if a
+client adheres to all the locking mechanisms in place. This option is
+set to <tt class="literal">no</tt> by default; however, you can reset it
+per share as follows:</p>
+
+<blockquote><pre class="code">[accounting]
+    strict locking = yes</pre></blockquote>
+
+<p>If this option is set to <tt class="literal">yes</tt>, mandatory locks are
+enforced on any file with byte-range locks.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.3"/>
+
+<a name="INDEX-137"/><h3 class="head3">posix locking</h3>
+
+<p>On systems that support POSIX locking, Samba automatically maps
+oplocks to POSIX locks. This behavior can be disabled by setting
+<tt class="literal">posix</tt> <tt class="literal">locking</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt>. You should never need to
+change the default behavior, which is <tt class="literal">posix</tt>
+<tt class="literal">locking</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.4"/>
+
+<a name="INDEX-138"/><h3 class="head3">oplocks</h3>
+
+<p>This option enables or disables support for oplocks on the client.
+The option is enabled by default. However, you can disable it with
+the following command:</p>
+
+<blockquote><pre class="code">[data]
+    oplocks = no</pre></blockquote>
+
+<p>If you are in an extremely unstable network environment or have many
+clients that cannot take advantage of opportunistic locking, it might
+be better to shut this Samba feature off. If the host operating
+system does not support kernel oplocks, oplocks should be disabled if
+users are accessing the same files from both Unix applications (such
+as <em class="emphasis">vi</em>) and SMB clients.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.5"/>
+
+<a name="INDEX-139"/><h3 class="head3">kernel oplocks</h3>
+
+<p>If a Unix application on the Samba host system (that is not part of
+the Samba suite) tries to open a file for writing that Samba has
+oplocked to a Windows client, it is likely to succeed (depending on
+the operating system), and both Samba and the client are never aware
+of it.</p>
+
+<p>Some versions of Unix have support for oplocks in the kernel that can
+work along with Samba's oplocks. In this case, the
+Unix process trying to open the file is suspended while Samba directs
+the client to write its copy back. After that has happened, the
+operating system allows the open to complete. At the time of this
+writing, this feature is supported only by SGI Irix and Linux.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.6"/>
+
+<a name="INDEX-140"/><h3 class="head3">level2 oplocks</h3>
+
+<p>Windows NT/2000/XP clients can downgrade their read-write oplocks to
+read-only oplocks when another client opens the same file. This can
+result in significant improvements in performance on files that are
+written infrequently or not at all&mdash;especially
+executables&mdash;because all clients can then maintain a read-ahead
+cache for the file. By default, <tt class="literal">level2</tt>
+<tt class="literal">oplocks</tt> is set to <tt class="literal">yes</tt>, and you
+probably won't need to change it.</p>
+
+<p>Currently, Samba cannot support level 2 oplocks along with kernel
+oplocks and automatically disables level 2 oplocks when kernel
+oplocks are in use. (This might change in future releases as improved
+support for oplocks is added by the Samba developers.) If you are
+running Samba on a host system that supports kernel oplocks, you must
+set <tt class="literal">kernel</tt> <tt class="literal">oplocks</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt> to enable support for
+level 2 oplocks.</p>
+
+<p>Disabling oplocks with <tt class="literal">oplocks</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt> also disables level 2
+oplocks.</p>
+
+<p>Samba can automatically detect its Unix host's
+support of kernel oplocks and will set the value of
+<tt class="literal">kernel</tt> <tt class="literal">oplocks</tt> automatically.
+You should never need to set this option in your Samba configuration
+file.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.7"/>
+
+<a name="INDEX-141"/><h3 class="head3">fake oplocks</h3>
+
+<p>When this option is set to <tt class="literal">yes</tt>, Samba pretends to
+allow oplocks rather than actually supporting them. If this option is
+enabled on a read-only share (such as a shared CD-ROM drive), all
+clients are told that the files are available for opportunistic
+locking and never warned of simultaneous access. As a result, Windows
+clients cache more of the file's data and obtain
+much better performance.</p>
+
+<p>This option was added to Samba before opportunistic-locking support
+was available, and it is now generally considered better to use real
+oplocks. Do not ever enable <tt class="literal">fake</tt>
+<tt class="literal">oplocks</tt> on a read/write share.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.8"/>
+
+<h3 class="head3">blocking locks</h3>
+
+<p>Samba also supports <em class="firstterm">blocking locks</em>, a minor
+variant of range locks. Here, if the range of bytes is not available,
+the client specifies an amount of time that it's
+willing to wait. The server then caches the lock request,
+periodically checking to see if the file is available. If it is, it
+notifies the client; however, if time expires, Samba will tell the
+client that the request has failed. This strategy prevents the client
+from continually polling to see if the lock is available.</p>
+
+<p>You can disable this option per share as follows:</p>
+
+<blockquote><pre class="code">[accounting]
+    blocking locks = no</pre></blockquote>
+
+<p>When set to <tt class="literal">yes</tt>, blocking locks are enforced on
+the file. If this option is set to <tt class="literal">no</tt>, Samba
+behaves as if normal locking mechanisms are in place on the file. The
+default is <tt class="literal">yes</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.9"/>
+
+<a name="INDEX-142"/><h3 class="head3">veto oplock files</h3>
+
+<p>You can provide a list of filenames that are never granted
+opportunistic locks with the <tt class="literal">veto</tt>
+<tt class="literal">oplock</tt> <tt class="literal">files</tt> option. This
+option can be set either globally or on a per-share basis. For
+example:</p>
+
+<blockquote><pre class="code">veto oplock files = /*.bat/*.htm/</pre></blockquote>
+
+<p>The value of this option is a series of patterns. Each pattern entry
+must begin, end, or be separated from another with a slash ( / )
+character, even if only one pattern is listed. Asterisks can be used
+as a wildcard to represent zero or more characters. Questions marks
+can be used to represent exactly one character.</p>
+
+<p>We recommend that you disable oplocks on any files that are meant to
+be updated by Unix or are intended for simultaneous sharing by
+several processes.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-5.3.10"/>
+
+<a name="INDEX-143"/><h3 class="head3">lock directory</h3>
+
+<p>This option (sometimes called <tt class="literal">lock</tt>
+<tt class="literal">dir</tt>) specifies the location of a directory where
+Samba will store SMB deny-mode lock files. Samba stores other files
+in this directory as well, such as browse lists and its shared memory
+file. If WINS is enabled, the WINS database is written to this
+directory as well. The default for this option is specified in the
+Samba makefile; it is typically
+<em class="filename">/usr/local/samba/var/locks</em>. You can override
+this location as follows:</p>
+
+<blockquote><pre class="code">[global]
+    lock directory = /usr/local/samba/locks</pre></blockquote>
+
+<p>You typically would not need to override this option, unless you want
+to move the lock files to a more standard location, such as
+<em class="filename">/var/spool/locks</em>. <a name="INDEX-144"/> <a name="INDEX-145"/><a name="INDEX-146"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-6"/>
+
+<h2 class="head1">Connection Scripts</h2>
+
+<p><a name="INDEX-147"/><a name="INDEX-148"/><a name="INDEX-149"/>Samba supports a mechanism called
+<em class="firstterm">connection scripts</em>, by which commands can be
+executed on the server as clients connect to a share or later
+disconnect from it. By using configuration file variables along with
+some custom programming, you can create connection scripts that
+perform a wide range of functions. As a simple example, here is a
+&quot;quick and dirty&quot; way to monitor
+connections to shares on the Samba server in real time. First, the
+value of the <tt class="literal">preexec</tt><a name="INDEX-150"/> parameter is set as
+follows:</p>
+
+<blockquote><pre class="code">[global]
+    preexec = /bin/echo %u at %m connected to //%L/%S on %T &gt;&gt;/tmp/smblog</pre></blockquote>
+
+<p>This causes information about the user and the connection to be
+written to the file <em class="filename">/tmp/smblog</em> whenever any
+client connects to any share. To watch clients connect, run the
+following command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>tail -f /tmp/smblog</b></tt>
+jay at maya connected to //toltec/data on 2002/11/21 21:21:15
+david at apache connected to //toltec/techs on 2002/11/21 21:21:57
+sally at seminole connected to //toltec/payroll on 2002/11/21 21:22:16
+martha at dine connected to //toltec/profiles on 2002/11/21 21:23:38
+martha at dine connected to //toltec/netlogon on 2002/11/21 21:23:39
+martha at dine connected to //toltec/martha on 2002/11/21 21:23:40
+aaron at huastec connected to //toltec/netlogon on 2002/11/21 21:24:19
+aaron at huastec connected to //toltec/aaron on 2002/11/21 21:24:20</pre></blockquote>
+
+<p>With the <em class="emphasis">-f</em> option, the
+<em class="emphasis">tail</em> command monitors
+<em class="filename">/tmp/smblog</em> and prints additional output as new
+data is appended to the file. Every time a new connection is made, an
+additional line is printed, showing the output of the
+<tt class="literal">preexec</tt> command. Notice the lines resulting from
+connections by user <tt class="literal">martha</tt> and
+<tt class="literal">aaron</tt>. User <tt class="literal">martha</tt> logged on to
+the domain from a Windows NT client, which accessed the
+<tt class="literal">[profiles]</tt> share to download her profile, then the
+<tt class="literal">[netlogon]</tt> share to read the logon script, and
+then her home directory (because her logon script contains a
+<tt class="literal">net</tt> <tt class="literal">use</tt> <tt class="literal">H</tt>:
+<tt class="literal">/home</tt> command) to connect her home directory to
+drive letter H. The connections from <tt class="literal">aaron</tt> are
+similar, except that he connected from a Windows 98 system, which
+does not use the <tt class="literal">[profiles]</tt> share. (See <a href="ch04.html">Chapter 4</a> for more information about domain logons.)</p>
+
+<p>A more advanced use of
+<a name="INDEX-151"/><a name="INDEX-152"/>connection scripts is to monitor the
+contents of users' home directories and/or other
+shared directories and perform checks ensuring that local
+administrative policies are followed. Checked items might include the
+following:</p>
+
+<ul><li>
+<p>Disk usage, on a per-share, per-directory, or per-file basis</p>
+</li><li>
+<p>Types of files stored on the server</p>
+</li><li>
+<p>Whether filenames follow naming guidelines</p>
+</li><li>
+<p>Whether viruses have copied themselves to the Samba server</p>
+</li></ul>
+<p>To handle this kind of task, a shell script or other program would be
+written to perform the checks and take appropriate actions, such as
+removing offending files. The <tt class="literal">root</tt>
+<tt class="literal">preexec</tt> parameter would be used to run the command
+as the root user, using configuration file variables to pass
+arguments. For example:</p>
+
+<blockquote><pre class="code">[homes]
+    root preexec = admin_checks %S
+    root preexec close = yes</pre></blockquote>
+
+<p>In this example, a specially written administrative checking program
+(<em class="emphasis">admin_checks</em>) is used to monitor
+users' home directories on the Samba server. The
+<tt class="literal">%S</tt> variable is used to pass the name of the home
+directory to the script. The
+<tt class="literal">root</tt><a name="INDEX-153"/> <tt class="literal">preexec</tt>
+<tt class="literal">close</tt> parameter has been set to
+<tt class="literal">yes</tt> so that if <em class="emphasis">admin_checks</em>
+detects a serious violation of local policy, it can exit with a
+nonzero status, and the client is prevented from connecting.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-6.1"/>
+
+<h3 class="head2">Connection Script Options</h3>
+
+<p><a href="ch08.html#samba2-CHP-8-TABLE-7">Table 8-7</a> introduces some of the configuration
+options provided for setting up users.</p>
+
+<a name="samba2-CHP-8-TABLE-7"/><h4 class="head4">Table 8-7. Connection script options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">root preexec</tt></p>
+</td>
+<td>
+<p>string (Unix command)</p>
+</td>
+<td>
+<p>Sets a Unix command to run as <tt class="literal">root</tt>, before
+connecting to the share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">root preexec close</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, nonzero exit status of
+<tt class="literal">root preexec</tt> command will disconnect.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">preexec</tt> <tt class="literal">(exec)</tt></p>
+</td>
+<td>
+<p>string (Unix command)</p>
+</td>
+<td>
+<p>Sets a Unix command to run as the user before connecting to the share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">preexec close</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If set to <tt class="literal">yes</tt>, nonzero exit status of
+<tt class="literal">preexec</tt> command will disconnect.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">postexec</tt></p>
+</td>
+<td>
+<p>string (Unix command)</p>
+</td>
+<td>
+<p>Sets a Unix command to run as the user after disconnecting from the
+share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">root</tt> <tt class="literal">postexec</tt></p>
+</td>
+<td>
+<p>string (Unix command)</p>
+</td>
+<td>
+<p>Sets a Unix command to run as <tt class="literal">root</tt> after
+disconnecting from the share.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.1"/>
+
+<a name="INDEX-156"/><h3 class="head3">root preexec</h3>
+
+<p>This option specifies as its value a Unix command to be run
+<em class="emphasis">as the root user</em> before any connection to a
+share is completed. You should use this option specifically for
+performing actions that require root privilege.</p>
+
+<p>To ensure security, users should never be able to modify the target
+of the <tt class="literal">root</tt> <tt class="literal">preexec</tt> command. In
+addition, unless you explicitly redirect it, any information the
+command sends to standard output will be discarded. If you intend to
+use any <tt class="literal">preexec</tt> or <tt class="literal">postexec</tt>
+script, you should ensure that it will run correctly before having
+Samba invoke it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.2"/>
+
+<a name="INDEX-157"/><h3 class="head3">root preexec close</h3>
+
+<p>Sometimes you might want the share to disconnect if the
+<tt class="literal">root</tt> <tt class="literal">preexec</tt> script fails,
+giving the client an error rather than allowing it to connect. For
+example, if you are using <tt class="literal">root</tt>
+<tt class="literal">preexec</tt> to mount a CD-ROM or filesystem, it would
+make no sense to connect the client to it in the event that the mount
+fails. If you specify <tt class="literal">root</tt>
+<tt class="literal">preexec</tt> <tt class="literal">close</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt>, the share will fail to
+connect if the <tt class="literal">root</tt> <tt class="literal">preexec</tt>
+script returns a nonzero exit status.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.3"/>
+
+<a name="INDEX-158"/><h3 class="head3">preexec</h3>
+
+<p>Sometimes just called <tt class="literal">exec</tt>, this option defines an
+ordinary unprivileged command run by Samba as the user specified by
+the variable <tt class="literal">%u</tt>. For example, a common use of this
+option is to perform logging, such as the following:</p>
+
+<blockquote><pre class="code">[homes]
+    preexec = echo &quot;%u connected from %m (%I)\&quot; &gt;&gt;/tmp/.log</pre></blockquote>
+
+<p>You must redirect the standard output of the command if you want to
+use it. Otherwise, it is discarded. This warning also applies to the
+command's standard error output. If you intend to
+use a <tt class="literal">preexec</tt> script, you should ensure that it
+will run correctly before having Samba invoke it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.4"/>
+
+<a name="INDEX-159"/><h3 class="head3">preexec close</h3>
+
+<p>This is similar to <tt class="literal">root</tt> <tt class="literal">preexec</tt>
+<tt class="literal">close</tt>, except that it goes with the
+<tt class="literal">preexec</tt> option. By setting
+<tt class="literal">preexec</tt> <tt class="literal">close</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt>, a
+<tt class="literal">preexec</tt> script that returns nonzero will cause the
+share to disconnect immediately.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.5"/>
+
+<a name="INDEX-160"/><h3 class="head3">postexec</h3>
+
+<p>Once the user disconnects from the share, the command specified with
+<tt class="literal">postexec</tt> is run as the user on the Samba server to
+do any necessary cleanup. This option is essentially the same as the
+<tt class="literal">preexec</tt> option. Again, remember that the command
+is run as the user represented by <tt class="literal">%u</tt>, and any
+information sent to standard output will be ignored.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-6.1.6"/>
+
+<a name="INDEX-161"/><h3 class="head3">root postexec</h3>
+
+<p>Following the <tt class="literal">postexec</tt> option, the
+<tt class="literal">root</tt> <tt class="literal">postexec</tt> command is run,
+if one has been specified. Again, this option specifies as its value
+a Unix command to be run <em class="emphasis">as the root user</em> before
+disconnecting from a share. You should use this option specifically
+for performing actions that require root privilege. <a name="INDEX-162"/> <a name="INDEX-163"/><a name="INDEX-164"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-7"/>
+
+<h2 class="head1">Microsoft Distributed Filesystems</h2>
+
+<p><a name="INDEX-165"/>In a
+large network where many shared folders are spread out over a large
+number of servers, it can be difficult for users to locate the
+resources they are trying to find. Browsing through Network
+Neighborhood or My Network Places can become an ordeal rather than a
+time-saving convenience. To mitigate this problem, Microsoft added an
+extension to file sharing called <em class="firstterm">Distributed
+filesystem</em><a name="INDEX-166"/><a name="INDEX-167"/> (Dfs). Using Dfs, it
+is possible to organize file shares on the network so that they
+appear to users as organized in a single directory tree on a single
+server, regardless of which servers on the network actually contain
+the resources. Instead of having to browse the entire network, users
+can go to the Dfs share and locate their data much more easily.</p>
+
+<p>Dfs can also help administrators because it provides a level of
+indirection between the name of a shared folder and its actual
+location. The Dfs share contains references to resources on the
+network, and when a resource is accessed, the Dfs server hands the
+client off to the actual server of the resource. When moving
+resources to another computer, the reference to the resource in the
+Dfs share can be redirected to the new location in one step, with the
+change being entirely seamless for users.</p>
+
+<p>To a limited extent, Dfs also can help improve performance for
+read-only shares because it provides <a name="INDEX-168"/>load balancing. It is possible
+to set up a Dfs reference to point to identical shares on two or more
+servers. The Dfs server then divides requests between the servers,
+dividing the client load among them. However, this works well only
+for static, read-only data because no provision is included in Dfs
+for synchronization among the servers when changes are made on any of
+them.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-7.1"/>
+
+<h3 class="head2">Windows Dfs Clients</h3>
+
+<p><a name="INDEX-169"/>Modern versions of Windows come with
+client-side support for Dfs, and no extra configuration is required.
+Support is more limited for older versions, however. Windows for
+Workgroups cannot function as a Dfs client at all. Windows NT 4.0
+must be upgraded to at least Service Pack 3 to act as a Dfs client,
+and the Dfs Client must be installed. Later service packs (such as
+Service Pack 6) include the Dfs Client. Windows 95 must also have the
+Dfs Client software installed to act as a Dfs client. Without the Dfs
+Client software, double-clicking a remote folder in a Dfs share will
+show an empty folder, and no error message will appear.</p>
+
+<a name="samba2-CHP-8-NOTE-140"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>To use the Dfs Client for Windows 95 or Windows NT, you must first
+download and install it. See the web page <a href="http://microsoft.com/ntserver/nts/downloads/winfeatures/NTSDistrFile/default.asp">http://microsoft.com/ntserver/nts/downloads/winfeatures/NTSDistrFile/default.asp</a>
+for a link to download the installation program and instructions on
+how to install the Dfs Client.</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-7.2"/>
+
+<h3 class="head2">Configuring Samba for Dfs</h3>
+
+<p><a name="INDEX-170"/>To act as a Dfs server, Samba 2.2 must
+be compiled with the <tt class="literal">--with-msdfs</tt> configure
+option. (See <a href="ch02.html">Chapter 2</a> for instructions on
+configuring and compiling Samba.) Samba 3.0 includes Dfs support by
+default and does not need to be compiled with the
+<tt class="literal">--with-msdfs</tt> configure option.</p>
+
+<p>Once a Dfs-enabled Samba server is running, there are just two steps
+to serving a Dfs share. First we will set up a Dfs root directory on
+the server, and then we will modify the <em class="filename">smb.conf</em>
+configuration file to enable the share.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-7.2.1"/>
+
+<h3 class="head3">Setting up the Dfs root</h3>
+
+<p>First we need to create a directory to act as the Dfs root:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /usr/local/samba/dfs</b></tt></pre></blockquote>
+
+<p>This can be any directory, but it is important that it be owned by
+root and given the proper permissions:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chown root:root /usr/local/samba/dfs</b></tt>
+# <tt class="userinput"><b>chmod 755 /usr/local/samba/dfs</b></tt></pre></blockquote>
+
+<p>The Dfs directory tree can have subdirectories and files, just like
+any other shared directory. These will function just as they would in
+any other share, allowing clients to access the directories and files
+on the Samba server. The whole idea of Dfs, though, is to gather
+together shares on other servers by making references to them in the
+Dfs tree. The way this is implemented with Samba involves a clever
+use of symbolic links, which can be in the Dfs root directory or any
+subdirectory in the Dfs tree.</p>
+
+<p>You are probably familiar with using symbolic links to create
+references to files that exist on the same system, and perhaps
+crossing a local filesystem boundary (which ordinary Unix links
+cannot do). But maybe you didn't know that symbolic
+links have a more general functionality. Although we
+can't display its contents directly, as we could
+with a text or binary file, a symbolic link
+&quot;contains&quot; an ASCII text string
+naming what the link points to. For example, take a look at the
+listing for these symbolic links:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l wrdlnk alnk</b></tt>
+lrwxrwxrwx    1 jay      jay            15 Mar 14 06:50 wrdlnk -&gt; /usr/dict/words
+lrwxrwxrwx    1 jay      jay             9 Mar 14 06:53 alnk -&gt; dreamtime</pre></blockquote>
+
+<p>As you can infer from the size of the <em class="filename">wrdlnk</em>
+link (15 bytes), the string <tt class="literal">/usr/dict/words</tt> is
+encoded into it. The size of <em class="filename">alnk</em> (9 bytes) is
+smaller, corresponding to the shorter name of
+<em class="filename">dreamtime</em>.</p>
+
+<p>Now let's create a link in our Dfs root for an SMB
+share:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>cd /usr/local/samba/dfs</b></tt>
+# <tt class="userinput"><b>ln -s 'msdfs:maya\e' maya-e</b></tt>
+# <tt class="userinput"><b>ls -l maya-e</b></tt>
+lrwxrwxrwx    1 root     root           12 Mar 13 17:34 maya-e -&gt; msdfs:maya\e</pre></blockquote>
+
+<p>This link might appear as a
+&quot;broken&quot; link in a directory
+listing because it points to something that isn't a
+file on the local system. For example, the <em class="emphasis">file</em>
+command will report:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>file maya-e</b></tt>
+maya-e: broken symbolic link to msdfs:maya\e</pre></blockquote>
+
+<p>However, <em class="filename">maya-e</em> is a valid reference to the
+<em class="filename">\\maya\e</em> share when used with
+Samba's Dfs support. When Samba encounters this
+file, it sees the leading <tt class="literal">msdfs</tt>: and interprets
+the rest as the name of a remote share. The client is then redirected
+to the remote share.</p>
+
+<p>When creating links in the Dfs root directory, simply follow the same
+format, which in general is
+<tt class="literal">msdfs</tt>:<em class="replaceable">server</em>\<em class="replaceable">share</em>.
+Note that this is similar to a UNC appended onto the
+<tt class="literal">msdfs</tt>: string, except that in this case, the two
+backslashes preceding the server's name are omitted.</p>
+
+<a name="samba2-CHP-8-NOTE-141"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The names for the symbolic links in Dfs shares must be in all
+lowercase.</p>
+</blockquote>
+
+<p>In addition to regular network shares, you can use symbolic links of
+this type to reference Dfs shares on other Dfs servers. However,
+referencing printer shares does not work. Dfs is for sharing files
+only. <a name="INDEX-171"/></p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-7.2.2"/>
+
+<h3 class="head3">Load balancing</h3>
+
+<p><a name="INDEX-172"/>To
+set up a load-balancing Dfs share, create the symbolic link like
+this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ln -s 'msdfs:toltec\data,msdfs:mixtec\data' lb-data</b></tt></pre></blockquote>
+
+<p>That is, simply use a list of shares separated by commas as the
+reference. Remember, it is up to you to make sure the shared folders
+remain identical. Set up permissions on the servers to make the
+shares read-only to users.</p>
+
+<p>The last thing we need to do is to modify the
+<em class="filename">smb.conf</em> file to define the Dfs root share and
+add Dfs support. The Dfs root is added as a share definition:</p>
+
+<a name="INDEX-173"/><blockquote><pre class="code">[dfs]
+    path = /usr/local/samba/dfs
+    msdfs root = yes</pre></blockquote>
+
+<p>You can use any name you like for the share. The path is set to the
+Dfs root directory we just set up, and the parameter
+<tt class="literal">msdfs</tt> <tt class="literal">root</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> tells Samba that this share is a Dfs root.</p>
+
+<p>To enable support for Dfs in the server, we need to add one line to
+the <tt class="literal">[global]</tt> section:</p>
+
+<a name="INDEX-174"/><blockquote><pre class="code">[global]
+    host msdfs = yes</pre></blockquote>
+
+<p>Restart the Samba daemons&mdash;or just wait a minute for them to
+reread the configuration file&mdash;and you will see the new share
+from Windows clients. If you have trouble accessing any of the remote
+shares in the Dfs share, recheck your symbolic links to make sure
+they were created correctly. <a name="INDEX-175"/></p>
+
+<a name="samba2-CHP-8-NOTE-142"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you previously had a share by the same name as your Dfs share, you
+might need to reboot Windows clients before they can access the share
+as a Dfs share.</p>
+</blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-8-SECT-8"/>
+
+<h2 class="head1">Working with NIS</h2>
+
+<p>In networks where NIS and NFS are in use, it is common for
+users' home directories to be mounted over the
+network by NFS. If a Samba server being used to authenticate user
+logons is running on a system with NFS-mounted home directories
+shared with a <tt class="literal">[homes]</tt> share, the additional
+overhead can result in poor performance&mdash;about 30% of normal
+Samba speed.</p>
+
+<p>Samba has the ability to work with <a name="INDEX-176"/>NIS and NIS+ to find the
+server on which the home directories actually reside so that they can
+be shared directly from that server. For this to work, the server
+that holds the home directories must also have Samba running, with a
+<tt class="literal">[homes]</tt> share of its own.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-8-SECT-8.1"/>
+
+<h3 class="head2">NIS Configuration Options</h3>
+
+<p><a href="ch08.html#samba2-CHP-8-TABLE-8">Table 8-8</a> introduces the
+<a name="INDEX-177"/><a name="INDEX-178"/>NIS configuration options specifically
+for setting up users.</p>
+
+<a name="samba2-CHP-8-TABLE-8"/><h4 class="head4">Table 8-8. NIS options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">nis homedir</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, uses NIS instead of
+<em class="filename">/etc/passwd</em> to look up the path of a
+user's home directory.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">homedir map</tt></p>
+</td>
+<td>
+<p>string (NIS map name)</p>
+</td>
+<td>
+<p>Sets the NIS map to use to look up a user's home
+directory.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-8-SECT-8.1.1"/>
+
+<h3 class="head3">nis homedir, homedir map</h3>
+
+<p>The <tt class="literal">nis</tt><a name="INDEX-179"/> <tt class="literal">homedir</tt> and
+<tt class="literal">homedir</tt><a name="INDEX-180"/> <tt class="literal">map</tt> options
+are for Samba servers on network sites where Unix home directories
+are provided using NFS, the automounter, and NIS.</p>
+
+<p>The <tt class="literal">nis</tt> <tt class="literal">homedir</tt> option
+indicates that the home-directory server for the user needs to be
+looked up in NIS. The <tt class="literal">homedir</tt>
+<tt class="literal">map</tt> option tells Samba in which NIS map to look
+for the server that has the user's home directory.
+The server needs to be a Samba server so that the client can do an
+SMB connect to it, and the other Samba servers need to have NIS
+installed so that they can do the lookup.</p>
+
+<p>For example, if user <tt class="literal">joe</tt> asks for a share called
+<tt class="literal">[joe]</tt>, and the <tt class="literal">nis</tt>
+<tt class="literal">homedir</tt> option is set to <tt class="literal">yes</tt>,
+Samba will look in the file specified by <tt class="literal">homedir</tt>
+<tt class="literal">map</tt> for a home directory for
+<tt class="literal">joe</tt>. If it finds one, Samba will return the
+associated system name to the client. The client will then try to
+connect to that machine and get the share from there. Enabling NIS
+lookups looks like the following:</p>
+
+<blockquote><pre class="code">[globals]
+    nis homedir = yes
+    homedir map = amd.map</pre></blockquote>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> The system checkbox will
+probably be grayed for your file. Don't worry about
+that&mdash;you should still be able to see when the box is checked
+and when it isn't.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch09.html b/docs/htmldocs/using_samba/ch09.html
new file mode 100644
index 0000000000..bc2a5bb007
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch09.html
@@ -0,0 +1,3448 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 9. Users and Security</h1>
+
+ 
+
+<p><a name="INDEX-1"/>In this chapter, we
+cover the basic concepts of managing security in Samba so that you
+can set up your Samba server with a security policy suited to your
+network.</p>
+
+<p>One of Samba's most complicated tasks lies in
+reconciling the security models of Unix and Windows systems. Samba
+must identify users by associating them with valid usernames and
+groups, authenticate them by checking their passwords, then control
+their access to resources by comparing their access rights to the
+permissions on files and directories. These are complex topics on
+their own, and it doesn't help that there are three
+different operating system types to deal with (Unix, Windows
+95/98/Me, and Windows NT/2000/XP) and that Samba supports multiple
+methods of handling user authentication.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-9-SECT-1"/>
+
+<h2 class="head1">Users and Groups</h2>
+
+<p><a name="INDEX-2"/>Let's start
+out as simply as possible and add support for a single user. The
+easiest way to set up a client user is to create a Unix account (and
+home directory) for that individual on the server and notify Samba of
+the user's existence. You can do the latter by
+creating a disk share that maps to the user's home
+directory in the Samba configuration file and restricting access to
+that user with the <tt class="literal">valid</tt><a name="INDEX-3"/>
+<tt class="literal">users</tt> option. For example:</p>
+
+<blockquote><pre class="code">[dave]
+        path = /home/dave
+        comment = Dave's home directory
+        writable = yes
+        valid users = dave</pre></blockquote>
+
+<p>The <tt class="literal">valid</tt> <tt class="literal">users</tt> option lists
+the users allowed to access the share. In this case, only the user
+<tt class="literal">dave</tt> is allowed to access the share. In some
+situations it is possible to specify that any user can access a disk
+share by using the <tt class="literal">guest</tt> <tt class="literal">ok</tt>
+parameter. Because we don't wish to allow guest
+access, that option is absent here. If you allow both authenticated
+users and guest users access to the same share, you can make some
+files accessible to guest users by assigning world-readable
+permissions to those files while restricting access to other files to
+particular users or groups.</p>
+
+<p>When client users access a Samba share, they have to pass two levels
+of restriction. Unix permissions on files and directories apply as
+usual, and configuration parameters specified in the Samba
+configuration file apply as well. In other words, a client must first
+pass Samba's security mechanisms (e.g.,
+authenticating with a valid username and password, passing the check
+for the <tt class="literal">valid</tt> <tt class="literal">users</tt> parameter
+and the <tt class="literal">read</tt> <tt class="literal">only</tt> parameter,
+etc.), as well as the normal Unix file and directory permissions of
+its Unix-side user, before it can gain read/write access to a share.</p>
+
+<p>Remember that you can abbreviate the user's home
+directory by using the <tt class="literal">%H</tt><a name="INDEX-4"/> variable. In addition, you can use the
+Unix username variable <tt class="literal">%u</tt><a name="INDEX-5"/> and/or the client username variable
+<tt class="literal">%U</tt><a name="INDEX-6"/> in your options as well. For
+example :</p>
+
+<blockquote><pre class="code">[dave]
+    comment = %U home directory
+    writable = yes
+    valid users = dave
+    path = %H</pre></blockquote>
+
+<p>With a single user accessing a home directory, access permissions are
+taken care of when the user account is created. The home directory is
+owned by the user, and permissions on it are set appropriately.
+However, if you're creating a shared directory for
+group access, you need to perform a few more steps.
+Let's take a stab at a
+<a name="INDEX-7"/>group share for the
+accounting department in the <em class="emphasis">smb.conf</em> file:</p>
+
+<blockquote><pre class="code">[accounting]
+    comment = Accounting Department Directory
+    writable = yes
+    valid users = @account
+    path = /home/samba/accounting
+    create mode = 0660
+    directory mode = 0770</pre></blockquote>
+
+<p>The first thing we did differently is to specify
+<tt class="literal">@account</tt> as the valid user instead of one or more
+individual usernames. This is shorthand for saying that the valid
+users are represented by the Unix group <tt class="literal">account</tt>.
+These users will need to be added to the group entry
+<tt class="literal">account</tt> in the
+<a name="INDEX-8"/><a name="INDEX-9"/>system group file (
+<em class="filename">/etc/group</em><a name="INDEX-10"/>
+or equivalent) to be recognized as part of the group. Once they are,
+Samba will recognize those users as valid users for the share.</p>
+
+<p>In addition, you need to create a shared directory that the members
+of the group can access and point to it with the
+<tt class="literal">path</tt> configuration option. Here are the Unix
+commands that create the shared directory for the accounting
+department (assuming <em class="emphasis">/home/samba</em> already
+exists):</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /home/samba/accounting</b></tt>
+# <tt class="userinput"><b>chgrp account /home/samba/accounting</b></tt>
+# <tt class="userinput"><b>chmod 770 /home/samba/accounting</b></tt></pre></blockquote>
+
+<p>There are two other options in this <em class="filename">smb.conf</em>
+example, both of which we saw in the previous chapter. These options
+are <tt class="literal">create</tt><a name="INDEX-11"/> <tt class="literal">mode</tt> and
+<tt class="literal">directory</tt><a name="INDEX-12"/> <tt class="literal">mode</tt>. These
+options set the maximum file and directory permissions that a new
+file or directory can have. In this case, we have denied all world
+access to the contents of this share. (This is reinforced by the
+<em class="emphasis">chmod</em> command, shown earlier.)<a name="INDEX-13"/></p>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-1.1"/>
+
+<h3 class="head2">Handling Multiple Individual Users</h3>
+
+<p><a name="INDEX-14"/>Let's return
+to user shares for a moment. If we have several users for whom to set
+up home directory shares, we probably want to use the special
+<tt class="literal">[homes]</tt> share that we introduced in <a href="ch08.html">Chapter 8</a>. With the
+<tt class="literal">[homes]</tt><a name="INDEX-15"/> share, all we need to say is:</p>
+
+<blockquote><pre class="code">[homes]
+    browsable = no
+    writable = yes</pre></blockquote>
+
+<p>The <tt class="literal">[homes]</tt> share is a special section of the
+Samba configuration file. If a user attempts to connect to an
+ordinary share that doesn't appear in the
+<em class="filename">smb.conf</em> file (such as specifying it with a UNC
+in Windows Explorer), Samba will search for a
+<tt class="literal">[homes]</tt> share. If one exists, the incoming share
+name is assumed to be a username and is queried as such in the
+password database ( <em class="filename">/etc/passwd</em> or equivalent)
+file of the Samba server. If it appears, Samba assumes the client is
+a Unix user trying to connect to his home directory.</p>
+
+<p>As an illustration, let's assume that
+<tt class="literal">sofia</tt> is attempting to connect to a share called
+<tt class="literal">[sofia]</tt> on the Samba server. There is no share by
+that name in the configuration file, but a <tt class="literal">[homes]</tt>
+share exists and user <tt class="literal">sofia</tt> is present in the
+password database, so Samba takes the following steps:</p>
+
+<ol><li>
+<p>Samba creates a new disk share called <tt class="literal">[sofia]</tt> with
+the <tt class="literal">path</tt> specified in the
+<tt class="literal">[homes]</tt> section. If no <tt class="literal">path</tt>
+option is specified in <tt class="literal">[homes]</tt>, Samba initializes
+it to her home directory.</p>
+</li><li>
+<p>Samba initializes the new share's options from the
+defaults in <tt class="literal">[globals]</tt>, as well as any overriding
+options in <tt class="literal">[homes]</tt> with the exception of
+<tt class="literal">browsable</tt>.</p>
+</li><li>
+<p>Samba connects <tt class="literal">sofia</tt>'s client to
+that share.</p>
+</li></ol>
+<p>The <tt class="literal">[homes]</tt> share is a fast, painless way to
+create shares for your user community without having to duplicate the
+information from the password database file in the
+<em class="filename">smb.conf</em> file. It does have some
+<a name="INDEX-16"/>peculiarities, however, that we need to
+point out:</p>
+
+<ul><li>
+<p>The <tt class="literal">[homes]</tt> section can represent any account on
+the machine, which isn't always desirable. For
+example, it can potentially create a share for
+<tt class="literal">root</tt>, <tt class="literal">bin</tt>,
+<tt class="literal">sys</tt>, <tt class="literal">uucp</tt>, and the like. You
+can set a global
+<tt class="literal">invalid</tt><a name="INDEX-17"/> <tt class="literal">users</tt> option
+to protect against this.</p>
+</li><li>
+<p>The meaning of the
+<tt class="literal">browsable</tt><a name="INDEX-18"/> configuration option is
+different from other shares; it indicates only that a
+<tt class="literal">[homes]</tt> section won't show up in
+the local browse list, not that the <tt class="literal">[alice]</tt> share
+won't. When the <tt class="literal">[alice]</tt> section
+is created (after the initial connection), it will use the
+<tt class="literal">browsable</tt> value from the
+<tt class="literal">[globals]</tt> section for that share, not the value
+from <tt class="literal">[homes]</tt>.</p>
+</li></ul>
+<p>As we mentioned, there is no need for a path statement in
+<tt class="literal">[homes]</tt> if the users have Unix home directories in
+the server's <em class="filename">/etc/passwd</em> file.
+You should ensure that a valid home directory does exist, however, as
+Samba will not automatically create a home directory for a user and
+will refuse a tree connect if the user's directory
+does not exist or is not accessible. <a name="INDEX-19"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-9-SECT-2"/>
+
+<h2 class="head1">Controlling Access to Shares</h2>
+
+<p><a name="INDEX-20"/><a name="INDEX-21"/>Often you will need to restrict the users who
+can access a specific share for security reasons. This is very easy
+to do with Samba because it contains a wealth of options for creating
+practically any security configuration. Let's
+introduce a few configurations that you might want to use in your own
+Samba setup.</p>
+
+<p>We've seen what happens when you specify valid
+users. However, you are also allowed to specify a list of
+<a name="INDEX-22"/>invalid users&mdash;users who should never be
+allowed access to Samba or its shares. This is done with the
+<tt class="literal">invalid</tt><a name="INDEX-23"/> <tt class="literal">users</tt>
+option. We hinted at one frequent use of this option earlier: a
+global default with the <tt class="literal">[homes]</tt> section to ensure
+that various system users and superusers cannot be forged for access.
+For example:</p>
+
+<blockquote><pre class="code">[global]
+    invalid users = root bin daemon adm sync shutdown \
+                        halt mail news uucp operator
+    auto services = dave peter bob
+
+[homes]
+    browsable = no
+    writable = yes</pre></blockquote>
+
+<p>The <tt class="literal">invalid</tt> <tt class="literal">users</tt> option, like
+<tt class="literal">valid</tt> <tt class="literal">users</tt>, can take group
+names, preceded by an at sign (<tt class="literal">@</tt>), as well as
+usernames. In the event that a user or group appears in both lists,
+the <tt class="literal">invalid</tt> <tt class="literal">users</tt> option takes
+precedence, and the user or group is denied access to the share.</p>
+
+<p>At the other end of the spectrum, you can explicitly specify users
+who will be allowed <a name="INDEX-24"/><a name="INDEX-25"/>superuser (root) access to a share with
+the <tt class="literal">admin</tt><a name="INDEX-26"/> <tt class="literal">users</tt>
+option. An example follows:</p>
+
+<blockquote><pre class="code">[sales]
+        path = /home/sales
+        comment = Sedona Real Estate Sales Data
+        writable = yes
+        valid users = sofie shelby adilia
+        admin users = mike</pre></blockquote>
+
+<p>This option takes both group names and usernames. In addition, you
+can specify NIS netgroups by preceding them with an
+<tt class="literal">@</tt> as well; if the netgroup is not found, Samba
+will assume that you are referring to a standard Unix group.</p>
+
+<p>Be careful if you assign administrative privileges to a share for an
+entire group. The Samba Team highly recommends you avoid using this
+option, as it essentially gives root access to the specified users or
+groups for that share.</p>
+
+<p>If you wish to force read-only or read/write access on users who
+access a share, you can do so with the
+<tt class="literal">read</tt><a name="INDEX-27"/> <tt class="literal">list</tt> and
+<tt class="literal">write</tt> <tt class="literal">list</tt> options,
+respectively. These options can be used on a per-share basis to
+restrict a writable share or to grant write access to specific users
+in a read-only share, respectively. For example:</p>
+
+<blockquote><pre class="code">[sales]
+        path = /home/sales
+        comment = Sedona Real Estate Sales Data
+        read only = yes
+        write list = sofie shelby</pre></blockquote>
+
+<p>The <tt class="literal">write</tt><a name="INDEX-28"/> <tt class="literal">list</tt> option
+cannot override Unix permissions. If you've created
+the share without giving the <tt class="literal">write-list</tt> user write
+permission on the Unix system, she will be denied write access
+regardless of the setting of <tt class="literal">write</tt>
+<tt class="literal">list</tt>.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-2.1"/>
+
+<h3 class="head2">Guest Access</h3>
+
+<p><a name="INDEX-29"/>As mentioned
+earlier, you can configure a share using
+<tt class="literal">guest</tt><a name="INDEX-30"/> <tt class="literal">ok</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> to allow access to guest
+users. This works only when using share-level security, which we will
+cover later in this chapter. When a user connects as a guest,
+authenticating with a username and password is unnecessary, but Samba
+still needs a way to map the connected client to a user on the local
+system. The <tt class="literal">guest</tt><a name="INDEX-31"/>
+<tt class="literal">account</tt> parameter can be used in the share to
+specify the Unix account that guest users should be assigned when
+connecting to the Samba server. The default value for this is set
+during compilation and is typically <tt class="literal">nobody</tt>, which
+works well with most Unix versions. However, on some systems the
+<tt class="literal">nobody</tt><a name="INDEX-32"/> account is not allowed to access some
+services (e.g., printing), and you might need to set the guest user
+to <tt class="literal">ftp</tt> or some other account instead.</p>
+
+<p>If you wish to restrict access in a share only to guests&mdash;in
+other words, all clients connect as the guest account when accessing
+the share&mdash;you can use the <tt class="literal">guest</tt>
+<tt class="literal">only</tt> option in conjunction with the
+<tt class="literal">guest</tt> <tt class="literal">ok</tt> option, as shown in
+the following example:</p>
+
+<blockquote><pre class="code">[sales]
+        path = /home/sales
+        comment = Sedona Real Estate Sales Data
+        writable = yes
+        guest ok = yes
+        guest account = ftp
+        guest only = yes</pre></blockquote>
+
+<p>Make sure you specify <tt class="literal">yes</tt> for both
+<tt class="literal">guest</tt> <tt class="literal">only</tt> and
+<tt class="literal">guest</tt> <tt class="literal">ok</tt>; otherwise, Samba will
+not use the guest account that you specify.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-2.2"/>
+
+<h3 class="head2">Access Control Options</h3>
+
+<p><a href="ch09.html#samba2-CHP-9-TABLE-1">Table 9-1</a> <a name="INDEX-33"/><a name="INDEX-34"/>summarizes the options that you can use
+to control access to shares.</p>
+
+<a name="samba2-CHP-9-TABLE-1"/><h4 class="head4">Table 9-1. Share-level access options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">admin users</tt></p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users who can perform operations as root</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">valid users</tt></p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users who can connect to a share</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">invalid users</tt></p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users who will be denied access to a share</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">read list</tt></p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users who have read-only access to a writable share</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">write list</tt></p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users who have read/write access to a read-only share</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max connections</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum number of connections for a share at a given time</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">guest only</tt> <tt class="literal">(only guest)</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows only guest access</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">guest account</tt></p>
+</td>
+<td>
+<p>string (name of account)</p>
+</td>
+<td>
+<p>Unix account that will be used for guest access</p>
+</td>
+<td>
+<p><tt class="literal">nobody</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.1"/>
+
+<a name="INDEX-35"/><h3 class="head3">admin users</h3>
+
+<p>This option specifies a list of users that perform file operations as
+if they were <tt class="literal">root</tt>. This means that they can modify
+or destroy any other user's files, regardless of the
+permissions. Any files that they create will have root ownership and
+will use the default group of the admin user. The
+<tt class="literal">admin</tt> <tt class="literal">users</tt> option allows PC
+users to act as administrators for particular shares. Be very careful
+when using this option, and make sure good password and other
+security policies are in place.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.2"/>
+
+<a name="INDEX-36"/><a name="INDEX-37"/><h3 class="head3">valid users, invalid users</h3>
+
+<p>These two options let you enumerate the users and groups who are
+granted or denied access to a particular share. You can enter a list
+of user and/or group names. If a name is prefixed by an at sign
+(<tt class="literal">@</tt>), it is interpreted as a group name&mdash;with
+NIS groups searched before Unix groups. If the name is prefixed by a
+plus sign (<tt class="literal">+</tt>), it is interpreted as the name of a
+Unix group, and NIS is not searched. If the name is prefixed by an
+ampersand (<tt class="literal">&amp;</tt>), it is interpreted as an NIS
+group name rather than as a Unix group name. The plus sign and
+ampersand can be used together to specify whether NIS or Unix groups
+are searched first. For example:</p>
+
+<blockquote><pre class="code">[database]
+    valid users = mary ellen sue &amp;sales +marketing @dbadmin
+    invalid users = gavin syd dana &amp;techies +&amp;helpdesk</pre></blockquote>
+
+<p>In the <tt class="literal">valid</tt> <tt class="literal">users</tt> parameter,
+users <tt class="literal">mary</tt>, <tt class="literal">ellen</tt>, and
+<tt class="literal">sue</tt> are allowed access to the
+<tt class="literal">[database]</tt> share, as are the members of the Unix
+group <tt class="literal">marketing</tt> and NIS/Unix group
+<tt class="literal">dbadmin</tt>. The <tt class="literal">invalid</tt>
+<tt class="literal">users</tt> parameter denies access to the share by
+users <tt class="literal">gavin</tt>, <tt class="literal">syd</tt>, and
+<tt class="literal">dana</tt>, as well as members of the NIS group
+<tt class="literal">techies</tt> and Unix/NIS group
+<tt class="literal">helpdesk</tt>. In this last case, the list of Unix
+groups is searched first for the <tt class="literal">helpdesk</tt> group,
+and if it is not found there, the list of NIS groups is searched.</p>
+
+<p>The important rule to remember with these options is that any name or
+group in the <tt class="literal">invalid</tt> <tt class="literal">users</tt> list
+will <em class="emphasis">always</em> be denied access, even if it is
+included (in any form) in the <tt class="literal">valid</tt>
+<tt class="literal">users</tt> list.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.3"/>
+
+<a name="INDEX-38"/><a name="INDEX-39"/><h3 class="head3">read list, write list</h3>
+
+<p>Like the <tt class="literal">valid</tt> <tt class="literal">users</tt>
+<tt class="literal">and</tt> <tt class="literal">invalid</tt>
+<tt class="literal">users</tt> options, this pair of options specifies
+which users have read-only access to a writable share and read/write
+access to a read-only share, respectively. The value of either
+options is a list of users. The <tt class="literal">read</tt>
+<tt class="literal">list</tt> parameter overrides any other Samba
+permissions granted&mdash;as well as Unix file permissions on the
+server system&mdash;to deny users write access.
+<tt class="literal">The</tt> <tt class="literal">write</tt>
+<tt class="literal">list</tt> parameter overrides other Samba permissions
+to grant write access, but cannot grant write access if the user
+lacks write permissions for the file on the Unix system. You can
+specify NIS or Unix group names by prefixing the name with an at sign
+(such as <tt class="literal">@users</tt>). Neither configuration option has
+a default value associated with it.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.4"/>
+
+<a name="INDEX-40"/><h3 class="head3">max connections</h3>
+
+<p>This option specifies the maximum number of client connections that a
+share can have at any given time. Any connections that are attempted
+after the maximum is reached will be rejected. The default value is
+<tt class="literal">0</tt>, which is a special case that allows an
+unlimited number of connections. You can override it per share as
+follows:</p>
+
+<blockquote><pre class="code">[accounting]
+    max connections = 30</pre></blockquote>
+
+<p>This option is useful in the event that you need to limit the number
+of users who are accessing a licensed program or piece of data
+concurrently.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.5"/>
+
+<a name="INDEX-41"/><h3 class="head3">guest only</h3>
+
+<p>This share-level option (also called <tt class="literal">only</tt>
+<tt class="literal">guest</tt>) forces a connection to a share to be
+performed with the user specified by the <tt class="literal">guest</tt>
+<tt class="literal">account</tt> option. The share to which this is applied
+must explicitly specify <tt class="literal">guest</tt>
+<tt class="literal">ok</tt> <tt class="literal">=</tt> <tt class="literal">yes</tt> for
+this option to be recognized by Samba. The default value for this
+option is <tt class="literal">no</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.2.6"/>
+
+<a name="INDEX-42"/><h3 class="head3">guest account</h3>
+
+<p>This option specifies the name of the account to be used for guest
+access to shares in Samba. The default for this option varies from
+system to system, but it is often set to <tt class="literal">nobody</tt>.
+Some default user accounts have trouble connecting as guest users. If
+that occurs on your system, the Samba Team recommends using the
+<tt class="literal">ftp</tt> account as the guest user. <a name="INDEX-43"/> <a name="INDEX-44"/><a name="INDEX-45"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-2.3"/>
+
+<h3 class="head2">Username Options</h3>
+
+<p><a href="ch09.html#samba2-CHP-9-TABLE-2">Table 9-2</a> shows two additional options that Samba
+can use to correct for incompatibilities in usernames between Windows
+and Unix.</p>
+
+<a name="samba2-CHP-9-TABLE-2"/><h4 class="head4">Table 9-2. Username options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">username</tt> <tt class="literal">map</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>Sets the name of the username mapping file</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">username</tt> <tt class="literal">level</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Indicates the number of capital letters to use when trying to match a
+username</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.3.1"/>
+
+<a name="INDEX-46"/><h3 class="head3">username map</h3>
+
+<p>Client usernames on an SMB network can be relatively long (up to 255
+characters), while usernames on a Unix network often cannot be longer
+than eight characters. This means that an individual user can have
+one username on a client and another (shorter) one on the Samba
+server. You can get past this issue by<em class="firstterm">
+</em><a name="INDEX-47"/>mapping a free-form client
+username to a Unix username of eight or fewer characters. It is
+placed in a standard text file, using a format that
+we'll describe shortly. You can then specify the
+pathname to Samba with the global <tt class="literal">username</tt>
+<tt class="literal">map</tt> option. Be sure to restrict access to this
+file; make the root user the file's owner and deny
+write access to others (with octal permissions of 744 or 644).
+Otherwise, an untrusted user with access to the file can easily map
+his client username to the root user of the Samba server.</p>
+
+<p>You can specify this option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    username map = /usr/local/samba/private/usermap.txt</pre></blockquote>
+
+<p>Each entry in the username map file should be listed as follows: the
+Unix username, followed by an equal sign (<tt class="literal">=</tt>),
+followed by one or more whitespace-separated SMB client usernames.
+Note that unless instructed otherwise (i.e., a guest connection),
+Samba will expect both the client and the server user to have the
+same password. You can also map NT groups to one or more specific
+Unix groups using the <tt class="literal">@</tt> sign. Here are some
+examples:</p>
+
+<blockquote><pre class="code">jarwin = JosephArwin
+manderso = MarkAnderson
+users = @account</pre></blockquote>
+
+<p>You can also use the asterisk to specify a wildcard that matches any
+free-form client username as an entry in the username map file:</p>
+
+<blockquote><pre class="code">nobody = *</pre></blockquote>
+
+<p>Comments can be placed in the file by starting the line with a hash
+mark (<tt class="literal">#</tt>) or a semicolon (<tt class="literal">;</tt>).</p>
+
+<p>Note that you can also use this file to redirect one Unix user to
+another user. Be careful, though, as Samba and your client might not
+notify the user that the mapping has been made and Samba might be
+expecting a different password.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-2.3.2"/>
+
+<a name="INDEX-48"/><h3 class="head3">username level</h3>
+
+<p>SMB clients (such as Windows) will often send usernames in SMB
+connection requests entirely in capital letters; in other words,
+client usernames are not necessarily case-sensitive. On a Unix
+server, however, usernames <em class="emphasis">are</em> case-sensitive:
+the user <tt class="literal">ANDY</tt> is different from the user
+<tt class="literal">andy</tt>. By default, Samba attacks this problem by
+doing the following:</p>
+
+<ol><li>
+<p>Checking for a user account with the exact name sent by the client</p>
+</li><li>
+<p>Testing the username in all lowercase letters</p>
+</li><li>
+<p>Testing the username in lowercase letters with only the first letter
+capitalized</p>
+</li></ol>
+<p>If you wish to have Samba attempt more combinations of upper- and
+lowercase letters, you can use the <tt class="literal">username</tt>
+<tt class="literal">level</tt> global configuration option. This option
+takes an integer value that specifies how many letters in the
+username should be capitalized when attempting to connect to a share.
+You can specify this option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    username level = 3</pre></blockquote>
+
+<p>In this case, Samba attempts all possible permutations of usernames
+having three capital letters. The larger the number, the more
+computations Samba has to perform to match the username, and the
+longer the authentication will take.</p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-9-SECT-3"/>
+
+<h2 class="head1">Authentication of Clients</h2>
+
+<p><a name="INDEX-49"/>At
+this point, we should discuss how Samba authenticates users. Each
+user who attempts to connect to a share not allowing guest access
+must provide a password to
+<a name="INDEX-50"/>make a successful connection. What
+Samba does with that password&mdash;and consequently the strategy
+Samba will use to handle user authentication&mdash;is the arena of
+the <tt class="literal">security</tt> configuration option. Samba currently
+supports <a name="INDEX-51"/><a name="INDEX-52"/><a name="INDEX-53"/>four
+<a name="INDEX-54"/>security levels on its network:
+<em class="firstterm">share</em>, <em class="firstterm">user</em>,
+<em class="firstterm">server</em>, and <em class="firstterm">domain</em>.</p>
+
+<dl>
+<dt><b><a name="INDEX-55"/>Share-level security</b></dt>
+<dd>
+<p>Each share in the workgroup has one or more passwords associated with
+it. Anyone who knows a valid password for the share can access it.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-56"/>User-level security</b></dt>
+<dd>
+<p>Each share in the workgroup is configured to allow access from
+certain users. With each initial tree connection, the Samba server
+verifies users and their passwords to allow them access to the share.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-57"/>Server-level security</b></dt>
+<dd>
+<p>This is the same as user-level security, except that the Samba server
+uses another server to validate users and their passwords before
+granting access to the share.</p>
+</dd>
+
+
+
+<dt><b><a name="INDEX-58"/>Domain-level security</b></dt>
+<dd>
+<p>Samba becomes a member of a Windows NT domain and uses one of the
+domain's domain controllers&mdash;either the PDC or
+a BDC&mdash;to perform authentication. Once authenticated, the user
+is given a special token that allows her access to any share with
+appropriate access rights. With this token, the domain controller
+will not have to revalidate the user's password each
+time she attempts to access another share within the domain. The
+domain controller can be a Windows NT/2000 PDC or BDC, or Samba
+acting as a Windows NT PDC.</p>
+</dd>
+
+</dl>
+
+<p>Each security policy can be implemented with the global
+<tt class="literal">security</tt> option, as shown in <a href="ch09.html#samba2-CHP-9-TABLE-3">Table 9-3</a>.</p>
+
+<a name="samba2-CHP-9-TABLE-3"/><h4 class="head4">Table 9-3. Security option</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">security</tt><a name="INDEX-59"/></p>
+</td>
+<td>
+<p><tt class="literal">domain</tt>, <tt class="literal">server</tt>,
+<tt class="literal">share</tt>, or <tt class="literal">user</tt></p>
+</td>
+<td>
+<p>Indicates the type of security that the Samba server will use</p>
+</td>
+<td>
+<p><tt class="literal">user</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-3.1"/>
+
+<h3 class="head2">Share-Level Security</h3>
+
+<p>With share-level security, each share has one or more passwords
+associated with it, with the client being authenticated when first
+connecting to the share. This differs from the other modes of
+security in that there are no restrictions as to whom can access a
+share, as long as that individual knows the correct password. Shares
+often have multiple passwords. For example, one password might grant
+read-only access, while another might grant read/write access.
+Security is maintained as long as unauthorized users do not discover
+the password for a share to which they shouldn't
+have access.</p>
+
+<p>OS/2 and Windows 95/98/Me both support share-level security on their
+resources. You can set up share-level security with Windows 95/98/Me
+by first enabling share-level security using the Access Control tab
+of the Network Control Panel dialog. Then select the
+&quot;Share-level access control&quot; radio
+button (which deselects the &quot;User-level access
+control&quot; radio button), as shown in <a href="ch09.html#samba2-CHP-9-FIG-1">Figure 9-1</a>, and click the OK button. Reboot as requested.</p>
+
+<div class="figure"><a name="samba2-CHP-9-FIG-1"/><img src="figs/sam2_0901.gif"/></div><h4 class="head4">Figure 9-1. Selecting share-level security on a Windows 95/98/Me system</h4>
+
+<p>Next, right-click a resource&mdash;such as a hard drive or a
+CD-ROM&mdash;and select the Properties menu item. This will bring up
+the Resource Properties dialog box. Select the Sharing tab at the top
+of the dialog box, and enable the resource as Shared As. From here,
+you can configure how the shared resource will appear to individual
+users, as well as assign whether the resource will appear as
+read-only, read/write, or a mix, depending on the password that is
+supplied.</p>
+
+<p>You might be thinking that this security model is not a good fit for
+Samba&mdash;and you would be right. In fact, if you set the
+<tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">share</tt> option in the Samba configuration file,
+Samba will still reuse the username/password combinations in the
+system password files to authenticate access. More precisely, Samba
+will take the following steps when a client requests a connection
+using share-level security:</p>
+
+<ol><li>
+<p>When a connection is requested, Samba will accept the password and
+(if sent) the username of the client.</p>
+</li><li>
+<p>If the share is <tt class="literal">guest</tt> <tt class="literal">only</tt> ,
+the user is immediately granted access to the share with the rights
+of the user specified by the <tt class="literal">guest</tt>
+<tt class="literal">account</tt> parameter; no password checking is
+performed.</p>
+</li><li>
+<p>For other shares, Samba appends the username to a list of users who
+are allowed access to the share. It then attempts to validate the
+password given in association with that username. If successful,
+Samba grants the user access to the share with the rights assigned to
+that user. The user will not need to authenticate again unless a
+<tt class="literal">revalidate</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> option has been set inside the share.</p>
+</li><li>
+<p>If the authentication is unsuccessful, Samba attempts to validate the
+password against the list of users previously compiled during
+attempted connections, as well as those specified under the share in
+the configuration file. If the password matches that of any username
+(as specified in the system password file, typically
+<em class="filename">/etc/passwd </em>), the user is granted access to the
+share under that username.</p>
+</li><li>
+<p>However, if the share has a <tt class="literal">guest</tt>
+<tt class="literal">ok</tt> or <tt class="literal">public</tt> option set, the
+user will default to access with the rights of the user specified by
+the <tt class="literal">guest</tt> <tt class="literal">account</tt> option.</p>
+</li></ol>
+<p>You can indicate in the configuration file which users should be
+initially placed on the share-level security user list by using the
+<tt class="literal">username</tt> configuration option, as shown here:</p>
+
+<blockquote><pre class="code">[global]
+    security = share
+
+[accounting1]
+    path = /home/samba/accounting1
+    guest ok = no
+    writable = yes
+    username = davecb, pkelly, andyo</pre></blockquote>
+
+<p>Here, when a user attempts to connect to a share, Samba verifies the
+sent password against each user in its own list, in addition to the
+passwords of users <tt class="literal">davecb</tt>,
+<tt class="literal">pkelly</tt>, and <tt class="literal">andyo</tt>. If any of
+the passwords match, the connection is verified, and the user is
+allowed. Otherwise, connection to the specific share will fail.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-3.2"/>
+
+<h3 class="head2">Share-Level Security Options</h3>
+
+<p><a href="ch09.html#samba2-CHP-9-TABLE-4">Table 9-4</a> shows the options typically associated
+with <em class="firstterm">share-level
+security</em><a name="INDEX-60"/>.</p>
+
+<a name="samba2-CHP-9-TABLE-4"/><h4 class="head4">Table 9-4. Share-level access options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">only user</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, usernames specified by
+<tt class="literal">username</tt> are the only ones allowed</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">username</tt> (<tt class="literal">user</tt> or
+<tt class="literal">users</tt>)</p>
+</td>
+<td>
+<p>string (list of usernames)</p>
+</td>
+<td>
+<p>Users against which a client's password is tested</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-3.2.1"/>
+
+<a name="INDEX-61"/><h3 class="head3">only user</h3>
+
+<p>This Boolean option indicates whether Samba will allow connections to
+a share using share-level security based solely on the individuals
+specified in the <tt class="literal">username</tt> option, instead of those
+users compiled on Samba's internal list. The default
+value for this option is <tt class="literal">no</tt>. You can override it
+per share as follows:</p>
+
+<blockquote><pre class="code">[global]
+    security = share
+[data]
+    username = andy, peter, valerie
+    only user = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-3.2.2"/>
+
+<a name="INDEX-62"/><h3 class="head3">username</h3>
+
+<p>This option presents a list of usernames and/or group names against
+which Samba tests a connection password to allow access. It is
+typically used with clients that have share-level security to allow
+connections to a particular service based solely on a qualifying
+password&mdash;in this case, one that matches a password set up for a
+specific user:</p>
+
+<blockquote><pre class="code">[global]
+    security = share
+[data]
+    username = andy, peter, terry</pre></blockquote>
+
+<p>You can enter a list of usernames and/or group names. If a name is
+prefixed by an at sign (<tt class="literal">@</tt>), it is interpreted as a
+group name, with NIS groups searched before Unix groups. If the name
+is prefixed by a plus sign (<tt class="literal">+</tt>), it is interpreted
+as the name of a Unix group, and NIS is not searched. If the name is
+prefixed by an ampersand (<tt class="literal">&amp;</tt>), it is
+interpreted as an NIS group name rather than a Unix group name. The
+plus sign and ampersand can be used together to specify whether NIS
+or Unix groups are searched first. When Samba encounters a group name
+in this option, it attempts to authenticate each user in the group
+until if finds one that succeeds. Beware that this can be very
+inefficient.</p>
+
+<p>We recommend against using this option unless you are implementing a
+Samba server with share-level security.</p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-3.3"/>
+
+<h3 class="head2">User-Level Security</h3>
+
+<p>The default mode of security with Samba is <em class="firstterm">user-level
+security</em><a name="INDEX-63"/>. With this method, each share is
+assigned specific users that can access it. When a user requests a
+connection to a share, Samba authenticates by validating the given
+username and password with the authorized users in the configuration
+file and the passwords in the password database of the Samba server.
+As mentioned earlier in the chapter, one way to isolate which users
+are allowed access to a specific share is by using the
+<tt class="literal">valid</tt> <tt class="literal">users</tt> option for each
+share:</p>
+
+<blockquote><pre class="code">[global]
+    security = user
+
+[accounting1]
+    writable = yes
+    valid users = bob, joe, sandy</pre></blockquote>
+
+<p>Each user listed can connect to the share if the password provided
+matches the password stored in the system password database on the
+server. Once the initial authentication succeeds, the client will not
+need to supply a password again to access that share unless the
+<tt class="literal">revalidate</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> option has been set.</p>
+
+<p>Passwords can be sent to the Samba server in either an encrypted or a
+nonencrypted format. If you have both types of systems on your
+network, you should ensure that the passwords represented by each
+user are stored both in a traditional account database and
+Samba's encrypted password database. This way,
+authorized users can gain access to their shares from any type of
+client.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> However, we recommend that you
+move your system to encrypted passwords and abandon nonencrypted
+passwords if security is an issue. <a href="ch09.html#samba2-CHP-9-SECT-4">Section 9.4</a> of this chapter
+explains how to use encrypted as well as nonencrypted passwords.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-3.4"/>
+
+<h3 class="head2">Server-Level Security</h3>
+
+<p><em class="firstterm">Server-level
+security</em><a name="INDEX-64"/> is similar to user-level security.
+However, with server-level security, Samba delegates password
+authentication to another SMB password server&mdash;typically another
+Samba server or a Windows NT/2000 server acting as a PDC on the
+network. Note that Samba still maintains its list of shares and their
+configuration in its <em class="filename">smb.conf</em> file. When a
+client attempts to make a connection to a particular share, Samba
+validates that the user is indeed authorized to connect to the share.
+Samba then attempts to validate the password by passing the username
+and password to the SMB password server. If the password is accepted,
+a session is established with the client. See <a href="ch09.html#samba2-CHP-9-FIG-2">Figure 9-2</a> for an illustration of this setup.</p>
+
+<div class="figure"><a name="samba2-CHP-9-FIG-2"/><img src="figs/sam2_0902.gif"/></div><h4 class="head4">Figure 9-2. A typical system setup using server-level security</h4>
+
+<p>You can configure Samba to use a separate password server under
+server-level security with the use of the
+<tt class="literal">password</tt><a name="INDEX-65"/> <tt class="literal">server</tt>
+global configuration option, as follows:</p>
+
+<blockquote><pre class="code">[global]
+    security = server
+    password server = mixtec toltec</pre></blockquote>
+
+<p>Note that you can specify more than one machine as the target of the
+<tt class="literal">password</tt> <tt class="literal">server</tt>; Samba moves
+down the list of servers in the event that its first choice is
+unreachable. The servers identified by the
+<tt class="literal">password</tt> <tt class="literal">server</tt> option are
+given as NetBIOS names, not their DNS names or equivalent IP
+addresses. Also, if any of the servers reject the given password, the
+connection automatically fails&mdash;Samba will not attempt another
+server.</p>
+
+<p>One caveat: when using this option, you still need an account
+representing that user on the regular Samba server. This is because
+the Unix operating system needs a username to perform various I/O
+operations. The preferable method of handling this is to give the
+user an account on the Samba server but disable the
+account's password by replacing it in the system
+password file (e.g., <em class="filename">/etc/passwd </em>) with an
+asterisk (*).</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-3.5"/>
+
+<h3 class="head2">Domain-Level Security</h3>
+
+<p>With <em class="firstterm">domain-level
+security</em><a name="INDEX-66"/>, the Samba server acts as a member of
+a Windows domain. Recall from <a href="ch01.html">Chapter 1</a> that each
+domain has a primary domain controller, which can be a Windows
+NT/2000 or Samba server offering password authentication. The domain
+controller keeps track of users and passwords in its own database and
+authenticates each user when she first logs on and wishes to access
+another machine's shares.</p>
+
+<p>As mentioned earlier in this chapter, Samba has a similar ability to
+offer user-level security, but that option is Unix-centric and
+assumes that the authentication occurs via Unix password files. If
+the Unix machine is part of an NIS or NIS+ domain, Samba
+authenticates users transparently against a shared password file in
+typical Unix fashion. Samba then provides access to the NIS or NIS+
+domain from Windows. There is, of course, no relationship between the
+NIS concept of a domain and a Windows NT domain.</p>
+
+<p>Configuring Samba for domain-level security is covered in <a href="ch04.html">Chapter 4</a> in <a href="ch04.html#samba2-CHP-4-SECT-7">Section 4.7</a>. <a name="INDEX-67"/></p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-9-SECT-4"/>
+
+<h2 class="head1">Passwords</h2>
+
+<p><a name="INDEX-68"/>Passwords
+are a thorny issue with Samba. So much so, in fact, that they are
+often the first major problem that users encounter when they install
+Samba. At this point, we need to delve deeper into Samba to discover
+what is happening on the network.</p>
+
+<p>Passwords sent from individual clients can be either encrypted or
+nonencrypted. Encrypted passwords are, of course, more secure. A
+nonencrypted, plain-text password can be easily read with a
+packet-sniffing program, such as the modified
+<em class="emphasis">tcpdump</em> program for Samba that we used in <a href="ch01.html">Chapter 1</a>. Whether passwords are encrypted by default
+depends on the operating system that the client is using to connect
+to the Samba server. <a href="ch09.html#samba2-CHP-9-TABLE-5">Table 9-5</a> lists which
+<a name="INDEX-69"/>Windows operating
+systems encrypt their passwords and which send plain-text passwords
+by default.</p>
+
+<a name="samba2-CHP-9-TABLE-5"/><h4 class="head4">Table 9-5. Windows operating systems with encrypted passwords</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Operating system</p>
+</th>
+<th>
+<p>Encrypted or plain text</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>Windows for Workgroups</p>
+</td>
+<td>
+<p>Plain text</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95</p>
+</td>
+<td>
+<p>Plain text</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 95 with SMB Update</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 98</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows Me</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT 3.x</p>
+</td>
+<td>
+<p>Plain text</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT 4.0 before SP <tt class="literal">3</tt></p>
+</td>
+<td>
+<p>Plain text</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows NT 4.0 after SP 3</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows 2000</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Windows XP</p>
+</td>
+<td>
+<p>Encrypted</p>
+</td>
+</tr>
+
+</table>
+
+<p>Three different encryption methods are used. Windows 95/98/Me clients
+use a method inherited from Microsoft's LAN Manager
+network software. Windows NT/2000/XP systems use a newer system,
+called NT LAN Manager, or NTLM. A newer version of this (called NT
+LAN Manager Version 2, or NTLMv2) uses a different method for
+password hashing.</p>
+
+<p>If encrypted passwords are supported, Samba stores the encrypted
+passwords in a file called <em class="filename">smbpasswd</em>. By
+default, this file is located in the <em class="filename">private</em>
+directory of the Samba distribution (typically
+<em class="filename">/usr/local/samba/private</em>). At the same time, the
+client stores an encrypted version of a user's
+password on its own system. The plain-text password is never stored
+on either system. Each system encrypts the password automatically
+using a standard algorithm when the password is set or changed.</p>
+
+<p>When a client requests a connection to an SMB server that supports
+encrypted passwords (such as Samba or Windows NT/2000/XP), the two
+computers undergo the following negotiations:</p>
+
+<ol><li>
+<p>The client attempts to negotiate a protocol with the server.</p>
+</li><li>
+<p>The server responds with a protocol and indicates that it supports
+encrypted passwords. At this time, it sends back a randomly generated
+8-byte challenge string.</p>
+</li><li>
+<p>The client uses the challenge string as a key to encrypt its already
+encrypted password using an algorithm predefined by the negotiated
+protocol. It then sends the result to the server.</p>
+</li><li>
+<p>The server does the same thing with the encrypted password stored in
+its database. If the results match, the passwords are equivalent, and
+the user is authenticated.</p>
+</li></ol>
+<p>Note that even though the original passwords are not involved in the
+authentication process, you need to be very careful that the
+encrypted passwords located inside the <em class="filename">smbpasswd</em>
+file are guarded from unauthorized users. If they are compromised, an
+unauthorized user can break into the system by replaying the steps of
+the previous algorithm. The encrypted passwords are just as sensitive
+as the plain-text passwords&mdash;this is known as
+<em class="firstterm">plain-text-equivalent</em> data in the cryptography
+world. Of course, your local security policy should require that the
+clients safeguard their plain-text-equivalent passwords as well.</p>
+
+<p>You can configure Samba to accept encrypted passwords with the
+following global additions to <em class="filename">smb.conf</em>. Note
+that we explicitly name the location of the Samba password file:</p>
+
+<blockquote><pre class="code">[global]
+    security = user
+    encrypt passwords = yes
+    smb passwd file = /usr/local/samba/private/smbpasswd</pre></blockquote>
+
+<p>Samba, however, will not accept any users until the
+<em class="filename">smbpasswd</em> file has been created and the users
+have been added to it with the <em class="emphasis">smbpasswd</em>
+command, as we showed you in <a href="ch02.html">Chapter 2</a>.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-4.1"/>
+
+<h3 class="head2">Disabling Encrypted Passwords on the Client</h3>
+
+<p><a name="INDEX-70"/><a name="INDEX-71"/>While Unix authentication has been
+in use for decades&mdash;including the use of
+<em class="emphasis">telnet</em> and <em class="emphasis">rlogin</em> access
+across the Internet&mdash;it embodies well-known security risks.
+Plaintext passwords are sent over the Internet and can be retrieved
+from TCP packets by malicious snoopers. However, if you feel that
+your network is secure and you wish to use standard Unix
+<em class="filename">/etc/passwd</em> authentication for all clients, you
+can do so, but you must disable encrypted passwords on those Windows
+clients that default to using them.</p>
+
+<p>To do this, you must modify the Windows registry on each client
+system. The Samba distribution includes the <em class="filename">.reg</em>
+files you need for this, located in the source
+distribution's <em class="filename">/docs/Registry</em>
+directory. Depending on the platform, you use one of the following
+files:</p>
+
+<blockquote class="simplelist">
+
+<p><em class="filename">Win95_PlainPassword.reg</em></p>
+
+<p><em class="filename">Win98_PlainPassword.reg</em></p>
+
+<p><em class="filename">WinME_PlainPassword.reg</em></p>
+
+<p><em class="filename">NT_PlainPassword.reg</em></p>
+
+<p><em class="filename">Win2000_PlainPassword.reg</em></p>
+
+</blockquote>
+
+<p>(For Windows XP, use the <em class="filename">.reg</em> file for Windows
+2000.) You can perform the installation by copying the appropriate
+<em class="filename">.reg</em> file to a DOS floppy, inserting the floppy
+in the client's floppy drive, and running the
+<em class="filename">.reg</em> file from the Run menu item in the
+client's Start menu. (Or you can just double-click
+the file's icon.)</p>
+
+<p>After you reboot the machine, the client will not encrypt its hashed
+passwords before sending them to the server. This means that the
+plain-text passwords can been seen in the TCP packets that are
+broadcast across the network. Again, we encourage you not to do this
+unless you are absolutely sure that your network is secure.</p>
+
+<p>If passwords are not encrypted, use these two lines in your Samba
+configuration file:</p>
+
+<blockquote><pre class="code">[global]
+    security = user
+    encrypt passwords = no</pre></blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-4.2"/>
+
+<h3 class="head2">The smbpasswd File</h3>
+
+<p>Samba stores its encrypted passwords in a file called
+<em class="filename">smbpasswd</em><a name="INDEX-72"/>,
+which by default resides in the
+<em class="filename">/usr/local/samba/private</em> directory. The
+<em class="filename">smbpasswd</em> file should be guarded as closely as
+the Unix system's password file (either
+<em class="filename">/etc/passwd</em> or
+<em class="filename">/etc/shadow</em>). Only the root user should have
+read/write access to the <em class="filename">private</em> directory, and
+no other users should have access to it at all. In addition, the
+<em class="filename">smbpasswd</em> file should have all access denied to
+all users except for root. When things are set up for good security,
+long listings of the <em class="filename">private</em> directory and
+<em class="filename">smbpasswd</em> file look like the following:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ls -ld /usr/local/samba/private</b></tt>
+drwx- - - - - -   2 root   root   4096 Nov 26 01:11 /usr/local/samba/private
+# <tt class="userinput"><b>ls -l /usr/local/samba/private/smbpasswd</b></tt>
+-rw- - - - - - -   1 root   root    204 Nov 26 01:11 /usr/local/samba/private/smbpasswd</pre></blockquote>
+
+<p>Before you can use encrypted passwords, you need to create an entry
+for each Unix user in the <em class="filename">smbpasswd</em> file. The
+structure of the file is somewhat similar to a Unix
+<em class="filename">passwd</em> file, but has different fields. <a href="ch09.html#samba2-CHP-9-FIG-3">Figure 9-3</a> illustrates the layout of the
+<em class="filename">smbpasswd</em> file; the entry shown is actually one
+line in the file.</p>
+
+<div class="figure"><a name="samba2-CHP-9-FIG-3"/><img src="figs/sam2_0903.gif"/></div><h4 class="head4">Figure 9-3. Structure of the smbpasswd file entry (actually one line)</h4>
+
+<p>Normally, entries in the <em class="filename">smbpasswd</em> file are
+created automatically by the <em class="emphasis">smbpasswd</em> command.
+Still, you might like to know how to interpret data within the
+<em class="filename">smbpasswd</em> file, in case you'd
+like to see what accounts are stored in it or even modify it
+manually. Here is a breakdown of the individual fields:</p>
+
+<dl>
+<dt><b>Username</b></dt>
+<dd>
+<p>This is the username of the account. It is taken directly from the
+system password file.</p>
+</dd>
+
+
+
+<dt><b>UID</b></dt>
+<dd>
+<p>This is the user ID (UID) of the account. Like the username, it is
+taken directly from the system password file and must match the UID
+there.</p>
+</dd>
+
+
+
+<dt><b>LAN Manager Password Hash</b></dt>
+<dd>
+<p>This is a 32-bit hexadecimal sequence that represents the password
+Windows 95/98/Me clients will use. It is derived by splitting the
+password into two 7-character strings, with all lowercase letters
+forced into uppercase. If fewer than 14 characters are in the
+password, the strings are padded with nulls. Then each 7-character
+string is converted to a 56-bit DES key and used to encrypt the
+constant string <tt class="literal">KGS!@#$%</tt>. The two 64-bit results
+are concatenated and stored as the password hash.</p>
+
+
+<p>If there is currently no password for the user, the first 11
+characters of the hash will consist of the sequence
+<tt class="literal">NO</tt> <tt class="literal">PASSWORD</tt> followed by
+<tt class="literal">X</tt> characters for the remainder. If the password
+has been disabled, it will consist of 32 <tt class="literal">X</tt>
+characters.</p>
+</dd>
+
+
+<dt><b>NT LAN Manager (NTLM) Password Hash</b></dt>
+<dd>
+<p>This is a 32-bit hexadecimal sequence that represents the password
+Windows NT/2000/XP clients will use. It is derived by hashing the
+user's password (represented as a 16-bit
+little-endian Unicode sequence) with an MD4 hash. The password is not
+converted to uppercase letters first.</p>
+</dd>
+
+
+
+<dt><b>Account Flags</b></dt>
+<dd>
+<p>This field consists of 11 characters between two braces ( [ ] ). Any
+of the following characters can appear in any order; the remaining
+characters should be spaces:</p>
+
+
+<dl>
+<dt><b>U</b></dt>
+<dd>
+<p>This account is a standard user account.</p>
+</dd>
+
+
+
+<dt><b>D</b></dt>
+<dd>
+<p>This account is currently disabled, and Samba should not allow any
+logins.</p>
+</dd>
+
+
+
+<dt><b>N</b></dt>
+<dd>
+<p>This account has no password associated with it.</p>
+</dd>
+
+
+
+<dt><b>W</b></dt>
+<dd>
+<p>This is a workstation trust account that can be used to configure
+Samba as a PDC when allowing Windows NT machines to join its domain.</p>
+</dd>
+
+</dl>
+</dd>
+
+
+<dt><b>Last Change Time</b></dt>
+<dd>
+<p>This code consists of the characters <tt class="literal">LCT-</tt> followed
+by a hexadecimal representation of the number of seconds since the
+epoch (midnight on January 1, 1970) that the entry was last changed.
+<a name="INDEX-73"/></p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-4.3"/>
+
+<h3 class="head2">Password Synchronization</h3>
+
+<p><a name="INDEX-74"/><a name="INDEX-75"/>Having a regular password (either in
+<em class="filename">/etc/passwd</em> or <em class="filename">/etc/shadow</em>)
+and an encrypted version of the same password (in the
+<em class="filename">smbpasswd</em> file) can be troublesome when you need
+to change both of them. Luckily, Samba affords you a limited ability
+to keep your passwords synchronized. Samba has a pair of
+configuration options to update a user's regular
+Unix password automatically when the encrypted password is changed on
+the system. The feature can be activated by specifying the
+<tt class="literal">unix</tt><a name="INDEX-76"/> <tt class="literal">password</tt>
+<tt class="literal">sync</tt> global configuration option:</p>
+
+<blockquote><pre class="code">[global]
+    unix password sync = yes</pre></blockquote>
+
+<p>With this option enabled, Samba attempts to change the
+user's regular password (as <tt class="literal">root</tt>)
+when the encrypted version is changed with
+<em class="filename">smbpasswd</em>. However, two other options have to be
+set correctly for this to work.</p>
+
+<p>The easier of the two is <tt class="literal">passwd</tt>
+<tt class="literal">program</tt>. This option simply specifies the Unix
+command used to change a user's standard system
+password. It is set to <tt class="literal">/bin/passwd</tt>
+<tt class="literal">%u</tt> by default. With some Unix systems, this is
+sufficient, and you do not need to change anything. Others, such as
+Red Hat Linux, use <em class="emphasis">/usr/bin/passwd</em> instead. In
+addition, you might want to change this to another program or script
+at some point in the future. For example, let's
+assume that you want to use a script called
+<em class="emphasis">changepass</em> to change a user's
+password. Recall that you can use the variable <tt class="literal">%u</tt>
+to represent the current Unix username. So the example becomes:</p>
+
+<blockquote><pre class="code">[global]
+    unix password sync = yes
+    passwd program = changepass %u</pre></blockquote>
+
+<p>Note that this program is called as the <tt class="literal">root</tt> user
+when the <tt class="literal">unix</tt> <tt class="literal">password</tt>
+<tt class="literal">sync</tt> option is set to <tt class="literal">yes</tt>. This
+is because Samba does not necessarily have the old plain-text
+password of the user.</p>
+
+<p>The harder option to configure is
+<tt class="literal">passwd</tt><a name="INDEX-77"/> <tt class="literal">chat</tt>. The
+<tt class="literal">passwd</tt> <tt class="literal">chat</tt> option works like a
+Unix chat script. It specifies a series of strings to send, as well
+as responses to expect from the program specified by the
+<tt class="literal">passwd</tt> <tt class="literal">program</tt> option. For
+example, this is what the default <tt class="literal">passwd</tt>
+<tt class="literal">chat</tt> looks like. The delimiters are the spaces
+between each grouping of characters:</p>
+
+<blockquote><pre class="code">passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*</pre></blockquote>
+
+<p>The first grouping represents a response expected from the
+password-changing program. Note that it can contain wildcards
+(<tt class="literal">*</tt>), which help to generalize the chat programs to
+handle a variety of similar outputs. Here,
+<tt class="literal">*old*password*</tt> indicates that Samba is expecting
+any line from the password program containing the letters
+<tt class="literal">old</tt> followed by the letters
+<tt class="literal">password</tt>, without regard for what comes before,
+after, or between them. If Samba does not receive the expected
+response, the password change will fail.</p>
+
+<p>The second grouping indicates what Samba should send back once the
+data in the first grouping has been matched. In this case, you see
+<tt class="literal">%o\n</tt>. This response is actually two items: the
+variable <tt class="literal">%o</tt> represents the old password, while the
+<tt class="literal">\n</tt> is a newline character. So, in effect, this
+will &quot;type&quot; the old password into
+the standard input of the password-changing program, and then
+&quot;press&quot; Enter.</p>
+
+<p>Following that is another response grouping, followed by data that
+will be sent back to the password-changing program. (In fact, this
+response/send pattern continues indefinitely in any standard Unix
+<em class="emphasis">chat</em> script.) The script continues until the
+final pattern is matched.</p>
+
+<p>You can help match the response strings sent from the password
+program with the characters listed in <a href="ch09.html#samba2-CHP-9-TABLE-6">Table 9-6</a>.
+In addition, you can use the characters listed in <a href="ch09.html#samba2-CHP-9-TABLE-7">Table 9-7</a> to help formulate your response.</p>
+
+<a name="samba2-CHP-9-TABLE-6"/><h4 class="head4">Table 9-6. Password chat response characters</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Character</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">*</tt></p>
+</td>
+<td>
+<p>Zero or more occurrences of any character.</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>&quot;<tt class="literal"> </tt>&quot;</p>
+</td>
+<td>
+<p>Allows you to include matching strings that contain spaces. Asterisks
+are still considered wildcards even inside of quotes, and you can
+represent a null response with empty quotes.</p>
+</td>
+</tr>
+
+</table>
+
+<a name="samba2-CHP-9-TABLE-7"/><h4 class="head4">Table 9-7. Password chat send characters</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Character</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">%o</tt></p>
+</td>
+<td>
+<p>The user's old password</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%n</tt></p>
+</td>
+<td>
+<p>The user's new password</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">\n</tt></p>
+</td>
+<td>
+<p>The linefeed character</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">\r</tt></p>
+</td>
+<td>
+<p>The carriage-return character</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">\t</tt></p>
+</td>
+<td>
+<p>The tab character</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">\s</tt></p>
+</td>
+<td>
+<p>A space</p>
+</td>
+</tr>
+
+</table>
+
+<p>For example, you might want to change your password chat to the
+following entry. This handles scenarios in which you do not have to
+enter the old password. In addition, this also handles the new
+<tt class="literal">all</tt> <tt class="literal">tokens</tt>
+<tt class="literal">updated</tt> <tt class="literal">successfully</tt> string
+that Red Hat Linux sends:</p>
+
+<blockquote><pre class="code">passwd chat = *New password* %n\n *new password* %n\n *success*</pre></blockquote>
+
+<p>Again, the default chat should be sufficient for many Unix systems.
+If it isn't, you can use the
+<tt class="literal">passwd</tt> <tt class="literal">chat</tt>
+<tt class="literal">debug</tt> global option to set up a new chat script
+for the password change program. The <tt class="literal">passwd</tt>
+<tt class="literal">chat</tt> <tt class="literal">debug</tt> option logs
+everything during a password chat. This option is a simple Boolean,
+as shown here:</p>
+
+<blockquote><pre class="code">[global]
+    unix password sync = yes
+    passwd chat debug = yes
+    log level = 100</pre></blockquote>
+
+<p>After you activate the password chat debug feature, all I/O received
+by Samba through the password chat can be sent to the
+<em class="filename">log.smbd</em> Samba log file with a debug level of
+100, which is why we entered a new <tt class="literal">log</tt>
+<tt class="literal">level</tt> option as well. As this can often generate
+multitudes of error logs, it can be more efficient to use your own
+script&mdash;by setting the <tt class="literal">passwd</tt>
+<tt class="literal">program</tt> option&mdash;in place of
+<em class="filename">/bin/passwd</em> to record what happens during the
+exchange. Be careful because the log file contains the passwords in
+plain text. Keeping files containing plain-text passwords can (or
+<em class="emphasis">should</em>) be against local security policy in your
+organization, and it also might raise serious legal issues. Make sure
+to protect your log files with strict file permissions and to delete
+them as soon as you've grabbed the information you
+need. If possible, use the <tt class="literal">passwd</tt>
+<tt class="literal">chat</tt> <tt class="literal">debug</tt> option only while
+your own password is being changed.</p>
+
+<p>The operating system on which Samba is running might have strict
+requirements for valid passwords to make them more impervious to
+dictionary attacks and the like. Users should be made aware of these
+restrictions when changing their passwords.</p>
+
+<p>Earlier we said that password synchronization is limited. This is
+because there is no reverse synchronization of the encrypted
+<em class="filename">smbpasswd</em> file when a standard Unix password is
+updated by a user. There are various strategies to get around this,
+including NIS and freely available implementations of the Pluggable
+Authentication Modules (PAM) standard, but none of them really solves
+all the problems.</p>
+
+<p>More information regarding passwords can be found in the in the Samba
+source distribution file
+<em class="filename">docs/htmldocs/ENCRYPTION.html</em>.<a name="INDEX-80"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-4.4"/>
+
+<h3 class="head2">Password Configuration Options</h3>
+
+<p><a name="INDEX-81"/><a name="INDEX-82"/>The options in <a href="ch09.html#samba2-CHP-9-TABLE-8">Table 9-8</a> will help you work with passwords in Samba.</p>
+
+<a name="samba2-CHP-9-TABLE-8"/><h4 class="head4">Table 9-8. Password configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">encrypt</tt> <tt class="literal">passwords</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, enables encrypted passwords.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">unix password</tt> <tt class="literal">sync</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, updates the standard Unix password
+database when a user changes his encrypted password.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">passwd chat</tt></p>
+</td>
+<td>
+<p>string (chat commands)</p>
+</td>
+<td>
+<p>Sequence of commands sent to the password program.</p>
+</td>
+<td>
+<p>See earlier section on this option</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">passwd chat</tt> <tt class="literal">debug</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, sends debug logs of the password-change
+process to the log files with a level of 100.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">passwd program</tt></p>
+</td>
+<td>
+<p>string (Unix command)</p>
+</td>
+<td>
+<p>Program to be used to change passwords.</p>
+</td>
+<td>
+<p><tt class="literal">/bin/passwd</tt> <tt class="literal">%u</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">password level</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Number of capital-letter permutations to attempt when matching a
+client's password.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">update</tt> <tt class="literal">encrypted</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, updates the encrypted password file when a
+client connects to a share with a plain-text password.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">null passwords</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows access for users with null
+passwords.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">smb passwd file</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>Name of the encrypted password file.</p>
+</td>
+<td>
+<p><tt class="literal">/usr/local/samba/private/smbpasswd</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">hosts equiv</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>Name of a file that contains hosts and users that can connect without
+using a password.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">use rhosts</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>Name of a .<em class="emphasis">rhosts</em> file that allows users to
+connect without using a password.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.1"/>
+
+<h3 class="head3">encrypt passwords</h3>
+
+<p>The <tt class="literal">encrypt</tt><a name="INDEX-83"/>
+<tt class="literal">passwords</tt> global option switches Samba from using
+plain-text passwords to encrypted passwords for authentication.
+Encrypted passwords will be expected from clients if the option is
+set to <tt class="literal">yes</tt>:</p>
+
+<blockquote><pre class="code">encrypt passwords = yes</pre></blockquote>
+
+<p>In Samba 2.2.x versions and with previous versions, encrypted
+passwords are disabled by default. This was changed in Samba 3.0 to
+make encrypted passwords enabled by default.</p>
+
+<p>If you use encrypted passwords, you must have a valid
+<em class="filename">smbpasswd</em> file in place and populated with
+usernames that authenticate with encrypted passwords. (See <a href="ch09.html#samba2-CHP-9-SECT-4.2">Section 9.4.2</a> earlier in
+this chapter.) In addition, Samba must know the location of the
+<em class="filename">smbpasswd</em> file; if it is not in the default
+location (typically
+<em class="filename">/usr/local/samba/private/smbpasswd</em> ), you can
+explicitly name it using the <tt class="literal">smb</tt>
+<tt class="literal">passwd</tt> <tt class="literal">file</tt> option.</p>
+
+<p>If you wish, you can use <tt class="literal">update</tt>
+<tt class="literal">encrypted</tt> to force Samba to update the
+<em class="filename">smbpasswd</em> file with encrypted passwords each
+time a client connects using a nonencrypted password.</p>
+
+<p>If you have a mixture of clients on your network, with some of them
+using encrypted passwords and others using plain-text passwords, you
+can use the <tt class="literal">include</tt> option to make Samba treat
+each client appropriately. To do this, create individual
+configuration files based on the client name (<tt class="literal">%m</tt>).
+These host-specific configuration files can contain an
+<tt class="literal">encrypted</tt> <tt class="literal">passwords</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> option that activates
+only when those clients are connecting to the server.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.2"/>
+
+<a name="INDEX-84"/><h3 class="head3">unix password sync</h3>
+
+<p>The <tt class="literal">unix</tt> <tt class="literal">password</tt>
+<tt class="literal">sync</tt> global option allows Samba to update the
+standard Unix password file when a user changes her encrypted
+password. The encrypted password is stored on a Samba server in the
+<em class="filename">smbpasswd</em> file, which is located by default in
+<em class="filename">/usr/local/samba/private</em>. You can activate this
+feature as follows:</p>
+
+<blockquote><pre class="code">[global]
+    unix password sync = yes</pre></blockquote>
+
+<p>If this option is enabled, Samba changes the encrypted password and,
+in addition, attempts to change the standard Unix password by passing
+the username and new password to the program specified by the
+<tt class="literal">passwd</tt> <tt class="literal">program</tt> option
+(described earlier). Note that Samba does not necessarily have access
+to the plain-text password for this user, so the password changing
+program must be invoked as <tt class="literal">root</tt>.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> If the Unix password change does not
+succeed, for whatever reason, the SMB password is not changed either.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.3"/>
+
+<a name="INDEX-85"/><h3 class="head3">passwd chat</h3>
+
+<p>This option specifies a series of send/response strings similar to a
+Unix chat script, which interface with the password-changing program
+on the Samba server. <a href="ch09.html#samba2-CHP-9-SECT-4.3">Section 9.4.3</a> earlier in this
+chapter covers this option in detail.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.4"/>
+
+<h3 class="head3">passwd chat debug</h3>
+
+<p>If set to <tt class="literal">yes</tt>, the
+<tt class="literal">passwd</tt><a name="INDEX-86"/> <tt class="literal">chat</tt>
+<tt class="literal">debug</tt> global option logs everything sent or
+received by Samba during a password chat. All the I/O received by
+Samba through the password chat is sent to the Samba logs with a
+debug level of 100; you must specify <tt class="literal">log</tt>
+<tt class="literal">level</tt> <tt class="literal">=</tt> <tt class="literal">100</tt>
+for the information to be recorded. <a href="ch09.html#samba2-CHP-9-SECT-4.3">Section 9.4.3</a> earlier in this
+chapter describes this option in more detail. Be aware that if you do
+set this option, the plain-text passwords will be visible in the
+debugging logs, which could be a security hazard if they are not
+properly secured. It is against the security policy of some
+organizations for system administrators to have access to
+users' passwords.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.5"/>
+
+<h3 class="head3">passwd program</h3>
+
+<p>The <tt class="literal">passwd</tt><a name="INDEX-87"/>
+<tt class="literal">program</tt> option specifies a program on the Unix
+Samba server that Samba can use to update the standard system
+password file when the encrypted password file is updated. This
+option defaults to the standard <em class="emphasis">passwd</em> program,
+usually located in the <em class="filename">/bin</em> directory. The
+<tt class="literal">%u</tt> variable is typically used as the requesting
+user when the command is executed. The actual handling of input and
+output to this program during execution is handled through the
+<tt class="literal">passwd</tt> <tt class="literal">chat</tt> option. <a href="ch09.html#samba2-CHP-9-SECT-4.3">Section 9.4.3</a> earlier in this
+chapter covers this option in detail.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.6"/>
+
+<a name="INDEX-88"/><h3 class="head3">password level</h3>
+
+<p>With SMB, nonencrypted (or plain-text) passwords are sent with
+capital letters, just like the usernames mentioned previously. Many
+Unix users, however, choose passwords with both upper- and lowercase
+letters. Samba, by default, only attempts to match the password
+entirely in lowercase letters and not capitalizing the first letter.</p>
+
+<p>Like <tt class="literal">username</tt> <tt class="literal">level</tt>, a
+<tt class="literal">password</tt> <tt class="literal">level</tt> option can be
+used to attempt various permutations of the password with capital
+letters. This option takes an integer value that specifies how many
+letters in the password should be capitalized when attempting to
+connect to a share. You can specify this option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    password level = 3</pre></blockquote>
+
+<p>In this case, Samba then attempts all permutations of the password it
+can compute having three capital letters. The larger the number, the
+more computations Samba has to perform to match the password, and the
+longer a connection to a specific share might take.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.7"/>
+
+<a name="INDEX-89"/><h3 class="head3">update encrypted</h3>
+
+<p>For sites switching over to the encrypted password format, Samba
+provides an option that should help with the transition. The
+<tt class="literal">update</tt> <tt class="literal">encrypted</tt> option allows
+a site to ease into using encrypted passwords from plain-text
+passwords. You can activate this option as follows:</p>
+
+<blockquote><pre class="code">[global]
+    update encrypted = yes</pre></blockquote>
+
+<p>This instructs Samba to create an encrypted version of each
+user's Unix password in the
+<em class="filename">smbpasswd</em> file each time she connects to a
+share. When this option is enabled, you must have the
+<tt class="literal">encrypt</tt> <tt class="literal">passwords</tt> option set to
+<tt class="literal">no</tt> so that the client passes plain-text passwords
+to Samba to update the files. Once each user has connected at least
+once, you can set <tt class="literal">encrypted</tt>
+<tt class="literal">passwords</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt>, allowing you to use only the encrypted
+passwords. The user must already have a valid entry in the
+<em class="filename">smbpasswd</em> file for this option to work.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.8"/>
+
+<a name="INDEX-90"/><h3 class="head3">null passwords</h3>
+
+<p>This global option tells Samba whether to allow access from users
+that have null passwords (encrypted or nonencrypted) set in their
+accounts. The default value is <tt class="literal">no</tt>. You can
+override it as follows:</p>
+
+<blockquote><pre class="code">null passwords = yes</pre></blockquote>
+
+<p>We highly recommend against doing so because of the security risks
+this option can present to your system, including inadvertent access
+to system users (such as <tt class="literal">bin</tt>) in the system
+password file who have null passwords set.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.9"/>
+
+<a name="INDEX-91"/><h3 class="head3">smb passwd file</h3>
+
+<p>This global option identifies the location of the encrypted password
+database. By default, it is set to
+<em class="filename">/usr/local/samba/private/smbpasswd</em>. You can
+override it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    smb passwd file = /etc/samba/smbpasswd</pre></blockquote>
+
+<p>This location, for example, is common on many Red Hat distributions
+on which Samba has been installed using an RPM package.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.10"/>
+
+<a name="INDEX-92"/><h3 class="head3">hosts equiv</h3>
+
+<p>This global option specifies the name of a standard Unix
+<em class="filename">hosts.equiv</em> file that allows hosts or users to
+access shares without specifying a password. You can specify the
+location of such a file as follows:</p>
+
+<blockquote><pre class="code">[global]
+    hosts equiv = /etc/hosts.equiv</pre></blockquote>
+
+<p>The default value for this option does not specify any
+<em class="filename">hosts.equiv</em> file. Because using a
+<em class="filename">hosts.equiv</em> file is a huge security risk, we
+strongly recommend against using this option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-4.4.11"/>
+
+<a name="INDEX-93"/><h3 class="head3">use rhosts</h3>
+
+<p>This global option specifies the name of a standard Unix
+user's <em class="filename">.rhosts</em> file that allows
+foreign hosts to access shares without specifying a password. You can
+specify the location of such a file as follows:</p>
+
+<blockquote><pre class="code">[global]
+    use rhosts = /home/dave/.rhosts</pre></blockquote>
+
+<p>The default value for this option does not specify any
+<em class="filename">.rhosts</em> file. Like the <tt class="literal">hosts</tt>
+<tt class="literal">equiv</tt> option discussed earlier, using such a file
+is a security risk. We highly recommend that you do not use this
+option unless you are confident in the security of your network.
+<a name="INDEX-94"/>
+<a name="INDEX-95"/><a name="INDEX-96"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-9-SECT-5"/>
+
+<h2 class="head1">Authentication with winbind</h2>
+
+<p><a name="INDEX-97"/><a name="INDEX-98"/>In <a href="ch03.html">Chapter 3</a>, we
+showed you how to add Windows clients to a network in which user
+accounts were maintained on the Samba server. We added a user account
+to the Windows client using the same username and password as an
+account on the Unix system. This method works well in many computing
+environments. However, if a Samba server is added to a Windows
+network that already has a Windows NT/2000 primary domain controller,
+the PDC has a preexisting database of user accounts and group
+information that is used for authentication. It can be a big chore to
+transfer that database manually to the Unix server, and later
+maintain and synchronize the Unix and Windows databases.</p>
+
+<p>In <a href="ch04.html">Chapter 4</a>, we showed you how to add a Samba
+server as a domain member server to a network having a Windows
+NT/2000 primary domain controller. We set <tt class="literal">security</tt>
+<tt class="literal">=</tt> <tt class="literal">domain</tt> in the Samba
+configuration file to have the Samba server hand off authentication
+to the Windows PDC. Using that method, passwords are kept only on the
+PDC, but it is still necessary to set up user accounts on the Unix
+side to make sure each client has a valid Unix UID and group ID
+(GID). This is necessary for maintaining the file ownerships and
+permissions of the Unix security model. Whenever Samba performs an
+operation on the Unix filesystem on behalf of the Windows client, the
+user must have a valid UID and GID on the local Unix system.</p>
+
+<p>A facility that has recently been added to Samba, winbind, allows the
+Windows <a name="INDEX-99"/>PDC to handle
+not only authentication, but the user and group information as well.
+Winbind works by extending the Unix user and group databases beyond
+the standard <em class="filename">/etc/passwd</em> and
+<em class="filename">/etc/group</em> files such that users and groups on
+the Windows PDC also exist as valid users and groups on the Unix
+system. The extension applies to the entire Unix system and allows
+users who are members of a Windows domain to perform any action on
+the Unix system that a local user would, including logging in to the
+Unix system by <em class="emphasis">telnet</em> or even on the local
+system, using their domain usernames and passwords.</p>
+
+<p>When winbind is in use, administration of user accounts can be done
+on the Windows PDC, without having to repeat the tasks on the Unix
+side. This includes password expiration and allowing users to change
+their passwords, which would otherwise not be practical. Aside from
+simplifying domain administration and being a great time saver,
+winbind lets Samba be used in computing environments where it
+otherwise might not be allowed.</p>
+<a name="samba2-CHP-9-NOTE-143"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Because this is a chapter on security, we want to point out that some
+issues might relate to allowing a Windows system to authenticate
+users accessing a Unix system! Whatever you might think of the
+relative merits of Unix and Windows security models (and even more
+importantly, their <em class="emphasis">implementations</em>), one thing
+is certain: adding winbind support to your Samba server greatly
+complicates the authentication system overall&mdash;and quite
+possibly allows more opportunities for crackers.</p>
+
+<p>We present winbind in this chapter not as a means of improving
+security, but rather as a further example of Samba's
+ability to integrate itself into a modern Windows environment.</p>
+</blockquote>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-5.1"/>
+
+<h3 class="head2">Installing winbind</h3>
+
+<p><a name="INDEX-100"/>Installing
+and configuring winbind is fairly complicated and involves the
+following steps:</p>
+
+<ol><li>
+<p>Reconfigure, recompile, and reinstall Samba&mdash;to add support for
+winbind.</p>
+</li><li>
+<p>Configure the Unix name server switch.</p>
+</li><li>
+<p>Modify the Samba configuration file.</p>
+</li><li>
+<p>Start and test the <em class="emphasis">winbindd</em> daemon.</p>
+</li><li>
+<p>Configure the system to start and stop the
+<em class="emphasis">winbindd</em> daemon automatically.</p>
+</li><li>
+<p>Optionally, configure PAM for use with winbind.</p>
+</li></ol>
+<p>At the time this book was written, winbind was supported only on
+Linux, so all of the following directions are specific to it. Other
+Unix flavors might be supported at a later time. In addition, we
+assume you have a Windows NT/2000 primary domain controller running
+on your network.</p>
+
+<p>First, you will need to configure and compile Samba using the
+<tt class="literal">--with-winbind</tt> configure option. Directions for
+doing this are included in <a href="ch02.html">Chapter 2</a> in <a href="ch02.html#samba2-CHP-2-SECT-3">Section 2.3</a>. As usual, run
+<em class="emphasis">make install</em> to reinstall the Samba binaries.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-5.2"/>
+
+<h3 class="head2">Configuring nsswitch</h3>
+
+<p><a name="INDEX-101"/>When
+Samba is compiled after being configured with the
+<tt class="literal">--with-winbind</tt> option, the compilation process
+produces a library called
+<em class="filename">libnss_winbind.so</em><a name="INDEX-102"/> in the
+<em class="filename">source/nsswitch</em> directory. This library needs to
+be copied to the <em class="filename">/lib</em> directory:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>cp nsswitch/libnss_winbind.so /lib</b></tt></pre></blockquote>
+
+<p>Also, a symbolic link must be created for winbind to be fully
+functional:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</b></tt></pre></blockquote>
+
+<a name="samba2-CHP-9-NOTE-144"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The name of this symbolic link is correct for Samba 2.2.3 and Red Hat
+7.1. The name might change&mdash;with a higher version number in the
+extension&mdash;in future releases. See the
+<em class="emphasis">winbindd</em> manual page for details.</p>
+</blockquote>
+
+<p>Next, we need to modify <em class="filename">/etc/nsswitch.conf</em> to
+make the lines for <tt class="literal">passwd</tt> and
+<tt class="literal">group</tt> look like this:</p>
+
+<blockquote><pre class="code">passwd:     files winbind
+group:      files winbind</pre></blockquote>
+
+<p>Then activate these changes by issuing the following command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/sbin/ldconfig</b></tt></pre></blockquote>
+
+<p>What we've just done is reconfigure the Linux name
+service switch, which allows name service and other tasks to be
+configured to use the traditional method (files in the
+<em class="filename">/etc</em> directory) or an extension coded in a
+library, such as the <em class="filename">libnss_winbind.so</em> library
+we've just installed. We've
+specified in our configuration that Samba will search for user and
+group information first in the <em class="filename">/etc/passwd</em> and
+<em class="filename">/etc/group files</em>, and if they are not found
+there, in the winbind service.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-5.3"/>
+
+<h3 class="head2">Modifying smb.conf</h3>
+
+<p><a name="INDEX-103"/><a name="INDEX-104"/>To use winbind, we must have our Samba
+server added to the Windows NT domain as a domain member server (as
+we described in <a href="ch04.html">Chapter 4</a>) and also add some
+parameters to the Samba configuration file to configure winbind. In
+addition to the options required to configure Samba as a domain
+member server, we need:</p>
+
+<blockquote><pre class="code">[global]
+    winbind uid = 10000-20000
+    winbind gid = 10000-20000</pre></blockquote>
+
+<p>The <tt class="literal">winbind</tt> <tt class="literal">uid</tt> and
+<tt class="literal">winbind</tt> <tt class="literal">gid</tt> options tell
+winbind how to map between Windows relative identifiers (RIDs) and
+Unix UIDs and GIDs. Windows uses RIDs to identify users and groups
+within the domain, and to function, the Unix system must have a UID
+and GID associated with every user and group RID that is received
+from the Windows primary domain controller. The
+<tt class="literal">winbind</tt> <tt class="literal">uid</tt> and
+<tt class="literal">winbind</tt> <tt class="literal">gid</tt> parameters simply
+provide winbind with a range of UIDs and GIDs, respectively, that are
+allocated by the system administrator for Windows NT domain users and
+groups. You can use whatever range you want for each; just make sure
+the lowest number in the range does not conflict with any entries in
+your <em class="filename">/etc/passwd</em> or
+<em class="filename">/etc/group</em> files at any time, either now or in
+the future. It is important to be conservative about this. Once
+winbind adds an RID to UID/GID mapping to its database, it is very
+difficult to modify the mapping.</p>
+<a name="samba2-CHP-9-NOTE-145"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p><a name="INDEX-105"/>The file
+<em class="filename">/usr/local/samba/locks/winbindd_idmap.tdb</em>
+contains winbind's RID mapping file by default. We
+suggest you regard this file as extremely sensitive and make sure to
+guard it carefully against any kind of harm or loss. If you lose it,
+you will have to re-create it manually, which can be a very
+labor-intensive task.</p>
+</blockquote>
+
+<a name="samba2-CHP-9-NOTE-145a"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>Be careful when adding local users after domain users have started
+accessing the Samba server. The domain users will have entries
+created for them by winbind in <em class="filename">/etc/passwd,</em> with
+UIDs in the range you specify. If you are using a method of creating
+new accounts that automatically assigns UIDs, it might choose UIDs by
+adding 1 to the highest UID assigned thus far, which will be the most
+recent UID added by winbind. (This is the case on Red Hat Linux, with
+the <em class="emphasis">useradd</em> script, for example.) The UID for
+the new local user will be within the range allocated for winbind,
+which will have undesired effects. Make sure to add new local users
+using a method that assigns them UIDs in the proper range. For
+example, you can use the <em class="emphasis">-u</em> option of
+<em class="emphasis">useradd</em> to specify the UID to assign to the new
+user.</p>
+</blockquote>
+
+<p>Restart the Samba daemons to put your changes to the configuration
+file into effect. If you have not already done so while adding your
+Samba server as a domain member server, you must issue the command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -j </b></tt><em class="replaceable">domain</em><tt class="userinput"><b> -r </b></tt><em class="replaceable">pdc</em><tt class="userinput"><b> -U Administrator</b></tt></pre></blockquote>
+
+<p>as we described in <a href="ch04.html">Chapter 4</a>. At this point, you
+can start the <em class="emphasis">winbindd</em> daemon:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>winbindd</b></tt></pre></blockquote>
+
+<p><a name="INDEX-106"/>You might want to
+run a <em class="emphasis">ps ax</em> command to see that the
+<em class="emphasis">winbindd</em> daemon is running. Now, to make sure
+everything we've done up to this point works, we can
+use Samba's <em class="emphasis">wbinfo</em> command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>wbinfo -u</b></tt>
+METRAN\Administrator
+METRAN\bebe
+METRAN\Guest
+METRAN\jay
+METRAN\linda
+$ <tt class="userinput"><b>wbinfo -g</b></tt>
+METRAN\Domain Admins
+METRAN\Domain Guests
+METRAN\Domain Users</pre></blockquote>
+
+<p>The <em class="emphasis">-u</em> option queries the domain controller for
+a list of domain users, and the <em class="emphasis">-g</em> option asks
+for the list of groups. The output shows that the Samba host system
+can query the Windows PDC through winbind.</p>
+
+<p>Another thing to check is the list of users and groups, using the
+<em class="emphasis">getent</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>getent passwd</b></tt>
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:
+daemon:x:2:2:daemon:/sbin:
+    <i class="lineannotation">... deleted ...</i>
+jay:x:500:500:Jay Ts:/home/jay:/bin/bash
+rik:x:501:501::/home/rik:/bin/bash
+METRAN\Administrator:x:10000:10000::/home/METRAN/administrator:/bin/bash
+METRAN\bebe:x:10001:10000:Bebe Larta:/home/METRAN/bebe:/bin/bash
+METRAN\Guest:x:10002:10000::/home/METRAN/guest:/bin/bash
+METRAN\jay:x:10003:10000:Jay Ts:/home/METRAN/jay:/bin/bash
+METRAN\linda:x:10004:10000:Linda Lewis:/home/METRAN/linda:/bin/bash
+
+# getent group
+root:x:0:root
+bin:x:1:root,bin,daemon
+daemon:x:2:root,bin,daemon
+    <i class="lineannotation">... deleted ...</i>
+jay:x:500:
+rik:x:501:
+METRAN\Domain Admins:x:10001:METRAN\Administrator
+METRAN\Domain Guests:x:10002:METRAN\Guest
+METRAN\Domain Users:x:10000:METRAN\Administrator,METRAN\jay,METRAN\linda,METRAN\bebe</pre></blockquote>
+
+<p>This shows that the Linux system is finding the domain users and
+groups through winbind, in addition to those in the
+<em class="filename">/etc/passwd</em> and <em class="filename">/etc/group</em>
+files. If this part doesn't work as shown earlier,
+with the domain users and groups listed after the local ones, check
+to make sure you made the symbolic link to
+<em class="filename">libnss_winbind.so</em> in <em class="filename">/lib</em>
+correctly.</p>
+
+<p>Now you can try connecting to a Samba share from a Windows system
+using a domain account. You can either log on to the domain from a
+Windows NT/2000/XP workstation or use <em class="emphasis">smbclient</em>
+with the <em class="emphasis">-U</em> option to specify a username.</p>
+
+<a name="samba2-CHP-9-NOTE-147"/><blockquote class="note"><h4 class="objtitle">NOTE</h4>
+<p>If you get errors while attempting to log on to the domain, it is
+probably because you had previously configured the client system with
+a computer account on another domain controller. Commonly, you get a
+dialog box that says, &quot;The domain
+<em class="replaceable">NAME</em> is not available.&quot;
+On a Windows 2000 system, the fix is to log in to the system as an
+administrative user and open the Control Panel, double-click the
+System icon, click the Network Identification tab, then click the
+Properties button. In the dialog that comes up, click the
+&quot;Workgroup:&quot; radio button and fill
+in the name of the workgroup (you can use the same name as the
+domain). Click the OK buttons in the dialogs, and reboot if
+requested.</p>
+
+<p>This removes the computer account from the primary domain controller.
+Now log in again as the administrative user and repeat the previous
+directions, but change from the workgroup back to the domain. This
+creates a new computer account that
+&quot;fits&quot; the workstation to the new
+primary domain controller. If your network has backup domain
+controllers, it will take up to 15 minutes for the new computer
+account to propagate to the BDCs.</p>
+
+<p>If you are using Windows NT/XP, the method is slightly different. For
+the exact procedure, see the section in <a href="ch04.html">Chapter 4</a>
+that is specific to your Windows version.</p>
+</blockquote>
+
+<p>After logging in as a domain user, try creating a file or two in a
+Samba share. (You might need to change the permissions on the shared
+directory&mdash;say, to 777&mdash;to allow this access. This is very
+permissive, but after you finish reading this section, you will
+understand how to change ownership and permissions on the directory
+to restrict access to selected domain users.) After
+you've created files by one or more domain users,
+take a look at the directory's contents from a Linux
+shell. You will see something like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ls -l /u</b></tt>
+-rwxrw-rw-    1 METRAN\b METRAN\D        0 Apr 13 00:00 bebes-file.doc
+-rwxrw-rw-    1 METRAN\l METRAN\D        0 Apr 12 23:58 lindas-file.doc
+drwxrwxr-x    6 jay      jay          4096 Jan 15 05:12 snd
+<b class="emphasis-bold">$ ls -ln /u</b>
+total 4
+-rwxrw-rw-    1 10001    10000           0 Apr 13 00:00 bebes-file.doc
+-rwxrw-rw-    1 10004    10000           0 Apr 12 23:58 lindas-file.doc
+drwxrwxr-x    6 500      500          4096 Jan 15 05:12 snd</pre></blockquote>
+
+<p>We can even use the domain usernames and groups from the Linux shell:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>chown 'METRAN\linda:METRAN\Domain Users' /u</b></tt>
+# <tt class="userinput"><b>ls -ldu /u</b></tt>
+drwxrwxrwx    3 METRAN\l METRAN\D     4096 Apr 13 00:44 /u
+# <tt class="userinput"><b>ls -ldn /u</b></tt>
+drwxrwxrwx    3 10004    10000        4096 Apr 13 00:00 /u</pre></blockquote>
+
+<p>Notice how the owner and group are listed as being those of the
+domain user and group. Unfortunately, the GNU <em class="emphasis">ls</em>
+command won't show the full names of the domain
+users and groups, but we can use the <em class="emphasis">-ln</em> listing
+to show the UIDs and GIDs and then translate with the
+<em class="emphasis">wbinfo</em> command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>wbinfo -s `wbinfo -U 10004`</b></tt>
+METRAN\LINDA 1
+$ <tt class="userinput"><b>wbinfo -s `wbinfo -G 10000`</b></tt>
+METRAN\Domain Users 2</pre></blockquote>
+
+<p>(It's a bit messy, but it works, and it shows that
+the winbind system is working!) At this point, you might want to
+modify your <em class="filename">/etc/rc.d/init.d/smb</em> script to start
+and stop the <em class="emphasis">winbindd</em> daemon automatically along
+with the <em class="emphasis">smbd</em> and <em class="emphasis">nmbd</em>
+daemons. Starting with the script we presented in <a href="ch02.html">Chapter 2</a>, we first add this code to the
+<em class="emphasis">start( )</em> function:</p>
+
+<blockquote><pre class="code">echo -n $&quot;Starting WINBIND services: &quot;
+/usr/local/samba/bin/winbindd
+ERROR2=$?
+if [ $ERROR2 -ne 0 ]
+then
+    ERROR=1
+fi
+echo</pre></blockquote>
+
+<p>The previous code should be located after the code that starts
+<em class="emphasis">nmbd</em> and before the <em class="emphasis">return</em>
+statement.</p>
+
+<a name="samba2-CHP-9-NOTE-148"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>We start <em class="emphasis">winbindd</em> after
+<em class="emphasis">nmbd</em> because <em class="emphasis">winbindd</em> needs
+<em class="emphasis">nmbd</em> to be running to work properly.</p>
+</blockquote>
+
+<p>In the <tt class="function">stop( )</tt> function, we add the following:</p>
+
+<blockquote><pre class="code">echo -n $&quot;Shutting down WINBIND services: &quot;
+/bin/kill -TERM -a winbindd
+ERROR2=$?
+if [ $ERROR2 -ne 0 ]
+then
+    ERROR=1
+fi
+echo</pre></blockquote>
+
+<p>Again, this code should be located after the code that stops
+<em class="emphasis">nmbd</em> and before the <em class="emphasis">return</em>
+statement. <a name="INDEX-107"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-5.4"/>
+
+<h3 class="head2">Configuring PAM</h3>
+
+<p><a name="INDEX-108"/>Most
+popular Linux distributions use <a name="INDEX-109"/>Pluggable
+Authentication Modules (PAM), a suite of shared libraries that
+provide a centralized source of authentication for applications
+running on the Unix system. PAM can be configured differently for
+each application (or service) that uses it, without needing to
+recompile the application. As a hypothetical example, if an
+organization's security policy mandated the use of
+passwords exactly 10 characters in length, a PAM module could be
+written to check the length of passwords submitted by users and
+reject any attempts to use a longer or shorter password. PAM would
+then be reconfigured to include the new module for services such as
+<em class="emphasis">ftp</em>, console login, and GUI login that call upon
+PAM to authenticate users.</p>
+
+<p>If you are not already familiar with PAM, we suggest you read the
+documentation provided with the Linux PAM package before continuing.
+On most Linux systems, it is located in the
+<em class="filename">/usr/share/doc</em> directory hierarchy. Another
+resource is the <em class="citetitle">Linux-PAM System
+Administrator's
+Guide</em><a name="INDEX-110"/>, which you can find
+on the Internet at <a href="http://www.kernel.org/pub/linux/libs/pam">http://www.kernel.org/pub/linux/libs/pam</a>.</p>
+
+<p>The rest of this section is about using the PAM module provided in
+the Samba distribution to enable Windows domain users to authenticate
+on the Linux system hosting Samba. Depending on which services you
+choose to configure, this allows Windows domain users to log in on a
+local console (or through <em class="emphasis">telnet</em>), log in to a
+GUI desktop on the Linux system, authenticate with an FTP server
+running on the Linux system, or use other services normally limited
+to users who have an account on the Linux system. The PAM module
+authenticates Windows domain users by querying winbind, which passes
+the authentication off to a Windows NT domain controller.</p>
+
+<p>As an example, we will show how to allow Windows domain users to log
+in to a text console on the Linux system and get a command shell and
+home directory. The method used in our example can be applied (with
+variations) to other services.</p>
+
+<p>All users who can log in to the Linux system need a shell and a home
+directory. Unix and Linux keep this user information in the password
+file (<em class="filename">/etc/passwd</em> ), but information about
+Windows users isn't located there. Instead, in the
+Samba configuration file, we add the following to notify winbind what
+the shell and home directory for Windows domain users will be:</p>
+
+<blockquote><pre class="code">[global]
+    template shell = /bin/bash
+    template homedir = /home/%D/%U</pre></blockquote>
+
+<p>The first line sets the
+<tt class="literal">template</tt><a name="INDEX-111"/> <tt class="literal">shell</tt>
+parameter, which tells winbind what shell to use for domain users
+that are logging in to the Unix host. The
+<tt class="literal">template</tt><a name="INDEX-112"/>
+<tt class="literal">homedir</tt> parameter specifies the location of
+users' home directories. The <tt class="literal">%D</tt>
+variable is replaced by the name of the domain in which the
+user's account resides, and <tt class="literal">%U</tt> is
+replaced by the user's username in that domain.</p>
+
+<p>Before the domain users can successfully log in, their home
+directories must be created manually. To add a single account for
+<tt class="literal">linda</tt> in the METRAN domain, we would use these
+commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mkdir /home/METRAN</b></tt>
+# <tt class="userinput"><b>chmod 755 /home/METRAN</b></tt>
+
+# <tt class="userinput"><b>mkdir /home/METRAN/linda</b></tt>
+# <tt class="userinput"><b>chown 'METRAN\linda:METRAN\Domain Users' /home/METRAN/linda</b></tt>
+# <tt class="userinput"><b>chmod 700 /home/METRAN/linda</b></tt></pre></blockquote>
+<a name="samba2-CHP-9-NOTE-149"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>One side effect of creating the home directories is that if the Samba
+server is configured with a <tt class="literal">[homes]</tt> share, the
+domain users can see and access their home directories through
+Samba's file sharing.</p>
+</blockquote>
+
+<p>Next, we need to compile and install the PAM module in the Samba
+distribution. From the source directory in the Samba distribution,
+issue the following commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>make nsswitch/pam_winbind.so</b></tt>
+# <tt class="userinput"><b>cp nsswitch/pam_winbind.so /lib/security</b></tt></pre></blockquote>
+
+<p>and check that it was copied over correctly:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ls /lib/security/pam_winbind.so</b></tt>
+/lib/security/pam_winbind.so</pre></blockquote>
+
+<p>On Red Hat Linux, the PAM configuration files reside in
+<em class="filename">/etc/pam.d</em>. Before making any modifications, we
+strongly advise making a backup of this directory:</p>
+
+<blockquote><pre class="code"># cp -pR /etc/pam.d /etc/pam.d.backup</pre></blockquote>
+
+<p>The reason for this is that we will be modifying the Linux
+system's means of authenticating logins, and if our
+configuration goes awry, all users (including
+<tt class="literal">root</tt>) will be locked out of the system. In case
+the worst happens, we would reboot into single-user mode (by typing
+<tt class="literal">linux</tt> <tt class="literal">single</tt> at the LILO:
+prompt) or boot a rescue disk, and then we would issue these two
+commands:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>mv /etc/pam.d /etc/pam.d.bad</b></tt>
+# <tt class="userinput"><b>mv /etc/pam.d.backup /etc/pam.d</b></tt></pre></blockquote>
+
+<p>Be very careful to make sure you can recover from any errors you make
+because when PAM encounters any configuration information it
+doesn't understand, its action is not to allow
+access. This means you must be sure to enter everything correctly!
+You might want to leave yourself logged in as root on a spare virtual
+terminal while you are modifying your PAM configuration to ensure
+yourself a means of easy recovery.</p>
+
+<p>In the <em class="filename">/etc/pam.d</em> directory, you will encounter
+a file for each service that uses PAM. We are interested only in the
+file corresponding to the login service, which is called
+<em class="filename">login</em>. It contains the following lines:</p>
+
+<blockquote><pre class="code">auth       required     /lib/security/pam_securetty.so
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_nologin.so
+account    required     /lib/security/pam_stack.so service=system-auth
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so</pre></blockquote>
+
+<p>The lines starting with <tt class="literal">auth</tt> are related to the
+function of authentication&mdash;that is, printing a password prompt,
+accepting the password, verifying that it is correct, and matching
+the user to a valid user and group ID. The line starting with
+<tt class="literal">account</tt> is for account management, which allows
+access to be controlled by other factors, such as what times during
+the day a user is allowed access. We are not concerned with the lines
+starting with <tt class="literal">password</tt> or
+<tt class="literal">session</tt> because winbind does not add to either of
+those functions.</p>
+
+<p>The third column lists the PAM module, possibly with arguments, that
+is called in for the task. The
+<em class="filename">pam_stack.so</em><a name="INDEX-113"/> module has been added by Red Hat to act
+somewhat like a macro or a subroutine. It calls the file in the
+<em class="filename">pam.d</em> directory named by the service argument.
+In this case, the file <em class="filename">/etc/pam.d/system-auth</em>
+contains a common set of lines that are used as a default for many
+services. Because we want to customize the login service for winbind,
+we first replace the <em class="filename">pam_stack.so</em> lines for
+<tt class="literal">auth</tt> and <tt class="literal">account</tt> with the
+<tt class="literal">auth</tt> and <tt class="literal">account</tt> lines from
+<em class="filename">/etc/pam.d/system-auth</em>. This yields:</p>
+
+<blockquote><pre class="code">auth       required     /lib/security/pam_securetty.so
+<b class="emphasis-bold">auth       required     /lib/security/pam_env.so</b>
+<b class="emphasis-bold">auth       sufficient   /lib/security/pam_unix.so likeauth nullok</b>
+<b class="emphasis-bold">auth       required     /lib/security/pam_deny.so</b>
+auth       required     /lib/security/pam_nologin.so
+<b class="emphasis-bold">account    required     /lib/security/pam_unix.so</b>
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so</pre></blockquote>
+
+<p>To add winbind support, we need to add a line in both the
+<tt class="literal">auth</tt> and <tt class="literal">account</tt> sections to
+call the
+<em class="filename">pam_winbind.so</em><a name="INDEX-114"/> module:</p>
+
+<blockquote><pre class="code">auth       required     /lib/security/pam_securetty.so
+auth       required     /lib/security/pam_env.so
+<b class="emphasis-bold">auth       sufficient   /lib/security/pam_winbind.so</b>
+auth       sufficient   /lib/security/pam_unix.so <b class="emphasis-bold">use_first_pass</b> likeauth nullok
+auth       required     /lib/security/pam_deny.so
+auth       required     /lib/security/pam_nologin.so
+<b class="emphasis-bold">account    sufficient   /lib/security/pam_winbind.so</b>
+account    required     /lib/security/pam_unix.so
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so</pre></blockquote>
+
+<p>The keywords <tt class="literal">required</tt> and
+<tt class="literal">sufficient</tt> in the second column are significant.
+The keyword <tt class="literal">required</tt> specifies that the result
+returned by the module (either to pass or fail the authentication)
+must be taken into account, whereas the keyword
+<tt class="literal">sufficient</tt> specifies that if the module
+successfully authenticates the user, no further lines need to be
+processed. By specifying <tt class="literal">sufficient</tt> for the
+<em class="filename">pam_winbind.so</em> module, we let winbind attempt to
+authenticate users, and if it succeeds, the PAM system returns to the
+application. If the <em class="filename">pam_winbind.so</em> module
+doesn't find the user or the password does not
+match, the PAM system continues with the next line, which performs
+authentication according to the usual Linux user authentication. This
+way, both domain users and local users can log in.</p>
+
+<p>Notice that we also added the <tt class="literal">use_first_pass</tt>
+argument to the <em class="filename">pam_unix.so</em> module in the
+<tt class="literal">auth</tt> section. By default, both the
+<em class="filename">pam_winbind.so</em> and
+<em class="filename">pam_unix.so</em> modules print a password prompt and
+accept a password. In cases where users are logging in to the Linux
+system using their local accounts, this would require them to enter
+their password twice. The <tt class="literal">user_first_pass</tt> argument
+tells the <em class="filename">pam_unix.so</em> module to reuse the
+password that was given to the <em class="filename">pam_winbind.so</em>
+module, which results in users having to enter the password only
+once.</p>
+
+<p>After modifying the <em class="filename">login</em> configuration file,
+switch to a spare virtual console and make sure you can still log in
+using a regular Linux account. If not, check your modifications
+carefully and try again until you get it right. Then log in using a
+domain user account from the Windows PDC database to check that the
+winbind authentication works. You will need to specify the username
+in <em class="replaceable">DOMAIN</em>\<em class="replaceable">user</em>
+format, like this:</p>
+
+<blockquote><pre class="code">login: METRAN\linda
+Password:</pre></blockquote>
+
+<p>More information on configuring winbind can be found in the Samba
+source distribution file
+<em class="filename">docs/htmldocs/winbind.html</em>, and in the
+<em class="emphasis">winbindd</em> manual page. If you would like to learn
+more about configuring PAM, we recommend the web page <a href="http://www.kernel.org/pub/linux/libs/pam/">http://www.kernel.org/pub/linux/libs/pam/</a> as
+a starting place. Some of the documentation for Linux PAM, including
+Red Hat's extensions, can also be found on Red Hat
+Linux in
+<em class="filename">/usr/share/doc/pam-</em><em class="replaceable">version</em>.
+<a name="INDEX-115"/></p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-9-SECT-5.5"/>
+
+<h3 class="head2">winbind Configuration Options</h3>
+
+<p><a href="ch09.html#samba2-CHP-9-TABLE-9">Table 9-9</a> <a name="INDEX-116"/><a name="INDEX-117"/>summarizes some commonly used options
+that you can use to configure winbind.</p>
+
+<a name="samba2-CHP-9-TABLE-9"/><h4 class="head4">Table 9-9. winbind options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">winbind</tt> <tt class="literal">separator</tt></p>
+</td>
+<td>
+<p>string (single character)</p>
+</td>
+<td>
+<p>Character to use as a separator in domain usernames and group names</p>
+</td>
+<td>
+<p>Backslash (<tt class="literal">\</tt>)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">winbind uid</tt></p>
+</td>
+<td>
+<p>string (numeric range)</p>
+</td>
+<td>
+<p>Range of UIDs for RID-to-UID mapping</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">winbind gid</tt></p>
+</td>
+<td>
+<p>string (numeric range)</p>
+</td>
+<td>
+<p>Range of GIDs for RID-to-GID mapping</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">winbind cache time</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Number of seconds the <em class="emphasis">winbindd</em> daemon caches
+user and group data</p>
+</td>
+<td>
+<p><tt class="literal">15</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">template</tt> <tt class="literal">homedir</tt></p>
+</td>
+<td>
+<p>string (directory name)</p>
+</td>
+<td>
+<p>Directory to be used as the home directory of the logged-in domain
+user</p>
+</td>
+<td>
+<p><tt class="literal">/home/%D/%U</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">template</tt> <tt class="literal">shell</tt></p>
+</td>
+<td>
+<p>string (command name)</p>
+</td>
+<td>
+<p>The program to use as the logged-in domain user's
+shell</p>
+</td>
+<td>
+<p><tt class="literal">/bin/false</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.1"/>
+
+<a name="INDEX-118"/><h3 class="head3">winbind separator</h3>
+
+<p>On Windows systems, the backslash (<tt class="literal">\</tt>) is commonly
+used as a separator in file names, UNCs, and the names of domain
+users and groups. For example, an account in the METRAN domain with a
+username of <tt class="literal">linda</tt> would be written as
+<tt class="literal">METRAN\linda</tt>. On Unix systems, the backslash is
+commonly used as a metacharacter for quoting, so the account would
+have to be specified as <tt class="literal">METRAN\\linda</tt> or
+'<tt class="literal">METRAN\linda</tt>'. The winbind separator parameter
+allows another character to be used instead of the backslash
+character, making it much easier to type in domain user and group
+names. For example, with:</p>
+
+<blockquote><pre class="code">[global]
+    winbind separator = +</pre></blockquote>
+
+<p>the aforementioned account could be written simply as
+<tt class="literal">METRAN+linda</tt> on the Unix host, making it
+unnecessary to use additional backslashes or single quotes. Winbind
+then uses the same format for reporting domain user and group names.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.2"/>
+
+<a name="INDEX-119"/><h3 class="head3">winbind uid</h3>
+
+<p>As part of <em class="emphasis">winbindd</em> 's task of
+letting Windows NT domain users function as local users on the Unix
+host, <em class="emphasis">winbindd</em> supplies a Unix UID that is
+linked to the Windows RID of the domain user. The
+<tt class="literal">winbind</tt> <tt class="literal">uid</tt> parameter allows
+the Unix system administrator to allocate a range of UIDs for this
+purpose. It is very important that this range not overlap any UIDs
+used for other purposes on the Unix system, so we recommend you begin
+your range at a very high number, one much larger than the number of
+local users and NIS users that will ever exist. For example,
+<tt class="literal">winbind</tt> <tt class="literal">uid</tt> might be defined
+as:</p>
+
+<blockquote><pre class="code">[global]
+    winbind uid = 10000-15000</pre></blockquote>
+
+<p>on a system that would never have more than 9,999 local and NIS
+users, or for that matter, any other entries in
+<em class="filename">/etc/passwd</em> that would use up another UID.
+Because the example allocates 5,000 UIDs to
+<em class="emphasis">winbindd</em>, the assumption is that there will
+never be more than 5,000 domain users accessing the Samba host.</p>
+
+<p>If your method for adding new local users to the system assigns UIDs
+automatically, make sure it does not assign them within the range of
+UIDs allocated to winbind. This might happen if the algorithm used
+adds 1 to the highest UID assigned thus far.</p>
+
+<p>There is no default for <tt class="literal">winbind</tt>
+<tt class="literal">uid</tt>, so you must specify it in your Samba
+configuration file for winbind to work.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.3"/>
+
+<a name="INDEX-120"/><h3 class="head3">winbind gid</h3>
+
+<p>This option works like <tt class="literal">winbind</tt>
+<tt class="literal">uid</tt>, except that it is for allocating a range of
+GIDs for use with <em class="emphasis">winbindd</em>. You might not need
+to allocate as many GIDs as UIDs because you probably have relatively
+few domain groups that need corresponding GIDs. (In many cases, users
+are all members of the Domain Users group, requiring only one GID.)
+However, it is best to play it safe, so make sure to allocate many
+more GIDs than you think you will need.</p>
+
+<p>As with <tt class="literal">winbind</tt> <tt class="literal">uid</tt>, if you are
+using a method of adding new local users to your Unix host that
+automatically assigns GIDs, either make sure the method used
+doesn't conflict with winbind or set the GIDs
+manually.</p>
+
+<p>There is no default for <tt class="literal">winbind</tt>
+<tt class="literal">gid</tt>, so you must specify it in your Samba
+configuration file for winbind to work.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.4"/>
+
+<a name="INDEX-121"/><h3 class="head3">winbind cache time</h3>
+
+<p>The <em class="emphasis">winbindd</em> daemon maintains a cache of user
+and group data that has been retrieved from the Windows PDC to reduce
+network queries and increase performance. The
+<tt class="literal">winbind</tt> <tt class="literal">cache</tt>
+<tt class="literal">time</tt> parameter allows the amount of time (in
+seconds) <em class="emphasis">winbindd</em> can use the cached data before
+querying the PDC to check for an update. By default, this interval is
+set to 15 seconds. This means that when any part of a user or group
+account on the PDC is modified, it can take up to 15 seconds for
+<em class="emphasis">winbindd</em> to update its own database.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.5"/>
+
+<a name="INDEX-122"/><h3 class="head3">template homedir</h3>
+
+<p>When the local Unix system is configured to allow domain users to log
+in, the user must be provided with a home directory for many
+programs, including command shells, to function properly. The
+<tt class="literal">template</tt> <tt class="literal">homedir</tt> option is used
+to set the name of the home directory. In the name of the directory,
+<tt class="literal">%D</tt> is replaced by the name of the Windows NT
+domain the user is in, and <tt class="literal">%U</tt> is replaced by his
+username. By default, <tt class="literal">template</tt>
+<tt class="literal">homedir</tt> is set to <tt class="literal">/home/%D/%U</tt>,
+which works fine for a network in which there might be more than one
+Windows NT domain, and it is possible for different people in
+different domains to have the same username. If you are sure you will
+never have more than one Windows NT domain on your network, or you
+have more than one domain but know for sure that unique users have
+identical usernames in each multiple domain, you might prefer to set
+<tt class="literal">template</tt> <tt class="literal">homedir</tt> like this:</p>
+
+<blockquote><pre class="code">[global]
+    template homedir = /home/%U</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-9-SECT-5.5.6"/>
+
+<a name="INDEX-123"/><h3 class="head3">template shell</h3>
+
+<p>This option specifies the program to use as the shell for domain
+users who are logged in to the Unix host. By default, it is set to
+<em class="emphasis">/bin/false</em>, which effectively denies domain
+users to log in. If you wish to allow logins for domain users, set
+<tt class="literal">template</tt> <tt class="literal">shell</tt> to a valid
+command shell (or other program) that you want to act as the textual
+interface the domain users will receive when logged in. A common
+setting on Linux would be:</p>
+
+<blockquote><pre class="code">[global]
+    template shell = /bin/bash</pre></blockquote>
+
+<p>which would give users the Bash shell for their interactive login
+sessions. <a name="INDEX-124"/><a name="INDEX-125"/> <a name="INDEX-126"/><a name="INDEX-127"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> Having both encrypted and nonencrypted
+password clients on your network is one of the reasons why Samba
+allows you to include (or not include) various options in the Samba
+configuration file based on the client operating system or machine
+name variables.</p> <a name="FOOTNOTE-2"/>
+<p><a href="#FNPTR-2">[2]</a> This is because the Unix <em class="emphasis">passwd</em> program,
+which is the usual target for this operation, allows
+<tt class="literal">root</tt> to change a user's password
+without the security restriction that requests the old password of
+that user.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch10.html b/docs/htmldocs/using_samba/ch10.html
new file mode 100644
index 0000000000..7ba29b1e95
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch10.html
@@ -0,0 +1,1695 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 10. Printing</h1>
+
+
+
+<p><a name="INDEX-1"/>This
+chapter tackles the topic of setting up printers for use with Samba.
+Aside from the &quot;coolness factor&quot; of
+seeing documents from Windows word processing and graphics
+applications appearing in the output tray of the Unix printer, this
+facility can greatly increase the usefulness of your Samba server. In
+many organizations, using a Unix system as the print server has led
+to happier system administrators and users alike, due to the reduced
+frequency of problems.</p>
+
+<p>Samba allows client machines to share printers connected to the Samba
+host system, and Samba can also send Unix documents to printers
+shared by Windows systems. In this chapter, we discuss how to get
+printers configured to work in either direction.</p>
+
+<p>We focus in this chapter on getting Samba to serve up printers that
+are already functioning on the Unix host. We include just a few
+basics about setting up printers on Unix. Good references for this
+topic include <em class="citetitle">Network Printing</em>,
+<em class="citetitle">Essential System Administration</em>, and
+<em class="citetitle">Running Linux</em>, all by
+O'Reilly and Associates.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-10-SECT-1"/>
+
+<h2 class="head1">Sending Print Jobs to Samba</h2>
+
+<p><a name="INDEX-2"/>A
+printer shared by the Samba server shows up in the list of shares
+offered in the Network Neighborhood. If the printer is registered on
+the client machine and the client has the correct printer driver
+installed, the client can effortlessly send print jobs to a printer
+attached to a Samba server. <a href="ch10.html#samba2-CHP-10-FIG-1">Figure 10-1</a> shows a
+Samba printer as it appears in the Network Neighborhood of a Windows
+client.</p>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-1"/><img src="figs/sam2_1001.gif"/></div><h4 class="head4">Figure 10-1. A Samba printer in the Network Neighborhood</h4>
+
+<p>To administer printers with Samba, you should understand the basic
+process by which
+<a name="INDEX-3"/>printing
+takes place on a network. On the client system, the application
+software prints by utilizing the system's printer
+driver for the printer that will be creating the actual output. It is
+the printer driver software running on the client system that
+translates the application's high-level calls into a
+stream of binary data specific to the model of printer in use. In the
+case of a serial, parallel, or USB printer, the data is stored in a
+temporary file in the local system's printer queue
+and then sent through the respective port directly to the printer.
+For a network printer, the file is sent over the network.</p>
+
+<a name="samba2-CHP-10-NOTE-150"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Because the data has already been processed through a printer driver
+by the time it reaches the Samba host, make sure the printer on the
+Unix system is configured without any printer driver and that it will
+print whatever data it receives in raw form. If you already have the
+printer configured for use by Unix applications, you might need to
+set up another queue for it to print documents received from Windows
+clients correctly.</p>
+</blockquote>
+
+<p>Sending a <a name="INDEX-4"/>print job to a printer on a
+<a name="INDEX-5"/>Samba server involves four steps:</p>
+
+<ol><li>
+<p>Opening and authenticating a connection to the printer share</p>
+</li><li>
+<p>Copying the file over the network</p>
+</li><li>
+<p>Closing the connection</p>
+</li><li>
+<p>Printing and deleting the copy of the file</p>
+</li></ol>
+<p>When a print job arrives at a Samba server, the print data is
+temporarily written to disk in the directory specified by the
+<tt class="literal">path</tt> option of the printer share. Samba then
+executes a Unix print command to send that datafile to the printer.
+The job is then printed as the authenticated user of the share. Note
+that this can be the guest user, depending on how the share is
+configured.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.1"/>
+
+<h3 class="head2">Print Commands</h3>
+
+<p><a name="INDEX-6"/>To print the
+document, you'll need to inform Samba of the command
+used to print and delete a file. On Linux, which uses a BSD-style
+printing system, a command that does this is:</p>
+
+<blockquote><pre class="code">lpr -r -P<em class="replaceable">printer</em> <em class="replaceable">file</em></pre></blockquote>
+
+<p>This command tells <a name="INDEX-7"/><em class="emphasis">lpr</em> to retrieve the
+name of the printer in the system configuration file
+(<em class="filename">/etc/printcap</em>) and interpret the rules it finds
+there to decide how to process the data and which physical device to
+send it to. Note that because the <em class="emphasis">-r</em> option has
+been specified, the file will be deleted after it has been printed.
+Of course, the file removed is just a copy stored on the Samba
+server; the original document on the client is unaffected.</p>
+
+<p>The process is similar on System V Unix. Here, printing and deleting
+become a compound command:</p>
+
+<blockquote><pre class="code">lp -d<em class="replaceable">printer</em> -s <em class="replaceable">file</em>; rm <em class="replaceable">file</em></pre></blockquote>
+
+<p>In this case, the <em class="filename">/etc/printcap</em> file is replaced
+with a different set of configuration files residing in
+<em class="filename">/usr/spool/lp</em>. Because the
+<em class="emphasis">lp</em> command has no option to delete the file
+after it is printed, we have added the <em class="emphasis">rm</em>
+command.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.2"/>
+
+<h3 class="head2">A Minimal Printing Setup</h3>
+
+<p>Let's start with a simple yet illustrative
+<a name="INDEX-8"/>printing
+share. Assuming that you're on a Linux system and
+you have a printer called <tt class="literal">netprinter</tt> listed in the
+printer capabilities file, the following addition to your
+<em class="filename">smb.conf</em> file makes the printer accessible
+through the network:</p>
+
+<blockquote><pre class="code">[printer1]
+    printable = yes
+    print command = /usr/bin/lpr -P%p -r %s
+    printer = netprinter
+    printing = BSD
+    path = /var/tmp</pre></blockquote>
+
+<p>The variable <tt class="literal">%s</tt> in the
+<tt class="literal">print</tt><a name="INDEX-9"/> <tt class="literal">command</tt>
+option is replaced with the name of the file to be printed when Samba
+executes the command. There are four Samba configuration-file
+variables specifically for use with
+<a name="INDEX-10"/>printing
+options. They are shown in <a href="ch10.html#samba2-CHP-10-TABLE-1">Table 10-1</a>.</p>
+
+<a name="samba2-CHP-10-TABLE-1"/><h4 class="head4">Table 10-1. Printing variables</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Variable</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">%s</tt></p>
+</td>
+<td>
+<p>The full pathname of the file on the Samba server to be printed</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%f</tt></p>
+</td>
+<td>
+<p>The name of the file itself (without the preceding path) on the Samba
+server to be printed</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%p</tt></p>
+</td>
+<td>
+<p>The name of the Unix printer to use</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%j</tt></p>
+</td>
+<td>
+<p>The number of the print job (for use with <tt class="literal">lprm</tt>,
+<tt class="literal">lppause</tt>, and <tt class="literal">lpresume</tt>)</p>
+</td>
+</tr>
+
+</table>
+
+<p>For other flavors of Unix, it is necessary to modify both the
+<tt class="literal">printing</tt> and <tt class="literal">print</tt>
+<tt class="literal">command</tt> options. For System V Unix, we would
+specify:</p>
+
+<blockquote><pre class="code">[printer1]
+    printing = SYSV
+    print command = lp -d%p -s %s; rm %s</pre></blockquote>
+
+<p>With the <tt class="literal">printing</tt> <tt class="literal">=</tt>
+<tt class="literal">SYSV</tt> parameter, we notify Samba that the local
+printing system uses the System V Unix method. As mentioned earlier,
+the <tt class="literal">%p</tt> variable resolves to the name of the
+printer, while the <tt class="literal">%s</tt> variable resolves to the
+name of the file.</p>
+
+<p>Clients might need to request the status of a print job sent to the
+Samba server. Because Samba sends print jobs to the Unix printing
+system for spooling, there might be a number of jobs in the queue at
+any given time. Consequently, Samba needs to communicate to the
+client not only the status of the current printing job, but also
+which documents are waiting to be printed on that printer. Samba also
+has to provide the client the ability to pause print jobs, resume
+print jobs, and remove print jobs from the printing queue. Samba
+provides options for each of these tasks. As you might expect, they
+borrow functionality from the following existing Unix commands:</p>
+
+<ul><li>
+<p><tt class="literal">lpq</tt><a name="INDEX-11"/></p>
+</li><li>
+<p><tt class="literal">lprm</tt><a name="INDEX-12"/></p>
+</li><li>
+<p><tt class="literal">lppause</tt><a name="INDEX-13"/></p>
+</li><li>
+<p><tt class="literal">lpresume</tt><a name="INDEX-14"/></p>
+</li></ul>
+<p>We cover these options in more detail later in this chapter. For the
+most part, Samba provides reasonable default values for them based on
+the value of the <tt class="literal">printing</tt> configuration option, so
+you can probably get by without having to formulate your own commands
+for them.</p>
+
+<p>Here are a few important items to remember about
+<a name="INDEX-15"/>printing shares:</p>
+
+<ul><li>
+<p>You must put
+<tt class="literal">printable</tt><a name="INDEX-16"/> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> in all printer shares (even
+<tt class="literal">[printers]</tt>) so that Samba knows they are printer
+shares. If you forget, the shares will be unusable for printing and
+will instead be treated as disk shares.</p>
+</li><li>
+<p>If you set the <tt class="literal">path</tt> configuration option in the
+printer section, any files sent to the printer(s) will be copied to
+the directory you specify instead of to the default location of
+<em class="filename">/tmp</em>. Because the amount of disk space allocated
+to <em class="filename">/tmp</em> can be relatively small in some Unix
+operating systems, many administrators prefer to use
+<em class="filename">/var/tmp, /var/spool/tmp</em>, or some other
+directory instead.</p>
+</li><li>
+<p>If you set <tt class="literal">guest</tt> <tt class="literal">ok</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in a printer share and
+Samba is configured for share-level security, anyone can send data to
+the printer as the <tt class="literal">guest</tt>
+<tt class="literal">account</tt> user.</p>
+</li></ul>
+<p>Using one or more Samba machines as a print server gives you a great
+deal of flexibility on your LAN. You can easily partition your
+available printers, restricting some to members of one department, or
+you can maintain a bank of printers available to all. In addition,
+you can restrict a printer to a select few by adding the
+<tt class="literal">valid</tt> <tt class="literal">users</tt> option to its share
+definition:</p>
+
+<blockquote><pre class="code">[deskjet]
+    printable = yes
+    path = /var/spool/samba/print
+    valid users = elizabeth cozy jack heather alexander lina emerald</pre></blockquote>
+
+<p>All the other share accessibility options work for printing shares as
+well.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.3"/>
+
+<h3 class="head2">The [printers] Share</h3>
+
+<p>If a share named
+<tt class="literal">[printers]</tt><a name="INDEX-17"/> is in the configuration file,
+Samba will automatically read in your printer capabilities file and
+create a printing share for each printer that appears in the file.
+For example, if the Samba server had <tt class="literal">lp</tt>,
+<tt class="literal">pcl</tt>, and <tt class="literal">ps</tt> printers in its
+printer capabilities file, Samba would provide three printer shares
+with those names, each configured with the options in the
+<tt class="literal">[printers]</tt> share.</p>
+
+<p>Recall that Samba obeys the following rules when a client requests a
+share that has not been created with an explicit share definition in
+the <em class="filename">smb.conf</em> file:</p>
+
+<ul><li>
+<p>If the share name matches a username in the system password file and
+a <tt class="literal">[homes]</tt> share exists, a new share is created
+with the name of the user and is initialized using the values given
+in the <tt class="literal">[homes]</tt> and <tt class="literal">[global]</tt>
+sections.</p>
+</li><li>
+<p>Otherwise, if the name matches a printer in the system printer
+capabilities file and a <tt class="literal">[printers]</tt> share exists, a
+new share is created with the name of the printer and initialized
+using the values given in the <tt class="literal">[printers]</tt> section.
+(Variables in the <tt class="literal">[global]</tt> section do not apply
+here.)</p>
+</li><li>
+<p>If neither of those succeeds, Samba looks for a
+<tt class="literal">default</tt> <tt class="literal">service</tt> share. If none
+is found, it returns an error.</p>
+</li></ul>
+<p>This brings to light an important point: be careful that you do not
+give a printer the same name as a user. Otherwise, users end up
+connecting to a disk share when they might have wanted a printer
+share instead.</p>
+
+<p>Here is an example
+<tt class="literal">[printers]</tt><a name="INDEX-18"/> share for a Linux system. Some of
+these options are already defaults; however, we have listed them
+anyway for illustrative purposes:</p>
+
+<blockquote><pre class="code">[printers]
+    printable = yes
+    printing = BSD
+    printcap name = /etc/printcap
+    print command = /usr/bin/lpr -P%p -r %s
+    path = /var/spool/lpd/tmp
+    min print space = 2000</pre></blockquote>
+
+<p>Here, we've given Samba global options that specify
+the printing type (BSD), a print command to send data to the printer
+and later remove the temporary file, the location of our printer
+capabilities file, and a minimum disk space for printing of 2MB.</p>
+
+<p>In addition, we've created a
+<tt class="literal">[printers]</tt> share for each system printer. Our
+temporary spooling directory is specified by the
+<tt class="literal">path</tt> option:
+<em class="filename">/var/spool/lpd/tmp</em>. Each share is marked as
+printable&mdash;this is a necessary option, even in the
+<tt class="literal">[printers]</tt> section.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.4"/>
+
+<h3 class="head2">Testing the Configuration</h3>
+
+<p><a name="INDEX-19"/>After running
+<em class="emphasis">testparm</em> and restarting the Samba daemons, you
+can check to make sure everything is set up correctly by using
+<em class="emphasis">smbclient</em><a name="INDEX-20"/><a name="INDEX-21"/> to send a file to the printer.
+Connect to the printer using the command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbclient /</b></tt><em class="replaceable">server</em><tt class="userinput"><b>/</b></tt><em class="replaceable">printshare</em></pre></blockquote>
+
+<p>and then use the <em class="emphasis">print</em> command to print a file:</p>
+
+<blockquote><pre class="code">smb: /&gt; <tt class="userinput"><b>print </b></tt><em class="replaceable">textfile</em></pre></blockquote>
+
+<a name="samba2-CHP-10-NOTE-151"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you connect to a print share served by a Windows 95/98/Me system
+configured to use user-mode security and cannot authenticate using
+what you know to be a correct username and password, try
+reconfiguring the Windows system to use share-mode security.</p>
+</blockquote>
+
+<p>When you print something through the Samba server via
+<em class="emphasis">smbclient</em>, the following actions should occur:</p>
+
+<ul><li>
+<p>The job appears (briefly) in the Samba spool directory specified by
+the path.</p>
+</li><li>
+<p>The job shows up in your print system's spool
+directory.</p>
+</li><li>
+<p>The job disappears from the spool directory that Samba used.</p>
+</li></ul>
+<p>If <em class="emphasis">smbclient</em> cannot print, you can reset the
+<tt class="literal">print</tt> <tt class="literal">command</tt> option to collect
+debugging information:</p>
+
+<blockquote><pre class="code">print command = echo &quot;printed %s on %p&quot; &gt;&gt;/tmp/printlog</pre></blockquote>
+
+<p>A <a name="INDEX-22"/>common
+problem with Samba printer configuration is forgetting to use the
+full pathnames for commands. Another frequent problem is not having
+the correct permissions on the spooling directory.<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a> As usual,
+check your Samba log files and system log files for error messages.
+If you use BSD printing, you can change the <tt class="literal">lp</tt>
+keyword in the printer's printcap entry to something
+other than <em class="filename">/dev/null</em>, allowing you to collect
+error messages from the printing system.</p>
+
+<a name="samba2-CHP-10-NOTE-152"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>More information on
+<a name="INDEX-23"/>debugging printers is in the file
+<em class="filename">docs/textdocs/Printing.txt</em> in the Samba source
+distribution. The Unix print systems are covered in detail in
+<a name="INDEX-24"/>&AElig;leen
+Frisch's <em class="emphasis">Essential Systems
+Administration</em> (published by O'Reilly).</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.5"/>
+
+<h3 class="head2">Enabling SMB Printer Sharing in Mac OS X</h3>
+
+<p>With Samba preinstalled with
+<a name="INDEX-25"/><a name="INDEX-26"/>Mac OS X, sharing access to a printer
+among Windows clients is easy. First, of course, you should set up
+local access using the Print Center application (located in
+<em class="filename">/Applications/Utilities</em>). Under the Printers
+menu, select Add Printer..., and make the appropriate selection from
+the pop-up menu. For example, if the printer is directly attached,
+select USB; if the printer is powered on, it should appear in the
+list. Choose the printer, and press the Add button.</p>
+
+<p>Edit <em class="filename">/etc/smb.conf</em>, uncommenting the
+<tt class="literal">[printers]</tt> share and making any additional
+configuration changes you feel are necessary. Finally, enable the
+Samba startup item as described in <a href="ch02.html">Chapter 2</a>,
+either by checking Windows File Sharing in Sharing Preferences or by
+manually editing <em class="filename">/etc/hostconfig</em>. Now your
+printer can be used by remote Windows clients.</p>
+
+<p>On Mac OS X and some other BSD-based systems, you can test your
+configuration using
+<em class="emphasis">smbutil</em><a name="INDEX-27"/>. The following will send the
+file named <em class="filename">print_test_file</em> to the printer named
+<em class="filename">printshare</em> on the server
+<em class="emphasis">bsdserver</em> :</p>
+
+<blockquote><pre class="code">% <tt class="userinput"><b>smbutil print //bsdserver/printshare print_test_file</b></tt></pre></blockquote>
+
+<p>See <a href="ch05.html">Chapter 5</a> for more information on using
+<em class="emphasis">smbutil</em>.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-1.6"/>
+
+<h3 class="head2">Setting Up and Testing a Windows Client</h3>
+
+<p><a name="INDEX-28"/>Now that Samba is
+offering a workable printer, you can set up your access to it on a
+Windows client. Browse through the Samba server in the Network
+Neighborhood. It should now show each printer that is available. For
+example, in <a href="ch10.html#samba2-CHP-10-FIG-1">Figure 10-1</a>, we saw a printer called
+<tt class="literal">lp</tt>.</p>
+
+<p>Next, you need to have the Windows client recognize the printer.
+Double-click the printer icon to get started. If you try to select an
+uninstalled printer (as you just did), Windows will ask you if it
+should help configure it for the Windows system. Click the Yes or OK
+button, and the Printer Wizard will open.</p>
+
+<p>If you are installing a printer on Windows 95/98/Me, the first thing
+the wizard will ask is whether you need to print from DOS.
+Let's assume you don't, so choose
+the &quot;No&quot; radio button and press the
+Next &gt; button to get to the manufacturer/model window, as shown in
+<a href="ch10.html#samba2-CHP-10-FIG-2">Figure 10-2</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-2"/><img src="figs/sam2_1002.gif"/></div><h4 class="head4">Figure 10-2. Setting the manufacturer and model of the printer</h4>
+
+<p>In this dialog box, you should see a large list of manufacturers and
+models for a huge number of printers. Select the manufacturer of your
+printer in the left side of the dialog box, and then the exact model
+of the printer in the list on the right side.</p>
+
+<p>In some cases, you might not find your printer in the list, or the
+version of the printer driver included with Windows might be out of
+date. In cases such as these, consult the printer
+manufacturer's documentation on how to install the
+driver. Typically, you will click the Have Disk... button to install
+the driver from a CD-ROM or disk file.</p>
+
+<p>If you don't see your printer on the list, but you
+know it's a PostScript printer, select Apple as the
+manufacturer and Apple LaserWriter as the model. This will give you
+the most basic PostScript printer setup&mdash;and arguably one of the
+most reliable. If you already have PostScript printers attached, you
+will be asked about replacing or reusing the existing driver. Be
+aware that if you replace it with a new one, you might make your
+other printers fail. Therefore, we recommend you keep using your
+existing printer drivers as long as they're working
+properly.</p>
+
+<p>Click the Next &gt; or OK button. On Windows 95/98/Me, the Printer
+Wizard asks you to name the printer. On Windows NT/2000/XP, you need
+to right-click the printer's icon and select
+Properties to assign the printer a name. <a href="ch10.html#samba2-CHP-10-FIG-3">Figure 10-3</a>
+shows how we've named our printer to show that
+it's shared by the <tt class="literal">mixtec</tt> Samba
+server.</p>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-3"/><img src="figs/sam2_1003.gif"/></div><h4 class="head4">Figure 10-3. Setting the printer name</h4>
+
+<p>Finally, on Windows 95/98/Me the Printing Wizard asks if it should
+print a test page. Click the &quot;Yes&quot;
+radio button, then the Finish button, and you should be presented
+with the dialog box shown in <a href="ch10.html#samba2-CHP-10-FIG-4">Figure 10-4</a>. On Windows
+NT/2000/XP, the printer test function is also accessed through the
+printer's Properties dialog box.</p>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-4"/><img src="figs/sam2_1004.gif"/></div><h4 class="head4">Figure 10-4. Sending a test page to the printer</h4>
+
+<p>If the test printing was unsuccessful, click the No button and the
+Printing Wizard will walk you through some debugging steps for the
+client side of the process. If the test printing does work, the
+remote printer will now be available to all Windows applications
+through the File and Print menu items.</p>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-10-SECT-2"/>
+
+<h2 class="head1">Printing to Windows Printers</h2>
+
+<p><a name="INDEX-29"/>If you have printers
+connected to systems running Windows 95/98/Me or Windows NT/2000/XP,
+the printers can also be accessed from your Unix system using tools
+that are part of the Samba distribution. First, it is necessary to
+create a printer share on the Windows system. Then set up the printer
+on the Unix side by configuring a new printer and using a Samba
+printing program as the printer's filter.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-2.1"/>
+
+<h3 class="head2">Sharing Windows Printers</h3>
+
+<p>Sharing printers on Windows is not unlike sharing files. In fact, it
+is a little simpler. Open the Control Panel, then double-click the
+Printers icon to open the Printers window. Right-click the icon for
+the printer you want to share, and select Sharing.... This opens the
+dialog box shown in <a href="ch10.html#samba2-CHP-10-FIG-5">Figure 10-5</a> for a Windows 98
+system, or <a href="ch10.html#samba2-CHP-10-FIG-6">Figure 10-6</a> on a Windows 2000 system.
+(The dialog box appears slightly different on other Windows versions,
+but functions almost identically.)</p>
+
+<a name="samba2-CHP-10-NOTE-153"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>On Windows 95/98/Me systems, you may need to run file sharing in
+share-level (rather than user-level) access control mode to access a
+shared printer from Samba. To check or set this mode, go to Control
+Panel, then double-click on Network, then click on the Access Control
+tab. More detailed information on this can be found in <a href="ch05.html">Chapter 5</a>.</p>
+</blockquote>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-5"/><img src="figs/sam2_1005.gif"/></div><h4 class="head4">Figure 10-5. Sharing printers on Windows 98</h4>
+
+<div class="figure"><a name="samba2-CHP-10-FIG-6"/><img src="figs/sam2_1006.gif"/></div><h4 class="head4">Figure 10-6. Sharing printers on Windows 2000</h4>
+
+<p>Click the &quot;Shared as&quot; radio button,
+then click the OK button. The printer is now accessible by other
+systems on the network.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-2.2"/>
+
+<h3 class="head2">Adding a Unix Printer</h3>
+
+<p><a name="INDEX-30"/>The Samba distribution comes with
+three programs that assist with printing on shared printers. The
+<em class="emphasis">smbprint</em><a name="INDEX-31"/> program works with systems that use the
+BSD printing system,
+<em class="emphasis">smbprint.sysv</em><a name="INDEX-32"/>
+works with systems that use System V printing, and
+<em class="emphasis">smbspool</em><a name="INDEX-33"/>
+works with systems that use the Common Unix Printing System (CUPS).
+In the following sections we show you how to install printers for
+each system.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.2.1"/>
+
+<h3 class="head3">BSD printers</h3>
+
+<p><a name="INDEX-34"/><a name="INDEX-35"/>The
+BSD printing system is used by many Unix variants, including Red Hat
+Linux. With BSD printing, all the printers on the system have an
+entry in the <em class="filename">/etc/printcap</em> file, which is the
+database of printer capabilities used by the <em class="emphasis">lpd</em>
+line printer daemon and other programs that assist with printing. The
+Red Hat Linux implementation is a bit different in that
+<em class="filename">/etc/printcap</em> is a machine-generated file, which
+is re-created every time the <em class="emphasis">lpd</em> daemon is
+restarted by the <em class="emphasis">/etc/rc.d/init.d/lpd</em> script.
+Instead of editing <em class="filename">/etc/printcap</em>, we will add an
+entry for our printer in <em class="filename">/etc/printcap.local</em>,
+which the system automatically includes verbatim when creating
+<em class="filename">/etc/printcap</em>.</p>
+
+<a name="samba2-CHP-10-NOTE-154"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If you are using the version of Samba installed from an RPM file as
+on Red Hat Linux, you might be able to skip these directions and use
+the <em class="emphasis">printconf</em> tool, which has support for SMB
+printers. Unfortunately, this tool might not work correctly if you
+have installed Samba from the Samba source distribution.</p>
+</blockquote>
+
+<p>Here is the entry we added to our
+<em class="filename">/etc/printcap.local</em><a name="INDEX-36"/><a name="INDEX-37"/> file to support our Hewlett-Packard
+DeskJet 932C printer, which is shared by <tt class="literal">maya</tt>, a
+Windows 98 system:</p>
+
+<blockquote><pre class="code">lp|maya-hp932c:\
+    :cm=HP 932C on maya:\
+    :sd=/var/spool/lpd/maya:\
+    :af=/var/spool/lpd/maya/acct:\
+    :if=/usr/local/samba/bin/smbprint:\
+    :mx=0:\
+    :lp=/dev/null:</pre></blockquote>
+
+<p>The first line creates names for the printer. We are calling it both
+<tt class="literal">maya-hp932c</tt>, to describe its location on the
+network and the type of printer, and <tt class="literal">lp</tt> so that
+programs will use it as the default printer. The rest of the lines
+specify keywords and values. The <tt class="literal">cm</tt> keyword allows
+us to assign a comment string to the printer. The
+<tt class="literal">sd</tt> and <tt class="literal">af</tt> keywords assign the
+printer's spool directory and accounting files,
+respectively. The <tt class="literal">if</tt> keyword assigns the print
+filter. We are using the <em class="emphasis">smbprint</em> command to
+send the output to the shared SMB printer. The <tt class="literal">mx</tt>
+keyword is set to zero to allow any size file to be printed, and
+<tt class="literal">lp</tt> is set to <em class="filename">/dev/null</em> to
+discard error messages.</p>
+
+<p>You can follow our model to create an entry for your own printer. If
+you want to go beyond the capabilities we used, refer to your
+system's <em class="emphasis">printcap(5)</em> manual
+page for a complete listing of keywords.</p>
+
+<p>Go to your Samba source distribution's root
+directory, and install the <em class="emphasis">smbprint</em> program like
+this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>cp examples/printing/smbprint /usr/local/samba/bin</b></tt></pre></blockquote>
+
+<p>We next create the printer's spool directory:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>cd /var/spool/lpd</b></tt>
+# <tt class="userinput"><b>mkdir maya</b></tt>
+# <tt class="userinput"><b>chown lp:lp maya</b></tt>
+# <tt class="userinput"><b>chmod 700 maya</b></tt></pre></blockquote>
+
+<p>The <em class="emphasis">smbprint</em> program looks for a file named
+<em class="filename">.config</em> in the printer's spool
+directory, which contains information on how to connect to the
+printer share. We create this file and then fill in the required
+information:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>cd maya</b></tt>
+# <tt class="userinput"><b>&gt;.config</b></tt>
+# <tt class="userinput"><b>chown lp:lp .config</b></tt>
+# <tt class="userinput"><b>chmod 600 .config</b></tt></pre></blockquote>
+
+<p>Use your preferred text editor to edit the
+<em class="filename">.config</em> file, and enter three lines, like this:</p>
+
+<blockquote><pre class="code">server=maya
+service=hp
+password=&quot;&quot;</pre></blockquote>
+
+<p>This is for our shared printer having a UNC of
+<em class="filename">\\maya\hp</em>. When we created the printer share, we
+did not give it a password, so we use a null password here. If your
+printer share is on a Windows NT/2000/XP system, use your domain
+password.</p>
+
+<p>Finally, restart the printer daemon:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>/etc/rc.d/init.d/lpd restart</b></tt></pre></blockquote>
+
+<p>You can now try printing something. Run the following command:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>lpr textfile</b></tt></pre></blockquote>
+
+<p>If you have everything set up correctly, the file prints on the
+shared printer. If you get &quot;stair
+stepping&quot; of text, caused by the printer not
+returning to the left margin at the beginning of every line, modify
+the <tt class="literal">if</tt> keyword in your printcap entry to run
+<em class="emphasis">smbprint</em> with the <em class="emphasis">-t</em>
+option. <a name="INDEX-38"/><a name="INDEX-39"/></p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.2.2"/>
+
+<h3 class="head3">System V printers</h3>
+
+<p><a name="INDEX-40"/><a name="INDEX-41"/>Sending print jobs from a System V Unix
+system is a little easier than with the BSD system. Here, you need to
+edit the <em class="filename">smbprint.sysv</em> script in the
+<em class="filename">examples/printing</em> directory of the Samba
+distribution and do the following:</p>
+
+<ol><li>
+<p>Change the <tt class="literal">server</tt>, <tt class="literal">service</tt>, and
+<tt class="literal">password</tt> parameters in the script to match the
+NetBIOS computer name, its shared printer service, and its password,
+respectively. For example, the following entries would be correct for
+the service in the previous example:</p>
+
+<blockquote><pre class="code">server = maya
+service = hp
+password = &quot;&quot;</pre></blockquote>
+</li>
+<li>
+<p>Run the following commands, which create a reference for the new
+printer (which we are naming <tt class="literal">hp_printer</tt>) in the
+printer capabilities file:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>lpadmin -p hp_printer -v /dev/null -i./smbprint.sysv</b></tt>
+# <tt class="userinput"><b>enable hp_printer</b></tt>
+# <tt class="userinput"><b>accept hp_printer</b></tt></pre></blockquote>
+</li></ol>
+<p>After you've done that, restart the Samba daemons
+and try printing to <tt class="literal">hp_printer</tt> using any standard
+Unix program.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.2.3"/>
+
+<h3 class="head3">CUPS printers</h3>
+
+<p><a name="INDEX-42"/><a name="INDEX-43"/><a name="INDEX-44"/>CUPS<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a> uses
+a set of modules, called
+<em class="firstterm">backends</em><a name="INDEX-45"/>, to send print jobs to various
+destinations, such as local printers attached to parallel, serial, or
+Universal Serial Bus (USB) ports, or over the network using Unix line
+printer daemon (LPD) protocol, Internet Printing Protocol (IPP),
+AppleTalk Printer Access Protocol (PAP), and so on. The software
+package does not come with a backend for SMB; the Samba suite
+includes the <em class="emphasis">smbspool</em>
+<a name="INDEX-46"/>utility for this purpose.</p>
+
+<p>To enable printing to remote SMB printers using CUPS, create a
+symbolic link named <em class="filename">smb</em> in the CUPS backend
+directory pointing to <em class="emphasis">smbspool</em>. Depending on
+installation options, these could be in a number of places in the
+directory hierarchy, so be sure to check your system. Using a common
+default installation, the command would look like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>ln -s /usr/local/samba/bin/smbspool /usr/lib/cups/backend/smb</b></tt></pre></blockquote>
+
+<p>Issue a HUP signal to the CUPS daemon, <em class="emphasis">cupsd</em>,
+and check for the existence of SMB support with the <em class="emphasis">lpinfo
+-v</em> command. Its output should now include a line that says
+<tt class="literal">network</tt> <tt class="literal">smb</tt>.</p>
+
+<p>To add a printer, use the CUPS web interface, accessible on the local
+system at <em class="emphasis">http://localhost:631/</em>,
+or use the <em class="emphasis">lpadmin</em> command:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>lpadmin -p hp932c -E -v smb://maya/hp932c -D &quot;HP 932C on maya&quot;</b></tt></pre></blockquote>
+
+<p>This creates and enables the new print spool called
+<tt class="literal">hp932c</tt>. The <em class="emphasis">-v</em> argument
+specifies the printer device, which in this case is accessed over the
+network using an SMB URI. If the printer is not guest-accessible,
+you'll need to provide a username and password in
+the URI. The full format is as follows:</p>
+
+<blockquote><pre class="code">smb://[<em class="replaceable">username</em>[:<em class="replaceable">password</em>]@][<em class="replaceable">workgroup</em>/]<em class="replaceable">server</em>/<em class="replaceable">printshare</em></pre></blockquote>
+
+<p>The <em class="emphasis">lpadmin</em><a name="INDEX-47"/> command makes changes to
+<em class="filename">/etc/cups/printers.conf</em> and sends a HUP signal
+to the <em class="emphasis">cupsd</em> daemon, resulting in the creation
+of a local raw printer spool. In this example, print data is passed
+in raw format to the Windows system, which has the necessary printer
+drivers and printer description files to format the data
+appropriately. The <em class="emphasis">-D</em> option is used to give the
+printer a comment string.</p>
+
+<p>Once you have the printer set up, it's time to test
+it out. CUPS understands both BSD-style and System V-style printing
+commands, so you can use whichever is more comfortable. Using the BSD
+<em class="emphasis">lpr</em> command, try something like:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>lpr -P hp932c textfile</b></tt></pre></blockquote>
+
+<p>You should now be set up to use the printer from any application on
+the Unix system. <a name="INDEX-48"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-10-SECT-2.3"/>
+
+<h3 class="head2">Samba Printing Options</h3>
+
+<p><a href="ch10.html#samba2-CHP-10-TABLE-2">Table 10-2</a> summarizes the Samba <a name="INDEX-49"/><a name="INDEX-50"/>printing
+options.</p>
+
+<a name="samba2-CHP-10-TABLE-2"/><h4 class="head4">Table 10-2. Printing configuration options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">printing</tt></p>
+</td>
+<td>
+<p><tt class="literal">bsd</tt>, <tt class="literal">sysv</tt>,
+<tt class="literal">cups</tt>, <tt class="literal">hpux</tt>,
+<tt class="literal">aix</tt>, <tt class="literal">qnx</tt>,
+<tt class="literal">plp</tt>, <tt class="literal">softq</tt>, or
+<tt class="literal">lprng</tt></p>
+</td>
+<td>
+<p>Printing system type of the Samba host</p>
+</td>
+<td>
+<p>System-dependent</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">printable</tt> <tt class="literal">(print ok)</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>Marks a share as a printing share</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">printer</tt> <tt class="literal">(printer name)</tt></p>
+</td>
+<td>
+<p>string (Unix printer name)</p>
+</td>
+<td>
+<p>Name for the printer that is shown to clients</p>
+</td>
+<td>
+<p>System-dependent</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lpq cache time</tt></p>
+</td>
+<td>
+<p>numeric (time in seconds)</p>
+</td>
+<td>
+<p>Amount of time in seconds that Samba will cache the printer queue
+status</p>
+</td>
+<td>
+<p><tt class="literal">10</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">postscript</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>Treats all print jobs as PostScript by prefixing
+<tt class="literal">%!</tt> at the beginning of each file</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">load printers</tt></p>
+</td>
+<td>
+<p>boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, automatically loads each printer in the
+<em class="emphasis">printcap</em> file as printing shares</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">print command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to perform printing</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lpq command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to return the status of the printing queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lprm command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to remove a job from the printing queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lppause command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to pause a job on the printing queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lpresume</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to resume a paused job on the printing queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">printcap name</tt></p>
+
+<p><tt class="literal">(printcap)</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>Location of the printer capabilities file</p>
+</td>
+<td>
+<p>System-dependent</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">min print space</tt></p>
+</td>
+<td>
+<p>numeric (size in kilobytes)</p>
+</td>
+<td>
+<p>Minimum amount of free disk space that must be present to print</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">queuepause</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to pause a queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">queueresume</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Unix command to resume a queue</p>
+</td>
+<td>
+<p>See below</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.1"/>
+
+<h3 class="head3">printing</h3>
+
+<p>The <tt class="literal">printing</tt><a name="INDEX-51"/> configuration option tells
+Samba which <a name="INDEX-52"/>printing system to use. There are
+several different families of commands to control printing and print
+statusing. Samba supports seven different types, as shown in <a href="ch10.html#samba2-CHP-10-TABLE-3">Table 10-3</a>.</p>
+
+<a name="samba2-CHP-10-TABLE-3"/><h4 class="head4">Table 10-3. Printing system types</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Variable</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>BSD</p>
+</td>
+<td>
+<p>Berkeley Unix system</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>SYSV</p>
+</td>
+<td>
+<p>System V</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>CUPS</p>
+</td>
+<td>
+<p>Common Unix Printing System</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>AIX</p>
+</td>
+<td>
+<p>IBM's AIX operating system</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>HPUX</p>
+</td>
+<td>
+<p>Hewlett-Packard Unix</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>QNX</p>
+</td>
+<td>
+<p>QNX Realtime Operating System</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>LPRNG</p>
+</td>
+<td>
+<p>LPR Next Generation</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>SOFTQ</p>
+</td>
+<td>
+<p>SOFTQ system</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>PLP</p>
+</td>
+<td>
+<p>Portable Line Printer</p>
+</td>
+</tr>
+
+</table>
+
+<p>The value for this option must be one of these seven selections. For
+example:</p>
+
+<blockquote><pre class="code">printing = SYSV</pre></blockquote>
+
+<p>The default value of this option is system-dependent and is
+configured when Samba is first compiled. For most systems, the
+<em class="filename">configure</em> script automatically detects the
+printing system to be used and configures it properly in the Samba
+makefile. However, if your system is a PLP, LPRNG, or QNX printing
+system, you need to specify this explicitly in the makefile or the
+printing share.</p>
+
+<p>The most common system types are BSD, SYSV, and CUPS. Each printer on
+a BSD Unix server is described in the printer capabilities
+file&mdash;normally <em class="filename">/etc/printcap</em>. See the
+section on the <tt class="literal">printcap</tt> <tt class="literal">file</tt>
+parameter for more information on this topic.</p>
+
+<p>Setting the <tt class="literal">printing</tt> configuration option
+automatically sets at least three other printing options for the
+service in question: <tt class="literal">print</tt>
+<tt class="literal">command</tt>, <tt class="literal">lpq</tt>
+<tt class="literal">command</tt>, and <tt class="literal">lprm</tt>
+<tt class="literal">command</tt>. If you are running Samba on a system that
+doesn't support any of the printing styles listed in
+<a href="ch10.html#samba2-CHP-10-TABLE-3">Table 10-3</a>, simply set the commands for each of
+these manually.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.2"/>
+
+<h3 class="head3">printable</h3>
+
+<p>The <tt class="literal">printable</tt><a name="INDEX-53"/> option must be set to
+<tt class="literal">yes</tt> to flag a share as a printing service. If this
+option is not set, the share will be treated as a disk share instead.
+You can set the option as follows:</p>
+
+<blockquote><pre class="code">[printer1]
+    printable = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.3"/>
+
+<a name="INDEX-54"/><h3 class="head3">printer</h3>
+
+<p>The option, also called
+<tt class="literal">printer</tt><a name="INDEX-55"/> <tt class="literal">name</tt>,
+specifies the name of the printer on the server to which the share
+points. This option has no default and should be set explicitly in
+the configuration file, even though Unix systems themselves often
+recognize a default name such as <tt class="literal">lp</tt> for a printer.
+For example:</p>
+
+<blockquote><pre class="code">[deskjet]
+    printer = hpdkjet1</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.4"/>
+
+<h3 class="head3">lpq cache time</h3>
+
+<p>The global <tt class="literal">lpq</tt><a name="INDEX-56"/> <tt class="literal">cache</tt>
+<tt class="literal">time</tt> option allows you to set the number of
+seconds for which Samba will remember the current printer status.
+After this time elapses, Samba will issue an <em class="emphasis">lpq</em>
+command (or whatever command you specify with the
+<tt class="literal">lpq</tt> <tt class="literal">command</tt> option) to get a
+more up-to-date status that it can report to users. This defaults to
+10 seconds, but can be increased if your <tt class="literal">lpq</tt>
+<tt class="literal">command</tt> takes an unusually long time to run or you
+have lots of clients. A time setting of 0 disables caching of queue
+status. The following example resets the time to 30 seconds:</p>
+
+<blockquote><pre class="code">[deskjet]
+    lpq cache time = 30</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.5"/>
+
+<h3 class="head3">postscript</h3>
+
+<p>The <tt class="literal">postscript</tt><a name="INDEX-57"/> option forces the
+printer to treat all data sent to it as PostScript. It does this by
+prefixing the characters <tt class="literal">%!</tt> to the beginning of
+the first line of each job. It is normally used with PCs that insert
+a <tt class="literal">^D</tt> (control-D or
+&quot;end-of-file&quot; mark) in front of the
+first line of a PostScript file. It will not, obviously, turn a
+non-PostScript printer into a PostScript one. The default value of
+this options is <tt class="literal">no</tt>. You can override it as
+follows:</p>
+
+<blockquote><pre class="code">[deskjet]
+    postscript = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.6"/>
+
+<h3 class="head3">load printers</h3>
+
+<p>The <tt class="literal">load</tt><a name="INDEX-58"/> <tt class="literal">printers</tt>
+option tells Samba to create shares for all known printer names and
+load those shares into the browse list. Samba will create and list a
+printer share for each printer name in
+<em class="filename">/etc/printcap</em> (or the system equivalent). For
+example, if your
+<em class="filename">printcap</em><a name="INDEX-59"/> file looks
+like this:<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a></p>
+
+<blockquote><pre class="code">lp:\
+  :sd=/var/spool/lpd/lp:\            <i class="lineannotation">spool directory</i>
+  :mx#0:\                            <i class="lineannotation">maximum file size (none)</i>
+  :sh:\                              <i class="lineannotation">supress burst header (no)</i>
+  :lp=/dev/lp1:\                     <i class="lineannotation">device name for output</i>
+  :if=/var/spool/lpd/lp/filter:      <i class="lineannotation">text filter</i>
+
+laser:\
+  :sd=/var/spool/lpd/laser:\         <i class="lineannotation">spool directory</i>
+  :mx#0:\                            <i class="lineannotation">maximum file size (none)</i>
+  :sh:\                              <i class="lineannotation">supress burst header (no)</i>
+  :lp=/dev/laser:\                   <i class="lineannotation">device name for output</i>
+  :if=/var/spool/lpd/lp/filter:      <i class="lineannotation">text filter</i></pre></blockquote>
+
+<p>the shares <tt class="literal">[lp]</tt> and <tt class="literal">[laser]</tt> are
+automatically created as valid print shares when Samba is started.
+Both shares borrow the configuration options specified in the
+<tt class="literal">[printers]</tt> section to configure themselves and are
+available in the browse list for the Samba server. The default value
+for this option is <tt class="literal">yes</tt>. If you prefer to specify
+each printer explicitly in your configuration file, use the
+following:</p>
+
+<blockquote><pre class="code">[global]
+    load printers = no</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.7"/>
+
+<a name="INDEX-60"/><a name="INDEX-61"/><a name="INDEX-62"/><a name="INDEX-63"/><a name="INDEX-64"/><h3 class="head3">print command, lpq command, lprm command,lppause command, lpresume command</h3>
+
+<p>These options tell Samba which Unix commands control and send data to
+the printer. The Unix commands involved are: <em class="emphasis">lpr</em>
+(send to Line PRinter), <em class="emphasis">lpq</em> (List Printer
+Queue), <em class="emphasis">lprm</em> (Line Printer ReMove), and
+optionally <em class="emphasis">lppause</em> and
+<em class="emphasis">lpresume</em>. Samba provides an option named after
+each command, in case you need to override any of the system
+defaults. For example, consider the following:</p>
+
+<blockquote><pre class="code">lpq command = /usr/ucb/lpq %p</pre></blockquote>
+
+<p>This would set <tt class="literal">lpq</tt> <tt class="literal">command</tt> to
+use <em class="filename">/usr/ucb/lpq</em>. Similarly:</p>
+
+<blockquote><pre class="code">lprm command = /usr/local/bin/lprm -P%p %j</pre></blockquote>
+
+<p>would set the Samba printer remove command to
+<em class="filename">/usr/local/bin/lprm</em> and provide it the print job
+number using the <tt class="literal">%j</tt> variable.</p>
+
+<p>The default values for each option are dependent on the value of the
+<tt class="literal">printing</tt> option. <a href="ch10.html#samba2-CHP-10-TABLE-4">Table 10-4</a>
+shows the default commands for each printing option. The most popular
+printing system is BSD.</p>
+
+<a name="samba2-CHP-10-TABLE-4"/><h4 class="head4">Table 10-4. Default commands for various printing options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>BSD, AIX, PLP, LPRNG</p>
+</th>
+<th>
+<p>SYSV, HPUX</p>
+</th>
+<th>
+<p>QNX</p>
+</th>
+<th>
+<p>SOFTQ</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">print</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpr -r -P%p %s</tt></p>
+</td>
+<td>
+<p><tt class="literal">lp -c -d%p %s; rm</tt> <tt class="literal">%s</tt></p>
+</td>
+<td>
+<p><tt class="literal">lp -r -P%p %s</tt></p>
+</td>
+<td>
+<p><tt class="literal">lp -d%p -s %s; rm %s</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lpq</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpq -P%p</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpstat -o%p</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpq -P%p</tt></p>
+</td>
+<td>
+<p><tt class="literal">lpstat -o%p</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lprm</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lprm -P%p %j</tt></p>
+</td>
+<td>
+<p><tt class="literal">cancel %p-%j</tt></p>
+</td>
+<td>
+<p><tt class="literal">cancel %p-%j</tt></p>
+</td>
+<td>
+<p><tt class="literal">cancel %p-%j</tt></p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lppause</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lp -i %p-%j -H</tt> <tt class="literal">hold</tt></p>
+
+<p>(SYSV only)</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>None</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">lpresume</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p><tt class="literal">lp -i %p-%j -H</tt> <tt class="literal">resume</tt></p>
+
+<p>(SYSV only)</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p><tt class="literal">qstat -s -j%j -r</tt></p>
+</td>
+</tr>
+
+</table>
+
+<p>It is usually unnecessary to reset these options in Samba, with the
+possible exception of the <tt class="literal">print</tt>
+<tt class="literal">command</tt>. This option might need to be set
+explicitly if your printing system doesn't have a
+<em class="emphasis">-r</em> (remove after printing) option on the
+printing command. For example:</p>
+
+<blockquote><pre class="code">print command = /usr/local/lpr -P%p %s; /bin/rm %s</pre></blockquote>
+
+<p>With a bit of judicious programming, these
+<em class="filename">smb.conf</em> options can also be used for debugging:</p>
+
+<blockquote><pre class="code">print command = cat %s &gt;&gt;/tmp/printlog; lpr -r -P%p %s</pre></blockquote>
+
+<p>Using the previous configuration, it is possible to verify that files
+are actually being delivered to the Samba server. If they are, their
+contents will show up in the file <em class="filename">/tmp/printlog</em>.</p>
+
+<p>After BSD, the next most popular kind of printing system is SYSV (or
+System V) printing, plus some SYSV variants for
+IBM's AIX and Hewlett-Packard's
+HP-UX. These systems do not have an
+<em class="filename">/etc/printcap</em> file. Instead, the
+<tt class="literal">printcap</tt> <tt class="literal">file</tt> option can be set
+to an appropriate <em class="emphasis">lpstat</em> command for the system.
+This tells Samba to get a list of printers from the
+<em class="emphasis">lpstat</em> command. Alternatively, you can set the
+global configuration option <tt class="literal">printcap</tt>
+<tt class="literal">name</tt> to the name of a dummy
+<em class="filename">printcap</em> file you provide. In the latter case,
+the file must contain a series of lines such as:</p>
+
+<blockquote><pre class="code">lp|print1|My Printer 1
+print2|My Printer 2
+print3|My Printer 3</pre></blockquote>
+
+<p>Each line names a printer followed by aliases for it. In this
+example, the first printer is called <tt class="literal">lp</tt>,
+<tt class="literal">print1</tt>, or <tt class="literal">My</tt>
+<tt class="literal">Printer</tt> <tt class="literal">1</tt>, whichever the user
+prefers to use. The first name is used in place of
+<tt class="literal">%p</tt> in any command Samba executes for that printer.</p>
+
+<p>Two additional printer types are also supported by Samba: LPRNG (LPR
+New Generation) and PLP (Public Line Printer). These are public
+domain and open source printing systems and are used by many sites to
+overcome problems with vendor-supplied software. Samba also supports
+the printing systems of the SOFTQ and QNX real-time operating
+systems.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.8"/>
+
+<h3 class="head3">printcap name</h3>
+
+<p>If the <tt class="literal">printcap</tt><a name="INDEX-65"/><a name="INDEX-66"/>
+<tt class="literal">name</tt> option (also called
+<tt class="literal">printcap</tt>) appears in a printing share, Samba uses
+the file specified as the system printer capabilities file (normally
+<em class="filename">/etc/printcap</em>). However, you can reset it to a
+file consisting of only the printers you want to share over the
+network. The value must be the filename (with its complete path
+specified) of a printer capabilities file on the server:</p>
+
+<blockquote><pre class="code">[deskjet]
+    printcap name = /usr/local/samba/lib/printcap</pre></blockquote>
+
+<p>The CUPS printing system uses its own method of determining printer
+capabilities, rather than the standard <em class="filename">printcap</em>
+file. In this case, set <tt class="literal">printcap</tt>
+<tt class="literal">name</tt> as follows:</p>
+
+<blockquote><pre class="code">[global]
+    printing = cups
+    printcap name = cups</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.9"/>
+
+<h3 class="head3">min print space</h3>
+
+<p>The <tt class="literal">min</tt><a name="INDEX-67"/> <tt class="literal">print</tt>
+<tt class="literal">space</tt> option sets the amount of space that must be
+available on the disk that contains the spool directory if printing
+is to be allowed. Setting it to zero (the default) turns the check
+off; setting it to any other number sets the amount of free space in
+kilobytes required. This option helps to avoid having print jobs fill
+up the remaining disk space on the server, which can cause other
+processes to fail:</p>
+
+<blockquote><pre class="code">[deskjet]
+    min print space = 4000</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.10"/>
+
+<a name="INDEX-68"/><h3 class="head3">queuepause command</h3>
+
+<p>This configuration option specifies a command that tells Samba how to
+pause an entire print queue, as opposed to a single job on the queue.
+The default value depends on the printing type chosen. You should not
+need to alter this option.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-10-SECT-2.3.11"/>
+
+<a name="INDEX-69"/><h3 class="head3">queueresume command</h3>
+
+<p>This configuration option specifies a command that tells Samba how to
+resume a paused print queue, as opposed to resuming a single job on
+the print queue. The default value depends on the printing type
+chosen. You should not need to alter this option. <a name="INDEX-70"/> <a name="INDEX-71"/> <a name="INDEX-72"/><a name="INDEX-73"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> If
+you are using Linux, you can use the <em class="emphasis">checkpc</em>
+command to check for this type of error.</p> <a name="FOOTNOTE-2"/>
+<p><a href="#FNPTR-2">[2]</a> CUPS is open source software (<a href="http://www.opensource.org">http://www.opensource.org</a>) developed by Easy
+Software Products. For more information, visit <a href="http://www.cups.org">http://www.cups.org</a>.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> We have placed annotated comments off to
+the right in case you've never dealt with this file
+before.</p> </blockquote><hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch11.html b/docs/htmldocs/using_samba/ch11.html
new file mode 100644
index 0000000000..026879db40
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch11.html
@@ -0,0 +1,2123 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 11. Additional Samba Information</h1>
+
+
+<p>This chapter wraps up our coverage of the
+<em class="filename">smb.conf</em> configuration file with some
+miscellaneous options that can perform a variety of tasks. We talk
+briefly about options for time synchronization, internationalization,
+messages, and common Windows bugs. For the most part, you will use
+these options only in isolated circumstances.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-11-SECT-1"/>
+
+<h2 class="head1">Time Synchronization</h2>
+
+<p>In a network of computers, the systems on the network must agree on
+the current time and also on what time files have been modified. One
+example of the importance of synchronization is the
+<a name="INDEX-1"/>roaming profiles we covered in
+<a href="ch04.html">Chapter 4</a>. It is vital for all clients accessing a
+roaming profile to agree on what time it is and which client last
+modified the user's profile.</p>
+
+<p><a name="INDEX-2"/>Time synchronization can also be
+very important to programmers. A useful group of settings consists of
+the following options:</p>
+
+<blockquote><pre class="code">[global]
+    time server = yes
+    dos filetimes = yes
+    fake directory create times = yes
+    dos filetime resolution = yes
+    delete readonly = yes</pre></blockquote>
+
+<p>If you set these options, Samba shares will provide compatibility of
+file-modification times that Visual C++, <em class="emphasis">nmake</em>,
+and other Microsoft programming tools require. Otherwise, PC
+<em class="emphasis">make</em> programs might think that all the files in
+a directory need to be recompiled every time. Obviously, this is not
+the behavior you want.</p>
+
+<p>In <a href="ch04.html">Chapter 4</a>, we showed you how to create a logon
+script that used the <em class="emphasis">net
+time</em><a name="INDEX-3"/> command to synchronize
+clients' clocks automatically when they log on to
+the domain. If your network is configured as a workgroup rather than
+a domain, you can still make use of <em class="emphasis">net time</em> by
+placing the command:</p>
+
+<blockquote><pre class="code">net time \\<em class="replaceable">sambaserver</em> /set /yes</pre></blockquote>
+
+<p>in a startup script on each client that is run when the system boots.
+Samba always provides time service&mdash;regardless of whether it is
+running as a primary domain controller&mdash;or the
+<tt class="literal">time</tt> <tt class="literal">service</tt> configuration file
+parameter is set.</p>
+
+<p>Assuming that domain users log on to the domain at least once per day
+and workgroup clients reboot frequently, the <em class="emphasis">net
+time</em> command can keep client systems'
+clocks fairly well synchronized. However, sometimes domain users stay
+logged on for longer periods, and workgroup clients can run for days
+between reboots. In the meantime, the systems'
+hardware clocks can wander enough to become a problem. It might be
+possible to work around this, depending on the version of Windows the
+client system is running. On Windows 98/Me, you can use the Task
+Scheduler to run the <em class="emphasis">net time</em> command at regular
+intervals. Likewise, on Windows 2000/XP you can use the MS-DOS
+<em class="emphasis">at</em> command. However, a better way to deal with
+this issue is to use Network Time Protocol, which we will discuss
+shortly.</p>
+
+<p>Proper time synchronization is also important when operating in an
+Active Directory domain because Active Directory uses
+<a name="INDEX-4"/>Kerberos authentication.
+When a Kerberos domain controller creates an authentication ticket
+for a client, the time is encoded into the challenge-and-response
+exchanges between the client and domain controller. If the
+client's clock disagrees with the
+server's clock, authentication can fail.</p>
+
+<p>To provide proper time synchronization in <a name="INDEX-5"/>Active Directory domains, Microsoft has
+adopted <a name="INDEX-6"/>Network Time Protocol (NTP), using the
+name Windows Time Service for its implementation. For further
+information, the Microsoft white paper entitled <em class="citetitle">The
+Windows Time Service</em> can be downloaded from <a href="http://www.microsoft.com">http://www.microsoft.com</a>.</p>
+
+<p>The nice thing about this is that NTP is the standard method for
+synchronizing Unix hosts on a network, so you can synchronize all
+your Unix systems (including the Samba server) and Windows systems
+with the following method:</p>
+
+<ol><li>
+<p>Run NTP on the Unix systems in your network. For more information on
+using NTP, refer to <a href="http://www.ntp.org">http://www.ntp.org</a>.</p>
+</li><li>
+<p>Use one of the Unix systems (such as the Samba host system) as an NTP
+server to serve Windows 2000/XP clients.</p>
+</li><li>
+<p>For other Windows clients, you might have to download an update from
+Microsoft to add <a name="INDEX-7"/><a name="INDEX-8"/>Windows Time Service client support or
+use a third-party application such as the free
+<a name="INDEX-9"/>analogX Atomic TimeSync (<a href="http://www.analogx.com">http://www.analogx.com</a>). Or you can use the
+<em class="emphasis">net time</em> command to update the
+client's clock periodically, as discussed
+previously.</p>
+</li></ol>
+
+<div class="sect2"><a name="samba2-CHP-11-SECT-1.1"/>
+
+<h3 class="head2">Time-Synchronization Options</h3>
+
+<p>To support roaming profiles, programmers accessing your Samba server,
+and other time-sensitive functions on your network,
+you'll want to be aware of the options listed in
+<a href="ch11.html#samba2-CHP-11-TABLE-1">Table 11-1</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-1"/><h4 class="head4">Table 11-1. Time-synchronization options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">time server</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, announces <em class="emphasis">nmbd</em> as an
+SMB time service to Windows clients</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">time offset</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Adds a specified number of minutes to the reported time</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">dos filetimes</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Allows non-owners of a file to change its time if they can write to it</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">dos filetime</tt></p>
+
+<p><tt class="literal">resolution</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Causes file times to be rounded to the next even second</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">fake directory</tt> <tt class="literal">create times</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Sets directory times to avoid an MS <em class="emphasis">nmake</em> bug</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-1.1.1"/>
+
+<a name="INDEX-12"/><h3 class="head3">time server</h3>
+
+<p>Samba always operates as an SMB time server, matching the behavior of
+Windows systems. However, Samba's default is not to
+advertise itself as a time server to the network. When this option is
+set to <tt class="literal">yes</tt>, Samba advertises itself as an SMB time
+server:</p>
+
+<blockquote><pre class="code">[global]
+    time service = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-1.1.2"/>
+
+<a name="INDEX-13"/><h3 class="head3">time offset</h3>
+
+<p>To deal with clients that don't properly process
+daylight savings time, Samba provides the <tt class="literal">time</tt>
+<tt class="literal">offset</tt> option. If set, it adds the specified
+number of minutes to the current time. This is handy if
+you're in Newfoundland and Windows
+doesn't know about the 30-minute time difference
+there:</p>
+
+<blockquote><pre class="code">[global]
+    time offset = 30</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-1.1.3"/>
+
+<a name="INDEX-14"/><h3 class="head3">dos filetimes</h3>
+
+<p>Traditionally, only the root user and the owner of a file can change
+its last-modified date on a Unix system. The share-level
+<tt class="literal">dos</tt> <tt class="literal">filetimes</tt> option allows the
+Samba server to mimic the characteristics of a DOS or Windows system:
+any user can change the last-modified date on a file in that share if
+she has write permission to it. To do this, Samba uses its root
+privileges to modify the timestamp on the file.</p>
+
+<p>By default, this option is disabled. Setting this option to
+<tt class="literal">yes</tt> is often necessary to allow PC
+<em class="emphasis">make</em> programs to work properly. Without it, they
+cannot change the last-modified date themselves. This often results
+in the program thinking <em class="emphasis">all</em> files need
+recompiling when they really don't.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-1.1.4"/>
+
+<h3 class="head3">dos filetime resolution</h3>
+
+<p>The <tt class="literal">dos</tt><a name="INDEX-15"/>
+<tt class="literal">filetime</tt> <tt class="literal">resolution</tt> parameter
+is a share-level option. If set to <tt class="literal">yes</tt>, Samba
+rounds file times to the closest 2-second boundary. This option
+exists primarily to satisfy a quirk in Windows that prevents Visual
+C++ from correctly recognizing that a file has not changed. You can
+enable it as follows:</p>
+
+<blockquote><pre class="code">[data]
+    dos filetime resolution = yes</pre></blockquote>
+
+<p>We recommend using this option only if you are using Microsoft Visual
+C++ on a Samba share that supports opportunistic locking.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-1.1.5"/>
+
+<h3 class="head3">fake directory create times</h3>
+
+<p>The <tt class="literal">fake</tt><a name="INDEX-16"/>
+<tt class="literal">directory</tt> <tt class="literal">create</tt>
+<tt class="literal">times</tt> option exists to keep PC
+<em class="emphasis">make</em> programs sane. VFAT and NTFS filesystems
+record the creation date of a specific directory, while Unix does
+not. Without this option, Samba takes the earliest recorded date it
+has for the directory (often the last-modified date of a file) and
+returns it to the client. If this is not sufficient, set the
+following option under a share definition:</p>
+
+<blockquote><pre class="code">[data]
+    fake directory create times = yes</pre></blockquote>
+
+<p>If set, Samba will adjust the directory create time it reports to the
+hardcoded value January 1, 1980. This is primarily used to convince
+the Visual C++ <em class="emphasis">nmake</em> program that any object
+files in its build directories are indeed younger than the creation
+date of the directory itself and need to be recompiled. <a name="INDEX-17"/> <a name="INDEX-18"/><a name="INDEX-19"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-11-SECT-2"/>
+
+<h2 class="head1">Magic Scripts</h2>
+
+<p><em class="firstterm">Magic scripts</em> are a method of running programs
+on Unix and redirecting the output back to the SMB client. These are
+essentially an experimental hack. However, some users and their
+programs still rely on these two options for their programs to
+function correctly. Magic scripts are not widely trusted, and their
+use is highly discouraged by the Samba Team.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-11-SECT-2.1"/>
+
+<h3 class="head2">Magic Script Options</h3>
+
+<p><a href="ch11.html#samba2-CHP-11-TABLE-2">Table 11-2</a> lists the options that deal with
+<a name="INDEX-20"/>magic scripts
+on the Samba server.</p>
+
+<a name="samba2-CHP-11-TABLE-2"/><h4 class="head4">Table 11-2. Magic script options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">magic</tt> <tt class="literal">script</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>File to be executed by Samba, as the logged-on user, when closed</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">magic</tt> <tt class="literal">output</tt></p>
+</td>
+<td>
+<p>string (filename)</p>
+</td>
+<td>
+<p>File to log output from the magic file</p>
+</td>
+<td>
+<p><em class="emphasis">scriptname.out</em></p>
+</td>
+<td>
+<p>Share</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-2.1.1"/>
+
+<h3 class="head3">magic script</h3>
+
+<p>If the <tt class="literal">magic</tt><a name="INDEX-21"/>
+<tt class="literal">script</tt> option is set to a filename and the client
+creates a file by that name in that share, Samba will run the file as
+soon as the user has opened and closed it. For example,
+let's assume that the following option was created
+in the share <tt class="literal">[accounting]</tt>:</p>
+
+<blockquote><pre class="code">[accounting]
+    magic script = tally.sh</pre></blockquote>
+
+<p>Samba continually monitors the files in that share. If one by the
+name of <em class="emphasis">tally.sh</em> is closed (after being opened)
+by a user, Samba will execute the contents of that file locally. The
+file will be passed to the shell to execute; it must therefore be a
+legal Unix shell script. This means that it must have newline
+characters as line endings instead of Windows CRLFs. In addition, you
+need to use the <tt class="literal">#!</tt> directive at the beginning of
+the file to indicate under which shell or interpreter the script
+should run, unless the script is for the default shell on your
+system.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-2.1.2"/>
+
+<a name="INDEX-22"/><h3 class="head3">magic output</h3>
+
+<p>This option specifies an output file to which the script specified by
+the <tt class="literal">magic</tt> <tt class="literal">script</tt> option will
+send output. You must specify a filename in a writable directory:</p>
+
+<blockquote><pre class="code">[accounting]
+    magic script = tally.sh
+    magic output = /var/log/magicoutput</pre></blockquote>
+
+<p>If this option is omitted, the default output file is the name of the
+script (as stated in the <tt class="literal">magic</tt>
+<tt class="literal">script</tt> option) with the extension
+<em class="emphasis">.out</em> appended onto it.</p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-11-SECT-3"/>
+
+<h2 class="head1">Internationalization</h2>
+
+<p><a name="INDEX-23"/><a name="INDEX-24"/>Starting
+with Samba 3.0, Samba supports Unicode &quot;on the
+wire,&quot; requiring no additional effort on your part
+to support filenames and other text containing characters in
+international character sets.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-11-SECT-3.1"/>
+
+<h3 class="head2">Internationalization Options</h3>
+
+<p>Samba 2.2.x has a limited ability to speak foreign tongues: if you
+need to support filenames containing characters that
+aren't in standard ASCII, some options that can help
+you are shown in <a href="ch11.html#samba2-CHP-11-TABLE-3">Table 11-3</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-3"/><h4 class="head4">Table 11-3. Internationalization options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">client code</tt> <tt class="literal">page</tt></p>
+</td>
+<td>
+<p>Described in this section</p>
+</td>
+<td>
+<p>Sets a code page to expect from clients</p>
+</td>
+<td>
+<p>850</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">character set</tt></p>
+</td>
+<td>
+<p>Described in this section</p>
+</td>
+<td>
+<p>Translates code pages into alternate Unix character sets</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">coding system</tt></p>
+</td>
+<td>
+<p>Described in this section</p>
+</td>
+<td>
+<p>Translates code page 932 into an Asian character set</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">valid chars</tt></p>
+</td>
+<td>
+<p>string (set of characters)</p>
+</td>
+<td>
+<p>Adds individual characters to a code page</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-3.1.1"/>
+
+<h3 class="head3">client code page</h3>
+
+<p>The character sets on Windows platforms hark back to the original
+concept of a <em class="emphasis">code page</em><a name="INDEX-25"/>. These code pages are used by DOS and
+Windows clients to determine rules for mapping lowercase letters to
+uppercase letters. Samba can be instructed to use a variety of code
+pages through the use of the global
+<tt class="literal">client</tt><a name="INDEX-26"/> <tt class="literal">code</tt>
+<tt class="literal">page</tt> option to match the corresponding code page
+in use on the client. This option loads a code page definition file
+and can take the values specified in <a href="ch11.html#samba2-CHP-11-TABLE-4">Table 11-4</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-4"/><h4 class="head4">Table 11-4. Valid code pages with Samba 2.0</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Code page</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">437</tt></p>
+</td>
+<td>
+<p>MS-DOS Latin (United States)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">737</tt></p>
+</td>
+<td>
+<p>Windows 95 Greek</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">850</tt></p>
+</td>
+<td>
+<p>MS-DOS Latin 1 (Western European)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">852</tt></p>
+</td>
+<td>
+<p>MS-DOS Latin 2 (Eastern European)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">861</tt></p>
+</td>
+<td>
+<p>MS-DOS Icelandic</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">866</tt></p>
+</td>
+<td>
+<p>MS-DOS Cyrillic (Russian)</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">932</tt></p>
+</td>
+<td>
+<p>MS-DOS Japanese Shift-JIS</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">936</tt></p>
+</td>
+<td>
+<p>MS-DOS Simplified Chinese</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">949</tt></p>
+</td>
+<td>
+<p>MS-DOS Korean Hangul</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">950</tt></p>
+</td>
+<td>
+<p>MS-DOS Traditional Chinese</p>
+</td>
+</tr>
+
+</table>
+
+<p>You can set the client code page as follows:</p>
+
+<blockquote><pre class="code">[global]
+    client code page = 852</pre></blockquote>
+
+<p>The default value of this option is 850, for MS-DOS Latin 1. You can
+use the <em class="emphasis">make_smbcodepage</em> tool that comes with
+Samba (by default in <em class="filename">/usr/local/samba/bin</em> ) to
+create your own SMB code pages, in the event that those listed
+earlier are not sufficient.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-3.1.2"/>
+
+<h3 class="head3">character set</h3>
+
+<p>The global <tt class="literal">character</tt><a name="INDEX-27"/>
+<tt class="literal">set</tt> option can be used to convert filenames
+offered through a DOS code page (see the previous section, <a href="ch11.html#samba2-CHP-11-SECT-3.1.1">Section 11.3.1.1</a>) to equivalents that can be
+represented by Unix character sets other than those in the United
+States. For example, if you want to convert the Western European
+MS-DOS character set on the client to a Western European Unix
+character set on the server, you can use the following in your
+configuration file:</p>
+
+<blockquote><pre class="code">[global]
+    client code page = 850
+    character set = ISO8859-1</pre></blockquote>
+
+<p>Note that you must include a <tt class="literal">client</tt>
+<tt class="literal">code</tt> <tt class="literal">page</tt> option to specify the
+character set from which you are converting. The valid character sets
+(and their matching code pages) that Samba accepts are listed in
+<a href="ch11.html#samba2-CHP-11-TABLE-5">Table 11-5</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-5"/><h4 class="head4">Table 11-5. Valid character sets</h4><table border="1">
+
+
+
+
+<tr>
+<th>
+<p>Character set</p>
+</th>
+<th>
+<p>Matching code page</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">ISO8859-1</tt></p>
+</td>
+<td>
+<p><tt class="literal">850</tt></p>
+</td>
+<td>
+<p>Western European Unix</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ISO8859-2</tt></p>
+</td>
+<td>
+<p><tt class="literal">852</tt></p>
+</td>
+<td>
+<p>Eastern European Unix</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ISO8859-5</tt></p>
+</td>
+<td>
+<p><tt class="literal">866</tt></p>
+</td>
+<td>
+<p>Russian Cyrillic Unix</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ISO8859-7</tt></p>
+</td>
+<td>
+<p>737</p>
+</td>
+<td>
+<p>Greek Unix</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">KOI8-R</tt></p>
+</td>
+<td>
+<p><tt class="literal">866</tt></p>
+</td>
+<td>
+<p>Alternate Russian Cyrillic Unix</p>
+</td>
+</tr>
+
+</table>
+
+<p>Normally, the <tt class="literal">character</tt> <tt class="literal">set</tt>
+option is disabled completely.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-3.1.3"/>
+
+<h3 class="head3">coding system</h3>
+
+<p>The <tt class="literal">coding</tt><a name="INDEX-28"/> <tt class="literal">system</tt>
+option is similar to the <tt class="literal">character</tt>
+<tt class="literal">set</tt> option. However, its purpose is to determine
+how to convert a Japanese Shift JIS code page into an appropriate
+Unix character set. To use this option, the <tt class="literal">client</tt>
+<tt class="literal">code</tt> <tt class="literal">page</tt> option described
+previously must be set to page <tt class="literal">932</tt>. The valid
+coding systems that Samba accepts are listed in <a href="ch11.html#samba2-CHP-11-TABLE-6">Table 11-6</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-6"/><h4 class="head4">Table 11-6. Valid coding-system parameters</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Character set</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">SJIS</tt></p>
+</td>
+<td>
+<p>Standard Shift JIS</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JIS8</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J8BB</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J8BH</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J8@B</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J8@J</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J8@H</tt></p>
+</td>
+<td>
+<p>Eight-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JIS7</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J7BB</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J7BH</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J7@B</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J7@J</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">J7@H</tt></p>
+</td>
+<td>
+<p>Seven-bit JIS codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JUNET</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JUBB</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JUBH</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JU@B</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JU@J</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">JU@H</tt></p>
+</td>
+<td>
+<p>JUNET codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">EUC</tt></p>
+</td>
+<td>
+<p>EUC codes</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">HEX</tt></p>
+</td>
+<td>
+<p>Three-byte hexadecimal code</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">CAP</tt></p>
+</td>
+<td>
+<p>Three-byte hexadecimal code (Columbia AppleTalk Program)</p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-3.1.4"/>
+
+<h3 class="head3">valid chars</h3>
+
+<p>The <tt class="literal">valid</tt><a name="INDEX-29"/> <tt class="literal">chars</tt> option
+can be used to add individual characters to a code page. You can use
+this option as follows:</p>
+
+<blockquote><pre class="code">valid chars = &Icirc;
+valid chars = 0450:0420 0x0A20:0x0A00
+valid chars = A:a</pre></blockquote>
+
+<p>Each character in the list specified should be separated by spaces.
+If there is a colon between two characters or a numerical equivalent,
+the data to the left of the colon is considered an uppercase
+character, while the data to the right is considered the lowercase
+character. You can represent characters both by literals (if you can
+type them) and by octal, hexadecimal, or decimal Unicode equivalents.</p>
+
+<p>If you use this option, it must be listed after the
+<tt class="literal">client</tt> <tt class="literal">code</tt>
+<tt class="literal">page</tt> to which you wish to add the character.
+<a name="INDEX-30"/><a name="INDEX-31"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-11-SECT-4"/>
+
+<h2 class="head1">Windows Messenger Service</h2>
+
+<p>One of the odd features of SMB protocol is its ability to send text
+messages between computers. Although both the name and functionality
+are similar to that of Windows Messenger, the two are not the same.
+<a name="INDEX-32"/><a name="INDEX-33"/><a name="INDEX-34"/>Windows Messenger (also called MSN
+Messenger) is an Internet-oriented instant messenging service, while
+Windows Messenger Service is an older and simpler LAN-oriented
+service. Using the Windows Messenger Service, messages can be
+addressed to users, individual computers, or entire workgroups on the
+network.</p>
+
+<p>The <a name="INDEX-35"/>WinPopup
+tool (<em class="filename">Winpopup.exe</em>), shown in <a href="ch11.html#samba2-CHP-11-FIG-1">Figure 11-1</a>, can be used on Windows 95/98/Me to send or
+receive messages. WinPopup is a handy tool for sending messages.
+However, to receive messages, it must already be running when the
+message is sent from the remote system.</p>
+
+<div class="figure"><a name="samba2-CHP-11-FIG-1"/><img src="figs/sam2_1101.gif"/></div><h4 class="head4">Figure 11-1. Sending a message from a Windows 95/98/Me system (left); receiving a message (right)</h4>
+
+<p>On Windows NT/2000/XP, the messenger service lets you receive
+messages without having an application already running; messages will
+automatically appear in a small dialog box on the screen when
+received, as shown in <a href="ch11.html#samba2-CHP-11-FIG-2">Figure 11-2</a>.</p>
+
+<div class="figure"><a name="samba2-CHP-11-FIG-2"/><img src="figs/sam2_1102.gif"/></div><h4 class="head4">Figure 11-2. Receiving a message on a Windows 2000 system</h4>
+
+<p>To send messages, it is necessary to use the <em class="emphasis">net
+send</em> command from a command-prompt window, like this:</p>
+
+<blockquote><pre class="code">C:\&gt; <tt class="userinput"><b>net send maya &quot;Who's There?&quot;</b></tt>
+The message was successfully sent to MAYA.</pre></blockquote>
+
+
+<div class="sect2"><a name="samba2-CHP-11-SECT-4.1"/>
+
+<h3 class="head2">Windows Messenger Service Configuration Option</h3>
+
+<p>Samba has a single option to handle Windows Messenger Service,
+<tt class="literal">message</tt> <tt class="literal">command</tt>, as shown in
+<a href="ch11.html#samba2-CHP-11-TABLE-7">Table 11-7</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-7"/><h4 class="head4">Table 11-7. Windows Messenger Service configuration option</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameter</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">message</tt> <tt class="literal">command</tt></p>
+</td>
+<td>
+<p>string (shell command)</p>
+</td>
+<td>
+<p>Sets a command to run on Unix when a WinPopup message is received</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-4.1.1"/>
+
+<h3 class="head3">message command</h3>
+
+<p>Samba's
+<tt class="literal">message</tt><a name="INDEX-36"/> <tt class="literal">command</tt>
+option defines the command that will run on the server when a Windows
+Messenger Service message arrives. The command will be executed as
+the <tt class="literal">guest</tt> <tt class="literal">account</tt> user. What to
+do with messages is questionable because most Samba hosts run as
+unattended servers. One solution is to mail the messages to root like
+this:</p>
+
+<blockquote><pre class="code">[global]
+    message command = /bin/mail -s &quot;SMB Message From %f on %m&quot; root &lt;%s; rm %s</pre></blockquote>
+
+<p>Note the use of variables here. The <tt class="literal">%s</tt> variable
+will be replaced by the name of the file in which the message
+resides. This file should be deleted when the command is finished
+with it; otherwise, a buildup of message files will collect on the
+Samba server. In addition, the command must either exit quickly or
+fork its own process (using an <tt class="literal">&amp;</tt> after the
+command); otherwise, the client might suspend and wait for
+notification that the command was sent successfully before
+continuing.</p>
+
+<p>In addition to the standard variables, <a href="ch11.html#samba2-CHP-11-TABLE-8">Table 11-8</a>
+shows the three unique variables that you can use in a
+<tt class="literal">message</tt> <tt class="literal">command</tt>.</p>
+
+<a name="samba2-CHP-11-TABLE-8"/><h4 class="head4">Table 11-8. message command variables</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Variable</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">%s</tt></p>
+</td>
+<td>
+<p>The name of the file in which the message resides</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%f</tt></p>
+</td>
+<td>
+<p>The name of the system that sent the message</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">%t</tt></p>
+</td>
+<td>
+<p>The name of the system that is the destination of the message
+<a name="INDEX-37"/><a name="INDEX-38"/><a name="INDEX-39"/></p>
+</td>
+</tr>
+
+</table>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-11-SECT-5"/>
+
+<h2 class="head1">Miscellaneous Options</h2>
+
+<p>Many Samba options are available to deal with operating system issues
+on either Unix or Windows. In particular, some of these options are
+used for setting limits for clients' use of
+resources on the Unix server. The options shown in <a href="ch11.html#samba2-CHP-11-TABLE-9">Table 11-9</a> deal with some of these issues.</p>
+
+<a name="samba2-CHP-11-TABLE-9"/><h4 class="head4">Table 11-9. Miscellaneous options</h4><table border="1">
+
+
+
+
+
+
+<tr>
+<th>
+<p>Option</p>
+</th>
+<th>
+<p>Parameters</p>
+</th>
+<th>
+<p>Function</p>
+</th>
+<th>
+<p>Default</p>
+</th>
+<th>
+<p>Scope</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p><tt class="literal">deadtime</tt></p>
+</td>
+<td>
+<p>numeric (minutes)</p>
+</td>
+<td>
+<p>Number of minutes of inactivity before a connection should be
+terminated.</p>
+</td>
+<td>
+<p><tt class="literal">0</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">dfree command</tt></p>
+</td>
+<td>
+<p>string (command)</p>
+</td>
+<td>
+<p>Used to specify a command that returns free disk space in a format
+recognized by Samba.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">fstype</tt></p>
+</td>
+<td>
+<p><tt class="literal">NTFS</tt>, <tt class="literal">FAT</tt>, or
+<tt class="literal">Samba</tt></p>
+</td>
+<td>
+<p>Filesystem type reported by the server to the client.</p>
+</td>
+<td>
+<p><tt class="literal">NTFS</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">keepalive</tt></p>
+</td>
+<td>
+<p>numeric (seconds)</p>
+</td>
+<td>
+<p>Number of seconds between checks for an inoperative client.</p>
+</td>
+<td>
+<p><tt class="literal">300</tt> (none)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max disk size</tt></p>
+</td>
+<td>
+<p>numeric (MB)</p>
+</td>
+<td>
+<p>Largest disk size to return to a client, some of which have limits.
+Does not affect actual operations on the disk.</p>
+</td>
+<td>
+<p><tt class="literal">0</tt> (infinity)</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max mux</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Maximum number of simultaneous SMB operations that clients can make.</p>
+</td>
+<td>
+<p><tt class="literal">50</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max open files</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Limits number of open files to be below Unix limits.</p>
+</td>
+<td>
+<p><tt class="literal">10000</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">max xmit</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Specifies the maximum packet size that Samba will send.</p>
+</td>
+<td>
+<p><tt class="literal">65535</tt> or <tt class="literal">16644</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">nt pipe support</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Turns off an NT/2000/XP support feature; for benchmarking or in case
+of an error.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">nt smb support</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Turns off an NT/2000/XP support feature; for benchmarking or in case
+of an error.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">ole locking</tt> <tt class="literal">compatibility</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>Remaps out-of-range lock requests used on Windows to fit in allowable
+range on Unix. Turning it off causes Unix lock errors.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">panic action</tt></p>
+</td>
+<td>
+<p>string</p>
+</td>
+<td>
+<p>Command to run if Samba server fails; for debugging.</p>
+</td>
+<td>
+<p>None</p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">set directory</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows VMS clients to issue
+<tt class="literal">set</tt> <tt class="literal">dir</tt> commands.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">status</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, allows Samba to monitor status for
+<tt class="literal">smbstatus</tt> command.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">strict sync</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">no</tt>, ignores Windows application requests to
+perform a sync-to-disk.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">sync always</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, forces all client writes to be committed
+to disk before returning from the call.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">strip dot</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, strips trailing dots from Unix filenames.</p>
+</td>
+<td>
+<p><tt class="literal">no</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">change notify timeout</tt></p>
+</td>
+<td>
+<p>numeric (seconds)</p>
+</td>
+<td>
+<p>Interval between checks when a client asks to wait for a change in a
+specified directory.</p>
+</td>
+<td>
+<p><tt class="literal">60</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">stat cache</tt></p>
+</td>
+<td>
+<p>Boolean</p>
+</td>
+<td>
+<p>If <tt class="literal">yes</tt>, Samba will cache recent name mappings.</p>
+</td>
+<td>
+<p><tt class="literal">yes</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+<tr>
+<td>
+<p><tt class="literal">stat cache size</tt></p>
+</td>
+<td>
+<p>numeric</p>
+</td>
+<td>
+<p>Number of entries in the stat cache.</p>
+</td>
+<td>
+<p><tt class="literal">50</tt></p>
+</td>
+<td>
+<p>Global</p>
+</td>
+</tr>
+
+</table>
+
+
+<div class="sect2"><a name="samba2-CHP-11-SECT-5.1"/>
+
+<a name="INDEX-40"/><h3 class="head2">deadtime</h3>
+
+<p>This global option sets the number of minutes that Samba will wait
+for an inactive client before closing its session with the Samba
+server. A client is considered inactive when it has no open files and
+no data is being sent from it. The default value for this option is
+0, which means that Samba never closes any connection, regardless of
+how long they have been inactive. This can lead to unnecessary
+consumption of the server's resources by inactive
+clients. We recommend that you override the default as follows:</p>
+
+<blockquote><pre class="code">[global]
+    deadtime = 10</pre></blockquote>
+
+<p>This tells Samba to terminate any inactive client sessions after 10
+minutes. For most networks, setting this option as such will not
+inconvenience users because reconnections from the client are
+generally performed transparently to the user. See also the
+<tt class="literal">keepalive</tt> parameter.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.1"/>
+
+<a name="INDEX-41"/><h3 class="head3">dfree command</h3>
+
+<p>This global option is used on systems that incorrectly determine the
+free space left on the disk. So far, the only confirmed system that
+needs this option set is Ultrix. There is no default value for this
+option, which means that Samba already knows how to compute the free
+disk space on its own and the results are considered reliable. You
+can override it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    dfree command = /usr/local/bin/dfree</pre></blockquote>
+
+<p>This option should point to a script that returns the total disk
+space in a block and the number of available blocks. The Samba
+documentation recommends the following as a usable script:</p>
+
+<blockquote><pre class="code">#!/bin/sh
+df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'</pre></blockquote>
+
+<p>On System V machines, the following will work:</p>
+
+<blockquote><pre class="code">#!/bin/sh
+/usr/bin/df $1 | tail -1 | awk '{print $3&quot; &quot;$5}'</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.2"/>
+
+<a name="INDEX-42"/><h3 class="head3">fstype</h3>
+
+<p>This share-level option sets the type of filesystem that Samba
+reports when queried by the client. Three strings can be used as a
+value to this configuration option, as listed in <a href="ch11.html#samba2-CHP-11-TABLE-10">Table 11-10</a>.</p>
+
+<a name="samba2-CHP-11-TABLE-10"/><h4 class="head4">Table 11-10. Filesystem types</h4><table border="1">
+
+
+
+<tr>
+<th>
+<p>Value</p>
+</th>
+<th>
+<p>Definition</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>NTFS</p>
+</td>
+<td>
+<p>Microsoft Windows NT filesystem</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>FAT</p>
+</td>
+<td>
+<p>DOS FAT filesystem</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Samba</p>
+</td>
+<td>
+<p>Samba filesystem</p>
+</td>
+</tr>
+
+</table>
+
+<p>The default value for this option is <tt class="literal">NTFS</tt>, which
+represents a Windows NT filesystem. There probably
+isn't a need to specify any other type of
+filesystem. However, if you need to, you can override the default
+value per share as follows:</p>
+
+<blockquote><pre class="code">[data]
+    fstype = FAT</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.3"/>
+
+<a name="INDEX-43"/><h3 class="head3">keepalive</h3>
+
+<p>This global option specifies the number of seconds that Samba waits
+between sending NetBIOS <em class="emphasis">keepalive packets</em>. These
+packets are used to ping a client to detect whether it is still alive
+and on the network. The default value for this option is
+<tt class="literal">300</tt> (5 minutes), which you can override as
+follows:</p>
+
+<blockquote><pre class="code">[global]
+    keepalive = 600</pre></blockquote>
+
+<p>The value of <tt class="literal">600</tt> (10 minutes) is good for networks
+populated by reliable clients. If your network contains relatively
+unreliable clients, you might prefer to set
+<tt class="literal">keepalive</tt> to a lower value, such as
+<tt class="literal">30</tt>. If <tt class="literal">keepalive</tt> is set to 0,
+no NetBIOS keepalive packets will be sent. See also the
+<tt class="literal">deadtime</tt> parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.4"/>
+
+<a name="INDEX-44"/><h3 class="head3">max disk size</h3>
+
+<p>This global option specifies an illusory limit, in megabytes, for
+each share that Samba is offering. It only affects how much disk
+space Samba reports the share as having and does not prevent more
+disk space from actually being available for use. You would typically
+set this option to prevent clients with older operating
+systems&mdash;or running buggy applications&mdash;from being confused
+by large disk spaces. For example, some older Windows applications
+become confused when they encounter a share larger than 1 gigabyte.
+To work around this problem, <tt class="literal">max</tt>
+<tt class="literal">disk</tt> <tt class="literal">size</tt> can be set as
+follows:</p>
+
+<blockquote><pre class="code">[global]
+    max disk size = 1000</pre></blockquote>
+
+<p>The default value for this option is <tt class="literal">0</tt>, which
+means there is no upper limit.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.5"/>
+
+<a name="INDEX-45"/><h3 class="head3">max mux</h3>
+
+<p>This global option specifies the maximum number of concurrent SMB
+operations Samba allows. The default value for this option is
+<tt class="literal">50</tt>. You can override it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    max mux = 100</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.6"/>
+
+<a name="INDEX-46"/><h3 class="head3">max open files</h3>
+
+<p>This global option specifies the maximum number of open files that
+Samba should allow at any given time for all processes. This value
+must be equal to or less than the amount allowed by the operating
+system, which varies from system to system. The default value for
+this option is <tt class="literal">10000</tt>. You can override it as
+follows:</p>
+
+<blockquote><pre class="code">[global]
+    max open files = 8000</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.7"/>
+
+<a name="INDEX-47"/><h3 class="head3">max xmit</h3>
+
+<p>This global option sets the maximum size of packets that Samba
+exchanges with a client. In rare cases, setting a smaller maximum
+packet size can increase performance, especially with Windows for
+Workgroups. In Samba versions up to 2.2.5, the default value for this
+option is <tt class="literal">65535</tt>. In 2.2.7 and later versions, the
+default was changed to <tt class="literal">16644</tt> to match the behavior
+of Windows 2000 and improve support for Windows NT 4.0. You can
+override the default as follows:</p>
+
+<blockquote><pre class="code">[global]
+    max xmit = 4096</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.8"/>
+
+<a name="INDEX-48"/><h3 class="head3">nt pipe support</h3>
+
+<p>This global option is used by developers to allow or disallow Windows
+NT/2000/XP clients the ability to make connections to
+<a name="INDEX-49"/>NT-specific SMB IPC$ pipes. As a user, you
+should never need to override the default:</p>
+
+<blockquote><pre class="code">[global]
+    nt pipe support = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.9"/>
+
+<a name="INDEX-50"/><h3 class="head3">nt smb support</h3>
+
+<p>This global option is used by developers to negotiate NT-specific SMB
+options with Windows NT/2000/XP clients. The Samba Team has
+discovered that slightly better performance comes from setting this
+value to <tt class="literal">no</tt>. However, as a user, you should
+probably not override the default:</p>
+
+<blockquote><pre class="code">[global]
+    nt smb support = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.10"/>
+
+<a name="INDEX-51"/><h3 class="head3">ole locking compatibility</h3>
+
+<p>This global option turns off Samba's internal
+byte-range locking manipulation in files, which gives compatibility
+with Object Linking and Embedding (OLE) applications that use high
+byte-range locks as a method of interprocess communication. The
+default value for this option is <tt class="literal">yes</tt>. If you trust
+your Unix locking mechanisms, you can override it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    ole locking compatibility = no</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.11"/>
+
+<a name="INDEX-52"/><h3 class="head3">panic action</h3>
+
+<p>This global option specifies a command to execute in the event that
+Samba encounters a fatal error when loading or running. There is no
+default value for this option. You can specify an action as follows:</p>
+
+<blockquote><pre class="code">[global]
+    panic action = /bin/csh -c
+          'xedit &lt;&lt;: &quot;Samba has shutdown unexpectedly&quot;;:'</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.12"/>
+
+<a name="INDEX-53"/><h3 class="head3">set directory</h3>
+
+<p>This Boolean share-level option allows <a name="INDEX-54"/>Digital Pathworks clients to
+use the <em class="emphasis">setdir</em> command to change directories on
+the server. If you are not using the Digital Pathworks client, you
+should not need to alter this option. The default value for this
+option is <tt class="literal">no</tt>. You can override it per share as
+follows:</p>
+
+<blockquote><pre class="code">[data]
+    set directory = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.13"/>
+
+<a name="INDEX-55"/><h3 class="head3">status</h3>
+
+<p>This global option indicates whether Samba should log all active
+connections to a status file. This file is used only by the
+<em class="emphasis">smbstatus</em> command. If you have no intentions of
+using this command, you can set this option to <tt class="literal">no</tt>,
+which can result in a small increase of speed on the server. The
+default value for this option is <tt class="literal">yes</tt>. You can
+override it as follows:</p>
+
+<blockquote><pre class="code">[global]
+    status = no</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.14"/>
+
+<a name="INDEX-56"/><h3 class="head3">strict sync</h3>
+
+<p>This share-level option determines whether Samba honors all requests
+to perform a disk sync when requested to do so by a client. Many
+Windows clients request a disk sync when they are really just trying
+to flush data to their own open files. In this case, a disk sync is
+generally unnecessary on Unix due to its high reliability, and it
+mostly has the effect of substantially reducing the performance of
+the Samba host system. The default value for this option is
+<tt class="literal">no</tt>, which allows the superfluous disk sync
+requests to be ignored. You can override the default as follows:</p>
+
+<blockquote><pre class="code">[data]
+    strict sync = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.15"/>
+
+<a name="INDEX-57"/><h3 class="head3">sync always</h3>
+
+<p>This share-level option decides whether every write to disk should be
+followed by a disk synchronization before the write call returns
+control to the client. Even if the value of this option is
+<tt class="literal">no</tt>, clients can request a disk synchronization;
+see the earlier <tt class="literal">strict</tt> <tt class="literal">sync</tt>
+option. The default value for this option is <tt class="literal">no</tt>.
+You can override it per share as follows:</p>
+
+<blockquote><pre class="code">[data]
+    sync always = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.16"/>
+
+<a name="INDEX-58"/><h3 class="head3">strip dot</h3>
+
+<p>This global option determines whether to remove the trailing dot from
+Unix filenames that are formatted with a dot at the end. The default
+value for this option is <tt class="literal">no</tt>. You can override it
+per share as follows:</p>
+
+<blockquote><pre class="code">[global]
+    strip dot = yes</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.17"/>
+
+<h3 class="head3">change notify timeout</h3>
+
+<p>The <tt class="literal">change</tt><a name="INDEX-59"/>
+<tt class="literal">notify</tt> <tt class="literal">timeout</tt> global option
+emulates a Windows NT/2000 SMB feature called <em class="firstterm">change
+notification</em><a name="INDEX-60"/>. This allows a client to request
+that a Windows NT/2000 server periodically monitor a specific
+directory on a share for any changes. If changes occur, the server
+will notify the client.</p>
+
+<p>Samba performs this function for its clients at an interval that
+defaults to 1 minute (60 seconds). Performing these checks too often
+can slow down the server considerably; however, you can use this
+option to specify an alternate time that Samba should wait between
+performing checks:</p>
+
+<blockquote><pre class="code">[global]
+    change notify timeout = 30</pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.18"/>
+
+<h3 class="head3">stat cache</h3>
+
+<p>The <tt class="literal">stat</tt><a name="INDEX-61"/> <tt class="literal">cache</tt> global
+option turns on caching of recent case-insensitive name mappings. The
+default is <tt class="literal">yes</tt>. The Samba Team recommends that you
+never change this parameter.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-11-SECT-5.1.19"/>
+
+<h3 class="head3">stat cache size</h3>
+
+<p>The <tt class="literal">stat</tt><a name="INDEX-62"/> <tt class="literal">cache</tt>
+<tt class="literal">size</tt> global option sets the number of cache
+entries to be used for the <tt class="literal">stat</tt>
+<tt class="literal">cache</tt> option. The default here is
+<tt class="literal">50</tt>. Again, the Samba Team recommends that you
+never change this parameter.</p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/ch12.html b/docs/htmldocs/using_samba/ch12.html
new file mode 100644
index 0000000000..6ba643fe73
--- /dev/null
+++ b/docs/htmldocs/using_samba/ch12.html
@@ -0,0 +1,3341 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h1 class="head0">Chapter 12. Troubleshooting Samba</h1>
+
+
+<p><a name="INDEX-1"/><a name="INDEX-2"/>Samba is extremely robust. Once you have
+everything set up the way you want, you'll probably
+forget that it is running. When trouble occurs, it's
+typically during installation or when you're trying
+to reconfigure the server. Fortunately, a wide variety of resources
+are available to diagnose these troubles. While we
+can't describe in detail the solution to every
+problem you might encounter, you should be able to get a good start
+at resolving the problem by following the advice given in this
+chapter.</p>
+
+<p>The first section of this chapter lists the tool bag, a collection of
+tools available for troubleshooting Samba; the second section is a
+detailed how-to; the last section lists extra resources to track down
+particularly stubborn problems.</p>
+
+
+
+<div class="sect1"><a name="samba2-CHP-12-SECT-1"/>
+
+<h2 class="head1">The Tool Box</h2>
+
+<p><a name="INDEX-3"/><a name="INDEX-4"/>Sometimes Unix
+seems to be made up of a grab bag of applications and tools. There
+are tools to troubleshoot tools. And of course, there are several
+ways to accomplish the same task. When trying to solve a problem
+related to Samba, a good plan of attack is to use the following:</p>
+
+<ul><li>
+<p>Samba logs</p>
+</li><li>
+<p>Samba test utilities</p>
+</li><li>
+<p>Unix utilities</p>
+</li><li>
+<p>Fault tree</p>
+</li><li>
+<p>Documentation and FAQs</p>
+</li><li>
+<p>Samba newsgroups</p>
+</li><li>
+<p>Searchable mailing list archives</p>
+</li></ul>
+<p>Let's go over each of these one-by-one in the
+following sections.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-1.1"/>
+
+<h3 class="head2">Samba Logs</h3>
+
+<p><a name="INDEX-5"/><a name="INDEX-6"/>Your first line of attack should always
+be to check the log files. The Samba log files can help diagnose the
+vast majority of the problems faced by beginning- to
+intermediate-level Samba administrators. Samba is quite flexible when
+it comes to logging. You can set up the server to log as little or as
+much information as you want. Using substitution variables in the
+Samba configuration file allows you to isolate individual logs for
+each system, share, or combination thereof.</p>
+
+<p>Logs are placed in <em class="filename">/usr/local/samba/var/smbd.log</em>
+and <em class="filename">/usr/local/samba/var/nmbd.log</em> by default.
+You can specify a log directory to use with the
+<em class="emphasis">-l</em> flag on the command line when starting the
+Samba daemons. For example:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>smbd -l /var/log/samba</b></tt>
+# <tt class="userinput"><b>nmbd -l /var/log/samba</b></tt></pre></blockquote>
+
+<p>Alternatively, you can override the location and name using the
+<tt class="literal">log</tt><a name="INDEX-7"/> <tt class="literal">file</tt> configuration
+option in <em class="filename">smb.conf</em>. This option accepts all the
+substitution variables, so you could easily have the server keep a
+separate log for each connecting client system by specifying the
+following:</p>
+
+<blockquote><pre class="code">[global]
+    log file = %m.log</pre></blockquote>
+
+<p>Another useful trick is to have the server keep a log for each
+service (share) that is offered, especially if you suspect a
+particular share is causing trouble. To do this, use the
+<tt class="literal">%S</tt> variable, like this:</p>
+
+<blockquote><pre class="code">[global]
+    log file = %S.log</pre></blockquote>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.1.1"/>
+
+<h3 class="head3">Log levels</h3>
+
+<p><a name="INDEX-8"/>The level of logging that Samba uses
+can be set in the <em class="filename">smb.conf</em> file using the global
+<tt class="literal">log</tt> <tt class="literal">level</tt> or
+<tt class="literal">debug</tt> <tt class="literal">level</tt> option; they are
+equivalent. The logging level is an integer that can range from 0 to
+10. At level 0, no logging is done. Higher values result in more
+voluminous logging. For example, let's assume that
+we will use a Windows client to browse a directory on a Samba server.
+For a small amount of log information, you can use
+<tt class="literal">log</tt> <tt class="literal">level</tt> <tt class="literal">=</tt>
+<tt class="literal">1</tt>, which instructs Samba to show only cursory
+information, in this case only the connection itself:</p>
+
+<blockquote><pre class="code">05/25/02 22:02:11 server (192.168.236.86) connect to service public as user pcguest 
+(uid=503,gid=100) (pid 3377)</pre></blockquote>
+
+<p>Higher debug levels produce more detailed information. Usually, you
+won't need more than level 3, which is fully
+adequate for most Samba administrators. Levels above 3 are used by
+the developers and dump enormous amounts of cryptic information.</p>
+
+<p>Here is an example of output at levels 2 and 3 for the same
+operation. Don't worry if you don't
+understand the intricacies of an SMB connection; the point is simply
+to show you what types of information are shown at the different
+<a name="INDEX-9"/>logging levels:</p>
+
+<blockquote><pre class="code"> /* Level 2 */
+Got SIGHUP
+Processing section &quot;[homes]&quot;
+Processing section &quot;[public]&quot;
+Processing section &quot;[temp]&quot;
+Allowed connection from 192.168.236.86 (192.168.236.86) to IPC$
+Allowed connection from 192.168.236.86 (192.168.236.86) to IPC/
+
+
+/* Level 3 */
+05/25/02 22:15:09 Transaction 63 of length 67
+switch message SMBtconX (pid 3377)
+Allowed connection from 192.168.236.86 (192.168.236.86) to IPC$
+ACCEPTED: guest account and guest ok
+found free connection number 105
+Connect path is /tmp
+chdir to /tmp
+chdir to /
+05/25/02 22:15:09 server (192.168.236.86) connect to service IPC$ as user pcguest 
+(uid=503,gid=100) (pid 3377)
+05/25/02 22:15:09 tconX service=ipc$ user=pcguest cnum=105
+05/25/02 22:15:09 Transaction 64 of length 99
+switch message SMBtrans (pid 3377)
+chdir to /tmp
+trans &lt;\PIPE\LANMAN&gt; data=0 params=19 setup=0
+Got API command 0 of form &lt;WrLeh&gt; &lt;B13BWz&gt; (tdscnt=0,tpscnt=19,mdrcnt=4096,mprcnt=8)
+Doing RNetShareEnum
+RNetShareEnum gave 4 entries of 4 (1 4096 126 4096)
+05/25/02 22:15:11 Transaction 65 of length 99
+switch message SMBtrans (pid 3377)
+chdir to /
+chdir to /tmp
+trans &lt;\PIPE\LANMAN&gt; data=0 params=19 setup=0
+Got API command 0 of form &lt;WrLeh&gt; &lt;B13BWz&gt; (tdscnt=0,tpscnt=19,mdrcnt=4096,mprcnt=8)
+Doing RNetShareEnum
+RNetShareEnum gave 4 entries of 4 (1 4096 126 4096)
+05/25/02 22:15:11 Transaction 66 of length 95
+switch message SMBtrans2 (pid 3377)
+chdir to /
+chdir to /pcdisk/public
+call_trans2findfirst: dirtype = 0, maxentries = 6, close_after_first=0, close_if_end 
+= 0 requires_resume_key = 0 level = 260, max_data_bytes = 2432
+unix_clean_name [./DESKTOP.INI]
+unix_clean_name [desktop.ini]
+unix_clean_name [./]
+creating new dirptr 1 for path ./, expect_close = 1
+05/25/02 22:15:11 Transaction 67 of length 53
+switch message SMBgetatr (pid 3377)
+chdir to /
+
+<i class="lineannotation">[... deleted ...]</i></pre></blockquote>
+
+<p>We cut off this listing after the first packet because it runs on for
+many pages. However, be aware that log levels above 3 will quickly
+consume disk space with megabytes of excruciating detail concerning
+Samba's internal operations. Log level 3 is
+extremely useful for following exactly what the server is doing, and
+most of the time it will be obvious where an error occurs by glancing
+through the log file.</p>
+
+<p>Using a high log level (3 or above) will
+<em class="emphasis">seriously</em> slow down the Samba server. Remember
+that every log message generated causes a write to disk (an
+inherently slow operation) and log levels greater than 2 produce
+massive amounts of data. Essentially, you should turn on logging
+level 3 only when you're actively tracking a problem
+in the Samba server. <a name="INDEX-10"/></p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.1.2"/>
+
+<h3 class="head3">Activating and deactivating logging</h3>
+
+<p><a name="INDEX-11"/><a name="INDEX-12"/>To turn logging on and off,
+set the appropriate level in the <tt class="literal">[global]</tt> section
+of <em class="filename">smb.conf</em>. Then, you can either restart Samba
+or force the current daemon to reprocess the configuration file by
+sending it a hangup (HUP) signal. You also can send the
+<em class="emphasis">smbd</em> process a SIGUSR1 signal to increase its
+log level by one while it's running, like this:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>kill -SIGUSR1 1234</b></tt></pre></blockquote>
+
+<p>or a SIGUSR2 signal to decrease it by one:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>kill -SIGUSR2 1234</b></tt></pre></blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.1.3"/>
+
+<h3 class="head3">Logging by individual client systems or users</h3>
+
+<p>An effective way to diagnose problems without hampering other users
+is to assign different log levels for different systems in the
+<tt class="literal">[global]</tt> section of the
+<em class="filename">smb.conf</em> file. We can do this by building on the
+strategy we presented earlier:</p>
+
+<blockquote><pre class="code">[global]
+    log level = 0
+    log file = /usr/local/samba/var/log.%m
+    include = /usr/local/samba/lib/smb.conf.%m</pre></blockquote>
+
+<p>These options instruct Samba to use unique configuration and log
+files for each client that connects. Now all you have to do is create
+an <em class="filename">smb.conf</em> file for a specific client system
+with a <tt class="literal">log</tt> <tt class="literal">level</tt>
+<tt class="literal">=</tt> <tt class="literal">3</tt> entry in it (the others
+will pick up the default log level of 0) and use that log file to
+track down the problem.</p>
+
+<p>Similarly, if only particular users are experiencing a
+problem&mdash;and it travels from system to system with
+them&mdash;you can isolate logging to a specific user by adding the
+following to the <em class="filename">smb.conf</em> file:</p>
+
+<blockquote><pre class="code">[global]
+    log level = 0
+    log file = /usr/local/samba/var/log.%u
+    include = /usr/local/samba/lib/smb.conf.%u</pre></blockquote>
+
+<p>Then you can create a unique <em class="filename">smb.conf</em> file for
+each user you wish to monitor (e.g.,
+<em class="filename">/usr/local/samba/lib/smb.conf.tim</em>). Files
+containing the configuration option <tt class="literal">log</tt>
+<tt class="literal">level</tt> <tt class="literal">=</tt> <tt class="literal">3</tt>
+and only those users will get more detailed logging.<a name="INDEX-13"/><a name="INDEX-14"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-1.2"/>
+
+<h3 class="head2">Samba Test Utilities</h3>
+
+<p><a name="INDEX-15"/><a name="INDEX-16"/>A rigorous set of tests that exercise
+the major parts of Samba are described in various files in the
+<em class="emphasis">/docs/textdocs</em> directory of the Samba
+distribution kit, starting with <em class="emphasis">DIAGNOSIS.txt</em>.
+The fault tree in this chapter is a more detailed version of the
+basic tests suggested by the Samba Team, but it covers only
+installation and reconfiguration diagnosis, such as
+<em class="emphasis">DIAGNOSIS.txt</em>. The other files in the
+<em class="emphasis">/docs</em> subdirectories address specific problems
+and instruct you how to troubleshoot items not included in this book.
+If the fault tree doesn't suffice, be sure to look
+at
+<em class="emphasis">DIAGNOSIS.txt</em><a name="INDEX-17"/>
+and its friends.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-1.3"/>
+
+<h3 class="head2">Unix Utilities</h3>
+
+<p>Sometimes it's useful to use a tool outside the
+Samba suite to examine what's happening inside the
+server. Three diagnostic tools can be of particular help in debugging
+Samba troubles: <em class="emphasis">trace</em>,
+<em class="emphasis">tcpdump</em>, and <em class="emphasis">Ethereal</em>.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.3.1"/>
+
+<h3 class="head3">Using trace</h3>
+
+<p>The <em class="emphasis">trace</em><a name="INDEX-18"/> command masquerades under several
+different names, depending on the operating system you are using. On
+Linux it will be
+<em class="emphasis">strace</em><a name="INDEX-19"/>; on Solaris you'll use
+<em class="emphasis">truss</em><a name="INDEX-20"/>; SGI will have
+<em class="emphasis">padc</em><a name="INDEX-21"/> and
+<em class="emphasis">par</em><a name="INDEX-22"/>; and HP-UX will have
+<em class="emphasis">trace</em> or
+<em class="emphasis">tusc</em><a name="INDEX-23"/>. All have essentially the same
+function, which is to display each operating system function call as
+it is executed. This allows you to follow the execution of a program,
+such as the Samba server, and often pinpoints the exact call that is
+causing the difficulty.</p>
+
+<p>One problem that <em class="emphasis">trace</em> can highlight is an
+incorrect version of a dynamically linked library. This can happen if
+you've downloaded prebuilt binaries of Samba.
+You'll typically see the offending call at the end
+of the <em class="emphasis">trace</em>, just before the program
+terminates.</p>
+
+<p>A sample <em class="emphasis">strace</em> output for the Linux operating
+system follows. This is a small section of a larger file created
+during the opening of a directory on the Samba server. Each line
+lists a system call and includes its parameters and the return value.
+If there was an error, the error value (e.g.,
+<tt class="literal">ENOENT</tt>) and its explanation are also shown. You
+can look up the parameter types and the errors that can occur in the
+appropriate <em class="emphasis">trace</em> manual page for the operating
+system you are using.</p>
+
+<blockquote><pre class="code">chdir(&quot;/pcdisk/public&quot;)                 = 0
+stat(&quot;mini/desktop.ini&quot;, 0xbffff7ec)    = -1 ENOENT (No such file or directory)
+stat(&quot;mini&quot;, {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
+stat(&quot;mini/desktop.ini&quot;, 0xbffff7ec)    = -1 ENOENT (No such file or directory)
+open(&quot;mini&quot;, O_RDONLY)                  = 5
+fcntl(5, F_SETFD, FD_CLOEXEC)           = 0
+fstat(5, {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
+lseek(5, 0, SEEK_CUR)                   = 0
+SYS_141(0x5, 0xbfffdbbc, 0xedc, 0xbfffdbbc, 0x80ba708) = 196
+lseek(5, 0, SEEK_CUR)                   = 1024
+SYS_141(0x5, 0xbfffdbbc, 0xedc, 0xbfffdbbc, 0x80ba708) = 0
+close(5)                                = 0
+stat(&quot;mini/desktop.ini&quot;, 0xbffff86c)    = -1 ENOENT (No such file or directory)
+write(3, &quot;\0\0\0#\377SMB\10\1\0\2\0\200\1\0&quot;..., 39) = 39
+SYS_142(0xff, 0xbffffc3c, 0, 0, 0xbffffc08) = 1
+read(3, &quot;\0\0\0?&quot;, 4)                   = 4
+read(3, &quot;\377SMBu\0\0\0\0\0\0\0\0\0\0\0\0&quot;..., 63) = 63
+time(NULL)                              = 896143871</pre></blockquote>
+
+<p>This example shows several <em class="emphasis">stat() calls</em> failing
+to find the files they were expecting. You don't
+have to be an expert to see that the file
+<em class="emphasis">desktop.ini</em> is missing from that directory. In
+fact, many difficult problems can be identified by looking for
+obvious, repeatable errors with <em class="emphasis">trace</em>. Often,
+you need not look further than the last message before a crash.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.3.2"/>
+
+<h3 class="head3">Using tcpdump</h3>
+
+<p>The <em class="emphasis">tcpdump</em><a name="INDEX-24"/> program, as extended by Andrew
+<a name="INDEX-25"/>Tridgell,
+allows you to monitor SMB <a name="INDEX-26"/>network
+traffic in real time. A variety of output formats are available, and
+you can filter the output to look at only a particular type of
+traffic. You can examine all conversations between client and server,
+including SMB and NMB broadcast messages. While its troubleshooting
+capabilities lie mainly at the OSI network layer, you can still use
+its output to get a general idea of what the server and client are
+attempting to do.</p>
+
+<p>A sample <em class="emphasis">tcpdump</em> log follows. In this instance,
+the client has requested a directory listing, and the server has
+responded appropriately, giving the directory names
+<tt class="literal">homes</tt>, <tt class="literal">public</tt>,
+<tt class="literal">IPC$</tt>, and <tt class="literal">temp</tt>
+(we've added a few explanations on the right):</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>tcpdump -v -s 255 -i eth0 port not telnet</b></tt>
+SMB PACKET: SMBtrans (REQUEST)                <i class="lineannotation"> Request packet</i>
+SMB Command   =  0x25                         <i class="lineannotation">Request was ls or dir</i>
+
+[000] 01 00 00 10                             <i class="lineannotation">....</i>
+
+
+&gt;&gt;&gt; NBT Packet                                <i class="lineannotation">Outer frame of SMB packet</i>
+NBT Session Packet
+Flags=0x0
+Length=226
+[lines skipped]
+                         
+SMB PACKET: SMBtrans (REPLY)                  <i class="lineannotation">Beginning of a reply to  request</i>
+SMB Command   =  0x25                         <i class="lineannotation">Command was an ls or dir</i>
+Error class   =  0x0             
+Error code    =  0                            <i class="lineannotation">No errors</i>
+Flags1        =  0x80
+Flags2        =  0x1
+Tree ID       =  105
+Proc ID       =  6075
+UID           =  100
+MID           =  30337
+Word Count    =  10
+TotParamCnt=8 
+TotDataCnt=163 
+Res1=0
+ParamCnt=8 
+ParamOff=55 
+Res2=0 
+DataCnt=163 
+DataOff=63 
+Res3=0
+Lsetup=0
+Param Data: (8 bytes)
+[000] 00 00 00 00 05 00 05 00                           ........ 
+
+Data Data: (135 bytes)                        <i class="lineannotation">Actual directory contents:</i>
+[000] 68 6F 6D 65 73 00 00 00  00 00 00 00 00 00 00 00  homes... ........
+[010] 64 00 00 00 70 75 62 6C  69 63 00 00 00 00 00 00  d...publ ic......
+[020] 00 00 00 00 75 00 00 00  74 65 6D 70 00 00 00 00  ....u... temp....
+[030] 00 00 00 00 00 00 00 00  76 00 00 00 49 50 43 24  ........ v...IPC$
+[040] 00 00 00 00 00 00 00 00  00 00 03 00 77 00 00 00  ........ ....w...
+[050] 64 6F 6E 68 61 6D 00 00  00 00 00 00 00 00 00 00  donham.. ........
+[060] 92 00 00 00 48 6F 6D 65  20 44 69 72 65 63 74 6F  ....Home  Directo
+[070] 72 69 65 73 00 00 00 49  50 43 20 53 65 72 76 69  ries...I PC Servi
+[080] 63 65 20 28 53 61 6D                              ce (Sam</pre></blockquote>
+
+<p>This is more of the same debugging session as we saw before with the
+<em class="emphasis">trace</em> command: the listing of a directory. The options
+we used were <em class="emphasis">-v</em> (verbose), <em class="emphasis">-i
+eth0</em> to tell <em class="emphasis">tcpdump</em> on which
+interface to listen (an Ethernet port), and <em class="emphasis">-s
+255</em> to tell it to save the first 255 bytes of each packet
+instead of the default: the first 68. The option
+<tt class="literal">port</tt> <tt class="literal">not</tt>
+<tt class="literal">telnet</tt> is used to avoid screens of telnet traffic,
+because we were logged in to the server remotely. The
+<em class="emphasis">tcpdump</em> program actually has quite a number of
+options to filter just the traffic you want to look at. If
+you've used <em class="emphasis">snoop</em> or
+<em class="emphasis">etherdump</em>, it will look vaguely familiar.</p>
+
+<p>You can download the modified <em class="emphasis">tcpdump</em> from the
+Samba FTP server, located at
+<a href="ftp://samba.anu.edu.au/pub/samba/tcpdump-smb">ftp://samba.anu.edu.au/pub/samba/tcpdump-smb</a>.
+Other versions might not include support for the SMB protocol; if you
+don't see output such as that shown in the example,
+you'll need to use the SMB-enabled version.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-1.3.3"/>
+
+<h3 class="head3">Using Ethereal</h3>
+
+<p><a name="INDEX-27"/>Ethereal (<a href="http://www.ethereal.com">http://www.ethereal.com</a>) is a GUI-based
+utility that performs the same basic function as
+<em class="emphasis">tcpdump</em>. You might prefer Ethereal because it is
+much easier to use. Once you have Ethereal running, just do the
+following:</p>
+
+<ol><li>
+<p>Select Start from the Capture menu.</p>
+</li><li>
+<p>Click the OK button in the dialog box that appears. This will bring
+up a dialog box showing how many packets Ethereal has seen. Perform
+the actions on the system(s) in your network to reproduce the problem
+you are analyzing.</p>
+</li><li>
+<p>Click the Stop button in the Ethereal dialog box to make it finish
+collecting data.</p>
+</li><li>
+<p>In the main Ethereal window, click any item in the upper window to
+view it in the lower window. In the lower window, click any of the
+boxes containing a plus sign (<tt class="literal">+</tt>) to expand the
+view.</p>
+</li></ol>
+<p>Ethereal does a good job of translating the content of the packets it
+encounters into human-readable format, and you should have little
+trouble seeing what happened on the network during the capture
+period. <a name="INDEX-28"/><a name="INDEX-29"/></p>
+
+
+</div>
+
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-12-SECT-2"/>
+
+<h2 class="head1">The Fault Tree</h2>
+
+<p><a name="INDEX-30"/><a name="INDEX-31"/><a name="INDEX-32"/><a name="INDEX-33"/>The fault
+tree presented in this section is for diagnosing and fixing problems
+that occur when you're installing and reconfiguring
+Samba. It's an expanded form of the trouble and
+diagnostic document <em class="filename">DIAGNOSIS.txt</em>, which is part
+of the Samba distribution.</p>
+
+<p>Before you set out to troubleshoot any part of the Samba suite, you
+should know the following information:</p>
+
+<ul><li>
+<p>Your client IP address (we use 192.168.236.10)</p>
+</li><li>
+<p>Your server IP address (we use 192.168.236.86)</p>
+</li><li>
+<p>The netmask for your network (typically 255.255.255.0)</p>
+</li><li>
+<p>Whether the systems are all on the same subnet (ours are)</p>
+</li></ul>
+<p>For clarity, we've renamed the server in the
+following examples to <tt class="literal">server.example.com</tt>, and the
+client system to <tt class="literal">client.example.com</tt>.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.1"/>
+
+<h3 class="head2">How to Use the Fault Tree</h3>
+
+<p>Start the tests here, without skipping forward; it
+won't take long (about 5 minutes) and might actually
+save you time backtracking. Whenever a test succeeds, you will be
+given a name of a section to which you can safely skip.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.2"/>
+
+<h3 class="head2">Troubleshooting Low-Level IP</h3>
+
+<p><a name="INDEX-34"/>The
+first series of tests is that of the low-level services that Samba
+needs to run. The tests in this section verify that:</p>
+
+<ul><li>
+<p>The IP software works</p>
+</li><li>
+<p>The Ethernet hardware works</p>
+</li><li>
+<p>Basic name service is in place</p>
+</li></ul>
+<p>Subsequent sections add TCP software, the Samba daemons
+<em class="emphasis">smbd</em> and <em class="emphasis">nmbd</em>, host-based
+access control, authentication and per-user access control, file
+services, and browsing. The tests are described in considerable
+detail to make them understandable by both technically oriented end
+users and experienced systems and network administrators.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.2.1"/>
+
+<h3 class="head3">Testing the networking software with ping</h3>
+
+<p><a name="INDEX-35"/>The first command to enter
+on both the server and the client is
+<tt class="literal">ping</tt><a name="INDEX-36"/><a name="INDEX-37"/>
+<tt class="literal">127.0.0.1</tt>. This pings the loopback address and
+indicates whether any networking support is functioning. On Unix, you
+can use <tt class="literal">ping</tt> <tt class="literal">127.0.0.1</tt> with the
+statistics option and interrupt it after a few lines. On Sun
+workstations, the command is typically
+<tt class="literal">/usr/etc/ping</tt> <tt class="literal">-s</tt>
+<tt class="literal">127.0.0.1</tt>; on Linux, just <tt class="literal">ping</tt>
+<tt class="literal">127.0.0.1</tt>. On Windows clients, run
+<tt class="literal">ping</tt> <tt class="literal">127.0.0.1</tt> in an MS-DOS
+(command prompt) window, and it will stop by itself after four lines.</p>
+
+<p>Here is an example on a Linux server:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ping 127.0.0.1 </b></tt>
+PING localhost: 56 data bytes 64 bytes from localhost (127.0.0.1): 
+icmp-seq=0. time=1. ms 64 bytes from localhost (127.0.0.1): 
+icmp-seq=1. time=0. ms 64 bytes from localhost (127.0.0.1): 
+icmp-seq=2. time=1. ms ^C 
+----127.0.0.1 PING Statistics---- 
+3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)  
+min/avg/max = 0/0/1</pre></blockquote>
+
+<p>If you get &quot;ping: no answer from . . .
+&quot; or &quot;100% packet
+loss,&quot; you have no IP networking installed on the
+system. The address <tt class="literal">127.0.0.1</tt> is the internal
+loopback address and doesn't depend on the computer
+being physically connected to a network. If this test fails, you have
+a serious local problem. TCP/IP either isn't
+installed or is seriously misconfigured. See your operating system
+documentation if it's a Unix server. If
+it's a Windows client, follow the instructions in
+<a href="ch03.html">Chapter 3</a> to install networking support.</p>
+
+<a name="samba2-CHP-12-NOTE-155"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>If <em class="emphasis">you're</em> the network manager,
+some good references are Craig Hunt's
+<em class="emphasis">TCP/IP Network Administration</em>, Chapter 11, and Craig Hunt and Robert Bruce
+Thompson's <em class="emphasis">Windows NT TCP/IP Network
+Administration</em>, both published by
+O'Reilly.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.2.2"/>
+
+<h3 class="head3">Testing local name services with ping</h3>
+
+<p><a name="INDEX-38"/>Next, try to ping
+<tt class="literal">localhost</tt> on the Samba server. The
+<tt class="literal">localhost</tt> hostname is the conventional hostname
+for the <tt class="literal">127.0.0.1</tt> loopback interface, and it
+should resolve to that address. After typing <tt class="literal">ping</tt>
+<tt class="literal">localhost</tt>, you should see output similar to the
+following:</p>
+
+<blockquote><pre class="code">$  <tt class="userinput"><b>ping localhost  </b></tt>
+PING localhost: 56 data bytes  64 bytes from localhost (127.0.0.1):
+icmp-seq=0. time=0. ms  64 bytes from localhost (127.0.0.1): 
+icmp-seq=1. time=0. ms  64 bytes from localhost (127.0.0.1): 
+icmp-seq=2. time=0. ms  ^C</pre></blockquote>
+
+<p>If this succeeds, try the same test on the client. Otherwise:</p>
+
+<ul><li>
+<p>If you get &quot;unknown host:
+localhost,&quot; there is a problem resolving the
+hostname <em class="filename">localhost</em> into a valid IP address.
+(This might be as simple as a missing entry in a local
+<em class="emphasis">hosts</em> file.) From here, skip down to
+<a href="ch03.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a> later in this chapter.</p>
+</li><li>
+<p>If you get &quot;ping: no answer,&quot; or
+&quot;100% packet loss,&quot; but pinging
+<tt class="literal">127.0.0.1</tt> worked, name services is resolving to an
+address, but it isn't the correct one. Check the
+file or database (typically <em class="filename">/etc/hosts</em> on a Unix
+system) that the name service is using to resolve addresses to ensure
+that the entry is correct.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.2.3"/>
+
+<h3 class="head3">Testing the networking hardware with ping</h3>
+
+<p><a name="INDEX-39"/>Next, ping the
+server's network IP address from itself. This should
+get you exactly the same results as pinging
+<tt class="literal">127.0.0.1</tt>:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ping 192.168.236.86 </b></tt>
+PING 192.168.236.86: 56 data bytes 64 bytes from 192.168.236.86 (192.168.236.86): 
+icmp-seq=0. time=1. ms 64 bytes from 192.168.236.86 (192.168.236.86): 
+icmp-seq=1. time=0. ms 64 bytes from 192.168.236.86 (192.168.236.86): 
+icmp-seq=2. time=1. ms ^C 
+----192.168.236.86 PING Statistics---- 
+3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)  
+min/avg/max = 0/0/1</pre></blockquote>
+
+<p>If this works on the server, repeat it for the client. Otherwise:</p>
+
+<ul><li>
+<p>If <tt class="literal">ping</tt> <em class="replaceable">network_ip</em>
+fails on either the server or client, but <tt class="literal">ping</tt>
+<tt class="literal">127.0.0.1</tt> works on that system, you have a TCP/IP
+problem that is specific to the Ethernet network interface card on
+the computer. Check with the documentation for the network card or
+host operating system to determine how to configure it correctly.
+However, be aware that on some operating systems, the
+<em class="emphasis">ping</em> command appears to work even if the network
+is disconnected, so this test doesn't always
+diagnose all hardware problems.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.2.4"/>
+
+<h3 class="head3">Testing connections with ping</h3>
+
+<p><a name="INDEX-40"/>Now, ping the server by name (instead
+of its IP address)&mdash;once from the server and once from the
+client. This is the general test for working network hardware:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ping server </b></tt>
+PING server.example.com: 56 data bytes 64 bytes from server.example.com (192.168.236.86): 
+icmp-seq=0. time=1. ms 64 bytes from server.example.com (192.168.236.86): 
+icmp-seq=1. time=0. ms 64 bytes from server.example.com (192.168.236.86): 
+icmp-seq=2. time=1. ms ^C 
+----server.example.com PING Statistics---- 
+3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)  
+min/avg/max = 0/0/1</pre></blockquote>
+
+<p>If successful, this test tells us five things:</p>
+
+<ul><li>
+<p>The hostname (e.g., <tt class="literal">server</tt>) is being found by your
+local name server.</p>
+</li><li>
+<p>The hostname has been expanded to the full name (e.g.,
+<tt class="literal">server.example.com</tt>).</p>
+</li><li>
+<p>Its address is being returned (<tt class="literal">192.168.236.86</tt>).</p>
+</li><li>
+<p>The client has sent the Samba server four 56-byte UDP/IP packets.</p>
+</li><li>
+<p>The Samba server has replied to all four packets.</p>
+</li></ul>
+<p>If this test isn't successful, one of several things
+can be wrong with the network:</p>
+
+<ul><li>
+<p>First, if you get <tt class="literal">ping</tt>: <tt class="literal">no</tt>
+<tt class="literal">answer</tt>, or <tt class="literal">100%</tt>
+<tt class="literal">packet</tt> <tt class="literal">loss</tt>,
+you're not connecting to the network, the other
+system isn't connecting, or one of the addresses is
+incorrect. Check the addresses that the <em class="emphasis">ping</em>
+command reports on each system, and ensure that they match the ones
+you set up initially.</p>
+
+<p>If not, there is at least one mismatched address between the two
+systems. Try entering the command <tt class="literal">arp</tt>
+<tt class="literal">-a</tt>, and see if there is an entry for the other
+system. (The <em class="emphasis">arp</em> command stands for the Address
+Resolution Protocol. The <tt class="literal">arp</tt> <tt class="literal">-a</tt>
+command lists all the addresses known on the local system.) Here are
+some things to try:</p>
+<ul><li>
+<p>If you receive a message like <tt class="literal">192.168.236.86</tt>
+<tt class="literal">at</tt> <tt class="literal">(incomplete)</tt>, the Ethernet
+address of 192.168.236.86 is unknown. This indicates a complete lack
+of connectivity, and you're likely having a problem
+at the very bottom of the TCP/IP protocol stack&mdash;the Ethernet
+interface layer. This is discussed in Chapters 5 and 6 of
+<em class="citetitle">TCP/IP Network Administration
+</em>(O'Reilly).</p>
+</li><li>
+<p>If you receive a response similar to server
+<tt class="literal">(192.168.236.86)</tt> <tt class="literal">at</tt>
+<tt class="literal">8:0:20:12:7c:94</tt>, the server has been reached at
+some time, or another system is answering on its behalf. However,
+this means that <em class="emphasis">ping</em> should have worked: you may
+have an intermittent networking or ARP problem.</p>
+</li><li>
+<p>If the IP address from ARP doesn't match the
+addresses you expected, investigate and correct the addresses
+manually.</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>If each system can ping itself but not another, something is wrong on
+the network between them.</p>
+</li><li>
+<p>If you get <tt class="literal">ping</tt>: <tt class="literal">network</tt>
+<tt class="literal">unreachable</tt> or <tt class="literal">ICMP</tt>
+<tt class="literal">Host</tt> <tt class="literal">Unreachable</tt>,
+you're not receiving an answer, and more than one
+network is probably involved.</p>
+
+<p>In principle, you shouldn't try to troubleshoot SMB
+clients and servers on different networks. Try to test a server and
+client that are on the same network:</p>
+
+<ol><li>
+<p>First, perform the tests for <tt class="literal">ping</tt>:
+<tt class="literal">no</tt> <tt class="literal">answer</tt> described earlier in
+this section. If this doesn't identify the problem,
+the remaining possibilities are the following: an address is wrong,
+your netmask is wrong, a network is down, or the packets have been
+stopped by a firewall.</p>
+</li>
+<li>
+<p>Check both the address and the netmasks on source and destination
+systems to see if something is obviously wrong. Assuming both systems
+really are on the same network, they both should have the same
+netmasks, and <em class="emphasis">ping</em> should report the correct
+addresses. If the addresses are wrong, you'll need
+to correct them. If they are correct, the programs might be confused
+by an incorrect netmask. See <a href="ch12.html#samba2-CHP-12-SECT-2.8.1">Section 12.2.8.1</a>, later in this chapter.</p>
+</li>
+<li>
+<p>If the commands are still reporting that the network is unreachable
+and neither of the previous two conditions are in error, one network
+really might be unreachable from the other. This, too, is an issue
+for the network manager.</p>
+</li></ol>
+</li><li>
+<p>If you get <tt class="literal">ICMP</tt>
+<tt class="literal">Administratively</tt> <tt class="literal">Prohibited</tt>,
+you've struck a firewall of some sort or a
+misconfigured router. You will need to speak to your network security
+officer.</p>
+</li><li>
+<p>If you get <tt class="literal">ICMP</tt> <tt class="literal">Host</tt>
+<tt class="literal">redirect</tt> and <em class="emphasis">ping</em> reports
+packets getting through, this is generally harmless:
+you're simply being rerouted over the network.</p>
+</li><li>
+<p>If you get a host redirect and no <em class="emphasis">ping</em>
+responses, you are being redirected, but no one is responding. Treat
+this just like the <tt class="literal">Network</tt>
+<tt class="literal">unreachable</tt> response, and check your addresses and
+netmasks.</p>
+</li><li>
+<p>If you get <tt class="literal">ICMP</tt> <tt class="literal">Host</tt>
+<tt class="literal">Unreachable</tt> <tt class="literal">from</tt>
+<tt class="literal">gateway</tt> <tt class="literal">gateway</tt>
+<tt class="literal">name</tt>, ping packets are being routed to another
+network, but the other system isn't responding and
+the router is reporting the problem on its behalf. Again, treat this
+like a <tt class="literal">Network</tt> <tt class="literal">unreachable</tt>
+response, and start checking addresses and netmasks.</p>
+</li><li>
+<p>If you get <tt class="literal">ping</tt>: <tt class="literal">unknown</tt>
+<tt class="literal">host</tt> <tt class="literal">hostname</tt>, your
+system's name is not known. This tends to indicate a
+name service problem, which didn't affect
+<tt class="literal">localhost</tt>. Have a look at <a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>, later in this chapter.</p>
+</li><li>
+<p>If you get a partial success&mdash;with some pings failing but others
+succeeding&mdash;you have either an intermittent problem between the
+systems or an overloaded network. Ping a bit longer, and see if more
+than about three percent of the packets fail. If so, check it with
+your network manager: a problem might just be starting. However, if
+only a few fail, or if you happen to know some massive network
+program is running, don't worry unduly. The ICMP
+(and UDP) protocols used by <em class="emphasis">ping</em> are allowed to
+drop occasional packets.</p>
+</li><li>
+<p>If you get a response such as <tt class="literal">smtsvr.antares.net</tt>
+<tt class="literal">is</tt> <tt class="literal">alive</tt> when you actually
+pinged <tt class="literal">client.example.com</tt>, either
+you're using someone else's address
+or the system has multiple names and addresses. If the address is
+wrong, the name service is clearly the culprit;
+you'll need to change the address in the name
+service database to refer to the correct system. This is discussed in
+<a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>, later in this
+chapter.</p>
+
+<p>Servers are often <em class="emphasis">multihomed</em> &mdash;i.e.,
+connected to more than one network, with different names on each net.
+If you are getting a response from an unexpected name on a multihomed
+server, look at the address and see if it's on your
+network (see <a href="ch12.html#samba2-CHP-12-SECT-2.8.1">Section 12.2.8.1</a>, later in this chapter). If
+so, you should use that address, rather than one on a different
+network, for both performance and reliability reasons.</p>
+
+<p>Servers can also have multiple names for a single Ethernet address,
+especially if they are web servers. This is harmless, albeit
+startling. You probably will want to use the official (and permanent)
+name, rather than an alias that might change.</p>
+</li><li>
+<p>If everything works but the IP address reported is
+<tt class="literal">127.0.0.1</tt>, you have a name service error. This
+typically occurs when an operating-system installation program
+generates an <em class="filename">/etc/hosts</em> line similar to
+<tt class="literal">127.0.0.1</tt> <tt class="literal">localhost</tt>
+<em class="emphasis">hostname.domainname</em>. The localhost line should
+say <tt class="literal">127.0.0.1</tt> <tt class="literal">localhost</tt> or
+<tt class="literal">127.0.0.1</tt> <tt class="literal">localhost</tt>
+<tt class="literal">loghost</tt>. Correct it, lest it cause failures to
+negotiate who is the master browse list holder and who is the master
+browser. It can also cause (ambiguous) errors in later tests.</p>
+</li></ul>
+<p>If this worked from the server, repeat it from the client. <a name="INDEX-41"/>
+<a name="INDEX-42"/><a name="INDEX-43"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.3"/>
+
+<h3 class="head2">Troubleshooting TCP</h3>
+
+<p><a name="INDEX-44"/><a name="INDEX-45"/>Now that
+you've tested IP, UDP, and a name service with
+<em class="emphasis">ping</em>, it's time to test TCP.
+Browsing and <em class="emphasis">ping</em> use ICMP and UDP; file and
+print services (shares) use TCP. Both depend on IP as a lower layer,
+and all four depend on name services. Testing TCP is most
+conveniently done using the FTP program.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.3.1"/>
+
+<h3 class="head3">Testing TCP with FTP</h3>
+
+<p>Try connecting via FTP, once from the server to itself, and once from
+the client to the server:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ftp server</b></tt>
+Connected to server.example.com. 
+220 server.example.com FTP server (Version 6.2/OpenBSD/Linux-0.10) ready.
+ Name (server:davecb): 
+331 Password required for davecb. 
+Password: 
+230 User davecb logged in.
+ ftp&gt;<tt class="userinput"><b> quit </b></tt>
+221 Goodbye.</pre></blockquote>
+
+<p>If this worked, skip to the next section, <a href="ch12.html#samba2-CHP-12-SECT-2.4">Section 12.2.4</a>. Otherwise:</p>
+
+<ul><li>
+<p>If you received the message <tt class="literal">server</tt>:
+<tt class="literal">unknown</tt> <tt class="literal">host</tt>, name service has
+failed. Go back to the corresponding <em class="emphasis">ping</em> step,
+<a href="ch12.html#samba2-CHP-12-SECT-2.2.2">Section 12.2.2.2</a>, and rerun those tests
+to see why name lookup failed.</p>
+</li><li>
+<p>If you received <tt class="literal">ftp</tt>: <tt class="literal">connect</tt>:
+<tt class="literal">Connection</tt> <tt class="literal">refused</tt>, the system
+isn't running an FTP daemon. This is mildly unusual
+on Unix servers. Optionally, you might try this test by connecting to
+the system using <em class="emphasis">telnet</em> instead of
+<em class="emphasis">ftp</em>; the messages are very similar, and
+<em class="emphasis">telnet</em> uses TCP as well.</p>
+</li><li>
+<p>If there was a long pause, and then <tt class="literal">ftp</tt>:
+<tt class="literal">connect</tt>: <tt class="literal">Connection</tt>
+<tt class="literal">timed</tt> <tt class="literal">out</tt>, the system
+isn't reachable. Return to <a href="ch12.html#samba2-CHP-12-SECT-2.2.4">Section 12.2.2.4</a>.</p>
+</li><li>
+<p>If you received <tt class="literal">530</tt> <tt class="literal">Logon</tt>
+<tt class="literal">Incorrect</tt>, you connected successfully, but
+you've just found a different problem. You likely
+provided an incorrect username or password. Try again, making sure
+you use your username from the Unix server and type your password
+correctly.</p>
+</li></ul>
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.4"/>
+
+<h3 class="head2">Troubleshooting Server Daemons</h3>
+
+<p><a name="INDEX-46"/>Once
+you've confirmed that TCP networking is working
+properly, the next step is to make sure the daemons are running on
+the server. This takes three separate tests because no single one of
+the following will decisively prove that they're
+working correctly.</p>
+
+<p>To be sure they're running, you need to find out
+whether the daemons:</p>
+
+<ol><li>
+<p>Have started</p>
+</li><li>
+<p>Are registered or bound to a TCP/IP port by the operating system</p>
+</li><li>
+<p>Are actually paying attention</p>
+</li></ol>
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.4.1"/>
+
+<h3 class="head3">Tracking daemon startup</h3>
+
+<p><a name="INDEX-47"/>First, check the Samba logs. If
+you've started the daemons, the message
+<tt class="literal">smbd</tt> <tt class="literal">version</tt>
+<tt class="literal">number</tt> <tt class="literal">started</tt> should appear.
+If it doesn't, you need to restart the Samba
+daemons.</p>
+
+<p>If the daemon reports that it has indeed started, look out for
+<tt class="literal">bind</tt> <tt class="literal">failed</tt>
+<tt class="literal">on</tt> <tt class="literal">port</tt> <tt class="literal">139</tt>
+<tt class="literal">socket_addr=0</tt> <tt class="literal">(Address</tt>
+<tt class="literal">already</tt> <tt class="literal">in</tt>
+<tt class="literal">use)</tt>. This means another daemon has been started
+on port 139 (<em class="emphasis">smbd</em> ). Also,
+<em class="emphasis">nmbd</em> will report a similar failure if it cannot
+bind to port 137. Either you've started them twice,
+or the <em class="emphasis">inetd</em> server has tried to provide a
+daemon for you. If it's the latter,
+we'll diagnose that in a moment.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.4.2"/>
+
+<h3 class="head3">Looking for daemon processes with ps</h3>
+
+<p><a name="INDEX-48"/>Another way to make sure the daemons are
+running is to check their processes on the system. Use the
+<em class="emphasis">ps</em><a name="INDEX-49"/> command on the server with the
+&quot;long&quot; option for your system type
+(commonly <tt class="literal">ps</tt> <tt class="literal">ax</tt> or
+<tt class="literal">ps</tt> <tt class="literal">-ef</tt>), and see whether
+<em class="emphasis">smbd</em> and <em class="emphasis">nmbd</em> are already
+running. This often looks like the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ps ax</b></tt>
+ PID TTY STAT TIME   COMMAND
+ 1   ?   S    0:03   init [2] 
+ 2   ?   SW   0:00   (kflushd)
+<i class="lineannotation">(...many lines of processes...) </i>
+ 234 ?   S    0:14   nmbd -D3
+ 237 ?   S    0:11   smbd -D3
+<i class="lineannotation">(...more lines, possibly including more smbd lines...)</i></pre></blockquote>
+
+<p>This example illustrates that <em class="emphasis">smbd</em> and
+<em class="emphasis">nmbd</em> have already started as standalone daemons
+(the <em class="emphasis">-D</em> option) at log level 3.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.4.3"/>
+
+<h3 class="head3">Looking for daemons bound to ports</h3>
+
+<p><a name="INDEX-50"/>Next, the daemons have to be registered
+with the operating system so that they can get access to TCP/IP
+ports. The <em class="emphasis">netstat</em> command will tell you if this
+has been done. Run the command <tt class="literal">netstat</tt>
+<tt class="literal">-a</tt> on the server, and look for lines mentioning
+<tt class="literal">netbios</tt>, <tt class="literal">137</tt>, or
+<tt class="literal">139</tt>:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>netstat -a </b></tt>
+Active Internet connections (including servers) 
+Proto Recv-Q Send-Q  Local Address          Foreign Address        (state) 
+udp   0      0       *.137                  *.* 
+tcp   0      0       *.139                  *.*                    LISTEN 
+tcp   8370   8760    server.139             client.1439            ESTABLISHED</pre></blockquote>
+
+<p>Among similar lines, there should be at least one UDP line for
+<tt class="literal">*.netbios-</tt> or <tt class="literal">*.137</tt>. This
+indicates that the <em class="emphasis">nmbd</em> server is registered and
+(we hope) is waiting to answer requests. There should also be at
+least one TCP line mentioning <tt class="literal">*.netbios-</tt> or
+<tt class="literal">*.139</tt>, and it will probably be in the LISTEN
+state. This means that <em class="emphasis">smbd</em> is up and listening
+for connections.</p>
+
+<p>There might be other TCP lines indicating connections from
+<em class="emphasis">smbd</em> to clients, one for each client. These are
+usually in the ESTABLISHED state. If there are
+<em class="emphasis">smbd</em> lines in the ESTABLISHED state,
+<em class="emphasis">smbd</em> is definitely running. If there is only one
+line in the LISTEN state, we're not sure yet. If
+both of the lines are missing, a daemon has not succeeded in
+starting, so it's time to check the logs and then go
+back to <a href="ch02.html">Chapter 2</a>.</p>
+
+<p>If there is a line for each client, it might be coming either from a
+Samba daemon or from the master IP daemon,
+<em class="emphasis">inetd</em>. It's quite possible that
+your <em class="emphasis">inetd</em> startup file contains lines that
+start Samba daemons without your realizing it; for instance, the
+lines might have been placed there if you installed Samba as part of
+a Linux distribution. The daemons started by
+<em class="emphasis">inetd</em> prevent ours from running. This problem
+typically produces log messages such as <tt class="literal">bind</tt>
+<tt class="literal">failed</tt> <tt class="literal">on</tt>
+<tt class="literal">port</tt> <tt class="literal">139</tt>
+<tt class="literal">socket</tt> <tt class="literal">addr=0</tt>
+<tt class="literal">(Address</tt> <tt class="literal">already</tt>
+<tt class="literal">in</tt> <tt class="literal">use)</tt>.</p>
+
+<p>Check your <em class="filename">/etc/inetd.conf</em> ; unless
+you're intentionally starting the daemons from
+there, <tt class="literal">netbios-ns</tt> (UDP port 137) or
+<tt class="literal">netbios-ssn</tt> (tcp port 139) servers should be
+mentioned there. If your system is providing an SMB daemon via
+<em class="emphasis">inetd</em>, lines such as the following will appear
+in the <em class="filename">inetd.conf</em> file:</p>
+
+<blockquote><pre class="code">netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
+netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd</pre></blockquote>
+
+<p>If your system uses <em class="emphasis">xinetd</em> instead of
+<em class="emphasis">inetd</em>, see <a href="ch02.html">Chapter 2</a> for
+details concerning its configuration.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.4.4"/>
+
+<h3 class="head3">Checking smbd with telnet</h3>
+
+<p><a name="INDEX-51"/><a name="INDEX-52"/><a name="INDEX-53"/>Ironically, the easiest way to test that
+the <em class="emphasis">smbd</em> server is actually working is to send
+it a meaningless message and see if it is rejected. Try something
+such as the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>echo &quot;hello&quot; | telnet localhost 139 </b></tt>
+Trying
+Trying 192.168.236.86 ... 
+Connected to localhost. Escape character is '^]'. 
+Connection closed by foreign host.</pre></blockquote>
+
+<p>This sends an erroneous but harmless message to
+<em class="emphasis">smbd</em>. If you get a <tt class="literal">Connected</tt>
+message followed by a <tt class="literal">Connection</tt>
+<tt class="literal">closed</tt> message, the test was a success. You have
+an <em class="emphasis">smbd</em> daemon listening on the port and
+rejecting improper connection messages. On the other hand, if you get
+<tt class="literal">telnet</tt>: <tt class="literal">connect</tt>:
+<tt class="literal">Connection</tt> <tt class="literal">refused</tt>, most likely
+no daemon is present. Check the logs and go back to <a href="ch02.html">Chapter 2</a>.</p>
+
+<p>Regrettably, there isn't an easy test for
+<em class="emphasis">nmbd</em>. If the <em class="emphasis">telnet</em> test
+and the <em class="emphasis">netstat</em> test both say that an
+<em class="emphasis">smbd</em> is running, there is a good chance that
+<em class="emphasis">netstat</em> will also be correct about
+<em class="emphasis">nmbd</em> running.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.4.5"/>
+
+<h3 class="head3">Testing daemons with testparm</h3>
+
+<p><a name="INDEX-54"/><a name="INDEX-55"/>Once you know
+there's a daemon, you should always run
+<em class="emphasis">testparm</em>, in hopes of getting something such as
+the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>testparm </b></tt>
+Load smb config files from /opt/samba/lib/smb.conf
+Processing section &quot;[homes]&quot; 
+Processing section &quot;[printers]&quot; ... 
+Processing section &quot;[tmp]&quot; 
+Loaded services file OK. ...</pre></blockquote>
+
+<p>The <em class="emphasis">testparm</em> program normally reports the
+processing of a series of sections and responds with
+<tt class="literal">Loaded</tt> <tt class="literal">services</tt>
+<tt class="literal">file</tt> <tt class="literal">OK</tt> if it succeeds. If not,
+it reports one or more of the following messages, which also appear
+in the logs as noted:</p>
+
+<dl>
+<dt><b>Allow/Deny connection from account (n) to service</b></dt>
+<dd>
+<p>A <em class="emphasis">testparm</em>-only message produced if you have
+<tt class="literal">valid</tt> <tt class="literal">user</tt> or
+<tt class="literal">invalid</tt> <tt class="literal">user</tt> options set in
+your <em class="emphasis">smb.conf</em>. You will want to make sure that
+you are on the valid user list, and that <tt class="literal">root</tt>,
+<tt class="literal">bin</tt>, etc., are on the invalid user list. If you
+don't, you will not be able to connect, or users who
+shouldn't <em class="emphasis">will</em> be able to.</p>
+</dd>
+
+
+
+<dt><b>Warning: You have some share names that are longer than eight chars</b></dt>
+<dd>
+<p>For anyone using Windows for Workgroups and older clients. They fail
+to connect to shares with long names, producing an overflow message
+that sounds confusingly like a memory overflow.</p>
+</dd>
+
+
+
+<dt><b>Warning: [name] service MUST be printable!</b></dt>
+<dd>
+<p>A printer share lacks a <tt class="literal">printable</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> option.</p>
+</dd>
+
+
+
+<dt><b>No path in service name using [name]</b></dt>
+<dd>
+<p>A file share doesn't know which directory to provide
+to the user, or a print share doesn't know which
+directory to use for spooling. If no path is specified, the service
+will try to run with a path of <em class="emphasis">/tmp</em>, which might
+not be what you want.</p>
+</dd>
+
+
+
+<dt><b>Note: Servicename is flagged unavailable</b></dt>
+<dd>
+<p>Just a reminder that you have used the <tt class="literal">available</tt>
+<tt class="literal">=</tt> <tt class="literal">no</tt> option in a share.</p>
+</dd>
+
+
+
+<dt><b>Can't find include file [name] </b></dt>
+<dd>
+<p>A configuration file referred to by an <tt class="literal">include</tt>
+option did not exist. If you were including the file unconditionally,
+this is an error and probably a serious one: the share will not have
+the configuration you intended. If you were including it based on one
+of the <tt class="literal">%</tt> variables, such as <tt class="literal">%a</tt>
+(architecture), you will need to decide whether, for example, a
+missing Windows for Workgroups configuration file is a problem. It
+often isn't.</p>
+</dd>
+
+
+
+<dt><b>Can't copy service name, unable to copy to itself</b></dt>
+<dd>
+<p>You tried to copy an <em class="filename">smb.conf</em> section into
+itself.</p>
+</dd>
+
+
+
+<dt><b>Unable to copy service&mdash;source not found: [name]</b></dt>
+<dd>
+<p>Indicates a missing or misspelled section in a
+<tt class="literal">copy</tt> <tt class="literal">=</tt> option.</p>
+</dd>
+
+
+
+<dt><b>Ignoring unknown parameter name </b></dt>
+<dd>
+<p>Typically indicates an obsolete, misspelled, or unsupported option.</p>
+</dd>
+
+
+
+<dt><b>Global parameter name found in service section </b></dt>
+<dd>
+<p>Indicates that a global-only parameter has been used in an individual
+share. Samba ignores the parameter.</p>
+</dd>
+
+</dl>
+
+<p>After the <em class="emphasis">testparm</em> test, repeat it with
+(exactly) three parameters: the name of your
+<em class="filename">smb.conf</em> file, the name of your client, and its
+IP address:</p>
+
+<blockquote><pre class="code"># <tt class="userinput"><b>testparm /usr/local/samba/lib/smb.conf client 192.168.236.10</b></tt></pre></blockquote>
+
+<p>This will run one more test that checks the hostname and address
+against <tt class="literal">hosts</tt> <tt class="literal">allow</tt> and
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> options and might
+produce the <tt class="literal">Allow</tt> <tt class="literal">connection</tt>
+<tt class="literal">from</tt> <tt class="literal">hostname</tt>
+<tt class="literal">to</tt> <tt class="literal">service</tt> and/or
+<tt class="literal">Deny</tt> <tt class="literal">connection</tt>
+<tt class="literal">from</tt> <tt class="literal">hostname</tt>
+<tt class="literal">to</tt> <tt class="literal">service</tt> messages for the
+client system. These messages indicate that you have
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> and/or
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> options in your
+<em class="filename">smb.conf</em>, and they prohibit access from the
+client system. <a name="INDEX-56"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.5"/>
+
+<h3 class="head2">Troubleshooting SMB Connections</h3>
+
+<p><a name="INDEX-57"/><a name="INDEX-58"/>Now
+that you know the servers are up, you need to make sure
+they're running properly. We start by placing a
+simple <em class="filename">smb.conf</em> file in the
+<em class="filename">/usr/local/samba/lib</em> directory.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.5.1"/>
+
+<h3 class="head3">A minimal smb.conf file</h3>
+
+<p>In the following tests, we assume you have a
+<tt class="literal">[temp]</tt> share suitable for testing, plus at least
+one account. An <em class="filename">smb.conf</em> file that includes just
+these is as follows:</p>
+
+<blockquote><pre class="code">[global] 
+    workgroup = <em class="replaceable">EXAMPLE</em> 
+    security = user
+    browsable = yes 
+    local master = yes 
+[homes] 
+    guest ok = no 
+    browsable = no
+[temp] 
+    path = /tmp 
+    public = yes</pre></blockquote>
+<a name="samba2-CHP-12-NOTE-156"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
+<p>The <tt class="literal">public</tt> <tt class="literal">=</tt>
+<tt class="literal">yes</tt> option in the <tt class="literal">[temp]</tt> share
+is just for testing. You probably don't want people
+without accounts storing things on your Samba server, so you should
+comment it out when you're done.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.5.2"/>
+
+<h3 class="head3">Testing locally with smbclient</h3>
+
+<p><a name="INDEX-59"/><a name="INDEX-60"/>The first test is to ensure that the
+server can list its own services (shares). Run the command
+<tt class="literal">smbclient</tt> <em class="emphasis">-L</em>
+<tt class="literal">localhost</tt> <tt class="literal">-U%</tt> to connect to the
+server from itself, and specify the guest user. You should see the
+following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient -L localhost -U% </b></tt>
+Server time is Wed May 27 17:57:40 2002 Timezone is UTC-4.0
+Server=[localhost] 
+User=[davecb] 
+Workgroup=[EXAMPLE] 
+Domain=[EXAMPLE]
+    Sharename      Type      Comment 
+    ---------      -----     ----------
+    temp           Disk
+    IPC$           IPC       IPC Service (Samba 1.9.18) 
+    homes          Disk      Home directories
+This machine does not have a browse list</pre></blockquote>
+
+<p>If you received this output, move on to the next section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.3">Section 12.2.5.3</a>. On the other hand, if you
+receive an error, check the following:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">Get_hostbyname</tt>:
+<tt class="literal">unknown</tt> <tt class="literal">host</tt>
+<tt class="literal">localhost</tt>, either you've spelled
+its name wrong or there actually is a problem (which should have been
+seen back in <a href="ch12.html#samba2-CHP-12-SECT-2.2.2">Section 12.2.2.2</a>). In the
+latter case, move on to <a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>, later in this chapter.</p>
+</li><li>
+<p>If you get <tt class="literal">Connect</tt> <tt class="literal">error</tt>:
+<tt class="literal">Connection</tt> <tt class="literal">refused</tt>, the server
+was found, but it wasn't running an
+<em class="emphasis">nmbd</em> daemon. Skip back to
+<a href="ch12.html#samba2-CHP-12-SECT-2.4">Section 12.2.4</a>,
+earlier in this chapter, and retest the daemons.</p>
+</li><li>
+<p>If you get the message <tt class="literal">Your</tt>
+<tt class="literal">server</tt> <tt class="literal">software</tt>
+<tt class="literal">is</tt> <tt class="literal">being</tt>
+<tt class="literal">unfriendly</tt>, the initial session request packet got
+a garbage response from the server. The server might have crashed or
+started improperly. The common causes of this can be discovered by
+scanning the logs for the following:</p>
+<ul><li>
+<p>Invalid command-line parameters to <em class="emphasis">smbd</em> ; see
+the <em class="emphasis">smbd</em> manual page.</p>
+</li><li>
+<p>A fatal problem with the <em class="filename">smb.conf</em> file that
+prevents the startup of <em class="emphasis">smbd</em>. Always check your
+changes with <em class="emphasis">testparm</em>, as was done in <a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>, earlier in this chapter.</p>
+</li><li>
+<p>Missing directories where Samba is supposed to keep its log and lock
+files.</p>
+</li><li>
+<p>The presence of a server already on the port (139 for
+<em class="emphasis">smbd</em>, 137 for <em class="emphasis">nmbd</em> ),
+preventing the daemon from starting.</p>
+</li></ul>
+</li>
+<li>
+<p>If you're using <em class="emphasis">inetd</em> (or
+xinetd ) instead of standalone daemons, be sure to check your
+<em class="filename">/etc/inetd.conf</em> (or xinetd configuration files)
+and <em class="filename">/etc/services</em> entries against their manual
+pages for errors as well.</p>
+</li><li>
+<p>If you get a <tt class="literal">Password</tt>: prompt, your guest account
+is not set up properly. The <em class="emphasis">-U%</em> option tells
+<em class="emphasis">smbclient</em> to do a &quot;null
+login,&quot; which requires that the guest account be
+present but does not require it to have any privileges.</p>
+</li><li>
+<p>If you get the message <tt class="literal">SMBtconX</tt>
+<tt class="literal">failed</tt>. <tt class="literal">ERRSRV--ERRaccess</tt>, you
+aren't permitted access to the server. This normally
+means you have a <tt class="literal">hosts</tt> <tt class="literal">allow</tt>
+option that doesn't include the server or a
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> option that does.
+Recheck with the command <tt class="literal">testparm</tt>
+<tt class="literal">smb.conf</tt> <em class="replaceable">your_hostname</em>
+<em class="replaceable">your_ip_address</em> (see
+<a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>),
+and correct any unintended prohibitions.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.5.3"/>
+
+<h3 class="head3">Testing connections with smbclient</h3>
+
+<p><a name="INDEX-61"/><a name="INDEX-62"/>Run the command
+<tt class="literal">smbclient</tt>
+<tt class="literal">\\</tt><em class="replaceable">server</em><tt class="literal">\temp</tt>
+to connect to the server's <tt class="literal">[temp]</tt>
+share and to see if you can connect to a file service. You should get
+the following response:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient '\\server\temp' </b></tt>
+Server time is Tue May  5 09:49:32 2002 Timezone is UTC-4.0 Password:
+<b class="emphasis-bold">smb: \&gt; quit</b></pre></blockquote>
+<p>You might receive the following errors:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">Get_Hostbyname</tt>:
+<tt class="literal">Unknown</tt> <tt class="literal">host</tt>
+<tt class="literal">name</tt>, <tt class="literal">Connect</tt>
+<tt class="literal">error</tt>: <tt class="literal">Connection</tt>
+<tt class="literal">refused</tt>, or <tt class="literal">Your</tt>
+<tt class="literal">server</tt> <tt class="literal">software</tt>
+<tt class="literal">is</tt> <tt class="literal">being</tt>
+<tt class="literal">unfriendly</tt>, see the previous section,
+<a href="ch12.html#samba2-CHP-12-SECT-2.5.2">Section 12.2.5.2</a>, for
+the diagnoses.</p>
+</li><li>
+<p>If you get the message <tt class="literal">servertemp</tt>:
+<tt class="literal">Not</tt> <tt class="literal">enough</tt>
+<tt class="literal">`\</tt>'
+<tt class="literal">characters</tt> <tt class="literal">in</tt>
+<tt class="literal">service</tt>, you likely didn't quote
+the address, so Unix stripped off backslashes. You can also write the
+command:</p>
+
+<blockquote><pre class="code">smbclient \\\\<em class="replaceable">server</em>\\temp</pre></blockquote>
+
+<p>or:</p>
+<blockquote><pre class="code">smbclient //<em class="replaceable">server</em>/temp</pre></blockquote>
+</li>
+</ul>
+<p>Now, provide your Unix account password to the
+<tt class="literal">Password</tt>: prompt. If you then get an
+<tt class="literal">smb</tt>: <tt class="literal">\&gt;</tt> prompt, it worked.
+Enter <tt class="literal">quit</tt> and continue on to the next section,
+<a href="ch12.html#samba2-CHP-12-SECT-2.5.4">Section 12.2.5.4</a>. If
+you got <tt class="literal">SMBtconX</tt> <tt class="literal">failed</tt>.
+<tt class="literal">ERRSRV--ERRinvnetname</tt>, the problem can be any of
+the following:</p>
+
+<ul><li>
+<p>A wrong share name: you might have spelled it wrong, it might be too
+long, it might be in mixed case, or it might not be available. Check
+that it's what you expect with
+<em class="emphasis">testparm</em> (see the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>).</p>
+</li><li>
+<p>A <tt class="literal">security</tt> <tt class="literal">=</tt>
+<tt class="literal">share</tt> parameter in your Samba configuration file,
+in which case you might have to add <tt class="literal">-U</tt>
+<em class="replaceable">your_account</em> to the
+<em class="emphasis">smbclient</em> command.</p>
+</li><li>
+<p>An erroneous username.</p>
+</li><li>
+<p>An erroneous password.</p>
+</li><li>
+<p>An <tt class="literal">invalid</tt> <tt class="literal">users</tt> or
+<tt class="literal">valid</tt> <tt class="literal">users</tt> option in your
+<em class="emphasis">smb.conf</em> file that doesn't
+allow your account to connect. Recheck using
+<tt class="literal">testparm</tt> <tt class="literal">smb.conf</tt>
+<em class="replaceable">your_hostname your_ip_address</em> (see the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>).</p>
+</li><li>
+<p>A <tt class="literal">valid</tt> <tt class="literal">hosts</tt> option that
+doesn't include the server, or an
+<tt class="literal">invalid</tt> <tt class="literal">hosts</tt> option that does.
+Also test this with <em class="emphasis">testparm</em>.</p>
+</li><li>
+<p>A problem in authentication, such as if shadow passwords or the
+Password Authentication Module (PAM) is used on the server, but Samba
+is not compiled to use it. This is rare, but it occasionally happens
+when a SunOS 4 Samba binary (with no shadow passwords) is run without
+recompilation on a Solaris system (with shadow passwords).</p>
+</li><li>
+<p>The <tt class="literal">encrypted</tt> <tt class="literal">passwords</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> option is in the
+configuration file, but no password for your account is in the
+<em class="emphasis">smbpasswd</em> file.</p>
+</li><li>
+<p>You have a null password entry, either in Unix
+<em class="filename">/etc/passwd</em> or in the
+<em class="emphasis">smbpasswd</em> file.</p>
+</li><li>
+<p>You are connecting to <tt class="literal">[temp]</tt>, and you do not have
+the <tt class="literal">guest</tt> <tt class="literal">ok</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> option in the
+<tt class="literal">[temp]</tt> section of the
+<em class="emphasis">smb.conf</em> file.</p>
+</li><li>
+<p>You are connecting to <tt class="literal">[temp]</tt> before connecting to
+your home directory, and your guest account isn't
+set up correctly. If you can connect to your home directory and then
+connect to <tt class="literal">[temp]</tt>, that's the
+problem. See <a href="ch02.html">Chapter 2</a> for more information on
+creating a basic Samba configuration file.</p>
+
+<p>A bad guest account will also prevent you from printing or browsing
+until after you've logged in to your home directory.</p>
+</li></ul>
+<p>There is one more reason for this failure that has nothing at all to
+do with passwords: the <tt class="literal">path</tt> parameter in your
+<em class="filename">smb.conf</em> file might point somewhere that
+doesn't exist. This will not be diagnosed by
+<em class="emphasis">testparm</em>, and most SMB clients
+can't distinguish it from other types of bad user
+accounts. You will have to check it manually.</p>
+
+<p>Once you have connected to <tt class="literal">[temp]</tt> successfully,
+repeat the test, this time logging in to your home directory (e.g.,
+map network drive
+<em class="replaceable">server</em><tt class="literal">\davecb</tt>). If you
+have to change anything to get that to work, retest
+<tt class="literal">[temp]</tt> again afterward.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.5.4"/>
+
+<h3 class="head3">Testing connections with net use</h3>
+
+<p><a name="INDEX-63"/><a name="INDEX-64"/>Run the command
+<tt class="literal">net</tt> <tt class="literal">use</tt> <tt class="literal">*</tt>
+<tt class="literal">\</tt><em class="replaceable">server</em><tt class="literal">\temp</tt>
+on the Windows client to see if it can connect to the server. You
+should be prompted for a password, then receive the response
+<tt class="literal">The</tt> <tt class="literal">command</tt>
+<tt class="literal">was</tt> <tt class="literal">completed</tt>
+<tt class="literal">successfully</tt>.</p>
+
+<p>If that worked, continue with the steps in the next section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.5">Section 12.2.5.5</a>. Otherwise:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">specified</tt>
+<tt class="literal">shared</tt> <tt class="literal">directory</tt>
+<tt class="literal">cannot</tt> <tt class="literal">be</tt>
+<tt class="literal">found</tt>, or <tt class="literal">Cannot</tt>
+<tt class="literal">locate</tt> <tt class="literal">specified</tt>
+<tt class="literal">share</tt> <tt class="literal">name</tt>, the directory name
+is either misspelled or not in the <em class="emphasis">smb.conf</em>
+file. This message can also warn of a name that is in mixed case,
+including spaces, or that is longer than eight characters.</p>
+</li><li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">computer</tt>
+<tt class="literal">name</tt> <tt class="literal">specified</tt>
+<tt class="literal">in</tt> <tt class="literal">the</tt>
+<tt class="literal">network</tt> <tt class="literal">path</tt>
+<tt class="literal">cannot</tt> <tt class="literal">be</tt>
+<tt class="literal">located</tt> or <tt class="literal">Cannot</tt>
+<tt class="literal">locate</tt> <tt class="literal">specified</tt>
+<tt class="literal">computer</tt>, the directory name has been misspelled,
+the name service has failed, there is a networking problem, or the
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> option includes your
+host.</p>
+<ul><li>
+<p>If it is not a spelling mistake, you need to double back at least to
+<a href="ch12.html#samba2-CHP-12-SECT-2.5.3">Section 12.2.5.3</a> to
+investigate why it doesn't connect.</p>
+</li><li>
+<p>If <em class="emphasis">smbclient</em> does work, there is a name service
+problem with the client name service, and you need to go forward to
+<a href="ch12.html#samba2-CHP-12-SECT-2.6.2">Section 12.2.6.2</a> and see if
+you can look up both the client and server with
+<em class="emphasis">nmblookup</em>.</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">password</tt>
+<tt class="literal">is</tt> <tt class="literal">invalid</tt>
+<tt class="literal">for</tt> <tt class="literal">\server\username</tt>, your
+locally cached copy on the client doesn't match the
+one on the server. You will be prompted for a replacement.</p>
+
+<a name="samba2-CHP-12-NOTE-157"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Each Windows 95/98/Me client keeps a local
+<em class="emphasis">password</em> file, but it's really
+just a cached copy of the password it sends to Samba and NT/2000/XP
+servers to authenticate you. That's what is being
+prompted for here. You can still log on to a Windows system without a
+password (but not to NT/2000/XP).</p>
+</blockquote>
+
+<p>If you provide your password and it still fails, your password is not
+being matched on the server, you have a <tt class="literal">valid</tt>
+<tt class="literal">users</tt> or <tt class="literal">invalid</tt>
+<tt class="literal">users</tt> list denying you permission, NetBEUI is
+interfering, or the encrypted password problem described in the next
+paragraph exists.</p>
+</li><li>
+<p>If your client is Windows NT 4.0, NT 3.5 with Patch 3, Windows 95
+with Patch 3, Windows 98, any of these with Internet Explorer 4.0, or
+any subsequent version of Windows, the system will default to
+Microsoft encryption for passwords. In general, if you have installed
+a major Microsoft product on any of the older Windows versions, you
+might have applied an update and turned on encrypted passwords. If
+the client is defaulting to encrypted passwords, you will need to
+specify <tt class="literal">encrypt</tt> <tt class="literal">passwords</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in your Samba
+configuration file if you are using a version of Samba prior to Samba
+3.0.</p>
+
+<a name="samba2-CHP-12-NOTE-158"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Because of Internet Explorer's willingness to honor
+URLs such as <em class="filename">file://somehost/somefile</em> by making
+SMB connections, clients up to and including Windows 95 Patch Level 2
+would happily send your password, in plain text, to SMB servers
+anywhere on the Internet. This was considered a bad idea, and
+Microsoft switched to using only encrypted passwords in the SMB
+protocol. All subsequent releases of Microsoft's
+products have included this correction.</p>
+</blockquote>
+</li>
+
+<li>
+<p>If you have a mixed-case password on Unix, the client is probably
+sending it in all one case. If changing your password to all one case
+works, this was the problem. Regrettably, all but the oldest clients
+support uppercase passwords, so Samba will try once with the password
+in uppercase and once in lowercase. If you wish to use mixed-case
+passwords, see the <tt class="literal">password</tt>
+<tt class="literal">level</tt> option in <a href="ch09.html">Chapter 9</a> for a
+workaround.</p>
+</li><li>
+<p>You might have a <tt class="literal">valid</tt> <tt class="literal">users</tt>
+problem, as tested with <em class="emphasis">smbclient</em> (see the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.3">Section 12.2.5.3</a>).</p>
+</li><li>
+<p>You might have the NetBEUI protocol bound to the Microsoft client.
+This often produces long timeouts and erratic failures and is known
+to have caused failures to accept passwords in the past. Unless you
+absolutely need the NetBEUI protocol, remove it.</p>
+</li></ul>
+<a name="samba2-CHP-12-NOTE-159"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The term &quot;bind&quot; is used here to
+mean connecting one piece of software to another. When configured
+correctly, the Microsoft SMB client is &quot;bound
+to&quot; TCP/IP in the bindings section of the TCP/IP
+properties panel under the Windows 95/98/Me Network icon in the
+Control Panel. TCP/IP in turn is bound to an Ethernet card. This is
+not the same sense of the word as binding an SMB daemon to a TCP/IP
+port.</p>
+</blockquote>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.5.5"/>
+
+<h3 class="head3">Testing connections with Windows Explorer</h3>
+
+<p><a name="INDEX-65"/><a name="INDEX-66"/>Start Windows Explorer
+(not Internet Explorer), select Map Network Drive from the Tools
+menu, and specify the UNC for one of your shares on the Samba server
+to see if you can make Explorer connect to it. If so,
+you've succeeded and can skip to the next section,
+<a href="ch12.html#samba2-CHP-12-SECT-2.6">Section 12.2.6</a>.</p>
+
+<p>Windows Explorer is a rather poor diagnostic tool: it tells you that
+something's wrong, but rarely what it is. If you get
+a failure, you'll need to track it down with the
+Windows <em class="emphasis">net use</em> command, which has far superior
+error reporting:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">password</tt>
+<tt class="literal">for</tt> <tt class="literal">this</tt>
+<tt class="literal">connection</tt> <tt class="literal">that</tt>
+<tt class="literal">is</tt> <tt class="literal">in</tt> <tt class="literal">your</tt>
+<tt class="literal">password</tt> <tt class="literal">file</tt>
+<tt class="literal">is</tt> <tt class="literal">no</tt> <tt class="literal">longer</tt>
+<tt class="literal">correct</tt>, you might have any of the following:</p>
+<ul><li>
+<p>Your locally cached copy on the client doesn't match
+the one on the server.</p>
+</li><li>
+<p>You didn't provide a username and password when
+logging on to the client. Some versions of Explorer will continue to
+send a null username and password, even if you provide a password.</p>
+</li><li>
+<p>You have misspelled the password.</p>
+</li><li>
+<p>You have an <tt class="literal">invalid</tt> <tt class="literal">users</tt> or
+<tt class="literal">valid</tt> <tt class="literal">users</tt> list denying
+permission.</p>
+</li><li>
+<p>Your client is defaulting to encrypted passwords, but Samba is
+configured with the <tt class="literal">encrypt</tt>
+<tt class="literal">passwords</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> configuration file parameter.</p>
+</li><li>
+<p>You have a mixed-case password, which the client is supplying in all
+one case.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">network</tt>
+<tt class="literal">name</tt> <tt class="literal">is</tt>
+<tt class="literal">either</tt> <tt class="literal">incorrect</tt>,
+<tt class="literal">or</tt> <tt class="literal">a</tt> <tt class="literal">network</tt>
+<tt class="literal">to</tt> <tt class="literal">which</tt> <tt class="literal">you</tt>
+<tt class="literal">do</tt> <tt class="literal">not</tt> <tt class="literal">have</tt>
+<tt class="literal">full</tt> <tt class="literal">access</tt>, or
+<tt class="literal">Cannot</tt> <tt class="literal">locate</tt>
+<tt class="literal">specified</tt> <tt class="literal">computer</tt>, you might
+have any of the following:</p>
+<ul><li>
+<p>Misspelled name</p>
+</li><li>
+<p>Malfunctioning service</p>
+</li><li>
+<p>Failed share</p>
+</li><li>
+<p>Networking problem</p>
+</li><li>
+<p>Bad <tt class="literal">path</tt> parameter in
+<em class="filename">smb.conf</em></p>
+</li><li>
+<p><tt class="literal">hosts</tt> <tt class="literal">deny</tt> line that excludes
+you</p>
+</li>
+</ul>
+</li>
+<li>
+<p>If you get <tt class="literal">You</tt> <tt class="literal">must</tt>
+<tt class="literal">supply</tt> <tt class="literal">a</tt>
+<tt class="literal">password</tt> <tt class="literal">to</tt>
+<tt class="literal">make</tt> <tt class="literal">this</tt>
+<tt class="literal">connection</tt>, the password on the client is out of
+synchronization with the server, or this is the first time
+you've tried from this client system and the client
+hasn't cached it locally yet.</p>
+</li><li>
+<p>If you get <tt class="literal">Cannot</tt> <tt class="literal">locate</tt>
+<tt class="literal">specified</tt> <tt class="literal">share</tt>
+<tt class="literal">name</tt>, you have a wrong share name or a syntax
+error in specifying it, a share name longer than eight characters, or
+one containing spaces or in mixed case.</p>
+</li></ul>
+<p>Once you can reliably connect to the share, try again, this time
+using your home directory. If you have to change something to get
+home directories working, retest with the first share, and vice
+versa, as we showed in the earlier section, &quot;Testing
+connections with net use.&quot; As always, if Explorer
+fails, drop back to that section and debug the connection there.
+<a name="INDEX-67"/><a name="INDEX-68"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.6"/>
+
+<h3 class="head2">Troubleshooting Browsing</h3>
+
+<p><a name="INDEX-69"/><a name="INDEX-70"/>Finally, we
+come to browsing. We've left this for last, not
+because it is the most difficult, but because it's
+both optional and partially dependent on a protocol that
+doesn't guarantee delivery of a packet. Browsing is
+hard to diagnose if you don't already know that all
+the other services are running.</p>
+
+<p>Browsing is purely optional: it's just a way to find
+the servers on your network and the shares that they provide. Unix
+has nothing of the sort and happily does without. Browsing also
+assumes all your systems are on a local area network (LAN) where
+broadcasts are allowable.</p>
+
+<p>First, the browsing mechanism identifies a system using the
+unreliable UDP protocol; it then makes a normal (reliable) TCP/IP
+connection to list the shares the system provides.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.1"/>
+
+<h3 class="head3">Testing browsing with smbclient</h3>
+
+<p><a name="INDEX-71"/><a name="INDEX-72"/>We'll start with
+testing the reliable connection first. From the server, try listing
+its own shares using <em class="emphasis">smbclient</em> with a
+<tt class="literal">-L</tt> option and your server's name.
+You should get something resembling the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient -L server</b></tt> 
+Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 Server 
+time is Tue Apr 28 09:57:28 2002 Timezone is UTC-4.0 
+Password: 
+Domain=[EXAMPLE] OS=[Unix] Server=[Samba 2.2.5]
+
+   Sharename      Type      Comment    
+   ---------      ----      -------    
+    cdrom          Disk      CD-ROM    
+    cl             Printer   Color Printer 1    
+    davecb         Disk      Home Directories
+
+   Server         Comment    
+   ---------      -------    
+   SERVER         Samba 2.2.5
+
+   Workgroup      Master    
+   ---------      -------    
+   EXAMPLE        SERVER</pre></blockquote>
+
+<ul><li>
+<p>If you didn't get a Sharename list, the server is
+not allowing you to browse any shares. This should not be the case if
+you've tested any of the shares with Windows
+Explorer or the <em class="emphasis">net use</em> command. If you
+haven't done the <tt class="literal">smbclient</tt>
+<tt class="literal">-L</tt> <tt class="literal">localhost</tt>
+<tt class="literal">-U%</tt> test yet (see the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.2">Section 12.2.5.2</a>), do it now. An erroneous
+guest account can prevent the shares from being seen. Also, check the
+<em class="filename">smb.conf</em> file to make sure you do not have the
+option <tt class="literal">browsable</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt> anywhere in it: we suggest using a minimal
+<em class="filename">smb.conf</em> file (see the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.1">Section 12.2.5.1</a>). You need to have
+<tt class="literal">browsable</tt> enabled (which is the default) to see
+the share.</p>
+</li><li>
+<p>If you didn't get a browse list, the server is not
+providing information about the systems on the network. At least one
+system on the net must support browse lists. Make sure you have
+<tt class="literal">local</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
+<em class="filename">smb.conf</em> file if you want Samba to be the local
+master browser.</p>
+</li><li>
+<p>If you got a browse list but didn't get
+<em class="emphasis">/tmp</em>, you probably have a
+<em class="filename">smb.conf</em> problem. Go back to <a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>.</p>
+</li><li>
+<p>If you didn't get a workgroup list with your
+workgroup name in it, it is possible that your workgroup is set
+incorrectly in the <em class="filename">smb.conf</em> file.</p>
+</li><li>
+<p>If you didn't get a workgroup list at all, ensure
+that <tt class="literal">workgroup</tt> <tt class="literal">=</tt>
+<tt class="literal">EXAMPLE</tt> is present in the
+<em class="filename">smb.conf</em> file.</p>
+</li><li>
+<p>If you get nothing, try once more with the options
+<tt class="literal">-I</tt> <em class="emphasis">ip_address</em>
+<tt class="literal">-n</tt> <em class="emphasis">netbios_name</em>
+<tt class="literal">-W</tt> <em class="emphasis">workgroup</em>
+<tt class="literal">-d3</tt> with the NetBIOS and workgroup name in
+uppercase. (The <tt class="literal">-d3</tt> option sets the log /debugging
+level to 3.) Then check the Samba logs for clues.</p>
+</li></ul>
+<p>If you're still getting nothing, you
+shouldn't have gotten this far; double back to at
+least <a href="ch12.html#samba2-CHP-12-SECT-2.3.1">Section 12.2.3.1</a>, or perhaps
+<a href="ch12.html#samba2-CHP-12-SECT-2.2.4">Section 12.2.2.4</a>. On the other hand:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">SMBtconX</tt> <tt class="literal">failed</tt>.
+<tt class="literal">ERRSRV--ERRaccess</tt>, you aren't
+permitted access to the server. This normally means you have a
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> option that
+doesn't include the server or a
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> option that does.</p>
+</li><li>
+<p>If you get <tt class="literal">Bad</tt> <tt class="literal">password</tt>, you
+presumably have one of the following:</p>
+<ul><li>
+<p>An incorrect <tt class="literal">hosts</tt> <tt class="literal">allow</tt> or
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> line</p>
+</li><li>
+<p>An incorrect <tt class="literal">invalid</tt> <tt class="literal">users</tt> or
+<tt class="literal">valid</tt> <tt class="literal">users</tt> line</p>
+</li><li>
+<p>A lowercase password and OS/2 or Windows for Workgroups clients</p>
+</li><li>
+<p>A missing or invalid guest account</p>
+</li></ul>
+<p>Check what your guest account is (see the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.2">Section 12.2.5.2</a>), change or comment out any
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt>,
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt>,
+<tt class="literal">valid</tt> <tt class="literal">users</tt>, or
+<tt class="literal">invalid</tt> <tt class="literal">users</tt> lines, and verify
+your <em class="filename">smb.conf</em> file with
+<tt class="literal">testparm</tt> <tt class="literal">smb.conf</tt>
+<em class="replaceable">your_hostname your_ip_address</em> (see the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.4.5">Section 12.2.4.5</a>).</p>
+</li><li>
+<p>If you get <tt class="literal">Connection</tt> <tt class="literal">refused</tt>,
+the <em class="emphasis">smbd</em> server is not running or has crashed.
+Check that it's up, running, and listening to the
+network with <em class="emphasis">netstat</em>. See the earlier section,
+<a href="ch12.html#samba2-CHP-12-SECT-2.4">Section 12.2.4</a>.</p>
+</li><li>
+<p>If you get <tt class="literal">Get_Hostbyname</tt>:
+<tt class="literal">Unknown</tt> <tt class="literal">host</tt>
+<tt class="literal">name</tt>, you've made a spelling
+error, there is a mismatch between the Unix and NetBIOS hostname, or
+there is a name service problem. Start name service debugging as
+discussed in the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.4">Section 12.2.5.4</a>. If this works, suspect a
+name mismatch, and go to the later section, <a href="ch12.html#samba2-CHP-12-SECT-2.9">Section 12.2.9</a>.</p>
+</li><li>
+<p>If you get <tt class="literal">Session</tt> <tt class="literal">request</tt>
+<tt class="literal">failed</tt>, the server refused the connection. This
+usually indicates an internal error, such as insufficient memory to
+fork a process.</p>
+</li><li>
+<p>If you get <tt class="literal">Your</tt> <tt class="literal">server</tt>
+<tt class="literal">software</tt> <tt class="literal">is</tt>
+<tt class="literal">being</tt> <tt class="literal">unfriendly</tt>, the initial
+session request packet received a garbage response from the server.
+The server might have crashed or started improperly. Go back to <a href="ch12.html#samba2-CHP-12-SECT-2.5.2">Section 12.2.5.2</a>, where the
+problem is first analyzed.</p>
+</li><li>
+<p>If you suspect the server is not running, go back to
+<a href="ch12.html#samba2-CHP-12-SECT-2.4.2">Section 12.2.4.2</a> to see why the server
+daemon isn't responding.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.2"/>
+
+<h3 class="head3">Testing the server with nmblookup</h3>
+
+<p><a name="INDEX-73"/><a name="INDEX-74"/>This will test the
+&quot;advertising&quot; system used for
+Windows name services and browsing. Advertising works by broadcasting
+one's presence or willingness to provide services.
+It is the part of browsing that uses an unreliable protocol (UDP) and
+works only on broadcast networks such as Ethernets. The
+<em class="emphasis">nmblookup</em> program broadcasts name queries for
+the hostname you provide and returns its IP address and the name of
+the system, much as <em class="emphasis">nslookup</em> does with DNS.
+Here, the <em class="emphasis">-d</em> (debug or log-level) and
+<em class="emphasis">-B</em> (broadcast address) options direct queries to
+specific systems.</p>
+
+<p>First, we check the server from itself. Run
+<em class="emphasis">nmblookup</em> with a <em class="emphasis">-B</em> option
+of your server's name (to tell it to send the query
+to the Samba server) and a parameter of <tt class="literal">_ _SAMBA_
+_</tt> as the symbolic name to look up. You should get:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>nmblookup -B server _ _SAMBA_ _</b></tt>
+Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 
+Sending queries to 192.168.236.86 192.168.236.86 _ _SAMBA_ _</pre></blockquote>
+
+<p>You should get the IP address of the server, followed by the name
+<tt class="literal">_ _SAMBA_ _</tt> , which means that the server has
+successfully advertised that it has a service called <tt class="literal">_
+_SAMBA_ _</tt> , and therefore at least part of NetBIOS name
+service works.</p>
+
+<ul><li>
+<p>If you get <tt class="literal">Name_query</tt> <tt class="literal">failed</tt>
+<tt class="literal">to</tt> <tt class="literal">find</tt> <tt class="literal">name</tt>
+<tt class="literal">_ _SAMBA_ _</tt>, you might have specified the server
+name to the <em class="emphasis">-B</em> option, or
+<em class="emphasis">nmbd</em> is not running. The <em class="emphasis">-B</em>
+option actually takes a broadcast address: we're
+using a computer name to get a unicast address and to ask the server
+if it has claimed <tt class="literal">_ _SAMBA_ _</tt>. Try again with
+<tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<em class="replaceable">ip_address</em>, and if that fails too,
+<em class="emphasis">nmbd</em> isn't claiming the name.
+Go back briefly to the earlier section, &quot;Testing
+daemons with testparm,&quot; to see if
+<em class="emphasis">nmbd</em> is running. If so, it might not be claiming
+names; this means that Samba is not providing the browsing
+service&mdash;a configuration problem. If that is the case, make sure
+that <em class="filename">smb.conf</em> doesn't contain
+the option <tt class="literal">browsing</tt> <tt class="literal">=</tt>
+<tt class="literal">no</tt>.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.3"/>
+
+<h3 class="head3">Testing the client with nmblookup</h3>
+
+<p><a name="INDEX-75"/><a name="INDEX-76"/>Next, check the IP address of the
+client from the server with <em class="emphasis">nmblookup</em> using the
+<tt class="literal">-B</tt> option for the client's name
+and a parameter of '<tt class="literal">*</tt>' meaning
+&quot;anything,&quot; as shown here:</p>
+
+<blockquote><pre class="code">$ <b class="emphasis-bold">nmblookup -B client '*</b>' 
+Sending queries to 192.168.236.10 192.168.236.10 *
+Got a positive name query response from 192.168.236.10 (192.168.236.10)</pre></blockquote>
+
+<p>You might get the following error:</p>
+
+<ul><li>
+<p>If you receive <tt class="literal">Name-query</tt>
+<tt class="literal">failed</tt> <tt class="literal">to</tt>
+<tt class="literal">find</tt> <tt class="literal">name</tt> <tt class="literal">*</tt>,
+you have made a spelling mistake, or the client software on the PC
+isn't installed, started, or bound to TCP/IP. Double
+back to <a href="ch03.html">Chapter 3</a> and ensure that you have a
+client installed that is listening to the network.</p>
+</li></ul>
+<p>Repeat the command with the following options if you had any failures:</p>
+
+<ul><li>
+<p>If <tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<em class="replaceable">client_IP_address</em> succeeds but
+<tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<em class="replaceable">client_name</em> fails, there is a name service
+problem with the client's name; go to <a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>, later in this chapter.</p>
+</li><li>
+<p>If <tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<tt class="literal">127.0.0.1</tt> '<tt class="literal">*</tt>' succeeds, but
+<tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<em class="replaceable">client_IP_address</em> fails, there is a
+hardware problem, and <em class="emphasis">ping</em> should have failed.
+See your network manager.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.4"/>
+
+<h3 class="head3">Testing the network with nmblookup</h3>
+
+<p><a name="INDEX-77"/><a name="INDEX-78"/>Run the command
+<em class="emphasis">nmblookup</em> again with a <em class="emphasis">-d2</em>
+option (for a debug level of 2) and a parameter of
+'<tt class="literal">*</tt>'. This time we are testing the ability of
+programs (such as <em class="emphasis">nmbd</em> ) to use broadcast.
+It's essentially a connectivity test, done via a
+broadcast to the default broadcast address.</p>
+
+<p>A number of NetBIOS over TCP/IP hosts on the network should respond
+with <tt class="literal">got</tt> <tt class="literal">a</tt>
+<tt class="literal">positive</tt> <tt class="literal">name</tt>
+<tt class="literal">query</tt> <tt class="literal">response</tt> messages. Samba
+might not catch all the responses in the short time it listens, so
+you won't always see all the SMB clients on the
+network. However, you should see most of them:</p>
+
+<blockquote><pre class="code">$ <b class="emphasis-bold">nmblookup -d 2 '*</b>' 
+Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 Sending 
+queries to 192.168.236.255 
+Got a positive name query response from 192.168.236.191 (192.168.236.191) 
+Got a positive name query response from 192.168.236.228 (192.168.236.228) 
+Got a positive name query response from 192.168.236.75 (192.168.236.75) 
+Got a positive name query response from 192.168.236.79 (192.168.236.79) 
+Got a positive name query response from 192.168.236.206 (192.168.236.206) 
+Got a positive name query response from 192.168.236.207 (192.168.236.207) 
+Got a positive name query response from 192.168.236.217 (192.168.236.217) 
+Got a positive name query response from 192.168.236.72 (192.168.236.72) 192.168.236.86 *</pre></blockquote>
+
+<p>However:</p>
+
+<ul><li>
+<p>If this doesn't give at least the client address you
+previously tested, the default broadcast address is wrong. Try
+<tt class="literal">nmblookup</tt> <tt class="literal">-B</tt>
+<tt class="literal">255.255.255.255</tt> <tt class="literal">-d</tt>
+<tt class="literal">2</tt> '<tt class="literal">*</tt>', which is a last-ditch
+variant (using a broadcast address of all 1s). If this draws
+responses, the broadcast address you've been using
+before is wrong. Troubleshooting these is discussed in <a href="ch12.html#samba2-CHP-12-SECT-2.8.2">Section 12.2.8.2</a>, later in this
+chapter.</p>
+</li><li>
+<p>If the address 255.255.255.255 fails too, check your notes to see if
+your PC and server are on different subnets, as discovered in the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.2.4">Section 12.2.2.4</a>. You
+should try to diagnose this step with a server and client on the same
+subnet, but if you can't, you can try specifying the
+remote subnet's broadcast address with
+<em class="emphasis">-B</em>. Finding that address is discussed in <a href="ch12.html#samba2-CHP-12-SECT-2.8.2">Section 12.2.8.2</a>, later in this
+chapter. The <em class="emphasis">-B</em> option will work if your router
+supports directed broadcasts; if it doesn't, you
+might be forced to test with a client on the same network.</p>
+</li></ul>
+<p>As usual, you can check the Samba log files for additional clues.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.5"/>
+
+<h3 class="head3">Testing client browsing with net view</h3>
+
+<p><a name="INDEX-79"/><a name="INDEX-80"/>On the client, run the
+command <em class="replaceable">net view \\server</em> in an MS-DOS
+(command prompt) window to see if you can connect to the client and
+ask what shares it provides. You should get back a list of available
+shares on the server.</p>
+
+<p>If this works, continue with the later section <a href="ch12.html#samba2-CHP-12-SECT-3.1">Section 12.3.1</a>. Otherwise:</p>
+
+<ul><li>
+<p>If you get <tt class="literal">Network</tt> <tt class="literal">name</tt>
+<tt class="literal">not</tt> <tt class="literal">found</tt> for the name you just
+tested in the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.6.3">Section 12.2.6.3</a>, there is a problem with the
+client software itself. Double-check this by running
+<em class="emphasis">nmblookup</em> on the client; if it works and
+<em class="emphasis">net view</em> doesn't, the client is
+at fault.</p>
+</li><li>
+<p>If <em class="emphasis">nmblookup</em> fails, there is a NetBIOS name
+service problem, as discussed in the later section, <a href="ch12.html#samba2-CHP-12-SECT-2.9">Section 12.2.9</a>.</p>
+</li><li>
+<p>If you get <tt class="literal">You</tt> <tt class="literal">do</tt>
+<tt class="literal">not</tt> <tt class="literal">have</tt> <tt class="literal">the</tt>
+<tt class="literal">necessary</tt> <tt class="literal">access</tt>
+<tt class="literal">rights</tt>, or <tt class="literal">This</tt>
+<tt class="literal">server</tt> <tt class="literal">is</tt>
+<tt class="literal">not</tt> <tt class="literal">configured</tt>
+<tt class="literal">to</tt> <tt class="literal">list</tt>
+<tt class="literal">shared</tt> <tt class="literal">resources</tt>, either your
+guest account is misconfigured (see the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.5.2">Section 12.2.5.2</a>) or you have a
+<tt class="literal">hosts</tt> <tt class="literal">allow</tt> or
+<tt class="literal">hosts</tt> <tt class="literal">deny</tt> line that prohibits
+connections from your system. These problems should have been
+detected by the <em class="emphasis">smbclient</em> tests starting in the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.6.1">Section 12.2.6.1</a>.</p>
+</li><li>
+<p>If you get <tt class="literal">The</tt> <tt class="literal">specified</tt>
+<tt class="literal">computer</tt> <tt class="literal">is</tt>
+<tt class="literal">not</tt> <tt class="literal">receiving</tt>
+<tt class="literal">requests</tt>, you have misspelled the name, the system
+is unreachable by broadcast (tested in the earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.6.4">Section 12.2.6.4</a>), or it's
+not running <em class="emphasis">nmbd</em>.</p>
+</li><li>
+<p>If you get <tt class="literal">Bad</tt> <tt class="literal">password</tt>
+<tt class="literal">error</tt>, you're probably
+encountering the Microsoft-encrypted password problem, as discussed
+earlier in this chapter and in <a href="ch09.html">Chapter 9</a>, with its
+corrections.</p>
+</li></ul>
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.6.6"/>
+
+<h3 class="head3">Browsing the server from the client</h3>
+
+<p><a name="INDEX-81"/><a name="INDEX-82"/>From the Windows Network
+Neighborhood (or My Network Places in newer releases), try to browse
+the server. Your Samba server should appear in the browse list of
+your local workgroup. You should be able to double-click the name of
+the server to get a list of shares.</p>
+
+<ul><li>
+<p>If you get an <tt class="literal">Invalid</tt> <tt class="literal">password</tt>
+error, it's most likely the encryption problem
+again.</p>
+</li><li>
+<p>If you receive an <tt class="literal">Unable</tt> <tt class="literal">to</tt>
+<tt class="literal">browse</tt> <tt class="literal">the</tt>
+<tt class="literal">network</tt> error, one of the following has occurred:</p>
+<ul><li>
+<p>You have looked too soon, before the broadcasts and updates have
+completed. Wait 30 seconds and try again.</p>
+</li><li>
+<p>There is a network problem you've not yet diagnosed.</p>
+</li><li>
+<p>There is no browse master. Add the configuration option
+<tt class="literal">local</tt> <tt class="literal">master</tt>
+<tt class="literal">=</tt> <tt class="literal">yes</tt> to your
+<em class="emphasis">smb.conf</em> file.</p>
+</li><li>
+<p>No shares are made browsable in the <em class="emphasis">smb.conf</em>
+file.</p>
+</li></ul>
+</li>
+<li>
+<p>If you receive the message <tt class="literal">\\server</tt>
+<tt class="literal">is</tt> <tt class="literal">not</tt>
+<tt class="literal">accessible</tt> then:</p>
+<ul><li>
+<p>You have the encrypted password problem.</p>
+</li><li>
+<p>The system really isn't accessible.</p>
+</li><li>
+<p>The system doesn't support browsing.</p>
+</li></ul>
+</li>
+</ul>
+
+<p>If you've made it this far and the problem is not
+yet solved, either the problem is one we've not yet
+seen, or it is a problem related to a topic we have already covered,
+and further analysis is required. Name resolution is often related to
+difficulties with Samba, so we cover it in more detail in the next
+sections. If you know your problem is not related to name resolution,
+skip to the <a href="ch12.html#samba2-CHP-12-SECT-3">Section 12.3</a> at the end of the chapter. <a name="INDEX-83"/><a name="INDEX-84"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.7"/>
+
+<h3 class="head2">Troubleshooting Name Services</h3>
+
+<p><a name="INDEX-85"/><a name="INDEX-86"/>This
+section looks at simple troubleshooting of all the name services
+you'll encounter, but only for the common problems
+that affect Samba.</p>
+
+<p>There are several good references for troubleshooting particular name
+services: Paul <a name="INDEX-87"/>Albitz and Cricket <a name="INDEX-88"/>Liu's <em class="emphasis">DNS and
+Bind</em> (O'Reilly) covers the DNS, Hal
+<a name="INDEX-89"/>Stern's <em class="emphasis">NFS and
+NIS</em> (O'Reilly) covers NIS
+(&quot;Yellow pages&quot;), while Windows
+Internet Name Service (WINS), <em class="filename">hosts/LMHOSTS</em>
+files, and NIS+ are best covered by their respective
+vendors' manuals.</p>
+
+<p>The problems addressed in this section are as follows:</p>
+
+<ul><li>
+<p>Name services are identified.</p>
+</li><li>
+<p>A hostname can't be looked up.</p>
+</li><li>
+<p>The long (FQDN) form of a hostname works but the short form
+doesn't.</p>
+</li><li>
+<p>The short form of the name works, but the long form
+doesn't.</p>
+</li><li>
+<p>A long delay occurs before the expected result.</p>
+</li></ul>
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.7.1"/>
+
+<h3 class="head3">Identifying what's in use</h3>
+
+<p><a name="INDEX-90"/>First, see if both the
+server and the client are using DNS, WINS, NIS, or
+<em class="filename">hosts</em> files to look up IP addresses when you
+give them a name. Each kind of system has a different preference:</p>
+
+<ul><li>
+<p>Windows 95/98/Me tries WINS and the <em class="filename">LMHOSTS</em> file
+first, then broadcast, and finally DNS and <em class="filename">HOSTS</em>
+files.</p>
+</li><li>
+<p>Windows NT/2000/XP tries WINS, then broadcast, then the
+<em class="filename">LMHOSTS</em> file, and finally
+<em class="filename">HOSTS</em> and DNS.</p>
+</li><li>
+<p>Windows programs using the WINSOCK standard use the HOSTS file, DNS,
+WINS, and then broadcast. Don't assume that if a
+different program's name service works, the SMB
+client program's name service will!</p>
+</li><li>
+<p>Samba daemons use <em class="filename">lmhosts</em>, WINS, the Unix
+system's name resolution, and then broadcast.</p>
+</li><li>
+<p>Unix systems can be configured to use any combination of DNS,
+<em class="filename">HOSTS</em> files, NIS or NIS+, and winbind, generally
+in any order.</p>
+</li></ul>
+<p>We recommend that the client systems be configured to use WINS and
+DNS, the Samba daemons to use WINS and DNS, and the Unix server to
+use DNS, <em class="filename">hosts</em> files, and perhaps NIS+.
+You'll have to look at your notes and the actual
+systems to see which is in use.</p>
+
+<p>On the clients, the name services are all set in the TCP/IP
+Properties panel of the Networking Control Panel, as discussed in
+<a href="ch03.html">Chapter 3</a>. You might need to check there to see
+what you've actually turned on. On the server, see
+if a <em class="filename">/etc/resolv.conf</em> file exists. If it does,
+you're using DNS. You might be using the others as
+well, though. You'll need to check for NIS and
+combinations of services.</p>
+
+<p>Check for a <em class="filename">/etc/nsswitch.conf</em> file on Solaris
+and other System V Unix operating systems. If you have one, look for
+a line that begins with <tt class="literal">host</tt>: followed by one or
+more of <tt class="literal">files</tt>, <tt class="literal">bind</tt>,
+<tt class="literal">nis</tt>, or <tt class="literal">nis+</tt>. These are the
+name services to use, in order, with optional extra material in
+square brackets. The <tt class="literal">files</tt> keyword is for
+using <em class="emphasis">HOSTS</em> files, while <tt class="literal">bind</tt>
+(the Berkeley Internet Name Daemon) refers to using DNS.</p>
+
+<p>If the client and server differ, the first thing to do is to get them
+in sync. Clients can use DNS, WINS, <em class="emphasis">HOSTS</em>, and
+<em class="emphasis">LMHOSTS</em> files, but not NIS or NIS+. Servers can
+use <em class="emphasis">HOSTS</em> and <em class="filename">LMHOSTS</em>
+files, DNS, NIS or NIS+, and winbind, but not WINS&mdash;even if your
+Samba server provides WINS services. If you can't
+get all the systems to use the same services, you'll
+have to check the server and the client carefully for the same data.</p>
+
+<p>You can also make use of the <em class="emphasis">-R</em> (resolve order)
+option for <em class="emphasis">smbclient</em>. If you want to
+troubleshoot WINS, for example, you'd say:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>smbclient -L </b></tt><em class="replaceable">server</em> <tt class="userinput"><b>-R wins</b></tt></pre></blockquote>
+
+<p>The possible settings are <tt class="literal">hosts</tt> (which means
+whatever the Unix system is using, not just<em class="filename">
+/etc/hosts</em> files), <tt class="literal">lmhosts</tt>,
+<tt class="literal">wins</tt>, and <tt class="literal">bcast</tt> (broadcast).</p>
+
+<p>In the following sections, we use the term <em class="emphasis">long
+name</em> for a fully qualified domain name (FQDN), such as
+<tt class="literal">server.example.com</tt> , and the term <em class="emphasis">short
+name</em> for the host part of an FQDN, such as
+<tt class="literal">server</tt>.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.7.2"/>
+
+<h3 class="head3">Cannot look up hostnames</h3>
+
+<p><a name="INDEX-91"/>Try the
+following:</p>
+
+<dl>
+<dt><b>DNS</b></dt>
+<dd>
+<p>Run <tt class="literal">nslookup</tt> <em class="replaceable">name</em>. If
+this fails, look for a <em class="filename">resolv.conf</em> error, a
+downed DNS server, or a short/long name problem (see the next
+section). Try the following:</p>
+
+
+<ul><li>
+<p>Your <em class="filename">/etc/resolv.conf</em> file should contain one or
+more <tt class="literal">nameserver</tt> lines, each with an IP address.
+These are the addresses of your DNS servers.</p>
+</li><li>
+<p>Ping each server address you find. If this fails for one, suspect the
+system. If it fails for each, suspect your network.</p>
+</li><li>
+<p>Retry the lookup using the full domain name (e.g.,
+<tt class="literal">server.example.com</tt>) if you tried the short name
+first, or the short name if you tried the long name first. If results
+differ, skip to the next section.</p>
+</li></ul>
+</dd>
+
+
+
+<dt><b>Broadcast/ WINS</b></dt>
+<dd>
+<p>Broadcast/ WINS does only short names such as
+<tt class="literal">server</tt>, and not long ones, such as
+<tt class="literal">server.example.com</tt>. Run
+<tt class="literal">nmblookup</tt> <tt class="literal">-S</tt>
+<em class="replaceable">server</em>. This reports everything broadcast
+has registered for the name. In our example, it looks like this:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>nmblookup -S server</b></tt>
+Looking up status of 192.168.236.86
+received 10 names
+        SERVER           &lt;00&gt; -         M &lt;ACTIVE&gt; 
+        SERVER           &lt;03&gt; -         M &lt;ACTIVE&gt; 
+        SERVER           &lt;1f&gt; -         M &lt;ACTIVE&gt; 
+        SERVER           &lt;20&gt; -         M &lt;ACTIVE&gt; 
+        ..__MSBROWSE__.  &lt;01&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt; 
+        MYGROUP          &lt;00&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt; 
+        MYGROUP          &lt;1b&gt; -         M &lt;ACTIVE&gt; 
+        MYGROUP          &lt;1c&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt; 
+        MYGROUP          &lt;1d&gt; -         M &lt;ACTIVE&gt; 
+        MYGROUP          &lt;1e&gt; - &lt;GROUP&gt; M &lt;ACTIVE&gt;</pre></blockquote>
+
+<p>The required entry is <tt class="literal">SERVER</tt>
+<tt class="literal">&lt;00&gt;</tt>, which identifies
+<em class="replaceable">server</em> as being this
+system's NetBIOS name. You should also see your
+workgroup mentioned one or more times. If these lines are missing,
+Broadcast/WINS cannot look up names and will need attention.</p>
+
+<a name="samba2-CHP-12-NOTE-160"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>The numbers in angle brackets in the previous output identify NetBIOS
+names as being workgroups, workstations, and file users of the
+messenger service, master browsers, domain master browsers, domain
+controllers, and a plethora of others. We primarily use
+<tt class="literal">&lt;00&gt;</tt> to identify system and workgroup names
+and <tt class="literal">&lt;20&gt;</tt> to identify systems as servers. The
+complete list is available at <a href="http://support.microsoft.com/support/kb/articles/q163/4/09.asp">http://support.microsoft.com/support/kb/articles/q163/4/09.asp</a>.</p>
+</blockquote>
+</dd>
+
+
+
+<dt><b>NIS</b></dt>
+<dd>
+<p>Try <tt class="literal">ypmatch</tt> <tt class="literal">name</tt>
+<tt class="literal">hosts</tt>. If this fails, NIS is down. Find out the
+NIS server's name by running
+<em class="emphasis">ypwhich</em>, and ping the system to see if
+it's accessible.</p>
+</dd>
+
+
+
+<dt><b>NIS+</b></dt>
+<dd>
+<p>If you're running NIS+, try
+<tt class="literal">nismatch</tt> <tt class="literal">name</tt>
+<tt class="literal">hosts</tt>. If this fails, NIS is down. Find out the
+NIS+ server's name by running
+<em class="emphasis">niswhich</em>, and ping that system to see if
+it's accessible.</p>
+</dd>
+
+
+
+<dt><b>hosts and HOSTS files</b></dt>
+<dd>
+<p>Inspect the <em class="filename">HOSTS</em> file on the client
+(<em class="filename">C:\Windows\ Hosts</em> on Windows 95/98/Me, and
+<em class="filename">C:\WINNT \system32\drivers\etc\hosts</em> on Windows
+NT/2000/XP). Each line should have an IP number and one or more
+names, the primary name first, then any optional aliases. An example
+follows:</p>
+
+
+<blockquote><pre class="code">127.0.0.1         localhost
+192.168.236.1     dns.svc.example.com 
+192.168.236.10    client.example.com client 
+192.168.236.11    backup.example.com loghost 
+192.168.236.86    server.example.com server 
+192.168.236.254   router.svc.example.com</pre></blockquote>
+
+<p>On Unix, <tt class="literal">localhost</tt> should always be 127.0.0.1,
+although it might be just an alias for a hostname on the PC. On the
+client, check that there are no <tt class="literal">#XXX</tt> directives at
+the ends of the lines; these are LAN Manager/NetBIOS directives and
+should appear only in <em class="emphasis">LMHOSTS</em> files.</p>
+</dd>
+
+
+
+<dt><b>LMHOSTS files</b></dt>
+<dd>
+<p>This file is a local source for LAN Manager (NetBIOS) names. It has a
+format similar to <em class="filename">hosts</em> files, but it does not
+support long-form domain names (e.g.,
+<tt class="literal">server.example.com</tt>) and can have a number of
+optional <tt class="literal">#XXX</tt> directives following the NetBIOS
+names. There is usually an <em class="emphasis">lmhosts.sam</em> (for
+sample) file located in <em class="filename">C:\Windows</em> on Windows
+95/98/Me, and in <em class="filename">C:\WINNT\system32\drivers\etc</em>
+on Windows NT/2000/XP, but it's not used unless it
+is renamed to <em class="emphasis">Lmhosts</em> in the same directory.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.7.3"/>
+
+<h3 class="head3">Long and short hostnames</h3>
+
+<p><a name="INDEX-92"/>Where the long (FQDN) form of a hostname
+works but the short name doesn't (for example,
+<tt class="literal">client.example.com</tt> works but
+<tt class="literal">client</tt> doesn't), consider the
+following:</p>
+
+<dl>
+<dt><b>DNS </b></dt>
+<dd>
+<p>This usually indicates that there is no default domain in which to
+look up the short names. Look for a <tt class="literal">default</tt> line
+in <em class="filename">/etc/resolv.conf</em> on the Samba server with
+your domain in it, or look for a <tt class="literal">search</tt> line with
+one or more domains in it. One or the other might need to be present
+to make short names usable; which one depends on the vendor and
+version of the DNS resolver. Try adding <tt class="literal">domain</tt>
+<em class="replaceable">your_domain</em> to
+<em class="filename">resolv.conf</em>, and ask your network or DNS
+administrator what should be in the file.</p>
+</dd>
+
+
+
+<dt><b>Broadcast/WINS </b></dt>
+<dd>
+<p>Broadcast/WINS doesn't support long names; it
+won't suffer from this problem.</p>
+</dd>
+
+
+
+<dt><b>NIS </b></dt>
+<dd>
+<p>Try the command <tt class="literal">ypmatch</tt>
+<em class="replaceable">hostname</em> <tt class="literal">hosts</tt>. If you
+don't get a match, your tables
+don't include short names. Speak to your network
+manager; short names might be missing by accident or might be
+unsupported as a matter of policy. Some sites don't
+ever use (ambiguous) short names.</p>
+</dd>
+
+
+
+<dt><b>NIS+</b></dt>
+<dd>
+<p>Try <tt class="literal">nismatch</tt> <em class="replaceable">hostname</em>
+<tt class="literal">hosts</tt>, and treat failure exactly as with NIS.</p>
+</dd>
+
+
+
+<dt><b>hosts </b></dt>
+<dd>
+<p>If the short name is not in <em class="filename">/etc/hosts</em>, consider
+adding it as an alias. Avoid, if you can, short names as primary
+names (the first one on a line). Have them as aliases if your system
+permits.</p>
+</dd>
+
+
+
+<dt><b>LMHOSTS </b></dt>
+<dd>
+<p>LAN Manager doesn't support long names, so it
+won't suffer from this problem.</p>
+</dd>
+
+</dl>
+
+<p>On the other hand, if the short form of the name works and the long
+form doesn't, consider the following:</p>
+
+<dl>
+<dt><b>DNS </b></dt>
+<dd>
+<p>This is bizarre; see your network or DNS administrator, as this is
+probably a DNS setup error.</p>
+</dd>
+
+
+
+<dt><b>Broadcast/WINS </b></dt>
+<dd>
+<p>This is normal; Broadcast/WINS can't use the long
+form. Optionally, consider DNS. (Be aware that Microsoft has stated
+that it will eventually switch entirely to DNS, even though DNS does
+not provide name types such as &lt;00&gt;.)</p>
+</dd>
+
+
+
+<dt><b>NIS</b></dt>
+<dd>
+<p>If you can use <em class="emphasis">ypmatch</em> to look up the short form
+but not the long, consider adding the long form to the table as at
+least an alias.</p>
+</dd>
+
+
+
+<dt><b>NIS+ </b></dt>
+<dd>
+<p>Same as NIS, except you use <em class="emphasis">nismatch</em> instead of
+<em class="emphasis">ypmatch</em> to look up names.</p>
+</dd>
+
+
+
+<dt><b>hosts and HOSTS</b></dt>
+<dd>
+<p>Add the long name as at least an alias, and preferably as the primary
+form. Also consider using DNS if it's practical.</p>
+</dd>
+
+
+
+<dt><b>LMHOSTS </b></dt>
+<dd>
+<p>This is normal. LAN Manager can't use the long form;
+consider switching to DNS or <em class="filename">hosts</em>.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.7.4"/>
+
+<h3 class="head3">Unusual delays</h3>
+
+<p><a name="INDEX-93"/>When there is a long delay before the
+expected result:</p>
+
+<dl>
+<dt><b>DNS </b></dt>
+<dd>
+<p>Test the same name with the <em class="emphasis">nslookup</em> command on
+the system that is slow (client or server). If
+<em class="emphasis">nslookup</em> is also slow, you have a DNS problem.
+If it's slower on a client, you might have too many
+protocols bound to the Ethernet card. Eliminate NetBEUI, which is
+infamously slow, and, optionally, Novell&mdash;assuming you
+don't need them. This is especially important on
+Windows 95, which is particularly sensitive to excess protocols.</p>
+</dd>
+
+
+
+<dt><b>Broadcast/ WINS</b></dt>
+<dd>
+<p>Test the client using <em class="emphasis">nmblookup</em>; if
+it's faster, you probably have the protocols problem
+as mentioned in the previous item.</p>
+</dd>
+
+
+
+<dt><b>NIS</b></dt>
+<dd>
+<p>Try <em class="emphasis">ypmatch</em>; if it's slow,
+report the problem to your network manager.</p>
+</dd>
+
+
+
+<dt><b>NIS+ </b></dt>
+<dd>
+<p>Try <em class="emphasis">nismatch</em>, similarly.</p>
+</dd>
+
+
+
+<dt><b>hosts and HOSTS</b></dt>
+<dd>
+<p>The <em class="emphasis">hosts</em> files, if of reasonable size, are
+always fast. You probably have the protocols problem mentioned
+previously under DNS.</p>
+</dd>
+
+
+
+<dt><b>lmhosts and LMHOSTS</b></dt>
+<dd>
+<p>This is not a name lookup problem; <em class="emphasis">LMHOSTS</em> files
+are as fast as <em class="emphasis">hosts</em> and
+<em class="filename">HOSTS</em> files.</p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.7.5"/>
+
+<h3 class="head3">Localhost issues</h3>
+
+<p><a name="INDEX-94"/>When a localhost isn't
+127.0.0.1, try the following:</p>
+
+<dl>
+<dt><b>DNS</b></dt>
+<dd>
+<p>There is probably no record for <tt class="literal">localhost</tt>.
+<tt class="literal">A</tt> <tt class="literal">127.0.0.1</tt>. Arrange to add
+one, as well as a reverse entry,
+<tt class="literal">1.0.0.127.IN-ADDR.ARPA</tt> <tt class="literal">PTR</tt>
+<tt class="literal">127.0.0.1</tt>.</p>
+</dd>
+
+
+
+<dt><b>Broadcast/WINS</b></dt>
+<dd>
+<p>Not applicable.</p>
+</dd>
+
+
+
+<dt><b>NIS</b></dt>
+<dd>
+<p>If <tt class="literal">localhost</tt> isn't in the table,
+add it.</p>
+</dd>
+
+
+
+<dt><b>NIS+ </b></dt>
+<dd>
+<p>If <tt class="literal">localhost</tt> isn't in the table,
+add it.</p>
+</dd>
+
+
+
+<dt><b>hosts and HOSTS</b></dt>
+<dd>
+<p>Add a line that says <tt class="literal">127.0.0.1</tt>
+<tt class="literal">localhost</tt>.</p>
+</dd>
+
+
+
+<dt><b>LMHOSTS</b></dt>
+<dd>
+<p>Not applicable. <a name="INDEX-95"/><a name="INDEX-96"/></p>
+</dd>
+
+</dl>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.8"/>
+
+<h3 class="head2">Troubleshooting Network Addresses</h3>
+
+<p><a name="INDEX-97"/><a name="INDEX-98"/>A
+number of common problems are caused by incorrect routing of Internet
+addresses or by the incorrect assignment of addresses. This section
+helps you determine what your addresses are.</p>
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.8.1"/>
+
+<h3 class="head3">Netmasks</h3>
+
+<p>Using the <a name="INDEX-99"/>netmask, it is possible to
+determine which addresses can be reached directly (i.e., which are on
+the local network) and which addresses require forwarding packets
+through a router. If the netmask is wrong, the systems will make one
+of two mistakes. One is to route local packets via a router, which is
+an expensive waste of time&mdash;it might work reasonably fast, it
+might run slowly, or it might fail utterly. The second mistake is to
+fail to send packets from a remote system to the router, which will
+prevent them from being forwarded to the remote system.</p>
+
+<p>The netmask is a number like an IP address, with one-bits for the
+network part of an address and zero-bits for the host portion. It is
+used as a bitmask to mask off parts of the address inside the TCP/IP
+code. If the mask is 255.255.0.0, the first 2 bytes are the network
+part and the last 2 are the host part. More common is 255.255.255.0,
+in which the first 3 bytes are the network part and the last one is
+the host part.</p>
+
+<p>For example, let's say your IP address is
+192.168.0.10 and the Samba server is 192.168.236.86. If your netmask
+happens to be 255.255.255.0, the network part of the address is the
+first 3 bytes, and the host part is the last byte. In this case, the
+network parts are different, and the systems are on different
+networks:</p>
+
+<a name="ch12-37-fm2xml"/><table border="1">
+
+
+
+<tr>
+<th>
+<p>Network part</p>
+</th>
+<th>
+<p>Host part</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>192 168 000</p>
+</td>
+<td>
+<p>10</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>192 168 235</p>
+</td>
+<td>
+<p>86</p>
+</td>
+</tr>
+
+</table>
+
+<p>If your netmask happens to be 255.255.0.0, the network part is just
+the first 2 bytes. In this case, the network parts match, and so the
+two systems are on the same network:</p>
+
+<a name="ch12-38-fm2xml"/><table border="1">
+
+
+
+<tr>
+<th>
+<p>Network part</p>
+</th>
+<th>
+<p>Host part</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>192 168</p>
+</td>
+<td>
+<p>000 10</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>192 168</p>
+</td>
+<td>
+<p>236 86</p>
+</td>
+</tr>
+
+</table>
+
+<p>Make sure the netmask in use on each system matches the structure of
+your network. On every subnet, the netmask should be identical on
+each system.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.8.2"/>
+
+<h3 class="head3">Broadcast addresses</h3>
+
+<p>The <a name="INDEX-100"/>broadcast address is a normal address,
+with the hosts part all one-bits. It means &quot;all
+hosts on your network.&quot; You can compute it easily
+from your netmask and address: take the address and put one-bits in
+it for all the bits that are zero at the end of the netmask (the host
+part). The following table illustrates this:</p>
+
+<a name="ch12-39-fm2xml"/><table border="1">
+
+
+
+
+<tr>
+<th>
+</th>
+<th>
+<p>Network part</p>
+</th>
+<th>
+<p>Host part</p>
+</th>
+</tr>
+
+
+<tr>
+<td>
+<p>IP address</p>
+</td>
+<td>
+<p>192 168 236</p>
+</td>
+<td>
+<p>86</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Netmask</p>
+</td>
+<td>
+<p>255 255 255</p>
+</td>
+<td>
+<p>000</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Broadcast</p>
+</td>
+<td>
+<p>192 168 236</p>
+</td>
+<td>
+<p>255</p>
+</td>
+</tr>
+
+</table>
+
+<p>In this example, the broadcast address on the 192.168.236 network is
+192.168.236.255. There is also an old
+&quot;universal&quot; broadcast address,
+255.255.255.255. Routers are prohibited from forwarding these, but
+most systems on your local network will respond to broadcasts to this
+address.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.8.3"/>
+
+<h3 class="head3">Network address ranges</h3>
+
+<p>A <a name="INDEX-101"/>number of address ranges have been
+reserved for testing and for nonconnected networks; we use these for
+the examples in this book. If you don't have an
+address yet, feel free to use one of these to start. They include one
+class A network, 10.*.*.*, a range of class B network addresses,
+172.16.*.* through 172.31.*.*, and 254 class C networks, 192.168.1.*
+through 192.168.254.*. The domain <tt class="literal">example.com</tt> is
+also reserved for unconnected networks, explanatory examples, and
+books.</p>
+
+<p>If you're actually connecting to the Internet,
+you'll need to get an appropriate IP address and a
+domain name, probably through the same company that provides your
+connection.</p>
+
+
+</div>
+
+
+
+<div class="sect3"><a name="samba2-CHP-12-SECT-2.8.4"/>
+
+<h3 class="head3">Finding your network address</h3>
+
+<p><a name="INDEX-102"/>If you
+haven't recorded your IP address, you can learn it
+through the <em class="emphasis">ifconfig</em><a name="INDEX-103"/> command on Unix or the
+<em class="emphasis">ipconfig</em> <a name="INDEX-104"/>command on Windows. (Check your manual
+pages for any options required by your brand of Unix. For example,
+<tt class="literal">ifconfig</tt> <tt class="literal">-a</tt> works on Solaris.)
+You should see output similar to the following:</p>
+
+<blockquote><pre class="code">$ <tt class="userinput"><b>ifconfig -a</b></tt> 
+le0: flags=63&lt;UP,BROADCAST,NOTRAILERS,RUNNING &gt; 
+      inet 192.168.236.11 netmask ffffff00 broadcast 192.168.236.255 
+lo0: flags=49&lt;&amp;lt&gt;UP,LOOPBACK,RUNNING&lt;&amp;gt&gt;         
+      inet 127.0.0.1 netmask ff000000</pre></blockquote>
+
+<p>One of the interfaces will be loopback (in our examples,
+<tt class="literal">lo0</tt>), and the other will be the regular IP
+interface. The flags should show that the interface is running, and
+Ethernet interfaces will also say they support broadcasts (PPP
+interfaces don't). The other places to look for IP
+addresses are <em class="filename">/etc/hosts</em> files, Windows
+<em class="emphasis">HOSTS</em> files, Windows
+<em class="emphasis">LMHOSTS</em> files, NIS, NIS+, and DNS. <a name="INDEX-105"/><a name="INDEX-106"/></p>
+
+
+</div>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-2.9"/>
+
+<h3 class="head2">Troubleshooting NetBIOS Names</h3>
+
+<p><a name="INDEX-107"/><a name="INDEX-108"/>Historically, SMB protocols have
+depended on the NetBIOS name system, also called the LAN Manager name
+system. This was a simple scheme where each system had a unique
+20-character name and broadcast it on the LAN for everyone to know.
+With TCP/IP, we tend to use names such as
+<tt class="literal">client.example.com</tt>, stored in
+<em class="filename">/etc/hosts</em> files through DNS or WINS.</p>
+
+<p>The usual mapping of domain names such as
+<tt class="literal">server.example.com</tt> to NetBIOS names simply uses
+the <tt class="literal">server</tt> part as the NetBIOS name and converts
+it to uppercase. Alas, this doesn't always work,
+especially if you have a system with a 21-character name; not
+everyone uses the same NetBIOS and DNS names. For example,
+<tt class="literal">corpvm1</tt> along with <tt class="literal">vm1.corp.com</tt>
+is not unusual.</p>
+
+<p>A system with a different NetBIOS name and domain name is confusing
+when you're troubleshooting; we recommend that you
+try to avoid this wherever possible. NetBIOS names are discoverable
+with <em class="emphasis">smbclient</em> :</p>
+
+<ul><li>
+<p>If you can list shares on your Samba server with
+<tt class="literal">smbclient</tt> <tt class="literal">-L</tt>
+<tt class="literal">short_name</tt>, the short name is the NetBIOS name.</p>
+</li><li>
+<p>If you get <tt class="literal">Get_Hostbyname</tt>:
+<tt class="literal">Unknown</tt> <tt class="literal">host</tt>
+<tt class="literal">name</tt>, there is probably a mismatch. Check in the
+<em class="filename">smb.conf</em> file to see if the NetBIOS name is
+explicitly set.</p>
+</li><li>
+<p>Try to list shares again, specifying <tt class="literal">-I</tt> and the IP
+address of the Samba server (e.g., <tt class="literal">smbclient</tt>
+<tt class="literal">-L</tt> <tt class="literal">server</tt> <tt class="literal">-I</tt>
+<tt class="literal">192.168.236.86</tt>). This overrides the name lookup
+and forces the packets to go to the IP address. If this works, there
+was a mismatch.</p>
+</li><li>
+<p>Try with <tt class="literal">-I</tt> and the full domain name of the server
+(e.g., <tt class="literal">smbclient</tt> <tt class="literal">-L</tt>
+<tt class="literal">server</tt> <tt class="literal">-I</tt>
+<tt class="literal">server.example.com</tt>). This tests the lookup of the
+domain name, using whatever scheme the Samba server uses (e.g., DNS).
+If it fails, you have a name service problem. You should reread the
+earlier section, <a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>,
+after you finish troubleshooting the NetBIOS names.</p>
+</li><li>
+<p>Try with the <tt class="literal">-n</tt> (NetBIOS name) option, giving it
+the name you expect to work (e.g., <tt class="literal">smbclient</tt>
+<tt class="literal">-n</tt> <tt class="literal">server</tt> <tt class="literal">-L</tt>
+<tt class="literal">server-12</tt>), but without overriding the IP address
+through <tt class="literal">-I</tt>. If this works, the name you specified
+with <tt class="literal">-n</tt> is the actual NetBIOS name of the server.
+If you receive <tt class="literal">Get-Hostbyname</tt>:
+<tt class="literal">Unknown</tt> <tt class="literal">host</tt>
+<tt class="literal">SERVER</tt>, it's not the right server
+yet.</p>
+</li><li>
+<p>If nothing is working so far, repeat the tests specifying
+<tt class="literal">-U</tt> <em class="emphasis">username</em> and
+<tt class="literal">-W</tt> <em class="emphasis">workgroup</em>, with the
+username and workgroup in uppercase, to make sure
+you're not being derailed by a user or workgroup
+mismatch.</p>
+</li><li>
+<p>If still nothing works and you had evidence of a name service
+problem, troubleshoot the name service (see the earlier section,
+<a href="ch12.html#samba2-CHP-12-SECT-2.7">Section 12.2.7</a>) and then return to
+the NetBIOS name service. <a name="INDEX-109"/><a name="INDEX-110"/></p>
+</li></ul>
+
+</div>
+
+
+</div>
+
+
+
+<div class="sect1"><a name="samba2-CHP-12-SECT-3"/>
+
+<h2 class="head1">Extra Resources</h2>
+
+<p>At some point during your work with Samba, you'll
+want to turn to online or printed resources for news, updates, and
+aid.</p>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-3.1"/>
+
+<h3 class="head2">Documentation and FAQs</h3>
+
+<p>It's OK to read the <a name="INDEX-111"/><a name="INDEX-112"/>documentation. Really. Nobody can see you,
+and we won't tell. In fact, Samba ships with a large
+set of documentation files, and it is well worth the effort to at
+least browse through them, either in the distribution directory on
+your computer under <em class="filename">/docs</em> or online at the Samba
+web site: <a href="http://www.samba.org">http://www.samba.org</a>. The most current
+FAQ list, bug information, and distribution locations are located at
+the web site, with links to all the Samba manual pages and HOWTOs.</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-3.2"/>
+
+<h3 class="head2">Samba Newsgroups</h3>
+
+<p><a name="INDEX-113"/>Usenet
+newsgroups have always been a great place to get advice on just about
+any topic. In the past few years, though, this vast pool of knowledge
+has developed something that has made it into an invaluable resource:
+a memory. Archival and search sites such as the one at
+<a name="INDEX-114"/>Google (<a href="http://groups.google.com/advanced_group_search">http://groups.google.com/advanced_group_search</a>)
+have made sifting through years of valuable solutions as simple as a
+few mouse clicks.</p>
+
+<p>The primary newsgroup for Samba is
+<em class="emphasis">comp.protocols.smb</em><a name="INDEX-115"/>. This should always be your first
+stop when there's a problem. More often than not,
+spending 5 minutes researching an error here will save hours of
+frustration while trying to debug something yourself.</p>
+
+<p>When searching a newsgroup, try to be as specific as possible, but
+not too wordy. Searching on actual error messages is best. If you
+don't find an answer immediately in the newsgroup,
+resist the temptation to post a request for help until
+you've done a bit more work on the problem. You
+might find that the answer is in a FAQ or one of the many
+documentation files that ship with Samba, or a solution might become
+evident when you run one of Samba's diagnostic
+tools. If nothing works, post a request in
+<em class="emphasis">comp.protocols.smb</em>, and be as specific as
+possible about what you have tried and what you are seeing. Include
+any error messages that appear. It might be days before you receive
+help, so be patient and keep trying things while you wait.</p>
+
+<a name="samba2-CHP-12-NOTE-161"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
+<p>Once you post a request for help, keep poking at the problem
+yourself. Most of us have had the experience of posting a Usenet
+article containing hundreds of lines of intricate detail, only to
+solve the problem an hour later after the article has blazed its way
+across several continents. The rule of thumb goes something like
+this: the more folks who have read your request, the simpler the
+solution. Usually this means that once everyone in the Unix community
+has seen your article, the solution will be something simple such as,
+&quot;Plug the power cord into the wall
+socket.&quot;</p>
+</blockquote>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-3.3"/>
+
+<h3 class="head2">Samba Mailing Lists</h3>
+
+<p>The following are <a name="INDEX-116"/>mailing lists for support with Samba. See
+the Samba home page, <a href="http://www.samba.org/">http://www.samba.org/</a>, for
+information on subscribing and unsubscribing to these mailing lists:</p>
+
+<dl>
+<dt><b>samba@samba.org</b></dt>
+<dd>
+<p>This is the primary mailing list for general questions and discussion
+regarding Samba.</p>
+</dd>
+
+
+
+<dt><b>samba-announce@samba.org</b></dt>
+<dd>
+<p>This list is for receiving news regarding Samba, such as
+announcements of new releases.</p>
+</dd>
+
+
+
+<dt><b>samba-cvs@samba.org</b></dt>
+<dd>
+<p>By subscribing to this list, you can automatically receive a message
+every time one of the Samba developers updates the Samba source code
+in the CVS repository. You might want to do this if you are waiting
+for a specific bug fix or feature to be applied. To avoid congesting
+your email inbox, we suggest using the digest feature, which
+consolidates messages into a smaller number of emails.</p>
+</dd>
+
+
+
+<dt><b>samba-docs@samba.org</b></dt>
+<dd>
+<p>This list is for discussing Samba documentation.</p>
+</dd>
+
+
+
+<dt><b>samba-vms@samba.org</b></dt>
+<dd>
+<p>This mailing list is for people who are running Samba on the VMS
+operating system.</p>
+</dd>
+
+
+
+<dt><b>samba-binaries@samba.org</b></dt>
+<dd>
+<p>This is a list for developers to use when discussing precompiled
+Samba distributions.</p>
+</dd>
+
+
+
+<dt><b>samba-technical@samba.org</b></dt>
+<dd>
+<p>This mailing list is for developer discussion of the Samba code.</p>
+</dd>
+
+</dl>
+
+<p>Searchable versions of the Samba mailing list archives can be found
+at <a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>.</p>
+
+<p>When posting messages to the Samba mailing lists, keep in mind that
+you are sending your message to a large audience. The notes in the
+previous section regarding Usenet postings also apply here. A
+well-formulated question or comment is more likely to be answered,
+and a poorly conceived message is <em class="emphasis">very</em> likely to
+be ignored!</p>
+
+
+</div>
+
+
+<div class="sect2"><a name="samba2-CHP-12-SECT-3.4"/>
+
+<h3 class="head2">Further Reading</h3>
+
+<ol><li>
+<p>Hunt, Craig. <em class="emphasis">TCP/IP Network Administration</em>,
+Third Edition. Sebastopol, CA: O'Reilly
+&amp; Associates, 1997.</p>
+</li>
+<li>
+<p>Hunt, Craig, and Robert Bruce Thompson. <em class="emphasis">Windows NT TCP/IP
+Network Administration</em>. Sebastopol, CA:
+O'Reilly &amp; Associates, 1998.</p>
+</li>
+<li>
+<p>Albitz, Paul, and Cricket Liu. <em class="emphasis">DNS and Bind</em>,
+Fourth Edition. Sebastopol, CA: O'Reilly
+&amp; Associates, 1998.</p>
+</li>
+<li>
+<p>Stern, Hal. <em class="emphasis">Managing NFS and NIS</em>, Second
+Edition. Sebastopol, CA: O'Reilly &amp; Associates,
+1991.<a name="INDEX-117"/></p>
+</li></ol>
+
+</div>
+
+
+</div>
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4></body></html>
diff --git a/docs/htmldocs/using_samba/figs/sam2_0101.gif b/docs/htmldocs/using_samba/figs/sam2_0101.gif
new file mode 100644
index 0000000000..195326a205
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0101.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0102.gif b/docs/htmldocs/using_samba/figs/sam2_0102.gif
new file mode 100644
index 0000000000..e453dbf023
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0102.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0103.gif b/docs/htmldocs/using_samba/figs/sam2_0103.gif
new file mode 100644
index 0000000000..ed50af69af
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0103.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0104.gif b/docs/htmldocs/using_samba/figs/sam2_0104.gif
new file mode 100644
index 0000000000..e903a0f22e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0104.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0105.gif b/docs/htmldocs/using_samba/figs/sam2_0105.gif
new file mode 100644
index 0000000000..0fec77125d
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0105.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0106.gif b/docs/htmldocs/using_samba/figs/sam2_0106.gif
new file mode 100644
index 0000000000..32cbfdbee4
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0106.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0107.gif b/docs/htmldocs/using_samba/figs/sam2_0107.gif
new file mode 100644
index 0000000000..2d8b8e66b7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0107.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0108.gif b/docs/htmldocs/using_samba/figs/sam2_0108.gif
new file mode 100644
index 0000000000..9d26856e38
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0108.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0109.gif b/docs/htmldocs/using_samba/figs/sam2_0109.gif
new file mode 100644
index 0000000000..2c7db9617a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0109.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0110.gif b/docs/htmldocs/using_samba/figs/sam2_0110.gif
new file mode 100644
index 0000000000..2d7d50a702
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0110.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0111.gif b/docs/htmldocs/using_samba/figs/sam2_0111.gif
new file mode 100644
index 0000000000..f6be700fa5
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0111.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0112.gif b/docs/htmldocs/using_samba/figs/sam2_0112.gif
new file mode 100644
index 0000000000..4eddb82069
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0112.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0113.gif b/docs/htmldocs/using_samba/figs/sam2_0113.gif
new file mode 100644
index 0000000000..1886bbcb5a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0113.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0114.gif b/docs/htmldocs/using_samba/figs/sam2_0114.gif
new file mode 100644
index 0000000000..75cf0a750a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0114.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0201.gif b/docs/htmldocs/using_samba/figs/sam2_0201.gif
new file mode 100644
index 0000000000..7dc140530c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0201.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0202.gif b/docs/htmldocs/using_samba/figs/sam2_0202.gif
new file mode 100644
index 0000000000..ccbaeed4fe
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0202.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0203.gif b/docs/htmldocs/using_samba/figs/sam2_0203.gif
new file mode 100644
index 0000000000..127705fd38
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0203.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0204.gif b/docs/htmldocs/using_samba/figs/sam2_0204.gif
new file mode 100644
index 0000000000..5359423fd5
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0204.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0301.gif b/docs/htmldocs/using_samba/figs/sam2_0301.gif
new file mode 100644
index 0000000000..30759463cf
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0301.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0302.gif b/docs/htmldocs/using_samba/figs/sam2_0302.gif
new file mode 100644
index 0000000000..5576573e83
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0302.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0303.gif b/docs/htmldocs/using_samba/figs/sam2_0303.gif
new file mode 100644
index 0000000000..76b8dd36bb
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0303.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0304.gif b/docs/htmldocs/using_samba/figs/sam2_0304.gif
new file mode 100644
index 0000000000..b309fc9968
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0304.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0305.gif b/docs/htmldocs/using_samba/figs/sam2_0305.gif
new file mode 100644
index 0000000000..5a9fd77443
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0305.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0306.gif b/docs/htmldocs/using_samba/figs/sam2_0306.gif
new file mode 100644
index 0000000000..47b15548f3
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0306.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0307.gif b/docs/htmldocs/using_samba/figs/sam2_0307.gif
new file mode 100644
index 0000000000..7874ccb889
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0307.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0308.gif b/docs/htmldocs/using_samba/figs/sam2_0308.gif
new file mode 100644
index 0000000000..23d4fccd65
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0308.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0309.gif b/docs/htmldocs/using_samba/figs/sam2_0309.gif
new file mode 100644
index 0000000000..2e27a2f407
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0309.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0310.gif b/docs/htmldocs/using_samba/figs/sam2_0310.gif
new file mode 100644
index 0000000000..846b228eff
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0310.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0311.gif b/docs/htmldocs/using_samba/figs/sam2_0311.gif
new file mode 100644
index 0000000000..acb82fa77b
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0311.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0312.gif b/docs/htmldocs/using_samba/figs/sam2_0312.gif
new file mode 100644
index 0000000000..2a96425312
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0312.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0313.gif b/docs/htmldocs/using_samba/figs/sam2_0313.gif
new file mode 100644
index 0000000000..4482a8b27b
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0313.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0314.gif b/docs/htmldocs/using_samba/figs/sam2_0314.gif
new file mode 100644
index 0000000000..02b8bcd2c7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0314.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0315.gif b/docs/htmldocs/using_samba/figs/sam2_0315.gif
new file mode 100644
index 0000000000..bd747a23a9
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0315.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0316.gif b/docs/htmldocs/using_samba/figs/sam2_0316.gif
new file mode 100644
index 0000000000..a12e20e8b4
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0316.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0317.gif b/docs/htmldocs/using_samba/figs/sam2_0317.gif
new file mode 100644
index 0000000000..1957fc09e6
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0317.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0318.gif b/docs/htmldocs/using_samba/figs/sam2_0318.gif
new file mode 100644
index 0000000000..2c90ee6523
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0318.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0319.gif b/docs/htmldocs/using_samba/figs/sam2_0319.gif
new file mode 100644
index 0000000000..ceb8041299
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0319.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0320.gif b/docs/htmldocs/using_samba/figs/sam2_0320.gif
new file mode 100644
index 0000000000..766c0ec4ba
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0320.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0321.gif b/docs/htmldocs/using_samba/figs/sam2_0321.gif
new file mode 100644
index 0000000000..b1dac33f23
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0321.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0322.gif b/docs/htmldocs/using_samba/figs/sam2_0322.gif
new file mode 100644
index 0000000000..fa0c2a3ed2
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0322.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0323.gif b/docs/htmldocs/using_samba/figs/sam2_0323.gif
new file mode 100644
index 0000000000..9678a4b0da
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0323.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0324.gif b/docs/htmldocs/using_samba/figs/sam2_0324.gif
new file mode 100644
index 0000000000..f1fd719fc2
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0324.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0325.gif b/docs/htmldocs/using_samba/figs/sam2_0325.gif
new file mode 100644
index 0000000000..3887d36b94
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0325.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0326.gif b/docs/htmldocs/using_samba/figs/sam2_0326.gif
new file mode 100644
index 0000000000..26047eb48e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0326.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0327.gif b/docs/htmldocs/using_samba/figs/sam2_0327.gif
new file mode 100644
index 0000000000..f8b661bce8
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0327.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0328.gif b/docs/htmldocs/using_samba/figs/sam2_0328.gif
new file mode 100644
index 0000000000..9f767a156e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0328.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0329.gif b/docs/htmldocs/using_samba/figs/sam2_0329.gif
new file mode 100644
index 0000000000..4cfa231e86
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0329.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0330.gif b/docs/htmldocs/using_samba/figs/sam2_0330.gif
new file mode 100644
index 0000000000..4c90f3b8c7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0330.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0331.gif b/docs/htmldocs/using_samba/figs/sam2_0331.gif
new file mode 100644
index 0000000000..bc1fc19721
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0331.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0332.gif b/docs/htmldocs/using_samba/figs/sam2_0332.gif
new file mode 100644
index 0000000000..a507e19018
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0332.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0333.gif b/docs/htmldocs/using_samba/figs/sam2_0333.gif
new file mode 100644
index 0000000000..6b1b2a7dd5
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0333.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0334.gif b/docs/htmldocs/using_samba/figs/sam2_0334.gif
new file mode 100644
index 0000000000..ff408ecd6c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0334.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0335.gif b/docs/htmldocs/using_samba/figs/sam2_0335.gif
new file mode 100644
index 0000000000..fdf01219e1
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0335.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0336.gif b/docs/htmldocs/using_samba/figs/sam2_0336.gif
new file mode 100644
index 0000000000..a44851c340
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0336.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0337.gif b/docs/htmldocs/using_samba/figs/sam2_0337.gif
new file mode 100644
index 0000000000..219afbd147
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0337.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0338.gif b/docs/htmldocs/using_samba/figs/sam2_0338.gif
new file mode 100644
index 0000000000..8f1ba6e36f
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0338.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0339.gif b/docs/htmldocs/using_samba/figs/sam2_0339.gif
new file mode 100644
index 0000000000..f42c1b57ec
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0339.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0340.gif b/docs/htmldocs/using_samba/figs/sam2_0340.gif
new file mode 100644
index 0000000000..76c5a1b347
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0340.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0341.gif b/docs/htmldocs/using_samba/figs/sam2_0341.gif
new file mode 100644
index 0000000000..634b847d04
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0341.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0342.gif b/docs/htmldocs/using_samba/figs/sam2_0342.gif
new file mode 100644
index 0000000000..51284782a3
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0342.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0343.gif b/docs/htmldocs/using_samba/figs/sam2_0343.gif
new file mode 100644
index 0000000000..0618a841cf
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0343.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0344.gif b/docs/htmldocs/using_samba/figs/sam2_0344.gif
new file mode 100644
index 0000000000..7d40dbcdf1
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0344.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0345.gif b/docs/htmldocs/using_samba/figs/sam2_0345.gif
new file mode 100644
index 0000000000..0b36aa6da3
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0345.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0346.gif b/docs/htmldocs/using_samba/figs/sam2_0346.gif
new file mode 100644
index 0000000000..36c3999ad1
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0346.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0347.gif b/docs/htmldocs/using_samba/figs/sam2_0347.gif
new file mode 100644
index 0000000000..db6c3e10ce
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0347.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0348.gif b/docs/htmldocs/using_samba/figs/sam2_0348.gif
new file mode 100644
index 0000000000..16457a3421
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0348.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0349.gif b/docs/htmldocs/using_samba/figs/sam2_0349.gif
new file mode 100644
index 0000000000..6445cdd3bc
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0349.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0350.gif b/docs/htmldocs/using_samba/figs/sam2_0350.gif
new file mode 100644
index 0000000000..08ee35b8e7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0350.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0351.gif b/docs/htmldocs/using_samba/figs/sam2_0351.gif
new file mode 100644
index 0000000000..b30b603818
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0351.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0352.gif b/docs/htmldocs/using_samba/figs/sam2_0352.gif
new file mode 100644
index 0000000000..bfab1e0031
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0352.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0353.gif b/docs/htmldocs/using_samba/figs/sam2_0353.gif
new file mode 100644
index 0000000000..4c1e84f37e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0353.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0354.gif b/docs/htmldocs/using_samba/figs/sam2_0354.gif
new file mode 100644
index 0000000000..3519397705
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0354.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0355.gif b/docs/htmldocs/using_samba/figs/sam2_0355.gif
new file mode 100644
index 0000000000..8559956df8
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0355.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0356.gif b/docs/htmldocs/using_samba/figs/sam2_0356.gif
new file mode 100644
index 0000000000..9cffddf4b2
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0356.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0357.gif b/docs/htmldocs/using_samba/figs/sam2_0357.gif
new file mode 100644
index 0000000000..f1a7043858
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0357.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0358.gif b/docs/htmldocs/using_samba/figs/sam2_0358.gif
new file mode 100644
index 0000000000..58073c2d19
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0358.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0359.gif b/docs/htmldocs/using_samba/figs/sam2_0359.gif
new file mode 100644
index 0000000000..1fe90edca6
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0359.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0360.gif b/docs/htmldocs/using_samba/figs/sam2_0360.gif
new file mode 100644
index 0000000000..c306296f08
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0360.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0361.gif b/docs/htmldocs/using_samba/figs/sam2_0361.gif
new file mode 100644
index 0000000000..7b6cc3c878
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0361.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0401.gif b/docs/htmldocs/using_samba/figs/sam2_0401.gif
new file mode 100644
index 0000000000..68c4ec949e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0401.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0402.gif b/docs/htmldocs/using_samba/figs/sam2_0402.gif
new file mode 100644
index 0000000000..817622adee
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0402.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0403.gif b/docs/htmldocs/using_samba/figs/sam2_0403.gif
new file mode 100644
index 0000000000..8d2bf580e6
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0403.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0404.gif b/docs/htmldocs/using_samba/figs/sam2_0404.gif
new file mode 100644
index 0000000000..5f93a6715c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0404.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0405.gif b/docs/htmldocs/using_samba/figs/sam2_0405.gif
new file mode 100644
index 0000000000..67925c1db5
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0405.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0406.gif b/docs/htmldocs/using_samba/figs/sam2_0406.gif
new file mode 100644
index 0000000000..f6b3924711
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0406.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0407.gif b/docs/htmldocs/using_samba/figs/sam2_0407.gif
new file mode 100644
index 0000000000..486a629e9e
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0407.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0408.gif b/docs/htmldocs/using_samba/figs/sam2_0408.gif
new file mode 100644
index 0000000000..dbc31bb54d
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0408.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0409.gif b/docs/htmldocs/using_samba/figs/sam2_0409.gif
new file mode 100644
index 0000000000..b9d31f2a4d
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0409.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0410.gif b/docs/htmldocs/using_samba/figs/sam2_0410.gif
new file mode 100644
index 0000000000..83e4c9cb89
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0410.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0411.gif b/docs/htmldocs/using_samba/figs/sam2_0411.gif
new file mode 100644
index 0000000000..c6684d625c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0411.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0412.gif b/docs/htmldocs/using_samba/figs/sam2_0412.gif
new file mode 100644
index 0000000000..4706a99f51
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0412.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0413.gif b/docs/htmldocs/using_samba/figs/sam2_0413.gif
new file mode 100644
index 0000000000..71bf8690f8
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0413.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0414.gif b/docs/htmldocs/using_samba/figs/sam2_0414.gif
new file mode 100644
index 0000000000..2056eb45bb
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0414.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0415.gif b/docs/htmldocs/using_samba/figs/sam2_0415.gif
new file mode 100644
index 0000000000..0c8eb01774
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0415.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0416.gif b/docs/htmldocs/using_samba/figs/sam2_0416.gif
new file mode 100644
index 0000000000..c2b2fecf3d
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0416.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0417.gif b/docs/htmldocs/using_samba/figs/sam2_0417.gif
new file mode 100644
index 0000000000..a84d217c1f
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0417.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0501.gif b/docs/htmldocs/using_samba/figs/sam2_0501.gif
new file mode 100644
index 0000000000..eda8e934d7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0501.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0502.gif b/docs/htmldocs/using_samba/figs/sam2_0502.gif
new file mode 100644
index 0000000000..1f996e1b63
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0502.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0503.gif b/docs/htmldocs/using_samba/figs/sam2_0503.gif
new file mode 100644
index 0000000000..0d7e3654ec
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0503.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0504.gif b/docs/htmldocs/using_samba/figs/sam2_0504.gif
new file mode 100644
index 0000000000..9c60c26ef5
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0504.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0505.gif b/docs/htmldocs/using_samba/figs/sam2_0505.gif
new file mode 100644
index 0000000000..346409e3e6
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0505.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0506.gif b/docs/htmldocs/using_samba/figs/sam2_0506.gif
new file mode 100644
index 0000000000..78f5d54da2
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0506.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0507.gif b/docs/htmldocs/using_samba/figs/sam2_0507.gif
new file mode 100644
index 0000000000..e6ff6f14bd
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0507.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0508.gif b/docs/htmldocs/using_samba/figs/sam2_0508.gif
new file mode 100644
index 0000000000..28dcb6227a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0508.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0601.gif b/docs/htmldocs/using_samba/figs/sam2_0601.gif
new file mode 100644
index 0000000000..006fa95580
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0601.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0602.gif b/docs/htmldocs/using_samba/figs/sam2_0602.gif
new file mode 100644
index 0000000000..598a7015dc
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0602.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0603.gif b/docs/htmldocs/using_samba/figs/sam2_0603.gif
new file mode 100644
index 0000000000..62a8054c6f
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0603.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0604.gif b/docs/htmldocs/using_samba/figs/sam2_0604.gif
new file mode 100644
index 0000000000..9327385eed
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0604.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0605.gif b/docs/htmldocs/using_samba/figs/sam2_0605.gif
new file mode 100644
index 0000000000..236badf15f
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0605.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0701.gif b/docs/htmldocs/using_samba/figs/sam2_0701.gif
new file mode 100644
index 0000000000..b0b16d458c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0701.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0801.gif b/docs/htmldocs/using_samba/figs/sam2_0801.gif
new file mode 100644
index 0000000000..5f9d87b206
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0801.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0802.gif b/docs/htmldocs/using_samba/figs/sam2_0802.gif
new file mode 100644
index 0000000000..fde794c19a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0802.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0803.gif b/docs/htmldocs/using_samba/figs/sam2_0803.gif
new file mode 100644
index 0000000000..13baa02ed4
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0803.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0804.gif b/docs/htmldocs/using_samba/figs/sam2_0804.gif
new file mode 100644
index 0000000000..fc42ebf685
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0804.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0805.gif b/docs/htmldocs/using_samba/figs/sam2_0805.gif
new file mode 100644
index 0000000000..015ca5df19
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0805.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0806.gif b/docs/htmldocs/using_samba/figs/sam2_0806.gif
new file mode 100644
index 0000000000..f11b8a18c9
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0806.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0807.gif b/docs/htmldocs/using_samba/figs/sam2_0807.gif
new file mode 100644
index 0000000000..1ffc3eac39
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0807.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0808.gif b/docs/htmldocs/using_samba/figs/sam2_0808.gif
new file mode 100644
index 0000000000..36839a754c
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0808.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0809.gif b/docs/htmldocs/using_samba/figs/sam2_0809.gif
new file mode 100644
index 0000000000..3145d367ce
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0809.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0810.gif b/docs/htmldocs/using_samba/figs/sam2_0810.gif
new file mode 100644
index 0000000000..cd76217d1f
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0810.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0811.gif b/docs/htmldocs/using_samba/figs/sam2_0811.gif
new file mode 100644
index 0000000000..e7add2a0e7
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0811.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0901.gif b/docs/htmldocs/using_samba/figs/sam2_0901.gif
new file mode 100644
index 0000000000..6ac1e9c966
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0901.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0902.gif b/docs/htmldocs/using_samba/figs/sam2_0902.gif
new file mode 100644
index 0000000000..f30bd1037d
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0902.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_0903.gif b/docs/htmldocs/using_samba/figs/sam2_0903.gif
new file mode 100644
index 0000000000..0a073278dd
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_0903.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1001.gif b/docs/htmldocs/using_samba/figs/sam2_1001.gif
new file mode 100644
index 0000000000..491cbaf8eb
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1001.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1002.gif b/docs/htmldocs/using_samba/figs/sam2_1002.gif
new file mode 100644
index 0000000000..2b3177c433
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1002.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1003.gif b/docs/htmldocs/using_samba/figs/sam2_1003.gif
new file mode 100644
index 0000000000..39077e86ad
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1003.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1004.gif b/docs/htmldocs/using_samba/figs/sam2_1004.gif
new file mode 100644
index 0000000000..9e81522a65
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1004.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1005.gif b/docs/htmldocs/using_samba/figs/sam2_1005.gif
new file mode 100644
index 0000000000..5d9fe6f72a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1005.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1006.gif b/docs/htmldocs/using_samba/figs/sam2_1006.gif
new file mode 100644
index 0000000000..34fcb1054b
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1006.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1101.gif b/docs/htmldocs/using_samba/figs/sam2_1101.gif
new file mode 100644
index 0000000000..0a8afebd6a
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1101.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_1102.gif b/docs/htmldocs/using_samba/figs/sam2_1102.gif
new file mode 100644
index 0000000000..5bfc6b5521
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_1102.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af01.gif b/docs/htmldocs/using_samba/figs/sam2_af01.gif
new file mode 100644
index 0000000000..290cc7f491
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af01.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af02.gif b/docs/htmldocs/using_samba/figs/sam2_af02.gif
new file mode 100644
index 0000000000..2bc59dab69
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af02.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af03.gif b/docs/htmldocs/using_samba/figs/sam2_af03.gif
new file mode 100644
index 0000000000..5bff6142f8
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af03.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af04.gif b/docs/htmldocs/using_samba/figs/sam2_af04.gif
new file mode 100644
index 0000000000..f1ee885f32
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af04.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af05.gif b/docs/htmldocs/using_samba/figs/sam2_af05.gif
new file mode 100644
index 0000000000..ef15448708
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af05.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af06.gif b/docs/htmldocs/using_samba/figs/sam2_af06.gif
new file mode 100644
index 0000000000..756a6b1c99
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af06.gif
diff --git a/docs/htmldocs/using_samba/figs/sam2_af07.gif b/docs/htmldocs/using_samba/figs/sam2_af07.gif
new file mode 100644
index 0000000000..dfe2199484
--- /dev/null
+++ b/docs/htmldocs/using_samba/figs/sam2_af07.gif
diff --git a/docs/htmldocs/using_samba/inx.html b/docs/htmldocs/using_samba/inx.html
new file mode 100644
index 0000000000..cc01eeb56c
--- /dev/null
+++ b/docs/htmldocs/using_samba/inx.html
@@ -0,0 +1,1814 @@
+<html>
+<body bgcolor="#ffffff">
+
+<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
+hspace="10" align="left" />
+
+<h2>Index</h2>
+
+<A HREF="#Symbols">[&nbsp;Symbols&nbsp;]</A>, 
+<A HREF="#Numbers">[&nbsp;Numbers&nbsp;]</A>, 
+<A HREF="#A">[&nbsp;A&nbsp;]</A>, 
+<A HREF="#B">[&nbsp;B&nbsp;]</A>, 
+<A HREF="#C">[&nbsp;C&nbsp;]</A>, 
+<A HREF="#D">[&nbsp;D&nbsp;]</A>, 
+<A HREF="#E">[&nbsp;E&nbsp;]</A>, 
+<A HREF="#F">[&nbsp;F&nbsp;]</A>, 
+<A HREF="#G">[&nbsp;G&nbsp;]</A>, 
+<A HREF="#H">[&nbsp;H&nbsp;]</A>, 
+<A HREF="#I">[&nbsp;I&nbsp;]</A>, 
+<A HREF="#K">[&nbsp;K&nbsp;]</A>, 
+<A HREF="#L">[&nbsp;L&nbsp;]</A>, 
+<A HREF="#M">[&nbsp;M&nbsp;]</A>, 
+<A HREF="#N">[&nbsp;N&nbsp;]</A>, 
+<A HREF="#O">[&nbsp;O&nbsp;]</A>, 
+<A HREF="#P">[&nbsp;P&nbsp;]</A>, 
+<A HREF="#Q">[&nbsp;Q&nbsp;]</A>, 
+<A HREF="#R">[&nbsp;R&nbsp;]</A>, 
+<A HREF="#S">[&nbsp;S&nbsp;]</A>, 
+<A HREF="#T">[&nbsp;T&nbsp;]</A>, 
+<A HREF="#U">[&nbsp;U&nbsp;]</A>, 
+<A HREF="#V">[&nbsp;V&nbsp;]</A>, 
+<A HREF="#W">[&nbsp;W&nbsp;]</A>, 
+<A HREF="#X">[&nbsp;X&nbsp;]</A> 
+
+
+<P><A NAME="Symbols"><B>Symbols</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>_ _MSBROWSE _ _ resource entry, 16, 229
+<BR>. (period)
+<BR> &nbsp; &nbsp; &nbsp;   NetBIOS names and, 14
+<BR> &nbsp; &nbsp; &nbsp;   (see also dot files)
+<BR>%$ variable, 192
+<P><A NAME="Numbers"><B>Numbers</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>127.0.0.1 (localhost), 73
+<BR> &nbsp; &nbsp; &nbsp;   bind interfaces only option, 208
+<P><A NAME="A"><B>A</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%a variable, 143, 192
+<BR> &nbsp; &nbsp; &nbsp;   variable substitution, 191
+<BR>abort shutdown script option (smb.conf file), 401
+<BR>Access Control Entries (ACEs), 31, 253
+<BR>Access Control Lists (see ACLs)
+<BR>access control options, 287-288
+<BR>access, controlling (see ACLs; controlling access to shares)
+<BR>accounts (see computer accounts, adding; users)
+<BR>ACLs, 30
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 260-262
+<BR> &nbsp; &nbsp; &nbsp;   inheriting, 416
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 495
+<BR> &nbsp; &nbsp; &nbsp;   mapping to Unix permissions, 426
+<BR> &nbsp; &nbsp; &nbsp;   POSIX.1e, 259
+<BR> &nbsp; &nbsp; &nbsp;   support in Samba 2.2, 37
+<BR> &nbsp; &nbsp; &nbsp;   Unix, 259
+<BR> &nbsp; &nbsp; &nbsp;   versus Unix file permissions, 31
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT/2000/XP, 165, 253-262
+<BR>Active Directory
+<BR> &nbsp; &nbsp; &nbsp;   Samba 2.2, 34, 121
+<BR> &nbsp; &nbsp; &nbsp;   Samba 3.0, 34
+<BR> &nbsp; &nbsp; &nbsp;   server, specifying, 402
+<BR> &nbsp; &nbsp; &nbsp;   time synchronization and, 340
+<BR>adapters, 69
+<BR>add machine script option (smb.conf file), 402
+<BR>add printer command option (smb.conf file), 401
+<BR>add share command option (smb.conf file), 402
+<BR>add user script option (smb.conf file), 159, 402
+<BR>admin users option (smb.conf file), 285, 287, 402
+<BR>admin users (see root accounts)
+<BR>administrator (see domain administrator)
+<BR>ads server option (smb.conf file), 402
+<BR>AFS (Andrew Filesystem), installing Samba with support for, 495
+<BR>Albitz, Paul, 383
+<BR>algorithmic rid base option (smb.conf file), 402
+<BR>allow hosts option (smb.conf file), 403
+<BR>allow trusted domains option (smb.conf file), 403
+<BR>analogX Atomic TimeSync, 340
+<BR>announce as option (smb.conf file), 234, 403
+<BR>announce version option (smb.conf file), 235, 403
+<BR>anonymous
+<BR> &nbsp; &nbsp; &nbsp;   restricting access, 434
+<BR> &nbsp; &nbsp; &nbsp;   (see also guest access)
+<BR>ANSI C compiler required by Samba source, 44
+<BR>auth methods option (smb.conf file), 403
+<BR>authentication
+<BR> &nbsp; &nbsp; &nbsp;   client, 290-296
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting method of, 436
+<BR> &nbsp; &nbsp; &nbsp;   defined, 30
+<BR> &nbsp; &nbsp; &nbsp;   enabling Samba as WINS server, configuration file example, 395
+<BR> &nbsp; &nbsp; &nbsp;   files, specifying where Samba keeps, 497
+<BR> &nbsp; &nbsp; &nbsp;   methods, specifying, 403
+<BR> &nbsp; &nbsp; &nbsp;   overview, 31
+<BR> &nbsp; &nbsp; &nbsp;   pass-through, 33
+<BR> &nbsp; &nbsp; &nbsp;   Samba security levels, 290
+<BR> &nbsp; &nbsp; &nbsp;   Samba's default user-level versus Windows, 74
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 28
+<BR> &nbsp; &nbsp; &nbsp;   with winbind, 307-319
+<BR> &nbsp; &nbsp; &nbsp;   (see also passwords)
+<BR>auto services option (smb.conf file), 233, 235, 403
+<BR>automounting shares, 495
+<BR>available option (smb.conf file), 403
+<P><A NAME="B"><B>B</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>backends (CUPS modules), 332
+<BR>backup browsers, 27, 226
+<BR>backup domain controllers (BDCs), 31
+<BR> &nbsp; &nbsp; &nbsp;   Samba 2.2's inability to work with, 122
+<BR> &nbsp; &nbsp; &nbsp;   (see also primary domain controllers)
+<BR>backups, creating and restoring using smbclient, 172-174
+<BR>.bak files, 251
+<BR>.bat files, 138
+<BR>bind interfaces only option (smb.conf file), 208, 403
+<BR>bindings, 69
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 100
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 80
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 93
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 110
+<BR>--bindir (configure script option), 48
+<BR>bitmasks, 176
+<BR> &nbsp; &nbsp; &nbsp;   CIDR format, 208
+<BR>block size option (smb.conf file), 404
+<BR>blocking locks option (smb.conf file), 404
+<BR>b-node (NetBios node type), 13
+<BR>broadcast
+<BR> &nbsp; &nbsp; &nbsp;   name resolution, 71
+<BR> &nbsp; &nbsp; &nbsp;   versus NBNS name registration, 11
+<BR>broadcast address, 389
+<BR>broadcasting, 12
+<BR>browsable option (smb.conf file), 233, 235, 284, 404
+<BR>browse list option (smb.conf file), 235, 404
+<BR>browse lists, 27, 224
+<BR> &nbsp; &nbsp; &nbsp;   invisible shares, 233
+<BR> &nbsp; &nbsp; &nbsp;   printer names, 419
+<BR> &nbsp; &nbsp; &nbsp;   specifying list of shares, 431
+<BR> &nbsp; &nbsp; &nbsp;   specifying shares in, 403, 404
+<BR> &nbsp; &nbsp; &nbsp;   specifying the directory where Samba keeps, 497
+<BR> &nbsp; &nbsp; &nbsp;   synchronizing with all domain master browsers, 411
+<BR>browse master (see local master browser)
+<BR>browse server (see local master browser)
+<BR>browseable option (smb.conf file) (see browsable option (smb.conf file))
+<BR>browser elections, 28, 226-229, 419
+<BR>browsers
+<BR> &nbsp; &nbsp; &nbsp;   backup (see backup browsers)
+<BR> &nbsp; &nbsp; &nbsp;   domain master browser (see domain master browser)
+<BR> &nbsp; &nbsp; &nbsp;   local master (see local master browser)
+<BR>browsing, 216, 224-239
+<BR> &nbsp; &nbsp; &nbsp;   a list of computers and shared resources, defined, 26
+<BR> &nbsp; &nbsp; &nbsp;   configuring Samba for, 229
+<BR> &nbsp; &nbsp; &nbsp;   cross-subnet, 231
+<BR> &nbsp; &nbsp; &nbsp;   in a Windows network, 224-229
+<BR> &nbsp; &nbsp; &nbsp;   invisible shares, 233
+<BR> &nbsp; &nbsp; &nbsp;   options, 233-239
+<BR> &nbsp; &nbsp; &nbsp;   overview, 26-28
+<BR> &nbsp; &nbsp; &nbsp;   server from the client, 382
+<BR> &nbsp; &nbsp; &nbsp;   shared resource of a specific computer, 26
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting problems, 377-383
+<BR>Browsing and Windows 95 Networking and CIFS/E Browser Protocol, 229
+<BR>BROWSING.txt and BROWSING-Config.txt, 229
+<BR>BSD Unix
+<BR> &nbsp; &nbsp; &nbsp;   automatically starting Samba daemons, 61
+<BR> &nbsp; &nbsp; &nbsp;   printers, 330-331
+<P><A NAME="C"><B>C</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>caching policy, client-side, 406
+<BR>case sensitive option (smb.conf file), 265, 404
+<BR>case sensitivity, 262-267
+<BR> &nbsp; &nbsp; &nbsp;   how Samba handles, 264
+<BR> &nbsp; &nbsp; &nbsp;   preserving case of filename, 431
+<BR>casesignames option (smb.conf file), 404
+<BR>change notification, 354
+<BR>change notify timeout option (smb.conf file), 354, 405
+<BR>change share command option (smb.conf file), 405
+<BR>character set option (smb.conf file), 344, 405
+<BR>character sets, translating, 405
+<BR>checking (message from configure script), 48
+<BR>CIDR format bitmask, 208
+<BR>CIFS, 21
+<BR> &nbsp; &nbsp; &nbsp;   Unix extensions, 37, 442
+<BR> &nbsp; &nbsp; &nbsp;   (see also SMB)
+<BR>CIFS Technical Reference, 20
+<BR>client code page option (smb.conf file), 344, 405
+<BR>clustered environment, Samba in, 437
+<BR> &nbsp; &nbsp; &nbsp;   (see also multihomed system; multiple subnets), 437
+<BR>.cmd files, 138
+<BR>code page directory option (smb.conf file), 405
+<BR>code pages, 344
+<BR>coding system option (smb.conf file), 345, 405
+<BR>command-line options, parsing, 495
+<BR>comment option (smb.conf file), 203, 406
+<BR>Common Internet File System (see CIFS)
+<BR>compiling Samba, 49-52
+<BR>components, Windows, 69
+<BR>comp.protocols.smb newsgroup, 392
+<BR>computer accounts, adding, 126
+<BR>computer names
+<BR> &nbsp; &nbsp; &nbsp;   name resolution (see name resolution)
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 103
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 81
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 93
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 113
+<BR>computers, adding to domains, 402
+<BR>Concurrent Versions System (CVS), 491
+<BR>config file option (smb.conf file), 196, 406
+<BR>config.log file, 49
+<BR>config.pol file, 155
+<BR>config.status file, 51
+<BR>configuration file
+<BR> &nbsp; &nbsp; &nbsp;   Samba's main (see smb.conf file)
+<BR> &nbsp; &nbsp; &nbsp;   selecting new, 406
+<BR> &nbsp; &nbsp; &nbsp;   variables (see smb.conf file, variables)
+<BR> &nbsp; &nbsp; &nbsp;   (see also configuring Samba)
+<BR>configuration management tool (see CVS)
+<BR>configuration value types, 448-449
+<BR>configure script, 46
+<BR> &nbsp; &nbsp; &nbsp;   options, 493-499
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --bindir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --datadir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --eprefix, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --include dir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --infodir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --libdir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --libexec dir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --mandir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --prefix, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --sbindir, 48
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      with feature, 47
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-acl-support, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-afs, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-automount, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-codepagedir, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-configdir, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-dce-dfs, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-fhs, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-included-popt, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-krb4, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-krb5, 495
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-ldapsam, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-libiconv, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-libsmbclient, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-lockdir, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-logfilebase, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-manpages-langs, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-msdfs, 47, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-nisplus-home, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-nisplussam, 496
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      without feature, 47
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-pam, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-pam_smbpass, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-piddir, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-privatedir, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-profiling-data, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-quotas, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-readline, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-sendfile-support, 497
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-smbmount, 47, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-smbwrapper, 47, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-spinlocks, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-ssl, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-sslinc, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-ssllib, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-swatdir, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-syslog, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-tdbsam, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-utmp, 498
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      --with-winbind, 499
+<BR> &nbsp; &nbsp; &nbsp;   sample execution, 48
+<BR>configuring Samba, 46-49
+<BR> &nbsp; &nbsp; &nbsp;   configuration file (see smb.conf file)
+<BR> &nbsp; &nbsp; &nbsp;   for browsing, 229
+<BR> &nbsp; &nbsp; &nbsp;   for installation (see configure script)
+<BR> &nbsp; &nbsp; &nbsp;   for roaming profiles, 143-147
+<BR> &nbsp; &nbsp; &nbsp;   identifying options used in previous installations, 51
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting problems (see troubleshooting Samba, fault tree)
+<BR>connection scripts, 274-277
+<BR> &nbsp; &nbsp; &nbsp;   monitoring directory contents, 275
+<BR> &nbsp; &nbsp; &nbsp;   options, 275-277
+<BR>connections
+<BR> &nbsp; &nbsp; &nbsp;   denying, 409
+<BR> &nbsp; &nbsp; &nbsp;   specifying time limits for unused, 407
+<BR>controlling access to shares, 285-288
+<BR>copy option (smb.conf file), 197, 406
+<BR>Core and Core Plus, 20
+<BR>create mask option (smb.conf file), 248, 250, 406
+<BR>create mode option (smb.conf file), 284, 406
+<BR>creating (message from configure script), 48
+<BR>creation masks, 247-250
+<BR>csc policy option (smb.conf file), 406
+<BR>CVS (Concurrent Versions System), 491
+<P><A NAME="D"><B>D</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%d variable, 192
+<BR>daemons (see inetd daemon; nmbd daemon; smbd daemon; xinetd daemon)
+<BR>Darwin, automatically starting Samba daemons, 64
+<BR>.dat files
+<BR> &nbsp; &nbsp; &nbsp;   changing to .man files, 150
+<BR> &nbsp; &nbsp; &nbsp;   NTUSER.DAT, 141
+<BR> &nbsp; &nbsp; &nbsp;   USER.DAT, 141
+<BR>--datadir (configure script option), 48
+<BR>datagram primitives, 17
+<BR>datagram services, defined, 10
+<BR>datagram services (NBT)
+<BR> &nbsp; &nbsp; &nbsp;   defined, 16
+<BR> &nbsp; &nbsp; &nbsp;   tips, 18
+<BR>deadtime option (smb.conf file), 349, 407
+<BR>debug hires timestamp option (smb.conf file), 407
+<BR>debug pid option (smb.conf file), 407
+<BR>debug timestamp option (smb.conf file), 214, 407
+<BR>debug uid option (smb.conf file), 407
+<BR>debuglevel option (smb.conf file), 407
+<BR>default case option (smb.conf file), 264, 265, 408
+<BR>default device mode, setting, 408
+<BR>default devmode option (smb.conf file), 408
+<BR>default option (smb.conf file), 407
+<BR>default service option (smb.conf file), 236, 408
+<BR>defending the hostname, 12
+<BR>delete printer command option (smb.conf file), 408
+<BR>delete readonly option (smb.conf file), 250, 251, 408
+<BR>delete share command option (smb.conf file), 408
+<BR>delete user script option (smb.conf file), 159, 409
+<BR>delete veto files option (smb.conf file), 241, 245, 409
+<BR>deny hosts option (smb.conf file), 409
+<BR>dfree command option (smb.conf file), 350, 409
+<BR>Dfs (Microsoft's Distributed filesystem), 277-280
+<BR> &nbsp; &nbsp; &nbsp;   configuring Samba as Dfs server, 278-279
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 496
+<BR> &nbsp; &nbsp; &nbsp;   providing services, 415
+<BR> &nbsp; &nbsp; &nbsp;   support in Samba 2.2, 36
+<BR> &nbsp; &nbsp; &nbsp;   Windows clients, 278
+<BR>DHCP and IP addresses, 70
+<BR>DIAGNOSIS.txt, 359
+<BR>dig command (Unix), 73
+<BR>Digital Pathworks clients, 353
+<BR>directories
+<BR> &nbsp; &nbsp; &nbsp;   caching for performance, 414
+<BR> &nbsp; &nbsp; &nbsp;   connecting to drive letter, 138
+<BR> &nbsp; &nbsp; &nbsp;   creating on the Samba server, 125
+<BR> &nbsp; &nbsp; &nbsp;   deleting when vetoed files are present, 241, 409
+<BR> &nbsp; &nbsp; &nbsp;   home, setting, 420
+<BR> &nbsp; &nbsp; &nbsp;   monitoring contents, 275
+<BR> &nbsp; &nbsp; &nbsp;   setting maximum allowable permissions, 409
+<BR> &nbsp; &nbsp; &nbsp;   setting paths, 409
+<BR>directory mask option (smb.conf file), 249, 251, 409
+<BR>directory mode option (smb.conf file), 284, 410
+<BR>directory option (smb.conf file), 409
+<BR>directory permissions, 416
+<BR> &nbsp; &nbsp; &nbsp;   options, 250-253
+<BR>directory recursion, 171
+<BR>directory security mask option (smb.conf file), 261, 262, 410
+<BR>disable spools option (smb.conf file), 410
+<BR>disk services, example of sharing, 4-7
+<BR>disk share configuration, 201-203
+<BR>disk-quota support, 497
+<BR>Distributed Computing Environment Distributed Filesystem (DCE/DFS), 495
+<BR>Distributed filesystem (see Dfs)
+<BR>dmask option, 176
+<BR>DNS, 70
+<BR> &nbsp; &nbsp; &nbsp;   configuration
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 2000, 101
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 95/98/Me, 79
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows NT, 92
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows XP, 111
+<BR> &nbsp; &nbsp; &nbsp;   NetBIOS names
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      translating between DNS names and, 182
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      versus hostnames versus, 14
+<BR> &nbsp; &nbsp; &nbsp;   overview, 73
+<BR> &nbsp; &nbsp; &nbsp;   servers, name resolution and, 217
+<BR>DNS proxy, configuring on WINS server, 220
+<BR>dns proxy option (smb.conf file), 220, 223, 410
+<BR>documentation, Samba, 45, 391
+<BR>domain admin group option (smb.conf file), 160, 410
+<BR>domain administrator, 126, 410
+<BR>Domain Admins group, 410
+<BR>domain controllers, 30
+<BR> &nbsp; &nbsp; &nbsp;   backup (see backup domain controllers)
+<BR> &nbsp; &nbsp; &nbsp;   primary (see primary domain controllers)
+<BR>Domain Guest group, 410
+<BR>domain guest group option (smb.conf file), 410
+<BR>domain logons
+<BR> &nbsp; &nbsp; &nbsp;   configuring Windows clients for, 128-137
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 133-135
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 128-131
+<BR> &nbsp; &nbsp; &nbsp;   Windows complains that you are already logged on, 129
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 131-133
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP Professional, 135-137
+<BR>domain logons option (smb.conf file), 159, 410
+<BR>domain master browser, 35, 226
+<BR> &nbsp; &nbsp; &nbsp;   configuring Samba as both local master browser and, 124
+<BR> &nbsp; &nbsp; &nbsp;   forcing Samba to be, 237, 411
+<BR> &nbsp; &nbsp; &nbsp;   problems with, 35
+<BR> &nbsp; &nbsp; &nbsp;   Samba as, 230
+<BR> &nbsp; &nbsp; &nbsp;   synchronizing browse lists with all, 411
+<BR> &nbsp; &nbsp; &nbsp;   verifying Samba as, 231
+<BR>domain master option (smb.conf file), 159, 237, 411
+<BR>domain member server, 34
+<BR> &nbsp; &nbsp; &nbsp;   Samba as, 156-157
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      smb.conf file example, 400
+<BR>domain membership, 126
+<BR>Domain Name System (see DNS)
+<BR>domain-level security, 291, 296
+<BR>domains
+<BR> &nbsp; &nbsp; &nbsp;   adding computers to, 402
+<BR> &nbsp; &nbsp; &nbsp;   advantages of, 120
+<BR> &nbsp; &nbsp; &nbsp;   more information on how to set up, 122
+<BR> &nbsp; &nbsp; &nbsp;   trust relationships, 33
+<BR> &nbsp; &nbsp; &nbsp;   trusted, 403
+<BR> &nbsp; &nbsp; &nbsp;   (see also Windows NT domain options)
+<BR>dont descend option (smb.conf file), 241, 243, 411
+<BR>dos filemode option (smb.conf file), 411
+<BR>dos filetime resolution option (smb.conf file), 342, 411
+<BR>dos filetimes option (smb.conf file), 341, 411
+<BR>dos2unix command, 170
+<BR>dot files, 240
+<BR> &nbsp; &nbsp; &nbsp;   hiding, 414
+<BR> &nbsp; &nbsp; &nbsp;   (see also hiding files)
+<BR>drive letter, connecting a directory to, 6, 138
+<P><A NAME="E"><B>E</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>emacs text editor, 139
+<BR>encrypt passwords option (smb.conf file), 304, 411
+<BR>encrypted passwords
+<BR> &nbsp; &nbsp; &nbsp;   disabling, 298
+<BR> &nbsp; &nbsp; &nbsp;   managing, 483
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      (see also smbpasswd program)
+<BR> &nbsp; &nbsp; &nbsp;   smb.conf file and, 55
+<BR> &nbsp; &nbsp; &nbsp;   (see also passwords)
+<BR>enhanced browsing option (smb.conf file), 411
+<BR>enumports command option (smb.conf file), 412
+<BR>environment variables, forcing Samba to read list of, 437
+<BR>--eprefix (configure script option), 48
+<BR>error messages from configure script, 48
+<BR>/etc/fstab file, warning about editing, 177
+<BR>/etc/group, 283
+<BR>/etc/hosts file, 70
+<BR>/etc/nsswitch.conf file, 71
+<BR>/etc/passwd file, creating entries manually, 127
+<BR>/etc/printcap.local file, 330
+<BR>/etc/resolv.conf file, 73, 220
+<BR>Ethereal (SMB sniffer), 20, 361
+<BR>exec option (smb.conf file), 412
+<BR>executable file permission bit, 248
+<BR>ext2/ext3 filesystem, 37
+<P><A NAME="F"><B>F</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>fake directory create times option (smb.conf file), 342, 412
+<BR>fake oplocks option (smb.conf file), 273, 412
+<BR>FAQs, Samba, 391
+<BR>fault tree, troubleshooting Samba, 362-391
+<BR>file locking (see locks and oplocks)
+<BR>file permissions
+<BR> &nbsp; &nbsp; &nbsp;   executable bit, 248
+<BR> &nbsp; &nbsp; &nbsp;   on MS-DOS and Unix, 245-253
+<BR> &nbsp; &nbsp; &nbsp;   options, 250-253
+<BR> &nbsp; &nbsp; &nbsp;   setting in Windows NT/2000/XP, 165
+<BR> &nbsp; &nbsp; &nbsp;   setting maximum allowable, 406
+<BR> &nbsp; &nbsp; &nbsp;   Unix permission bits summary, 247
+<BR> &nbsp; &nbsp; &nbsp;   Unix permissions versus ACLs, 31
+<BR> &nbsp; &nbsp; &nbsp;   versus ACLs, 31
+<BR>file transfer using smbclient, 170
+<BR>filenames
+<BR> &nbsp; &nbsp; &nbsp;   conventions, 262
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      (see also name mangling)
+<BR> &nbsp; &nbsp; &nbsp;   representing and resolving in Samba, 264
+<BR>Filesystem Hierarchy Standard, 495
+<BR>filesystem options, 243-245
+<BR>findsmb program, 40, 455
+<BR>firewall configuration, 60
+<BR>fmask option (sbmount), 176
+<BR>follow symlinks option (smb.conf file), 242, 243, 412
+<BR>force create mode option (smb.conf file), 251, 412
+<BR>force directory mode option (smb.conf file), 251, 413
+<BR>force directory security mode option (smb.conf file), 262, 413
+<BR>force group option (smb.conf file), 249, 251, 413
+<BR>force security mode option (smb.conf file), 261, 413
+<BR>force unknown acl user option (smb.conf file), 413
+<BR>force user option (smb.conf file), 249, 251, 413
+<BR>Frisch, �leen, 325
+<BR>fstab file, warning about editing, 177
+<BR>fstype option (smb.conf file), 350, 413
+<P><A NAME="G"><B>G</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%G variable, 192
+<BR>%g variable, 192
+<BR>gcc binaries, 44
+<BR>get command, 170
+<BR>getwd cache option (smb.conf file), 243, 414
+<BR>[global] section (smb.conf file), 193
+<BR>GNU configure script (see configure script)
+<BR>GNU Free Documentation License, 511-518
+<BR>Google, 392
+<BR>group ID (GID), 31
+<BR>group option (smb.conf file), 414
+<BR>grouppol.inf file, 153
+<BR>groups
+<BR> &nbsp; &nbsp; &nbsp;   additional information, 16
+<BR> &nbsp; &nbsp; &nbsp;   overriding a user's normal group membership, 413
+<BR> &nbsp; &nbsp; &nbsp;   setting a group share in smb.conf file, 283
+<BR> &nbsp; &nbsp; &nbsp;   system group file, 283
+<BR> &nbsp; &nbsp; &nbsp;   (see also workgroups; SMB, groups)
+<BR>guest access, 286
+<BR>guest account option (smb.conf file), 286, 288, 414
+<BR>guest ok option (smb.conf file), 286, 414
+<BR>guest only option (smb.conf file), 288, 414
+<P><A NAME="H"><B>H</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%H variable, 192, 283
+<BR>%h variable, 192
+<BR>hide dot files option (smb.conf file), 240, 244, 414
+<BR>hide files option (smb.conf file), 241, 244, 414
+<BR>hide local users option (smb.conf file), 415
+<BR>hide unreadable option (smb.conf file), 415
+<BR>hiding files, 240-242
+<BR>h-node (NetBios node type), 13
+<BR>home directory, setting, 420
+<BR>homedir map option (smb.conf file), 281, 415
+<BR>[homes] share (smb.conf file), 125, 194, 233, 284
+<BR> &nbsp; &nbsp; &nbsp;   peculiarities with, 284
+<BR>host msdfs option (smb.conf file), 280, 415
+<BR>hostname, defending, 12
+<BR>hosts allow option (smb.conf file), 204-207, 415
+<BR>hosts deny option (smb.conf file), 204-207, 415
+<BR>hosts equiv option (smb.conf file), 307, 415
+<BR>HOSTS file, 70, 74
+<BR>hosts.sam file, 74
+<BR>Hunt, Craig, 87
+<P><A NAME="I"><B>I</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%I variable, 192
+<BR>iconv( ) function, 496
+<BR>ifconfig command, 390
+<BR>Implementing Policies and Profiles for Windows NT 4.0, 141
+<BR>--include dir (configure script option), 48
+<BR>include option (smb.conf file), 193, 197, 416
+<BR>inetd daemon, 53
+<BR> &nbsp; &nbsp; &nbsp;   starting smbd and nmbd daemons, 66
+<BR>--infodir (configure script option), 48
+<BR>inherit acls option (smb.conf file), 416
+<BR>inherit permissions option (smb.conf file), 253, 416
+<BR>.ini files, 187
+<BR>installation directories for Samba, 50
+<BR>installing Samba, 49-52
+<BR> &nbsp; &nbsp; &nbsp;   on a Unix system, 42-67
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ANSI C compiler required by Samba source, 44
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      binary versus source, 43
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      bundled versions, 42-45
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      configuration (see configure script)
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      source, overview of steps, 44
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting problems (see troubleshooting Samba, fault tree)
+<BR>interfaces list, 403
+<BR>interfaces option (smb.conf file), 207, 416
+<BR>internationalization, 343-346
+<BR> &nbsp; &nbsp; &nbsp;   features of Samba 2.2, 456
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 495
+<BR>invalid users option (smb.conf file), 284, 285, 287, 416
+<BR>invalid users, specifying list of, 285
+<BR>IP addresses, 70
+<BR> &nbsp; &nbsp; &nbsp;   127.0.0.1 (localhost), 73
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      bind interfaces only option, 208
+<BR> &nbsp; &nbsp; &nbsp;   translating between NetBIOS names and, 182
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 100
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me networks, 78
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 90
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 111
+<BR>IPC$ password, 75
+<BR>ipconfig /all command (Windows NT/2000/XP), 13
+<BR>ipconfig command, 390
+<P><A NAME="K"><B>K</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>keepalive option (smb.conf file), 351, 416
+<BR>Kerberos authentication, 38
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 495
+<BR> &nbsp; &nbsp; &nbsp;   Samba 2.2 and, 121
+<BR> &nbsp; &nbsp; &nbsp;   time synchronization and, 340
+<BR>kernel oplocks option (smb.conf file), 272, 417
+<P><A NAME="L"><B>L</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%L variable, 140, 144, 192
+<BR>LAN Manager host announcements, 236
+<BR>LAN Manager versions 1.0, 2.0, and 2.1, 20
+<BR>lanman auth option (smb.conf file), 417
+<BR>large readwrite option (smb.conf file), 417
+<BR>LDAP, 34, 38
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 496
+<BR> &nbsp; &nbsp; &nbsp;   Samba 2.2 and, 121
+<BR>ldap admin dn option (smb.conf file), 417
+<BR>ldap filter option (smb.conf file), 417
+<BR>ldap port option (smb.conf file), 417
+<BR>ldap server option (smb.conf file), 418
+<BR>ldap ssl option (smb.conf file), 418
+<BR>ldap suffix option (smb.conf file), 418
+<BR>level2 oplocks option (smb.conf file), 272, 418
+<BR>--libdir (configure script option), 48
+<BR>--libexec dir (configure script option), 48
+<BR>libnss_winbind.so library, 309
+<BR>Linux-PAM System Administrator's Guide, 314
+<BR>Liu, Cricket, 383
+<BR>lm announce option (smb.conf file), 236, 418
+<BR>lm interval option (smb.conf file), 237, 418
+<BR>LMHOSTS file, 72
+<BR> &nbsp; &nbsp; &nbsp;   name resolution and, 218
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 102
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 80
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 92
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 112
+<BR>load balancing and Dfs, 277, 279
+<BR>load printers option (smb.conf file), 336, 419
+<BR>local master browser, 27, 224
+<BR> &nbsp; &nbsp; &nbsp;   configuring Samba as both domain master browser and, 124
+<BR>local master option (smb.conf file), 230, 236, 419
+<BR>local profiles, 141
+<BR>localhost address (see 127.0.0.1 (localhost))
+<BR>lock dir option (smb.conf file), 419
+<BR>lock directory option (smb.conf file), 274, 419
+<BR>lock spin count option (smb.conf file), 419
+<BR>lock spin time option (smb.conf file), 419
+<BR>locking files (see locks and oplocks)
+<BR>locking option (smb.conf file), 271, 419
+<BR>locks and oplocks, 268-274
+<BR> &nbsp; &nbsp; &nbsp;   advanced tuning parameter, 428
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      release an oplock, 427
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 270-274
+<BR> &nbsp; &nbsp; &nbsp;   oplock failure, 269
+<BR> &nbsp; &nbsp; &nbsp;   opportunistic locking process, 268
+<BR> &nbsp; &nbsp; &nbsp;   setting file locking, 419
+<BR> &nbsp; &nbsp; &nbsp;   specifying directory where Samba keeps lock files, 496
+<BR> &nbsp; &nbsp; &nbsp;   spin locks, 498
+<BR> &nbsp; &nbsp; &nbsp;   Unix and oplocks, 270
+<BR>log file option (smb.conf file), 213, 356, 419
+<BR>log files, 67
+<BR> &nbsp; &nbsp; &nbsp;   changing timestamps, 407
+<BR> &nbsp; &nbsp; &nbsp;   example, 210
+<BR> &nbsp; &nbsp; &nbsp;   levels of logging, 356-358
+<BR> &nbsp; &nbsp; &nbsp;   nmbd, 231
+<BR> &nbsp; &nbsp; &nbsp;   sample output of levels 2 and 3, 356
+<BR> &nbsp; &nbsp; &nbsp;   setting location of, 419
+<BR> &nbsp; &nbsp; &nbsp;   setting maximum size, 423
+<BR> &nbsp; &nbsp; &nbsp;   specifying the directory where Samba keeps, 496
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting with, 356-359
+<BR> &nbsp; &nbsp; &nbsp;   (see also logging)
+<BR>log level option (smb.conf file), 213, 420
+<BR>logging
+<BR> &nbsp; &nbsp; &nbsp;   activating and deactivating, 358
+<BR> &nbsp; &nbsp; &nbsp;   adding process ID, 407
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 210-215
+<BR> &nbsp; &nbsp; &nbsp;   debugging particular user, 407
+<BR> &nbsp; &nbsp; &nbsp;   (see also log files)
+<BR>login parameters, setting, 24
+<BR>logon drive option (smb.conf file), 151, 420
+<BR>logon home line (smb.conf file), 144
+<BR>logon home option (smb.conf file), 152, 420
+<BR>logon path line (smb.conf file), 144
+<BR>logon path option (smb.conf file), 151, 420
+<BR>logon path, supporting roaming profiles for Windows NT/2000/XP clients, 124
+<BR>logon script option (smb.conf file), 151, 420
+<BR>logon scripts, 120, 137-140
+<BR> &nbsp; &nbsp; &nbsp;   checking the format, 139
+<BR> &nbsp; &nbsp; &nbsp;   creating, 138-140
+<BR> &nbsp; &nbsp; &nbsp;   more information regarding, 140
+<BR> &nbsp; &nbsp; &nbsp;   options, 150
+<BR> &nbsp; &nbsp; &nbsp;   using variables inside, 139
+<BR>logon.bat, 138
+<BR>log.smb file, 67
+<BR>lpadmin command (Unix), 333
+<BR>lppause command option (smb.conf file), 336, 420
+<BR>lppause command (Unix), 323
+<BR>lpq cache time option (smb.conf file), 335, 420
+<BR>lpq command option (smb.conf file), 336, 421
+<BR>lpq command (Unix), 323
+<BR>lpr command (Unix), 322
+<BR>lpresume command option (smb.conf file), 336, 421
+<BR>lpresume command (Unix), 323
+<BR>lprm command option (smb.conf file), 336, 421
+<BR>lprm command (Unix), 323
+<P><A NAME="M"><B>M</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%M variable, 192
+<BR>%m variable, 140, 143, 192
+<BR>Mac OS X
+<BR> &nbsp; &nbsp; &nbsp;   automatically starting Samba daemons, 64
+<BR> &nbsp; &nbsp; &nbsp;   configuration details, 506-509
+<BR> &nbsp; &nbsp; &nbsp;   enabling SMB printer sharing, 325
+<BR> &nbsp; &nbsp; &nbsp;   monitoring services, 505
+<BR> &nbsp; &nbsp; &nbsp;   Password Server, 504
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      activating, 504
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      enabling, 505
+<BR> &nbsp; &nbsp; &nbsp;   smbutil and mount_smbfs, 184-186
+<BR>Mac OS X Server
+<BR> &nbsp; &nbsp; &nbsp;   configuration settings, 508
+<BR> &nbsp; &nbsp; &nbsp;   configuring and activating services, 503
+<BR> &nbsp; &nbsp; &nbsp;   running Samba on, 500-510
+<BR> &nbsp; &nbsp; &nbsp;   sharing files, 501
+<BR> &nbsp; &nbsp; &nbsp;   sharing printers, 501
+<BR>Mac OS X Server Administrator's Guide, 500
+<BR>machine password timeout option (smb.conf file), 160, 421
+<BR>magic output option (smb.conf file), 343, 421
+<BR>magic script option (smb.conf file), 343, 421
+<BR>magic scripts, 342
+<BR>mailing lists, Samba, 392
+<BR> &nbsp; &nbsp; &nbsp;   archives, 45
+<BR>make install command (Unix), 50
+<BR> &nbsp; &nbsp; &nbsp;   upgrading installations, 52
+<BR>make revert command (Unix), 50
+<BR>make utility (Unix), 49
+<BR>makefile, generating for Samba configuration, 46
+<BR>make_smbcodepage program, 40, 456
+<BR>make_unicodemap program, 40, 456
+<BR>.man files, changing from .dat files, 150
+<BR>man pages (see manual pages)
+<BR>managing connections to shares (see connection scripts)
+<BR>mandatory profiles, 149
+<BR> &nbsp; &nbsp; &nbsp;   changing from roaming profiles, 150
+<BR>--mandir (configure script option), 48
+<BR>mangle case option (smb.conf file), 267, 421
+<BR>mangled map option (smb.conf file), 267, 422
+<BR>mangled names option (smb.conf file), 266, 422
+<BR>mangled stack option (smb.conf file), 267, 422
+<BR>mangling char option (smb.conf file), 267, 422
+<BR>mangling method option (smb.conf file), 422
+<BR>MANPATH environment variable, 52
+<BR>manual pages, 52
+<BR> &nbsp; &nbsp; &nbsp;   in different languages, 496
+<BR>map archive option (smb.conf file), 247, 252, 422
+<BR>map hidden option (smb.conf file), 247, 252, 422
+<BR>map system option (smb.conf file), 247, 252, 422
+<BR>map to guest option (smb.conf file), 423
+<BR>mapping a free-form client username to a Unix username, 289
+<BR>mapping a network drive (see drive letter, connecting a directory to)
+<BR>master browser (see local master browser)
+<BR>max connections option (smb.conf file), 288, 423
+<BR>max disk size option (smb.conf file), 351, 423
+<BR>max log size option (smb.conf file), 213, 423
+<BR>max mux option (smb.conf file), 351, 423
+<BR>max open files option (smb.conf file), 423
+<BR>max open files (smb.conf file), 351
+<BR>max print jobs option (smb.conf file), 424
+<BR>max protocol option (smb.conf file), 424
+<BR>max smbd processes option (smb.conf file), 424
+<BR>max ttl option (smb.conf file), 224, 424
+<BR>max wins ttl option (smb.conf file), 224, 424
+<BR>max xmit option (smb.conf file), 352, 424
+<BR>message command option (smb.conf file), 348, 424
+<BR>messenger service, 346-348
+<BR>mget command, 170
+<BR>Microsoft Distributed filesystem (see Dfs)
+<BR>min passwd length option (smb.conf file), 425
+<BR>min password length option (smb.conf file), 425
+<BR>min print space option (smb.conf file), 338, 425
+<BR>min protocol option (smb.conf file), 425
+<BR>min wins ttl option (smb.conf file), 224, 425
+<BR>m-node (NetBios node type), 13
+<BR>mount_smbfs program, 161, 182
+<BR> &nbsp; &nbsp; &nbsp;   options, 183
+<BR>mput command, 170
+<BR>msdfs root option (smb.conf file), 280, 425
+<BR>MS-DOS file permissions, 245-253
+<BR>MSN Messenger, 346-348
+<BR>multihomed system
+<BR> &nbsp; &nbsp; &nbsp;   running Samba on, 204
+<BR> &nbsp; &nbsp; &nbsp;   (see also clustered environment, Samba in; multiple subnets)
+<BR>multiple subnets
+<BR> &nbsp; &nbsp; &nbsp;   cross-subnet browsing, 232
+<BR> &nbsp; &nbsp; &nbsp;   with Samba servers, 232
+<BR> &nbsp; &nbsp; &nbsp;   (see also clustered environment, Samba in; multihomed system)
+<BR>My Network Places, 26
+<BR> &nbsp; &nbsp; &nbsp;   (see also Network Neighborhood)
+<P><A NAME="N"><B>N</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%N variable, 192
+<BR>name mangling, 262-267
+<BR> &nbsp; &nbsp; &nbsp;   how Samba mangles a long filename into a 8.3 filename, 263
+<BR> &nbsp; &nbsp; &nbsp;   options, 265-267, 421
+<BR>name registration, 11-13
+<BR>name resolution, 11-13, 70, 216-224
+<BR> &nbsp; &nbsp; &nbsp;   broadcast method, 71
+<BR> &nbsp; &nbsp; &nbsp;   configuring in Samba, 219
+<BR> &nbsp; &nbsp; &nbsp;   methods, 217
+<BR> &nbsp; &nbsp; &nbsp;   using broadcast packets, 217
+<BR>name resolve order option (smb.conf file), 219, 223, 425
+<BR>name services
+<BR> &nbsp; &nbsp; &nbsp;   defined, 10
+<BR> &nbsp; &nbsp; &nbsp;   identifying what's in use, 383
+<BR> &nbsp; &nbsp; &nbsp;   switching, 71
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting, 383-388
+<BR>name-resolution configuration options, 221-224
+<BR>NBNS name registration
+<BR> &nbsp; &nbsp; &nbsp;   versus broadcast, 11
+<BR>NBT, 10, 69
+<BR> &nbsp; &nbsp; &nbsp;   services, 16
+<BR>NBT Standard, 10
+<BR>nbtstat utility, 228
+<BR> &nbsp; &nbsp; &nbsp;   examples, 14, 15
+<BR>net program, 40, 457-462
+<BR>net time command, 138, 339
+<BR>net use command, 138, 144
+<BR> &nbsp; &nbsp; &nbsp;   testing connections with, 374
+<BR>net view program, 225
+<BR> &nbsp; &nbsp; &nbsp;   testing client browsing, 381
+<BR>NetBEUI protocol, 10
+<BR> &nbsp; &nbsp; &nbsp;   running at same time as NetBIOS over TCP/IP, 69
+<BR>NetBIOS
+<BR> &nbsp; &nbsp; &nbsp;   group resource types, 16
+<BR> &nbsp; &nbsp; &nbsp;   names
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      translating between IP address or DNS names and, 182
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      troubleshooting, 390
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      versus DNS hostnames, 14
+<BR> &nbsp; &nbsp; &nbsp;   node types, 13
+<BR> &nbsp; &nbsp; &nbsp;   overview, 9
+<BR> &nbsp; &nbsp; &nbsp;   resource names and types, 14
+<BR> &nbsp; &nbsp; &nbsp;   session, establishing, 22
+<BR> &nbsp; &nbsp; &nbsp;   unique resource types, 15
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 80
+<BR>netbios aliases option (smb.conf file), 209, 426
+<BR>netbios name option (smb.conf file), 200, 426
+<BR>NetBIOS over TCP/IP (see NBT)
+<BR>netbios scope option (smb.conf file), 426
+<BR>[netlogon] share (smb.conf file), 125, 138, 233
+<BR>netmask, using to troubleshoot, 388
+<BR>network adapters, 69
+<BR>network addresses
+<BR> &nbsp; &nbsp; &nbsp;   finding your specific address, 390
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting, 388-390
+<BR>Network Information Service (see NIS)
+<BR>Network Neighborhood, 27
+<BR> &nbsp; &nbsp; &nbsp;   (see also My Network Places)
+<BR>Network Time Protocol (NTP), 340
+<BR>network traffic, monitoring (see tcpdump program)
+<BR>networking
+<BR> &nbsp; &nbsp; &nbsp;   components
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 2000, 99
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows XP, 109
+<BR> &nbsp; &nbsp; &nbsp;   concepts, Windows (see Windows, networking concepts)
+<BR> &nbsp; &nbsp; &nbsp;   options, 204-208
+<BR>new features
+<BR> &nbsp; &nbsp; &nbsp;   in Samba 2.2, 36
+<BR> &nbsp; &nbsp; &nbsp;   in Samba 3.0, 38
+<BR>news, Samba, 45
+<BR>newsgroups, Samba, 391
+<BR>NFS, installing Samba with support for, 495
+<BR>NIS+
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 496
+<BR> &nbsp; &nbsp; &nbsp;   server, installing Samba with support for locating, 496
+<BR>nis homedir option (smb.conf file), 281, 426
+<BR>NIS (Network Information Service), 71, 280
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 280
+<BR> &nbsp; &nbsp; &nbsp;   server, 30
+<BR>nmake command, 412
+<BR>nmap command (Unix), 73
+<BR>nmbd daemon, 3, 39, 61, 453
+<BR> &nbsp; &nbsp; &nbsp;   starting automatically, 61-65
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      BSD Unix, 61
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Darwin and Mac OS X, 64
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      System V Unix, 61
+<BR> &nbsp; &nbsp; &nbsp;   starting from inetd, 66
+<BR> &nbsp; &nbsp; &nbsp;   starting manually, 61
+<BR> &nbsp; &nbsp; &nbsp;   testing, 66
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      automatic startup, 65
+<BR> &nbsp; &nbsp; &nbsp;   time service, 442
+<BR>nmbd log file, 231
+<BR>nmblookup program, 40, 229, 231, 462
+<BR> &nbsp; &nbsp; &nbsp;   testing clients, 380
+<BR> &nbsp; &nbsp; &nbsp;   testing network, 381
+<BR> &nbsp; &nbsp; &nbsp;   testing servers, 379
+<BR>nobody account, 286
+<BR>node types, 13
+<BR>non unix account range option (smb.conf file), 426
+<BR>nslookup command (Unix), 73
+<BR>nsmb.conf file, 181
+<BR>.nsmbrc files, 181
+<BR>nsswitch, configuring, 309
+<BR>nsswitch.conf file, 71
+<BR>nt acl support option (smb.conf file), 260, 426
+<BR>NT LAN Manager 1.0, 21
+<BR>nt pipe support option (smb.conf file), 352, 426
+<BR>nt smb support option (smb.conf file), 352, 427
+<BR>nt status support option (smb.conf file), 427
+<BR>ntconfig.pol file, 155
+<BR>NT-specific SMB IPC$ pipes, 352
+<BR>NTUSER.DAT file, 141
+<BR>null passwords option (smb.conf file), 306, 427
+<BR>number of address ranges, 389
+
+<P><A NAME="O"><B>O</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>obey pam restrictions option (smb.conf file), 427
+<BR>od command, 139
+<BR>.old files, 50
+<BR>ole locking compatibility (smb.conf file), 352
+<BR>only guest option (smb.conf file), 427
+<BR>only user option (smb.conf file), 293, 427
+<BR>Open Directory Password Server, 504
+<BR>oplock break wait time option (smb.conf file), 427
+<BR>oplock contention limit option (smb.conf file), 428
+<BR>oplocks option (smb.conf file), 272, 428
+<BR>opportunistic locking (see locks and oplocks)
+<BR>os level option (smb.conf file), 230, 238, 428
+<BR>os2 driver map option (smb.conf file), 428
+<BR>overwriting files (see locks and oplocks)
+
+<P><A NAME="P"><B>P</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%P variable, 192
+<BR>%p variable, 192
+<BR>padc command, 359
+<BR>pam password change option (smb.conf file), 428
+<BR>PAM (Pluggable Authentication Modules), 38
+<BR> &nbsp; &nbsp; &nbsp;   configuring, 313-317
+<BR>pam_stack.so module, 316
+<BR>pam_winbind.so module, 316
+<BR>panic action option (smb.conf file), 352, 428
+<BR>par command, 359
+<BR>passdb backend option (smb.conf file), 429
+<BR>pass-through authentication, 33
+<BR>passwd chat debug option (smb.conf file), 305, 429
+<BR>passwd chat option (smb.conf file), 301, 305, 429
+<BR>PASSWD environment variable, 167
+<BR>passwd file, creating entries manually, 127
+<BR>passwd program option (smb.conf file), 305, 429
+<BR>password chat response characters, 302
+<BR>password chat send characters, 302
+<BR>password level option (smb.conf file), 305, 429
+<BR>Password Server (Mac OS X), 504
+<BR> &nbsp; &nbsp; &nbsp;   activating, 504
+<BR> &nbsp; &nbsp; &nbsp;   enabling, 505
+<BR>password server option (smb.conf file), 160, 295, 429
+<BR>passwords, 74, 296-307
+<BR> &nbsp; &nbsp; &nbsp;   adding to smb.conf file, 75
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 303-307
+<BR> &nbsp; &nbsp; &nbsp;   disabling encrypted, 298
+<BR> &nbsp; &nbsp; &nbsp;   encrypted (see encrypted passwords)
+<BR> &nbsp; &nbsp; &nbsp;   IPC$, 75
+<BR> &nbsp; &nbsp; &nbsp;   limiting length of, 425
+<BR> &nbsp; &nbsp; &nbsp;   plain-text versus encrypted, 74
+<BR> &nbsp; &nbsp; &nbsp;   setting on Windows 95/98/Me, 83
+<BR> &nbsp; &nbsp; &nbsp;   setting servers that validate, 429
+<BR> &nbsp; &nbsp; &nbsp;   synchronization, 300-303
+<BR> &nbsp; &nbsp; &nbsp;   Windows versus Unix, 29
+<BR> &nbsp; &nbsp; &nbsp;   (see also authentication)
+<BR>PATH environment variable, 52
+<BR>path option (smb.conf file), 202, 430
+<BR>pdbedit program, 40, 464
+<BR>PDC emulator, 121
+<BR>PDCs (see primary domain controllers)
+<BR>Pearce, Eric, 16, 160
+<BR>performance, caching directories, 414
+<BR>period (.)
+<BR> &nbsp; &nbsp; &nbsp;   NetBIOS names and, 14
+<BR> &nbsp; &nbsp; &nbsp;   (see also dot files)
+<BR>permissions
+<BR> &nbsp; &nbsp; &nbsp;   mapping to Windows NT ACLs, 426
+<BR> &nbsp; &nbsp; &nbsp;   (see also file permissions; directory permissions)
+<BR>pid directory option (smb.conf file), 430
+<BR>PIDs, adding to log lines, 407
+<BR>ping, troubleshooting with, 363-367
+<BR>Pluggable Authentication Modules (see PAM)
+<BR>p-node (NetBios node type), 13
+<BR>point-to-point communication, 12
+<BR>policies, defined, 120
+<BR>port names, customized, 412
+<BR>POSIX ACL support, 416
+<BR>posix locking option (smb.conf file), 272, 430
+<BR>POSIX.1e ACLs, 259
+<BR>postexec option (smb.conf file), 277, 430
+<BR>postscript option (smb.conf file), 335, 430
+<BR>preexec close option (smb.conf file), 277, 430
+<BR>preexec option (smb.conf file), 274, 276, 430
+<BR>preferred master option (smb.conf file), 237, 431
+<BR>preferred master parameter (smb.conf file), 230
+<BR>--prefix (configure script option), 48
+<BR>preload option (smb.conf file), 235, 431
+<BR>preserve case option (smb.conf file), 264, 266, 431
+<BR>preventing file overwrites (see locks and oplocks)
+<BR>primary domain controllers (PDCs), 31, 226
+<BR> &nbsp; &nbsp; &nbsp;   handling authentication (see winbind)
+<BR> &nbsp; &nbsp; &nbsp;   modifying smb.conf file, 122-125
+<BR> &nbsp; &nbsp; &nbsp;   Samba as, 121-126
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      smb.conf file example, 397-399
+<BR>primary WINS server, 32
+<BR> &nbsp; &nbsp; &nbsp;   synchronization problems with Samba 2.2, 33
+<BR>print command option (smb.conf file), 322, 336, 431
+<BR>print commands, 321
+<BR>print jobs
+<BR> &nbsp; &nbsp; &nbsp;   deleting, 421
+<BR> &nbsp; &nbsp; &nbsp;   limiting number of, 424
+<BR> &nbsp; &nbsp; &nbsp;   pausing, 420
+<BR> &nbsp; &nbsp; &nbsp;   resuming, 421
+<BR> &nbsp; &nbsp; &nbsp;   sending over Samba, 321
+<BR>print ok option (smb.conf file), 433
+<BR>printable option (smb.conf file), 323, 335, 431
+<BR>printcap file, 419
+<BR> &nbsp; &nbsp; &nbsp;   example, 336
+<BR>printcap name option (smb.conf file), 338, 431
+<BR>printcap option (smb.conf file), 338
+<BR>printcap.local file, 330
+<BR>printer admin option (smb.conf file), 432
+<BR>printer driver file option (smb.conf file), 432
+<BR>printer driver location option (smb.conf file), 432
+<BR>printer driver option (smb.conf file), 432
+<BR>printer name option (smb.conf file), 335, 432
+<BR>printer option (smb.conf file), 335, 432
+<BR>printer status, setting command for, 421
+<BR>printers
+<BR> &nbsp; &nbsp; &nbsp;   adding new to system, 401
+<BR> &nbsp; &nbsp; &nbsp;   BSD, 330-331
+<BR> &nbsp; &nbsp; &nbsp;   CUPS, 332
+<BR> &nbsp; &nbsp; &nbsp;   example of sharing, 8
+<BR> &nbsp; &nbsp; &nbsp;   names in browse lists, 419
+<BR> &nbsp; &nbsp; &nbsp;   removing from system, 408
+<BR> &nbsp; &nbsp; &nbsp;   sending files using smbclient, 325
+<BR> &nbsp; &nbsp; &nbsp;   setting default device mode, 408
+<BR> &nbsp; &nbsp; &nbsp;   setting up from Windows, 8
+<BR> &nbsp; &nbsp; &nbsp;   sharing, 320
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      on Mac OS X, 501
+<BR> &nbsp; &nbsp; &nbsp;   System V, 331
+<BR> &nbsp; &nbsp; &nbsp;   (see also printing)
+<BR>[printers] share (smb.conf file), 195, 324
+<BR> &nbsp; &nbsp; &nbsp;   example for a Linux system, 324
+<BR>printing, 320-338
+<BR> &nbsp; &nbsp; &nbsp;   adding a Unix printer, 330-333
+<BR> &nbsp; &nbsp; &nbsp;   common problem with Samba printer configuration, 325
+<BR> &nbsp; &nbsp; &nbsp;   CUPS-compatible, 486
+<BR> &nbsp; &nbsp; &nbsp;   debugging printers, 325
+<BR> &nbsp; &nbsp; &nbsp;   Mac OS X environment, 325
+<BR> &nbsp; &nbsp; &nbsp;   network, 320
+<BR> &nbsp; &nbsp; &nbsp;   options, 333-338
+<BR> &nbsp; &nbsp; &nbsp;   setting up and testing a Windows client, 326
+<BR> &nbsp; &nbsp; &nbsp;   shares
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      example, 322
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      important information about, 323
+<BR> &nbsp; &nbsp; &nbsp;   system types, 334
+<BR> &nbsp; &nbsp; &nbsp;   testing the configuration, 325
+<BR> &nbsp; &nbsp; &nbsp;   to Windows from Unix, 327-338
+<BR> &nbsp; &nbsp; &nbsp;   variables, 322
+<BR> &nbsp; &nbsp; &nbsp;   (see also printers)
+<BR>printing option (smb.conf file), 334, 432
+<BR>private directory option (smb.conf file), 433
+<BR>process IDs, adding to log lines, 407
+<BR>processes, viewing in Unix, 8
+<BR>[profiles] share (smb.conf file), 125
+<BR>prompt command, 171
+<BR>protocol option (smb.conf file), 433
+<BR>ps command (Unix), 8
+<BR> &nbsp; &nbsp; &nbsp;   looking for daemon processes with, 368
+<BR>public option (smb.conf file), 433
+<BR>put command, 170
+<BR>.pwl files, 29
+<P><A NAME="Q"><B>Q</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>queuepause command option (smb.conf file), 338, 433
+<BR>queueresume command option (smb.conf file), 338, 433
+<P><A NAME="R"><B>R</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%R variable, 192
+<BR>read bmpx option (smb.conf file), 433
+<BR>read list option (smb.conf file), 286, 288, 433
+<BR>read only option (smb.conf file), 203, 434
+<BR>read raw option (smb.conf file), 434
+<BR>read size option (smb.conf file), 434
+<BR>readline( ) support, 497
+<BR>read-only access, specifying users, 433
+<BR>realm option (smb.conf file), 434
+<BR>reconfiguring Samba, 52
+<BR>recurse command, 171
+<BR>registry files, 141
+<BR> &nbsp; &nbsp; &nbsp;   settings and passwords, 74
+<BR>relative identifier (RID), 30
+<BR>remote announce option (smb.conf file), 232, 238, 434
+<BR>remote browse sync option (smb.conf file), 238, 434
+<BR>remote logons (see roaming profiles)
+<BR>resolv.conf file, 73, 220
+<BR>resource names and types (NetBIOS), 14
+<BR>restrict anonymous option (smb.conf file), 434
+<BR>roaming profiles, 120, 140-152
+<BR> &nbsp; &nbsp; &nbsp;   changing to mandatory profiles, 150
+<BR> &nbsp; &nbsp; &nbsp;   configuring
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Samba for, 143-147
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 95/98/Me for, 147
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows NT/2000/XP for, 148
+<BR> &nbsp; &nbsp; &nbsp;   defining a logon path for Windows NT/2000/XP clients, 124
+<BR> &nbsp; &nbsp; &nbsp;   definitive documentation, 141
+<BR> &nbsp; &nbsp; &nbsp;   how they work, 141
+<BR> &nbsp; &nbsp; &nbsp;   options, 150
+<BR> &nbsp; &nbsp; &nbsp;   possible problems, 142
+<BR> &nbsp; &nbsp; &nbsp;   restricting users from editing their own, 149
+<BR> &nbsp; &nbsp; &nbsp;   setting path to directory (Windows NT/2000/XP), 420
+<BR> &nbsp; &nbsp; &nbsp;   smb.conf file, 138
+<BR> &nbsp; &nbsp; &nbsp;   Temporary Internet Files folder, 143
+<BR> &nbsp; &nbsp; &nbsp;   time synchronization, 339
+<BR> &nbsp; &nbsp; &nbsp;   users logged onto multiple clients, 142
+<BR> &nbsp; &nbsp; &nbsp;   warning, 141
+<BR> &nbsp; &nbsp; &nbsp;   (see also mandatory profiles)
+<BR>root access, 285
+<BR>root accounts
+<BR> &nbsp; &nbsp; &nbsp;   adding root user to Samba's password database, 126
+<BR> &nbsp; &nbsp; &nbsp;   (see also domain administrator)
+<BR> &nbsp; &nbsp; &nbsp;   specifying users with root permissions, 402
+<BR>root dir option (smb.conf file), 435
+<BR>root directory option (smb.conf file), 435
+<BR>root option (smb.conf file), 435
+<BR>root postexec option (smb.conf file), 277, 435
+<BR>root preexec close option (smb.conf file), 276, 435
+<BR>root preexec option (smb.conf file), 275, 276, 435
+<BR>roving profiles (see roaming profiles)
+<BR>rpcclient commands, 467-470
+<BR>rpcclient program, 40, 465
+<BR>rpm command (Unix), 43
+<P><A NAME="S"><B>S</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%S variable, 192
+<BR>SAM (Security Account Manager), 30
+<BR> &nbsp; &nbsp; &nbsp;   database, 126
+<BR>Samba
+<BR> &nbsp; &nbsp; &nbsp;   advantages of using, 3
+<BR> &nbsp; &nbsp; &nbsp;   allowing outside applications to access Samba features, 496
+<BR> &nbsp; &nbsp; &nbsp;   compiling (see compiling Samba)
+<BR> &nbsp; &nbsp; &nbsp;   configuration file (see smb.conf file)
+<BR> &nbsp; &nbsp; &nbsp;   configuring (see configuring Samba)
+<BR> &nbsp; &nbsp; &nbsp;   defined, 2
+<BR> &nbsp; &nbsp; &nbsp;   distribution, overview, 39
+<BR> &nbsp; &nbsp; &nbsp;   as domain member server, 34
+<BR> &nbsp; &nbsp; &nbsp;   downloading, 45
+<BR> &nbsp; &nbsp; &nbsp;   examples
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      sharing a printer, 8
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      sharing disk service, 4-7
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      simple network, 4
+<BR> &nbsp; &nbsp; &nbsp;   in a clustered environment, 437
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      (see also multihomed system; multiple subnets), 437
+<BR> &nbsp; &nbsp; &nbsp;   installing (see installing Samba)
+<BR> &nbsp; &nbsp; &nbsp;   manual pages, 52
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      in different languages, 496
+<BR> &nbsp; &nbsp; &nbsp;   obtaining, 41
+<BR> &nbsp; &nbsp; &nbsp;   overview, 1-41
+<BR> &nbsp; &nbsp; &nbsp;   running on a multihomed system, 204
+<BR> &nbsp; &nbsp; &nbsp;   troubleshooting (see troubleshooting Samba)
+<BR> &nbsp; &nbsp; &nbsp;   upgrading installations, 51
+<BR> &nbsp; &nbsp; &nbsp;   variables (see smb.conf file, variables)
+<BR> &nbsp; &nbsp; &nbsp;   web site, 41
+<BR>Samba 2.2
+<BR> &nbsp; &nbsp; &nbsp;   in a domain hosted by native mode Windows 2000 server, 34
+<BR> &nbsp; &nbsp; &nbsp;   issues with Active Directory, 34, 121
+<BR> &nbsp; &nbsp; &nbsp;   new features, 36
+<BR>Samba 3.0
+<BR> &nbsp; &nbsp; &nbsp;   new features, 38
+<BR> &nbsp; &nbsp; &nbsp;   obsolete options
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      blocksize, 404
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      character set, 405
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      client code page, 405
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      code page directory, 405
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      coding system, 405
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      domain guest group, 410
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      force unknown acl user, 413
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap admin dn, 417
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap filter, 417
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap port, 417
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap server, 418
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap ssl, 418
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ldap suffix, 418
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      nt smb support, 427
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      related to SSL, 438-440
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      status, 440
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      unix extensions, 442
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      userhosts, 443
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      valid chars, 444
+<BR> &nbsp; &nbsp; &nbsp;   roles, 38
+<BR>Samba server
+<BR> &nbsp; &nbsp; &nbsp;   adding to workgroup, configuration file example, 396
+<BR> &nbsp; &nbsp; &nbsp;   connecting from
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 2000, 107
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 95/98/Me, 84
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows NT, 96
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows XP, 116
+<BR> &nbsp; &nbsp; &nbsp;   connection listings (see smbstatus program)
+<BR> &nbsp; &nbsp; &nbsp;   creating directories on, 125
+<BR> &nbsp; &nbsp; &nbsp;   restarting, 126
+<BR> &nbsp; &nbsp; &nbsp;   sending a print job, 321
+<BR> &nbsp; &nbsp; &nbsp;   services, 2
+<BR>Samba Web Administration Tool (see SWAT)
+<BR>Samba-BDC-HOWTO.html, 122
+<BR>Samba-PDC-HOWTO.html, 122
+<BR>Samba's NT LM 0.12, 21
+<BR>SASL (Simple Authentication and Security Layer) standard, 504
+<BR>--sbindir (configure script option), 48
+<BR>scope ID (SMB packet), 16
+<BR>search paths, setting, 52
+<BR>secrets.tdb file, 156
+<BR>security
+<BR> &nbsp; &nbsp; &nbsp;   Samba security levels
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      domain (see domain-level security)
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      server (see server-level security)
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      share (see share-level security)
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      user (see user-level security)
+<BR> &nbsp; &nbsp; &nbsp;   user-level for Windows 95/98/Me, 129
+<BR> &nbsp; &nbsp; &nbsp;   (see also authentication)
+<BR>Security Access Token (SAT), 31
+<BR>Security Account Manager (SAM), 30
+<BR>security identifiers (SIDs), 30
+<BR>security issues
+<BR> &nbsp; &nbsp; &nbsp;   creating entries for /etc/passwd and smbpasswd manually, 127
+<BR> &nbsp; &nbsp; &nbsp;   disabling oplocks in smb.conf file, 58
+<BR>security mask option (smb.conf file), 261, 436
+<BR>security models, Unix versus Windows, 253
+<BR>security option (smb.conf file), 291, 436
+<BR>sendfile( ) system call, 497
+<BR>server announcements, 229
+<BR>Server Message Block (SMB) protocol (see SMB)
+<BR>server string option (smb.conf file), 200, 436
+<BR>server-level security, 291, 295
+<BR>session parameters, setting, 24
+<BR>session primitives, 17
+<BR>session service, defined, 10
+<BR>session services (NBT)
+<BR> &nbsp; &nbsp; &nbsp;   defined, 16
+<BR> &nbsp; &nbsp; &nbsp;   tips, 18
+<BR>set directory option (smb.conf file), 353, 436
+<BR>share modes option (smb.conf file), 436
+<BR>share-level security, 290
+<BR> &nbsp; &nbsp; &nbsp;   options, 293
+<BR> &nbsp; &nbsp; &nbsp;   versus user-level security, 162
+<BR>shares
+<BR> &nbsp; &nbsp; &nbsp;   adding new, 402
+<BR> &nbsp; &nbsp; &nbsp;   allowing and denying, 415
+<BR> &nbsp; &nbsp; &nbsp;   copying configurations, 406
+<BR> &nbsp; &nbsp; &nbsp;   deleting, 408
+<BR> &nbsp; &nbsp; &nbsp;   denying access to, 403
+<BR> &nbsp; &nbsp; &nbsp;   invisible, 233
+<BR> &nbsp; &nbsp; &nbsp;   managing connections to (see connection scripts)
+<BR> &nbsp; &nbsp; &nbsp;   modifying, 405
+<BR> &nbsp; &nbsp; &nbsp;   printers, setting default device mode, 408
+<BR> &nbsp; &nbsp; &nbsp;   sections in smb.conf file, 125
+<BR> &nbsp; &nbsp; &nbsp;   setting maximum number, 423
+<BR> &nbsp; &nbsp; &nbsp;   specifying in browse lists, 403, 404, 431
+<BR> &nbsp; &nbsp; &nbsp;   specifying systems that may connect to, 403
+<BR>sharing
+<BR> &nbsp; &nbsp; &nbsp;   disk services example, 4-7
+<BR> &nbsp; &nbsp; &nbsp;   files
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Mac OS X, 501
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 95/98/Me, 162
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows NT/2000/XP, 163, 165
+<BR> &nbsp; &nbsp; &nbsp;   printers (see printers, sharing)
+<BR>Sharpe, Richard, 19
+<BR>short preserve case option (smb.conf file), 264, 266, 436
+<BR>show add printer wizard option (smb.conf file), 437
+<BR>shutdown script option (smb.conf file), 437
+<BR>SIDs (security identifiers), 30
+<BR>SMB, 2
+<BR> &nbsp; &nbsp; &nbsp;   CIFS and, 21
+<BR> &nbsp; &nbsp; &nbsp;   clients, 21
+<BR> &nbsp; &nbsp; &nbsp;   command format, 19
+<BR> &nbsp; &nbsp; &nbsp;   connections, troubleshooting, 371-377
+<BR> &nbsp; &nbsp; &nbsp;   groups, 15
+<BR> &nbsp; &nbsp; &nbsp;   header fields, 19
+<BR> &nbsp; &nbsp; &nbsp;   header format, 19
+<BR> &nbsp; &nbsp; &nbsp;   message format, 19
+<BR> &nbsp; &nbsp; &nbsp;   network, overview, 9-18
+<BR> &nbsp; &nbsp; &nbsp;   online summary, 19
+<BR> &nbsp; &nbsp; &nbsp;   packets, 16
+<BR> &nbsp; &nbsp; &nbsp;   protocol
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      additional information, 20
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      negotiating a protocol variant, 22
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      overview, 18-26
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      versions, 20
+<BR> &nbsp; &nbsp; &nbsp;   servers, 21
+<BR> &nbsp; &nbsp; &nbsp;   simple connection, 22
+<BR>smb passwd file option (smb.conf file), 306, 437
+<BR>SMB sniffer (Ethereal), 20
+<BR>smbcacls program, 40, 470
+<BR>smbclient commands, 168
+<BR>smbclient program, 40, 67, 161, 165-174, 472-478
+<BR> &nbsp; &nbsp; &nbsp;   authenticating with, 167
+<BR> &nbsp; &nbsp; &nbsp;   compared to smbfs and smbsh, 165
+<BR> &nbsp; &nbsp; &nbsp;   creating and restoring backups, 172-174
+<BR> &nbsp; &nbsp; &nbsp;   file transfer, 170
+<BR> &nbsp; &nbsp; &nbsp;   interactive session, 168-171
+<BR> &nbsp; &nbsp; &nbsp;   listing services, 165
+<BR> &nbsp; &nbsp; &nbsp;   programming with, 171
+<BR> &nbsp; &nbsp; &nbsp;   security and, 168
+<BR> &nbsp; &nbsp; &nbsp;   sending a file to the printer, 325
+<BR> &nbsp; &nbsp; &nbsp;   testing
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      browsing, 377
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connections with, 373
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      locally with, 372
+<BR>smb.conf file, 187-215
+<BR> &nbsp; &nbsp; &nbsp;   adding user passwords, 75
+<BR> &nbsp; &nbsp; &nbsp;   bracketed names, 188
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      (see also shares, sections in smb.conf file)
+<BR> &nbsp; &nbsp; &nbsp;   capitalization, 189
+<BR> &nbsp; &nbsp; &nbsp;   comments, 190
+<BR> &nbsp; &nbsp; &nbsp;   configuring winbind, 309
+<BR> &nbsp; &nbsp; &nbsp;   creating and modifying (see SWAT)
+<BR> &nbsp; &nbsp; &nbsp;   disabling oplocks, 58
+<BR> &nbsp; &nbsp; &nbsp;   encrypted passwords and, 55
+<BR> &nbsp; &nbsp; &nbsp;   examples, 187
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      configuring Samba to use another WINS server, 396
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      disk share, 201-203
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      enabling Samba as WINS server, 395
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      server configuration file, 198-201
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting Samba as domain member server, 400
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting Samba as PDC, 397-399
+<BR> &nbsp; &nbsp; &nbsp;   file structure, 188-191
+<BR> &nbsp; &nbsp; &nbsp;   getting started, 54-60
+<BR> &nbsp; &nbsp; &nbsp;   [global] section, 193
+<BR> &nbsp; &nbsp; &nbsp;   include option, 193
+<BR> &nbsp; &nbsp; &nbsp;   line continuation, 189
+<BR> &nbsp; &nbsp; &nbsp;   location from bundled installation, 42
+<BR> &nbsp; &nbsp; &nbsp;   logon scripts (see logon scripts)
+<BR> &nbsp; &nbsp; &nbsp;   Mac OS X, 509
+<BR> &nbsp; &nbsp; &nbsp;   making significant changes, 190
+<BR> &nbsp; &nbsp; &nbsp;   modifying Samba to be a PDC, 122-125
+<BR> &nbsp; &nbsp; &nbsp;   modifying Samba to be domain member server, 157
+<BR> &nbsp; &nbsp; &nbsp;   name resolution, 219
+<BR> &nbsp; &nbsp; &nbsp;   options, 188, 195-198
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      access control, 287-288
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ACLs, 260-262
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      browsing, 233-239
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connection scripts, 275-277
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      disk share, 202
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      dot files, 240
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      file and directory permissions, 250-253
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      filesystem, 243-245
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      internationalization, 343-346
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      locks and oplocks, 270-274
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      logging, 210-215
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      name mangling, 265-267
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      name resolution, 221-224
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      networking, 204-208
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      NIS, 280
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      password, 303-307
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      printing, 333-338
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      server, 199
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      time synchronization, 341-342
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      virtual servers, 209
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      winbind, 317-319
+<BR> &nbsp; &nbsp; &nbsp;   [printers] section, 195
+<BR> &nbsp; &nbsp; &nbsp;   roaming profiles, 138
+<BR> &nbsp; &nbsp; &nbsp;   runtime changes, 190
+<BR> &nbsp; &nbsp; &nbsp;   shares, 125, 194
+<BR> &nbsp; &nbsp; &nbsp;   smbmount program and, 174
+<BR> &nbsp; &nbsp; &nbsp;   smbsh and, 179
+<BR> &nbsp; &nbsp; &nbsp;   testing, 59
+<BR> &nbsp; &nbsp; &nbsp;   variables, 191-193
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      example of use, 193
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      table, 192
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      used at runtime, 140
+<BR> &nbsp; &nbsp; &nbsp;   WINS support, 71
+<BR>smbcontrol program, 40, 478
+<BR>smbd daemon, 3, 39, 61, 451
+<BR> &nbsp; &nbsp; &nbsp;   checking with telnet, 369
+<BR> &nbsp; &nbsp; &nbsp;   starting automatically, 61-65
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      BSD Unix, 61
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Darwin and Mac OS X, 64
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      System V Unix, 61
+<BR> &nbsp; &nbsp; &nbsp;   starting from inetd, 66
+<BR> &nbsp; &nbsp; &nbsp;   starting manually, 61
+<BR> &nbsp; &nbsp; &nbsp;   testing, 66
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      automatic startup, 65
+<BR>smbfs filesystem, 161, 174-178
+<BR> &nbsp; &nbsp; &nbsp;   compared to smbclient, 165
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 498
+<BR> &nbsp; &nbsp; &nbsp;   mounting automatically, 177
+<BR>smbgroupedit program, 40, 479
+<BR>smbmnt program, 40, 174, 480
+<BR>smbmount program, 40, 175, 481
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 498
+<BR> &nbsp; &nbsp; &nbsp;   options, 178
+<BR> &nbsp; &nbsp; &nbsp;   smb.conf file, 174
+<BR>SMBnegprot request, 23
+<BR>smbpasswd file, 126, 299-300
+<BR> &nbsp; &nbsp; &nbsp;   creating entries manually, 127
+<BR>smbpasswd program, 41, 55, 483
+<BR>smbprint program, 330
+<BR>smbprint.sysv, 330
+<BR>SMBSesssetupX command, 24
+<BR>smbsh program, 41, 161, 179, 485
+<BR> &nbsp; &nbsp; &nbsp;   compared to smbclient, 165
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba with support for, 498
+<BR> &nbsp; &nbsp; &nbsp;   interactive session, 179
+<BR> &nbsp; &nbsp; &nbsp;   smb.conf file, 179
+<BR>smbspool, 330
+<BR>smbspool program, 41, 486
+<BR>smbspool utility, 332
+<BR>smbstatus program, 8, 41, 487
+<BR>smbtar program, 41, 487
+<BR>SMBtconX message, 25
+<BR>smbumount program, 41, 488
+<BR>smbutil program, 161, 181
+<BR> &nbsp; &nbsp; &nbsp;   options, 183
+<BR> &nbsp; &nbsp; &nbsp;   testing print configuration, 326
+<BR>smbwrapper library, 179, 498
+<BR>socket address option (smb.conf file), 437
+<BR>socket options option (smb.conf file), 437
+<BR>source environment option (smb.conf file), 437
+<BR>source/config.status file, 51
+<BR>spin locks, 498
+<BR>SSL
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba to support, 498
+<BR> &nbsp; &nbsp; &nbsp;   options, 438-440
+<BR>ssl CA certDir option (smb.conf file), 438
+<BR>ssl CA certFile option (smb.conf file), 438
+<BR>ssl ciphers option (smb.conf file), 438
+<BR>ssl client cert option (smb.conf file), 438
+<BR>ssl client key option (smb.conf file), 438
+<BR>ssl compatibility option (smb.conf file), 439
+<BR>ssl hosts option (smb.conf file), 439
+<BR>ssl hosts resign option (smb.conf file), 439
+<BR>ssl option (smb.conf file), 438
+<BR>ssl require clientcert option (smb.conf file), 439
+<BR>ssl require servercert option (smb.conf file), 439
+<BR>ssl server cert option (smb.conf file), 439
+<BR>ssl server key option (smb.conf file), 440
+<BR>ssl version option (smb.conf file), 440
+<BR>stat cache option (smb.conf file), 354, 440
+<BR>stat cache size option (smb.conf file), 354, 440
+<BR>status option (smb.conf file), 440
+<BR>status (smb.conf file), 353
+<BR>Stern, Hal, 383
+<BR>strace command, 359
+<BR>strict allocate option (smb.conf file), 440
+<BR>strict locking option (smb.conf file), 271, 441
+<BR>strict sync option (smb.conf file), 353, 441
+<BR>strip dot option (smb.conf file), 353, 441
+<BR>subnets, workgroups spanning multiple, 34
+<BR>superuser (root) access, 285
+<BR>SWAT
+<BR> &nbsp; &nbsp; &nbsp;   enabling, 52
+<BR> &nbsp; &nbsp; &nbsp;   login, 56
+<BR> &nbsp; &nbsp; &nbsp;   specifying where to install files for, 498
+<BR> &nbsp; &nbsp; &nbsp;   using, 56-58
+<BR>symbolic links, 242
+<BR> &nbsp; &nbsp; &nbsp;   creating before clients are added to network, 147
+<BR> &nbsp; &nbsp; &nbsp;   in file shares, 412
+<BR>symlinks option (smb.conf file), 242
+<BR>sync always option (smb.conf file), 353, 441
+<BR>synchronization, password (see passwords, synchronization)
+<BR>synchronization problems with WINS servers in Samba, 33, 71
+<BR>syslog, 211
+<BR> &nbsp; &nbsp; &nbsp;   error logging, installing Samba to support, 498
+<BR>syslog only option (smb.conf file), 215, 441
+<BR>syslog option (smb.conf file), 214, 441
+<BR>syslog.conf file, 212
+<BR>system group file, 283
+<BR>system policies, 152-156
+<BR> &nbsp; &nbsp; &nbsp;   Windows Me, 155
+<BR>System Policy Editor, 152-156
+<BR>System V Unix
+<BR> &nbsp; &nbsp; &nbsp;   automatically starting Samba daemons, 61
+<BR> &nbsp; &nbsp; &nbsp;   printers, 331
+
+<P><A NAME="T"><B>T</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%T variable, 192
+<BR>TCP, troubleshooting, 367
+<BR>tcpdump program, 360
+<BR> &nbsp; &nbsp; &nbsp;   download, 22
+<BR> &nbsp; &nbsp; &nbsp;   example, 22
+<BR>TCP/IP
+<BR> &nbsp; &nbsp; &nbsp;   adding to Windows 95/98/Me network, 76
+<BR> &nbsp; &nbsp; &nbsp;   configuring for Windows 2000, 100
+<BR> &nbsp; &nbsp; &nbsp;   configuring for Windows 95/98/Me, 78
+<BR> &nbsp; &nbsp; &nbsp;   configuring for Windows NT, 89
+<BR> &nbsp; &nbsp; &nbsp;   configuring for Windows XP, 110
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 88
+<BR>telnet, checking smbd with, 369
+<BR>template homedir option (smb.conf file), 314, 319, 441
+<BR>template shell option (smb.conf file), 314, 319, 442
+<BR>Temporary Internet Files folder, 143
+<BR>test utilities, troubleshooting with, 359-362
+<BR>testing Samba (see testparm program; troubleshooting Samba)
+<BR>testparm program, 41, 59, 125, 489
+<BR> &nbsp; &nbsp; &nbsp;   testing daemons with, 370
+<BR>testprns program, 41, 489
+<BR>Thompson, Robert Bruce, 87
+<BR>time offset option (smb.conf file), 341, 442
+<BR>time server option (smb.conf file), 341, 442
+<BR>time service, 340
+<BR> &nbsp; &nbsp; &nbsp;   configuring in Samba for network use, 124
+<BR>time synchronization, 339-342
+<BR>time to live (TTL), 424, 425
+<BR>timestamp logs option (smb.conf file), 214, 442
+<BR>timestamps
+<BR> &nbsp; &nbsp; &nbsp;   changing in logs, 407
+<BR> &nbsp; &nbsp; &nbsp;   importance of, 142
+<BR>time-synchronization options, 341-342
+<BR>total print jobs option (smb.conf file), 442
+<BR>trace command, 359
+<BR>translating between IP addresses or DNS names and NetBIOS names, 182
+<BR>tree identifier (TID), defined, 22
+<BR>Tridgell, Andrew, 2, 360
+<BR>troubleshooting Samba, 355-393
+<BR> &nbsp; &nbsp; &nbsp;   browsing, 377-383
+<BR> &nbsp; &nbsp; &nbsp;   fault tree, 362-391
+<BR> &nbsp; &nbsp; &nbsp;   hostnames, 384
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      long and short, 386
+<BR> &nbsp; &nbsp; &nbsp;   localhost issues, 388
+<BR> &nbsp; &nbsp; &nbsp;   low-level IP, 362-367
+<BR> &nbsp; &nbsp; &nbsp;   name services, 383-388
+<BR> &nbsp; &nbsp; &nbsp;   NetBIOS names, 390
+<BR> &nbsp; &nbsp; &nbsp;   network addresses, 388-390
+<BR> &nbsp; &nbsp; &nbsp;   server daemons, 368-371
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      checking smbd with telnet, 369
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      looking for daemon processes with ps, 368
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      looking for daemons bound to ports, 369
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      testing daemons with testparm, 370
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      tracking daemon startup, 368
+<BR> &nbsp; &nbsp; &nbsp;   SMB connections, 371-377
+<BR> &nbsp; &nbsp; &nbsp;   TCP, 367
+<BR> &nbsp; &nbsp; &nbsp;   testing
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      browsing the server from the client, 382
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      browsing with smbclient, 377
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      client browsing with net view, 381
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      clients with nmblookup, 380
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connections with net use, 374
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connections with ping, 364
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connections with smbclient, 373
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      connections with Windows Explorer, 376
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      locally with smbclient, 372
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      name services with ping, 363
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      network software with ping, 363
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      network with nmblookup, 381
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      networking hardware with ping, 364
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      servers with nmblookup, 379
+<BR> &nbsp; &nbsp; &nbsp;   tools, 355
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      log files, 356-359
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      ping, 363-367
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      test utilities, 359-362
+<BR> &nbsp; &nbsp; &nbsp;   unusual delays, 387
+<BR>truss command, 359
+<BR>trust relationships, 33
+<BR>trusted domains, 403
+<BR>tusc command, 359
+<BR>tutorials, Samba, 45
+<P><A NAME="U"><B>U</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%U variable, 192, 283
+<BR>%u variable, 140, 144, 192, 283
+<BR>umasks, 247
+<BR>UNC (Universal Naming Convention) defined, 6
+<BR>Unicode, 456
+<BR>uniform resource locators (see URLs)
+<BR>Unix
+<BR> &nbsp; &nbsp; &nbsp;   ACLs, 259
+<BR> &nbsp; &nbsp; &nbsp;   CIFS extensions, 37
+<BR> &nbsp; &nbsp; &nbsp;   configuring clients to access shared resources, 161-186
+<BR> &nbsp; &nbsp; &nbsp;   file permissions, 245-253
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      versus ACLs, 31
+<BR> &nbsp; &nbsp; &nbsp;   permission bits summary, 247
+<BR> &nbsp; &nbsp; &nbsp;   viewing processes, 8
+<BR>unix extensions option (smb.conf file), 442
+<BR>unix password sync option (smb.conf file), 300, 304, 442
+<BR>unix2dos program, 139, 170
+<BR>update encrypted option (smb.conf file), 306, 443
+<BR>upgrading Samba, 50, 51
+<BR>URLs, defined, 6
+<BR>use client driver option (smb.conf file), 443
+<BR>use mmap option (smb.conf file), 443
+<BR>use rhosts option (smb.conf file), 307, 443
+<BR>use sendfile option (smb.conf file), 443
+<BR>user accounting, 498
+<BR>USER environment variable, 167
+<BR>user ID (UID), 31
+<BR>user option (smb.conf file), 443
+<BR>USER.DAT file, 141
+<BR>user-level security, 290, 294
+<BR> &nbsp; &nbsp; &nbsp;   for Windows 95/98/Me, 129
+<BR> &nbsp; &nbsp; &nbsp;   versus share-level security, 162
+<BR>username level option (smb.conf file), 290, 444
+<BR>username map option (smb.conf file), 289, 444
+<BR>username option (smb.conf file), 293, 443
+<BR>users
+<BR> &nbsp; &nbsp; &nbsp;   account files in Windows, 29
+<BR> &nbsp; &nbsp; &nbsp;   adding new, 402
+<BR> &nbsp; &nbsp; &nbsp;   adding to
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 2000, 104
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows 95/98/Me, 83
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows NT, 95
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      Windows XP, 115
+<BR> &nbsp; &nbsp; &nbsp;   debugging particular, 407
+<BR> &nbsp; &nbsp; &nbsp;   deleting account automatically, 409
+<BR> &nbsp; &nbsp; &nbsp;   group membership, overriding, 413
+<BR> &nbsp; &nbsp; &nbsp;   multiple, adding in Unix, 284-285
+<BR> &nbsp; &nbsp; &nbsp;   single, adding in Unix, 282-284
+<BR> &nbsp; &nbsp; &nbsp;   specifying read-only access, 433
+<BR>users option (smb.conf file), 444
+<BR>/usr/local/etc/nsmb.conf file, 181
+<BR>utmp directory option (smb.conf file), 444
+<BR>utmp file, 498
+<BR>utmp option (smb.conf file), 444
+<P><A NAME="V"><B>V</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>%v variable, 192
+<BR>valid chars option (smb.conf file), 346, 444
+<BR>valid users option (smb.conf file), 282, 287, 444
+<BR>variables used at runtime in smb.conf file (see smb.conf file, variables)
+<BR>veto files option (smb.conf file), 241, 244, 445
+<BR>veto oplock files option (smb.conf file), 269, 270, 273, 445
+<BR>vetoing files, 240-242
+<BR>vfs object option (smb.conf file), 445
+<BR>vfs options option (smb.conf file), 445
+<BR>vi text editor, 139
+<BR>vim text editor, 139
+<BR>virtual servers, 208
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 209
+<BR>volume option (smb.conf file), 203, 445
+<BR>VPN (virtual private network), 498
+
+<P><A NAME="W"><B>W</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>wbinfo program, 41, 489
+<BR>wide links option (smb.conf file), 242, 244, 445
+<BR>winbind, 37
+<BR> &nbsp; &nbsp; &nbsp;   authentication with, 307-319
+<BR> &nbsp; &nbsp; &nbsp;   configuration options, 317-319
+<BR> &nbsp; &nbsp; &nbsp;   configuring in smb.conf file, 309
+<BR> &nbsp; &nbsp; &nbsp;   installing, 308
+<BR> &nbsp; &nbsp; &nbsp;   installing Samba to support, 499
+<BR> &nbsp; &nbsp; &nbsp;   RID mapping file, 310
+<BR> &nbsp; &nbsp; &nbsp;   verifying it's working properly, 310-313
+<BR>winbind cache time option (smb.conf file), 319, 445
+<BR>winbind enum groups option (smb.conf file), 446
+<BR>winbind enum users option (smb.conf file), 445
+<BR>winbind gid option (smb.conf file), 318, 446
+<BR>winbind separator option (smb.conf file), 317, 446
+<BR>winbind uid option (smb.conf file), 318, 446
+<BR>winbindd daemon, 39, 41, 454
+<BR>Windows
+<BR> &nbsp; &nbsp; &nbsp;   components, 69
+<BR> &nbsp; &nbsp; &nbsp;   configuring clients to access shared resources, 68-119
+<BR> &nbsp; &nbsp; &nbsp;   domain with a local master and local backup browser (diagram), 33
+<BR> &nbsp; &nbsp; &nbsp;   .ini files, 187
+<BR> &nbsp; &nbsp; &nbsp;   networking concepts, 68-76
+<BR> &nbsp; &nbsp; &nbsp;   operating systems and password format defaults, 296
+<BR> &nbsp; &nbsp; &nbsp;   printers, setting up, 8
+<BR> &nbsp; &nbsp; &nbsp;   registry settings and passwords, 74
+<BR> &nbsp; &nbsp; &nbsp;   user account files, 29
+<BR>Windows 2000
+<BR> &nbsp; &nbsp; &nbsp;   ACLs, 253-262
+<BR> &nbsp; &nbsp; &nbsp;   adding users, 104
+<BR> &nbsp; &nbsp; &nbsp;   bindings, 100
+<BR> &nbsp; &nbsp; &nbsp;   client connecting to Samba server, 107
+<BR> &nbsp; &nbsp; &nbsp;   computer names, 103
+<BR> &nbsp; &nbsp; &nbsp;   configuring for roaming profiles, 148
+<BR> &nbsp; &nbsp; &nbsp;   configuring TCP/IP, 100
+<BR> &nbsp; &nbsp; &nbsp;   DNS configuration, 101
+<BR> &nbsp; &nbsp; &nbsp;   domain logons, 133-135
+<BR> &nbsp; &nbsp; &nbsp;   identify node type, ipconfig /all command, 13
+<BR> &nbsp; &nbsp; &nbsp;   IP addresses, 100
+<BR> &nbsp; &nbsp; &nbsp;   LMHOSTS file, 102
+<BR> &nbsp; &nbsp; &nbsp;   networking components, 99
+<BR> &nbsp; &nbsp; &nbsp;   registry file, 141
+<BR> &nbsp; &nbsp; &nbsp;   security model (see ACLs)
+<BR> &nbsp; &nbsp; &nbsp;   servers
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      operating in native mode, 34
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      PDC emulation mode, 34
+<BR> &nbsp; &nbsp; &nbsp;   setting path to directory of roaming profiles, 420
+<BR> &nbsp; &nbsp; &nbsp;   setting up, 98-108
+<BR> &nbsp; &nbsp; &nbsp;   sharing files, 163
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting permissions, 165
+<BR> &nbsp; &nbsp; &nbsp;   WINS server, 101
+<BR> &nbsp; &nbsp; &nbsp;   workgroups, 103
+<BR>Windows 95/98/Me
+<BR> &nbsp; &nbsp; &nbsp;   accessing Samba server, 84
+<BR> &nbsp; &nbsp; &nbsp;   adding TCP/IP, 76
+<BR> &nbsp; &nbsp; &nbsp;   authentication, 28
+<BR> &nbsp; &nbsp; &nbsp;   bindings, 80
+<BR> &nbsp; &nbsp; &nbsp;   configuring for roaming profiles, 147
+<BR> &nbsp; &nbsp; &nbsp;   configuring TCP/IP, 78
+<BR> &nbsp; &nbsp; &nbsp;   DNS configuration, 79
+<BR> &nbsp; &nbsp; &nbsp;   domain logons, 128-131
+<BR> &nbsp; &nbsp; &nbsp;   identify node type, 13
+<BR> &nbsp; &nbsp; &nbsp;   IP addresses, 78
+<BR> &nbsp; &nbsp; &nbsp;   LMHOSTS file, 80
+<BR> &nbsp; &nbsp; &nbsp;   NetBIOS, 80
+<BR> &nbsp; &nbsp; &nbsp;   registry file, 141
+<BR> &nbsp; &nbsp; &nbsp;   security model, 253
+<BR> &nbsp; &nbsp; &nbsp;   setting computer name, 81
+<BR> &nbsp; &nbsp; &nbsp;   setting up, 76-87
+<BR> &nbsp; &nbsp; &nbsp;   setting workgroup, 81
+<BR> &nbsp; &nbsp; &nbsp;   sharing files, 162
+<BR> &nbsp; &nbsp; &nbsp;   system policies, 155
+<BR> &nbsp; &nbsp; &nbsp;   user-level security for, 129
+<BR> &nbsp; &nbsp; &nbsp;   username and password, 83
+<BR> &nbsp; &nbsp; &nbsp;   WINS configuration, 78
+<BR> &nbsp; &nbsp; &nbsp;   (see also Windows)
+<BR>Windows Explorer, testing connections with, 376
+<BR>Windows Internet Name Service (see WINS)
+<BR>Windows Internet Naming Service (WINS) Architecture and Capacity Planning, 218
+<BR>Windows Messenger Service, 346-348
+<BR>Windows NT
+<BR> &nbsp; &nbsp; &nbsp;   ACLs, 253-262
+<BR> &nbsp; &nbsp; &nbsp;   adding a user, 95
+<BR> &nbsp; &nbsp; &nbsp;   basic configuration, 87
+<BR> &nbsp; &nbsp; &nbsp;   bindings, 93
+<BR> &nbsp; &nbsp; &nbsp;   computer names, 93
+<BR> &nbsp; &nbsp; &nbsp;   configuring for roaming profiles, 148
+<BR> &nbsp; &nbsp; &nbsp;   configuring TCP/IP, 89
+<BR> &nbsp; &nbsp; &nbsp;   connecting to a Samba server, 96
+<BR> &nbsp; &nbsp; &nbsp;   DNS configuration, 92
+<BR> &nbsp; &nbsp; &nbsp;   domains, 120-160
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      logons, 131-133
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      overview, 29-34
+<BR> &nbsp; &nbsp; &nbsp;   identify node type, ipconfig /all command, 13
+<BR> &nbsp; &nbsp; &nbsp;   installing Workstation service, 89
+<BR> &nbsp; &nbsp; &nbsp;   IP addresses, 90
+<BR> &nbsp; &nbsp; &nbsp;   LMHOSTS file, 92
+<BR> &nbsp; &nbsp; &nbsp;   registry file, 141
+<BR> &nbsp; &nbsp; &nbsp;   security model, 30
+<BR> &nbsp; &nbsp; &nbsp;   security model (see ACLs)
+<BR> &nbsp; &nbsp; &nbsp;   setting path to directory of roaming profiles, 420
+<BR> &nbsp; &nbsp; &nbsp;   setting up, 87-98
+<BR> &nbsp; &nbsp; &nbsp;   sharing files, 163
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting permissions, 165
+<BR> &nbsp; &nbsp; &nbsp;   TCP/IP installing, 88
+<BR> &nbsp; &nbsp; &nbsp;   WINS server, 90
+<BR> &nbsp; &nbsp; &nbsp;   workgroups, 93
+<BR>Windows NT domain options, 158
+<BR>Windows Time Service, 340
+<BR>Windows Workgroups (see workgroups)
+<BR>Windows XP
+<BR> &nbsp; &nbsp; &nbsp;   ACLs, 253-262
+<BR> &nbsp; &nbsp; &nbsp;   adding users, 115
+<BR> &nbsp; &nbsp; &nbsp;   bindings, 110
+<BR> &nbsp; &nbsp; &nbsp;   computer names, 113
+<BR> &nbsp; &nbsp; &nbsp;   configuring for roaming profiles, 148
+<BR> &nbsp; &nbsp; &nbsp;   configuring TCP/IP, 110
+<BR> &nbsp; &nbsp; &nbsp;   connecting to Samba server, 116
+<BR> &nbsp; &nbsp; &nbsp;   DNS configuration, 111
+<BR> &nbsp; &nbsp; &nbsp;   domain logons, 135-137
+<BR> &nbsp; &nbsp; &nbsp;   Home version, problems in a domain environment, 135
+<BR> &nbsp; &nbsp; &nbsp;   identify node type, ipconfig /all command, 13
+<BR> &nbsp; &nbsp; &nbsp;   IP addresses, 111
+<BR> &nbsp; &nbsp; &nbsp;   LMHOSTS file, 112
+<BR> &nbsp; &nbsp; &nbsp;   networking components, 109
+<BR> &nbsp; &nbsp; &nbsp;   registry file, 141
+<BR> &nbsp; &nbsp; &nbsp;   security model (see ACLs)
+<BR> &nbsp; &nbsp; &nbsp;   setting path to directory of roaming profiles, 420
+<BR> &nbsp; &nbsp; &nbsp;   setting up, 109-119
+<BR> &nbsp; &nbsp; &nbsp;   sharing files, 163
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      setting permissions, 165
+<BR> &nbsp; &nbsp; &nbsp;   WINS server, 112
+<BR> &nbsp; &nbsp; &nbsp;   workgroups, 113
+<BR>winipcfg command (Windows 95/98/Me), 13
+<BR>WinPopup tool, 346
+<BR>.win_profile directory, 144
+<BR> &nbsp; &nbsp; &nbsp;   example, 145
+<BR>WINS, 32
+<BR> &nbsp; &nbsp; &nbsp;   client and a server interaction, 218
+<BR> &nbsp; &nbsp; &nbsp;   configuration, Windows 95/98/Me, 78
+<BR> &nbsp; &nbsp; &nbsp;   proxy, configuring, 221
+<BR> &nbsp; &nbsp; &nbsp;   replication, 38
+<BR> &nbsp; &nbsp; &nbsp;   support, smb.conf file, 71
+<BR>wins hook option (smb.conf file), 223, 446
+<BR>wins proxy option (smb.conf file), 221, 222, 446
+<BR>wins server option (smb.conf file), 220, 222, 446
+<BR>WINS servers
+<BR> &nbsp; &nbsp; &nbsp;   configuring a DNS proxy, 220
+<BR> &nbsp; &nbsp; &nbsp;   configuring Samba to use another, 220
+<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;      configuration file example, 396
+<BR> &nbsp; &nbsp; &nbsp;   enabling Samba as, configuration file example, 395
+<BR> &nbsp; &nbsp; &nbsp;   multiple, 32
+<BR> &nbsp; &nbsp; &nbsp;   primary (see primary WINS server)
+<BR> &nbsp; &nbsp; &nbsp;   setting Samba as, 220
+<BR> &nbsp; &nbsp; &nbsp;   synchronization problems in Samba, 71
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 101
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 90
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 112
+<BR>wins support option (smb.conf file), 222, 447
+<BR>wins support parameter (smb.conf file), 220
+<BR>with feature option, configuring Samba, 47
+<BR>--with-acl-support (configure script option), 495
+<BR>--with-afs (configure script option), 495
+<BR>--with-automount (configure script option), 495
+<BR>--with-codepagedir (configure script option), 495
+<BR>--with-configdir (configure script option), 495
+<BR>--with-dce-dfs (configure script option), 495
+<BR>--with-fhs (configure script option), 495
+<BR>--with-included-popt (configure script option), 495
+<BR>--with-krb4 (configure script option), 495
+<BR>--with-krb5 (configure script option), 495
+<BR>--with-ldapsam (configure script option), 496
+<BR>--with-libiconv (configure script option), 496
+<BR>--with-libsmbclient (configure script option), 496
+<BR>--with-lockdir (configure script option), 496
+<BR>--with-logfilebase (configure script option), 496
+<BR>--with-manpages-langs (configure script option), 496
+<BR>--with-msdfs (configure script option), 47, 496
+<BR>--with-nisplus-home (configure script option), 496
+<BR>--with-nisplussam (configure script option), 496
+<BR>without feature option, configuring Samba, 47
+<BR>--with-pam (configure script option), 497
+<BR>--with-pam_smbpass (configure script option), 497
+<BR>--with-piddir (configure script option), 497
+<BR>--with-privatedir (configure script option), 497
+<BR>--with-profiling-data (configure script option), 497
+<BR>--with-quotas (configure script option), 497
+<BR>--with-readline (configure script option), 497
+<BR>--with-sendfile-support (configure script option), 497
+<BR>--with-smbmount (configure script option), 47, 498
+<BR>--with-smbwrapper (configure script option), 47, 498
+<BR>--with-spinlocks (configure script option), 498
+<BR>--with-ssl (configure script option), 498
+<BR>--with-sslinc (configure script option), 498
+<BR>--with-ssllib (configure script option), 498
+<BR>--with-swatdir (configure script option), 498
+<BR>--with-syslog (configure script option), 498
+<BR>--with-tdbsam (configure script option), 498
+<BR>--with-utmp (configure script option), 498
+<BR>--with-winbind (configure script option), 499
+<BR>workgroup option (smb.conf file), 447
+<BR>workgroup parameter (smb.conf file), 200
+<BR>workgroups, 26-29
+<BR> &nbsp; &nbsp; &nbsp;   adding first Samba server to, 396
+<BR> &nbsp; &nbsp; &nbsp;   defined, 15
+<BR> &nbsp; &nbsp; &nbsp;   problems related to, 29
+<BR> &nbsp; &nbsp; &nbsp;   spanning multiple subnets, 34
+<BR> &nbsp; &nbsp; &nbsp;   Windows 2000, 103
+<BR> &nbsp; &nbsp; &nbsp;   Windows 95/98/Me, 81
+<BR> &nbsp; &nbsp; &nbsp;   Windows NT, 93
+<BR> &nbsp; &nbsp; &nbsp;   Windows XP, 113
+<BR>Workstation service, installing on Windows NT, 89
+<BR>writable option (smb.conf file), 203, 447
+<BR>write cache size option (smb.conf file), 447
+<BR>write list option (smb.conf file), 286, 288, 447
+<BR>write ok option (smb.conf file), 203, 447
+<BR>write raw option (smb.conf file), 448
+<BR>writeable option (smb.conf file), 203, 447
+<P><A NAME="X"><B>X</B><A HREF="inx.html">[&nbsp;Top&nbsp;]</A>
+<BR>XFS filesystem, 37
+<BR>xinetd daemon, 53
+
+<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
+
+</body></html>
diff --git a/docs/htmldocs/using_samba/samba2_s.gif b/docs/htmldocs/using_samba/samba2_s.gif
new file mode 100644
index 0000000000..23d7e5ee64
--- /dev/null
+++ b/docs/htmldocs/using_samba/samba2_s.gif
diff --git a/docs/htmldocs/using_samba/samba2_xs.gif b/docs/htmldocs/using_samba/samba2_xs.gif
new file mode 100644
index 0000000000..e489480df6
--- /dev/null
+++ b/docs/htmldocs/using_samba/samba2_xs.gif
diff --git a/docs/htmldocs/using_samba/toc.html b/docs/htmldocs/using_samba/toc.html
new file mode 100644
index 0000000000..54d5c3f55f
--- /dev/null
+++ b/docs/htmldocs/using_samba/toc.html
@@ -0,0 +1,138 @@
+<html>
+<body bgcolor="#ffffff">
+
+<table border="0" cellpadding="4" cellspacing="4">
+<tr>
+<td>
+<img src="samba2_s.gif" border="0" height="190" width="145" alt="Using Samba, 
+2nd Edition" />
+</td>
+<td>
+<h2>Using Samba, 2nd Edition</h2>
+By Jay Ts, Robert Eckstein, and David Collier-Brown<br />
+2nd Edition, February 2003 <br />
+O'Reilly &amp; Associates, ISBN: 0-596-00256-4<br />
+<a href="http://www.oreilly.com/catalog/samba2/"><b>www.oreilly.com/catalog/samba2/</b></a>
+</td>
+</tr>
+</table>
+
+<blockquote>
+<h2>Table of Contents</h2>
+
+<P><B><a href="ch00.html">Preface</a></B>
+
+<P><B><a href="ch01.html">1. Learning the Samba</a></B>
+<BR> &nbsp; &nbsp; &nbsp;What Is Samba? 
+<BR> &nbsp; &nbsp; &nbsp;What Can Samba Do for Me? 
+<BR> &nbsp; &nbsp; &nbsp;Getting Familiar with an SMB Network 
+<BR> &nbsp; &nbsp; &nbsp;An Introduction to the SMB Protocol 
+<BR> &nbsp; &nbsp; &nbsp;Windows Workgroups and Domains 
+<BR> &nbsp; &nbsp; &nbsp;What's New in Samba 2.2? 
+<BR> &nbsp; &nbsp; &nbsp;What's New in Samba 3.0? 
+<BR> &nbsp; &nbsp; &nbsp;What Can Samba Do? 
+<BR> &nbsp; &nbsp; &nbsp;An Overview of the Samba Distribution 
+<BR> &nbsp; &nbsp; &nbsp;How Can I Get Samba? 
+
+<P><B><a href="ch02.html">2. Installing Samba on a Unix System</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Bundled Versions 
+<BR> &nbsp; &nbsp; &nbsp;Downloading the Samba Distribution 
+<BR> &nbsp; &nbsp; &nbsp;Configuring Samba 
+<BR> &nbsp; &nbsp; &nbsp;Compiling and Installing Samba 
+<BR> &nbsp; &nbsp; &nbsp;Enabling SWAT 
+<BR> &nbsp; &nbsp; &nbsp;A Basic Samba Configuration File 
+<BR> &nbsp; &nbsp; &nbsp;Firewall Configuration 
+<BR> &nbsp; &nbsp; &nbsp;Starting the Samba Daemons 
+<BR> &nbsp; &nbsp; &nbsp;Testing the Samba Daemons 
+
+<P><B><a href="ch03.html">3. Configuring Windows Clients</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Windows Networking Concepts 
+<BR> &nbsp; &nbsp; &nbsp;Setting Up Windows 95/98/Me Computers 
+<BR> &nbsp; &nbsp; &nbsp;Setting Up Windows NT 4.0 Computers 
+<BR> &nbsp; &nbsp; &nbsp;Setting Up Windows 2000 Computers 
+<BR> &nbsp; &nbsp; &nbsp;Setting Up Windows XP Computers 
+
+<P><B><a href="ch04.html">4. Windows NT Domains</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Samba as the Primary Domain Controller 
+<BR> &nbsp; &nbsp; &nbsp;Adding Computer Accounts 
+<BR> &nbsp; &nbsp; &nbsp;Configuring Windows Clients for Domain Logons 
+<BR> &nbsp; &nbsp; &nbsp;Logon Scripts 
+<BR> &nbsp; &nbsp; &nbsp;Roaming Profiles 
+<BR> &nbsp; &nbsp; &nbsp;System Policies 
+<BR> &nbsp; &nbsp; &nbsp;Samba as a Domain Member Server 
+<BR> &nbsp; &nbsp; &nbsp;Windows NT Domain Options 
+
+<P><B><a href="ch05.html">5. Unix Clients</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Sharing Files on Windows 95/98/Me 
+<BR> &nbsp; &nbsp; &nbsp;Sharing Files on Windows NT/2000/XP 
+<BR> &nbsp; &nbsp; &nbsp;smbclient 
+<BR> &nbsp; &nbsp; &nbsp;smbfs 
+<BR> &nbsp; &nbsp; &nbsp;smbsh 
+<BR> &nbsp; &nbsp; &nbsp;smbutil and mount_smbfs 
+
+<P><B><a href="ch06.html">6. The Samba Configuration File</a></B>
+<BR> &nbsp; &nbsp; &nbsp;The Samba Configuration File 
+<BR> &nbsp; &nbsp; &nbsp;Special Sections 
+<BR> &nbsp; &nbsp; &nbsp;Configuration Options 
+<BR> &nbsp; &nbsp; &nbsp;Server Configuration 
+<BR> &nbsp; &nbsp; &nbsp;Disk Share Configuration 
+<BR> &nbsp; &nbsp; &nbsp;Networking Options with Samba 
+<BR> &nbsp; &nbsp; &nbsp;Virtual Servers 
+<BR> &nbsp; &nbsp; &nbsp;Logging Configuration Options 
+
+<P><B><a href="ch07.html">7. Name Resolution and Browsing</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Name Resolution 
+<BR> &nbsp; &nbsp; &nbsp;Browsing 
+
+<P><B><a href="ch08.html">8. Advanced Disk Shares</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Filesystem Differences 
+<BR> &nbsp; &nbsp; &nbsp;File Permissions and Attributes on MS-DOS and Unix 
+<BR> &nbsp; &nbsp; &nbsp;Windows NT/2000/XP ACLs 
+<BR> &nbsp; &nbsp; &nbsp;Name Mangling and Case 
+<BR> &nbsp; &nbsp; &nbsp;Locks and Oplocks 
+<BR> &nbsp; &nbsp; &nbsp;Connection Scripts 
+<BR> &nbsp; &nbsp; &nbsp;Microsoft Distributed Filesystems 
+<BR> &nbsp; &nbsp; &nbsp;Working with NIS 
+
+<P><B><a href="ch09.html">9. Users and Security</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Users and Groups 
+<BR> &nbsp; &nbsp; &nbsp;Controlling Access to Shares 
+<BR> &nbsp; &nbsp; &nbsp;Authentication of Clients 
+<BR> &nbsp; &nbsp; &nbsp;Passwords 
+<BR> &nbsp; &nbsp; &nbsp;Authentication with winbind 
+
+<P><B><a href="ch10.html">10. Printing</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Sending Print Jobs to Samba 
+<BR> &nbsp; &nbsp; &nbsp;Printing to Windows Printers 
+
+<P><B><a href="ch11.html">11. Additional Samba Information</a></B>
+<BR> &nbsp; &nbsp; &nbsp;Time Synchronization 
+<BR> &nbsp; &nbsp; &nbsp;Magic Scripts 
+<BR> &nbsp; &nbsp; &nbsp;Internationalization 
+<BR> &nbsp; &nbsp; &nbsp;Windows Messenger Service 
+<BR> &nbsp; &nbsp; &nbsp;Miscellaneous Options 
+
+<P><B><a href="ch12.html">12. Troubleshooting Samba</a></B>
+<BR> &nbsp; &nbsp; &nbsp;The Tool Box 
+<BR> &nbsp; &nbsp; &nbsp;The Fault Tree 
+<BR> &nbsp; &nbsp; &nbsp;Extra Resources 
+
+<P><B><a href="appa.html">Appendix A. Example Configuration Files</a></B>
+
+<P><B><a href="appb.html">Appendix B. Samba Configuration Option Quick Reference</a></B>
+
+<P><B><a href="appc.html">Appendix C. Summary of Samba Daemons and Commands</a></B>
+
+<P><B><a href="appd.html">Appendix D. Downloading Samba with CVS</a></B>
+
+<P><B><a href="appe.html">Appendix E. Configure Options</a></B>
+
+<P><B><a href="appf.html">Appendix F. Running Samba on Mac OS X Server</a></B>
+
+<P><B><a href="appg.html">Appendix G. GNU Free Documentation License</a></B>
+
+<P><B><a href="inx.html">Index</a></B>
+</blockquote>
+
+</body>
+</html>
author	bubulle <bubulle@alioth.debian.org>	2010-04-06 18:12:47 +0000
committer	bubulle <bubulle@alioth.debian.org>	2010-04-06 18:12:47 +0000
commit	c038a4e9c09ba4ac77d885ac0afee418f41b8891 (patch)
tree	f5b2444727ff995f46dabbbf94863e9926501444 /docs/htmldocs
parent	9e2f5a6ab663f7a111832217c527508c75ddae8a (diff)
download	samba-c038a4e9c09ba4ac77d885ac0afee418f41b8891.tar.gz